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

ENBR CAT H RNPs in STAR list #471

Closed
Atriusftw opened this issue Oct 14, 2024 · 6 comments
Closed

ENBR CAT H RNPs in STAR list #471

Atriusftw opened this issue Oct 14, 2024 · 6 comments
Assignees
Labels
enhancement GNG Alias, sectors, positions, SID/STAR/APP etc

Comments

@Atriusftw
Copy link
Collaborator

Atriusftw commented Oct 14, 2024

Creating this issue from the discussion on Discord to track it.

The CAT H RNPs on Flesland are missing in the STAR list, namely RNP 043 and RNP 139.

A blocker is that we can't use numbers in the procedures with the current sector file provider.
Alternatives could be discussed here. My suggestion is to use the transitions as prefix to identify them. Example:

RNP043:
ELMEG · RNP
VIKSO · RNP

RNP139:
VENIN · RNP

@github-project-automation github-project-automation bot moved this to Unassigned in ENOR Sectorfile Oct 14, 2024
@Atriusftw Atriusftw added the GNG Alias, sectors, positions, SID/STAR/APP etc label Oct 14, 2024
@Dekuistic
Copy link

I believe the suggestion in the origin post is a very good solution given our circumstances, and blockers, however just to vairy it up a little l'll give my input :)

A suggestion is that we can give it a prefix that makes sense, for example RNP H RWY 35/17, or RNP R RWY 35/17 (Stands for Helicopter/Rotorcraft) M;aybe K for Kopter, V for Vertical, etc.
The downside i see with this is that controllers might be accident clear the aircraft for an "RNP H" Instead of RNP 043/139. Though i believe this is destined to happen no matter what we call it.

@Azchk
Copy link

Azchk commented Oct 14, 2024

I would go with Marius's suggestion. It's benificial to limit the use of symbols not in direct relation to the approach. Runway numbers should also not be used (e.g. RNP 17 H and RNP 35 H) as these are not approaches to a runway, but to a point in space (PinS).

@Adrian2k
Copy link
Collaborator

I always tried adding these as APP inside GNG - someone suggested adding them as a STAR entry instead which give a optimal solution

STAR:ENBR:35:ELMEG·RNP043:ELMEG BR711 BR710 ;  Combiner=ENBR2/12 | ID=35_ELMEG_RNP043
STAR:ENBR:35:VIKSO·RNP043:VIKSO MOMUX BR711 BR710 ;  Combiner=ENBR2/12 | ID=35_VIKSO_RNP043

@Adrian2k Adrian2k self-assigned this Oct 14, 2024
@Adrian2k Adrian2k moved this from Unassigned to In progress in ENOR Sectorfile Oct 14, 2024
@Adrian2k
Copy link
Collaborator

STAR:ENBR:17:VENIN·RNP139:VENIN BR812 BR810 ; Combiner=ENBR2/12 | ID=17_VENIN_RNP139

@github-project-automation github-project-automation bot moved this from In progress to Done in ENOR Sectorfile Oct 14, 2024
@Azchk
Copy link

Azchk commented Oct 14, 2024

Does this combine with OXEBU/ELMEG STARs, or will it overwrite it?

@Atriusftw
Copy link
Collaborator Author

Does this combine with OXEBU/ELMEG STARs, or will it overwrite it?

It is only possible to select one STAR from the list, so one would have to switch at some point if the pilot follows the entire OBEXU STAR. This is however normal with other approaches as well, as the same field is used to assign approach.

Example:
348388403-4bf59fed-47c9-461d-941e-822274f659e5

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement GNG Alias, sectors, positions, SID/STAR/APP etc
Projects
Archived in project
Development

No branches or pull requests

4 participants