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

Departures (11)

Callsign Dep Arr Status ETA
QFA173 KLAX YBBN Enroute 1636
AUA82 KLAX LOWW Enroute 1833
CFG2081 KLAX EDDF Enroute 1832
ASA503 KLAX KSEA Enroute 0508
UAL551 KLAX KAUS Enroute 1619
JBU2885 KLAX KMIA Enroute 1726
AAL1977 KLAX KMIA Enroute 1920
CAO3106 KLAX ZBAA Arriving
AAL905 KLAX SKRG Enroute 2157
QFA007 KLAX YSSY Enroute 0503
SWA1345 KLAX KABQ Enroute 1600

Arrivals (21)

Callsign Dep Arr Status ETA
SVA041 OEJN KLAX Enroute 0148
LOT21 EPWA KLAX Enroute 0909
JBU2123 KJFK KLAX Enroute 0243
ASA866 PHNL KLAX Enroute 0021
ASA1267 MMSD KLAX Enroute 1600
ASA250 MMPR KLAX Enroute 0135
SPK286 KSEA KLAX Enroute 0141
WJA1696 CYVR KLAX Enroute 0218
DAL440 NZAA KLAX Enroute 2130
SWA1282 KDAL KLAX Enroute 0247
CKS369 PHNL KLAX Enroute 2338
DAL1445 KDFW KLAX Enroute 0138
MLISHS1 KAMA KLAX Enroute 0109
NKS561 KLAS KLAX Enroute 0358
NKS1545 KLAS KLAX Enroute 0227
SWA2819 KLAS KLAX Enroute 1524
FCY241 KMSP KLAX Enroute 1102
FDX1402 KATL KLAX Departing
CAL6 RCTP KLAX Departing
GLJM KONT KLAX Enroute 1600
ANZ6 NZAA KLAX Enroute 2202

Los Angeles (SoCal) 32

Departures (1)

Callsign Dep Arr Status ETA
GLJM KONT KLAX Enroute 1600

Arrivals (1)

Callsign Dep Arr Status ETA
TKK837 VHHH KONT Enroute 0112

Empire (SoCal) 2

Departures (6)

Callsign Dep Arr Status ETA
UAL1165 KSAN PHNL Enroute 2308
UAL2508 KSAN KSTL Enroute 1729
ASA579 KSAN KSEA Enroute 0645
SWA5230 KSAN KMSY Enroute 1841
WAT1812 KSAN KSFO Enroute 0232
FFT28P KSAN KPHX Enroute 1600

Arrivals (2)

Callsign Dep Arr Status ETA
DLH5Y EDDM KSAN Enroute 0609
ASA783 KPDX KSAN Enroute 1016

San Diego (SoCal) 8

Departures (2)

Callsign Dep Arr Status ETA
BOXER22 KSLI KLSV Enroute 1600
SWA763 KSNA MMPR Enroute 1600

Arrivals (4)

Callsign Dep Arr Status ETA
SWA1 KPHX KSNA Enroute 0134
B6179 KLAS KLGB Enroute 1600
DAL2151 KDTW KLGB Enroute 0351
SWA2640 KPHX KSNA Enroute 0209

Coast (SoCal) 6

Departures (2)

Callsign Dep Arr Status ETA
SWA2624 KBUR KSJC Enroute 0203
SWA2602 KBUR KLAS Enroute 0140

Arrivals (1)

Callsign Dep Arr Status ETA
SWA1150 KSJC KBUR Enroute 0414

Burbank (SoCal) 3

Departures (1)

Callsign Dep Arr Status ETA
SWA2129 KPSP KOAK Enroute 0446

Arrivals (2)

Callsign Dep Arr Status ETA
SWA1412 KDEN KPSP Enroute 1600
N1M KMDW KPSP Departing

Palm Springs (SoCal) 3

Departures (7)

Callsign Dep Arr Status ETA
FFT2136 KLAS KDFW Enroute 1703
B6179 KLAS KLGB Enroute 1600
NKS486 KLAS KSEA Enroute 1600
NKS561 KLAS KLAX Enroute 0358
NKS1545 KLAS KLAX Enroute 0227
SWA1424 KLAS KSEA Enroute 1600
SWA2819 KLAS KLAX Enroute 1524

Arrivals (4)

Callsign Dep Arr Status ETA
ASA1366 KPDX KLAS Enroute 0204
SWA2602 KBUR KLAS Enroute 0140
NWA1193 KDTW KLAS Departing
SWA1404 KSMF KLAS Enroute 0106

Las Vegas 11

Departures (2)

Callsign Dep Arr Status ETA
MNF50 KLSV LKPR Enroute 2243
AFS1000 KLSV KVPS Enroute 1710

Arrivals (1)

Callsign Dep Arr Status ETA
BOXER22 KSLI KLSV Enroute 1600

Nellis 3
  • Flights To/From ZLA: 68
  • Flights in ZLA Airspace: 22
  • Controller Schedule

    May 25th, 2022

    No sessions found for selected date

    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.