Table Of Contents
Clearance
-
Frequency
- Bozeman Ground: 121.800
-
Procedures
- When appropriate, inform pilots of the current ATIS information prior to contacting ground control.
-
IFR Routing
- Initial Altitude: 16,000.
- Route all IFR departures on an approved SID appropriate for their route of flight. Aircraft unable/refusing to accept a SID will be assigned radar vectors.
- All Operations
- N and S to NW departures issue TEERX SID.
- NE to SE departures issue BOBKT SID. Issue HIA SID for SW to NW
- Issue HIA SID for SW to NW Non-RNAV aircraft and radar vectors for all other Non-RNAV aircraft.
- If a pilot cannot accept a departure procedure, issue the following headings for radar vectors to their route, per their departure runway:
- Runway 12 – Heading 250
- Runway 30 – Heading 290
-
Standard Departure Frequencies
- When appropriate, issue the following frequencies to IFR aircraft:
- Big Sky 118.975
- When appropriate, issue the following frequencies to VFR aircraft requiring radar services after departure:
- Big Sky 118.975
- When appropriate, issue the following frequencies to IFR aircraft:
-
VFR Routing
- Not applicable.
Ground
-
Frequency
- Bozeman Ground: 121.800
-
Airspace
- All movement areas with the exception of active runways.
-
Procedures
- Not applicable.
-
Departures
- All aircraft requiring pushback onto the movement area will contact ground prior to pushback and start-up.
- All aircraft will contact ground with position and ATIS prior to being issued taxi instructions.
- During periods of high volumes of traffic, the published Standard Runway Assignments may be used to expedite the flow of departures.
- Standard Runway Assignments
- East Operations
- Runway 12: All departures.
- West Operations
- Runway 30: All departures.
- East Operations
-
Arrivals
- All aircraft will remain on ground frequency until off the movement area.
Local
-
Frequency
- Bozeman Tower (Local): 118.200
-
Airspace
- Local: Runways 12/30, 3/21, and airspace as depicted on sector file.
-
Procedures
- Runway operations
- Use runway 12 (East) during calm wind operations.
- Use runway 30 (West) when the tailwind component exceeds 5 knots.
- LAHSO
- The following procedure defines position responsibilities for the use of Land and Hold Short Operations.
- The LASHO runway must be dry
- The tailwind on the LAHSO runway shall be calm (less than 3 knots)
- The RED LAHSO CHIP will be placed face up at the bottom center of the TMB, when LAHSO is authorized, and placed face down in the same place when not
- A RED magnetic chip will accompany the magnetic chip of the aircraft which is landing and holding short
- LAHSO must not be utilized if wind shear has been reported
- Ceiling of 1000 feet and 3 miles visibility must be reported at the airfield
- Runway 12 has 6,841 feet available landing distance (ALD) for LAHSO, when ALD is requested by a Pilot; it will be rounded down to 6,800 ft. of ALD, IAW JO 7110.65
- All other procedures are outlined in FAA JO 7110.118.
- Traffic will be issued in accordance with FAA JO 7110.118 and the FAA JO 7110 .65
- LAHSO for Runway 12 will be limited to:
- Daytime operations only
- Propeller driven aircraft in FAA Group 7 and below
- The following aircraft WILL NOT be allowed to conduct LAHSO.
- All Air Carrier and Air Taxi aircraft
- All jet aircraft
- All solo student pilots
- BE60 Beach Duke
- Super DC-3 (C-117, R4D 8)
- HERN Heron DH-114
- PAY3 Piper Cheyenne 3
- The following procedure defines position responsibilities for the use of Land and Hold Short Operations.
- Runway operations
- LOCAL RADAR
- Tower Use of Radar
- Limited
- Tower Use of Radar
-
Departures
- Departure Notification / Releases:
- Departure Notifications are not required, unless otherwise coordinated by TRACON.
- Departures are automatically released, unless otherwise coordinated by TRACON.
- IFR Departures
- Ensure aircraft turn to assigned point/heading and altitude reporting is operating prior to handoff to departure.
- VFR Departures
- Handoff to departure control as soon as clear of any possible conflicts.
- Ensure all aircraft requiring flight following have the appropriate scratchpad entry prior to handoff to departure.
- Departure Notification / Releases:
-
Arrivals
- IFR Arrivals
- N/A
- Missed Approach / Go Around
- Acquire the track control for the aircraft conducting a missed approach.
- 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.
- 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.
- The following is considered Primary Climb-Out procedure and does not require any special coordination with Approach Control or Strip marking (Scratchpad entries) other than the basic Missed Notification. Aircraft must not turn prior to the departure end of the runway. Handoff/Comm-Change to the appropriate TRACON sector must be completed no later than 1 mile off the departure end of the runway.
- Climb out procedure:
- East Flow: Heading 120, Maintain 8000.
- West Flow: Heading 300, Maintain 8000.
- VFR traffic join local pattern.
- IFR Arrivals