ERA10LA235 · Cessna 152
Cessna 152 · Accident: loss of engine power (total) en route
From Lakeland Linder International Airport (LAL) to North Perry Airport (HWO)
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- ERA10LA235
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Cessna 152
- Aircraft type
- Cessna 152
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N5499B
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route Narrative disagrees
- From Lakeland Linder International Airport (LAL), Lakeland, FLTo North Perry Airport (HWO), Hollywod, FL
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- En route · cruise
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Loss of engine power (total)
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Wire
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft handling/service
- Organizational issues › Management
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
About one week prior to the accident, the pilot noticed fuel leaking from the accident airplane’s carburetor. He informed a mechanic responsible for the airplane, who assured him that the airplane was fine and that the leak could be stopped by knocking a screwdriver against the carburetor. The pilot did as instructed, and the leak stopped. The day before the accident, the pilot asked the mechanic whether any maintenance was conducted on the carburetor, and the mechanic informed him that no maintenance was conducted, because it was not necessary. The pilot then rented the airplane from the operator and conducted an uneventful flight to his destination. The next day, during the cruise portion of the return flight, the engine rpm suddenly decreased below 2,000 rpm. The pilot manipulated the mixture and carburetor heat controls, and verified that the ignition switch and master switches were appropriately set. The rpm continued to decrease, and about 30 seconds after the onset of the rpm drop, the engine stopped producing power. The pilot initiated a forced landing on a road, and the airplane was substantially damaged when the left wing struck a fence post.
Meteorological conditions recorded about 25 miles from the accident location indicated the conditions were conducive to carburetor icing with the engine at glide power, but not at cruise power. On-scene examination of the airplane revealed that sufficient, uncontaminated fuel was available, and that the fuel selector valve was properly set. The engine was test run on the airplane, at various rpm settings, with no anomalies noted. The carburetor was removed and further examined. When fuel was introduced via the fuel inlet, the carburetor immediately started flooding and leaking from the venturi, which was consistent with an open float valve. Further examination and teardown revealed multiple anomalies, including internal contamination and corrosion, excessive wear, incorrect parts, incorrectly installed parts, and a damaged float assembly. Some of the internal contaminants floated, and some sank in the fuel, which allowed for the possibility that the contaminants could prevent full closure of the float valve. The excessive wear and twisted float assembly could also prevent proper float operation. Improper float valve or float operation could result in either intermittent abnormal engine operation or a complete loss of power.
Probable cause
The operator's failure to correct known deficiencies with the carburetor, which resulted in a complete loss of engine power and subsequent forced landing by the pilot. Also causal was the operator's decision to rent the airplane in an unairworthy condition.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA10LA235
- Event ID
- 20100419X50320
- Case number
- ERA10LA235
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 282a992429826ff9d8f63022a4d29a23d8c99b9eb1519b9c13298a65e7f80437; retrieved 2026-09-15T13:52:31.639Z.