ZLA Logo
Who's Online
Online Controllers

No controllers online

Flights to/from ZLA

Departures (18)

Callsign Dep Arr Status ETA
UAL801 KLAX VHHH Enroute 0751
DLH9AG KLAX EDDF Enroute 0745
SWR41 KLAX LSZH Enroute 1200
N207BZ KLAX MPTO Enroute 0823
KAL012 KLAX RKSI Enroute 1600
DAL7 KLAX RJTT Enroute 1508
DAL377 KLAX KDEN Enroute 1616
DAL20 KLAX KDEN Enroute 1555
DAL2828 KLAX KDEN Enroute 1653
CFC383 KLAX KDEN Enroute 1642
AAL340 KLAX KMIA Enroute 1036
AAL73 KLAX YSSY Enroute 1855
SAS932 KLAX EKCH Enroute 1524
AAL2061 KLAX KSFO Enroute 1648
THY10 KLAX LTFM Enroute 1340
CAL5133 KLAX RJBB Enroute 0818
DAL515 KLAX KATL Enroute 0825
BAW283 KLAX EGLL Arriving

Arrivals (13)

Callsign Dep Arr Status ETA
SVA041 OEJN KLAX Enroute 1833
AAL72 YSSY KLAX Enroute 1150
AAL172 YSSY KLAX Enroute 1300
UAL2318 PHNL KLAX Enroute 1323
DAL2103 KMSP KLAX Enroute 1531
AAL1719 CYVR KLAX Enroute 1704
UAE83M OMDB KLAX Enroute 0334
UAL2064 KSFO KLAX Enroute 1600
VIR7G EGLL KLAX Enroute 2159
SVA41 OEJN KLAX Departing
SWA4236 KPHX KLAX Enroute 2007
AFR26A LFPG KLAX Enroute 1545
UAL1190 KSFO KLAX Enroute 2203

Los Angeles (SoCal) 31

Departures (7)

Callsign Dep Arr Status ETA
CFG7WJ KSAN EDDF Enroute 0730
N78F KSAN KSQL Enroute 0247
LH467 KSAN EDDM Enroute 1925
AAL254 KSAN EDDM Enroute 2356
DAL5774 KSAN KSEA Enroute 2116
CMP850 KSAN MPTO Enroute 0308
A1 KNKX KCGX Enroute 1600

Arrivals (3)

Callsign Dep Arr Status ETA
SWA3105 KDAL KSAN Enroute 1541
RPV201 KSEA KSAN Enroute 1542
DAL263 KSJC KSAN Enroute 1600

San Diego (SoCal) 10

Departures (1)

Callsign Dep Arr Status ETA
AAY1586 KSNA KCOS Enroute 1608

Coast (SoCal) 1

Departures (1)

Callsign Dep Arr Status ETA
WAT5233 KPSP KELP Enroute 1250

Palm Springs (SoCal) 1

Departures (2)

Callsign Dep Arr Status ETA
DAL1 KLAS KDEN Enroute 1634
CMP253 KLAS MPTO Enroute 2119

Arrivals (1)

Callsign Dep Arr Status ETA
DAL1152 KDEN KLAS Enroute 1631

Las Vegas 3
  • Flights To/From ZLA: 46
  • Flights in ZLA Airspace: 14
  • Controller Schedule

    July 11th, 2025

    Lindbergh Tower
    William Collister

    Session with NS

    0930 - 1100 PDT / 1630 - 1800 Zulu

    Socal Approach (West)
    Akari King-Wright

    Session with NS

    1230 - 1330 PDT / 1930 - 2030 Zulu

    Socal Approach (Combined)
    Mohammad Mirza

    Session with LB

    1600 - 1700 PDT / 2300 - 0000 Zulu

    Socal Approach (Combined)
    Aaryan Khan

    OTS with NS

    1800 - 1930 PDT / 0100 - 0230 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?"