FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA98LA118 · Dassault MYSTERE FALCON 900 MYSTERE FA

2 Jul 1998 · Hamilton, MT, United States

Tag Aviation USA Dassault MYSTERE FALCON 900 MYSTERE FA · Accident: on ground/water collision with object during landing

From San Francisco International Airport (SFO) to an unrecorded destination

Report a problem

Event

NTSB case
SEA98LA118
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 MYSTERE FALCON 900 MYSTERE FA

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
N900CS
Onboard fatalities
Unknown
Route
From San Francisco International Airport (SFO), San Francisco, CATo 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
On ground/water collision with object
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

  • Landing gear, anti-skid brake system › Contamination
  • Landing gear, anti-skid brake system › Failure, partial

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

NTSB narrative

The pilot reported that, after a normal approach and touchdown, he applied the brakes and thrust reversers. He stated that as the aircraft slowed to 60 to 70 knots, it veered to the right and exited the side of the runway. The pilot regained directional control after the aircraft exited the runway. Before the aircraft came to a stop, the right wing collided with the VASI lights for the opposite runway. Skid marks leading to the exit point on the runway, indicated that the right-side tire marks displayed heavier braking action than on the left side. Post-accident testing performed on the anti-skid generators revealed that the left-side inboard and outboard generators failed the manufacturer's specifications. The right-side inboard and outboard generators passed all manufacturers specifications. The left-side generators were disassembled. The inspection did not reveal any anomalies. A slight difference in the brush wear between the brush fittings was noted between the two generators. A short circuit between two adjacent collectors was found in the outboard generator rotor fitting. The manufacturer's representative reported that the short circuit was not due to a failure within a cell of the rotor, but was likely due to contamination present between the two collectors.

Probable cause

Partial failure of the anti-skid brake system due to contamination.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA98LA118
Event ID
20001211X10701
Case number
SEA98LA118
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: 45c96923de7f5b47a68d2acc491423fa501259ffcbecb186a6119a1383614b65; retrieved 2026-09-22T17:35:28.605Z.