ZLA Logo
Who's Online
Online Controllers

No controllers online

Flights to/from ZLA

Departures (20)

Callsign Dep Arr Status ETA
DAL480 KLAX PHNL Enroute 0216
NDF1MX KLAX BGGH Enroute 2239
ACA786 KLAX CYYZ Enroute 2030
DAL615 KLAX MMUN Enroute 2052
UAE2 KLAX OMDB Enroute 0845
UAL2184 KLAX KIAD Enroute 2026
AAL31 KLAX PHNL Enroute 0343
N757AG KLAX KDCA Enroute 2242
N301AZ KLAX KSAT Enroute 2048
UAL1905 KLAX KSFO Enroute 1355
AAL3241 KLAX KBNA Enroute 2301
FFL1201 KSMO KPAE Enroute 0644
DAL986 KLAX KAUS Arriving
KAL018 KLAX RKSI Enroute 0800
AAL2129 KLAX KMIA Enroute 0408
N75MG KLAX KJFK Enroute 0239
ACA794 KLAX CYYZ Enroute 2015
AAL118 KLAX KJFK Enroute 1600
AAL3169 KLAX KMIA Enroute 1600
UAL839 KLAX YSSY Enroute 1950

Arrivals (23)

Callsign Dep Arr Status ETA
DLH452 EDDM KLAX Enroute 0819
DAL12 YMML KLAX Enroute 0155
FIN1 EFHK KLAX Enroute 0535
BOX748 VHHH KLAX Enroute 0544
BAW21B EGLL KLAX Enroute 0855
VIR7B EGLL KLAX Enroute 0611
DAL24C EHAM KLAX Enroute 0737
UAE888 EDDM KLAX Enroute 1125
UAL783 CYYZ KLAX Enroute 1138
AFR28 LFPG KLAX Enroute 1005
DAL392 KDCA KLAX Enroute 0658
WAT6783 KSEA KLAX Enroute 0334
MSR983 HECA KLAX Enroute 1058
CPA88 VHHH KLAX Enroute 0843
UAL2808 KLAS KLAX Enroute 0948
UAL2238 KEWR KLAX Enroute 1201
FDX756 KLBB KLAX Enroute 0703
FDX79 PHNL KLAX Enroute 1600
UAL2191 KEWR KLAX Departing
DAL500 KATL KLAX Departing
FFT3308 KSFO KLAX Enroute 0841
SWA1200 KLAS KLAX Enroute 2324
UAL1638 KDEN KLAX Enroute 1600

Los Angeles (SoCal) 43

Departures (1)

Callsign Dep Arr Status ETA
UPS1TF KONT KMEM Enroute 2041

Empire (SoCal) 1

Departures (8)

Callsign Dep Arr Status ETA
DLH467 KSAN EDDM Enroute 2102
DAL21V KSAN MSLP Enroute 2113
DAE5496 KSAN SPJC Enroute 0759
SKW225 KSAN KSLC Enroute 0628
TWY295 KSAN KTVL Enroute 0658
EJA990 KSAN KFLL Enroute 0024
UAL1492 KSAN KLAS Enroute 0437
SUR5186 KSAN KSFO Enroute 1600

Arrivals (5)

Callsign Dep Arr Status ETA
BAW82P EGLL KSAN Enroute 0859
AAL2131 KORD KSAN Enroute 0543
SWA2050 KDAL KSAN Departing
DAL560 KATL KSAN Enroute 0616
PRWYW KORL KMYF Departing

San Diego (SoCal) 13

Departures (8)

Callsign Dep Arr Status ETA
SWA1883 KSNA KDEN Enroute 0555
UAL1766 KSNA KSFO Enroute 1509
EJA27 KSNA KSFO Enroute 1349
SWA936 KSNA KDEN Enroute 0426
EJA339 KSNA KASE Enroute 0731
N221S KLGB KVNY Enroute 1010
FFT4372 KSNA KDEN Enroute 1600
MXY801 KSNA KLAS Enroute 1600

