Sign in to follow this  
Elsmoko

Adding airports to FMC database

Recommended Posts

I've read a topic in the manual concerning additions to the PMDG navdata,  but don't follow it very well.

Is there "step by step" somewhere that explains how to do this with the FMC?  I'd like to add some

of the Antarctic airfields.

Thank you,

Ken Boardman

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

 

 


Is there "step by step" somewhere that explains how to do this with the FMC?

 

I can't think of any off the top of my head.  Honestly, the best thing to do would be to open the navdata AIRPORTS.txt file and have a look at the existing format and use that as an example.  It's pretty straightforward from what I remember.

Share this post


Link to post
Share on other sites

I'll give that a shot Kyle.  And do some experimenting with FMC  > perhaps I'll get lucky.

Thank you,

Ken 

Share this post


Link to post
Share on other sites

 

 


I'll give that a shot Kyle.  And do some experimenting with FMC  > perhaps I'll get lucky.

 

Definitely!  Yeah, check it out.  I haven't looked at those files in years, but I do remember getting pretty upset back in college, when the FAA/mil took the DAFIF out of public access.  I started looking into updating those files myself (mostly for SID/STARs and IAPs...because...well...college student) and I don't remember it being too hard.

 

...then again, that's now 8 years ago.

Share this post


Link to post
Share on other sites

Last year I successfully added VAPO - Pune International to my own PMDG and FSBuild nav data sets. You obviously need raw information such as the airport's LAT/LON, runway designations, length, headings, runway LAT/LON data, etc. Most of the work involved figuring out which files required data and the exact location and formats for entering it. Also, some LAT/LON conversions from DDDMMSS to decimal format will probably be needed. If there are charted approaches you can also add these to the SIDSTARS file for a given airport or create a SIDSTAR file for a new airport. This information from PMDG about the files and data formats will get you started.

 

The biggest problem is that if you're a Navigraph subscriber all of the PMDG nav data files are over-written each data cycle, so whatever new entries you make will have to be manually re-entered. You can also request that Navigraph add airports to their data sets, but I wouldn't hold your breath. About a year ago I requested that VAPO be added, even supplied most of the required information in proper formats, but never got a reply.

 

If you get stuck give me a yell.

Share this post


Link to post
Share on other sites

Thank you Kyle and Jev. I posted the below elsewhere here but I'd appreciate any tips you
could offer regarding the following:

What exactly do the "RW" and "RS" stand for at the beginning of the lines in some of the PMDG airport
data files? At first I believed that RW stood for runway, but now I'm not so sure ~:)

Also, in the wpnavapt.txt file how is a typical line decoded ? >>
example :
MEMPHIS INTL KMEM27 08946271 35.057781 -89.955856108.7027100292

Some of the data is obvious of course. And I'm guessing that the "08946271" refers to length and heading. And that
appears to be followed by Lat / Lon. I guess what puzzles me most is the length of the Longitude, especially where
it extends past the second decimal point.

Best regards,
Ken

Share this post


Link to post
Share on other sites

Here's how it actually works - I'll use the KPHX Runway 26 entry as an example with color coding so you can see the fields easier:

 

PHOENIX SKY HARBOR INTL KPHX26 11489258 33.440822-111.992136111.7525801135
 

PHOENIX SKY HARBOR INTL - airport name
KPHX26 - runway identifier

11489 - runway length in feet

258 - runway heading

33.440822 - latitude of the runway threshold on the centerline

-111.992136  - longitude of the runway threshold on the centerline

111.75 - ILS frequency (is 000.00 if none exists)

