Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

September 15, 2000 · Piper PA-28-161 · N381AS

Phoenix, AZ

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
September 15, 2000
Injury Outcomes
No injuries (2 uninjured)
Location
Phoenix, AZ
Aircraft
Piper PA-28-161
Tail Number
N381AS
Operator
Dgv Holdings
Injuries
None
Aircraft Damage
Substantial
NTSB Number
LAX00LA336

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.

NTSB 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.

Full 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.

Flight

Event TypeAccident
Event Time11:00 MST
Nearest AirportDeer Valley (0nm)
Runway7L
Runway Length4500 ft
Runway Width75 ft
Flight Plan FiledNone
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftPiper PA-28-161
Tail NumberN381AS
Aircraft CategoryAir
DamageSubstantial
OperatorDgv Holdings
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-320-D3F · Reciprocating · 160
Seats4

People & Injuries

Injury SummaryNo injuries (2 uninjured)
Fatal0
Serious0
Minor0
Uninjured2
Total2
Crew 1Age 27 · First Class

Conditions

ConditionsVMC
LightDaylight
Wind5 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point14 C
Altimeter29.00 inHg
Observation Time18:00
Weather SourceWFAC

Appendix: Source Data