RNP authorization required: what the approval covers, and what it leaves to you

Pilots in a cockpit navigating a tight RNP approach in mountainous terrain at dusk, with the aircraft's navigation display showing a constrained path.

This is a common scenario in constrained terrain: a final RNP value markedly tighter than on an ordinary approach, two fixed-radius turns wedged between two ridgelines, a reduced missed-approach climb gradient, and a temperature range outside of which the procedure is prohibited. The crew is qualified, the aircraft is on the list, the operator holds the specific approval. Across these four objects — aircraft, crew, operator, procedure — what the authority actually approved and what remains intact once the trajectory is flown do not coincide.

“Authorization required” does not describe difficulty, but the burden of proof

Within performance-based navigation, most specifications are used without any particular procedure: aircraft eligibility falls under airworthiness, training is part of the standard syllabus, and the operator has nothing to submit for case-by-case approval. The RNP approach with authorization required is the exception — not because it is harder to fly, but because the procedure design has already consumed the margins.

On an ordinary RNP approach, the designer protects an area whose half-width equals twice the RNP value, to which, in the general case, a buffer zone is added: an aircraft that exits containment still encounters evaluated airspace before encountering an obstacle. On an authorization-required procedure, this buffer disappears — obstacle evaluation stops at twice the RNP value. Containment is no longer a margin laid on top of protection: it is the protection.

Obstacle evaluation areas comparedCross-section view of the two regimes. At the top, the ordinary RNP approach: the evaluated area, twice the RNP value wide on either side of the track, is further doubled by a buffer zone drawn in dashes. At the bottom, the authorization-required approach: the same twice-RNP-value area, but nothing beyond it — obstacles come right up against the edge.buffer zone2 × RNPOrdinaryapproachno bufferAuthorisationrequired
Containment is no longer a margin laid on top of protection: it is the protection. Under the ordinary regime, the evaluated area of twice the RNP value is still surrounded by a buffer. Under the authorization-required regime, evaluation stops at the edge: exiting containment is no longer cushioned by airspace already assessed.

On an ordinary RNP approach, there’s extra safety space around the flight path. But on an authorization-required approach, that extra space is gone. The flight path itself is the only safety margin, so staying exactly on it is critical.

An Airbus A320 flying an RNP AR approach to an airport in the Andes with a 0.1 NM RNP value. The procedure has no buffer zone, so if the aircraft deviates more than 0.2 NM from the centerline, it could hit an obstacle. The crew must monitor their position very closely, especially during fixed-radius turns where bank angles are tight.

The safety case therefore no longer rests on the geometry of the airspace but on a demonstration: the total system error stays within one RNP value for at least 95% of the time, and the probability of exceeding twice that value remains extremely low — design criteria reason on an order of magnitude close to 10⁻⁷. It only holds if the aircraft, its configuration, the way the crew holds the track, and the quality of the coding are all known. Hence an approval that bears on a combination: remove a single element and it becomes inoperative for that day’s flight, with no warning light coming on.

The four objects of the approval, and what each one commits

The aircraft. Eligibility is assessed at configuration level, not at type level: it stems from a manufacturer declaration, the approved flight manual, or operational suitability data, and targets a given avionics standard. It covers sensor and computer redundancy, the required position source — many installations mandate a GNSS-only position —, the ability to fly a fixed-radius turn, alerting on loss of the function, the assumption of coupling to an autopilot, and vertical guidance whose temperature envelope is published.

The crew. Qualification is a standalone module, not a paragraph within type training: fixed-radius turns, handling a performance alert, temperature limits, reduced missed-approach climb gradient, degraded cases. It includes recurrent currency, and a lapsed currency date removes access to the procedure on an aircraft that is otherwise perfectly eligible.

The operator. This is the heaviest and least visible part from the flight deck: procedures written into the operations manual, amendment of the minimum equipment list, a data provider whose quality has been accepted, validation of each procedure before first use — coded track checked against the chart —, reporting of navigation deviations, continued airworthiness of the systems involved.

