Connecting to the network

ATL is one of the busiest airports in VATSIM, consistently ranking in the top 10 by both traffic volume and ATC coverage. When connecting your simulator at Atlanta, you should first determine where to spawn your aircraft. Take a look at the ramp status map below so you don't connect on top of another aircraft!

Live ATL gate status

Who should I talk to?

Controllers come and go on VATSIM and unlike the real-world, staffing in control positions is not consistent throughout the day. It can be complicated to figure out who you should talk to! Similar to real-world facilities, we use the “top-down” control method, where higher facilities controller lower ones when the lower facility is not staffed. Here are a couple of examples:

You are departing from ATL. Atlanta Clearance Delivery is not online, but Atlanta Approach is online. Approach is performing the duties of clearance delivery, ground, tower, and approach at ATL.

You are departing from ATL. Atlanta Tower and Atlanta Center are the only controllers logged in. You will talk to Atlanta Tower for clearance delivery, ground, and tower. You will talk to Atlanta Center for approach and enroute services.

Current ATC staffing at Atlanta:

If more than one ground controller is online at ATL, you should call GC-N/121.9 for taxi to runway 8R/26L or GC-C/121.75 for taxi to runway 9L/27R.

If more than 1 tower controller is online at ATL, you should call the controller on the frequency provided by ground.

Filing a flight plan

All IFR operations at ATL require a flight plan on-file. We highly recommend that all VFR operators file flight plans. If you cannot file a flight plan, a controller will assist you (workload depending).

IFR flight plans should file an appropriate RNAV standard departure procedure. For aircraft that are not RNAV-capable, file the ATL departure.

One common area of confusion for Atlanta involves filed altitudes for departures to destinations in Florida. Because of Florida's geographic north-south orientation, certain areas of airspace do not operate on traditional north-odd/south-even (NEODD/SWEVEN) rules. You may expect a change in altitude while en route flying along the eastern part of Florida. Additionally, because of ATL’s proximity to north Florida, there are some restrictions regarding final altitudes. Here are some common routes and acceptable altitudes.

Receiving a clearance

After filing a flight plan, you should receive your clearance from ATC. If you have not received a clearance after a reasonable amount of time, you should call OFFLINE on OFFLINE and request your clearance.

Example: Atlanta Clearance, Delta 1234 clearance to Charlotte ready to copy.

Aircraft with CPDLC capabilities should expect to receive a computerized pre-departure clearance from ATC. Because ATC sends this type of clearance directly to your aircraft, a read back is not necessary.

Aircraft without CPDLC should expect an abbreviated or full-route clearance from ATC. When calling for your clearance, be prepared to write it down. Some pilots write the letters C-R-A-F-T vertically on a sheet of paper to assist in copying a clearance as read by ATC. After issuing your clearance, ATC expects you to reply with at least your callsign and squawk code to confirm that you copied the information correctly. At your discretion you may readback your entire clearance to verify information was copied correctly. If you have questions about your route of flight, you should ask clearance delivery. Voice clearances may not include an altitude or departure frequency. In this case, use the information published on the appropriate departure procedure chart.

You should listen to ATIS at this time. The ATIS provides important information regarding weather and NOTAMs at the airfield. ATL publishes both an arrival ATIS and a departure ATIS – you should listen to the one applicable to your operation.

Take the time now to ensure that your FMS or GPS flight plan matches the clearance that ATC issued to you. Your departure runway is determined by the standard instrument departure (SID) that you were issued, your requirements for takeoff, and your parking location on the airfield. Here is a guide to determine your departure runway:

• ATL departs runways 8R/26L and 9L/27R. Do not expect other runways for departure.
• Runway 9L/27R is the longest runway at ATL at 12,390 feet. If your aircraft’s takeoff data indicates that you need this runway for departure, you should inform the ground controller on first contact.
• If parked at concourse T, A, B, C, D, E, F, your departure runway is dependent on your filed SID. See chart on the right side of this page.
• If you are departing from the GA ramp/Signature or the north cargo ramp, you should expect runway 8R/26L for departure.
• If you are departing from the South Cargo ramp, you should expect runway 9L/27R for departure.

Push & Start

ATL does not simulate ramp control. During non-event periods, push and start clearances are at your discretion and do not require ATC clearance. For major events (example: cross the pond) where you have been issued an estimated departure clearance time (EDCT), you may be required to call ground prior to push. Do not call ground for push/start unless the ATIS or your PDC advises you to do so.

Exception: If you must push onto an active taxiway, you are required to call OFFLINE on OFFLINE and request clearance to do so. Gate E36 is the only gate at ATL that may require push back onto an active taxiway for Boeing 757 and larger aircraft.

Make sure that you push the correct direction! If you are departing on runway 8R/26L, you want to face north. If you are departing on runway 9L/27R you should be facing south.

Refer to the Attention All Users Page (AAUP) for your expected runway based on your SID and push at the appropriate north or south end of the ramp. This resource is available on the 'taxi' tab of this guide. If your PDC tells you to call at the north or south end specifically, disregard the AAUP and expect the runway corresponding to that direction.

