Great news, thanks in advance. K is in the north of Linz (LOWL) at danube river.

Cheers

Thanks, it's only VRPs we are working with at the moment however. Where is the VRP "K" you mentioned in your last post please?

(This highlights the issue really. If I don't know where it is, how is the controller supposed to know?)

Just a two examples of what has been accepted in Austria on my last flights:

OEAES LOAD 1315-LOAS
LOAU LOAG
(DOF/131002)
N0100VFR GRAFENEGG STO KREUZENSTEIN KL DT FR SC PE

OEAES LOWL 1050-LOAD
LOAG
(DOF/140311)
N0105VFR K PLESCHINGERSEE TRAGWEIN GREIN LOLG MELK

In the last plan you can see there are published VRPs (K), Lakes (Pleschingersee), Villages (Grein) and even airfields (lolg) in it - and accepted without any notice!

Once again, please rethink that as an option,
Bernhard.

Those are not VRPs and would never have been converted to coordinates in the flightplan route field.

For example the points STEIN, PESAT and SASAL. They are coordination points on the border between Austria and Hungary and frequently used as border crossing points.

-- Chris.

Can you give an example of some VRPs in Austria which meet that specification?

I'm quite sure coordinates must be allowed, as not every route has turning points which coincide with defined waypoints. Especially routes along valleys etc.

Here is the excerpt from Austro Control regarding specification of flight routes in a flightplan (translated from German):

For those parts of the route which lie inside FIR WIEN, only ATS routes, pre-defined routes and 3 or 5 letter identifiers as specified in the AIP are allowed to be used in field 15 as enroute points.

This means quite specifically, that geo coordinates are not accepted.

If SD already maintains a list of reporting points and knows where they come from (either AIP or not) then use that information. Otherwise I would use names that either are 3 or 5 letters long verbatim in the flight plan. All others still as geo coordinates.

-- Chris.

I think we may have a potential solution to this, where some VRPs are left with their identifiers intact when generating a flightplan. Specifically just those which HAVE identifiers. Could somebody give me a few example flightplans where there are VRPs which should be left intact according to local rules?

The added difficulty of parsing a route description without DCT would be negligible. (At least as long as it is impossible for an ATS route and a significant point to have the same designator.)