Photo: Plenumchamber, licensed under CC BY-SA 3.0.
There’s no worse moment for a bird to cross your flight path than the two or three seconds after rotation. You’re airborne but barely so — too fast and too committed to stop on the remaining runway, too low and too slow to have the full climb performance a jet is designed around. If the strike is a single bird, it’s usually a loud bang and a maintenance write-up. If it’s a flock, both engines can go quiet at once, and the crew has to fly a genuine emergency with almost no altitude to work with.
Three times it happened for real
Bird strikes at rotation aren’t a theoretical training scenario — they’ve shaped how airplanes are certified and how crews are trained, largely because of a handful of incidents that went very differently from each other.
Eastern Air Lines Flight 375, a Lockheed Electra departing Boston in October 1960, flew into a 20,000-strong flock of starlings seconds after liftoff and lost control from asymmetric engine thrust. US Airways Flight 1549, an Airbus A320 departing LaGuardia in January 2009, lost both engines to a flock of Canada geese and ditched in the Hudson River. Ural Airlines Flight 178, an A321 departing Zhukovsky in August 2019, struck birds in both engines during rotation and came down gear-up in a cornfield.
What separates the 1960 Boston accident and the 2019 Moscow accident from the 2009 Hudson ditching isn’t luck alone. Sullenberger and Skiles had roughly three minutes and about 2,800 feet to work the problem before committing to a landing site — enough altitude to think. The Eastern and Ural crews had seconds and a few hundred feet. That’s the entire argument for why the procedures below exist: they’re designed to buy a crew the clearest possible picture of the aircraft before it runs out of altitude to use.
A recent case close to home
This isn’t just a historical pattern. On Friday, 17 July 2026, Air Serbia Flight JU130, an Airbus A320 (registration YU-APH) departing Belgrade Nikola Tesla Airport for Moscow, struck a bird shortly after takeoff, during the initial climb. The impact damaged the right engine. The crew declared “PAN PAN” — the standard urgency call, one step below a Mayday — and elected to return rather than continue toward Moscow. Public flight-tracking data shows the aircraft flying two holding patterns south of Belgrade — a larger one first, then a tighter one closer in — before lining up and landing back at Belgrade without incident. Nobody on board was hurt.
It’s a textbook illustration of everything above, at a much smaller scale than Eastern 375, Ural 178, or the Hudson: a single engine affected rather than both, altitude and time enough to run the procedure properly, a deliberate return rather than a scramble, and an outcome that barely made the news because the system worked exactly as designed.
The first ten seconds: fly the airplane, then diagnose
The instinctive reaction to a bang, a flash, or a smell of burnt feathers is to look for what happened. That’s the wrong first move. The trained response is to hold pitch and airspeed and let the engine instruments — not assumption — say what’s actually going on. A strike on one engine is a very different problem from a strike on both, and at 300 feet you often can’t tell the difference by feel alone.
If the indications are severe — an engine fire warning, or clear signs of a severe, uncontained failure — the response is a set of memory items: thrust lever to idle, the affected engine’s fuel/master switch off, fire agent discharged if called for. These are done from recall, before anyone opens a checklist, because there isn’t time to read. Anything short of that — vibration, an EGT spike, suspected damage without fire — is flown as a controlled single-engine (or reduced-thrust) climbout while the crew works the applicable non-normal procedure.
On Airbus aircraft this is largely ECAM-driven: the system detects the failure and presents the checklist. Boeing crews lean more on recognizing the failure themselves and pulling the correct QRH procedure. Either way, once the memory items (if any) are complete, the rest is worked deliberately — item by item, not from memory, and not rushed.
Why crews hold instead of turning straight back
Once the aircraft is climbing safely and the checklist is under control, the instinct from the ground looking up is usually “just land, now.” In practice, crews will almost always request a hold near the departure airport instead of an immediate return. The hold isn’t hesitation — it’s exactly what separates a controlled outcome from a rushed one.
That time is used to finish the non-normal checklist properly, brief the cabin crew on what happened and whether landing will require an evacuation, get passengers briefed and the cabin secured, recompute landing performance for the aircraft’s actual configuration, and coordinate the approach and any emergency services with ATC. It’s also, simply, time to think rather than react — the Ural 178 investigation is often cited precisely because the crew didn’t use the altitude they had to fully stabilize the aircraft’s energy state before landing.
The other reason to hold: weight
Most jets take off well above their maximum landing weight, since they burn down fuel over the course of a normal flight. Landing overweight increases stopping distance and structural loads on the gear and airframe, so if there’s no urgency — no fire, no fuel leak, damage that’s serious but controllable — the crew will hold and burn fuel down toward max landing weight, or, on aircraft fitted with a jettison system, dump fuel to get there faster.
But weight is never allowed to be the deciding factor in when to land. Every certified transport aircraft has an Overweight Landing procedure in the QRH for exactly this situation: it adjusts approach speed, sets the expectation of a firmer-than-normal touchdown, and requires a structural inspection once the aircraft is on the ground. If the situation is time-critical, crews are trained to use it without hesitation rather than extend a hold to chase a fuel number. The rule that gets taught: burn or dump fuel if you have time to spare, land overweight if you don’t — but never delay a landing you actually need to make.
The takeaway
None of this is about memorizing a script for its own sake. Every step — the memory items, the deliberate checklist pace, the hold, the weight decision — exists to give a crew the clearest possible picture of a damaged aircraft before altitude runs out. Eastern 375 didn’t have that time. US Airways 1549 did, and used every second of it. That’s the entire difference the procedure is designed to protect.
