FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC03FA129 · Cessna 150H

12 Jun 2003 · Pittsfield, ME, United States

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

From Pittsfield Municipal Airport (2B7) to 2B7

Report a problem

Event

NTSB case
NYC03FA129
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
2 · 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 150H

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
N6566S
Operator
Unknown
Onboard fatalities
Unknown
Route
From Pittsfield Municipal Airport (2B7), Piitsfield, METo 2B7
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
Fuel contamination; Stall/spin
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Powerplant › Surge

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The flight instructor and a certificated pilot were conducting a local instructional flight. According to a witness, he heard the aircraft power up and start its take off roll. He then heard the engine "skip," which made him look up and observe the airplane in a steep left turn with a nose high attitude. At the same time he heard the engine noise decrease "like the throttle was pulled to idle." When the airplane was about parallel with the "old runway 28," the witness observed the tail swing aggressively to the right, and at the same time, he heard the engine rev-up. The airplane then stalled, and began to spiral downward counter-clockwise, before impacting the asphalt and bursting into flames. Several other witnesses had observed the airplane flying 30 minutes prior to the accident. The local training flight was the airplane's first flight since the annual inspection was performed 2 months prior to the accident. Inspection of the carburetor revealed contaminated residual fuel and contamination of the fuel screen. Examination of the fuel sample and the fuel screen revealed that the fuel sample contained water, copper sediments, and varnish. The fuel sample was consistent with "old fuel." Residue observed on the fuel screen was consistent with grease. Review of maintenance records revealed that the airplane's most recent annual inspection was performed on April 1, 2003. The work accomplished during the annual inspection included the draining of the fuel sumps, and inspection of the fuel screen. The maintenance records also contained a checklist for a 100 hour inspection, dated March 31, 2003, and a discrepancy sheet log. Included in the checklist was, "Drain carburetor float bowl - resafety plug... Remove fuel inlet screen from carb or injection throttle body, clean, reinstall and safety." The checklist items were initialed by a mechanic, and additionally by an inspector. Included in the discrepancy sheet log was an entry which stated, "carb float bowl drain froze in place, fab tool to remove and removed drain plug." The entry was initialed by a mechanic. According to 14 CFR Part 43 Appendix D - Scope and Detail of Items (as Applicable to the Particular Aircraft) To Be Included in Annual and 100 Hour Inspections, "Each person performing an annual or 100 hour inspection shall inspect (where applicable) components of the engine and nacelle group..."

Probable cause

The inadvertent resumption of power during a forced landing that resulted in a subsequent spin. Factors related to the accident were the CFI's delayed remedial action, the loss of engine power due to contaminated fuel, an obstructed fuel screen, and the inadequate annual inspection performed by maintenance personnel.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC03FA129
Event ID
20030625X00954
Case number
NYC03FA129
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, coordinates. 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: 31ff45f59a29d31471afe8f7d55176003b37b73608c5a8b2bcfcdc2deeb4e76b; retrieved 2026-09-20T19:10:10.206Z.