San Carlos Airport, San Carlos, CA

Airport Location:  The San Carlos Airport is located 2 miles north east of San Carlos, California.

Airport History:

The San Carlos Airport was moved to its present location in 1950.  Before that, the airport was located approximately one-half mile southwest of its current location at the site where a Best Buy is now located. This original San Carlos airport was opened by Frank S. Cooley prior to 1928.

San Carlos Airport Today:  Obstructions reported; 100' power lines parallel to and on the west side of the runway; Intensive flight training; Helicopter operations;



Airport Services & Amenities: Air West; Bel-Air International; Diamond Aviation; Golden Gate Helicopters; Rabbit Aviation Services; Zanette Aircraft Insurance Center; Restaurant on the field; Burger King; Izzy's; Sky Kitchen; Lodging within 2 miles;

Special Events and Attractions:  Hiller Air Museum; 

Airport Area Accident History:

Accident occurred Monday, September 21, 2009 in San Carlos, CA
Probable Cause Approval Date: 12/15/2009
Aircraft: CESSNA 172S, registration: N21591
Injuries: 1 Uninjured.
The student pilot's attention was momentarily diverted as he was taxiing around another airplane to the runup area. The pilot subsequently heard the right wing impact a fence post, which resulted in substantial damage to the wing's leading edge.
= = =
= = =
Accident occurred Saturday, March 28, 2009 in San Carlos, CA
Probable Cause Approval Date: 12/29/2009
Aircraft: PIPER PA-28-235, registration: N9249W
Injuries: 4 Serious.
The pilot had just departed on a local visual flight rules (VFR) flight when the airplane's engine suddenly lost all power as it was about 100 to 150 feet above ground level. Because of the airplane's low altitude, once the pilot checked the position of the magnetos, fuel selector, and fuel pump, he focused his attention on finding a landing spot in the nearby rough swampy terrain. During the landing, the airplane's wings and fuselage sustained substantial damage. A post-accident teardown inspection of the airframe, fuel system, air induction system, and the engine did not find any evidence of pre-accident anomalies or malfunctions.
= = =
= = =
Incident occurred Saturday, September 13, 2008 in San Carlos, CA
Probable Cause Approval Date: 11/9/2009
Aircraft: DIAMOND DA 40, registration: N419JS
Injuries: 1 Uninjured.
The pilot departed on a local area flight when the engine had higher than normal RPMs. The pilot elected to return to the departure airport and his mechanic inspected the airplane. The mechanic discovered a blister in the engine casing and fragments of metal in the oil. The engine was then disassembled and a ball bearing from the propeller governor was located in the engine which had the potential of resulting in a catastrophic engine failure. Examination of the engine showed that the ball bearings from the governor were able to pass through the oil drain hole of the governor. Follow up examinations of the propeller governor showed that the governor bearing race and plunger were assembled with the bearing race set screw and plunger hole misaligned. When the bearing race set screw was torqued down, the set screw tip flattened against the harder plunger surface. During operation, the set screw/plunger race separated.
= = =
= = =

