The U.S. aircraft register, updated daily
Accidents · NTSB DCA16FA217 · Final report

Boeing 737-700 accident near Pensacola, Florida, August 27, 2016

On August 27, 2016 at about 2:30 pm local time, a 2000 Boeing 737-700, registered N766SW, was substantially damaged in an accident during enroute near Pensacola, Florida (Pensacola airport). It was flown under scheduled airline rules (Part 121). No one was hurt; 104 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

A low-cycle fatigue crack in the dovetail of fan blade No. 23, which resulted in the fan blade separating in flight and impacting the fan case. This impact caused the fan blade to fracture into fragments that traveled farther than expected into the inlet, which compromised the structural integrity of the inlet and led to the in-flight separation of inlet components. A portion of the inlet struck the fuselage and created a hole, causing the cabin to depressurize.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
August 27, 2016 · about 2:30 pm local time
Place
Pensacola, Florida · Pensacola · map
Type
Accident
Injuries
No one was hurt; 104 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Boeing 737-700, built 2000 · all 737-700s on the register
Registration
N766SW · no longer on the register · serial 29806
Damage
Substantial damage
Flight
Flight · scheduled airline rules (Part 121)

The NTSB's narrative final · quoted from the NTSB record

The Boeing 737-700 airplane was climbing through flight level 310 when fan blade No. 23 in the left CFM56-7B engine fractured at its root, with the dovetail (part of the blade root) remaining within a slot of the fan disk. The separated fan blade impacted the engine fan case and fractured into multiple fragments. The blade fragments traveled forward into the inlet and caused substantial damage that compromised the structural integrity of the inlet, causing most of the inlet structure to depart from the airplane. A large portion of the inlet contacted and punctured the left side of the fuselage, creating a hole of sufficient size to cause the cabin to depressurize. The flight crew conducted an emergency descent and landed safely at Pensacola International Airport, Pensacola, Florida, about 21 minutes after the fan-blade-out (FBO) event occurred.    The fan blade fractured due to a low-cycle fatigue crack that initiated in the blade root dovetail under the blade coating near the outboard edge. Metallurgical examination of the fan blade found that its material composition and microstructure were consistent with the specified titanium alloy and that no surface anomalies or material defects were observed in the fracture origin area. The fracture surface had fatigue cracks that initiated close to the dovetail leading edge convex side area, which is where the greatest stresses from operational loads, and thus the greatest potential for cracking, were predicted to occur. The fan blades were not certified as life-limited parts. The accident fan blade (as well as the six other cracked fan blades in the accident engine) failed with 38,152 cycles since new. Similarly, the fan blade associated with an April 2018 FBO accident (case number DCA18MA142) failed with 32,636 cycles since new. Further, 19 other cracked fan blades on CFM56-7B engines had been identified as of January 2020, and those fan blades had accumulated an average of about 33,000 cycles since new when the cracks were detected. After this accident, CFM reevaluated the fan blade dovetail stresses and determined that the fatigue cracks initiated in an area of high stress on the dovetail and that the dovetail was experiencing peak stresses that were higher than originally predicted. CFM found that the higher operational stresses resulted from coating spalling, higher friction levels when operated without lubrication or a shim, variations in coating thickness, higher dovetail edge loading than predicted, and a loss or relaxation of compressive residual stress (the stress that is present in solid material in the absence of external forces). Before the application of the dovetail coating during manufacturing and before the reapplication of the coating that is stripped during each overhaul, the entire blade, including the dovetail, is shot-peened to provide a compressive residual stress surface layer for the material, which increases the fatigue strength of the material and relieves surface tensile stresses that can lead to cracking. A loss of residual stress could be the result of a fan blade's exposure to high temperatures during the application of the dovetail coating as part of the overhaul of a blade set, but no evidence indicated that the accident fan blade dovetail was subjected to an overheat situation during the coating repair process. However, higher-than-expected dovetail operational stresses could also lead to the loss/relaxation of residual stress and premature fatigue crack initiation, which occurred during this event. Residual stress measurements were taken from multiple areas of the dovetail surface on fan blade No. 23 and eight other blades from the accident engine, including three blades with no identified cracks. All nine blades had abnormal residual stress profiles compared with the reference profile data. One method that CFM recommended to maintain the fan blade loads within the predicted range and reduce the overall stresses on the blade root in the contact areas is repetitive relubrication of the fan blade dovetails. As part of the relubrication procedure, the fan blades were visually inspected for crack indications. The investigation of this accident found fan blade cracks that had initiated and propagated underneath the dovetail coating. Because such cracks might not be detected during a visual inspection, CFM implemented, in March 2017, an on-wing ultrasonic inspection method to detect cracks with the coating still on the dovetail. A review of the fan blade overhaul process found that a fluorescent penetrant inspection (FPI) was performed (as specified in the CFM engine shop manual) during the fan blade set's last overhaul in August 2007 to detect cracks. As a result of this accident, CFM implemented, in November 2016, an eddy current inspection (ECI) technique for the fan blade dovetail as part of the overhaul process (in addition to the FPI). An ECI has a higher sensitivity than an FPI and can detect cracks at or near the surface (unlike an FPI, which can only detect surface cracks). The shims for fan blade Nos. 22 through 24 had a newer design configuration that was introduced after the blades and their associated hardware were first installed on the accident disk. Wear patterns on the shims from blade Nos. 23 and 24 showed that a significant area of coating was missing from the blade dovetails at the time that the shims were installed. The location of the missing coating was in the area where overhaul of the blades was required within 50 cycles. The National Transportation Safety Board could not determine, with the available evidence, how long the dovetail coating damage existed and whether the cracks were large enough to be detected by an FPI during an overhaul in response to the coating damage (when the dovetail coating damage first became significant enough during visual inspections conducted at relubrication to trigger the overhaul).   The damage to the accident inlet and fan case showed that there were significant differences between the accident FBO event and the engine FBO containment certification tests. For example, during the accident FBO event, the fan blade fragments that went forward of the fan case and into the inlet had a greater total mass and a different trajectory (a larger exit angle) and traveled beyond the containment shield. Also, the inlet damage caused by these fan blade fragments was significantly greater than the amount of damage that was defined at the time of inlet certification. Given the results of CFM's engine FBO containment certification tests and Boeing's subsequent structural analyses of the effects of an FBO event on the airframe, the post-FBO events that occurred during this accident could not have been predicted.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Pressure/environ sys malf/fail during enroute (cruise)
  2. Powerplant sys/comp malf/fail during enroute defining event