258  - ILS front course (note this isn't always the same as the heading)

01135 - altitude of the runway in feet

 

Also - very important point:

Everything in this file needs to be sorted precisely by ascending latitude. You can't just put an airport in at the end. A bunch of aspects of how we sort things on the ND depend on this ordering and if you mess it up, you'll get all kinds of wrong data showing up - stuff like the wrong terrain displayed in the NGX and 777 etc.

Share this post


Link to post
Share on other sites

What exactly do the "RW" and "RS" stand for at the beginning of the lines in some of the PMDG airport

data files? At first I believed that RW stood for runway, but now I'm not so sure ~:)

 

Ken,

 

I didn't deal with the ARPT_RWY.dat file when I was working on VAPO, but from studying the entries for my local airport (see below), this is what I suggest.

AP;KFLL;FT LAUDERDALE-HOLLYWOOD ;26.072583;-80.152750;6
RW;10L;26.076942;-80.164783;6;11010;096;096;9000
RW;28R;26.076803;-80.140969;5;11070;276;276;9000
FS;09L;26.076948;-80.166573;9;11010;095;095;9000
FS;09R;26.065964;-80.160316;9;10850;095;095;5276
FS;13;26.078892;-80.160393;9;10935;141;141;6930
FS;27L;26.065872;-80.144203;9;0;275;275;5276
FS;27R;26.076792;-80.139091;9;11070;275;275;9000
FS;31;26.065346;-80.145546;9;0;321;321;6930

The lines beginning with "RW" are current working runways. For example, with a huge construction project now underway at KFLL, there is only one working rwy: 10L-28R.

 

Lines beginning with "FS" are

 

- unused designations (for example, KFLL10L-28R used to be  09L-27R)

- runways that are now closed

 

Also, even if a runway hasn't closed or been redesignated, the LAT/LON may have changed since 2007, so these FS entries also display the LAT/LON values in the default FSX database.

 

So, in the case of KFLL, 09L-27R is now an unused designation due to the runway being renamed 10L-28R. Runways 09R-27L and 13-31 are both currently closed. Runway 09R-27L is being considerably lengthened and will reopen sometime later this year as 10R-28L, so this will appear in the file with a "RW" code when that happens. Runway 13-31 is probably closed forever.

 

So the FS lines, I believe, are the runway listings as they appear in the stock FSX runways database, and many are now incorrect. Hope this is correct.

 

And, thanks to Ryan for the great post deciphering the airports data. The color coding was pure genius!

Share this post


Link to post
Share on other sites

The ARPT_RWY.dat file is not something you ever need to edit - it's a cache of sorts that the FMC uses, it'll generate the data as it needs it.

 

RW = real world, FS = FSX. It's a way of cataloging differences between the real life navdata and FSX's world.

Share this post


Link to post
Share on other sites

OK Ryan. Sorry for stirring up the old thread on this.  It happened by reflex while I was doing what a

good poster should do, by looking for answers in threads that already exist. I forgot about this thread.

I'm old, butt I'm forgetful. 

  I've been trying for a few days to add a few "Antarctica X" airports to the navdata and I've not been

100% successful as yet.  With respect to earlier replies, I've not made changes to the ARPT_RWY.dat file

and I'm working with just the airports.dat, and wpnavapt.txt files. I've used the VHHX manual installation

guide(for PMDG FMC) to get me in the ballpark, but I'm obviously overlooking something. Can't get the FMC

to accept my NZPGNZCH saved (FS Commander) flight plan when entered in the "co route" block; and the NZPG

runways don't appear on the DEParture page. The lines below illustrate what I've done so far. I used

ADE160 to open the NZPG scenery (bgl) file to obtain runway specs and then ran the T7 in FSX

and let new lines be created in the ARPT_RWY.dat. I then changed data the McMurdo NZPG lines below

as necessary to match what appeared in the ARPT_RWY.dat file.

 

wpnavapt.txt NZPG lines :

 

MCMURDO STATION PEG NZPG08 10000309-77.957161 166.551514000.0030900000

MCMURDO STATION PEG NZPG15 11024016-77.952072 166.489395000.0001600000

MCMURDO STATION PEG NZPG26 10000129-77.958916 166.682709000.0012900000

MCMURDO STATION PEG NZPG33 11024196-77.980484 166.538956000.0019600000

ROTHERA EGAR18 02875180-67.563833 -68.123333000.0018000013

ROTHERA EGAR36 02875000-67.571167 -68.130833000.0000000013

WILKINS YWKS09 10499094-66.689686 111.487472000.0009402353

WILKINS YWKS27 10499274-66.691970 111.559683000.0027402519

 

The airport.dat line for NZPG follows >

 

NZPG-77.955197 166.522621

EGAR-67.570500 -68.129333

YWKS-66.690833 111.525000

 

Regards,

Ken

Share this post


Link to post
Share on other sites

Update, I've got the NZPG rwys appearing in the FMC now and it all looks good, except I still can't

enter the flight plan via the "co route" block and when I select the runway and approach procedure

for the DESTination airport (NZCH), the FMC gives me a "PIN" error on the scratch pad and gives

a lit Execute light that won't extinguish when pressed, and the FMC generally stops working correctly.

If I try to pursue the issue then the FMC stops functioning altogether (freezes).

What's a "PIN" error?

Ken

Share this post


Link to post
Share on other sites

Maybe proximity to the South Pole is hampering this. I'm nearly positive I've accomplished the necessary

steps correctly. I've started from scratch several times after restoring the original nav data files.

I've tried using the VHHX manual modification guide(for PMDG db) . I've tried using the guide offered by

PMDG @ >>

http://support.precisionmanuals.com/kb/a60/pmdg-navdata-glossary

 

After all this, when the original nav data is restored the FMC still works "as advertised". Amazing !! >

It should be tied in knots by now ~:)

