WPR14CA299 · Diamond Aircraft IND Inc DA 20 C1
Diamond Aircraft IND Inc DA 20 C1 · Accident: landing area overshoot
From Grants Pass Airport (3S8) to Palo Alto Airport (PAO)
Event
- NTSB case
- WPR14CA299
- 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
Diamond Aircraft IND Inc DA 20 C1
- Aircraft type
- Diamond DA-20
- 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
- N528DC
- Operator
- Larsen Norman K
- Onboard fatalities
- Unknown
- Route
- From Grants Pass Airport (3S8), Grants Pass, ORTo Palo Alto Airport (PAO), Palo Alto, CA
- Aircraft age
- About 14 years (built 2000)
- 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 from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot reported that during the approach to landing to an airport located within a canyon, the airplane was high and fast. The pilot slipped the airplane, however the airspeed remained above the desirable 60 knots. The airplane "floated down the runway" and touched down further than normal. The airplane subsequently overran the departure end of the runway onto rough terrain which resulted in substantial damage to the wings, empennage and fuselage. The pilot added that there was no possibility of a go-around due to the airport's location in the canyon.
The pilot reported no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation.
Probable cause
The pilot's inadequate approach and excessive airspeed which resulted in a long landing and subsequent runway overrun onto rough terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR14CA299
- Event ID
- 20140718X83852
- Case number
- WPR14CA299
- 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: ef979b43335d7c9fcb11a9431e5957e86e7c382f0b000c4f4eb02c2eac817478; retrieved 2026-09-16T00:56:17.722Z.