FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA85LA119 · Cessna 150M

18 May 1985 · Santa Rosa, CA, United States

Cessna 150M · Accident: partial loss of engine power (mechanical failure) en route

From Charles M. Schulz Sonoma County Airport (STS) to Charles M. Schulz Sonoma County Airport (STS)

Report a problem

Event

NTSB case
SEA85LA119
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
0
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 150M

Aircraft type
Cessna 150
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
N704UV
Operator
Unknown
Onboard fatalities
Unknown
Route
From Charles M. Schulz Sonoma County Airport (STS), Santa Rosa, CATo Charles M. Schulz Sonoma County Airport (STS), Santa Rosa, CA
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
First occurrenceThe 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
Partial loss of engine power (mechanical failure)
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

  • Carburetor heat control › Inoperative
  • Weather condition › Carburetor icing conditions

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

WHILE ON A SHORT LOCAL FLIGHT TO A COSTAL AREA AND RETURN. THE ENGINE LOST SOME POWER. CARBURETOR HEAT WAS APPLIED BUT NO INCREASE IN POWER WAS NOTED. THE PLT THEN SET UP A GLIDE WITH INTENTIONS OF MAKING A LANDING ONTO THE BEACH AREA. AT ABOUT 500 FEET M.S.L. POWER WAS RESUMED AND THE PLT ELECTED TO CLIMB TO 2,000 FEET M.S.L. WITH THE INTENTIONS OF RETURNING TO THE DEPARTURE AIRPORT. OVER RUGGED TREED TERRAIN A POWER LOSS WAS AGAIN NOTED. APPLICATION OF CARBURETOR HEAT HAD NO EFFECT UPON THE ENGINE. A FORCED LANDING WAS MADE INTO TALL HAY. INSPECTION OF THE ENGINE REVEALED THAT THE ENGINE COMPARTMENT CARBURETOR AIR HEAT CONTROL LEVER WAS BROKEN WITH THE CONTROL CABLE DISCONNECTED AND THE HOT AIR DOOR JAMMED IN THE COLD POSITION.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record SEA85LA119
Event ID
20001214X36620
Case number
SEA85LA119
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 79f36a12b75e56b27f1456810559f953dd1b71a5cd1f4f51b8484ba269141e1f; retrieved 2026-09-23T17:37:10.074Z.