FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR23LA334 · Piper PA-28-140

2 Sept 2023 · Prescott, AZ, United States

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

From Prescott Regional Airport - Ernest A. Love Field (KPRC) to Sedona Airport (KSEZ)

Report a problem

Event

NTSB case
WPR23LA334
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
Event fatalities
Unknown
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
N6834W
Operator
Unknown
Onboard fatalities
Unknown
Route
From Prescott Regional Airport - Ernest A. Love Field (KPRC), Prescott, AZTo Sedona Airport (KSEZ), Sedona, AZ
Aircraft age
About 58 years (built 1965)
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
Takeoff
Defining eventThe 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
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

  • Aircraft › Aircraft oper/perf/capability
  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The private pilot, who was pilot-in-command (PIC) and seated in the left seat, and the student pilot, who owned the airplane and was seated in the right seat, had landed at the airport with the two passengers to refuel the airplane. The airport had a field elevation of 5,045 ft mean sea level (msl) and the density altitude was calculated to be 6,375 ft. The PIC calculated that the airplane’s weight after fueling was about 38 lbs under its maximum gross weight and within the center of gravity envelope. The student pilot taxied the airplane for departure and reported that the engine run-up was normal. He subsequently requested a “short delay” from the air traffic controller to review the takeoff checklist with the PIC, including verifying the flap setting, rotation airspeed, and climb airspeed. During the takeoff roll, the airplane used about 3,000 ft of runway before rotating. When the airplane was about 200 ft above ground level (agl), it stopped climbing, and the stall warning light illuminated. The student pilot said he had “every intent of us pulling on the yoke to maintain the climb” but that, after a few seconds of trying to gain airspeed by leveling the nose, the airplane would not maintain airspeed or gain altitude. The PIC took control of the airplane to attempt to maximize airspeed and glide distance but stated that his forward visibility was limited due to the airplane’s nose-high attitude and that he was unable to see a nearby road that the student pilot had identified as suitable for landing; the student pilot took control of the airplane and directed it toward the road. During the landing sequence, the airplane collided with treetops and a tree branch before coming to rest at the side of the road. Postaccident examination of the airplane and engine revealed no evidence of any preimpact mechanical malfunctions or failures that would have precluded normal operation. Using an external fuel source, the engine was run uneventfully throughout various power settings. According to the airplane performance charts in the owner’s handbook (OH) for the airplane, based on the density altitude conditions at the time of takeoff, the calculated takeoff distance ground run for the airplane was about 1,600 ft. Although the student pilot had mistakenly calculated that the ground run would be “around 2,700 ft,” the student pilot continued the takeoff after the airplane’s ground roll exceeded that distance, and the PIC did not call for a rejected takeoff. The 7,619-ft runway would have provided ample distance to stop the airplane on the runway had a rejected takeoff been initiated, even at the erroneously calculated ground roll distance. The excessive ground roll before rotation, the illumination of the stall warning light shortly after rotation, and the student pilot’s statement that his intention was to pull on the yoke to maintain the climb all provide evidence that the student pilot excessively raised the airplane’s nose during the takeoff roll and climb; the PIC did not intervene until after the stall warning light illuminated. The excessive nose-high attitude degraded the airplane’s takeoff roll and climb performance. Further, the PIC stated that the student pilot reported a loss of engine rpm during the climb. The pretakeoff engine run-up (ground check) procedures in the OH for the airplane specified the use of carburetor heat to melt any ice that may have formed during taxiing. However, as noted earlier, after completing the run-up, the PIC and the student pilot delayed initiating the takeoff roll. Given this extended ground time after run-up, and based on the carburetor icing probability charts that indicated the conditions were conducive to the formation of serious carburetor icing at glide power, it is possible that carburetor icing formed, further degrading the airplane’s takeoff and climb performance.

Probable cause

The pilot-in-command’s inadequate preflight planning for the high density altitude and relative humidity conditions and his failure to recognize the need to reject the takeoff, allowing the student pilot to execute an abnormally long takeoff roll and apply excessive nose-high control inputs, which resulted in rotation with inadequate climb performance and an inflight collision with terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR23LA334
Event ID
20230905193011
Case number
WPR23LA334
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, cause areas. 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: e02412084bb279c2f1032e31274962f61ef30a6786e3968eba132a140461ba44; retrieved 2026-09-16T18:05:27.950Z.