OpenAirDocs.org

NTSB investigations: Mooney M20F

7 cases on aircraft the registry lists as Mooney M20F, where the first occurrence was “In flight collision with object”. 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

19822026

Where

Open the map

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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('5870214')
      AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 220))
  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.

NTSB IAD00FA079Accident · 1 fatalField investigationFinal reportMooney M20F · Jonestown, PAThe pilot's delay in aborting the landing, which resulted in a collision with transmission wires. Factors in the accident were the pilot's improper inflight decision to attempt a landing with a 14-knot tailwind, and his use of an unapproved pain medication.Aug 29, 2000 · N9436V · DestroyedNTSB NYC00LA115Accident · No injuriesLimited investigationFinal reportMooney M-20F · Parker, PAThe pilot's failure to maintain an adequate visual lookout, due to his distraction with a flock of birds. A factor was the pilot's improper in flight decision to continue the simulated engine failure to too low of an altitude.Apr 1, 2000 · N737HB · Substantial damageNTSB SEA98FA062Accident · 1 fatalField investigationFinal reportMooney M20F · Lodgepole, MTThe pilot's failure to maintain clearance from the terrain after flying into an area of known adverse weather. Factors include low ceilings, fog, snow showers, drizzle, and trees along his intended route.Apr 6, 1998 · N9131V · DestroyedNTSB IAD97LA031Accident · 2 fatalLimited investigationFinal reportMooney M20F · Wellsville, NYDescent below the published minimum descent altitude followed by collision with the surrounding terrain.Dec 11, 1996 · N3424N · DestroyedNTSB ATL88LA090Accident · Minor injuriesLimited investigationFinal reportMooney M20F · Birmingham, ALThe airplane collided with trees on a hill at night, while on final approach. The plt rptd that he 'evidently got too low' on the approach. The visibility was 10 miles. The hilly terrain in the vicinity of the accident site was undeveloped, and had no…Feb 15, 1988 · N7448V · Substantial damageNTSB SEA87LA096Accident · No injuriesLimited investigationFinal reportMooney M20F · Wagontire, ORDuring takeoff with full flaps and a density altitude of about 6,200 feet the aircraft failed to gain flying speed. Shortly after becoming airborne the aircrafts gear caught on a barbed wire fence at the departure end of the runway. The aircraft then struck…May 17, 1987 · N3523X · Substantial damageNTSB MIA82DA162Accident · No injuriesFinal reportMooney M20F · Orlando, FLThe pilot reported that rain had occurred on the previous night and there was water on the 2430 ft grass runway. He reported that during rotation, the aircraft hit the water and lost airspeed. Subsequently, the aircraft failed to gain sufficient altitude to…Aug 1, 1982 · N9109V · Substantial damage