NTSB investigations: Mooney M20F, VA
8 cases on aircraft the registry lists as Mooney M20F. 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
| 1979 | 1 |
|---|---|
| 1981 | 1 |
| 1986 | 1 |
| 1991 | 1 |
| 1996 | 1 |
| 1997 | 1 |
| 2009 | 1 |
| 2015 | 1 |
Where
Latest 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\" = 'VA' AND c.\"eventCountry\" = 'USA'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('5870214'))
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" = 'VA' AND c."eventCountry" = 'USA'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('5870214'))
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 ERA15FA144Accident · 3 fatalField investigationFinal reportMooney M20F · Norfolk, VAThe pilot's failure to properly execute the instrument approach procedure. Contributing to the accident were the pilot's improper preflight planning and his decision to conduct the flight in instrument meteorological conditions at night into forecast moderate…NTSB ERA09LA441Accident · Serious injuriesLimited investigationFinal reportMooney M20F · Suffolk, VAA loss of engine power due to fuel exhaustion as a result of the pilot’s failure to accurately calculate the fuel required for the flight. Contributing to the accident was a malfunction of the fuel quantity indicators.NTSB NYC98LA056Accident · Minor injuriesLimited investigationFinal reportMooney M20F · Ferncliff, VAthe improper installation of the engine oil temperature probe which resulted in oil starvation and a total loss of engine power. A factor in the accident was the pilot's overflight of available airports in an effort to reach the 'Nearest Airport' displayed on…NTSB IAD96LA109Accident · 1 fatalLimited investigationFinal reportMooney M20F · Cape Charles, VAThe pilot's improper in-flight planning/decision making by continuing flight into known adverse weather conditions. Related factors were the dark night and the winter storm (snow and fog).NTSB BFO92LA008Accident · No injuriesLimited investigationFinal reportMooney 20F · Basye, VAThe pilot misjudged the altitude and distance to the runway. Factors were the gusty weather conditions and the pilot's delay in executing a go around.NTSB BFO86FA050Accident · 1 fatalField investigationFinal reportMooney M20F · Leesburg, VADrg arrival, the plt was clrd for a VOR rwy 35 apch. Also, he was advised that there were problems with the rwy lights &that other plts had made missed apchs that evening due to dim arpt lighting. He was then clrd to UNICOM freq & told to cancel his IFR clnc…NTSB MIA82FA015Accident · 2 fatalClosedMooney M20F · Richmond, VANTSB IAD79FA077Accident · 1 fatalClosedMooney M-20F · Troutdale, VA