What Happened and When the Plane Actually Landed in the Hudson
US Airways Flight 1549, an A320 departing New York LaGuardia on January 15, 2009, landed in the Hudson River at 15:24 local time after a dual bird strike disabled both engines. Often called the "Miracle on the Hudson," the event involved a successful off-airport landing on the river, immediate evacuation, and zero fatalities among the 155 people on board. This verified explainer outlines the key moments, decisions, and timeline that turned a potential disaster into a widely studied aviation safety case.
Aircraft, Flight Path, and Key Timeline
Sequence of Critical Moments
The flight followed a standard departure profile until about 1.5 miles northeast of LaGuardia, where the Airbus encountered a flock of Canada geese. The collision damaged both CFM56 engines, leading to a complete loss of thrust from each. With no time to return to LaGuardia and no suitable runway ahead, Captain Chesley "Sully" Sullenberger opted for a controlled ditching on the Hudson River. This section summarizes verified details about the aircraft, flight path, and timeline below.
| Date or Period | Event | Why It Matters |
|---|---|---|
| January 15, 2009, 15:20 EDT | Flight 1549 departed LaGuardia Runway 4 | Established baseline for timeline and flight origin |
| January 15, 2009, 15:24:08 EDT | Both engines lost thrust after bird strike near George Washington Bridge | Critical inflection point that eliminated return-to-airport options |
| January 15, 2009, 15:24:12 EDT | Decision to ditch on the Hudson River made by Captain Sullenberger | Resulted in high survivability due to controlled contact with water |
| January 15, 2009, 15:24:25 EDT | Landing on the Hudson River ("landing in the Hudson") | Core event answering when the plane landed in the Hudson |
| January 15, 2009, 15:25–15:30 EDT | Rapid evacuation onto wings and life rafts; all 155 persons rescued | Confirmed planning, preparation, and execution of emergency procedures |
| January 15–20, 2009 | NTSB investigation and recovery operations | Provided factual basis for official timeline and safety recommendations |
| May 2010 | NTSB published final report with probable cause and safety recommendations | Institutional learning and regulatory outcomes |
Key Decisions and Crew Actions
Survivability hingered on rapid diagnostics, crew coordination, and choosing the least-hazardous available option. After the bird strike, the crew had under 20 seconds to assess whether they could return to LaGuardia or reach Teterboro. With both engines unresponsive, Captain Sullenberger and First Officer Jeffrey Skiles executed a ditching plan that prioritized controlled attitude and airspeed, minimizing fuselage damage and enabling a swift evacuation. Communication with air traffic control and public advisories informed coordinated rescue responses.
Checklist Elements and Priorities
- Engine restart attempts — immediate, ruled out within seconds
- Consideration of nearby airports — time and distance made options unavailable
- Ditching preparation — flap settings, pitch attitude, and landing gear retraction to reduce drag and prevent structural failure
- Emergency announcement and brace commands — improved passenger readiness and compliance
- Coordinated rescue requests — alerted services before landing to reduce response lag
Aircraft Type, Systems, and Design Factors
The Airbus A320 equipped with two CFM56-5B engines has robust flight control laws, including protections against stalling and overspeed. However, when both engines ingested the same flock of birds, the loss of thrust was total regardless of airframe design. Still, the A320’s efficient wing and proven ditching characteristics allowed the crew to maintain controlled flight and a gradual descent onto the water, which contributed to low injury rates during the landing in the Hudson.
Passenger and Crew Experience During and After
Passengers reported a sudden noise, apparent loss of power, and spray upon water contact, followed by effective crew instructions to brace and prepare for evacuation. Life jacket usage, cabin lighting, and the proximity of rescue vessels enabled rapid egress. The lack of fire, controlled flooding, and timely arrival of ferries and emergency services all improved outcomes. In total, 150 passengers and five crew members were taken to hospitals for evaluation, mostly for minor injuries and hypothermia, reinforcing the effectiveness of procedures and timing.
Official Investigations, Findings, and Safety Changes
The National Transportation Safety Board (NTSB) concluded that the probable cause was the ingestion of large birds into both engines, a low-probability but high-consequence event. Contributing factors included the lack of time for altitude to assess alternatives and the absence of suitable terrain or runways en route. The board recommended enhancements to wildlife hazard management at airports, guidance on extended overwater operations, and crew resource training for unusual attitudes and off-airport scenarios. Many recommendations fed into broader regulatory updates and airline training protocols, making this a lasting reference point in aviation safety.
Comparison With Other Water Landings
While rarely executed, controlled water landings have occurred in other incidents; outcomes vary based on sea state, aircraft type, crew decision speed, and rescue response. Compared with some earlier events with higher loss of life, Flight 1549 benefited from daylight, calm conditions, proximity to shore, and highly trained crew, which together underscore why a prompt, coordinated response matters more than the simple fact of landing on water.
| Event | Aircraft | Location | Outcome |
|---|---|---|---|
| US Airways Flight 1549 (Jan 2009) | Airbus A320 | Hudson River, NYC | 155 aboard, 0 fatalities |
| Ethiopian Airlines Flight 604 (Sep 1988) | Boeing 737 | Bahir Dar, Ethiopia | 35 fatalities from fire post-landing |
| Flybe Flight 2319 (Feb 2009) | Bombardier Dash 8 | Southampton, UK | Minor injuries, runway landing |