Cessna 172S N108VK
25 September 2020 · San Marcos, Texas, United States · Serious injuries
Summary
On 25 September 2020 at about 00:18 local time, a Cessna 172S registered N108VK was involved in an accident near San Marcos, Texas, United States. 3 people were on board and one was seriously injured, 2 had minor injuries. The aircraft was substantially damaged. The NTSB has published a probable cause for this accident; it is quoted in full below.
The record
- Date
- at 00:18
- Classification
- Accident
- Location
- San Marcos, Texas, United States
- Nearest airport
- San Marcos Regional Airport (KHYI)
- Coordinates
- 29.8917, -97.8791
- Aircraft
- Cessna 172S
- Registration
- N108VK
- Category
- Airplane
- Year built
- 2001
- Engines
- 1
- Operator
- Not recorded
- Operating rule
- Part 91: General Aviation
- Purpose of flight
- Instructional
- Phase of flight
- Not recorded
- Route
- Lockhart → Unknown
- Aircraft damage
- Substantial
- Weather
- VMC
- Light
- Dusk
- NTSB number
- CEN20LA419
People
1 person was seriously injured.
| On board | Died | Serious | Minor | Uninjured |
|---|---|---|---|---|
| 3 | 0 | 1 | 2 | 0 |
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.
Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.
Read the full NTSB narrative
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.
Quoted verbatim from the NTSB record.
Aircraft involved
| Aircraft | Registration | Operator | Damage |
|---|---|---|---|
| Cessna 172S | N108VK | - | Substantial |
| Team Rockets F1 | N540LK | - | Destroyed |
Other Cessna 172 accidents
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 30 Sep 2020 | Cessna 172 | Higginsville, Missouri, United States | University of Central Missouri | No injuries | - |
| 6 Feb 2020 | Cessna 172 | Palmer, Alaska, United States | - | No injuries | - |
| 2 May 2020 | Cessna 172 | Fresno, California, United States | - | Minor injuries | - |
| 2 Aug 2020 | Cessna 172 | Conway, Arkansas, United States | Barrett Aviation | No injuries | - |
| 3 Oct 2020 | Cessna 172 | Hinckley, Minnesota, United States | - | No injuries | - |
| 31 Dec 2020 | Cessna 172R | Hope, Alaska, United States | Elmendorf Air Force Base Aero Club | Minor injuries | - |
All 12,209 records for this type
Other accidents in this area
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 24 Jun 2020 | Cessna 182 | Winfield, Texas, United States | Brentco Aerial Patrol | Serious injuries | - |
| 2 May 2020 | MD Helicopters 369 | Houston, Texas, United States | City Of Houston | Fatal | 1 |
| 28 Dec 2020 | Piper PA-30 | Navasota, Texas, United States | - | No injuries | - |
| 24 Jun 2020 | CubCrafters CC19-180 | Fredericksburg, Texas, United States | Kgnf, LLC | No injuries | - |
| 27 Jun 2020 | Piper PA32R | Zavalla, Texas, United States | - | Fatal | 1 |
| 6 Nov 2020 | Cirrus SR20 | Fort Worth, Texas, United States | Plane Smart! Aviation | No injuries | - |