Reduced Vertical Separation Minimum Approval: What the Operator Must Prove on Both Sides

A pilot in the cockpit of an airliner at dusk, closely monitoring the altimeter while maintaining a precise altitude in the RVSM band.

An aircraft returns from a paint shop, rejoins the line, and three weeks later operations discovers that its registration no longer appears among those whose altitude-keeping is judged acceptable. No incident, no deviation reported by a controller: one measurement too many, taken at the wrong moment, and a mean that has drifted. RVSM approval is rarely lost through an event; it is lost through the drift of a measurement. The two major regulatory systems detect this drift differently, and do not require the same proof.

What the Approval Certifies: An Error Budget

Between flight level 290 and flight level 410, the minimum vertical separation is reduced from 2,000 to 1,000 feet. This doubling of capacity rests on no new margin, but on the demonstration that the population of aircraft operating in this band holds its level with a known and bounded dispersion. A collision risk model estimates the probability that two aircraft assigned to adjacent levels end up in vertical overlap; this probability is derived from the distribution of height-keeping deviations measured across the whole fleet, and the safety target is expressed in accidents per flight hour, at a level counted in billionths — an order of magnitude, the target value being whatever the applicable text retains.

Hence a consequence that is easily lost from view: the approval is not the property of a single flight, nor entirely that of an isolated aircraft. It is an admitted contribution to a collective statistic. An aircraft whose measurement chain drifts by two hundred feet does not put its own flight in danger — the separation remains far greater than its error — but it distorts the tail of the distribution on which every other aircraft’s authorisation rests.

The total vertical error, the TVE, breaks down into two terms of a very different nature. The altimetry system error, the ASE, separates the displayed pressure altitude from the pressure altitude actually occupied: a matter of static ports, source error correction and surface condition. The deviation from the assigned level, the AAD, separates the displayed altitude from the assigned level: a matter of autopilot, level-off and crew discipline. Only their sum matters to the risk model.

The RVSM system works because all aircraft stay within a tight altitude range. If one aircraft drifts even slightly, it affects the safety calculations for all others. The system measures two types of error: how accurately the aircraft measures altitude (ASE) and how well it stays at the assigned altitude (AAD). Both must stay within strict limits.

An Airbus A320 with a static port error of 150 feet (ASE) and an autopilot deviation of 50 feet (AAD) would have a total vertical error (TVE) of 200 feet. While this doesn’t endanger the flight, if enough aircraft in the fleet show similar errors, the overall safety margin is reduced, potentially leading to RVSM approval being revoked for the entire fleet.

Breakdown of the total vertical errorThree horizontal lines stacked on top of each other: at the top the assigned level, in long dashes; in the middle the altitude displayed by the altimetry chain, in short dashes; at the bottom the pressure altitude actually occupied, as a solid line, carrying a side-view aircraft silhouette. A first bracket measures the gap between the assigned level and the displayed altitude, a second the error between the displayed altitude and the actual altitude, a third the sum of the two.assigned leveldisplayed altitudeactual altitudeAADASETVETVE = ASE + AAD
The deviation that monitoring measures is not the one the crew sees. The deviation from the assigned level is read in the cockpit; the error of the measurement chain, meanwhile, is invisible on board. Only their sum fixes the level actually occupied.

The Two Halves of the File: Measurement and Height-Keeping

This division dictates the structure of the file, identical in principle on both sides of the Atlantic: one half falls under airworthiness and is demonstrated at type-design level, the other falls under operations and is demonstrated at the level of the management system. A file with only one solid half is a rejected file.

On the airworthiness side, the demonstration covers a minimal architecture — two independent altitude-measuring systems, an altitude alert, an automatic height-keeping capability able to maintain the acquired level to within a few tens of feet in stabilised flight, a transponder fed by the altitude actually used for height-keeping — and then, above all, performance.

