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

Departures (18)

Callsign Dep Arr Status ETA
QFA12 KLAX YSSY Arriving
AFR021 KLAX LFPG Enroute 0854
AFR028 KLAX NTAA Enroute 0534
TAM8087 KLAX SBGR Enroute 1131
UAL1591 KLAX KIAH Arriving
NWA6YF KLAX LTFM Enroute 1419
DAL7 KLAX RJTT Enroute 1154
QFA94 KLAX YMML Enroute 1711
CFG145 KLAX EDDF Enroute 1152
DLH66R KLAX EDDF Enroute 1153
AFR121 KLAX KJFK Enroute 1101
SKW4888 KLAX KSMF Enroute 2212
QXE2020 KLAX KPAE Enroute 1447
DAL2311 KLAX KSLC Enroute 1446
N525UP KLAX KAVX Enroute 1427
AFR23 KLAX LFPG Enroute 1600
EAG5502 KLAX SBGR Enroute 1600
FDX1526 KLAX KOAK Enroute 1600

Arrivals (26)

Callsign Dep Arr Status ETA
QTR52XA OTHH KLAX Enroute 1505
SIA3412 WSSS KLAX Enroute 1249
CES123 ZSPD KLAX Enroute 1204
KLM55 OMDB KLAX Enroute 1917
AAR204 RKSI KLAX Enroute 1238
NBT81B ENGM KLAX Enroute 1550
UAE2973 OMDB KLAX Enroute 1412
SAS146 ESSA KLAX Enroute 1712
AAR202 RKSI KLAX Enroute 1447
AA87 KDCA KLAX Enroute 1408
DAL791 CYYZ KLAX Enroute 1414
JBU1015 KDFW KLAX Enroute 0830
AAL1142 KORD KLAX Enroute 0032
UAL2343 KIAH KLAX Enroute 0256
UAL209D KIAH KLAX Enroute 1158
NWA1209 KMKE KLAX Enroute 1323
AAL1362 KPHX KLAX Enroute 1600
KAL9207 RKSI KLAX Enroute 1716
ETD2 OMAA KLAX Enroute 0109
AAL622 KJFK KLAX Enroute 1515
N525UP KLAX KAVX Enroute 1427
N154TS KACT KLAX Enroute 1235
ASA1143 KPDX KLAX Enroute 1349
AAL767A KPHX KLAX Enroute 0516
DAL5798 KPHL KLAX Departing
FDX9735 PANC KLAX Enroute 1600

Los Angeles (SoCal) 44

Arrivals (2)

Callsign Dep Arr Status ETA
UPS1042 KSLC KONT Enroute 1233
UPS921 KIAH KONT Enroute 1119

Empire (SoCal) 2

Departures (5)

Callsign Dep Arr Status ETA
SIA444 KSAN WSSS Enroute 1236
N923ES KSAN PHNL Enroute 1036
ASA1199 KSAN KSEA Enroute 1418
N171TR KCRQ KEUG Enroute 1553
UAL215 KSAN KDEN Enroute 1132

Arrivals (7)

Callsign Dep Arr Status ETA
KLM639 EHAM KSAN Enroute 1302
DLH4C EDDM KSAN Enroute 1646
SWA2022 PHNL KSAN Enroute 1017
SWA2083 KDEN KSAN Enroute 1100
SWA4189 KLAS KSAN Enroute 1343
SWA2784 KPHX KSAN Enroute 1324
SWA673 KDEN KSAN Enroute 1341

San Diego (SoCal) 12

Departures (1)

Callsign Dep Arr Status ETA
EJM81 KSNA KDVN Enroute 0313

Coast (SoCal) 1

Departures (1)

Callsign Dep Arr Status ETA
N316PR KVNY KLAS Enroute 2115

Arrivals (2)

Callsign Dep Arr Status ETA
ACL6698 KTVL KBUR Enroute 1600
VXP122 KRDM KBUR Enroute 1214

Burbank (SoCal) 3

Arrivals (1)

Callsign Dep Arr Status ETA
AAL423 KLAS KPSP Enroute 0704

Palm Springs (SoCal) 1

Departures (7)

Callsign Dep Arr Status ETA
UAL526 KLAS KEWR Enroute 0300
SWA4121 KLAS KMSP Enroute 0409
SWA2672 KLAS KTUS Enroute 1231
AAL423 KLAS KPSP Enroute 0704
BAW4LV KLAS EGLL Enroute 1600
SWA4189 KLAS KSAN Enroute 1343
JBU1488 KLAS KDEN Enroute 0825

Arrivals (5)

Callsign Dep Arr Status ETA
VIR155M EGLL KLAS Enroute 1230
N316PR KVNY KLAS Enroute 2115
UAL2339 KIAH KLAS Enroute 1249
CJN248 KSMF KLAS Enroute 1600
N64BV KAPA KLAS Enroute 2107

Las Vegas 12

Arrivals (1)

Callsign Dep Arr Status ETA
NTA18 KLSV KLSV Enroute 1600

