Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Gatwick (EGKK) SFD4Z departure SI #5276

Open
PLM1995 opened this issue Apr 20, 2024 · 5 comments
Open

Gatwick (EGKK) SFD4Z departure SI #5276

PLM1995 opened this issue Apr 20, 2024 · 5 comments
Assignees
Labels
bug Bugs or errors

Comments

@PLM1995
Copy link
Collaborator

PLM1995 commented Apr 20, 2024

What is the bug/error?

With EGKK_APP, LON_S_CTR and LON_D_CTR.

Aircraft assumed by EGKK_APP flying a SFD4Z departure has its SI 'toggle' between LD and LS multiple times after departure.

Example:
EZY4EX - Flying EGKK > LFPG via SFD M605 XIDIL/N0326F190 M605 BIBAX

Initially LS, then LD, then LS, etc.:
KK_SFD4Z_SI_A
KK_SFD4Z_SI_B
KK_SFD4Z_SI_C
KK_SFD4Z_SI_D

What is the expected functionality?

SI Should remain LS, as they are top-down of TCSW in this situation.

Sources

EGKK vMATS.

File changes (if known)

Unsure.

@PLM1995 PLM1995 added bug Bugs or errors up-for-grabs Unassigned labels Apr 20, 2024
@KHardern
Copy link
Contributor

KHardern commented May 5, 2024

I don't think this is fixable. It does it because the TCSE/SW boundary line is west of the SFD track for about 10NM and so ES prediction switches to TCSE (LD) when the plane is climbing rapidly. (i.e. it predicts it will enter LD)

@PLM1995
Copy link
Collaborator Author

PLM1995 commented May 8, 2024

I don't think this is fixable. It does it because the TCSE/SW boundary line is west of the SFD track for about 10NM and so ES prediction switches to TCSE (LD) when the plane is climbing rapidly. (i.e. it predicts it will enter LD)

Ahhh right. Will leave this issue open a wee while longer in case anyone has some spark of genius then close it if not.

@hazzas-99
Copy link
Contributor

hazzas-99 commented May 8, 2024

@PLM1995 most likely to do with this change: 3130e4d

The problem with using FIX SFD is that when the aircraft is assumed by TC SW (or the controller covering it) after transfer, I believe the SFD 70 still displays in the list until the aircraft passes SFD. We could perhaps try using FIX KKS22 or D344G, but we probably need a fallback with FIX AFTER SFD in case Gatwick holds on to the aircraft for longer.

So we could maybe try:

COPX:EGKK:08R:KKS22:SFD:*:KKAPP_E:London TC SW:7000:*:^SFD
COPX:EGKK:08R:D344G:SFD:*:KKAPP_E:London TC SW:7000:*:^SFD

COPX:EGKK:08R:*:SFD:*:KKAPP_E:London TC SW:7000:*:^SFD

COPX:EGKK:08L:D344G:SFD:*:KKAPP_E:London TC SW:7000:*:^SFD

COPX:EGKK:08L:*:SFD:*:KKAPP_E:London TC SW:7000:*:^SFD

@PLM1995 PLM1995 self-assigned this May 11, 2024
@PLM1995 PLM1995 removed the up-for-grabs Unassigned label May 11, 2024
@PLM1995
Copy link
Collaborator Author

PLM1995 commented May 11, 2024

Thanks, I'll put that in and try it out.

@PLM1995
Copy link
Collaborator Author

PLM1995 commented May 11, 2024

Thanks @hazzas-99, having tried that out, in the same scenario of KKR, LS and LD; it seems to give LD initially (not toggling now with the one aircraft I tested) until it switches to LS after like 15 miles around FL70. My understanding is it should be LS from departure. (Gives TCSE initally with KKR, TCSE and TCSW until around KKS16 when is switches to TCSW). So seems to be whichever sector it's in.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Bugs or errors
Projects
None yet
Development

No branches or pull requests

3 participants