The U.S. aircraft register, updated daily
Accidents · NTSB DFW05LA053 · Final report

Amateur-built Kit Fox Series VI accident near Cleveland, Oklahoma, January 10, 2005

On January 10, 2005 at about 10:50 pm local time, a amateur-built Kit Fox Series VI, registered N982KF, was destroyed in an accident near Cleveland, Oklahoma (Cleveland Municipal Airport). It was a personal flight under general aviation rules (Part 91). 1 person was seriously injured. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot's failure to maintain control and sufficient airspeed while performing an abrupt pull-up manuever after takeoff, which resulted in an inadvertent stall/spin.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
January 10, 2005 · about 10:50 pm local time
Place
Cleveland, Oklahoma · Cleveland Municipal Airport · map
Type
Accident
Injuries
1 person was seriously injured.
Weather
visual conditions (good weather)
Aircraft
Amateur-built Kit Fox Series VI
Registration
N982KF · no longer on the register · serial 50004-023
Damage
Destroyed
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The home-built experimental airplane was performing touch and go landings. One witness, who was located on airport property, observed the airplane flying "very low" to the ground at a "high rate of speed" (in ground effect) parallel to the runway. As the airplane reached the end of the runway, it "climbed steeply," started a left turn, and "spun" nose first into the ground. In a written statement, the 389-hour private pilot reported that he did "not have any recollection of the accident due to a head injury and/or medications." An FAA inspector, who examined the wreckage at the accident site, reported that the horizontal stabilator and electric trim for pitch control did not exhibit pre-impact anomalies. Additionally, a check of flight control cable continuity did not reveal abnormalities other than impact damage.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 389 hours in all; 26 in this make and model; 11 in the last 90 days; 2 in the last 30 days; 346 as pilot in command
  • Last flight review: June 26, 2004
  • Medical certificate: Class 3 (valid medical--w/ waivers/lim.)
  • Seat: left
  • Injury: serious injuries

The aircraft

  • Airframe total time: 122 hours
  • Last inspection: annual inspection, October 25, 2004; 10 hours since
  • Maximum gross weight: 1,550 lb
  • Seats: 2
  • Landing gear: fixed
  • Engine: Continental O-200A (piston); 0 hours total

The flight

  • Departed from: 4F1 Tulsa OK at 10:15 pm
  • Destination: OK
  • Flight plan: none

Weather at the time

  • Light: daylight
  • Wind: from 210° at 7 knots
  • Visibility: 10 statute miles
  • Sky: a few clouds at 28,000 ft
  • Temperature: 66°F (19°C), dew point 57°F (14°C)
  • Altimeter: 29.87 inHg
  • Observation at 10:53 pm from RVS, 27 miles away

Injuries

FatalSeriousMinorNone
Crew1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.