ERA11LA489
2011-08-31 · Plymouth, Massachusetts, United States · None · 1 aircraft · Status: Completed
Airport PYM
Aircraft involved
Probable cause & findings
The pilot's inadequate flare and improper recovery from a bounced landing.
Factual narrative
On August 31, 2011, about 1630 eastern daylight time, a Cessna 172N, N739RU was substantially damaged during landing at Plymouth Municipal Airport (PYM), Plymouth, Massachusetts. The private pilot was not injured. The airplane was registered to a private owner, and operated by Alpha One Flight Service under the provisions of 14 Code of Federal Regulations Part 91. Visual meteorological conditions prevailed for the local flight and no flight plan had been filed. The pilot reported that she was planning to stay in the airport traffic pattern to conduct takeoff and landing practice. During the takeoff roll, forward pressure was required on the control column to prevent the airplane from pitching up prior to rotation speed. She reported that she was not concerned about the controllability of the airplane and elected not to abort the takeoff. During the climb, nose down trim was applied; however, forward pressure was still required to maintain the correct pitch attitude. However, she reported to a Federal Aviation Administration (FAA) inspector that once in flight everything was normal. During the landing flare, the pilot reduced engine power; however, she was unable to pull back on the control column. The airplane bounced several times, each time impacting the nose landing gear prior to the main landing gear. According to a written statement by a certificated flight instructor who flew the airplane prior to the accident flight; he "did not find any discrepancies with the aircraft during preflight and the flight was uneventful." The accident was not reported to the FAA or the NTSB, but the damaged airplane was discovered at the airport approximately two weeks after the accident by an FAA inspector. Prior to the discovery of the accident,one of the flight school's mechanics removed the engine cowling and noticed the firewall was damaged. He further noted that the elevator trim was in a slight nose-up setting. He moved the trim wheel and noted the elevator trim tab operated. He then disconnected the elevator push/pull rod that connected to the bellcrank and was able to move the elevator and reported the freedom of movement. He further noted slack in the elevator secondary control cables which he attributed to the damage to the structure. Examination of the airplane by an FAA inspector and an aircraft mechanic revealed that the firewall was buckled and the floor beneath the pilot and co-pilot's seat was damaged. The elevator push/pull rod, which connected to the bellcrank, was disconnected and the elevator moved unobstructed. The primary flight control cables remained connected at the elevator and the bellcrank. There was no evidence of damage to the elevator control "U." Examination behind the instrument panel revealed that there was nothing that would interfere with the travel of the control column. There was no indication of preimpact binding or damage. The aluminum channels, which were connected at the instrument panel and the firewall, remained attached at both ends by the rivets; however, were bent down causing binding to the aileron chain sprockets. The instrument panel had shifted aft of its normal position. The elevator control cables were void of tension and an accurate deflection indication of the elevator could not be obtained. The bearings and pulleys were free and showed no signs of previous damage. In a written statement, a representative of the flight school reported no mechanical malfunctions or failures that would have precluded normal operation of the airplane. The pilot reported that the intent of the flight was to perform practice takeoffs and landings. During the first takeoff roll, she noticed that the control column required forward pressure to prevent the airplane from prematurely rotating. The pilot further reported that she was not concerned about the controllability of the airplane, elected not to abort the takeoff, and continued around the traffic pattern. During the landing flare, she was unable to pull back on the control column, and the airplane bounced several times. Postaccident examination of the airplane revealed no evidence of any discrepancies that would have interfered with movement of the control column or operation of the elevator and elevator trim controls. Additionally, the operator reported that there were no mechanical malfunctions or failures with the airplane that would have precluded normal flight operations of the airplane. It is likely that the pilot did not arrest the airplane’s descent rate, resulting in a bounced landing, and then allowed the airplane to porpoise. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
FAA avdata. C = Cause, F = Factor.
- C Personnel issues-Action/decision-Action-Incorrect action performance-Pilot - C
- C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Landing flare-Incorrect use/operation - C
Verbatim from NTSB's published report. Source file
NTSB_2011_ERA11LA489.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Search this event elsewhere
External sources are reported, not agency: signal that something happened, not fact about what happened.
- TallyAero Live Wire Aviation press
- NTSB CAROL Agency ↗
- NTSB Docket Agency ↗
- Aviation Safety Network Aviation press ↗
- Kathryn's Report Aviation press ↗
- Aviation Herald Aviation press ↗
- AVweb Aviation press ↗
- Pilots of America Community ↗
- Reddit /r/flying Community ↗
- FlightAware Aviation press ↗
- AOPA accident database Aviation press ↗
- Google News News ↗
- DuckDuckGo News ↗