GAA17CA170 · Maule M5 180C
Maule M5 180C · Accident: loss of control in flight during landing
From Camdenton Memorial Airport (OZS) to Roxbury, KS
Event
- NTSB case
- GAA17CA170
- 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
Maule M5 180C
- Aircraft type
- Maule M5
- 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
- N56552
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Camdenton Memorial Airport (OZS), Camdenton, MOTo Roxbury, KS
- Aircraft age
- About 33 years (built 1984)
- 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
- Landing
- 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
- Loss of control in flight
- 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
- Tower/antenna (incl guy wires)
- 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
The pilot of the tailwheel-equipped airplane reported that, while landing on a road in gusting crosswind conditions, the right wing lifted to about a 60° angle. He immediately initiated a go-around and added full power and right aileron and lowered the nose. The airplane had drifted off the center of the road to the left heading toward power lines, and the pilot chose to go under them. After the airplane cleared the power lines, the left wing tip struck the ground, and the airplane cart-wheeled. The airplane sustained substantial damage to both wings, the fuselage, and the empennage.
The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation.
Probable cause
The pilot’s failure to maintain directional control during a go-around.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA17CA170
- Event ID
- 20170306X21055
- Case number
- GAA17CA170
- 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: f73492c1888a9d436e7b3d17e1af1c5850b2f9481dfab741e8c7dfacee1318f6; retrieved 2026-09-16T05:04:08.136Z.