FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA18LA058 · Mooney M20K

21 Dec 2017 · Venice, FL, United States

Mooney M20K · Accident: landing gear not configured

From Darlington County Airport (UDG) to Venice Municipal Airport (VNC)

Report a problem

Event

NTSB case
ERA18LA058
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

Mooney M20K

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
N5254G
Operator
Unknown
Onboard fatalities
Unknown
Route
From Darlington County Airport (UDG), Darlington, SCTo Venice Municipal Airport (VNC), Venice, FL
Aircraft age
About 29 years (built 1988)
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
Landing
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
Landing gear not configured
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

  • Aircraft › Aircraft systems
  • Personnel issues › Action/decision

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

NTSB narrative

The private pilot approached the destination airport at the conclusion of the visual flight rules flight while receiving traffic advisory services from an air traffic controller. The pilot could not recall at what point during the approach he extended the landing gear but postulated that he may have done so about 10 miles from the airport. As the pilot was "dodging clouds" during the approach, he heard another pilot, who was also heading to the same airport, request a "pop-up" instrument flight rules clearance from the controller due to sea fog in the area. The controller then advised the accident pilot to follow the other airplane to the airport. During the approach to the runway, the accident pilot reduced the throttle to avoid overtaking the other airplane, and the landing gear warning horn activated. He then applied a small amount of throttle, and the horn stopped. The subsequent landing was normal until the landing flare, when the pilot heard a scraping noise. The airplane slid along the runway on its belly for 400 ft before coming to a stop. Postaccident examination of the landing gear revealed that the landing gear circuit breaker was open and that the landing gear position selector was in the down position. The main landing gear had extended minimally out of their respective wells, suggesting that the landing gear extension cycle had at least started but was not successfully completed. During recovery from the runway, the airplane was placed on jacks, and the landing gear was lowered using the emergency gear extension without incident. Damage to the landing gear extension system precluded further functional testing.

Based on the available information, it is possible that at some point during the flight, the pilot moved the landing gear selector handle to the down position, but the landing gear did not extend. When the pilot heard the landing gear warning horn activate as he reduced throttle, he should have realized that the landing gear was not in a safe position for landing. It is likely that his fixation on the weather conditions and the other airplane landing at the airport distracted him from completing this task. Had the pilot diverted to another nearby airport where the weather was better, he could have performed additional troubleshooting and likely could have performed a successful emergency extension of the landing gear without the distraction of the weather and other traffic.

Probable cause

A failure of the normal landing gear extension system for reasons that could not be determined due to damage to the system and the pilot's failure to ensure that the landing gear was down and locked before touchdown. Contributing to the accident was the pilot’s distraction due to weather and traffic.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA18LA058
Event ID
20171221X95947
Case number
ERA18LA058
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. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2017-12-22.
  • API snapshot SHA-256: f8e17433d919787c37ad9d303d8c95de70902981b00954fc030e905acc74e31e; retrieved 2026-09-16T06:13:39.859Z.