20260404002919A

Sequence of events leading to the accident:

On the morning of the flight, the pilot awoke at approximately 8:00 am, feeling well-rested. After having breakfast, the pilot and a passenger decided to undertake a spontaneous flight, which was not previously planned in advance. The pilot drove to a gas station near Martinsburg airport, where they purchased fuel for the aircraft and performed standard preflight checks.

Preflight checks:

The preflight inspection was conducted without incident. The aircraft's fuel consisted of a mix of 70% mogas and 30% avgas, totaling 13 gallons. Weather conditions and NOTAMS were checked using foreflight, and it was determined to be a suitable day for flying, yet warm. Due to these conditions, the pilot decided against landing at sky bryce, opting instead to fly over the area. The aircraft was inspected, and all systems, including lights, oil levels, and control surfaces, were found to be in working order. The pilot noted that the brake pucks, recently replaced, needed to bed in but were functioning adequately.

Takeoff and climb out:

Takeoff occurred at approximately 1:31 pm EDT. The aircraft, noted to be heavy, performed normally with an engine RPM between 3030 and 3040. During the climb, power was gradually reduced to maintain a comfortable ascent rate. Around 2,500 MSL, the pilot observed higher-than-expected exhaust gas temperatures (egts) but attributed this to the warm weather. The oil temperature sensor displayed erratic readings, prompting the pilot to stabilize it by pulling back the power, confirming the oil temperature was within safe limits.

Onset of engine problems:

At approximately 1:37 pm, the pilot noticed an increase in egts and a delay in the engine's response when attempting to return to 2750 RPM. Concerned, the pilot decided to return to the airport. During the radio call to Martinsburg tower, the engine experienced its first stumble. The tower was informed, and a runway change was requested and granted.

Engine failure and emergency response:

At 1:38 pm, the engine began to exhibit significant issues, unable to maintain 2750 RPM and stumbling around 2650-2700 RPM. The pilot declared an emergency. The aircraft, at approximately 1600 AGL, the pilot determined to be unable to reach the runway. The pilot declared an emergancy and initiated emergency procedures, maintaining control and performing troubleshooting. The aircraft continued towards the runway for a short duration before the pilot realized a landing on the runway was unfeasible.

Field landing decision:

The pilot, familiar with the surrounding area, selected a field for an emergency landing, avoiding nearby infrastructure and unsuitable terrain. The field was identified as within reach and appeared adequate for landing.

Landing sequence:

At 1:40 pm, the aircraft turned towards the selected field. Communication with Martinsburg tower confirmed the landing location as a farm. The pilot observed terrain challenges within the field but proceeded with landing. The engine stalled, and two flaps were deployed to manage speed. The aircraft touched down at approximately 60-65 knots. Despite brake application, the aircraft was unable to stop before encountering a birch post wire fence and subsequently a barbed wire fence, which halted the aircraft.

Aftermath:

Both the pilot and passenger exited the aircraft uninjured. Emergency services arrived promptly, and measures were taken to prevent fuel leakage. The national transportation safety board (NTSB) was contacted, photographs of the incident were taken, and the aircraft was cleared by the NTSB for removal to the hangar. The aircraft sustained substantial damage to the internal transverse spar in the fuselage behind the pilot seat. Additionally, there was damage to the leading edge of the root wing on the co-pilot side. The propeller was damaged, and the landing gear fairing was broken.