FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX03FA135 · Beech A36

13 Apr 2003 · Sedona, AZ, United States

Beech A36 · Accident: partial loss of engine power (non-mechanical) during takeoff

From Sedona Airport (SEZ) to Mesa Gateway Airport (IWA)

Report a problem

Event

NTSB case
LAX03FA135
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
3 · 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

Beech A36

Aircraft type
Beechcraft 36
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
N323D
Operator
Unknown
Onboard fatalities
Unknown
Route
From Sedona Airport (SEZ), Sedona, AZTo Mesa Gateway Airport (IWA), Phoenix, AZ
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
Takeoff · roll/run
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
Partial loss of engine power (non-mechanical)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Pilot in command(cfi) › Aborted takeoff, not performed
  • Pilot in command(cfi) › Mixture, improper use of
  • Pilot in command(cfi) › Procedures/directives, not complied with
  • Pilot in command(cfi) › Supervision, inadequate

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 lifted off near the end of the runway, snagged the airport boundary fence, crossed a canyon, and then collided with terrain. Runway 21 was 5,132 feet long, 75 feet wide, and the airport elevation was 4,827 feet. The density altitude was calculated at 6,435 feet. Witnesses noted that the airplane did not seem to accelerate and was rolling very slowly as it passed the midfield point. The engine did not sound like it was producing much power, yet the engine tones stayed steady and the engine sounded smooth. Several of the witnesses noted that the flaps were partially down. The witnesses thought that the pilot would abort the takeoff; however, the airplane continued down the runway and was still on the ground about 80 percent of the way down the runway. Then the pilot rotated it to a takeoff attitude, and broke ground with an extremely nose high attitude. The airplane only attained an altitude of several feet. The landing gear caught the upper strands of the airport boundary fence. The airplane then collided with the far side of a canyon that bordered the airport. The operator had a form that they used for weight and balance and performance. They required pilots to complete the form prior to each flight. The form provided spaces for pilots to record pertinent data, and log computed parameters. Those parameters included takeoff weight, density altitude, runway length, rotation speed, takeoff distance, takeoff distance over a 50-foot obstacle, rate of climb, and landing distance. Calculations for the given takeoff conditions indicated that the airplane should have had a ground roll of 1,900 feet, and would clear a 50-foot obstacle at 2,100 feet. The airplane had an altitude compensating fuel pump installed. The pump would automatically lean or enrich the engine's fuel mixture as the airplane changed altitude. The before takeoff checklist in Section IV of the Pilot Operating Handbook instructed the pilot to takeoff with the mixture in the full rich position. Other instructors from the operator who had flown with the accident instructor indicated that contrary to the instructions in the POH, they all leaned the engine prior to takeoff from high density altitude airports. The spark plugs indicated operation with an excessively lean mixture. Investigators noted no other anomalies with the airframe or engine that would have precluded normal operation.

Probable cause

a partial loss of engine power due to the certified flight instructor's failure to comply with the pilot operating handbook requirements for the mixture setting during takeoff. Also causal was the instructor's inadequate supervision of the flight, failure to monitor the airplane's performance, and failure to initiate an aborted takeoff in a timely way.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX03FA135
Event ID
20030418X00530
Case number
LAX03FA135
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: e8fea7a67960ef5f6d641ef0403e289d263f9bb77190a0a38f5c569782ac6cd9; retrieved 2026-09-20T19:18:26.646Z.