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

Cessna 172N accident near Valkaria, Florida, August 6, 2014

On August 6, 2014 at about 1:30 pm local time, a 1979 Cessna 172N, registered N9400E, was substantially damaged in an accident during landing (flare/touchdown) near Valkaria, Florida (Valkaria airport). It was an instructional flight under general aviation rules (Part 91). 1 person had minor injuries. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot's misjudgment of speed and distance on final approach during a precautionary landing, resulting in a touchdown off the departure end of the runway and collision with terrain. A factor in the accident was a partial loss of engine power for reasons that could not be determined in post accident testing.

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

What the record shows

Date
August 6, 2014 · about 1:30 pm local time · cases in 2014
Place
Valkaria, Florida · Valkaria · cases near this airport · map
Type
Accident
Injuries
1 person had minor injuries.
Weather
visual conditions (good weather)
Aircraft
Cessna 172N, built 1979 · all 172Ns on the register
Registration
N9400E · registry record · serial 17272249
Damage
Substantial damage
Flight
Instructional flight · general aviation rules (Part 91)

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

According to the student pilot, she had just landed after a local instructional flight.  Her instructor completed the solo endorsement in her logbook as they taxied back to the arrival end of the runway 28.  The student pilot then taxied on to runway 28 for departure.   She applied full throttle and the airplane lifted off the runway normally.  At approximately 500 feet above ground level the engine began to run rough and dropped to 1900 RPMs.  The student pilot immediately lowered the nose of the airplane to attain best glide speed and started a left hand turn to return to the airport. She attempted to land on runway 10. Approximately 20 seconds after the engine began running rough the pilot applied the carburetor heat and then reduced the throttle to idle. The student pilot did not attempt however to increase power after the application of carburetor heat and the throttle remained in the idle position for the remainder of the approach.  The pilot then applied full flaps as the airplane was descending over midfield.  The airplane overflew the runway and touched down in the grass immediately off the departure end of runway 10.  The airplane subsequently struck a fence and nosed over. Post accident examination of the airplane and engine showed no evidence of mechanical failure or malfunction. The engine was started and operated with no signs of failure. A review of the carburetor icing probability chart shows the aircraft was operating in conditions that were not conductive to carburetor icing at the time of the accident. The pilot had 43 total flight hours.

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 (partial) during initial climb
  2. Runway excursion during landing (flare/touchdown) defining event
  3. Collision with terrain or object (not controlled flight into terrain) during landing (flare/touchdown)

The NTSB's findings

  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Airspeed › Incorrect use/operation
  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Descent/approach/glide path › Incorrect use/operation
  • factor Not determined › Not determined › (general) › (general) › Unknown/Not determined
  • cause Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Student/instructed pilot

Pilot

  • Certificate: student
  • Flight time: 43 hours in all; 43 in this make and model; 43 in the last 90 days; 43 in the last 30 days
  • Medical certificate: Class 3 (without waivers/limitations)
  • Seat: left
  • Injury: minor injuries

The aircraft

  • Airframe total time: 6,940 hours
  • Last inspection: 100-hour inspection, June 18, 2014; 100 hours since
  • Maximum gross weight: 2,299 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming 0-320 SERIES (piston); 0 hours total

The flight

  • Departed from: X59 Valkaria FL at 1:30 pm
  • Destination: X59 Valkaria FL
  • Flight plan: none
  • Runway 10, 4,000 ft by 75 ft

Weather at the time

  • Light: daylight
  • Visibility: 10 statute miles
  • Sky: a few clouds at 2,000 ft
  • Temperature: 86°F (30°C), dew point 79°F (26°C)
  • Altimeter: 30.05 inHg
  • Observation at 1:53 pm from MLB, 10 miles away

Injuries

FatalSeriousMinorNone
Flight crew1

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

7 documents, released by the NTSB on October 16, 2014. 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.

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/ERA14CA375.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

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 does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.