NTSB investigations: Cessna 310R
12 cases on aircraft the registry lists as Cessna 310R, where the first occurrence was “In flight collision with terrain/water”. 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
| 1982 | 3 |
|---|---|
| 1983 | 1 |
| 1985 | 1 |
| 1986 | 1 |
| 1992 | 1 |
| 1993 | 1 |
| 1997 | 1 |
| 2000 | 1 |
| 2001 | 1 |
| 2004 | 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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2074245')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 230))
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."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2074245')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o."occurrenceNumber" = 1 AND o."occurrenceCode" = 230))
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 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 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 SEA00LA040Accident · Serious injuriesLimited investigationFinal reportCessna 310R · Columbia Falls, MTFailure of the pilot-in-command to follow the prescribed instrument approach missed approach procedure.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 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 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 ATL86LMG01Accident · No injuriesFinal reportCessna 310R · Rocky Mount, NCThe acft touched down 150 ft short of rwy 04 at the Rocky mountain-wilson arpt. The acft contacted two rows of apch lights and a ground drop off which sheared all three landing gears. The flt departed wilson municipal arpt and upon reaching 3700 ft the plt…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 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…