Find KATL runway details, ILS localiser frequencies and Atlanta ATC channels, with chart checks and simulator troubleshooting.
Hartsfield-Jackson Atlanta International Airport (KATL) has five parallel runways: 08L/26R, 08R/26L, 09L/27R, 09R/27L and 10/28. Each end has a published ILS/localiser frequency. ATC uses separate ATIS, clearance, ground, tower, approach and departure frequencies; use the channel assigned on the latest chart or by ATC.
For Aviation & Real-World Flying, treat the figures below as planning references. Frequencies and operational assignments can change, so check the KATL airport diagram and approach plates before a real flight.
What runways and ILS frequencies does KATL use?
KATL has five concrete runways, all 150 feet wide, with an ILS or localiser published for both approach directions. The differing 08, 09 and 10 designators allow several closely parallel runways to have unambiguous names; our explanation of how parallel runway numbers are assigned covers that convention.
| Runway | Length | ILS for eastbound end | ILS for westbound end |
|---|---|---|---|
| 08L/26R | 9,000 ft | 08L — 111.10 MHz | 26R — 109.90 MHz |
| 08R/26L | 9,999 ft | 08R — 109.50 MHz | 26L — 110.50 MHz |
| 09L/27R | 12,390 ft | 09L — 110.10 MHz | 27R — 111.30 MHz |
| 09R/27L | 9,000 ft | 09R — 109.30 MHz | 27L — 108.90 MHz |
| 10/28 | 9,000 ft | 10 — 111.75 MHz | 28 — 108.95 MHz |
These are localiser frequencies within the standard ILS localiser frequency band. Pilots do not tune a separate glideslope frequency: the aircraft’s receiver pairs it automatically with the selected localiser channel.
Which ATC frequency should I use at Atlanta?
Start with the appropriate ATIS frequency, then use the clearance, ground, tower, approach or departure frequency assigned for your runway and sector. KATL divides traffic among several positions, and one controller may combine multiple positions during quieter periods.
| ATC service | Published VHF frequencies |
|---|---|
| Arrival ATIS | 119.650 MHz |
| Departure ATIS | 125.550 MHz |
| Clearance delivery | 118.100 MHz |
| Ground | 121.650, 121.750, 121.900 MHz |
| Tower | 119.100, 119.300, 119.500, 123.850, 125.325 MHz |
| Approach | 118.350, 119.800, 125.700, 126.900, 127.900, 128.000 MHz |
| Departure | 125.000, 125.650, 125.700, 126.900 MHz |
Do not choose a tower, ground or radar frequency merely because it appears in this table. Listen to ATIS and follow the charted or spoken hand-off. The approach and departure entries are airport-listed contact frequencies, not a complete map of every Atlanta TRACON sector.
How do I tune a KATL ILS in a flight simulator?
Tune the frequency belonging to the exact landing runway end, set the published inbound course and make sure the flight instruments are using the navigation receiver rather than GPS guidance.
- Confirm the runway: distinguish carefully between 08L and 08R, or 27L and 27R. A mistake we see constantly is selecting the frequency for the opposite end of the same strip.
- Tune the localiser: enter the listed frequency in
NAV1, or verify that the flight-management system has auto-tuned the same value. - Set the front course: use the final approach course printed on the applicable approach plate, not an estimated runway heading.
- Check the navigation source: select the appropriate NAV or ILS source on the primary flight display and identify the localiser where the aircraft supports identifier audio or text.
- Arm approach mode at the correct point: intercept the localiser from the published or ATC-assigned heading and avoid trying to capture it from behind the antenna.
Why does a KATL ILS or ATC frequency not work in the simulator?
A mismatch usually means the simulator’s navigation database, airport scenery and ATC database come from different update cycles.
- Old navigation data: the chart may show a newer frequency than the simulator database. Update the supported navdata or use the simulator’s own published value for an offline flight.
- Wrong runway end: 09L and 27R share pavement but use different localiser transmitters and frequencies.
- Conflicting airport scenery: duplicate KATL packages or an older AFCAD can produce misplaced runways, incorrect parking assignments or inconsistent approach data. Leave only one airport-layout package active while testing.
- Incorrect cockpit source: a correctly tuned receiver will not drive the display if the CDI remains set to GPS/FMS rather than NAV/LOC.
- Combined simulator ATC positions: built-in ATC and online controllers may consolidate Atlanta tower or radar sectors, so the assigned frequency need not match the runway-specific position a full real-world staffing plan would use.