NTSB investigations: Lycoming IO-360-L2A, 2022
10 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\") = 2022
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") = 2022
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 ERA23LA074Accident · No injuriesClass 4 · LimitedFinal reportTextron 172 · Newnan, GAThe flight instructor’s inadequate remedial action during a simulated engine failure and low approach, which resulted in a collision with a runway light.NTSB CEN23LA035Accident · No injuriesClass 4 · LimitedFinal reportCessna 172 · Olathe, KSThe inflight collision with multiple geese during initial climb.NTSB ERA23LA159Accident · Minor injuriesClass 3 · LimitedFinal reportTextron 172S · Tuskegee, ALThe flight instructor’s improper flare, which resulted in a hard landing and subsequent runway excursion.NTSB ERA23LA022Accident · 1 fatalClass 3 · LimitedFinal reportCessna 172S · Statesboro, GAThe pilot’s failure to include deplaning procedures as part of a passenger safety briefing and failure to have the passengers remain onboard until the engine was shut down, which resulted in a passenger subsequently being struck by the rotating propeller.NTSB ERA23LA017Accident · No injuriesClass 4 · LimitedFinal reportCessna 172 · Sanford, FLThe pilot's unstable approach, which resulted in a hard landing and impact with a runway threshold light. Also causal was the flight instructor’s failure to take remedial action to prevent the hard landing.NTSB ERA23FA001Accident · 3 fatalClass 3 · FieldFinal reportCessna 172S · Hermantown, MNThe pilot’s loss of airplane control due to spatial disorientation during initial climb in dark night and low instrument meteorological conditions, which resulted in a descent into terrain. Contributing to the accident was the pilot’s fatigue due to a long…NTSB CEN22FA424Accident · 3 fatalClass 3 · FieldFinal reportCessna 172S · Longmont, COThe pilots’ inability to see and avoid each other, resulting in a midair collision.NTSB CEN22LA281Accident · No injuriesClass 4 · LimitedFinal reportCessna 172S · Fargo, NDThe flight instructor’s failure to adequately monitor the pilot flying, which resulted in a nose-wheel first hard landing.NTSB CEN22LA194Accident · No injuriesClass 3 · LimitedFinal reportCessna 172S · Traverse City, MIThe failure of maintenance personnel to properly torque a fuel line “B” nut, which resulted in a total loss of engine power.NTSB WPR22LA123Accident · No injuriesClass 4 · LimitedFinal reportCessna 172S · San Carlos, CAThe pilot’s improper landing flare which resulted in a bounced landing.