Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Adding waypoints to the FMC database

Featured Replies

Hi,

I wanted to create and RNAV approach for LLET airport, that located in Eilat, southern Israel.

I need to create a few new waypoints for the RNAV approach.

The first of them caller RODED, located on the following cordinates: ojbs2cdrqejzeq03dww7.png

How do I add this waypoint to the "wpnavfix.txt" file?

Liam K

I believe you just open the wpnavfix.txt file using Notebook and insert the data following the format which you can see. The waypoints are listed in order of latitude, starting from 90 S (-ve) to 90 N (+ve). Latitude and longitude are +ve or -ve like co-ordinates on a graph. North is +ve, east is +ve, south is -ve and west is -ve.

 

Your latitude would be 29.574722 and, in my old wpnavfix.txt file, RODED would be detween ZIGDA 29.573950 and SWANO 29.574856. Your longitude would be 34.942222.

 

So, your entry would be RODED RODED 29.574722 34.942222 being aligned with the existing columns.

 

I believe that's all you need to do.

 

To be safe, you might want to make a copy of the wpnavfix.txt file before you make any changes.

Dugald Walker

  • Author

Thank you dmwalker!

How did you translate the cordinates?

I mean, how did you got to 29.574722 ?

Is there a way to calculate it?

Liam K

Sorry, I meant Notepad, not Notebook.

 

You have 29 degrees, 34 minutes, 29 seconds.

 

Start with the seconds.

 

There are 60 seconds in a minute so 29 seconds = 29/60 = 0.483333 minute.

 

Add this to your 34 minutes = 34.483333 minutes.

 

There are 60 minutes in a degree so 34.483333 minutes = 34.483333/60 degree = 0.574722 degree.

 

Add this to your 29 degrees = 29.574722 degrees.

Dugald Walker

Or you could use this online resource. :smile:

 

If you also want to use the waypoints you create for an approach procedure at LLET that would be available in the FMC, you enter the fixes into PMDG\SIDSTARS\LLET.txt, and then write the approach commands there as well. Note that the format for fixes in the SIDSTARS files is a bit different than those in the wpnavfix.txt file. The above calculator delivers results in both of these formats.

- Jev McKee, AVSIM member since 2006.
Specs: i7-2600K oc to 4.7GHz, 8GB, GTX580-1.5GB, 512GB SSD, Saitek Pro Flight Yoke System, FSX-Acceleration 

 

  • Author

Thank you both! :)

Do you know how can I create an approach?

I understood that this belongs to the airport's file in SIDSTAR folder.

Liam K

Do you know how can I create an approach?

 

Liam,

 

It's easiest if you're adding a procedure to a SIDSTARS file from an existing chart because the procedure commands are right there in black and white. I've begun to learn how to do this simply by sitting with a few charts and looking at their corresponding approach procedures in the SIDSTARS files with a focus on learning the syntax used. It's really not that difficult to absorb the syntax rules and then write your own procedure, especially if it's already charted. Most of the commands are similar to this:

 

APPROACH RNAV02R FIX AFSNB 4800 FIX RJ088 3200 FIX RJ089 2130 FIX OVERFLY RJ091 1680 FIX OVERFLY RJ092 1270 TURN LEFT DIRECT FIX OVERFLY RJ093 490 RNW 02R FIX RJ094 FIX RJ096 FIX MIA 3000 SPEED 210 HOLD AT FIX MIA RIGHT TURN INBOUNDCOURSE 325 ALT 3000 LEGTIME 1
TRANSITION SCR FIX SCR FIX PASO 8000
TRANSITION LIME FIX LIME FIX TERE 6000

 

For example, have a look at this thread. You could start reading it from here.

- Jev McKee, AVSIM member since 2006.
Specs: i7-2600K oc to 4.7GHz, 8GB, GTX580-1.5GB, 512GB SSD, Saitek Pro Flight Yoke System, FSX-Acceleration 

 

  • Author

Thank you again coa1117 :smile:

I have a problam, In the FMC, in the DEP/ARR page, when I select the airport the approach is not showing.

This is what I wrote in LLET.txt in SIDSTAR folder:

APPROACHES
APPROACH RNAV03 FIX KITOR 5000 FIX LOT 4000 RODED 2500 FIX SHAKI 2400 FIX HILIT 1800 FIX GODAR 1100 FIX YAMAD RNW 03 TRK 028
ENDAPPROACHES

Is there something wrong with it?

Liam K

Try adding FIX before RODED. See if that works.

 

Another thing you might want to try is to make RODED the first fix on the approach, and move KITOR and LOT to a transition, such as:

 

