Fatal NTSB investigations: Continental IO-360 series
11 cases on aircraft whose registry engine model is Continental IO-360 series, where the first occurrence was “In flight collision with object”. 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
| 1986 | 2 |
|---|---|
| 1987 | 1 |
| 1988 | 1 |
| 1990 | 1 |
| 1998 | 1 |
| 2002 | 1 |
| 2004 | 2 |
| 2005 | 1 |
| 2007 | 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.engine_model_code IN ('17025', '17045')
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\" = 220))
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.engine_model_code IN ('17025', '17045')
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" = 220))
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 NYC08FA041Accident · 1 fatalField investigationFinal reportCirrus Design SR20 · New Windsor, NYThe pilot's failure to maintain the proper glidepath during an instrument-landing-system approach in fog. Contributing to the accident were pilot fatigue and air traffic control's failure to issue a minimum safe altitude warning.NTSB DFW05FA192Accident · 2 fatalField investigationFinal reportAero Commander 112 · Junction, TXThe pilot's failure to attain the proper climb rate resulting in the airplane's wing colliding with a tree and subsequent impact with the ground. Contributing factors were the pilot's improper use of the airplane's flaps, and the rising terrain.NTSB ATL05FA034Accident · 3 fatalField investigationFinal reportDiamond DA40-180 · Pelzer, SCThe pilot's failure to follow IFR procedures and to maintain assigned altitude resulting in a collision with a transmission wire and trees.NTSB NYC04FA127Accident · 1 fatalField investigationFinal reportMooney M20J · Oxford, CTThe pilot's failure to maintain altitude/clearance during an instrument approach, which resulted in a collision with trees prior to the runway. Factors were nighttime conditions and cloud cover.NTSB MIA02LA085Accident · 1 fatalLimited investigationFinal reportGrote Cruiser TR-4 · Pembroke Pines, FLthe pilot-in-command delayed initiating a go-around and failed to obtain sufficient altitude to clear obstacles at the departure end of the airport which resulted in an in-flight collision with power lines.NTSB NYC98LA110Accident · 1 fatalLimited investigationFinal reportCessna 337B · Montgomery, NYthe pilot's improper decision to initiate a takeoff with the rear engine inoperative, which resulted in an airplane that could not climb sufficiently to clear obstacles (trees).NTSB FTW90GA088Accident · 1 fatalFinal reportCessna 337G · Notrees, TXThe pilot's decision to continue VFR flight into known IMC.NTSB MIA88FA179Accident · 1 fatalField investigationFinal reportCessna 172K · Lake City, FLThe acft, while on a local flight, struck a telephone transmission line on the approach end of runway 1. Witnesses stated that they saw the acft takeoff to the west and make a right turn and go out of sight. Aprx three to five minutes later, they heard the…NTSB SEA87FA135Accident · 2 fatalField investigationFinal reportMaule M-4-210C · Sitka, AKPlt was on local VFR flight plan. Witnesses observed acft flying at low level along beaches. Later, witness saw smoke rising from wooded terrain about two miles inland from nearest beach. Investigation revealed no evidence of inflight failure of malfunction…NTSB SEA86FA053Accident · 1 fatalField investigationFinal reportCessna 172XP · Napa, CABefore taking off, the plt appeared to have difficulty following taxi instructions. He then took off without clearance against crossing traffic. When he returned to land, he was cleared for rgt traffic to rwy 18. The acft entered a left downwind for rwy 24…NTSB ATL86FA055Accident · 2 fatalField investigationFinal reportCessna T337B · Talladega, ALThe acft collided with trees during the final approach to landing. The light conditions were dark, skies were clear and winds were calm. Prior to the accident, the plt had landed and visited the FBO from where the acft was recently purchased to correct some…