Single-Sensor Satellite Approach: What the Minimum Equipment List Actually Allows

A maintenance crew removes a satellite receiver from an aircraft on a dimly lit ramp at dusk, with a pilot reviewing flight documents in the cockpit.

On the ramp, paperwork closed, maintenance announces a satellite receiver deferred under the minimum equipment list. The unit comes off: the required-number column allows it. The useful question, though, lies elsewhere. It is which operations have just disappeared from the flight, and whether the destination and the alternates selected at the briefing stage needed them. One fewer sensor almost never removes a function; it removes operations, and the list says so in only one place.

What a second sensor provides, and what it does not

A navigation specification does not reduce to a single accuracy value. It sets out distinct requirements that must be read separately: accuracy, integrity, continuity, availability, and the functions the equipment must offer. Sensor redundancy does not act on all of them the same way, and that asymmetry drives everything that follows.

Accuracy does not change. It comes out of the pseudorange measurement and processing of a given receiver: two identical boxes do not measure better than one, they measure the same thing twice. Integrity does not change either, and this is the point most often misunderstood. Receiver autonomous integrity monitoring, or the confidence bounds received from a satellite-based augmentation system, are computed inside the receiver that remains. A single sensor can always tell you it can no longer guarantee its position: the alerting function survives the deferral intact.

What falls away is continuity — the ability to retain the function through to the end of the operation already under way. With two chains, the failure of one degrades the configuration without interrupting the operation. With one, the same failure becomes a loss of function. Availability drops too, but in the planning sense: the aircraft remains capable of a narrower range of operations, which is paid for in scheduling flexibility more than in safety.

Continuity is not, for all that, an absolute requirement, and this is where the rule shows itself to be consistent rather than arbitrary: it is calibrated to what the loss of the function costs at the moment it occurs. Where a safe means exists to complete the operation another way, a single sensor is enough; where none exists, two are required.

A second sensor doesn’t make the system more accurate or reliable in detecting errors. It mainly ensures that if one sensor fails, the other can keep the flight going. Without the second sensor, a failure means the function stops, but only if there’s no backup plan (like switching to radar or another procedure).

An Airbus A320 with one satellite receiver can still fly an RNP approach to lateral minima, but if the receiver fails on final, the crew must go around and try again. However, in oceanic airspace, a single receiver isn’t allowed because there’s no backup if it fails—no radar, no ground aids, and no quick way to reroute.

The bail-out stands in for redundancy, but not everywhere

An approach flown to lateral minima with a single receiver is not an act of complacency. If the receiver alerts on final, the expected response is known, immediate and safe: discontinue, then another approach, another aerodrome, or a holding pattern under supervision. The bail-out is structural: it depends on no additional equipment on board.

A cruise segment in oceanic or remote airspace is the opposite case. There is no substitute ground aid, no radar surveillance, and no way to complete the operation within a few minutes. That is why the rule there requires, absent specific provisions established for certain routes or segments, two independent long-range navigation systems: the loss of one must leave the aircraft able to hold its track until it exits the airspace concerned. The number required and the conditions that relax it are read in the applicable airspace documents and in the authorisation held, never by analogy with a neighbouring airspace. The same reasoning applies to an approach requiring specific approval whose go-around is itself flown to required navigation performance, over constrained terrain: since the safeguard manoeuvre then relies on the same equipment as the approach, it cannot serve as a bail-out. This is precisely why this type of approval generally assumes a full configuration, from which the deferral departs by definition.

What a single sensor still allows, depending on the bail-out available
Operation What losing the sensor costs Available bail-out Single sensor
Oceanic cruise and remote airspace Loss of track-keeping over an extended period None within immediate reach Excluded as a general rule: two independent systems required
Continental en route under surveillance Fall back to radar or conventional guidance ATS surveillance, ground aids Generally permitted, subject to coverage conditions
Terminal-area arrival and departure Heading guidance, then interception of an aid Vectoring, conventional aids Generally permitted
RNP approach to lateral or vertical minima One discontinued approach Discontinuation, another procedure, another aerodrome Permitted, if a bail-out exists at destination and at the alternate
Approach requiring specific approval, low RNP value Loss of guidance in constrained airspace None when the go-around itself requires performance-based navigation Closed as soon as the approval assumes the full configuration
Airspace with a detection-and-exclusion requirement Loss of the ability to reject a faulty measurement Depends on the airspace crossed To be checked provision by provision, not by counting boxes

Anatomy of a deferral: reading the columns in the right order

A minimum equipment list is derived from the master list approved for the type. The operator may restrict it, never relax it: a tolerance absent from the master list cannot appear in the operator’s own.

