CEN15FA278 · Cessna 172
Bag Flying Club Cessna 172 · Accident: loss of control in flight during takeoff
From Shreveport Downtown Airport (DTN) to Shreveport Downtown Airport (DTN)
Event
- NTSB case
- CEN15FA278
- 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
Cessna 172
- Aircraft type
- Cessna 172
- 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
- N5743A
- Operator
- Bag Flying Club
- Onboard fatalities
- Unknown
- Route
- From Shreveport Downtown Airport (DTN), Shreveport, LATo Shreveport Downtown Airport (DTN), Shreveport, LA
- Aircraft age
- About 59 years (built 1956)
- 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
- Takeoff
- 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
The pilot was performing touch-and-go landings at a controlled airport. During the accident takeoff, the airplane was observed in a nose-high attitude. The pilot made an abbreviated radio call indicating that he was returning to the airport. The airplane rolled to the left, nosed over, impacted the ground with its left wing, cartwheeled on its nose, and came to rest upright. An on-scene examination revealed no preimpact flight control anomalies, and the pilot's seat was found pinned in a seat rail's hole, indicating that the loss of control was not the result of inadvertent slippage of the seat. The engine was test run and no anomalies were noted.
The airplane was equipped with lap belts, and it did not have (nor was it required to have) shoulder harnesses. The pilot sustained injuries that were consistent with unrestrained upper body impact with the control yoke. No medical issues were identified with the pilot that would have contributed to the accident.
Probable cause
The pilot's loss of airplane control during initial climb after takeoff for reasons that could not be determined because an examination of the airframe and engine did not reveal any preimpact anomalies.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN15FA278
- Event ID
- 20150619X00546
- Case number
- CEN15FA278
- 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: ac32c8b51f99d43eb9a542f7bef0cff59732750d2ede62ba5ee98f6dc420b7c0; retrieved 2026-09-14T19:30:21.933Z.