Welcome to Dallas/Fort Worth.

General Overview

As a general rule, all arrival procedures are filed with the route in an aircraft's flightplan. This cuts down on the number of transmissions and controller workload.

RNAV Optimized Profile Descent Procedures

As of AIRAC 1503, RNAV Optimzed Profile Descent profiles are the preferred arrival routes into DFW for turbojet aircraft only. These arrival routes are the BEREE, BOOVE, BOWIE, BRDJE, CABBY, CAINE, CQY, JOVEM,
SEEVR, SOCKK, VKTRY, and WHINY. These types of arrival routes are designed to minimize or eliminate steps during descent, saving fuel and time. Please file these arrivals, if able, into DFW.

Dallas Fort Worth Arrivals are dependant on the flow (North or South) of landing and
departing aircraft. Please read your charts carefully and tune in to the ATIS
to determine the flow at DFW. Pilots should not descend to meet the minimum altitude possible for an "at-or-above" fix.

Pilots should comply with all speed an altitude restrictions on the STAR unless otherwise
instructed by ATC. Prior to arrival into the Terminal Radar Area of Control
pilots will be instructed to "Contact Lone star approach and given a frequency.

Conventional Arrival Procedures

Pilots operating non-jet aircraft into DFW and all types of aircraft into DFW Satellite Airports (DTO, AFW, ADS, etc.) should file and expect to fly "conventional" or "legacy" arrival procedures. These aircraft are typically issued "descend at pilot's discretion, maintain a specific altitude". It is imperative that pilots do not descend immediately when issued this instruction, but rather descend at the computed top of descent in order to meet hard altitude restrictions.

Once reaching the low Fort Worth Center sector, aircraft will be issued a crossing restriction in line with the altitude restrictions published on the chart. If a speed restriction is assigned, aircraft are expected to meet the assigned speed by the crossing restriction.

If arriving into Dallas-Fort Worth, be careful to fly the appropriate assigned headings on the chart.

Initial Contact

When checking on with Lone Star Approach, advise the controller of the current ATIS code at your destination airfield. The controller will usually respond with a runway assignment and any relevant information or control instructions. From entering D10's airspace to gate arrival, please give the controller your full attention, as frequencies will be busy and instructions will be issued in rapid succession to multiple aircraft. Use of ACARS or V/X Pilot chat functions should be kept at a minimum once in the terminal environment.

By this point, you should have familiarized yourself with the arrival procedure and runway transition. Note the instructions on each of the arrivals, particularly on arrivals with a downwind portion (DFW in South Flow coming from South, e.g.). Note that these arrivals typically assign a heading to fly after the last fix (heading 357 after BEONE, e.g.), and pilots are expected to comply. Once on one of these assigned headings, pilots should expect vectors to the airport. At no point should a pilot execute a base turn or execute an RNAV approach unless cleared to do so.

Final Approach

Depending on the traffic levels, you may be issued another frequency change to the Final Approach controller. If you are landing at an D10 satellite airport, you will be handed off to the satellite controller (D10_M_APP) who will sequence you onto your requested approach at your destination airport. When instructed, please check on with the controller as soon as possible. Not doing so will lead to delays.

When instructed to turn, it is imperative to initiate the turn upon receipt prior to or during your readback. Not doing so will lead to missed localizer captures. When cleared for the approach, the controller may assign a speed restriction to the final approach fix ("maintain 170 knots or greater until BBAKR", e.g.) For sequencing purposes, do not reduce to final approach speed until inside of the final approach fix.

Gate Assignment

Before arriving at DFW, decide where you are parking. Either on approach or after landing, you will be asked for your gate number in order to facilitate taxi. Please have an airport diagram available for reference for your assigned taxi route.

Landing & Taxi

ZFW simulates ASDE-X. Please taxi with your transponder with altitude encoding on ("Mode C") while on all taxiways and runways. If unable, advise controllers as soon as practical.

Do not cross any runway without a clearance from a controller. This rule applies to all active, inactive, and closed runways.

There is no need to advise the controller that you have arrived or parked at the gate.

If you will be departing DFW, please obtain the most recent ATIS information and contact DFW_DEL (or DFW_GND if DFW_DEL is not online) to obtain your clearance. Be prepared to copy amendments, as routes may change due to weather or traffic volume.

Standard Instrument Departures

All DFW SIDs are RNAV procedures, with the exception of a few departures. Departures from DFW are advised to "climb via SID." As such, on departure, pilots are required to fly the appropriate departure and to comply with all altitude restrictions on the chart on the climb to the published top altitude.

Pushback & Taxi

Pushback onto movement areas (e.g. taxiways) requires a clearance from DFW_GND. However, push into the ramp is at pilot’s discretion. All of the gates at DFW are in a non-movement area.

Taxi instructions at DFW tend to be lengthy. Be sure to have an airport diagram for reference, and to copy down taxi instructions accurately. Pilots are reminded that in order to cross any runway, a clearance must be obtained.

Pre-Departure Clearance

DFW Clearance Delivery uses text-based Pre-Departure Clearances which simulate PDCs on ACARS-equipped aircraft. If your route of flight and other flightplan information is valid, expect to receive two private messages from the appropriate clearance delivery controller. The PDC formatting at KDFW is as follows:

**** PREDEPARTURE CLEARANCE **** [2:56:51] ACARS: PDC | CALLSIGN: AAL1460 | EQUIPMENT: A321 | DEPARTURE: KDFW | DESTINATION: KDCA |
ROUTE: KDFW TRYTN4 LOOSE MEM J42 TONIO J42 BKW TRUPS3 KDCA | ALTITUDE: 310 | SQUAWK: 3667 |
REMARKS: CLEARED TRYTN4 DEPARTURE LOOSE TRSN CLIMB VIA SID EXP 310 10 MIN AFT DP,DPFRQ 125.025
ADVS WITH SPOT NUMBER CTC 121.65 FOR TAXI

Ground Metering Procedures

During the busiest periods of an event, departure slot and ground metering procedures may be utilized in order to efficiently manage departure traffic from the airport. In the event that a flight booking system is used, priority will be given to pre-booked flights. If this procedure is used, the ATIS will be updated with the relevant NOTAM. It is very important that all airline traffic contact DFW_DEL prior to pushing back during metering procedures so that a proper departure sequence can be maintained. When contacting DFW_DEL for push, check on with the current ATIS information, gate, and assigned beacon code. (e.g. "DFW Ground, Delta 589, gate C4.") Clearance Delivery will advise you monitor the appropriate DFW_GND controller, who will approve your push in sequence, and assign you a departure runway.