Performance-Based Navigation Approval: Fleet, Crews, Documentation

Antenne de navigation par satellite installée sur le dessus d'un fuselage, ligne de rivets et joint visibles

Three used aircraft join the fleet: same type, same livery, same line in the operations specifications. The flight manual carries the expected performance-based navigation entry, the approval line names a type, no one lingers over it. Six weeks later, an internal audit finds that the delivered batch carries an earlier computer software version, without the constant-radius-to-fix turn function. These three aircraft flew arrivals they had no right to fly, with no warning light illuminated and no parameter out of tolerance. The approval was not false: it simply did not cover what everyone believed it covered.

What the specification requires, and of whom it requires it

A navigation specification is not a list of equipment. It is a set of requirements of three kinds, and each has its own producer of proof.

  • Requirements of performance — accuracy, integrity, continuity, and for the tighter specifications an onboard monitoring function paired with an alert. These are demonstrated on the design side, for a defined configuration, and never for a type in general.
  • Requirements functional — what the system must be able to compute, sequence and display: admitted leg types, cross-track deviation resolution, selection of the performance value, go-around management. These are read element by element in the aircraft’s definition.
  • Requirements operational — what the operator must write down, what the crew must know, what is checked before departure and what is monitored in flight.

From this follows the first rule of reading: a specification qualifies an aircraft-crew pair, never an aircraft alone. A perfectly capable aircraft, entrusted to crews whose training programme does not name the specification, makes nothing eligible; and a remarkably well-trained crew does not make up for a function missing from the computer. Demonstrating eligibility therefore consists of assembling three pieces of proof that do not sit in the same binders, are not held by the same departments and do not expire at the same pace. This mismatch in pace produces nearly all of the discrepancies found in oversight.

A navigation spec is like a recipe: it lists what the plane and crew must do together. The plane alone isn’t enough—you need trained pilots too. If either part is missing, the whole thing fails.

An A320 with RNP 0.3 approval but missing the constant-radius-to-fix turn function flew an approach it shouldn’t have. No alarms sounded, but the aircraft wasn’t properly approved for that procedure.

The proof for the aircraft: what the flight manual says, what it does not say

On the aircraft side, the proof takes a brief form: an eligibility statement, in the flight manual, in a supplement, or in a manufacturer document the manual refers to. This statement names the specifications held. Three precautions in reading are essential, and each has already cost someone a finding.

The statement is granular. Capability for the RNP approach down to lateral minimums does not carry capability for barometric vertical guidance, which in turn does not carry capability for satellite-based augmentation guidance. These three lines rest on neither the same sensors, nor the same temperature assumptions, nor the same demonstrations. They often appear in the same paragraph, which invites reading them as a single block.

The statement is conditional. It holds for a configuration: receiver part number, computer software version, sensor fit, display means, sometimes even the presence of a second system. Change any one of these elements through an approved modification, a retrofit or a removal, and the statement does not automatically follow. It must be checked that it still holds true.

The statement is not an authorisation. It says what the aircraft can do; it does not say what the operator is entitled to do with it. Two files, two owners, two life cycles. The point of contact between them is a document no one holds by default: the list of eligible aircraft, registration by registration and specification by specification. When this list does not exist, or when it is kept by type, the operator has a fleet it believes is homogeneous and a proof that is not.

The point of junction: what the aircraft does not do, the crew must hold

This is where the two halves of the file meet, and it is the mechanism that an ordinary regulatory reading leaves in the shadows. Every functional requirement of the specification has two possible outcomes: either the function exists on board, and the proof is a document; or it is missing, and the operator has only two ways out — restrict the operation, or produce a procedural mitigation.

A procedural mitigation exists only under three cumulative conditions: it is written into the operating documentation, it is taught, and it is checked. An instruction known to everyone but absent from the manual is not a mitigation; nor is a written procedure that nobody has ever seen in a training session. A few examples of this shift of burden: the absence of automatic availability prediction imposes a check during flight preparation; the absence of a usable-scale cross-track deviation display imposes a substitute method and a numerical limit not to be exceeded; the absence of a constant-radius-to-fix turn imposes a restriction on procedures, hence a list kept up to date; a single sensor imposes a constraint on the choice of alternate aerodrome.

