LAX98LA204 · Fife LANCAIR 320 LANCAIR 32
Fife LANCAIR 320 LANCAIR 32 · Accident: airframe, component or system failure en route
From Prescott Regional Airport - Ernest A. Love Field (PRC) to Oceanside Municipal Airport (OCN)
Event
- NTSB case
- LAX98LA204
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- 0
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Fife LANCAIR 320 LANCAIR 32
- Aircraft type
- Fife LANCAIR 320
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N96GF
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Prescott Regional Airport - Ernest A. Love Field (PRC), Prescott, AZTo Oceanside Municipal Airport (OCN), Oceanside, CA
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- En route · cruise
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Airframe, component or system failure
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Electrical system › Failure
- Reason for occurrence undetermined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
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.
Probable cause
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX98LA204
- Event ID
- 20001211X10360
- Case number
- LAX98LA204
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 09186465f544547d607dfbf7c400fa968d08b78c93d0d56bf8a07183184a4e8c; retrieved 2026-09-22T17:40:28.840Z.