FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX06LA182 · Piper PA-28-140

26 May 2006 · Eagar, AZ, United States

Piper PA-28-140 · Accident: loss of control in flight during initial climb

From D68 · Springerville, AZ to D68

Report a problem

Event

NTSB case
LAX06LA182
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Piper PA-28-140

Aircraft type
Piper PA-28
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N6309W
Operator
Unknown
Onboard fatalities
Unknown
Route
From D68 · Springerville, AZTo D68
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Initial climb
First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Loss of control in flight
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Stall/mush
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Pilot in command(cfi) › Airspeed, not obtained/maintained
  • Pilot in command(cfi) › Stall/mush, encountered

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

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

Probable cause

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

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX06LA182
Event ID
20060602X00671
Case number
LAX06LA182
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 2799efd0f280e204c3d4bc1ab8e58a5c749a9f353b99963cd41046080be570a7; retrieved 2026-09-21T18:46:01.098Z.