CESSNA 172 near Atlanta, GA — 2020-11-25
- Date
- 2020-11-25
- Location
- Atlanta, GA, USA
- Airport
- PDK
- Aircraft
- CESSNA 172
- Registration
- N8125U
- Category
- Airplane
- Highest injury
- None
- Fatalities
- 0
- Phase of flight
- Approach
Probable cause
The Cessna pilot’s failure to tune his radio to the common traffic advisory frequency, which resulted in a lack of awareness of the other aircraft operating at the airport. Contributing to the accident was the Cessna pilot’s lack of understanding of the airport lighting system.
NTSB narrative
The private pilot of the Cessna was landing while the airline transport pilot of the Aero Commander was landing on the opposite runway during night visual meteorological conditions, after the airport control tower had closed. The Cessna pilot activated the runway approach lighting system and mistakenly believed that the green threshold lights indicated the direction for landing on the active runway. The pilot-controlled lighting system used a separate radio frequency from the common traffic advisory frequency (CTAF) at this airport. The Cessna pilot stated that he then “switched radio channels” and made “routine calls.” The Aero Commander pilot made radio announcements on the CTAF during each leg of the traffic pattern, announcing his location and intentions. Contrary to the Cessna pilot’s belief that the green lights he observed indicated the active runway (and the one on which he intended to land), they denoted the location of the (displaced) runway threshold of the adjacent runway. During landing rollout, the right-wing tip of the Cessna contacted the underside of the right wing of the Aero Commander, which had landed on the opposite runway, resulting in substantial damage to the Cessna’s right wing. The Cessna pilot reported that he did not hear any radio transmission from other aircraft operating at the time, and the pilot of the Aero Commander did not hear any radio transmissions from the Cessna pilot. Audio recordings of the CTAF frequency captured the radio transmissions made by the Aero Commander pilot (and other traffic) but did not capture any transmissions from the Cessna pilot. It is therefore likely that the Cessna pilot kept his single communications radio tuned to the pilot-controlled lighting frequency rather than change it to the CTAF as indicated in the airport/facility directory, which resulted in his communications not being heard by other pilots in the vicinity and his lack of awareness of the Aero Commander pilot’s position.
Analysis
- Primary failure mode
- Human factors
- First missed decision gate
- Cessna pilot could have confirmed active runway before landing.
NTSB coding
Evidence available
- ATC audio
- Video
- ADS-B / radar
- Photos
- 12 docket documents
Docket documents12
- MEMORANDUM FOR RECORD - INFORMATION FROM FAA INSPECTORform
- MEMORANDUM FOR RECORD - INFORMATION PROVIDED BY CESSNA (N8125U) PILOTform
- PILOT/OPERATOR AIRCRAFT ACCIDENT REPORT, NTSB FORM 6120.1 - N777CMform
- AIRPORT DIAGRAMother
- DESCRIPTION OF APPROACH LIGHTING SYSTEM - RUNWAY 21L AT PDKother
- INVESTIGATIVE PHOTOGRAPHSphotos
- ADS-B TRACK DATA - TABULAR - N777CMradar
- ADS-B TRACK DATA - TABULAR - N8125Uradar
- ADS-B TRACK DATA- PLOTradar
- AIRPORT (PDK) SECURITY OFFICER REPORTreport
- FAA AIR TRAFFIC CONTROL AUDIO/TRACKING DATA PLAYBACK VIDEOvideo
- SECURITY VIDEO RECORDINGvideo
Related mishaps
- I.C.A.-BRASOV (ROMANIA) IS-28B2
2026-05-12 · Scotts Fork, VA
- CZECH SPORT AIRCRAFT AS PIPER SPORT
2026-04-24 · Crownpoint, NM
- PIPER PA-28-160
2026-04-22 · Lanett, AL
- MAULE M-7-235B
2026-01-17 · Cody, WY
- PIPER PA-18-150
2025-09-08 · Eagle, AK
- PIPER PA-18-150
2024-12-25 · Palmer, AK