DEN08FA036 · Cessna 182Q
Cessna 182Q · Accident: in flight collision with object while maneuvering
From McKellar-Sipes Regional Airport (MKL) to East Texas Regional Airport (GGG)
Event
- NTSB case
- DEN08FA036
- 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 182Q
- Aircraft type
- Cessna 182
- 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
- N5134N
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From McKellar-Sipes Regional Airport (MKL), Jackson, TNTo East Texas Regional Airport (GGG), Longview, 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 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
- Maneuvering
- First occurrenceThe 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
- In flight collision with object
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Aircraft control, not maintained
- Pilot in command › Impairment(alcohol)
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The commercial pilot was supposed to be performing a flight to patrol a pipeline. However, he was flying in an erratic manner away from the pipeline he was suppose to be patrolling. In telephone communications with the pipeline company, he seemed "weird and disorientated." The airplane collided with trees and was destroyed by impact and post-impact fire. Examinations of the airframe and engine revealed no evidence of mechanical malfunctions or failures. Post-accident toxicological tests on specimens from the pilot found a blood ethanol level of 373 mg/dL (0.373 percent), and a urine ethanol level of 556 mg/dL, indicating that the pilot's blood level had been higher than 0.556 percent at some time within the previous 6 to 8 hours. Toxicology tests also detected a very high level of citalopram, a prescription antidepressant, and its metabolites in the pilot's blood, consistent with either ingestion of larger than typical amounts or accumulation of the substance as a result of liver impairment. On his most recent FAA application for a medical certificate less than one month prior to the accident, the pilot reported one Driving Under the Influence (DUI) conviction, which occurred less than 1 year prior to the accident; the FAA medical records contained no details of that DUI, but a review of publicly available court documents for the conviction noted that the pilot's blood alcohol concentration was 0.31 percent during that arrest. The pilot denied any history of alcohol dependence, abuse, or of mental disorders on his most recent application for medical certificate, though his employer was aware of his attendance at a rehabilitation program due to alcohol problems in 2006. The FAA specifically disqualifies pilot applicants with a history or clinical diagnosis of substance dependence, which is defined in 14 CFR 67.107, 67.207, and 67.307 as "evidenced by (A) increased tolerance, (B) manifestation of withdrawal symptoms, (C) impaired control of use, or (D) continued use despite damage to physical health or impairment of social, personal, or occupational functioning." Had the FAA obtained details regarding the pilot's DUI conviction and/or contacted the pilot's employer, the FAA would have been aware that this pilot met the FAA's definition for substance dependence, and he likely would have not been issued a medical certificate without having undergone thorough evaluation and additional treatment.
Probable cause
The pilot's failure to maintain aircraft control due to the effects of impairment from alcohol consumption resulting in the collision with the trees.. A contributing factor was the Federal Aviation Administration's failure to identify existing evidence of substance (alcohol) dependence in this commercial pilot due to an inadequate and incomplete process of screening medical applications.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN08FA036
- Event ID
- 20071203X01889
- Case number
- DEN08FA036
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 7fb3cb49d65d3cc8e5e379b6dceb8347aad5e3111c505bafd5eb01272f82f1ec; retrieved 2026-09-20T16:05:19.048Z.