Final approach is universally recognized as one of the most demanding phases of flight. The aircraft is low, slow, and configured for landing; margins are tight, and the workload is high because pilots are simultaneously managing airspeed, descent rate, lateral alignment, and communications. When an unanticipated system anomaly occurs during this critical phase, the combination of time pressure and reduced altitude leaves little room for error. A methodical, well-practiced response can mean the difference between a safe outcome and a serious incident. This article examines common anomalies that can appear on final approach, provides a structured decision-making framework, and underscores the value of recurrent simulation training to build the requisite skills and confidence.

The High‑Stakes Environment of Final Approach

During final approach the aircraft is typically within 10 nautical miles of the runway and descending below 2,000 feet above ground level. Crews are focused on flying a precise glide path, meeting stabilized approach criteria, and preparing for landing. Any sudden malfunction — whether in flight controls, automation, or systems — demands immediate attention. The pilot flying must continue to aviate while the pilot monitoring diagnoses the issue and runs checklists. This dual‑task environment is why the aviation industry emphasizes crew resource management (CRM) and threat and error management (TEM).

Understanding the specific systems that are most likely to cause trouble during this phase — and the procedures designed to handle them — is essential for every professional pilot.

Common Aircraft System Anomalies on Final Approach

While the list of possible malfunctions is long, a handful of anomalies occur most frequently in line operations and simulator training. Each presents unique challenges that require rapid recognition and appropriate action.

Autopilot Failure or Disengagement

Modern aircraft rely heavily on the autopilot for precision approaches, especially in low visibility. An unexpected autopilot disconnect — whether caused by a servo fault, sensor disagreement, or a flight‑director issue — forces the pilot flying to immediately take manual control. The key risk here is loss of situational awareness while the crew works to identify the cause. Standard procedure: the pilot flying calls “my airplane,” maintains attitude and thrust, and the pilot monitoring executes the autopilot failure checklist, which often includes resetting the flight director and confirming raw‑data guidance.

GNSS signal loss, FMS anomalies, or instrument landing system (ILS) receiver failures can degrade navigation accuracy at the worst possible moment. A glitch in the ILS glideslope or localizer indication, for example, may lead to an incorrect deviation display. Pilots must be ready to cross‑check with other sources (e.g., the backup ILS, VOR, DME, GPS, or even visual references). If the approach becomes unreliable, the safest action is often to execute a missed approach and either re‑attempt using a different procedure or divert.

Landing Gear Malfunctions

Landing gear problems on final approach can range from a partial extension (one gear leg not down‑and‑locked) to an unsafe indication despite a properly downlocked mechanism. An unstable gear situation forces the crew to weigh landing risk against the complexity of a go‑around and possible gear‑up landing. Most manufacturer checklists include steps to cycle the gear, use alternate extension systems, or consult the landing gear abnormality chart. If a gear‑unsafe condition persists, the crew should consider a low‑approach inspection by maintenance personnel or a controlled gear‑up landing on a prepared surface.

Flap or Slat System Issues

Flap asymmetry, jamming, or electrical failures can prevent the wing from reaching the landing configuration. Without full flaps, the stall speed increases, and the recommended landing distance grows. The checklist typically directs the crew to set the last known safe flap position and recalculate approach speeds and landing distance. If the available runway length is insufficient, a diversion becomes necessary. Some aircraft allow for a “flap zero” landing, which requires an entirely different technique and is rarely practiced outside the simulator.

Hydraulic or Electrical System Failures

A total hydraulic loss leaves the crew without normal braking, nose‑wheel steering, or flap extension. Emergency systems — such as an accumulator or electric backup pump — may provide limited functionality, but the landing will be at higher speed and with reduced controllability on the runway. Electrical failures can disable navigation aids, flight instruments, or the autopilot, forcing reliance on backup systems (e.g., standby instruments and battery power). The critical action in either case is to execute the appropriate memory items immediately and then work the checklist for the specific failure.

Priority Framework: Aviate, Navigate, Communicate

The aviation maxim “Aviate, Navigate, Communicate” is never more important than on final approach. When an anomaly appears, the pilot flying’s first and most important duty is to maintain control of the aircraft — attitude, airspeed, and flight path. Only after the aircraft is stable should the crew begin identifying the problem and coordinating with air traffic control. Attempting to troubleshoot a failure while losing control of the approach is a recipe for disaster. The framework works in this order:

  1. Aviate – Fly the airplane. Keep the wings level, maintain appropriate speed, and be ready to initiate a go‑around if the approach cannot be stabilized.
  2. Navigate – Determine the aircraft’s position relative to terrain and obstacles. Decide whether to continue the approach, execute a missed approach, or divert.
  3. Communicate – Advise ATC of the nature of the problem and intended course of action. Request vectors for a re‑approach or diversion as needed.

This simple hierarchy prevents task saturation and keeps the focus on what matters most: flying the airplane safely.

Detailed Procedures for Specific Anomalies

General guidance only goes so far. Every aircraft type has detailed procedures, but the underlying logic is consistent across transport‑category airplanes. We expand on the protocols for the anomalies listed above.

Autopilot Failure – Manual Reversion

Upon an unexpected autopilot disconnect, the pilot flying immediately takes control. A brief cross‑check of the attitude indicator, altimeter, and vertical speed confirms the aircraft is not entering an unusual attitude. The pilot monitoring then performs the autopilot failure checklist, which may include pressing the “AP DISC” button to silence the warning, turning off the autopilot master switch, and verifying the flight director is either off or set to a valid mode. If the approach continues, the pilot flying must hand‑fly the approach using raw data or flight director guidance, whichever is reliable. If the workload becomes unmanageable, a go‑around is prudent.

