Beechcraft 65 N832B
2 September 2010 · Redwood City, California, United States · Fatal
Summary
On 2 September 2010 at about 18:51 local time, a Beechcraft 65 registered N832B was involved in an accident near Redwood City, California, United States. 3 people were on board and 3 died. The aircraft was substantially damaged. The NTSB has published a probable cause for this accident; it is quoted in full below.
The record
- Date
- at 18:51
- Classification
- Accident
- Location
- Redwood City, California, United States
- Nearest airport
- San Carlos (SQL)
- Coordinates
- 37.5119, -122.2506
- Aircraft
- Beechcraft 65
- Registration
- N832B
- Category
- Airplane
- Engines
- 2
- Operator
- Not recorded
- Operating rule
- Part 91: General Aviation
- Purpose of flight
- Personal
- Phase of flight
- Not recorded
- Route
- San Carlos → Santa Clara
- Aircraft damage
- Substantial
- Weather
- VMC
- Light
- Day
- NTSB number
- WPR10FA448
People
3 people died.
| On board | Died | Serious | Minor | Uninjured |
|---|---|---|---|---|
| 3 | 3 | 0 | 0 | 0 |
Probable cause
A loss of power in the right engine for undetermined reasons and the pilot’s subsequent failure to maintain adequate airspeed, which resulted in a loss of control. Contributing to the loss of control was the regulatory certification basis of the airplane that does not require airspeed indicator markings that are critical to maintaining airplane control with one engine inoperative.
Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.
Read the full NTSB narrative
Shortly after takeoff for a repositioning flight for the airplane’s upcoming annual inspection, numerous witnesses, including the two air traffic controllers, reported observing the airplane climbing out normally until it was about 1/2 mile beyond the runway. The witnesses stated that the airplane then underwent a short series of attitude excursions, rolled right, and descended steeply into a lagoon. All radio communications between the airplane and the air traffic controllers were normal. Ground-based radar tracking data indicated that the airplane's climb to about 500 feet was normal and that it was airborne for about 40 seconds. Postaccident examination of the airframe, systems, and engines did not reveal any mechanical failures that would have precluded continued normal operation. Damage to both engines’ propeller blades suggested low or moderate power at the time of impact; however, the right propeller blades exhibited less damage than the left. The propeller damage, witness-observed airplane dynamics, and the airplane’s trajectory were consistent with a loss of power in the right engine and a subsequent loss of control due to airspeed decay below the minimum control speed (referred to as VMC). Although required by the Federal Aviation Administration (FAA)-approved Airplane Flight Manual, no evidence of a cockpit placard to designate the single engine operating speeds, including VMC, was found in the wreckage. The underlying reason for the loss of power in the right engine could not be determined. The airplane's certification basis (Civil Air Regulation [CAR] 3) did not require either a red radial line denoting VMC or a blue radial line denoting the single engine climb speed (VYSE) on the airspeed indicators; no such markings were observed on the airspeed indicators in the wreckage. Those markings were only mandated for airplanes certificated under Federal Aviation Regulation Part 23, which became effective about 3 years after the accident airplane was manufactured. Neither the Federal Aviation Administration (FAA) nor the airplane manufacturer mandated or recommended such VMC or VYSE markings on the airspeed indicators of the accident airplane make and model. In addition, a cursory search did not reveal any such retroactive guidance for any twin-engine airplane models certificated under CAR 3. Follow-up communication from the FAA Small Airplane Directorate stated that the FAA has "not discussed this as a possible retroactive action... Our take from the accident studies is that because of the accident record with light/reciprocating engine twins, the insurance industry has restricted them to a select group of pilot/owners…" Toxicology testing revealed evidence consistent with previous use of marijuana by the pilot; however, it was not possible to determine when that usage occurred or whether the pilot might have been impaired by its use during the accident flight.
Quoted verbatim from the NTSB record.
Other Beechcraft 65 accidents
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 2 Mar 2010 | Beechcraft 65-A90 | DeKalb, Illinois, United States | Eagle Air Transport | No injuries | - |
| 8 Feb 2010 | Beechcraft 65 | Lawrenceville, Georgia, United States | - | Fatal | 1 |
| 24 Feb 2010 | Beechcraft 65-B80 | Minneapolis, Minnesota, United States | Bemidji Aviation Services Inc | No injuries | - |
| 16 Feb 2009 | Beechcraft 65-A90-1 | Soldotna, Alaska, United States | Missionary Aviation Repair Center | No injuries | - |
| 6 May 2008 | Beechcraft 65-A90 | Titusville, Florida, United States | Titusville Drop Zone | No injuries | - |
| 3 Aug 2008 | Beechcraft 65-A90 | Pitt Meadows, Canada | Pacific Skydivers | Serious injuries | - |
Other accidents in this area
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 13 Jun 2010 | Grumman Acft Eng Cor-Schweizer G-164B | Courtland, California, United States | Walter Avery | Serious injuries | - |
| 7 Mar 2010 | Cessna 172P | Camarillo Airport, California, United States | Channel Islands Aviation Inc | No injuries | - |
| 27 Apr 2010 | Piper PA-30 | Merced, California, United States | - | Fatal | 1 |
| 12 Oct 2010 | Robinson R22 BETA | Long Beach, California, United States | Temco Sky Networks | Serious injuries | - |
| 15 Jun 2010 | Rans COYOTE II S6 | Lincoln, California, United States | Michael S. Gorden | Fatal | 2 |
| 12 Oct 2010 | Boeing A75N1(PT17) | Palm Springs, California, United States | Kent Thomas | No injuries | - |