FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Fast Air Carrier Boeing 707-341 incident

2 Aug 1993 · Miami, FL, United States

Boeing 707-341 · Incident: airframe, component or system failure during initial climb

From Miami International Airport (MIA) to Jorge Chávez International Airport (SPIM)

Report a problem

Event

NTSB case
MIA93IA168
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
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
0
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 707-341

Aircraft type
Boeing 707
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
N107BV
Onboard fatalities
Unknown
Route
From Miami International Airport (MIA)To Jorge Chávez International Airport (SPIM), Lima
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 129: Foreign
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
Initial climb
First occurrenceThe 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
Airframe, component or system failure
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

  • Company maintenance personnel › Maintenance, inspection, not performed

Approximate · Estimated position: the centre of Miami, FL, the place the record names. Not the accident site.

NTSB narrative

FLIGHT EXPERIENCED LOSS OF THE NUMBER ONE ENGINE CORE COWLING SHORTLY AFTER LIFTOFF. METALLURGICAL EXAMINATION OF THE SEPARATED COWLING INDICATED THE INBOARD FORWARD COWLING HINGE SUPPORT STRUCTURE HAD FAILED DUE TO FATIGUE. THIS ALLOWED THE COWLING TO OPEN AND THEN SEPARATE FROM THE ENGINE. THE HINGE REMAINED IN PLACE ON THE AIRCRAFT AFTER THE COWLING SEPARATED. THE MANUFACTURER OF THE COWLING, WHICH IS PART OF AN ENGINE HUSH KIT, REQUIRES THE HINGE SUPPORT STRUCTURE BE INSPECTED FOR CRACKS EACH 300 FLIGHT HOURS.

Probable cause

THE IMPROPER INSPECTION OF THE ENGINE CORE COWLING, WHICH RESULTED IN FATIGUE CRACKS IN THE FORWARD INBOARD HINGE SUPPORT STRUCTURE TO GO UNDETECTED. THIS RESULTED IN THE HINGE SEPARATING AND THE COWLING SEPARATING IN FLIGHT.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA93IA168
Event ID
20001211X13195
Case number
MIA93IA168
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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. 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: 322447e87a42b64d99994fd5ed8f2248e200aac5f26272b8d4ebb78f2739080e; retrieved 2026-09-18T18:32:09.833Z.