Recently I have been given some really weird instructions for getting on an ILS approach. The worst is at Kahului (Hawaii). Within 25 milies and SW of the airport, I'm sent onto a heading of 270 degrees (this happened twice). Im cleared for a SW to NE RW but never seem to be able to get vectored in. Another try, from due south I am vectored north and cleared to descend to the glideslope. This flew me into a mountain.At Fairbanks (Alaska) I am vectored to the NE of the airport even though I'm cleared for ILS approach to RW 01. App. control releases me to acquire the glideslope at this point which is at the wrong side of the field. Am I setting something up incorrectly? Vectors are frequently leading me away from a good approach setup.

Recently I have been given some really weird instructions for getting on an ILS approach. The worst is at Kahului (Hawaii). Within 25 milies and SW of the airport, I'm sent onto a heading of 270 degrees (this happened twice). Im cleared for a SW to NE RW but never seem to be able to get vectored in. Another try, from due south I am vectored north and cleared to descend to the glideslope. This flew me into a mountain.At Fairbanks (Alaska) I am vectored to the NE of the airport even though I'm cleared for ILS approach to RW 01. App. control releases me to acquire the glideslope at this point which is at the wrong side of the field. Am I setting something up incorrectly? Vectors are frequently leading me away from a good approach setup.

rc controllers are forbidden to drink on the job.i'd have to see a log, to explain what is happening. if you can duplicate it, make a log, and lets see what is going on. and it would be very useful to see a screenshot of the fs map of your flight path. with those two things, i can probably explain it.jd

sorry to hijack but jd, i've noticed that RC controllers can't vector me in properly to Geneva airport in Switzerland. I am using some payware scenery though, could I do the same and send it off to you?

I will try the Honolulu to Kaluhui again tomorrow. I forgot to mention that once I was told to fly 270 I flew on until I was 45 miles away before cancelling IFR.

I will try the Honolulu to Kaluhui again tomorrow. I forgot to mention that once I was told to fly 270 I flew on until I was 45 miles away before cancelling IFR.

sounds like you missed your crossing restriction

sorry to hijack but jd, i've noticed that RC controllers can't vector me in properly to Geneva airport in Switzerland. I am using some payware scenery though, could I do the same and send it off to you?

you may need to use arrival notams. i'll never clear you below the msa. what was the msa for the airport?

sorry to hijack but jd, i've noticed that RC controllers can't vector me in properly to Geneva airport in Switzerland. I am using some payware scenery though, could I do the same and send it off to you?

Luke,I have the same FSDreamTeam scenery and coincidentally I flew Manchester-Geneva a couple of weeks ago in real life. Geneva has high ground on 3 sides of the airport so you should be selecting NOTAMS. You will probably be vectored quite far out (20 miles +) and only down to 7000ft which is the Minimum Safe Altitude (MSA). That should ensure you don't fly into any mountains but isn't particularly realistic. RC knows there are mountains in the area but not the direction of them. v5 will have MSAs for the four quadrants surrounding an airport so you should get improved vectors.Make sure you have rebuilt your scenery database after adding any new scenery. What I've tended to do at airports with NOTAMS is to base my approach on STARS rather than RC vectors for a quicker approach and landing.

Hi jd/Ray,Thank you for the reply, it has restored my faith in good old ATC! Could I possibly ask what NOTAMs are? can I read up on them and how to use them in the manual?Thanks guys, I really do appreciate the support.

Hi jd/Ray,Thank you for the reply, it has restored my faith in good old ATC! Could I possibly ask what NOTAMs are? can I read up on them and how to use them in the manual?Thanks guys, I really do appreciate the support.

it's in the manualit's a way to tell rc, now to rag you about altitudes, when you are being descended into airports surround by mountainsjd

Recently I have been given some really weird instructions for getting on an ILS approach. The worst is at Kahului (Hawaii). Within 25 milies and SW of the airport, I'm sent onto a heading of 270 degrees (this happened twice). Im cleared for a SW to NE RW but never seem to be able to get vectored in. Another try, from due south I am vectored north and cleared to descend to the glideslope.

Here is what happened when I tried the flight from Honolulu to Kahului yesterday: On course from the west, passed over Lanai (STAR beginning), at 25 miles from destination told to fly 095 degrees which is correct. Contacted app. cont at 20 miles,then at 15 miles told to take heading 205 deg and desc to 8K. Held this heading until I was 31 miles away thennew heading of 120 deg. At 28 miles told to hold 015 deg until intercept glidepath for Rwy 24. Unfortunately, by this time I was already past the glideslope and had to turn NW to intercept.Finally landed, parked, chocked, rented a car, and headed to town to PARTEE! :)Neal HowardBtw: Kahului isn't much of a party town at 4AM

