NTSB investigations: Lycoming IO-360-A1B6D, KY
6 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
| 1973 | 1 |
|---|---|
| 1984 | 1 |
| 1986 | 1 |
| 1988 | 1 |
| 2005 | 1 |
| 2010 | 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\" = 'KY' 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" = 'KY' 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 ERA11CA047Accident · No injuriesData collectionFinal reportCessna 177RG · Bedford, KYThe mechanic's failure to properly secure a fuel line when it was reinstalled during an engine inspection.NTSB IAD05LA136Accident · Serious injuriesLimited investigationFinal reportCessna 177RG · Cadiz, KYThe pilot's inadequate in-flight decision, which resulted in fuel exhaustion and subsequent loss of engine power. A factor was the pilot's early flare during the emergency landing.NTSB ATL88LA244Accident · Minor injuriesLimited investigationFinal reportCessna 177RG · Berkeley, KYThe plt reported that he departed with 6 hrs of fuel on board. He encountered low ceilings while en route, and flew at 3-500 ft AGL to maintain VFR. About 3 hrs & 15 minutes after departure, the engine sputtered and lost power. The plt made a forced ldg in…NTSB ATL86FA049Accident · 1 fatalField investigationFinal reportCessna 177RG · Hazard, KYThe plt called the arpt on UNICOM and asked how to find the arpt, stated that he needed fuel and asked if fuel was available. He was given directions and asked if he had landed there before. He replied no, and inquired about the traffic pattern. It was…NTSB ATL85FLT02Accident · Minor injuriesFinal reportCessna 177RG · White Mills, KYThe plt made a gear-up forced landing after experiencing a total loss of power during cruise flt. Post accident inspection of the aircraft revealed less than 12 ounces of fuel on board. Plt stated he did not visually check the fuel quantity on the day of the…NTSB CHI73ALQ20Accident · No injuriesClosedCessna 177RG · Lexington, KY