AI Traffic FP creation question - why override ETA?
Posted: 02 Jun 2024, 13:10
Recently I have been experimenting a bit with making my own traffic flight plan files. I like to review what has been done before me since you guys are the masters in this domain) and I notice that all these flight plans have a specified ETA time listed. There is something entered in the ETA Override Box, and I never understood why.
What is the reason for doing this? What negative AI behavior does this help alleviate or avoid?
I have read the section(s) that Don G wrote in his AIFP manual on the 37-minute rule, aircraft arriving late (in some cases) and all that.
There was something also about a 22 minute offset -- from DON:
" If AI traffic is more than about 20 minutes late, it is discarded. From extensive testing (by others), it has been determined that the critical time difference is 22 minutes. Given the standard 15-minute allowance for approach, landing and taxiing, the 22-minute interval equates to 37 minutes later that a user-specified arrival time. Hence, the name “37-minute problem. "
OK so now I go back and open a traffic file and sure enough, this one is showing an ETA override of 22 minutes early - as compared to what AIFP calculates.
So is that it then? Is this just considered a best practice here, so that we reduce or avoid this problem of aircraft being delayed and disappearing?
Just use AIFP calcs and then slice off 22 minutes as an override in the FP? This works best?
What is the reason for doing this? What negative AI behavior does this help alleviate or avoid?
I have read the section(s) that Don G wrote in his AIFP manual on the 37-minute rule, aircraft arriving late (in some cases) and all that.
There was something also about a 22 minute offset -- from DON:
" If AI traffic is more than about 20 minutes late, it is discarded. From extensive testing (by others), it has been determined that the critical time difference is 22 minutes. Given the standard 15-minute allowance for approach, landing and taxiing, the 22-minute interval equates to 37 minutes later that a user-specified arrival time. Hence, the name “37-minute problem. "
OK so now I go back and open a traffic file and sure enough, this one is showing an ETA override of 22 minutes early - as compared to what AIFP calculates.
So is that it then? Is this just considered a best practice here, so that we reduce or avoid this problem of aircraft being delayed and disappearing?
Just use AIFP calcs and then slice off 22 minutes as an override in the FP? This works best?