The U.S. aircraft register, updated daily
Accidents · NTSB CEN26LA258 · Preliminary: the investigation is not finished

Vans Aircraft Inc RV-8A accident near Mineral Point, Wisconsin, July 17, 2026

On July 17, 2026 at about 5:48 pm local time, a 2001 Vans Aircraft Inc RV-8A, an amateur-built aircraft,, registered N22SZ, was substantially damaged in an accident during enroute (climb to cruise) near Mineral Point, Wisconsin (Iowa County Airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).

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 November 2, 2026. Docket and reports at the NTSB.

What the record shows

Date
July 17, 2026 · about 5:48 pm local time · cases in 2026
Place
Mineral Point, Wisconsin · Iowa County Airport · cases near this airport · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Vans Aircraft Inc RV-8A, built 2001, amateur-built · all RV-8As on the register
Registration
N22SZ · registry record · serial 81381
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

On July 17, 2026, at 1748 central daylight time, an experimental amateur-built Vans Aircraft Inc RV-8A, N22SZ, sustained substantial damage when it was involved in an accident in Mineral Point, Wisconsin. The commercial pilot was uninjured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The pilot stated that while en route to Oshkosh, Wisconsin, he stopped at Iowa County Airport, Mineral Point (MRJ), Wisconsin, for fuel and to wait for visual flight conditions to improve at the destination airport. He then departed MRJ, and after climbing to 9,000 ft mean sea level, he switched fuel tanks and a “moment or so” later, the engine lost power. He then initiated a return to MRJ, during which he attempted several engine restarts. The engine restarted during the descent to MRJ, then lost power, restarted again, and continued to operate for the remainder flight to and taxi at MRJ. After the flight, the pilot stated that he talked to six or eight pilots at MRJ, two of which were mechanics, and a mechanic based at MRJ, about the loss of engine power that he had experienced. The group discussed mechanical and electrical fuel pump failures, carburetor icing, vapor lock, and test flying the airplane. On the following day, the pilot attempted a test flight of the airplane from MRJ. The pilot stated that the engine start for the test flight was “very clean normal start,” there were no hot start or fuel vapor problems, and the engine run-up was normal. He said that shortly after takeoff and early in the climb, the airplane engine began to run rough, and he decided to end the test flight and return to the airport. While turning left and climbing into the airport traffic pattern, the engine lost power. The pilot then decided to turn and land the airplane in the opposite direction since there was no engine power to fly an airport traffic pattern. During the turn, the engine started again but later lost power, and the airplane was high and fast. The pilot performed a forced landing on runway 11 where it impacted the runway surface. The airplane sustained substantial to both wings, the engine firewall, and an engine mount. The airplane was retained for further examination.

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

What happened, in order

  1. Loss of engine power (total) during enroute (climb to cruise) defining event

The aircraft

  • Airframe total time: 704.6 hours
  • Last inspection: condition inspection, May 19, 2026
  • Maximum gross weight: 1,800 lb
  • Seats: 2
  • Landing gear: fixed

The flight

  • Flight plan: none
  • Runway 11, 5,001 ft by 75 ft

Weather at the time

  • Light: daylight
  • Wind: from 240° at 6 knots
  • Visibility: 8 statute miles
  • Sky: scat at 4,000 ft
  • Temperature: 90°F (32°C), dew point 66°F (19°C)
  • Altimeter: 30.03 inHg
  • Observation at 12:35 pm from PVB, 15 miles away

Injuries

FatalSeriousMinorNone
Flight crew1

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

The NTSB has not released the docket for this case yet. The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), is usually released when the investigation is nearly complete, and the list here is refreshed when it appears. Check at the NTSB.

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/CEN26LA258.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

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 does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.