Aviation Crash Map

Piper PA-28-161 N9089N

29 August 2013 · Danville, Virginia, United States · Fatal

Summary

On 29 August 2013 at about 23:45 local time, a Piper PA-28-161 registered N9089N, operated by General Aviation Inc, was involved in an accident near Danville, Virginia, United States. One person was on board and one died. The aircraft was destroyed. The NTSB has published a probable cause for this accident; it is quoted in full below.

The record

Date
at 23:45
Classification
Accident
Location
Danville, Virginia, United States
Nearest airport
Danville Regional Airport (DAN)
Coordinates
36.5653, -79.3417
Aircraft
Piper PA-28-161
Registration
N9089N
Category
Airplane
Year built
1986
Engines
1
Operator
General Aviation Inc
Operating rule
Part 91: General Aviation
Purpose of flight
Instructional
Phase of flight
Not recorded
Route
Danville → Danville
Aircraft damage
Destroyed
Weather
VMC
Light
Dusk
NTSB number
ERA13FA385

People

1 person died.

On board Died Serious Minor Uninjured
1 1 0 0 0

Probable cause

The student pilot's failure to maintain control and climb the airplane during a go-around maneuver. Contributing to the accident was the flight instructor's failure to provide adequate oversight of the student pilot by ensuring that the cockpit was free of distractions.

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

Read the full NTSB narrative

Several eyewitnesses reported observing the airplane performing several takeoffs and landings. One witness stated that, during one landing attempt, the airplane was low, that a go-around maneuver was initiated, and that the airplane banked sharply left and right during the maneuver. The witness reported that the second landing attempt was successful and that the airplane was then taxied back to the beginning of the runway for another takeoff. During the accident approach, the airplane was observed flaring too high and banking left. One witness stated that the pilot added power and categorized the subsequent climbout as very shallow just before the airplane impacted an antenna and terrain. A postimpact fire ensued. Examination of the wreckage revealed no abnormalities or malfunctions that would have precluded normal operation. Review of flight school records revealed that the student pilot's first solo flight was 4 days before the accident and that the flight was 0.8 hour long. It could not be determined if the first solo flight was considered the student pilot's supervised solo or if the accident flight was considered the supervised solo. The flight school's standard operating procedure was to "completely go through all requirements twice"; therefore, although the accident flight was the student pilot's second solo flight, it should still have been supervised by the flight instructor. The flight instructor reported that the student pilot was scheduled to fly about an hour earlier than when the accident flight initiated; however, due to work requirements, the student pilot had to delay the flight. The flight instructor stated that the student was "upset" about the delay. He said that they conducted three takeoffs and landings together, which took about 30 minutes, and that he then exited the airplane for the student pilot's solo flight. The flight instructor reported that, when the student pilot departed on the solo flight, he witnessed a "beautiful" landing and then went inside to check on another student. He subsequently observed the student pilot conduct more landings, which he categorized as "good." A cell phone was located inside a thermally damaged case. The cell phone was found off; however, when activated, it indicated that a missed call occurred around the time of the accident. According to the manufacturer, the cell phone may overheat and shut down when exposed to high temperatures and will not register a call when powered off. Therefore, it is likely that the cell phone was on and that the pilot was aware of the incoming call when it was received. Although the investigation could not determine if the student pilot had become distracted by a cell phone call, the flight instructor further stated that the student was very focused on learning but that he was distracted when his cell phone rang. However, the flight instructor did not require the pilot to turn the cell phone off during flight. The flight instructor was in a position of authority and operational control and should have taken steps to ensure that the student was not distracted by the cell phone while flying.

Quoted verbatim from the NTSB record.

Other Piper PA-28 accidents

Date Aircraft Location Operator Outcome Died
9 Feb 2013 Piper PA-28-140
N6726J
Sunnyside, Washington, United States John Gilman Minor injuries -
8 Jun 2013 Piper PA-28-140
N7147R
Mosca, Colorado, United States - Fatal 2
14 Oct 2013 Piper PA 28-150
N5873W
Newport, New Hampshire, United States Bret Lukezic No injuries -
2 Oct 2013 Piper PA 28-180
N8084W
Benton Harbor, Michigan, United States - Minor injuries -
27 Jul 2013 Piper PA-28-181
N371JB
Columbus, Georgia, United States - No injuries -
9 Nov 2013 Piper PA 28-150
N5790W
Concordia, Kansas, United States Link Gerald L No injuries -

All 9,402 records for this type

Other accidents in this area

Date Aircraft Location Operator Outcome Died
19 Apr 2013 Cessna 210E
N111BK
Williamsburg, Virginia, United States Brown Joseph Daniel IV Fatal 2
7 Sep 2013 Fleet 7
N9433
Louisa, Virginia, United States - No injuries -
13 Sep 2013 Piper PA28 151
N4379F
Abingdon, Virginia, United States Ivanov Tochev T No injuries -
4 May 2013 Newgent Barry S6S
N388KB
Suffolk, Virginia, United States - Fatal 2
12 Aug 2013 Piper PA-28R-180
N4969J
Fredericksburg, Virginia, United States - No injuries -
17 Mar 2013 New Piper PA32-301FT
N32EV
Stafford, Virginia, United States Alberto Toledo Serious injuries -

All 170,864 records in United States