ASN Wikibase Occurrence # 281291
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information.
If you feel this information is incomplete or incorrect, you can submit corrected information.
| Date: | Wednesday 20 July 2022 |
| Time: | 08:15 |
| Type: |  Maule M-5-235C |
| Owner/operator: | Private |
| Registration: | N6224M |
| MSN: | 7196C |
| Year of manufacture: | 1978 |
| Total airframe hrs: | 569 hours |
| Fatalities: | Fatalities: 0 / Occupants: 1 |
| Aircraft damage: | Substantial |
| Category: | Accident |
| Location: | Three Forks Airport (9S5), MT -
 United States of America
|
| Phase: | Landing |
| Nature: | Private |
| Departure airport: | Three Forks Airport, MT (9S5) |
| Three Forks Airport, MT (9S5) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Information verified through data from accident investigation authorities |
On July 20, 2022, about 0815 mountain daylight time, a Maule M-5-235C, N6224M, sustained substantial damage when it was involved in an accident in Three Forks, Montana. The commercial pilot was not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.
According to the pilot who holds a Federal Aviation Administration Airframe & Powerplant Mechanic certificate, the accident flight was the first flight following an engine overhaul and new avionics. He recalled that he had completed several engine ground run iterations and multiple full power, high speed test run iterations. Stemming from the test run engine data obtained by the onboard engine data monitoring system, he adjusted the idle and mixture controls. Eight engine test runs were accomplished, and the engine monitoring data identified normal operational engine parameters.
Confident in the engine performance, the pilot took off and continued with engine break-in procedures. He recalled that several flight maneuvers were accomplished with consistent normal engine parameters confirmed by the flight instruments. He decided to land, established the airplane on the right downwind leg of the airport traffic pattern, and noticed that the engine rpm was winding down slowly. Troubleshooting the anomaly to no avail, he pitched for best glide, no flaps applied, and made a right 180° turn for runway 03. However, the airplane’s sink rate was too high to land on the runway. The airplane touched down about 1,000 ft short of the runway threshold, on an unplowed pasture surface and collided with a barbed wire fence.
Sources:
NTSB
Location
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 09-Aug-2022 18:36 | Captain Adam | Added |
Corrections or additions? ... Edit this accident description
The Aviation Safety Network is an exclusive service provided by:
Quick Links:
| ASN Home | Send Correction / Feedback |
| FSF Home | Disclaimer | Copyright |
| Contact Us | Privacy Policy |
| Press / Media |
CONNECT WITH US:
©2024 Flight Safety Foundation