IVAO USA > Los Angeles ARTCC > Sop

Operating Procedures for ATCs on Los Angeles ARTCC Facilities


Introduction

The Los Angeles ARTCC would like to welcome you to the Training Department.  As you review the information on this page, you will find the necessary information for your continued enjoyment of being a virtual air traffic controller or pilot with the IVAO Network.  Whether you are an experienced ATC/Pilot or just getting started, you will find the members of IVAO to be very helpful and dedicated to improve your online virtual experience.  Here at KZLA, we strive to improve our members knowledge and abilities in the areas of ATC and Pilot performance.  As you progress in the ratings of IVAO, you will find continued enjoyment with your virtual flying experiences.

The two links shown on the upper left will give you the basic information about ProController (ATC) and Squawk Box (Pilot).  Please take the time to review this information which will make it easier as you first get started with your virtual aviation experience on the IVAO Network.

 

Content:

1 – Introduction

2 – ATIS and Ground Basics

3 – Tower Controller Basics

4 – Approach Basics

5 – SOCAL

6 – St. Maarten (TNCM)

2 – ATIS and Gorund Basics

 

ATIS Information in ProController

From the ProController tutorials, you will find the necessary information of how to add this information.  As a general rule, DEL, GND, TWR, and APP ATIS information should contain the following information;

DEL - GND - TWR - APP :

- Team Speak

- Airport name and station ID, then the identification letter (phonetic name of the letter,such as BRAVO} and time (UTC).

- Runway in use for Arrival and Departure, Transition Level (US TL FL180)

- Wind dir and speed and altimeter. If there are any special weather considerations, it should be noted here as well. (no need to copy full METAR into ATIS, pilots have it from ACARS).

- Controller Information/Specific instructions (if any, like speed restrictions or specific noise abatement procedures).

 

An example for KLAX_TWR would be as follows:

 

-br.ts.ivao.aero/KLAX_TWR

-LOS ANGELES APP INF ALPHA at 23:56Z, RD BCK ALL INSTS REQ

-ACT RWYS 25R DEP/ 25L ARR, TL FL180, WDS 240 AT 12 A2998

-CTRL JOHN DOE S-2 (Your Rating), KIAS RESTRICTIONS APPLY

 

(Note:  Try to keep your ATIS to three to four lines maximum.)
I prefer to capatalize my ATIS to make it easier for the pilots to read as it scrolls across the screen. This is not a requirement, but it is recommended.



KZLA Ground Procedures.

FREQUENCY: KLAX_GND:  121.650
   
   
ATIS BASICS:
       To Create an ATIS (Automated Terminal Information Service) double click on the radar screen and select Misc. After doing so there will be a white box. In that box is where the atis will be entered. An example of the atis for Los Angeles' Ground Contoller. <Los Angeles Ground information Alpha, ALL information requires a readback. On initial contact advise information Alpha has been recieved. Expected runways for departure are 25R and 24R. Your Ground controller is John Doe, C1>

   When controllers sign on, they should sign on as observers to begin with. This is so they can survey the situation to find out what stations are available. Once you are logged on, use the command .atis for each of the manned stations. Note the letters of the active controllers ATIS and set your ATIS at the next highest letter in the seiries. Set up your ATIS and frequency for the position you intend to man. Log off and log back in at that station and then send a chat to each of the active controllers to let them know you are available for handoffs. You should also use the ATC channel to announce that you are on line with the zulu time of your sign on.

    The Atis shall be updated every hour and when updated the "Alpha" would be changed to "Bravo" and so forth as time goes on. Also as Ground Controller you do not set the runways for takeoff or landing, that is Tower's Job, so you would coordinate with them for the active runways.

Ground Basics:

    First you need to obtain the ground chart for Los Angeles International so you know the taxi ways and holding points as well as the terminals. REMEMBER, the Runways are the only part of the ground that does not belong to you. If you are having a jet taxi and needs to cross a runway, the Jet MUST contact tower to do so. Also a jet must not Taxi faster than 25 knots unless he is in the high speed taxi way (usually the closest taxi way to the runway.), then he is authorized to taxi up to 50 knots.

    Once the jet is holding short at the runway for takeoff, you the would handoff the Jet to the tower controller. You do this by right clicking on the jet you wish to handoff, select aircraft ant then select handoff request, then you select the position you would like to handoff to,in this case the tower position.

    When a jet lands, and departs the active runway, the tower controller will handoff the aircraft to you, the gorund controller so that you can taxi him to his gate.

