Dense fog on an autumn morning, RVR of a few hundred meters, low-visibility procedures in effect: the aircraft is capable, the runway equipped, the operator approved — and yet, the crew abandons the approach. Nothing has failed. One of the two pilots is out of recency, and that is enough for the entire crew to revert to standard minimums. Low-visibility operations rely on this subtle mechanism: an authorization granted to the operator, but permanently conditional on those who exercise it.
An authorization granted to the operator — never to the pilot
Low-visibility operations are under a specific approval: an authorization that the authority issues to the operator, for designated aircraft types and precise minimums, based on a file describing a complete system — procedures, maintenance, training program, and recency monitoring method. No pilot “owns” CAT III. They exercise, within the approved program, a capability that belongs to their operator and becomes unavailable as soon as they deviate from the program’s conditions.
This architecture rests on three pillars that must hold at the same time. The aircraft: an automatic landing capability certified according to applicable specifications, confirmed by the day’s technical status. The aerodrome: low-visibility procedures (LVP) actually in effect, with protection of sensitive areas, lighting, and required separation. The crew: qualified under the program and — this is the focus of this article — current in terms of recency.
Low-visibility operations are not just about the aircraft or the crew alone. All three elements—aircraft, aerodrome, and crew—must be perfectly aligned to allow the lowest landing minimums. If any one of them is not up to standard, the minimums increase automatically.
The consequence is brutally simple: a valid approval does not reduce minimums for a crew out of recency, and perfect recency does not compensate for an aircraft’s capability degraded by the minimum equipment list. The status is reassessed for each flight, by the combination of the three pillars.
Entering the regime: initial qualification
Entry requires a course defined in the operations manual’s training section, approved with the authorization. Ground training: the logic of minimums, the architecture of guidance chains, failure modes, phraseology, and the specific geography of a low-visibility aerodrome — remote holding points, mandatory taxi routes, signal protection. In the simulator: series of approaches down to the target minimums, failures injected around the decision height, go-arounds at very low altitude, transitions to manual flight, low-visibility takeoffs, and failures at the worst possible moment. The simulator itself must be qualified to reproduce these conditions.
Qualification is granted by aircraft type and minimums level — one may be authorized for CAT II but not for CAT III, authorized for automatic landings but not for the lowest takeoff minimums. It also takes experience in the role into account: a newly released captain first operates with increased minimums, until their experience on type reaches the thresholds set by the operations manual. Initial qualification opens the door; it does not exempt anyone from what follows.
The silent mechanism behind the approval
The heart of the mechanism is here: qualification only survives through recency. The approved program sets a minimum number of approaches and landings in the relevant mode, real or in the simulator, that must be completed within a rolling period. Each credited approach enters the window; each passing week removes the oldest ones. When the count falls below the threshold, the individual authorization lapses — without notification, without any decision, and without the operator’s approval being affected in the slightest. This is a lapse by default, not a sanction.
What makes this mechanism silent is that line operations barely sustain it. The conditions requiring an approach to the lowest minimums are rare; one can fly an entire season of rotations without encountering a single LVP. Automatic landings performed in good weather may count, if the program credits them and if the facility allows — but outside of LVP, nothing protects the beam, and the exercise may not be representative of what it is supposed to maintain.
Low-visibility recency is like a countdown timer. Every week, the oldest approaches “expire” and are removed from the count. If the count drops below the required minimum, the pilot loses their low-visibility authorization until they complete more accredited approaches, usually in a simulator.
A Boeing 737 crew at Paris Charles de Gaulle is cleared for a CAT III approach with RVR 200 meters. The captain has 4 accredited approaches in their 90-day window, but the first one expires the day before the flight. Now with only 3 approaches, they are out of recency and must abort the approach, reverting to standard minimums of 550 meters.
The operator is required to keep this record: its tracking system is part of the approval file, and it is the first thing the auditor opens. But the mechanism has a blind spot: between updates, only the pilot knows what they actually flew and in what mode. An unrecorded creditable approach does not exist; one incorrectly recorded — degraded mode, inadequate facility — is worse, as it maintains on paper a recency that the hands no longer have.
The trap: approaching the first LVP of the season believing that summer flying has maintained recency. Fog does not wait for the required competence to be refreshed: it arrives precisely when the window has just expired for those who did not anticipate — and the discovery is made at the briefing.
The correct reflex: treat LVO recency as a perishable commodity with a known expiry date. Check your window before the fog season, ask for the autumn simulator session to include creditable approaches, and know exactly what your manual credits — line landing, simulator approach, pilot monitoring role — instead of assuming it.
The aircraft and the runway degrade faster than the crew
The crew is only one of the three pillars, and the other two move faster. On the aircraft side, the automatic landing capability is not a binary attribute: it comes in architectures — fail-passive, where a single failure disconnects the system without significant deviation but hands control back to the crew, and fail-operational, where redundancy continues the guidance to touchdown. The difference is not academic: it determines the decision reference — decision height with visual references in one case, alert height in the other — and, consequently, the lowest minimums available. A failure in flight, a maintenance deferral under the MEL, and the day’s capability is downgraded: the announcement may come on final approach, and the crew must know instantly what minimums they have left.

