RL18

RWY N/A issues with PMDG 737

Recommended Posts

Hello,

I made an airport by the AirportDesignEditor. I tried to implement the runway data into the database of the PMDG737. When I start at this airport and try to make a flightplan I get an error message when I put in the ICAO Airport code in the FMC. The message is: ''ERR: 18L RWY N/A''. And when I put it in I just see a white circle which symbolizes my airport on the navigation display and nothing when I didn't put it in. I just see then the blue circles of the other airports.

 

How can I fix the problem??

Share this post


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

Normally, the solution would be to delete ARPT_RWY.dat in the NavData folder, restart the simulator, and let it rebuild, so I'd try that first. If that doesn't work, since you made an airport yourself, you may have to open that file up and see what needs to be done. Make sure you back your files up, though, because if you do update the AIRAC, it'll overwrite what you put in.

Share this post


Link to post
Share on other sites
45 minutes ago, Captain Kevin said:

Normally, the solution would be to delete ARPT_RWY.dat in the NavData folder, restart the simulator, and let it rebuild, so I'd try that first. If that doesn't work, since you made an airport yourself, you may have to open that file up and see what needs to be done. Make sure you back your files up, though, because if you do update the AIRAC, it'll overwrite what you put in.

The NGX doesn't use this like the 777 and 747 do, I don't believe.

Moreover, this isn't an issue of that file getting out of sync. The OP stated that he modified the files himself, which means that the error is a result of his own actions.

1 hour ago, RL18 said:

How can I fix the problem??

It's not really a problem, as much as it's not knowing how to properly edit the files you've edited.

See here:

https://library.avsim.net/download.php?DLID=164933

NOTE: Full names - first and last - are required here in the forum.

Share this post


Link to post
Share on other sites

A common error when editing those wpNAVApt.txt files is using a Tab instead of Space.... all white space in the file has to be spaces.  The column position is significant.

Share this post


Link to post
Share on other sites
22 hours ago, RL18 said:

I made an airport by the AirportDesignEditor. I tried to implement the runway data into the database of the PMDG737. When I start at this airport and try to make a flightplan I get an error message when I put in the ICAO Airport code in the FMC. The message is: ''ERR: 18L RWY N/A''. And when I put it in I just see a white circle which symbolizes my airport on the navigation display and nothing when I didn't put it in. I just see then the blue circles of the other airports.

 

21 hours ago, scandinavian13 said:

It's not really a problem, as much as it's not knowing how to properly edit the files you've edited.

Kyle, thanks for the data format file.

RL18, is this an entirely new airport or a renaming of an existing one (FAJS>FAOR for example)?

If this is an entirely new airport or new ICAO, it seems to me that you will also need to make an entry for it in Airports.dat of latitude and longitude.  This file appears to have the airports listed in order of Latitude as will be evident by looking at the file.  It will be overwritten by the next Airac update too.  

I'm not sure if this will work without an [ICAO].txt file in SIDSTARS even if there are no SIDs/STARs or approaches.

Mike

 

 

Share this post


Link to post
Share on other sites
On 4/23/2018 at 1:22 PM, Mike777 said:

I'm not sure if this will work without an [ICAO].txt file in SIDSTARS even if there are no SIDs/STARs or approaches

In the unlikely case where there are no terminal procedures, the FMS will still recognize an airport that is correctly entered into wpNavAPT.txt and Airports.dat. However, even the least significant GA airports will usually have a VOR or RNV approach.

Share this post


Link to post
Share on other sites
1 hour ago, downscc said:

In the unlikely case where there are no terminal procedures, the FMS will still recognize an airport that is correctly entered into wpNavAPT.txt and Airports.dat. However, even the least significant GA airports will usually have a VOR or RNV approach.

Hi Dan,

Thanks for clearing that up!  Also thanks for drawing up the PMDG Navdata to which Kyle linked.

Mike

Share this post


Link to post
Share on other sites
On 4/22/2018 at 11:15 PM, scandinavian13 said:

The NGX doesn't use this like the 777 and 747 do, I don't believe.

Moreover, this isn't an issue of that file getting out of sync. The OP stated that he modified the files himself, which means that the error is a result of his own actions.

It's not really a problem, as much as it's not knowing how to properly edit the files you've edited.

