WPR26LA055 · Maule M-5-210C
Maule M-5-210C · Accident: loss of control in flight during landing
From Ferndale Airfield (53U) to Eureka Airport (88M)
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- WPR26LA055
- 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
- Event fatalities
- Unknown
- 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 M-5-210C
- Aircraft type
- Maule M-5
- 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
- N339X
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route Possible conflict
- From Ferndale Airfield (53U), Big Fork, MTTo Eureka Airport (88M), Eureka, MT
- Aircraft age
- About 50 years (built 1975)
- 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
- 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 › Experience/knowledge
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that upon landing in the tailwheel-equipped airplane, it encountered a crosswind. The right wing lifted, and the left wing dropped and struck the runway, contacting the asphalt surface. The pilot reported that he did not apply appropriate crosswind control inputs during landing. The airplane subsequently ground looped and exited the runway, resulting in substantial damage to the left wing and aileron. The pilot reported no pre-accident mechanical failures or malfunctions that would have precluded normal operation. At the time of the accident, the pilot was landing on runway 19 with light and variable wind at 5 knots. The pilot added that the accident flight was his first flight in about 7 years, but could not remember exactly when his last flight was.
Probable cause
The pilot’s failure to maintain directional control during landing in crosswind conditions. Contributing to the accident was the pilot's lack of recent flight experience.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR26LA055
- Event ID
- 20251211202143
- Case number
- WPR26LA055
- 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, cause areas. 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: b6876c7432b0fa37e49b987f31d9aa4e2cc0b9a32ee1d9191f716c2aae083d36; retrieved 2026-09-16T20:36:05.259Z.