NTSB investigations: Lycoming IO-360-L2A, 2006
15 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
| 2001 | 2 |
|---|---|
| 2002 | 1 |
| 2003 | 7 |
| 2004 | 18 |
| 2005 | 13 |
| 2006 | 15 |
| 2007 | 22 |
| 2008 | 24 |
| 2009 | 20 |
| 2010 | 20 |
| 2011 | 21 |
| 2012 | 22 |
| 2013 | 14 |
| 2014 | 16 |
| 2015 | 12 |
| 2016 | 21 |
| 2017 | 24 |
| 2018 | 11 |
| 2019 | 14 |
| 2020 | 14 |
| 2021 | 20 |
| 2022 | 10 |
| 2023 | 15 |
| 2024 | 19 |
| 2025 | 13 |
| 2026 | 16 |
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'))
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'))
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 MIA07CA019Accident · No injuriesData collectionFinal reportCessna 172S · New Smyrna, FLThe student pilot's improper recovery from a bounced landing.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.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 MIA07CA008Accident · No injuriesData collectionFinal reportCessna 172S · Ormond Beach, FLThe failure of the student pilot to initiate a recovery from the bounced landing resulting in a hard landing.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 ANC06CA114Accident · No injuriesData collectionFinal reportCessna 172 · Palatka, FLThe student's failure to maintain adequate airspeed to preclude a stall while maneuvering over the runway, and the instructor's inadequate supervision of the student pilot, which resulted in a collision with the runway. A factor in the accident was an…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 NYC06IA143Incident · No injuriesIncident investigationFinal reportCessna 172S · Lawrence, MAForeign object damage to the leading edge of the propeller blade, which resulted in fatigue cracking and subsequent blade failure.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 ATL06CA068Accident · No injuriesData collectionFinal reportCessna 172S · Gainsville, GAThe pilot's improper landing flare which resulted in a hard landing.NTSB ATL06CA062Accident · No injuriesData collectionFinal reportCessna C-172S · Sanford, NCThe pilot's improper landing flare which resulted in a hard landing.NTSB DFW06CA098Accident · No injuriesData collectionFinal reportCessna 172S · Denton, TXThe student pilot's failure to maintain directional control during the takeoff roll.NTSB ANC06CA036Accident · No injuriesData collectionFinal reportCessna 172S · Prescott, AZThe pilot's improper recovery from a bounced landing, which resulted in structural damage to the firewall and fuselage.