NTSB investigations: Lycoming IO-360-L2A, MD
14 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
| 2004 | 2 |
|---|---|
| 2005 | 1 |
| 2006 | 1 |
| 2008 | 2 |
| 2010 | 1 |
| 2011 | 1 |
| 2012 | 1 |
| 2016 | 2 |
| 2018 | 1 |
| 2020 | 1 |
| 2025 | 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\" = 'MD' 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" = 'MD' 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 ERA25LA306Accident · No injuriesClass 4 · LimitedFinal reportCessna 172 · Baltimore, MDThe pilot’s inadequate landing flare at night, which resulted in a hard landing.NTSB ERA20CA141Accident · No injuriesData collectionFinal reportCessna 172 · Ocean City, MDThe pilot's failure to maintain directional control during an attempted go-around to avoid birds, which resulted in a runway excursion and subsequent nose-over.NTSB ERA18LA094Accident · 2 fatalLimited investigationFinal reportCessna 172 · Ocean City, MDThe pilot's flight in dark night visual meteorological conditions, which resulted in an impact with water for reasons that could not be determined based on the available information.NTSB GAA16CA343Accident · No injuriesData collectionFinal reportCessna 172 · Frederick, MDThe student pilot's failure to maintain pitch control during the touch down resulting in a bounced landing, subsequent hard landing and substantial damage to the firewall.NTSB GAA16CA158Accident · No injuriesData collectionFinal reportCessna 172 · Frederick, MDThe student pilot's improper pitch control during the landing flare, which resulted in a hard bounced landing.NTSB ERA12CA439Accident · No injuriesData collectionFinal reportCessna 172S · Frederick, MDThe pilot's inadequate landing flare, which resulted in a hard landing.NTSB ERA11CA516Accident · No injuriesData collectionFinal reportCessna 172S · Westminster, MDThe pilot's inadequate recovery from a bounced landing, which resulted in a loss of airplane control. Contributing to the accident was the pilot's improper approach airspeed for a short-field landing.NTSB ERA10CA468Accident · No injuriesData collectionFinal reportCessna 172S · Frederick, MDUndetermined.NTSB ERA09CA041Accident · Serious injuriesData collectionFinal reportCessna 172 · Frederick, MDThe passenger’s failure to avoid the rotating propeller after exiting the airplane. Contributing to the accident was the pilot’s failure to include deplaning procedures as part of the passenger safety briefing.NTSB MIA08CA068Accident · No injuriesData collectionFinal reportCessna 172S · Westiminster, MDThe student pilot's improper flare.NTSB NYC06CA232Accident · No injuriesData collectionFinal reportCessna 172S · Cambridge, MDThe pilot's failure to maintain directional control while landing.NTSB IAD05LA043Accident · No injuriesLimited investigationFinal reportCessna 172N · Frederick, MDThe inadequate visual lookout of the pilots in each airplane, which resulted in a ground collision.NTSB NYC04CA164Accident · No injuriesData collectionFinal reportCessna 172S · Stevensville, MDThe pilot's improper flare during touch down, which resulted in a hard landing.NTSB IAD04CA009Accident · No injuriesData collectionFinal reportCessna 172R · Fredrick, MDThe student pilot's failure to maintain directional control during the landing. A factor was the snow bank.