ERA12LA314
2012-04-28 · Lake Wales, Florida, United States · None · 1 aircraft · Status: Completed
Airport X07
Aircraft involved
Probable cause & findings
The student pilot’s decision to depart from an intersection with insufficient runway remaining for takeoff, which resulted in a rejected takeoff and subsequent runway excursion.
Factual narrative
On April 28, 2012, about 1300 eastern daylight time, a Piper PA-28-161, N746RA, registered to N70FT, Inc., operated by Airline Career Academy, collided with bushes during a rejected takeoff at Lake Wales Municipal Airport (X07), Lake Wales, Florida. Visual meteorological conditions prevailed at the time and no flight plan was filed for the 14 Code of Federal Regulations (CFR) Part 91 instructional flight from X07. The airplane sustained substantial damage and the student pilot, the sole occupant, was not injured. The flight was originating at the time of the accident. The student pilot stated that earlier that day he and his certified flight instructor (CFI) flew to X07 where he performed several touch-and-go landings. The CFI later reported that the student performed 3 uneventful landings and a go-around. On approach before the last landing the CFI simulated loss of engine power, and the student maneuvered the airplane in the traffic pattern and landed uneventfully. The CFI endorsed the student pilot’s logbook and medical certificate for solo flight, and the student pilot reported that he taxied to runway 06, and departed remaining in the traffic pattern performing an uneventful full-stop landing. While taxiing towards the approach end of runway 06, he missed the turn and taxied onto taxiway Delta, where he held short of the runway. The CFI later reported that he transmitted to the student to advise him not to depart from the intersection; however, the student stated he did not hear the transmission from the CFI. The student stated that based on his preflight planning, he knew he would need only 800 feet for takeoff and knew there was sufficient runway remaining to depart. He taxied onto the runway, and applied takeoff power. The airplane accelerated to rotation speed (63 knots) and he pulled on the control yoke to rotate, but the airplane did not rotate so he elected to abort the takeoff. The CFI further reported that the airplane became airborne flying for about 5 to 6 seconds only 3 to 4 feet above the runway. The student pilot stated that he was unable to bring the airplane to a stop on the runway, veered to the right and collided with bushes. According to the Federal Aviation Administration (FAA) inspector-in-charge, approximately 1,000 feet of runway remained at the intersection of taxiway Delta. A surface observation weather report taken at Bartow Municipal Airport at 1215 eastern daylight time indicated the wind was from 080 degrees at 8 knots, the visibility was 10 miles, and scattered clouds existed. The temperature and dew point were 28 and 17 degrees Celsius respectively, and the altimeter setting was 30.10 inches of Mercury. The accident site was located approximately 9 nautical miles and 294 degrees from X07. After the accident the engine was operated under supervision of an FAA Inspector to full static rpm with no discrepancies noted The FAA Inspector also inspected the main landing gear brakes and found no evidence of pre-accident failure or malfunction. After observing the student pilot’s successful performance of several takeoffs and landings, the flight instructor exited the airplane and briefed the student pilot for solo traffic pattern work. The student pilot taxied to the end of the runway and performed the first takeoff and landing without incident. The student pilot then began his second takeoff at the runway’s intersection with a taxiway, which left about 1,000 feet of runway remaining. The flight instructor advised the student pilot on the common traffic advisory frequency not to perform an intersection departure. The student pilot stated that he did not hear the radio call. The student pilot initiated the takeoff but stated the airplane was not climbing properly and aborted the takeoff. With insufficient runway remaining to stop and with obstacles ahead, the student pilot veered right then collided with bushes. Postaccident examination and an engine run revealed no mechanical malfunctions or failure that would have precluded normal operation. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
FAA avdata. C = Cause, F = Factor.
- C Aircraft-Aircraft oper/perf/capability-Aircraft capability-Takeoff distance-Incorrect use/operation - C
- C Personnel issues-Action/decision-Info processing/decision-Decision making/judgment-Student pilot - C
Verbatim from NTSB's published report. Source file
NTSB_2012_ERA12LA314.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Search this event elsewhere
External sources are reported, not agency: signal that something happened, not fact about what happened.
- TallyAero Live Wire Aviation press
- NTSB CAROL Agency ↗
- NTSB Docket Agency ↗
- Aviation Safety Network Aviation press ↗
- Kathryn's Report Aviation press ↗
- Aviation Herald Aviation press ↗
- AVweb Aviation press ↗
- Pilots of America Community ↗
- Reddit /r/flying Community ↗
- FlightAware Aviation press ↗
- AOPA accident database Aviation press ↗
- Google News News ↗
- DuckDuckGo News ↗
Related research
Matched on aircraft type or causal vocabulary (runway excursion, go-around). All research papers
- SKYbrary (Eurocontrol) 2024 · SKYbrary article Runway Excursion — SKYbrary Knowledge Base
SKYbrary runway excursion review — RE-OE (overruns) + RE-LO (lateral). Risk drivers: long landing, high approach speed, contaminated surface, tailwind, mis-set autobrakes.
- NASA NTRS 2025 · Conference Paper A Training Study to Improve Monitoring During A Go-Around
As part of an FAA program to improve go-around (GA) safety, we were asked to determine if we could improve the performance of the Pilot Monitoring (PM) during a GA maneuver.
- Flight Safety Foundation 2024 · FSF / AeroSafety World Go-Around Safety Forum Findings
Foundation Go-Around Safety Forum technical findings — examines why pilots fail to execute go-arounds when criteria are met (stabilized approach gate not met, energy state out of envelope, traffic con…
- Semantic Scholar 2022 · Article (Journal of Safety Research) Go-around accidents and general aviation safety.
INTRODUCTION Changes in General Aviation (GA) accident rates, specifically in the go-around phase, are examined by comparing the number of accidents, the proportion of fatal accidents, and the proport…
- Semantic Scholar 2021 · Article (Aerospace) Classification and Analysis of Go-Arounds in Commercial Aviation Using ADS-B Data
Go-arounds are a necessary aspect of commercial aviation and are conducted after a landing attempt has been aborted. It is necessary to conduct go-arounds in the safest possible manner, as go-arounds …
- NASA NTRS 2021 · Accepted Manuscript (Version with final changes) Go-Around Criteria Refinement for Transport Category Aircraft
Presently, airline pilots are trained to go around if, when lower than 500 ft above the ground, they are outside of a handful of parameters such as airspeed, position, and rate of descent.