ERA09CA122 · Dassault-Breguet FALCON 50
Ingles Markets Dassault-Breguet FALCON 50 · Accident: ground collision while standing
From Asheville Regional Airport (AVL) to Asheville Regional Airport (AVL)
Event
- NTSB case
- ERA09CA122
- 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
- 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-Breguet FALCON 50
- Aircraft type
- Dassault Breguet FALCON 50
- 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
- N200SG
- Operator
- Ingles Markets
- Onboard fatalities
- Unknown
- Route
- From Asheville Regional Airport (AVL), Asheville, NCTo Asheville Regional Airport (AVL), Asheville, NC
- 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
- Standing · engine(s) not operating
- Defining eventThe 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
- Ground collision
- 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
- Aircraft › Aircraft handling/service
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The First Officer (FO) said that he spoke to the Pilot-In-Command (PIC) of his intention to get up, open the cabin entry door, and secure the airplane with chocks after landing rollout. The FO got up out of the right cockpit seat and started towards the main entry door in preparation to open the door. He stated that the PIC "also started to leave the cockpit when [the FO] realized that the airplane was rolling and alerted [the PIC] that the airplane was moving." The PIC "got back in the left seat in an attempt to stop the aircraft." The FO stated that the hydraulic pressure was in a "diminished state" and the PIC could not stop the airplane in time to avoid contact with the fence. When asked if he knew why the airplane started to move, he stated that he "believes that his son, [the PIC had] assumed that [he] had opened the entry door and completed chocking the aircraft wheels." According to the FO, the PIC "mistakenly released the parking brake which had been set during the normal shutdown checklist procedure."
Probable cause
The pilot's failure to ensure that the airplane's wheels were properly secured before releasing the parking brake.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA09CA122
- Event ID
- 20090102X71942
- Case number
- ERA09CA122
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 4f97483757a0a33a5ad275bd342a3f59aa9d50e9782e5979418bd307c71b3ca9; retrieved 2026-09-15T10:39:42.354Z.