ZLA Logo
Who's Online
Online Controllers

No controllers online

Flights to/from ZLA

Departures (8)

Callsign Dep Arr Status ETA
DLH505 KLAX EDDF Enroute 0844
DLH453 KLAX EDDM Enroute 1100
CI852 KLAX KSFO Enroute 1932
CPA495 KLAX KSFO Enroute 2038
DAL672 KLAX KDEN Enroute 1939
DLH25C KLAX KLAS Enroute 2036
CPA146 KLAX LSFO Enroute 0119
DLH451 KLAX EDDM Enroute 1027

Arrivals (8)

Callsign Dep Arr Status ETA
AAL9712 YSSY KLAX Enroute 1606
UAL2046 KCLE KLAX Enroute 0232
ANZ6 PHNL KLAX Enroute 1623
BAW215 EGLL KLAX Enroute 0116
VIR7 EGLL KLAX Enroute 1928
DAL464 KLAS KLAX Enroute 0101
AFR066 LFPG KLAX Enroute 1016
BAW1880 KABQ KLAX Enroute 1600

Los Angeles (SoCal) 16

Departures (1)

Callsign Dep Arr Status ETA
KAL6831 KSAN KDEN Enroute 1709

Arrivals (1)

Callsign Dep Arr Status ETA
DLH466 EDDF KSAN Enroute 0228

San Diego (SoCal) 2

Departures (2)

Callsign Dep Arr Status ETA
DAL464 KLAS KLAX Enroute 0101
PAA35 KLAS KSEA Enroute 1853

Arrivals (2)

Callsign Dep Arr Status ETA
ACA1060 CYVR KLAS Enroute 2305
DLH25C KLAX KLAS Enroute 2036

Las Vegas 4
  • Flights To/From ZLA: 22
  • Flights in ZLA Airspace: 13
  • Controller Schedule

    October 26th, 2021

    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.


    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.




    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!