NTSB investigations: Lycoming 0-320 series, 2002, NC

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

Cases per year

19642026
NTSB investigations: Lycoming 0-320 series, 2002, NC per year, 1964–2026: 261 cases
19647
19658
19665
19676
19685
19694
19703
197113
197210
19738
197411
19759
19763
19773
19788
19797
19803
19817
19822
19836
19843
19852
19865
19871
19883
19897
19903
19911
19923
19935
19942
19952
19961
19971
19984
19991
20005
20013
20027
20035
20043
20051
20064
20074
20083
20091
20102
20116
20124
20133
20142
20153
20161
20172
20182
20194
20204
20213
20221
20234
20246
20251
20265

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.\"eventStateOrRegion\" = 'NC' 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'))
  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 MIA03LA029Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-150 · Cashiers, NCThe pilot's inadequate in-flight decision by which he conducted visual flight into instrument meteorological conditions and his failure to maintain terrain clearance. Contributing factors were a low ceiling and mountainous terrain.Dec 14, 2002 · N5899W · 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 ATL02LA168Accident · Serious injuriesLimited investigationFinal reportCessna 172P · Mocksville, NCThe pilot's failure to maintain airspeed during the takeoff and initial climb which resulted in an inadvertent stall and the subsequent collision with trees.Sep 10, 2002 · N62602 · Substantial damageNTSB MIA02LA158Accident · No injuriesLimited investigationFinal reportCessna 172N · Tarboro, NCThe failure of the solo student to maintain directional control of the airplane during the takeoff roll/run which resulted in the airplane veering off the runway and impacting trees, incurring substantial damage.Aug 25, 2002 · N2291E · Substantial damageNTSB MIA02LA157Accident · No injuriesLimited investigationFinal reportCessna 172N · Pinehurst, NCThe student pilot's improper recovery from bounced landing which resulted in substantial damage to the airplane.Aug 25, 2002 · N4859F · Substantial damageNTSB MIA02LA118Accident · No injuriesLimited investigationFinal reportCessna 150D · Louisburg, NCthe failure of the pilot-in-command to follow emergency procedures after smelling smoke that resulted in an electrical fire, damage to the airplane, and a forced landing.Jun 23, 2002 · N4313U · Substantial damageNTSB ATL02LA039Accident · No injuriesLimited investigationFinal reportCessna 172M · Sanford, NCThe pilots failure to maintain directional control during landing roll that resulted in a collision with an airport sign. Factors were wet runway surface and wind gust.Jan 13, 2002 · N9334H · Substantial damage