NTSB CAROL · Event
Event DFW05LA175
Aircraft involved
Probable cause & findings
The other pilot's failure to maintain clearance while taxiing. Contributing factors were the other pilot's diverted attention and the inaccurate frequency listing for ground control.
Factual narrative
On June 24, 2005, approximately 1150 central daylight time (CDT), a vintage North American T-28B single-engine airplane, N9060F, was substantially damaged upon collision with another airplane while holding short on taxiway Delta at Dyess Air Force Base (DYS), near Abilene, Texas. The commercial pilot and passenger were not injured. The airplane was registered to and operated by Trojan Phlyers II Inc, of Fort Worth, Texas. Visual meteorological conditions prevailed and a flight plan was not filed for the 14 Code of Federal Regulations Part 91 personal flight. The cross-country flight originated from Hicks Airfield (T67), near Fort Worth, Texas, at 1110, and was destined for DYS. In a written statement, the 27,996-hour pilot of a vintage tail-wheel equipped Canadian Car & Foundry Harvard MK IV single-engine airplane, N15797, reported that after performing a formation 360-degree overhead approach as a flight of two, the control tower told the lead airplane to execute a go-around. N15797 was then cleared to land. During the landing roll on the active runway, the tower informed N15797 to exit on the next available taxiway, and then contact ground control. After exiting the active runway onto taxiway Delta, the pilot switched to 119.35 megahertz (MHz), the ground control frequency depicted on his Jeppesen IFR Flight Star printout and Global Positioning System (GPS). After calling on this frequency, the pilot was notified that the correct ground control frequency was 118.35 MHz. While taxiing on taxiway Delta, the pilot switched to the correct frequency. While taxiing the pilot stated that he heard the sound of an Emergency Locator Transmitter (ELT) beacon, and thinking that the signal was emitting from his airplane, he attempted to reset the ELT while he continued to taxi. While taxiing straight ahead the pilot of N15797 allowed his airplane to collide with N9060F, which was holding short of taxiway Alpha on taxiway Delta awaiting further taxiing instructions. Examination of the T-28B by an Federal Aviation Administration (FAA) inspector revealed that the left horizontal stabilizer and elevator were separated from the fuselage. Examination of the Harvard MK IV revealed that the propeller and engine cowling were damaged. **This report was modified on April 8, 2008.** The 25,500-hour pilot was holding short of taxiway Alpha on taxiway Delta awaiting further taxi instructions when another airplane collided into the rear of his airplane. The 27,996-hour pilot of the other airplane stated that after exiting the active runway onto taxiway Delta, he switched to 119.35 megahertz (MHz), the ground control frequency depicted on his Jeppesen IFR Flight Star printout and Global Positioning System (GPS). After calling on this frequency, the pilot was notified that the correct ground control frequency was 118.35 MHz. After switching frequencies, the pilot heard an Emergency Locator Transmitter (ELT) beacon, and thinking that the signal was emitting from his airplane, the pilot attempted to reset the ELT while he continued to taxi straight ahead. Subsequently, his airplane struck the other airplane that was holding short on taxiway Delta. **This report was modified on April 10, 2008.** Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2005_DFW05LA175.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (go-around). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- NASA NTRS 2025 · Conference Paper
A Training Study to Improve Monitoring During A Go-Around
As part of an FAA program to improve go-around (GA) safety, we were asked to determine if we could improve the performance of the Pilot Monitoring (PM) during a GA maneuver.
- Flight Safety Foundation 2024 · FSF / AeroSafety World
Go-Around Safety Forum Findings
Foundation Go-Around Safety Forum technical findings — examines why pilots fail to execute go-arounds when criteria are met (stabilized approach gate not met, energy state out of envelope, traffic con…
- Semantic Scholar 2022 · Article (Journal of Safety Research)
Go-around accidents and general aviation safety.
INTRODUCTION Changes in General Aviation (GA) accident rates, specifically in the go-around phase, are examined by comparing the number of accidents, the proportion of fatal accidents, and the proport…
- Semantic Scholar 2021 · Article (Aerospace)
Classification and Analysis of Go-Arounds in Commercial Aviation Using ADS-B Data
Go-arounds are a necessary aspect of commercial aviation and are conducted after a landing attempt has been aborted. It is necessary to conduct go-arounds in the safest possible manner, as go-arounds …
- NASA NTRS 2021 · Accepted Manuscript (Version with final changes)
Go-Around Criteria Refinement for Transport Category Aircraft
Presently, airline pilots are trained to go around if, when lower than 500 ft above the ground, they are outside of a handful of parameters such as airspeed, position, and rate of descent.
- NASA NTRS 2019 · Conference Paper
Validation of Proposed Go-Around Criteria Under Various Environmental Conditions
This paper evaluates the effects of environmental conditions on touchdown performance under varying approach states and validates proposed go-around criteria developed using data from a previously con…
Browse the full corpus — academia portal ↗