To elaborate on Ray's good answer ...
Remember that when you enter times in to the program, they must be typed in 24 hour format with no spaces or colons or anything – and then you need to press the ENTER key. For example, to enter 8:00pm, type in 2000 and then press your ENTER key. The program will accept it and change it to 20:00.
The time that you enter must be 50 minutes (or more), after the ARRIVAL time of the plane's previous leg. For example, if the plane leaves Melbourne at 5:00pm and arrives in Sydney at 6:15pm, then the ARRIVAL time, in Sydney, of that leg is 6:15pm. So, if you now want that plane to fly on to Brisbane, or back to Melbourne, or whatever, you need to set the takeoff time for that Brisbane leg (or return to Melbourne leg, or whatever) to be 50 minutes AFTER 6:15pm ... which would be 7:05pm. Or, to put it another way, the plane must be parked in Sydney for at least 50 minutes or more, and therefore it cannot depart Sydney until at least 7:05pm or later. If you chose 7:05pm as it's departure time, then you need to set it for 1905 in the program and press your ENTER key. If the time is accepted, the program will change your entry to 19:05 and it will be in black font. If it is not accepted, it will be in red font and you will get an error message telling you it needs to be more than 50 minutes. You can, of course, set the plane to leave later than that 7:05pm time if you wish; say, 19:30 (7:30pm) or 20:00 (8:00pm) or whatever later time you choose ... as long as the time you're choosing is more than 50 minutes after the arrival time of the plane's previous leg (ie, more than 50 minutes after 6:15pm in our example here). Now, as for the 50 minute "rule" itself ... there is actually a (Microsoft) reason for the restriction, believe it or not.
This is from the FSX SDK, Traffic Toolbox section ... link: https://msdn.microsoft.com/en-au/library/cc526965.aspx" rel="nofollow - https://msdn.microsoft.com/en-au/library/cc526965.aspx ============================================
Q: Why does the TrafficDatabaseBuilder generate an error message if I schedule an aircraft to depart within 45 minutes of the time it arrived at an airport?
A: The TrafficDatabaseBuilder enforces a minimum aircraft turnaround time of 45 minutes. A bit of flexibility is needed in the schedule to account for uncertainties due to winds aloft, approach vectoring, taxiing, obtaining takeoff clearances, etc. This flexibility in the schedule helps to ensure that if you follow an AI aircraft through its complete route that it would never get too far off schedule. Staying reasonably close to schedule is important because at 100 percent traffic density, nearly 100 percent of the available airport parking is utilized. If the schedules were constructed inflexibly, airports and parking spaces would frequently be over-utilized, creating traffic jams. ============================================ I don't know what AIFP does, but if it allows LESS than 45 minutes, then you need to be careful ... otherwise you will possibly experience unexpected behaviour from your AI.
|