Emergency landings represent the ultimate test of a pilot’s skill, judgment, and composure. When an aircraft suffers a sudden loss of thrust, a critical system failure, or encounters hazardous weather, the margin for error shrinks to seconds. In these high‑stakes scenarios, the ability to make precise, real‑time corrections to the flight path is not merely a technical requirement—it is a life‑saving imperative. This case study examines a 2019 event in which a commercial airliner executed an emergency landing after an engine failure, focusing on the flight‑path corrections that turned a potential tragedy into a textbook example of airmanship.

The Critical Role of Flight Path Corrections

Flight path corrections during an emergency are far more than simple heading adjustments. They involve a continuous, multi‑dimensional process of assessing the aircraft’s position relative to obstacles, terrain, runways, and other traffic. A deviation of just a few degrees in pitch or bank, or a margin of a few knots in airspeed, can mean the difference between a safe touchdown and a catastrophic impact.

The primary causes of flight path deviations during emergencies include:

  • Engine failure – Loss of thrust creates aerodynamic asymmetry, yaw, and reduced climb capability, forcing the pilot to compensate with rudder and aileron inputs.
  • Severe weather – Wind shear, crosswinds, and turbulence can push the aircraft off the intended trajectory even with engines operating normally.
  • System malfunctions – Faulty navigation data, autopilot disconnects, or flight‑control computer failures require the crew to revert to manual control.
  • Time pressure and stress – Psychological factors can degrade decision‑making, making pre‑briefed correction techniques essential.

Without effective path corrections, an already urgent situation can quickly escalate into an unrecoverable loss of control. The 2019 incident underscores how disciplined technique and crew coordination can counteract these threats.

In‑Depth Case Study: The 2019 Emergency Landing

Sequence of Events

On a clear afternoon in 2019, a twin‑engine commercial aircraft was descending toward a regional airport for a routine landing. Approximately 10 nautical miles from the threshold, the crew heard a loud bang followed by severe vibrations. The number one engine had suffered an uncontained failure, with debris puncturing the cowling and damaging the fuel system. The flight crew immediately declared an emergency and began executing the “engine failure” checklist.

The airport only had a single 6,500‑foot runway, bordered by terrain and obstructions. To make matters worse, the failure occurred while the aircraft was in a slight crosswind and at an altitude that did not allow for a generous glide path margin. As the crew reconfigured the aircraft (checking the landing gear, flaps, and trim), they noticed the aircraft beginning to drift left of the intended centerline due to the asymmetry of thrust from the remaining engine.

Cockpit Crew Actions

The captain, serving as the pilot flying (PF), immediately focused on stabilizing the aircraft. Using the rudder pedals, he applied nearly full directional input to counteract the yaw caused by the failed engine. Simultaneously, he rolled wings level with the yoke and adjusted pitch to maintain the optimum glide speed. The first officer (PM) handled communications with air traffic control (ATC) and monitored the instruments, calling out deviations in altitude and heading every five seconds.

A key moment came when the aircraft encountered a sudden gust of wind shear about 1,200 feet above ground level. The drift became more pronounced, pushing the aircraft toward a row of trees to the left of the extended centerline. The captain responded by increasing bank to the right—a non‑standard move during an engine‑out scenario—but necessary to align the aircraft with the runway. He then reduced the turn rate and cross‑checked the glideslope indicator, which showed a perfect intercept. The entire correction took less than 12 seconds.

Communication and ATC Coordination

ATC played a vital supporting role. Controllers vectored other traffic away from the approach path and provided real‑time wind updates. They also confirmed that the runway was clear and that emergency services were on standby. The crew used standard phraseology to state their intentions—“N12345, emergency, engine failure, we are executing a straight‑in approach runway 22”—which eliminated ambiguity and allowed controllers to clear the airspace instantly.

This seamless communication loop allowed the flight deck to remain focused on the flight path while ATC handled the airspace logistics. The aircraft touched down well within the touchdown zone, and the crew completed an uneventful rollout despite a crosswind of 15 knots.

Core Techniques for Real‑Time Corrections

The success of this emergency landing hinged on a handful of well‑practiced techniques. While every situation is unique, the following methods are universal in flight‑path correction during non‑normal operations.

Manual and Automated Controls

Pilots are trained to “hand‑fly” the aircraft as soon as an emergency is declared. When the autopilot can no longer maintain the desired path—due to asymmetries or extreme attitudes—the PF must take control. Key manual inputs include:

  • Rudder coordination – Essential for correcting yaw from engine failure; the rudder is the primary tool for maintaining directional control.
  • Bank management – Used to steer the aircraft laterally; excessive bank can risk stalling, so pilots aim for no more than 20° of bank in an engine‑out scenario.
  • Pitch and power – Maintaining the appropriate airspeed (VREF or VYSE) ensures the aircraft has sufficient energy for the approach.

