# Incident 20140130003239I: Quad City Ultralight Acft Corp CHALLENGER II, Lodi, CA, January 30, 2014

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: January 30, 2014, 11:00 local time
- Place: Lodi, CA
- Damage: Substantial damage
- Phase of flight: Other, Specify
- Operating rules: General operating rules (Part 91)
- Location: 38.1216° N, 121.2908° W: Placed by OpenAirDocs: center of Lodi, CA, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=38.1216&lon=-121.2908&mi=10
- Aircraft: N7999C, a cancelled registration (https://openairdocs.org/deregistered/N7999C-2020-02-28) (OpenAirDocs)
- Registry model: Quad City Ultralight Acft CHALLENGER II (registry code 059010Q, https://openairdocs.org/model/quad-city-ultralight-acft-challenger-ii) (OpenAirDocs)
- Registry engine: Rotax 503 DCDI (registry code 55566, https://openairdocs.org/engine/rotax-503-dcdi) (OpenAirDocs)
- Reported make and model: QUAD CITY ULTRALIGHT ACFT CORP CHALLENGER II
- Reported engine: ROTAX 503 DCDI
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Student
- Pilot flight hours: 170 total, 74 in this make and model, 4 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20140130003239I

## Narrative

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

STUDENT PILOT PREFLIGHTED HIS AIRCRAFT AND FUELED THE AIRCRAFT IN HIS HANGAR.

HE PULLED THE AIRCRAFT OUT TO THE FRONT OF HIS HANGER FACING SOUTH TOWARDS THE TAXIWAY AND SET THE BRAKES.  HE WENT THROUGH THE AIRCRAFT CHECK LIST AND ATTEMPTED TO START THE AIRCRAFT.  HE MADE SEVERAL ATTEMPTS HOWEVER THE BATTERY HAD INSUFFICENT POWER TO START THE AIRCRAFT ENGING. THE STUDENT PILOT THEN DECIDED TO HAND PROP TO START THE ENGINE.

HE SET THE BRAKES AND HE BELIEVES HE MOVED THE THROTTLE TO THE RETARDED POSITION BUT COULD NOT RECALL THAT THE HE MOVED THE THROTTLE TO THE CLOSED POSITION.

HE THEN WENT TO THE REAR OF THE AIRCRAFT TO HAND PROP THE ENGINE.

AFTER ONE PULL OF THE PROP THE ENGINE STARTED AND THE AIRCRAFT BEGAN TO BOUNCE FORWARD. THE PILOT ATTEMPTED TO RUN AROUND TO THE COCKPIT, HOWEVER THE AIRCRAFT CONTINUED ON A COURSE TOWARDS THE RAMP AND CONTINUED TO BOUNCE.

THE STUDENT PILOT RAN AFTER THE AIRCRAFT AND WAS UNABLE TO CONTROL THE AIRCRAFT. THE AIRCRAFT  LAUNCHED INTO THE AIR IN A STEEP CLIMB JUST NORTH OF THE BEGINNING OF THE RUNWAY AND HEADED TOWARDS THE HANGARS AND AIRCRAFT PARKED ON THE OTHER SIDE OR THE RUNWAY.  THE AIRCRAFT STALLED IN A STEEP CLIMB AND LOOPED BACK DOWN TOWARDS THE OTHER SIDE OF THE RUNWAY RAMP AREA IMPACTING THE RAMP APPROXIMATELY 10 FEET FROM THE FRONT OF A DC-3 PARKED ON THE RAMP. THE IMPACT CAUSED SIGNIFICANT DAMAGE TO THE AIRCRAFT.  NO COLATERAL DAMAGE TO ANY OTHER AIRCRAFT OR STRUCTURES OCCURRED.

THE STUDENT PILOT DID NOT INTEND TO FLY.  HE WAS ONLY GOING TO TAXI THE AIRCRAFT TO THE LOCATION WHERE HE WOULD MEET HIS CERTIFIED FLIGHT INSTRUCTOR (CFI) AND SHUT DOWN THE ENGINE FOR FURTHER TRAINING PRIOR TO FLYING THE AIRCRAFT TO CONTINUE HIS TRAINING.

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.
