CEN24FA089 · Cessna 310R
Cessna 310R · Accident: medical event en route
From Dimmit County Airport (CZT) to Bridgeport Municipal Airport (XBP)
Event
- NTSB case
- CEN24FA089
- 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
- 3 · all aircraft and ground
- Ground fatalities
- 0
- 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
- N252DL
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Dimmit County Airport (CZT), Carrizo Springs, TXTo Bridgeport Municipal Airport (XBP), Bridgeport, TX
- Aircraft age
- About 49 years (built 1975)
- 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 · descent
- 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
- Medical event
- 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
- Personnel issues › Physical
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Before departing on an instrument-flight-rules (IFR) cross-country flight, the pilot obtained a standard weather briefing of the forecast and observed weather conditions along the flight route, which included AIRMETs for moderate icing between the departure and destination airports during the time of the filed IFR flight plan. The airplane was likely in instrument meteorological conditions during the descent between 6,000 ft and 3,000 ft msl in moderate or greater icing with supercooled large droplets. Below 3,000 ft, the accident flight was likely in visual meteorological conditions and below freezing temperatures. During the descent, ATC attempted to communicate with the pilot for about 7 minutes with no response from the pilot. The descent profile was controlled on a relatively straight heading and the witness marks on the ground, damage to the airplane, and distribution of the wreckage were consistent with controlled flight into terrain. The airplane impacted a field in a relatively level attitude. The airplane may have accumulated some ice while descending through the cloud layer. However, the ½ mile long wreckage path from initial impact with the ground to where the main wreckage came to rest is not consistent with loss of control due to ice accumulation. The witness seeing the airplane flying parallel to the ground in a wings level attitude also suggests that the airplane did not depart controlled flight. Due to the fragmentation and thermal damage to the airplane, functional tests of the system were not possible; however, there was no evidence to suggest a preimpact anomaly with the flight controls or engines which would have precluded normal operations. The pilot’s moderate coronary artery disease conveyed some increased risk of a sudden impairing or incapacitating cardiovascular event, such as chest pain, arrhythmia, or heart attack. The autopsy did not provide specific evidence that such an event occurred; however, such an event does not leave reliable autopsy evidence if the event occurs shortly before death. Ethanol levels measured by two laboratories were elevated to a relatively similar degree in vitreous fluid and urine, indicating a possibility that the pilot may have consumed alcohol and may have been impaired by ethanol effects at the time of the accident or while engaged in earlier activities related to the safety of flight. However, cautious interpretation of the alcohol results is prudent, given the extent of the pilot’s injuries, the fact that only two specimen types were tested for ethanol, and the detection of other volatiles in both of those specimen types. It is possible that some or all of the detected ethanol may have been from postmortem sources rather than alcohol consumption. Although toxicological results also indicated that the pilot had used the medication cetirizine, no determination could be made from the medical evidence indicating whether the pilot might have been experiencing some associated sedation at the time of the accident. Based on the available evidence, it is possible that the pilot became incapacitated during the descent. The reason for the incapacitation could not be determined.
Probable cause
Pilot incapacitation for undetermined reasons which resulted into controlled descent into terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN24FA089
- Event ID
- 20240114193646
- Case number
- CEN24FA089
- 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, cause areas. 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: 5440e41c8d982b3d101d4b9ebfdec65c12c73d53d1ee222f733626067cf756af; retrieved 2026-09-15T08:10:07.153Z.