FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA00IA191 · Dassault F2TH FALCON F2TH FALCO

27 Jun 2000 · Fort Lauderdale, FL, United States

Dassault F2TH FALCON F2TH FALCO · Incident: total loss of engine power (mechanical failure) during initial climb

From Fort Lauderdale Hollywood International Airport (FLL) to Monterrey International Airport (MMMY)

Report a problem

Event

NTSB case
MIA00IA191
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
General aviation
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

Dassault F2TH FALCON F2TH FALCO

Aircraft type
Dassault F2
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
XATDU
Operator
Unknown
Onboard fatalities
Unknown
Route
From Fort Lauderdale Hollywood International Airport (FLL)To Monterrey International Airport (MMMY), Monterrey
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 91: General Aviation
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
Total loss of engine power (mechanical 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

  • Manufacturer › Acft/equip, inadequate design
  • Miscellaneous, bolt/nut/fastener/clamp/spring › Loose
  • Turbine assembly, seal › Shifted

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

NTSB narrative

The captain stated that the copilot was flying the aircraft, and after rotation, as they were climbing through about 150 to 200 feet, there was the sound of a loud bang, and they felt extreme vibrations. The captain stated that the No. 2 engine gages went to zero, and there was no indication of fire. He further stated that the copilot continued flying the aircraft, and stayed in the pattern, returning for an otherwise uneventful landing. Postincident examination of the airplane revealed that a 2 to 3-foot section of the right engine nacelle, from approximately the 9:00 to the 6:00 o'clock positions, had torn outward, in line with the high-pressure turbine (HPT) area of the engine. Macroscopic examinations, as well as microscopic examinations of the No. 2 engine and recovered portions were conducted, and the examinations revealed a 360-degree circumferential groove on the aft face of the disk, just outboard of the aft 4-tooth knife-edge steel flange. The groove in the disk was consistent with the disk having been in contact with the 1st-stage low-pressure turbine support/nozzle assembly inner casting forward static seal. In addition, rivet holes on the forward static seal, and on the forward flange revealed the presence of fretting marks, which were inconsistent with those of a tightly mated assembly. Instead, the fretting was indicative of an assembly that allowed relative motion between the surfaces. Furthermore, an examination using a scanning electron microscope on the available rivet heads and rivet shanks revealed that one of the rivet shanks showed indications of fatigue, and that the fatigue originated from at least two areas on the outer diameter surface of the shank, and was indicative of high cycle fatigue. There were also heavy fretting underneath the heads of the rivets on the surface that mated with the seal, and the fretting was similar to that found on the front face of the seal, The fretting was consistent with there being insufficient clamping preload on the rivets.

Probable cause

the fatigue failure of the rivets used to secure the inner casting forward static seal to the 1st-stage low-pressure turbine support/nozzle assembly. The failure of the rivets allowed the forward static seal to machine a groove into the 2nd-stage high-pressure turbine disk to a depth that the disk could not withstand the operating loads, eventually leading to a disk burst and a high pressure turbine failure.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA00IA191
Event ID
20001212X21289
Case number
MIA00IA191
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2000-06-28.
  • API snapshot SHA-256: f6969a17001fcfe2b1d47a5816f4585146c9f41a396ab32e34186f7636f0253b; retrieved 2026-09-22T12:45:59.270Z.