Preparation Before the Approach

Low visibility operations demand meticulous preparation. Every successful low-visibility approach begins long before the aircraft descends from cruise altitude. Pilots must treat the entire planning phase with the same rigor as the approach itself, because once you enter instrument meteorological conditions (IMC), the margin for error shrinks dramatically.

Weather and NOTAM Review

Start by obtaining the latest METARs, TAFs, and SIGMETs for the destination and all alternate airports. Pay special attention to visibility, runway visual range (RVR), ceiling, and freezing levels. Check NOTAMs for outages of navigation aids (NAVAIDs), approach lighting systems, or runway lighting – any of these can downgrade the required minima. Use official sources such as the FAA’s Aviation Weather Center or the ICAO Meteorology page for global operations.

Aircraft and Systems Readiness

Verify that all equipment required for the intended approach is serviceable: ILS receivers, GPS (with RAIM prediction), autopilot, flight director, and head-up display (HUD) if available. For Category II/III operations, confirm that the aircraft’s maintenance release specifically authorizes the lower minima. Ensure that two independent navigation sources are available when required by regulations. A thorough pre-flight functions check of the approach mode annunciators, marker beacon receivers, and radio altimeter can prevent surprises at the most critical moment.

Personal Minimums and Risk Assessment

Set personal minimums that are more conservative than regulatory minima, especially when operating infrequently in low-visibility environments. Consider fatigue, recency of experience, and overall workload. Use a risk assessment matrix: low visibility combined with unfamiliar airports, single-pilot operations, or non-precision approaches increases risk exponentially. The FAA’s FAA Safety Team resources can help structure these evaluations.

Approach Strategy and Planning

Once you have a clear picture of conditions and aircraft status, develop a detailed approach plan. This includes selecting the appropriate approach procedure, setting up the flight management system (FMS), and briefing the crew (or yourself) on the step-down fixes, decision height/altitude, and missed approach procedure.

Selecting the Right Approach

Prefer precision approaches (ILS, MLS, GLS) whenever available because they provide both lateral and vertical guidance. If only a non-precision approach (VOR, NDB, LP) is available, consider whether the visibility is sufficient to maintain a stabilized approach without vertical guidance or with barometric vertical navigation (Baro-VNAV). For GPS-based approaches, confirm RAIM availability and any approach-specific requirements such as LPV versus LNAV minima. The SKYbrary database offers detailed guidance on approach classification and limitations.

Stabilized Approach Criteria

Define a stabilized approach point (typically 1,000 feet AGL in IMC) by which the aircraft must be on the correct flight path, in the landing configuration, and at the target speed. Any deviation beyond defined limits (e.g., more than half-scale deflection of the localizer or glideslope, or airspeed variations greater than 10 knots) must trigger an immediate go-around. Document these criteria in your approach briefing. Low visibility eliminates the ability to recover visually from an unstable approach, so discipline here is non-negotiable.

During the Approach: Execution and Monitoring

Execution in low visibility is a high-fidelity instrument flying exercise. The pilot’s mental model shifts from visual scanning to a steady cross-check of primary flight instruments, navigation displays, and engine parameters. Automation can reduce workload, but only if it is properly armed and monitored.

Effective Use of Automation

Engaging the autopilot and autothrottle early reduces manual flying demands and allows more attention to navigation, communication, and systems monitoring. However, remain ready to disconnect and hand-fly if the automation behaves unexpectedly. Use the flight director to interpret the desired flight path rather than chasing raw data. For Category II/III approaches, autoland may be required – verify that all annunciations (e.g., LAND 2 or LAND 3) are present before descending below Category I minima.

Crew Coordination and Sterile Cockpit

In multi-pilot operations, the pilot flying (PF) should focus on the primary instruments while the pilot monitoring (PM) handles radio calls, approach chart changes, and cross-check of altitudes and headings. Use standardized callouts (e.g., “1,000 to minimums,” “approach lights in sight,” “no visual contact”). Enforce a sterile cockpit from the top of descent until the aircraft is cleared of the runway. In single-pilot operations, consider using a voice recorder or checklist to reduce the memory load.