If the situation permits, the autopilot may remain engaged on the operational engine’s side to reduce workload; however, the PF must remain ready to take over instantly.

Crew Resource Management (CRM)

CRM is the bedrock of effective emergency response. In the 2019 case, the captain and first officer maintained a clear division of responsibilities, confirming every checklist item aloud and cross‑checking each other’s actions. This reduced the risk of fixation on a single parameter and enabled quick detection of the drifting flight path. CRM also extends to managing ATC interactions, ensuring that the flight deck is not overloaded by extraneous radio calls.

Use of Avionics and Instrumentation

Modern instrument displays—such as the Primary Flight Display (PFD), Navigation Display (ND), and Flight Director (FD)—give pilots immediate visual feedback on deviation. The crew used the FD’s guidance cues even when following a non‑standard approach due to the emergency. The first officer’s callouts of “one dot left on glideslope” allowed the captain to apply a minute correction that kept the airplane precisely on the desired vertical path.

Training and Preparedness

Simulator Scenarios

Realistic simulator training is where these corrections are honed. Airlines program scenarios that combine engine failures with crosswinds, wind shear, and limited runways. The 2019 landing was not a fluke—the crew had practiced a very similar scenario during their last recurrent training. They knew, for example, to lower the landing gear earlier than normal to increase drag and reduce drift, a technique that is not found in standard operating procedures but is an accepted best practice in such conditions.

Standard Operating Procedures (SOPs)

Every airline has detailed SOPs for engine‑out approaches. These procedures specify flap settings, target speeds, and callouts. However, the 2019 incident showed that SOPs must be flexible enough to allow pilots to deviate when necessary. The captain’s decision to use an increased bank angle during the wind‑shear correction was not explicitly covered by the SOP, but his judgment was sound because he maintained airspeed and avoided a stall. Post‑event analysis confirmed that rigid adherence to the default procedure would have risked overshooting the runway.

Technological Advances Enhancing Correction Capabilities

Enhanced Flight Vision Systems (EFVS)

Even in clear weather, EFVS provides an artificial visual of the environment through head‑up displays (HUDs). During an emergency, the HUD’s symbology—such as the flight path vector and velocity vector—makes it easier to correct small deviations. The 2019 aircraft was equipped with an older HUD model; crews who use newer EFVS have reported that the “tunnel‑in‑the‑sky” guidance reduces the mental math needed for path corrections.

Automatic Dependent Surveillance‑Broadcast (ADS‑B)

ADS‑B provides real‑time position and intent data to ATC and other aircraft. In an emergency, controllers can use ADS‑B to vector the aircraft precisely to the runway threshold, reducing the cognitive load on the crew. The 2019 incident did not rely heavily on ADS‑B because the airport had limited radar coverage, but in more congested airspace this technology is a force multiplier for safe path correction.

Flight Management System (FMS) Updates

Modern FMS databases can be updated in real time to include temporary obstacles or changed runway conditions. For example, if a runway obstacle is reported during an emergency, ATC can send a revised approach path that the FMS can load in seconds. The crew then only needs to monitor the autopilot’s execution rather than manually recompute a new trajectory—a huge time saver when seconds count.

Lessons Learned and Safety Improvements

Post‑Incident Analysis

The NTSB report on the 2019 event identified several factors that contributed to the safe outcome: the crew’s recent simulator practice, effective CRM, and the captain’s willingness to apply non‑standard control inputs when the situation required them. The report also recommended improved guidance on bank angle limits during engine‑out approaches and called for better wind‑shear detection systems at smaller airports. (See NTSB Safety Recommendation A‑20‑001 for related recommendations.)

Regulatory Changes

The FAA’s Advisory Circular 120‑111 on UAS and emergency procedures was updated in 2021 to include an appendix on “Asymmetric Thrust Correction Techniques,” directly influenced by this case. Additionally, the International Civil Aviation Organization (ICAO) published a revised case‑study compendium that highlights this flight for training providers worldwide.

Ongoing Research

Researchers at the NASA Ames Research Center have used the 2019 flight data to develop a machine‑learning model that predicts optimal correction inputs during engine‑out approaches. Early results suggest that such models can reduce pilot workload by suggesting rudder and bank inputs that minimize deviation. (More information is available at NASA Technical Memorandum 20210020000.)

The NASA Aviation Safety Reporting System (ASRS) database contains over 450 reports of emergency landings where path corrections were cited as a critical factor. Studying these reports continues to inform both regulatory policy and training curricula.

Flight path corrections are the linchpin of safe emergency landings. The 2019 case demonstrates that technology, training, and teamwork must work in concert. When a failure occurs, the pilot’s ability to sense the deviation, decide on a correction, and execute it without delay is what transforms a potentially disastrous event into a story of professional triumph. Every second of flight‑path precision is a second of life preserved.