NTSB investigations: Lycoming O&VO-360 series, MI
5 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
| 1983 | 1 |
|---|---|
| 1986 | 1 |
| 2005 | 3 |
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.\"eventStateOrRegion\" = 'MI' 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 ('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.
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."eventStateOrRegion" = 'MI' 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 ('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" 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 CHI05CA265Accident · No injuriesData collectionFinal reportAviat A-1B · Drummond Island, MIThe pilot's failure to adequately compensate for the wind conditions, his failure to perform a go-around, and he flared improperly. Factors included the downdraft and the shoreline.NTSB CHI05CA247Accident · No injuriesData collectionFinal reportPiper PA-28-181 · Ypsilanti, MIThe pilot's failure to maintain adequate airspeed which resulted in his inability to properly flare the airplane and the subsequent hard landing.NTSB CHI05CA060Accident · No injuriesData collectionFinal reportCessna 172RG · Berrien Springs, MIThe pilot not maintaining airspeed leading to an excessive sink rate during a simulated emergency landing after takeoff. An additional cause was the certified flight instructor's inadequate supervision.NTSB CHI86LA184Accident · No injuriesLimited investigationFinal reportPiper PA-28-181 · Traverse City, MIWhile flaring to land, the aircraft had excessive speed and ballooned. Subsequently, it bounced twice, then began to veer to the left. The pilot performed a go-around. During the initial portion of the go-around, the left wing struck a runway edge identifier…NTSB CHI83LA168Accident · No injuriesLimited investigationFinal reportPiper PA-28-181 · Harrison, MIThe pilot stated that he executed a go-around on the first landing attempt because of a strong crosswind and high airspeed. On the second approach, he executed a go-around from the flare because of a 'strong updraft'. The pilot statedthat during the…