RayForgot to mention I am using the default scenery.Roger

i will have a look at it.

Thanks Roger. I'll fly that tomorrow night with my trusty 737-700. I have FS Flight Keeper which keeps a track of my flown route. I'll upload it tomorrow so you can check out my flight.I'm sure the version of the airport isn't a major factor.Cheers,

Thanks John. I've only flown into KBOS once and that was with Concorde from Miami. My FS Flight Keeper log shows no problems intercepting the localiser at 210kts.Cheers,

Hi Roger,I've just fed this route into FSNav to get a feel for your flight. PVD is 43 miles from the BOS VOR and your confirmation that your first approach vector was shortly after passing PVD enroute to INNDY looks spot on.I've setup northerly winds for a 04L departure from KEWR and I would anticipate a 04R landing at KBOS. I'll fly higher but that won't be a factor as I'll be at 11,000ft shortly after passing PVD.More tomorrow.Cheers,

Thanks,I think it's 1800 feet in our database.Out of interest can you remember the altitude which you were told to maintain until you were established on the localiser?All the best,John

Just might mention that sometimes flying into Boston using the FS9 ATC, I used to bring some pretty weird vectoring also. I always attributed that to strange data in the BGL files. More than once, I have been vectored way past the extended localizer line, and had to make steep turn on my own in order to get on the localizer.

Hi Ron,Thanks, that may be a very pertinent point.The other reported problem (at KHOU further down the thread) is another rwy where the ils's have the same frequency at both ends.All the best,John

if i build the plan from that, i'll be using my data. i want your data.open the .pln in notepad, ctrl-a, ctrl-c, and reply to this post by hitting ctrl-vi'll fly tonight, while the brits sleep and the aussies wake upjd

Hi RonIt looks like you hit the nail on the head. I just flew the approach again and the first localizer signal I picked up was ILQN which is for 22L. Thats why the reversal. I took up a heading of 050 and with in another mile or so locked on to IBOS which is the LOC for 4R. Great Call.RegardsRoger

And my thanks as well Ron. I'd forgotten all about that issue :-(Now to figure out why Matthew was sent so far downwind!All the best,John

hi john,that is correct, it was 1800. i flew the plan at 9000 feet, dropped by atc to 5000, then to 2000 on the downwind leg, when receiving clearance for the ILS rwy 4 approach, i was told to turn and descend and maintain 1800. but at this stage i was over 40 miles out.if you require any further info please let me know and thanks for the help in advance. i do not see this a something major, the product worked super first time around, i just found the leg distance a bit odd.

Hi Matthew,Thanks for the info. That's a strange one, I find the downwind leg distance odd too ;-)Hopefully you won't see it again.All the best,John

Roger,As ths problem has been resolved I've cancelled my planned flight to Boston this evening. It's nice the solution was so simple :-)Cheers,

Hi RayYou can still fly to Boston. Its a nice place.:) I guess the next question would be to determine if there is a way to prevent such circumstances. In my original post I mentioned that a similar thing happend at KPDX. When I checked the plates, sure enough, rwy 28R and 10L shared the same frequency. Don't know how often this occurs in FS but if it IS common, perhaps a fix should be sought. Just vectoring to an intercept point further in (rather than 30 miles out) would seem to help alot.RegardsRoger