aviation-safety

Sully Hudson River Crash Verified Explainer: What Happened and Why It Still Matters

On January 15, 2009, US Airways Flight 1549—an Airbus A320 bound for Charlotte and Denver from New York’s LaGuardia—landed in the Hudson River after losing thrust in both...

Mara Ellison
Sully Hudson River Crash Verified Explainer: What Happened and Why It Still Matters

On January 15, 2009, US Airways Flight 1549—an Airbus A320 bound for Charlotte and Denver from New York’s LaGuardia—landed in the Hudson River after losing thrust in both engines. Captained by Chesley B. ‘Sully’ Sullenberger and First Officer Jeffrey B. Skiles, the crew executed a successful water ditching, and all 155 people aboard were rescued by nearby boats. This verified explainer outlines what occurred, why decisions were made, how the response unfolded, and the lasting impact on aviation safety and emergency preparedness.

Flight, Failure, and Ditching

Takeoff and Bird Strike

Flight 1549 lifted off from LaGuardia’s Runway 4 at 15:26 local time. Less than a minute into climb, the airplane encountered a flock of European starlings. Both engines ingested birds, suffered near-total loss of thrust, and began to surge and silently lose power. Within seconds, the cockpit indications shifted to diminished engine performance, then to a complete flameout. With limited altitude and no viable runway ahead, Sullenberger judged that a return to LaGuardia or a diversion to Teterboro was not feasible.

Decision to Ditch in the Hudson

Over the next few minutes, Sullenberger and Skiles evaluated options along the river. The aircraft was descending; reaching a suitable patch of land or structure in New York was unlikely. Sullenberger selected the relatively calm waters of the Hudson River between Manhattan and nearby airports, a site offering the best chance for survivable impact and effective rescue. At approximately 15:35, the airplane touched down smoothly, stayed intact, and remained floating long enough for passengers and crew to evacuate.

Procedures and Performance

Emergency Configuration and Ditching Technique

During the descent, the crew configured the airplane for landing: flaps set, landing gear extended, and cabin preparation called for an emergency evacuation. Sullenberger maintained controlled airspeed and attitude, applying steady back pressure to minimize porpoising and deceleration forces. The Airbus remained largely level, and the touchdown was gentle enough that emergency exits remained functional and the fuselage stayed largely above water.

Evacuation and Rescue

Flight attendants directed passengers to the nearest exits and deployed slides/rafts where applicable. Many passengers exited through main doors and overwing exits, assisted by crew initiating rapid egress. Nearby vessels, including first responders, tugboats, and commuter craft, converged quickly. All 155 occupants were rescued within approximately 24 minutes, with only minor injuries reported.

AttributeVerified DetailSource Type
AircraftAirbus A320-214, registration N106USOfficial investigation reports
Flight NumberUS Airways 1549Air traffic control data
Date and TimeJanuary 15, 2009, about 15:26–15:35 localNTSB timeline
LocationHudson River near Midtown ManhattanRadar and GPS data
Onboard150 passengers, 5 crewCrew and passenger manifest
InjuriesFew serious; majority minor or noneMedical records and NTSB
OutcomeAll survived; aircraft substantially damaged and recoveredInvestigation final reports

Crew Actions and Training

Sullenberger and Skiles: Crew Resource Management

Captained by Sullenberger, a former fighter pilot with extensive glider experience, and First Officer Skiles, a seasoned Airbus pilot, the crew applied disciplined CRM. Sullenberger managed the big picture—aircraft state, terrain, time, and priorities—while Skiles handled standard callouts, checklists, and radio communications. Their shared situational awareness, practiced emergency drills, and calm coordination were central to the successful outcome.

Checklist Execution Under Duress

Although the situation moved quickly, the crew followed memory items and checklist protocols where practicable. Engine restart attempts were made and then discontinued as unsafe. Declaring an emergency, notifying air traffic control, and requesting priority handling gave the airplane necessary clearance and support. The emphasis shifted to preparation for a water landing, balancing aircraft configuration with passenger readiness.

Investigations and Findings

NTSB and Aviation Safety conclusions

The National Transportation Safety Board (NTSB) concluded that the crew’s decisions were appropriate given the constraints. Contributing factors included the ingestion of birds into both engines and the lack of time to identify alternate landing sites. The Airbus A320 performed as expected in the ditching, and the crew’s execution aligned with training. The investigation reinforced the value of wildlife hazard management at airports and enhanced guidance on ditching procedures.

Regulatory and operational responses

Regulators and manufacturers updated checklists, flight-crew training materials, and airport wildlife hazard management recommendations. Airlines incorporated lessons into recurrent training, emphasizing go-around decisions near wildlife areas and preparations for unlikely but survivable emergency scenarios. The event became a benchmark in CRM training and passenger safety briefings.

Legacy and Safety Outcomes

Public perception and industry impact

Often described as ‘the miracle on the Hudson,’ the event highlighted the importance of crew judgment, training, and design. Public confidence in aviation remained intact, and the story was used to underscore how thorough preparation can turn a severe situation into a survivable outcome. Media portrayals and continued education efforts have reinforced the technical and human factors behind the result.

Long-term aviation improvements

Beyond immediate procedural updates, the accident influenced research into bird strike mitigation, aircraft design for water operations, and communication protocols between cockpits and cabin crew. Training programs now include more robust simulations of dual-engine loss at low altitude, and airports have refined wildlife hazard controls. These changes have contributed to continued improvements in safety across the industry.

Key Takeaways

  • Dual-engine failure caused by bird ingestion left the airplane with no thrust but remained controllable.
  • Crew selected a controlled water landing in the Hudson River, prioritizing survivability and rescue accessibility.
  • Effective crew resource management, disciplined checklists, and clear communication enabled an orderly evacuation.
  • All 155 people on board survived, with mostly minor injuries; the aircraft was recovered and investigated.
  • The event led to lasting changes in training, wildlife hazard management, and emergency preparedness.

Today, US Airways Flight 1549 is studied not only as a remarkable rescue but also as a case study in aviation safety systems working as designed. The decisions made by Captain Sullenberger and First Officer Skiles, supported by robust aircraft design and thorough crew preparation, continue to inform best practices and reinforce the value of training, checklists, and coordinated emergency response.

Related Reading

More pages in this topic cluster.

Understanding Why Pilots Died: Causes, Patterns, and Safety Lessons

Pilots died in a range of events, from early test flights and combat operations to routine public transport, private flights, and training accidents. This evergreen explainer ou...

Read next
Catalina Plane Crash Victims: Verified Information and Memorial Context

The Catalina plane crash refers to the loss of a sightseeing aircraft near Catalina Island, a small island located approximately 20 miles southwest of Los Angeles, California. S...

Read next
Potomac River Crash 1982: What Happened, Why It Mattered

On January 13, 1982, a Boeing 737–200 operating as Air Florida Flight 90 crashed into the 14th Street Bridge and subsequently into the Potomac River shortly after takeoff from...

Read next