Fatal NTSB investigations: Cessna 310R
60 cases on aircraft the registry lists as Cessna 310R. Aircraft are matched to the registry by N-number and event date, checked against the reported serial number, make and model, so older matches can be wrong.
Cases per year
| 1978 | 1 |
|---|---|
| 1979 | 6 |
| 1981 | 3 |
| 1982 | 3 |
| 1983 | 3 |
| 1984 | 2 |
| 1986 | 1 |
| 1987 | 1 |
| 1988 | 2 |
| 1990 | 1 |
| 1992 | 5 |
| 1993 | 1 |
| 1994 | 2 |
| 1995 | 1 |
| 1996 | 2 |
| 1997 | 1 |
| 1998 | 1 |
| 1999 | 1 |
| 2001 | 2 |
| 2004 | 2 |
| 2005 | 1 |
| 2007 | 3 |
| 2009 | 1 |
| 2010 | 1 |
| 2011 | 3 |
| 2013 | 2 |
| 2014 | 2 |
| 2015 | 1 |
| 2018 | 1 |
| 2020 | 1 |
| 2022 | 1 |
| 2024 | 1 |
| 2025 | 1 |
Where
Open the mapLatest cases
Query with SQL
duckdb -csv -c "SELECT c.\"ntsbNumber\", c.\"eventDate\", c.\"eventType\", c.\"eventCity\", c.\"eventStateOrRegion\", a.n_number, a.\"aircraftMake\", a.\"aircraftModel\", c.\"highestInjuryLevel\", c.\"totalFatal\", c.\"completionStatus\", c.report_url
FROM 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c LEFT JOIN 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a ON a.case_mkey = c.\"mKey\" AND a.position = 1
WHERE c.\"highestInjuryLevel\" = 'Fatal'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2074245'))
ORDER BY c.\"eventDate\" DESC, c.\"ntsbNumber\" DESC"Prints the whole list as CSV. It reads the release’s Parquet files over HTTPS, so there’s nothing to download first. Install DuckDB to run it.
SELECT c."ntsbNumber", c."eventDate", c."eventType", c."eventCity", c."eventStateOrRegion", a.n_number, a."aircraftMake", a."aircraftModel", c."highestInjuryLevel", c."totalFatal", c."completionStatus", c.report_url
FROM 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c LEFT JOIN 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a ON a.case_mkey = c."mKey" AND a.position = 1
WHERE c."highestInjuryLevel" = 'Fatal'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2074245'))
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESCRun it at the DuckDB prompt, or in any tool that reads Parquet over HTTPS. More ways to query the release are on Use the data.
NTSB ERA25FA173Accident · 3 fatalClass 3 · FieldPreliminary reportCessna 310R · Boca Raton, FLOn April 11, 2025, at 1023 eastern daylight time, a Cessna 310R, N8930N, was destroyed when it was involved in an accident near Boca Raton, Florida. The two pilots and the passenger were fatally injured, and one person on the ground sustained minor injuries.…NTSB CEN24FA089Accident · 3 fatalClass 3 · FieldFinal reportCessna 310R · Poolville, TXPilot incapacitation for undetermined reasons which resulted into controlled descent into terrain.NTSB ERA22FA114Accident · 1 fatalClass 3 · FieldFinal reportCessna 310 · Danville, VAThe pilot’s impairment due to exposure to carbon monoxide as a result of undetected engine exhaust penetration into the cockpit, resulting in the pilot's failure to maintain a minimum controllable airspeed after partially securing an engine after takeoff.NTSB WPR21LA030Accident · 2 fatalClass 3 · LimitedFinal reportCessna 310 · Las Vegas, NVThe 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…NTSB ERA19FA039Accident · 1 fatalField investigationFinal reportCessna 310 · Walton, NYAn in-flight fire of undetermined origin. Contributing to the accident were the severe icing conditions encountered during the final minutes of the flight, which led to a loss of airplane control.NTSB ERA15FA325Accident · 1 fatalField investigationFinal reportCessna 310R · Titusville, FLThe pilot's continued flight into known convective weather conditions, which resulted in the airplane's encounter with thunderstorms and the pilot's subsequent loss of airplane control during a missed approach. Contributing to the accident was the failure of…NTSB ERA15WA026Accident · 1 fatalForeign investigationCessna 310R · Governors Harbor, BahamasNTSB CEN14FA110Accident · 1 fatalField investigationFinal reportCessna 310R · Waterford, MIThe pilot's controlled flight into terrain during an instrument landing system approach at night in instrument flight rules conditions. Contributing to the accident were the operator's inadequate training of the pilot, the operator's failure to provide a…NTSB ERA14FA068Accident · 3 fatalField investigationFinal reportCessna 310R · Jacksonville, FLThe pilot’s failure to maintain airplane control during a missed approach in night instrument meteorological conditions due to spatial disorientation and a lack of instrument proficiency.NTSB CEN14FA051Accident · 2 fatalField investigationFinal reportCessna T310R · Junction, TXThe noninstrument-rated private pilot's decision to continue a visual flight rules flight into instrument meteorological conditions, which resulted in the loss of airplane control. Contributing to the accident was the pilot’s failure to obtain a weather…NTSB ERA11FA232Accident · 3 fatalField investigationFinal reportCessna 310R · McComb, MSThe pilot's impairment due to alcohol ingestion and his failure to maintain airplane control during an approach at night in instrument meteorological conditions.NTSB ERA11FA218Accident · 2 fatalField investigationFinal reportCessna 310R · Pikeville, KYThe 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…NTSB ERA11FA185Accident · 1 fatalField investigationFinal reportCessna 310R · Smyrna, TNThe pilot's improper response to a known autopilot pitch divergence anomaly. Contributing to the accident was the pilot's decision to perform a test flight on a system for which he lacked a complete working knowledge.NTSB WPR10FA136Accident · 3 fatalField investigationFinal reportCessna 310R · Palo Alto, CAThe pilot’s failure follow the standard instrument departure as instructed, and his failure to attain a sufficient altitude to maintain clearance from power lines during takeoff in instrument meteorological conditions.NTSB CEN10FA071Accident · 1 fatalField investigationFinal reportCessna 310R · Alva, OKThe 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…NTSB CHI08FA055Accident · 1 fatalField investigationFinal reportCessna 310R · Traverse City, MIThe pilot's failure to maintain a proper glidepath during the instrument approach, which led to his loss of control and subsequent impact with trees and terrain.NTSB NYC08FA046Accident · 1 fatalField investigationFinal reportCessna 310R · Owensboro, KYA loss of control during approach for undetermined reasons.NTSB NYC07MA162Accident · 5 fatalClass 1 · MajorFinal reportCessna 310R · Sanford, FLActions and decisions by National Association for Stock Car Auto Racing's corporate aviation division's management and maintenance personnel to allow the accident airplane to be released for flight with a known and unresolved discrepancy, and the accident…NTSB ATL05FA145Accident · 1 fatalField investigationFinal reportCessna 310R · Apopka, FLThe pilot's failure to maintain adequate visual lookout and object clearance, which resulted in the in-flight collision with trees.NTSB NYC05FA021Accident · 2 fatalField investigationFinal reportCessna 310R · Paeonian Spring, VAThe pilot's failure to follow the published instrument approach procedure, which resulted in an in-flight collision with terrain. A factor related to the accident was the low cloud ceiling.NTSB NYC04FA123Accident · 1 fatalField investigationFinal reportCessna 310R · Willoughby, OHThe pilot's failure to maintain aircraft control during the initial climb after takeoff. Factors in this accident were clouds and the night conditions.NTSB CHI01FA218Accident · 1 fatalField investigationFinal reportCessna 310R · Oak Creek, WIThe pilot not maintaining clearance from objects during an ILS approach in low night IFR conditions and his descent below decision height. Factors were the dark night, mist, low ceiling, and the trees west of the approach.NTSB NYC01FA064Accident · 1 fatalField investigationFinal reportCessna 310R · Bluefield, WVThe pilot's failure to execute the published missed approach procedure. A factor was heavy snowfall during the approach.NTSB NYC99FA047Accident · 1 fatalField investigationFinal reportCessna 310R · Kearny, NJa loss of elevator control for undetermined reasons.NTSB CHI98FA356Accident · 2 fatalField investigationFinal reportCessna 310R · Seymour Twp., WIthe pilots of both airplanes not maintaining visual separation from the other airplane.NTSB NYC98FA035Accident · 2 fatalField investigationFinal reportCessna 310R · St Mary'S, PAwas the pilot's descent below the minimum descent altitude and his failure to comply with published procedures.NTSB ATL96FA066Accident · 1 fatalField investigationFinal reportCessna 310R · Winder, GAThe pilot's failure to maintain visual flight conditions which resulted in the loss of control and subsequent inflight breakup of the airplane when he exceeded the design stress limits of the airframe.NTSB CHI96FA095Accident · 1 fatalField investigationFinal reportCessna 310 · Portland, INthe pilot's failure to maintain an altitude adequate for terrain clearance. A factor was the weather.NTSB BFO96FA032Accident · 3 fatalField investigationFinal reportCessna 310R · Bellville, OHthe pilot's in-flight loss of aircraft control for undetermined reason(s), which resulted in the airplane exceeding its design stress limitations and an in-flight breakup.NTSB NYC94FA166Accident · 2 fatalField investigationFinal reportCessna 310R · Blain, PAThe pilot's impairment of judgment and performance due to drugs, failure to maintain control of the airplane, and exceeding the design stress limits of the airplane, which resulted in an in-flight breakup of the airplane. A factor related to the accident was:…NTSB LAX94FA116Accident · 1 fatalField investigationFinal reportCessna 310R · La Jolla, CAthe pilot's failure to maintain control of the airplane. Factors in the accident were the dark night lighting conditions, moderate to severe turbulence, and heavy rain.NTSB ANC93FA027Accident · 1 fatalField investigationFinal reportCessna 310 · Teller, AKThe pilot-in-command's failure to maintain an adequate terrain avoidance altitude. Factors which contributed to the accident were the dark night and featureless snow covered terrain, both which created a 'featureless terrain illusion' which probably led the…NTSB BFO93FA003Accident · 1 fatalField investigationFinal reportCessna 310R · Summersville, WVThe pilot's inadequate altitude (or clearance) from mountainous hilly terrain. Factors related to the accident were darkness, low clouds, and light snow.NTSB LAX93LA019Accident · 3 fatalLimited investigationFinal reportCessna 310R · Saipan, MauritiusThe pilot not following wake turbulence (votex) avoidance procedures, which are detailed in FAA publications, resulting in the airplane encountering wake turbulence. Factors in this accident were: 1) the pilot's inability to control the airplane after…NTSB FTW92FA232Accident · 1 fatalField investigationFinal reportCessna 310R · Idabel, OKThe pilot's descent below the minimum descent altitude. Factors were the pilot's improper IFR procedure, low ceiling, and dark night conditions.NTSB ATL92FA091Accident · 1 fatalField investigationFinal reportCessna 310R · Gatlinburg, TNThe pilot's continued VFR flight into IMC, and his failure to attain a proper altitude over high, mountainous terrain. Factors were the high terrain, and the fog, clouds, and obscuration at the accident site.NTSB CHI92FA110Accident · 2 fatalField investigationFinal reportCessna 310R · Superior, WIInadequate airspeed, which resulted in an inadvertent stall/spin, and failure of the instructor pilot to take sufficient remedial action to prevent the loss of control.NTSB NYC90FA054Accident · 3 fatalField investigationFinal reportCessna 310R · Burlington, VTFor an unknown reason, the aircraft entered a descent and crashed in a lake.NTSB CHI89FA035Accident · 2 fatalField investigationFinal reportCessna 310R · Madison, INPilot-in-command's disregard of IFR procedures in descending below the minimum decision height for the approach to a point where collision with towers and/or wires became possible. His abrupt maneuver to avoid such collision resulted in a stall/spin, from…NTSB MKC88FA175Accident · 1 fatalField investigationFinal reportCessna 310R · Latimer, IAThe pilot had completed his normal flight schedule and was assigned an additional trip from des moines, Iowa to st paul, Minnesota. Calculations show that the pilot had flown an estimated 5 hours in the 8 1/2 hours preceding the accident. The line attendant…NTSB NYC88FA051Accident · 1 fatalField investigationFinal reportCessna 310R · Hector, NYThe pilot made a routine IFR position report 12 minutes prior to the accident. Witnesses observed an 'orange ball' before the crash. Evidence at the crash site showed inflight jettison of the pilot's emergency window, positive aerodydnamic overload separation…NTSB SEA86FA194Accident · 1 fatalField investigationFinal reportCessna 310C · Vancouver, WAPlt not IFR rated. Attempted departure from own airstrip in fog during early dawn. Positive rate of climb not established. Acft contacted terrain 3/4 mile from runway end. Psgrs reported no sensation of power probs, but complete loss of ground ref at liftoff.…NTSB ATL84FA169Accident · 2 fatalField investigationFinal reportCessna 310R · Clarkson, KYThe acft crashed after an in-flt separation of various components of the airframe. Post accident evidence provided by the failed parts gave a graphic picture of the in-flt seq which was supplemented by a witness who saw & heard the acft in its final dive.…NTSB MIA84FA090Accident · 1 fatalField investigationFinal reportCessna 310R · St. Petersburg, FLPrior to departure the plt noticed thunderstorms & lightning to the north of the arpt. He stated that immediately after takeoff he remembered a flash of light & a noise. His next recollection is impact & being in the water. The area around St. Petersburg at…NTSB NYC84FA054Accident · 1 fatalField investigationFinal reportCessna 310R · Buffalo, NYThe acft collided with lake erie during ILS approach to rwy 05 at Buffalo, NY. The acft had been descended to 3000 ft and the plt reported turning inbound from dunkirk VOR to the ILS. He was cleared for the approach and told to report the outer marker to…NTSB MIA83LA114Accident · 1 fatalLimited investigationFinal reportCessna 310R · Gulf Of MexicoThe plt flew from mobile, al to pensacola, FL, where a passenger enplaned for a flt to columbus, MS. After the passenger disembarked at columbus, the plt took off on an IFR flt plan back to mobile at an altutude of 7000 ft. reportedly, the flt progressed…NTSB ATL83FA128Accident · 3 fatalField investigationFinal reportCessna 310 · Hopkinsville, KYThe plt obtained a wx briefing & filed a flt plan from lexington to paducah,KY with a 15 min en route stop at bowling green, KY. While inbound to bowling green, he reported that the cloud base was at aprx 6000 ft & that there was lightning to the west. After…NTSB MIA83FA054Accident · 1 fatalField investigationFinal reportCessna 310R · Ft. Lauderdale, FLThe aircraft crashed while the pilot was apparently attempting to return to land after takeoff. No radio calls were made, but landing gear had been lowered. High speed and excessive rate of descent are not consistant with a normal or even emergency attempt to…NTSB MKC82FA160Accident · 2 fatalField investigationFinal reportCessna T310R · Council Bluffs, IAThe omaha weather was reported (in part) to be 3500 ft scattered, estimated 6000 ft broken, 18000 ft broken, visibility 4 mi with fog and haze, wind 200 deg at 5 KTS. However, the aircrew of a preceeding flight that arrived about 8 min earlier said they…NTSB NYC82FA188Accident · 1 fatalField investigationFinal reportCessna 310R · Danbury, CTApproaching the destination arpt, the plt was advised to plan a VOR rwy 24 approach & that he would be turned just inside the faf. At 0055, newark a/c identified the acft 3 mi north of the arpt still at 2,000 ft & asked the plt if he was able to execute the…