See here:

https://library.avsim.net/download.php?DLID=164933

NOTE: Full names - first and last - are required here in the forum.

I entered the neccesary data like it was given in the structure of https://library.avsim.net/download.php?DLID=164933.

Then I made a new folder of the new airport in SIDSTARS and entered the runways of the airport like how in the other airport folders. I entered just that:

RNWS
RNW 18L
RNW 18R
RNW 36L
RNW 36R
ENDRNWS

Share this post


Link to post
Share on other sites
23 minutes ago, RL18 said:

I still get an Error.

Then you're still doing it incorrectly.

Share this post


Link to post
Share on other sites

What steps are to do when I want to insert a new created airport into the navdata of the PMDG737?

Share this post


Link to post
Share on other sites
1 hour ago, RL18 said:

What steps are to do when I want to insert a new created airport into the navdata of the PMDG737?

The FMC requires that your airport exist in at least airport.dat and wpNavApt.txt navdata files.  If your airport has any approaches or other terminal procedures then those must be defined in a sidstar file to be available in the FMC.

Share this post


Link to post
Share on other sites

Yes and I put the data into this two files. Also I made a file in SIDSTARS for my airport. For now there is only one runway for testing.

FIXES
FIX TT010 LATLON N 30 25.592160 W 18 57.165360
FIX TT012 LATLON N 30 17.592900 W 18 57.171660
FIX TT001 LATLON N 30 3.759480 W 18 57.184320
FIX IF36L LATLON N 30 3.759180 W 19 1.795800
FIX FF36L LATLON N 30 7.759140 W 19 1.795800
ENDFIXES


RNWS
RNW 36L
ENDRNWS

STARS
STAR TT01Z2 FIX TT010 FIX TT012
  RNW 36L
ENDSTARS

APPROACHES
APPROACH 36L FIX FF36R AT OR ABOVE 2000 RNW 36L TRK 358 UNTIL 1000 TURN LEFT DIRECT FIX TT012 4000
 TRANSITION TT012 FIX TT012 AT OR ABOVE 4000 FIX TT001 AT OR ABOVE 3000 FIX AT OR ABOVE 2000
ENDAPPROACHES

 

But I still get an error :''LN:1 ERR AT FIXES''

Here is a picture of the routes(coulered red) with the marked fixes (coulered yellow) and the runways(coulrede green) http://www.directupload.net/file/d/5078/79ogajwm_png.htm

The orange line is the go around route with a left turn at 1000ft direct to TT012.

So what went wrong???

Edited by RL18

Share this post


Link to post
Share on other sites
2 hours ago, RL18 said:

 

But I still get an error :''LN:1 ERR AT FIXES''

Hi RL18,

Dan, DOWNSCC, said you don't need a SIDSTAR file.  He is very knowledgeable, so I suggest  you remove it to eliminate an additional complication.  Please post your entries for Airports.dat and WPNavAirport.txt  and the other airport entries immediately around them.

Mike

Share this post


Link to post
Share on other sites

Ok. I deleted this file. I get no error messages. But when I want to to have approach procedures what is wrong in my code of my last post?

Share this post


Link to post
Share on other sites
4 minutes ago, RL18 said:

But when I want to to have approach procedures what is wrong in my code of my last post? 

I don't know the code well  enough to answer, but if you have a discrepancy between the runways in WPNavAPT.txt and the runways in the SIDSTAR file for that airport, you are likely to get an error. 

Mike

Share this post


Link to post
Share on other sites

You have a fix,  "FF36R" that is not defined in your list of fixes.

Mike

Share this post


Link to post
Share on other sites

Ohhh yes. Thank you! And I forgot to insert a Fix in the Transition line. So this is my actual version:

FIXES
FIX TT010 LATLON N 30 25.592160 W 18 57.165360
FIX TT012 LATLON N 30 17.592900 W 18 57.171660
FIX TT001 LATLON N 30 3.759480 W 18 57.184320
FIX IF36L LATLON N 30 3.759180 W 19 1.795800
FIX FF36L LATLON N 30 7.759140 W 19 1.795800
ENDFIXES


RNWS
RNW 36L
ENDRNWS

