ATL02LA173 · Piper PA-32RT-300
Piper PA-32RT-300 · Accident: loss of control in flight on approach
From Brunswick, GA to an unrecorded destination
Event
- NTSB case
- ATL02LA173
- 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
- 0 · 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-32RT-300
- Aircraft type
- Piper PA-32
- 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
- N607JW
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Brunswick, GATo not recorded
- Aircraft age
- Not recorded
- 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 pattern final
- First occurrenceThe 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
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Stall; Tree(s)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Pilot in command › Airspeed, not maintained
- Pilot in command › Remedial action, delayed
- Pilot in command › Stall, inadvertent
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
According to the pilot, he was taking a check-ride for his certified flight instructor's rating in single engine airplanes. He and the check pilot had completed several flight maneuvers and were conducting a simulated 180-degree power-off landing. The simulated maneuver was established for runway 04; the engine was operating at reduced power. The pilot recalled that approximately three quarters through the turn, the airspeed got slow and the sink rate increased. At approximately the same time, witnesses on the ground noticed that thee airplane had overshoot the final approach course for the runway. The pilot applied power to arrest the sink rate and to reestablish the final approach course. When the check pilot elected to take control of the airplane, he realized that there was not enough altitude to complete the recovery. Witnesses on the ground also observed the airplane as it collided with tops of tree short of the runway. One witness reported that the nose of the airplane pitched up and the pilot recalled that the left wing fell and the airplane collided with the ground in a nose low attitude. The airplane came to rest about 60 feet short of the runway surface and burst into flames. Neither pilot reported a mechanical problem with the airplane during the simulated emergency.
Probable cause
The pilot's failure to maintain airspeed during a simulated emergency landing, and his delayed remedial action that resulted in a stall, and an uncontrolled collision with trees. A factor was the check pilot's inadaquate supervision of the check ride.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL02LA173
- Event ID
- 20020930X05239
- Case number
- ATL02LA173
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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, coordinates. 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: 59e12128485355c9dcc9ac67f034c4283387f48ed2d462f146e2ce61841b0f72; retrieved 2026-09-21T09:34:23.270Z.