CEN11FA465 · Pipistrel Taurus 503
Gemtec Pipistrel Taurus 503 · Accident: loss of control in flight during landing
From Durango La Plata County Airport (KDRO) to Durango, CO
Event
- NTSB case
- CEN11FA465
- 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
- 1 · 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
Pipistrel Taurus 503
- Aircraft type
- Pipistrel TAURUS
- 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
- N261T
- Operator
- Gemtec
- Onboard fatalities
- Unknown
- Route
- From Durango La Plata County Airport (KDRO), Durango, COTo Durango, CO
- 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
- Loss of control in flight
- 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
Witnesses observed the glider maneuvering at low altitude with the engine running, and it landed hard at an off-airport location. An examination of the airframe and engine did not detect any preimpact anomalies that would have prevented the normal operation of the glider, and the glider's ballistic recovery parachute had not been deployed. A review of the weather in the area found that conditions were favorable for convective clouds with updrafts and downdrafts up to 40 knots with the possibility of microbursts; therefore, it is likely that the pilot encountered strong wind conditions and chose to perform an off-airport landing. It is also likely that, had the pilot lost control of the glider at altitude (prior to the attempted landing), he would have deployed the ballistic recovery parachute.
Probable cause
The pilot’s loss of control during the off-airport landing in strong winds, which resulted in a hard landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN11FA465
- Event ID
- 20110708X04710
- Case number
- CEN11FA465
- 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: 970eb034c3390c7ba07062550d91132862aaf7aadb78e6833a1c74f884f9d946; retrieved 2026-09-13T21:32:33.430Z.