ERA21LA181 · Piper PA-32R-300
SouthEast Aircraft Leasing Piper PA-32R-300 · Accident: runway excursion during takeoff
From an unrecorded airport to DeKalb Peachtree Airport (PDK)
Event
- NTSB case
- ERA21LA181
- 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
- Event fatalities
- Unknown
- 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-32R-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
- N1664H
- Operator
- SouthEast Aircraft Leasing
- Onboard fatalities
- Unknown
- Route
- From not recordedTo DeKalb Peachtree Airport (PDK), Chamblee, GA
- Aircraft age
- About 44 years (built 1977)
- 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
- Takeoff · rejected takeoff
- 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
- Runway excursion
- 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Action/decision
- Personnel issues › Task performance
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 owner of the airplane, who was the non-flying pilot seated in the right seat, prior to takeoff an engine runup was completed with no anomalies observed, and in addition, the wind sock indicated a calm wind. The owner reported that he and the pilot flying briefed the procedures for a short-field takeoff, back taxied to the end of the runway, and applied the brakes. The pilot flying increased the engine power, released the brakes, and began the takeoff roll. He attempted to rotate; however, the stall warning sounded, and he lowered the nose to accelerate more. The pilot flying again attempted to rotate, the stall warning horn sounded, and at this point the owner took the controls, calling for an aborted takeoff. The owner reduced engine power and applied the brakes; however, the airplane continued off the end of the runway and struck a ditch. A postaccident fire ensued, and the pilots and passenger egressed the airplane without injury. During the accident sequence, the airplane incurred substantial damage to the wings and fuselage. The owner reported no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation. According to the airplane’s pilot operating handbook, the flaps should be set to the second notch, or 25° for a short field takeoff. After the accident, a Federal Aviation Administration inspector examined the airplane and noted that the flaps were in the first notch, or 10° position. Further, the owner acknowledged that, “…it is possible that the flaps were not set correctly on takeoff.” Given this information, it is likely that the pilot did not properly configure the airplane, which is why the airplane was unable to become airborne during the short field takeoff attempt.
Probable cause
The flying pilot’s failure to configure the flaps for a short field takeoff and delayed decision to abort the takeoff, which resulted in a runway overrun.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA21LA181
- Event ID
- 20210409102900
- Case number
- ERA21LA181
- 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, coordinates, cause areas. 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: 7a09521ef922684743136f0519ab0bc14d4508a58591bea7b101d2525aa10b4d; retrieved 2026-09-16T13:56:27.110Z.