¶ Standard Operating Procedures
¶ IFR
| SID | SID Type | Pronounciation | Aircraft | Runways | Initial Climb | Notes |
|---|---|---|---|---|---|---|
| ASHEVILLE# | RNAV | Asheville | All | All | 8000 | |
- Instruct aircraft to fly runway heading, on initial climb, assign vectors to initial route fix.
¶ IFR Clearance
IFR (RNAV) Example:
Cleared to Chattanooga via the Asheville 7 deparutre, radar vectors to BALNN, then as filed. Maintain 8000, Expect FL240 10 minutes after departure. Departure frequency Asheville Approach 124.65, squawk 2001.
¶ IFR Squawk codes
via Aurora or 2001-2777
¶ VFR
Asheville Regional Airport is surrounded by class C airspace. Aircraft entering class C airspace VFR require two-way communication with ATC and an operational transponder. 7110.65 Chapter 7, Section 8.
VFR Deaprture Example:
Squawk VFR. Runway runway 17, taxi via A.
VFR Local Pattern Example:
Local traffic approved. Pattern altitude 3200’, expect left closed traffic runway 17, squawk VFR.
Asheville Ground 121.90 | KAVL_GND
Ground is responsible for all movement areas.
Arriving GA traffic and private jets shall be routed to park at Signature Aviation FBO located at taxiways D1 and D2.
¶ 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.
Asheville Tower 121.00 | KAVL_TWR
¶ Area of Responsibility
- TWR owns airspace from the surface up to and including 8,000 feet MSL, 8 miles from the departure/arrival end of the active runway and 1.5NM on either side of the centerline.
¶ Missed Approaches and Go-Arounds
Aircraft should be advised to climb and maintain 6000’, fly runway heading, and handed off to the approach or center controller if available.
Asheville Approach 124.65 | KAVL_APP
¶ Area of Responsibility
KAVL_APP is responsible for airspace up to and including 10000’
