# NTSB LAX01LA223: Rudolph Venture, N84V, Grass Valley, CA, June 26, 2001 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: June 26, 2001, 08:40 local (15:40 UTC) - Place: Grass Valley, CA - Coordinates: 39.228889, -121.005279 - Nearby events: https://openairdocs.org/map.md?lat=39.2289&lon=-121.0053&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report February 5, 2002 - Report: Approved by Office Director - Parties: FEDERAL AVIATION ADMINISTRATION - NTSB case key (mKey): 53354 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=LAX01LA223 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/53354/pdf - Page: https://openairdocs.org/ntsb/LAX01LA223 ## Probable cause The pilot's failure to maintain directional control during the landing rollout. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Loss of control - on ground/water, landing - roll - directional control - not maintained, pilot in command (cause) - ground loop/swerve - not corrected, pilot in command - On ground/water collision with object, landing - roll - object - sign ## Analysis On the landing rollout the airplane veered to the right off the runway and collided with runway signs. The airplane was equipped with a free castering nose wheel mechanism without steering linkages. The pilot made an unsuccessful attempt to return the airplane to runway centerline with left rudder input. The airplane landing gear and brake system were inspected with no mechanical discrepancies noted. ## Factual narrative On June 26, 2001, at 0840 hours Pacific daylight time, a Rudolph Venture, N84V, veered off the runway on the landing rollout, and collided with runway signs at the Nevada County Air Park, Grass Valley, California. The experimental homebuilt airplane was operated by the pilot/owner under the provisions of 14 CFR Part 91, and sustained substantial damage. The airline transport pilot, the sole occupant, was not injured. Visual meteorological conditions prevailed for the local area flight, and no flight plan had been filed. The Safety Board Investigator-in-Charge interviewed the pilot. The pilot stated that the approach and touchdown were normal. On the landing rollout the airplane veered to the right. He input full left rudder, but was unable to bring the airplane back to runway centerline. The airplane continued off the right side of the runway where it contacted runway signs. The pilot reported that this particular type of airplane has a history of runway departures due to the design of the nose wheel landing gear. A Federal Aviation Administration (FAA) inspector interviewed the pilot. The pilot stated that he felt confident that he might have regained control of the airplane if the airplane had not contacted runway signs. The FAA inspector examined the airplane on-scene and stated that there was no damage to the nose gear doors and that the gear remained down and locked during landing. He indicated that the gear trunnion, down lock linkages, and strut were intact and displayed no visible damage. He further stated that according to the owner/pilot, the nose wheel is centered on an extension by internal cerntering cams inside the oleo strut. On the ground, the oleo piston and the nose wheel are free to castor right and left of center to physical external stops. The FAA inspector stated that he inspected this area and found it intact and functional. Another item of note was that there is no "steering" linkage which the pilot physically uses to steer the airplane. No further discrepancies were noted. According to the FAA inspector, the kit manufacturer is aware that the airplane has a history of nose gear steering problems, and they are attempting to resolve the problems. ## Aircraft - Registration: [N84V](https://openairdocs.org/deregistered/N84V-2003-02-26), registration cancelled 2003-02-26, S/N 74, built 2000 (OpenAirDocs) - Reported make and model: Rudolph Venture - Registry model: [Rudolph Gary RUDOLPH VENTURE](https://openairdocs.org/model/rudolph-gary-rudolph-venture) (registry code 05610RP) (OpenAirDocs) - Registry engine: [Continental IO-550 series](https://openairdocs.org/engine/continental-io-550-series) (registry code 17042, reciprocating) (OpenAirDocs) - Category: Airplane, amateur-built - Serial number: 74 - Airframe hours: 2 - Engines: Continental IO-550-G 280 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Registered owner: Forrest G. Rudolph - Airworthiness certificate: Special, Experimental (Special) - Departed: O17, Grass Valley, CA - Destination: O17, Grass Valley, CA - Airport: O17, Nevada County Air Park, runway 7, 4,350 × 75 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 64; injuries: none; airline transport; airplane ratings: multi-engine sea, single-engine land, multi-engine land, single-engine sea; instrument ratings: airplane; medical: class 2, valid medical--w/ waivers/lim; last flight review March 16, 2001; seat: left; flight hours: 28,000 total, 4 in this make and model, 22,000 as pilot in command, 104 in the last 90 days, 59 in the last 30 days, 3 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 0° at 0 knots - Visibility: 10 statute miles - Lowest ceiling: 4,100 ft broken - Temperature: 52 °F, dew point 48 °F - Altimeter: 30.04 inHg - Observed at: BLU, 17 nm away ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20010626015929A](https://openairdocs.org/incident/20010626015929A), Jun 26, 2001: Amtr VENTURE, Grass Valley, CA, Substantial damage. (-23) Upon landing the nose wheel failed to remain centered and caused aircraft to veer right off runway. Aircraft struck runway sign, spun sideways, then… From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.