NTSB investigations: Lycoming AEIO-360 series, AZ
9 cases on aircraft whose registry engine model is Lycoming AEIO-360 series. 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
| 1978 | 1 |
|---|---|
| 1984 | 1 |
| 1985 | 1 |
| 1987 | 1 |
| 1990 | 1 |
| 1993 | 1 |
| 1995 | 1 |
| 2010 | 1 |
| 2018 | 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 ('41522', '41601'))
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 ('41522', '41601'))
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 WPR18FA229Accident · 2 fatalField investigationFinal reportJames E Causey Acroduster II · Phoenix, AZAn exceedance of the airplane's critical angle of attack while maneuvering for landing, which resulted in an aerodynamic stall/spin at an altitude too low for recovery.NTSB WPR10CA282Accident · No injuriesData collectionFinal reportGreat Lakes 2T-1A-2 · Chandler, AZThe pilot’s failure to maintain directional control and the flight instructor's inadequate remedial action during the landing roll, which resulted in a ground loop.NTSB LAX96LA023Accident · No injuriesLimited investigationFinal reportGreat Lakes 2T-1A-2 · Chandler, AZthe improper installation of an intake manifold tube assembly during engine overhaul which permitted leakage into the induction system resulting in detonation and piston failure in the associated cylinder.NTSB LAX94LA057Accident · Minor injuriesLimited investigationFinal reportBellanca 8KCAB · Buckeye, AZA loss of engine power due to fuel system contamination. A factor in the accident was the soft terrain in the landing area.NTSB LAX90DUJ06Accident · 2 fatalFinal reportChristen/Walter Christen Eagle II · Marana, AZThe loss of control by the pilot.NTSB LAX87LA211Accident · No injuriesLimited investigationFinal reportGreat Lakes 2T-1A-2 · Tucson, AZA Great Lakes 2T-1A-2 nosed over during landing. The pilot indicated that he had contacted the airport on the UNICOM frequency and was informed that the winds were favoring runway 30. On short final approach to runway 30 the pilot glanced a wind sock located…NTSB LAX86LA034Accident · No injuriesLimited investigationFinal reportAerotek Pitts S-2A · Chandler, AZDuring a dual instructional flight the CFI stated that he was looking for traffic while monitoring his student's performance. The CFI failed to observe that an acft was ahead of him in the traffic pattern. That acft was at a lower altitude & was on short…NTSB LAX84LA450Accident · No injuriesLimited investigationFinal reportBastian Pitts S1S · Tucson, AZThe plt stated after the accident that he was flying inverted when he experienced an engine failure. Several in flight restart attempts were unsuccessful and the pilot initiated a forced landing on a dirt road. While on final apch to the dirt road, a pick up…NTSB LAX78FUJ30Accident · No injuriesClosedPitts S-1S · Marana, AZ