Here is what happened when I tried the flight from Honolulu to Kahului yesterday: On course from the west, passed over Lanai (STAR beginning), at 25 miles from destination told to fly 095 degrees which is correct. Contacted app. cont at 20 miles,then at 15 miles told to take heading 205 deg and desc to 8K. Held this heading until I was 31 miles away thennew heading of 120 deg. At 28 miles told to hold 015 deg until intercept glidepath for Rwy 24. Unfortunately, by this time I was already past the glideslope and had to turn NW to intercept.Finally landed, parked, chocked, rented a car, and headed to town to PARTEE! :)Neal HowardBtw: Kahului isn't much of a party town at 4AM

that is one of those cases where you have to watch the rc display, and when the bearing to the airport is the same as the runway heading, turn to the runway heading. unfortunately, at that distance, you won't recieve the localizer signal.once you are on the runway heading, and recieve the localizer, correct your heading left of right until you are centered. the glideslope should be below you.jd

Hopefully the GS is above in order to catch it. :)The current IFR data shows runways 20 and 23 to the west. 23 is a GPS/RNAV with no published ILS. I only have the default scenery and the RC data only shows a localizer with GS for runway 2 and a backcourse for runway 20.http://flightaware.com/resources/airport/O...S%29+RWY+23/pdfBecause of the mountains surrounding the average MSA RC probably had was too high so this is one case in which NOTAMS or better yet an IAP might have been more appropriate.You can get all the charts here single or bundled:http://flightaware.com/resources/airport/PHOG/proceduresThe airport data shows one STAR CAMPS TWO and that is aligned with runway 2.http://flightaware.com/resources/airport/O...R/CAMPS+TWO/pdfIf AI were using 24, a short runway, then RC assigned it to you, vectored you way out for the 205 nearside upwind due to the high MSA, and then your right base at 120 and your merge still too high for the GS intercept (my data shows no GS/ILS for 24 and that it is in fact 23) and too far out to receive it if your scenery has one. My FS9 default does not.RWY 20 R/W has a backcourse approach. In FS you would be receiving a false GS and you must not use the GS.http://flightaware.com/resources/airport/O...E+BC+RWY+20/pdfYou would manually control descent using DME in this case. Runway 23 has no localizer in either direction in FS and R/W. (There might be a runway renumbering somewhere as well. Check your scenery.)

that is one of those cases where you have to watch the rc display, and when the bearing to the airport is the same as the runway heading, turn to the runway heading. unfortunately, at that distance, you won't recieve the localizer signal.once you are on the runway heading, and recieve the localizer, correct your heading left of right until you are centered. the glideslope should be below you.jd

Hopefully the GS is above in order to catch it. :)The current IFR data shows runways 20 and 23 to the west. 23 is a GPS/RNAV with no published ILS. I only have the default scenery and the RC data only shows a localizer with GS for runway 2 and a backcourse for runway 20.http://flightaware.com/resources/airport/O...S%29+RWY+23/pdfBecause of the mountains surrounding the average MSA RC probably had was too high so this is one case in which NOTAMS or better yet an IAP might have been more appropriate.You can get all the charts here single or bundled:http://flightaware.com/resources/airport/PHOG/proceduresThe airport data shows one STAR CAMPS TWO and that is aligned with runway 2.http://flightaware.com/resources/airport/O...R/CAMPS+TWO/pdfIf AI were using 24, a short runway, then RC assigned it to you, vectored you way out for the 205 nearside upwind due to the high MSA, and then your right base at 120 and your merge still too high for the GS intercept (my data shows no GS/ILS for 24 and that it is in fact 23) and too far out to receive it if your scenery has one. My FS9 default does not.RWY 20 R/W has a backcourse approach. In FS you would be receiving a false GS and you must not use the GS.http://flightaware.com/resources/airport/O...E+BC+RWY+20/pdfYou would manually control descent using DME in this case. Runway 23 has no localizer in either direction in FS and R/W. (There might be a runway renumbering somewhere as well. Check your scenery.)

my bad. of course, i meant it would be above you :-)if the arrival airport has mountains around it, you may need to choose arrival notams. if it is a complicated approach, then you may need to ask for an IAP approach, and fly it per the plate, and not let rc vector you.jd

I made a MAJOR TYPO in my last post. Everything is correct until I said Rwy 24 :( I was cleared for Rwy 02 which has mag hdg of 024.Sorry for the goof (no, I wasn't drinking :( ).Anyhow, I still plan to try it again one of these days.Thanks for all the replies and especially the info sources.Neal Howard