Jump to content

Export of NDBs to flight plan


Recommended Posts

NDB names after exporting to the PMDG FMC are given the letters NB after the name of the navigation beacon.

Example my flight plan has an NDB named SQ, loading the exported plan into PMDG's FMC, the name is SQNB

Activesky does not recognize any of those points when loading wind data.

Can you work with them to fix this or make the exported NDB just the name of the beacon without NB at the end?

Link to comment
Share on other sites

I carried out a test here and cannot identify an issue with the 'NB' suffix:

 

Please login to display this image.

 

Post your route where this fails.

 

Which AIRAC provider, is it the same provider and cycle for all addons

Link to comment
Share on other sites

On 2/6/2019 at 12:30 AM, srcooke said:

I carried out a test here and cannot identify an issue with the 'NB' suffix:

 

Please login to display this image.

 

Post your route where this fails.

 

Which AIRAC provider, is it the same provider and cycle for all addons

Forgot to explain that this is through the PMDG fmc. Loading in the legs page the wind data there is not an entry for the NBD every other line (fixes, vors) on the legs page has the wind data loaded in.

Link to comment
Share on other sites

Here I have loaded the f/p in the 777 FMC which then creates the WX.PLN that is loaded in AS:

 

Please login to display this image.

 

Please login to display this image.

 

 

 

This produces the weather file for the FMC upload ( referencing LDNB as the example):

 

KDFW        149@12(0)    181@14(0)    234@29(-4)    249@51(-17)    250@74(-28)
        244@100(-42)    235@111(-51)    237@125(-56)    249@106(-57)    253@96(-68)
GHXNB        164@18(-1)    188@18(-1)    233@24(-5)    253@47(-18)    252@68(-29)
        248@97(-43)    241@105(-52)    240@115(-56)    248@106(-57)    250@97(-68)
TOC        169@19(-1)    189@20(-1)    234@22(-5)    253@46(-18)    253@67(-29)
        249@96(-44)    243@104(-52)    241@112(-56)    248@105(-57)    249@96(-68)
LDNB        176@28(-4)    191@38(-3)    237@18(-5)    250@40(-19)    255@53(-32)
        260@90(-45)    256@98(-54)    252@100(-56)    250@104(-56)    247@85(-65)
CEPNB        146@12(0)    180@16(1)    239@23(-5)    246@33(-19)    254@55(-30)
        260@84(-45)    256@90(-55)    253@92(-58)    250@97(-56)    249@73(-64)
BXK        163@10(9)    190@16(6)    217@32(-6)    228@45(-20)    245@59(-32)
        257@87(-45)    255@91(-56)    254@92(-58)    255@89(-56)    262@70(-61)
TOD        205@11(4)    224@19(3)    230@39(-5)    234@48(-20)    245@63(-33)
        255@89(-46)    258@95(-56)    257@90(-57)    259@88(-56)    266@73(-61)
PSP        205@11(4)    224@19(3)    230@39(-5)    234@48(-20)    245@63(-33)
        255@89(-46)    258@95(-56)    257@90(-57)    259@88(-56)    266@73(-61)
KLAX        208@12(1)    226@18(0)    232@42(-7)    237@59(-22)    247@75(-33)
        257@100(-46)    258@102(-55)    258@88(-54)    262@84(-55)    268@68(-61)

 

 

Upon upload LNDB indicates:

 

Please login to display this image.

 

This looks correct ?

 

 

Link to comment
Share on other sites

On 2/9/2019 at 12:08 AM, srcooke said:

Here I have loaded the f/p in the 777 FMC which then creates the WX.PLN that is loaded in AS:

 

 

Please login to display this image.

 

 

 

This produces the weather file for the FMC upload ( referencing LDNB as the example):

 

KDFW        149@12(0)    181@14(0)    234@29(-4)    249@51(-17)    250@74(-28)
        244@100(-42)    235@111(-51)    237@125(-56)    249@106(-57)    253@96(-68)
GHXNB        164@18(-1)    188@18(-1)    233@24(-5)    253@47(-18)    252@68(-29)
        248@97(-43)    241@105(-52)    240@115(-56)    248@106(-57)    250@97(-68)
TOC        169@19(-1)    189@20(-1)    234@22(-5)    253@46(-18)    253@67(-29)
        249@96(-44)    243@104(-52)    241@112(-56)    248@105(-57)    249@96(-68)
LDNB        176@28(-4)    191@38(-3)    237@18(-5)    250@40(-19)    255@53(-32)
        260@90(-45)    256@98(-54)    252@100(-56)    250@104(-56)    247@85(-65)
CEPNB        146@12(0)    180@16(1)    239@23(-5)    246@33(-19)    254@55(-30)
        260@84(-45)    256@90(-55)    253@92(-58)    250@97(-56)    249@73(-64)
BXK        163@10(9)    190@16(6)    217@32(-6)    228@45(-20)    245@59(-32)
        257@87(-45)    255@91(-56)    254@92(-58)    255@89(-56)    262@70(-61)
TOD        205@11(4)    224@19(3)    230@39(-5)    234@48(-20)    245@63(-33)
        255@89(-46)    258@95(-56)    257@90(-57)    259@88(-56)    266@73(-61)
PSP        205@11(4)    224@19(3)    230@39(-5)    234@48(-20)    245@63(-33)
        255@89(-46)    258@95(-56)    257@90(-57)    259@88(-56)    266@73(-61)
KLAX        208@12(1)    226@18(0)    232@42(-7)    237@59(-22)    247@75(-33)
        257@100(-46)    258@102(-55)    258@88(-54)    262@84(-55)    268@68(-61)

 

 

Upon upload LNDB indicates:

 

 

This looks correct ?

 

 

 

 

Please login to display this image.

 

Please login to display this image.

Link to comment
Share on other sites

Jeppesen naming convention for 'Waypoint Identifiers'


 

Quote

 

B. NDB

 

NDB as Waypoint Concept

 

For systems employing the "NDB as Waypoint" concept, waypoints located at NDB’s will be identified by the use of the station identifier followed by the alpha characters "NB".

Examples:

Ft. Nelson NDB  YENB

Newark     NDB  EWRNB

 

 

So the NDB naming exported from PFPX looks correct.

 

Have you setup the PMDG to 'Create and Load to P3D' the WX.PLN ? Do not load a plan into AS prior.

 

Please login to display this image.

 

 

Link to comment
Share on other sites

On 2/13/2019 at 4:07 AM, srcooke said:

Jeppesen naming convention for 'Waypoint Identifiers'


 

 

So the NDB naming exported from PFPX looks correct.

 

Have you setup the PMDG to 'Create and Load to P3D' the WX.PLN ? Do not load a plan into AS prior.

 

 

 

Affirmative I have that setting and it loads the plan by itself.

Link to comment
Share on other sites

Archived

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

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy & Terms of Use