The minimum performance specifications for onboard systems do not set one error limit but three, and it is their interplay that makes the file. One ceiling applies to the mean measurement error of the group: it forbids systematic bias, the aircraft that always flies a little high or a little low. A second applies to that mean plus three standard deviations: it forbids dispersion, that is, a fleet whose mean looks good only because errors cancel each other out. A third, tighter than the first and wider than the second, applies to an aircraft treated outside the group: it refuses to let a single unit hide behind a population. The numerical values belong to the applicable specification and have shifted over its revisions; it is that specification a file must cite, never an order of magnitude recalled from memory. Two points are regularly lost along the way: these ceilings apply across the entire declared flight envelope, not only at the usual cruise level, and they concern the error of the measurement chain alone, the deviation from the assigned level being counted separately.

The notion of a group is the most widely misunderstood part of the scheme. A group brings together aircraft whose airframe, static-port geometry and measurement chain are nominally identical; the demonstration is made once and for all, and each aircraft inherits it as long as it remains compliant with that definition. A skin repair, an antenna modification, a build-up of paint in a critical area: an aircraft can drop out of the group without anyone having decided so, and it falls back into the individual regime, which is more demanding.

On the operations side, the demonstration covers written and traceable procedures: cross-check of altimeters before entering the band, with the maximum permitted discrepancy set by the approved documentation; level-off technique; the course of action in case of failure, severe turbulence, traffic collision avoidance system resolution, or lateral offset; initial and recurrent training; and finally a deviation-reporting loop. This last item is the one audits most often find empty.

The right reflex. Include the critical area of the static ports on the work order, not only in the maintenance manual. Any skin, paint or antenna work then triggers a check before return to service, instead of being discovered six months later by a height-keeping measurement.

Europe and the United States: Two Paths to the Same Assurance

The European framework for air operations places reduced vertical separation among specific approvals: the operator’s state issues an act, this appears in the operations specifications, and it is maintained through the authority’s continuing oversight. The review checks the eligibility of each aircraft, the altimetry tasks in the maintenance programme, the operations manual procedures, training, and the commitment to take part in the regional monitoring programme. The proof is documented, precedes the flight, and has a signatory.

Two technicians work on maintenance documentation and equipment in front of an aircraft.
Maintenance documentation ensures compliance with reduced vertical separation standards.

The American framework followed the same pattern for years, through individual authorisation issued for a given aircraft. It departs from this on one decisive point: when an aircraft is eligible and broadcasts its position by means of a transmitter meeting the performance requirements, individual authorisation is no longer required. The authority draws its assurance from the data stream, which it analyses continuously, and notifies the operator when it detects an anomaly. The proof becomes post-flight, permanent, and without a signatory.

Two paths to the same assurance of height-keepingTwo sequences of three steps leading to the same result. At the top: airworthiness demonstrated, operational approval, periodic check. At the bottom: airworthiness demonstrated, qualified position transmitter, continuous monitoring. The two converge on a single box, operation admitted.documented approvalinstrumented eligibilitydemonstratedairworthinessoperationalapprovalperiodiccheckdemonstratedairworthinessqualified positiontransmittercontinuousmonitoringpermittedoperation
The requirement is the same; it is the proof that changes medium. One path establishes compliance before the flight by means of an act, the other after the flight by means of measurement. The first two steps remain common to both.

The shift is not cosmetic. Under the first regime, the operator must be able to produce a file on request; under the second, to react to a notification it did not trigger, within a constrained time, without control over the data that accuses it.

What Each System Requires as Proof, from the Eligibility File to the Return to Compliance
Item European system American system
Aircraft eligibility Type design and flight manual supplement Same requirement, carried by the operational annex
Administrative act Specific approval by the operator’s state, entered in the operations specifications Individual authorisation, not required of an eligible aircraft that broadcasts its position
Permanent proof The file, re-examined under continuing oversight The position stream, analysed continuously
Maintenance Altimetry tasks approved with the programme Equivalent tasks attached to the programme
Height-keeping measurement Ground station, satellite monitoring unit or broadcast position; deadline per aircraft Broadcast position first; near-permanent observation
Trigger for action Significant deviation, out-of-limit error, missed check Anomaly detected in the data and notified
Return to compliance Corrective action, new measurement, reinstatement by the state Correction followed by a new observation period