The practical consequence is stark: two aircraft of the same type, under the same approval line, do not demand the same work on the flight deck. The boundary between what the machine guarantees and what the crew must hold shifts with the configuration, while the specification itself has not moved an inch.

How requirements are shared between the aircraft and the crew, by configurationSchematic diagram. Two horizontal bars of equal length represent the full set of requirements of a single navigation specification. On the top bar, a recent configuration, onboard functions cover the largest share and procedures and the crew hold only a narrow remainder. On the bottom bar, an older configuration, the boundary has shifted to the left: the aircraft’s share shrinks and the crew’s share grows accordingly. The required specification is identical in both cases; only the proportions drawn are illustrative.One specification, two different splitsaircraft functionsprocedures and crewrecent config.older config.the boundary shiftsthe requirement itself does not move
The specification is fixed; the split of the work is not. What the computer does not guarantee falls to the procedure and to the crew. It is this variable share, not the acronym printed on the approval line, that determines the actual workload on the flight deck. The split shown is a reading principle, not a measurement.

Training: what the programme must demonstrate

A training programme that teaches how to fly the approach does not demonstrate much. What the demonstration calls for is explicit coverage of the targeted specification, across five strands that each leave a verifiable trace.

Two pilots in a cockpit at night, one using a tablet with a navigation map.
Pilots use modern tech for precise navigation, ensuring safer, more efficient flights.
  • Ground knowledge. What the performance value bounds and what it does not, the difference between current accuracy and containment, how onboard monitoring works and the exact meaning of its alert, the nature of a navigation database and its limits, failure modes and their signatures.
  • Procedures. Loading and checking the procedure against the chart, verifying the leg type, deviation limits to respect, actions to take on an alert, on sensor loss, on non-sequencing.
  • Practice. Simulator sessions covering the specification and its degraded cases, with scenarios that actually generate the alert rather than merely describing it.
  • Differences. Any new specification, any new fleet configuration, any notable computer software evolution calls for differences training — this is the strand most often omitted, because the aircraft keeps its name.
  • Checking and the record. A point checked during periodic proficiency checks, and a record allowing one to say, for a given crew on a given date, that it is covered.

Two groups regularly fall outside the scope even though they carry part of the file: flight preparation staff, who handle availability prediction, alternate policy and procedure restrictions; and maintenance, who hold the configuration and load the data. A procedural mitigation entrusted to flight preparation is only valid if that team has been trained on what it is checking. Finally, traceability must lead back to the specification: a generic line about area navigation in the approved programme is not proof, it is an intention. The corresponding preparation is handled as an identified module, in line with the FL330 training programmes.

The right instinct. Keep a three-column correspondence table: the specification’s requirement, the means that satisfies it (onboard function or written procedure), and the training session and check that covers it. It fits on two pages, it can be reviewed in ten minutes, and it immediately reveals the two defects that no manual audit ever catches: the requirement covered by a function today’s aircraft does not have, and the written mitigation that no one teaches.

Aircraft capability and training coverage: the four situationsTwo-way matrix. In rows, the aircraft’s capability: complete or partial. In columns, coverage by the training programme and written procedures: on the programme or absent. Complete capability with training on the programme yields a tenable approval. Complete capability without training yields an unusable capability. Partial capability with training yields eligibility with written restrictions. Partial capability without training yields no eligibility at all, and it is the box most often flown without anyone knowing it.Two proofs, four situationstraining on the programmetraining absentcomplete capabilitypartial capabilitytenable approvaland defensiblecapabilityunusableeligiblewith restrictionsnot eligibleand often flown anywayrows: what the configuration can docolumns: what the programme covers
A capability without training cannot be used, a training without capability makes up for nothing. Three boxes out of four are visible: the operator exploits, forgoes, or restricts. The fourth signals nothing at all — the aircraft flies, and no one on board knows what is missing.

One proof, two regulatory vehicles

The content of the demonstration varies little from one system to another; what varies is the vehicle that carries it. On the European side, the recast of the airspace usage requirements has narrowed the scope of specific approval: most navigation specifications are no longer subject to it. Only the most demanding — the RNP authorisation-required approach chief among them — remain listed as a specific approval annexed to the certificate. For the others, the line has disappeared from the document, not the demonstration: it has simply moved inside the operator’s ordinary file, under the responsibility of its compliance monitoring function.

