Piper PA-30 accident near Big Bear City, California, January 30, 2011
On January 30, 2011 at about 3:20 pm local time, a Piper PA-30, registered N64RJ, was substantially damaged in an accident during enroute (climb to cruise) near Big Bear City, California (Big Bear City Airport). It was a personal flight under general aviation rules (Part 91). 1 person was seriously injured. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot’s failure to maintain the minimum single-engine control speed while on final approach for landing. Contributing to the accident was the pilot's decision to fly with a known deficiency in one engine and a loss of power in that engine for reasons that could not be determined because postaccident examination did not reveal any mechanical failures or malfunctions that would have precluded normal operation.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- January 30, 2011 · about 3:20 pm local time
- Place
- Big Bear City, California · Big Bear City Airport · map
- Type
- Accident
- Injuries
- 1 person was seriously injured.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA-30 · all PA-30s on the register
- Registration
- N64RJ · registry record · serial 30-1931
- 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 after takeoff the right engine lost power as he turned onto the left crosswind leg of the traffic pattern. He continued to turn onto the downwind leg, making sure to keep the airspeed above the single-engine control speed of 90 mph. The pilot’s last recollection was turning to final approach and seeing the runway. A witness in the area reported hearing the sound of an engine popping and backfiring before the airplane started the takeoff roll. The airplane subsequently impacted the roof of a private residence located about 900 feet from the runway threshold. The airplane came to rest inverted in the front yard. The airplane had recently undergone maintenance, which included the overhaul of both engines. The pilot had flown the airplane into the airport the day before and, after landing, called the maintenance facility to report that the right engine was running rough. A mechanic was not available to help him and he was told that he should not fly the airplane. A postaccident examination of both the right and left engines revealed no evidence of mechanical failures or malfunctions that would have precluded normal operation. A global positioning system (GPS) unit was recovered and downloaded. The information indicated that the airplane continued to climb on the downwind leg to pattern altitude and then descended and reduced power to final approach. The last heading was aligned with the runway with a ground speed of 76 miles per hour and 1,400 feet east of the landing threshold. The pilot likely allowed the airspeed to decrease below the single-engine control speed and did not maintain sufficient altitude to clear the house while on final approach.
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
- Aircraft maintenance event during prior to flight
- Loss of engine power (partial) during enroute (climb to cruise) defining event
- Loss of control in flight during emergency descent
- Collision with terrain or object (not controlled flight into terrain) during emergency descent
The NTSB's findings
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Airspeed › Not attained/maintained
- factor Not determined › Not determined › (general) › (general) › Unknown/Not determined
- factor Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
- factor Aircraft › Aircraft power plant › Power plant › (general) › Not specified
Pilot
- Certificate: private
- Ratings: multi-engine land; single-engine land
- Flight time: 593 hours in all; 10 in this make and model; 535 as pilot in command
- Last flight review: August 8, 2010
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: serious injuries
The aircraft
- Airframe total time: 2,167 hours
- Last inspection: annual inspection, January 8, 2011; 11 hours since
- Maximum gross weight: 3,725 lb
- Seats: 4
- Landing gear: fixed
- Engine 1: Lycoming IO-320 SERIES (piston); 0 hours total
- Engine 2: Lycoming IO-320 SERIES (piston); 0 hours total
- Operator: Tower General Construction Inc
The flight
- Departed from: L35 Big Bear CA at 3:12 pm
- Destination: Pacoima CA
- Flight plan: not recorded
- Runway 26, 5,850 ft by 75 ft
Weather at the time
- Light: daylight
- Wind: from 240° at 5 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 30°F (-1°C), dew point 3°F (-16°C)
- Altimeter: 30.04 inHg
- Observation at 2:51 pm from L35, 1 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.
