FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

American Airlines Flight 1640

26 Oct 2010 · Miami, FL, United States

Boeing 757-223 · Accident: aircraft structural failure en route

Report a problem

Event

NTSB case
DCA11FA004
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
Accident
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
API-reported fatalities
0 · all aircraft and ground
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
Not recorded

Boeing 757-223

Aircraft type
Boeing 757
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
N626AA
Onboard fatalities
Unknown
Route
From not recordedTo not recorded
Aircraft age
Not recorded
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
En route
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
Aircraft structural failure
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft structures
  • Organizational issues › Development

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

Flight data recorder data revealed that, after takeoff from Miami International Airport (MIA), Miami, Florida, the airplane climbed for about 16 minutes and was passing through an altitude of approximately 32,000 feet when the rapid decompression occurred. The flight crew declared an emergency (the first officer was the pilot flying) and returned to MIA. Post accident examination of the airplane revealed fatigue cracking of the upper fuselage skin above the forward left passenger (L1) door. The fatigue cracking penetrated the fuselage skin, leading to a rupture and an approximate 18-inch-by-7-inch hole that depressurized the airplane.

NTSB examinations of a section of the fuselage crown skin (from body station 374 to body station 439) where the rupture occurred revealed fatigue cracking along the lower longitudinal step of the chemically milled pocket just above the stringer S-4L (left) lap joint. The fatigue cracking initiated on the interior surface of the skin at multiple locations and propagated through the skin thickness. The skin thickness at the base of the chemically milled step measured 0.035 to 0.037 inch—which is less than the 0.039-inch minimum thickness specified by Boeing. Calculations from an NTSB study of the fatigue striation density and propagation in the fatigue region indicate that it would take an average of 3,709 total cycles for a crack to grow through skin with 0.035-inch thickness and an average interval of 917 cycles for a crack to grow from a minimally detectable size and penetrate a 0.035-inch skin thickness.

The area of cracking and rupture on the accident airplane was not subject to any specific inspections, service bulletins (SB), or airworthiness directives (AD) at the time of the accident. Following the accident, on November 22, 2010, Boeing issued SB 757-53-0097, which called for repetitive external inspections (every 30, 200 cycles, or 300 hours depending on the inspection method) to detect cracks in the fuselage skin along the chemically milled step at stringers S-4L (left) and S 4R (right) between body station 297 and body station 439. On January 10, 2011, the Federal Aviation Administration issued AD 2011-01-15 (effective January 25, 2011) mandating the inspections recommended in SB 757-53-0097.

During its investigation, the NTSB learned of a United Airlines 757 and a second American Airlines 757 that exhibited cracking in the fuselage skin similar to the accident airplane; both had nonconforming thickness at the base of the chemically milled step at the stringer location specified in the SB. Records of manufacture for the skin panels on the accident airplane and the other airplanes with fuselage skin cracking were not retained, and were not required to be retained; therefore, a cause for the manufacturing nonconformance could not be identified.

Probable cause

Fatigue failure of the fuselage crown skin due to incorrect manufacturing of the crown skin panel that resulted in a skin thickness less than the manufacturer-specified thickness.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DCA11FA004
Event ID
20101027X04916
Case number
DCA11FA004
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2010-10-27.
  • API snapshot SHA-256: 8b788ed48ae314563a36f0ae8ef0a22f98d61008485c2ca49da763ea923815db; retrieved 2026-09-15T15:31:15.613Z.