This is a treacherous shift. As long as the approval was a title to be applied for, someone had to build a file and defend it before an inspector. Once the line is removed, the same proof must still exist, but nothing any longer forces it to be assembled by a given date. On the day of an audit, the operator must produce what an approval file used to contain — the list of eligible aircraft, the correspondence of requirements, the training programme, the data chain — without ever having gathered it in one place.

On the American side, the logic remains that of an authorisation line in the operations specifications, issued by the team attached to the certificate, with an application file whose content is described by an advisory circular and an authorisation naming the fleet concerned. The difference is not one of severity: it is a difference of timing. Where one system checks at entry, the other checks continuously.

By specification, what the proof must contain
Specification What grounds the aircraft’s eligibility What training must cover specifically What most often brings it down
Area navigation in continental cruise Eligibility statement citing the admitted sensors, satellite-based or conventional, and the limits on the use of the inertial reference unit Recognising the active sensor, knowing how to revert to conventional navigation Removal of an admitted sensor, undocumented reversion
Area navigation in departure and arrival Area navigation functions, cross-track deviation display at a usable scale, admitted position sources Loading and checking the procedure, deviation limit, actions in case of loss Database not loaded, procedure redrawn without review
RNP approach, lateral then vertical minimums Distinct statement by minimums family: lateral only, barometric guidance, satellite-based augmentation guidance Reading the minimums block, effect of temperature, actions on alert and on go-around Confusion between the three lines, training deadline exceeded
RNP authorisation-required approach Full demonstration, including go-around and engine failure cases, often accompanied by handling conditions Dedicated programme, specific check, sometimes crew restriction Crew not covered for the day’s procedure, aircraft not compliant with the file

What brings down an approval already obtained

An approval is a statement about a configuration, on a given date. Yet each of its components drifts at its own pace: the computer’s software with each campaign, the fleet with each delivery, the data at the pace of the aeronautical publication cycle, every twenty-eight days, crew coverage at the pace of individual deadlines, published procedures at the pace of airspace redesigns. An approval therefore almost never fails all at once: it develops holes.

Seven ordinary events, and what they actually affect
Event What changes in the proof What must be redone Visible in flight?
Computer software update The configuration cited by the eligibility statement is no longer that of the aircraft Revalidate the statement, review differences training No
Entry of a used aircraft An individual example of the type may carry a different definition Check the statement example by example, update the eligible-aircraft list No
Removal or failure of a sensor Performance is no longer held by the same architecture Requalify or restrict, document the fallback Sometimes
Application of a technical tolerance The aircraft remains operable, but not necessarily for the targeted specification Read the associated operating procedure before departure, pass on the restriction Only if the crew rereads the tolerance
Data cycle not loaded The procedure flown is no longer the one published Prohibit use, regularise the loading Yes, the computer flags an outdated database
Training deadline exceeded The crew is no longer covered for the specification Reschedule, restrict the assignment in the meantime No
Published procedure redesigned The restrictions held by the operator concern an object that no longer exists Review the list of authorised procedures and the coding No

The trap. The technical tolerance is read at departure, by a team handling a dispatch issue, and forgotten three legs later by a crew preparing an arrival. Yet a minimum equipment list entry does not merely make the aircraft dispatchable: it often carries an operating procedure that excludes certain navigation specifications. Nothing on board will recall this exclusion at the approach briefing, and the aircraft will fly the procedure it no longer has the right to fly, perfectly.

What the approval line states and what real capability is worth over timeGraph over time. A constant, horizontal dashed line represents the recorded approval, which never varies. A solid line represents actual capability: it first follows the dashed line, drops sharply at a computer software version update, rises again after revalidation, drops again when a data cycle is not loaded, then rises again after regularisation. Neither dip is visible anywhere on the approval document.capabilityapproval lineactual capabilitycomputer software versioncycle not loadedtime
The document never goes down; capability does. Dashed line: the approval as recorded. Solid line: what the fleet actually holds. The two dips are periods of uncovered operation, and neither one shows up on the certificate.