Accident occurred Saturday, October 27, 2007 in San Carlos, CA
Probable Cause Approval Date: 9/26/2008
Aircraft: Beech F35, registration: N5050B
Injuries: 2 Uninjured.
After leveling off at 1,000 feet over a salt water bay for the short repositioning flight, the engine lost power. Attempts by the pilot to restart the engine proved unsuccessful, prompting him to ditch the airplane in the salt water bay. The airplane was recovered from the salt water environment about 24 hours after the ditching. The engine subsequently underwent two examinations, the first of which resulted in the engine running for a period of 5 seconds before losing power. A second later attempted test run was unsuccessful due to the effects of the extensive degree of salt water contamination and corrosion. A visual inspection of the engine failed to reveal any anomalies that would have precluded normal operation. The airplane had just come out of its most recent annual inspection the day prior to the accident, and maintenance records indicated the engine had accumulated 60.20 hours since its most recent overhaul. The pilot reported that prior to takeoff the fuel selector was positioned on the left main tank, and that 60 to 65 gallons of fuel was on board.
The National Transportation Safety Board determines the probable cause(s) of this accident as follows: A total loss of engine power for undetermined reasons. Contributing to the accident was the lack of suitable terrain for a forced landing. ===
Accident occurred Sunday, August 20, 2006 in San Carlos, CA
Probable Cause Approval Date: 2/28/2008
Aircraft: Cessna TR182, registration: N2526S
Injuries: 2 Uninjured.
The pilot landed on the runway 30 centerline with 20 degrees of flaps and an airspeed of 65 knots. After a ground roll of 100 feet the airplane suddenly veered to the left. Aileron and rudder inputs were ineffective and he decided to go around. He applied full power and retracted 10 degrees of flaps, and the airplane became airborne. The airplane then struck a sign during the climb out. After a flyby to check the landing gear position, the pilot again landed on runway centerline, and about 3/4 of the way down the runway he began to apply the brakes. The pilot discovered that the brakes were not working and the airplane veered off the right side of the runway and struck a taxiway sign. The airplane finally came to a stop in front of transient parking. Reported winds were from 360 degrees at 14 knots. No gusts were reported. The National Transportation Safety Board determines the probable cause(s) of this accident as follows: The pilot's inadequate compensation for the crosswind condition and failure to maintain directional control during the landing roll. ===
Accident occurred Friday, March 28, 2003 in San Carlos, CA
Probable Cause Approval Date: 9/1/2004
Aircraft: Enstrom F280FX, registration: N5698M
Injuries: 2 Uninjured.
The helicopter was returning from a local area photography flight when the engine lost power during the landing flare causing the helicopter to land hard. The pilot stated that he made a long approach towards the departure end of runway 30, he executed a 15-foot flare for landing. The low fuel pressure light illuminated, he verified that the fuel boost pump was on, and as he "rolled the throttle on," the engine "sputtered and went dead." In an attempt to safely land the helicopter the pilot made a hard autorotative landing causing substantial damage. Fueling receipts from Rabbit Aviation Services show that the helicopter was fueled on two separate occasions on the day of the accident. At 1125, 32.9 gallons of fuel were added, and at 1403, 39.4 gallons were added. The Enstrom 280FX has a usable fuel capacity of 40 gallons. At 30 inches of manifold pressure and 78 percent power, the endurance at sea level is 2.0 hours. At 32 inches of manifold pressure and 83 percent power, the endurance is 1.8 hours. The pilot reported taking off at 1445, and the accident occurred about 1650.
The National Transportation Safety Board determines the probable cause(s) of this accident as follows: Fuel exhaustion due to the pilot's inadequate fuel consumption calculations and his inadequate in-flight planning decision. A factor was the low altitude from which the autorotation was attempted. ===
Accident occurred Thursday, December 21, 2000 in SAN CARLOS, CA
Probable Cause Approval Date: 12/6/2002
Aircraft: Cessna 177RG, registration: N2102Q
Injuries: 1 Uninjured.
While on an extended downwind for landing the airplane experienced a power failure after throttle was applied. The pilot executed the prelanding and an emergency checklist. Engine power was not restored. According to the same account, the pilot turned the fuel selector to the "off" position before the forced landing was made in the slough west of the airport. The nose wheel was caught in the rough terain and the airplane came to rest inverted. Fuel was added before the flight and post crash examination revealed the tanks carried a supply 1 inch below the tabs. The airplane was successfully started after it was righted and ran roughly. The National Transportation Safety Board determines the probable cause(s) of this accident as follows: A loss of engine power for undetermined reasons during an extended downwind leg in the landing pattern. ===
Accident occurred Thursday, October 12, 2000 in SAN CARLOS, CA
Probable Cause Approval Date: 1/2/2002
Aircraft: Cessna 170B, registration: N2562D
Injuries: 1 Uninjured.
Upon completing one circuit around the traffic pattern, the pilot landed on runway 30. Upon slowing to about 15 miles per hour, the rudder lost effectiveness, and the airplane rolled toward the side of the runway. The pilot indicated that as his airplane was about to depart the runway he "stepped hard on the brakes," and the airplane nosed over. A witness reported that the midfield windsock indicated that a right quartering tail wind existed at the time of the mishap. According to San Carlos control tower personnel, at the time of the mishap the official wind was from 300 degrees at 4 knots. The National Transportation Safety Board determines the probable cause(s) of this accident as follows: The pilot's improper and excessive application of brakes resulting from his failure to maintain directional control during landing rollout. ===
Accident occurred Wednesday, September 27, 2000 in SAN CARLOS, CA
Probable Cause Approval Date: 7/17/2001
Aircraft: Mooney M20S, registration: N68FM
Injuries: 1 Minor.
The pilot's first landing approach to the runway was too high and he performed a go-around. The second approach to the same runway was also too high and the aircraft touched down and began porpoising. After two bounces the pilot attempted to abort the landing; however, the aircraft drifted off the runway to the left and the left wing struck a hangar in the northwest corner of the airport. The aircraft came to rest between two rows of hangars. The pilot reported that he attempted the landing abort after several bounces by placing 'the power to full, verified mixture rich, and placed the wing flaps in the 10 [degree] position.' He said the plane began to veer to the left of the runway and, although he applied right rudder and right aileron, the drift to the left continued. The stall warning horn never sounded prior to the left wingtip hitting the hangar. The pilot also reported there were no mechanical malfunctions with the airplane. The National Transportation Safety Board determines the probable cause(s) of this accident as follows: The pilot's failure to maintain directional control of the airplane during an aborted landing.
UTube Airport Approach / Landing: