CHI08LA185 · Traxler John N KITFOX
Traxler John N KITFOX · Accident: runway excursion during landing
From Hartford Brainard Airport (HFD) to Hartford Brainard Airport (HFD)
Event
- NTSB case
- CHI08LA185
- 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
Traxler John N KITFOX
- Aircraft type
- Traxler John KITFOX
- 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
- N767JD
- Operator
- Dill Jeffrey R
- Onboard fatalities
- Unknown
- Route
- From Hartford Brainard Airport (HFD), Hartford, CTTo Hartford Brainard Airport (HFD), Hartford, CT
- 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
- 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
- Runway excursion
- 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
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Experience/knowledge
- Personnel issues › Task performance
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 touch-and-go landings with a passenger in his experimental tailwheel-equipped airplane. On the fourth touch and go, the pilot decided to land on a different runway with a mild crosswind, where he veered off the right side of the runway. He tried to conduct a go-around, but departed the right side of the runway and hit a taxiway sign, resulting in substantial damage to the airplane. The pilot's written statement suggested that his inexperience in tailwheel aircraft was likely the root cause and that additional training in tailwheel aircraft was appropriate.
Probable cause
The pilot's failure to compensate for crosswinds resulting in a loss of directional control while landing. Contributing to the accident was the pilot's lack of experience and training in tailwheeled airplanes.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI08LA185
- Event ID
- 20081004X12056
- Case number
- CHI08LA185
- 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, 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: 263acd512bcd16dfd392bf8c10f4a86b710fd23021def1c26b8250798fdcd169; retrieved 2026-09-15T10:24:02.225Z.