Embedded Files
Call for Release
Call for Release
A Call For Release instruction means that PDX must call P80 to obtain an IFR release for each departure before they can take off. If a call for release is in effect, you can use STARS <F13> function.
Refer to THIS document for the coordination list commands.
Stop all departures
Stop all departures
Certain situations may require P80 to request that PDX hold/stop all departures. This coordination applies to all IFR and VFR departures receiving services from the sector/TRACON. P80 must include the estimated time for delay with the coordination. VFR aircraft remaining clear of the Class C would not be affected.
Rolling Calls
Rolling Calls
Rolling calls are only required if SOP or coordination determines they are. This lets the departure controller wants to know when a departure is rolling. This can be done verbally, but it's usually easier to use the built-in alias command:
.RC (Controller Sector ID) (runway) (free text)
Usage examples:
.RC 1D 10L CASCD
.RC 1D 28R H300
Circle to Land
Circle to Land
Many instrument approaches allow a "circle to land" at the end. This basically means that once the pilot has the airport in sight, they can maneuver visually to land on a runway they weren't lined up for. This may look like entering the traffic pattern for that runway, but it's up to the pilot how to get there. At a towered airport like PDX, the controller should be telling the pilot what runway they should circle to land on.
Some approaches, like the VOR-A into PDX, are not designed for a specific runway, so circling is required to reach whichever runway has been assigned. Others, like ILS approaches, may also have circling minimums that allow pilots to circle to land on a different runway, perhaps one without an ILS approach.
P80 should coordinate with PDX for any aircraft flying a VOR-A approach. PDX should let P80 know what runway the pilot should be told to circle to land on.
From the perspective of local control, you will be clearing the arrival to land on a specific runway just as with a normal approach, with the understanding that they will have to maneuver themselves to line up for that runway. You can not extend a downwind or delay their landing in any way.
Land And Hold Short Operations
Land And Hold Short Operations
A LASHO instruction will clear an aircraft to land but instruct them to hold short of some point on the runway if they do not exit before then. This is seen more at airports where intersecting runways are used. In addition to other requirements, a specific LAHSO directive is required that will list aircraft types and landing distances that must be met to issue a LAHSO instruction.
“Runway one eight cleared to land, hold short of runway one four left, traffic, (type aircraft) landing runway one four left.”
Reference: 7110.65 3-10-4
TTD Operations
TTD Operations
Because of the proximity of TTD airport to the east, PDX may need to adjust operations to account for operations at TTD.
In west flow, FINAL is responsible for sequencing arrivals to account for TTD operations.
In east flow, PDX must adjust departures in coordination with P80.
TTD departures in runway 10 flow:
PDX must advise P80 of the departure sequence based on aircraft ready for imminent departure. PDX must provide P80 the callsign and estimated airborne time of the aircraft the TTD departure will follow.
TTD arrivals in runway 10 flow:
P80 may require PDX to call for releases.
PDX must advise P80 of any departures on the runway, cleared for takeoff, or airborne and not yet transferred to P80.
Page updated
Report abuse