GAA17CA412 · Mooney M20C
Badger Flyers Mooney M20C · Accident: collision during takeoff/landing on approach
From an unrecorded airport to Washington Island Airport (2P2)
Event
- NTSB case
- GAA17CA412
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Mooney M20C
- Aircraft type
- Mooney M20
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N9303V
- Operator
- Badger Flyers
- Onboard fatalities
- Unknown
- Route
- From not recordedTo Washington Island Airport (2P2), Washington Island, WI
- Aircraft age
- About 48 years (built 1969)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Approach · VFR pattern final
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Collision during takeoff/landing
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
During the final approach for landing, the airplane was too low and struck trees short of the runway threshold, spun about 180°, and then impacted the ground.
The airplane sustained substantial damage to the left wing and fuselage.
The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.
The pilot did not submit the National Transportation Safety Board Form 6120.1 Pilot/Operator Aircraft Accident/Incident Report.
Probable cause
The pilot's failure to maintain a proper approach path, which resulted in impact with trees.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA17CA412
- Event ID
- 20170717X54242
- Case number
- GAA17CA412
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 8f709dcadef2757b61edb0d5ea5a8a1fa933c473146b4f0ed0077191418a38a9; retrieved 2026-09-16T05:32:59.759Z.