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

October 20, 2025 · Piper Aircraft PA 46-350P · N699PG

Queen Creek, AZ

Overview

Report Status
Probable Cause
Event Type
Accident
Date
October 20, 2025
Injury Outcomes
No injuries (1 uninjured)
Location
Queen Creek, AZ
Aircraft
Piper Aircraft PA 46-350P (2013)
Tail Number
N699PG
Injuries
None
Aircraft Damage
Substantial
NTSB Number
WPR26LA025

The pilot reported that he was conducting a cross-country flight to an airport he had flown to a few days earlier. According to the pilot, during an approach his selected destination runway on the accident flight, his forward view was significantly obscured by a sun glare. He aligned the airplane to land on what he initially thought was the runway, which he later identified as an irrigation canal. As the airplane descended toward the canal, the pilot observed high-tension transmission lines immediately ahead and at about the same altitude. He maneuvered the airplane in an aggressive descent in an attempt to fly under the powerlines. He reported feeling “a thud” and immediately increased power, retracted the landing gear and flaps, and maneuvered the airplane into a climb. The pilot ascertained the airplane was flying normally and decided to divert to a familiar airport about 16 miles away. As the airplane was on the final approach leg of the traffic pattern, the airplane rolled aggressively to the left. In response, the pilot used aileron control inputs to compensate and landed the airplane without further incident. After exiting the airplane, the pilot observed that the rudder and most of the vertical stabilizer were separated from the airplane. Local law enforcement located the missing airplane parts in the immediate vicinity of an impacted transmission line and observed a paint signature matching the airplane’s paint on one of the transmission lines. The airplane sustained substantial damage to the vertical stabilizer and rudder. Surveillance video obtained from a nearby hospital with a view of the accident site captured the airplane flying at a low altitude, with the rudder and most of the vertical stabilizer missing. The surveillance video showed the airplane passing the transmission towers at about 17:53:30; ADS-B data also indicated the airplane passed the transmission towers at about 17:53:30. At that time, the sun’s azimuth was 267° and its elevation was slightly below the horizon at -1.19°. (See Figure 2). The pilot reported no preimpact mechanical malfunctions or anomalies with the airplane that would have precluded normal operation.

NTSB Probable Cause

The pilot’s improper runway alignment and failure to maintain clearance from powerlines. Contributing to the accident was sun glare, which obscured the pilot’s view of the runway.

Full Narrative

The pilot reported that he was conducting a cross-country flight to an airport he had flown to a few days earlier. According to the pilot, during an approach his selected destination runway on the accident flight, his forward view was significantly obscured by a sun glare. He aligned the airplane to land on what he initially thought was the runway, which he later identified as an irrigation canal. As the airplane descended toward the canal, the pilot observed high-tension transmission lines immediately ahead and at about the same altitude. He maneuvered the airplane in an aggressive descent in an attempt to fly under the powerlines. He reported feeling “a thud” and immediately increased power, retracted the landing gear and flaps, and maneuvered the airplane into a climb. The pilot ascertained the airplane was flying normally and decided to divert to a familiar airport about 16 miles away. As the airplane was on the final approach leg of the traffic pattern, the airplane rolled aggressively to the left. In response, the pilot used aileron control inputs to compensate and landed the airplane without further incident. After exiting the airplane, the pilot observed that the rudder and most of the vertical stabilizer were separated from the airplane. Local law enforcement located the missing airplane parts in the immediate vicinity of an impacted transmission line and observed a paint signature matching the airplane’s paint on one of the transmission lines. The airplane sustained substantial damage to the vertical stabilizer and rudder. Surveillance video obtained from a nearby hospital with a view of the accident site captured the airplane flying at a low altitude, with the rudder and most of the vertical stabilizer missing. The surveillance video showed the airplane passing the transmission towers at about 17:53:30; ADS-B data also indicated the airplane passed the transmission towers at about 17:53:30. At that time, the sun’s azimuth was 267° and its elevation was slightly below the horizon at -1.19°. (See Figure 2). The pilot reported no preimpact mechanical malfunctions or anomalies with the airplane that would have precluded normal operation.

Flight

Event TypeAccident
Event Time17:53 MST
Nearest Airport0nm
Flight Plan FiledNone
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftPiper Aircraft PA 46-350P
Tail NumberN699PG
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeTurboprop
Engine DetailsLycoming · TIO-540-AE2A · Turboprop · 350
Seats6

People & Injuries

Injury SummaryNo injuries (1 uninjured)
Fatal0
Serious0
Minor0
Uninjured1
Total1
Crew 1Age 61 · Third Class · None

Conditions

ConditionsVMC
LightDaylight
Wind240° @ 6 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point45 F
Altimeter29.96 inHg
Observation Time17:50
Weather SourceWFAC

Appendix: Source Data