NTSB investigations: Lycoming 0-320 series, 2002

22 cases on aircraft whose registry engine model is Lycoming 0-320 series, where the first occurrence was “Hard landing”. 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: 384 cases
198220
198312
198416
198515
198613
198721
19888
198913
19905
199112
199212
199315
199419
199512
199622
199715
199816
199920
200016
200112
200222
200312
200416
200513
200616
200711

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\" = 200))
  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 LAX03LA053Accident · No injuriesLimited investigationFinal reportCessna 172N · Pacoima, CAthe student pilot's excessive use of the elevator control that resulted in an inadvertent lift-off and his failure to maintain/attain adequate airspeed, which resulted in a stall and hard landing.Dec 21, 2002 · N733AM · Substantial damageNTSB CHI03LA030Accident · Minor injuriesLimited investigationFinal reportPiper PA-22-150 · Cuba, MOThe pilots inadequate flare and recovery from a bounced landing. Contributing factors to this accident were the crosswind and the ditch.Nov 28, 2002 · N4901S · Substantial damageNTSB SEA02LA186Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Spokane, WAThe flight instructor's delay of the remedial action necessary to correct for the student pilot's error during the landing flare. Factors include the student pilot's misjudgment of the aircraft's height above the runway when he initiated the flare.Sep 28, 2002 · N132ND · Substantial damageNTSB NYC02LA191Accident · Minor injuriesLimited investigationFinal reportRobinson R-22B · Frederick, MDThe student pilot's failure to maintain adequate rotor rpm, and the flight instructor's delayed remedial action. A factor was the manufacturer's inadequate written guidance regarding simulated engine failures during takeoff.Sep 16, 2002 · N2549R · 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 MIA02LA155Accident · Serious injuriesLimited investigationFinal reportBarnes Vans RV-6 · Chesnee, SCthe pilot misjudged the landing flare, resulting in a hard landing, loss of directional control, and damage to the airplane.Aug 21, 2002 · N190TB · Substantial damageNTSB ATL02LA154Accident · No injuriesLimited investigationFinal reportCessna 172M · Enterprise, ALThe pilot's delayed flare on landing that resulted in a hard landing.Aug 9, 2002 · N73461 · Substantial damageNTSB ANC02LA124Accident · No injuriesLimited investigationFinal reportWilliamson GlaStar · Anchorage, AKThe pilot's failure to maintain directional control of the airplane during the landing roll. Factors in the accident were the pilot's inadequate compensation for the crosswind condition, and the misjudged landing flare.Aug 8, 2002 · N62849 · Substantial damageNTSB IAD02LA082Accident · No injuriesLimited investigationFinal reportCessna 172M · Mount Pocono, PAThe pilot's improper flare, which resulted in a hard landing.Aug 7, 2002 · N1727V · Substantial damageNTSB NYC02LA145Accident · No injuriesLimited investigationFinal reportCessna 172N · Middletown, RIThe pilot's improper flare. A factor was the shifting wind.Jul 14, 2002 · N733NQ · Substantial damageNTSB ATL02LA140Accident · No injuriesLimited investigationFinal reportCessna 172P · Merritt Island, FLThe pilot's improper recovery after a bounced landing and improper landing flare which resulted in the airplane colliding with the runway.Jul 12, 2002 · N54119 · Substantial damageNTSB NYC02LA134Accident · No injuriesLimited investigationFinal reportCessna 172 · West Milford, NJThe flight instructor's improper recovery from a bounced landing.Jul 11, 2002 · N1502E · Substantial damageNTSB IAD02LA067Accident · No injuriesLimited investigationFinal reportCessna 172 · Fulton, NYThe pilot's improper flare, which resulted in a misaligned, hard landing.Jul 4, 2002 · N6338F · Substantial damageNTSB DEN02LA060Accident · No injuriesLimited investigationFinal reportCessna 172M · Telluride, COthe pilot not maintaining proper aircraft control resulting in a hard landing. Factors contributing to this accident were the high airspeed, the porpoise encountered during the landing, and the pilot's delayed remedial action resulting in the damage to the…Jun 19, 2002 · N9089H · Substantial damageNTSB FTW02LA175Accident · Serious injuriesLimited investigationFinal reportCessna 177 · Sherman, TXThe hard landing as result of the pilot's failure to maintain aircraft control during landing. A contributing factor was the gusty crosswinds.Jun 9, 2002 · N2282Y · Substantial damageNTSB LAX02LA153Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Green Valley, AZThe pilot's failure to identify the wind direction, which led to an attempted downwind landing approach that resulted in a hard landing and severe bounce. Also causal was the pilot's failure to promptly retract the flaps during the rejected landing after…May 8, 2002 · N754LT · Substantial damageNTSB ATL02LA090Accident · No injuriesLimited investigationFinal reportCessna 177 · Locust Grove, GAThe pilot improper flare during an aborted takeoff, followed by an subsequent hard landing.Apr 29, 2002 · N2809X · Substantial damageNTSB FTW02LA147Accident · No injuriesLimited investigationFinal reportCessna 172P · McKinney, TXthe student pilot's failure to properly recover from a bounced landing which resulted in the airplane porpoising. A contributing factor was the student pilot's improper landing flare which resulted in a bounced landing.Apr 8, 2002 · N99341 · Substantial damageNTSB LAX02LA128Accident · No injuriesLimited investigationFinal reportWilson Magnum · Woodland, CAThe pilot's inadequate compensation for the gusty crosswind condition, and his failure to maintain airplane control.Apr 6, 2002 · N229JW · Substantial damageNTSB LAX02LA135Accident · No injuriesLimited investigationFinal reportCessna 172M · Avalon, CAThe pilot's inadequate bounced landing recovery technique, which resulted in an inadvertent porpoise.Mar 24, 2002 · N61737 · Substantial damageNTSB LAX02LA106Accident · No injuriesLimited investigationFinal reportCessna 172M · Tucson, AZthe pilot's misjudged landing flare and improper bounced landing recovery.Mar 10, 2002 · N4410R · Substantial damageNTSB NYC02LA070Accident · No injuriesLimited investigationFinal reportCessna 172P · Coatesville, PAThe student pilot's loss of aircraft control which resulted in a hard landing, and the CFI's delayed remedial action. Factors related to the accident were the fatigue cracks which initiated at the attachment hole on the landing gear strut, and the crosswind…Mar 2, 2002 · N65021 · Substantial damage