OpenAirDocs.org

19960712017959A

Accident · Destroyed
Open the Markdown

FAA accident report · Cessna 150H · Parker, SD · July 12, 1996

FAA Aviation Safety Information Portal

© OpenStreetMap
Date
July 12, 1996 · 17:30 local
Place
Parker, SD
Phase of flight
Starting Engines
Operating rules
General operating rules (Part 91)
Damage
Destroyed
Aircraft
N50104
NTSB investigation
NTSBCHI96LA241
Reported as
Cessna 150H
Reported engine
AMTR O200
People aboard
2
Fatal injuries
0
Pilot’s flight hours
80 total80 in this make and model22 in the last 90 days
N50104Registration cancelled Oct 11, 1996 · Cessna 150HS/N 15069064Airframe modelCessna 150H

From the FAA’s Accident/Incident Data System (AIDS), through its Aviation Safety Information Portal, as reported. The NTSB investigates accidents separately, and its record of an accident is the fuller one. The aircraft is matched to the registry by N-number and event date, checked against the reported make and model; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

What happened

The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.

Pilot attempted to start engine, caught on fire and burned. (.4)the pilot reported that he had landed about 30 minutes prior to the accident. When he attempted to start the engine before the next planned flight, it 'turned over but wouldn't start.' He pumped the throttle three times. He said he engaged the starter, the engine 'popped through the carb,' and fire ignited in the engine compartment. The pilot and passenger egressed the airplane uneventfully. The emergency procedure published in the pilot's operating handbook (for engine fire during start on ground), specified 'cranking-continue, to get start which would suck the flames and accumulated fuel through the carburetor and into the engine.' (-23) after an earlier flight the pilot attempted to start the engine. It did not start. While cranking he noticed smoke coming from the front of the engine. He got out to investigate. He could smell smoke by then. He found flames coming from the air breather. He went back to the cabin and grabbed the aircraft logbooks. He then ran to call the fire dept. But the plane burned to the ground in a short time.

As the FAA filed it

PILOT ATTEMPTED TO START ENGINE, CAUGHT ON FIRE AND BURNED. (.4)THE PILOT REPORTED THAT HE HAD LANDED ABOUT 30 MINUTES PRIOR TO THE ACCIDENT. WHEN HE ATTEMPTED TO START THE ENGINE BEFORE THE NEXT PLANNED FLIGHT, IT 'TURNED OVER BUT WOULDN'T START.' HE PUMPED THE THROTTLE THREE TIMES. HE SAID HE ENGAGED THE STARTER, THE ENGINE 'POPPED THROUGH THE CARB,' AND FIRE IGNITED IN THE ENGINE COMPARTMENT. THE PILOT AND PASSENGER EGRESSED THE AIRPLANE UNEVENTFULLY. THE EMERGENCY PROCEDURE PUBLISHED IN THE PILOT'S OPERATING HANDBOOK (FOR ENGINE FIRE DURING START ON GROUND), SPECIFIED 'CRANKING-CONTINUE, TO GET START WHICH WOULD SUCK THE FLAMES AND ACCUMULATED FUEL THROUGH THE CARBURETOR AND INTO THE ENGINE.' (-23) AFTER AN EARLIER FLIGHT THE PILOT ATTEMPTED TO START THE ENGINE. IT DID NOT START. WHILE CRANKING HE NOTICED SMOKE COMING FROM THE FRONT OF THE ENGINE. HE GOT OUT TO INVESTIGATE. HE COULD SMELL SMOKE BY THEN. HE FOUND FLAMES COMING FROM THE AIR BREATHER. HE WENT BACK TO THE CABIN AND GRABBED THE AIRCRAFT LOGBOOKS. HE THEN RAN TO CALL THE FIRE DEPT. BUT THE PLANE BURNED TO THE GROUND IN A SHORT TIME.

NTSB investigation

The NTSB’s investigation of this event, with its probable cause and findings. Matched to this report by N-number and date.

NTSB CHI96LA241Accident · No injuriesLimited investigationFinal reportParker, SDengine compartment fire from accumulated fuel in the carburetor, and failure of the pilot to follow the emergency checklist procedure.Jul 12, 1996 · Destroyed