All missing heli procedures

[Adrian2k]

So in this AIRAC these charts was suddenly removed?

It is not mentioned in the AMDT cover letter?

AD 2 ENZV 1 | TLOF SAR established.
AD 2 ENZV 2 | TLOF SAR established.
AD 2 ENZV 4 | Editorial changes.
AD 2 ENZV 5 | Editorial changes.

[Adrian2k]

For me this is a low priority to look into - especially as ENZV make heli changes 4-5 times a year at this point.

Perhaps @Azchk wants to look more into this?
This is what data we have in GNG atm:

What I would need:
Which procedures to delete
Link to any other procedures that is missing (charts)

alternatively - procedures decoded as following:

Procedure name: 
Type (APP/SID/STAR):
Procedure main waypoints:
Procedure transition waypoints (last waypoint must be first waypoint of main):
Runway(s):

Example:

Procedure name: RNP081
Type (APP/SID/STAR): APP
Procedure main waypoints: ZV441 ZV442 ZV465
Procedure transition waypoints:
ZV439 ZV441
ZV440 ZV441
Runway(s): 36,10

[Azchk]

No changes to the procedures at all. It seems the document order was just moved around a little.

[Azchk]

Thanks, I will check out the other missing airports and provide them as you describe. There is going to be waypoints that need to be added aswell. For simplicity I will just provide all the waypoints with coordinates, and you can sort out the duplicates.

[Adrian2k]

Thanks, I will check out the other missing airports and provide them as you describe. There is going to be waypoints that need to be added aswell. For simplicity I will just provide all the waypoints with coordinates, and you can sort out the duplicates.

Waypoints should already be included in the AIRAC data (for offshore procedures).

[Adrian2k]

If there are waypoints missing, they need for be formatted in the following CVS file.

waypoints_ENOR.xls

Ident = waypoint
Countrycode = EN
ICAO = Airport (or ENOR if not related to an aiport)
Area: Enroute
Lat: In following format N060.18.07.636
Lon: In following format E005.07.29.201

https://webtools.kusternet.ch/geo/coordinatesconverter can be useful for converting coordinates

(but check if they are included in the sectorfile first - usually only hospital waypoints procedures are not included)

[Azchk]

Should we close this issue, then I can post the finished spreadsheet in another one relating to all heli procedures?

[Adrian2k]

We can continue working in this issue, for documentation/tracking purposes if I ever need to go back to this in the future. Renamed the issue to something else

[github-actions]

This issue has been tagged as procedure related.
Here is a checklist of items to remember when ammending procedures:

• Procedure included in AIRAC data?
• If removal of proc: Check all manual data is deleted (NAV > Proc)
• Procedure combiner (check it actually combines)
• GNG generated maps working (important if GM, BR, VA, ZV - check topsky maps!)
• TopSky initial climb (SID)
• Documentation? (renumbering usually don´t require changes)
• TopSky maps/manual maps?

[Azchk]

https://docs.google.com/spreadsheets/d/1kAQsax_PzzQFxuEV0IEk1SHQ7AdK9ZWQhjja49iAa_4/edit?usp=sharing

[Azchk]

I can write in the offshore and air ambulance helicopter routes as well, if you can specify how that should be formatted for the secorfile.

[Adrian2k]

Those are already in the sectorfile?

[Adrian2k]

[Azchk]

Nice! Thanks. I see there might be some outdated segments that changed in relation to the Ekofisk and Tampen HTZ. No it is the HTZ themselves that are incorrect, my mistake.

[Azchk]

And sorry if this is a stupid question, but does euroscope parse those routes correctly and draw them if in a route in a flight plan? Or is it a visual map only?

[Adrian2k]

Nice! Thanks. I see there might be some outdated segments that changed in relation to the Ekofisk and Tampen HTZ. No it is the HTZ themselves that are incorrect, my mistake.

Already known - low priority issue for me #389

And sorry if this is a stupid question, but does euroscope parse those routes correctly and draw them if in a route in a flight plan? Or is it a visual map only?

While avinor uses the phrase «routes» they are in reality airways.
The data is directly from the AIRAC data, so anyone should be able to fly them provided they have a updated nav database.
For euroscope, it will parse them just as any other flightplans containing airways.
We currently get AIRAC data from navdatapro (Lufthansa Lido), but I would assume navigraph (jeppesen) have this also included.

[Adrian2k]

https://docs.google.com/spreadsheets/d/1kAQsax_PzzQFxuEV0IEk1SHQ7AdK9ZWQhjja49iAa_4/edit?usp=sharing

I have started on some of this now - added the following:
ENFL Heli SID + APP
ENKB Heli SID + APP
ENHF Heli SID + APP
ENVR Heli APP

For the hospitals - we need to add the helipads as a runway in the sectorfile - since ES requires all procedures to be connected to a runway.
To add a runway it requires quite alot of information - example from ENVR (which had FATO coordinates defined in AIP)

(03C/21C was the closest I could do make it appear as a "chopper" runway)

[Azchk]

Nice! I can go over the AHM and add the runway information to the spreadsheet.> > https://docs.google.com/spreadsheets/d/1kAQsax_PzzQFxuEV0IEk1SHQ7AdK9ZWQhjja49iAa_4/edit?usp=sharing

I have started on some of this now - added the following:
ENFL Heli SID + APP
ENKB Heli SID + APP
ENHF Heli SID + APP
ENVR Heli APP

For the hospitals - we need to add the helipads as a runway in the sectorfile - since ES requires all procedures to be connected to a runway.
To add a runway it requires quite alot of information - example from ENVR (which had FATO coordinates defined in AIP)

(03C/21C was the closest I could do make it appear as a "chopper" runway)

[Azchk]

Will there be issues if the "thresholds" have the same coordinates? As many of the pads are just circles.

[Adrian2k]

Will there be issues if the "thresholds" have the same coordinates? As many of the pads are just circles.

It let me submit it in GNG 🤷🏻‍♂️

[Azchk]

Okay that should be all of them added now. Notice ENAX Elev2 should be 74 ft