Aviation Safety

The 2009 US Airways Flight 1549 Hudson River Ditching: Verified Facts, Timeline, and Safety Lessons

On January 15, 2009, US Airways Flight 1549—an Airbus A320—lost both engines after striking a flock of Canada geese during climb from New York’s LaGuardia Airport. Within...

Mara Ellison
The 2009 US Airways Flight 1549 Hudson River Ditching: Verified Facts, Timeline, and Safety Lessons

Verified Summary: What Truly Happened on the Hudson

On January 15, 2009, US Airways Flight 1549—an Airbus A320—lost both engines after striking a flock of Canada geese during climb from New York’s LaGuardia Airport. Within minutes, Captain Chesley "Sully" Sullenberger and First Officer Jeffrey Skiles executed a successful emergency landing on the Hudson River, in what became known as the "Miracle on the Hudson." All 155 people aboard survived. This verified explainer presents the established facts, decisions, and outcomes based on official investigations and authoritative sources.

Key Facts at a Glance

AttributeVerified DetailSource Type
FlightUS Airways Flight 1549Official report
DateJanuary 15, 2009NTSB, FAA
AircraftAirbus A320-214 (registration N106US)Operator records
RouteLaGuardia (LGA) to Charlotte Douglas (CLT)Flight plan
Occupants150 passengers, 5 crewCockpit voice recorder, manifest
OutcomeAll 155 on board evacuated safely; minor injuriesNTSB, NTSB hearings
Contributing FactorBird strike—aerial dual-engine lossICAO, NTSB investigation

Timeline of the Flight

Pre-Departure and Takeoff

Flight 1549 was a regularly scheduled domestic service from LaGuardia to Charlotte Douglas. Taxi, pushback, and takeoff proceeded normally. Radar and ATC recordings confirm standard departure procedures, with the aircraft climbing out over Flushing Bay after takeoff at 15:26 local time.

Bird Strike and Dual Engine Loss

Approximately 90 seconds into climb, the A320 encountered a flock of North American Canada geese. Both engines ingested birds, resulting in a dual engine flameout. The cockpit voice recorder captured the moment of impact and the crew’s immediate recognition of the emergency.

Decision to Land on the Hudson

With limited altitude and no suitable airport options ahead, Captain Sullenberger assessed the river near the North River Water Pollution Control Plant as the least-risk option available. This decision was based on minimizing fatalities and maximizing survivability for all on board.

Emergency Landing and Ditching

The aircraft was configured for a controlled ditching, with flaps set appropriately and thrust levers idle at touchdown. The A320 remained largely intact, allowing structured evacuation by crew and passengers. Flight attendants played a critical role in organizing evacuations under rapidly worsening conditions.

Evacuation and Rescue

Emergency services were alerted quickly. Survivors were rescued using nearby vessels and helicopters. Hypothermia risk was managed by rapid response; medical triage on nearby piers ensured timely treatment for minor injuries and exposure.

Investigation and Official Findings

The National Transportation Safety Board (NTSB) led a comprehensive investigation, analyzing cockpit voice and flight data recorders, conducting metallurgical examinations of engine wreckage, and modeling the bird strike dynamics. The final report concluded the dual engine loss was primarily attributable to the bird ingestion and that the crew’s decision to land on the Hudson was the most appropriate under the circumstances.

Contributory Factors Identified

  • Bird flock location and altitude predictable with known limitations in radar detection for wildlife.
  • Time-critical nature of the decision: limited altitude left minimal margin for alternatives.
  • Effective crew coordination and standardized emergency procedures.
  • Robust design of the A320 fuselage facilitating controlled ditching and evacuation.

Crew Performance and Human Factors

Captain Sullenberger’s extensive experience, including prior military and commercial jet time, informed risk management under extreme pressure. First Officer Skiles contributed through checklist discipline and communication with air traffic control. The investigation noted exemplary crew resource management (CRM), with clear task delegation and calm coordination that directly influenced the positive outcome.

Evacuation Procedures and Passenger Outcomes

Aft overwing and main cabin doors, along with deployed slides and rafts, were used efficiently. Flight attendants maintained command even as water ingress increased, prioritizing child and mobility-impaired passengers. Post-evacuation care on shore included hot blankets, basic medical evaluation, and psychological support, which were critical for managing shock and preventing hypothermia.

Legacy and Safety Improvements

The "Miracle on the Hudson" reinforced several long-term changes: wildlife hazard management around airports, enhanced crew training for emergency ditching, and public communication protocols. Operator checklists now explicitly consider wildlife strikes during climb. The event also prompted improvements in passenger briefing for water evacuations and coordination between airport emergency services and nearby municipal resources.

Lessons for Operators and Regulators

  • Continued emphasis on wildlife detection and deterrence at airports.
  • Simulation-based training for rare, high-consequence events like dual engine loss during climb.
  • Standardized guidance for flight crews evaluating off-airport landing options.
  • Strengthened interagency response planning to ensure rapid rescue and medical support.

Related Reading

More pages in this topic cluster.

What Happened to the Woman Who Died on the Southwest Flight: Verified Facts and Timeline

In early 2024, a woman died on a Southwest Airlines flight operating as Flight 1365 from Tampa to Baltimore, prompting questions about what happened and why. The incident involv...

Read next
Plane Crash in Costa Rica: Causes, Notable Incidents, and Safety Insights

This article explains the broader patterns behind plane crash incidents in Costa Rica, with factual incident profiles, investigation factors, and how these events fit into natio...

Read next
Pete Hegseth Emergency Landing: What Happened and What It Means

On the date of the incident, Pete Hegseth was aboard a commercial flight that initiated an emergency landing shortly after takeoff. An uncontained engine failure triggered a rap...

Read next