Key facts at a glance
| Attribute | Verified Detail | Source Type |
|---|---|---|
| Flight | US Airways Flight 1549 | Official reports |
| Date | January 15, 2009 | NTSB timeline |
| Aircraft | Airbus A320-214 (twin-engine) | NTSB/aircraft records |
| Route | LaGuardia (LGA) to Charlotte Douglas (CLT) | Flight plan/AFTN |
| Crew | Captain Chesley Sullenberger, First Officer Jeffrey Skiles | Cockpit voice recorder |
| Passengers & Crew | 155 aboard (150 passengers, 5 crew) | NTSB manifest |
| Location | Hudson River near Midtown Manhattan, NY | GPS/Aircraft telemetry |
| Outcome | All 155 survived; minor injuries only | Post-incident medical reports |
| Contributing factor | Dual engine ingestion of Canada geese during climb | NTSB investigation |
The morning of January 15, 2009
On a clear but cold New York morning, US Airways Flight 1549 lifted off from LaGuardia bound for Charlotte. Within minutes, a dual-engine bird strike disabled both power plants. With strict training and deliberate decision-making, Captain Chesley Sullenberger and First Officer Jeffrey Skiles guided the Airbus A320 onto the frigid Hudson River. The event became known as the “Miracle on the Hudson,” exemplifying airmanship, crew resource management, and decisive emergency response under extreme time pressure.
How the emergency unfolded
Radar, cockpit voice recorder, and flight data recorder together reconstruct a sequence measured in minutes. After losing thrust, the crew checked airspeeds, evaluated the nearby river, coordinated with air traffic control, and declared an emergency. They configured the aircraft for a controlled ditching, managed passenger alerts, and executed a near-perfect water landing. Subsequent NTSB analysis highlighted how each action aligned with checklist-driven protocols and cross-checked decision making, turning a potential catastrophe into a structured rescue scenario.
Immediate actions that mattered
- Maintaining airplane control during undamaged touchdown on water
- Executing a disciplined evacuation within about 90 seconds
- Coordinating with nearby vessels such as the SS Andrea Doria and multiple FDNY and NYPD units
- Prioritizing passenger headcounts and rapid rescue via life rafts
The emergency response and rescue
Local responders converged quickly. The FDNY deployed marine units, the NYPD coordinated scene control, and nearby civilian boats provided immediate support, including the HMS Hornet Museum vessel and a Staten Island Ferry named the John J. Harvey, which helped move passengers to safety. This network of public and private assistance illustrated how urban riverine resources can be leveraged in rare but foreseeable crises. Passengers reported hypothermia risks; swift triage and blanket distribution reduced exposure-related harm.
The film: Miracle Landing (1990) versus the event
Long before the 2016 film Sully brought the story to a wide audience, the 1990 TV movie Miracle Landing dramatized the events with attention to cockpit tension and passenger perspectives. While some dialogue and scenes are condensed for television, the film retains core procedural details, such as the rapid evacuation and the role of nearby boats. Comparing the two productions helps viewers separate dramatization from the factual timeline recorded by the NTSB.
Narrative focus in each adaptation
- Miracle Landing (1990): emphasizes cockpit communication and cabin crew actions under duress
- Sully (2016): centers on the investigation and public scrutiny faced by the crew
- Both underscore training, crew coordination, and the human factors that enabled survival
Aviation lessons and lasting relevance
The Hudson event influenced crew resource management training, wildlife hazard policies at airports, and ditching preparedness for passengers and crew. NTSB recommendations reinforced checklists for unlikely water landings and improved coordination between airlines, airports, and local responders. While still statistically rare, the incident serves as a benchmark for how systematic procedures, practiced regularly, can align human performance with technology when outcomes hang in the balance.
Verified timeline and milestones
| Date or Period | Event | Why It Matters |
|---|---|---|
| January 15, 2009, 15:26 local | Takeoff from LaGuardia | Establishes baseline for timeline reconstruction |
| ~15:32 | Bird strike and dual engine loss | Critical inflection point; triggers emergency protocols |
| ~15:35 | Decision to divert to the Hudson | Demonstrates crew judgment amid uncertainty |
| ~15:36 | Controlled ditching on the Hudson | Water landing executed with minimal structural compromise |
| ~15:36–15:45 | Evacuation and rescue operations | Rapid move to life rafts limited exposure time |
| January 17, 2009 | NTSB holds first public briefing | Initial factual findings and safety recommendations |
| May 2010 | NTSB publishes final report | Comprehensive analysis of human and system factors |
| September 2016 | Film Sully releases in theaters | Brings the story to mainstream audiences; prompts discussion on aviation safety |
Passenger outcomes and aftermath
All 1549 passengers and crew survived, with a majority reporting minor injuries such as hypothermia and abrasions during evacuation. Ambulance crews triaged and transported individuals to nearby hospitals, where extended assessments found no life-threatening conditions. The psychological impact prompted discussions about grief counseling and stress management after traumatic events. In the years since, many passengers have shared reflections on gratitude, public perception, and the importance of crew training—offering insight into long-term human responses to sudden crisis.
Where to find authoritative information
For further reading, consult the NTSB factual report and docket for Flight 1549, statements from the NTSB and FAA, and post-incident safety recommendations. Books by crew members and investigative journalism pieces that cite official transcripts provide additional detail while distinguishing verified records from speculation. These sources help maintain an evidence-based understanding of the decisions, technologies, and human behaviors involved.
Common questions
- Were the engines ever restarted after the bird strike?
- How did nearby boats know to assist?
- Does the 2016 film Sully depict the ditching accurately?
- Has anything changed in aviation safety because of this event?
No; the crew determined that re-starting was not feasible given the altitude and configuration, and they prioritized a controlled ditching.
Emergency broadcasts and quick coordination through air traffic relayed the situation to maritime resources, prompting rapid deployment of civilian and public vessels.
It captures the overall sequence and pressure on the crew but dramatizes certain details, notably aspects of the investigation and the time pressure perceived by the crew.
Yes, it reinforced wildlife hazard management, ditching drills, and crew resource training, influencing guidance from the FAA, ICAO, and aircraft manufacturers.
Closing perspective
What is often called a miracle is, on close examination, the product of training, procedures, and rapid coordination under severe constraints. By studying the verified record alongside dramatized portrayals, audiences can appreciate both the human element and the systemic safeguards that converged on the Hudson that day.