ZLA Logo
Who's Online
Online Controllers

No controllers online

Flights to/from ZLA

Departures (13)

Callsign Dep Arr Status ETA
CSS7424 KLAX ZHEC Enroute 1417
DAL465 KLAX PHNL Enroute 0636
AAL445 KLAX KPHX Enroute 1600
FDX1227 KLAX KMEM Enroute 0114
AAL382 KLAX KBOS Enroute 0411
MET4456 KLAX KEUG Enroute 1032
AAL4 KLAX KJFK Enroute 1409
AAL274 KLAX KJFK Enroute 0404
DAL689 KLAX KRDU Enroute 0022
UAL5977 KLAX KBOI Enroute 1024
AAL556 KLAX KPHX Enroute 1038
JBU942 KLAX KRNO Enroute 1600
GTI523 KLAX SEQM Enroute 1024

Arrivals (20)

Callsign Dep Arr Status ETA
DLH456 EDDF KLAX Enroute 0848
DLH1979 EDDF KLAX Enroute 1017
THY9 LTFM KLAX Enroute 1651
UAL1403 KDEN KLAX Enroute 0922
ACA791 CYYZ KLAX Enroute 1002
UPS73 KSDF KLAX Enroute 1136
ASA285 KEWR KLAX Enroute 0945
UAL1205 PHKO KLAX Enroute 1600
AAL5145 KDFW KLAX Enroute 1600
UAL1933 MRLB KLAX Enroute 0903
DAL442 KBOS KLAX Enroute 0911
DAL5193 KOAK KLAX Enroute 1600
DAL27 KORD KLAX Enroute 0942
ASA1092 KSEA KLAX Enroute 0933
AAL2709 KLAS KLAX Enroute 1019
AAL9831 KMIA KLAX Departing
N58G KPHX KLAX Enroute 1709
UPS2040 KJFK KLAX Enroute 0903
AAL846 KMCO KLAX Departing
VIR23 EGLL KLAX Departing

Los Angeles (SoCal) 33

Departures (1)

Callsign Dep Arr Status ETA
SWA2728 KONT KSMF Enroute 0954

Empire (SoCal) 1

Departures (5)

Callsign Dep Arr Status ETA
DAL894 KSAN KATL Enroute 0127
ETD6989 KSAN KMDW Enroute 0059
N618BY KSDM KJAC Enroute 1412
SCRCH55 KNZY KIPL Enroute 0224
UAL2760 KSAN KLAS Enroute 1600

Arrivals (5)

Callsign Dep Arr Status ETA
NKS743 KOAK KSAN Enroute 1600
DAL866 KDTW KSAN Enroute 0950
DAL2346 KSFO KSAN Enroute 0908
SWA1640 KDEN KSAN Enroute 1600
SWA2208 KSMF KSAN Enroute 1600

San Diego (SoCal) 10

Departures (3)

Callsign Dep Arr Status ETA
SWA2602 KSNA KAUS Enroute 0029
AAL2458 KSNA KAUS Enroute 0032
SWA2924 KLGB KMDW Enroute 0214

Arrivals (2)

Callsign Dep Arr Status ETA
SWA3829 KPHX KLGB Enroute 1600
SWA3145 KLAS KLGB Enroute 1052

Coast (SoCal) 5

Arrivals (1)

Callsign Dep Arr Status ETA
SWA279 KSMF KBUR Enroute 1536

Burbank (SoCal) 1

Departures (2)

Callsign Dep Arr Status ETA
AAL2709 KLAS KLAX Enroute 1019
SWA3145 KLAS KLGB Enroute 1052

Arrivals (11)

Callsign Dep Arr Status ETA
SWA359 KTPA KLAS Enroute 0933
AAY3082 KVPS KLAS Enroute 0934
DAL4751 KMSP KLAS Enroute 0943
ACA1060 CYVR KLAS Enroute 1034
DAL789 KMSP KLAS Enroute 0919
UAL2307 KSFO KLAS Enroute 1103
AAY33 KOAK KLAS Enroute 1600
SWA2495 KSEA KLAS Enroute 1044
UAL2760 KSAN KLAS Enroute 1600
EJA225 KBZN KLAS Enroute 1011
SWA543 KAUS KLAS Departing

Las Vegas 13

Departures (1)

Callsign Dep Arr Status ETA
N801XL KHII KSZP Enroute 1600

Arrivals (1)

Callsign Dep Arr Status ETA
SCRCH55 KNZY KIPL Enroute 0224

Other 2
  • Flights To/From ZLA: 65
  • Flights in ZLA Airspace: 27
  • Controller Schedule

    June 4th, 2023

    Las Vegas Approach
    Jack Croteau

    Session with WX

    1800 - 1900 PDT / 0100 - 0200 Zulu

    Socal Approach (Combined)
    Joshua Daily

    Session with NC

    1800 - 1930 PDT / 0100 - 0230 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.


    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!