The procedure. The approval is not a blank check for every authorization-required procedure in the world. It states an envelope: minimum RNP value, fixed-radius turns authorized or not, reduced missed-approach climb authorized or not, temperature compensation covered or not, list of aircraft, sometimes a named list of procedures — some are specific to one operator and appear on no public chart.

What the approval attests, and what it leaves entirely up to you
Object What the approval attests What remains your responsibility
Aircraft A demonstrated-capable avionics configuration That the day’s aircraft actually matches it, technical tolerances included
Crew Specific training and checking, validated on a given date The currency deadline, actual conduct of the flight path
Operator Written procedures, a validated data chain, monitoring Applying the written procedure rather than habit, reporting the deviation
Procedure An envelope: minimum RNP, turns, missed approach, compensation That the day’s procedure fits within it, and that the coding matches the chart

The error budget, and exactly where your flying enters it

Total system error combines three contributions: navigation system error, the gap between true position and computed position; path definition error, the gap between the published path and the coded path; flight technical error, the gap between the coded path and the path actually flown. The second is supposed to be negligible, and it only is because someone validated the coding — that is the whole point of the requirement on the data provider. The third one is you, or the automation you are being asked to delegate to.

A helicopter pilot's hands on the controls with a large aircraft flying in a mountainous valley at dusk.
RNP approval ensures precision navigation in challenging terrain.

This third contribution is estimated under an assumption: an autopilot loop, a speed range, a bank-angle limit. The fixed-radius turn is where the assumption becomes binding. The radius is fixed by the procedure, and the bank angle needed to hold it grows with ground speed. A speed higher than expected, a tailwind in the turn, a high density altitude: the same coded path then demands a bank angle that the autopilot may refuse to command. Track-keeping there is a speed-management problem before it is a navigation problem.

Bank angle required on a fixed-radius turnRising curve of the bank angle needed to hold a fixed radius, as a function of ground speed. A horizontal dashed line marks the automation’s bank-angle limit; its intersection with the curve defines a maximum ground speed beyond which the coded path can no longer be held.automation limitbank angle requiredbank angleground speedV max
On a fixed-radius turn, the constraint is a speed constraint, not a navigation one. At a fixed radius, the bank angle required grows faster than ground speed. Beyond the point where it reaches the limit the automation will command, the coded path is no longer held: the deviation opens up with a navigation system in perfect working order.

The trap. On a fixed-radius turn, the deviation almost never comes from a navigation failure: it comes from excessive speed, an unanticipated wind, or a configuration set up late. Containment can be broken with a system in perfect working order and no alert on the screen. This is the case where lateral deviation must be monitored as a flying parameter, not as a navigation cue.

The vertical plane follows the same logic. Barometric vertical guidance builds its angle on the standard atmosphere: in cold temperatures, the flown path passes lower than nominal, and the deviation grows with height above the reference station. Published temperature limits are therefore not an editorial precaution — they are part of the envelope. A compensation function exists on some installations, but its use must itself be covered. And a barometric setting error shifts the entire vertical path.

Effect of a low temperature on barometric vertical guidanceSide view of the final segment. The nominal path, shown as a solid line, joins the threshold from the final fix. In cold temperatures, the path actually flown, shown dashed, passes lower: the gap between the two is greatest far from the airfield, where the height above the reference station is greatest, and closes to zero at the threshold.deviationfinal fixnominal pathin cold temperaturesthreshold
The barometric path flown in cold temperatures passes below the published path, and the deviation grows with height. It is therefore greatest at the start of the segment, where level flight is left, and closes to zero near the reference station. Published temperature limits bound precisely this effect.

The exact gap between an ordinary RNP approach and an authorization-required approach

Between the two regimes an intermediate specification has emerged, known as Advanced RNP, which brings scalable values and the fixed-radius turn without requiring specific approval, but keeps the ordinary approach’s criteria on the final segment. It does not close the gap: it provides the tools, not the reduced margins. An aircraft capable of fixed-radius turns is not, on that basis alone, eligible for the authorization-required regime.

