FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA11IA110 · Mooney M20E

5 Jan 2011 · St. Petersburg, FL, United States

Mooney M20E · Incident: flight control system malfunction/failure on approach

From Baytown Airport (HPY) to St. Petersburg Clearwater International Airport (PIE)

Report a problem

Event

NTSB case
ERA11IA110
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
Incident
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

Mooney M20E

Aircraft type
Mooney M20
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
N7828V
Operator
Unknown
Onboard fatalities
Unknown
Route
From Baytown Airport (HPY), Baytown, TXTo St. Petersburg Clearwater International Airport (PIE), St. Petersburg, 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
Approach · IFR final approach
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
None

Cause areas

  • Aircraft › Aircraft structures

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

As the pilot was making a night, overwater instrument approach to a coastal airport in the borrowed airplane, he attempted to extend the landing gear normally via the Johnson bar, which he could only partially raise. He checked to see if anything was blocking it then attempted to raise it again without success. He tried a third time before calling the tower air traffic controller and reporting that he had a landing gear problem. About 1/4 mile from the runway, the pilot applied more pressure to the Johnson bar, and it clicked into place; however, the airplane immediately banked to the left. The pilot was unable to turn the yoke to the right, and the airplane continued to roll while descending, at one point approaching a 60-degree bank. The pilot declared an emergency with the tower controller and was cleared to land on any runway. He then retracted the landing gear, but the roll continued. The pilot then retracted the flaps, reduced power, and added full right rudder. He was able to stop the turn with the airplane in a left slip with about 15 to 20 degrees of left bank. After completing about 315 degrees of a 360-degree turn, the pilot saw that he was about to be lined up with the runway again. He lowered the landing gear, and with a right crosswind and left slip, the airplane touched down well left of runway centerline and came to a stop.

A subsequent examination of the airplane revealed no damage. However, below the cockpit, a small flashlight of unknown ownership was found jammed between the aft side of the aft nosewheel well bulkhead and the landing gear bellcrank, adjacent to the aileron control linkage and below where the Johnson bar went through the deck. When the Johnson bar was raised, a 3- to 4-inch hole could be seen in the old, worn boot above where the flashlight was found, which likely allowed the flashlight to fall through. The airplane had been rebuilt between 2004 and 2006, and the latest annual inspection was completed in April 2010 with the airplane determined to be in an airworthy condition. Per Federal Aviation Administration Order 8130.2F, the term “airworthy” is not defined in United States Code; however, for an aircraft to be so, it must conform to its type certificate, and it must be in a condition for safe operation. The Order further defines the condition as being relative to wear and deterioration and states, as examples, skin corrosion, window delamination/crazing, fluid leaks, and tire wear, but nothing relating to interior items. Researched government, industry and advocacy group publications did not emphasize that the condition of interior items, such as boots and covers, could affect aircraft airworthiness.

Probable cause

An inadequately maintained interior cockpit boot, which allowed a flashlight to fall through and subsequently jam the airplane's flight controls. Contributing to the incident was a lack of emphasis by government, industry, and advocacy groups that the condition of interior items, such as boots and covers, could affect aircraft airworthiness.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA11IA110
Event ID
20110111X92431
Case number
ERA11IA110
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: local date, investigation status, damage. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2011-01-06.
  • API snapshot SHA-256: e4a37d5906f0277f980cbc95aa2c8f24c38a25de81a8290cca4f0838a7d6b4ff; retrieved 2026-09-15T15:41:11.972Z.