COPX Master issue

[Adrian2k]

We have multiple COPX issues open atm - all of them being stale atm.
Merging it into one issue, so we can reduce the amount of clutter in our issue board.

---

#458

@krislarsen Check if all COPX related to OGDIT is in there. Looked to me that Møre APP> ENSV is missing for OGDIT COPX
@Sanderli25 No COPX to OGDIT defined in GNG. Will look into this.

---

#303

@krislarsen
Looks like Polaris gets the DCT IPMOD COPX that are supposed to go to ENGM_W_APP

---

#290

@krislarsen
This is a combined issue of #208 , #220 & #231
All of theese issue is due to incorrect COPXes. I believe many of the added "dummy" COPX lines made more trouble than solutions. I've removed all unnessesary COPX now and need now a lot of help to check following things:

• ENBR Dep via S5 and S8 gets RFL
• ENBR Arr via S8 is handed over to S9 with no descend
• ENBR arrr via S5 & S6 is getting XFL FL320
• ENSV can give COPX TNO, AAL and LOKSA without bypassing COPX

Phase 2:

• TIPAN + BAVTA COPX

Any missing COPX according to SOP/LoA between ENBD/ENSV/ENOS AoR shall be reported here.

@Adrian2k
ENSV_CTR via S9 to ENOR_S_CTR via S8 dep ENBR seems to still trigger XFL F310

---

#287

@marud94
SOP says BR APP can route flights to GUNPA and VALDI if in their flightplans without prior coordination. When selecting VALDI in the direct list it says it will send COPX to ACC.

@krislarsen
Both VALDI and GUNPA were added in GNG. Have adjusted Sortorder and moved the respective point from COPX FIX to Fixafter. Testing is nessesary.

@marud94
Tried testing on sweatbox, ended up with it sending COPX for REKLI as well. Need more testing, preferably on live network.

[Adrian2k]

Leaving this as unassigned until someone actually will start looking into this.

[Sanderli25]

OGDIT Added

[janfelhut04]

#376

Climb altitude gives cruise an not FL190 which is max permittable for APP (No direct given) From APP to ENBD

[marud94]

@janfelhut04 Do you have a screenshot with aircraft position in relation to TMA, the route and the altitude? Easier for troubleshooting that way

[Adrian2k]

Its all AMIMO departures, reported by multiple controllers now

Also all BARVI inbounds RWY18 has CFL 110 when its supposed to be 190 (S25 > TC APP)

[Atriusftw]

Missing suggested altitude/level in Helgeland TMA (ENBN_APP)

[Atriusftw]

COPX suggests FL330 (cruise) for flights to Sweden, when ESOS is online and Polaris offline. Should be 290? Also CJI is advisory.

[marud94]

@Atriusftw in the future, please include a screenshot of the tag when it happens, makes it easier to troubleshoot for us.

It looks like he just got airborne, what was his altitude? It’s pretty normal for the CJI and altitude to be wrong if he hasn’t actually entered the TMA. Also did it correct itself at any point, for example above FL100?

[Atriusftw]

@Atriusftw in the future, please include a screenshot of the tag when it happens, makes it easier to troubleshoot for us.

It looks like he just got airborne, what was his altitude? It’s pretty normal for the CJI and altitude to be wrong if he hasn’t actually entered the TMA. Also did it correct itself at any point, for example above FL100?

Yup, shortly after rotate. I estimate that the aircraft was around 1100ft or something.
Did not try after FL100, but it did not change when trying around 6000ft here. Have experienced this with other aircraft as well above ~4000ft tho.

[marud94]

@Atriusftw ES handles COPX weird and different all of the time. I generally notice that it fixes itself around FL100 if something is wrong. Doing anything in the tag immediately after rotate and expecting COPX to be correct is not the wisest as most checks for COPX and such will fail. There is nothing wrong in doing these things so early if you do it by knowledge of SOP though, and not by COPX.

[Atriusftw]

@Atriusftw ES handles COPX weird and different all of the time. I generally notice that it fixes itself around FL100 if something is wrong. Doing anything in the tag immediately after rotate and expecting COPX to be correct is not the wisest as most checks for COPX and such will fail. There is nothing wrong in doing these things so early if you do it by knowledge of SOP though, and not by COPX.

I simply didn't know about this quirk, atleast expected it to be "loaded" before aircraft reaches initial climb.

[marud94]

@Atriusftw unfortunately no. The initial climb is a kind of COPX on its own so sometimes things get weird. I generally only encounter this when covering top down, when tower is online I am yet to have these «issues»

[krislarsen]

COPX suggests FL330 (cruise) for flights to Sweden, when ESOS is online and Polaris offline. Should be 290? Also CJI is advisory.

Adjusted with some new lines that hopefully will work better. Please test this with next sectorfile update or dev and let me know the outcome

[krislarsen]

Missing suggested altitude/level in Helgeland TMA (ENBN_APP)

All departure agreeements were missing. Added a line to each SID + a general agreement for climb to FL140 from all AD within Helgeland TMA.

[krislarsen]

#303
Reconfigured a new method to see if we get a better outcome. COPX FIX and FIX AFTER is all clear in the lines. COPX should only be looking at name, witch is IPMOD

[krislarsen]

#376

Climb altitude gives cruise an not FL190 which is max permittable for APP (No direct given) From APP to ENBD

• COPX altitude ENTC SIDs #376

Old waypoint in GNG witch made it difficult to find the rule for ES. Should be working now. Did anything else work @janfelhut04 ?