Imagine you have a trip coming up for Amsterdam. Here’s your schedule and general flight info:
Tail number/Call sign: NXXXX Type of flight: Private non-revenue Crew: 3 Passengers: 7 Purpose of flight: Business
KSAT 10 August // 0515 UTC (0015 local)
CYQX 10 August // 1045 UTC (0815 local)
CYQX 10 August // 1130 UTC (0900 local)
EHAM 10 August // 1630 UTC (1830 local)
Now here’s the information on airport operations for EHAM:
THE FOLLOWING PROCEDURE CONCERNS SLOT ALLOCATION FOR GA:BASED ON THE SLOT POOL, TIME BRACKETS AVAILABLE FOR GA ARE CALCULATED ON AN AVERAGE DAY BASIS AND WILL BE PUBLISHED BY NTM.
AIRCRAFT EXPECTED TO ARRIVE/DEPART WITHIN -15/+15 WITH ASSIGNED RESERVATION TIME.
GA, OPERATING WITHIN THE TIME BRACKETS AS PUBLISHED IN THE LATEST NOTAM, DON’T NEED TO APPLY FOR A SLOT. FOR ARRIVAL/DEPARTURE OUTSIDE OF THESE BRACKETS MUST SUBMIT A REQUEST FOR THE ALLOCATION OF AVAILABLE ADHOC SLOTS TO SACN AND AWAIT APPROVAL BEFORE OPS. SUBMIT REQUESTS 3 DAYS OR LESS BEFORE OPERATIONS.
AMBULANCE FLIGHTS MAY APPLY FOR AN EXEMPTION DURING PERIODS WHEN THE AIRPORT IS CLOSED TO GA (SEE CURFEW).
THE FOLLOWING NOTAM CONCERNS SLOT ALLOCATION TIME BRACKETS:
Q) EHAA/QFAXX/IV/NBO/A /000/999/5218N00446E005
A) EHAM B) 1203250100 C) 1210270200
E) REF: AIP EHAM AD 2.20 (LOCAL TRAFFIC REGULATIONS)
TIME BRACKETS (AVBL CAPACITY) FOR GA
GA FLTS: ARR 0520/0600 0720/0820 1100/1640 1800/2040
DEP 0500/0715 0920/1020 1200/1815 1920/2040
Based on this information, do you need to obtain an airport slot when operating to EHAM at 1600 UTC? Answer below and come back next Friday to see if your answer is correct!
Thank you for reading Operational Insight blog and participating.
This is a group account for the people busily trying to make this blog the best it can be for you and the rest of the business-aviation community. If you have questions or comments about this blog, you can reach us at firstname.lastname@example.org.
If you enjoyed this article, subscribe to receive more just like it.
Operational Insight is a moderated blog. Before adding your comments, please read our Comment Policy.