Arrivals (2)

Callsign Dep Arr Status ETA
WAT7176 KFAT KSNA Enroute 1600
DAL1857 KDTW KSNA Enroute 0721

Coast (SoCal) 10

Departures (1)

Callsign Dep Arr Status ETA
VQBXG KVNY KMIA Enroute 2106

Arrivals (3)

Callsign Dep Arr Status ETA
N19VV KDEN KVNY Enroute 0542
SWA3992 KSMF KBUR Enroute 0946
N221S KLGB KVNY Enroute 1010

Burbank (SoCal) 4

Departures (7)

Callsign Dep Arr Status ETA
DAL5789 KLAS KJFK Enroute 2053
AAY46 KLAS KMFE Enroute 2027
SWA169 KLAS MMUN Enroute 2205
UAL2808 KLAS KLAX Enroute 0948
SWA267 KLAS KDEN Enroute 1131
DAL1659 KLAS KSLC Enroute 1600
SWA1200 KLAS KLAX Enroute 2324

Arrivals (10)

Callsign Dep Arr Status ETA
KLM635 EHAM KLAS Enroute 0714
DAL2905 KSEA KLAS Enroute 0619
EJA243 KAUS KLAS Enroute 0643
UAL1492 KSAN KLAS Enroute 0437
UAL1020 KSFO KLAS Enroute 1313
EJA305 KSJC KLAS Enroute 1259
SPJ145 KPHX KLAS Enroute 1600
AXI562 EGBB KLAS Enroute 0744
SWA1943 KTPA KLAS Departing
MXY801 KSNA KLAS Enroute 1600

Las Vegas 17

Arrivals (1)

Callsign Dep Arr Status ETA
A1008 KFFO KLSV Enroute 0701

