ZLA Logo
Who's Online
Online Controllers Flights to/from ZLA

Departures (16)

Callsign Dep Arr Status ETA
PAA25 KLAX LFPG Enroute 0735
NWA41 KLAX PHNL Enroute 1339
SWR41G KLAX LSZH Enroute 1625
AAL1041 KLAX KDFW Enroute 0744
BAW28F KLAX EGLL Enroute 1523
AAL1061 KLAX KDFW Enroute 0742
FIN2 KLAX EFHK Enroute 1702
N28ZA KLAX KSAN Enroute 2317
AAL134 KLAX EGLL Enroute 2250
DAL1425 KLAX KLAS Enroute 1610
QFA12 KLAX YSSY Enroute 1915
FFT1142 KLAX KSLC Enroute 1808
AAL71 KLAX KDFW Enroute 1600
UAL1170 KLAX PHNL Enroute 1600
DAL443 KLAX PHNL Enroute 1600
SJX1 KLAX RCTP Enroute 1600

Arrivals (9)

Callsign Dep Arr Status ETA
SCG8891 YBBN KLAX Enroute 1334
DLH452 EDDM KLAX Enroute 1914
DAL284 RKSI KLAX Enroute 1749
LAN600 SPJC KLAX Enroute 1209
SWA2651 KOAK KLAX Enroute 1600
AAL1408 KPHX KLAX Enroute 1655
B78X KSFO KLAX Enroute 0110
SWA1245 KRNO KLAX Enroute 1600
AAL3130 KLAS KLAX Enroute 2010

Los Angeles (SoCal) 25

Arrivals (1)

Callsign Dep Arr Status ETA
FDX394 KAUS KONT Enroute 1542

Empire (SoCal) 1

Departures (5)

Callsign Dep Arr Status ETA
AAL69 KSAN RJTT Enroute 1703
DAL2378 KSAN KOAK Enroute 1625
N2RF KSAN KFAT Enroute 1600
ASA220 KSAN KPHX Enroute 1600
UAL10 KSAN KFAT Enroute 1600

Arrivals (6)

Callsign Dep Arr Status ETA
UAL1835 KDEN KSAN Enroute 1504
FDX537G KPHX KSAN Enroute 0250
AAL1950 KPHX KSAN Enroute 2326
N28ZA KLAX KSAN Enroute 2317
DAL1974 PHOG KSAN Enroute 1433
UAL696 SKBO KSAN Departing

San Diego (SoCal) 11

Departures (5)

Callsign Dep Arr Status ETA
BAW4LV KLAS EGLL Enroute 1356
SWA450 KLAS KDEN Enroute 1726
N510CX KLAS KASE Enroute 0631
AAL3130 KLAS KLAX Enroute 2010
N125RH KLAS KASE Enroute 1127

Arrivals (3)

Callsign Dep Arr Status ETA
FHA9145 NTAA KLAS Enroute 1213
AAY1712 KBOI KLAS Enroute 1359
DAL1425 KLAX KLAS Enroute 1610

Las Vegas 8
  • Flights To/From ZLA: 45
  • Flights in ZLA Airspace: 23
  • Controller Schedule

    December 15th, 2025

    Socal Approach (West)
    Anthony Ferrando

    Session with ER

    1630 - 1800 PST / 0030 - 0200 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?"