Skip to content

Atlas / NTSB / LAX01LA265

NTSB CAROL · Event

Event LAX01LA265

2001-07-31 Hesperia, California, United States Airport · L26 Serious 1 aircraft Status: Completed

Registry · N5346W

FAA Aircraft Registry record.

Make / Model

TEAM AIRCRAFT HI-MAX

Year of manufacture

1997 · 4 years old at event

Engine

ROTAX 503 SERIES (52 hp)

Seats / Engines

1 seats · 1 engine

Last airworthiness date

20080115

ADS-B equipped

Yes — Mode-S A6C288

Registrant of record

MOORE DAVID R

Source: FAA Aircraft Registry (releasable master file).

Aircraft involved

Probable cause & findings

the loss of engine power due to fuel exhaustion while maneuvering in an attempt to locate the runway. Contributing factors were the inadequate runway maintenance that resulted in inoperative runway edge lights, and the night light conditions.

Factual narrative

On July 28, 2001, at 0038 Pacific daylight time, a Piper PA-28-150 single engine airplane, N5346W, impacted a wire and terrain following a loss of engine power while maneuvering near the Hesperia Airport, Hesperia, California. The airplane was registered to and operated by the pilot under the provisions of 14 CFR Part 91 as a personal flight. The commercial pilot, who was the sole occupant, received serious injuries. The airplane was substantially damaged. Night visual meteorological conditions prevailed, and a visual flight rules flight plan was filed. The flight originated from Redding, California, and was originally destined for Upland, California. Upon arriving at Upland, the pilot was unable to land due to poor visibility, so he diverted to Hesperia. According to the San Bernardino Sheriff Department Deputy, who responded to the accident site, the pilot obtained a weather briefing from the flight service station at 1908, and filed a flight plan, advising them he had 5 hours 20 minutes of fuel on board, and he planned on a total of 4 hours 45 minutes for his route of flight. The accident flight departed Redding at 1938, after topping off the fuel tanks. At 2330, the pilot made several attempts to land at Cable Airport (Upland), but was unsuccessful due to "poor visibility." The pilot elected to fly to Hesperia to land. The sheriff's deputy interviewed the pilot, and was told that he circled the Cable Airport two or three times but was unable to locate the runway due to poor visibility. He then called the Riverside Flight Service Station and informed them he was diverting to Hesperia. Once he arrived at the Hesperia airport, the pilot illuminated the pilot controlled runway lighting and they stayed illuminated for approximately 5 minutes. The pilot then utilized his global positioning system to navigate around the airport in an attempt to locate the runway. He told the deputy he attempted to reilluminate the lights but was unsuccessful. The pilot was aware he was running low on fuel and descended closer to the ground in an attempt to find the runway. The engine lost power and the airplane then impacted a wire and terrain 0.6 miles west of the airport. It should be noted that Hesperia is approximately 20 nautical miles northeast of Upland; however, there were two airports within 5 nautical miles from Upland, and five more that are within 15 nautical miles of Upland. Four of those airports had continuous runway lighting. According to the flight service station, the reported weather at the Ontario International Airport (5 miles southeast of Upland) at 2345, was visibility 6 statute miles in mist, with overcast clouds at 1,300 feet agl. The pilot told the sheriff's deputy he was unable to locate the Ontario International Airport when he was near Upland. On August 31, 2001, the sheriff's deputy flew approximately 0.6 miles west of the Hesperia airport and attempted to activate the pilot controlled lighting. After several attempts from various locations, he was unable to illuminate the lights. The sheriff's deputy noticed the airport beacon was functioning properly, but was unable to detect any lights on or near the runway. The airplane impacted wires and terrain following a loss of engine power while maneuvering near an airport. The commercial pilot planned a 4 hour 45 minute flight with 5 hours 20 minutes of fuel on board. When the pilot arrived at his destination airport, he was unable to locate the airport because of poor visibility. The pilot then diverted to another airport, and activated its pilot controlled runway lighting; however, the runway lights only remained illuminated for 5 minutes, then went out. The pilot attempted to reactivate the runway lights, but was unsuccessful. The pilot became concerned about the fuel situation and descended toward the ground in an attempt to locate the runway. The engine lost power and the airplane impacted wires approximately 0.6 miles west of the airport. The sheriff deputy, who responded to the accident site and interviewed the pilot, indicated he flew within 0.6 miles of the diversion airport approximately 1 month after the accident, and attempted to illuminate the pilot controlled runway lights. According to the deputy, he was unsuccessful in activating the runway lights after several attempts from various locations around the airport. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12

Verbatim from NTSB's published report. Source file NTSB_2001_LAX01LA265.txt. Findings + structured fields enriched from FAA avall.mdb. Full investigation docket on data.ntsb.gov ↗.

Related research

What the literature says.

Academic papers and agency reports matching this event's aircraft type or causal vocabulary (fuel exhaustion, maintenance). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.

Browse the full corpus — academia portal ↗