ATL05CA080 · Piper J4E
Piper J4E · Accident: loss of control in flight during takeoff
From Akron, AL to an unrecorded destination
Event
- NTSB case
- ATL05CA080
- 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 J4E
- Aircraft type
- Piper J4
- 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
- N35920
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Akron, ALTo 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
- Takeoff
- 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/mush
- 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 › Aborted takeoff, delayed
- Pilot in command › Airspeed, inadequate
- Pilot in command › Lift-off, premature
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot stated he started the takeoff roll on runway 19 with no noticeable head wind. The airplane accelerated down the runway to a point where he normally rotates the airplane at 50 mph. The pilot observed the airspeed indicator slightly below 50 mph, applied aft pressure on the flight controls, and the airplane became airborne. The pilot observed a decrease in airspeed and knew he could not clear trees located off the departure end of the runway. The pilot aborted the takeoff by reducing power. The airplane touched back on the ground and the pilot applied aft pressure on the flight controls. The airplane became airborne and touched back down on the ground. The pilot started a left turn maneuver to avoid the trees and applied brakes. The pilot stated he lost directional control, the nose and right wing collided with the ground. The pilot further stated there were no anomalies noted with the airframe, flight controls, or engine assembly.
Probable cause
The pilot's premature liftoff and his failure to attain adequate airspeed which resulted in a stall/mush. Also causal was the pilot's delay in aborting the takeoff.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL05CA080
- Event ID
- 20050601X00690
- Case number
- ATL05CA080
- 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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2005-05-16.
- API snapshot SHA-256: 4bdfe91a1dc05f05121f55cbc1325ecae279ec4bb06b3e7f64599e6fcc57cd08; retrieved 2026-09-22T05:54:58.642Z.