NTSB investigations: Lycoming 0-320 series, 2002

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

19822026
NTSB investigations: Lycoming 0-320 series, 2002 per year, 1982–2026: 393 cases
198232
198312
198417
198519
198620
198712
198814
198915
199013
199114
199218
199315
199417
199511
199614
199715
199815
199916
20009
200115
200213
200311
200415
200512
200616
200713

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 year(c.\"eventDate\") = 2002
    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\" = 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 CHI03LA040Accident · No injuriesLimited investigationFinal reportCessna 172M · Moline, ILThe pilot's failure to maintain altitude clearance during a base to final turn on approach. Contributing factors to the accident were the night conditions and the trees.Dec 6, 2002 · N80213 · Substantial damageNTSB MIA03FA016Accident · 1 fatalField investigationFinal reportPiper PA-28-140 · Climax, NCThe pilot's operation of the airplane at a low altitude during final approach that resulted in an in-flight collision with a tree, a witness reported pitch-up, and subsequent stall and in-flight collision with terrain.Nov 15, 2002 · N8162N · Substantial damageNTSB IAD03FA005Accident · 2 fatalField investigationFinal reportCessna 172N · Mount Sterling, KYThe failure of the pilot to follow the published instrument approach procedure, which resulted in an early descent into an antenna tower. A factor was the low ceiling.Oct 15, 2002 · N6413J · DestroyedNTSB SEA03LA004Accident · Minor injuriesLimited investigationFinal reportBellanca 7GCBC · Helena, MTThe student pilot's failure to maintain clearance from a tower during an aborted landing. Factors include landing with a tailwind and a tower.Oct 13, 2002 · N8752 · Substantial damageNTSB IAD02FA088Accident · 1 fatalField investigationFinal reportCessna 172N · Stanardsville, VAThe pilot's failure to maintain sufficient altitude/clearance while descending over mountainous terrain. A factor was the night lighting conditions.Aug 19, 2002 · N738JR · DestroyedNTSB LAX02FA234Accident · 1 fatalField investigationFinal reportPiper PA-28-140 · Kneeland, CAThe pilot's failure to maintain clearance with the trees while executing an instrument approach. Contributing factors were the clouds and obscuration weather conditions.Jul 23, 2002 · N8801N · DestroyedNTSB CHI02LA205Accident · Serious injuriesLimited investigationFinal reportPiper PA28-140 · El Dorado Sprgs, MOThe failure by the flight crew to abort the takeoff, as well as a failure by the flight instructor to properly monitor takeoff performance. Contributing factors to the accident were the flight crew's failure to calculate required takeoff distance, considering…Jul 19, 2002 · N8220N · Substantial damageNTSB SEA02FA125Accident · 2 fatalField investigationFinal reportCessna 172N · Otis, ORThe pilot's failure to maintain adequate clearance with power lines while conducting low altitude flight resulting in a loss of control and subsequent collision with terrain. Contributing factors were the pilot's low altitude flight and the power lines.Jul 6, 2002 · N738QT · DestroyedNTSB ANC02LA059Accident · No injuriesLimited investigationFinal reportBellanca 7GCBC · Wasilla, AKThe unqualified pilot's selection of an unsuitable landing site which resulted in an in-flight collision with a power line. Factors associated with the accident are the unqualified pilot's failure to see and avoid a power line, an unmarked power line, and…Jun 22, 2002 · N57391 · Substantial damageNTSB FTW02LA180Accident · Serious injuriesLimited investigationFinal reportFrennance Twinstar · Bastrop, LAthe pilot's failure to maintain altitude for an undetermined reason, which resulted in an in-flight collision with trees.Jun 14, 2002 · N711FS · DestroyedNTSB SEA02FA085Accident · 2 fatalField investigationFinal reportRobinson R-22 Mariner · Merlin, ORClearance from a cable running perpendicular to a river was not maintained during low level cruise flight. A cable was a factor.May 23, 2002 · N2322Y · Substantial damageNTSB ATL02FA059Accident · 2 fatalField investigationFinal reportPiper PA-28-151 · Macon, GAThe pilot's failure to maintain clearance from a tree while maneuvering after takeoff.Mar 4, 2002 · N41340 · Substantial damageNTSB FTW02LA063Accident · Serious injuriesLimited investigationFinal reportCessna 172N · Durango, COthe pilot's failure to maintain clearance with the trees and mountainous terrain while maneuvering. A contributing factor was the pilot's delay in taking remedial action.Jan 9, 2002 · N3535E · Substantial damage