Jump to content

Archived

This topic is now archived and is closed to further replies.

Tim/Rodeo314

AIRAC 1606, SBCT, PNG SIDs, bogus waypoint (IXEG data)

Recommended Posts

Hi!

 

Some users on the X-Pilot forum noticed that, in the Aerosoft-provided navdata for the IXEG 737 Classic, some SIDs end with a bogus waypoint "PNGNB" instead of the correct waypoint "PNG". I have confirmed it with cycle 1606, using PNG1A.15 as an example:

<Sid Name="PNG1A.15" Runways="15">
      <Sid_Waypoint ID="0">
        <Name>CT011</Name>
        <Type>Normal</Type>
        <Latitude>-25.653333</Latitude>
        <Longitude>-49.035667</Longitude>
        <Speed>0</Speed>
        <Altitude>5000</Altitude>
        <AltitudeCons>0</AltitudeCons>
        <AltitudeRestriction>above</AltitudeRestriction>
        <Flytype>Fly-over</Flytype>
        <BankLimit>25</BankLimit>
        <Sp_Turn>Auto</Sp_Turn>
      </Sid_Waypoint>
      <Sid_Waypoint ID="1">
        <Name>PNGNB</Name>
        <Type>Normal</Type>
        <Latitude>-25.534667</Latitude>
        <Longitude>-48.530833</Longitude>
        <Speed>0</Speed>
        <Altitude>0</Altitude>
        <AltitudeCons>0</AltitudeCons>
        <AltitudeRestriction>at</AltitudeRestriction>
        <Flytype>Fly-by</Flytype>
        <BankLimit>25</BankLimit>
        <Sp_Turn>Auto</Sp_Turn>
      </Sid_Waypoint>
    </Sid>

…there are 12 occurrences of the bogus waypoint in SBCT.xml

 

The "old" Airbus X Extended database (as used by e.g. X-Plane's GNS430) doesn't exhibit the issue (SBCT.txt):

SID,PNG1A,15,4
CF,CT011,-25.65333333,-49.03566667,0,CTB,153.6,10.2,153,10.00,2,5000,0,0,0,0,0,1
TF,PNG,-25.53466667,-48.53083333,0, ,0.0,0.0,0,0.00,0,0,0,0,0,0,0,0

FWIW, both the correct PNG and incorrect PNGNB share the same latitude/longitude coordinates.

 

I didn't keep a backup of the Aerosoft AIRAC 1509 that comes with the plane, so I don't know if it's a recent regression or an old issue.

 

Regards,

 

Tim

Share this post


Link to post
Share on other sites

That could be a feature instead of a bug, depending on the IXEG File specification:

 

https://www.faa.gov/regulations_policies/handbooks_manuals/aviation/instrument_procedures_handbook/media/Chapter_6.pdf

 

Quote

Non-directional beacons (NDBs) and locator outer markers
(LOMs) can be displayed differently than they are charted.
When the first airborne navigation databases were being
implemented,  NDBs  were  included  in  the  database  as  
waypoints  instead  of  NAVAIDs.  This  necessitated  the  use  
of five character identifiers for NDBs. Eventually, the NDBs
were  coded  into  the  database  as  NAVAIDs,  but  many  of  
the  RNAV  systems  in  use  today  continue  to  use  the  five-
character identifier. These systems display the characters
“NB” after the charted NDB identifier. Therefore, NDB ABC
would be displayed as “ABCNB.”

 

 

Regards

 

Jan-Paul

Share this post


Link to post
Share on other sites

This makes sense, though the exact same waypoint is called PNG in the airway data (e.g. UM548).

 

Shouldn't waypoint/navaid naming at least be consistent across the same database?

Share this post


Link to post
Share on other sites

Hi, it´s Jan from the IXEG team.

 

I can confirm that this is not something we desire, or asked for - it would be nice if all NDB waypoints in the dataset would be called by their real letter identifier instead of having a "NB" at the end.

 

Cheers, Jan

 

Share this post


Link to post
Share on other sites

The issue is still present in Aerosoft-provided IXEG data as of AIRAC 1608. The PNG-based SIDs at SBCT are not currently active, but there's e.g. waypoint POYNB in procedure PO1B at LFPG.

Share this post


Link to post
Share on other sites

Same again in AIRAC cycle 1609.

 

I understand this may actually be considered either a non-issue or a non-fixable issue, but some (preferably official) feedback would be welcome.

Share this post


Link to post
Share on other sites

×
×
  • Create New...