RWY N/A issues with PMDG 737

[Mike777 163]

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

[Mike777 163]

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

Mike

[RL18 0]

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 May 5, 2018 by RL18

[Mike777 163]

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

Mike

[RL18 0]

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 May 6, 2018 by RL18

[downscc 1,327]

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.

[RL18 0]

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''.

[downscc 1,327]

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.

[RL18 0]

I used always TAB.

[scandinavian13 5,192]

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.

[RL18 0]

9 hours ago, scandinavian13 said:

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.

I didn't know that there have to be no TAB-Spaces. I removed them all. Now I don't get some error messages.

Thank you!