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

Luscombe 8A accident near Homosassa, Florida, September 30, 2000

On September 30, 2000 at about 1:50 pm local time, a Luscombe 8A, registered N2234K, was substantially damaged in an accident near Homosassa, Florida. It was a personal flight under general aviation rules (Part 91). 1 person had minor injuries. The weather was instrument conditions (cloud, fog or low visibility).

The NTSB's probable cause their words, unchanged

The pilot's inadvertent flight into instrument meteorological conditions and subsequently exhausting his fuel supply. Factors were his failure to obtain a weather briefing, the weather conditions which included clouds and obscuration, the residence and the tree.

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

What the record shows

Date
September 30, 2000 · about 1:50 pm local time
Place
Homosassa, Florida · map
Type
Accident
Injuries
1 person had minor injuries.
Weather
instrument conditions (cloud, fog or low visibility)
Aircraft
Luscombe 8A · all 8As on the register
Registration
N2234K · registry record · serial 4961
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The pilot departed the airport en route to another airport located 24.5 miles to the south/southeast to have an annual maintenance inspection performed on the airplane. Prior to departure, he did not receive a weather briefing. The pilot stated that upon arrival at his destination airport, low clouds and an overcast fog layer had developed. He circled the area looking for better ground visibility and none was found. An attempt was made to return to the departure airport for landing. While maneuvering to maintain visual conditions for the landing, the engine lost power due to fuel starvation, and attempts to restart the engine were unsuccessful. Unable to reach the airport, the pilot made an off airport landing between a house and a tree. Upon impact with the ground, the airplane nosed over.

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

Pilot

  • Certificate: private
  • Ratings: single-engine land; single-engine sea
  • Flight time: 1,124 hours in all; 100 in this make and model; 5 in the last 90 days; 1 in the last 30 days; 1,052 as pilot in command
  • Medical certificate: Class 3 (valid medical--w/ waivers/lim.)
  • Seat: left

The aircraft

  • Airframe total time: 876 hours
  • Last inspection: annual inspection, September 2, 1999; 261 hours since
  • Maximum gross weight: 1,260 lb
  • Seats: 2
  • Landing gear: fixed
  • Engine: Continental A65-8F (piston); 0 hours total

The flight

  • Departed from: CGC Crystal River FL at 12:00 pm
  • Destination: BKV Brooksville FL
  • Flight plan: none
  • Runway 0

Weather at the time

  • Light: daylight
  • Wind: from 010° at 10 knots
  • Visibility: 10 statute miles
  • Sky: overcast at 1,200 ft; scat at 900 ft
  • Temperature: 75°F (24°C), dew point 75°F (24°C)
  • Altimeter: 29.00 inHg
  • Observation at 1:53 pm from BKV, 16 miles away

Injuries

FatalSeriousMinorNone
Crew1

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.