I am working on adding an NDB to a scenery location that does not exist using an airport with a made up ICAO. If I add an NDB within the Airport element the NDB shows up but the range is much less than I set:
<Ndb type="HH" lat="30.00000000000000" lon="-140.00000000000000" alt="0.00000000000000" frequency="370.00" range="300N" region="US" ident="NAN" name="NAN"/>
I tried putting this string outside of the Airport element using the example of the VORs at the bottom of the sample SimpleNavData files in the SDK – as I thought perhaps since the SDK says if you put it inside the Airport element it’s a terminal NDB and perhaps that limits the range? – but when rebuilding the package that line was deleted from the XML so I assume the formatting outside of the Airport element for an NDB is different.
Can anyone offer any guidance on how to do that?
And before anyone says 300nm is too far of a range for an NDB to begin with, according to https://www.casa.gov.au/sites/default/files/non-directional-beacons-associated-automatic-direction-finding.pdf over water NDB range can be as high as 600nm and my NDB is meant for over water use