Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

September 25, 2020 · Cessna 172S · N108VK

San Marcos, TX

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
September 25, 2020
Injury Outcomes
3 injuries (1 serious injury, 2 minor injuries)
Location
San Marcos, TX
Aircraft
Cessna 172S (2001)
Tail Number
N108VK
Injuries
Serious
Aircraft Damage
Substantial
NTSB Number
CEN20LA419

A low-wing Team Rockets F1 airplane and a high-wing Cessna 172 airplane were involved in a mid-air collision on final approach for landing. The airplanes entered the downwind leg of the traffic pattern within one minute of each other, with the F1 in front of the Cessna. There were four other airplanes in the traffic pattern or communicating on the airport’s common traffic frequency at that time. Shortly after entering the traffic pattern, the F1 pilot announced and performed a right 360° turn to increase spacing with the preceding airplane. The instructor onboard the trailing Cessna could not see the F1 and asked if the F1 had completed the turn. The F1 pilot responded that he was about to turn base, but he saw a Cessna below him and that he would extend downwind before turning to final. The instructor onboard the Cessna began a turn to base and reported that they saw the F1. About 45 seconds later, the F1 pilot reported that he was on final approach over a highway about 2 miles from the runway, which indicates he did not extend his downwind sufficiently to attain sufficient separation. The Cessna crossed the highway about the same time and also reported a 2-mile final. About 45 seconds later, the F1 pilot reported a 1 mile final. The instructor onboard the Cessna then reported a .8-mile final. Shortly after the last radio calls from the two airplanes, the F1 impacted the Cessna on the Cessna’s top left side. Both airplanes impacted the ground short of the runway. The Cessna flipped over and the F1 came to rest against a fence and caught fire. The Cessna sustained substantial damage and the F1 was destroyed. The F1 pilot recalled an airplane making position calls on final, which he assumed was behind him. He said that he had a clear view of the runway while on final and he did not see any traffic between him and the runway. It is likely that the low-wing configuration of the F1 prevented the F1 pilot from seeing the Cessna below him. Likewise, the occupants of the high-wing Cessna were restricted from seeing the F1 above them. Although the F1 pilot stated that he would extend his downwind leg, he did not extend it enough to gain safe separation from the Cessna, which resulted in the F1 and the Cessna arriving at nearly the same geographical point on 2- mile final at the same time. The standard position reports issued by both pilots were sufficient for the pilots to have had awareness of each other’s position on final; however, neither comprehended the conflict between their airplanes, possibly due to the high volume of radio calls from other aircraft in the traffic pattern and both pilots’ increased attention on preparing for landing.

NTSB Probable Cause

The F1 pilot’s failure to see and avoid the lower altitude Cessna while on final approach for landing. Contributing to the accident were the restrictions to pilot visibility inherent to low- and high-wing airplanes, and both pilots’ failure to recognize the conflict that developed between their airplanes.

Full Narrative

