Skip to content

Airports

Right now there’s one field to work: Coral Cay. More airports arrive once each has enough stable, player-facing behavior to be worth its own page.

Two runways, and they cross each other. 01/19 runs roughly north-south; 14/32 cuts across it at an angle. That intersection is the airport’s signature problem - clearing one runway doesn’t automatically make the other safe to use, and a careless sequencing call on one can quietly box in the other.

Four gates share a single main apron. The apron is open enough that a slow pushback stands out, but close enough that push order matters.

Pushback at KCRL includes the aircraft’s first turn away from the stand. The game checks the whole swept path, including the space before the pushback endpoint. That makes some neighboring gates order-sensitive:

  • Push Gate 2 before Gate 1 when both are waiting. Gate 2’s first turn moves away from Gate 1’s pushback pocket.
  • Push Gate 3 before Gate 4 for the same reason.
  • Reversing either order can produce Unable pushback: ramp blocked. That means the ramp is physically blocked right now; it does not mean the clearance system is stuck.

If a pushback is refused, move the aircraft already on the apron first. Giving it a taxi clearance is not always enough immediately: it may still need to complete the physical turn that is blocking the neighboring stand. Retry the waiting pushback after that turn clears.

The practical rule is to plan the first pushback in each adjacent pair so its initial turn leads away from the aircraft still at the neighboring gate. This matters most with larger aircraft, whose longer and wider swept paths leave less room on the apron.

Future fields will differ in runway count and geometry, taxiway layout, gate count, and pattern shape. The clearance panel and phase logic stay the same everywhere - what changes is which sequencing problem shows up first.