Charts User waypoints X-Plane 12 read error

I created a simple VFR flight plan using Charts 8.38.3 (latest)

here it is: -

ADEP EGMD
DEPRWY RW03
ADES EGKA
DESRWY RW02
APP R02
APPTRANS GODOT
NUMENR 7
1 EGMD ADEP 13.000000 50.956100 0.938889
11 NIVKO DRCT 0.000000 50.934936 0.540983
11 505111N0003046E DRCT 0.000000 50.853056 0.512778
11 504817N0001943E DRCT 0.000000 50.804722 0.328611
3 SFD DRCT 0.000000 50.760689 0.121914
11 BOGNA DRCT 0.000000 50.701944 -0.251547
1 EGKA ADES 7.000000 50.835600 -0.297222

All looks reasonable .. but .. when I load it into X-Plane 12 G1000 the two user waypoints (lines 10 and 11) are over 1400nm away in the mid Atlantic.

I’ve tracked down the problem and its the second field which is the text identifier.

The problem is they both start with a number. When I replace the first digit with a letter the waypoint(s) load correctly.

i.e. change 505111N0003046E to A05111N0003046E

Is this problem due to Charts creating the identifier with a leading digit, or X-Plane 12 not coping with identifiers that don’t start with a letter ?

That is, is it valid to have an identifer that starts with a digit ?

I’ve asked in the relevant X-Plane 12 forum but no answer as yet, so I thought I’d ask here as well.

For now as a workaround I manually edit the created plan before use on X-Plane 12

Instead of adding a letter to the identifier, have you tried changing the row code from 11 to 28 like so?

ADEP EGMD
DEPRWY RW03
ADES EGKA
DESRWY RW02
APP R02
APPTRANS GODOT
NUMENR 7
1 EGMD ADEP 13.000000 50.956100 0.938889
11 NIVKO DRCT 0.000000 50.934936 0.540983
28 505111N0003046E DRCT 0.000000 50.853056 0.512778
28 504817N0001943E DRCT 0.000000 50.804722 0.328611
3 SFD DRCT 0.000000 50.760689 0.121914
11 BOGNA DRCT 0.000000 50.701944 -0.251547
1 EGKA ADES 7.000000 50.835600 -0.297222

Does that also work around the issue?

Regards,

Tim

Thanks for the reply.

I can confirm changing the waypoint type code to 28 does indeed fix the problem.

I understand why now too.

11 is for named fix, 28 for unnamed lat/lon which is what a user waypoint is.

Therefore my workaround worked because it lets X-Plane treat the entry as a named fix but the correct solution is change the 11 to the correct type code 28.

Seems to me when I add user waypoints Navigraph Charts is assigning type 11 when it should be assigning type 28, so is likely a Navigraph Charts bug when exporting to X-Plane 12 ?

Regards,

Mark

Seems related to:

Regards,

Tim

Clearly is similar. Now I understsnd what the issue is I’ve looked to see what it is I’m doing to cause the problem.

Answer is it’s how I export the file to X-Plane.

I’m so used to choosing “X-Plane 11/12” for the export it’s what I choose by default.

However, if I choose “X-Plane 11/12 (No SID/STAR)” then all is well for user waypoints as they get a type code 28 and the 15 character identifier becomes FIX01 FIX02 etc.

However, the issue occured when I added a RVAV approach to EGKA. Seemed OK to me to do that seeing as the Cessna Skyhawk G1000 supports RNAV, as does the Cessna 208, and EGKA has RNAV approaches.

Saving as NO SID/STAR loses the RNAV information hence exporting using “X-Plane 12” option, but that then exports user waypoints as type 11

Regards,

Mark