Closed hazzas-99 closed 3 years ago
I think this was PEBKAC - probably aircraft too high or past the COPX, but would be good to verify if that is the case.
Looks to be a bit of both so far! Before BADSI, it flickers between D1 and D2 periodically and then once past BADSI, it sticks with D2 for the most part.
In terms of ownership and agreements, that's all fine.
It seems like EuroScope can't decide whether the aircraft will continue descending into D2 or stay in D1 (whilst under S5's control), hence the erratic change from one sector to another and back. So far I've tried a few different combinations but none have worked so I shall continue testing.
I wonder whether defining the STARs would help EuroScope predict a better profile...
Ok so I have got a solution and the PR will be up in a second.
I added the Dublin STARs that start at ABLIN or LIPGO and with the newly calculated descent profiles, ES is predicting the correct sector. However, I have had to perform a bit of bodging to get it working perfectly.
STARs for 10R and 16 are unaffected however, I have added a virtual fix to the 34 STAR to extend the STAR by a touch and for 28L, I defined the STAR that has a lateral hold rather than the regular STAR, again, for added distance so that ES can predict the correct sector.
There might be some other way to do this that isn't as odd as the way I've done it, however, this method works and I don't see a problem with it seeing as the STARs are only there for Sector Prediction purposes 😉
What is the bug/ error?
From Discord:
Just reporting an issue, DW arrivals via LIPGO/ABLIN are defaulting to D2 when Dublin is split upper and lower, they should go to D1.
Additional Information
Will either be an issue with the ownership order (so check LoA), or that ES isn’t predicting it into the right sector