| Criterion | Fail-passive | Fail-operational |
|---|---|---|
| Single failure below the critical height | The system disconnects without significant deviation; the crew takes over | Redundancy continues guidance to landing |
| Decision reference | Decision height, visual references required | Alert height; below it, a single failure no longer interrupts the landing |
| Accessible minimums | Intermediate floor | The lowest minimums of the approval |
| Weight in training | Manual takeover and go-around at very low height | Management of degradation announcements and capability downgrades |
On the runway side, the regime only opens if the aerodrome has actually implemented its low-visibility procedures: protection of ILS sensitive areas, increased spacing, enhanced lighting and a dedicated electrical configuration. An ILS of the best category without active LVP is of no use for the minimums: unprotected signal, unconfigured environment. On the day, the question is never “can the aircraft do it?”, but “is the entire chain, at this precise moment, within the program’s conditions?” — and the answer is rebuilt for each flight.
| Failed link | Immediate effect | Recovery path |
|---|---|---|
| Crew out of the recency window | Increased minimums for this crew, approval intact | Accredited session according to the program, typically in the simulator |
| Aircraft capability degraded (failure, MEL) | Downgrade to a higher minimums level, sometimes in flight | Restoration and verification of capability |
| Aerodrome without LVP in effect | Standard minimums, regardless of the aircraft and crew status | Implementation of procedures, imposed on the crew |
| Training program not followed | The approval itself weakened, for all crews | Demonstration to the authority that the system has been restored |
Recurrent training and checking: what keeps the approval valid over time
Maintaining the qualification is not a separate activity: it is integrated into the recurrent check cycle, typically linked to the six-monthly check, with a low-visibility section identified in the program. Here is what line flying almost never provides: a failure injected below the decision height, a go-around initiated as the wheels reach the touchdown zone, a capability downgrade announced on final approach, a low-visibility takeoff rejected at the worst moment. The simulator is the only place where these situations are repeated until they become reflexes — and the only place where the approaches needed for recency are available on demand.
This program is not an internal policy: it is an integral part of the approval. Changing it — session spacing, scenario content, credit rules — requires the authority’s agreement, and its implementation is audited through training records. The authority did not approve a capability demonstrated on a test day: it approved a system that reproduces it continuously. The day the records show that the system no longer reproduces it — postponed sessions, lightened scenarios, recency tracked from afar — the entire approval becomes indefensible, for all crews at once.
What this changes for a type rating or a recruitment
For those preparing a type rating or an operator change, the mechanism has very concrete consequences. Experience is transferable — a training file showing years of maintained CAT III carries weight in a recruitment — but the authorization is not: with the new operator, one enters through its course, sessions and credit rules, even on the same type. Recruiters know this and read training files accordingly; candidates benefit from showing the continuity of their recency rather than just the initial qualification.
- Check your recency window definition: Know exactly how many approaches you need and over what time period. Some operators require 6 approaches in 90 days, others 4 in 60.
- Understand capability reclassification: If the aircraft has a failure, how does that affect your minimums? Some operators allow a temporary downgrade, others require an immediate abort.
- Know your increased minimums: New captains often have higher minimums until they gain experience. Make sure you know when this period ends for you.
- Clarify automatic landing credits: Some operators allow automatic landings in good weather to count toward recency, others do not. Check your manual.
The above describes a mechanism, not its specific regime: the applicable regulation, the operator’s approval and its approved documentation take precedence over this article in all circumstances.

Leave a Reply
You must be logged in to post a comment.