The U.S. aircraft register, updated daily
Accidents · NTSB ERA18LA058 · Final report

Mooney M20K accident near Venice, Florida, December 22, 2017

On December 22, 2017, a 1988 Mooney M20K, registered N5254G, was substantially damaged in an accident during landing near Venice, Florida (Venice Muni airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

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.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
December 22, 2017
Place
Venice, Florida · Venice Muni · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Mooney M20K NO SERIES, built 1988 · all M20Ks on the register
Registration
N5254G · registry record · serial 25-1180
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

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.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Landing gear not configured during landing defining event

The NTSB's findings

  • cause Aircraft › Aircraft systems › Landing gear system › (general) › Malfunction
  • cause Personnel issues › Action/decision › Action › Forgotten action/omission › Pilot
  • factor Personnel issues › Psychological › Attention/monitoring › Monitoring equip/instruments › Pilot

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 216 hours in all; 43 in this make and model; 16 in the last 90 days; 12 in the last 30 days; 216 as pilot in command
  • Last flight review: July 8, 2017
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 4,272.7 hours
  • Last inspection: annual inspection, October 2, 2017
  • Maximum gross weight: 2,900 lb
  • Seats: 4
  • Landing gear: retractable
  • Engine: Cont Motor TSIO-360 SER (piston); 0 hours total

The flight

  • Departed from: UDG Darlington SC at 5:00 pm
  • Destination: VNC Venice FL
  • Flight plan: none
  • Runway 23, 5,000 ft by 150 ft

Weather at the time

  • Light: night
  • Wind: from 280° at 4 knots
  • Visibility: 9 statute miles
  • Sky: clear
  • Temperature: 72°F (22°C), dew point 72°F (22°C)
  • Altimeter: 30.10 inHg
  • Observation at 11:53 pm from KSRQ, 21 miles away

Injuries

FatalSeriousMinorNone
Flight crew1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

4 documents, released by the NTSB on April 18, 2019. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Other NTSB records under N5254G the same tail number, which may have belonged to a different aircraft at the time

2013-06-28CEN13LA388 · accident near Hudson, CO · substantial damage · serious injuries

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.