ATL06IA108 · Dassault Aviation Mystere Falcon 900
ERG Aviation II Dassault Aviation Mystere Falcon 900 · Incident: airframe, component or system failure during landing
From Concord-Padgett Regional Airport (JQF) to Greenville Downtown Airport (GMU)
Event
- NTSB case
- ATL06IA108
- 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
- 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
- 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 Aviation Mystere Falcon 900
- Aircraft type
- Dassault MYSTERE 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
- N699BG
- Operator
- ERG Aviation II
- Onboard fatalities
- Unknown
- Route
- From Concord-Padgett Regional Airport (JQF), Concord, NCTo Greenville Downtown Airport (GMU), Greenville, SC
- 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
- None
Cause areas
- Landing gear, anti-skid brake system › Malfunction
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot stated that the en route phase of the flight was uneventful, until he was on the final approach to land, when the anti-skid system test required a second test to receive the correct indication. Upon touch down, the co-pilot deployed the spoilers and thrust reverser. When the wheel brakes were applied, the airplane began to drift to the left side of the centerline. The pilot indicated that the wheel brakes did not appear to be effective, however he was able to maintain directional control of the airplane. The airplane slowed, but did not stop until it overran the runway, and encountered the engineered materials arresting system (EMAS). A postincident functional test of the landing gear system was conducted in the ground and flight configuration. During the in-flight functional test, a malfunction in the right main landing gear brakes anti-skid system occurred. The anti-skid system was removed, and a functional test of the system was performed. During the test, the components of the anti-skid system were examined, and the SPAD (Advanced Anti-Skid System) controller was found to be the origination of the brake failure. The controller was replaced, and another functional test was performed. The anti-skid system passed all functional tests, and the airplane was returned to service.
Probable cause
The malfunction of the anti-skid system SPAD controller during the landing roll, which resulted in failure of the anti-skid braking system, and a runway overrun.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL06IA108
- Event ID
- 20060802X01070
- Case number
- ATL06IA108
- 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, coordinates, damage. 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: 8efd65ede0eda8351b9f8f5e74616336a52640f224de7c9a1b4a97fdfc309f66; retrieved 2026-09-22T04:40:02.836Z.