# NTSB LAX00LA336: Piper PA-28-161, N381AS, Phoenix, AZ, September 15, 2000 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: September 15, 2000, 11:00 local (18:00 UTC) - Place: Phoenix, AZ - Coordinates: 33.68003, -112.09027 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=33.6800&lon=-112.0903&mi=10 - Phase of flight: [Initial climb](https://openairdocs.org/ntsb-phases/350) (OpenAirDocs' grouping) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report November 1, 2001 - Report: Approved by Office Director - NTSB case key (mKey): 50262 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=LAX00LA336 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/50262/pdf - Page: https://openairdocs.org/ntsb/LAX00LA336 ## Probable cause Loss of engine power for undetermined reasons. A factor was the lack of suitable terrain available for a straight ahead landing during the takeoff initial climb. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Loss of engine power, takeoff - initial climb - reason for occurrence undetermined (cause) - In flight collision with object, maneuvering - turn to landing area (emergency) - object - fence - terrain condition - none suitable (contributing factor) - low altitude flight/maneuver - initiated, pilot in command (contributing factor) - Nose over, emergency descent/landing ## Analysis The airplane struck the airport perimeter fence and came to rest inverted after initiating a turn back to the runway for an emergency landing due to a loss of engine power. No discrepancies were found during the preflight inspection or the startup, run-up, or pretakeoff procedures. During the initial climb out the engine began to sputter. The CFI took control of the airplane and verified that the fuel pump was on, throttle was full forward, and the mixture was rich. The engine sputtered again and he noted that the fuel pressure gage was indicating zero. During the turn back to the runway the airplane lost altitude. A post crash engine inspection and run-up were conducted. No discrepancies were noted with the visual inspection of the engine. A remote fuel source was attached to the fuel line on the left wing to facilitate an engine run-up. The electric fuel pump was engaged and fuel pressure was observed on the fuel pressure gage. No visible fuel leaks were observed on the engine. The engine was started per manufacturer's checklist and a warm up period was initiated. After the warm up period the throttle was advanced to full power with no discrepancies noted. ## Factual narrative On September 15, 2000, at 1100 hours mountain standard time, a Piper PA-28-161, N381AS, experienced a loss of engine power during the takeoff initial climb from runway 7L at the Deer Valley Airport, Phoenix, Arizona. During an attempted return to runway maneuver the airplane struck a perimeter fence, and came to rest inverted at the departure end of the runway. The airplane was operated by DEV Holdings, d.b.a. Pan Am International Flight Academy, under the provisions of 14 CFR Part 91, and sustained substantial damage. The certified flight instructor (CFI) and student pilot were not injured. Visual meteorological conditions existed for the local area instructional flight, and no flight plan was filed. In an interview with a Federal Aviation Administration inspector, the CFI stated that after takeoff a loss of power was experienced. He took the controls from the student, and attempted to turn back to the runway for landing but had insufficient altitude to make the landing surface. In the CFI's written statement, he reported that during the preflight the student noted that the airplane was low on fuel. After the airplane was refueled, the CFI strained fuel from the fuel sumps with no anomalies noted. He further stated that there were no discrepancies noted with the startup, run-up or pretakeoff checklists. After receiving takeoff clearance, the student pilot advanced the throttles with no "unusual indications from the engine instruments" noted by the CFI. He estimated that at 100 feet agl the engine began to sputter. He took the controls from the student and checked that the fuel pump was on. He also verified that the throttle was full forward, and the mixture was rich. He heard the engine sputter again, which he attributed to a fuel related issue. He saw the fuel pressure gage indicating zero and rechecked that the fuel pump was on. He transmitted a mayday call to the tower and began a turn back to the runway. In the turn the airplane lost altitude. As the pilot returned the airplane to a wings level flight attitude he noted that the airport perimeter fence was in front of them. The airplane struck the perimeter fence and came to rest upside down. He asked if his student was okay. The CFI shut the airplane down and they evacuated the airplane. In the student pilot's written statement he reported the engine instruments were indicating normal and no discrepancies were noted with the takeoff. When he noted the power loss, he gave control of the airplane to his instructor. He reported that his instructor attempted resolve the problem and then made the mayday call. The power plant was inspected at Air Transport in Phoenix on October 11, 2000, by a Safety Board investigator with a representative from Textron Lycoming engines, who was a party to the investigation. A visual inspection was conducted, with no discrepancies noted. A remote fuel source was attached to the fuel line of the left wing to facilitate an engine run-up. The electric fuel pump was activated via a switch in the cockpit and fuel pressure was observed on the fuel pressure gage. No visible fuel leaks were observed coming from the engine. The engine was started per the manufacturer's checklist. After the engine was warmed up the throttles were advanced to full power with no discrepancies noted. A magneto check was conducted and found to be within manufacturer's limits. ## Aircraft - Registration: N381AS (not matched to a registry record) - Reported make and model: Piper PA-28-161 - Category: Airplane - Serial number: 28-8516036 - Airframe hours: 6225 - Engines: Lycoming O-320-D3F 160 horsepower reciprocating - Damage: Substantial damage - Flight: Instructional, Part 91 - Operator: Dgv Holdings, doing business as Pan Am International Flt Acdmy - Registered owner: Ew Holdings - Airworthiness certificate: Standard, Normal; Standard, Utility - Last inspection: 100 hour, September 14, 2000, 1 hours before - Departed: DVT - Destination: DVT - Airport: DVT, Deer Valley, runway 7L, 4,500 × 75 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 27; flight instructor, commercial; airplane ratings: multi-engine land, single-engine land; instrument ratings: airplane; medical: class 1, valid medical--no waivers/lim.; seat: right; flight hours: 515 total, 191 in this make and model, 432 as pilot in command, 140 in the last 90 days, 62 in the last 30 days, 4 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 0° at 5 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 210 °F, dew point 145 °F - Altimeter: 29.00 inHg - Observed at: DVT ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20000915015669A](https://openairdocs.org/incident/20000915015669A), Sep 15, 2000: Piper PA28161, Phoenix, AZ, Substantial damage. (-23) The flight instructor and student departed runway 7 left at the Deer valley airport, AZ. For closed traffic touch and go's. at approx. 200' AGL, on the… From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.