13 May 202513:01 reconstruction4K views

SWA 3472: Another Engine Blowout—Just 5 Years After SWA 812's Mid-Air EXPLOSION (2016)

Advertisement

Southwest 3472 — The Engine Failure That Exposed a Fan-Blade Fatigue Problem

On August 27, 2016, Southwest Airlines Flight 3472 was climbing over the Gulf of Mexico when its left CFM56-7B engine suffered an uncontained failure. The Boeing 737-700, registered N766SW, was operating from New Orleans to Orlando with 99 passengers and five crewmembers. The engine failure damaged the inlet and fuselage and caused cabin depressurization, forcing the crew to divert to Pensacola.

The Failure at Flight Level 310

The NTSB states that the event occurred at about 0930 Central Daylight Time while the aircraft was climbing through FL310. The failure involved fan blade No. 23. A fatigue crack in the blade’s dovetail allowed the blade to separate. The released blade struck the fan case, fragmented and sent debris into the engine inlet.

Damage Beyond the Engine

The engine event was not contained within the engine. The NTSB found that the blade fragments traveled farther than expected into the inlet and compromised its structural integrity. Inlet components separated in flight. A portion of the inlet struck the fuselage and created a hole, causing the cabin to depressurize. The aircraft also sustained substantial damage to other areas.

The Emergency Descent and Diversion

The crew declared an emergency and diverted to Pensacola International Airport. Oxygen masks deployed after the loss of cabin pressure. NTSB factual material shows that the aircraft continued to fly for roughly another 18 minutes after the fan-blade separation and landed safely at about 0940 local time. None of the 104 people aboard were injured.

Why the Fan Blade Became the Focus

The investigation did not stop at identifying the broken engine. Metallurgical examination established the fatigue origin in the fan-blade dovetail. The event became important to later CFM56-7B fan-blade inspection work because the failure mechanism involved a component that had accumulated fatigue damage before separation.

A Safety Record That Continued After the Landing

NTSB and FAA documentation following Flight 3472 shows that the event contributed to subsequent inspection and corrective-action work for CFM56-7B fan blades. The investigation record later referenced additional inspection methods for fan-blade dovetails. The significance of Flight 3472 therefore extends beyond the emergency landing: the investigation connected the in-flight failure to a specific fatigue mechanism and helped drive changes in how similar components were examined.

Inside the failed engine

The NTSB investigation traced the initiating damage to fan blade No. 23. A low-cycle fatigue crack developed in the blade dovetail and grew until the blade separated. The released blade struck the fan case and fragmented. Those fragments traveled into the inlet and damaged its structure. The inlet then separated in flight, and a portion struck the fuselage, creating a hole and causing the cabin to depressurize. The NTSB’s factual material also shows that the flight data recorder continued to capture the event for several minutes and that the airplane remained controllable enough to continue toward Pensacola. Pilot statements placed the safe landing at about 9:40 a.m., roughly 18 minutes after the fan-blade separation. Subsequent FAA and CFM documentation addressed fan-blade dovetail inspection practices. The significance of the accident therefore extends from the immediate emergency to a component-level fatigue problem that required changes in inspection attention.

The investigation after the safe landing

The NTSB’s technical work also examined the condition of the affected fan blade and related components. The documented fatigue crack in the dovetail was not a superficial observation; the investigation traced the fracture mechanism through the blade separation, fan-case impact and subsequent inlet damage. The event became particularly significant because the same CFM56-7B engine family later experienced another full-length fan-blade release on Southwest Flight 1380 in 2018. The later accident is not part of the 2016 occurrence and is not used to alter its facts, but the NTSB’s subsequent safety work explicitly reviewed the two events together when discussing fan-blade inspection measures. After Flight 3472, CFM developed additional inspection procedures for fan-blade dovetails, and the FAA and EASA issued related airworthiness actions. The 2016 event therefore produced both an emergency landing and a documented technical response aimed at preventing recurrence.

The safety response

The technical consequences continued after the aircraft was repaired. NTSB and FAA records document subsequent work on CFM56-7B fan-blade inspections. The investigation noted that CFM developed an eddy-current inspection procedure for the dovetail at overhaul, in addition to existing fluorescent-penetrant inspection. Later service bulletins and regulatory actions addressed ultrasonic inspection and repetitive inspection of affected fan blades. Those measures were not part of the emergency response on August 27, 2016, but they are part of the documented investigation outcome. They show that the probable cause was not merely recorded as an isolated blade break: the event was used to identify a fatigue mechanism and improve the inspection regime for the component.

The cabin-pressure event

The cabin depressurization was a separate stage of the emergency. NTSB records show that the inlet separation created an opening in the fuselage, while the released fan and inlet material did not directly penetrate the passenger compartment. Oxygen masks were deployed and the crew diverted to Pensacola. The safe landing does not reduce the seriousness of the event: the aircraft sustained substantial damage and required an emergency response, but the flight crew retained sufficient control and performance to complete the diversion. The investigation’s component-level conclusion is also why the event should not be described simply as an engine explosion. The initiating mechanism was a fatigue crack in a fan-blade dovetail, followed by blade separation, fan-case impact, inlet damage, fuselage penetration and cabin depressurization. Each stage is documented separately in the NTSB record.

Accident Facts

Date
August 27, 2016
Aircraft
Boeing 737-700
Registration
N766SW
Event
Southwest 3472 — The Engine Failure That Exposed a Fan-Blade Fatigue Problem
Category
Fatal Crash
Timeline
August 27, 2016, about 0930 CDT —
Southwest 3472 was climbing through FL310 over the Gulf of Mexico.
1.
During the climb —
Fan blade No. 23 separated after a low-cycle fatigue crack developed in its dovetail.
2.
Immediately afterward —
Fan debris damaged the inlet and components separated from the engine.
3.
During the emergency —
An inlet section struck the fuselage and cabin pressure was lost.
4.
Shortly afterward —
The crew diverted toward Pensacola and conducted the emergency descent.
5.
About 0940 CDT —
The aircraft landed safely at Pensacola.
6.
After the accident —
The NTSB completed the investigation and corrective inspection work followed.
7.

Sources

Audio from the original air traffic control recording, sourced from public recordings and released investigation records. The reconstruction, animation and written account are our own.
Advertisement

The weekly incident