CHI89MA047 · Dassault-Breguet FALCON 900
Dassault-Breguet FALCON 900 · Accident: airframe, component or system failure during landing
From Philadelphia International Airport (PHL) to an unrecorded destination
Event
- NTSB case
- CHI89MA047
- 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
- 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-Breguet FALCON 900
- Aircraft type
- Dassault Breguet FALCON 900
- 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
- N901B
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Philadelphia International Airport (PHL), Philadelphia, PATo 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 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
- Landing · landing roll
- 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
- Substantial
Cause areas
- Thrust reverser, actuator › Failure, total
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PLTS RPRTD THAT WHILE LNDG ON A SNOW & SLUSH CVRD RWY, THEY USED FULL REVERSE THRUST & MAX BRAKING WITH ANTI-SKID, BUT THE ACFT DID NOT DECELERATE. THEY SELECTED THE #2 BRAKE SYS WITHOUT ANTI-SKID. SUBSEQUENTLY, THE MAIN TIRES FAILED (BLEW-OUT) & THE ACFT SLID OFF THE LEFT SIDE OF THE RWY, COLLAPSING THE LEFT MAIN GEAR. INV REVEALED THAT BOTH THRUST REVERSER ACTUATOR LINKS ON THE #2 ENG HAD FAILED. WITH THESE FAILURES THE #2 ENG WOULD HAVE CONTD TO PROVIDE FWD THRUST,PROPELLING THE ACFT DWN THE RWY. (ON THIS MODEL OF ACFT, ONLY THE #2 ENG WAS EQUIPPED WITH REVERSE THRUST CAPABILITY.) METALLURGICAL EXAMS OF THE FWD ROD END FITTINGS OF BOTH REVERSE THRUST ACTUATOR LINKS (P/N 8140-06LK) REVEALED THE BEARING LOOPS HAD FAILED FROM OVERSTRESS. MANDATORY SERVICE BULLETIN (S/B) F900-78-1 WAS ISSUED ON 5/18/89 TO PROVIDE A SAFETY SYSTEM TO PREVENT ACTIVATION OF THE THRUST REVERSER ABOVE IDLE, WHILE THE AIRCRAFT IS ON THE GROUND. ALSO, MANDATORY S/B F900-78-2 WAS ISSUED ON 7/19/89 TO REINFORCE THE THRUST REVERSER ACTUATING MECHANISMS.
Probable cause
FAILURE OF THE THRUST REVERSER ACTUATOR LINKS DUE TO A MANUFACTURING/DESIGN PROBLEM. FACTORS RELATED TO THE ACCIDENT WERE: THE ADVERSE RUNWAY CONDITIONS AND THE CROSSWIND.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI89MA047
- Event ID
- 20001213X27559
- Case number
- CHI89MA047
- 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: 1bf09671c3fa795bfb129149511b49866e13f4a09f2f5dd5edd116406f4a9318; retrieved 2026-09-23T07:57:02.490Z.