Taxi

Check ATIS one more time prior to calling for taxi to ensure that nothing has changed. Ensure that your transponder is on with the correct squawk code entered and in altitude mode. Taxi to the north or south hold point on the ramp and call OFFLINE on OFFLINE. Inform the controller of your ramp location (see airfield diagram) and provide them with the ATIS code.

*Note: If more than one ground controller is online at ATL, you should call GC-N/121.9 for taxi to runway 8R/26L or GC-C/121.75 for taxi to runway 9L/27R.

Example: Atlanta Ground, Delta 1234 ramp 1 south taxi with A.

The controller will respond with taxi instructions to a runway. You should have an airfield diagram available so you can follow the precise route given to the runway. If you are not assigned a runway intersection, you should taxi to the hold point at the end of the runway. If you are assigned an intersection, make sure that you hold at the intersection. Note: intersections that are within 500 feet of the end of the runway are considered full-length departures. Hold points are commonly used on runway 9L (M2) and 27R (LB, LC).

Taxiway D at Atlanta between G and L is a non-movement area and is not controlled by ATC. If you are taxiing to a runway and intend to use D, you should still call ATC prior to proceeding on any taxiway.

When taxiing to runway 26L, expect a clearance via F. Pilots should continue taxiing on E to the runway unless given specific instructions to hold short.

Aircraft may be instructed to hold midfield to reduce congestion at the end of the runway. Follow all hold short instructions

If you are instructed to contact the next controller, you should call them with your location. If you are instructed to monitor the next controller, tune your radio to the proper frequency and wait for ATC to call you. ATL has airport surface detection equipment (ASDE), so controllers can monitor the precise location of all aircraft on the ground at all times.

Takeoff & Climbout

As part of your takeoff clearance, the controller will state your initial RNAV waypoint or your departure heading. These items must be read back to the controller issuing your takeoff clearance. This step ensures that you will remain clear of traffic departing on parallel runways between takeoff and your initial contact with radar control. When you read back your first RNAV waypoint, verify that the first point in your FMS LEGS page matches the point provided by the controller. If the point does not match, tell the controller "UNABLE" and discuss the discrepancy with them. It may be necessary for a controller to verify a pilot's departure name, number and first waypoint.

Example: Delta 1234, Atlanta Tower RNAV to SLAWW runway 27R clear for takeoff.

Precisely follow the instructions given by tower to ensure that you remain clear of traffic departing on parallel runways. If you do not understand the instruction, just ask! Wait to switch to departure frequency until instructed to do so.

Turbojets should accelerate to 250 knots without delay.

Ensure that you do not exceed the initial altitude given in your clearance (10,000 feet). Contact departure control on the published frequency when instructed to "contact departure" unless provided another frequency. Atlanta Departure (a.k.a. Approach) will monitor your climb-out and provide you with a hand-off to Atlanta Center.

Arrival

Welcome to Atlanta – we’re glad that you decided to make us your destination today. Ensure that you monitor the arrival ATIS when you are inbound (no later than 60 miles from the airport). Atlanta Approach is responsible for assigning your arrival runway – Center will not be able to do this unless Center is also controlling the Approach position.

To check-in with Atlanta Approach, provide your callsign, current altitude and the altitude that you are descending to, your location on the arrival, your current indicated airspeed, and the current arrival ATIS code. For example: Atlanta Approach DAL69 FL180 descending 13,000 at CHPPR speed 250 with Yankee

On initial contact with Atlanta Approach, you will be assigned an arrival runway and an approach type. If you have a special request for a different runway or approach, you should state that request at this time. Aircraft parking at the GA ramp (Signature) and North Cargo should expect runway 8L/26R. Aircraft parking at the South Cargo ramp should expect runway 9R/27L. All other aircraft will be assigned runways based on traffic flow.

After you are established on an arrival and approach has issued a landing runway, check your FMS to ensure that you have the entire arrival and approach programmed correctly. RNAV arrivals and approaches should be continuous with no discontinuity.

At peak traffic periods, six or more controllers may be working positions in the Atlanta large terminal radar approach control facility (TRACON). It is important that you listen to the controller’s instructions during a hand-off to ensure that you contact the proper controller. If you switch to the wrong frequency, go back to your previous frequency and ask for clarification.

For planning purposes and to manage traffic flow, you should expect to fly 210 knots on downwind and once cleared for the approach no less than 180 knots until the final approach fix. ATC will provide specific instructions if other speeds are necessary.

On landing roll-out, taxi clear of the runway in the direction of your preferred parking location and hold short of the parallel taxiway. Remain on the tower frequency until instructed to monitor or contact ground. If given a crossing instruction, listen to the taxi instructions for the other side of the runway you will cross. Parking gate assignment is at the discretion of the pilot – not ATC. When given instructions to taxi to parking, you may select any open gate.