NTSB investigations: Lycoming O-360 series
8 cases on aircraft whose registry engine model is Lycoming O-360 series, where the first occurrence was “Airframe/component/system failure/malfunction”. 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
| 2002 | 3 |
|---|---|
| 2003 | 2 |
| 2005 | 1 |
| 2007 | 2 |
Where
Open the mapLatest 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 c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41575')
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\" = 130))
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.
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 c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41575')
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" = 130))
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESCRun it at the DuckDB prompt, or in any tool that reads Parquet over HTTPS. More ways to query the release are on Use the data.
NTSB NYC08LA052Accident · No injuriesLimited investigationFinal reportRobinson Helicopter R22 Beta · Gainesville, FLThe pilot's failure to follow the published emergency procedure. Contributing to the accident was a malfunction of the clutch assembly.NTSB LAX07LA274Accident · No injuriesLimited investigationFinal reportRobinson R22 Beta · El Monte, CAa failure of the main rotor drive system V-belts due to damage sustained when the alternator drive belt failed and pieces of that belt got between the main drive belts and their associated pulleys. A contributing factor was the uneven terrain encountered in…NTSB LAX05LA122Accident · No injuriesLimited investigationFinal reportRobinson R22 Beta · Prescott, AZThe company mechanic's improper maintenance actions, which resulted in the total failure of the main rotor drive belt system on approach to landing. A factor was the soft terrain.NTSB LAX03LA228Accident · No injuriesLimited investigationFinal reportPiper PA-28-181 · Phoenix, AZThe disengagement of the left control wheel from the control column, which was due to the attaching screw backing out of the nut plate. Also causal was the manufacturer's inadequate design of the installation and the improper length of the screw.NTSB FTW03LA099Accident · Minor injuriesLimited investigationFinal reportRobinson R22 Beta II · Kent, TXThe loss of main rotor drive due to a drive belt separation resulting in a forced landing. A contributing factor was the lack of suitable terrain for the forced landing.NTSB CHI03FA025Accident · No injuriesField investigationFinal reportRobinson R22 · St. Jacob, ILFatigue fracture of the clutch assembly fan shaft and the resulting complete loss of power to the rotor drive system. A contributing factor was the loss of tail rotor authority due to the secondary failure of the control tube assembly.NTSB SEA02LA182Accident · No injuriesLimited investigationFinal reportCessna 172RG · Billings, MTThe failure of the landing gear actuator during landing as a result of fatigue.NTSB FTW02LA227Accident · Minor injuriesLimited investigationFinal reportRobinson R22 Beta · Cornudas, TXThe pilot's failure to maintain rotor RPM and his improper landing flare. A contributing factor was the activation of a warning light.