CEN11FA319 · Thomas EUROPA
Thomas EUROPA · Accident: loss of control in flight en route
From Shreveport, LA to Shreveport, LA
Event
- NTSB case
- CEN11FA319
- 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
- 1 · 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
Thomas EUROPA
- Aircraft type
- Thomas EUROPA
- 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
- N914KM
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Shreveport, LATo Shreveport, LA
- 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
- En route
- 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
- Loss of control in flight
- 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
- Not determined › Not determined
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Radar data provided by the Federal Aviation Administration depicted the accident airplane for about five minutes. According to a summary of the flight, the pilot requested taxi instructions at 1134, a takeoff clearance at 1137, and the controller issued a frequency change at 1142 to which there was no response from the pilot.
The airplane initially climbed from 700 feet mean sea level (msl), to 1,200 feet msl on a north-northeasterly heading shortly after departing the local airport. Three minutes later, the airplane began to descend. The last two minutes of radar data depicted the airplane in a gradual descent from 1,200 feet mean sea level (msl) to 200 feet msl. Ground scars and damage to the airplane were consistent with a low airspeed and nose down attitude at the time of impact. The airplane sustained substantial damage to both wings, the fuselage, and empennage. A postaccident examination of the airframe, airplane systems, and engine revealed no mechanical anomalies that would have precluded normal operation. There were no witnesses to the accident. The reason for the loss of control was not determined.
Probable cause
The loss of aircraft control and subsequent impact with terrain for undetermined reasons.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN11FA319
- Event ID
- 20110504X40153
- Case number
- CEN11FA319
- 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: e16ff8cbb99985ece792574ef6809995a75dc35a615f5c5bc18a450a2b16fa70; retrieved 2026-09-13T21:23:10.129Z.