FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA09CA495 · Underland/Grothe/Finstrom MMII (MUST

29 Aug 2009 · Lantana, FL, United States Narrative disagrees

Underland/Grothe/Finstrom MMII (MUST · Accident: flight control system malfunction/failure during takeoff

From Palm Beach County Park Airport (LNA) to Palm Beach County Park Airport (LNA)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's location and aircraft involved. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
ERA09CA495
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Underland/Grothe/Finstrom MMII (MUST Narrative disagrees

Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N7798R
Operator
Unknown
Onboard fatalities
Unknown
Route
From Palm Beach County Park Airport (LNA), Lantana, FLTo Palm Beach County Park Airport (LNA), Lantana, FL
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Takeoff
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Flight control system malfunction/failure
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Personnel issues › Action/decision

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot stated that he completed the takeoff checklist and began the takeoff roll. The airplane accelerated, and at 75 to 80 miles-per-hour (mph) indicated, he attempted to rotate, but was unsuccessful because of what he thought was his seat restricting aft movement of the control stick. The certified flight instructor (CFI) attempted to move his control stick and was also unable. He (CFI) reduced the throttle and mixture controls, and both applied brake pressure. The airplane went off the end of the runway onto grass and came to rest with the nose landing gear collapsed. The CFI stated that, before takeoff, he confirmed freedom of the flight controls. During the takeoff roll when the airplane had reached 65 mph and the pilot had not begun to rotate he informed the pilot to “…lighten the nose….” The pilot acknowledged, and when at 85 mph, the CFI told the pilot to rotate. The pilot replied that he was trying. The CFI reported he attempted to rotate, applying aft elevator control, and he then felt metal on metal contact. Realizing that a control problem of unknown origin existed, he reduced the throttle and mixture controls, took control of the airplane, and asked the pilot to assist him on the brakes. He avoided the runway end lights and had the canopy released before contacting bushes at the edge of a lake. Both exited the airplane, and the pilot mentioned to him at that time that his seat had slid forward while turning onto the runway resulting in elevator control interference. Postaccident inspection of the airplane by a Federal Aviation Administration airworthiness inspector revealed the left seat was in the most forward position and the flight control stick was in contact with the seat. While in that position the elevator primary and secondary flight control surfaces were in positions corresponding to airplane nose-down input. The left seat was moved aft, and full elevator control authority was obtained. Further examination of the seat revealed the locking mechanism appeared to be operational; however, it was noted that the seat did not contain a cutout which allowed full aft movement of the control stick.

Probable cause

The delay by both pilots to abort the takeoff resulting in a runway overrun. Contributing to the accident was the unintentional forward movement of the pilot's seat resulting in interference with the control stick.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA09CA495
Event ID
20090901X94617
Case number
ERA09CA495
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: d092718cabe6672c22e0be645e58e0d4fe69e3b6cc01c7ba20f2764dba804913; retrieved 2026-09-15T12:52:47.874Z.