WPR21LA030 · Cessna 310 R
Cessna 310 R · Accident: loss of engine power (partial) en route
From North Las Vegas Airport (VGT) to Gillespie Field (SEE)
Event
- NTSB case
- WPR21LA030
- 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
- 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 310 R
- 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
- N101G
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From North Las Vegas Airport (VGT), Las Vegas, NVTo Gillespie Field (SEE), San Diego, CA
- Aircraft age
- About 45 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 · climb to cruise
- 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
- Loss of engine power (partial)
- 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
- Aircraft › Aircraft oper/perf/capability
- Aircraft › Fluids/miscellaneous hardware
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot departed in the twin-engine airplane for the cross-country flight. About 1 mile south of the airport, at an altitude of 2,800 ft, the pilot requested a destination change from air traffic control to a nearby airport. The pilot further requested a direct heading to the airport and stated he needed to shut down one engine. As the airplane flew toward the new destination airport, a witness observed the airplane fly over powerlines and then pitch down. The airplane maintained its altitude briefly then nosed down again before it rolled sharply to the left. The airplane impacted the ground about 8 nautical miles northwest of the airport and a postcrash fire ensued. The witness stated that the left engine appeared to be inoperable as the propeller was not spinning. Recorded footage from a witness video confirmed the lack of power from the left engine and power being produced on the right engine. Recorded automatic dependent surveillance–broadcast data indicate the airplane’s airspeed was approximately 86 knots at the time the turn to the new destination airport was initiated. The airspeed briefly increased to 97 knots over the next minute then gradually decreased to a final airspeed of 78 knots when the data was lost. The airplane’s minimum controllable airspeed (VMC) was 80 knots; therefore, as the airspeed decreased below VMC, the pilot was likely unable to maintain control of the airplane while maneuvering with one engine inoperative. A postaccident examination of the left engine revealed two holes in the crankcase above cylinder Nos. 3 and 4. The No. 2 connecting rod was separated from the crankshaft and no indication of lubrication was noted in the crankcase. The lack of lubrication, combined with signatures of thermal damage on many of the crankshaft journals and bearings, indicated the likelihood of an oil pressure problem, which resulted in a loss of engine power. About 10 months before the accident, the engine was disassembled and inspected for a low oil pressure problem. During the maintenance, the main bearings and rod bearings were replaced, as well as the alternator, oil cooler, and starter adapter. The airplane flew about 40 hours after the maintenance was completed; an annual inspection was performed about 6 months before the accident. During the inspection, cylinder compression was noted between 61-65 pounds per square inch (psi) on each cylinder. FAA guidance states cylinder compression less than 60 psi requires removal and inspection of the cylinder. While the cylinder compressions were just above the limit requiring removal, their low compression readings should have indicated a problem to maintenance personnel that needed to be addressed. The low compression readings only 40 hours after engine disassembly and the failure to identify or correct the reason for the low compression indicates inadequate maintenance. Toxicology testing detected ethanol in the pilot’s liver and muscle tissue but not in his brain tissue. The ethanol concentration in his liver was over ten times higher than the concentration detected in his muscle tissue. Extensive trauma increases the risk of postmortem ethanol production. Given the differing ethanol tissue concentrations and the trauma received by the body from the crash, it is likely that the identified ethanol was from sources other than ingestion. Thus, the identified ethanol did not contribute to the accident. Additionally, although toxicology testing detected the sedating antihistamine diphenhydramine in the pilot’s urine and liver tissue, the amounts were too low to quantify. Based on the circumstances of this accident, including the pilot’s appropriate decision to land after an engine failure, it is unlikely that effects from the pilot’s use of diphenhydramine contributed to this accident.
Probable cause
The pilot’s failure to maintain the airplane’s minimum controllable airspeed while maneuvering with one engine inoperative. Also causal was the loss of power in the left engine due to oil starvation. Contributing to the accident were inadequate maintenance that failed to correct an ongoing problem with the engine in the months preceding the accident.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR21LA030
- Event ID
- 20201029102215
- Case number
- WPR21LA030
- 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, coordinates, 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: aaf55def5125d5577a1a80217f614ad2ed2627a5d14208e95872844fa39ad219; retrieved 2026-09-15T07:21:47.635Z.