A FedEx cargo plane was forced to turn back to Newark Liberty International Airport on Saturday morning after one of its engines caught fire mid-flight. The cause? A bird strike shortly after takeoff.
The Boeing 767, operating as FedEx Flight 3609, was bound for Indianapolis when it collided with a bird, damaging one of its engines. Flames erupted. Smoke trailed behind. The pilots didn’t hesitate. They declared an emergency and made the call to return.
A Controlled Crisis
The plane landed safely. Emergency crews stood ready as the aircraft touched down, bringing the harrowing flight to an end. The Port Authority of New York and New Jersey confirmed that all three crew members on board were unharmed. Firefighters and airport operations teams moved in fast, securing the runway and assessing the damage.
Footage from the ground captured the eerie scene—fire licking the underside of the aircraft, black smoke curling into the morning sky. Social media lit up with speculation and concern.
FedEx Responds
FedEx issued a statement later that day. “Our crew declared an emergency and returned safely to Newark,” the company said. The aircraft was undergoing inspection, though no word was given on whether any cargo had been aboard. The airline remained tight-lipped beyond confirming that safety protocols were followed.
The Silent Threat in the Skies
Bird strikes are more common than most people realize. The Federal Aviation Administration (FAA) logged over 19,600 wildlife strikes in the U.S. last year alone. That’s 54 per day. Most cause little to no damage. But when they do, the results can be devastating.
Engines are built to withstand a lot, but birds pose a unique challenge. A large enough collision can shred turbine blades, disrupt fuel combustion, or—like in this case—ignite a fire. While air traffic controllers and ground crews do their best to keep flight paths clear, nature doesn’t follow schedules.
The 2009 “Miracle on the Hudson” remains the most infamous bird strike in aviation history. A flock of geese took out both engines of US Airways Flight 1549, forcing Captain Chesley “Sully” Sullenberger to ditch the plane in the river. Miraculously, all 155 passengers and crew survived.
This time, Newark’s FedEx flight ended without disaster. But the fire in the sky served as a stark reminder—nature and technology will always be at odds.
The Aftermath
The FAA confirmed that the engine sustained significant damage. The plane, now disabled on the runway, underwent a full inspection. Meanwhile, Newark Airport resumed normal operations within hours, showing just how routine aviation crises can be when handled well.
Experts are already debating what more can be done. Some suggest better bird-detection radar. Others propose different flight routes. But the reality is simpler: Some risks just can’t be eliminated.
As the FedEx plane sits in Newark, grounded but intact, one thing is certain—the skies are unpredictable. The next bird strike could be a harmless bump. Or it could be something far worse.
Dan is a contributor at New Jersey Digest, a software developer, and a dedicated jiu-jitsu practitioner with a passion for great food. A Bergen County native, he’s always seeking out new challenges—whether in coding, on the mats, or discovering the Garden State's hidden mysteries. When he’s not immersed in his work, you’ll find him training, exploring local restaurants, or unwinding with a round of golf.
