FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Southwest Airlines Flight 554

20 Dec 2023 · Kenner, LA, United States

Boeing 737-8 · Incident: birdstrike during takeoff

From an unrecorded airport to Tampa International Airport (KTPA)

Report a problem

Event

NTSB case
DCA24LA330
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

Boeing 737-8

Aircraft type
Boeing 737
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
N8830Q
Onboard fatalities
Unknown
Route
From not recordedTo Tampa International Airport (KTPA), Tampa, FL
Aircraft age
About 1 year (built 2022)
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

  • Aircraft › Aircraft power plant
  • 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

During initial climbout shortly after takeoff, Southwest Airlines flight 554 struck and ingested a bird into its No. 1 (left) engine, resulting in damage to the left engine fan blades and a partial loss of engine power. The airplane began to “shake violently with a distinct loss of thrust” in the left engine. The engine master caution activated, and the captain reported that he heard the fire bell sound. The captain called for the Engine Fire or Engine Severe Damage or Separation checklist on the Quick Reference Card (QRC). According to the captain, after the first officer (FO) started the checklist, the cockpit began to fill with “acrid white smoke.” The FO called out “masks,” the pilots donned their masks, and they resumed performance of the checklist. The flight crew declared an emergency to air traffic control and requested airport rescue and firefighting (ARFF) in preparation for the flight’s return to the departure airport. The flight crew notified the cabin crew and passengers about the emergency. The captain later reported that, due to the smoke, his instrument panel was difficult to see and that he thought he might need to fly the airplane by solely using the heads-up guidance system. However, the captain stated that the smoke began to rapidly dissipate after the FO pulled the engine fire switch. After flight 554 landed and came to a full stop, ARFF personnel inspected the airplane before the flight crew taxied to the assigned gate. The passengers deplaned normally, and no injuries were reported. Postaccident examination found that the smoke in the cockpit was a result of the activation of the No. 1 engine’s load reduction device (LRD) after the bird ingestion. LRD activation is designed to reduce the severity of the vibration transmitted into the airframe by disconnecting the left engine’s fan blades from the turbomachinery. When the LRD activated, tubes supplying oil to the engine sump became dislodged and the flange from the sump area opened, allowing engine oil to enter the core compressor upstream of the pneumatic bleed ports that supply bleed air to the cabin and cockpit. The oil was exposed to high temperatures and resulted in smoke and fumes that were then fed into the cockpit. About 15 seconds after the bird ingestion, the left engine’s core speed (N2) was below 62% rpm, which would have de-energized the engine’s running relay and subsequently closed the pressure regulating shutoff valve (PRSOV). Following the closure of the PRSOV, which was the point of access into the cockpit, the smoke and fumes would have quickly dissipated. Considering that both crewmembers described the airplane as shaking following the bird ingestion, the captain’s decision to begin the Engine Fire or Engine Severe Damage or Separation checklist was appropriate (one of the conditions for using the checklist was airframe vibrations). Although the crew did not report performing the Smoke, Fire or Fumes checklist, the first officer stating “masks” accomplished two of the three memory items by donning their one-piece oxygen masks. Postincident review of this checklist found that it instructed pilots to turn off various switches, including the RECIRC FAN switches at step 9. It is not until step 11 that the checklist instructs that if the smoke or fumes become the greatest threat, pilots should reference another checklist. It is likely that the incident flight crew would have performed the Smoke, Fire or Fumes checklist first if they had not experienced severe airframe vibration following the bird ingestion. Boeing released a flight crew operations manual (FCOM) bulletin on February 9, 2024, that described the results of the bird ingestion in this incident and the actions a flight crew should take if they experience a similar incident. Boeing also updated the system description in the Boeing 737-8 FCOM on November 15, 2024, and the Quick Reference Handbook (QRH) on November 30, 2024, to include engine failure with smoke or fumes in the flight deck or cabin as a condition to trigger reference to the Engine Fire or Engine Severe Damage or Separation QRC. Although the NTSB found no clear evidence of significant toxic or irritant exposure to the flight crew resulting from the LRD activation on the incident flight, such an event may pose a toxicological risk. There are insufficient data to reliably determine the nature and magnitude of such risk, especially at what is expected to be limited exposure duration. It is reasonable to consider the potential for irritant effects on the pilots among the threats to the immediate safety of the flight in an LRD-related smoke event.

Probable cause

A partial loss of engine power due to bird ingestion in the No. 1 (left) engine, which resulted in the activation of the load reduction device to prevent vibration. The load reduction device activation resulted in smoke and fumes entering the cockpit.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DCA24LA330
Event ID
20241121195527
Case number
DCA24LA330
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: 150d3dff5f3026aca0b7321c9b1d56cdaeb840fd1dd34982cbdac7153f116b81; retrieved 2026-09-16T19:29:29.113Z.