Cessna 172 and Aero Commander 500 accident near Atlanta, Georgia, November 25, 2020
On November 25, 2020 at about 5:09 am local time, 2 aircraft, Cessna 172 (N8125U) and Aero Commander 500 (N777CM), were involved in the same accident near Atlanta, Georgia (Dekalb-Peachtree Airport). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
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.
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.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- November 25, 2020 · about 5:09 am local time · cases in 2020
- Place
- Atlanta, Georgia · Dekalb-Peachtree Airport · cases near this airport · map
- Type
- Accident · collision on the ground
- Injuries
- No one was hurt; 2 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft 1
- Cessna 172 F, built 1964 · all 172s on the register
- Registration
- N8125U · registry record · serial 17252025
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
- Aircraft 2
- Aero Commander 500 B, built 1964 · all 500s on the register
- Registration
- N777CM · registry record · serial 1412-147
- Damage
- Minor damage
- Flight
- Business flight · charter and air-taxi rules (Part 135)
The NTSB's narrative for the Cessna 172 final · quoted from the NTSB record
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.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The NTSB's narrative for the Aero Commander 500 final · quoted from the NTSB record
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.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record for the Cessna 172 from the NTSB's investigation tables, in plain English
What happened, in order
- Collision during takeoff/land during landing (landing roll) defining event
The NTSB's findings
- Personnel issues › Action/decision › Action › Forgotten action/omission › Pilot
- Personnel issues › Experience/knowledge › Knowledge › Aeronautical knowledge › Pilot
- Environmental issues › Operating environment › Communication system › VHF/HF radio › Compliance w/ procedure
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 580 hours in all
- Medical certificate: BasicMed
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 6,021 hours
- Last inspection: annual inspection, June 1, 2020; 15 hours since
- Maximum gross weight: 2,300 lb
- Seats: 4
- Landing gear: fixed
- Engine: Continental Motors O-300D (piston); 0 hours total
The flight
- Departed from: SAV Savannah GA at 3:00 am
- Flight plan: none
- Runway 21L, 6,001 ft by 100 ft
Weather at the time
- Light: night
- Wind: from 090° at 5 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 46°F (8°C), dew point 36°F (2°C)
- Altimeter: 30.26 inHg
- Observation at 11:53 pm from PDK
Weather report (METAR): KPDK 250453Z AUTO 09005KT 10SM CLR 08/02 A3026 RMK AO2 SLP252 T00830022 401440017
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
The factual record for the Aero Commander 500 from the NTSB's investigation tables, in plain English
What happened, in order
- Collision during takeoff/land during landing (landing roll)
The NTSB's findings
- Personnel issues › Action/decision › Action › Forgotten action/omission › Pilot of other aircraft
- Personnel issues › Experience/knowledge › Knowledge › Aeronautical knowledge › Pilot of other aircraft
- Environmental issues › Operating environment › Communication system › VHF/HF radio › Compliance w/ procedure
Pilot
- Certificate: airline transport pilot
- Ratings: multi-engine land; single-engine land; instrument: airplane
- Flight time: 11,500 hours in all; 3,500 in this make and model; 150 in the last 90 days; 50 in the last 30 days
- Last flight review: June 30, 2020
- Medical certificate: Class 2 (with waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 24,520 hours
- Last inspection: approved inspection programme, September 18, 2020
- Maximum gross weight: 6,750 lb
- Seats: 2
- Landing gear: retractable
- Engine 1: Lycoming IO-540-E1A5 (piston); 28,899 hours total
- Engine 2: Lycoming IO-540-E1A5 (piston); 18,877 hours total
- Operator: Central Air Southwest
The flight
- Departed from: BHM Birmingham AL at 6:00 am
- Flight plan: IFR
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Photographs from the investigation 4 pictures from the NTSB's docket, as the NTSB released them
N8125U Right Wing Tip
N8125U Right Wing Tip – Outboard Rib
N777CM – Underside of Right Wing
N777CM – Underside of Right Flap and Aileron (view from rear)The NTSB's photographs with the NTSB's captions, at screen size. Open a picture to see it full size or to report one that should not be shown.
Documents from the investigation the NTSB's docket: the evidence folder behind the report
12 documents, released by the NTSB on September 28, 2022. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 - N777CM | PDF, 10 pages | View Download |
| 2 | Memorandum for Record - Information Provided by Cessna (N8125U) Pilot | PDF, 12 pages | View Download |
| 3 | Memorandum for Record - Information from FAA Inspector | PDF, 1 page | View Download |
| 4 | Airport (Pdk) Security Officer Report | PDF, 1 page | View Download |
| 5 | FAA Air Traffic Control Audio/tracking Data Playback Video | video | View Download |
| 6 | ADS-B Track Data- Plot | PDF, 1 page | View Download |
| 7 | ADS-B Track Data - Tabular - N777CM | data file | Download |
| 8 | ADS-B Track Data - Tabular - N8125U | data file | Download |
| 9 | Airport Diagram | PDF, 1 page | View Download |
| 10 | Description of Approach Lighting System - Runway 21L at Pdk | PDF, 2 pages | View Download |
| 11 | Investigative Photographs | PDF, 4 pages · our copy | View Download |
| 12 | Security Video Recording | AVI file | Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Connections how this case links to the rest of the register
- N8125U on the register today · the tail number may have moved to another aircraft since
- Cessna 172 Skyhawk 20,693 registered today · the model family and its accident history
- Cessna 72,678 aircraft on the register
- N777CM on the register today · the tail number may have moved to another aircraft since
- Aero Commander 500 163 registered today · the model family and its accident history
- Aero Commander 709 aircraft on the register
- Engine: Continental Motors O-300D 31 aircraft carry this series today · as the NTSB recorded it
- Engine: Lycoming IO-540-E1A5 4 aircraft carry this series today · as the NTSB recorded it
- Dekalb-Peachtree Airport · nearest airport
- Savannah/Hilton Head International · departed from
- Birmingham-Shuttlesworth International · departed from
- Accidents and incidents in Georgia 2,138 since 1982 · 361 in the last ten years
- Georgia 8,800 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/ERA21LA056.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