But I'd still like to know what a "Program PIN error" is.

Ken

Share this post


Link to post
Share on other sites

Program PIN Error means the FMC crashed internally (this is what the real unit says if something happens too). There's something in your FS Commander files causing that. (this program seems to be really terrible, I always get complaints like this about routes made with it at support)

 

I would try creating and saving your routes inside the actual FMC. Those should always work.

Share this post


Link to post
Share on other sites

Thank you for the info about Pin Error Ryan. Although I've successfully exported hundreds of routes to the PMDG FMC

and been able to successfully enter them into the FMC via the "co route" block, I will look into this as best I can.

I am able to enter the NZPGNZCH route and waypoints via the DEP and DEST blocks and the route pages, but then the FMC

fails when I enter the NZCH arrival / procedure / STAR.

Everything returns to normal (thankfully ~:) after the original FMC nav data files are restored to the ..\PMDG\Navdata

folder.

I consider this still a "work in progress", but I'm back to flying now...... I will appreciate any additional

suggestions that you or others may have. If VHHX can be successfully added to the PMDG database, then so should

NZPG, NZIR, and NZWD (just my thoughts ~:)

Best regards,

Ken

Share this post


Link to post
Share on other sites

Last year I successfully added VAPO - Pune International to my own PMDG and FSBuild nav data sets. You obviously need raw information such as the airport's LAT/LON, runway designations, length, headings, runway LAT/LON data, etc. Most of the work involved figuring out which files required data and the exact location and formats for entering it. Also, some LAT/LON conversions from DDDMMSS to decimal format will probably be needed. If there are charted approaches you can also add these to the SIDSTARS file for a given airport or create a SIDSTAR file for a new airport. This information from PMDG about the files and data formats will get you started.

 

The biggest problem is that if you're a Navigraph subscriber all of the PMDG nav data files are over-written each data cycle, so whatever new entries you make will have to be manually re-entered. You can also request that Navigraph add airports to their data sets, but I wouldn't hold your breath. About a year ago I requested that VAPO be added, even supplied most of the required information in proper formats, but never got a reply.

 

If you get stuck give me a yell.

Hi, I have installed the AIRAC1412 for PMDG and ProATCx, but still in the FMC "VAPO" doesnt show up, no SID and no STAR. likewise many airports are missing in India, Middle East... Could you help me how can i update details into the navdata and to which all folders, also from where to obtain the details. it will be of really great help if you could guide me step by step. Thank you. 

Jobin.

Share this post


Link to post
Share on other sites

Jobin, full names in the PMDG forums please.

 

The information in the post that you copied should get you started.  Don't expect anybody to help you step by step, you should just jump in and start learning.  The biggest problem is finding the airport information and I am no help in that part of the world.  I could use Google earth to defing the location of the airport and runways but without charts or data files I have no idea how to define the navaids.

 

I suspect that the reason Navigraph does not provide VAPO is because they do not receive the information from their data source, and the reason for that is because Prune is a military base with civilian operations limited to the civilian ramps and terminals. I'm just guessing based on a quick browse of the Wikipedia article on the location.

Share this post


Link to post
Share on other sites

OK Ryan. Sorry for stirring up the old thread on this.  It happened by reflex while I was doing what a

good poster should do, by looking for answers in threads that already exist. I forgot about this thread.

I'm old, butt I'm forgetful. 

  I've been trying for a few days to add a few "Antarctica X" airports to the navdata and I've not been

100% successful as yet.  With respect to earlier replies, I've not made changes to the ARPT_RWY.dat file

and I'm working with just the airports.dat, and wpnavapt.txt files. I've used the VHHX manual installation

guide(for PMDG FMC) to get me in the ballpark, but I'm obviously overlooking something. Can't get the FMC

to accept my NZPGNZCH saved (FS Commander) flight plan when entered in the "co route" block; and the NZPG

runways don't appear on the DEParture page. The lines below illustrate what I've done so far. I used

ADE160 to open the NZPG scenery (bgl) file to obtain runway specs and then ran the T7 in FSX