The two RNP approach regimes: what actually changes
Element Ordinary RNP approach Authorization-required approach
Final RNP value Single, standardized value Published procedure by procedure, markedly tighter
Missed approach Ordinary missed-approach value Reducible value, subject to a separate authorization
Obstacle evaluation area Twice the RNP, plus a buffer zone Twice the RNP, with no addition
Radar vectoring Interception of a final course possible Flown as published; a fixed-radius turn cannot be intercepted
Approval regime No specific approval Specific approval, envelope and aircraft list
Training Standard syllabus Dedicated module and its own currency requirement
Navigation data General quality requirements Accepted provider, validation of each procedure

The relative weight of the four objects shifts with the type of operation. At an airline, the aircraft and training are standardized, avionics standards are homogeneous, and the constraint shifts toward document control: cycle validation, maintaining the procedure list, handling deviation reports. In business aviation or with a small fleet, the difficulty is reversed: two aircraft of the same type can carry different avionics standards, hence different eligibilities; coding validation and deviation tracking rest on very few people; and the approved envelope is often limited to a named list of procedures, which makes diverting to a nearby field something that needs careful preparation. In helicopter operations, the same requirements apply to shorter tracks, where the time between a deviation appearing and the decision to discontinue is correspondingly reduced.

When one piece of equipment is missing, the chain breaks silently

The minimum equipment list answers one question — can the flight depart? — and only that one. It does not answer the question of eligibility for the authorization-required regime, which rests precisely on the redundancy that the tolerance has just consumed. A perfectly legal departure with a navigation computer, a GNSS chain, or an autopilot unserviceable can remove access to the only usable approach at the destination: a different approach, different minimums, different fuel, sometimes a different destination.

The trap. A technical tolerance accepted at departure and an authorization-required approach planned at arrival form a combination that triggers no automatic refusal. The flight-planning system computes a route, air traffic control will offer the procedure, and nothing reminds anyone that the aircraft has left the approved configuration.

The right reflex. Treat eligibility as a five-point preparation check: the operator’s approval envelope, the day’s aircraft configuration against the technical tolerance, the navigation database cycle checked against the chart in use, the forecast temperature at the estimated arrival time against the published limits, the forecast availability of GNSS. None of these five checks can be caught up on after the initial approach fix.

Forecast availability deserves a clarification: the instantaneous status read on the flight deck says nothing about the situation at arrival time — a question addressed with a prediction tool fed by published satellite outages. The navigation database cycle imposes a less intuitive discipline: a procedure amended in the following cycle becomes unvalidated again until the operator revalidates it, and a changed altitude constraint or a re-coded turn cannot be seen just by reading the chart.

Decision matrix: where the degradation occurs, and what it implies
Event Before the initial approach fix After the final approach fix
Performance alert Do not engage; request another approach Discontinue per the published procedure: containment was the protection
Loss of a GNSS chain Reassess eligibility with the remaining redundancy Discontinue, unless explicit provision states otherwise
Autopilot disconnect Check whether manual flying is covered at this RNP Departure from the design assumption, not a simple mode change
Temperature below the published limit Unavailable without approved compensation To be excluded during preparation, not handled during descent

What the authorization does not cover, though it is often assumed to

The design publishes a gradient to hold in the event of a discontinued approach, established on the assumption of normal engine operation. It does not address a failure occurring at the worst possible moment: that demonstration belongs to the operator — performance analysis, a possible terrain-specific escape procedure, a mass limitation. A crew that assumes the approval has settled this point is conflating two separate matters, and it is the single costliest misunderstanding in mountainous terrain.

Nor does the authorization say anything about operating conditions other than temperature: it provides a track, not visibility. Operating minimums and visual references at the decision altitude fall under the all-weather regime. It says nothing about the decision to commit — fatigue, night over rising terrain, absence of radar coverage, fuel, a realistic alternate. And it does not bind air traffic control, which can offer a shortcut incompatible with the coded track: accepting it by reflex is enough to depart from the approved procedure.