Two men review a 'Conformity' document in front of an aircraft at dusk.
Pilots verify compliance documents before flight, ensuring safety and regulatory adherence.

The usual reflex compares the number installed against the number required at departure, concludes the box is ticked, and moves on. Yet the number required at departure says only one thing: the aircraft may leave the ramp. The entire operational scope of the deferral sits in the remarks and exceptions column, and in the procedures it invokes. That is where the sentence that closes off operations is found, and where the positive conditions to be met are listed: sometimes a procedure of another type at destination and at the alternate, sometimes a configuration requirement or an airspace restriction.

What the columns of a deferral entry actually say, and the reading errors they produce
Column What it actually says What is wrongly read into it
Number installed The configuration of the aircraft, not of the fleet That it is identical across every registration of the type
Number required at departure The condition for departure, and nothing more That the flight is deemed fit for what was planned
Remarks and exceptions The operations withdrawn and the conditions to be met An informative note that may be skimmed
Operational procedure invoked A crew obligation, often located outside the list itself A cross-reference with no practical effect
Maintenance procedure invoked An action to be recorded before departure That it is implied by the deferral
Rectification interval category The correction deadline, tied to when the fault was found, per the operator’s counting convention That it resets at every leg or every crew change
No entry for the equipment No tolerance at all: no departure That silence amounts to permission

Two side effects escape a provision-by-provision reading. Interaction, first: two harmless-looking deferrals taken in isolation combine into a configuration no one has assessed — a sensor on one side, a navigation computer or an autopilot on the other. The lists sometimes anticipate the combination, rarely all of them. The deadline count, second: it is tied to when the fault was found, per the operator’s own counting convention, not to the number of legs flown since — a deferral taken at the start of a rotation does not reset along the way.

The trap. The deferral is granted at departure, but its conditions run throughout the flight. A destination whose only instrument procedure requires the withdrawn capability, or an alternate in the same position, turns a departure tolerance into a dead end on arrival: the condition that ruled it out was in the remarks column, not the required-number one. The same logic applies in flight: a reroute into airspace requiring two independent systems does not become acceptable just because the aircraft is close to it. What a deferral closes off stays closed until the equipment is restored.

Real independence: what two chains do not protect against

It remains to ask what redundancy was protecting against, because that is exactly what the deferral removes. Two chains cover only one class of event: the random, independent failure of a piece of equipment. As soon as the failure mode is shared between them, the second box does nothing — and was already doing nothing before the deferral.

What the second chain used to cover, and what protects in the other cases
Origin of the loss Did the second chain help? What actually protects
Hardware failure of a receiver Yes: this is the design case Redundancy, hence nothing left after deferral
Loss of a power bus Only if the chains are electrically separated The electrical architecture, to be checked in the type’s documentation
Shared antenna or wiring No Nothing on board: the failure is single by design
Signal jamming over an area No: both receivers lose track together Inertial reference, ground aids, ATS surveillance
Spoofed signal, consistent across all channels No Cross-check against a source of a different nature
Error in the navigation database No: both chains load the same database Checking the loaded procedure against the chart
Fault affecting the constellation or the augmentation No Pre-flight prediction, notices to navigators, bail-out minima

One nuance escapes this grid, and it works against the deferral. The second chain did not only provide a spare function: it provided a comparison. Two position solutions side by side reveal a drifting receiver, a diverging entry, a procedure loaded incorrectly on one chain only. This cross-check disappears without a single line mentioning it, and compensating for it is manual: checking distances and bearings against a ground aid.

The right reflex. Read the entry backwards. Start with the remarks column, write down in plain terms the list of operations withdrawn, then check it against the filed route, the destination, each alternate and each procedure available at those aerodromes. Only then look at the number required at departure. And correct the capability declaration on the flight plan before filing, not after the first clearance refusal.

What the deferral changes in flight preparation

The deferral triggers adjustments, none of which is automatic. The first concerns the aerodromes: destination and alternate must offer a procedure compatible with the actual configuration, and an aerodrome whose every procedure relies on the withdrawn capability is no longer a valid alternate, whatever its weather. This is the check that the dossier prepared before the announcement did not make.

The second concerns minima, when the capability lost is vertical guidance based on a satellite-based augmentation system. On fleets with asymmetric equipment — one augmented receiver, the other not — which box is deferred changes the outcome, even though the remark does not always distinguish between them. Losing vertical guidance is not simply a higher minimum: it is switching from a decision height to a minimum descent altitude, hence a different final descent technique, a revised visibility or runway visual range requirement, and sometimes different diversion fuel.