Nellis 1
  • Flights To/From ZLA: 76
  • Flights in ZLA Airspace: 22
  • Controller Schedule

    May 24th, 2025

    Lindbergh Tower
    Daniel Que

    Session with CH

    1300 - 1430 PDT / 2000 - 2130 Zulu

    Los Angeles Tower
    Aneesh Reddy

    Session with ER

    1430 - 1600 PDT / 2130 - 2300 Zulu

    Socal Approach (West)
    Dylan Keetle

    Session with MX

    1430 - 1600 PDT / 2130 - 2300 Zulu

    Left Turn ORCKA

    LAX is one of the busiest airports on VATSIM, both for controllers and pilots. Since it is such a heavily trafficked airport on VATSIM and in the real world, there are many departure and arrival procedures that are used to expedite the flow of traffic. Of these departures, the ORCKA departure, is both very commonly included in flight plans, and prone to some mistakes. By writing this, I hope to clear up some confusion caused by the unique departure procedure and the cluttered plate.

    70a1b2aeae0b885ddb2017ae0886db7b18f2bc6a.PNG

    Let’s start by looking at the departure, shown here first using the FAA plate.

     

    Despite what the lines may appear to show, pilots must not proceed to KLIPR after crossing their runway’s respective RNAV fix.

    This is not the complete procedure, simply the first page. We can see on the bottom the plate that there is a second page for us to look at. Additionally, we should know that dotted lines on a procedure indicate what pilots should do during a Lost Communications scenario. The second page, which describes how to fly the departure in text, is much more enlightening than this first page. For the south complex (runways 25R and 25L) it says, “... cross DOCKR (25R) or HIPPR (25L) at or below 3000, then on heading 236 or as assigned by ATC,” and for the north complex (runways 24R and 24L) “...cross FABRA (24R) or DLREY (24L) at or below 3000, then on heading 251 or as assigned by ATC.”

    That last part seems to trip the most pilots up, “then on heading <> or as assigned by ATC.” This means that, if flying by hand, simply fly the heading on the departure until ATC gives you a turn direct to KLIPR, then resume the departure from there (on to KEGGS and so on). It seems far more often pilots let the FMC dictate where they go, which while not an issue generally can cause problems when programmed incorrectly. Specifically, with the deletion of “VECTORS” legs and the removal of discontinuities therein. In order for the FMC to properly fly the departure, it is imperative that the “VECTORS” leg be left intact. Such a leg will keep your airplane flying the correct heading until ATC gives you a turn.

    Let’s work through this with a scenario. I will be using the Zibo 737-800 mod for XPlane 11 as an example.

    You are N12345, flying from LAX to LAS. Clearance delivery has cleared you on the ORCKA5 departure, MISEN transition, climb via SID except maintain 5000. Loading the departure into the flight plan, you are greeted with this.

     

    4b236587da2295c20cfbc3aacbbcd01a1438e0c7.png

     

    As we can see, there is the 640’ crossing, from which we navigate to DOCKR at or below 3000. After, the “VECTOR” leg mentioned earlier is shown. It is absolutely imperative that pilots do not delete this leg. As shown, the vector leg is on a heading of 236, as published on the departure. The same is true for the north runways, but on a heading of 251.

    But what if your FMC does not have this VECTORS leg present? If after ensuring that there hasn’t been a mistake in loading the departure, and that your navdata is up to date and the leg still isn’t present, simply fly using heading. The two ways of doing this (with or without autopilot engaged) is to fly in LNAV mode until DOCKR and then switch to heading mode, or to use heading mode from the start. While the latter option does not legally fly the RNAV departure, it is fairly accurate for sim reasons, as real aircraft would not have this issue when loading the departure.

    You start up and taxi out to runway 25R. Tower tells you “N12345 RNAV DOCKR wind calm runway 25R cleared for takeoff.” Throttles go up, airspeed builds, and you takeoff. Per the departure “climb on heading 251 to 640 feet, then climb direct to cross DOCKR at or below 3000.” Up you go, passing through 640’ easily, and onto DOCKR.

    Contacting departure, the controller says “N12345 radar contact, altitude as reported, climb via ORCKA5 departure.” Now what? Simple, continue flying the departure. After DOCKR, begin the vectors leg, in this case on heading 236. The “climb via SID” part of the instruction simply means you can ignore the “except maintain 5000” from the initial clearance on the ground. To what altitude? FL230, shown on the bottom right of the Jeppesen chart and top middle of the FAA charts, complying with altitude restrictions. In short order, the controller will issue an instruction for you to rejoin the departure at KLIPR, either with another assigned heading or a vector directly to the fix.

    To briefly summarize, the ORCKA departure is frequently flown incorrectly, causing loss of separation issues at LAX. This can be attributed to some misinformation floating around online about deleting VECTORS legs in flight plans, and confusing charting on FAA departure plates. Ensure that the VECTORS leg is present in your FMC when loading the departure into the FMC. If it is not present, simply fly either manually or using the heading mode present in almost all autopilots manufactured in the last 70 years.

    I hope this has been informative, and I look forward to seeing you all in the virtual skies!