• Skip to primary navigation
  • Skip to main content
General Aviation News

General Aviation News

Because flying is cool

  • Pictures of the Day
    • Submit Picture of the Day
  • Stories
    • News
    • Features
    • Opinion
    • Products
    • NTSB Accidents
    • ASRS Reports
  • Comments
  • Classifieds
    • Place Classified Ad
  • Events
  • Print Archives
  • Subscribe
  • Show Search
Hide Search

Pilot Crashes After Ignoring Go/No-Go Decision Point

By General Aviation News Staff · April 2, 2026 · 2 Comments

The pilot and his passenger were preparing for a cross-country flight in the Beech F35. After a routine preflight inspection and engine start, the pilot taxied to Runway 27 at the airport in McAlpin, Florida, which was turf and 2,644 feet long. 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 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, but 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 post-accident fire ensued. The pilot and passenger were able to get out of the airplane without injuries.

Despite attempts to extinguish the fire, it progressed and eventually consumed the fuselage. An FAA inspector 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.

NTSB Identification: 194172

To download the final report. Click here. This will trigger a PDF download to your device.

This April 2024 accident report is provided by the National Transportation Safety Board. Published as an educational tool, it is intended to help pilots learn from the misfortunes of others.

Reader Interactions

Share this story

  • Share on Twitter Share on Twitter
  • Share on Facebook Share on Facebook
  • Share on LinkedIn Share on LinkedIn
  • Share on Reddit Share on Reddit
  • Share via Email Share via Email

NTSB Report - One Accident. One Lesson.

NTSB Report delivers one NTSB accident report per email, Monday through Friday — so pilots can learn from real-world outcomes. Free. No spam. Unsubscribe anytime.

This field is for validation purposes and should be left unchanged.


Curious to know what fellow pilots think on random stories on the General Aviation News website? Click on our Recent Comments page to find out. Read our Comment Policy here.

Comments

  1. Michael A. Schulz says

    April 4, 2026 at 8:26 am

    It looks like the firewall did a good job protecting the engine from the fire.

    Reply
  2. LT says

    April 3, 2026 at 4:58 am

    Pulling a plane into the air will normally end this way! You must let it fly when it’s ready.
    Any time your pulling on the yoke or stick your headed for trouble, stall/spin.

    Reply

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

© 2026 Flyer Media, Inc. All rights reserved. Privacy Policy.

  • About
  • Advertise
  • Comment Policy
  • Submit Press Release
  • Contact Us
  • Privacy Policy
  • Writer’s Guidelines
  • Photographer’s Guidelines