
Let’s pick this up right where the departure side of the story ends. We’ve already talked about how aircraft get sequenced for take-off, so now I want to walk you through what happens when that sequence breaks down, and then how we handle aircraft that are arriving.
First, delays. It is inevitable that at some point a delay will occur — that’s the opening line of paragraph 16.47, and it’s a realistic statement. When a delay happens, flights may be cleared to take off in an order based on the estimated departure time. So the default rule is: you line them up by when they were estimated to depart. But deviation from that order is permitted, and it’s permitted for two specific reasons. One, to facilitate the maximum number of departures with the least average delay — that’s an efficiency-driven reordering. Two, in response to requests from operators — so an airline can ask for a change. Now, there’s a hard duty on the ATC unit here: ATCUs — that’s Air Traffic Control Units — should inform operators when anticipated delays exceed 30 minutes. So the moment a delay is expected to go past half an hour, the operator must be told. That’s a threshold you need to remember: 30 minutes.
Now let’s move to the arrival side, paragraph 16.48. Arriving IFR aircraft — that’s Instrument Flight Rules traffic — may be cleared to make a visual approach. But that clearance is conditional. There are three conditions, and any one of them can be satisfied. First, the pilot can maintain visual reference to terrain. Second, the reported ceiling is at or above the approved initial approach level. Third, the pilot reports that at any time during an instrument approach the meteorological conditions are such that there is a reasonable assurance that an approach and landing will be made visually. So it’s a three-way OR: terrain in sight, ceiling high enough, or the pilot’s own report that conditions guarantee a visual landing is reasonably assured.
Then paragraph 16.49 — this is the separation core. ATC will provide separation between aircraft making a visual approach and all other arriving or departing traffic. So even though the approach is visual, the controller still owns the separation responsibility. And for arriving IFR traffic in IMC — that’s Instrument Meteorological Conditions — the Approach Controller will transfer control of the aircraft. The excerpt cuts off mid-sentence there, but the key point is the handover of control from the Approach Controller for IFR arrivals in IMC.
Let me tie the whole picture together. On departure, the Ground Movements Planner sequences aircraft so the Off Blocks Time translates into the slot time, and the aircraft arrive at the holding point in the correct order. On arrival, the Approach Controller manages the transfer for IFR traffic in IMC, and separation is maintained against all other traffic. The visual approach is the bridge — it lets an IFR aircraft go visual, but only under those three conditions, and ATC still separates it from everything else.
One more thing I want to make sure you’ve got, because it’s easy to miss: the departure sequence paragraph mentions that departure may be expedited by suggesting a take-off direction that is not into wind. That’s a non-standard suggestion, and the decision rests with the PIC — the Pilot in Command — to accept it or not. So the controller can suggest, but the pilot decides. That’s a clear division of authority.
So the three numbers and thresholds to hold onto: 30 minutes for the delay notification, the three conditions for a visual approach clearance, and the PIC’s authority over the non-into-wind take-off direction. That’s the departure and arrival picture.
This is one saved preview. Continue from this exact book or paper with BlueFlash voice AI.
Continue in BlueFlash