FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA24LA197 · Beech F35

27 Apr 2024 · McAlpin, FL, United States

Beech F35 · Accident: runway excursion during takeoff

From an unrecorded airport to Palm Beach County Park Airport (LNA)

Report a problem

Event

NTSB case
ERA24LA197
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
0
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

Beech F35

Aircraft type
Beechcraft 35
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
N3880B
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo Palm Beach County Park Airport (LNA), Palm Beach, FL
Aircraft age
About 69 years (built 1955)
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
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
Destroyed

Cause areas

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

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

NTSB narrative

The pilot and his passenger were preparing for a cross-country flight. After a routine preflight inspection and engine start, the pilot taxied to runway 27, which was 2,644 ft-long and comprised of turf. The grass was “mid height” and wet from the morning dew. The pilot commonly used a “hump” in the runway as a go/no-go decision point, which was about midfield. During the takeoff roll, he scanned his tablet device for speed and noted 47 knots; 52 knots was stall speed, configured. As the takeoff roll continued, he tried to “pop” the airplane off the ground and into ground effect; this attempt was unsuccessful. He realized that the airplane would not become airborne and it departed the end of the runway, collided with a berm, and spun around to a stop. A postaccident fire ensued and the pilot and passenger egressed the airplane without injuries. Despite attempts to extinguish the fire, it progressed and eventually consumed the fuselage. An inspector with the Federal Aviation Administration reported that the airplane was destroyed. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation. He also reported that performing the “no go” decision at the hump in the runway would have prevented the accident.

Probable cause

The pilot’s inadequate preflight planning and failure to abort the takeoff at the predetermined decision point.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA24LA197
Event ID
20240430194172
Case number
ERA24LA197
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, 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: 375293f0f98010527063c2b6fd2ad52d80fd317cccc658c7954da5459a7c73e2; retrieved 2026-09-16T18:42:47.761Z.