NTSB investigations: Lycoming IO-360-A1B6D
15 cases on aircraft whose registry engine model is Lycoming IO-360-A1B6D, where the first occurrence was “In flight collision with terrain/water”. 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
| 1982 | 2 |
|---|---|
| 1983 | 2 |
| 1986 | 3 |
| 1988 | 1 |
| 1989 | 1 |
| 1991 | 1 |
| 1993 | 1 |
| 1999 | 1 |
| 2001 | 1 |
| 2003 | 1 |
| 2005 | 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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41593')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 230))
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."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41593')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o."occurrenceNumber" = 1 AND o."occurrenceCode" = 230))
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 SEA05FA169Accident · 3 fatalField investigationFinal reportCessna 177RG · Cascade, IDThe pilot's failure to maintain clearance from a stand of conifer trees during low altitude maneuvering in mountainous terrain. Factors include the mountainous/hilly terrain, gusty winds, a high density altitude, and maneuvering at a low altitude.NTSB LAX03FA161Accident · 2 fatalField investigationFinal reportCessna 177RG · Ely, NVthe airplane collided with terrain for undetermined reasons.NTSB LAX01LA193Accident · Minor injuriesLimited investigationFinal reportCessna 177RG · Pauma Valley, CAThe pilot's intentional flight into instrument meteorological conditions and failure to maintain clearance from terrain during an approach for landing under visual flight rules.NTSB LAX99LA243Accident · Minor injuriesLimited investigationFinal reportCessna 177RG · Quincy, CAthe pilot's failure to attain and maintain an adequate airspeed for the existing wind conditions, and, his failure to abort the takeoff when it became apparent that the aircraft performance was not as anticipated. Factors in the accident were the tailwind and…NTSB LAX94FA004Accident · 4 fatalField investigationFinal reportCessna 177RG · Petaluma, CAVFR flight by the pilot(s) into instrument meteorological conditions (IMC), and failure to maintain a proper altitude and/or clearance from terrain, while approaching the destination airport. Factors related to the accident were: the low ceiling and terrain.NTSB SEA91FA183Accident · 4 fatalField investigationFinal reportCessna 177RG · Salmon, IDImproper inflight planning and decision by the pilot, and his failure to maintain sufficient altitude and clearance from mountainous/hilly terrain.NTSB SEA89FA180Accident · 2 fatalField investigationFinal reportCessna 177RG · Nyssa, ORFailure of the pilot to attain sufficient altitude before flying over mountainous/hilly terrain. Factors related to the accident were: dark night, rising/mountainous terrain, and probable impairment from a prescription drug.NTSB LAX88FA314Accident · 1 fatalField investigationFinal reportCessna 177RG · San Luis Obispo, CAPilots erroneous interpretation of his missed approach clearance, and, his performance of the published missed approach procedure for the santa maria ILS instead of the San Luis Obispo localizer.NTSB ANC86FA130Accident · 3 fatalField investigationFinal reportCessna 177RG · Hinchinbrook Is, AKAt 1323 adt, the plt rprtd near Hinchinbrook island & requested clearance for an ndb-a apch to the cordova mile 13 arpt. About 3 min later, cordova fss provided clearance for the apch 'from over Hinchinbrook.' Radar data showed that the acft flew to the…NTSB LAX86FVM07Accident · No injuriesFinal reportCessna 177RG · San Jose, CAThe acft was landed with the gear in the partially extended. Tower personnel attempted to warn the plt of the gear position with use of the radio and light gun signals; however, the landing was continued. Post accident examination of the landing gear system…NTSB NYC86LA064Accident · Minor injuriesLimited investigationFinal reportCessna 177RG · Farmingdale, NYThe acft collided with trees in the bethpage state park during a rwy 14 ILS apch at republic airport, Farmingdale, NY. The plt had instructed his passenger, a private plt, to report when he had the apch lights in sight. The plt stated the apch was continued…NTSB ANC83FA133Accident · No injuriesField investigationFinal reportCessna 177RG · Anchorage, AKDuring arrival, the acft was landed with the gear retracted. After touchdown, it slid appx 980 ft before coming to rest. The pilot stated that after he was cleared to land, he was looking for other VFR traffic & forgot to extend the gear. Reportedly, he did…NTSB ANC83IA045Incident · No injuriesIncident investigationFinal reportCessna 177RG · Anchorage, AKThe acft was intentionally landed gear up due to a failure of the main landing gear actuator bearing. The bearing failed due to fatigue.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 MIA82DA086Accident · No injuriesFinal reportCessna 177RG · Jacksonville, FLThe pilot stated that he became distracted by radio communications with the control tower and forgot to lower the landing gear prior to landing.