Maule M-5-210C N6617R accident near Verona, New York

Aug 11, 2013 · NTSB number ERA13CA369 · Final report

Probable cause

The pilot’s delay in applying power after a bounced landing, resulting in collision with terrain during a go-around.

NTSB analysis

The pilot stated after takeoff while en route to the destination airport he elected to fly to a private airstrip (Bates Field) located in rolling farmland. He lined up onto base leg for landing to the northwest on the upslope grass runway, and turned onto final approach. With 40 degrees of flaps extended, he identified the intended touchdown point, flared, and then climbed to attain the intended touchdown point. He landed, “but too hard and bounced up…,” touched down on the runway, and drifted off the runway into 6 to 8 inch high grass. He added power to abort the landing but impacted a knoll at the top of a crest on a hill, then continued climbing. While safely airborne he assessed the condition of the airplane noting the pilot and co-pilot doors were ajar, but did not find any other damage. He flew over the private airstrip and did not observe any damage then elected to proceed to his destination airport, where he landed uneventfully. While taxiing after landing he noticed the left landing gear was out of position. He further stated there was no preimpact mechanical failure or malfunction that caused the hard landing.

Inspection of the airplane by a Federal Aviation Administration inspector revealed damage and distortion to structural tubing in the cockpit, and wrinkles in the fabric adjacent to the left main landing gear.

Text from the NTSB. Open the NTSB docket for ERA13CA369 for the full record.

Event

Date
Aug 11, 2013
Type
Accident
Place
Verona, New York
Nearest airport
Bates Field (NONE)
Highest injury
None
Weather
Visual (VMC)
Light
Day

Maule M-5-210C

N-number
N6617R
Category
Airplane
Damage
Substantial
Operating rule
Part 91 (general aviation)
Purpose of flight
Personal

From the NTSB aviation accident database: N-registered aircraft, events since 2008, data through Oct 28, 2026. The file is published monthly, so the latest weeks are incomplete and recent records can change. The official source is the NTSB aviation investigation search. CheckAero is independent and not affiliated with the NTSB.