When the flight director or lateral/vertical deviation becomes suspect, the pilot flying should switch to raw data: tune the ILS frequency manually, display the localizer and glideslope needles, and cross‑reference with GPS approach data if available. If the approach is still within tolerances, the crew can continue to minimums. If any parameter is unreliable, the missed approach has already been briefed — execute it. Do not descend below the published minimum altitude unless all required navigation signals are correct and the runway environment is in sight.

Landing Gear Abnormalities – Alternate Extension

The first step for any gear‑related malfunction is to reduce airspeed to the maximum gear extension speed and then attempt to cycle the landing gear using the normal lever. If the gear still does not indicate down and locked, the crew should refer to the alternate gear extension procedure, which often involves a manual blow‑down handle or a gravity‑extension mechanism. After alternate extension, the crew must verify the gear’s status using electrical mechanical indicators or a visual check from the cabin (if applicable). If any leg remains unsafe, the pilot should prepare for a gear‑up landing. The checklist will provide guidance on fuel dumping, passenger preparation, and the approach itself (typically a low‑pass for visual inspection by tower personnel).

Flap or Slat Malfunction – Config‑Adjusted Landing

If the flaps fail to extend fully, the crew must determine the current flap position and its effect on reference speeds. The performance section of the flight manual provides landing distance adjustments for partial flap settings. A go‑around may be necessary if the required landing distance exceeds the available runway or if the approach speed becomes too high for the conditions. In the event of an asymmetric flap condition, the pilot receiving the asymmetric flap drill should immediately set the flaps to the last symmetrical position and maintain a bank toward the good side to compensate for the roll moment. This scenario is challenging and almost always warrants a diversion to a longer runway.

Hydraulic or Electrical System Failure – Emergency Landing Procedure

A total hydraulic failure demands immediate action. The crew must check the standby hydraulic system or electric backup pump to restore braking and steering. If that fails, a no‑hydraulic landing is conducted at a higher speed with limited braking. The antiskid system may be inoperative, so the pilot must be careful to not lock the wheels. Electrical failures common on final approach include a generator failure or a bus fault. The crew should shed non‑essential electrical loads and rely on the battery for essential instruments. Many aircraft have an emergency bus that powers critical flight instruments. A missed approach may be required if the electrical system cannot support the ILS or runway lighting.

Go‑Around Decision Making

Perhaps the most important skill in anomaly management on final approach is the willingness to go around. A go‑around is not a failure — it is the deliberate, professional choice to abort an unstable approach. The decision to go around should be made the moment the approach becomes destabilized due to a system malfunction, excessive workload, or any factor that compromises safety. The go‑around procedure is straightforward: apply full thrust, rotate to go‑around pitch attitude, clean up the aircraft (flaps and gear retraction), and follow the missed approach procedure. Once at a safe altitude and in a stable configuration, the crew can troubleshoot the anomaly without the pressure of an imminent landing.

In simulator training, pilots learn that hesitation to go around — often driven by a desire to “get it on the ground” — can lead to loss of control or runway excursions. Operational data shows that a large percentage of approach and landing accidents involve an unstabilized approach. When in doubt, go around. It is a decision that can be reversed; a landing attempt that goes wrong cannot.

The Role of Simulator Training

No amount of classroom theory can replace the muscle memory and decision‑making skills developed in a high‑fidelity simulator. Platforms like Aerosimulations.com allow pilots to encounter unexpected system failures in a safe, controlled environment. The ability to practice a no‑hydraulic landing, a flap‑up approach, or a split‑flap malfunction on final approach builds the confidence needed to handle the real event. Effective simulator sessions should include a mix of planned fail‑points and random anomalies to foster adaptive thinking.

Many operators require recurrent training that covers these exact scenarios, emphasizing the importance of CRM and standard operating procedures. The FAA Advisory Circulars on approach and landing accident prevention recommend frequent practice of go‑arounds and system emergency procedures. Similarly, the European Union Aviation Safety Agency (EASA) provides guidance on upset prevention and recovery training (UPRT) that applies to final‑approach anomalies.

For pilots seeking to enhance their skills, platforms like Aerosimulations.com offer realistic scenarios that mirror real‑world line operations. By incorporating unexpected system failures into routine approach training, pilots can reduce the surprise factor and respond more effectively. The International Civil Aviation Organization (ICAO) also stresses the value of scenario‑based training over rote memorization.

Conclusion

Unanticipated aircraft system anomalies during final approach are among the most challenging situations a pilot can face. The combination of low altitude, high workload, and limited time to recover demands a structured response that prioritizes aircraft control above all else. By understanding the most common failures — autopilot disengagement, navigation glitches, landing gear issues, flap problems, and hydraulic/electrical failures — and by practicing the appropriate checklists and go‑around procedures, pilots can significantly improve their chances of a safe outcome.

Simulator‑based training, such as that offered by Aerosimulations.com, provides the ideal environment to develop these critical skills. The investment in regular, high‑quality training pays dividends when a real anomaly occurs. In aviation, preparation transforms an emergency into a managed situation. Pilots who commit to ongoing proficiency and maintain a low threshold for executing a go‑around will consistently deliver the safe outcome that passengers and crew expect.