# Accident 20000820039629A: Pulsar SUPER PULSAR 100, Victorville, CA, August 20, 2000

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: August 20, 2000, 14:23 local time
- Place: Victorville, CA
- Damage: Substantial damage
- Phase of flight: Missed Approach IFR
- Operating rules: General operating rules (Part 91)
- Location: 34.4905° N, 117.3607° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=34.4905&lon=-117.3607&mi=10
- Aircraft: N601SP, a cancelled registration (https://openairdocs.org/deregistered/N601SP-2012-12-13) (OpenAirDocs)
- Registry model: Pulsar SUPER PULSAR 100 (registry code 05610KJ, https://openairdocs.org/model/pulsar-super-pulsar-100) (OpenAirDocs)
- Registry engine: Amateur-built UNKNOWN ENG (registry code 99999, https://openairdocs.org/engine/amateur-built-unknown-eng) (OpenAirDocs)
- Fatal injuries: 0
- Pilot flight hours: 263 total, 2 in this make and model, 5 in the last 90 days
- NTSB investigation: [NTSB LAX00LA308](https://openairdocs.org/ntsb/LAX00LA308) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20000820039629A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

(.4)ON AUGUST 20, 2000, ABOUT 1423 PDT, AN EXPERIMENTAL PULSAR 100, N601SP, WAS SUBSTANTIALLY DAMAGED DURING AN OFF-AIRPORT LANDING AT VICTORVILLE, CALIFORNIA. THE PRIVATE PILOT/BUILDER RECEIVED MINOR INJURIES.  THE AIRPLANE WAS OPERATED BY THE PILOT, D.B.A. PULSAR AIRCRAFT CORP., EL MONTE, CALIFORNIA, UNDER 14 CFR PART 91.  VISUAL METEOROLOGICAL CONDITIONS PREVAILED FOR THE PERSONAL FLIGHT AND NO FLIGHT PLAN WAS FILED.  THE RECENTLY BUILT AIRPLANE HAD BEEN TRUCKED FROM EL MONTE TO THE SOUTHERN CALIFORNIA LOGISTICS AIRPORT AT VICTORVILLE FOR THE PURPOSE OF PERFORMING THE FIRST TEST FLIGHTS.  A PROFESSIONAL PILOT HAD FLOWN THE FIRST FLIGHT SUCCESSFULLY.  THE SECOND FLIGHT WAS FLOWN BY THE OWNER/BUILDER.  BOTH FLIGHTS HAD OPERATED FROM A FUEL LOAD OF 10 GALLONS, 5 GALLONS EACH SIDE.  ON APPROACH TO RUNWAY 21, THE ACCIDENT PILOT EXPERIENCED A LOSS OF ENGINE POWER WHILE ON THE LEFT FUEL TANK.  HE SWITCHED TO THE RIGHT TANK BUT WAS UNABLE TO GET A RESTART.  THE PILOT FORCED TO PERFORM AN OFF-ARIPORT LANDING.  DURING THE LANDING ROLL, AFTER ABOUT 300 FEET, THE LANDING GEAR COLLIDED WITH A SMALL RAVINE AND COLLAPSED.  THE PILOT STATED THAT THE FUEL VAPOR RETURN, WHICH WAS PLUMBED INTO TH E RIGHT FUEL RANK, WAS GREATER THAN ADVERTISED. HE HAD UNDERSTOOD THE RATE TO BE 20/30 PERCENT OF THE FUEL CONSUMPTION RATE.                         (-23) EXPERIMENTAL AMATUER BUILT FLOWN BY KIT MANUFACTURER VALIDATING NEW ENGINE INSTALLATION. AIRCRAFT DEPARTED FOR LOCAL MAINTENANCE OPERATIONAL CHECK. FUEL PUMP BYPASS DIVERTED TO RIGHT HAND FUEL TANK. AIRCRAFT SELECTED TO LEFT HAND TANK. LEFT TANK EMPTY OF FUEL AFTER FIFTEEN MINUTES. PILOT RETURNED TO AIRPORT AND LANDED SHORT.

## The NTSB's investigation of this event (1)

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.

- [NTSB LAX00LA308](https://openairdocs.org/ntsb/LAX00LA308), Aug 20, 2000: Pulsar 100 (N601SP), Victorville, CA, substantial damage. Probable cause: the pilot's failure to provide enough fuel for the intended flight. Contributing to the accident was an improper fuel vapor return system.

## Other reports on N601SP (1)

Matched to the same aircraft by N-number and date.

- [Incident 20000719040479I](https://openairdocs.org/incident/20000719040479I), Jul 19, 2000: Amtr SUPPULSAR100 (N601SP), El Monte, CA, Minor damage. (-23) Aircraft had 97 hours on airframe, owner removed fixed pitch propeller and installed a non-certificated aerotek variable pitch propeller, model #RB2000…

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
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.
