Charts creates invalid FMS file vs SimBrief for same route

Charts General
1

I created a flight plan using Charts and tried to load it into the Hot Start Challenger 650 like I normally do, but it gave the error BAD ROUTE PARSE.

When I tried Simbrief instead, that flight plan was accepted.

This is the FMS file created by Charts:

I
1100 Version
CYCLE 2513
ADEP LPPD
DEPRWY RW30
SID TIMT3X
SIDTRANS TIMTO
ADES TXKF
DESRWY RW30
STAR MOMOM1
STARTRANS RNGRS
APP I30-Z
APPTRANS BIDVE
NUMENR 12
1 LPPD ADEP 259.000000 37.741900 -25.697800
11 TIMTO DRCT 0.000000 38.387778 -27.321389
11 SOLGI H115 0.000000 38.624900 -28.032672
11 ELBEN H115 0.000000 38.702683 -28.269978
3 FRS H115 0.000000 39.453583 -31.210417
11 3938N DRCT 0.000000 39.000000 -38.000000
11 3944N DRCT 0.000000 39.000000 -44.000000
11 3851N DRCT 0.000000 38.000000 -51.000000
11 3757N DRCT 0.000000 37.000000 -57.000000
11 RNGRS DRCT 0.000000 35.066667 -63.150000
11 RNGRS DRCT 0.000000 35.066667 -63.150000
1 TXKF ADES 18.000000 32.364000 -64.678700

This is the FMS plan created by SimBrief for the same route (minus the approach, which it doesn’t include):

I
1100 Version
CYCLE 2513
ADEP LPPD
DEPRWY RW30
SID TIMT3X
ADES TXKF
DESRWY RW30
STAR MOMOM1
STARTRANS RNGRS
NUMENR 12
1 LPPD ADEP 259.000000 37.741944 -25.697778
11 TIMTO DRCT 32200.000000 38.387778 -27.321389
11 SOLGI H115 36200.000000 38.624900 -28.032672
11 ELBEN H115 37000.000000 38.702683 -28.269978
3 FRS H115 40000.000000 39.453583 -31.210417
28 FIX01 DRCT 40000.000000 39.000000 -38.000000
28 FIX02 DRCT 40000.000000 39.000000 -44.000000
28 FIX03 DRCT 40000.000000 38.000000 -51.000000
28 FIX04 DRCT 40000.000000 37.000000 -57.000000
11 RNGRS DRCT 40000.000000 35.066667 -63.150000
11 RNGRS DRCT 40000.000000 35.066667 -63.150000
1 TXKF ADES 2500.000000 32.364042 -64.678703

The issue appears to be the use of 3938N vs FIX01 etc.

Just wondering if this is intentional? Is there a setting or something?

Thanks.

2

It’s the row code, Navigraph uses 11 (named fix) but then provides identifiers that do not exist as fixes in the database:

% grep -e 3938N -e 3944N -e 3851N -e 3757N -e Navigraph earth_fix.dat
1200 Version - data cycle 2513, build 20251216, metadata FixXP1200. Copyright (c) 2025 Navigraph, Datasource Jeppesen
%

Simbrief instead uses row code 28 (latitude/longitude coordinates).

Regards,

Tim

3

BTW, this is not exactly the same issue as, but arguably related to:

Regards,

Tim

4

Hi,
Yes Tim is right. It seems that we export such “unnamend fixes” with the wrong row code. It will forward this to the responsible person in the team.

Here the correct technical specs from X-Plane to this:

Screenshot_20260113_043641_Chrome
Screenshot_20260113_043641_Chrome1065×415 80.4 KB

Cheers
Richard