Plane Crash List

Cessna 172 N5396D

16 September 2017 · Lynchburg, Virginia, United States · No injuries

Summary

On 16 September 2017 at about 00:00 local time, a Cessna 172 registered N5396D was involved in an accident near Lynchburg, Virginia, United States. 2 people were on board and nobody was injured. The aircraft was substantially damaged. The NTSB has published a probable cause for this accident; it is quoted in full below.

The record

Date
at 00:00
Classification
Accident
Location
Lynchburg, Virginia, United States
Nearest airport
Falwell (W24)
Coordinates
37.3781, -79.1222
Aircraft
Cessna 172
Registration
N5396D
Category
Airplane
Year built
1979
Engines
1
Operator
Not recorded
Operating rule
Part 91: General Aviation
Purpose of flight
Personal
Phase of flight
Not recorded
Route
Hanover → Lynchburg
Aircraft damage
Substantial
Weather
VMC
Light
Night
NTSB number
GAA17CA540

People

Nobody was injured.

On board Died Serious Minor Uninjured
2 0 0 0 2

Probable cause

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

Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.

Read the full NTSB narrative

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.

Quoted verbatim from the NTSB record.

Other Cessna 172 accidents

Date Aircraft Location Operator Outcome Died
1 Mar 2017 Cessna 172S
N22904
St Petersburg, Florida, United States - No injuries -
9 Nov 2017 Cessna 172
N2138W
Trenton, New Jersey, United States Christiansen Aviation Inc No injuries -
19 Nov 2017 Cessna 172M
N9678Q
Chico, California, United States Northgate Aviation Inc Minor injuries -
19 Nov 2017 Cessna 172P
N52492
San Jose, California, United States Squadron 2 Serious injuries -
24 Jun 2017 Cessna 172
N6474B
Fulton, Missouri, United States - Minor injuries -
16 Nov 2017 Cessna 172RG
N6102R
Opa Locka, Florida, United States - No injuries -

All 12,209 records for this type

Other accidents in this area

Date Aircraft Location Operator Outcome Died
28 Jun 2017 Cessna 172
N2460A
Emporia, Virginia, United States Epix Services LLC No injuries -
22 Nov 2017 Hughes 300
N9685F
Woodlawn, Virginia, United States - No injuries -
15 May 2017 Piper PA22
N31JP
South Boston, Virginia, United States - No injuries -
29 Nov 2017 Driggers Quillan E TITAN TORNADO
N50F
Mechanicsville, Virginia, United States - No injuries -
3 Jul 2017 Piper PA 15
N4195H
Farmville, Virginia, United States Philip Cianciolo Serious injuries -
4 Jul 2017 Aviat A-1C-180
N272WY
Dillwyn, Virginia, United States - Serious injuries -

All 170,864 records in United States