The trap. Reading the removal of an authorisation as the removal of a requirement. Where individual authorisation is no longer required, the aircraft must still be eligible, altimetry maintenance still performed, procedures still written and performance still monitored: the authority observes instead of issuing, that is all. Whoever moves an aircraft from one regime to the other without reconstituting these items finds itself without a file the day an anomaly is notified to it.

Height Monitoring: What the Programme Measures

The system does not read the onboard altimeters. It obtains the aircraft’s geometric height by another route — a ground station interrogating the transponder from several points, a satellite monitoring unit carried on board for a handful of flights, or the position broadcast by the aircraft — then converts this height into pressure altitude by means of a numerical model of the pressure field, at that place and at that moment. The difference with the altitude reported by the transponder gives the error of the measurement chain; the comparison with the assigned level gives the height-keeping deviation.

These measurements are not judged one by one. They feed a statistic per aircraft and per group, maintained by the competent regional monitoring agency, and it is this statistic that the state consults. The frequency rule adopted by these agencies typically requires an aircraft to be measured roughly once every two years, or after a volume of flight hours on the order of a thousand, whichever period is longer; the exact deadline and the way it is counted fall to the agency the operator depends on. Where broadcast position is used, monitoring becomes near-permanent and the notion of a window fades away. In parallel, air traffic control bodies report significant level deviations: beyond a threshold on the order of a few hundred feet, set region by region, this is no longer treated as a data point but as an event, with its own report.

Shift in the distribution of a fleet’s measurement errorsTwo bell curves plotted on a horizontal axis of measurement errors. The first, a solid line, is narrow and centred to the left: it stays entirely within the acceptance limit, shown as a dashed vertical line. The second, a dashed line, is wider, shifted to the right and lower; its tail crosses the limit, and the portion beyond it is shaded.measurement errorcountacceptance limitcompliant fleetdrifting fleettail beyond limit
A slight shift in the mean costs far more than its own value. The limit does not bite into the centre of the distribution but into its tail: a few tens of feet of drift multiply the share of aircraft that cross it, and it is that share the model counts.

The consequence is harsh: an aircraft can be perfectly safe and still lose its eligibility. It is enough for its contribution to the tail of the distribution to become unacceptable, or for its measurement to be missing. The absence of a measurement counts as non-compliance, because the model has no way to handle an aircraft whose performance is unknown.

What Causes the Approval to Be Lost

The real causes of withdrawal form a short and stable list. None of them resemble an accident; almost all resemble an administrative oversight, or a technical intervention whose altimetric impact no one measured.

Six Ordinary Causes of Withdrawal, and What It Takes to Return to the Band
Event What the authority sees Immediate effect What must be produced
Missed height-keeping check No recent measurement on record Removal from the list of admitted aircraft Scheduled measurement and reason for the delay
Out-of-limit measurement error An isolated point, then its confirmation Aircraft suspended, group placed under observation Altimetric investigation and new measurement
Level deviation reported by air traffic control Report cross-checked against the assigned level Investigation into the event Crew analysis and flight data
Skin, paint or antenna work in a critical area Nothing, until the next measurement Silent exit from the group Conformity of the repair, sealing and geometry
Change of registration or of operator Link with the approval broken Loss of the benefit of the original approval File reconstituted with the new state
Departure with an inoperative item Deviation from the minimum equipment list Flight not eligible within the band Documented decision and alternative routing

Two lines deserve attention. The fourth, because the workshop has no reason to know it is working in a critical area for pressure measurement: the documentation says so, the work order rarely does. The fifth, because the link between an aircraft and its approval is neither universal nor portable: established by a state for the benefit of a given operator, it is broken by a dry lease, a registry transfer or a change of certificate, even though the aircraft itself has not moved.

The trap. Believing that a justified deviation does not need to be reported. A deviation caused by a traffic collision avoidance system resolution, severe turbulence or an outright failure is not a fault and is not held against the crew. But it is seen from the ground and enters the statistics as a height-keeping deviation: without a report, the authority concludes there is a failure in the measurement chain.

The right reflex. Treat the monitoring window as a maintenance deadline: a date, a named person responsible, an advance alert, a flight slot in an area covered by a monitoring means. Those who suffer this measurement instead of planning it discover their withdrawal through a flight plan refusal.

The File That Must Be Produced Without Delay

