NTSB investigations: Lycoming IO-360-L2A, 2006
7 cases on aircraft whose registry engine model is Lycoming IO-360-L2A, where the first occurrence was “Loss of control - on ground/water”. 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
| 2003 | 1 |
|---|---|
| 2004 | 6 |
| 2005 | 3 |
| 2006 | 7 |
| 2007 | 8 |
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 year(c.\"eventDate\") = 2006
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')
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\" = 260))
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 year(c."eventDate") = 2006
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')
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" = 260))
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 SEA07LA013Accident · No injuriesLimited investigationFinal reportCessna 172S · Richfield, UTThe student pilot's inability to compensate for the gusty crosswinds during the initial part of the landing roll, which resulted in a loss of control and a noseover. Factors associated with the accident are gusty crosswinds, and a mound/berm of dirt alongside…NTSB NYC06CA232Accident · No injuriesData collectionFinal reportCessna 172S · Cambridge, MDThe pilot's failure to maintain directional control while landing.NTSB SEA06CA187Accident · No injuriesData collectionFinal reportCessna 172S · Naples, FLThe student pilot's failure to adequately compensate for wind conditions during the landing roll. A drainage ditch and wind were contributing factors.NTSB ATL06CA117Accident · No injuriesData collectionFinal reportCessna 172S · Thomson, GAThe student pilot's failure to maintain directional control during the landing roll resulting in an on-ground collision with an embankment.NTSB LAX06CA174Accident · No injuriesData collectionFinal reportCessna 172S · Madera, CAthe pilot's failure to maintain directional control during the landing rollout.NTSB NYC06CA116Accident · No injuriesData collectionFinal reportCessna 172S · Louisville, KYThe student pilot's failure to maintain directional control during the takeoff roll.NTSB DFW06CA098Accident · No injuriesData collectionFinal reportCessna 172S · Denton, TXThe student pilot's failure to maintain directional control during the takeoff roll.