Fatal NTSB investigations: Lycoming I0360 series, CT

7 cases on aircraft whose registry engine model is Lycoming I0360 series. 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.

Defining event

Finding

Phase of flight

Aircraft model

Cases per year

19842026

Fatal NTSB investigations: Lycoming I0360 series, CT per year, 1984–2026: 7 cases
1984	2
1988	1
2001	1
2002	1
2016	1
2017	1

Where

Open the map

Latest cases

Query with SQL

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."eventStateOrRegion" = 'CT' AND c."eventCountry" = 'USA' AND 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 ('41515')) ORDER BY c."eventDate" DESC, c."ntsbNumber" DESC

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.\"eventStateOrRegion\" = 'CT' AND c.\"eventCountry\" = 'USA'
    AND 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 ('41515'))
  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."eventStateOrRegion" = 'CT' AND c."eventCountry" = 'USA'
  AND 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 ('41515'))
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESC

Run 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 ERA17FA327Accident · 2 fatalField investigationFinal reportMooney M20C · North Branford, CTA total loss of engine power due to fuel starvation as the result of foreign object debris in the fuel selector valve. Contributing to the accident was the pilot's selection of a low cruising altitude, which reduced the available time to troubleshoot the loss…Sep 16, 2017 · N53CP · Substantial damage NTSB ERA17FA011Accident · 1 fatalField investigationFinal reportPiper PA 34-200 · East Hartford, CTThe NTSB did not determine the probable cause of this event and does not plan to issue a report or open a public docket. The investigation of this event is being conducted under the jurisdiction of the Federal Bureau of Investigation.Oct 11, 2016 · N15294 · Destroyed NTSB IAD02FA086Accident · 2 fatalField investigationFinal reportCessna 172S · Plainville, CTAn in-flight engine compartment fire of unknown origin, and a loss of engine power for undetermined reasons. Also causal, was the pilot's failure to maintain airspeed during a turn back to the airfield, which resulted in an inadvertent stall and subsequent…Aug 17, 2002 · N35073 · Destroyed NTSB IAD02FA024Accident · 1 fatalField investigationFinal reportPiper PA-28R-180 · Milford, CTThe pilot's failure to follow the published IFR approach procedure, which resulted in a premature descent and subsequent impact with water. A factor was the night, overwater visual conditions.Dec 30, 2001 · N7427J · Substantial damage NTSB NYC88FA229Accident · 4 fatalField investigationFinal reportPiper PA-28R-201 · Pomfret, CTThe Piper arrow PA-28R-201, had asked ATC for vectors to windam airport. After being vectored the pilot requested his distance from the airport. He was told that he was 12 miles from the airport, the pilot then decided to descend. ATC advised the pilot to…Aug 28, 1988 · N3478M · Destroyed NTSB NYC84FA129Accident · 1 fatalField investigationFinal reportPiper PA-28R-201 · Burlington, CTThe acft crashed in a steep right descending turn shortly after takeoff. The student plt flying the acft had been scheduled to fly that day but the instructor canceled the flt on account of weather. The acft was seen taxiing out ABOUT1230. After takeoff the…Apr 14, 1984 · N9487C · Destroyed NTSB NYC84FA108Accident · 1 fatalField investigationFinal reportPiper PA-28R-200 · Groton, CTThe plt received 2 wx briefings prior to departing & both called for low ceilings. During arrival at the destination, the plt requested & was cleared for an ILS apch to rwy 5. While on the apch, the acft collided with a small tree & crashed. The wreckage came…Mar 14, 1984 · N5022S · Destroyed