CEN10CA464 · Cessna 414
Cessna 414 · Accident: runway excursion during landing
From North Texas Regional Airport Perrin Field (GYI) to 501 · Vici, OK
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- CEN10CA464
- 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 414
- Aircraft type
- Cessna 414
- 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
- N414TT
- Operator
- Wireless Connections
- Onboard fatalities
- Unknown
- Route Possible conflict
- From North Texas Regional Airport Perrin Field (GYI), Sherman, TXTo 501 · Vici, OK
- 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 as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the pilot, he was landing on a short runway and during landing rollout he was unable to stop the airplane. The airplane overran the end of the runway at about 10 to 15 miles per hour. The pilot steered the airplane to miss a four-inch diameter pipe sticking out of the ground on the extended runway centerline, but the right main landing gear struck the pipe. The right main gear collapsed and the airplane came to rest in a shallow ditch and on a road. The right wing spar was bent. Flight control continuity was confirmed and no systems anomalies were found. Skid mark analysis by police on scene indicated that the airplane landed 300 feet down the 2,565-foot runway. The Federal Aviation Administration inspector on scene computed a landing roll of approximately 2,200 feet.
Probable cause
The pilot's failure to ensure adequate runway remaining during landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN10CA464
- Event ID
- 20100809X84516
- Case number
- CEN10CA464
- 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: e6a530eedb860de5b30a1ff174b0f371057706eed451f8b8391f0a0679496910; retrieved 2026-09-15T14:48:59.808Z.