You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using del for an aircraft waiting on the runway successfully removes it from the screen; however, any subsequent aircraft wanting to takeoff on that same runway will throw back a "cleared for takeoff, number [#]...behind the [deleted aircraft]...," thus rendering the game unusable.
Ex at JFK: AA1, BA2, DL3, VS4 on the apron looking for taxi to a runway. Meanwhile CX10, EK11, and AF12 on approach for runway 31L.
CX10 ILS 31L // followed by a valid intercept; 10 mi final
EK11 ILS 31L // also successful intercept; 14 mi final
AF12 ILS 31L // successful intercept; 18 mi final [then, ]
AA1 W 31L
BA2 W 31L
DL3 W 31L
VS4 W 31L [all my departures are headed to 31L and have valid SIDS and climbs]
[by this time, CX10 is on a 2 mi final, EK11 on a 6 mi final, and AF12 on a 10 mi final. AA1 is waiting on the runway and to avoid an incursion, I issue]
AA1 DEL // Aircraft then disappears, flight strip gone. [That's good and all. So, let's say the Emirates and Air France land successfully on 31R after I clear them for the parallel; the Cathay lands successfully on 31L. Now I can roll out my departures]
BA2 CAF CVS TO // (on 31L) [and here's what I get back]
"Speedbird two, cleared as filed, climb via the SID, runway 31L cleared for takeoff, number 2 behind the AA1."
Since AA1 is no longer on the field nor in my flight strip bay, there's nothing I can do and BA2 will just sit, waiting for AA1 to depart (i.e., forever).
Anybody else have this issue?
The text was updated successfully, but these errors were encountered:
Using del for an aircraft waiting on the runway successfully removes it from the screen; however, any subsequent aircraft wanting to takeoff on that same runway will throw back a "cleared for takeoff, number [#]...behind the [deleted aircraft]...," thus rendering the game unusable.
Ex at JFK: AA1, BA2, DL3, VS4 on the apron looking for taxi to a runway. Meanwhile CX10, EK11, and AF12 on approach for runway 31L.
[then, ]
[all my departures are headed to 31L and have valid SIDS and climbs]
[by this time, CX10 is on a 2 mi final, EK11 on a 6 mi final, and AF12 on a 10 mi final. AA1 is waiting on the runway and to avoid an incursion, I issue]
[That's good and all. So, let's say the Emirates and Air France land successfully on 31R after I clear them for the parallel; the Cathay lands successfully on 31L. Now I can roll out my departures]
[and here's what I get back]
Since AA1 is no longer on the field nor in my flight strip bay, there's nothing I can do and BA2 will just sit, waiting for AA1 to depart (i.e., forever).
Anybody else have this issue?
The text was updated successfully, but these errors were encountered: