Eccker HURRICANE HAULER accident near Jamul, California, September 28, 2010
On September 28, 2010 at about 6:20 pm local time, a Eccker HURRICANE HAULER, registered N7519W, was substantially damaged in an accident during enroute (cruise) near Jamul, California. It was a personal flight under general aviation rules (Part 91). 1 person had minor injuries. The weather was instrument conditions (cloud, fog or low visibility).
The NTSB's probable cause their words, unchanged
The loss of engine power during cruise flight due to engine seizure as a result of lack of lubrication from excessive carbon buildup on the piston rings.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- September 28, 2010 · about 6:20 pm local time
- Place
- Jamul, California · map
- Type
- Accident
- Injuries
- 1 person had minor injuries.
- Weather
- instrument conditions (cloud, fog or low visibility)
- Aircraft
- Eccker HURRICANE HAULER
- Registration
- N7519W · no longer on the register · serial HAUL-10
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
While in cruise flight, the airplane's engine began to lose power and eventually stopped running. The pilot performed a forced landing in a field. During the landing roll, the airplane impacted a fence, substantially damaging the airframe and wings. According to the pilot, the airplane's two-cycle engine is designed to receive lubrication to the piston via engine oil premixed into the automobile gasoline. A postaccident examination of the engine revealed excessive carbon buildup on the piston rings, which more than likely reduced the lubrication between the piston rings and the cylinder wall and led to overheating and a subsequent seizure of the engine.
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
- Loss of engine power (total) during enroute (cruise) defining event
- Collision with terrain or object (not controlled flight into terrain) during landing (landing roll)
The NTSB's findings
- cause Aircraft › Aircraft power plant › Engine (reciprocating) › Recip eng cyl section › Not specified
- Environmental issues › Physical environment › Object/animal/substance › Fence/fence post › Contributed to outcome
Pilot
- Certificate: sport pilot
- Ratings: single-engine land
- Flight time: 160 hours in all; 120 in this make and model; 32 in the last 90 days; 12 in the last 30 days; 140 as pilot in command
- Last flight review: September 28, 2009
- Medical certificate: Sport Pilot
- Seat: ctr
- Injury: minor injuries
The aircraft
- Last inspection: condition inspection
- Maximum gross weight: 670 lb
- Seats: 1
- Landing gear: fixed
- Engine: Rotax 503 DCDI (piston); 0 hours total
The flight
- Departed from: OCL3 San Diego CA at 6:00 pm
- Destination: OCL3 San Diego CA
- Flight plan: none
Weather at the time
- Light: daylight
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 84°F (29°C), dew point 0°F (-18°C)
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.