This has happened to me a few times and I am not sure how to go about avoiding it. I was doing a full auto land into KBOS today and came down on the GS fine, but the plane lands a few feet to the side of the runway, instead of on the runway itself. This does not happen with every flight, but occurs on occasion. Is it caused by wind? Am I not entering an essential setting into FMC? I use opus for weather and have the default kbos airport. I enter the ils data into my radios in advance and pull the course heading off of EFB. 

Does your FMA confirm LOC and G/S captured?

 

The ND map shows o.k.? Nothing unusual there?

 

If in doubt run a registry repair tool (freeware, available from either Flight1 or ORBX).

Either

 

1.) Magnetic deviation caused by a slight changed in the localizer course between the time the AFCAD was created with FSX and now with the current navdata.

 

2.) An offset localizer. In this case it's supposed to be like that.

 

3.) The AFCAD isn't necessarily right in FSX. (which wouldn't be shocking).

 

I know for a fact there's a fix you can download for #1. I'm pretty sure you can fix #3, although I've never done this myself.

 

If it's #2, then it's purposely done and an autoland was never supposed to happen on this runway. Which is entirely possible. Not all runways/airports are equipped for it. Which then drifts into what Kyle commonly refers to as a "sim-ism". But that's his territory. So if he takes a break during T7 testing/cruise to browse the forums he can explain it much better than me. I'm at work and far too tired to really get into how to fix any of the above issues. But a quick Google search should find the proper fixes.

 

I'm incredibly tired and most likely prone to rambling at this point so if the above seems "ramblish", I apologize.

So if he takes a break during T7 testing/cruise to browse the forums he can explain it much better than me.

 

 

In fact he's done that already a few weeks (months?) back, when someone asked the exact same question regarding the ILS 15R approach into KBOS. So in order to avoid a repeat performance, we'll award this thread's winner's trophy right now for your suggestion #2, which turns out to be the right answer:

 

 

Bah. I was hoping to make KJFK KBOS a regular run. I didn't even know about offset localizers. Still trying to learn flight sim and its amazing how much material there is to cover. 

 

 

So in order to avoid a repeat performance, we'll award this thread's winner's trophy right now for your suggestion #2, which turns out to be the right answer:

 

Woo! Trophy. Ha. Being at work, I wasn't able to look up the charts but I figured that was a front-runner.

Bah. I was hoping to make KJFK KBOS a regular run. I didn't even know about offset localizers. Still trying to learn flight sim and its amazing how much material there is to cover. 

 

 

Just turn off crash detection make a go of it. Take manual control and if you slam it into the grass, no one will ever know. You learn something new every approach and each one gets a little better. One day, everything clicks and offset localizers won't even get a 2nd glance.

 

Ok, maybe a 2nd just to see HOW offset it is.

 

 

Bah. I was hoping to make KJFK KBOS a regular run.

 

Well, you do realize that you can land this thing manually, right? Even if you've got no experience hand-flying a tubeliner, the inclusion of the HGS in the NGX makes the process especially painless -- or at least not as excruciating as it otherwise could be. All you have to do is aim the green thingy for the point in space on the grey thingy right between the white thingies, while maintaining your approach speed, and you're pretty much assured of at least making it to the runway threshold, and being just a flare away from a half-decent landing!