APPROACHES
APPROACH RNAV03 FIX RODED 2500 FIX SHAKI 2400 FIX OVERFLY HILIT 1800 SPEED 150 TURN LEFT DIRECT FIX OVERFLY GODAR 1100 FIX YAMAD RNW 03 TRK 028
TRANSITION KITOR FIX KITOR 5000 FIX LOT 4000
ENDAPPROACHES

 

Also, it's a very tight turn from HILIT to GODAR, so I added an OVERFLY at HILIT, and also a speed restriction there per the chart. Also some additional instructions for GODAR. See how that works.

- Jev McKee, AVSIM member since 2006.
Specs: i7-2600K oc to 4.7GHz, 8GB, GTX580-1.5GB, 512GB SSD, Saitek Pro Flight Yoke System, FSX-Acceleration 

 

  • Author

Thank you again!

There is still something wrong.

This is what is desplayed in the ARR page:

 

yuwxxony2emreu8j9qey.png

Maybe that's because I didn't place the new fixs in there correct position on the list "wpnavfix"?

BTW, is there a way to put the new fixs in all the FMC's, not only the PMDG's?

Liam K

Liam, attach your LLET.txt file to your reply and let me take a look at it. Meanwhile I'll do some testing of my own edits.

- Jev McKee, AVSIM member since 2006.
Specs: i7-2600K oc to 4.7GHz, 8GB, GTX580-1.5GB, 512GB SSD, Saitek Pro Flight Yoke System, FSX-Acceleration 

 

Liam ...

 

I got it working. There were a couple of potential issues, and I'm not sure which one(s) caused the problem of the approach not being available in the FMC.

 

These are my fixes in LLET.txt:

 

FIXES
FIX GODAR LATLON N 29 30.35 E 34 55.86666
FIX HILIT LATLON N 29 28.48333 E 34 54.16666
FIX KITOR LATLON N 29 43.38333 E 34 59.9
FIX LOT LATLON N 29 36.485 E 34 58.56833
FIX RODED LATLON N 29 34.48333 E 34 56.83333
FIX RW03 LATLON N 29 33.29082 E 34 57.39516
FIX SAMAR LATLON N 29 49.33332 E 35 1.06668
FIX SHAKI LATLON N 29 31.66666 E 34 54.38333
FIX YAMAD LATLON N 29 31.43333 E 34 56.38333
ENDFIXES

 

To avoid duplicate entries in wpnavfix.txt I searched on each fix to see if it was already in that database. There are lots of fixes with duplicate names in the database so you have to be careful to check the LAT/LON to verify that the fix is in fact located near LLET. While doing this I failed to check the location of fix GODAR. In fact there's another fix with this name located at longitude -095, and it's roughly 6200nm from LLET. So, I added the GODAR fix near LLET, and it now appears properly in the FMC.

 

I also made some changes in the Approach commands. I'm not sure if ending your command line with TRK 024 was the issue or not, but I changed the missed approach procedure to direct SAMAR (about 15nm) and then a left turn back to LOT and HOLD. I also set the speed at KITOR to 190 and the altitude at LOT to 3500 to better enable the VNAV to handle the approach. Remember this is not going to set you up aligned with the runway which is offset .

 

APPROACHES
APPROACH RNAV03 FIX RODED 2500 FIX SHAKI 2400 FIX OVERFLY HILIT 1800 TURN LEFT DIRECT FIX OVERFLY GODAR 1100 FIX YAMAD RNW 03 FIX SAMAR TURN LEFT DIRECT FIX LOT 6000 HOLD AT FIX LOT RIGHT TURN INBOUNDCOURSE 186 ALT 6000 LEGTIME 1
TRANSITION KITOR FIX KITOR 5000 SPEED 190 FIX LOT 3500
ENDAPPROACHES

 

If this doesn't work for you, double check your fixes in LLET.txt and your fix entries in wpnavfix.txt.

 

 

- Jev McKee, AVSIM member since 2006.
Specs: i7-2600K oc to 4.7GHz, 8GB, GTX580-1.5GB, 512GB SSD, Saitek Pro Flight Yoke System, FSX-Acceleration 

 

  • Author

Thank you so much coa1117! It works!

 

COME TO ISRAEL :israel-flag:

Liam K

Yeah, I flew it a couple of times last nite. A very nice approach especially with the sharp turn to final over the Red Sea. Lots of fun to fly manually. Enjoy!

- Jev McKee, AVSIM member since 2006.
Specs: i7-2600K oc to 4.7GHz, 8GB, GTX580-1.5GB, 512GB SSD, Saitek Pro Flight Yoke System, FSX-Acceleration 

 

A nice way to end this thread ...

 

 

 

Eilat scenery, Israel landclass and more available here.

- Jev McKee, AVSIM member since 2006.
Specs: i7-2600K oc to 4.7GHz, 8GB, GTX580-1.5GB, 512GB SSD, Saitek Pro Flight Yoke System, FSX-Acceleration 

 

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.