The third concerns the capability declaration on the flight plan. The equipment indicators and the performance-based navigation descriptors must reflect the actual configuration, or air traffic control will issue clearances the aircraft cannot accept, and the discovery will happen over the radio. The reverse costs something too: a degraded declaration sometimes forces a longer routing, hence more fuel — a trade-off decided at filing, not on climb-out.

The fourth concerns the briefing. A failure of the remaining receiver no longer carries the same weight: what was a switch to the other chain becomes a loss of function, with a fall back to conventional aids or to inertial reference. The abnormal procedures concerned are often written on the assumption of a full configuration, so they bear rereading before engine start.

Grey areas, and what to look for in your own documentation

Three grey areas remain, and it is better to know them than to discover them. The first is terminological: the remark speaks of operations, sometimes of specific approvals, in terms that do not map word for word onto the list of navigation specifications. Translating a general wording into a list of operations actually withdrawn is the operator’s job, and the result varies from one manual to another. The second is material: asymmetric configurations, where the two sensors are not worth the same capability, are poorly captured by a counting logic. The third is technological: a multi-constellation receiver already contains several partially independent sources of measurement, something a box-counting argument does not represent.

Four checks are worth doing cold, once and for all. In the minimum equipment list: the exact wording of the remark attached to the satellite sensors, the crew procedure it invokes, the rectification category. In the operations manual: who decides, who records, how flight preparation learns that a capability has been withdrawn. In the specific approval documents: the configuration assumed by each approval held, since that is precisely the assumption the deferral contradicts. In the type’s documentation: which chain feeds which display, which antenna is shared, which bus feeds what — the only place to learn whether the two chains were genuinely independent.

For anyone preparing a type rating or a recurrent check, the exercise is never about whether the aircraft may depart: it is about naming the operations withdrawn, demonstrating that the route, the destination and the alternates do not need them, and stating what becomes of the next failure. Discussions on forums.fl330.com tend, in fact, to focus more often on reading the remarks than on the principle of deferral itself.

The applicable regulation, the master minimum equipment list approved for the type, and the operator’s documentation take precedence over this article, whose sole purpose is to lay out the mechanism behind the rule.

Questions fréquentes

Does a satellite receiver deferred on the minimum equipment list rule out an RNP approach?

Not as a matter of principle. Integrity continues to be computed inside the receiver that remains, and an RNP approach has a bail-out built in by design: discontinuation, then another procedure, another aerodrome, or a holding pattern under supervision. What decides the matter is the remarks column of the relevant entry and the crew procedure it invokes, which may require that a procedure of another type be available at destination and at the alternate.

Why do oceanic and remote airspaces require two systems when an approach can do without?

Because the requirement bears on continuity, and continuity is calibrated to what the loss of the function costs at the moment it occurs. On approach, discontinuation ends the operation within a few minutes using means independent of the satellite. In oceanic or remote airspace, there is no substitute ground aid and no immediate surveillance, and the loss of one system must leave the aircraft able to hold its track until it exits the airspace: the rule there therefore requires, absent specific provisions applicable to certain routes, two independent long-range navigation systems.

Must the filed flight plan be corrected after a sensor deferral?

Yes, because the equipment indicators and the performance-based navigation descriptors declare a capability. If they do not reflect the actual configuration, air traffic control will issue clearances the aircraft cannot accept, and the discovery will happen in flight. The corrected declaration may in turn force a longer routing, hence extra fuel: this trade-off is handled at flight-plan filing, not after engine start.

Does a second receiver protect against jamming or spoofing of the signal?

No, these are failure modes common to both chains. Two receivers placed in the same radio environment lose track together, and a spoofed signal that is consistent across all channels cannot be detected by comparing two solutions of the same nature. Satellite redundancy covers random hardware failure; against interference, protection comes from inertial reference, ground aids and air traffic control surveillance.

Where exactly is it written what operations a deferral withdraws?

In the remarks and exceptions column of the entry, and in the crew procedure it invokes, often written elsewhere than in the list itself. The number required at departure tells you only about the legality of departure, not about the operations that remain. And a piece of equipment with no entry at all benefits from no tolerance: the list’s silence forbids departure rather than allowing it.

Does the rectification deadline run from when the fault was found or from the first leg flown?

It is tied to when the fault was found and recorded, according to the rectification interval category attached to the entry and the counting convention adopted by the operator: the day of discovery does not always count, and this detail is found in the operations manual rather than in the list. The number of legs flown in the meantime extends nothing, and any extension obeys its own conditions, set out by the operations manual and overseen by the authority. Follow-up belongs to the technical department, but the crew benefits from knowing the deadline before accepting the aircraft.

Commentaires

Leave a Reply

Découvrez l’écosystème FL330

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