Add missing airports to Nav database?

[Maddin91]

Hi all, especially jeehell,

is there a way to manually add additional airports to the database?
I'm talking about the (not anymore existing) Kai Tak airport in Hong Kong. Everyone knows the nice scenery of FlyTampa and I'd love to fly there.

Any chance to add the airport manually into the database?

Regards,
Martin

[OmniAtlas]

Hi Martin, take a look here http://www.vapap.com/kai-tak-airport

There are manual instructions on how to hack the database, but I've never got it to work. Perhaps you will have better luck (let me know if you do!).

[Maddin91]

Thanks for the reply. But which of those corresponds to JeeHell? The Level-D Installer?

[OmniAtlas]

Read any of the manual instructions on the website - it should key you in what you should do.

I think you need to edit the

\A320FMGS\Navdata\Navdata1\navrecord.dat

and

\A320FMGS\Navdata\Navdata2\navrecord.dat

files -- this is a text file where you can put in the coordinates.

[OmniAtlas]

Any luck Martin?

JL -- could we lend a helping hand? I also found these instructions here -- http://www.kennair.com.au/wp-content...HX-Navdata.pdf

Is the JL FMGS navdata database readable with Microsoft Access?

Should we be editing the ARPT.bin file? I would also like to get the Kai Tak coordinates usable by the MCDU.

Thank you.

[jeehell]

Hi,

You can add your own navdata inside a file called additional.txt into the navdata1 and navdata2 folders (Server computer only).
Then it is compiled into the bin files which you can redistribute over the network (compilation done after deleting the old bin files of course).
I do not have any documentation on the navdata format used, but you may check the navigraph navrecord.dat to see how it works. This is based on ARINC424 format, not very easy task.

regards,
JL

[OmniAtlas]

Cheers, thansk JL -- I had a look at the navrecord.dat.

I've referenced an existing airport -- YBCG (Gold Coast) --
PG|YBCG|YB|RW14|8176|0|148|-28.156511|153.500706|21|140.0|||
PG|YBCG|YB|RW17|1909|0|059|-28.164356|153.506753|17|173.0|||
PG|YBCG|YB|RW32|8176|984|148|-28.172569|153.510920|13|320.0|||
PG|YBCG|YB|RW35|1909|0|059|-28.169594|153.506331|13|353.0|||

I Will try and figure out what this all means --

I'm assuming --

PG|airport ICAO|YB|Runway|runwaylength|?|?|coordinates|coordinates|?|?

Question mark - I still need to determine.

[jeehell]

PG entries are "runway entries", and this is the format to use:
PG|ARPT identifier|ICAO code|RWY|length|DTHR|width|latitude|longitude|elevation|mag bearing|LLZ ID|LLZ category|

You need one PG per runway direction.

But you also need one entry for the airport alone, this is a PA entry and looks like:
PA|ARPT identifier|ICAO code|latitude|longitude|elevation|speed limit|speed limit alt|transition alt|name|



And you may need one entry per ILS as well, the PI entries:
PI|ARPT identifier|ICAO code|LLZ ID|category|frequency|RWY|LLZ latitude|LLZ longitude|LLZ mag brg|GS latitude|GS longitude|GS angle|GS elevation|STN DEC|

And then you'll eventually need to code the procedure, but this starts to be really difficult, try to do the runways correctly first then we'll see for procedures.

JL

[OmniAtlas]

Cheers JL -- thank you. Will trial this out and provide you with an update. VHHX is a visual approach so we don't have to worry about ILS.

[OmniAtlas]

Success! Kai Tak, VHHX is now open for duties!



This is the information I added to additional.txt --

PA|VHHX|VH|22.316667|114.203333|15|250|F100|9000|KAI TAK INTL|
PG|VHHX|VH|RW13|10930|1864|197|22.322177|114.196318|15|136||
PG|VHHX|VH|RW31|10930|716|197|22.305538|114.215179|15|316||