and let new lines be created in the ARPT_RWY.dat. I then changed data the McMurdo NZPG lines below

as necessary to match what appeared in the ARPT_RWY.dat file.

 

wpnavapt.txt NZPG lines :

 

MCMURDO STATION PEG NZPG08 10000309-77.957161 166.551514000.0030900000

MCMURDO STATION PEG NZPG15 11024016-77.952072 166.489395000.0001600000

MCMURDO STATION PEG NZPG26 10000129-77.958916 166.682709000.0012900000

MCMURDO STATION PEG NZPG33 11024196-77.980484 166.538956000.0019600000

ROTHERA EGAR18 02875180-67.563833 -68.123333000.0018000013

ROTHERA EGAR36 02875000-67.571167 -68.130833000.0000000013

WILKINS YWKS09 10499094-66.689686 111.487472000.0009402353

WILKINS YWKS27 10499274-66.691970 111.559683000.0027402519

 

The airport.dat line for NZPG follows >

 

NZPG-77.955197 166.522621

EGAR-67.570500 -68.129333

YWKS-66.690833 111.525000

 

Regards,

Ken

Hello everybody,

i have inserted thoose lines in a rispective navdata folder,planning a fly to NZPG.

a step forward is done,before FMC(using 777 PMDG for FSX)was sayng not in data base,now is accepting the ICAO,but but still keep says "none" about rwy for ARR/DEP.

Any others suggestions?

Thank you!

Fabio

Share this post


Link to post
Share on other sites

The 777 also has a arpt_rwy.dat file in the navdata folder, acts as cache to reduce memory load.  Erase the file, the 777 will build a new one and should include your add-ons to the navdata.

Share this post


Link to post
Share on other sites

 

 


Hello everybody,

i have inserted thoose lines in a rispective navdata folder,planning a fly to NZPG.

a step forward is done,before FMC(using 777 PMDG for FSX)was sayng not in data base,now is accepting the ICAO,but but still keep says "none" about rwy for ARR/DEP.

Any others suggestions?

Thank you!

Fabio

 

Hi, Fabio,

 

I just tried it and it's working for me.  So, a couple of things:

 

1) Don't try to edit  ARPT_RWY.dat.  It's a cache as Dan said.  However you might try deleting it and letting it rebuild after you've made the NZPG entries and saved the files.  It will rebuild the next time you load the 777.  That might be the source of your problem.

 

If that doesn't work:

 

2) You only need to enter the following lines in WPNavApt.txt; the ones coming after are there only to illustrate the proper placement of the NZPG lines.  As it turns out, they go at the very beginning of the file after the header stuff -- first entry -- because MCMurdo is further south than any other airport.

 

MCMURDO STATION PEG NZPG08 10000309-77.957161 166.551514000.0030900000
MCMURDO STATION PEG NZPG15 11024016-77.952072 166.489395000.0001600000
MCMURDO STATION PEG NZPG26 10000129-77.958916 166.682709000.0012900000
MCMURDO STATION PEG NZPG33 11024196-77.980484 166.538956000.0019600000

 

3) Same for Airports.dat:

NZPG-77.955197 166.522621

 

Again, at the head of the file after header, the very first entry.  When you're done, the entries should look the same as the ones you copied from Ken.

 

If this doesn't work, please post your entries for the two files.

 

Hope this helps!

 

Mike

 

PS: PMDG wants you to use your full name in its forums.

Share this post


Link to post
Share on other sites

Hello Mike.

thank you for the help!

I never tryed to edit the ARPT.RWY.DAT.(so nevere touch it)

I follewed your tips i did reinsert

:

1)Airports.dat:

NZPG-77.955197 166.522621

2)WPNavApt.txt

MCMURDO STATION PEG NZPG08 10000309-77.957161 166.551514000.0030900000
MCMURDO STATION PEG NZPG15 11024016-77.952072 166.489395000.0001600000
MCMURDO STATION PEG NZPG26 10000129-77.958916 166.682709000.0012900000
MCMURDO STATION PEG NZPG33 11024196-77.980484 166.538956000.0019600000

 

Still NZPG in database on FMC, but still no rwys.......

 

Waiting for good news

Regards

Fabio


I have forgot as Dan says i went to ARPT_RWY.dat it rebuild and write this:

AP;NZPG;;77.955197;166.522621;0

 

but there are no rwys as are in other airport,is it normal?

 

Fabio

Share this post


Link to post
Share on other sites

Begening of airport.dat:

