chkl

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?

Share this post


Link to post
Share on other sites

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

 

as-ndb.thumb.jpg.dcf7bc1f94a6e5f4dcb38a3005613dd4.jpg

 

Post your route where this fails.

 

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

Share this post


Link to post
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:

 

as-ndb.thumb.jpg.dcf7bc1f94a6e5f4dcb38a3005613dd4.jpg

 

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.

Share this post


Link to post
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:

 

777-fmc-pln.jpg.22e076d7e7321d36ac47ebbd4604323a.jpg

 

777-as-pln.thumb.jpg.9419146ba339c40b2c992cbf0594dc22.jpg

 

 

 

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:

 

777-lndb-wx.jpg.df99411dd953b79850db417754f25f50.jpg

 

This looks correct ?

 

 

Share this post


Link to post
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:

 

777-fmc-pln.jpg.22e076d7e7321d36ac47ebbd4604323a.jpg

 

777-as-pln.thumb.jpg.9419146ba339c40b2c992cbf0594dc22.jpg

 

 

 

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:

 

777-lndb-wx.jpg.df99411dd953b79850db417754f25f50.jpg

 

This looks correct ?

 

 

 

 

hLua2wa.jpg

 

NTmnGX3.jpg

Share this post


Link to post
Share on other sites
20 hours ago, srcooke said:

Identified and submitted to the developer.

 

 

Who is the developer at fault, Activesky, pmdg? Thanks!

Share this post


Link to post
Share on other sites

Without access to the AIRAC data I cannot say so will await a response.

 

I'm aware Navigraph/Jeppesen use the NB suffix.

Share this post


Link to post
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.

 

capture_001_13022019_123802.jpg.28bd4b36bc9d2d6130d7a9a78080a03e.jpg

 

 

Share this post


Link to post
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.

 

capture_001_13022019_123802.jpg.28bd4b36bc9d2d6130d7a9a78080a03e.jpg

 

 

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

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now