Key Event Timeline
On January 15, 2009, US Airways Flight 1549 departed LaGuardia Airport for Charlotte Douglas International Airport. Minutes into climb, the Airbus A320 struck a flock of Canada geese, losing thrust in both engines. With limited options, Captain Chesley Sullenberger opted to land on the Hudson River. The landing occurred at approximately 3:55p.m. EST, about three minutes after the bird strike and 8 minutes after departure. Emergency evacuation proceeded quickly; all 155 aboard were rescued, and the aircraft was later recovered. Below is a concise, source-aligned timeline of decision points and actions.
Timeline of Actions and Decisions
| Date or Period | Event | Why It Matters |
|---|---|---|
| 15 Jan 2009, 15:26 EST | Departure from LaGuardia | Planned northbound climb to cruise altitude |
| 15 Jan 2009, 15:29 EST (~) | Bird strike at low altitude | Both engines lost power; aircraft unable to maintain flight |
| 15 Jan 2009, 15:31 EST (~) | Decision to divert to Teterboro, then Hudson | Attempt to reach a nearby airport failed; river landing chosen as safest option |
| 15 Jan 2009, 15:35 EST (~) | Final alignment and descent onto Hudson | Powered glide to maintain control and achieve survivable touchdown |
| 15 Jan 2009, 15:55 EST | Touchdown on the Hudson River | Landing within a narrow window of current and visibility; main fuselage remained intact |
| 15 Jan 2009, 15:57–16:05 EST | Evacuation and rescue | All 155 aboard evacuated in ~3 minutes; rescue vessels arrived within minutes |
| 15 Jan 2009 onward | Investigation and recovery | NTSB investigation confirmed successful decision-making and crew performance; aircraft raised and transported for examination |
Immediate Context and Crew Actions
After the bird strike, Sullenberger and First Officer Jeffrey Skiles executed a wings-level, gentle turn toward Teterboro while configuring the aircraft for a possible landing. When Teterboro was unreachable, they assessed the river, declared an emergency, and configured the Airbus for a controlled ditching. Power was reduced to idle just above the water, and the aircraft was flown onto the Hudson at a pitch attitude that helped distribute energy across the fuselage, minimizing structural failure. The coordinated application of flaps and thrust reversers during the rare full-ditching procedure contributed to the successful outcome.
Contributing Factors and Decision Rationale
- Dual-engine flameout caused by Canada geese ingestion at low altitude, leaving no restart option within available time or altitude.
- Limited suitable terrain and glide range in the congested New York metropolitan area.
- River surface conditions were calm, improving survivability compared to alternative surfaces.
- Crew training, discipline, and timely communication with air traffic control enabled an organized emergency response.
- Predeployment of rescue resources and proximity of vessels reduced evacuation time and exposure.
Aftermath and Safety Outcomes
The incident, known as the Miracle on the Hudson, resulted in zero fatalities despite minor injuries during evacuation. The aircraft was raised from the Hudson in March 2009 and transported for detailed examination. The NTSB concluded that Captain Sullenberger’s decision to land on the river was the most appropriate option given the constraints. The event prompted aviation stakeholders to review wildlife hazard management, ditching training, and passenger evacuation protocols. While specifics of ongoing legal and insurance matters are documented in investigative and court records, the core operational facts remain consistent across official reports.
Comparison with Similar Events
Controlled water landings are rare; this event stands out due to the absence of fatalities and the visibility of the rescue operation. The timeline below compares key metrics relevant to water ditching scenarios, illustrating why this incident is often used as a benchmark in aviation safety training.
| Metric | Estimate or Range | Context |
|---|---|---|
| Time from takeoff to landing | ~8 minutes | Short flight duration limited options for diversion |
| Altitude at bird strike | Approx. 2,800–3,200 feet AGL | Low altitude reduced altitude for troubleshooting |
| Touchdown speed | Estimated 140–150 knots | Consistent with powered glide and flap configuration |
| Evacuation time | Approx. 3 minutes | Rapid due to proximity to shore and vessel presence |
| Survivability outcome | 155 onboard, 0 fatalities | Result of crew decision, aircraft performance, and rescue coordination |
Aviation Safety and Operational Lessons
Investigations underscored the importance of bird hazard awareness, crew resource management, and realistic training for extreme scenarios. Airlines updated checklists and simulator scenarios to include multiple-engine failure at low altitude near urban areas. Regulators emphasized proactive wildlife management around airports and clearer guidance for declaring emergencies. These lessons remain foundational to emergency preparedness and are revisited periodically as part of recurrent training and safety management system updates.
Long-Term Reference and Records
In addition to official reports, the event is documented through flight data, cockpit voice recordings, and extensive media and institutional archives. NTSB materials, court filings, and aviation safety databases preserve the technical and factual record, enabling ongoing analysis and education. The phrase ‘when did the plane land on the Hudson River’ typically refers to the precise moment of touchdown, which occurred at approximately 3:55p.m. EST on January 15, 2009, following a decision process spanning just a few critical minutes.