The U.S. aircraft register, updated daily
Accidents · NTSB LAX08FA058 · Final report

Cessna 340A accident near Cabazon, California, February 2, 2008

On February 2, 2008 at about 9:40 pm local time, a Cessna 340A, registered N354TJ, was destroyed in an accident during enroute near Cabazon, California. It was a personal flight under general aviation rules (Part 91). 4 people were killed. The weather was instrument conditions (cloud, fog or low visibility).

The NTSB's probable cause their words, unchanged

The pilot's continued visual flight into instrument meteorological conditions and failure to maintain terrain clearance while en route. Contributing to the accident were clouds and mountainous terrain.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
February 2, 2008 · about 9:40 pm local time
Place
Cabazon, California · map
Type
Accident
Injuries
4 people were killed.
Weather
instrument conditions (cloud, fog or low visibility)
Aircraft
Cessna 340A · all 340As on the register
Registration
N354TJ · no longer on the register · serial 340A0042
Damage
Destroyed
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The airplane departed under daytime visual meteorological conditions on a cross-country flight from an airport on the east side of a mountain range to a destination on the west side of the mountains. The airplane, which had been receiving flight following, then collided with upsloping mountainous terrain in a mountain pass while in controlled flight after encountering instrument meteorological conditions. The controller terminated radar services due to anticipation of losing radar coverage within the mountainous pass area, and notified the pilot to contact the next sector once through the pass while staying northwest of an interstate highway due to opposing traffic on the south side of the highway. The pilot later contacted the controller asking if he still needed to remain on a northwesterly heading. The controller replied that he never assigned a northwesterly heading. No further radio communications were received from the accident airplane. Radar data revealed that while proceeding on a northeasterly course, the airplane climbed to an altitude of 6,400 feet mean sea level (msl). A few minutes later, the radar data showed the airplane turning to an easterly heading and initiating a climb to an altitude of 6,900 feet msl. The airplane then started descending in a right turn from 6,900 feet to 5,800 feet msl prior to it being lost from radar contact about 0.65 miles southeast of the accident site. A weather observation station located at the departure airport reported a scattered cloud layer at 10,000 feet above ground level (agl). A weather observation system located about 29 miles southwest of the accident site reported a broken cloud layer at 4,000 feet agl. A pilot, who was flying west bound at 8,500 feet through the same pass around the time of the accident, reported overcast cloud coverage in the area of the accident site that extended west of the mountains. The pilot stated that the ceiling was around 4,000 feet msl and the tops of the clouds were 7,000 feet msl or higher throughout the area. Postaccident examination of the airframe and both engines revealed no anomalies that would have precluded normal operation.

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

  1. VFR encounter with IMC during enroute defining event
  2. Controlled flight into terrain or object (CFIT) during enroute

The NTSB's findings

  • cause Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
  • cause Environmental issues › Conditions/weather/phenomena › Ceiling/visibility/precip › Below VFR minima › Decision related to condition
  • cause Environmental issues › Physical environment › Terrain › Mountainous/hilly terrain › Response/compensation
  • factor Environmental issues › Conditions/weather/phenomena › Ceiling/visibility/precip › Clouds › Not specified
  • factor Environmental issues › Physical environment › Terrain › Mountainous/hilly terrain › Not specified

Pilot

  • Certificate: private
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 5,972 hours in all
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: unk
  • Injury: fatal

The aircraft

  • Maximum gross weight: 5,990 lb
  • Seats: 6
  • Landing gear: fixed
  • Engine 1: Teledyne Continental TSIO-520 SER (piston); 0 hours total
  • Engine 2: Teledyne Continental TSIO-520 SER (piston); 0 hours total

The flight

  • Departed from: UDD Palm Springs CA at 9:30 pm
  • Destination: CNO Chino CA
  • Flight plan: none

Weather at the time

  • Light: daylight
  • Wind: from 320° at 8 knots
  • Visibility: 10 statute miles
  • Sky: overcast at 4,000 ft
  • Temperature: 61°F (16°C), dew point 36°F (2°C)
  • Altimeter: 29.98 inHg
  • Observation at 9:53 pm

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers3

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.