No fatalities

8 May 2025: CESSNA 172 E (N5405T) — EnvySky — Florida City, FL

Florida City, FL, United States

On 8 May 2025, a CESSNA 172 E (registration N5405T) operated by EnvySky was involved in an aviation accident near Florida City, FL. No fatalities were reported. Investigators recorded the probable cause as: The commercial pilot’s improper fuel management, which resulted in a loss of total engine power due to fuel starvation. This summary draws on records from NTSB; 12 related events involving the same aircraft type or operator are linked below.

SourcesNTSBPrimary reportUpdated 1778583330Data APIEditorial standards

On May 8, 2025, a Cessna 172E (N5405T) sustained substantial damage during a forced landing in a swamp near Florida City, Florida. The commercial pilot was uninjured; the private pilot sustained minor injuries. Postaccident examination revealed fuel imbalance and fuel selector placard differences.

Accident Overview

On May 8, 2025, about 1930 eastern daylight time, a Cessna 172E airplane, registration N5405T, was substantially damaged when it came to rest inverted in a swamp near Florida City, Florida. The commercial pilot, occupying the left seat, was not injured, while the private pilot in the right seat sustained minor injuries. The flight was conducted under Title 14 Code of Federal Regulations Part 91 as a personal flight.

Flight Details

The purpose of the flight was to build flight experience, with the commercial pilot practicing simulated instrument meteorological conditions and the private pilot acting as a safety pilot. Departing North Perry Airport (HWO) in Hollywood, Florida, at about 1733, the airplane carried 38 gallons of fuel. The planned route took the pilots out over the Florida Keys and back, with an intended destination of Naples Municipal Airport (APF) in Naples, Florida.

Engine Power Loss

Near the destination, while the commercial pilot was making a left turn, the engine became silent, and the engine speed indicator showed less than 1,000 rpm. The commercial pilot applied carburetor heat, but the engine did not respond. She then transferred control of the airplane to the private pilot so she could attempt an engine restart using the Engine Start checklist. After two unsuccessful restart attempts, the private pilot executed a forced landing.

Forced Landing

The forced landing occurred in a swampy area, during which the airplane nosed over and came to rest inverted. Both pilots reported that there was no jolt or vibration preceding the engine power loss. They also stated that the fuel selector handle was positioned to Both for the entire flight. After the accident, the private pilot moved the fuel selector to the Off position as part of securing the airplane, which also included turning off the master switch and ignition key.

Postaccident Examination

An examination of the wreckage three days later revealed substantial damage to the empennage. The left wing fuel tank contained only residual fuel, while the right wing fuel tank vent continued to leak fuel, indicating that several gallons remained in that tank. Notably, the fuel selector placarding on the 1964 Cessna model 172E differed from other Cessna model 172 airplanes and was described as not intuitive.

Fuel Selector Confusion

When queried about the correct selector position for Both fuel tanks, the commercial pilot indicated it should be at 11 o'clock. However, the Both selection corresponds to the 12 o'clock position; the 11 o'clock position lies between the Both and Left fuel tank selections. Additionally, the private pilot moved the fuel selector handle to the 4:30 position (between Off and Right) to turn the fuel off, but the Off position is at 6 o'clock. The commercial pilot remarked that greater awareness of specific aircraft model differences—between the Cessna 172E and the Cessna 172S—could have prevented the accident.

Engine Test Run

The wreckage was transported to a recovery facility, where a successful test run of the engine was performed. Once fuel was supplied to the engine, it started on the airframe and ran continuously without issue.

Contributing factors

PilotFluid management