19991202044899A

Accident · Substantial damage

FAA accident report · Piper PA-28-181 · Palo Alto, CA · December 2, 1999

Date
December 2, 1999 · 11:24 local
Place
Palo Alto, CA
Airport
Palo Alto Airport-Santa Clara Cou
Phase of flight
Touch And Go Landing
Operating rules
General operating rules (Part 91)
Damage
Substantial damage
Aircraft
N4319Y
NTSB investigation
NTSBLAX00LA067
Reported as
Piper PA28181
Reported engine
Lycoming O360*
People aboard
2
Fatal injuries
0
Pilot’s flight hours
920 total28 in this make and model44 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.

(-23) On December 2, 1999 at 0736 PST N4319Y a Piper PA-28-180 deaprted carlsbad palomar airport (crq) on an IFR flight plan to Palo Alto, CA(pao). The a/c departed carlsbad palomar airport with full fuel tanks. Pilot cancelled IFR flight plan north of the gorman VOR then proceeded VFR until south of san jose, CA then requested IFR flight plan due to clouds in the bay area. At this time pilot reported minimum fuel to bay area TRACON facility. Palo Alto traffic was using runway 12. Pilot requested landing clearance for runway 30 and was approved. A/c made straight in approach to runway 30 at excessive air speed and above normal glide path. Pilot elected to go around, during the turn back to land on runway 12 pilot force landed on shore line one half mile from runway 12 at 1124 PST. A/c substained minor damage. No injuries to the two occupants. Visual meteorological conditions prevailed at the time of the accident. (.4)prior to departure to return to home base, the pilot filed an IFR flight plan, conducted a preflight, and had the fuel tanks topped off. He flew on the left fuel tank for approximately 1 hour and then switched to the righ t fuel tank. Upon reaching his destination he noted multiple cloud layers, and requested and received an IFR clearance to his destination airport. About an hour later he switched back to the left fuel tank. He noted a drop to zero in the left fuel gage about 45 minutes later, and switched to the right tank, where he noted that the fuel gage read 5 gallons. He switched back to the left tank and the engine stopped; he switched back to the right tank and the engine restarted. He declared minimum fuel and received information on nearby airports; one 7 miles in his direction of flight, and his destination airport was 11 miles in his direction of flight. He continued the flight to the destination airport in order to lose altitude. He was at 4,000 feet, and traffic pattern altitude is 800 feet. He requested a straight in to a runway 30 even though 12 was the active runway. On short final, he initiated a go-around due to high speed, and high altitude. During the turn back to the runway the engine lost power and landed in a marshy area. There was no fuel observed in the tanks during the recovery of the airplane. During the engine examination it was noted that were was no fuel staining observed on the wings or fuselage of the airplane, and there were no leaks in the fuel system. No discrepancies were noted with the run-up.

As the FAA filed it

(-23) ON DECEMBER 2, 1999 AT 0736 PST N4319Y A PIPER PA-28-180 DEAPRTED CARLSBAD PALOMAR AIRPORT (CRQ) ON AN IFR FLIGHT PLAN TO PALO ALTO, CA(PAO). THE A/C DEPARTED CARLSBAD PALOMAR AIRPORT WITH FULL FUEL TANKS. PILOT CANCELLED IFR FLIGHT PLAN NORTH OF THE GORMAN VOR THEN PROCEEDED VFR UNTIL SOUTH OF SAN JOSE, CA THEN REQUESTED IFR FLIGHT PLAN DUE TO CLOUDS IN THE BAY AREA. AT THIS TIME PILOT REPORTED MINIMUM FUEL TO BAY AREA TRACON FACILITY. PALO ALTO TRAFFIC WAS USING RUNWAY 12. PILOT REQUESTED LANDING CLEARANCE FOR RUNWAY 30 AND WAS APPROVED. A/C MADE STRAIGHT IN APPROACH TO RUNWAY 30 AT EXCESSIVE AIR SPEED AND ABOVE NORMAL GLIDE PATH. PILOT ELECTED TO GO AROUND, DURING THE TURN BACK TO LAND ON RUNWAY 12 PILOT FORCE LANDED ON SHORE LINE ONE HALF MILE FROM RUNWAY 12 AT 1124 PST. A/C SUBSTAINED MINOR DAMAGE. NO INJURIES TO THE TWO OCCUPANTS. VISUAL METEOROLOGICAL CONDITIONS PREVAILED AT THE TIME OF THE ACCIDENT. (.4)PRIOR TO DEPARTURE TO RETURN TO HOME BASE, THE PILOT FILED AN IFR FLIGHT PLAN, CONDUCTED A PREFLIGHT, AND HAD THE FUEL TANKS TOPPED OFF. HE FLEW ON THE LEFT FUEL TANK FOR APPROXIMATELY 1 HOUR AND THEN SWITCHED TO THE RIGH T FUEL TANK. UPON REACHING HIS DESTINATION HE NOTED MULTIPLE CLOUD LAYERS, AND REQUESTED AND RECEIVED AN IFR CLEARANCE TO HIS DESTINATION AIRPORT. ABOUT AN HOUR LATER HE SWITCHED BACK TO THE LEFT FUEL TANK. HE NOTED A DROP TO ZERO IN THE LEFT FUEL GAGE ABOUT 45 MINUTES LATER, AND SWITCHED TO THE RIGHT TANK, WHERE HE NOTED THAT THE FUEL GAGE READ 5 GALLONS. HE SWITCHED BACK TO THE LEFT TANK AND THE ENGINE STOPPED; HE SWITCHED BACK TO THE RIGHT TANK AND THE ENGINE RESTARTED. HE DECLARED MINIMUM FUEL AND RECEIVED INFORMATION ON NEARBY AIRPORTS; ONE 7 MILES IN HIS DIRECTION OF FLIGHT, AND HIS DESTINATION AIRPORT WAS 11 MILES IN HIS DIRECTION OF FLIGHT. HE CONTINUED THE FLIGHT TO THE DESTINATION AIRPORT IN ORDER TO LOSE ALTITUDE. HE WAS AT 4,000 FEET, AND TRAFFIC PATTERN ALTITUDE IS 800 FEET. HE REQUESTED A STRAIGHT IN TO A RUNWAY 30 EVEN THOUGH 12 WAS THE ACTIVE RUNWAY. ON SHORT FINAL, HE INITIATED A GO-AROUND DUE TO HIGH SPEED, AND HIGH ALTITUDE. DURING THE TURN BACK TO THE RUNWAY THE ENGINE LOST POWER AND LANDED IN A MARSHY AREA. THERE WAS NO FUEL OBSERVED IN THE TANKS DURING THE RECOVERY OF THE AIRPLANE. DURING THE ENGINE EXAMINATION IT WAS NOTED THAT WERE WAS NO FUEL STAINING OBSERVED ON THE WINGS OR FUSELAGE OF THE AIRPLANE, AND THERE WERE NO LEAKS IN THE FUEL SYSTEM. NO DISCREPANCIES WERE NOTED WITH THE RUN-UP.

NTSB investigation

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

Other reports on N4319Y · 1

Matched to the same aircraft by N-number and date.