NTSB investigations: Maule MX-7-180
15 cases on aircraft the registry lists as Maule MX-7-180. 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
| 1987 | 1 |
|---|---|
| 1988 | 1 |
| 1989 | 2 |
| 1992 | 3 |
| 1993 | 1 |
| 1996 | 1 |
| 1997 | 1 |
| 2000 | 1 |
| 2005 | 1 |
| 2010 | 1 |
| 2015 | 1 |
| 2023 | 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.aircraft_model_code IN ('5470205', '5460185'))
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.aircraft_model_code IN ('5470205', '5460185'))
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 WPR23LA254Accident · Minor injuriesClass 4 · LimitedFinal reportMaule MX7-180C · Belgrade, MTThe pilot’s failure to maintain directional control during landing with a quartering tailwind, which resulted in a runway excursion and nose over.NTSB CEN15CA134Accident · No injuriesData collectionFinal reportMaule MX 7-180 · Georgetown, TXThe pilot did not maintain control of the airplane while landing in gusting crosswind conditions.NTSB WPR10CA455Accident · No injuriesData collectionFinal reportMaule MX7 · Willows, CAThe pilot's inadequate compensation for the gusty crosswind condition and his failure to maintain directional control.NTSB ANC05CA109Accident · No injuriesData collectionFinal reportMaule MX7-180 · Yakutat, AKThe pilot's selection of unsuitable terrain for landing, and his failure to maintain directional control of the airplane during the landing roll, which resulted in a nose-over. A factor contributing to the accident was soft terrain.NTSB NYC00LA179Accident · No injuriesLimited investigationFinal reportMaule MX-7-180 · Woodbine, NJThe pilot-in-command's failure to initiate a timely go-around.NTSB CHI97LA107Accident · Minor injuriesLimited investigationFinal reportMaule MX-7-180 · Lakeville, MNthe pilot's inadequate compensation for the crosswind.NTSB SEA96LA142Accident · No injuriesLimited investigationFinal reportMaule MX-7-180 · Newport, ORthe passenger's inadvertent activation of the aircraft's rudder, which resulted in a loss of directional control and collision with a tree during an attempted go-around (aborted landing).NTSB FTW93LA199Accident · Serious injuriesLimited investigationFinal reportMaule MX-7-180 · Eufaula, OKThe pilots improper compensation for the wind conditions. A factor was the crosswindNTSB LAX93LA082Accident · No injuriesLimited investigationFinal reportMaule MX-7-180 · Oceano, CAThe pilot's operation of the aircraft with known deficiencies in the brake system.NTSB LAX92LA317Accident · No injuriesLimited investigationFinal reportMaule MX-7-180 · Lovelock, NVThe failure of the pilot to maintain directional control of the aircraft. A factor in the accident was the presence of dust devils in the vicinity of the airport.NTSB MIA92LA147Accident · Minor injuriesLimited investigationFinal reportMaule MX-7-180 · Okeechobee, FLThe failure of the pilot-in-command of N148DP to obtain NOTAM information concerning military routes along his route of flight, resulting in his encounter with a flight of F16 aircraft who were operating on a military route.NTSB MKC89GA147Accident · 2 fatalFinal reportMaule MX-7 · Atlantic, IAFailure of the pilot to maintain adequate airspeed, while maneuvering at low altitude, which led to an inadvertent stall and loss of control. A contributing factor was the lack of altitude to recover from a stall.NTSB ATL89LA134Accident · No injuriesLimited investigationFinal reportMaule MX-7-180 · Millersburg, OHThe pilots failure to compensate for the gusty wind conditions during landing.NTSB BFO88LA020Accident · No injuriesLimited investigationFinal reportMaule MX7-180 · Lewisburg, WVThe plt started landing flare on rwy 22 when he encountered wind gusts. The acft swung right and the left wing struck the rwy. The acft cartwheeled and came to a stop inverted.NTSB ATL87LA128Accident · No injuriesLimited investigationFinal reportMaule MX-7-180 · Greenville, SCThe pilot was doing touch and go's to become familiar with his new aircraft. On the fifth landing the aircraft started a groundloop and he recovered by adding full power. On the next landing the aircraft again started a groundloop to the right, he added full…