Miller Aviation Cessna 310R accident
Cessna 310R · Accident: controlled flight into terrain/object (CFIT) on approach
From Dayton-Wright Brothers Airport (MGY) to Pike County Airport Hatcher Field (PBX)
Event
- NTSB case
- ERA11FA218
- 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
- 2 · 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
- Charter & commuter
- 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
- N1914G
- Operator
- Miller Aviation
- Onboard fatalities
- Unknown
- Route
- From Dayton-Wright Brothers Airport (MGY), Dayton, OHTo Pike County Airport Hatcher Field (PBX), Pikeville, KY
- 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 135: Air Taxi & Commuter
- 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)
- 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
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot requested and was cleared for a non-precision instrument approach to the mountaintop airport that was obscured by clouds and fog; a precision approach to the same airport was also available. Review of the radar data revealed that the last two data points were aligned with the runway but below the published minimum descent altitude. Witnesses at a worksite 200 to 300 feet below the airport elevation heard the airplane approach and then saw it appear from beneath the clouds directly on top of, and parallel to, a ridgeline approximately in line with the final approach course. The witnesses heard and saw the airplane hit small branches in the treetops of some trees and then strike a large tree before disappearing from view. They each said that the sound of the airplane’s engines was smooth and continuous until contact with the trees. They stated that the fog was heavy and that the clouds were on top of the trees. The first identifiable tree strikes were 1,100 feet right of the runway centerline and about 100 feet below the airport elevation. The local director of public safety who responded to the airport immediately after the accident estimated that visibility was less than 30 feet due to fog. A postaccident examination of the wreckage revealed no preimpact mechanical anomalies. Toxicological testing of the pilot revealed use of nighttime cold medication at doses above therapeutic levels; such levels may have posed a hazard to flight safety.
Probable cause
The pilot's flight below the published minimum descent altitude in instrument meteorological conditions, which resulted in a collision with trees and the ground. Contributing to the accident was the pilot's use of nighttime cold medication at doses above therapeutic levels that may have resulted in impairment and posed a hazard to flight safety.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA11FA218
- Event ID
- 20110330X44100
- Case number
- ERA11FA218
- 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: 4a5a178d0ab0a420b980857ef45e10b884b88b523be7b6c75e35d49eef71c907; retrieved 2026-09-13T21:18:09.167Z.