Cirrus Design CORP SR22 and amateur-built VANS RV-8 mid-air collision near Hollister, California, July 19, 2025
On July 19, 2025 at about 6:34 pm local time, 2 aircraft, Cirrus Design CORP SR22 (N551SG) and amateur-built VANS RV-8 (N926DT), were involved in a mid-air collision near Hollister, California (Hollister Municipal Airport). 1 person was seriously injured; 1 other was unhurt. 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 departing pilot’s failure to see and avoid the landing airplane during the takeoff, which resulted in a mid-air collision.
The departing pilot’s failure to see and avoid the landing airplane during the takeoff, which resulted in a mid-air collision.
Source: NTSB aviation accident database, copy made October 4, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- July 19, 2025 · about 6:34 pm local time
- Place
- Hollister, California · Hollister Municipal Airport · map
- Type
- Accident · mid-air collision
- Injuries
- 1 person was seriously injured; 1 other was unhurt.
- Weather
- visual conditions (good weather)
- Aircraft 1
- Cirrus Design CORP SR22, built 2017
- Registration
- N551SG · registry record · serial 4562
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
- Aircraft 2
- Amateur-built VANS RV-8, built 2002
- Registration
- N926DT · registry record · serial 80759
- Damage
- Minor damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative for the Cirrus Design CORP SR22 final · quoted from the NTSB record
The pilot of the Cirrus reported that he was conducting the RNAV GPS runway 31 approach in visual conditions. While crossing the threshold of the runway he saw what he thought was a wing and he heard a loud bang. The airplane nosed over and impacted the runway. The pilot of the RV-8 reported that he taxied to the beginning of the runway, near the fire base [CAL FIRE hangars]. The pilot looked for traffic and did not see any. The pilot applied power, rotated and the airplane began to climb. When the airplane was about 50 to 100 ft above ground level, he saw something from below and on the right side, then experienced “the inflight collision.” The pilot then reduced power and landed on the remaining runway. A video, from an airplane on a taxiway, captured the infight collision between the Cirrus and RV-8 airplanes. White flashing lights were in view near the runway that were consistent with runway end identifier lights (REIL) for runway 31. The Cirrus was descending to a point beyond the relocated threshold. The RV-8 was airborne prior to the relocated threshold and while climbing, struck the empennage of the Cirrus. The Cirrus rapidly descended to the runway, which substantially damaged the fuselage and empennage. The RV-8 landed on the runway. Both pilots reported no mechanical malfunctions or failures, with their respective airplanes, that would have precluded normal operations. According to 14 Code of Federal Regulations §91.113(g), “Landing. Aircraft, while on final approach to land or while landing, have the right-of-way over other aircraft in flight or operating on the surface…”
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 amateur-built VANS RV-8 final · quoted from the NTSB record
The pilot of the Cirrus reported that he was conducting the RNAV GPS runway 31 approach in visual conditions. While crossing the threshold of the runway he saw what he thought was a wing and he heard a loud bang. The airplane nosed over and impacted the runway. The pilot of the RV-8 reported that he taxied to the beginning of the runway, near the fire base [CAL FIRE hangars]. The pilot looked for traffic and did not see any. The pilot applied power, rotated and the airplane began to climb. When the airplane was about 50 to 100 ft above ground level, he saw something from below and on the right side, then experienced “the inflight collision.” The pilot then reduced power and landed on the remaining runway. A video, from an airplane on a taxiway, captured the infight collision between the Cirrus and RV-8 airplanes. White flashing lights were in view near the runway that were consistent with runway end identifier lights (REIL) for runway 31. The Cirrus was descending to a point beyond the relocated threshold. The RV-8 was airborne prior to the relocated threshold and while climbing, struck the empennage of the Cirrus. The Cirrus rapidly descended to the runway, which substantially damaged the fuselage and empennage. The RV-8 landed on the runway. Both pilots reported no mechanical malfunctions or failures, with their respective airplanes, that would have precluded normal operations. According to 14 Code of Federal Regulations §91.113(g), “Landing. Aircraft, while on final approach to land or while landing, have the right-of-way over other aircraft in flight or operating on the surface…”
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 Cirrus Design CORP SR22 from the NTSB's investigation tables, in plain English
What happened, in order
- Collision during takeoff/land during landing defining event
The NTSB's findings
- Environmental issues › Physical environment › Object/animal/substance › Aircraft › Effect on equipment
Pilot
- Certificate: private
- Ratings: single-engine land; instrument: airplane
- Flight time: 292.9 hours in all; 156 in this make and model; 15.2 in the last 90 days; 2.1 in the last 30 days; 219.2 as pilot in command
- Last flight review: December 1, 2023
- Medical certificate: Class 3 (without waivers/limitations)
- Seat: left
- Injury: serious injuries
The aircraft
- Last inspection: 100-hour inspection
- Maximum gross weight: 3,600 lb
- Seats: 5
- Landing gear: fixed
- Engine: Continental IO-550-N (piston); 0 hours total
- Fire on the ground
The flight
- Departed from: VNY Van Nuys CA at 5:07 pm
- Flight plan: IFR
- Runway 31, 6,350 ft by 150 ft
Weather at the time
- Light: daylight
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 72°F (22°C), dew point 55°F (13°C)
- Altimeter: 30.04 inHg
- Observation at 12:15 pm from KCVH, 1 miles away
Weather report (METAR): KCVH 191915Z AUTO 00000KT 10SM CLR 22/13 A3004 RMK A01
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flig | 1 |
The factual record for the amateur-built VANS RV-8 from the NTSB's investigation tables, in plain English
What happened, in order
- Collision during takeoff/land during takeoff
The NTSB's findings
- Personnel issues › Action/decision › Action › Incorrect action selection › Pilot
- Personnel issues › Psychological › Attention/monitoring › Monitoring other aircraft › Pilot
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 4,049 hours in all; 1,344 in this make and model
- Last flight review: September 14, 2024
- Medical certificate: Unknown
- Seat: frt
- Injury: no injuries
The aircraft
- Airframe total time: 1,768 hours
- Last inspection: condition inspection, June 2, 2025; 6 hours since
- Maximum gross weight: 1,800 lb
- Seats: 2
- Landing gear: fixed
- Engine: Lycoming IO360-A1B6 (piston); 1,768 hours total
The flight
- Flight plan: none
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flig | 1 |
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 WPR25LA219.
