Final NTSB investigations: Lycoming IO-540-V4A5D
9 cases on aircraft whose registry engine model is Lycoming IO-540-V4A5D. 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
| 1980 | 1 |
|---|---|
| 1984 | 1 |
| 2010 | 1 |
| 2014 | 1 |
| 2015 | 1 |
| 2018 | 1 |
| 2020 | 1 |
| 2025 | 1 |
| 2026 | 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.\"completionStatus\" = 'Completed'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41807'))
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."completionStatus" = 'Completed'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41807'))
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 ERA26LA184Accident · Minor injuriesClass 4 · LimitedFinal reportMaule M-7-260C · Tampa, FLThe pilot’s failure to maintain directional control of the airplane during the aborted landing, which resulted in a runway excursion, collision with a runway sign, and nose over.NTSB ERA26LA002Accident · No injuriesClass 4 · LimitedFinal reportMaule M-7-260 · Parkland, FLThe pilot’s failure to retract the amphibious airplane’s landing gear before conducting a forced landing on the water, which resulted in a nose over.NTSB WPR20CA198Accident · No injuriesClass 4 · Data collectionFinal reportMaule M7 · Yellow Pine, IDThe pilot's improper approach airspeed and landing flare, which resulted in a bounced landing, and subsequent nose over.NTSB GAA18CA569Accident · No injuriesData collectionFinal reportMaule M7 · Grass Valley, ORThe pilot’s failure to maintain directional control during the landing roll.NTSB GAA16CA015Accident · No injuriesData collectionFinal reportMaule M 7-260C · Grace, IDThe pilot's selection of unsuitable terrain for landing, which resulted in a nose over.NTSB CEN14CA503Accident · No injuriesData collectionFinal reportMaule MT 7-260 · Largo Vista, TXThe pilot's inadequate compensation for gusting wind conditions during takeoff, which resulted in the nose landing gear impacting the runway and the subsequent collapse of the nose landing gear.NTSB ERA10CA393Accident · No injuriesData collectionFinal reportMaule M-7-260 · Onset, MAThe pilot's loss of airplane control during the initial climb.NTSB ANC84FA080Accident · 2 fatalField investigationFinal reportCessna 180G · Tyonek, AKTaking off from an abandoned road near a fishing camp, the Cessna turned back and descended with power on over his departure point, heading into the sun which was low on the horizon. It collided left wing to left wing with the Maule which had climbed out at a…NTSB ANC80DAG51Accident · No injuriesClosedMaule M-5 · Polly Creek, AK