NTSB investigations: Lycoming I0360 series, TX

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

19872026
NTSB investigations: Lycoming I0360 series, TX per year, 1987–2026: 7 cases
19872
19901
19941
20011
20031
20051

Latest 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.\"eventStateOrRegion\" = 'TX' AND c.\"eventCountry\" = 'USA'
    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')
      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.

NTSB DFW05FA099Accident · 3 fatalField investigationFinal reportPiper PA-28R-200 · Jefferson, TXThe pilot's failure to maintain clearance from an unmarked transmission line. A contributing factor was the low altitude flight.Apr 10, 2005 · N2981R · DestroyedNTSB FTW03FA182Accident · 2 fatalField investigationFinal reportCessna 172S · McKinney, TXThe CFI's failure to maintain airspeed sufficient for flight resulting in an inadvertent stall/spin during the forced landing. A contributing factor was the impact with a bird, which affected the performance of the airplane.Jul 8, 2003 · N166ME · DestroyedNTSB FTW02LA038Accident · Serious injuriesLimited investigationFinal reportHughes 269C · Richmond, TXthe pilot's failure to maintain clearance from the power line while landing.Nov 17, 2001 · N9294F · Substantial damageNTSB FTW95LA011Accident · No injuriesLimited investigationFinal reportHughes 269C · Livingston, TXThe improper flare resulting in an undershoot of the intended landing area. A factor was the bird strike.Oct 10, 1994 · N9616F · Substantial damageNTSB FTW90LA099Accident · Minor injuriesLimited investigationFinal reportEnstrom F-28A · Danbury, TXPilot in command's failure to see and avoid wires during the final stage of an approach to a confined area. A contributing factor to the accident was the pilot's disregard of the operator's instructions after he landed the first time.Apr 22, 1990 · N287Q · Substantial damageNTSB FTW88FA038Accident · 1 fatalField investigationFinal reportPiper PA-28R-200 · Burnet, TXThe pilot arrived in the area of his planned destination and completed the outbound and inbound procedure turns for the NDB runway 17 approach without reported incident. Almost immediately thereafter, the aircraft impacted a large oak tree about 15 feet AGL…Dec 19, 1987 · N33007 · DestroyedNTSB FTW87LA144Accident · No injuriesLimited investigationFinal reportGreat Lakes 2T-1A · Lago Vista, TXWhile maneuvering at approximately 50 feet AGL, the aircraft's landing gear contacted a 7200 volt powerline. Control of the aircraft was lost, and it descended out of control into about 2 feet of water, causing substantial damage.Jun 14, 1987 · N874K · Substantial damage