20071115828549I

Incident · No damage

FAA incident report · Piper PA-34-200 · San Diego, CA · November 15, 2007

Date
November 15, 2007 · 10:44 local
Place
San Diego, CA
Airport
Montgomery Field
Phase of flight
Sfl Final Approach
Operating rules
General operating rules (Part 91)
Damage
No damage
Aircraft
N15068
Reported as
Piper PA34200
People aboard
2
Fatal injuries
0
Pilot’s flight hours
4,500 total0 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.

(-23) Pilot simulated an engine failure at altitude on an instructional flight, could not restart engine. Pilot contacted Montgomery air traffic control tower for landing clearance, and landed without further incident. Pilot statement attached. Report will be amended when pilot appears for logbook inspection on January 2, 2008. Pilot's statement: on 11-15-2007, I was conducting an instructional flight for a commercial multi engine candidate in N15068 a PA-34. My student privacy data omitted was briefed on oei, and other factors and considerations involving oei and fully feathering and restarting procedures. Just NE of "nesty" intersection at about 3500' MSL I failed the port side engine using the mixture knob. My student went through a trouble shoot flow and then a shut down flow, omitting the shut down of mags, fuel and x-feeding. I allowed my student to fly the aircraft for about 3 minutes with the feathered engine. I then did a flight control exchange and told her to re-start using the "hot start" check list. After several attempts to re-start, I gave her the flight control and attempted a flooded engine start after noticing that the fuel pump was "on" the failed engine. The starter engaged momentarily and then quit. At the time, I thought that two things had happened. The engine was flooded and the series wound starter motor was over heated and would not crank. I considered that I had the following options: 1. Loiter at 3500' feet in a heavy traffic area for up to 15 to 20 minutes (single engine) until the starter motor cooled off and hope for a restart. 2. Ask for priority handling, get on the ILS and land it. 3. Declare an emergency if I could not get priority handling and land it. I asked for and was given priority to the runway. I briefed my student and she made a near perfect single engine approach and landing.

As the FAA filed it

(-23) PILOT SIMULATED AN ENGINE FAILURE AT ALTITUDE ON AN INSTRUCTIONAL FLIGHT, COULD NOT RESTART ENGINE. PILOT CONTACTED MONTGOMERY AIR TRAFFIC CONTROL TOWER FOR LANDING CLEARANCE, AND LANDED WITHOUT FURTHER INCIDENT. PILOT STATEMENT ATTACHED. REPORT WILL BE AMENDED WHEN PILOT APPEARS FOR LOGBOOK INSPECTION ON JANUARY 2, 2008. PILOT'S STATEMENT: ON 11-15-2007, I WAS CONDUCTING AN INSTRUCTIONAL FLIGHT FOR A COMMERCIAL MULTI ENGINE CANDIDATE IN N15068 A PA-34. MY STUDENT ^PRIVACY DATA OMITTED^ WAS BRIEFED ON OEI, AND OTHER FACTORS AND CONSIDERATIONS INVOLVING OEI AND FULLY FEATHERING AND RESTARTING PROCEDURES. JUST NE OF "NESTY" INTERSECTION AT ABOUT 3500' MSL I FAILED THE PORT SIDE ENGINE USING THE MIXTURE KNOB. MY STUDENT WENT THROUGH A TROUBLE SHOOT FLOW AND THEN A SHUT DOWN FLOW, OMITTING THE SHUT DOWN OF MAGS, FUEL AND X-FEEDING. I ALLOWED MY STUDENT TO FLY THE AIRCRAFT FOR ABOUT 3 MINUTES WITH THE FEATHERED ENGINE. I THEN DID A FLIGHT CONTROL EXCHANGE AND TOLD HER TO RE-START USING THE "HOT START" CHECK LIST. AFTER SEVERAL ATTEMPTS TO RE-START, I GAVE HER THE FLIGHT CONTROL AND ATTEMPTED A FLOODED ENGINE START AFTER NOTICING THAT THE FUEL PUMP WAS "ON" THE FAILED ENGINE. THE STARTER ENGAGED MOMENTARILY AND THEN QUIT. AT THE TIME, I THOUGHT THAT TWO THINGS HAD HAPPENED. THE ENGINE WAS FLOODED AND THE SERIES WOUND STARTER MOTOR WAS OVER HEATED AND WOULD NOT CRANK. I CONSIDERED THAT I HAD THE FOLLOWING OPTIONS: 1. LOITER AT 3500' FEET IN A HEAVY TRAFFIC AREA FOR UP TO 15 TO 20 MINUTES (SINGLE ENGINE) UNTIL THE STARTER MOTOR COOLED OFF AND HOPE FOR A RESTART. 2. ASK FOR PRIORITY HANDLING, GET ON THE ILS AND LAND IT. 3. DECLARE AN EMERGENCY IF I COULD NOT GET PRIORITY HANDLING AND LAND IT. I ASKED FOR AND WAS GIVEN PRIORITY TO THE RUNWAY. I BRIEFED MY STUDENT AND SHE MADE A NEAR PERFECT SINGLE ENGINE APPROACH AND LANDING.

Other reports on N15068 · 4

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