The U.S. aircraft register, updated daily · Carbon Free Flight by 2050
Accidents · NTSB CEN25LA250 · Preliminary: the investigation is not finished

Game Composites LLC GB1 GAMEBIRD and Vans RV-8 mid-air collision near Tarkio, Missouri, July 12, 2025

On July 12, 2025 at about 1:30 pm local time, 2 aircraft, Game Composites LLC GB1 GAMEBIRD (N588AF) and Vans RV-8 (N931KZ), were involved in a mid-air collision near Tarkio, Missouri (Gould Peterson Municipal airport). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).

Preview. This page is not yet listed for search engines.

The NTSB's probable cause their words, unchanged

The NTSB has not yet published a probable cause for this accident. Investigations usually take one to two years; this page updates when the final report is released.

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

What the record shows

Date
July 12, 2025 · about 1:30 pm local time
Place
Tarkio, Missouri · Gould Peterson Municipal · map
Type
Accident · mid-air collision
Injuries
No one was hurt; 2 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft 1
Game Composites LLC GB1 GAMEBIRD, built 2021 · all GB1 GAMEBIRDs on the register
Registration
N588AF · registry record · serial 0039
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)
Aircraft 2
Vans RV-8, built 2024
Registration
N931KZ · registry record · serial 83685
Damage
Minor damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative for the Game Composites LLC GB1 GAMEBIRD preliminary · quoted from the NTSB record

On July 12, 2025, about 0830 central daylight time, a Game Composites GB-1 Gamebird airplane, N588AF, was substantially damaged, and a Vans RV-8, N931KZ, sustained minor damage, when they were involved in an accident near the Gould Peterson Municipal Airport (K57), Tarkio, Missouri. Neither pilot was injured. Both airplanes were operated as a Title 14 Code of Federal Regulations Part 91 personal flights. The airport was hosting the Wing Nuts Flying Circus event on the day of the accident. This included an air show, aircraft flybys, and static aircraft displays. A temporary flight restriction (TFR) was in effect on July 11th and July 12th from 1230 until 1430 each day in conjunction with the event. The TFR consisted of a 5 nm radius centered on K57 from the surface to 15,000 ft mean sea level. A temporary control tower was established at K57 for the event and was in operation at the time of the accident. The airport was normally a non-towered airport. The pilot of N588AF was the lead in a formation of five airplanes. He reported reaching the base leg in the traffic pattern and was then cleared to land. The approach was without incident until another pilot in his formation instructed him to execute a go-around. He complied immediately; however, that was not in time to prevent a collision with an airplane already on the runway. The airplane sustained substantial damage when the rudder contacted the propeller of the airplane on the runway. The lower aft corner of the rudder was cutoff by the propeller. The pilot of N931KZ reported that he had landed and was rolling out at the time of the accident. He heard an increase in noise and then a severe vibration as the other airplane passed overhead. The propeller of his airplane contacted the rudder of the other airplane. A witness reported that he observed the events leading to the accident. He landed about 30 minutes prior and had parked his airplane in a grass area about halfway down the runway. From that vantage point, he observed an airplane on what appeared to be a straight-in final for runway 36. He then observed a second airplane turn from a close-in left base to final as it descended on top of the first airplane on final. He was unable to see if the airplanes continued or if they came into contact with each other. From his vantage point, it did not appear that either plane was in distress.  A witness reported that he observed the events leading to the accident. He landed about 30 minutes prior and had parked his airplane in a grass area about halfway down the runway. From that vantage point, he observed an airplane on what appeared to be a straight-in final for runway 36. He then observed a second airplane turn from a close-in left base to final as it descended on top of the first airplane on final. He was unable to see if the airplanes continued or if they came into contact with each other. From his vantage point, it did not appear that either plane was in distress.  Figure 1 – Rudder damage to accident airplane

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 NTSB's narrative for the Vans RV-8 preliminary · quoted from the NTSB record

