Placerville Airport, Placerville, CA
Airport Location: The Placerville Airport is located 3 miles east of
Placerville, California.
Airport History:
Placerville
Airport Today: Obstructions reported; Hills east of the airport;
Helicopters operations; Ultralights;
Airport
Services & Amenities: Placerville Aviation; Stancil Aviation; Helipads;
Fuel; Air BP Jet, 100LL; Self service; 100LL, Jet, 24 hours; Public
transportation; taxis; rental cars available; Food and lodging within 3
miles;
Special Events and
Attractions: American River Rafting; Coloma State Park; Gold Bug Mine;
Wineries; Golf; Sly Park Lake;
Airport
Area Accident History:
Accident occurred Saturday, October 17, 2009
in Placerville, CA
Probable Cause Approval Date: 3/3/2010
Aircraft: AEROMOT AMT-200(SU, registration:
N107MJ
Injuries: 1 Uninjured.
The pilot reported that during the landing
rollout at the private airport, the glider's
left wing struck a series of bushes located
along the side of the landing runway. After
striking the bushes, the glider swerved, exited
the runway and came to rest in a ravine located
along the right side of the runway. The glider
sustained substantial damage to the right wing
and aileron. The pilot reported that the
airplane's wing span is approximately 60-feet
and the width of the paved runway is
approximately 50-feet, with a 10-foot shoulder
on each side of the runway. The pilot reported
the bushes were located approximately 900-feet
from the landing threshold, were 4-7 feet tall,
and 8-12 feet from the pavement edge on
neighboring property to the north of his runway.
In a written report, he indicated that there
were no mechanical malfunctions or failures with
the glider at the time of the accident.
Following the accident, the neighboring property
owner removed the
bush.
= = =
= = =
On June 13, 2009, about 1750 Pacific Daylight
time, an amateur built Howard Long EZ
experimental airplane, N7999H, was substantially
damaged when it collided with a stationary
vehicle during landing roll at the Placerville
Airport (PVF), Placerville, California. The
airplane was registered to and operated by the
pilot under the provisions of Title 14 Code of
Federal Regulations Part 91. The private pilot,
sole occupant of the airplane, was not injured.
Visual meteorological conditions prevailed and
no flight plan was filed for the personal
flight. The cross-country flight originated from
Marysville, California at 1715, with an intended
destination of PVF.
In a written statement, the pilot reported that
during cruise flight, he noticed an unusual yaw
and obtained visual assistance from the pilot of
another airplane to detect the source of the
yaw. The pilot stated that the left winglet was
observed "out of alignment." The pilot entered
the traffic pattern for runway 23, a 4,201-foot
long and 75-foot wide asphalt runway. While
turning final, the pilot noticed that the left
rudder was "possibly inoperative." Following an
uneventful landing, the pilot applied light
pressure to both the left and right brakes. The
pilot noted that the left brake was inoperative
and the airplane began to veer to the right.
Despite the pilot's control inputs, the airplane
exited the runway onto a parallel taxiway. The
pilot stated that the airplane was heading
towards a row of stationary airplanes and
applied full right rudder/brake to miss the
parked aircraft. Subsequently, the airplane
impacted an unoccupied stationary vehicle
and came to rest upright.
Examination of the airplane by the pilot
revealed that the right wing, fuselage, and left
wing were structurally damaged.
Examination of the airplane's flight control and
brake system was conducted by a Federal Aviation
Administration (FAA) inspector. The inspector
reported that the left and right brake systems
are independent of one another. A 14-foot long
8th inch diameter stainless steel cable was
routed through the interior area of the fuselage
from the rudder pedals to a bellcrank located
near the brake master cylinder on the engine
firewall. The left and right brake cables were
mostly routed independently from the forward
cockpit rudder pegs through a stainless steel
sleeve, which was embedded within the fuselage
fiberglass structure.
The inspector further reported, to allow the
cables to be routed through an auxiliary set of
rear mounted rudder foot pegs, about 8 inches of
each brake cable was exposed underneath the
floor of the rear cockpit. Each cable passed
through the middle of a neoprene plastic
housing, which was an attachment point for the
rear foot pegs. The neoprene plastic housing was
attached to an aluminum sliding fixture, which
was mounted to the interior fuselage structure.
A compression sleeve band swaged onto the brake
cable allowed the cable to engage the neoprene
plastic housing when forward pressure was
applied to the rear foot pegs.
The left brake primary cable was disconnected
from the bellcrank. The left master cylinder
brake unit was actuated manually and functioned
normally. The cable, outer casing and general
routing were inspected. The inspector noted
normal wear and reduction of cable tension on
the left brake cable. The left brake cable was
reattached to the bellcrank assembly. A small
amount of sideways pressure was applied to the
brake cable within the exposed area under the
rear cockpit floor. The cable compression sleeve
contacted the aluminum sliding fixture.
Subsequently, normal pressure was applied to the
forward left foot peg with restricted forward
movement noted.
The inspector added that prior to the accident
flight; the airplane was unoccupied and parked
at an air show. An unoccupied airplane was blown
into the left wing of the accident airplane by a
dust devil.
= = =
= = =
On October 10, 2008, at 1715 Pacific daylight
time, a Cessna 210, N7418E, landed hard
following a loss of engine power while on
approach to runway 23 at the Placerville Airport
(PVF), Placerville, California. The private
pilot/owner operated the airplane under the
provisions of Title 14 Code of Federal
Regulations Part 91 as a personal cross-country
flight. The airplane sustained substantial
damage to the left wing. The pilot and one
passenger were not injured. Visual
meteorological conditions prevailed for the
flight that departed the Corona Municipal
Airport (AJO), Corona, California, about 1440,
for Placerville. No flight plan had been filed.
According to the pilot, he attempted to contact
the common traffic advisory frequency (CTAF) for
traffic advisories to the airport at 10 miles
out, and again at 5 miles out, with no response.
Upon arriving at PVF, he overflew the airport at
4,000 feet to check the wind direction. He made
a right-hand entry to the traffic pattern for
runway 23. On downwind he lowered the gear and
set up for landing. He was on a mile final with
flaps at 30 degrees and the airspeed at 85
knots. He thought his approach was high about
1/2 mile out, so he initiated a forward slip to
lose altitude; he returned to level flight about
200 feet above the ground. The pilot stated that
he was still high and close to the runway
threshold. He decided to go around and pushed
the throttle full in; however, the engine did
not respond. He checked the settings, reduced
the throttle, and then pushed the throttle in
again with no response.
The pilot reported that due to obstacles off the
end of the runway, he decided to make a forced
landing on the remaining last half of the
runway. He told his passenger to brace for a
hard landing and then pointed the nose toward
the runway. He stated at that point the
airplane's altitude was about 50 feet above the
ground. When they were about 10 to 15 feet above
the ground, he pitched up and landed flat on all
three landing gear. The nose landing gear tire
popped, and after applying brakes, collapsed.
The propeller struck the ground stopping the
engine. The pilot lifted his foot off the left
brake, and the airplane slid off the runway to
the right. The airplane slid about 40 feet
before coming to a stop. The pilot noted damage
to the front engine cowling, the nose landing
gear, and the left wing spar.
A witness to the accident reported that he was
standing at the opposite end of the runway when
he saw the airplane enter the traffic pattern
for runway 23 from the east. The witness
indicated that the airplane was landing with a
tailwind of about 8 to 10 knots. The airplane
appeared to be too high on the approach, and
appeared to be in a slip in an effort to lose
altitude on final. The witness was able to hear
the engine for a short period of time and it did
not sound abnormal. From his position, the
airplane appeared to touch down about halfway
down the runway, and bounced 2 times. The next
thing he saw was a large cloud of dust; when it
finally cleared he saw the accident airplane’s
tail in the air.
A Federal Aviation Administration (FAA)
inspector examined the airplane at Placerville
Aviation. A visual examination of the airplane
revealed that the fuel tanks had not been
breached during the accident. Maintenance
personnel reported that they drained 9.6 gallons
of fuel from the left fuel tank, and 15 gallons
from the right fuel tank. Visual examination
revealed no mechanical anomalies. Maintenance
personnel removed the spark plugs, which
appeared to be good condition, and fuel was
found in the gascolator. An engine ground run
was performed; the engine started normally, the
magneto check was performed at 1,700 revolutions
per minute (rpm) and a normal magneto drop was
observed. The engine was then run at full power
with no "hesitation or missing experienced."
= = =
= = =
Accident occurred Friday, January 11, 2008 in Placerville, CA
Probable Cause Approval Date: 8/28/2008
Aircraft: Piper PA-24-250, registration: N7988P
Injuries: 1 Uninjured.
The pilot reported that shortly after touchdown,
the right main landing gear collapsed, and the airplane veered off the
runway. After exiting the paved runway, the left main and nose landing gear
collapsed. The airplane received structural damage to the right wing.
Examination of the landing gear system revealed that the left main landing
gear actuator rod was separated, and that the fracture was consistent with
overload; no other anomalies were found. Continuity was established
throughout the landing gear system. The landing gear was extended manually
and locked in the down position. The landing gear warning light functioned
normally when tested. The National Transportation Safety Board determines
the probable cause(s) of this accident as follows: The collapse of the right
main landing gear during landing for undetermined reasons. ===
Accident occurred Tuesday, September 11, 2007 in
Placerville, CA
Probable Cause Approval Date: 11/29/2007
Aircraft: Mooney M20D, registration: N1229X
Injuries: 1 Uninjured.
The pilot did not extend the gear prior to
landing and the airplane sustained substantial damage to the tubular
structure on the underside of the fuselage. The pilot had recently purchased
the airplane and was flying it on a cross-country flight. During the flight,
the pilot became ill and diverted to a nearby airport. The airplane bounced
upon touchdown and the airplane skidded down the runway. The pilot reported
to responding police personnel that he forgot to extend the landing gear.
Post accident examination of the airplane and landing gear systems by the
Federal Aviation Administration inspector revealed no mechanical anomalies
with the landing gear system. The National Transportation Safety Board
determines the probable cause(s) of this accident as follows: The pilot's
failure to extend the landing gear prior to landing. A contributing factor
was the pilots impaired performance. ===
Accident occurred Thursday, October 14, 2004 in
Placerville, CA
Probable Cause Approval Date: 12/28/2004
Aircraft: Cessna 182RG, registration: N6071C
Injuries: 2 Minor.
The airplane ran off the departure end of the
runway during the landing roll, encountered soft soil, and nosed over. On
landing, the airplane floated most of the length of the runway before it
finally touched down and then the pilot applied brakes. While the pilot
applied a substantial amount of brake pressure, the airplane skidded to the
end of the runway, into soft dirt, over an embankment, and came to rest
inverted. The pilot reported no pre-impact 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
misjudged distance and speed, and failure to attain the proper touchdown
point, which resulted in the airplane overrunning the runway surface and
nosing over after encountering soft terrain. ===
Accident occurred Thursday, March 18, 2004 in
Placerville, CA
Probable Cause Approval Date: 1/31/2006
Aircraft: Globe GC-1B, registration: N369BZ
Injuries: 1 Serious.
The airplane collided with trees and terrain
following a loss of engine power in the takeoff initial climb. The pilot
reported that he had just dropped off a passenger and was repositioning the
airplane to another airport. At 200 to 300 feet above ground level (agl) in
the takeoff initial climb the engine lost power. He attempted to turn back
to the runway but did not have enough altitude. He elected to stall the
airplane into the trees on the south slope of the airport boundary. The
accident was witnessed by personnel at the airport. The witnesses reported
that the pilot was departing using runway 23, the airplane took off and did
a steep, almost vertical ascent, and banked hard to the left (south). The
pilot appeared to stall the airplane, as it went into the trees on the south
side of the runway. The pilot held an airframe and powerplant mechanic
certificate and was the primary maintainer of the airplane. Federal Aviation
Administration inspectors examined the wreckage at the accident scene and
Safety Board investigators later examined the wreckage following recovery.
Disassembly of the gascolator revealed that both the upper and lower gaskets
in the gascolator were 1/8 to 3/16 inches smaller in diameter than the
gascolator canister and the top and bottom covers. The investigators
observed that in order to affect a seal, both gaskets had to be centered
when installed. Both gaskets were off center. No fuel was observed in the
fuel lines and the manifold valve was disassembled and found to be dry and
void of any fuel. The manifold valve body and screen were clean. No other
discrepancies were found during the engine examination. The National
Transportation Safety Board determines the probable cause(s) of this
accident as follows: a loss of engine power due to an improperly sized and
installed set of sealing gaskets in the gascolator, which resulted in fuel
starvation. A factor to the accident was the unsuitable terrain for the
forced landing. ===
Accident occurred Thursday, January 29, 2004 in
PLACERVILLE, CA
Probable Cause Approval Date: 4/28/2004
Aircraft: Piper PA-28-161, registration: N28385
Injuries: 2 Uninjured.
While attempting to land, the airplane undershot
the runway and collided with terrain short of the runway, shearing off the
main landing gear. The student pilot was practicing night flying. While on
final approach, the airplane was below the glide path and he attempted a
go-around. The airplane's main gear collided with a berm located before the
runway. The airplane bounced and the ELT (emergency locator transmitter)
became activated. The impact sheered off the left main landing gear and the
right main landing gear was still attached, but dangling from the strut.
After testing the airplane's controllability, the certified flight
instructor (CFI) determined it was in "flyable" condition and elected to
return to the airport the flight originated from. He made a normal approach
and started his rollout solely on the nose wheel. Although the airplane did
not have any brakes, the airplane came to rest about three quarters of the
way down the runway. The CFI did not report any mechanical malfunctions 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
failure to attain a proper glide path during the final approach and delayed
go-around, resulting in an undershoot of the runway. The inadequate
supervision of the flight and flight instructor's delayed remedial action
was also causal. ===
Accident occurred Monday, December 08, 2003 in
Placerville, CA
Probable Cause Approval Date: 4/28/2005
Aircraft: Iniziative Industriali Italian Sky
Arrow 650 TC, registration: N14XL
Injuries: 1 Fatal.
The airplane entered a stall/mush condition
during the takeoff initial climb, descended back to ground impact, veered
off the runway, and collided with trees and terrain. A witness saw the
airplane taxi to the runway about 0650. The nearest weather reporting
station was 20 miles northwest, and at 0630, recorded a temperature of 03 C,
the dew point 0 C, with clear sky conditions. A Federal Aviation
Administration inspector lives 8 miles from the airport and reported that
there was frost on his outdoor furniture that morning. Another pilot stopped
by the airport around 0510, and noted that the top of the wings of his
airplane and others had frost and ice on them. The first responder to the
accident reported that large water droplets covered the tops of the wing.
The wreckage was located approximately 1,450 feet down the runway and 140
feet to the south on downhill sloping terrain. Approximately 1,250 feet down
the runway, a 21-foot-long ground scar resembling tire tracks was located on
a grass shoulder area on the south side off the runway. The track was angled
away from the runway and ran in a direction pointing towards the airplane
wreckage. The tracks originated about the middle of a grass shoulder area
that parallels the runway. Between and forward of two narrow parallel tracks
was an elongated and much wider area of disturbed earth that approximated
the dimensions of the aircraft's nose. Examination of the wreckage found no
evidence of a preimpact malfunction or failure of the control system or
power plant. Following recovery of the wreckage, the engine was test run
successfully while still installed in the airframe. Using the airplane
flight manual the takeoff ground roll under the accident ambient conditions
was calculated as 912 feet and the distance to clear a 50-foot obstacle was
1,556 feet. The normal takeoff flap configuration, as described in the
Flight Manual, is the 10-degree setting. The flaps were found in the
retracted position with the cockpit control in a matching setting. The
National Transportation Safety Board determines the probable cause(s) of
this accident as follows: the pilot's failure to fully remove an
accumulation of ice and frost on the wings, which led to an inadvertent
stall/mush and collision with the ground. A factor in the accident was the
pilot's failure to correctly configure the flaps for takeoff. ===
Accident occurred Friday, June 07, 2002 in
Placerville, CA
Probable Cause Approval Date: 7/29/2004
Aircraft: Mooney M20E, registration: N1285X
Injuries: 1 Serious.
About 6 miles from the pilot's home airport, all
engine power was lost. The airplane impacted trees during its approach to a
landing. A witness reported observing the airplane glide in very quietly
with its propeller barely turning "as if only from the wind." The witness
indicated that the airplane "skipped off the ground once, as if trying to
land, and then lifted back into the air again." Thereafter, the airplane
came back down and crashed into a grove of trees. The accident site was
about 6 miles from the pilot's destination airport. No evidence of fuel
spillage was noted on the ground around the crashed airplane. Between 10 and
15 drops of fuel were found in fuel lines. No evidence of preimpact
mechanical malfunctions was observed during the engine examination. The
National Transportation Safety Board determines the probable cause(s) of
this accident as follows: A loss of engine power due to the pilot's
inadequate in-flight planning/decision which led to fuel exhaustion. ===
Accident occurred Friday, August 17, 2001 in
Placerville, CA
Probable Cause Approval Date: 5/21/2002
Aircraft: JOHNSON LANCAIR 360, registration:
N417DJ
Injuries: 2 Fatal.
The airplane dove into a residential property
adjacent to the pilot's residence in near-vertical flight. Neighbors
believed the pilot intended to fly over his home to alert his wife prior to
landing at the nearby airport. The neighbor, in whose front yard the
airplane crashed, reported there was a brief whining sound before the crash.
When he opened the front door, the wreckage was in his front yard within a
few feet of the house. He said there are trees surrounding the location, and
the fact that the plane didn't hit any of them told him it had to have come
nearly straight down and narrowly missed his house. The wreckage was
scattered in a fan-shaped pattern over about 200 feet to the northwest. The
engine was embedded into the (very hard) ground about 10 inches in a
near-vertical attitude and with the propeller attached. Examination of the
wreckage at an impound facility did not reveal any evidence of a preimpact
mechanical failure; however, the flight control cables were severed at
several locations and it was not possible to determine if the entire
aircraft was present due to extensive fracturing of the composite structure.
There was no fire. The National Transportation Safety Board determines the
probable cause(s) of this accident as follows: In-flight loss of control for
undetermined reasons. ===
Accident occurred Tuesday, July 24, 2001 in
Placerville, CA
Probable Cause Approval Date: 2/25/2003
Aircraft: Cessna 172M, registration: N8962V
Injuries: 1 Minor.
Upon reaching the destination airport on a dark,
nighttime cross-country flight, the pilot's approach was too high and fast,
so he performed a go-around. On his second approach, the pilot was also too
high, but the airplane touched down on the 4,200-foot-long runway. Concerned
about being able to stop before reaching the runway's departure end, the
pilot added full engine power and tried to go around. The engine power
increased normally. During the initial climb out, the pilot experienced
difficulty controlling the airplane. Contrary to Cessna's published
recommended balked landing procedure, the pilot failed to retract the wing
flaps from their 40-degrees setting. The airspeed was slow, the airplane
stalled, and it impacted trees and terrain. About 1.5 months earlier, the
pilot was issued a private pilot certificate. The accident occurred during
the pilot's first, solo, night cross-country flight, and his total
pilot-in-command night experience was 1.5 hours. The National Transportation
Safety Board determines the probable cause(s) of this accident as follows:
Inadequate airspeed during climb out following an aborted landing that was
precipitated by the pilot's misjudged speed/distance on final approach.
Also, contributing to the accident was the pilot's inexperience in the type
of operation, his failure to properly configure the airplane's flaps for the
go-around, and the dark nighttime condition. ===
Accident occurred Monday, January 01, 2001 in
Placerville, CA
Probable Cause Approval Date: 11/6/2001
Aircraft: Wallace Rotorway EXEC 152,
registration: N94LW
Injuries: 1 Uninjured.
The student pilot finished building the
helicopter and this was its first flight. He had received 11 hours of flight
instruction and was endorsed for hover only solo. The pilot reported that he
was 1-2 feet in the air and as he began backing the helicopter the tail
rotor guard struck the ground, the main rotor struck the tail boom, and the
left skid struck the ground. The skid collapsed and the helicopter rolled
over. After exiting, the pilot attempted to right the helicopter, but fuel
leaking from the fuel cap ignited when it contacted the exhaust. The
helicopter was destroyed in the subsequent fire. The National Transportation
Safety Board determines the probable cause(s) of this accident as follows:
The failure of the student pilot to maintain adequate ground clearance while
hovering.
Airport Approach /
Landing: