ATL96LA065

NTSB accident investigation · Cessna 152 · Flamingo, FL · March 13, 1996

Accident · No injuriesLimited investigationFinal report
Date
March 13, 1996, 16:47 local (20:47 UTC)
Place
Flamingo, FL
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Enroute
Aircraft
N6174QCessna 152
Weather
Visual (VMC) · Day
Status
Completed · report October 4, 1996
Report
Approved by Office Director
FAA report
19960313003959A
Case key
3708

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

Probable cause

The student pilot's selection of unsuitable terrain for a precautionary landing. Failure of the #3 exhaust tube was a related factor.

Sequence of events

NTSB’s coding before 2008: each occurrence and phase of flight, and the causes and factors under it. The codes are defined in NTSB’s coding manual.

Airframe/component/system failure/malfunctionCruise - normal
Exhaust system,stack - failureFactor
Nose overEmergency landing
Precautionary landing - performedPilot in command
Terrain condition - softFactor
Unsuitable terrain or takeoff/landing/taxi area - selectedPilot in commandCause

Analysis

The student pilot stated he was in cruise flight at 3,500 feet, when the airplane engine began making a loud continuous noise. He made a precautionary landing in an open field. During the landing roll out, the airplane encountered soft terrain and nosed over. Examination of the airplane, revealed the #3 exhaust tube had failed (separated) below the weld joint. When the student pilot was informed of the examination results, he said he misdiagnosed the perceived emergency.

Factual narrative

On March 13, 1996, at about 1647 eastern daylight time, a Cessna 152, N6174Q, registered to Alternate Flying Club, operated by Fort Myers Airways Inc., as a 14 CFR Part 91 instructional flight, made a precautionary landing in the vicinity of Flamingo, Florida. Visual meteorological conditions prevailed and a VFR flight plan was filed. The airplane nosed over on soft terrain on landing roll out and sustained substantial damage. The student pilot reported no injuries. The flight originated from Marathon, Florida, about 37 minutes before the accident.

The student pilot stated, he was in cruise flight at 3,500 feet when the aircraft engine began making a loud continuous noise. He made a precautionary landing, and the airplane nosed over during the landing roll out.

Examination of the airplane, revealed the number 3 exhaust tube had separated below the weld joint. There was no evidence of a precrash mechanical failure or malfunction of the engine assembly. When the student pilot was informed of the source of the loud noise, he stated, he used improper flight planning and decision when he misdiagnosed the perceived emergency, which resulted in an unnecessary precautionary landing.

An NTSB Pilot/Operator Aircraft Accident Report was mailed to Fort Myers Airways Inc., on March 14, 1996. The certified letter was received on March 22, 1996. No reply was received by the NTSB.

Aircraft

Registration
N6174Q
Reported as
Cessna 152
Category
Airplane
Serial number
15285183
Airframe hours
9,248
Engine
Lycoming O-235, 110 horsepower, reciprocating
Damage
Substantial damage
Flight
Instructional · Part 91
Operator
Ft. Myers Airways, Inc.
Registered owner
Alternative Flying Club, Inc.
Airworthiness certificate
Standard, Utility
Last inspection
100 hour · March 1, 1996 · 23 hours before
Departed
MTH · Marathon, FL
Destination
OBE · Okeechobee, FL
Flight plan
VFR

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Flight crew

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
30
Certificate
Student
Medical
Class 3, Valid Medical--no waivers/lim.
Seat
Left
Flight hours
60 total

Weather

Conditions
Visual (VMC) · Day
Wind
310° at 4 knots
Visibility
10 statute miles
Lowest ceiling
None
Temperature
66 °F, dew point 55 °F
Altimeter
30.00 inHg
Observed at
MTH, 25 nm away

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.