APRON DEP

Apron Departure is used when the apron is split and one of these applies:
- B_GND — A_GND is online and C_GND is offline, or
- C_GND — B_GND and A_GND are both online.
Strip behaviour matches AA + AD in general, but this scope has a smaller set of bays and some columns are locked.
Bay overview
Section titled “Bay overview”| Bay | Strip type | Notes |
|---|---|---|
| Messages | Messages | Coordination / free-text. |
| Final | Arrival locked | Locked — not accessible in this scope. |
| RWY ARR | Arrival locked (ARR-LOCKED) | Locked — not the same strip as RWY ARR in AA+AD / Apron Arrival. |
| STAND | APN-ARR | Active. |
| TWY ARR | APN-ARR | Apron arrival taxi; active. |
| De-ice | APN-TAXI-DEP | Active — taxi / de-ice routing. |
| Push back | APNPUSH | Locked — not accessible in this scope. |
| SAS | Uncleared | Locked if CLR DEL, DEL+SEQ, or SEQ PLN is online. |
| Norwegian | Uncleared | Same as SAS. |
| Others | Uncleared | Same family as CLR DEL. |
Using this scope
Section titled “Using this scope”Active bays (STAND, TWY ARR, De-ice) cover apron arrival and de-ice taxi movements. Locked columns are visible for situational awareness but are not manipulated here.
Use REQ only where the bay and strip type allow — locked bays do not offer REQ behaviour.
For full pushback → taxi → TWY DEP sequencing, see AA + AD or Apron Arrival. For clearance and PDC, see CLR DEL and Pre-departure clearance.
Related
Section titled “Related”- AA + AD — full combined layout
- Apron Arrival — A_GND with B/C online