Plane crash map Locate crash sites, wreckage and more

N1606B accident description

California map... California list
Crash location 34.431945°N, 116.921111°W
Reported location is a long distance from the NTSB's reported nearest city. This often means that the location has a typo, or is incorrect.
Nearest city Apple Valley, CA
34.500831°N, 117.185876°W
15.8 miles away
Tail number N1606B
Accident date 18 May 2001
Aircraft type Luscombe 11A
Additional details: None

NTSB Factual Report

On May 18, 2001, at 1400 hours Pacific daylight time (PDT), a Luscombe 11A, N1606B, sustained substantial damage when it was force landed near Apple Valley, California. The forced landing was precipitated by a loss of engine power during cruise. The airplane was operated by the airline transport pilot/owner under the provisions of 14 CFR Part 91, and sustained substantial damage. The pilot and his pilot-rated passenger sustained minor injuries. The personal cross-country flight departed Glendale, Arizona, at 1130 PDT. Visual meteorological conditions prevailed, and no flight plan had been filed. The flight was scheduled to terminate at the Columbia Airport, Columbia, California.

According to the pilot's written statement to the Safety Board, he stated that there were no discrepancies noted with the preflight inspection, takeoff, climb, and cruise portions of the flight. He indicated that he checked fuel and time over Twenty-Nine Palms, California, and asked the Los Angeles Air Route Traffic Control Center (ARTCC) air traffic controller how far he was from Apple Valley. ARTCC informed him he was 18 miles away.

The pilot reported that it was his intention to land at Apple Valley for fuel and lunch. He started his descent from 8,500 msl to 6,500 feet msl, where he encountered light to moderate turbulence. He noted that the fuel gage was fluctuating, which indicated to him that the fuel was sloshing around in the tank. The pilot reported that the engine quit. He suspected that the fuel line had been uncovered and air had gotten into the fuel line causing vapor lock. He "pumped" the throttle "thinking I might get the fuel moving back into the carburetor to get the engine started again." He stated that he picked a place to land after his unsuccessful attempt to restart the engine. He chose a small dirt road; he indicated that his only problem was a paved road with poles that was parallel to the dirt road. He setup for the forced landing. At 20 mph he pushed the airplane's nose over to land in a level attitude with some forward movement. The pilot stated that he did this to lessen the downward direction of the airplane and to slow it down enough to be able to stop before hitting the poles.

According to a Federal Aviation Administration inspector, controllers from ARTCC were providing the pilot with flight following. The pilot informed the ARTCC controller that he was out of fuel and would be making a forced landing.

A responding San Bernardino Sheriff's Department deputy stated that he observed no fuel in either of the airplane's fuel tanks or on the ground beneath the airplane. He also stated that the airplane's wings showed indications of brushing against vegetation, and were damaged. The propeller was bent at the tips, and the landing gear had been sheared off.

NTSB Probable Cause

The pilot's fuel mismanagement, which led to fuel exhaustion, a loss of engine power, and subsequent landing on unsuitable terrain.

© 2009-2020 Lee C. Baker / Crosswind Software, LLC. For informational purposes only.