One genuinely grey area remains: using an authorization-required procedure in planning, in particular as the reference approach at an alternate airfield. The logic of planning is not to rely on what may not be available, and a capability conditioned on an envelope is exactly that by construction. The answer is not improvised in the briefing room: it is written, or should be, in the approved documentation.

What to go and check in your own documentation

The useful reading does not start with the chart but with the operator’s specific approval sheet. Five things are to be found there: the minimum authorized RNP value, fixed-radius turns, reduced missed-approach climb, temperature compensation, and the list of aircraft with their avionics standard. These five lines define the real scope, often narrower than the fleet might suggest.

In the operations manual, four points deserve to be located before they are needed: the actions to take on an alert depending on position along the track, the relationship between technical tolerance and eligibility, the validation workflow for a new or amended procedure, and the deviation-reporting channel. This last one is the only mechanism through which an operator learns that a procedure flies poorly in practice; it only works if the deviation is reported even when nothing actually happened.

For anyone preparing a type rating or joining an operator serving demanding airfields, the subject changes the nature of the questions worth asking in a technical interview. Not ‘do you hold the approval’, but: down to what RNP value, with or without reduced missed-approach climb, across what part of the fleet, and who validates the coding at each cycle. The corresponding preparation is treated as a module in its own right — that is the logic behind FL330 training courses. A pocket of uncertainty almost always remains: manual flying, mixed fleets, temperature compensation, use in planning. Knowing which one is yours is worth more than assuming none remain.

The applicable regulations, the charts in force, and the operator’s approved documentation take precedence over this article, which sets out a mechanism and replaces neither the specific approval sheet, nor the operations manual, nor the approved flight manual.

Questions fréquentes

Does an RNP AR qualification obtained at one operator follow a pilot who changes airlines?

No. The specific approval is held by the operator, and crew qualification exists only within that operator’s approved training and checking programme. A change of airline requires going back through the new operator’s module and check, even on the same aircraft type. Prior experience shortens the learning curve; it transfers no entitlement.

Can an RNP authorization-required approach be flown by hand?

It depends on the aircraft’s eligibility declaration and on what the operations manual says. Under the tightest RNP values, the flight technical error budget is established on the assumption of coupling to the autopilot or of following a flight director: manual flying then falls outside the design assumption. The answer is found in the approved flight manual and the operator’s procedures, not in how easy it feels.

The minimum equipment list allows departure with a navigation computer unserviceable: does the RNP AR approach remain available?

No, unless the approved documentation explicitly states otherwise. Eligibility for the authorization-required regime rests on the redundancy that the technical tolerance has just consumed. The legality of the departure and the eligibility for the procedure are two separate questions: another approach must be selected at destination, with the corresponding minimums, fuel, and alternate.

What should be done if a navigation performance alert occurs after the final approach fix?

The crew discontinues per the published procedure, without attempting to diagnose during the descent. On an authorization-required procedure, the obstacle evaluation area stops at the containment boundary: there is no buffer zone behind the alert. This is precisely why that procedure is briefed before the approach, together with the planned missed-approach path.

Does the temperature compensation function exempt the crew from the limits published on the chart?

Only if the function is approved for the installation concerned and its use is covered by the specific approval and the operator’s procedures. Otherwise, the temperature limits shown on the chart are firm limits, and the procedure becomes unavailable outside that range. This is addressed during flight preparation, based on the forecast temperature at the estimated time of arrival.

Can an authorization-required procedure be used as the basis for alternate-airfield planning?

The answer lies in the operator’s approved documentation, which frequently restricts this use. The logic of planning is not to rely on a capability that may be unavailable, and a capability conditioned on an approval envelope is exactly that by construction. If the operations manual is silent on the point, it is better to ask the operator than to decide it in the briefing room.

Commentaires

Leave a Reply

Découvrez l’écosystème FL330

FL330, c’est toute l’aviation professionnelle — explorez nos autres espaces.