Federal Express Boeing 767 300F incident
Boeing 767 300F · Incident: birdstrike during initial climb
From Newark Liberty International Airport (EWR) to Indianapolis International Airport (IND)
Event
- NTSB case
- DCA25FA148
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Incident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Ongoing
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- 0
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- Airline
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Boeing 767 300F
- Aircraft type
- Boeing 767
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N178FE
- Operator
- Federal Express
- Onboard fatalities
- Unknown
- Route
- From Newark Liberty International Airport (EWR), Newark, NJTo Indianapolis International Airport (IND), Indianapolis, IN
- Aircraft age
- About 6 years (built 2019)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 121: Air Carrier
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Initial climb
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Birdstrike
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Minor
Cause areas
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
On March 1, 2025, at 0800 eastern standard time, FedEx flight 3609, a Boeing 767-300F, powered by two General Electric CF6-80C2 turbofan engines, registration number N178FE, struck birds during initial climb after takeoff from Newark Liberty International Airport (EWR), Newark, New Jersey. There were no injuries to the 2 crew and 1 passenger on board. The flight was conducted under the provisions of Title 14 Code of Federal Regulations Part 121 domestic cargo flight from EWR to Indianapolis International Airport (IND), Indianapolis, Indiana.
The flight crewmembers reported that after takeoff and while climbing through an altitude of about 500 ft, the first officer (FO), who was the flying pilot, saw three white birds to the left side and underneath the airplane. He called “Birds!” and immediately thereafter heard an “abrupt bang” and the airplane experienced moderate to severe vibrations. The FO began a right turn back towards the airport and asked the captain to declare an emergency and advise Air Traffic Control (ATC) that they were returning to EWR.
The captain checked the engine indications “which soon displayed right engine damage including fire indications (fire bell, warning lights, discrete fire light on the right fuel control) and an R ENGINE FIRE message on the Engine Indicating and Crew Alerting System (EICAS) display”. As the FO continued to fly, the captain began the quick reference checklist (QRC) for the ‘ENGINE FIRE or Engine Severe Damage or Separation’, which resulted in the shutdown of the No. 2 (right engine) and discharge of one fire bottle. After the engine was shutdown, the airplane “flew much smoother” and the noise level reduced substantially. As the captain continued through the follow-up quick reference handbook (QRH) procedure, the fire indications persisted, and he discharged the 2nd fire bottle. However, the fire indications remained present for the rest of the flight.
The crew asked the passenger, who was type rated in the airplane, to move to the first observer seat and assist with checklists and airplane monitoring. During the base traffic pattern leg, the captain took control of the airplane from the FO, who assumed the pilot monitoring duties. After issuing the landing clearance, ATC initially advised that it appeared as though the fire on the right engine had gone out. Shortly afterward ATC called and advised there was fire visible on the right engine.
After landing, the captain stopped the airplane on the runway, shut down the left engine and contacted the aircraft rescue and fire fighting (ARFF) responders on the tower frequency. ARFF advised that fire was still visible, and they began applying water. Soon after, all the fire indications in the cockpit ceased. After receiving an “all clear” from the ARFF responders, the crew exited the airplane via the crew stairs.
A post accident examination of the airplane revealed bird remnants on the No. 1 engine nacelle (on the inside and outside of the inlet) as well as on sections of the engine spinner, fan blades, inlet and outlet guide vanes, the thrust reverser blocker doors, and on the drag link arms. All the fan blades were present and whole, several of the fan blades exhibited round soft-body airfoil leading-edge impacts and blade tip bending. The nacelle inlet lip skin was dented/impacted at about the 9:00 o’clock position with evidence of bird remains at the 2:30 o’clock position but no impact damage.
Bird remnants were present on the No. 2 engine spinner and fan blades, and on the thrust reverser blocker door drag links. All of the fan blades were present and exhibited a combination of leading edge and airfoil hard-body impact, missing material, gouging, tip rub, rips and tears, and bending in both the direction opposite of rotation and in the direction of rotation. One blade was fractured just outboard of the mid-span shroud. The inlet inner barrel liner exhibited multiple impact marks, holes, areas of missing material, trenching, and embedded metallic material, around the entire circumference.
Figure 1. Picture of the inlet of engine No. 2 (right engine).
Several through-hole penetrations were also noted in the inlet outer barrel. The outer skin of the turbine exhaust sleeve departed the engine and was recovered in a grassy field near Interstate 95 along the airplane’s flight path. The No. 2 engine was heavily damaged by fire. Sooting and thermal distress were present 360° circumferentially from the aft flange of the aft fan case to the rear flange of the combustion case. Sooting was also present along the length of the top of the engine from the 11:00 – 1:00 o’clock position. Thermal distress consisted of consumed electrical wire outer sheathing and isolator grommets, as well as damaged or consumed wire clamp cushions. Portions of some air, oil, and fuel tubes were consumed by fire.
Figure 2. Left and right sides of engine No. 2.
The right side of the airplane exhibited multiple small impact marks in the horizontal stabilizer, fuselage, and the wing control surfaces, consistent with debris liberated from the No 2 engine. None of this damage met the definition of substantial damage or affected the flight control system of the airplane.
Qualified parties were invited to participate in the investigation. These included the Federal Aviation Administration (FAA), Federal Express, Boeing Commercial Airplanes, and General Electric Aerospace. In accordance with the provisions of Annex 13 to the Convention on International Civil Aviation, an Accredited Representative from the Swiss Transportation Safety Investigation Board of Switzerland, the State of Manufacture for the engine vibration monitor, was appointed to support the investigation, with Paker Meggitt as a technical advisor. The following NTSB specialists were assigned to investigate the accident: Powerplants, Flight Data Recorder (FDR), and Cockpit Voice Recorder (CVR). The FDR and CVR were sent to the NTSB’s Vehicle Recorder Laboratory in Washington, DC. The investigation is continuing.
Verbatim NTSB factual narrative from the NTSB dataset
Sources
NTSB record DCA25FA148
- Event ID
- 20250301199780
- Case number
- DCA25FA148
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: c0a54dd82ffdfdebc19b55c019ba6b7d02fb7a32d3d811ed7d9b014262a98f71; retrieved 2026-09-16T19:42:00.781Z.