Spirit Airlines Flight 3044
Airbus A320-271N · Incident: birdstrike during takeoff
From Atlantic City International Airport (ACY) to Fort Lauderdale Hollywood International Airport (FLL)
Event
- NTSB case
- ENG22LA002
- 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
- Completed
- Event fatalities
- Unknown
- Ground fatalities
- Unknown
- 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
Airbus A320-271N
- Aircraft type
- Airbus A320
- 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
- N922NK
- Operator
- Spirit Airlines
- Onboard fatalities
- Unknown
- Route
- From Atlantic City International Airport (ACY), Atlantic City International Airport, NJTo Fort Lauderdale Hollywood International Airport (FLL), Ft. Lauderdale-Hollywood International Airport, FL
- Aircraft age
- About 2 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
- Takeoff
- 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
- Environmental issues › Physical environment
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
Based on the bird remains and feathers collected and identified by Smithsonian Institution National Museum of Nature History Division of Birds - Feather Identification Laboratory, a male immature Blade Eagle was ingested into the right engine striking the fan and causing a single fan blade to fracture near the blade root; the fractured fan blade was contained by the fan case and the remaining fan blades exhibited a combination of leading and trailing edge, as well as blade tip, impact damage, tearing, missing material and bending in the direction opposite rotation. Upon further examination of the engine, it was discovered that two of the thermal management system (TMS) manifold lower aft mounting bracket securing bolts had fractured in shear overstress allowing the bracket to swivel/rotate radially outward. This is one of three mounting brackets that secure the TMS manifold to the engine and prevents excessive moment of the TMS manifold during operation. Along with the broken/sheared TMS lower aft bracket bolts, a crack was visible on the CP-09 fuel line that initiated in fatigue; the CP-09 fuel line is attached to the TMS and contains high pressure fuel. The crack in the CP-09 fuel line was due to necking down of the material as the fuel tube bent and stretched (elongated) under the vibration/cyclic loads after the bird strike and not as a manufacturing issue.
The TMS manifold lower aft mounting bracket securing bolts fractured due to the high impact and vibration loads because of the fan blade release after the bird strike. Subsequently the TMS manifold was allowed to move radially back and forward from the engine in response to the engine vibrations that were recorded on the flight data recorder to be in excess of the 10 cockpit units which is the highest value that the flight data recorder will record. The CP-09 fuel line flexed, bent, and stretched under the cyclical radial motion of the TMS manifold until it cracked due to fatigue spraying high pressure fuel onto the hot engine cases igniting an undercowl fire.
An immature male Bald Eagle has a mean mass of about 4,130 grams (g) (9.1 lbs.). The Federal Aviation Administration large bird ingestion certification test bird weight requirement was 2.75 kilograms (6.05 pounds) for the size of the inlet throat area on the PW1127G-JM geared turbofan engine; thus, the incident ingested bird was larger than the certification basis for the engine.
Probable cause
The ingestion of a bird into the right engine during the takeoff roll caused a fan blade to fracture near the blade platform resulting in high fan blade off loads and engine vibrations sufficient to result in an eventual failure of a fuel tube in the right engine that sprayed fuel onto hot engine cases, igniting an undercowl engine fire and triggering a rejected takeoff.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ENG22LA002
- Event ID
- 20211004104029
- Case number
- ENG22LA002
- 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, cause areas. 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: d7247273e062edd9563f303e0dfe7149a4451391d419694b46379d0210e62a66; retrieved 2026-09-16T14:36:57.574Z.