Nevada County Airpark, Grass Valley, CA

Location:  The Nevada County Airpark is located 3 miles east of Grass Valley, California.

History:

 
Nevada County Airpark Today:  Extensive fire fighting operations from June through October; Intensive flight training; Ultralights;

Nevada County Airpark, Grass Valley California

Airport Services and Amenities:  Alpine Aviation; County of Nevada; Sierra Mountain Aviation; Fuel; BP Jet, 100LL; Self service; 100LL; 24 hours; Food and lodging within 3 miles;

Special Events and Attractions: Empire Mine State Park; Nevada City;

Airport Area Accident History:

Accident occurred Saturday, August 02, 2008 in Grass Valley, CA
Probable Cause Approval Date: 9/26/2008
Aircraft: Piper PA-20, registration: N7635K
Injuries: 1 Uninjured.
The pilot reported that he made a wheel landing on the runway. He lowered the tail and started to apply the brakes when his right foot slipped off the rudder pedal. The plane veered left and he applied full left brake to avoid nosing into a drainage ditch head first. During this turn the tail wheel struck a boulder and the right wing tipped down and struck the ground.
The National Transportation Safety Board determines the probable cause(s) of this accident as follows: The pilot's failure to maintain directional control due to his foot slipping off one rudder pedal while braking. ===
Accident occurred Thursday, April 17, 2008 in Grass Valley, CA
Probable Cause Approval Date: 5/28/2008
Aircraft: Murphy Aircraft Murphy Rebel, registration: N3VK
Injuries: 1 Uninjured.
The pilot was attempting to land the tailwheel equipped airplane on an upsloping runway. The airplane touched down normally on the asphalt runway surface. During the landing roll the airplane began to ground loop. The pilot added power in an effort to recover and the airplane continued off the runway surface and encountered a ditch, incurring damage to the left fuselage structure. The pilot reported no preimpact mechanical malfunctions or failures with the airframe or engine. He added that the wind conditions were light and variable. The National Transportation Safety Board determines the probable cause(s) of this accident as follows: The pilot's failure to maintain directional control. ===
Accident occurred Sunday, February 17, 2008 in Nevada City, CA
Aircraft: Wilson RV-7, registration: N331KM
Injuries: 1 Fatal. This is preliminary information, subject to change, and may contain errors. Any errors in this report will be corrected when the final report has been completed. On February 17, 2008, at 1638 Pacific standard time, a Wilson RV-7, N331KM, collided with terrain approximately 1.7 miles northwest of Nevada City, California. The pilot operated the airplane under the provisions of 14 Code of Federal Regulations Part 91. The private pilot was killed, and the airplane was substantially damaged. Visual meteorological conditions prevailed, and no flight plan had been filed. The personal flight originated at Nevada County Air Park, Grass Valley, California, approximately 1610. A witness told a Federal Aviation Administration inspector on-scene that she heard the airplane's engine quit and observed the airplane in a descent just before the accident. The wreckage was located in heavily wooded terrain. ===
Accident occurred Saturday, August 02, 2008 in Grass Valley, CA
Probable Cause Approval Date: 9/26/2008
Aircraft: Piper PA-20, registration: N7635K
Injuries: 1 Uninjured.
The pilot reported that he made a wheel landing on the runway. He lowered the tail and started to apply the brakes when his right foot slipped off the rudder pedal. The plane veered left and he applied full left brake to avoid nosing into a drainage ditch head first. During this turn the tail wheel struck a boulder and the right wing tipped down and struck the ground.
The National Transportation Safety Board determines the probable cause(s) of this accident as follows: The pilot's failure to maintain directional control due to his foot slipping off one rudder pedal while braking. ===
Accident occurred Wednesday, August 16, 2006 in Grass Valley, CA
Probable Cause Approval Date: 12/28/2006
Aircraft: Stinson 108-2, registration: N9818K
Injuries: 1 Uninjured.
The pilot attempted to exit onto a taxiway during the landing roll; however, the airplane skidded off the runway where it impacted a cement culvert and nosed over. While on final approach the pilot noted the wind conditions were variable with up and downdrafts, as well as a crosswind condition. The pilot said the landing was normal; however, the airplane encountered a gust of wind during the rollout and he was unable to maintain directional control. A responding deputy noted a skid mark, 118.5 feet in length, from the runway to the edge of the taxiway where it continued on for an additional 35.7 feet into a dry grass area. The airplane struck a cement culvert and came to rest inverted, 40 feet beyond the cement culvert. The deputy reported that when he arrived at the airport the winds were out of the south from about 8 knots, gusting to 16. Witnesses to the accident reported that the airplane appeared to be traveling too fast after landing to safely make the turn onto the taxiway and the brakes locked up as the pilot attempted to turn. After the brakes locked up the airplane skidded off the runway and came to rest inverted after impacting a cement culvert. The National Transportation Safety Board determines the probable cause(s) of this accident as follows: failure of the pilot to maintain directional control on the landing rollout due to inadequate compensation for a gusty crosswind condition and an attempt to turn at an excessive taxi speed. ===
Accident occurred Saturday, July 22, 2006 in Grass Valley, CA
Probable Cause Approval Date: 3/26/2007
Aircraft: Piper PA-28-161, registration: N2115R
Injuries: 1 Uninjured.
On the pilot's second attempted takeoff, the engine lost power and the airplane overran the runway surface. The temperature was 96 degrees Fahrenheit, and the density altitude was calculated to be 6,273 feet mean sea level. The pilot was planning on making a local flight in the airplane to verify its performance. On the first takeoff attempt, the pilot aborted the takeoff due to loss of available engine power. He landed the airplane on the runway and taxied back to the run-up area to attempt another takeoff. He conducted another run-up at full power and noted no anomalies. During the second takeoff attempt, the airplane climbed to 60 feet and the engine lost power. The pilot force-landed the airplane on the remaining runway, the airplane overran the surface and encountered rough terrain. A Federal Aviation Administration inspector performed an inspection and test-run of the engine following the accident and found no operational anomalies. A condition known as vapor lock can occur when the engine heats the fuel lines and the contained fuel becomes a vapor. This tendency is increased if the fuel in the tank is warm, commonly as a result of high atmospheric temperatures. The fuel vapor can result in partial or complete interruption of fuel flow to the engine. The National Transportation Safety Board determines the probable cause(s) of this accident as follows: The loss of available engine power due to vapor lock. A contributing factor was the high temperature. ===
Accident occurred Monday, February 14, 2005 in Grass Valley, CA
Probable Cause Approval Date: 6/8/2005
Aircraft: Aeronca 7EC, registration: N4725E
Injuries: 1 Uninjured.
The airplane veered off the runway to the right, and the right wing collided with a tree. The pilot said he lost directional control during the roll out after landing. The pilot stated that the airplane and engine had no mechanical failures or malfunctions during the flight. The National Transportation Safety Board determines the probable cause(s) of this accident as follows: the pilot's failure to maintain directional control. ===
Accident occurred Monday, April 12, 2004 in Grass Valley, CA
Probable Cause Approval Date: 6/30/2004
Aircraft: Aeronca 65-TAC, registration: N39515
Injuries: 2 Uninjured.
The pilot experienced a loss of directional control, veered off the runway, and collided with trees while on the landing roll. The pilot stated that the runway he was attempting to land on is solely used for landing at the airport, due to an excessive gradient. During the approach, the pilot noted tailwind conditions and opted to perform a wheel landing. While on the landing roll, the airplane encountered a gust of wind from the right, resulting in the tail being pushed to the left. The airplane veered to the right and began a 45-degree arc off the right side of the runway. The pilot applied full left rudder pressure and left brake to counteract the veer. The airplane departed the right side of the runway and collided with trees. The pilot stated that on the right side of the runway are two groups of dense trees. In between the tree groups, about halfway down the runway, air funnels through creating wind gusts. He thought this was why he encountered sudden crosswind gusts. The pilot reported no preimpact mechanical malfunctions or failures with the airplane. The pilot reported that the winds were from 190 degrees at 5 knots. The National Transportation Safety Board determines the probable cause(s) of this accident as follows: the pilot's inadequate compensation for wind conditions and failure to maintain directional control of the airplane. Factors in the accident were wind gusts and tailwind/crosswind conditions. ===
Accident occurred Monday, January 19, 2004 in Grass Valley, CA
Probable Cause Approval Date: 10/27/2005
Aircraft: Cessna 172K, registration: N99LR
Injuries: 2 Fatal.
The airplane collided with trees while attempting to land in IFR conditions of near zero visibility in fog. While en route to the destination airport on an IFR clearance, the TRACON controller observed the airplane's transponder discrete code change to 7600 (used by flight crews to indicate a communications failure). The TRACON controller determined that the pilot could hear them, but they could not hear his transmissions. Because of the requirement for full communications in controlled, Class B airspace, they suggested the pilot contact a nearby airport outside of the Class B airspace on the frequency they provided. The pilot contacted the suggested ATCT while 12 miles west of that airport, and the controller could barely hear the pilot's transmissions. The pilot advised the tower to cancel his IFR flight plan and he would proceed visual flight rules (VFR) back to his departure airport without VFR flight following. This was the last communication from the pilot. Witnesses heard the pilot make two approach attempts to land at original departure airport but they could not see the airplane because the airport had become zero visibility and zero ceiling in fog about 20 minutes prior to the airplanes arrival. The National Transportation Safety Board determines the probable cause(s) of this accident as follows: the pilot's continued visual flight into instrument meteorological conditions and failure to maintain an adequate terrain/object clearance altitude. Also causal was the pilot's improper in-flight decision to return to the origin airport in the face of deteriorating weather conditions instead of diverting to a more suitable alternate.

Nevada County Airpark Approach / Landing:

FeedbackForm
Feedback Analytics