FTW02LA125 · Howard Harder Skybolt
Howard Harder Skybolt · Accident: in flight collision with terrain/water en route
From GCK · Claremore, OK to GCK · Claremore, OK
Event
- NTSB case
- FTW02LA125
- 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
- 1 · 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
Howard Harder Skybolt
- Aircraft type
- Howard Harder SKYBOLT
- 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
- N16HH
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From GCK · Claremore, OKTo GCK · Claremore, OK
- 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
- En route · descent
- 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
- In flight 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
- Destroyed
Cause areas
- Pilot in command › Clearance, 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
After calling the Flight Service Station to check the winds and have the aerobatic box opened, the pilot instructed the lineman to add 5 gallons of fuel to the airplane's main tank. After fueling the pilot taxied to runway 17 and departed at 1010. At 1040 the pilot called in for the winds. The lineman advised him they were 180 degrees at 18 knots with gusts to 22 knots. The pilot then made another call, but the lineman didn't understand what he said. At 1045 the lineman attempted to contact the pilot to inform him that personnel would be on the runway doing repair work. The pilot did not respond. At 1050 the lineman was notified in person by a local resident that he had observed an airplane doing maneuvers, that it went behind a tree line and he didn't see it come back up. At 1052 the lineman began an aerial search, spotting the aircraft wreckage at 1054, approximately 1,000 feet northwest of the departure end of runway 17. One witness said he observed the airplane descending straight down from about 1,000 feet above the ground with the wings rotating clockwise, impacting the ground after it went out of sight behind a row of trees. A second witness said he saw the airplane headed downward in a steep angle, loop, float for 1 second, loop again, and then go straight down. A third witness said he saw a small two-wing airplane wobble in the air, then suddenly go into a loop, and then come down and disappear below a tree line. The pilot had been under treatment for frequent and severe headaches, and had been prescribed frequent narcotic medications and anti-migraine medications as primary treatments for the condition. The most recent prescriptions for narcotic medication and anti-migraine medication were filled 3 days prior to the accident. Post-accident toxicoloty testing revealed the presence of multiple medications, including two different prescription antidepressants detected in blood and a prescription anti-anxiety medication, metabolites of a different prescription anti-anxiety medication, and a prescription narcotic detected in urine. Examination of the airframe and engine, and their logbooks, did not reveal any pre-existing anomalies which would have prevented normal operations.
Probable cause
The failure of the pilot to maintain clearance with terrain for undetermined reasons while conducting aerobatic maneuvers. A factor contributing to the accident was the physical impairment of the pilot.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW02LA125
- Event ID
- 20020422X00568
- Case number
- FTW02LA125
- 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: 7fc995b6862ede57b2fbf540bbc4d259293b5d13caee2b58bba89d7c29c8445f; retrieved 2026-09-20T20:02:45.168Z.