# NTSB DFW07LA082: Cessna T210R, N766DP, Boerne, TX, March 8, 2007 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: March 8, 2007, 11:30 local (17:30 UTC) - Place: Boerne, TX - Coordinates: 29.729722, -98.695274 - Nearby events: https://openairdocs.org/map.md?lat=29.7297&lon=-98.6953&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Highest injury: No injuries - Injuries: 3 uninjured - Status: Completed, report May 29, 2007 - Report: Approved by Office Director - Parties: Flight Standards District Office - NTSB case key (mKey): 65397 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=DFW07LA082 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/65397/pdf - Page: https://openairdocs.org/ntsb/DFW07LA082 ## Probable cause (aircraft 2) The pilot of the other airplane's failure to maintain proper spacing during approach to landing and subsequent go-around, which resulted in a midair collision. ## Probable cause (aircraft 1) The pilot's failure to maintain proper spacing during approach to landing and subsequent go-around, which resulted in a midair collision. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Midair collision, go-around (vfr) - traffic pattern procedure - improper (cause) - clearance - not maintained, pilot in command (cause) - Midair collision, go-around (vfr) - clearance - not maintained, pilot of other aircraft (cause) - traffic pattern procedure - improper (cause) ## Analysis (aircraft 2) While executing a go-around at an uncontrolled airport, a Cessna T210R airplane collided with a Cessna 172K airplane that was performing a touch and go landing to the same runway. The 9,100-hour pilot of the 172K reported that while preparing for takeoff on the touch and go he heard the T210R announce that he was going around. The 172K pilot then advised the T210R pilot again that he was performing a touch and go. While climbing out at approximately 50 feet above the runway the 172K pilot felt what he thought was a large bird strike. The 1,440-hour pilot of the T210R reported that, on short final, he realized he was going to overtake the 172K that had landed on the runway, and initiated a go-around at the approach end of the runway. Upon announcing his go-around on UNICOM he subsequently heard the 172K pilot state "touch and go" on the same frequency. At the same instant, the T210R pilot saw the 172K rise from below and fill up his windshield. He attempted an evasive maneuver to avoid a collision but contacted the tail section of the 172K. A witness on the ground confirmed these events, stating that the T210R rapidly gained speed on the 172K and climbed into him. The T210R impacted the 172K from the rear while climbing. The Cessna 172K sustained structural damage, while the damage to the T210R was limited to the propeller blades. None of the occupants on either aircraft was injured. The visibility at the time of the collision was reported as 10 statute miles. ## Analysis (aircraft 1) While executing a go-around at an uncontrolled airport, a Cessna T210R airplane collided with a Cessna 172K airplane that was performing a touch and go landing to the same runway. The 9,100-hour pilot of the 172K reported that while preparing for takeoff on the touch and go he heard the T210R announce that he was going around. The 172K pilot then advised the T210R pilot again that he was performing a touch and go. While climbing out at approximately 50 feet above the runway the 172K pilot felt what he thought was a large bird strike. The 1,440-hour pilot of the T210R reported that, on short final, he realized he was going to overtake the 172K that had landed on the runway, and initiated a go-around at the approach end of the runway. Upon announcing his go-around on UNICOM he subsequently heard the 172K pilot state "touch and go" on the same frequency. At the same instant, the T210R pilot saw the 172K rise from below and fill up his windshield. He attempted an evasive maneuver to avoid a collision but contacted the tail section of the 172K. A witness on the ground confirmed these events, stating that the T210R rapidly gained speed on the 172K and climbed into him. The T210R impacted the 172K from the rear while climbing. The Cessna 172K sustained structural damage, while the damage to the T210R was limited to the propeller blades. None of the occupants on either aircraft was injured. The visibility at the time of the collision was reported as 10 statute miles. ## Factual narrative (aircraft 2) On March 8, 2007 at 1130 central standard time, a single-engine Cessna T210R airplane, N766DP, collided with a single-engine Cessna 172K airplane, N79286, while executing a go-around on runway 17 at the Boerne Stage Field Airport (5C1), near Boerne, Texas. The Cessna 172K sustained substantial damage to the left horizontal stabilizer, while the Cessna T210R reported minor damage to the propeller blades. Neither the pilot of the Cessna 172K, his passenger, nor the pilot of the Cessna T210R reported any injuries. Visual meteorological conditions prevailed and flight plans were not filed for the 14 Code of Federal Regulations Part 91 local flights. The 9,100-hour airline transport rated pilot of the Cessna 172K, N79286, stated in the Pilot/Operator Aircraft Accident Report (NTSB Form 6120.1) that upon turning downwind for runway 17 he announced on the UNICOM his intentions to perform a touch and go. He admitted that he observed the Cessna 210 on downwind to his right and perceived that the T210R "initiated a left turn to the west as though to depart the traffic pattern." The Cessna 172 pilot added that when on final approach, while approximately a quarter of a mile from the runway, he heard the pilot of the Cessna 210 call his position on final approach for runway 17. After touching down and preparing for takeoff on the touch and go, he heard the Cessna 210 pilot announced on the UNICOM that he was executing a go-around and subsequently "called on the radio to advise him again that I was doing a touch and go." While climbing away from the runway at approximately 50 feet above ground level he "heard what I thought was a large bird strike." After assessing the damage to the airplane, he executed another closed traffic pattern and landed without further incident. The 1,440-hour instrument rated private pilot of the Cessna T210R, N766DP, stated in the Pilot/Operator Aircraft Accident Report (NTSB Form 6120.1) that he announced his departure from runway 17 on UNICOM but heard no other radio calls on that frequency until "approximately one second before we collided." He further reports that he announced his turns to crosswind and downwind for runway 17. While midfield on the downwind leg, he noticed "a Cessna going west to east about 1.5 to 2 miles ahead of me" and figured the traffic was traversing the area and not planning to land. The pilot continued his right hand pattern turning to base and final while reporting each turn on UNICOM. Once on final approach the pilot saw the Cessna 172K on short final and "believed we had plenty of separation for him to land and exit the runway well before I landed." He reports that at this point he has heard no transmissions from the 172K on UNICOM. After the 172K landed the pilot states that "it became obvious that I was overtaking him too quickly to allow him to exit the runway before I landed" and initiated a go-around at the approach end of the runway. He announced his go-around on UNICOM stating he was "going around for the Cessna on the runway." As he was climbing out on the go-around he heard the 172K state "touch and go" and "almost instantaneously the C-172 rose from below and filled my windshield directly in front of me." The pilot reports making an evasive descending left turn to avoid the 172K, but "heard a brief 'clunk' as he passed above me." Following the collision, the Cessna T210R pilot contacted the Cessna 172K to confirm that he was alright and offered to check out his landing gear for damage. He stated that the "gear looked OK" and both aircraft continued around the pattern to land. Each airplane landed without further incident and taxied to parking. At a later time while on the ground, the pilots discussed the accident. As reported by the Cessna T210R pilot, the Cessna 172K pilot stated that "he had heard my radio calls on final, but 'thought you were way out'." The T210R pilot further recalls that the 172K pilot "indicated he had been making radio calls" but heard none of them until his touch and go call just before the collision. A witness on the ground at the airport reported that he first saw the Cessna 172 about mid field initiating a climb out and then seconds afterwards saw a second airplane, the Cessna 210, at a lower altitude also initiating a climb out. The witness stated that the T210R was rapidly gaining speed on the 172K and climbed right into the 172K. He continued to observe both airplanes, unsure of whether they had collided, until each made a successful landing at the airport. The Boerne Stage Field Airport lies within Class G (uncontrolled) airspace, does not have an operational control tower, and the UNICOM frequency is not monitored or recorded. Weather reported 30 minutes prior to the mishap from San Antonio Airport (KSAT), approximately 16 miles to the southeast was: Few clouds at 3,500 feet, scattered clouds at 25,000 feet, visibility 10 statute miles, wind from 200 degrees at 8 knots, temperature 21 degrees Celsius, dew point of 12 degrees Celsius, with an altimeter setting of 30.16 inches of Mercury. ## Factual narrative (aircraft 1) On March 8, 2007 at 1130 central standard time, a single-engine Cessna T210R airplane, N766DP, collided with a single-engine Cessna 172K airplane, N79286, while executing a go-around on runway 17 at the Boerne Stage Field Airport (5C1), near Boerne, Texas. The Cessna 172K sustained substantial damage to the left horizontal stabilizer, while the Cessna T210R reported minor damage to the propeller blades. Neither the pilot of the Cessna 172K, his passenger, nor the pilot of the Cessna T210R reported any injuries. Visual meteorological conditions prevailed and flight plans were not filed for the 14 Code of Federal Regulations Part 91 local flights. The 9,100-hour airline transport rated pilot of the Cessna 172K, N79286, stated in the Pilot/Operator Aircraft Accident Report (NTSB Form 6120.1) that upon turning downwind for runway 17 he announced on the UNICOM his intentions to perform a touch and go. He stated that he observed the Cessna 210 on downwind to his right and perceived that the T210R "initiated a left turn to the west as though to depart the traffic pattern." The Cessna 172 pilot added that when on final approach, while approximately a quarter of a mile from the runway, he heard the pilot of the Cessna 210 call his position on final approach for runway 17. After touching down and preparing for takeoff on the touch and go, he heard the Cessna 210 pilot announced on the UNICOM that he was executing a go-around and subsequently "called on the radio to advise him again that I was doing a touch and go." While climbing away from the runway at approximately 50 feet above ground level he "heard what I thought was a large bird strike." After assessing the damage to the airplane, he executed another closed traffic pattern and landed without further incident. The 1,440-hour instrument rated private pilot of the Cessna T210R, N766DP, stated in the Pilot/Operator Aircraft Accident Report (NTSB Form 6120.1) that he announced his departure from runway 17 on UNICOM but heard no other radio calls on that frequency until "approximately one second before we collided." He further reports that he announced his turns to crosswind and downwind for runway 17. While midfield on the downwind leg, he noticed "a Cessna going west to east about 1.5 to 2 miles ahead of me" and figured the traffic was traversing the area and not planning to land. The pilot continued his right hand pattern turning to base and final while reporting each turn on UNICOM. Once on final approach the pilot saw the Cessna 172K on short final and "believed we had plenty of separation for him to land and exit the runway well before I landed." He reports that at this point he has heard no transmissions from the 172K on UNICOM. After the 172K landed the pilot states that "it became obvious that I was overtaking him too quickly to allow him to exit the runway before I landed" and initiated a go-around at the approach end of the runway. He announced his go-around on UNICOM stating he was "going around for the Cessna on the runway." As he was climbing out on the go-around he heard the 172K state "touch and go" and "almost instantaneously the C-172 rose from below and filled my windshield directly in front of me." The pilot reports making an evasive descending left turn to avoid the 172K, but "heard a brief 'clunk' as he passed above me." Following the collision, the Cessna T210R pilot contacted the Cessna 172K to confirm that he was alright and offered to check out his landing gear for damage. He stated that the "gear looked OK" and both aircraft continued around the pattern to land. Each airplane landed without further incident and taxied to parking. At a later time while on the ground, the pilots discussed the accident. As reported by the Cessna T210R pilot, the Cessna 172K pilot stated that "he had heard my radio calls on final, but 'thought you were way out'." The T210R pilot further recalls that the 172K pilot "indicated he had been making radio calls" but heard none of them until his touch and go call just before the collision. A witness on the ground at the airport reported that he first saw the Cessna 172 about mid field initiating a climb out and then seconds afterwards saw a second airplane, the Cessna 210, at a lower altitude also initiating a climb out. The witness stated that the T210R was rapidly gaining speed on the 172K and climbed right into the 172K. He continued to observe both airplanes, unsure of whether they had collided, until each made a successful landing at the airport. The Boerne Stage Field Airport lies within Class G (uncontrolled) airspace, does not have an operational control tower, and the UNICOM frequency is not monitored or recorded. Weather reported 30 minutes prior to the mishap from San Antonio Airport (KSAT), approximately 16 miles to the southeast was: Few clouds at 3,500 feet, scattered clouds at 25,000 feet, visibility 10 statute miles, wind from 200 degrees at 8 knots, temperature 21 degrees Celsius, dew point of 12 degrees Celsius, with an altimeter setting of 30.16 inches of Mercury. ## Aircraft 1 - Registration: [N766DP](https://openairdocs.org/deregistered/N766DP-2007-10-25), registration cancelled 2007-10-25, S/N 21064969, built 1986 (OpenAirDocs) - Reported make and model: Cessna T210R - Registry model: [Cessna T210R](https://openairdocs.org/model/cessna-t210r) (registry code 2073459) (OpenAirDocs) - Registry engine: [Continental TSIO-520 series](https://openairdocs.org/engine/continental-tsio-520-series) (registry code 17040, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 21064969 - Airframe hours: 2113 - Engines: Continental TSIO 520CE 325 horsepower reciprocating - Damage: Minor damage - Flight: Personal, Part 91 - Operator: Robert K. Daniel Peterson, doing business as Personal - Registered owner: Viking Aviation LTD - Airworthiness certificate: Standard, Normal - Last inspection: Annual, May 1, 2006 - Departed: 5C1, Boerne, TX - Destination: 5C1, Boerne, TX - Airport: 5C1, Boerne Stage Field, runway 17, 4,300 × 50 ft, asphalt ## Aircraft 2 - Registration: [N79286](https://openairdocs.org/aircraft/N79286), registered now, S/N 17258023 (OpenAirDocs) - Reported make and model: Cessna 172K - Registry model: [Cessna 172K](https://openairdocs.org/model/cessna-172k) (registry code 2072430) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 17258023 - Engines: Lycoming O-320 180 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Registered owner: Alamo Aerodyne, Inc - Airworthiness certificate: Standard, Normal - Departed: 5C1, Boerne, TX - Destination: 5C1, Boerne, TX - Airport: 5C1, Boerne Stage Field, runway 17, 4,300 × 60 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot, aircraft N766DP; age 63; injuries: none; private; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 3, with waivers/limitations; last flight review March 1, 2007; seat: left; flight hours: 1,440 total, 340 in this make and model, 1,350 as pilot in command, 16 in the last 90 days, 7 in the last 30 days - Pilot, aircraft N79286; age 47; injuries: none; recreational, commercial, airline transport, flight instructor, flight engineer; airplane ratings: single-engine sea, single-engine land, multi-engine land; instrument ratings: airplane; medical: class 1, with waivers/limitations; last flight review September 1, 2006; seat: left; flight hours: 9,100 total, 1,750 in this make and model, 8,600 as pilot in command, 14 in the last 90 days, 8 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Wind: 200° at 8 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 70 °F, dew point 54 °F - Altimeter: 30.17 inHg - Observed at: KSAT, 16 nm away ## FAA reports on this event (2) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20070308004151A](https://openairdocs.org/incident/20070308004151A), Mar 8, 2007: Cessna T210R, San Antonio, TX, Minor damage. (-23) Cessna N79286 was doing a touch and go landing on runway 17 at Boerne Stage airport. Cessna N766DP was on final approach to runway 17, behind N79286. The… - [Accident 20070308004152A](https://openairdocs.org/incident/20070308004152A), Mar 8, 2007: Cessna 172K, San Antonio, TX, Substantial damage. (-23) After completing a touch and go on runway 17 at Boerne Stage airport, the pilot of Cessna 172, N79286, took off and started his initial climb. At… From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.