Cessna 310R N310CR
13 December 2009 · Alva, Oklahoma, United States · Fatal
Summary
On 13 December 2009 at about 05:55 local time, a Cessna 310R registered N310CR was involved in an accident near Alva, Oklahoma, United States. One person was on board and one died. The aircraft was substantially damaged. The NTSB has published a probable cause for this accident; it is quoted in full below.
The record
- Date
- at 05:55
- Classification
- Accident
- Location
- Alva, Oklahoma, United States
- Nearest airport
- Alva Regional Airport (KAVK)
- Coordinates
- 36.7558, -98.6706
- Aircraft
- Cessna 310R
- Registration
- N310CR
- Category
- Airplane
- Engines
- 2
- Operator
- Not recorded
- Operating rule
- Part 91: General Aviation
- Purpose of flight
- Personal
- Phase of flight
- Not recorded
- Route
- Oklahoma City → Alva
- Aircraft damage
- Substantial
- Weather
- IMC
- Light
- Night
- NTSB number
- CEN10FA071
People
1 person died.
| On board | Died | Serious | Minor | Uninjured |
|---|---|---|---|---|
| 1 | 1 | 0 | 0 | 0 |
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.
Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.
Read the full 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.
Quoted verbatim from the NTSB record.
Other Cessna 310 accidents
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 12 Dec 2009 | Cessna 310 | Pasco, Washington, United States | - | No injuries | - |
| 10 Jul 2009 | Cessna 310 | Fort Worth, Texas, United States | - | No injuries | - |
| 30 Oct 2009 | Cessna 310J | Lawrenceville, Georgia, United States | - | Fatal | 1 |
| 18 Mar 2009 | Cessna 310K | Ocala, Florida, United States | Owens Elmer Eugene Trustee | No injuries | - |
| 24 Jun 2010 | Cessna 310C | Ashdown, Arkansas, United States | Stoneman Excavating Co Inc | Minor injuries | - |
| 21 Oct 2008 | Cessna 310 | Ciudad Victoria, Mexico | - | Fatal | 5 |
All 1,745 records for this type
Other accidents in this area
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 6 Mar 2009 | Champion 7FC | Thomas, Oklahoma, United States | - | Minor injuries | - |
| 26 Feb 2009 | Neland Richard L DAYTONA SU | Guymon, Oklahoma, United States | Delta Charley Lease LLC | No injuries | - |
| 11 Jun 2009 | Hiller UH-12E | Stringtown, Oklahoma, United States | Texas Air Cargo, Inc. | No injuries | - |
| 14 Oct 2009 | Robinson R22 BETA | Tahlequah, Oklahoma, United States | - | Fatal | 2 |
| 9 Mar 2009 | Roach Neil GLASAIR SU | Tulsa, Oklahoma, United States | White Buffalo Environmental, Inc | No injuries | - |
| 25 Jul 2009 | Beechcraft V35 | Oklahoma City, Oklahoma, United States | - | Fatal | 1 |