NTSB investigations: Lycoming IO-360-L2A, NJ
7 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
| 2008 | 2 |
|---|---|
| 2016 | 1 |
| 2017 | 1 |
| 2019 | 1 |
| 2021 | 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\" = 'NJ' 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" = 'NJ' 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 ERA26LA003Accident · Minor injuriesClass 4 · LimitedFinal reportCessna 172 · West Milford, NJThe pilot’s failure to adequate clearance from obstacles while maneuvering during the landing approach and the instructor pilot’s delayed remedial action, which resulted in the airplane contacting a tree and terrain.NTSB ERA22FA058Accident · 2 fatalClass 3 · FieldFinal reportCessna 172 · Branchville, NJThe flight instructor’s failure to recover from a steep spiral turn during an instructional flight.NTSB GAA19CA153Accident · No injuriesData collectionFinal reportCessna 172 · Princeton, NJA collision with deer on the runway while landing at night and the airport's lack of a complete perimeter fence.NTSB GAA18CA045Accident · No injuriesData collectionFinal reportCessna 172 · Trenton, NJThe pilot’s improper landing flare, which resulted in a bounced landing.NTSB GAA16CA400Accident · No injuriesData collectionFinal reportCessna 172 · Morristown, NJThe pilot's failure to maintain a safe taxi distance from a large turbine-powered airplane, resulting in an encounter of the turbine-powered airplane's jet blast while taxiing.NTSB ERA09CA110Accident · No injuriesData collectionFinal reportCessna 172R · Morristown, NJThe flight instructor's failure to execute a missed approach when insufficient runway remained for landing. Contributing to the accident were the low ceiling and visibility conditions.NTSB OPS08IA010Incident · No injuriesIncident investigationFinal reportCessna 172 · Teterboro, NJProbable Cause The probable cause of this incident was the TEB ground controller's failure to direct N316AS to hold short of runway 24 when issuing taxi instructions to the aircraft as required FAA Order 7110.65, paragraph 3-7-2 (2a); Taxi and Ground Movement…