WPR16FA067 · Flight Design Gmbh CTLS
County of Tulare Sheriffs Office Flight Design Gmbh CTLS · Accident: aerodynamic stall/spin while maneuvering
From Visalia Municipal Airport (KVIS) to Visalia Municipal Airport (KVIS)
Event
- NTSB case
- WPR16FA067
- 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
- 2 · 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
Flight Design Gmbh CTLS
- Aircraft type
- Flight Design CTLS
- 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
- N911TS
- Operator
- County of Tulare Sheriffs Office
- Onboard fatalities
- Unknown
- Route
- From Visalia Municipal Airport (KVIS), Visalia, CATo Visalia Municipal Airport (KVIS), Visalia, CA
- Aircraft age
- About 5 years (built 2011)
- 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
- Maneuvering · low-altitude flying
- 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
- Aerodynamic stall/spin
- 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The airplane, which was owned and operated by the local county sheriff's department, was on a low-altitude observation flight. According to GPS data recovered from the airplane, about 1 minute before the accident, the airplane was flying westbound (heading 242°) over a highway, about 500 feet above ground level (agl), and at a groundspeed of 52 knots. The GPS data and witness observations indicated that the airplane entered a left turn. According to the witnesses, the airplane's wings then dipped left and right, and the airplane descended to ground impact. The witnesses heard the engine operating in a steady tone until ground impact. A postcrash fire ensued, which destroyed the airplane.
Examination of the wreckage did not reveal evidence of any preimpact mechanical malfunctions or anomalies that would have precluded normal operation. The airplane's estimated weight at the time of the accident was about 152 lbs over the airplane's maximum gross weight. Because of the higher gross weight, the airplane's stall speed in a 30° banked turn was 3 knots higher than it would have been at the airplane's maximum gross weight. This resulted in a stall speed of about 48 knots calibrated airspeed, which was near the airplane's recorded groundspeed of 52 knots.
The sun position at the time of the accident was on a bearing of 241° and was 13° above the horizon, indicating that the pilot was looking directly into the sun before the left turn began. Another pilot who flew in the vicinity shortly after the accident reported that when flying westbound over the highway, he was looking straight into the sun, there was a lot of haze, and he could not distinguish the tops of the hills to the left of the highway from the sky. It is likely that the accident pilot was partially blinded by sun glare and did not see the hills rising above him on his left. After he entered the left turn moving away from the sun line, it is likely that the rising terrain suddenly came into view, and he increased the airplane's bank angle in order to avoid the terrain and exceeded the wing's critical angle-of-attack, which resulted in an aerodynamic stall. The altitude the airplane was operating at was too low to allow for a recovery.
Probable cause
The pilot's failure to maintain adequate airspeed while maneuvering at low altitude in hilly terrain, which resulted in the airplane's wing exceeding its critical angle-of-attack and a subsequent aerodynamic stall. Contributing to the accident were the pilot's inability to recognize the rising terrain due to the sun glare and the pilot's operation of the airplane in excess of its gross weight.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR16FA067
- Event ID
- 20160210X12541
- Case number
- WPR16FA067
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2016-02-11.
- API snapshot SHA-256: 803b5c7c3a869408730394582ca02cbc5fe35f81a6eec2efb26ddfe32982ac4c; retrieved 2026-09-14T21:41:09.658Z.