The NTSB's findings

  • cause Aircraft › Aircraft power plant › Engine (turbine/turboprop) › Compressor section › Fatigue/wear/corrosion
  • factor Aircraft › Aircraft structures › Nacelles/pylons structure › Plates/skins (nacelle/pylon) › Damaged/degraded
  • factor Aircraft › Aircraft structures › Fuselage › Fuselage main structure › Damaged/degraded

The aircraft

  • Airframe total time: 58,344 hours
  • Last inspection: continuous airworthiness programme, August 24, 2016
  • Maximum gross weight: 154,500 lb
  • Seats: 151
  • Landing gear: retractable
  • Engine 1: Cfmi CFM56-7B24G22 (turbofan); 0 hours total
  • Engine 2: Cfmi CFM56-7B24G22 (turbofan); 0 hours total
  • Operator: Southwest Airlines

The flight

  • Departed from: KMSY New Orleans LA at 2:02 pm
  • Destination: KMCO Orlando FL
  • Flight plan: IFR
  • A second pilot was aboard

Weather at the time

  • Light: daylight
  • Wind: from 060° at 6 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 81°F (27°C), dew point 75°F (24°C)
  • Altimeter: 30.00 inHg
  • Observation at 1:53 pm from KPQL

Injuries

FatalSeriousMinorNone
Cabi3
Flight crew2
Passengers99

Documents from the investigation the NTSB's docket: the evidence folder behind the report

14 documents, released by the NTSB on November 14, 2018. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

#DocumentWhat it is
1 Materials Laboratory Factual Report 16-107 PDF, 9 pages View Download
2 Flight Data Recorder - Specialist’s Factual Report PDF, 14 pages View Download
3 Flight Data Recorder - Attachment 1 (Tabular Data for Event Flight) zip file Download
4 Flight Data Recorder - Attachment 2 (Tabular Data for Previous Flight) zip file Download
5 Flight Data Recorder - Attachment 3 (Tabular Data for Figure 9 Including Gmt Parameters) zip file Download
6 Materials Laboratory Factual Report 17-043 PDF, 91 pages View Download
7 Airworthiness Group Chairman's Factual Report PDF, 148 pages View Download
8 Airworthiness Group Chairman's Factual Report Attachment 1 PDF, 3 pages View Download
9 Airworthiness Group Chairman's Factual Report Attachment 2 PDF, 7 pages View Download
10 Airworthiness Group Chairman's Factual Report Attachment 3 PDF, 33 pages View Download
11 Airworthiness Group Chairman's Factual Report Attachment 4 PDF, 26 pages View Download
12 Airworthiness Group Chairman's Factual Report Attachment 5 PDF, 44 pages View Download
13 Airworthiness Group Chairman's Factual Report Attachment 6 PDF, 38 pages View Download
14 Cockpit Voice Recorder Factual PDF, 4 pages View Download

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.