;Worldwide Navigation Database
;Exported via DFD v1.0 16.0719
;Software copyright © 2016 Richard Stefan, NAVData-Service
;Support available via forum at http://forum.navigraph.com
;
;Data provided by Navigraph - www.navigraph.com
;Source data copyright © 2016 Jeppesen
;This data may be used for ground based recreational computer game
;simulation software only, and may not be recompiled, interpreted,
;or distributed for any purpose without the written consent of Navigraph.
;The contents of this database is dated and must not be used for real
;world navigation as it is unlawful and unsafe to do so.
;
;------------------------------------------------------
;AIRAC Cycle : 1608 (21/JUL/2016 - 17/AUG/2016) - Ver.1
;------------------------------------------------------
NZPG-77.955197 -166.522621
EGAR-67.570500 -68.129333
YWKS-66.691111 111.526667
SAWB-64.216667 -56.633333
SCRM-62.190833 -58.986667
SCGZ-54.931111 -67.626111
SAWH-54.843333 -68.295556
SCFN-53.800000 -69.270556
SAWE-53.777500 -67.750000
SCDW-53.601944 -70.477222
SCFM-53.253611 -70.319167
SCCI-53.003611 -70.853611
SCSB-52.736667 -69.333611
EGYP-51.821789 -58.456111
SFAL-51.685900 -57.777406
SCNT-51.670833 -72.528611
SAWT-51.609167 -72.221667
SAWG-51.608889 -69.312778
SCGD-50.970000 -72.419444
SAWC-50.280278 -72.053333
SAWU-50.017778 -68.580278
SAWJ-49.306667 -67.802778

as well wpnavapt.txt

;Worldwide Navigation Database
;Exported via DFD v1.0 16.0719
;Software copyright © 2016 Richard Stefan, NAVData-Service
;Support available via forum at http://forum.navigraph.com
;
;Data provided by Navigraph - www.navigraph.com
;Source data copyright © 2016 Jeppesen
;This data may be used for ground based recreational computer game
;simulation software only, and may not be recompiled, interpreted,
;or distributed for any purpose without the written consent of Navigraph.
;The contents of this database is dated and must not be used for real
;world navigation as it is unlawful and unsafe to do so.
;
;------------------------------------------------------
;AIRAC Cycle : 1608 (21/JUL/2016 - 17/AUG/2016) - Ver.1
;------------------------------------------------------
MCMURDO STATION PEG NZPG08 10000309-77.957161 166.551514000.0030900000
MCMURDO STATION PEG NZPG15 11024016-77.952072 166.489395000.0001600000
MCMURDO STATION PEG NZPG26 10000129-77.958916 166.682709000.0012900000
MCMURDO STATION PEG NZPG33 11024196-77.980484 166.538956000.0019600000
ROTHERA                 EGAR18 02875180-67.563833 -68.123333000.0018000013
ROTHERA                 EGAR36 02875000-67.571167 -68.130833000.0000000013
WILKINS                 YWKS09 10499094-66.689686 111.487472000.0009402549
WILKINS                 YWKS27 10499274-66.691969 111.559683000.0027402549
BASE MARAMBIO           SAWB06 04134060-64.242222 -56.641111000.0006000760
BASE MARAMBIO           SAWB24 04134240-64.236667 -56.618611000.0024000760
TTE. RODOLFO MARSH MARTISCRM11 04239106-62.187794 -58.997231000.0010600147
TTE. RODOLFO MARSH MARTISCRM29 04239286-62.193869 -58.976097000.0028600147
GUARDIAMARINA ZANARTU   SCGZ08 04724078-54.930747 -67.637325000.0007800088
GUARDIAMARINA ZANARTU   SCGZ26 04724258-54.931472 -67.614894000.0025800088
MALVINAS ARGENTINAS     SAWH07 09186072-54.844050 -68.314650000.0007200102
MALVINAS ARGENTINAS     SAWH25 09186252-54.842575 -68.276472111.3025200102
RUSSFIN                 SCFN09 04105090-53.800000 -69.270556000.0009000600
RUSSFIN                 SCFN27 04105270-53.800000 -69.270556000.0027000600
RIO GRANDE              SAWE07 06562075-53.777997 -67.764669000.0007500065
RIO GRANDE              SAWE25 06562255-53.777203 -67.734369109.5025500065
ALMIRANTE SCHROEDERS    SCDW04 03937040-53.604950 -70.484764000.0004000160
ALMIRANTE SCHROEDERS    SCDW12 04905120-53.597088 -70.485092000.0012000160
ALMIRANTE SCHROEDERS    SCDW22 03937220-53.598907 -70.469673000.0022000160
ALMIRANTE SCHROEDERS    SCDW30 04905300-53.606770 -70.469345000.0030000160
CAPITAN FUENTES MARTINEZSCFM03 03150030-53.251785 -70.332458000.0003000104
CAPITAN FUENTES MARTINEZSCFM09 08202096-53.249867 -70.336908000.0009600104
CAPITAN FUENTES MARTINEZSCFM21 03150210-53.246628 -70.324127000.0021000104
CAPITAN FUENTES MARTINEZSCFM27 08202276-53.257569 -70.301619000.0027600104
CARLOS IBANEZ DEL CAMPO SCCI01 05502015-53.008008 -70.854997000.0001500139
CARLOS IBANEZ DEL CAMPO SCCI07 09153075-53.001153 -70.875386000.0007500139
CARLOS IBANEZ DEL CAMPO SCCI12 07874125-52.997547 -70.868700000.0012500139
CARLOS IBANEZ DEL CAMPO SCCI19 05502195-52.994792 -70.842981000.0019500139
CARLOS IBANEZ DEL CAMPO SCCI25 09153255-53.000619 -70.833792109.9025500139
CARLOS IBANEZ DEL CAMPO SCCI30 07874305-53.013786 -70.845169000.0030500139
FRANCO BIANCO           SCSB01 03937014-52.736906 -69.344581000.0001400106
FRANCO BIANCO           SCSB07 04921074-52.737486 -69.344631000.0007400106

 

