FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX08FA117 · Cessna 510

19 Apr 2008 · Carlsbad, CA, United States

Cessna 510 · Accident: runway excursion during landing

From Lincoln Regional Karl Harder Field (LHM) to McClellan-Palomar Airport (CRQ)

Report a problem

Event

NTSB case
LAX08FA117
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Cessna 510

Aircraft type
Cessna 510
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N54PV
Onboard fatalities
Unknown
Route
From Lincoln Regional Karl Harder Field (LHM), Lincoln, CATo McClellan-Palomar Airport (CRQ), Carlsbad, CA
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Landing · landing roll
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Runway excursion
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft oper/perf/capability

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

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.

Probable cause

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.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX08FA117
Event ID
20080425X00554
Case number
LAX08FA117
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 9141a9465647185a03017bc282a9c240a4d2dc23dc84c0b75025fc780affa3a7; retrieved 2026-09-15T09:34:50.453Z.