hi guys,so im setting up a flight to mumbai, and i cant find a waypoint that is close to the runway heading of what runway i want to land at. is it possible to make a custom waypoint or 'fix'?cheers

If you chose an approach (ILS, LOC, VOR, NBD) from the list of runways, the IAF and FAF are lined up with the runway.

If you chose an approach (ILS, LOC, VOR, NBD) from the list of runways, the IAF and FAF are lined up with the runway.

i know, but there isnt enough for the aircraft to happily line up with the localizer. its happened to me before, there wasnt enough approach fixes, and i ended up landing on a runway to the right of that runway because it couldnt line up in time

If there is no STAR (that takes you to FAF) or transition then get ATC vectors or take manual control.But anyway to your question, Yes you can enter custom waypoints no problem, it would have been better to ask in the forum of the exact aircraft you are using as there is variations from plane to plane. I am assuming you are talking about the 744 (going by your sig) which I am not extremely familiar with so I can't give exact details. You should be able to create a waypoint by coordinates, VOR bearing and distance, distance from or past a flight plan waypoint or even make your own in the PMDG AIRAC files.For example you should be able enter something like "AD/230/15" (AD being VOR indentifier, 230 is the radial and 15 is NM) or similar into the scratch pad of the CDU and execute it, I don't remember the exact ways Boeing does its but someone else will be able to explain.Oh and you should read up on the FMC manual you should have got with the aircraft, it should have a section dedicated to custom waypoints.

If there is no STAR (that takes you to FAF) or transition then get ATC vectors or take manual control.But anyway to your question, Yes you can enter custom waypoints no problem, it would have been better to ask in the forum of the exact aircraft you are using as there is variations from plane to plane. I am assuming you are talking about the 744 (going by your sig) which I am not extremely familiar with so I can't give exact details. You should be able to create a waypoint by coordinates, VOR bearing and distance, distance from or past a flight plan waypoint or even make your own in the PMDG AIRAC files.For example you should be able enter something like "AD/230/15" (AD being VOR indentifier, 230 is the radial and 15 is NM) or similar into the scratch pad of the CDU and execute it, I don't remember the exact ways Boeing does its but someone else will be able to explain.Oh and you should read up on the FMC manual you should have got with the aircraft, it should have a section dedicated to custom waypoints.

thanks for your detailed reply. yes i was talking about the 744 (sorry bout not putting it in). do u have any more info on putting more waypoints in the AIRAC files?cheers

I am not familiar with Mumbai airport, but in some airports like Heahtrow(26R), Zurich(16), JFK and Midway, there are runway aligned VORs that can be used to create place/bearing/distance waypoints. I use them all the time in the FMS, to create race-track circuit EHSI paths for landing practice.Tony

I am not familiar with Mumbai airport, but in some airports like Heahtrow(26R), Zurich(16), JFK and Midway, there are runway aligned VORs that can be used to create place/bearing/distance waypoints. I use them all the time in the FMS, to create race-track circuit EHSI paths for landing practice.Tony

mumbai had them too, i had an autoland and full ILS approach, but i just needed one more waypoint out at sea, so i could align properly with the localizer

If you select just the runway (not an approach) on the ARR page for the airport there should be a "VFR APPR" field on the page - place for instance 10 or 12 into the RWY EXT field at LSK 3L and it'll make a waypoint right on the runway centerline at that distance from the threshold.

If you select just the runway (not an approach) on the ARR page for the airport there should be a "VFR APPR" field on the page - place for instance 10 or 12 into the RWY EXT field at LSK 3L and it'll make a waypoint right on the runway centerline at that distance from the threshold.

Wow, thanks, Ryan, for describing this dead easy runway extension waypoint placement system. I have sought such a simple expedient for ages, and never before knew of the options above. Printed.Tony

Still don't understand why you need a waypoint on the localizer. You shouldn't join the localizer via LNAV but via VOR/LOC. It seems you are trying to use LNAV in a precision approach which you shouldn't do. In many cases it will just parallel the localizer without ever joining it.

If you select just the runway (not an approach) on the ARR page for the airport there should be a "VFR APPR" field on the page - place for instance 10 or 12 into the RWY EXT field at LSK 3L and it'll make a waypoint right on the runway centerline at that distance from the threshold.

wow thanks, ill definatley try that out :(

Lachlan,Yeah, I guess I'm a bit unclear here too as to what you're actually trying to do now after rereading your posts. Are you trying to actually fly an instrument approach or are you doing a visual and just need a waypoint that's on the extended runway centerline? The way you used the word "localizer" almost makes me think you're referring to the extended centerline instead. The localizer is the radio signal that lines you up exactly with the runway laterally. (not all runways have them).If you're doing an instrument approach, you want to select it on the DEP/ARR page and LNAV should lead you right to it - just arm LOC mode prior to reaching the waypoints that constitute the approach.Eric - using LNAV mode to approach the localizer actually is a perfectly valid technique. In fact I've heard from several real pilots that this method results in a smoother capture a lot of times than the actual LOC mode itself. You use LNAV and watch the raw data from the LOC on the F/O's screen, then just press LOC once it's lined up and it'll capture. Then arm the full approach mode for GS capture.

Ryan - I used to do that. Actually the main STAR for Bucharest-Otopeni LROP is a closed STAR and brings you right on the localizer followed then with a RNP segment on the localizer. That segment wouldn't be exactly on the centerline of the LOC and if you would enable LOC after you were tracking the RNP track it would make a sharp S turn to establish. Now this was only my own experience, but just last week I found some documents from Boeing for the 737NG regarding the MCC procedures introduced in 2004 which said exactly that: enable LOC before reaching the localizer and do not use LNAV to track initially inbound because in this case it could just parallel the LLZ and never establish. So I would say, use the LNAV to begin the turn, as you said, softer turns, but within 10 degrees of the inbound course enable LOC, or you might miss the localizer completely if you enable it when on inbound course.

 

 

Lachlan,Yeah, I guess I'm a bit unclear here too as to what you're actually trying to do now after rereading your posts. Are you trying to actually fly an instrument approach or are you doing a visual and just need a waypoint that's on the extended runway centerline? The way you used the word "localizer" almost makes me think you're referring to the extended centerline instead. The localizer is the radio signal that lines you up exactly with the runway laterally. (not all runways have them).If you're doing an instrument approach, you want to select it on the DEP/ARR page and LNAV should lead you right to it - just arm LOC mode prior to reaching the waypoints that constitute the approach.Eric - using LNAV mode to approach the localizer actually is a perfectly valid technique. In fact I've heard from several real pilots that this method results in a smoother capture a lot of times than the actual LOC mode itself. You use LNAV and watch the raw data from the LOC on the F/O's screen, then just press LOC once it's lined up and it'll capture. Then arm the full approach mode for GS capture.

ok. this might sound even more confusing, but what im trying to do is put another waypoint on the runway heading before the approach fixes. i managed to do a lat/long custom fix, heres a screeny of what i mean:

You can do this too. Enter into the scratch pad "<IAF><RunwayHDG>/15" then put that into the "Legs" portion on top of the IAF.