In ARINC-424 17 specification, under
7.2.6 Terminal Waypoints subsection A the "Airport/Heliport or Runway/Helipad related Terminal Waypoints" naming conventions are described. It describes the steps to be taken in order to avoid duplicates.
For example: a final approach fix (FAF in short) on runway 36 for example, will be named
FF36 which works either for "Single Approach Procedure" or approaches that share a "common waypoint". If the common waypoint idea can't be applied, then the second letter becomes the route type described in section 5.7. So the FAF for a
VOR approach on 36 will be
FV36, for an
ILS on 36
FI36 and so on and so forth.
But here lies the problem (which unfortunately I am currently facing): what if there are more than one approaches of the same type on the same runway that can't share the same points? I have 2
VOR approaches where all points IAF, IF, FAF etc. do not coincide. According to the spec:
waypoint identifiers will be unique only for the airport specified; a waypoint identifier used in a terminal area cannot be repeated in that terminal area
I could get away with it as there are is no parallel runway and I can start adding numbers (eg
FV362 etc.) and it won't make any significant difference as these points will be used for simulation purposes and I have a couple of ways to "cheat". Though knowing what happens in reality will add to the simulation realism.