On September 24, 2020, about 1918 central daylight time (CDT), a Cessna 172 airplane, N108VK, was substantially damaged and a Team Rockets F1 airplane, N540LK, was destroyed when they were involved in a mid-air collision near San Marcos, Texas. The flight instructor onboard the Cessna received minor injuries, the student pilot was seriously injured, and the F1 pilot received minor injuries. The Cessna was operated as a Title 14 Code of Federal Regulations (CFR) Part 91 instructional flight and the F1 was operated as a Title 14 CFR Part 91 personal flight. San Marcos Regional Airport (HYI) was equipped with an air traffic control tower, which was closed at the time of the accident. Aircraft in the traffic pattern were self-reporting on the common traffic advisory frequency (CTAF), and a recording of the radio communications during the time of the accident was obtained. The Cessna was equipped with a GoPro camera mounted in the aft interior of the cockpit that captured video of the pilots and communications during the accident flight. The F1 was a tandem, two-seat, low-wing monoplane which was not equipped with Automatic Dependent Surveillance – Broadcast (ADS-B) equipment. The Cessna was a 4-seat, high-wing monoplane that was equipped with ADS-B. The Cessna entered the left downwind about 1912 for a full-stop landing. The student pilot was flying the airplane when they entered the pattern and there were 6 other airplanes in the traffic pattern or communicating on the CTAF at that time, including the F1. The F1 pilot stated that, when he entered the left downwind for runway 8 from the northeast he noticed an airplane in front of him and abeam the landing threshold. He announced and performed a right 360° turn for spacing and reentered the downwind. The instructor in the Cessna heard the F1 enter the traffic pattern on downwind, but he did not see the F1 perform the 360° turn and he tried to locate it using ADS-B. As the F1 was abeam the runway 8 threshold, the Cessna queried if the airplane that performed the 360° turn had rejoined the traffic pattern. The F1 pilot responded that he had and was about to turn left base, but he saw a Cessna below him on downwind at his 2 o’clock position and 0.7 to 0.9 miles away. The instructor took control of the airplane, announced they were “over the stadium turning left base,” and started a left turn. The “stadium” referenced was the Texas State University football stadium, located 2.9 miles east of the approach end of runway 8. At 19:15:40, the F1 pilot announced he would extend his downwind and “rejoin on the final.” Another airplane announced that they were on a short final a few seconds later. About 15 seconds later, the instructor continued a left turn and reported via radio that he saw another airplane “over the stadium.” At 19:16:24, the F1 pilot reported “over [Interstate 35 (I35)] inbound for landing on final for runway 8.” I35 passes under the flight path to runway 8 about 2.25 miles east of the approach end of the runway. The F1 pilot stated that he visually cleared his flight path at that point and did not see another airplane on final until the collision occurred. Nine seconds later, the Cessna reported that they were on a 2-mile final to runway 8. At 19:17:20 the F1 pilot reported he was on a 1-mile final. The instructor quickly looked outside, including upward and backward, and at 19:17:25 the Cessna radioed they were at 0.8 mile on final. There were no additional radio calls from either airplane for the remainder of the flight. The instructor continued to look outside until 19:17:52, when he focused his attention toward the runway. The Cessna’s altitude indicated 750 ft mean sea level (155 ft above ground level) at that time. The F1 pilot recalled an airplane making position calls on final, which he assumed was the airplane he had seen at his 2 o’clock and that it was behind him. He stated, “I had a clear, clear view of the runway, there was no traffic at all between me and the runway,” and “Obviously, to what I understood they were behind me because obviously they were not between me and the runway.” The F1 pilot said that he felt and saw the other airplane impact from the right side, 5 o’clock position shortly after he made his 1-mile position call and before the impact with the ground. The instructor stated that he felt the F1 impact the Cessna from above and the left, and the F1’s propeller hit the windshield and top of their cowling. He said that he could not control the airplane as it descended, and it hit the ground and flipped over. The Cessna came to rest inverted on the airport perimeter road and the F1 stopped a short distance away against the airport perimeter fence. The F1 pilot exited his airplane and assisted the occupants of the Cessna. The F1 subsequently caught fire and was destroyed. The Cessna sustained substantial damage to the fuselage, empennage, and both wings. The Federal Aviation Administration (FAA) Airplane Flying Handbook (AFH), Chapter 7, provides the following information to pilots: When approaching an airport for landing, the traffic pattern is normally entered at a 45° angle to the downwind leg, headed toward a point abeam the midpoint of the runway to be used for landing. The pilot should ensure that the entry leg is of sufficient length to provide a clear view of the entire traffic pattern and to allow adequate time for planning the intended path in the pattern and the landing approach. Banking from time to time can uncover blind spots. A mid-air collision is most likely to occur between two aircraft going in the same direction.

Flight

Event TypeAccident
Event Time19:18 CDT
Nearest AirportSan Marcos Regional Airport (1nm W)
Runway08
Runway Length6330 ft
Runway Width100 ft
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftCessna 172S
Tail NumberN108VK
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · I0360 SER A&C · Reciprocating · 200 | Lycoming · IO-540-C4B5 · Reciprocating · 250
Seats4

People & Injuries

Injury Summary3 injuries (1 serious injury, 2 minor injuries)
Fatal0
Serious1
Minor2
Uninjured0
Total3
Crew 1Age 29 · First Class · Minor
Crew 2Unknown · Serious
Crew 3Age 56 · Third Class · Minor

Conditions

ConditionsVMC
LightDusk
Wind70° @ 7 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point64 F
Altimeter29.92 inHg
Observation Time18:56
Weather SourceWFAC

Appendix: Source Data