FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA16CA018 · Furgason James E VANS RV 4

12 Oct 2015 · San Marcos, TX, United States

Furgason James E VANS RV 4 · Accident: loss of control on ground during landing

From New Braunfels National Airport (BAZ) to San Marcos Regional Airport (HYI)

Report a problem

Event

NTSB case
GAA16CA018
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

Furgason James E 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
N165DR
Operator
Unknown
Onboard fatalities
Unknown
Route
From New Braunfels National Airport (BAZ), New Braunfels, TXTo San Marcos Regional Airport (HYI), San Marcos, TX
Aircraft age
About 29 years (built 1986)
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 of a tailwheel-equipped airplane reported that during the landing roll, traveling about 45 to 55 knots, he encountered a crosswind. The airplane veered off the runway to the left into the wind and collided with a taxiway sign. The airplane came to a stop in grass adjacent to the runway. The fuselage sustained substantial damage.

The pilot stated there were no mechanical malfunctions or failures with the airplane that would have precluded normal operation.

About the time of the accident, a routine aviation weather report at the airport reported the wind at 190 degrees true at 12 knots and the runway heading was 260 degrees magnetic, which resulted in an 11 knot crosswind component.

Probable cause

The pilot's loss of directional control during the landing roll in crosswind conditions, which resulted in a runway excursion and an impact with an airport sign.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA16CA018
Event ID
20151019X65515
Case number
GAA16CA018
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: 2e9963c5ad58d93c35b3442dec0e999892543bef626959ab2745fbca0eae1cb7; retrieved 2026-09-16T02:54:07.265Z.