# NTSB SEA03LA003: Mooney M20K, N231EH, Rexburg, ID, October 12, 2002

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Limited investigation · Final report
- Date: October 12, 2002, 12:55 local (18:55 UTC)
- Place: Rexburg, ID
- Coordinates: 43.78004, -111.760658 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=43.7800&lon=-111.7607&mi=10
- Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping)
- Highest injury: No injuries
- Injuries: 4 uninjured
- Status: Completed, report April 8, 2003
- Report: Approved by Office Director
- Parties: Salt Lake FSDO
- NTSB case key (mKey): 55893
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=SEA03LA003
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/55893/pdf
- Page: https://openairdocs.org/ntsb/SEA03LA003

## Probable cause

The pilot's failure to perform a go-around once it became evident that his remedial action was not adequate to overcome the porpoise/pilot-induced oscillation that occurred during the landing flare. Factors include the pilot's inadvertent repeated ballooning/porpoising during the landing sequence, and a fence and line of trees off the departure end of the runway.

## Sequence of events

In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf).

- On ground/water collision with object, landing - roll
  - porpoise/pilot-induced oscillation - inadvertent, pilot in command (contributing factor)
  - remedial action - inadequate, pilot in command (contributing factor)
  - go-around - not performed, pilot in command (cause)
  - object - fence (contributing factor)
  - object - tree(s) (contributing factor)

## Analysis

The pilot entered a left downwind for Runway 17 with the intention of making a full stop landing on the 4,200 foot strip. He reportedly touched down on the runway numbers, but inadvertently allowed the aircraft to balloon back into the air. After a few seconds, the aircraft touched down a second time, but then ballooned even higher. According to the pilot, when the aircraft touched down the third time, he "...added some power to stay on the  ground." This resulted in the aircraft lifting off the runway for a third time. After the aircraft settled on the surface for the fourth and final time, the pilot concluded that he would not be able to stop before reaching the fence located just off the south end of the runway. At that point he decided to add full power in an attempt to clear the fence and complete the landing roll in the area beyond it. Although he got the aircraft off the ground, the landing gear caught on the fence and pulled the aircraft to the ground. Soon thereafter, the left wing collided with a tree and the aircraft came to rest. According to the pilot, there was no evidence of any malfunction of the flight control system or the engine. He also stated that during the entire landing sequence, including during the time he attempted to "clear the fence," the wing flaps were in the fully deployed (down) position. In his narrative report, he also stated that he has now learned to execute a go-around if the wheels are not firmly planted by the time the aircraft reaches the second VASI (Visual Approach Slope Indicator).

## Factual narrative

On October 12, 2002, approximately 1255 mountain daylight time, a Mooney M20K, N231EH, impacted a fence during the landing roll at Madison County Airport, Rexburg, Idaho. The private pilot and his three passengers were not injured, but the aircraft, which is owned and operated by Air Bound, LLC., sustained substantial damage. The 14 CFR Part 91 personal pleasure flight, which departed Driggs, Idaho, about 55 minutes earlier, was being operated in visual meteorological conditions. No flight plan had been filed.

According to the pilot, he entered a left downwind for Runway 17 with the intention of making a full stop landing on the 4,200 foot strip. He reportedly touched down on the runway numbers, but inadvertently allowed the aircraft to balloon back into the air. After a few seconds, the aircraft touched down a second time, but then ballooned even higher. According to the pilot, when the aircraft touched down the third time, he "...added some power to stay on the  ground." This resulted in the aircraft lifting off the runway for a third time. After the aircraft settled on the surface for the fourth and final time, the pilot concluded that he would not be able to stop before reaching the fence located just off the south end of the runway. At that point he decided to add full power in an attempt to clear the fence and complete the landing roll in the area beyond it. Although he got the aircraft off the ground, the landing gear caught on the fence and pulled the aircraft to the ground. Soon thereafter, the left wing collided with a tree and the aircraft came to rest.

According to the pilot, there was no evidence of any malfunction of the flight control system or the engine. He also stated that during the entire landing sequence, including during the time he attempted to "clear the fence," the wing flaps were in the fully deployed (down) position. In his narrative report, he also stated that he has now learned to execute a go-around if the wheels are not firmly planted by the time the aircraft reaches the second VASI (Visual Approach Slope Indicator).

## Aircraft

- Registration: [N231EH](https://openairdocs.org/deregistered/N231EH-2015-05-06), registration cancelled 2015-05-06, S/N 25-0179, built 1979 (OpenAirDocs)
- Reported make and model: Mooney M20K
- Registry model: [Mooney M20K](https://openairdocs.org/model/mooney-m20k) (registry code 5870220) (OpenAirDocs)
- Registry engine: [Continental TSIO-360 series](https://openairdocs.org/engine/continental-tsio-360-series) (registry code 17019, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 25-0179
- Airframe hours: 3444
- Engines: Continental TSIO-360-LB1B 210 horsepower reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Registered owner: Air Bound, LLC
- Airworthiness certificate: Standard, Normal
- Last inspection: Annual, June 10, 2002, 82 hours before
- Departed: RXE, Driggs, ID
- Destination: RXE, Rexburg, ID
- Airport: RXE, Madison County, runway 17, 4,200 × 75 ft, asphalt

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 39; injuries: none; private; airplane ratings: single-engine land; medical: class 2, valid medical--w/ waivers/lim; last flight review January 24, 2002; seat: left; flight hours: 266 total, 107 in this make and model, 118 as pilot in command, 41 in the last 90 days, 17 in the last 30 days, 5 in the last 24 hours

## Weather

- Conditions: Visual (VMC), Day
- Visibility: 10 statute miles
- Lowest ceiling: none
- Temperature: 25 °F

## FAA reports on this event (1)

The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs).

- [Accident 20021012028169A](https://openairdocs.org/incident/20021012028169A), Oct 12, 2002: Mooney M20K, Rexburg, ID, Substantial damage. (-23) Pilot stated that just prior to touch down the aircraft ballooned up a couple of times. The pilot landed the aircraft on the runway and applied the…

## Other investigations on N231EH (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB CEN11LA529](https://openairdocs.org/ntsb/CEN11LA529), Jul 30, 2011: Mooney M20K (N231EH), Opelousas, LA, substantial damage. Probable cause: The loss of engine power due to fuel contamination.

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.
