NTSB investigations: Lycoming IO-360-A1B6D, IN
5 cases on aircraft whose registry engine model is Lycoming IO-360-A1B6D. 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
| 1980 | 1 |
|---|---|
| 1984 | 1 |
| 1992 | 1 |
| 1993 | 1 |
| 1998 | 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\" = 'IN' 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 ('41593'))
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" = 'IN' 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 ('41593'))
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 CHI98LA179Accident · No injuriesLimited investigationFinal reportCessna 177RG · Tocsin, INthe pilot's failure to obtain adequate airspeed during the takeoff climb and the resulting inadvertant stall. A factor in the accident was the pilot's premature raising of the flaps.NTSB CHI93LA284Accident · No injuriesLimited investigationFinal reportCessna 177RG · Columbus, INthe pilot in command's failure to maintain proper clearance. A factor involved in this accident is the pilot in command's failure to maintain a proper glidepath.NTSB CHI92LA073Accident · No injuriesLimited investigationFinal reportCessna 177RG · Indianapolis, INEngine loss of power for undetermined reasons. The lack of suitable terrain for a forced landing was a factor.NTSB CHI84LA103Accident · Minor injuriesLimited investigationFinal reportCessna 177RG · Logansport, INThe plt stated that the acft eng was running rough at rotation. He climbed to approx 300 ft AGL and began a left trafficpattern back to rwy 27. A landing was made 225 ft short of the rwy. During the post-accident eng run-up the eng started easily and ran…NTSB CHI80FEX13Accident · No injuriesClosedCessna 177RG · Greenwood, IN