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

Cessna 510 accident near Carlsbad, California, April 19, 2008

On April 19, 2008 at about 5:10 pm local time, a Cessna 510, registered N54PV, was substantially damaged in an accident during landing (landing roll) near Carlsbad, California (Mcclellan-Palomar Airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 4 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot's misjudgment of speed and distance, resulting in an overshoot of the runway. Contributing to the accident was the pilot's failure to follow the Autopilot Preflight Test Fail checklist and his distraction with a flickering primary flight display screen.

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

What the record shows

Date
April 19, 2008 · about 5:10 pm local time
Place
Carlsbad, California · Mcclellan-Palomar Airport · map
Type
Accident
Injuries
No one was hurt; 4 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Cessna 510 · all 510s on the register
Registration
N54PV · registry record · serial 510-0028
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

As the airplane approached the destination airport, the pilot selected vertical speed mode on the autopilot. While descending, the copilot's Primary Flight Display (PFD) began to flicker. About 5 minutes later, as the airplane transitioned through 28,000 feet mean sea level, the left PFD flashed a "PFT" alert indicating that the autopilot had disconnected. The pilot said he immediately felt heavy control forces on the control yoke that he had to exert to fly the airplane. Shortly thereafter, the pilot discovered that the electric pitch trim was not operational. While hand-flying the airplane the pilot entered instrument meteorological conditions as the airplane descended through a 2,400-foot-thick cloud layer. Thereafter, the pilot continued a visual approach to the 4,897-foot-long runway. The pilot noted that he was overwhelmed with the electrical failures and fatigued from maneuvering the airplane by hand for such a long duration (which he approximated was around 45 minutes). The airplane crossed the runway threshold about 15 knots faster than the correct landing speed and the airplane touched down past the midpoint of the runway. The pilot realized that despite his braking attempts the airplane was going to continue off the runway surface over a small downsloping cliff at the end. He determined that he would not be able to abort the landing due to the airplane's diminished ground speed and elected to perform a 180-degree turn. The airplane ground looped, coming to rest in a dirt area south of the runway; the main landing gear collapsed and the flaps folded under the wings. According to the pilot, he never attempted to reset the autopilot system. The autopilot was designed for an automatic disengagement when there is a system failure, invalid sensor data, or yaw damper failure. On the manufacturer's current Pilots' Abbreviated Checklist, Emergency Procedures section, it states that if the autopilot preflight test fail warning (red "PFT" warning on the PFD) illuminates, the pilot should reset the associated circuit breaker to clear the fault. A post-accident examination of the airplane's systems revealed no mechanical malfunctions or failures, with the exception of a flickering PFD screen.

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. Landing area overshoot during landing
  2. Runway excursion during landing (landing roll) defining event

The NTSB's findings

  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Airspeed › Incorrect use/operation
  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Descent/approach/glide path › Incorrect use/operation
  • factor Personnel issues › Psychological › Attention/monitoring › Monitoring equip/instruments › Pilot
  • factor Personnel issues › Task performance › Use of equip/info › Use of checklist › Pilot
  • Aircraft › Aircraft systems › Navigation system › (general) › Malfunction

Pilot

  • Certificate: commercial pilot
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 1,398 hours in all; 104 in this make and model; 78 in the last 90 days; 38 in the last 30 days; 1,184 as pilot in command
  • Last flight review: March 22, 2008
  • Medical certificate: Class 2 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 120.4 hours
  • Last inspection: continuous airworthiness programme, April 14, 2008
  • Maximum gross weight: 8,645 lb
  • Seats: 8
  • Landing gear: retractable
  • Engine 1: Pratt & Whitney PW615F-A (turbofan); 0 hours total
  • Engine 2: Pratt & Whitney PW615F-A (turbofan); 0 hours total

The flight

  • Departed from: LHM Lincoln CA at 3:54 pm
  • Destination: CRQ Carlsbad CA
  • Flight plan: IFR
  • Runway 24, 4,897 ft by 150 ft

Weather at the time

  • Light: daylight
  • Wind: from 130° at 8 knots
  • Visibility: 8 statute miles
  • Sky: overcast at 2,700 ft; clear
  • Temperature: 57°F (14°C), dew point 46°F (8°C)
  • Altimeter: 29.95 inHg
  • Observation at 5:12 pm from CRQ

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.