Fuel Exhaustion: Cessna 172N Crash-Landing Near Grant-Valkaria

The event in context

On the evening of 17 November 2025, a 1979 Cessna 172N Skyhawk, N6124D, was on a personal flight that included a stop at Okeechobee County Airport. The private pilot, the sole occupant, later reported the flight had departed with full tanks. After a touch-and-go at Okeechobee, the aircraft continued toward Melbourne — and the engine lost power.

The pilot worked through the standard emergency sequence: establishing best-glide speed around 65 knots, checking the mixture and carburetor heat, verifying the magnetos, and attempting a restart. None of it brought the engine back. With no airport in reach, he set up for a forced landing on Babcock Street near Grant-Valkaria, Florida — a road, not a runway, but the best option available. After touchdown, he had to maneuver to avoid a car on the road; the right wing clipped a traffic sign in the process, and the aircraft came to rest in a drainage ditch, nose pitched upward. He walked away with minor injuries. The airplane didn't fare as well — substantial damage to both wings and the fuselage.

The NTSB preliminary account identifies N6124D as a 1979 Cessna 172N involved in a forced landing near Grant-Valkariafter engine roughness progressed to power loss. The pilot, the sole occupant, reported that the aircraft had departed with full tanks and had made a touch-and-go at Okeechobee before continuing toward Melbourne.

Reconstructing this flight

The NTSB's preliminary report on the accident documents the pilot's account and the physical damage, but a final probable-cause determination hasn't been issued yet. Fuel exhaustion or starvation is the leading working theory given the sequence described — engine roughness building to full power loss with no obvious mechanical trigger — but investigators are still examining the fuel system, remaining fuel quantity, and any possible mechanical contribution before that gets confirmed.

What stands out here isn't the failure itself but the landing that followed it. Forced landings after power loss are among the most heavily practiced emergency procedures in general aviation training, precisely because engines can and do quit with no warning. Choosing a road over trees or open water, then actively steering around a car mid-rollout rather than freezing up, is exactly the kind of decision-making that separates a survivable outcome from a fatal one. The gap between the pilot's minor injuries and the aircraft's substantial damage says a lot about how much of the impact energy was managed rather than simply absorbed.

Okeechobee County → Melbourne area; forced landing near Palm Bay/Grant-Valkaria, FL

The emergency sequence is worth preserving because it shows the pilot transitioning through the checklist: best glide, mixture and carburetor heat checks, magneto checks and restart attempts. None restored sustained power. The pilot then selected Babcock Street for the forced landing and had to maneuver around a vehicle during the rollout before the aircraft entered a drainage ditch.

What the evidence establishes

NTSB preliminary report; fuel exhaustion/starvation suspected, final cause pending.

The investigation remains preliminary. Fuel exhaustion or starvation may be considered, but the final cause should not be stated until the NTSB completes its examination of the fuel system, engine and remaining evidence. The strongest current lesson is the quality of the forced-landing response rather than a speculative explanation for why the engine stopped.

From Engine Roughness to a Forced Landing

The reconstructed sequence can be read as a chain of six decision points: Okeechobee stop → Engine roughness → Power loss → Restart checks → Road forced landing → Drainage-ditch stop. Each step changed the aircraft’s available options. The important analytical point is not to isolate the final impact from the preceding events; the final outcome was produced by the accumulation of the earlier changes in aircraft state, position, workload and available escape options.

The ATC/radar perspective is most useful when it is synchronized with the aircraft evidence. In this case the critical transition is the move from okeechobee stop to drainage-ditch stop. Once the aircraft reached the later stages of the sequence, the crew had fewer safe alternatives than they had at the beginning. That is the operational value of reconstructing the event rather than describing it only from the final crash scene.

The Power-Loss Sequence

The decisive safety issue in this incident was specific to the sequence: Engine roughness; Power loss; Restart checks. Treating those events as isolated anomalies would miss the way they interacted.

Sources and investigation material

• https://data.ntsb.gov/
• https://www.youtube.com/watch?v=l0xX2uURqq0

Accident Facts