The full picture
What happened
The Airbus A320 took off from LaGuardia for Charlotte. On the climb, the plane met a flock of Canadian Cossacks. The birds got into both engines; thrust became insufficient to continue the flight.
Commander Chesley Sullenberger took control, co-pilot Jeffrey Skyles began to execute a control map. The dispatcher offered a return to LaGuardia and then Teterboro, but the calculation of the trajectory showed that the turn to the lane left too little margin.
The A320 landed on the Hudson with the chassis removed. The hull was damaged and began to receive water, but all 150 passengers and five crew members left the plane alive. Five people were seriously injured.
Context and mechanisms
Detailed account
Background, technical details and decisions are examined separately to avoid reducing a complex event to a single explanation.
A flight that lasted less than five minutes
US Airways 1549 was to link New York's LaGuardia Airport with Charlotte. The Airbus A320-214 N106US carried 150 passengers; the crew included two pilots and three flight attendants. Commander Chesley Sullenberger had a large total raid and experience of glider flights, co-pilot Jeffrey Skyles recently underwent retraining on the A320 and on this flight performed takeoff.
The plane broke away from lane 4 at about 15:25 local time. Two minutes later, he walked about 2,800 feet and continued typing. The stage was the most unfavorable for double thrust loss: the airport was already left behind, but there were no heights for long planning, complete diagnostics and several launch attempts.
A flock of Canadian geese appeared ahead of almost no time for evasion. These birds are larger than the mass underlying part of the engine certification scenarios. The attacks happened almost simultaneously. The pilots heard the shocks, felt the vibration and smell, and the parameters of both engines deteriorated sharply. They did not collapse completely, but the available thrust became close to zero.
The event did not look like a neat shutdown of two identical systems. The instruments showed changing turns, the aircraft continued to move on inertia, and the crew needed to distinguish partial thrust from useless rotation of the compressors. During this time, the A320 reached a maximum altitude of about 3,000 feet and began to decline steadily.
Manage, diagnose, choose
Thirteen seconds after the strike, the commander declared "my plane". This short phrase eliminated the uncertainty: Sullenberger focused on the trajectory, Skyles on the control map of double thrust loss and launch attempts. Such a transfer did not mean the superiority of one pilot; it used fresh practical training of the second pilot on the A320 systems and freed the commander to select the site.
The control card was designed mainly for failure at a higher altitude. It contained actions that, under normal time, were performed sequentially, but over New York the plane lost hundreds of feet in tens of seconds. The crew did not reach all points. This is not a mechanical error of execution: in an accident, the priority "fly - navigation - communication" is more important than the formal completion of the document.
LaGuardia dispatcher immediately offered a return and freed the lanes. From the ground, the airport seemed like a natural solution, but the pilots saw the speed, altitude and rate of decline. Turning consumes energy and increases the path. An error in evaluation for a few seconds could leave the plane over dense urban development without a river and without a lane.
Then Teterboro was considered. The commander briefly agreed to try, but almost immediately saw that the stock did not add up. At 15:29:28, he finally announced that the plane would be on the Hudson. After that, the options were no longer discussed. The crew moved on to configuration, speed, flap position, launch auxiliary power plant and cabin preparation.
It was only half the task.
For landing, you need to simultaneously withstand a small vertical speed, almost zero roll and positive pitch. Too raised nose threatens to hit the tail, too low - the destruction of the front; roll forces one wing to hook the water and turns the plane. Without thrust, it is much more difficult to adjust the trajectory at the last moment, and protection at the angle of attack limits the reaction of the aircraft.
The chassis was removed. Released racks would increase the resistance still in the air and could cling to the water, creating a sharp rotation. The flaps were placed in an intermediate position to gain lift power, but not to lose too much range. The auxiliary power plant retained electrical power and helped the control systems to remain in normal configuration.
When touching the tail part of the fuselage was damaged, the water began to flow inside. The rear exits and part of the equipment were not suitable. Flight attendants independently changed the evacuation plan, directing people forward and onto the wings. Some passengers went out without outerwear, many did not take life jackets, and the water temperature posed a threat of hypothermia.
Survival was determined by the coincidence of several barriers. The aircraft accidentally had extended equipment for flights over water, although the route did not require it in full. Nearby were passenger ferries, whose crews immediately approached the wings. Firefighters, police and divers quickly established a second rescue line. All 155 people left the plane alive.
Why Simulator Doesn't Cancel Reality
After the incident, the researchers repeatedly simulated a return to LaGuardia and Teterboro. If the pilot began a perfect turn immediately after the birds hit, some attempts ended with a landing. But such a scenario presupposes impossible knowledge: a person understands the exact scale of the damage even before the strike, does not waste time on recognition and chooses the right strip without discussion.
When a realistic delay in evaluation and decision was added to the simulation, the probability of a successful return dropped dramatically. This is one of the most important principles of the analysis: you can not judge the actions of the crew on the information received by the commission for months of work. It is necessary to restore what data was available at a particular second, how reliable they were and what solution remained reversible.
NTSB called the likely cause of the hit of large birds in both engines. Among the factors of damage to the fuselage, the commission noted restrictions on certification of splashdown, a lack of industry training and overloading with tasks at the final site. Among the factors of survival are solutions and CRM pilots, the work of flight attendants, advanced rescue equipment and the immediate arrival of ships.
The recommendations covered engine crash tests with flocks of large birds, engine diagnostics, control chart structure, low-altitude double failure training, splashing technique, brace position, vests, and ornithological risk management. Therefore, the history of Hudson is not only a story about the skill of two pilots, but an example of how many independent links saved people’s lives.
Sequence
Event timeline
Rather than isolated episodes, this was an unfolding system: each stage inherited the constraints of the one before it.
- 01
Birds on course
At an altitude of about 830 meters, the crew saw a flock. It was already impossible to evade; the blows and hits of birds in both engines occurred almost immediately.
- 02
Transfer of control
The commanding officer pronounced "my plane", and the co-pilot focused on the dual engine failure map. This separation retained controllability and simultaneously launched diagnostics.
- 03
Mayday and Turn
The crew reported the failure of both engines and began a left turn. The dispatcher immediately released the strips, based on the initial intention to return.
- 04
No return is possible
The commander said the plane could be in the Hudson. The height quickly decreased, and the attempt to reach the strip threatened to fall in the built-up area.
- 05
Final decision
After a brief evaluation of Teterborough, the crew recorded the choice of the river. The cabin went from searching the airfield to configuration and preparation to touch.
- 06
Ditching
The aircraft touched the water with a small heel angle and positive pitch. Evacuation began immediately, and the approaching ferries became a critical link in the rescue.
More than one cause
Chain of contributing factors
An incident develops when several weaknesses come together along the same path.
Simultaneous loss of traction
The mass and number of birds exceeded the scenario for which the engines were certified. Both engines continued to rotate, but did not give the necessary thrust.
Deficit of height
In contrast to the failure at the echelon, the crew did not have time to complete a long control card or check the options several times.
Resource management
The commander piloted and selected the site; the co-pilot tried to restart the engines; the dispatcher freed the routes; the flight attendants prepared the cabin.
The Rescue Environment
Cold water poses a distinct threat. The rapid arrival of urban ferries has reduced the time people spend on wings and in the water.
From the flight deck
Decisions and constraints
Decisions are assessed against the information, altitude, time and aircraft condition at that moment, rather than what became known later.
Why not return to LaGuardia?
Later simulations sometimes showed a mathematical possibility of return only with an instant reversal. When normal recognition and decision times were added to the calculation, success declined dramatically.
Why the chassis was removed
The chassis would have increased resistance, worsened planning, and could have hooked more heavily on water. The smooth lower surface gave a more controlled slide.
What we did not have time to do
The short height did not allow to pass the entire control card and fully prepare the cabin. Success arose not from the perfect performance of each point, but from the right priority: to fly an airplane, choose an achievable platform, prepare people.
Summary
Investigation findings
- The reason for the loss of traction was the hit of large birds in both engines.
- The decision to float provided the greatest chance of survival in the real time available.
- The work of the crew, dispatchers, flight attendants and rescue vessels formed a single successful chain.
- The aircraft and procedures were not designed for the entire set of conditions: double loss of thrust at low altitude and immediate splashing in cold water.
After the investigation
What aviation learned
A lesson becomes useful when it leads to a procedure, training, a design change or a new safety barrier.
Low altitude scenarios
The investigation recommended taking into account the dual engine failure shortly after takeoff in maps and training.
Protection from birds
The recommendations concerned engine tests on large bird flocks, population management and risk data sharing.
Equipment and evacuation
They discussed life jackets, the availability of rafts, crew to passengers and the suitability of equipment on flights, the route of which formally passes over land.
Its relevance today
The successful outcome should also be investigated strictly.
Hudson is often retold as the story of one perfect solution, but the NTSB has shown a more useful picture. Survival was created by pilots, flight attendants, the design of the A320, accidentally expanded water equipment, the discipline of most passengers, dispatchers and ferries. Removing any link could significantly change the outcome.
That is why a successful accident is investigated not softer than a catastrophe. Damage to the tail, the inaccessibility of the rear stairs, the complexity of the vests and an incomplete control map revealed real vulnerabilities. The absence of fatalities does not mean the absence of system defects; it provides a rare opportunity to learn from the testimonies of all participants.
For decision-making, Flight 1549 remains a classic example of realistic delay. The commission must add the time that a live crew needs to recognize an unknown threat. Otherwise, the simulator turns into an unfair judge who knows the exact refusal and the correct answer in advance.