CHI04CA289 · Arganbright Vans RV-4
Arganbright Vans RV-4 · Accident: loss of control on ground/water during landing
From Chan Gurney Municipal Airport (YKN) to Custer County Airport (CUT)
Event
- NTSB case
- CHI04CA289
- 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
Arganbright Vans RV-4
- Aircraft type
- Arganbright VANS RV-4
- 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
- N968MA
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Chan Gurney Municipal Airport (YKN), Yankton, SDTo Custer County Airport (CUT), Custer, SD
- 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
- First occurrenceThe 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/water
- 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
- Pilot in command › Directional control, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane was damaged when it departed the runway and struck an embankment during landing. The pilot stated that he was landing to the west and during the landing roll, the airplane suddenly veered to the right. He stated that he attempted to correct with rudder and brakes but was unable to keep the airplane from exiting the runway surface. The airplane subsequently struck an embankment. In his statement, the pilot stated that there were no mechanical problems with regard to the airplane. He also stated that he suspected that the winds from the canyon adjacent to the airport caused a wind shift at the point where the loss of control occurred. The reported winds were from 290 degrees at 9 knots.
Probable cause
The pilot's failure to maintain directional control during the landing. Factors were the sudden wind shift and the embankment.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI04CA289
- Event ID
- 20041028X01718
- Case number
- CHI04CA289
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: bc83194faf7151b9d317199c212d7add66c58292e95fd14ff31db23f6e09f175; retrieved 2026-09-22T06:40:14.547Z.