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

May 26, 2006 · Piper PA-28-140 · N6309W

Eagar, AZ

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
May 26, 2006
Injury Outcomes
1 injury (1 minor injury), 1 uninjured
Location
Eagar, AZ
Aircraft
Piper PA-28-140
Tail Number
N6309W
Injuries
Minor
Aircraft Damage
Substantial
NTSB Number
LAX06LA182

The airplane settled down onto rocky upsloping terrain after a climb rate was not achieved in the takeoff initial climb. The flight instructor said he and the 3-hour primary student had been doing pattern work, and completed one flight around the pattern prior to the accident. On the accident takeoff, they had been doing a high-speed taxi on the 8,000-foot runway. He reported that he was on the controls (throttle and ailerons), and the student was on the rudders. The instructor was adding and reducing power to get the student used to maintaining directional control of the airplane and countering the left turning tendency encountered with power application. As he added power to takeoff, he noted 2,300 revolutions per minute (rpm). After liftoff, he said that the airplane was not climbing, and the engine sounded normal and was not stuttering or missing. The instructor indicated there was rising terrain ahead and houses in the area, so he decided a forced landing into rising terrain was the best option. There were also power lines located in front of them. He knew that he would have to give up the airspeed in order to get over the power lines. He said that he "lowered the nose to get best angle of climb airspeed" and noted only a 50 fpm climb. After clearing the power lines he made the forced landing. A sheriff's deputy who responded to the site reported that the accident location was 3 miles west of the airport. He noted landing gear skid marks in the rocky terrain. The airplane struck a small tree and came to rest upright facing towards the west. The deputy further noted that the landing gear wheels had separated from the airplane. The deputy interviewed the student pilot, who stated that after takeoff they were "not able to gain their normal airspeed."

NTSB Probable Cause

the flight instructor's failure to attain and maintain the proper climb airspeed, which resulted in a stall/mush.

Full Narrative

On May 26, 2006, about 0800 mountain standard time, a Piper PA-28-140, N6309W, made a forced landing in rocky terrain at Eagar, Arizona. Kestrel Aviation, Inc., operated the airplane under the provisions of 14 CFR Part 91 as an instructional flight. The airplane sustained substantial damage. The certified flight instructor (CFI) was not injured, and the student pilot sustained minor injuries. Visual meteorological conditions prevailed for the local area flight, and no flight plan had been filed. The National Transportation Safety Board investigator-in-charge interviewed the CFI. He and the student had been doing pattern work at the municipal airport in the town of Springerville, Arizona. They had completed one flight around the pattern prior to the accident. On the accident takeoff from runway 21, they had been doing a high-speed taxi on the 8,000-foot runway. He reported that he was on the controls (throttle and ailerons), and the student was on the rudders. The CFI was adding and reducing power to get the student used to the directional control of the airplane (left turning tendency). As the CFI added power to takeoff, he noted 2,300 revolutions per minute (rpm). After liftoff, he said that the airplane was not climbing, and the engine sounded normal, but was still only producing 2,300 rpm; not the 2,500 rpm that was normal. The engine was not stuttering or missing, and the airplane was not climbing. The CFI indicated there were houses and rising terrain in the area. There were also power lines. He knew that he would have to give up airspeed in order to get over the power lines. He lowered the nose to get the best angle of climb airspeed, and noted a 50 fpm rate of climb. After clearing the power lines, he made the forced landing. When the CFI noted that the airplane was not climbing, he checked the magnetos and mixture, but did not apply the carburetor heat. He said that it was dry and warm outside, and he did not believe that carburetor ice was an issue. He had the airplane configured for takeoff; the mixture was at a lean setting, and one notch of flaps. He attempted to readjust the mixture during the event, but that did not work. He also indicated that he did not raise the flaps, because the airplane would have settled. He noted the weather as calm winds, clear, and about 65 to 70 degrees. They used the calm wind runway 21. The CFI stated that he normally flies early in the morning with his students for density altitude considerations. The airplane had plenty of fuel onboard. A deputy from the Apache County Sheriff's Office reported that the accident site was 3 miles west of the Springerville airport in the neighboring town of Eagar. He noted landing gear skid marks in the rocky terrain. The airplane struck a small tree, and came to rest upright facing towards the west. The deputy further noted that the landing gear wheels had separated from the airplane. The deputy interviewed the student pilot, who indicated that after takeoff they were "not able to gain their normal airspeed." He noted their airspeed at 65 miles per hour (mph), with 2,000 rpm. A Federal Aviation Administration inspector interviewed the CFI. The CFI indicated that after applying power to takeoff, he noted they had no more available runway left in which to make the forced landing.

Flight

Event TypeAccident
Event Time08:00 MST
Nearest AirportSpringervile Municipal Airport (3nm)
Runway21
Runway Length8417 ft
Runway Width75 ft
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftPiper PA-28-140
Tail NumberN6309W
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-320-E2A · Reciprocating · 150
Seats2

People & Injuries

Injury Summary1 injury (1 minor injury), 1 uninjured
Fatal0
Serious0
Minor1
Uninjured1
Total2
Crew 1Age 69 · None · None
Crew 2None · None

Conditions

ConditionsVMC
LightDaylight
WindCalm
Visibility10 sm
CeilingNone
Temperature / Dew Point25 C
Altimeter29.97 inHg
Observation Time14:54
Weather SourceWFAC

Appendix: Source Data