AIM DECODED

5-2-4. Taxi Clearance

AIM Text

Pilots on IFR flight plans should communicate with the control tower on the appropriate ground control or clearance delivery frequency prior to starting engines, to receive engine start time, taxi, and/or clearance information.

5-2-5. Line Up and Wait (LUAW)

  1. Line up and wait is an air traffic control (ATC) procedure designed to position an aircraft onto the runway for an imminent departure. The ATC instruction “LINE UP AND WAIT” is used to instruct a pilot to taxi onto the assigned departure runway, align the aircraft with the correct departure direction and await for further ATC instructions. LUAW is not an authorization to takeoff.
  2. In instances where the pilot has been instructed to LUAW and has been advised of a reason/condition (wake turbulence, traffic on an intersecting runway, etc.) or the reason/condition is clearly visible (another aircraft that has landed on or is taking off on the same runway), and the reason/condition is satisfied, the pilot should expect an imminent takeoff clearance, unless advised of a delay. If you are uncertain about any ATC instruction or clearance, contact ATC immediately.
  3. If a takeoff clearance is not received within a reasonable amount of time after instructed to LUAW, ATC should be contacted.
  4. Situational awareness during line up and wait operations is enhanced by monitoring ATC instructions/clearances issued to other aircraft. Pilots should listen carefully if another aircraft is on frequency that has a similar call sign and pay close attention to communications between ATC and other aircraft. If you are uncertain of an ATC instruction or clearance, query ATC immediately. Care should be taken to not inadvertently execute a clearance/instruction for another aircraft.
  5. Pilots should be especially vigilant when conducting LUAW operations at night, when intersecting runway operations are being conducted, or during reduced visibility conditions. Pilots should scan the full length of the runway and look for aircraft crossing the runway, on final approach, or landing roll (including intersecting runways) prior to and while taxiing onto the runway. ATC should be contacted anytime there is a concern about a potential conflict or clarity is needed with assigned instructions.
  6. When two or more runways are active, aircraft may be instructed to “LINE UP AND WAIT” on two or more runways. When multiple runway operations are being conducted, it is important to listen closely for your call sign and runway. Be alert for similar sounding call signs and acknowledge all instructions with your call sign. When you are holding in position and are not sure if the takeoff clearance was for you, ask ATC before you begin takeoff roll. ATC prefers that you confirm a takeoff clearance rather than mistake another aircraft's clearance for your own.
  7. When ATC issues intersection “line up and wait” and takeoff clearances, the intersection designator will be used. If ATC omits the intersection designator, call ATC for clarification.
  8. If landing traffic is a factor during line up and wait operations, ATC will inform the aircraft in position of the closest traffic within 6 flying miles requesting a full-stop, touch-and-go, stop-and-go, or an unrestricted low approach to the same runway. Pilots should take care to note the position of landing traffic. ATC will also advise the landing traffic when an aircraft is authorized to “line up and wait” on the same runway.
  9. Never land on a runway that is occupied by another aircraft, even if a landing clearance was issued. Do not hesitate to ask the controller about the traffic on the runway and be prepared to execute a go-around.

5-2-6. Abbreviated IFR Departure Clearance (Cleared. . .as Filed) Procedures

  1. ATC facilities will issue an abbreviated IFR departure clearance based on the ROUTE of flight filed in the IFR flight plan, provided the filed route can be approved with little or no revision. These abbreviated clearance procedures are based on the following conditions:
    1. The aircraft is on the ground or it has departed visual flight rules (VFR) and the pilot is requesting IFR clearance while airborne.
    2. That a pilot will not accept an abbreviated clearance if the route or destination of a flight plan filed with ATC has been changed by the pilot or the company or the operations officer before departure.
    3. That it is the responsibility of the company or operations office to inform the pilot when they make a change to the filed flight plan.
    4. That it is the responsibility of the pilot to inform ATC in the initial call‐up (for clearance) when the filed flight plan has been either:
      1. Amended, or
      2. Canceled and replaced with a new filed flight plan.
  2. Controllers will issue a detailed clearance when they know that the original filed flight plan has been changed or when the pilot requests a full route clearance.
  3. The clearance as issued will include the destination airport filed in the flight plan.
  4. ATC procedures now require the controller to state the DP name, the current number and the DP transition name after the phrase “Cleared to (destination) airport” and prior to the phrase, “then as filed,” for ALL departure clearances when the DP or DP transition is to be flown. The procedures apply whether or not the DP is filed in the flight plan.
  5. STARs, when filed in a flight plan, are considered a part of the filed route of flight and will not normally be stated in an initial departure clearance. If the ARTCC's jurisdictional airspace includes both the departure airport and the fix where a STAR or STAR transition begins, the STAR name, the current number and the STAR transition name MAY be stated in the initial clearance.
  6. “Cleared to (destination) airport as filed” does NOT include the en route altitude filed in a flight plan. An en route altitude will be stated in the clearance or the pilot will be advised to expect an assigned or filed altitude within a given time frame or at a certain point after departure. This may be done verbally in the departure instructions or stated in the DP.
  7. In both radar and nonradar environments, the controller will state “Cleared to (destination) airport as filed” or:
    1. If a DP or DP transition is to be flown, specify the DP name, the current DP number, the DP transition name, the assigned altitude/flight level, and any additional instructions (departure control frequency, beacon code assignment, etc.) necessary to clear a departing aircraft via the DP or DP transition and the route filed.
    2. When there is no DP or when the pilot cannot accept a DP, the controller will specify the assigned altitude or flight level, and any additional instructions necessary to clear a departing aircraft via an appropriate departure routing and the route filed.
    3. If it is necessary to make a minor revision to the filed route, the controller will specify the assigned DP or DP transition (or departure routing), the revision to the filed route, the assigned altitude or flight level and any additional instructions necessary to clear a departing aircraft.
    4. Additionally, in a nonradar environment, the controller will specify one or more fixes, as necessary, to identify the initial route of flight.
  8. To ensure success of the program, pilots should:
    1. Avoid making changes to a filed flight plan just prior to departure.
    2. State the following information in the initial call‐up to the facility when no change has been made to the filed flight plan: Aircraft call sign, location, type operation (IFR) and the name of the airport (or fix) to which you expect clearance.
    3. If the flight plan has been changed, state the change and request a full route clearance.
    4. Request verification or clarification from ATC if ANY portion of the clearance is not clearly understood.
    5. When requesting clearance for the IFR portion of a VFR/IFR flight, request such clearance prior to the fix where IFR operation is proposed to commence in sufficient time to avoid delay. Use the following phraseology:

Source: FAA Aeronautical Information Manual · current edition · paragraph 5-2-4.

Research Notes

AIM 5-2-4 covers Pre-Taxi Considerations — the items pilots should consider before commencing taxi.

Pre-taxi checklist items:

  • Aircraft configured for taxi (flaps as needed, brakes verified, engine warm)
  • Taxi clearance received and read back
  • Taxi route understood — airport diagram reviewed
  • Hot spots identified
  • Communications: Ground frequency tuned, ATIS letter known
  • Lights: anti-collision on, position lights at night

Reference: AIM 5-2-4; AC 91-73B (Single-Pilot Procedures During Taxi Operations).