Piper PA-28-236 accident near Moreno Valley, California, June 26, 2010
On June 26, 2010 at about 2:30 pm local time, a Piper PA-28-236, registered N8118A, was substantially damaged in an accident during enroute (cruise) near Moreno Valley, California. 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).
The NTSB's probable cause their words, unchanged
A total loss of engine power due to fuel exhaustion.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- June 26, 2010 · about 2:30 pm local time
- Place
- Moreno Valley, California · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA-28-236 · all PA-28-236s on the register
- Registration
- N8118A · registry record · serial 28-8011028
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot reported that as he entered the vicinity of his destination airport, he decided the reduced visibility prohibited him from safely continuing. He opted to divert to an alternate airport to maintain visual conditions. While en route to the alternate airport, the fuel supply was exhausted and the engine experienced a loss of power. The pilot initiated a forced landing into a field. The airplane collided with terrain during the landing, damaging the firewall. The pilot reported no pre impact mechanical failures or malfunctions with the airframe or engine. He further stated that the accident may have been prevented if he had a larger fuel reserve.
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
- Fuel exhaustion during enroute (cruise) defining event
- Loss of engine power (total) during enroute (cruise)
The NTSB's findings
- Environmental issues › Conditions/weather/phenomena › Ceiling/visibility/precip › Low ceiling › Effect on operation
- cause Aircraft › Fluids/misc hardware › Fluids › Fuel › Fluid level
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 1,692 hours in all; 1,621 in this make and model
- Last flight review: May 5, 2010
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 1,473 hours
- Last inspection: 100-hour inspection, January 6, 2010; 10 hours since
- Maximum gross weight: 3,000 lb
- Seats: 4
- Landing gear: fixed
- Engine: Lycoming O-540 SERIES (piston); 0 hours total
The flight
- Departed from: KA20 Bullhead City AZ at 2:00 pm
- Destination: KAJO Corona CA
- Flight plan: none
Weather at the time
- Light: daylight
- Visibility: 7 statute miles
- Sky: broken clouds at 1,300 ft
- Temperature: 61°F (16°C), dew point 57°F (14°C)
- Altimeter: 29.95 inHg
- Observation at 1:56 pm from KAJO, 21 miles away
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.