Table Of Contents
1 Clearance
2 Ground
3 Local

Clearance

  1. Frequency
    1. Provo Ground: 119.400
  2. Procedures
    1. When appropriate, inform pilots of the current ATIS information prior to contacting ground control.
  3. IFR Routing
    1. Initial Altitude: 9,000.
    2. Route all IFR departures on an approved departure procedure appropriate for their route of flight. Aircraft unable/refusing to accept a departure procedure will be assigned radar vectors.
    3. All Operations
      1. Issue PROVO SID with a clearance limit of “FFU”, not the destination airport. Instruct all aircraft to “Hold as published”.
        “N123AB Cleared to Fairfield VORTAC, depart via the PROVO# obstacle departure procedure. Hold as published. Maintain 9,000. (etc…)”
    4. If a pilot cannot accept a departure procedure, issue the following headings for radar vectors to their route, per their departure runway:
      • Runway 13, 18 – Heading 270
      • Runway 31, 36 – Heading 310
  4. Standard Departure Frequencies
    1. When appropriate, issue the following frequencies to IFR aircraft:
      • Salt Lake City Approach (Jordan Sector) 128.6
    2. When appropriate, issue the following frequencies to VFR aircraft requiring radar services after departure:
      • Salt Lake City Approach (Jordan Sector) 128.6
  5. VFR Routing
    1. Not Applicable.

Ground

  1. Frequency
    1. Provo Ground: 119.400
  2. Airspace
    1. Ground: All movement areas except active runways.
  3. Procedures
    1. Not applicable.
  4. Departures
    1. All aircraft requiring pushback onto the movement area will contact ground prior to pushback and start-up.
    2. All aircraft will contact ground with position and ATIS prior to being issued taxi instructions.
  5. Arrivals
    1. All aircraft will remain on ground frequency until off the movement area.

Local

  1. Frequency
    1. Provo Tower: 125.300
  2. Airspace
    1. Local: Runway 13/31, 18/36, and airspace as depicted on sector file.
  3. Procedures
    1. Runway operations
      1. Use runway 13 (South) during calm wind operations.
      2. Use runway 31 (North) when the tailwind component exceeds 5 knots.
    2. LAHSO
      1. Not authorized.
    3. Tower Use of Radar:
      1. Limited
  4. Departures
    1. Departure Notification / Releases
      1. A “Release Request” (.RR) is required to be sent to the appropriate Departure Controller for all departing aircraft in accordance with the General Control Directive.
  5. Arrivals
    1. IFR Arrivals
      1. N/A
      2. Circling procedures are not authorized east of runway 18/36 anytime or runway 18 at night.
    2. Missed Approach / Go Around
      1. Send A Missed Notification (.MA) for the aircraft executing an unplanned Missed Approach / Go Around to the appropriate TRACON sector that will be receiving the aircraft for re-sequencing.
      2. VFR aircraft, and/or IFR Category I / II aircraft conducting a Visual approach and executing a Go-Around must be instructed to remain in the local pattern, if capable of doing so.
      3. The following is considered Primary Climb-Out procedure and does not require any special coordination with Approach Control or Strip marking other than the basic Missed Notification. Aircraft must not turn prior to the departure end of the runway. Comm-Change to the appropriate TRACON sector must be completed no later than 1 mile off the departure end of the runway.
      4. Climb out procedure:
        • South Flow: Heading 270, Maintain 9,000.
        • North Flow: Heading 310, Maintain 9,000.
      5. VFR traffic join local pattern.
  6. VFR Operations
    1. VFR Departures
      1. Depart on-course.
      2. Handoff to departure control as soon as clear of any possible conflicts.
        • Salt Lake City Approach (Jordan Sector) 128.6
    2. VFR Arrivals
      1. Direct to airport.
    3. VFR Flight Following
      1. Ensure all aircraft requiring flight following have the appropriate scratchpad entry prior to handoff to departure.