Engine Fire Leads to Loss of Total Engine Power — Crash at a Lake

Advertisement

Flight context

N52854 departed Austin-Bergstrom International Airport on 16 June 2022. Shortly after takeoff, the pilot saw smoke in the cockpit and immediately told ATC that he wanted to return. The smoke increased rapidly, the instrument panel became difficult to see and the engine eventually stopped producing power.

The pilot opened the side windows and identified a lake below. With the engine no longer producing power and the aircraft already committed to an emergency landing, he ditched in Lady Bird Lake. The NTSB later traced the power loss to a fractured V-band clamp in the turbocharger exhaust system.

Timeline
About 14:00 CDT —
N52854 departed Austin-Bergstrom International Airport.
1.
Shortly after departure —
Smoke appeared in the cockpit and the pilot requested a return.
2.
Return toward Austin —
Smoke increased until the pilot could no longer see the instrument panel.
3.
Engine failure —
The aircraft lost total engine power.
4.
Emergency landing —
The pilot selected Lady Bird Lake as the landing area.
5.
Ditching —
The aircraft entered the lake and the pilot sustained serious injuries.
6.

The critical sequence

The emergency started as a smoke event, not as an obvious engine failure. Smoke in the cockpit is itself a serious warning because it can indicate fire, electrical burning or an engine-related source. The pilot's decision to tell ATC he wanted to return was therefore immediate and appropriate.

The mechanical sequence was later established through wreckage examination. The V-band clamp securing the turbocharger exhaust fractured. Hot exhaust gases then escaped over the engine accessory section and damaged multiple components, producing a fire and total loss of engine power.

The timing of the accident was significant because it occurred on the first flight after a 100-hour inspection. Maintenance records showed that an exhaust-system inspection had been recorded, but investigators could not establish whether the specific V-band clamp had been inspected or how long it had been in service.

The FAA had previously issued SAIB CE-18-07 recommending detailed inspection of V-band exhaust couplings at 100-hour intervals. A General Aviation Joint Steering Committee guide also discussed service-life limitations for some coupling designs. These documents provided important maintenance context without proving that a specific inspection had been missed on N52854.

ATC decisions during the event

ATC was notified quickly, but the emergency developed faster than a normal return could be completed. Once the pilot could no longer see the instruments and the engine stopped, the decision space was reduced to finding a survivable landing area. A lake is not an ideal surface, but at low altitude the relevant comparison is not lake versus runway; it is a controlled ditching versus an uncontrolled descent into obstacles.

Investigation and aftermath

The NTSB's probable cause was total loss of engine power due to an engine fire resulting from failure of the turbocharger exhaust clamp, which allowed hot exhaust gases to damage vital engine components. The investigation also documented the maintenance history and the FAA's prior guidance concerning these exhaust couplings.

The aircraft's post-accident condition also helped investigators reconstruct the event. The investigation examined the engine and associated components after the forced landing, while the pilot's account and ATC communications established the rapid progression from cockpit smoke to total power loss. The survivability of the lake ditching was closely tied to the pilot's decision to use an open-water landing area after the cockpit became difficult to operate. The result was a serious accident with no fatality.

The aircraft was being operated for a public-use mission, which made the pilot's workload and the rapidly changing cockpit environment particularly important. The investigation's findings show how quickly an apparently manageable smoke indication can become a total-power emergency when the source is within the engine compartment. There was little time to transition from troubleshooting and returning to the airport to selecting a survivable off-airport landing area.

What the record establishes

The NTSB investigation traced the engine-power loss to an in-flight fire involving the engine compartment. The pilot reported smoke shortly after departure and turned back toward Austin-Bergstrom. As the smoke intensified, cockpit visibility deteriorated to the point that the pilot could no longer see the instrument panel. The aircraft then lost total engine power, leaving the pilot to choose an emergency landing area. The resulting ditching in Lady Bird Lake was survivable, although the pilot sustained serious injuries. The investigation's mechanical evidence and the service-history context are more useful here than a generic description of an 'engine failure.'

What the sequence shows

This accident shows why an emergency landing decision should be based on the best achievable outcome rather than the perfect outcome. The pilot could not wait for a runway after the engine failed. The lake became the available surface, and the aircraft was successfully brought down there despite the serious hazards involved.

  • Treat cockpit smoke as an immediate emergency.
  • Tell ATC what you need early, before communications or visibility deteriorate.
  • A forced landing is about selecting the most survivable remaining option.
  • Maintenance inspection requirements for turbocharger exhaust couplings matter because clamp failure can lead to cascading engine damage.
  • Do not confuse a maintenance recommendation with proof of a specific maintenance error.

Accident facts

Date
16 June 2022
Aircraft
Cessna T206H
Registration
N52854
Location
Austin, Texas
Operation
Texas Parks and Wildlife Department public-use flight
Defining event
Engine fire / total engine-power loss
Outcome
Pilot seriously injured
Investigation
NTSB CEN22LA253

Sources

Sources
Primary investigation: NTSB CEN22LA253. Supporting sources: Aviation Safety Network or equivalent accident database for cross-reference; ATC/radar or docket material where released; contemporary newspaper/aviation reporting for context only. Primary-source facts and official probable-cause wording take precedence over secondary reporting.
Advertisement

Primary investigation record

Primary Investigation Reference

NTSB accident number: CEN22LA253

The weekly incident