Managing Instrument Scan and Illusions

Low visibility, especially at night or in fog, can create powerful visual illusions: the runway may appear farther away or sloped. Rely exclusively on the instrument cross-check until the moment you have assured visual reference (e.g., approach lights visible and you can identify the runway threshold). The FAA’s AC 60-22 provides an excellent discussion of illusions. Use the radio altimeter for height awareness below 200 feet, as barometric altimeters lag in fast-changing terrain.

The Decision Point: Minimums and Missed Approach

Every approach ends with a clear go/no-go decision at the decision height/altitude (DH/DA) for precision approaches, or the missed approach point (MAP) for non-precision approaches. In low visibility, this decision is binary and must be based on objective criteria, not wishful thinking.

Visual Reference Requirements

Regulatory minima require specific visual cues to continue below DH/DA – typically at least one of: approach lights, runway threshold lights, runway end identifier lights, or the runway itself. The pilot must be able to see and maintain the required visual references to land. If only approach lights are visible (without the runway), continued descent to 100 feet AGL is permitted in some jurisdictions, but you must be able to identify the runway by that point. If not, initiate the missed approach immediately.

Executing a Missed Approach

The missed approach procedure should be briefed before the approach and flown with the same precision as the approach. Use the autopilot or flight director to fly the missed approach path, retract flaps and landing gear on schedule, and communicate with ATC. Do not attempt a second approach from a missed unless you understand the reason for the first failure (e.g., a temporary obstruction). Repeated low-visibility go-arounds can lead to spatial disorientation; consider diverting to the alternate.

Landing Rollout and Taxi

The landing phase in low visibility is not over when the wheels touch. Poor visibility continues to challenge directional control and situational awareness on the runway and taxiways.

Runway Alignment and Braking

Maintain descent path using the glideslope or visual approach slope indicators until flare. In crosswind conditions, use the instrument guidance until the last moment. After touchdown, use rudder and nosewheel steering to track the runway centerline, monitoring runway centerline lights. Apply brakes smoothly to avoid locking wheels on a wet or icy runway. Note that RVR reporting may not reflect localized patches of fog; use your own observations if cleared to continue.

Low-Visibility Taxi Procedures

After clearing the runway, inform ATC and request progressive taxi instructions if needed. Use airport moving maps (if available) or follow follow-me vehicles. Turn on taxi lights and all available exterior lights to maximize your own visibility to others. In extremely low visibility (RVR below 600 feet), some airports impose taxi restrictions – check ATC for “low visibility procedures” (LVP). The AOPA Pilot Resources section covers taxi operations in low visibility.

Post-Flight Debrief and Continued Improvement

After parking, take a moment to debrief the approach: what went well, what could be improved. Note any systemic issues such as radio communication problems, NAVAID anomalies, or workload management challenges. Reporting these through the NASA Aviation Safety Reporting System (ASRS) can improve safety for all aviators. Consider periodic training in a full-flight simulator that includes low-visibility scenarios.

Summary of Best Practices

  • Thoroughly brief weather, NOTAMs, and approach minima before descent.
  • Use the appropriate precision approach – ILS, GLS, or LPV – whenever possible.
  • Set and adhere to stabilized approach criteria; go around if deviating.
  • Leverage automation (autopilot, flight director) but monitor it actively.
  • Maintain a strict instrument cross-check until in sight of required visual references.
  • Know your missed approach procedure cold and be ready to execute at the decision point.
  • After landing, use low-visibility taxi procedures and do not hesitate to request progressive guidance.
  • Debrief every low-visibility approach and report any anomalies to improve procedures.

Low visibility approach and landing remains one of the most demanding phases of flight. With careful preparation, disciplined execution, and a commitment to using every available tool, pilots can safely navigate these conditions. The principles outlined here are drawn from industry best practices, regulatory guidance, and real-world operational experience. Stay sharp, stay cautious, and never let the pressure to land compromise safety.