American Eagle Bombardier CL600 2C10 700 accident
Bombardier CL600 2C10 700 · Accident: ground collision while standing
From William P. Hobby Airport (HOU) to Dallas Fort Worth International Airport (DFW)
Event
- NTSB case
- DCA10CA018
- 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
- Airline
- 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
Bombardier CL600 2C10 700
- Aircraft type
- Bombardier CL600
- 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
- N515AE
- Operator
- American Eagle
- Onboard fatalities
- Unknown
- Route
- From William P. Hobby Airport (HOU), Houston, TXTo Dallas Fort Worth International Airport (DFW), dallas, TX
- 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 121: Air Carrier
- 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) 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
- Personnel issues › Miscellaneous
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The fuel truck driver indicated that he had been waiting 10-15 minutes for the flight to arrive and that the truck was in neutral with no emergency brake set. He stated that he had his foot on the brake but that he closed his eyes briefly and fell asleep and was unaware of what happened until the fuel truck collided with a parked airplane that had just arrived at the gate. One of the two flight attendants received a minor injury; there were no injuries to the other crew members or the passengers. The airplane received substantial damage to the aft portion of the fuselage where the fuel truck impacted.
Probable cause
The fueler's falling asleep in the fueling truck with the truck in neutral and without the parking brake set, which allowed the truck to roll until it impacted the airplane.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DCA10CA018
- Event ID
- 20091223X50505
- Case number
- DCA10CA018
- 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, coordinates. 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: d184502fec07667368fbfd808b45399f990bfc500f764ea6accbd840c7ce6c31; retrieved 2026-09-15T13:35:19.425Z.