FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR11CA026 · Cessna 340A

23 Oct 2010 · Camp Verde, AZ, United States

Cessna 340A · Accident: landing area overshoot

From Prescott Regional Airport - Ernest A. Love Field (PRC) to Montezuma Airport (19AZ)

Report a problem

Event

NTSB case
WPR11CA026
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 340A

Aircraft type
Cessna 340
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
N630PL
Operator
Unknown
Onboard fatalities
Unknown
Route
From Prescott Regional Airport - Ernest A. Love Field (PRC), Prescott, AZTo Montezuma Airport (19AZ), Camp Verde, AZ
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 · flare/touchdown
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
Landing area overshoot
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
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

According to the pilot, he noted that the wind was calm as he made his traffic-pattern approach to the runway. He turned onto base leg early, which resulted in the airplane being higher than normal on the final approach. He reduced the engine power and lowered the nose in an attempt to land with enough runway surface remaining. The pilot reported that although the airplane floated much further than he expected during landing, he believed that he could still brake to a stop safely. The airplane subsequently overran the runway's end and came to rest on an embankment with collapsed landing gear and a bent wing. The pilot reported that he experienced no mechanical malfunctions with his airplane.

Probable cause

The pilot's misjudged approach and failure to attain the correct touchdown point, which resulted in a runway overrun.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR11CA026
Event ID
20101024X70145
Case number
WPR11CA026
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. 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: 49bf241bf5c9c9ad23f913a10c3ebbace699de7181cbc5f198ec31035683859c; retrieved 2026-09-15T15:30:51.842Z.