CEN11TA064 · Partenavia P.68
Texas Parks and Wildlife Department Partenavia P.68 · Accident: collision with terrain/object (non-CFIT) during an uncontrolled descent
From El Paso International Airport (ELP) to El Paso International Airport (ELP)
Event
- NTSB case
- CEN11TA064
- 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
- Government
- 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
Partenavia P.68
- Aircraft type
- Partenavia P-68
- 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
- N44956
- Onboard fatalities
- Unknown
- Route
- From El Paso International Airport (ELP), El Paso, TXTo El Paso International Airport (ELP), El Paso, TX
- 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
- Public Aircraft
- 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
- Uncontrolled descent
- 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
- Collision with terrain/object (non-CFIT)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.
NTSB narrative
While performing a low-level law enforcement patrol flight, the pilot crossed a ridge and observed a parked vehicle. To investigate further, he lowered the flaps and descended to approximately 200 feet, into a canyon. The pilot made a second pass over the vehicle and initiated a right turn, during which the airplane encountered a tailwind that resulted in a rapid loss of airspeed and a descent. The pilot leveled the airplane and increased the power; however, the airplane was too slow and low to turn out of the canyon. As a result, the airplane stalled and impacted terrain. The pilot stated there were no preflight mechanical malfunctions or anomalies with the airplane
Probable cause
The pilot's decision to conduct a low-level flight in mountainous terrain in an area where downdrafts were prevalent, resulting in the inadvertent loss of control and the collision with the terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN11TA064
- Event ID
- 20101110X55356
- Case number
- CEN11TA064
- 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: 1cc916d8fbd21328ab7a47aa905c29cafdd13a852c24e2e89d723933134fc67d; retrieved 2026-09-15T15:33:20.179Z.