FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX05LA305 · Beech 35-C33

19 Sept 2005 · Bisbee, AZ, United States

Chandler Air Service Beech 35-C33 · Accident: loss of control in flight during initial climb

From Bisbee Municipal Airport (P04) to Chandler Municipal Airport (CHD)

Report a problem

Event

NTSB case
LAX05LA305
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

Beech 35-C33

Aircraft type
Beechcraft 35
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
N5757D
Onboard fatalities
Unknown
Route
From Bisbee Municipal Airport (P04), Bisbee, AZTo Chandler Municipal Airport (CHD), Chandler, 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
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

  • Flight instructor(on ground) › Instructions, written/verbal, incorrect
  • Pilot in command › Aborted takeoff, not performed
  • Pilot in command › Airspeed, not obtained/maintained
  • Pilot in command › Mixture, incorrect
  • Pilot in command › Procedures/directives, not complied with
  • Pilot in command › 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 back to the ground during the takeoff initial climb and collided with bushes and desert terrain off the end of the runway, bending the right wing and aft carry-though spars. The airport was at an elevation of 4,780 feet mean sea level (msl) and the density altitude was 6,692 feet msl. During his leaning of the mixture, the pilot set the rpm at 1,800, leaned the mixture for an increase in rpm, then richened the mixture by one full turn, all in accordance with instructions given him during his check-out in the rental airplane by a flight instructor. The pilot completed his pre-takeoff checklist, made a traffic advisory, and positioned the airplane for takeoff. He held the brakes and applied full throttle. As the rpm came up to 2,600 rpm, the engine sounded normal, the brakes were released, and he began the takeoff roll. During the takeoff ground roll, a significantly greater distance was required to develop airspeed than the pilot expected; however, he thought this to be the result of the airport elevation and the outside air temperature. The pilot operating handbook (POH) performance charts showed that a ground roll of 2,100 feet should have been required to achieve takeoff over a 50-foot obstacle. The airplane reached 65 knots approximately 2/3 down the 5,929-foot-long runway and slight elevator back pressure was applied. The airplane lifted off and back pressure was eased to remain in ground effect and continue airspeed acceleration. However, the airplane did not accelerate, but instead settled back to the ground. The airplane touched down just off the end of the runway and came to a stop approximately 20 feet from the airport perimeter fence. The day prior to the accident, the pilot was checked out in the airplane. Following the check-out flight, he asked the certified flight instructor (CFI) the proper leaning procedures for the airplane. He was told to lean the mixture at run-up (1,800 rpm) using engine rpm, and then richen it one full turn at field elevations below 5,000 feet msl, and to lean the mixture at full power using the exhaust gas temperature gauge at field elevations above 5,000 feet msl. The POH states that the engine should be leaned using 2,600 rpm using the combined manifold and fuel flow indicator gauge. This gauge shows fuel flow in gallons per hour and is marked with a green arc to indicate normal fuel flow operating parameters for different power settings. The takeoff optimum fuel performance range is covered by green sectors and the high side of each green sector represents the appropriate fuel setting required to obtain maximum power when operating at full throttle and 2,600 rpm. A Federal Aviation Administration inspector test-ran the engine following the accident and no operational anomalies were noted.

Probable cause

the pilot's failure to lean the mixture in accordance with the pilot operating handbook specified procedures, which resulted in a power deficiency, a degraded climb capability, and the inability to attain/maintain an adequate airspeed that led to a stall/mush condition while departing in high density altitude conditions. The pilot's failure to abort the takeoff when an excessive takeoff ground roll became apparent was also causal. Also causal, was the certified flight instructor's failure to provide the proper leaning procedures during a preflight briefing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX05LA305
Event ID
20050922X01515
Case number
LAX05LA305
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: 9af76ffd6c136d487236b0d930f53929fe62d5fdca93f3a9438477e56978ae85; retrieved 2026-09-22T05:21:19.909Z.