Vans RV8 accident near Linden, Michigan, August 3, 2026
On August 3, 2026 at about 2:25 pm local time, a 2008 Vans RV8, registered N412CV, was substantially damaged in an accident during landing near Linden, Michigan (Prices 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 collision with a deer during touch-and-go landings.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- August 3, 2026 · about 2:25 pm local time · cases in 2026
- Place
- Linden, Michigan · Prices · 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 RV8, built 2008
- Registration
- N412CV · registry record · serial 81149
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot reported that during the landing roll on runway 27 he observed three deer crossing the runway. The pilot initiated a go-around and heard a loud bang during the maneuver. The pilot subsequently flew a traffic pattern and returned for landing, unaware that the deer strike had damaged the right main landing gear and separated a portion of the landing gear assembly. During the subsequent landing, the airplane veered to the right and struck a runway marker sign, which resulted in the collapse of the left main landing gear. The airplane then skidded into the grass area adjacent to the runway and came to a stop. The airplane sustained substantial damage to the aft lower fuselage structure. The pilot reported no preimpact mechanical malfunctions or failures with the airframe or the engine that would have precluded normal operation. A review of the airport directory found a remark to alert pilots to deer on and in the vicinity of the airport.
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
- Collision during takeoff/land during approach (VFR go-around)
- Landing gear collapse during landing (flare/touchdown)
- Wildlife encounter (non-bird) during landing defining event
The NTSB's findings
- Environmental issues › Physical environment › Object/animal/substance › Animal(s)/bird(s) › Ability to respond/compensate
- Environmental issues › Physical environment › Object/animal/substance › Animal(s)/bird(s) › Effect on equipment
Pilot
- Certificate: commercial pilot, private, remote
- Ratings: single-engine land; single-engine sea; instrument: airplane
- Flight time: 724 hours in all; 5 in this make and model; 724 as pilot in command
- Last flight review: August 7, 2026
- Medical certificate: BasicMed (without waivers/limitations)
- Seat: ctr
- Injury: no injuries
The aircraft
- Airframe total time: 276 hours
- Last inspection: condition inspection, August 20, 2025
- Maximum gross weight: 1,800 lb
- Seats: 2
- Landing gear: fixed
- Engine: Superior IO 360 xp-103 (piston); 281 hours total
The flight
- Departed from: 3DA Flushing MI at 1:30 pm
- Flight plan: none
- Runway 09/2, 3,999 ft by 75 ft
Weather at the time
- Light: daylight
- Wind: from 300° at 4 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 70°F (21°C), dew point 61°F (16°C)
- Altimeter: 29.99 inHg
- Observation at 9:53 am from KFNT, 10 miles away
Weather report (METAR): METAR KFNT 031353Z 30004KT 10SM CLR 21/16 A2999 RMK AO2 SLP154 T02060161=
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Photographs from the investigation 2 pictures from the NTSB's docket, as the NTSB released them
The NTSB's photographs with the NTSB's captions, at screen size. Open a picture to see it full size or to report one that should not be shown.
Documents from the investigation the NTSB's docket: the evidence folder behind the report
5 documents, released by the NTSB on October 1, 2026. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 10 pages | View Download |
| 2 | Photos | PDF, 3 pages · our copy | View Download |
| 3 | Memorandum for Record A�� Telephone Interview, Airport Manager | PDF, 1 page | View Download |
| 4 | Memorandum for Record A�� Additional Information to 6120.1, Pilot Email | PDF, 2 pages | View Download |
| 5 | Airport Facility Directory - Prices Airport (9G2) | PDF, 2 pages | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Connections how this case links to the rest of the register
- N412CV on the register today · the tail number may have moved to another aircraft since
- Engine: Superior IO 360 xp-103 202 aircraft carry this series today · as the NTSB recorded it
- Prices Airport · nearest airport
- Dalton Airport · departed from
- Accidents and incidents in Michigan 2,107 since 1982 · 230 in the last ten years
- Michigan 7,238 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/CEN26LA291.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.

