Runway change
Closed this issue · 12 comments
How are runway changes supposed to be handled exactly? Considering you cannot depart simultaneously on the old and the new departure runway.
- Select the new runways in the runway assigment dialog without removing the old ones.
- Assign manually the runways for the traffics.
- Once all have already the new runways, remove the old ones in the runway assigment dialog.
The TOBT should be manually set starting from the first available slot
The TOBT should be manually set starting from the first available slot
But there is still a risk that flights after this one might get an earlier TOBT/TTOT, because the plugin thinks the new runway has no other traffic, right?
Could you check an option to set an "earliest TTOT" for a specific runway? So kind of a delay gap, but for a runway.
- Select the new runways in the runway assigment dialog without removing the old ones.
- Assign manually the runways for the traffics.
- Once all have already the new runways, remove the old ones in the runway assigment dialog.
Why do you need to keep the old runway? Or, what would change if only the new runway is set?
Correct.
So if the last departing acft for the old rwy has TTOT 1100.
The first from the new rwy should be set a manual TOBT with at least TTOT 1101 (depending on the dep rate).
- Select the new runways in the runway assigment dialog without removing the old ones.
- Assign manually the runways for the traffics.
- Once all have already the new runways, remove the old ones in the runway assigment dialog.
Why do you need to keep the old runway? Or, what would change if only the new runway is set?
To get the correct rate, otherwise it would be standard rate from the xml.
Correct. So if the last departing acft for the old rwy has TTOT 1100. The first from the new rwy should be set a manual TOBT with at least TTOT 1101 (depending on the dep rate).
But if it's only 1040 now and the taxi time is 10 minutes, the next flight will receive a TTOT of 1050 unless you also manually do something, right?
- Select the new runways in the runway assigment dialog without removing the old ones.
- Assign manually the runways for the traffics.
- Once all have already the new runways, remove the old ones in the runway assigment dialog.
Why do you need to keep the old runway? Or, what would change if only the new runway is set?
To get the correct rate, otherwise it would be standard rate from the xml.
I wouldn't get the rate of the new runway if I have only this one activated as a departure runway? But then again this is exactly the setup later on. I can't really follow.
Correct. So if the last departing acft for the old rwy has TTOT 1100. The first from the new rwy should be set a manual TOBT with at least TTOT 1101 (depending on the dep rate).
But if it's only 1040 now and the taxi time is 10 minutes, the next flight will receive a TTOT of 1050 unless you also manually do something, right?
Correct
I wouldn't get the rate of the new runway if I have only this one activated as a departure runway? But then again this is exactly the setup later on. I can't really follow.
Disreagard. My mistake, with the new rwy config should not happen again.
Could you check an option to set an "earliest TTOT" for a specific runway? So kind of a delay gap, but for a runway.
So bringing back this idea: Would it be possible to offer a different time of delay gap where you don't specify the duration, but the first time where you allow again an actual traffic to be planned? So that something like
.cdm LSZH/32 1105 will add a delay gap on LSZH runway 32 for any slot still not yet booked before 1105.
.cdm customdelay LEBL/24L 1100 -> TSATs starting at 1100.
.cdm customdelay LEBL/24L 9999 -> Remove "restriction" for airport LEBL and rwy 24L.