Pine Mountain Lake Airport, Groveland, CA

Location:

History: Pine Mountain Lake is a unique private community close to Yosemite National Park, nestled into the natural landscape of the pines, oaks and mountains of Tuolumne County, Groveland, CA.

Pine Mountain Lake Airport Today:

The airport at Pine Mountain Lake is owned and operated by Tuolumne County. On-site facilities include fueling and parking.




Airport Services and Amenities:
Pine Mountain's lake consists of 202 surface acres with 6 miles of it being shoreline. Lakefront homeowners may have their own access to floating docks, beaches and sea walls. Other homeowners can enjoy the lake from one of three swimming beaches, picnicking and fishing areas.  They are the Main Marina, Dunn Court Beach, the Lake Lodge and from Fisherman’s Cove (fishing only). A water taxi shuttle operates between the four locations during the summer. Animals in the lake include: Rainbow Trout, Largemouth Bass, Catfish, Crappie, Blue Gill, Red Ear Perch, Crayfish, fresh water jelly fish, frogs and turtles.  Other wildlife in the area includes Deer, Gray Squirrels, Raccoons, Skunk, Possum, Mountain Lion, Bear and various birds, including bald eagles.

The Marina store is located conveniently at the Main Marina. Aside from taking care of boat registrations, launching, fishing licenses, and docking, owners and guests can enjoy various types of boat rentals. Rentals include kayaks, rowboats, sailboats, paddle boats, and fishing boats. The Marina Grill is open daily from May through September.

Pine Mountain Lake also offers a premier championship Gold Country Golf Course. It is available for public play and tournaments. After a long day on the greens, everyone can enjoy the Country Club Restaurant and Lounge. Other activities include tennis courts, a heated swimming pool, a full-service Equestrian Center that offers trail rides, special excursions, play days, and children’s horse camps, along with total care stalls, corrals, and paddock rentals for your horse.

Campground sites are available for property owners, guests and the general public. There are also many hiking and walking trails.
Special Events:

Airport Area Accident History:

On February 19, 2010, about 1915 Pacific standard time, a Piper PA-32R-301T, N4175A, collided with terrain in a residential area near Groveland, California. The pilot was operating the airplane under the provisions of Title 14 Code of Federal Regulations Part 91. The certificated private pilot and passenger were killed. The airplane was destroyed by impact forces and post crash fire. The cross-country personal flight departed San Carlos Airport, San Carlos, California, about 1830, with a planned destination of Pine Mountain Lake Airport, Groveland. Instrument night meteorological conditions prevailed at the accident site, and no flight plan had been filed.

A witness, who was located in a south facing room of a residence north of the Pine Mountain Lake runway, reported being startled by the sound of a "very loud engine." As the sound grew louder, the room became illuminated. The witness then looked out of the window and observed an airplane flying directly towards the house. Shortly thereafter, the witness felt a large impact, and observed a fireball erupt in an adjacent yard.

Another witness who was located in a north facing room in his residence, directly adjacent to the first witness, heard a sound that appeared to be emanating directly above his house. He described the sound as similar to an engine running at full power. He was concerned that someone was, "buzzing" his house and looked out of the window; a few seconds later he observed an explosion about 300 feet to the northeast in his neighbor’s yard. He reported light rain and mist to be present at the time of the accident.

A third witness, located 1/2 mile northeast of the approach end of runway 27, heard a low flying airplane, which he presumed was flying directly over his house, with engines running "full bore." He immediately ran onto his south facing deck, and a few seconds later observed a fireball erupt in the valley below. He stated that at the time of the accident the airport beacon was partially obscured by mist, and that from his vantage point the area of the explosion was encompassed with clouds.

First responders from the sheriff's department and additional witnesses all reported similar weather conditions of light rain, mist, and low clouds.

A pilot, who stated that he flies to the airport most weekends, reported attempting to land a Cessna 510 while on an instrument flight plan, about 1 hour prior to the accident. He reported that throughout the instrument approach he was unable to identify the runway environment. He performed a missed approach, and diverted to Modesto where he landed uneventfully. He stated that he has flown into the airport utilizing the instrument approach regularly over the last few years, and this was the first time he had to divert to an alternate airport.

A review of Federal Aviation Administration airman records revealed that the 70-year-old-pilot held a private pilot certificate with ratings for airplane single-engine land, and instrument airplane. The pilot held a third-class medical certificate issued in September 2008, with limitations that he must wear corrective lenses.