3 – Tower Controller Basics

 

  • Frequency: 120.950

    Tower Atis:

        The Tower ATIS is pretty much the same as ground's, but has more info. An Example of this is Los Angeles Tower information Alpha, ALL instructions require a readback! On initial contact advise information Alpha received. Active runway(s) for departure are 25R for Turbojets and 24L for turboprops and recips and for landing 25L and 24R respectively. Weather conditions are as follows. Winds 238 at 12 the local alt is 2998, with a Vis of 10 statute miles. Your Tower Controller is John Doe, C1

        As with Ground, you update your Atis once an hour and you change the Alpha, to Bravo and so forth. You pick your runways by the weather. As the example above we picked 25L and 24R because the winds are at 238. If they were at 080 we would pick the oposite side. Another thing to remember is that the Short runways are for landing and the longer runways are for departures, for the simple reason, the longer runway allows the aircraft to reach takeoff speed before reaching the end of the runway.

     

    Tower basics:

        As the Tower controller, you are Resposible for the jet while it is on takeoff and landing up to 10nm out from the airport. Ground will handoff the jet to you when it is holding short of the active runway, and you will hand off the jet to ground when it exits the active runway. You as the tower controller must give a jet permission to cross a runway, ground may not do so. Once the jet is holding short at the active runway, and it is clear for him or her to takeoff, you tell the pilot to line up and hold. Once he is lined up and holding and it is clear for takeoff, you give the jet clearance to takeoff as follows. Dal123 clear for takeoff rwy 25L winds 220 at 14. alt 2998.The pilot will readback, rgr clear for takeoff, winds and alt copied.

        Once the jet goes airborne, you then would handoff the jet to the Aproach control,( Departure if manned). You will do this the same way as ground hands off the jet, except you would hand off to the approach or departure controller. The approach controller will then handoff an aircraft to you when the jet is on final approach, somewhere close to 10 nm out from the airport. Once the aircraft is handed off to you, you will then clear the aircraft to land, here is an example. Dal123 clear to land rwy 25L winds 220 at 11 atlimeter 3014. The pilot will readback, clear to land rwy 25L winds and altimeter copied. Once the aircraft is on the ground, you will have the pilot exit the runway and handoff to the ground controller. NOTE: If the runway is fouled, or not safe to land, you would have the pilot excecute a missed approach and hand the jet back to the approach or departure controller so they can bring them back around.

4 – Approach Basics

JUST BLANK
BLANK BLANK BLANK BLANK BLANK BLANK BLANK BLANK BLANK BLANK BLANK
BLANK
BLANK BLANK BLANK BLANK BLANK
BLANK BLANK BLANK BLANK BLANK BLANK BLANK
BLANK BLANK BLANK BLANK BLANK BLANK BLANK BLANK BLANK
BLANK BLANK BLANK BLANK BLANK BLANK

5 – SOCAL

Southern California Terminal Radar Approach Control

SoCal TRACON is the busiest approach control area in the world, providing radar air traffic approach control services to all arriving and departing aircraft for most airports in southern California.  Airports receiving SoCal Tracon services include:

Burbank Airport
John Wayne Airport
Los Angeles International Airport
Long Beach Airport
March AFB
Miramar MCAS
North Island NAS
Ontario Airport
San Diego International Airport
Van Nuys Airport
and many more airports that service general aviation.

SOCAL's airspace covers an area from 20 miles north of Burbank to the US/Mexican border and from San Bernardino to Santa Catalina Island.


Listen to our real life counterpart:
Southern California Approach Southern California Live ATC

NOTAMS for 07/06/04
KZLA LOS ANGELES (ARTCC) PALMDALE, CA.

