I have been trying to do something similar to what is shown in the first 60 seconds of this video:

Two custom waypoints are added to help flying the visual approach, RW003 on the extended runway centerline, and RW004 at the start of a 3-mile base leg from RW004 to RW003. RW003 is created as an along-track waypoint 2 nm before the threshold of runway 06L (RW06L/-2). This works fine in the NGX. RW004 is created as a place/bearing waypoint from RW004 (RW003149/3). This does not work in the NGX. The problem seems to be that RW003 is not actually created as a true custom waypoint, it is simply stored as a shorthand notation for "RW06L/-2". So when I try to copy RW003 to the scratchpad, I get RW06L/-2 instead. (If I try to enter RW003 manually I get a NOT IN DATA BASE). Is there some way of accomplishing this in the NGX? I.e. to create the two waypoints that make up the left base leg, 2 nm away from the runway threshold?

Hi, thats a good question. I also tried to create such a waypoint. I would be very interested, how such waypoints could be created. Markus

Well... that was the sole purpose of this video (I think). To show that it's NOT correctly modelled in the NGX. Just hope for SP1. I also like the last part of the video, where he creates the points on the FIX page. Very cool. Oh, I digress, to come to your actual question, no, there's no way to do this in any elegant way as of yet. You could obviously use the usual methods of PBD, Lat/Lon (have fun) and so forth, but obviously the part to create a custom wpt on top of another custom one has somehow been missed.

I usually take a bearing and distance from the Airport (or a navaid on the airport). You do have to remember your maths class at school though. Trigonometry DOES have a use!

You do have to remember your maths class at school though. Trigonometry DOES have a use!

LOL

Hello Tom --- I have just gotten to this point with my NGX learning curve and had come upon the need to do what your video showed nicely.I am not sure if this provides the answer, as I have not put the time into it yet, BUT, I am in my Volume 2 of the FC Ops Manual in section 11.31.13 which addresses waypoints with section 11.31.19 gettting into manual pilot entered points (custom). I may be making a gross assumption that because it appears in the manual, that it works in the NGX. I have not tried it yet, but will soon. Let us know if you beat me to the punch in testing it. Good Luck! This is a great feature and it SHOULD WORK. A must for navigation flexibility. Cheers --- Bob

Well... that was the sole purpose of this video (I think). To show that it's NOT correctly modelled in the NGX. Just hope for SP1.

Maybe. I found it by chance and I thought it would be fun to try in the NGX. And certainly easier than doing the trigonometry during approach Obviously there are going to be limits to a simulation, and this is hardly core functionality.

Obviously there are going to be limits to a simulation, and this is hardly core functionality.

Sorry, but I tend to disagree. While I appreciate the fact that every single feature takes time to implement, the not core functionality argument applies to a thousand other things just as well. As the video proves though, there IS an obvious real world application for it. After all I hope it will be in a future SP.

Triggernometry: gently squeeze don't jerk it