No fatalities

30 Jul 2011: BEECH 76 (N6718X) — California Flight Center, Inc. — Perris, CA

Perris, CA, United States

On 30 Jul 2011, a BEECH 76 (registration N6718X) operated by California Flight Center, Inc. was involved in an aviation accident near Perris, CA. No fatalities were reported. Investigators recorded the probable cause as: The pilot’s failure to maintain airplane control and the resulting encounter with an aerodynamic stall. Also causal were the pilot’s inadequate preflight planning and preflight inspection, his failure to ensure the pitch trim was positioned correctly for… This summary draws on records from NTSB; 12 related events involving the same aircraft type or operator are linked below.

SourcesNTSBPrimary reportUpdated 1778583330Data APIEditorial standards

On July 30, 2011, a Beech 76 Duchess, N6718X, impacted terrain during initial climb after takeoff from Perris Valley Airport, stalling and striking a dirt berm. The pilot was seriously injured, and the aircraft was substantially damaged.

Accident Overview

On July 30, 2011, about 0825 Pacific daylight time, a Beech 76 (Duchess), N6718X, impacted terrain during initial climb seconds after takeoff from runway 15 at Perris Valley Airport, Perris, California. The airplane's fuselage and wings were deformed during the impact, and the airplane was substantially damaged. The flight was performed under the provisions of 14 Code of Federal Regulations Part 91. Visual meteorological conditions prevailed, and no flight plan was filed for the planned cross-country flight to Paso Robles, California.

Occupant and Aircraft Information

The airplane was operated by California Flight Center, Inc., Long Beach, California, and had been rented to the pilot for his personal flight. Of the four occupants on board, the private pilot was seriously injured, one passenger received minor injuries, and two passengers were not injured.

Flight Details

The pilot reported performing a preflight inspection and being familiar with the airplane's takeoff performance and runway distance requirements. The airplane was loaded to near its maximum certificated gross weight, and the pilot elected to depart from near the 5,100-foot-long runway's midfield location. During the engine run-up, no mechanical discrepancies were noted. Full engine power was attained, the brakes were released, and the takeoff roll commenced. However, prior to reaching the prescribed rotation airspeed, the airplane's nose pitched up, and the airplane became airborne. The pilot continued attempting to maintain control while in ground effect, climbing over one wingspan above the ground. When the left side cockpit door inadvertently opened, the pilot closed it. Thereafter, the airplane stalled, impacted an estimated 6-foot-high dirt berm, and crashed into an open field about 1,000 feet south of the runway's departure end. Winds at a nearby airport 6 miles away were from 330 degrees at 6 knots at the time of the accident.

Pilot Actions

The pilot stated that he adhered to the prescribed procedures written in the airplane's checklists. The elevator trim tab was found in the full nose-up position, and examination of the system disclosed normal function.

Weight and Balance Findings

FAA inspectors from the Riverside, California, Flight Standards District Office responded to the accident site. About 40 gallons of fuel were found in each of the two wing tanks, for a total of 80 gallons onboard. The baggage compartment contents were removed and weighed, totaling 288 pounds; the airplane flight manual (AFM) lists a structural limit of 200 pounds. Utilizing the aircraft empty weight and center of gravity from the AFM, the actual weights of the occupants, the fuel load, and the baggage weight, the inspectors determined that the aircraft gross weight at the accident site was 4,173.41 pounds with a center of gravity at 117.9 inches aft of the datum. The AFM and the FAA approved Type Certificate Data sheet list the maximum allowable gross weight as 3,900 pounds with an aft center of gravity limit at 117.5 inches.

Contributing factors

Causes

Capability exceededIncorrect use/operationPilot

Other contributing factors

Tailwind