The U.S. aircraft register, updated daily
Accidents · NTSB NYC03FA129 · Final report

Cessna 150H accident near Pittsfield, Maine, June 12, 2003

On June 12, 2003 at about 2:30 pm local time, a Cessna 150H, registered N6566S, was destroyed in an accident near Pittsfield, Maine (Pittsfield Municipal Airport). It was an instructional flight under general aviation rules (Part 91). 2 people were killed. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

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.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
June 12, 2003 · about 2:30 pm local time
Place
Pittsfield, Maine · Pittsfield Municipal Airport · map
Type
Accident
Injuries
2 people were killed.
Weather
visual conditions (good weather)
Aircraft
Cessna 150H · all 150Hs on the register
Registration
N6566S · no longer on the register · serial 15067366
Damage
Destroyed
Flight
Instructional flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

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..."

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

Flight instructor

  • Certificate: flight instructor, commercial pilot, private
  • Ratings: multi-engine land; single-engine land; instructor: airplane single-engine; instrument: airplane
  • Flight time: 1,565 hours in all; 12 in the last 30 days; 1,456 as pilot in command; 280 on instruments
  • Last flight review: January 7, 2003
  • Medical certificate: Class 2 (valid medical--w/ waivers/lim.)
  • Seat: rgt
  • Injury: fatal

Pilot

  • Certificate: commercial pilot
  • Ratings: multi-engine land; multi-engine sea; single-engine land
  • Flight time: 478 hours in all
  • Medical certificate: Class 3 (valid medical--w/ waivers/lim.)
  • Seat: left
  • Injury: fatal

The aircraft

  • Airframe total time: 4,224 hours
  • Last inspection: annual inspection, April 1, 2003
  • Maximum gross weight: 1,600 lb
  • Seats: 2
  • Landing gear: fixed
  • Engine: Continental O-200 (piston); 0 hours total
  • Fire on the ground

The flight

  • Departed from: 2B7 Piitsfield ME at 2:30 pm
  • Destination: 2B7
  • Flight plan: none
  • Runway 01, 3,998 ft by 150 ft
  • A second pilot was aboard

Weather at the time

  • Light: daylight
  • Wind: from 020° at 6 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 64°F (18°C), dew point 50°F (10°C)
  • Altimeter: 29.94 inHg
  • Observation at 1:53 pm from BGR, 22 miles away

Injuries

FatalSeriousMinorNone
Crew2

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.