Lycoming IO-540-AB1A5
NTSB investigations · 27
Matched to the registry by N-number and event date, newest first.
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_aircrafts.parquet' a JOIN 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c ON c.\"mKey\" = a.case_mkey
WHERE a.engine_model_code IN ('41808')
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_aircrafts.parquet' a JOIN 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c ON c."mKey" = a.case_mkey
WHERE a.engine_model_code IN ('41808')
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 ERA26LA278Accident · No injuriesClass 4 · LimitedFinal reportTextron 182T · Fredericksburg, VAThe pilot’s distraction during taxi, which resulted in a taxiway excursion.NTSB ANC26FA039Accident · 2 fatalClass 3 · FieldPreliminary reportCessna 182T · Armistead, CAOn May 7, 2026, about 1055 pacific daylight time (PDT), a Cessna 182T airplane, N227TF, was destroyed when it was involved in an accident near Armistead, California. The flight instructor and the pilot receiving instruction were fatally injured. The airplane…NTSB CEN26LA213Accident · No injuriesClass 3 · LimitedPreliminary reportTextron 182T · Newberry, MIOn January 22, 2026, about 18:40 eastern standard time, a Cessna 182T, N116D was substantially damaged when it was involved in an accident near Newberry, Michigan. The pilot was not injured. The airplane was operated under the provisions of Title 14 Code of…NTSB GAA26WA014Accident · 1 fatalClass 5 · ForeignTextron 182T · Nuuk, GreenlandNTSB CEN25FA047Accident · 2 fatalClass 3 · FieldFinal reportCessna 182T · Drake, COThe pilot’s failure to maintain airplane control while maneuvering in mountainous terrain. Contributing was mountain wave turbulence in the area.NTSB WPR21FA048Accident · 1 fatalClass 3 · FieldFinal reportCessna 182 · Los Angeles, CAMaintenance personnel’s failure to properly secure the throttle control hardware during recent maintenance, which resulted in its disconnection and a subsequent loss of engine power on approach for landing.NTSB CEN20FA075Accident · 3 fatalClass 3 · FieldFinal reportCessna 182 · Chatham, LAThe pilot’s encounter with icing in-flight, which resulted in a loss of control and impact with terrain.NTSB GAA19CA129Accident · No injuriesData collectionFinal reportCessna 182 · Marshall, TXThe pilot's failure to maintain directional control during landing.NTSB ERA18LA191Accident · Serious injuriesLimited investigationFinal reportCessna 182 · Geneseo, NYThe pilot's failure to properly set the elevator trim before takeoff, which resulted in an exceedance of the airplane's critical angle of attack during takeoff and a subsequent aerodynamic stall. Contributing to the accident was the pilot’s failure to follow…NTSB GAA18CA364Accident · No injuriesData collectionFinal reportCessna 182T · Sebring, FLThe pilot’s failure to maintain directional control during landing with a crosswind.NTSB GAA17CA492Accident · Minor injuriesData collectionFinal reportCessna 182 · Quitman, MSThe student pilot’s failure to maintain directional control during takeoff in gusting wind conditions after passing a large hill.NTSB GAA17CA048Accident · No injuriesData collectionFinal reportCessna 182 · Palo Alto, CAThe pilot's failure to perform a go-around when he recognized that the airplane was high and fast during the final approach, which resulted in an improper landing flare and a hard landing.NTSB CEN16FA373Accident · 2 fatalField investigationFinal reportCessna 182 · Ephraim, WIThe pilot's improper decision to execute a maneuvering approach at low altitude during night conditions, which resulted in controlled flight into terrain.NTSB GAA16CA484Accident · No injuriesData collectionFinal reportCessna 182 · Olathe, KSThe pilot’s failure to reduce the throttle during the landing roll resulting in a loss of directional control.NTSB ERA16FA100Accident · 2 fatalField investigationFinal reportCessna 182 · Mobile, ALThe pilot's loss of airplane control during a missed approach in instrument meteorological conditions due to spatial disorientation. Contributing to the accident was the pilot's inadequate preflight and inflight weather planning which resulted the pilot's…NTSB ERA14LA072Accident · No injuriesLimited investigationFinal reportCessna 182T · Burlington, NCA loss of airplane control during takeoff for reasons that could not be determined due to the postaccident condition of the elevator control system.NTSB WPR13LA286Accident · No injuriesLimited investigationFinal reportCessna 182T · San Diego, CABoth pilots’ failure to maintain a proper visual lookout while taxiing during nighttime conditions, which resulted in an on-ground collision.NTSB CEN13FA269Accident · 2 fatalField investigationFinal reportCessna 182T · Fredericksburg, TXThe pilot’s failure to maintain airspeed while transitioning from instrument to visual flight while still in instrument conditions, which resulted in an inadvertent stall.NTSB CEN13LA258Accident · No injuriesLimited investigationFinal reportCessna 182T · Delta, COThe loss of propeller control for reasons that could not be determined because postaccident examinations revealed no anomalies that would have precluded normal operation and the airplane’s subsequent collision with power lines during the forced landing.NTSB ERA11CA270Accident · No injuriesData collectionFinal reportCessna 182T · East Hampton, NYThe pilot's failure to maintain directional control while landing with a crosswind, which resulted in a runway excursion.NTSB ERA10CA253Accident · No injuriesData collectionFinal reportCessna 182T · Parkersburg, WVThe pilot's loss of aircraft control while landing with a gusting wind.NTSB WPR09CA469Accident · No injuriesData collectionFinal reportCessna 182 · Parowan, UTThe pilot's improper flare and recovery from a bounced landing.NTSB CEN09LA247Accident · Serious injuriesLimited investigationFinal reportCessna 182T · Stigler, OKThe loss of directional control during takeoff. Contributing to the accident was the pilot's decision to take off with 40-degrees of flaps and with a tailwind.NTSB ERA09CA017Accident · No injuriesData collectionFinal reportCessna 182T · Manchester, CTThe in-flight collision with a bird.NTSB DEN07CA128Accident · No injuriesData collectionFinal reportCessna 182T · Grand Junction, COThe pilot's failure to maintain aircraft control during the landing.NTSB FTW03FA114Accident · 1 fatalField investigationFinal reportCessna 182S · Fayetteville, ARThe pilot's failure to fly a stabilized, published instrument approach procedure, which resulted in a collision with trees and terrain. Factors were the low clouds and night conditions.NTSB CHI00LA304Accident · No injuriesLimited investigationFinal reportCessna 182S · Wichita, KSthe pilot's failure to maintain aircraft control during the landing. Factors relating to this accident were the pilot's improper recovery from the bounced landing and his failure to go-around.
Back to Lycoming IO-540-AB1A5