NTSB investigations: Lycoming IO-360-A1B6D, AZ
17 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
| 1976 | 1 |
|---|---|
| 1979 | 1 |
| 1980 | 2 |
| 1981 | 1 |
| 1982 | 1 |
| 1985 | 1 |
| 1986 | 1 |
| 1989 | 1 |
| 1991 | 1 |
| 1994 | 1 |
| 2003 | 1 |
| 2011 | 2 |
| 2020 | 1 |
| 2021 | 1 |
| 2022 | 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\" = 'AZ' 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" = 'AZ' 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 WPR23LA017Accident · Serious injuriesClass 3 · LimitedFinal reportCessna 177RG · Mesa, AZThe failure of maintenance personnel to properly secure the fuel supply line to the fuel flow divider, which resulted in a fuel leak, fuel exhaustion, and a total loss of engine power.NTSB WPR21FA340Accident · 1 fatalClass 3 · FieldFinal reportCessna 177RG · Lake Havasu City, AZA partial loss of engine power during the airplane's initial climb due to wear of internal engine components, which prevented the engine from developing full-rated power and resulted in a loss of altitude.NTSB WPR20LA144Accident · No injuriesClass 3 · LimitedFinal reportMooney M20J · Phoenix, AZA total loss of engine power due to oil starvation for reasons that could not be determined due to a lack of available evidence, which resulted in impact with terrain during a subsequent forced landing.NTSB WPR11LA287Accident · Serious injuriesLimited investigationFinal reportCessna 177RG · St Johns, AZThe pilot did not attain and maintain an adequate airspeed during the takeoff initial climb, which resulted in an aerodynamic stall.NTSB WPR11FA186Accident · No injuriesField investigationFinal reportCessna 177RG · Gila Bend, AZA total loss of engine power during cruise flight due to both sets of magneto points failing to open as a result of excessive wear of the magneto cam followers.NTSB LAX04FA042Accident · 1 fatalField investigationFinal reportCessna 177RG · Blk Canyon City, AZa loss of engine power due to the failure of the single-drive dual magneto that resulted from inadequate lubrication of the breaker cam. Also causal was the improper maintenance by other maintenance personnel during a recent inspection, which should have…NTSB LAX94LA179Accident · No injuriesLimited investigationFinal reportCessna 177RG · Sedona, AZthe pilot's inadequate compensation of the existing wind conditions, and failure to maintain directional control of the aircraft.NTSB LAX91LA335Accident · Minor injuriesLimited investigationFinal reportCessna 177 · Scottsdale, AZFailure of the pilot-in-command accurately performing inflight fuel consumption calculations resulting in a loss of engine power due to fuel exhaustion. Contributing to the accident was the pilot-in-command's poorly planned approached which terminated in a…NTSB LAX89LA323Accident · No injuriesLimited investigationFinal reportCessna 177RG · Tucson, AZA loss of engine power due to the pilot's improper use of the aircraft's powerplant controls. A contributing factor was the pilot's limited experience in a Cessna 177RG.NTSB LAX87FA014Accident · 2 fatalField investigationFinal reportCessna 177RG · Happy Jack, AZThe non-instrument rated private plt was informed that MVFR weather conditions existed along his planned route of flight. The plt took off & headed into the deteriorating wx. While cruising beneath clouds the acft collided with rapidly rising terrain. The plt…NTSB LAX85LA207Accident · No injuriesLimited investigationFinal reportCessna 177 · Chinle, AZThe aircraft landed on runway 17. The winds were form 220 degrees gusting to 30-35 knot. The pilot stated that, as he came by a quonset hangar, the aircraft was struck by a gust of wind from the right front quarter. The aircraft weather-vaned into the wind…NTSB LAX83FUJ03Accident · No injuriesFinal reportCessna 177RG · Bullhead City, AZLanding gear collapsed during landing. Several attempts both normal and emergency to extend gear failed. The rod end bearing (Cessna part # S-2049-6FG) had failed. This prevented gear extension. Service letter 79-37 recommending installing a new high strength…NTSB LAX81FA036Accident · 2 fatalClosedCessna 177RG · Flagstaff, AZNTSB LAX80DUK03Accident · No injuriesClosedCessna I77RG · Kingman, AZNTSB LAX80DUJ59Accident · No injuriesClosedCessna 177RG · Congress, AZNTSB LAX80DUJ02Accident · No injuriesClosedCessna 177RG · Vicksburg, AZNTSB LAX77DUJ18|LAX77DUG18Accident · No injuriesClosedCessna 182 · Phoenix, AZ