19991113047499A

Accident · Destroyed

FAA accident report · Piper PA18 · Malheurcity, OR · November 13, 1999

Date
November 13, 1999 · 11:20 local
Place
Malheurcity, OR
Phase of flight
Fcd/Prec Ldg From Cruise
Operating rules
General operating rules (Part 91)
Damage
Destroyed
Aircraft
N82553
NTSB investigation
NTSBSEA00LA018
Reported as
Piper PA18
Reported engine
Lycoming O320A2B
Fatal injuries
0
Pilot’s flight hours
35,000 total2,000 in this make and model0 in the last 90 days

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.

(.4) For about two months prior to the accident, the aircraft's electrical system had been operating improperly and failing to charge the battery. Although two maintenance shops had attempted to correct the problem, as of the date of the accident, the system was still not functioning correctly. During this two-month period, the pilot had continued to operate the aircraft, turning on the master switch only during engine start and for brief periods of radio transmission. On the day of the accident, he turned on the master switch to start the engine, and then not realizing that he had not turned it off, headed for his destination. About 10 minutes after takeoff, the pilot smelled what he thought was either smoke or fumes from a malfunctioning heater, and elected to make a precautionary landing. While attempting to land in an open area near a county road, the aircraft collided with a power line that the pilot was trying to go under in order to get to the point where he wanted to touch down. After hitting the power line, and with the fumes getting stronger, the pilot tried to get the aircraft on the ground as quickly as possible. As a result, the aircraft touched down at an excessive descent rate, and both main gear collapsed. Immediately after exiting the aircraft, the pilot noticed a small fire in the right wing root. He elected not to approach the aircraft to attempt to put out the fire, and it was eventually consumed by the flames. (-23) the pilot, who was the sole occupant of the aircraft, heard a loud pop which was immediately followed by a fire in the aircraft. While attempting to make an emergency landing in a nearby field, the aircraft clipped a power line, resulting in a hard landing and collapsing the main landing gear. The aircraft was consumed by fire after the pilot exited. The pilot reported having alternator problems for the past few months, which had not yet been resolved.

As the FAA filed it

(.4) FOR ABOUT TWO MONTHS PRIOR TO THE ACCIDENT, THE AIRCRAFT'S ELECTRICAL SYSTEM HAD BEEN OPERATING IMPROPERLY AND FAILING TO CHARGE THE BATTERY. ALTHOUGH TWO MAINTENANCE SHOPS HAD ATTEMPTED TO CORRECT THE PROBLEM, AS OF THE DATE OF THE ACCIDENT, THE SYSTEM WAS STILL NOT FUNCTIONING CORRECTLY. DURING THIS TWO-MONTH PERIOD, THE PILOT HAD CONTINUED TO OPERATE THE AIRCRAFT, TURNING ON THE MASTER SWITCH ONLY DURING ENGINE START AND FOR BRIEF PERIODS OF RADIO TRANSMISSION. ON THE DAY OF THE ACCIDENT, HE TURNED ON THE MASTER SWITCH TO START THE ENGINE, AND THEN NOT REALIZING THAT HE HAD NOT TURNED IT OFF, HEADED FOR HIS DESTINATION. ABOUT 10 MINUTES AFTER TAKEOFF, THE PILOT SMELLED WHAT HE THOUGHT WAS EITHER SMOKE OR FUMES FROM A MALFUNCTIONING HEATER, AND ELECTED TO MAKE A PRECAUTIONARY LANDING. WHILE ATTEMPTING TO LAND IN AN OPEN AREA NEAR A COUNTY ROAD, THE AIRCRAFT COLLIDED WITH A POWER LINE THAT THE PILOT WAS TRYING TO GO UNDER IN ORDER TO GET TO THE POINT WHERE HE WANTED TO TOUCH DOWN. AFTER HITTING THE POWER LINE, AND WITH THE FUMES GETTING STRONGER, THE PILOT TRIED TO GET THE AIRCRAFT ON THE GROUND AS QUICKLY AS POSSIBLE. AS A RESULT, THE AIRCRAFT TOUCHED DOWN AT AN EXCESSIVE DESCENT RATE, AND BOTH MAIN GEAR COLLAPSED. IMMEDIATELY AFTER EXITING THE AIRCRAFT, THE PILOT NOTICED A SMALL FIRE IN THE RIGHT WING ROOT. HE ELECTED NOT TO APPROACH THE AIRCRAFT TO ATTEMPT TO PUT OUT THE FIRE, AND IT WAS EVENTUALLY CONSUMED BY THE FLAMES. (-23) THE PILOT, WHO WAS THE SOLE OCCUPANT OF THE AIRCRAFT, HEARD A LOUD POP WHICH WAS IMMEDIATELY FOLLOWED BY A FIRE IN THE AIRCRAFT. WHILE ATTEMPTING TO MAKE AN EMERGENCY LANDING IN A NEARBY FIELD, THE AIRCRAFT CLIPPED A POWER LINE, RESULTING IN A HARD LANDING AND COLLAPSING THE MAIN LANDING GEAR. THE AIRCRAFT WAS CONSUMED BY FIRE AFTER THE PILOT EXITED. THE PILOT REPORTED HAVING ALTERNATOR PROBLEMS FOR THE PAST FEW MONTHS, WHICH HAD NOT YET BEEN RESOLVED.

NTSB investigation

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