WPR09CA311 · Maule M-5-235C
Maule M-5-235C · Accident: hard landing
From McCall Municipal Airport (MYL) to Elk Ridge Airport (ID76)
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
- WPR09CA311
- 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 M-5-235C
- 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
- N725V
- Operator
- James G Kusian · private individual
- Onboard fatalities
- Unknown
- Route Possible conflict
- From McCall Municipal Airport (MYL), McCall, IDTo Elk Ridge Airport (ID76), Dixie, ID
- Aircraft age
- Not recorded
- 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 · flare/touchdown
- 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
- Hard landing
- 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 and his passenger had been traveling across the country visiting backcountry airstrips. They had spent two nights at a backcountry airstrip and decided to go on a day flight to one of the other airstrips in the area that was 1,500 feet in length by 50 feet wide. After surveying the landing area, the pilot stated that, as he neared the approach end of the runway, he was approximately 20 feet above ground level when the airplane dropped straight down. The pilot indicated that his airspeed was slow and that he most likely encountered a downdraft. This resulted in the airplane landing hard on the runway surface, and the airplane porpoised prior to impacting rising terrain and trees. There were no mechanical malfunctions reported.
Probable cause
The pilot's failure to maintain an adequate airspeed while landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR09CA311
- Event ID
- 20090625X51425
- Case number
- WPR09CA311
- 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: 2112b4fa2a4289eb47fe6c1a65a8dffa96f10f99425190327a375d1804befff3; retrieved 2026-09-15T11:35:46.392Z.