The airplane came to rest in a residential area about 1,200 feet north and 50 feet below the approach end of runway 27. The first identified point of contact was characterized by a flat, 30-foot-wide, near vertical swath, cut mid-level through the branches of a 50-foot-tall tree. A shattered wooden fence was observed at the base of the tree, 20 feet north of the swath. Fragments of both the right wingtip, and green navigation light were observed at the base of the fence. A ground indentation continued from the fence on a heading of about 035 degrees magnetic for about 25 feet. The indentation gave way to a crater located at the base of a tree. The crater measured 18 feet long, 10 feet wide and 4 feet deep, and was oriented on a heading of 060 degrees. Fragments of the right wing, cabin belly stringers, and a propeller blade were located within the crater. The tree and the area immediately surrounding the crater contained fragmented sections of wing and fuselage skins, the right flap, and the right aileron. The debris field continued on a 060-degree heading for an additional 120 feet to the site of the main wreckage.

The main wreckage consisted of the cabin, empennage, and engine. The cabin came to rest in line with the debris field, and was consumed by fire. The tail cone exhibited heavy crush damage and the empennage structure was observed partially attached, crushed, and twisted radially around the tail cone.

The engine remained partially attached to the firewall, and did not sustain fire damage. The remaining two propeller blades were attached at the hub. All of the blades exhibited leading edge gouges, and varying degrees of tip twist.

The wreckage did not display obvious evidence of in-flight fire, and all major sections of the airplane were accounted for at the accident site.

Examination of the area surrounding the accident site did not reveal any evidence that the airplane had made prior contact with trees or obstructions. (Groveland)

