¶ Standard Operating Procedures
¶ IFR
| SID | SID Type | Pronounciation | Aircraft | Runways | Initial Climb | Notes |
|---|---|---|---|---|---|---|
| KINGS# | Vectors | Kings | All | All | 6000 | |
- Tower must instruct aircraft to fly runway heading. On initial climb, approach will assign vectors to initial route fix.
¶ IFR Clearance
IFR (RNAV) Example:
Cleared to Los Angeles International via radar vectors to London VOR, then as filed. Maintain 6000, Expect FL370 10 minutes after departure. Departure frequency Tri Cities Approach 125.5, squawk 2001.
¶ IFR Squawk codes
via Aurora or 2001-2777
¶ VFR
Tri Cities Airport is surrounded by class D airspace. Aircraft entering class D airspace VFR require two-way communication with ATC. 7400.2 Chapter 17, section 2.
VFR Departure Example:
Squawk VFR. Runway 9, taxi via A B.
VFR Local Pattern Example:
Local traffic approved. Pattern altitude 2500’, expect left closed traffic runway 5, squawk VFR.
Tri Cities Ground 121.70 | KTRI_GND
Ground is responsible for all movement areas.
Arriving GA traffic and private jets shall be routed to park at one of two GA Ramps:
| FBO | Location |
|---|---|
| Tri Cities Aviation | Northeast of the terminal on A |
| South GA Ramp | Next to the tower |
¶ Runway Crossings
When requesting a runway crossing from TWR, specify the runway and the point at which crossing will occur, using the format of “Cross (rwy) at (intersection)?”. Callsign is not required.
TWR’s approval is only valid for one aircraft to cross as specified.
Tri Cities Tower 129.50 | KTRI_TWR
¶ Area of Responsibility
- TWR owns airspace from the surface up to and including 2,000 feet MSL, 5-mile radius.
¶ Missed Approaches and Go-Arounds
Aircraft should be advised to climb and maintain 4000’, fly runway heading, and handed off to the approach or center controller if available.
Tri Cities Approach 125.50 | KTRI_APP
¶ Area of Responsibility
KTRI_APP is responsible for airspace up to and including 10000’
