NTSB investigations: Lycoming IO-360-L2A, OK
4 cases on aircraft whose registry engine model is Lycoming IO-360-L2A. 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
| 2006 | 1 |
|---|---|
| 2014 | 1 |
| 2016 | 1 |
| 2019 | 1 |
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\" = 'OK' 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 ('41597'))
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" = 'OK' 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 ('41597'))
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 GAA19CA368Accident · No injuriesData collectionFinal reportCessna 172 · Tulsa, OKThe pilot's failure to maintain directional control while landing in gusting crosswind conditions, which resulted in a runway excursion and impact with a taxiway sign.NTSB GAA16CA208Accident · No injuriesData collectionFinal reportCessna 172 · Durant, OKThe pilot candidate's incorrect action performance by pulling the throttle off early and the subsequent failure to maintain the descent rate, resulting in a hard landing.NTSB CEN14FA506Accident · 1 fatalField investigationFinal reportCessna 172R · Okmulgee, OKThe pilot's continued visual flight into instrument meteorological conditions, which resulted in his failure to maintain clearance with trees and terrain.NTSB DFW07FA019Accident · 2 fatalField investigationFinal reportCessna 172S · Hominy, OKThe pilot's continued cruise flight into adverse weather conditions, and his failure to maintain clearance from terrain. Contributing factors were the dark night conditions, and the low ceilings.