FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA13FA385 · Piper PA-28-161

29 Aug 2013 · Danville, VA, United States

General aviation Piper PA-28-161 · Accident: loss of control in flight on approach

From Danville Regional Airport (DAN) to Danville Regional Airport (DAN)

Report a problem

Event

NTSB case
ERA13FA385
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
1 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Piper PA-28-161

Aircraft type
Piper PA-28
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N9089N
Onboard fatalities
Unknown
Route
From Danville Regional Airport (DAN), Danville, VATo Danville Regional Airport (DAN), Danville, VA
Aircraft age
About 27 years (built 1986)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Approach · VFR go-around
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Loss of control in flight
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

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.

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.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA13FA385
Event ID
20130829X32417
Case number
ERA13FA385
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 14bf15986c81a4d6e5be0668a6dbe45a91b39b643933ed5d5a28ccb3cdd2c3c1; retrieved 2026-09-14T16:03:07.208Z.