Nellis 1
  • Flights To/From ZLA: 89
  • Flights in ZLA Airspace: 26
  • Controller Schedule

    November 21st, 2026

    Lindbergh Tower
    Zakaria Alsharif

    Session with RR

    1700 - 1830 PST / 0100 - 0230 Zulu

    Los Angeles Tower
    Matthew Oswald

    Session with LL

    1700 - 1830 PST / 0100 - 0230 Zulu

    The Art of the Timely Handoff

    As a controller, one of the easiest things you can do to improve your life and that of your fellow controllers is to work on timely handoffs. Nearly every controller will find him or herself guilty of holding onto an aircraft too long. The result can range from delays at the runway to airspace busts or go-arounds, but it is almost always bad for everyone involved.

    So, when should you hand an aircraft off to the next controller? As soon as you no longer need to talk to the aircraft. It really is as simple as that. If there is nothing more you anticipate needing to say to a pilot, hand them off to the next controller or approve a frequency change if there’s not a “next” controller.

    Let us look at a couple of practical examples, starting with LA Ground.

    LA Ground

    As a ground controller, your primary mission is the safe and efficient movement of aircraft around the airport. For our purposes, that means not crashing airplanes into one another, and getting them to the correct location on the airport. The biggest opportunity you will have to elevate your handoffs while working LA Ground is when aircraft are taxiing from Terminals 4 through 8 to Runway 25R.

    First and foremost, make sure the pilot is on the correct taxiway and headed in the correct direction (the green arrow in the diagram below). Pilots may be unfamiliar with the field or get disoriented, so it is important to make sure they’re going where you want them to go and that they won’t get lost.

    Secondly, you want to make sure that there are no conflicts with other aircraft, which would most likely take the form of an aircraft coming out of the “Box” or one of the cargo/GA pads north of the 25R departure end (the orange boxes). Absent any potential conflicts from those areas, there is no reason you shouldn’t advise the pilot to contact Tower (or the controller staffing that position) as the aircraft approaches C5 (the yellow circle) or, at the latest, C3 (the red circle).

    146568dc7d5353afb3c4a6f9eb85811307432817.png

    There are numerous operational advantages for all parties involved. As the Ground controller, you relieve yourself of the burden of remembering to hand off the aircraft later. Anyone who has received an annoyed transmission from a pilot or message from a Tower controller can relate to this. Additionally, pilots may switch to Tower on their own. This is quite common in the real world but can result in confusion when on VATSIM.

    From the pilot’s perspective, an early handoff makes better use of their time. It is also important to remember that a handoff isn’t instantaneous. The pilot’s workload may not allow for them to switch over immediately, so build in time for that to happen.

    Additionally, by giving the Tower controller (or the radar controller providing Tower services) more time with the aircraft, you open up a wealth of options: intersection departures, takeoff clearances without the aircraft coming to a stop, and more.

    Now let us look at a radar example but stay in the area of KLAX.

    SoCal Departure

    Working a departure position (be it sectorized or as part of a larger area of responsibility) is an excellent example of both needing a timely handoff from Tower (remember Tower controllers: as soon as you see the altitude block increment, ship ‘em to Departure!) and wanting to ensure a timely handoff to Center. Let’s look at everyone’s favorite example, the ORCKA 5 departure out of KLAX.

    2017900fcc4927233cd785e0ddf698d2c0960559.png

    As the Departure controller, you’re going to still be focused on the same two tasks as earlier: the safe and efficient movement of the aircraft. In this instance, we of course want to prevent loss of separation – that’s our top priority. Secondly, we want to make sure the traffic departs the terminal area efficiently and gets headed toward its ultimate destination. No one on the ORKCA5 is looking to fly heading 251 or 236 a minute longer than they must.

    After establishing radar contact with the departing aircraft, your first instruction will likely involve canceling the restriction that they stop their climb at 5,000 feet. This is accomplished either through “climb and maintain one-three thousand” or “climb via the ORCKA Five departure” if you still need compliance with the published crossing restrictions.

    The next instruction (provided you didn’t have to correct an erroneous pilot) will likely be the left turn back toward KLIPR. This instruction is usually provided as the aircraft is climbing through 5,000 feet, which serves two purposes. One, by observing the climb through 5,000 feet, you’ve verified the aircraft has correctly canceled the restriction they received on the ground to level off at 5,000. Secondly, at that point they are over halfway to their vertical goal of crossing KLIPR at or above 10,000 feet and can start the turn.

    Looking ahead on the SID, you’ll notice things progress quickly and if left unmonitored, an aircraft climbing via the SID can climb out of your airspace in little time. So, let us review our checklist:

    • Is the aircraft clear of conflict? Is there going to be a loss of separation?
    • Is the aircraft complying with your vertical instruction to climb above 5,000 feet?
    • Is the aircraft complying with your lateral instruction to make the LEFT TURN direct KLIPR?

    If these criteria are met, it’s time to initiate the handoff to the next controller. Even though your airspace goes all the way up to 13,000 feet, you gain nothing by holding onto the aircraft. And you run the very real risk of forgetting about the aircraft and a) having it level off at 13,000, or b) having it bust through your airspace if it’s climbing via the SID (note: the ORCKA5 has a top altitude of FL230).

    Adding to the delay in the handoff from a pilot’s perspective of changing frequencies, you also now need to consider the delay in the next controller seeing your handoff. By building in this extra time, you give everyone more breathing room while also freeing up your resources for the next pilot who just took off. And you never know, that next one could be someone trying a right-turn off the deck toward KLIPR – you’ll be glad you made things easier on yourself.

    Conclusion

    Ultimately, there is no reason to hold onto an aircraft until they are right at the end of your airspace or jurisdiction. You do not increase your level of interaction with the traffic, and you do not increase safety or efficiency. All you risk doing is causing undue delays or worse, a loss of separation. Keep in mind, this is a lesson that applies at every controller position, from Ground to Center, and most controllers would benefit from being more proactive with their handoffs.