NTSB investigations: Lycoming 0-320 series, CT

8 cases on aircraft whose registry engine model is Lycoming 0-320 series, where the first occurrence was “Loss of control - on ground/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

19862026
NTSB investigations: Lycoming 0-320 series, CT per year, 1986–2026: 8 cases
19861
19871
19911
19981
20001
20011
20031
20061

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\" = 'CT' 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 ('41508')
      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\" = 260))
  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 NYC06CA057Accident · No injuriesData collectionFinal reportPiper PA-28-161 · New Haven, CTThe student pilot's improper flare and inadequate recovery from a bounced landing, which resulted in a loss of aircraft control during landing and subsequent impact with a ditch.Jan 22, 2006 · N9284A · Substantial damageNTSB NYC03LA064Accident · No injuriesLimited investigationFinal reportPiper PA-22/20-150 · South Woodstock, CTThe pilot's failure to maintain directional controlMar 8, 2003 · N7342D · Substantial damageNTSB NYC01LA219Accident · No injuriesLimited investigationFinal reportCessna 172M · Danbury, CTAn inoperative airspeed indicator and the pilot's improper recovery from the bounced landing.Aug 26, 2001 · N9869Q · Substantial damageNTSB NYC00LA151Accident · No injuriesLimited investigationFinal reportMeadows Pitts Special S-1 · Meriden, CTThe pilot's loss of control of the airplane during the landing roll, due to his locking of the brakes.Jun 4, 2000 · N63DM · Substantial damageNTSB IAD98LA108Accident · No injuriesLimited investigationFinal reportPiper PA-18-150 · Oxford, CTThe pilot's inability to maintain directional control during the landing roll due to separation of the tailwheel spring assembly.Sep 13, 1998 · N7236K · Substantial damageNTSB NYC91LA106Accident · No injuriesLimited investigationFinal reportCessna 172P · Burlington, CTThe failure of the pilot to maintain directional control during the landing. Factors related to the accident were: improper use of the flight controls by the pilot, his lack of recent experience and total time, and the crosswind.Apr 6, 1991 · N64182 · Substantial damageNTSB NYC87LA213Accident · No injuriesLimited investigationFinal reportCessna 172P · Plainfield, CTWhile landing in crosswind conditions, the pilot failed to compensate for the conditions and lost directional control of the aircraft. The aircraft went down an embankment, collided with a fence and then flipped inverted.Aug 4, 1987 · N99171 · Substantial damageNTSB NYC86LA087Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Hartford, CTThe cross country solo flight was taking off on runway 02 at Hartford, Connecticut. The pilot performed a runup and was cleared for takeoff. The pilot attempted rotation at about 60 KIAS, but aircraft did not lift off. Trim tab was set at neutral on runup. As…Mar 22, 1986 · N4347G · Substantial damage