Whatever the regime, the operator must be able to produce, within a few hours, a limited but precise set of items. This is the most honest test of the solidity of an approval: not whether it exists, but how long it takes to prove it.

  • Eligibility of each aircraft: type design, approved modifications, flight manual supplement.
  • Altimetry tasks of the maintenance programme and their last execution: static system leak check, computer calibration, local port geometry.
  • Most recent height-keeping measurement results, with date and method.
  • Operations manual procedures, including failure, turbulence and lateral offset.
  • Crew training, initial and recurrent.
  • Deviation reports for the reference period retained by the management system — often the last twelve months — and the trace of their handling.

A file that fits within this list withstands both regimes. A file that relies on the existence of a certificate, without the items that support it, withstands neither — and least of all the instrumented regime, where there is no longer a certificate to show.

Grey Areas and Checks Worth Doing at Home

Several situations remain poorly covered. A third-country operator entering the other region carries its original approval with it, but not necessarily the recognition of its measurements: depending on the means used, they are accepted or redone. A mixed fleet, where a single aircraft is treated outside the group after a repair, forces two monitoring regimes to be maintained within the same information system — and that is where deadlines get lost. Non-eligible flights, ferry or special-mission, cross the band through an accommodation from air traffic control: this is not an approval and must not be planned as though it were.

Three checks are worth doing outside of any audit. The amendment status of the applicable text, first: both systems have moved on this subject, and the version cited in an operations manual is not always the one in force. The name of the person who holds the measurement deadline, next: if no one answers, the deadline does not exist. The actual presence of the critical area of the static ports in the documents read by a mechanic, finally, and not only in those read by an engineer. For anyone preparing to take up a role in operations oversight, these three points also make good interview questions, and are covered in the programmes on technical operations.

The applicable text in the state concerned and the operator’s approved documentation prevail over everything above: this article describes a mechanism and replaces neither an operations specification, nor a maintenance programme, nor a flight manual supplement.

Questions fréquentes

Is a brand-new aircraft automatically eligible for reduced vertical separation?

No. Type design may make the aircraft eligible, but operational eligibility further requires that the operator has incorporated the altimetry tasks into its maintenance programme, written its procedures, trained its crews, and enrolled the aircraft in the regional height-monitoring programme. An aircraft fresh off the production line can therefore be perfectly compliant and still remain non-eligible as long as this operational side is not in place.

What happens if the altitude-keeping monitoring window expires?

The aircraft drops off the list of those whose performance is known, which in practice amounts to a loss of eligibility. The absence of a measurement is not treated as a doubt but as non-compliance, because the risk model cannot accommodate an aircraft whose dispersion is unknown. Reinstatement requires a new measurement and, where applicable, an explanation for the delay.

Does a skin repair near a static port call the approval into question?

It can remove the aircraft from the group on which its statistical demonstration relied and send it back into the individual regime, which is more demanding. The difficulty is that nothing flags this at the time: the discrepancy only appears at the next measurement. The critical area must therefore appear on the work order, and a leak and geometry check must be carried out before return to service.

Does the absence of individual authorisation in the American system remove the need for oversight?

On the contrary: oversight is what replaces the authorisation. The aircraft must remain eligible and broadcast its position by means of a transmitter meeting the performance requirements, and its height-keeping is analysed continuously from that stream. All maintenance, procedural and training obligations remain; only the prior administrative item disappears.

Does a level deviation caused by a traffic collision avoidance system resolution count as a failing?

No, the deviation is justified and is not held against the crew. It remains visible from the ground, however, and enters the statistics as a height-keeping deviation: without a report, the authority has no way to distinguish it from a failure of the measurement chain, and it is the aircraft that carries the mark of it.

What must an operator produce when changing registration or taking over a leased aircraft?

The link between an aircraft and an approval is established by a state for the benefit of a given operator; it does not travel with the airframe. The file must be reconstituted with the new state: proof of eligibility, altimetry tasks of the maintenance programme, recent height-keeping measurement results, procedures and training. Measurements already obtained are often carried over, but their acceptance depends on the method used.

Commentaires

Leave a Reply

Découvrez l’écosystème FL330

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