CEN10FA071 · Cessna 310R
Cessna 310R · Accident: controlled flight into terrain/object (CFIT) on approach
From Sundance Airpark (KHSD) to Alva Regional Airport (KAVK)
Event
- NTSB case
- CEN10FA071
- 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
- Instrument Meteorological Cond
Cessna 310R
- Aircraft type
- Cessna 310
- 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
- N310CR
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Sundance Airpark (KHSD), Oklahoma City, OKTo Alva Regional Airport (KAVK), Alva, 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
- Approach · IFR final approach
- 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
- Controlled flight into terrain/object (CFIT)
- 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 › Action/decision
- Personnel issues › Physical
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Prior to departing on a night, instrument cross country flight, the pilot contacted Flight Service for a weather briefing. The pilot told the briefer that he was familiar with his destination airfield, and that the automated weather reporting station was out of service due to construction. The closest weather reporting station was approximately 45 miles from his airfield. It was noted that fog was reported in the general area, but due to the out of service weather station it was unknown if the destination airport had fog present. During the flight, the pilot reported to Air Traffic Control that fog was located around his destination airport and he was unsure if he could land or not. On the second approach to the airport, the airplane impacted open terrain just south of the airfield. First responders reported at the time of the crash, visibility was very poor due to fog. A postaccident examination of the airframe and engines revealed no mechanical malfunctions or failures that would have precluded normal operation. Additionally, examination of ground scars and propeller blades indicated the engines were producing power during the collision with the ground. Both global positioning system (GPS) and radar plots depicted the airplane making an approach to the airport, followed by a missed approach. The plots also revealed that during the accident approach, the airplane descended below approach minimums for the airport.
Post-mortem toxicology testing indicated positive results for ten different medications, several of them potentially impairing: Gabapentin (also known by the trade name Neurontin), a prescription antiseizure medication that is also used to treat chronic pain from a variety of neurological conditions; Hydrocodone, a prescription narcotic painkiller used for the control of moderate pain; and Dihydrocodeine and hydromorphone, which are metabolites of hydrocodone.
Personal medical records obtained on the pilot noted a long history of severe migraine headaches, occurring nearly daily at times, treated with a wide variety of potentially impairing medications with only limited effect. He had been treated for headaches by at least three different physicians, with a medical visit for injected medication less than a week prior to the accident. Additionally, the pilot had denied the use of medication and frequent or severe headaches on application to the FAA for medical certification.
Given the pilot’s reported familiarity with the aircraft and the airport, and his extensive reported experience, it seems likely that impairment due to migraine headache, medication use, or both played a role in the accident and the pilot's decision to descend below a safe altitude on the approach to the runway.
Probable cause
The pilot's impairment due to medication use, a migraine headache, or both, and his decision to continue the approach below minimums without the proper visual references, resulting in the subsequent collision with terrain. Contributing to the accident was the pilot’s falsification of medical information provided to the FAA.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN10FA071
- Event ID
- 20091213X85112
- Case number
- CEN10FA071
- 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 2009-12-13.
- API snapshot SHA-256: dbf88f6cebeb8a8d137c8be046ba294501f6edf8a251bea877560a6b963b3376; retrieved 2026-09-13T20:35:38.263Z.