NTSB investigations: Lycoming O&VO-360 series, 2004

8 cases on aircraft whose registry engine model is Lycoming O&VO-360 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 O&VO-360 series, 2004 per year, 1982–2026: 121 cases
198210
19835
19849
19856
19865
19872
19885
19893
19901
19911
19925
19934
19944
19953
19965
19971
19986
19995
20003
20012
20027
20033
20048
20058
20066
20074

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\") = 2004
    AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41514')
      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 MIA05CA002Accident · Minor injuriesData collectionFinal reportRobinson R-22 · Pompano Beach, FLThe flight crew's excessive descent rate during landing, resulting in a hard landing, and the tail boom being severed.Oct 2, 2004 · N220CK · Substantial damageNTSB LAX04CA321Accident · No injuriesData collectionFinal reportRobinson R22 Beta · Kona, HIthe CFI's failure to maintain an adequate airspeed and main rotor rpm, and his improper flare, which resulted in a hard landing. A factor in the accident was the CFI's diverted attention.Sep 18, 2004 · N22XM · Substantial damageNTSB LAX04CA279Accident · No injuriesData collectionFinal reportAviat A-1B · Minden, NVThe pilot's inadequate compensation for the crosswind conditions and failure to maintain directional control. The misjudged landing flare and the crosswind were factors.Jul 24, 2004 · N268DM · Substantial damageNTSB FTW04LA135Accident · No injuriesLimited investigationFinal reportPiper PA-28-181 · Many, LAThe pilot's improper touchdown which resulted in a hard landing.May 7, 2004 · N21131 · Substantial damageNTSB LAX04LA297Accident · No injuriesLimited investigationFinal reportAviat A-1A · Visalia, CAthe pilot's failure to maintain an adequate airspeed on final approach, which resulted in an inadvertent stall and a hard landing.Apr 20, 2004 · N40AW · Substantial damageNTSB NYC04CA091Accident · No injuriesData collectionFinal reportPiper PA-28-180 · Norwood, MAThe student pilot failure to recover from a bounced landing. A factor in this accident was the student pilot's lack of solo flight experience.Mar 24, 2004 · N6535J · Substantial damageNTSB LAX04LA151Accident · No injuriesLimited investigationFinal reportPiper PA-28-180 · Reno, NVthe pilot's premature flare and failure to maintain adequate airspeed resulted in an inadvertent stall and a hard landing, which collapsed the landing gear.Mar 6, 2004 · N6367J · Substantial damageNTSB LAX04CA136Accident · No injuriesData collectionFinal reportCessna 177A · Honolulu, HIthe pilot's misjudged landing flare, which resulted in a hard landing and porpoising down the runway.Feb 16, 2004 · N30599 · Substantial damage