STARS
STAR TT01Z2 FIX TT010 FIX TT012
  RNW 36L
ENDSTARS

APPROACHES
APPROACH 36L FIX FF36L AT OR ABOVE 2000 RNW 36L TRK 358 UNTIL 1000 TURN LEFT DIRECT FIX TT012 4000
 TRANSITION TT012 FIX TT012 AT OR ABOVE 4000 FIX TT001 AT OR ABOVE 3000 FIX IF36L AT OR ABOVE 2000
ENDAPPROACHES

Now I don't get an error of my fixes but for runway. XD

''TTTT ERR: 36L RWY N/A''

TTTT is the ICAO code of my airport. And yes I checked if this already existing. But that is not the case.

Edited by RL18

Share this post


Link to post
Share on other sites

If you have both runways in WPNavApt.txt and only one in SIDSTAR file you will probably get an error.

Mike

Share this post


Link to post
Share on other sites

I processed my file in SIDSTARS. Also I deleted the runway 18L and 36R. So now I have the two runway numbers 18R and 36L. I renamed it to 18 and 36. Now I have this code but I still get the same annoying error: ''TTTT ERR: 18 RWY N/A''

FIXES
FIX TT010 LATLON N 30 25.592160 W 18 57.165360
FIX TT012 LATLON N 30 17.592900 W 18 57.171660
FIX TT001 LATLON N 30 3.759480 W 18 57.184320
FIX IF36L LATLON N 30 3.759180 W 19 1.795800
FIX FF36L LATLON N 30 7.759140 W 19 1.795800
FIX IF18R LATLON N 30 25.594980 W 19 1.795800
FIX FF18R LATLON N 30 21.595020 W 19 1.795800
FIX TT003 LATLON N 30 11.758680 W 18 57.178080
ENDFIXES


RNWS
RNW 18
RNW 36
ENDRNWS

STARS
STAR TT01Z2 FIX TT010 FIX TT012
  RNW 36
STAR TT00Z2 FIX TT001 FIX TT003
  RNW 18
ENDSTARS

APPROACHES
APPROACH 36 FIX FF36L AT OR ABOVE 2000 RNW 36 TRK 358 UNTIL 1000 TURN LEFT DIRECT FIX TT012 4000
 TRANSITION TT012 FIX TT012 AT OR ABOVE 4000 FIX TT001 AT OR ABOVE 3000 FIX IF36L AT OR ABOVE 2000
APPROACH 18 FIX FF18R AT OR ABOVE 2000 RNW 18 TRK 178 UNTIL 1000 TURN RIGHT DIRECT FIX TT003 4000
 TRANSITION TT003 FIX TT003 AT OR ABOVE 4000 FIX TT010 AT OR ABOVE 3000 FIX IF18R AT OR ABOVE 2000
ENDAPPROACHES

The actuell routes http://www.directupload.net/file/d/5079/pgtlwtyk_png.htm

Edited by RL18

Share this post


Link to post
Share on other sites

Verify your wpNavAPT.txt file has entries for both runways 18 and 36.

Here is the decode for that file for ya:

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)

I'm not any smarter than anyone else on this stuff, but I created sidstar files for a couple of years until Stephan joined Navigraph so there is a little experience. Once you've done a couple it gets easy.

Share this post


Link to post
Share on other sites

Yes I did it like this for both runways. Annother thing I noticed is when I put in the file WPNAVFIX new fixes the FMC give the message:''NOT IN DATA BASAE''.

Share this post


Link to post
Share on other sites

Full names on all posts in the PMDG forums please.  You might find it helpful to create your signature using your forum profile settings.

Your files may look the same, but if you get errors then maybe you are using TAB instead of spaces?? All white space must be space characters.  Also, I don't know how we got to wpNavFIX.txt.... why did this come up?  If you define waypoints in a sidstar file you should not be defining them in the wpNavFIX.txt file.... why are we taking about fixes?  I'm lost.

Share this post


Link to post
Share on other sites
12 hours ago, RL18 said:

I used always TAB.

See the last post (and another one of the posts, too). As Dan mentioned:

"All white space must be space characters."

In order to get spaces/alignment, the only way to get that space is to hit the spacebar. Hitting the Tab key will create Tab-space, and not regular character space. It matters.

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