Accident occurred Wednesday, August 20, 2008 in Groveland, CA
Aircraft: Cessna TU206G, registration: N818CT
Injuries: 4 Minor. 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 August 20, 2008, about 0900 Pacific daylight time, a float-equipped Cessna TU206G, N818CT, nosed over after touchdown on Cherry Lake near Groveland, California. The pilot/owner operated the airplane under the provisions of 14 Code of Federal Regulations Part 91. The pilot and three passengers sustained minor injuries. The airplane sustained substantial damage to the left wing. Visual meteorological conditions prevailed for the local area flight that departed the Columbia Airport (O22), Columbia, California, about 0845. No flight plan had been filed for the flight destined for Cherry Lake. According to the pilot, there were no problems encountered during the brief flight from O22 to Cherry Lake. The pilot set up for a landing to the south. He noted the conditions as no wind and the lake appeared to be "glassy and black." He performed a GUMP check and noted four blue lights indicating that the landing gear was retracted for the water landing. He recalled telling his wife over the intercom system that he had observed the four blue lights. The pilot stated that as the airplane touched down there was a "severe" forward motion followed by the propeller blades contacting the water and the airplane pitching over coming to rest inverted. According to recovery personnel the flaps were noted in the full down position, the landing gear was in the down position, and the circuit breakers for the landing gear system and the landing gear advisory system were found in the OPEN positions. The landing gear handle was found in the UP position. The Wipline 3730 amphibious floats with an electrical/hydraulic actuation system manufactured by Wipaire, St. Paul, Minnesota. The system comes equipped with an airspeed actuated landing gear advisory system with an aural warning alarm. ==
Accident occurred Friday, June 27, 2008 in Groveland, CA
Probable Cause Approval Date: 7/30/2008
Aircraft: Beech F33/G, registration: N331HP
Injuries: 2 Uninjured.
During the landing flare, a crosswind gust blew the airplane off the runway centerline path. The airspeed was too low to perform a go-around, so the pilot attempted to regain the runway centerline. The airplane touched down while moving laterally, and the landing gear became side loaded and collapsed. The airplane slid off the runway and stopped. The National Transportation Safety Board determines the probable cause(s) of this accident as follows: The pilot's inadequate compensation for the gusty crosswind conditions and failure to maintain proper alignment at touchdown resulting in a side load on the landing gear, which caused them to collapse. ===
Accident occurred Saturday, April 19, 2008 in Groveland, CA
Aircraft: Cessna C175A, registration: N6868E
Injuries: 1 Serious. 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 April 19, 2008, about 1855 Pacific daylight time, a Cessna 175 Skylark, N6868E, experienced a loss of engine power and collided with a transmission wires following a departure from Pine Mountain Lake Airport, Groveland, California. The pilot, who was the owner, was operating the airplane under the provisions of 14 CFR Part 91. The commercial pilot, the sole occupant, sustained serious injuries; the airplane sustained substantial damage. The local personal flight was originating from Groveland. Visual meteorological conditions prevailed, and a flight plan had not been filed. An inspector from the Federal Aviation Administration (FAA) interviewed friends of the pilot that were based at Groveland. A friend stated that the pilot, who was additionally a certificated airframe and powerplant mechanic, had recently installed a new engine on the airplane. The pilot was conducting a series of high-speed taxi tests, when the airplane's groundspeed became excessive and it lifted off the runway surface. The airplane continued to climb and it appeared as though the pilot was attempting to return back to the airport. After the airplane made a 90-degree turn, the engine experienced a loss off power momentarily. The engine powered up again and then quit. The airplane collided with transmission wires and descended nose-low onto the road below. ===
Accident occurred Monday, March 12, 2007 in Groveland, CA
Probable Cause Approval Date: 5/29/2007
Aircraft: Piper PA-38-112, registration: N2489P
Injuries: 1 Uninjured.
The airplane landed long, veered off the runway, and collided with trees. The pilot flew over the airport and observed the windsock, which looked limp. He entered right traffic for runway 27 and noted the surrounding mountainous terrain. He did two rejected landings, and on the third attempt, he realized he was still high but felt that he could land in the first third of the runway. The airplane floated, and touched down in the last third of the runway. The airplane veered left off the runway, crossed a ditch, went down an embankment, and collided with trees. The pilot said there were no preimpact mechanical malfunctions or failures. 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 Thursday, July 06, 2006 in Groveland, CA
Probable Cause Approval Date: 10/31/2006
Aircraft: Barnard RV-6, registration: N157ST
Injuries: 2 Uninjured.
The airplane veered off the runway during a bounced landing recovery, went through an airport perimeter fence, and collided with trees in a residential backyard. The pilot reported that he miscalculated the landing flare. The airplane landed hard and bounced into the air. The pilot added full power to abort the landing, but did not compensate for the p-factor. The airplane turned to the left, impacted the runway, traversed through the airport perimeter fence, and down an embankment where it came to rest in a residential backyard between trees. The pilot reported that there were no mechanical anomalies noted with the airplane that would have precluded normal operation. The National Transportation Safety Board determines the probable cause(s) of this accident as follows: the misjudged flare by the pilot that resulted in a hard bounced landing, and his failure to maintain directional control during the attempted recovery. ===
Accident occurred Sunday, August 14, 2005 in Groveland, CA
Probable Cause Approval Date: 8/29/2006
Aircraft: Barnes Lancair Legacy, registration: N508DB
Injuries: 1 Uninjured.
Following fuel exhaustion in cruise flight, the pilot made a forced landing in an open field. The pilot elected to land with the landing gear retracted. The airplane was substantially damaged as it slid to a stop and hit a fence. The pilot said that prior to takeoff he believed he had 18 gallons of fuel onboard for the trip that he calculated would require 8 gallons. Upon his examination of the airplane the pilot noted that the fuel quantity sensors were improperly calibrated. The pilot reported that he did not experience any malfunction or failure with his airplane. The National Transportation Safety Board determines the probable cause(s) of this accident as follows: The inaccurate fuel quantity sensors and the pilot's failure to verify the fuel quantity on board prior to takeoff, which resulted in fuel exhaustion. ===
Accident occurred Saturday, February 07, 2004 in Groveland, CA
Probable Cause Approval Date: 4/28/2004
Aircraft: Bellanca 7ECA, registration: N5032G
Injuries: 1 Uninjured.
The airplane made a hard landing and veered of the runway while attempting to land. When the airplane was on final approach, the pilot determined that he was high above the glide path, but elected to perform the landing. During touchdown, the airplane hit hard and bounced back into the air. Upon returning back down onto the runway, the airplane veered to the left. It continued off the runway and encountered a ditch. The pilot reported no preimpact mechanical malfunctions or failures with the airplane. The National Transportation Safety Board determines the probable cause(s) of this accident as follows: the pilot's failure to maintain a proper glide path and misjudged landing flare, which resulted in a hard landing. Also causal was the pilot's inadequate recovery from a bounced landing, resulting in a loss of directional control and collision with terrain ===
Accident occurred Saturday, January 03, 2004 in Groveland, CA
Probable Cause Approval Date: 3/30/2004
Aircraft: Piper PA 28-181, registration: N9272Q
Injuries: 2 Uninjured.
The left wing of the airplane collided with a parked vehicle on the taxiway. The pilot was taxiing down the center of the taxiway, and was distracted by light snow and slush located in a dip. While he was focused on the dip, the collision occurred. The pilot did not report any mechanical problems with the airplane prior to the accident. The National Transportation Safety Board determines the probable cause(s) of this accident as follows: the pilot's inadequate visual lookout, and his failure to maintain obstacle clearance. Factors to the accident were the parked vehicle, and the pilot's diverted attention. ===
Accident occurred Monday, May 13, 2002 in GROVELAND, CA
Probable Cause Approval Date: 3/28/2006
Aircraft: Cessna T210M, registration: N761LX
Injuries: 2 Fatal.
The airplane collided with multiple trees during an attempted forced landing in mountainous terrain following a catastrophic engine failure in cruise. The flight was obtaining VFR flight following from air route traffic control center (ARTCC) when the facility lost radar and radio contact. The airplane came to rest near the edge of an elliptical meadow, which was about 1 mile long by 1/4 mile wide, with the long axis oriented east and west. The meadow was in mountainous terrain and surrounded by trees over 100 feet tall. The debris path was along the eastern edge of the meadow on a magnetic bearing of 210 degrees. Multiple large trees were observed with broken branches and major impact marks on their trunks. The crankcase had a 3-inch diameter hole in it above cylinder number 3. Examination of the engine found that the crankshaft fractured and separated at the rear of the number 4 cheek. The fracture was at the forward radius of the number 2 main bearing journal. Smeared metal was on the fracture surfaces. A metallurgical examination determined that a large portion of the fracture surface exhibited smooth crack arrest markings typical of fatigue propagation. Failure of the crankshaft was caused by a fatigue crack in the cheek between the number 3 rod journal and the number 2 main bearing journal. The fracture of the crankshaft caused the additional damage to the engine, including the separation of the numbers 3 and 4 connecting rods from their respective journals, and would have led to a complete loss of engine power. The origin of the fatigue fracture was in the transition between the number 2 main bearing journal surface and the forward fillet radius, approximately 0.036 inches below the surface of the journal. No metallurgical anomalies or manufacturing process errors were found to explain the fatigue initiation. This failure is very similar to a number of others investigated by the Safety Board's Materials Laboratory in the past, with a fatigue crack initiating just below the hardened case layer. As with many of those previous events, there were no material or microstructural defects that could be identified as the root cause of the fatigue initiation. The crankshaft met design material specifications. The National Transportation Safety Board determines the probable cause(s) of this accident as follows: a catastrophic engine failure due to the fatigue fracture and failure of the crankshaft. A factor contributing to the accident was the unsuitable nature of the mountainous terrain for a successful forced landing. The precipitating cause of the fatigue fracture could not be determined. ===
Accident occurred Monday, January 14, 2002 in Groveland, CA
Probable Cause Approval Date: 3/2/2004
Aircraft: Piper PA-28-180, registration: N3624R
Injuries: 1 Serious.
The airplane collided with a vehicle while attempting to make a precautionary landing on a highway. When the pilot arrived in the destination area he was confronted with a low stratus cloud condition. He diverted to another airport and landed. He contacted an operator at the destination, who told him that there were visual flight operations there with cloud bases about 1,500 to 2,000 feet. He departed the diversionary airport and proceeded towards his destination. Unable to descend through or maneuver around the stratus, he returned to the original diversionary airport, which was now covered by the stratus deck, as were other local airports. Realizing he was now too low on fuel to reach an airport in visual conditions, he contacted Oakland Air Traffic Control Center and requested assistance. The center provided vectors towards airports, but due to the weather conditions, the pilot was unable to find the airports. The consensus was to land the airplane as soon as possible and before fuel exhaustion. The pilot spotted a forestry camp with a windsock near a highway. He was successful in landing on the highway; however, the highway had a curve that prevented him from seeing an on-coming vehicle. He attempted to avoid the vehicle but the wing tip clipped it, causing him to lose control and collide with trees. The National Transportation Safety Board determines the probable cause(s) of this accident as follows: the pilot's improper preflight planning and improper weather evaluation.


Pine Mountain Lake Airport Approach / Landing: