ZLA Logo
Who's Online
Online Controllers

No controllers online

Flights to/from ZLA

Departures (15)

Callsign Dep Arr Status ETA
PTI737 KLAX NZAA Enroute 1731
THY10 KLAX LTFM Enroute 0303
UAL320 KLAX KPIT Enroute 1649
AIE702 KLAX PHOG Enroute 0007
AAL2078 KLAX KDFW Enroute 1657
UAL1258 KLAX KSEA Enroute 1305
DAL494 KLAX KDTW Enroute 1847
DAL2980 KLAX KSEA Enroute 0449
CLX7756 KLAX ELLX Enroute 0201
DAL65 KLAX NZAA Arriving
PAL103 KLAX RPLL Enroute 0617
DAL2975 KLAX KPDX Enroute 1226
QTR99Y KLAX OTHH Enroute 2227
DAL2134 KLAX KLAS Enroute 1600
AAL136 KLAX EGLL Enroute 1600

Arrivals (20)

Callsign Dep Arr Status ETA
DAL40 YSSY KLAX Enroute 2327
DAL42 YSSY KLAX Enroute 2327
DLH453 EDDF KLAX Enroute 0411
BAW283 EGLL KLAX Enroute 0316
KAL011 RKSI KLAX Enroute 0248
CSN477 PANC KLAX Enroute 1054
UAL447 EGLL KLAX Enroute 0525
SAS931 EKCH KLAX Enroute 0236
DAL883 KDTW KLAX Enroute 0226
SIA12 RJAA KLAX Enroute 0431
KLM601 EHAM KLAX Enroute 1612
DLH9Y EDDF KLAX Enroute 2307
SHYAM KBUR KAVX Enroute 1600
VTHOT KBUR KAVX Enroute 1600
ASA1550 KSTS KLAX Enroute 1600
DAL1628 KSEA KLAX Enroute 1600
DAL456 KJFK KLAX Departing
N64264 KBUR KAVX Enroute 1600
N64181 KBUR KAVX Enroute 1600
NOV743 KBUR KAVX Enroute 1600

Los Angeles (SoCal) 35

Departures (6)

Callsign Dep Arr Status ETA
CAL023 KONT RCTP Enroute 2011
FDX455 KONT KMEM Enroute 1600
FDX1171 KONT KMEM Enroute 2356
DAL24W KONT KMEM Enroute 1600
FDX120 KONT KMEM Enroute 1600
FDX1280 KONT KMEM Enroute 1600

Empire (SoCal) 6

Departures (6)

Callsign Dep Arr Status ETA
DAL729 KSAN KATL Enroute 1730
ASA712 KSAN MMPR Enroute 2225
N5817F KSAN KBUR Enroute 1600
SWA830 KSAN KPHX Enroute 2203
DAL1177 KSAN KSLC Enroute 0406
AAL625 KSAN KPHX Enroute 1600

Arrivals (1)

Callsign Dep Arr Status ETA
BAW82P EGLL KSAN Enroute 0809

San Diego (SoCal) 7

Departures (1)

Callsign Dep Arr Status ETA
AAY1591 KSNA KBOI Enroute 0444

Arrivals (3)

Callsign Dep Arr Status ETA
ASA669 KSEA KSNA Enroute 0225
USA265 KDEN KSNA Enroute 0252
SWA26H KPVU KSNA Enroute 1600

Coast (SoCal) 4

Departures (6)

Callsign Dep Arr Status ETA
DAL1128 KBUR KJFK Enroute 2057
SHYAM KBUR KAVX Enroute 1600
VTHOT KBUR KAVX Enroute 1600
N64264 KBUR KAVX Enroute 1600
N64181 KBUR KAVX Enroute 1600
NOV743 KBUR KAVX Enroute 1600

Arrivals (3)

Callsign Dep Arr Status ETA
N5817F KSAN KBUR Enroute 1600
UAL1164 KSFO KBUR Enroute 0258
ASA121 KPDX KBUR Enroute 0508

Burbank (SoCal) 9

Departures (3)

Callsign Dep Arr Status ETA
SWA3242 KLAS KPHX Enroute 1846
UAL3833 KLAS KSFO Enroute 0318
SWA575 KLAS KSLC Enroute 0320

Arrivals (3)

Callsign Dep Arr Status ETA
BAW2MW EGLL KLAS Enroute 0459
UAL636 KIAD KLAS Departing
DAL2134 KLAX KLAS Enroute 1600

Las Vegas 6
  • Flights To/From ZLA: 67
  • Flights in ZLA Airspace: 26
  • Controller Schedule

    March 24th, 2025

    No sessions found for selected date

    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!