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

Departures (10)

Callsign Dep Arr Status ETA
DAL9921 KLAX YSSY Enroute 0531
FIN2 KLAX EFHK Enroute 0427
VIR8Y KLAX EGLL Enroute 0720
UAL248 KLAX PHNL Enroute 0910
DAL287 KLAX MMSD Enroute 0019
SWA5522 KLAX KSAN Enroute 1600
DAL2272 KLAX KSFO Enroute 1600
UAL617 KLAX KSFO Enroute 1600
BAW164 KLAX EGLL Enroute 1600
UAL2603 KLAX KSFO Enroute 1600

Arrivals (21)

Callsign Dep Arr Status ETA
PAL921 RPLL KLAX Enroute 1158
EWG9547 BKPR KLAX Enroute 1145
DLH452 EDDM KLAX Enroute 1310
QTR58X OTHH KLAX Enroute 1807
BOX474 EDDF KLAX Enroute 1800
BAW269 EGLL KLAX Enroute 1621
SWA421 KMDW KLAX Enroute 1228
DAL1451 KATL KLAX Enroute 1217
DAL1305 KMSP KLAX Enroute 1343
BOX587 ZGSZ KLAX Enroute 1739
QTR8555 NZAA KLAX Enroute 0831
JAL16 RJTT KLAX Enroute 1703
AAL4916 KIAH KLAX Enroute 1057
AAL135 EGLL KLAX Departing
SWA587 KPHX KLAX Enroute 1144
CKS225 KCVG KLAX Departing
QTR7358 LFPG KLAX Enroute 1228
UAL2420 KABQ KLAX Enroute 1104
SWA1863 KPHX KLAX Enroute 0348
SWA4776 KSFO KLAX Enroute 1600
ASA1214 KSEA KLAX Enroute 1600

Los Angeles (SoCal) 31

Departures (2)

Callsign Dep Arr Status ETA
SWA504 KONT KDAL Arriving
FFT2232 KONT KLAS Enroute 1600

Arrivals (3)

Callsign Dep Arr Status ETA
UPS2928 KSDF KONT Enroute 1212
UPS983 KBFI KONT Enroute 1231
SKW6508 KPHX KONT Enroute 1227

Empire (SoCal) 5

Departures (11)

Callsign Dep Arr Status ETA
JAL65 KSAN RJAA Enroute 0325
AMX141 KSAN MMMX Enroute 0414
DAL832 KSAN KSEA Enroute 1651
JBU6942 KSAN KSFO Enroute 1600
ASA1175 KSAN KSEA Enroute 1404
NKS1827 KSAN KSJC Enroute 1635
DAL411 KSAN KDEN Enroute 1229
N69P KSAN KSLC Enroute 1658
UAL320 KSAN KDEN Enroute 0752
ASA1006 KSAN KGEG Enroute 1418
UAL777 KSAN KIAH Enroute 1600

Arrivals (12)

Callsign Dep Arr Status ETA
DAL2533 KSEA KSAN Enroute 1212
DAL900 KLAS KSAN Enroute 1600
UAL531 KDEN KSAN Enroute 1310
N110BW KCOS KSAN Enroute 1238
SWA5522 KLAX KSAN Enroute 1600
N555DT KSAN Enroute 0025
UAL430 KPHX KSAN Enroute 2139
KLM2621 KDEN KSAN Enroute 1600
CXPRP KSAN Enroute 1600
N1378 KSAN Enroute 1600
DAL2412 KPHX KSAN Enroute 1155
SWA464 KDEN KSAN Enroute 1600

San Diego (SoCal) 23

Departures (3)

Callsign Dep Arr Status ETA
SWA39 KLGB KLAS Enroute 0403
N60US KSNA MMSD Enroute 1313
DAL101 KSNA KJAC Enroute 1600

Coast (SoCal) 3

Departures (6)

Callsign Dep Arr Status ETA
SWA2636 KBUR KLAS Enroute 1839
NKS1441 KBUR KLAS Enroute 1419
SWA1570 KBUR KSMF Enroute 1320
ASA1052 KBUR KSEA Enroute 1445
NKS1766 KBUR KLAS Enroute 1519
N315TS KVNY KLAS Enroute 1600

Arrivals (1)

Callsign Dep Arr Status ETA
PTI737 VHHH KVNY Enroute 1209

Burbank (SoCal) 7

Arrivals (2)

Callsign Dep Arr Status ETA
CGAMN KSDL KPSP Enroute 1600
N35CZ KSDL KPSP Enroute 1700

Palm Springs (SoCal) 2

Departures (9)

Callsign Dep Arr Status ETA
FFT4116 KLAS KCVG Enroute 0341
HAL5 KLAS PHNL Enroute 1006
KAL006 KLAS RKSI Enroute 1142
SWA2932 KLAS KAUS Arriving
DAL900 KLAS KSAN Enroute 1600
NKS1140 KLAS KSJC Enroute 1327
ASA422 KLAS KSEA Enroute 1528
AAL605 KLAS KDEN Enroute 1244
JANET68 KLAS KSLC Enroute 1600

Arrivals (10)

Callsign Dep Arr Status ETA
UAL6299 KIAD KLAS Enroute 1411
JBU711 KJFK KLAS Enroute 1414
SWA187 KHOU KLAS Enroute 1910
SWA2636 KBUR KLAS Enroute 1839
NKS1441 KBUR KLAS Enroute 1419
SWA39 KLGB KLAS Enroute 0403
N12215 KBJC KHND Enroute 1706
FFT2232 KONT KLAS Enroute 1600
NKS1766 KBUR KLAS Enroute 1519
N315TS KVNY KLAS Enroute 1600

Las Vegas 19
  • Flights To/From ZLA: 90
  • Flights in ZLA Airspace: 37
  • Controller Schedule

    July 16th, 2025

    Socal Approach (Combined)
    Mohammad Mirza

    Session with AT

    1400 - 1500 PDT / 2100 - 2200 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!