FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DFW06CA167 · Agin Jeffrey T RV-4

27 Jun 2006 · Arlington, TX, United States

Agin Jeffrey T RV-4 · Accident: hard landing

From Arlington Municipal Airport (KGKY) to Arlington Municipal Airport (KGKY)

Report a problem

Event

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

Agin Jeffrey T RV-4

Aircraft type
Agin Jeffrey 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
N834JA
Operator
Unknown
Onboard fatalities
Unknown
Route
From Arlington Municipal Airport (KGKY), Arlington, TXTo Arlington Municipal Airport (KGKY), Arlington, 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
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 › Recovery from bounced landing, improper

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The 370-hour private pilot, who reported having accumulated a total of 133-hours in the same make and model aircraft, lost directional control of the tailwheel-equipped single-engine airplane while attempting to land on a 6.080-foot long, by 100-foot wide concrete runway. The pilot reported that while landing on runway 34, the airplane landed very hard which caused the airplane to bounce-back into the air. The pilot reported that she applied full engine power in an attempt to abort the landing; however, the airplane swerved-off the runway as the left wing struck the ground. The airplane was reported to remained airborne for about 200-yards prior to impacting a dirt embankment and came to rest in an upright position. At the time of the mishap the winds were reported as light and variable. The homebuilt airplane had accumulated a total of 304.5 hours since new. The pilot did not report any mechanical malfunctions that would have prevented normal flight operations.

Probable cause

The pilot's improper recovery from a bounced landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DFW06CA167
Event ID
20060713X00933
Case number
DFW06CA167
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: c1212c7b04d862d9698dcd507260ab05dabf307db0490b856f75e1c1200dd26c; retrieved 2026-09-21T18:44:25.766Z.