NTSB investigations: Lycoming 0-320 series, 1990

14 cases on aircraft whose registry engine model is Lycoming 0-320 series, where the first occurrence was “Overrun”. 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, 1990 per year, 1982–2026: 240 cases
198215
198322
198419
198512
19865
19876
198810
198911
199014
199110
199215
199312
19949
19957
19963
19978
19984
19998
20008
20014
20029
20039
20047
20056
20065
20072

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\") = 1990
    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\" = 340))
  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 ATL91LA003Accident · Serious injuriesLimited investigationFinal reportGrumman AA-5A · Lexington, NCThe pilot's failure to establish an approach profile which would have allowed him to make a safe landing on the runway. The pilot misjudged his altitude and airspeed throughout the approach. A factor to the accident was the collision with the railroad berm.Oct 14, 1990 · N7103L · Substantial damageNTSB ANC90LA183Accident · No injuriesLimited investigationFinal reportPiper PA-18-150 · Coal Creek, AKThe pilot's failure to adequately remove snow from the airplane and his delay in aborting the takeoff.Sep 23, 1990 · N7580Y · Substantial damageNTSB LAX90LA334Accident · No injuriesLimited investigationFinal reportCessna 172M · Orovada, NVThe pilot's failure to initiate a go-around. His lack of recent experience in type of operation, (landings), and the inadvertent ground loop were factors in the accident.Sep 22, 1990 · N13686 · Substantial damageNTSB CHI90LA251Accident · No injuriesLimited investigationFinal reportPiper PA-28-140 · Elwood, INThe pilot's failure to abort takeoff.Aug 31, 1990 · N16504 · Substantial damageNTSB LAX90LA287Accident · No injuriesLimited investigationFinal reportCessna 172P · Coalinga, CAThe failure of the student pilot to accurately interpret the wind sock, and his inadvertent attempt to perform a downwind landing.Aug 11, 1990 · N9551L · Substantial damageNTSB NYC90LA184Accident · No injuriesLimited investigationFinal reportPiper PA-28-140 · Tunkhannock, PAThe pilot did not obtain the proper touchdown point which resulted in an overrun. The factors were altitude, wet runway, and go around not performed.Aug 4, 1990 · N7265F · Substantial damageNTSB CHI90LA211Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-140 · Mooresville, INThe pilot in commands failure to land with enough runway remaining resulting in a runway overun and on ground collision with a wall.Aug 2, 1990 · N1753T · Substantial damageNTSB CHI90FA196Accident · No injuriesField investigationFinal reportCessna 172 · Canton, MIThe pilot's inadequate takeoff procedure, premature liftoff and delayed reaction to abort the takeoff.Jul 25, 1990 · N4330Q · Substantial damageNTSB LAX90LA237Accident · No injuriesLimited investigationFinal reportCessna 172M · El Cajon, CAThe pilot-in-command's failure to abort the landing after touchdown past the touchdown zone.Jun 30, 1990 · N9313H · Substantial damageNTSB DEN90LA126Accident · No injuriesLimited investigationFinal reportCessna 172 · Boulder, COThe pilot's failure to touch down at the proper point, his misjudgment of the distance required for takeoff following the touch and go, and his delayed decision to abort the takeoff.Jun 7, 1990 · N2723E · Substantial damageNTSB BFO90LA049Accident · No injuriesLimited investigationFinal reportPiper PA-28-140 · Lusby, MDThe pilot misjudged the distance needed to touchdown and stop his aircraft before running off the end of the runway. The pilot failed to use all of the available runway during the landing sequence.May 26, 1990 · N43078 · Substantial damageNTSB BFO90LA034Accident · Serious injuriesLimited investigationFinal reportPiper PA-22-150 · Lovingston, VAPilot failure to climb out of ground effect because of inadequate airspeed. Factor was unfavorable wind at takeoff.Apr 8, 1990 · N8874D · Substantial damageNTSB LAX90LA118Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Redding, CAThe pilot's decision not to use full flaps which resulted in a long landing on a wet runway.Mar 15, 1990 · N13317 · Substantial damageNTSB CHI90LA063Accident · No injuriesLimited investigationFinal reportCessna 172 · Newark, ILImproper planning/decision by the pilot. The wet condition of the grass runway was a related factor.Jan 6, 1990 · N98923 · Substantial damage