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

Cessna 172N accident near Sanford, Florida, November 9, 2004

On November 9, 2004 at about 3:15 am local time, a Cessna 172N, registered N8077E, was substantially damaged in an accident near Sanford, Florida (Orlando Sanford Int'L Airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 3 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The improper flare by the pilot in command resulting in a hard landing, Restricted movement of the throttle was a contributing factor.

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

What the record shows

Date
November 9, 2004 · about 3:15 am local time
Place
Sanford, Florida · Orlando Sanford Int'L Airport · map
Type
Accident
Injuries
No one was hurt; 3 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Cessna 172N · all 172Ns on the register
Registration
N8077E · registry record · serial 17272133
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The pilot stated that while on final approach to runway 9L when the flight was approximately 25 feet, he manipulated the throttle, but it appeared the throttle was stuck in a position which was insufficient to perform a go-around. The airplane contacted the runway causing the emergency locator transmitter (ELT) to activate. The pilot advised air traffic control of the ELT activation and taxied the airplane to the ramp where he secured the airplane. He reported the ELT activation on the aircraft discrepancy log sheet. The post accident inspection of the aircraft was conducted by Avion Aviation Maintenance on November 9, 2004, without FAA or NTSB oversight. The inspection consisted of a visual engine inspection, and freedom of movement of the throttle control system. The throttle and mixture controls were found free and smooth and no defects were noted.

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; instrument: airplane
  • Flight time: 165 hours in all; 53 as pilot in command
  • Last flight review: October 28, 2004
  • Medical certificate: Class 1 (valid medical--no waivers/lim.)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 13,029 hours
  • Last inspection: 100-hour inspection, October 18, 2004; 88.5 hours since
  • Maximum gross weight: 2,300 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming O-360-A4M (piston); 0 hours total

The flight

  • Departed from: KLAL Lakeland FL at 2:30 am
  • Destination: KSFB Sanford FL
  • Flight plan: IFR
  • Runway 9L, 9,600 ft by 150 ft

Weather at the time

  • Light: night
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 63°F (17°C), dew point 55°F (13°C)
  • Altimeter: 30.10 inHg
  • Observation at 2:53 am from KSFB

Injuries

FatalSeriousMinorNone
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.