GAA17CA127 · Vaughan Gerald R SIDE WINDER TD
Vaughan Gerald R SIDE WINDER TD · Accident: loss of control on ground during landing
From Claremore Regional Airport (GCM) to McCook Ben Nelson Regional Airport (MCK)
Event
- NTSB case
- GAA17CA127
- 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
Vaughan Gerald R SIDE WINDER TD
- Aircraft type
- Vaughan Gerald SIDE WINDER TD
- 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
- N60JV
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Claremore Regional Airport (GCM), Claremore, OKTo McCook Ben Nelson Regional Airport (MCK), McCook, NE
- 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
- Loss of control on ground
- 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
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that, during the landing roll in gusting wind conditions, the airplane veered to the left. He applied right rudder and brake, but the airplane struck a runway sign on the left side of the runway and exited the runway.
The airplane sustained substantial damage to the fuselage.
The pilot reported that there were no preaccident mechanical failures or malfunctions with the airframe or engine that would have precluded normal operation.
A review of recorded data from the automated weather observation station located on the airport revealed that, about 8 minutes after the accident, the wind was 320 ° true at 19 knots, gusting to 25 knots, and peak wind was 300 ° true at 27 knots. The airplane landed on runway 30.
Probable cause
The pilot’s failure to maintain directional control during the landing roll in gusting wind conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA17CA127
- Event ID
- 20170131X04522
- Case number
- GAA17CA127
- 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: 7bbd875784543f8941598490a2ca8f4475a4fa70e21dda535669223a11358769; retrieved 2026-09-16T04:59:04.974Z.