When the Engines Went Quiet

On a routine winter climb out of LaGuardia, a flock of geese erased thrust from both jets in seconds—and forced a captain to choose between runways he could not reach and a river he had never planned to land on.

Two minutes into a normal day

January 15, 2009, was cold and bright over New York. US Airways Flight 1549, an Airbus A320 bound for Charlotte with 155 people aboard, lifted off LaGuardia Airport into what looked like an ordinary departure. Captain Chesley “Sully” Sullenberger, a former U.S. Air Force fighter pilot with 19,663 total flight hours, was in the left seat. First Officer Jeffrey Skiles was flying the leg.

Barely two minutes after takeoff, at roughly 2,800 feet, the aircraft met a flock of Canada geese. Birds struck the airframe and were ingested into both CFM56 engines. Thrust collapsed on both sides almost at once—the kind of failure that checklists are written for, but that no crew expects to face on a clear afternoon over one of the most crowded airspaces on Earth.

Skiles began running the dual-engine failure checklist. Sullenberger took control. The cockpit filled with the work of a crew that had seconds, not minutes, to understand that their airplane was no longer an airplane in the usual sense: it was a very heavy glider with a city underneath it.

The geometry of no good options

From the NTSB’s investigation, published as Accident Report DCA09MA026, Loss of Thrust in Both Engines After Encountering a Flock of Birds and Subsequent Ditching on the Hudson River, the central story is not heroics in hindsight. It is decision-making under uncertainty.

Sullenberger quickly judged that a return to LaGuardia was not assured. Teterboro Airport in New Jersey was discussed with air traffic control and likewise did not offer a comfortable margin. Altitude was bleeding away. Obstacles and population density crowded every path. The FAA’s Lessons Learned entry on US Airways Flight 1549 emphasizes the same point: when both engines fail low and close to the ground, the menu of safe outcomes shrinks fast.

Sullenberger turned the A320 toward the Hudson River. A water landing—ditching—is among the least forgiving maneuvers in aviation. It demands controlled speed, attitude, and touchdown on a surface that is not a surface. He aimed for a controlled descent at about 125 knots, flaring the jet so it would meet the water as deliberately as a pilot can manage when everything has gone wrong at once.

Ditching on the Hudson

The touchdown on the Hudson was hard, loud, and survivable. The fuselage remained intact enough to float. In the cabin, flight attendants moved passengers into evacuation mode—cold water, wing exits, ferries turning toward the white-and-blue Airbus listing in the current.

Ferry crews and U.S. Coast Guard assets reached the scene quickly. Boats became the terminal jetway. People stood on wings in midwinter air while the city’s ordinary river traffic became a rescue fleet. The aircraft stayed afloat long enough for everyone to get off.

Of 155 occupants, none died. Five were seriously injured. The NTSB would later describe the event as “the most successful ditching in aviation history”—not because ditching is a goal pilots train toward, but because complete loss of thrust on departure so rarely ends with every soul accounted for.

What the record says

The board’s 2009 report on DCA09MA026 treats the flight as a case study in crew resource management, checklist discipline, and—above all—timely acceptance of reality. Sullenberger’s military flying background and deep experience in gliders and safety work informed his handling, but the report’s lessons are procedural: recognize the failure, assign tasks, communicate with ATC without letting radio work displace flying the airplane, and commit to the best bad option before altitude makes every option worse.

The FAA Lessons Learned Database entry on Flight 1549 distills the same event for operators and instructors: bird strikes can destroy thrust without warning; dual-engine failure at low altitude is a different problem than single-engine failure; and the successful outcome depended on a ditching decision made early enough to be flown with skill rather than desperation.

Why it matters to you

Modern training still circles back to this flight because the tempting mistake is the one Sullenberger refused to make: trying to stretch a dead airplane back to a runway that feels familiar. NTSB simulations of return-to-airport scenarios for Flight 1549 showed that with a realistic thirty-five-second delay—time for a human crew to recognize the emergency, discuss options, and act—attempts to reach LaGuardia or Teterboro ended in impact short of the field. Only the Hudson ditching, begun with that recognition lag built in, produced the outcome that actually occurred.

That is the skill worth drilling today: not romantic “stick and rudder” bravado, but the disciplined moment when you stop negotiating with the impossible. In a low-altitude, dual-engine failure, the checklist your FO runs is only half the job. The other half is cold assessment of energy, distance, and time—and the willingness to execute the survivable option, even when it is the one you never filed. Sullenberger’s river landing was not a miracle. It was a decision, made in time.