On July 12, 2025, about 0830 central daylight time, a Game Composites GB-1 Gamebird airplane, N588AF, was substantially damaged, and a Vans RV-8, N931KZ, sustained minor damage, when they were involved in an accident near the Gould Peterson Municipal Airport (K57), Tarkio, Missouri. Neither pilot was injured. Both airplanes were operated as a Title 14 Code of Federal Regulations Part 91 personal flights. The airport was hosting the Wing Nuts Flying Circus event on the day of the accident. This included an air show, aircraft flybys, and static aircraft displays. A temporary flight restriction (TFR) was in effect on July 11th and July 12th from 1230 until 1430 each day in conjunction with the event. The TFR consisted of a 5 nm radius centered on K57 from the surface to 15,000 ft mean sea level. A temporary control tower was established at K57 for the event and was in operation at the time of the accident. The airport was normally a non-towered airport. The pilot of N588AF was the lead in a formation of five airplanes. He reported reaching the base leg in the traffic pattern and was then cleared to land. The approach was without incident until another pilot in his formation instructed him to execute a go-around. He complied immediately; however, that was not in time to prevent a collision with an airplane already on the runway. The airplane sustained substantial damage when the rudder contacted the propeller of the airplane on the runway. The lower aft corner of the rudder was cutoff by the propeller. The pilot of N931KZ reported that he had landed and was rolling out at the time of the accident. He heard an increase in noise and then a severe vibration as the other airplane passed overhead. The propeller of his airplane contacted the rudder of the other airplane. A witness reported that he observed the events leading to the accident. He landed about 30 minutes prior and had parked his airplane in a grass area about halfway down the runway. From that vantage point, he observed an airplane on what appeared to be a straight-in final for runway 36. He then observed a second airplane turn from a close-in left base to final as it descended on top of the first airplane on final. He was unable to see if the airplanes continued or if they came into contact with each other. From his vantage point, it did not appear that either plane was in distress.  A witness reported that he observed the events leading to the accident. He landed about 30 minutes prior and had parked his airplane in a grass area about halfway down the runway. From that vantage point, he observed an airplane on what appeared to be a straight-in final for runway 36. He then observed a second airplane turn from a close-in left base to final as it descended on top of the first airplane on final. He was unable to see if the airplanes continued or if they came into contact with each other. From his vantage point, it did not appear that either plane was in distress.  Figure 1 – Rudder damage to accident airplane

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 for the Game Composites LLC GB1 GAMEBIRD from the NTSB's investigation tables, in plain English

What happened, in order

  1. Collision during takeoff/land during approach (VFR go-around) defining event

The aircraft

  • Airframe total time: 311 hours
  • Last inspection: annual inspection, April 3, 2025; 20 hours since
  • Maximum gross weight: 2,200 lb
  • Seats: 2
  • Landing gear: fixed

The flight

  • Departed from: K57 Tarkio MO at 1:00 pm
  • Destination: K57 Tarkio MO
  • Flight plan: none
  • Runway 36, 3,600 ft by 75 ft

Weather at the time

  • Light: daylight
  • Wind: from 340° at 9 knots, gusting 16
  • Visibility: 10 statute miles
  • Sky: a few clouds at 5,500 ft
  • Temperature: 72°F (22°C), dew point 66°F (19°C)
  • Altimeter: 29.99 inHg
  • Observation at 8:55 am from KSDA, 18 miles away

Weather report (METAR): METAR KSDA 121355Z AUTO 34009G16KT 10SM FEW055 22/19 A2999

Injuries

FatalSeriousMinorNone
Flig1

The factual record for the Vans RV-8 from the NTSB's investigation tables, in plain English

What happened, in order

  1. Collision during takeoff/land during landing (landing roll)

The aircraft

  • Airframe total time: 74 hours
  • Last inspection: condition inspection, August 19, 2024; 74 hours since
  • Maximum gross weight: 1,800 lb
  • Seats: 2
  • Landing gear: fixed

The flight

  • Departed from: PMV Murray NE at 11:09 pm
  • Destination: K57 Tarkio MO
  • Flight plan: none

Injuries

FatalSeriousMinorNone
Flig1

About this page

Everything above comes from the NTSB's public accident database: the narrative, probable cause and findings are the NTSB's own words, and the coded tables behind its report (pilot, aircraft, flight, weather, injuries, sequence of events) are written out in plain English. Pilots' ages, home towns and medical details are left out on purpose. The docket at the NTSB holds the report as a PDF and the investigation's photographs and documents. This site never names pilots, passengers or anyone else involved. A preliminary report describes what is known soon after the event and can change; the final report, with the probable cause, usually follows one to two years later and this page is refreshed when it does. Case number CEN25LA250.