The U.S. aircraft register, updated daily · Carbon Free Flight by 2050
Accidents · NTSB LAX98LA204 · Final report

Amateur-built LANCAIR 320 accident near Palm Springs, California, June 15, 1998

On June 15, 1998 at about 8:00 pm local time, a amateur-built LANCAIR 320, registered N96GF, was substantially damaged in an accident near Palm Springs, California (Palm Springs Regional 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).

Preview. This page is not yet listed for search engines.

The NTSB's probable cause their words, unchanged

A failure of the electrical system for undetermined reasons. The pilot's decision to continue flight with a suspected electrical system anomaly is a factor in the accident.

Source: NTSB aviation accident database, copy made October 4, 2026. Docket and reports at the NTSB.

What the record shows

Date
June 15, 1998 · about 8:00 pm local time
Place
Palm Springs, California · Palm Springs Regional · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Amateur-built LANCAIR 320 LANCAIR 32
Registration
N96GF · registry record · serial 633-320-378
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

After refueling, the aircraft had to be jump-started by a ground power source. After takeoff, the main circuit breaker tripped and the pilot manually reset it with a positive charge shown on the ammeter. About 30 minutes into the flight the pilot noted that the radio and fuel transfer pump were weak, and he reduced all nonessential electrical loads. A short time later the pilot noted that the header tank was 1/3 full, and attempted to make a precautionary landing. The pilot stated that he attempted to manually extend the landing gear, however, only the right main extended. After touchdown the airplane slid off the runway. The aircraft was moved prior to examination and the source of the electrical malfunction could not be determined.

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

  1. AIRFRAME/COMPONENT/SYSTEM FAILURE/MALFUNCTION during cruise
  2. WHEELS UP LANDING during landing - flare/touchdown

Pilot

  • Ratings: multi-engine land, multi-engine sea, single-engine land, none, APLN, none
  • Flight time: 3,969 hours in all; 52 in this make and model; 7 in the last 90 days; 4 in the last 30 days; 3,969 as pilot in command
  • Medical certificate: none

The aircraft

  • Airframe total time: 46 hours
  • Last inspection: continuous airworthiness programme, August 15, 1996; 46 hours since
  • Maximum gross weight: 1,900 lb
  • Seats: 2
  • Landing gear: retractable
  • Engine: Lycoming O-320 (piston); 0 hours total
  • Operating certificate: in the vicinity

The flight

  • Departed from: PRC Prescott AZ at 6:05 pm
  • Destination: OCN Oceanside CA
  • Flight plan: VFR
  • Runway 13L, 4,952 ft by 75 ft

Weather at the time

  • Light: daylight
  • Wind: from 340° at 18 knots, gusting 23
  • Visibility: 10 statute miles
  • Sky: scattered at 10,000 ft
  • Temperature: 102°C, dew point 52°C
  • Altimeter: 29 inHg
  • Observation at 7:53 pm from PSP

Injuries

FatalSeriousMinorNone
Crew1

About this page

Everything above comes from the NTSB's public accident database: the narrative, probable cause and findings are the NTSB's own words, and the coded tables behind its report (pilot, aircraft, flight, weather, injuries, sequence of events) are written out in plain English. Pilots' ages, home towns and medical details are left out on purpose. The docket at the NTSB holds the report as a PDF and the investigation's photographs and documents. This site never names pilots, passengers or anyone else involved. A preliminary report describes what is known soon after the event and can change; the final report, with the probable cause, usually follows one to two years later and this page is refreshed when it does. Case number LAX98LA204.