CEN11LA138 · Cessna 172H
Cessna 172H · Accident: loss of control in flight en route
From Waynesville-St. Robert Regional Airport-Forney Field (TBN) to Bartlesville Municipal Airport (BVO)
Event
- NTSB case
- CEN11LA138
- 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 172H
- 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
- N1416F
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Waynesville-St. Robert Regional Airport-Forney Field (TBN), Ft Leonard Wood, MOTo Bartlesville Municipal Airport (BVO), Bartlesville, OK
- 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 · cruise
- 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 accident occurred during the fourth leg of a visual flight rules cross-country flight. The pilot departed on the first leg of the trip shortly after sunrise, about 11 hours prior to the accident. The pilot made 3 intermediate stops during the day, where he purchased fuel. The accident flight was approximately 1 hour in duration and was conducted in night visual meteorological conditions. Radar track data depicted the airplane established on a west-southwest course and at a constant altitude. About 15 seconds prior to the accident, the airplane entered a descending left turn, and spiraled down, ultimately impacting an open field. A postaccident examination of the airplane did not reveal any anomalies consistent with a preimpact failure or malfunction. Postmortem toxicology testing was consistent with the prior use of a prescription anti-anxiety medication and marijuana. Due to limited samples, a determination could not be made as to when the substances were last used. Accordingly, no determination was made as to whether the pilot was impaired at the time of the accident. While the departure from controlled flight suggested spatial disorientation, and the extended duration of the trip likely contributed to pilot fatigue, the exact nature of the loss of control could not be determined.
Probable cause
The pilot's loss of control for undetermined reasons. Contributing to the accident was the pilot's fatigue.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN11LA138
- Event ID
- 20110103X35259
- Case number
- CEN11LA138
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2011-01-04.
- API snapshot SHA-256: f47ce48152a00cc32ae95eb6335d858215287322f0d119fdb9bb5a343e38fd2a; retrieved 2026-09-13T21:12:12.013Z.