NTSB investigations: Lycoming IO-360-A1B6D
12 cases on aircraft whose registry engine model is Lycoming IO-360-A1B6D, where the first occurrence was “Loss of engine power”. 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 | 1 |
|---|---|
| 1983 | 1 |
| 1987 | 2 |
| 1988 | 1 |
| 1992 | 2 |
| 1997 | 1 |
| 2000 | 1 |
| 2001 | 1 |
| 2002 | 1 |
| 2007 | 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\" = 350))
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" = 350))
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 ANC07LA063Accident · No injuriesLimited investigationFinal reportCessna 177RG · Pedricktown, NJThe first pilot's inadequate preflight inspection, and water contamination of the airplane's fuel system. A factor contributing to the accident was rough/uneven terrain.NTSB FTW03LA026Accident · Minor injuriesLimited investigationFinal reportCessna 177RG · Marshall, ARThe loss of engine power for undetermined reasons. A contributing factor was the lack of suitable terrain for the forced landing.NTSB CHI01LA283Accident · No injuriesLimited investigationFinal reportCessna 177RG · Sikeston, MOThe loss of engine power during the initial climb due to fuel contamination, water. A factor relating to the accident was the trees.NTSB LAX01LA062Accident · No injuriesLimited investigationFinal reportCessna 177RG · San Carlos, CAA loss of engine power for undetermined reasons during an extended downwind leg in the landing pattern.NTSB FTW98LA053Accident · Minor injuriesLimited investigationFinal reportCessna 177RG · Tomball, TXThe total loss of engine power resulting from the loss of oil and resultant seizure of a cylinder due to inadequate maintenance by maintenance personnel. A factor was the lack of suitable terrain for the forced landing and the low ceiling.NTSB SEA92LA068Accident · Minor injuriesLimited investigationFinal reportCessna 177RG · Scappoose, ORThe loss of engine power, cause undetermined. A factor relating to the accident was the lack of suitable terrain for a forced landing.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 BFO88FA054Accident · Serious injuriesField investigationFinal reportCessna 177RG · Clinton, MDEng pwr loss occurred when the instrument student advanced the throttle to do a go-around when the acft was too high to lnd on rwy 5 following a simulated instrmt apch. The instr took control of the acft and about half-way down the rwy, at about 300 ft AGL,…NTSB NYC87LA181Accident · No injuriesLimited investigationFinal reportCessna 177RG · Batavia, NYThe flt made an emgy lndg in a corn field after experiencing a loss of eng pwr. During lndg roll the acft collided with a fence. Examination of the propeller revealed that the low pitch stop was broken and had separated from the piston causing the blades to…NTSB LAX87FA093Accident · 4 fatalField investigationFinal reportCessna 177RG · S Lake Tahoe, CAAfter departing at night from south lake Tahoe, CA, the plt contacted ARTCC & requested radar flt following. A short time later, he declared an emergency & said he was reversing course with a loss of eng power. Radar & radio contact with the acft were lost as…NTSB ATL83FA313Accident · Serious injuriesField investigationFinal reportCessna 177RGII · Atlanta, GAJust before rotation & during climbout from rwy 26L the eng started surging. The acft made a left turn, into the wind, & the student plt attempted to land on rwy 8R. The acft became misaligned, overshot the rwy, & made a hard landing in the grass about 200 ft…NTSB MIA83LA028Accident · No injuriesLimited investigationFinal reportCessna 177RG · Pensacola, FLAccording to the pilot, shortly after liftoff the engine lost power and he aborted the takeoff. The aircraft overran the end of the runway and collided with uneven terrain.