Stay up to date with notifications from The Independent

Notifications can be managed in browser preferences.

FedEx plane catches fire just after takeoff following birdstrike, forcing emergency landing at Newark Airport

A birdstrike was confirmed by authorities shortly after the flight made its emergency landing

Paul Farrell
Saturday 01 March 2025 15:00 GMT
Comments
FedEx plane makes emergency landing after engine catches fire mid-air

Officials have confirmed that a FedEx plane was forced into an emergency landing at Newark Airport early Saturday after a birdstrike caused an engine fire.

The flight had just taken off from the airport in New Jersey when the birdstrike occurred. A video circulating on social media showed the plane landing with a fireball visible on one of the plane’s wings around 8 am local time.

“Our crew declared an emergency and returned safely to Newark. We are thankful for the quick actions of our crew and first responders,” a FedEx statement reads. The Port Authority of New York and New Jersey were the first to confirm the birdstrike.

A witness told ABC New York that they believed the strike that occurred was a single bird.

“I was driving and saw something falling and then fire start on the right wing engine. I believe a bird went through the engine, a big bird. I was in shock. I stopped immediately on the turnpike. Thankfully nothing happened,” Sofiane Zeblah said.

Nobody is believed to have been injured as a result of the incident and airport operations were not impacted. It’s not clear how many people were on board at the time of the incident.

This is just the latest aviation incident in the U.S. in the wake of plane crashes in Alaska and Philadelphia as well as the D.C. plane disaster that claimed the lives of 67 people earlier this month.

Join our commenting forum

Join thought-provoking conversations, follow other Independent readers and see their replies

Comments

Thank you for registering

Please refresh the page or navigate to another page on the site to be automatically logged inPlease refresh your browser to be logged in