FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC00LA262 · Cessna 150L

14 Sept 2000 · Salem, OH, United States

Cessna 150L · Accident: partial loss of engine power (non-mechanical) during initial climb

From Salem Airpark Inc Airport (38D) to an unrecorded destination

Report a problem

Event

NTSB case
NYC00LA262
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 150L

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
N10825
Operator
Unknown
Onboard fatalities
Unknown
Route
From Salem Airpark Inc Airport (38D), OHTo not recorded
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
Initial climb
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 (non-mechanical)
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
Pole
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

  • Reason for occurrence undetermined

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

NTSB narrative

The pilot reported that after takeoff while climbing through an altitude of 200-300 feet, the engine began to run rough, but never quit. There was insufficient power to maintain altitude and he attempted a forced landing on a road. The right wing struck a telephone pole and the airplane came to rest in field adjacent to the road. The pilot reported that he checked the carburetor heat prior to takeoff and observed a drop in engine rpm. When the engine roughness developed, he applied carburetor heat and there was no change in engine condition, after which he turned it off. Examination of the airplane by a FAA inspector found no evidence of contamination in the fuel system or blockage in the air intake system. Spark was obtained from both magnetos. A check of the temperature/dew point from the closest station, 21 miles away revealed a relative humidity of about 55 percent.

Probable cause

A partial power loss for undetermined reasons.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC00LA262
Event ID
20001212X22060
Case number
NYC00LA262
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: 07385836d0ca3a19e1c72665b815fc12440cb4f984d97a4008a1e2591b6cf704; retrieved 2026-09-22T12:27:05.417Z.