ZLA Logo
Who's Online
Online Controllers

No controllers online

Flights to/from ZLA

Departures (19)

Callsign Dep Arr Status ETA
SJX1 KLAX RCTP Enroute 1454
UAL027 KLAX VHHH Enroute 1608
DAL65 KLAX EGLL Enroute 1419
KLM602 KLAX EHAM Enroute 1550
THY12E KLAX LTFM Enroute 2227
BAW28F KLAX EGLL Enroute 1825
DAL67 KLAX EGLL Enroute 1428
BAW4E KLAX EGLL Enroute 2115
CFG3762 KLAX EDDV Enroute 2157
UAL1106 KLAX KLAS Enroute 1600
QTR39A KLAX OTHH Enroute 1600
DAL1330 KLAX KDCA Enroute 1705
JBU100 KLAX KFLL Enroute 1600
DAL1429 KLAX KDEN Enroute 0057
AAR2053 KLAX RKSI Enroute 2356
UAL1339 KLAX KDEN Enroute 0222
JBU588 KLAX KBOS Enroute 1759
UAL839 KLAX YSSY Enroute 1526
AAL2 KLAX KJFK Enroute 1439

Arrivals (16)

Callsign Dep Arr Status ETA
JAL99KE RJAA KLAX Enroute 2314
DLH452 EDDM KLAX Enroute 0122
QR739 OTHH KLAX Enroute 0935
KLM601 EHAM KLAX Enroute 0325
AAL735 KLAS KLAX Enroute 1600
DLH456 EDDF KLAX Enroute 0335
UAL935 EGLL KLAX Enroute 0325
SAS655A ENGM KLAX Enroute 0246
PAL112 RPLL KLAX Enroute 0211
CSG2537 PANC KLAX Enroute 2311
UAL1044 KORD KLAX Enroute 2325
DAL1AM PHNL KLAX Enroute 2130
UPS6020 KONT KLAX Enroute 0307
CPA882 VHHH KLAX Departing
UAL153N KLEX KLAX Departing
SWA279 KPHX KLAX Enroute 1600

Los Angeles (SoCal) 35

Departures (1)

Callsign Dep Arr Status ETA
UPS6020 KONT KLAX Enroute 0307

Empire (SoCal) 1

Departures (1)

Callsign Dep Arr Status ETA
DLH6TA KSAN EDDM Enroute 1850

Arrivals (1)

Callsign Dep Arr Status ETA
KLM639 EHAM KSAN Departing

San Diego (SoCal) 2

Departures (2)

Callsign Dep Arr Status ETA
UAL1543 KSNA KLAS Enroute 2326
SWA1080 KLGB PHNL Enroute 2225

Coast (SoCal) 2

Arrivals (1)

Callsign Dep Arr Status ETA
N876J KJAC KVNY Enroute 2335

Burbank (SoCal) 1

Departures (6)

Callsign Dep Arr Status ETA
AAL735 KLAS KLAX Enroute 1600
EWG83T KLAS KDEN Enroute 0041
UAL397 KLAS KSFO Enroute 1929
UAL33T KLAS KSFO Enroute 1903
LSA7FL KLAS LFLL Enroute 0120
SWA3302 KLAS KDEN Enroute 1600

Arrivals (5)

Callsign Dep Arr Status ETA
KLM635 EHAM KLAS Enroute 0414
KLM629 EHAM KLAS Enroute 0414
EDW2M LSZH KLAS Enroute 0000
UAL1106 KLAX KLAS Enroute 1600
UAL1543 KSNA KLAS Enroute 2326

Las Vegas 11

Departures (1)

Callsign Dep Arr Status ETA
UAL2638 KSBA KDEN Enroute 2250

Santa Barbara 1

Departures (1)

Callsign Dep Arr Status ETA
PEAK26 KOXR 7CA4 Enroute 2019

