Key Facts at a Glance
On January 15, 2009, US Airways Flight 1549, an Airbus A320-214, lost both engines after striking a flock of Canada geese shortly after takeoff from LaGuardia Airport. Captained by Chesley Sullenberger and First Officer Jeffrey Skiles, the crew executed a water landing on the Hudson River. All 155 people on board were rescued, and no one was killed in the accident. The event became known as the "Miracle on the Hudson." This verified explainer outlines what happened, why decisions were made, and how the response shaped aviation safety and emergency protocols.
| Attribute | Verified Detail | Source Type |
|---|---|---|
| Aircraft | Airbus A320-214, registration N106US | NTSB / operator records |
| Flight | US Airways Flight 1549, scheduled as LaGuardia to Charlotte Douglas | Flight manifest / airline schedule |
| Date and Time | January 15, 2009, approximately 15:26 local (EST) | Cockpit voice recorder / NTSB timeline |
| Location | Hudson River, near Midtown Manhattan, New York City | Maritime logs / NOAA charts |
| Onboard Persons | 150 passengers, 5 crew members (155 total) | NTSB / operator manifest |
| Fatalities | 0 | NTSB final report |
| Injuries | Minor to moderate reported by passengers and first responders | EMS / hospital records |
| Rescue Time | Approximately 9–10 minutes from impact to last passenger rescued | Emergency response timelines |
| Investigating Body | National Transportation Safety Board (NTSB) | Official investigation files |
Why the Aircraft Lost Power
The A320 encountered a flock of Canada geese approximately 2.5 to 3 miles from LaGuardia Airport during climb. Both engines ingested birds, causing a dual engine flameout. Bird strikes are a known hazard, but a dual-engine failure at low altitude is exceptionally rare. The crew immediately declared an emergency, following checklists for loss of thrust. Because the aircraft was too low to return to LaGuardia and insufficient altitude existed for a turn toward Teterboro, New Jersey, the options for a traditional landing were effectively eliminated within seconds of the strike.
Engine Ingestion and Dual Flameout
Modern jet engines are tested to handle bird strikes, yet they are vulnerable at certain phases of flight. In this case, the simultaneous ingestion of multiple large birds into both engines disrupted airflow, causing a complete loss of propulsion. The crew’s prompt recognition and callout allowed them to focus on managing the situation rather than attempting impossible return maneuvers. Their prioritization of a landing site began almost immediately after the strike.
Decision to Land on the Hudson River
With limited altitude and no suitable aerodrome in range, Capt. Sullenberger assessed the surface of the Hudson River as the least harmful option among a set of poor choices. The river offered a relatively smooth surface at that time, minimal traffic, and proximity to dense population where rescue response could be swift. Factors such as current, tide, and river traffic were quickly evaluated. The decision reflected training, experience, and real-time risk management rather than a spontaneous reaction. Crew coordination and communication with air traffic control were critical in compressing decision time into a few decisive minutes.
Evaluating the River as a Landing Site
- Minimal wave action and clear visibility at the time of the event
- Reduced number of obstacles compared with urban areas or confined waterways
- Proximity to rescue infrastructure, including boats that arrived within minutes
- Lower perceived risk compared with attempting an urban forced landing
Emergency Response and Evacuation
Multiple agencies responded almost immediately, including the New York City Fire Department, Coast Guard, and local marine units. Life rafts deployed automatically on impact, and passengers exited the aircraft using the slides and wings as guides. The evacuation was rapid, with the last person rescued within about 9 to 10 minutes. Cold water temperatures and the time required to extricate all passengers added pressure, but orderly procedures and strong passenger compliance reduced risks. First responders provided on-scene triage, and most individuals were transported to hospitals for evaluation of hypothermia and minor injuries.
Rescue Timeline at a Glance
| Time After Impact | Key Action | Notes |
|---|---|---|
| 0–2 minutes | Emergency declared; aircraft ditched; life rafts auto-deploy | Crew declares mayday; begins controlled descent |
| 2–5 minutes | First rescue boats arrive; passengers boarding begins | Coast Guard and nearby vessels on scene |
| 5–9 minutes | Ongoing passenger extraction; triage begins on shore | Most passengers removed by minute 9 |
| 9–10 minutes | Last passenger rescued; situation shifts to medical care | No loss of life reported |
Investigation Findings and Safety Recommendations
The NTSB investigation focused on the dual-engine failure, crew decision-making, and emergency response effectiveness. The report praised the crew’s professionalism and the adequacy of existing checklists while emphasizing the near-unique nature of the event. Recommendations reinforced crew resource management training, improvements in bird hazard mapping, and further study of ditching procedures for commercial aircraft. Regulators and manufacturers reviewed evacuation system performance, flotation characteristics, and communication protocols to ensure lessons were translated into actionable changes.
Investuring Outcomes and Regulatory Actions
- No design mandates for new engines after the event, but bird-strike modeling was refined
- Enhanced guidance for ditching training in airline simulator programs
- Updated coordination protocols between air traffic control and emergency services
- Improved passenger briefing requirements for over-water operations
Long-Term Industry Impact
The landing in the Hudson River influenced training, procedures, and public perception of risk in commercial aviation. Crew resource management drills incorporated more frequent water-landing scenarios, and regulators reviewed wildlife hazard management around airports. While no commercial aircraft has replicated a full ditching on a river since 2009, the event remains a benchmark example of effective emergency decision-making. It reinforced that robust preparation, clear communication, and disciplined execution can produce outstanding outcomes even in highly unusual circumstances.
Training and Drifts After 2009
Simulator sessions now routinely include low-altitude dual-engine failures and considerations for controlled water landings where feasible. Airlines emphasize timely decision-making, coordination with ATC, and passenger communication. The psychological component of managing fear and maintaining procedural compliance under stress has also been integrated more deeply into recurrent training for flight crews.
Conclusion
US Airways Flight 1549 demonstrated how preparation, rapid assessment, and coordinated response can mitigate severe outcomes in an emergency. The landing in the Hudson River was the result of time-pressured decisions based on training, available information, and risk prioritization. Investigations confirmed that no fatalities occurred and that the response was effective, leading to lasting improvements in bird-strike management, training, and emergency coordination. The event continues to inform best practices in commercial aviation safety and serves as a frequently referenced case in crew resource management education.