Beech Bonanza / Diamond DA20 Midair Collision

A private pilot and a flight instructor with her student collided on final approach at a non-towered Georgia airport September 7, 2016, 10:48 EDT · Final approach, runway 35, West Georgia Regional Airport (CTJ), Carrollton, Georgia
Accident
Mid-air collision
3 fatal / 3 aboard
No survivors, both aircraft
Investigation status
Final report published
NTSB · Final report published December 11, 2017

Case summary

The Bonanza pilot's radio was still tuned to a CTAF frequency the airport had retired five years earlier — he never heard the Diamond's calls.

A Beechcraft F33A Bonanza, the same model as the accident airplane, photographed on the ground — not the accident aircraft
Beechcraft F33A Bonanza
Private pilot, personal flight
Representative photo of a Beechcraft F33A Bonanza, the model involved — not the accident aircraft
Key facts
Aircraft
Beechcraft F33A Bonanza (A1) & Diamond DA20-C1 (A2)
Registration
N6027K (A1) · N85WP (A2)
Location
Carrollton, GeorgiaWest Georgia Regional Airport (CTJ)
Flights
Beech: Fulton County Airport (FTY) → CTJ · Diamond: Newnan Coweta County (CCO) → CTJ, local pattern workBoth inbound to CTJ's non-towered traffic pattern for runway 35
Phase of flight
Final approach, VFR traffic patternMid-air collision (defining event)
Operation
A1: Part 91 personal · A2: Part 91 instructional (dual)
Occupants
3
Fatalities
3
Serious injuries
0
Minor injuries
0
Damage
Beech: substantial · Diamond: destroyed
Weather
VMC, clear10 sm visibility, scattered clouds 8,500 ft, calm wind

What happened

Source: NTSB Final Report (excerpt)

The Diamond flight instructor and student pilot were in the traffic pattern at the non-towered airport practicing landings. The Beech pilot entered the traffic pattern on an extended left downwind leg with the intention of landing. Pilots of other airplanes in the pattern reported that the Diamond instructor was making standard traffic pattern callouts on the common traffic advisory frequency (CTAF); however, the Beech pilot was not transmitting on the CTAF. Witness observations, radar data, GPS data, and examination of the wreckage of the two airplanes revealed that, while both airplanes were on final approach for landing, the Beech overtook the Diamond from above and behind. The landing gear of the Beech struck the horizontal stabilizer and elevator of the Diamond, and then both airplanes abruptly descended into the terrain short of the runway. Testing of the Beech's VHF communications radio revealed that it was set to an old CTAF frequency for the airport that had been changed about 5 years before the accident — a local airport frequency card dated 7 years before the accident, found in the Beech's cockpit, still listed that old frequency.

Why it happened

Source: NTSB Final Report
NTSB probable causeNTSB

"The failure of the Beech pilot to see and avoid the Diamond that was in front of and below his airplane on final approach and his use of an incorrect radio communication frequency for the airport."

Contributing factors
  • Beech pilot's VHF radio was tuned to an outdated CTAF frequency (122.7 MHz) that the airport had retired about 5 years before the accident
  • A laminated local-area frequency card in the Beech's cockpit, dated 2009, still listed the obsolete CTAF frequency
  • Beech pilot was not transmitting or apparently monitoring the correct CTAF (122.975 MHz), so other pattern traffic never heard his position
  • Failure of the Beech pilot to see and avoid the Diamond, which was ahead of and below him on the same final approach course
  • Closing speed: the Beech was overtaking the slower Diamond by roughly 50 knots on the downwind and final legs
  • Non-towered airport with no ATC separation service — CTAF communication and visual scanning were the only safety barriers in the pattern
Safety takeaways
Verify your CTAF before flying into an unfamiliar or infrequently visited non-towered airport — frequencies do change, and a years-old card or a number from memory can be wrong with no indication of that in the cockpit.
Hearing other aircraft make position calls is not the same as being heard yourself — if you can't confirm two-way communication is actually happening on the correct frequency, don't assume it is.
At a non-towered airport, see-and-avoid is the only separation that exists. Overtaking another airplane on the same final approach course removes your own forward visual reference to it at the worst possible moment.
A faster airplane entering the pattern behind a slower one on the same leg is a closure-rate problem, not just a sequencing one — match your speed to the traffic ahead or extend the pattern, rather than assuming it will sort itself out on short final.
Flight instructors training in the pattern should expect, not assume, that every other aircraft is communicating correctly on CTAF — keep scanning visually even while you're making textbook-correct calls yourself.
Aircraft
Beechcraft F33A Bonanza (A1) & Diamond DA20-C1 (A2)
Registration
N6027K (A1) · N85WP (A2)
Location
Carrollton, GeorgiaWest Georgia Regional Airport (CTJ)
Flights
Beech: Fulton County Airport (FTY) → CTJ · Diamond: Newnan Coweta County (CCO) → CTJ, local pattern workBoth inbound to CTJ's non-towered traffic pattern for runway 35
Phase of flight
Final approach, VFR traffic patternMid-air collision (defining event)
Operation
A1: Part 91 personal · A2: Part 91 instructional (dual)
Occupants
3
Fatalities
3
Serious injuries
0
Minor injuries
0
Damage
Beech: substantial · Diamond: destroyed
Weather
VMC, clear10 sm visibility, scattered clouds 8,500 ft, calm wind
Verify your CTAF before flying into an unfamiliar or infrequently visited non-towered airport — frequencies do change, and a years-old card or a number from memory can be wrong with no indication of that in the cockpit.
Hearing other aircraft make position calls is not the same as being heard yourself — if you can't confirm two-way communication is actually happening on the correct frequency, don't assume it is.
At a non-towered airport, see-and-avoid is the only separation that exists. Overtaking another airplane on the same final approach course removes your own forward visual reference to it at the worst possible moment.
A faster airplane entering the pattern behind a slower one on the same leg is a closure-rate problem, not just a sequencing one — match your speed to the traffic ahead or extend the pattern, rather than assuming it will sort itself out on short final.
Flight instructors training in the pattern should expect, not assume, that every other aircraft is communicating correctly on CTAF — keep scanning visually even while you're making textbook-correct calls yourself.
← Back to search results