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

Departures (30)

Callsign Dep Arr Status ETA
AAL2546 KLAX MMMX Arriving
NKS76 KLAX KEWR Enroute 2235
DLH457 KLAX EDDF Enroute 0002
BVI73 KLAX KATL Enroute 2302
AAL2453 KLAX KBOS Enroute 0024
UAL1942 KLAX KPDX Enroute 0919
SWA2030 KLAX KBOS Arriving
VOI995 KLAX MMMX Enroute 2347
DAL1558 KLAX KDTW Enroute 0038
ACA786 KLAX CYYZ Enroute 2342
DAL1145 KLAX KSLC Enroute 0825
UAL3038 KLAX KORD Enroute 0013
ACA555 KLAX CYVR Enroute 1001
DAL2385 KLAX KLAS Enroute 1805
CFTPG KLAX KSAN Enroute 1342
JBU1080 KLAX KLAS Enroute 0755
VRD1474 KLAX KLAS Enroute 0804
SWA639 KLAX KLAS Enroute 1600
NKS7759 KLAX KPHX Enroute 0716
N204RM KLAX KSAN Enroute 0650
ASA140 KLAX KSFO Enroute 1600
UAL1250 KLAX KSFO Enroute 1600
SWA251 KLAX KLAS Enroute 0845
CDN1683 KLAX KAUS Enroute 1600
ASA4308 KLAX KSEA Enroute 1600
KAL012 KLAX RKSI Enroute 1600
UAL398 KLAX KSFO Enroute 1600
SWA2212 KLAX KSJC Enroute 1600
UAL1727 KLAX KLAS Enroute 1600
SWA217 KLAX KLAS Enroute 1600

Arrivals (23)

Callsign Dep Arr Status ETA
QTR741 OTHH KLAX Enroute 1939
FIN1 EFHK KLAX Enroute 1101
AST2877 PANC KLAX Enroute 0707
FIN11 EFHK KLAX Enroute 1527
FDX6075 KIND KLAX Enroute 0657
UAL1756 CYVR KLAX Enroute 0647
SWA2194 KABQ KLAX Enroute 1205
DAL2321 KLAS KLAX Enroute 0825
VNT722 KLAS KLAX Enroute 2319
SWA28F KOAK KLAX Enroute 1214
CHASE01 KSEA KLAX Enroute 0806
SWA1516 KSAT KLAX Enroute 0843
AAL2984 KSAT KLAX Enroute 0726
AVA84 SKBO KLAX Departing
SWA3155 KSFO KLAX Enroute 0636
KANGA1 KSGU KLAX Enroute 0756
SWA1513 KSJC KLAX Enroute 1244
SWA697 KLAS KLAX Enroute 2034
SWA373 KSJC KLAX Enroute 1800
FDX1049 KSAN KLAX Enroute 1800
UAL2676 KORD KLAX Enroute 1136
UAE13EA OMDB KLAX Departing
NKS1719 KLAS KLAX Enroute 1600

Los Angeles (SoCal) 53

Departures (1)

Callsign Dep Arr Status ETA
SWA895 KONT KOAK Enroute 1600

Empire (SoCal) 1

Departures (13)

Callsign Dep Arr Status ETA
PAC1262 KSAN BIKF Arriving
DSH4049 KSAN PHNL Enroute 1600
AAL518 KSAN KORD Enroute 2216
SWA1049 KSAN KBWI Enroute 0059
SWA873 KSAN KSFO Enroute 0955
DAL7689 KSAN KDEN Enroute 0713
OEWSP KSAN KLAS Enroute 1248
ASA518 KSAN KPDX Enroute 0859
SWA1458 KSAN KLAS Enroute 0757
SWA2325 KSAN KLAS Enroute 0713
NLL89 KSAN KCRQ Enroute 0921
FDX1049 KSAN KLAX Enroute 1800
AAL96 KSAN KPHX Enroute 1600

Arrivals (7)

Callsign Dep Arr Status ETA
N117HS KHND KCRQ Enroute 1600
FFT2127 KLAS KSAN Enroute 1006
CFTPG KLAX KSAN Enroute 1342
NLL89 KSAN KCRQ Enroute 0921
DAL902 KSJC KSAN Enroute 0924
N204RM KLAX KSAN Enroute 0650
AAL811 KDEN KSAN Enroute 1600

San Diego (SoCal) 20

Departures (2)

Callsign Dep Arr Status ETA
SWA2785 KBUR KABQ Enroute 2114
SWA3437 KBUR KSMF Enroute 1600

Arrivals (3)

Callsign Dep Arr Status ETA
N800KS KOPF KVNY Enroute 0653
SWA596 KLAS KBUR Enroute 1600
ASA2152 KEGE KBUR Enroute 0730

Burbank (SoCal) 5

Arrivals (1)

Callsign Dep Arr Status ETA
SWA2606 KLAS KPSP Enroute 1600

Palm Springs (SoCal) 1

Departures (21)

Callsign Dep Arr Status ETA
DAL1422 KLAS RPLL Enroute 0319
N117HS KHND KCRQ Enroute 1600
SWA596 KLAS KBUR Enroute 1600
NKS540 KLAS KAUS Enroute 2257
AAL20 KLAS KAUS Enroute 2252
DAL660 KLAS KATL Enroute 0034
DAL2321 KLAS KLAX Enroute 0825
ROU1846 KLAS CYYZ Enroute 0039
ASA776 KLAS PANC Enroute 1248
VNT722 KLAS KLAX Enroute 2319
FFT2127 KLAS KSAN Enroute 1006
DAL966 KLAS KATL Enroute 0031
SWA2231 KLAS KRNO Enroute 1600
SWA213 KLAS KPHX Enroute 0759
SWA697 KLAS KLAX Enroute 2034
N301TL KLAS CYVR Enroute 1214
SWA1162 KLAS KRNO Enroute 1600
SWA2606 KLAS KPSP Enroute 1600
NKS1719 KLAS KLAX Enroute 1600
NKS1038 KLAS KDTW Enroute 1600
AAY526 KLAS KPDX Enroute 1600

Arrivals (15)

Callsign Dep Arr Status ETA
BAW275 EGLL KLAS Enroute 1204
HAL2 PHOG KLAS Enroute 0604
SWA2105 KSLC KLAS Enroute 0721
JBU1121 KIAH KLAS Enroute 0726
N737GG PHOG KLAS Enroute 0554
OEWSP KSAN KLAS Enroute 1248
DAL2385 KLAX KLAS Enroute 1805
SWA1458 KSAN KLAS Enroute 0757
SWA2325 KSAN KLAS Enroute 0713
JBU1080 KLAX KLAS Enroute 0755
VRD1474 KLAX KLAS Enroute 0804
SWA639 KLAX KLAS Enroute 1600
SWA251 KLAX KLAS Enroute 0845
UAL1727 KLAX KLAS Enroute 1600
SWA217 KLAX KLAS Enroute 1600

Las Vegas 36

Departures (1)

Callsign Dep Arr Status ETA
KANGA1 KSGU KLAX Enroute 0756

Other 1
  • Flights To/From ZLA: 117
  • Flights in ZLA Airspace: 51
  • Controller Schedule

    October 5th, 2022

    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!