FTW02LA169 · Golias RV6
Golias RV6 · Accident: hard landing
From 5R3 · Lago Vista, TX to 77T · Kittie Hill, TX
Event
- NTSB case
- FTW02LA169
- 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
Golias RV6
- Aircraft type
- Golias RV6
- 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
- N16PG
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 5R3 · Lago Vista, TXTo 77T · Kittie Hill, 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
- Hard landing
- 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 pilot was practicing short field landings on the turf airstrip. He made his first approach at 80 miles per hour, which terminated in a full stop landing. Not satisfied with the first approach and landing, he decided to attempt another one. The second approach was executed using 40 degrees of flaps, an approach speed of 75 miles per hour, and a steeper descent angle. As the pilot flared, the airspeed degraded, which resulted in a high sink rate. The pilot applied full power; however, the airplane impacted the runway, bounced hard, and veered to the left. The pilot then pulled the power off, and subsequently, the airplane came to rest in an upright position after impacting a berm approximately 30 feet left and parallel to the runway.
Probable cause
the pilot's failure to maintain directional control while landing. Contributing factor is the pilot's improper recovery from a bounced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW02LA169
- Event ID
- 20020606X00819
- Case number
- FTW02LA169
- 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: 78199a6d191900adbd8bead06d302b5451d10f8f19c8164b0a04fe6238d9c1c2; retrieved 2026-09-22T10:53:27.705Z.