Separation — Page 303, Lesson 401

We're moving into a new part of the separation rules now — the high-tech end of things. I want to walk you through longitudinal separation based on RNAV where RNP is specified, and then the general rules for reducing separation minima. First, let's unpack the acronyms, because they're the whole game here. RNAV is area navigation — it lets an aircraft fly any desired track within the coverage of ground or space-based navigation aids, rather than being limited to flying directly to or from a ground station. RNP is Required Navigation Performance — a statement of the navigational performance accuracy needed within a particular airspace. So when I say "RNP RNAV environment," I mean an area where the aircraft's area navigation system must meet a specific, certified accuracy standard. Now, the core idea of this section: when aircraft are cruising, climbing, or descending on the same track in an RNP RNAV environment, the controller may use the reduced separation standards in the table instead of the normal ones. There are two levels, and each has its own set of requirements. Let's look at the first row. RNP Type 20. That means the aircraft must maintain a navigational accuracy of 20 nautical miles. For this, you need direct pilot/controller communications, procedural position reports, and distance verification at least every 60 minutes. With all that in place, the separation standard is 80 nautical miles. Now the second row. RNP Type 10 — accuracy of 10 nautical miles. Here you still need direct pilot/controller communications and procedural position reports, but the distance verification is more frequent: at least every 30 minutes. And the separation standard drops to 50 nautical miles. So you see the pattern — tighter navigational accuracy and more frequent verification buy you a smaller separation minimum. Now, there's a critical operational rule attached to that 50 NM minimum. During the application of the 50 NM minimum, if an aircraft fails to report its position, the controller must take action within 3 minutes to establish communications. That's a hard deadline — three minutes. If communication has not been established within 8 minutes from that point, then alternative separation is to be applied. So you have a two-stage response: act at 3 minutes, and if you haven't re-established contact by 8 minutes, you abandon this reduced standard and apply a different, larger separation. There's one more important point about vertical movement. An aircraft may climb or descend through an occupied level once it has been established that the aircraft concerned have passed. In other words, you can't just start a climb through another aircraft's level — you must first confirm, using the position reports, that the aircraft have actually passed each other. Only then is the level change permitted. Now let's move to the second part: reduction in separation minima. This is the general principle that the separation minima may be reduced as determined by the appropriate ATS authority — that's the Air Traffic Services authority — after prior consultation with the aircraft operators, as appropriate. So it's not automatic; it's a decision made by the authority, and the operators are consulted. There are several circumstances under which this reduction may be granted. Let me walk through each one. First: when special electronic or other aids enable the pilot-in-command of an aircraft to determine accurately the aircraft's position, and when adequate communication facilities exist for that position to be transmitted without delay to the appropriate air traffic control unit. So the pilot must be able to know exactly where they are, and get that information to the controller quickly. Second: when, in association with rapid and reliable communication facilities, radar-derived information of an aircraft's position is available to the appropriate air traffic control unit. Here the position information comes from radar, not from the pilot, but you still need fast, reliable communications. Third: when special electronic or other aids enable the air traffic controller to predict rapidly and accurately the flight paths of an aircraft, and adequate facilities exist to verify frequently the actual aircraft positions with the predicted positions. So the controller can forecast where the aircraft will be, and check that forecast against reality on a regular basis. Fourth: when RNAV-equipped aircraft operate within the coverage of electronic aids that provide the necessary updates to maintain navigational accuracy. The aircraft's area navigation system needs a continuous stream of updates from ground or space aids to keep its accuracy. And finally, the fifth circumstance is in accordance with RAN agreements — that's Regional Air Navigation agreements — after prior consultation with the aircraft operators. This one has two conditions. First, special electronic, area navigation, and other aids enable the aircraft to closely adhere to their current flight plans. And second, the air traffic situation is such that the conditions regarding communications between pilots and the appropriate ATS unit or units need not necessarily be met to the degree specified therein, in order to maintain an adequate level of safety. In plain terms: the aircraft can stick to its filed flight plan very precisely, and the traffic situation is so benign that you can relax the strict communication requirements and still keep safety at an adequate level. So the whole philosophy here is that separation minima are not fixed in stone. If you can prove — through better navigation accuracy, better surveillance, or better communication — that you know where the aircraft are with more certainty, you can safely reduce the distance between them. The authority grants that reduction, but only under these specific, controlled conditions. That's the heart of this section: the RNP RNAV table gives you specific reduced standards with their communication and verification requirements, and the general rules tell you the circumstances under which any reduction may be permitted.