Beech 35-C33 accident near Bisbee, Arizona, September 19, 2005
On September 19, 2005 at about 10:45 pm local time, a Beech 35-C33, registered N5757D, was substantially damaged in an accident near Bisbee, Arizona (Bisbee airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 3 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
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.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- September 19, 2005 · about 10:45 pm local time
- Place
- Bisbee, Arizona · Bisbee · map
- Type
- Accident
- Injuries
- No one was hurt; 3 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Beech 35-C33 · all 35-C33s on the register
- Registration
- N5757D · registry record · serial CD-1092
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
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.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
Pilot
- Certificate: private
- Ratings: single-engine land; single-engine sea
- Flight time: 393 hours in all; 5 in this make and model; 49 in the last 90 days; 9 in the last 30 days; 214 as pilot in command
- Last flight review: August 1, 2004
- Medical certificate: Class 3 (without waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 5,325 hours
- Last inspection: 100-hour inspection, June 1, 2005; 65 hours since
- Maximum gross weight: 3,050 lb
- Seats: 4
- Landing gear: retractable
- Engine: Continental IO-470K (piston); 0 hours total
- Operator: Chandler Air Service
The flight
- Departed from: P04 Bisbee AZ at 10:45 pm
- Destination: CHD Chandler AZ
- Flight plan: VFR
- Runway 17, 5,929 ft by 60 ft
Weather at the time
- Light: daylight
- Wind: from 360° at 11 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 73°F (23°C), dew point 61°F (16°C)
- Altimeter: 30.20 inHg
- Observation at 10:56 pm from DUG, 15 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Crew | 1 | |||
| Passengers | 2 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
