CARD Unconcerned conflicts

Bernardo Reis (1096507)

With Unco selected, the CARD is showing conflicts between unconcerned pairs. It should show conflicts with aircraft relevant to the sector with unconcerned flights.

Click AB on the Unco button check box to display/hide detected conflicts, PPC and PRC for which one of the
flights of the conflicting pair is an “unconcerned” flights (i.e. flight not moved to off-route sector, for which the
route doesn’t cross the specific position), this applies to CARD and flight leg.
Flight, when a manual transfer is in progress, is not hidden.

Juha Holopainen (839337)

Setting FPCP_MinState=0 does have that effect, allowing unconcerned tracks to be source tracks for MTCD. The default setting (1) does not allow that, so conflicts involving two unconcerned tracks will not be displayed.

Bernardo Reis (1096507)

It does solve the issue, kiitos!

Bernardo Reis (1096507)

Is there any setting that disables these kinds of conflicts where it predicts the profile is separated by 1000ft or more?

Juha Holopainen (839337)

It's not possible to tell based on that picture whether the conflict should've been displayed or not. As at least DLH22AK is flagged non-RVSM, the higher vertical separation applies. As apparently in your setup you've set the separation value to exactly 2000ft, it's enough for the predicted separation to be anything less than that for the conflict to be displayed (the default upper/lower separation values are 1800/800ft to account for small variations in the level predictions).

If you saved a logfile, you can go back to that situation and see what might have caused the alert. The default EuroScope tags' route prediction can be toggled to display the predicted altitudes along the route. If the predictions show even one foot less separation than 2000ft, then increasing the separation values should help (and I'd recommend it in any case). If not, then it's something else. Then make a dump file from that moment and send it to me. If there's no log file, there's no way to debug the issue.

Bernardo Reis (1096507)

You are correct with the RVSM remark, but I've seen similar cases where it warns about 1000ft with two /W planes.

I've checked the setting for the vertical separation values and they are the default ones.

I also checked the log file but now it did not warn about anything, both embelished flight legs showing a conflict free profile, even by forcing DLH22AK RFL to F360. Not sure if it enters with wind data for 4D calculations...?

Juha Holopainen (839337)

Unless your setup is different from the one currently available at GNG, then your vertical separation upper and lower values are 2000ft and 1000ft as specified in the areas data file that contains two FPCA's. The calculations do not use any wind data, it's just the EuroScope calculated path that knows nothing about the atmospheric conditions, so unless EuroScope calculates the path differently when online than when playing back a logfile, you should see the same results. You'll have to check it at the correct time though, as the calculated vertical path depends on the current aircraft altitude. In your case, if DLH was at say 37970ft, EuroScope would predict it to maintain exactly that (instead of 38000ft) until top of descent, and with TAP predicted at 36000ft, it would see a conflict.

Bernardo Reis (1096507)

I was looking for settings starting with MTCD but did not check the FPCAs. In the playback I've noticed that sometimes DLH would go to 37998ft in the Euroscope profile, so that's probably it.