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

Cessna 172S accident near Daytona Beach, Florida, February 15, 2011

On February 15, 2011 at about 5:00 pm local time, a Cessna 172S, registered N378FA, was substantially damaged in an accident during landing (flare/touchdown) near Daytona Beach, Florida (Daytona Beach International airport). It was an instructional 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

The pilot's inadequate flare that resulted in a hard landing.

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

What the record shows

Date
February 15, 2011 · about 5:00 pm local time
Place
Daytona Beach, Florida · Daytona Beach International · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Cessna 172S · all 172Ss on the register
Registration
N378FA · no longer on the register · serial 172S9378
Damage
Substantial damage
Flight
Instructional flight · general aviation rules (Part 91)

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

According to the pilot, as he approached the runway to land and crossed the temporary threshold, he configured the airplane in a level attitude. Upon touchdown, the airplane impacted the runway hard and bounced. The pilot pushed the yoke forward and the airplane bounced a second time, resulting in substantial damage to the firewall. The pilot reported no preimpact mechanical malfunctions with the airplane.

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. Hard landing during landing (flare/touchdown) defining event

The NTSB's findings

  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Landing flare › Not attained/maintained
  • cause Personnel issues › Action/decision › Action › Incorrect action performance › Pilot

Pilot

  • Certificate: student
  • Flight time: 70 hours in all; 70 in this make and model; 50 in the last 90 days; 13 in the last 30 days; 9 as pilot in command
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Last inspection: 100-hour inspection
  • Maximum gross weight: 2,558 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming IO-360-L2A (piston); 0 hours total
  • Operator: Phoenix East Aviation Inc.

The flight

  • Departed from: GNV Gainesville FL at 4:15 pm
  • Destination: DAB Daytona Beach FL
  • Flight plan: VFR
  • Runway 07L, 10,500 ft by 150 ft

Weather at the time

  • Light: daylight
  • Wind: from 010° at 10 knots
  • Visibility: 10 statute miles
  • Sky: a few clouds at 25,000 ft
  • Temperature: 64°F (18°C), dew point 48°F (9°C)
  • Altimeter: 30.27 inHg
  • Observation at 4:53 pm from DAB

Injuries

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

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

2003-11-21MIA04CA028 · accident near Orlando, FL · substantial damage · no 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.