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

Mooney M20C accident near Marathon, Florida, October 10, 2009

On October 10, 2009 at about 1:20 am local time, a Mooney M20C, registered N2558Y, was destroyed in an accident during enroute (cruise) near Marathon, Florida. It was a personal flight under general aviation rules (Part 91). 3 people had minor injuries. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

A total loss of engine power for undetermined reasons.

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

What the record shows

Date
October 10, 2009 · about 1:20 am local time
Place
Marathon, Florida · map
Type
Accident
Injuries
3 people had minor injuries.
Weather
visual conditions (good weather)
Aircraft
Mooney M20C · all M20Cs on the register
Registration
N2558Y · no longer on the register · serial 3267
Damage
Destroyed
Flight
Personal flight · general aviation rules (Part 91)

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

During cruise flight the pilot experienced an increase in engine noise before the engine suddenly lost power. While the fuel status and tank indications were normal, he attempted to restart the engine three separate times without success. The pilot reported to air traffic control that the engine had failed and that he would be conducting an emergency landing into the Gulf of Mexico. The pilot and passengers were able to egress the airplane and held onto a crab pot buoy. The occupants of the airplane were rescued by the United States Coast Guard the next morning. After impact, the airplane sank and was not located.

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. Loss of engine power (total) during enroute (cruise) defining event
  2. Ditching during emergency descent

The NTSB's findings

  • cause Aircraft › Aircraft power plant › Engine (reciprocating) › (general) › Failure
  • factor Environmental issues › Physical environment › Terrain › Water › Contributed to outcome
  • cause Not determined › Not determined › (general) › (general) › Unknown/Not determined

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 1,000 hours in all; 358 in this make and model; 12 in the last 90 days; 8 in the last 30 days; 940 as pilot in command
  • Last flight review: June 10, 2008
  • Medical certificate: Class 3 (without waivers/limitations)
  • Seat: left
  • Injury: minor injuries

The aircraft

  • Airframe total time: 5,721 hours
  • Last inspection: annual inspection, September 18, 2009
  • Maximum gross weight: 2,575 lb
  • Seats: 4
  • Landing gear: retractable
  • Engine: Lycoming O-360-A1D (piston); 0 hours total

The flight

  • Departed from: VDF Tampa FL at 11:53 pm
  • Destination: MTH Marathon FL
  • Flight plan: none

Weather at the time

  • Light: night, dark
  • Wind: from 110° at 7 knots
  • Visibility: 10 statute miles
  • Sky: scat at 2,400 ft
  • Temperature: 84°F (29°C), dew point 73°F (23°C)
  • Altimeter: 30.01 inHg

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers2

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

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

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.