Flight Clearance Processing Basics

Checking the Flight Plan

• Focus on accuracy, then speed when processing flight clearances.
• Key phrases for slow clearances: "Clearance on request (number X), stand by," and "Clearance available, advise ready to copy."
• Clearances are generally processed on a first-come, first-served basis.
• Verify aircraft type and equipment code.
• Use resources (like Wikipedia) for general information (engines, weights, ceiling, etc.).
• Ensure equipment code matches the aircraft type and intended route (e.g., RVSM, RNAV).
• For airliners, use "/L" as the equipment code if applicable.
• Refer to FlightAware's Equipment Suffix table for a more detailed code if needed.
• RVSM airspace is FL290-FL410.
• Aircraft operating in RVSM airspace should have RVSM capability but aren't required (coordinate with ATC).
• Above RVSM, flight levels are every 2,000 feet (FL430, FL450, etc.)
• Communicate flight plan changes clearly.
• Use magnetic headings and the NEODD/SWEVEN rule for proper altitudes (ref 4-5-2).
• Verify flight routes using tools like SkyVector.
• Routes within Zone of Significant Enroute (ZSE) should be accurate and reasonable outside; preferred routes aren’t mandatory, unless in LOA or event routes, unless otherwise coordinated.
• Review the entire flight plan before issuing clearance.
• Practice with real-world or VATSIM data to gain experience.

Giving the Clearance

• Practice proper clearance procedures (CRAFT, "and then as filed").
• Avoid extra words; use "cleared to" instead of "you are cleared to."
• PDX VFR departures only need AFT information (no clearance unless B or Special VFR).
• Specify destination airport (e.g., Seattle-Tacoma Airport).
• Include departure information (vectors, SID, transition). (ref 4-3-2)
• VUOs have different clearance procedures (refer to reference documents/SOP).
• Minimum readback includes squawk code and any changes from the filed plan.
• Verify readback for accuracy. Correct errors before proceeding.
• Aircraft pushing onto movement area from terminal must call Ground Control (GND) for pushback.
• Other aircraft can choose to remain in the non-movement area.

Pushback and Taxi

• Ground controllers should only "clear" aircraft for IFR plans, SVFR, or within Class B airspace.
• Avoid using "cleared" for pushback, taxi, and runway crossings.
• Example pushback instruction: "Push onto T approved, face west, expect 10L at E, advise when ready for taxi."
• Verify aircraft is squawking correct Mode C code before giving taxi instructions.
• CRC ASDE-X shows standby aircraft as blue cursors, and Mode C aircraft as icons.
• Incorrect Mode C squawk with altitude reporting shows incorrect code in the Data Block.
• Practice precise taxi phraseology (runway at intersection, taxi via route, cross/hold short, altimeter reading). (ref 3-7-2)
• Use "Taxi to (parking location) via (route)"
• For intersection departures, always mention "(runway) at (intersection)."
• Issue distance remaining only if requested or for military aircraft. (ref 3-7-1)
• Include taxiway crossings/hold-short instructions for each runway.
• PDX Runway 21 (rarely used, but considered open). Coordinate with TWR. Blanket crossing permission is often given, but include "cross runway 21" as needed. (includes taxiway K for 10L full length)
• Pilots can switch to TWR upon reaching the runway; you can send them over if clear of conflicts.

General Phraseology

• Begin transmissions with callsign.
• Identify yourself after the callsign, especially on initial communication.
• Use "heavy" or "super" to indicate wake turbulence categories for heavier aircraft.
• In frequencies, use only the first two decimal digits (e.g., omit the 5).
• Pronounce runway numbers clearly by stating each digit separately.
• Communication with other controllers can be informal, but still adhere to protocol. (ref 2-4-12).
• Prepare transmissions thoroughly before speaking. (ref 2-4-8)

Climb via SID Phraseology

• The FAA introduced new climb via SID phraseology in July 2014 (updated to NOTC51417-A). Reference FAA JO 7110.65AA for details.

• New phraseology differs based on whether a SID has a published top altitude with or without published altitude restrictions.

• Use "Climb via SID" if a SID has a published top altitude and altitude restrictions.

• Use "Maintain XXXX" if the SID has a published top altitude with no altitude restrictions.

• Use "Climb via SID except maintain (altitude)" if the SID has a published top altitude with altitude restrictions, but you want the plane to climb to a different altitude, ignoring the published restrictions

• Use "Maintain XXXX" if a SID has no published top altitude and no published altitude restrictions.

• Example phraseology in TRACON environment (for a SID with altitude adjustments): "Seattle Departure, Delta 112 one thousand four hundred climbing seven thousand, HAROB6 departure", "Delta 112, Seattle departure. Radar contact, climb via SID except maintain one-five thousand".

• SIDs with "TOP ALTITUDE: ASSIGNED BY ATC" have no published top altitude, but are still subject to restrictions

• Non-SID departures use "Maintain xxxx" phraseology.

• ZSE specific examples given for SIDs (SEA, SUMMA, MONTN, HAROB#, etc), for details, refer to 7110.65AA.

Special VFR Operations (SVFR)

• SVFR allows aircraft to operate below VFR minimums.

• SVFR is pilot-requested to enter/exit controlled airspace below 10,000 MSL.

• Only permitted in Class B, C, D or E surface areas (lateral boundaries)

• Limited to airports not listed in 14 CFR Part 91, Appendix D (e.g., PDX and SEA)

• Weather conditions must meet: airport's reported ground visibility and/or pilot-reported flight visibility (minimum "clear of clouds," 1 statute mile); these restrictions do not apply to helicopters.

• Clearances should specify the surface area and maintain SVFR conditions at or below a certain altitude, 500 feet below conflicting IFR traffic, but not below the MSA.

• Local operations may be permitted as long as the aircraft can be recalled if necessary.

• SVFR allows climb to VFR conditions.

• Visual separation is required between SVFR aircraft and other aircraft.

Test your knowledge on accurately processing flight clearances with a focus on terminology, aircraft types, and equipment codes. This quiz covers essential protocols, including the RVSM airspace requirements and communication practices. Enhance your understanding of flight plans and clearances for effective air traffic management.