A0109/03 (FDC 3/2123) - FLIGHT RESTRICTIONS ANAHEIM, CA. EFFECTIVE 0303182000 UTC (MARCH 18 AT 1200 LOCAL) UNTIL FURTHER NOTICE. PURSUANT TO RESTRICTIONS DETAILED IN SECTION 352 OF PUBLIC LAW 108-7, AND 14 CFR SECTION 99.7, SPECIAL SECURITY INSTRUCTIONS. AIRCRAFT FLIGHT OPERATIONS ARE PROHIBITED AT AND BELOW 3,000 FEET AGL, WITHIN A 3 NAUTICAL MILE RADIUS OF THE DISNEYLAND THEME PARK (334805N/1175517W OR THE SEAL BEACH /SLI/ 067 DEGREE RADIAL AT 6.7 NAUTICAL MILES. THIS RESTRICTION DOES NOT APPLY TO (A) THOSE AIRCRAFT AUTHORIZED BY ATC FOR OPERATIONAL OR SAFETY PURPOSES, INCLUDING AIRCRAFT ARRIVING OR DEPARTING FROM AN AIRPORT USING STANDARD AIR TRAFFIC PROCEDURES; (B) DEPARTMENT OF DEFENSE, LAW ENFORCEMENT, OR AEROMEDICAL FLIGHT OPERATIONS THAT ARE IN CONTACT WITH ATC. THOSE WHO MEET ANY OF THE FOLLOWING CRITERIA MAY APPLY FOR A WAIVER TO THESE RESTRICTIONS: (A) FOR OPERATIONAL PURPOSES OF THE VENUE INCLUDING THE TRANSPORTATION OF EQUIPMENT OR OFFICIALS OF THE GOVERNING BODY; (B) FOR SAFETY AND SECURITY PURPOSES OF THE VENUE. INFORMATION REGARDING WAIVER APPLICATIONS CAN BE OBTAINED FROM THE FAA WEBSITE AT HTTP://WWW.FAA.GOV/ATS/ATA/WAIVER, OR BY CALLING 571-227-1322. 18 MAR 20:00 UNTIL UFN

A0285/04 - THE FOLLOWING RESTRICTIONS ARE REQUIRED DUE TO NAVAL AIR WARFARE CENTER WEAPONS DIVISION ACTIVATION OF W537. IN THE INTEREST OF SAFETY, ALL NON-PARTICIPATING PILOTS ARE ADVISED TO AVOID THE AREA. IFR TRAFFIC UNDER ATC JURISDICTION SHOULD ANTICIPATE CLEARANCE AROUND THE ABOVE AREA. CONTROL AREA 1176 WILL NOT BE AVAILABLE. CONTROL AREA 1155 WILL NOT BE AVAILABLE FOR OCEANIC TRANSITION. SFC UNL 08 JUL 20:00 UNTIL 08 JUL 23:59

A0355/01 - AIRWAY V514-538 TWENTYNINE PALMS (TNP) VORTAC, CA TO GOFFS (GFS) VORTAC, CA MEA 12,000. TWENTYNINE PALMS (TNP) VORTAC, CA MCA V514-538 10200NE. WIE UNTIL UFN

A0356/01 - AIRWAY V458 JULIAN (JLI) VORTAC, CA TO KUMBA INT, CA, MOCA 7700. WIE UNTIL UFN

A0357/01 - AIRWAY V66-458 IMPERIAL (IPL) VORTAC, CA TO KUMBA INT, CA, MOCA 4100. WIE UNTIL UFN

FDC 3/9431 - FI/T AIRWAY ZLA ZSE ZOA Q-7 JINMO WPT, WA TO AVENAL (AVE) VORTAC, CA, FLIGHT PLANNING ONLY AUTHORIZED SOUTHBOUND FL390 AND ABOVE, FLIGHT PLANNING NORTHBOUND NA. WIE UNTIL UFN

FDC 3/9434 - FI/T AIRWAY ZLA ZSE ZOA Q-9 SUMMA WPT, WA TO DERBB INT, CA, FLIGHT PLANNING ONLY AUTHORIZED SOUTHBOUND FL390 AND ABOVE, FLIGHT PLANNING NORTHBOUND NA. WIE UNTIL UFN

FDC 3/9438 - FI/T AIRWAY ZLA ZSE ZOA Q-11 PAAGE WPT, WA TO LOS ANGELES (LAX) VORTAC, CA, FLIGHT PLANNING ONLY AUTHORIZED SOUTHBOUND FL390 AND ABOVE, FLIGHT PLANNING NORTHBOUND NA. WIE UNTIL UFN

FDC 4/5471 - CA.. POINT MUGU NAS, CA. RADIATION HAZARD TO AIRCRAFT EXISTS WITHIN A 1.5 NM RADIUS OF 340555N/1190700W. THE AREA IS HOT CONTINIOUSLY FROM SFC TO 8000 FT AGL. AIRCRAFT WISHING TO TRANSIT THE AREA SHOULD CONTACT THE APPROPRIATE ATC AGENCY FOR THE STATUS OF THE AREA PRIOR TO ENTRY OR TRANSIT. WIE UNTIL UFN

FDC 4/6438 - NV.. FLIGHT RESTRICTION, MORMON MESA, NV. EFFECTIVE IMMEDIATELY UNTIL FURTHER NOTICE. PURSUANT TO 14 CFR SECTION 91.137(A)(2) TEMPORARY FLIGHT RESTRICTIONS ARE IN EFFECT WITHIN A 5 NAUTICAL MILE RADIUS OF 365816N/1143942W AND THE MORMON MESA /MMM/ VORTAC 288 DEGREE RADIAL AT 022 NAUTICAL MILES AT AND BELOW 8000 FEET MSL TO PROVIDE A SAFE ENVIRONMENT FOR AIRCRAFT RECOVERY. COL. RESNIK, TELEPHONE 702-652-9080, IS IN CHARGE OF ON SCENE EMERGENCY RESPONSE ACTIVITIES. RENO /RNO/ AFSS, TELEPHONE 775-784-5048, IS THE FAA COORDINATION FACILITY. WIE UNTIL UFN

FDC 4/6439 - AZ.. FLIGHT RESTRICTION, JACOB LAKE, AZ. EFFECTIVE IMMEDIATELY UNTIL FURTHER NOTICE. PURSUANT TO 14 CFR SECTION 91.137(A)(2) TEMPORARY FLIGHT RESTRICTIONS ARE IN EFFECT WITHIN A 5 NAUTICAL MILE RADIUS OF 364535N/1121740W AND THE PAGE /PGA/ VOR/DME 243 DEGREE RADIAL AT 042.1 NAUTICAL MILES AT AND BELOW 11000 FEET MSL TO PROVIDE A SAFE ENVIRONMENT FOR THE /JACOB LAKE/ FIRE FIGHTING ACFT. THE U.S.F.S, TELEPHONE 505-842-3473 OR FREQ.135.6, IS IN CHARGE ON SCENE EMERGENCY RESPONSE ACTIVITIES. PRESCOTT /PRC/ AFSS, TELEPHONE 928-778-7810, IS THE FAA COORDINATION FACILITY. WIE UNTIL UFN

6 – St. Maarten (TNCM)

  • ATIS: As ATC Position fill in “Juliana <your position>” e.g. “Juliana Tower”
    TL: FL065 TA: 5,000 ft
  • Sectorfile: The use of the official San Juan CTR Sectorfile is recommend, but not compulsory.
  • The TNCM Charts ready (digital or printed)

 FOR LANDING RWY NEVER USE 27, ONLY 09

Approach: The Approach Control is provided by Juliana Approach or if offline by TJZS_CTR. For procedural control only a VOR approach is available. So the preferred way is to give vectors for visual. Therefore you should vector the inbound Aircrafts on a 15nm final at 3000ft on rwy hdg (095), and let them "report when airfield in sight". If they still dont have it sin sight on a 8nm final, give them a descend to 2000ft, to bring them under the ceiling. As soon as they report the field in sight, you should clear them for the Visual Approach.

Departure: For departure a special clearance is necessary cause of the high elevation behind the rwy. Therefore with the IFR ATC clearance the following should be assigned: "Cleared to XXXX ... as filed. When airborne turn immediately right hdg 140, and maintain 3000ft. Sqwk XXXX." Please be sure the Pilot made a correct readback (and has understood the clearence)

VFR: VFR shall be handled as normal. In Princess Juliana only right hand traffic patterns should be assigned.