Amateur-built LONG EZ accident near Placerville, California, June 14, 2009
On June 14, 2009, a amateur-built LONG EZ, registered N7999H, was substantially damaged in an accident during landing (landing roll) near Placerville, California (Placerville Airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot's inability to maintain directional control during the landing roll due to a jammed brake cable.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- June 14, 2009 · cases in 2009
- Place
- Placerville, California · Placerville Airport · cases near this airport · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Amateur-built LONG EZ
- Registration
- N7999H · registry record · serial 721
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot reported that following an uneventful landing, he 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 towards a row of stationary airplanes. He applied full right rudder/brake to miss the parked aircraft. Subsequently, the airplane impacted an unoccupied stationary vehicle which resulted in structural damage to both wings and fuselage. Examination of the brake system by a Federal Aviation Administration inspector revealed no anomalies with the left brake master cylinder. The inspector reported that the brake control cable was routed 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 that was mounted to the interior fuselage structure. A compression sleeve band attached to the brake cable allowed the cable to engage the neoprene plastic housing when forward pressure was applied to the rear foot pegs to actuate the brakes. The inspector stated that a small amount of sideways pressure was applied to the brake cable 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 complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Runway excursion during landing (landing roll)
- Sys/Comp malf/fail (non-power) during landing (landing roll) defining event
- Ground collision during landing (landing roll)
The NTSB's findings
- cause Aircraft › Aircraft systems › Landing gear system › Brake › Malfunction other cases naming the landing gear
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Directional control › Attain/maintain not possible
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 447 hours in all; 291 in this make and model; 19 in the last 90 days; 4 in the last 30 days; 384 as pilot in command
- Last flight review: October 17, 2007
- Medical certificate: Class 3 (without waivers/limitations)
- Seat: ctr
- Injury: no injuries
The aircraft
- Airframe total time: 1,239 hours
- Last inspection: condition inspection, April 5, 2009; 7 hours since
- Maximum gross weight: 1,600 lb
- Seats: 2
- Landing gear: retractable
- Engine: Lycoming O-235 SERIES (piston); 0 hours total
The flight
- Departed from: MYV Marysville CA
- Destination: PVF Placerville CA
- Flight plan: none
- Runway 23, 4,201 ft by 75 ft
Weather at the time
- Light: daylight
- Wind: from 200° at 7 knots
- Visibility: 10 statute miles
- Sky: overcast at 4,100 ft; ovct at 4,100 ft
- Temperature: 70°F (21°C), dew point 52°F (11°C)
- Altimeter: 29.94 inHg
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
3 documents, released by the NTSB on September 11, 2009. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 9 pages | View Download |
| 2 | Reports from Federal Agencies- FAA Inspector Statement | PDF, 2 pages | View Download |
| 3 | Photo 1: Aft Cockpit Left Brake Control Cable Assembly. | PDF, 1 page | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Connections how this case links to the rest of the register
- N7999H on the register today · the tail number may have moved to another aircraft since
- Engine: Lycoming O-235 SERIES 6,132 aircraft carry this series today · as the NTSB recorded it
- Placerville Airport · nearest airport
- Yuba County · departed from
- Accidents and incidents in California 9,080 since 1982 · 1,093 in the last ten years
- California 28,525 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/WPR09LA287.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.