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

Cessna 172 accident near Lynchburg, Virginia, September 16, 2017

On September 16, 2017, a 1979 Cessna 172, registered N5396D, was substantially damaged in an accident during landing (flare/touchdown) near Lynchburg, Virginia (Falwell airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot's unstabilized approach, which resulted in an aborted go-around, an aerodynamic stall, and a hard landing.

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

What the record shows

Date
September 16, 2017
Place
Lynchburg, Virginia · Falwell · map
Type
Accident
Injuries
No one was hurt; 2 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Cessna 172 N, built 1979 · all 172s on the register
Registration
N5396D · no longer on the register · serial 17272562
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The pilot reported that, during landing, the airplane approached with "extra speed" and ballooned in the landing flare. He added that, "instantly my training took over" and he applied power to go-around, but then also remembered he could not go around when landing in this direction, at this airport, due to terrain and obstacles. He further added that he then reduced power to idle and "stalled the airplane to the ground" and impacted the remining runway hard. Subsequently, he taxied the airplane to the ramp without further incident. The ailerons, wings, and firewall sustained substantial damage. During a telephone conversation with the NTSB investigator-in-charge, the pilot reported that he had flown into this airport numerous times prior to the accident and knew that, "once you get to the powerlines you are committed to landing." The power lines were located about ¼ nautical miles from the runway threshold. The pilot did not report that there were any preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation. The Federal Aviation Administration Chart Supplement for the airport stated in part: "Land Rwy [runway] 28 (west) tkf [takeoff] Rwy [runway] 10 (east)." The pilot reported that the landing was on runway 28.

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. Aerodynamic stall/spin during approach (VFR go-around)
  2. Loss of control in flight during approach (VFR go-around)
  3. Hard landing during landing (flare/touchdown) defining event

The NTSB's findings

  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Descent/approach/glide path › Incorrect use/operation
  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Angle of attack › Capability exceeded
  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Airspeed › Incorrect use/operation
  • Environmental issues › Physical environment › Terrain › Mountainous/hilly terrain › Contributed to outcome

Pilot

  • Certificate: flight instructor, commercial pilot
  • Ratings: multi-engine land; single-engine land; instructor: airplane multi-engine; instructor: airplane single-engine; instructor: instrument airplane; instrument: airplane
  • Flight time: 351 hours in all; 7 in this make and model; 88 in the last 90 days; 31 in the last 30 days; 194 as pilot in command; 12 on instruments
  • Last flight review: April 20, 2017
  • Medical certificate: Class 2 (without waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Last inspection: 100-hour inspection
  • Maximum gross weight: 2,400 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming O-320 SERIES (piston); 0 hours total

The flight

  • Departed from: OFP Hanover VA at 11:00 pm
  • Destination: W24 Lynchburg VA
  • Flight plan: none
  • Runway 28, 2,932 ft by 50 ft

Weather at the time

  • Light: night
  • Wind: from 350° at 3 knots
  • Visibility: 10 statute miles
  • Sky: overcast at 9,000 ft
  • Temperature: 72°F (22°C), dew point 63°F (17°C)
  • Altimeter: 30.11 inHg
  • Observation at 11:54 pm from KLYH, 5 miles away

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

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 N5396D the same tail number, which may have belonged to a different aircraft at the time

1999-07-14DEN99LA121 · accident near Englewood, CO · 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.