Fabio

Share this post


Link to post
Share on other sites

Hard to tell from the post because it has proportional character spacing, but in the wpnavapt.txt file the character position is important. I've posted a decode file in the AVSIM forum several years ago but here you go for convenience:

wpnavapt.txt AIRPORT DEFINITION FILE

....|....1....|....2....|....3....|....4....|....5....|....6....|....7....

ORLANDO INTL            KMCO17L09000184 28.443697 -81.282581110.9518400090
ORLANDO INTL            KMCO17R10000184 28.435611 -81.295881111.7518400090
ORLANDO INTL            KMCO18L12005184 28.448333 -81.322306000.0018400093
ORLANDO INTL            KMCO18R12004184 28.448295 -81.326975111.9018400093
LOS ANGELES INTERNATIONAKLAX24L10285249 33.950189-118.401664111.7025000111
LOS ANGELES INTERNATIONAKLAX24R08925249 33.952100-118.401945108.5024900117
LOS ANGELES INTERNATIONAKLAX25L11095249 33.937359-118.382708109.9024900098
LOS ANGELES INTERNATIONAKLAX25R12091249 33.939553-118.382906111.1025000094
FRANKFURT               EDDF25C13123248 50.045128   8.586981111.5524800364
FRANKFURT               EDDF25L13123248 50.040053   8.586531111.1524800362
FRANKFURT               EDDF25R09186248 50.045825   8.533717111.3524800353


1-24     Airport Name
25-28    Airport ICAO
29-31    Runway Designation (Two digits use leading zero if 1-9)
         Runway Designation column 31 = L C R or space only.
32-36    Runway Length (feet)
37-39    Runway Heading (magnetic, Three digits use leading zeros if 0-99)
40-49    Latitude signed decimal degrees (+N –S)
50-60    Longitude signed decimal degrees (+E –W)
              Note Lat/Lon fields are right justified
61-66    Localizer/ILS/LDA frequency (MHz)
67-69    Localizer/ILS/LDA Course (Three digits)
70-74    Runway Altitude (ft msl)

Share this post


Link to post
Share on other sites

 

 


but there are no rwys as are in other airport,is it normal?

 

Hi, Fabio,

 

To follow up on Dan's point, I think if you have any tabs instead of spaces that may mess things up.  Make sure all of your entries line up exactly with the next entry below.  "NZPG" in all the runway entries should be spaced (not tabbed) so that it lines up exactly with EGAR and all the later airports and runways listed.

 

BTW I just checked ARPT_RWY.dat and it did pick up NZPG even though I hadn't deleted it and allowed it to rebuild.  It even shows the discrepancy between the added data and the missing runway (8/26) in the FSX stock scenery.

 

Just a quick question: Where are you looking for the runways?  I see them on the CDU approach page on the right.  Of course there are no STARs as there is no separate STAR file in FSX/PMDG/SIDSTARS. 

 

Mike

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
Sign in to follow this