Point Mugu 1
  • Flights To/From ZLA: 54
  • Flights in ZLA Airspace: 19
  • Controller Schedule

    November 2nd, 2025

    Los Angeles Tower
    William Collister

    Session with AK

    1330 - 1500 PST / 2130 - 2300 Zulu

    Socal Approach (West)
    Jerome Sudhakar

    Session with SJ

    1600 - 1730 PST / 0000 - 0130 Zulu

    VFR Operations

    DATE VERSION CONTACT
    2024-12-16 2.10 Facility Advisory Board

    Los Angeles ARTCC VFR Operations

    Introduction and Purpose

    This document is standard operating procedure for VFR operations throughout ZLA. Refer to VFR Clearances section of the STM for more information on VFR departures.

    Facility SOPs may conflict. In the event of a conflict, follow the facility SOP.

    VFR Radar Services

    Radar services are always provided for aircraft operating within Class C and Class B airspace. (7110.65 7-8-2, 7-9-2.)

    Radar services for aircraft outside of Class C or Class B airspace are provided on a workload-permitting basis. (7110.65 7-8-2, 7-9-2.)

    The pilot may request radar service termination once outside of Class C or Class B airspace. ATC may terminate radar service if workload precludes providing radar services outside of Class C or B airspace.

    Radar services for aircraft operating within a TRSA are optional for pilots. When requested, provide TRSA radar service per 7110.65 7-7. ATC may terminate radar service once the aircraft leaves the TRSA (7110.65 7-7-7).

    Flight Plans

    Real-world VFR flight plans in the United States are not transmitted to air traffic control. They are sent to flight service stations for search and rescue purposes. VATSIM does allow pilots to file VFR fight plans; however, only filed remarks are retained in CRC.

    Therefore, when aircraft are to receive flight following, ATC must ask the pilot for the aircraft type and any other information required by this SOP.

    Aircraft not receiving flight following should not have a flight plan completed.

    If a pilot departing a Class C or Class B airport declines flight following on the ground, note "negative radar service" in the flight plan remarks. The pilot must still receive instructions as noted in this SOP. The radar controller will terminate radar service once the aircraft is outside of Class C or Class B airspace.

    Class D Airports

    • Flight Following: Aircraft departing Class D airports receive following only on pilot request. If flight following is requested by the pilot, use Class C procedures.
    • Flight Plan: No flight plan.
    • Clearance: There are no VFR instructions or clearances given by ground control. Pilots should call ground control stating direction of flight and ready to taxi with the current ATIS information.

    Class C Airports

    • Flight Following: Aircraft departing Class C airports receive flight following by default. It is required for all VFR departures while inside Class C airspace.
    • Flight Plan:
      • Aircraft type
      • Departure and arrival airports (The arrival airport is not necessary if the pilot will cancel once leaving the airspace.)
      • VFR cruise altitude
      • Discrete beacon code (squawk)
    • Clearance: Provide departure frequency and squawk. Include initial heading and/or altitude as required by SOP.
    • Notes: If the pilot does not want flight following, add "negative radar service" in the remarks. This will inform the radar controller to terminate radar service once the aircraft is outside of Class C airspace.
    Class B Airports
    • Flight Following: Aircraft departing Class B airports receive flight following by default. It is required for all VFR departures while in Class B airspace.
    • Flight Plan:
      • Aircraft type
      • Departure and arrival airports (The arrival airport is not necessary if the pilot will cancel once leaving the airspace.)
      • VFR cruise altitude
      • Discrete beacon code (squawk)
    • Clearance: Provide bravo clearance, departure frequency and squawk. Include initial heading and/or altitude as required by SOP.
    • Notes: If the pilot does not want flight following, add "negative radar service" in the remarks. This will inform the radar controller to terminate radar service once the aircraft is outside of Class B airspace.

    Class D Airports within a TRSA (PSP)

    • Flight Following: Optional - All VFR departures from PSP receive flight following unless the pilot declines (7110.65 7-7-7).
      • For all VFR aircraft departing PSP, use Class C procedures.
      • If the pilot declines, use Class D procedures.
    Closed Traffic at Class C or D Airports
    • Pilots should call requesting closed traffic and ready to taxi. No clearance is provided, only taxi instructions. No FP is used or filed. Pilots shall squawk VFR (1200) in the pattern by default.
    Closed Traffic at Class B Airports
    • Aircraft should be cleared to enter bravo airspace and assigned a squawk. After readback is correct, they should call when ready to taxi.
      • Example: "Cleared to enter San Diego Bravo airspace. Squawk 1234."
    • The flight plan for Class B closed traffic should only have aircraft type, a voice tag, and "VFR" in the altitude field. Avoid adding extra information.

    Example VFR Flight Plan for Flight Following

    bb4d0498e2e7e0f294dc9a759fea76a342b1691f.png

    VFR Practice Approaches

    • Class B, Class C, and TRSA Procedures:
      • Standard VFR separation services are provided.
      • Clear VFR aircraft using appropriate approach clearance phraseology except replace altitude assignment with "MAINTAIN VFR."
      • SCT and L30 TRACONs shall use these procedures.
    • Class D, E, and G Procedures:
      • No separation services are provided.
      • PHRASEOLOGY: "(Aircraft identification) MAINTAIN VFR, PRACTICE APPROACH APPROVED, NO SEPARATION SERVICES PROVIDED."
    • Missed approaches are not automatically authorized for VFR aircraft. (7110.65 4-8-11)
      • Prior to approach clearance or approval, the radar controller should ask the pilot to advise intentions. Example: "N123SP, how will this approach terminate?"