DFW07CA200 · Vans RV-7A
Vans RV-7A · Accident: loss of control on ground/water during landing
From Rocky Mountain Metropolitan Airport (KBJC) to Hicks Air Field (T67)
Event
- NTSB case
- DFW07CA200
- 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
- 0
- 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
Vans RV-7A
- Aircraft type
- Vans RV-7
- 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
- N729CM
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Rocky Mountain Metropolitan Airport (KBJC), Denver, COTo Hicks Air Field (T67), Fort Worth, TX
- 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
- 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 › Aircraft 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 603-hour private pilot lost control of the homebuilt airplane while landing with a tailwind. The pilot, who was also the builder of the airplane, stated on the NTSB form 6120.1 (Pilot/Operator Accident/Incident Report) that during her first attempt to land, she "was getting strong wind gusts and about the time she flared the airplane, a strong wind gust shot me 50 feet in the air." The pilot then applied power and regained runway alignment and came around for a second landing attempt on Runway 02. The pilot reported that her second landing attempt resulted in a hard landing. When the nose gear contacted the ground the pilot encountered "a bad shimmy and when it settled I knew I did not have control of the airplane." Following the loss of control, the airplane was reported to have turned sharply to the right, nosed over and came to rest in the inverted position. The wind at the time of the mishap was reported from 200 degrees at 12 knots, gusting to 19 knots. The pilot added that she had noted during Unicom radio traffic that the landing traffic was to Runway 20 and she mistakenly landed to Runway 02.
Probable cause
The pilot's failure to maintain control of the airplane while landing. A contributing factor was the prevailing tailwind.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DFW07CA200
- Event ID
- 20071126X01845
- Case number
- DFW07CA200
- 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: d62c67877bb8c1a32719eafd925320c33eb712402fb010b99bbc8b6b353b3fc2; retrieved 2026-09-21T18:23:53.066Z.