Introduction to vZLA

vZLA is one of 22 Air Route Traffic Control Centers (ARTCC) within VATUSA. Geographically vZLA covers portions of 4 states; Southern California, Southern Nevada, Southwestern Utah, and Western Arizona. It covers 3 civilian Class Bravo Airports (Los Angeles International, Las Vegas McCarran International, and San Diego’s Lindbergh Field), 4 civilian Class Charlie Airports, 30 civilian Class Delta Airports, and numerous uncontrolled airports. There are over 100 workable ATC positions with vZLA ranging from GA hubs, Airlines Hubs, and large approach and center sectors.

vZLA has high traffic levels, and complex airspace requiring a strong commitment from those wishing to control its skies, new controllers should expect to be challenged in this environment to be the best virtual controller possible.

The goals of ZLA are stated in the ZLA mission statement and can be summarized as follows:

- Provide safe and efficient and realistic air traffic control for simulated traffic on the VATSIM network.

- Accommodate pilots to the maximum extent possible.

- Create a facility that operates and provides services as close to a real world facility as possible.

There are several policies that you will need to be familiar with at ZLA. These are all found in the SOP section of the ZLA website. This introduction only gives a general overview of portions of policies which may affect your early ZLA career. Reading these policies in their entirety is highly recommended, this guide does not replace these policies.

The first policy is the general requirements policy. This policy is one of the most critical at ZLA and covers a wide range of topics. It can be summarized as follows:

- You must have operating initials (issued by the ATM) and be in compliance with given position restrictions (covered below) before logging onto a ZLA control position.

- You must advise certain controllers prior to logging onto a ZLA position.

- You must receive a briefing from the controller working your airspace before controlling it.

- Unless specific circumstances dictate, you should plan to control traffic for at least 30 minutes.

- To remain an active controller you must plug in (log on as an active controlling position) for at least 30 minutes every 180 days.

- If you are no longer an active controller you must be recertified before plugging in.

- You must use the official up to date ZLA sector file when controlling.

The second policy is the position restrictions policy. This policy is the most commonly violated policy by new controllers. A complete discussion of it will not be given here, only parts applicable for new controllers will be discussed.

Per the VATSIM Global Ratings Policy (GRP) (also known as Global Controllers or GC) all ZLA controlled airports are split up into 2 categories. A full list of airports in each category can be found under the global airports link on the ZLA website.

The first and most common category is the minor category. Minor airports are those airports where ZLA and VATUSA staff has concluded that specific local training is not required prior to plugging into those positions. Any airport which does not fit into another category is classified as a minor airport. Controllers are only required to have the proper VATSIM rating for the position desired (S1 for ground control, S2 for tower control, S3 for approach control, or C1 for center control), receive operating initials from the ATM, and receive a basic checkout by our training staff prior to plugging in.

The second and final class of airports is the major airports. Major airports are those determined by ZLA and VATUSA to have high enough traffic facilities to require specific training and certification by local staff. The following facilities are considered major facilities:
- Bob Hope Airport, Burbank, CA (KBUR)
- McCarran International Airport, Las Vegas, NV (KLAS)
- Los Angeles International Airport (KLAX)
- Nellis Air Force Base, Las Vegas, NV (KLSV)
- Lindbergh Field, San Diego, CA (KSAN)
- John Wayne Airport, Santa Ana, CA (KSNA)
- Socal Approach including all sub sectors
- Las Vegas Approach including all sub sectors
- Los Angeles Center including all sub sectors

Additionally this policy split the week into peak and non-peak times. There are different requirements to work positions during peak times as opposed to non-peak times. These times are defined as follows.

Peak Time:

Monday and Friday: 1800-2359 Pacific Time

Saturday and Sunday: 1200-2359 Pacific Time

Non-Peak Time:

Any time not defined as peak time.

A specific list of restrictions is available in the policy and will be summarized later in the training program. However it can be said that a controller may not plug into any position at ZLA without having been given operating initials by the ATM and without having either passed a GC competency check, or ZLA training.

The third policy is the Visiting and Transferring Controllers Policy. This policy only applies for controllers who have been at least S1 certified at another facility and wish to work any position at ZLA. A visiting controller is one who wished to remain part of another facility but work ZLA positions; a transferring controller is one who wishes to become a ZLA member. The following lists the main requirements under this policy. Note that VATUSA/VATSIM policies also apply to transferring/visiting controllers and will not be restated here.

- The controller wishing to transfer/visit ZLA must be in good standing at their present facility.

- Visiting controllers should be aware that training resources are primarily for ZLA members and instruction to visiting controllers is limited to local procedures and is given lowest priority.

- All controllers wishing to visit/transfer to ZLA must comply with all other policies.

- Any controller who is an Instructor at another facility may not use this rating when logged on as a ZLA controller.

- Any controller who wished to work a major or LCTP airport must go through the entire ZLA training program, previous credit for ratings earned may not be transferred over (aka. An ATL_CTR certification does not grant a LAX_CTR certification.)

The final policy we will review is the removal policy. This policy states the conditions under which a member may be removed from the ZLA roster.

- Failure to complete any training for a ZLA position within 60 days of joining with ZLA training staff within 60 days of joining.

- Not controlling for 60 days will result in being placed in inactive status.

- Not controlling for more then 120 days without arranging for a leave of absence (LOA) may result in removal. Note that this does not conflict with the 180 day period stated in the general requirements as that relates to solo controlling and not status at ZLA.

- Failure to pass the ZLA Basic exam after 4 attempts. There is a 6 month waiting period before being allowed to rejoin.

- Failure to pass the ZLA clearance exam after 3 attempts. There is a 6 month waiting period before being allowed to rejoin.

- Failure to comply with any ZLA policy or procedure.

- Failure to comply with VATSIM regulations.