FTW03LA169 · Kilishek RV-8
Kilishek RV-8 · Accident: on ground/water collision with terrain/water during landing
From Lancaster Airport (LNC) to Scott Airport (31TX)
Event
- NTSB case
- FTW03LA169
- 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
Kilishek RV-8
- Aircraft type
- Kilishek RV-8
- 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
- N888GK
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Lancaster Airport (LNC), Lancaster, TXTo Scott Airport (31TX), Crawford, 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 · 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
- On ground/water collision with terrain/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 › Ground loop/swerve, intentional
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 reported that while on final approach for runway 17, a 1,900 foot long by 120-foot wide grass runway, he stabilized the aircraft at 65 knots, aiming to touch down approximately one third of the way down the runway. The aircraft "floated slightly, then skipped before settling on the ground." The pilot stated the aircraft "touched down longer than he intended, and the aircraft was not slowed sufficiently to stop at the end of the runway." The pilot further stated that he "applied full left ruder (and tailwheel steering) to intentionally ground loop the airplane rather than go into a ditch at the end of the runway." Subsequently, the aircraft nosed over coming to rest in the inverted position.
Probable cause
The pilot's intentional ground looping of the airplane. A contributing factor was the pilot's improper in-flight planning resulting in an improper selection of a touchdown point.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW03LA169
- Event ID
- 20030612X00857
- Case number
- FTW03LA169
- 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: ef56050bd8a7905f893ab717d056f269c22bf7a34dd28e7d642dcf89eeb6ad39; retrieved 2026-09-21T19:27:59.673Z.