FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN10CA499 · Cessna 182P

20 Aug 2010 · Del Rio, TX, United States

Mid Valley Cessna 182P · Accident: landing area undershoot

From T65 · Wesaco, TX to Del Rio, TX (no airport)

Report a problem

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
CEN10CA499
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 182P

Aircraft type
Cessna 182
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
N1289S
Operator
Mid Valley
Onboard fatalities
Unknown
Route Narrative disagrees
From T65 · Wesaco, TXTo Del Rio, TX (no airport)
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 undershoot
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

  • Personnel issues › Action/decision

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

NTSB narrative

The private pilot was attempting to land his single-engine airplane on a private dirt strip when he got distracted by a cow that was adjacent to and moving toward the runway. Not paying attention to his glide path, the pilot made a lower than normal approach and landed short of the runway by about 5 to 10 feet. The airplane struck some rocks on a rise in the terrain and subsequently flipped over. The airplane sustained substantial damage to the nose and vertical tail, and showed wrinkles to the wings and fuselage. The pilot reported that there were no mechanical deficiencies with the airplane.

Probable cause

The pilot's failure to monitor his altitude while making a visual approach, which resulted in landing short of the runway and subsequent collision with terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN10CA499
Event ID
20100826X22427
Case number
CEN10CA499
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: d37b00c6f48de3c4e031824e93f79cbfd510813599be510c01a1d1f5bbbd1f85; retrieved 2026-09-15T14:57:56.219Z.