Among these forms of drift, that of the data deserves separate treatment, because it is the only one that touches the approval on every cycle and the only one the operator does not produce itself. The chain has four links: the aeronautical information service that publishes, the supplier that codes under a letter of acceptance issued by the authority, the operator that orders, adapts and loads, the computer that renders it. A performance-based navigation approval assumes that all four hold, and the operator directly controls only the third.

What the aircraft detects is narrower than one might think. A computer can tell that a database is outdated, because it compares a date. It cannot tell that coding is wrong: a point placed slightly off, a leg coded as a different type, a missing constraint altitude produce no alert at all. Checking against the published chart therefore remains a human operation, which is why checking the loaded procedure appears among the normal procedures and not among the abnormal ones. Add to this the data adapted by the operator, which falls outside the scope controlled by the supplier, and you get the link where an entire fleet can become non-compliant overnight without a single warning light coming on.

What must be produced within twenty minutes

The most honest test an operator can apply to itself is not to reread its manual: it is to ask what it would produce within twenty minutes if an inspector requested proof of eligibility for a given specification. Five items should come out without a search: the list of eligible aircraft by registration and by specification, with the date of the last check; the eligibility statement and the configuration conditions it is contingent upon; the correspondence table between requirements, means and sessions; the training records showing which crews are covered today; and finally the trace of the data chain, from supplier to loading, including the current cycle. If any one of these items requires a phone call, it does not exist.

Two grey areas remain, and it is better to name them than to discover them. The first is the aircraft that came from another regulatory system, whose eligibility statement was drafted in a different certification language and does not map exactly onto the specification one wants to operate. The second is the mixed fleet: a crew alternating between two configurations within the same week holds two sets of procedures, and this is precisely what the correspondence table makes visible before an audit does.

For anyone preparing a checkride or a technical interview, the angle has changed. Less and less is being asked to recite what a specification requires; more and more is being asked where, on today’s aircraft, the boundary lies between what the machine guarantees and what remains with the crew. This is the question field discussions come back to most often on the FL330 professional forums, and it is the only one that separates a learned answer from one truly held.

This article describes a mechanism and carries no binding value. In case of divergence, the applicable text, the operations specifications annexed to the certificate, the aircraft’s flight manual and the operator’s approved documentation prevail over what has just been written.

Questions fréquentes

Does a capability statement in the flight manual suffice to operate a given specification?

No. The eligibility statement says what the aircraft can do in a defined configuration; it does not say what the operator is entitled to do with it. It must be paired with written procedures, a training programme that names the specification, and a controlled data chain. These elements belong to the operator’s file, not the manufacturer’s.

When a specification no longer requires a specific approval, does the demonstration disappear along with the line?

No, it only changes location. The proof that used to be examined by the authority at the time of application must continue to exist inside the operator’s ordinary file and be maintained by its compliance monitoring function. The practical risk is that it is never assembled, for lack of a deadline forcing it. The useful test is to ask who, by name, would hold the list of eligible aircraft if an inspector requested it tomorrow.

Is a used aircraft of the same type automatically covered by the fleet's approval?

No. Eligibility attaches to an individual example’s definition: computer software version, receiver part number, sensor fit, display means. Two examples of the same type can differ on one of these lines and not hold the same functions. The check is done registration by registration before first operation.

Does the computer warn when the database no longer matches the chart?

It warns of an outdated database, because it compares a validity date. It does not detect a coding error: a point placed slightly off, a different leg type, or a missing constraint altitude pass without any alert. That is why checking the loaded procedure against the published chart appears among the normal procedures.

Can a technical tolerance applied at departure remove a navigation specification?

Yes, and it is a frequent case. A minimum equipment list entry can make the aircraft dispatchable while excluding, through its associated operating procedure, certain navigation operations. The restriction must be passed on to the crew and reread at the approach briefing, because nothing on board will recall it.

Does training for a specification transfer from one type to another?

The theoretical part transfers largely, since the notions of accuracy, containment and alerting do not change. The procedural part does not transfer: it depends on the functions actually present and the written mitigations used to make up for their absence. A change of type, and sometimes a mere change of configuration, therefore calls for differences training.

Commentaires

Leave a Reply

Découvrez l’écosystème FL330

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