VOR Approach and FMS to land

In a VOR Approach, I fly GPS until I am near the FAF, then I change FMS to VOR (with the frecuency of the VOR on NAV), but the aircraft deviates to the right of the course, so I returned to FMS to land.

Could you give some more info? What airport, plane etc.? What approach have you programmed in the FMS, RNAV or VOR since they could differ (different FAF as well in that case). Have you set the correct final approach course (magnetic)?

What do you mean with the aircraft deviating to the right of course? Is the Course Deviation Indicator (CDI) also to the right of center? Depending on the aircraft you might need to re-engage the NAV mode after switching NAV source.

If you did everything correctly on your end, it might be that the VOR is not at the correct place in FS2020. But as you can see there are many reasons, if you can give more concise information we might be able to help you.

1 Like

Flight Munich-Dusserldorf, Direct VOR (GPS), TBM 930
Approach: VORDME 23L
Arrival: ABIG1A
At USR, I change in Active Nav, FMS to VOR 1 (with frecuency change in NAV1 to the frecuency of VOR EDDL

As I can see, the ABIGI 1A arrival is for runway 05L? The VOR is located in between the two runways with VOR runway 23L being 1 degree offset and runway 23R being 2 degrees offset. I don’t know which FAF you navigated to the FAF for runway 23L is D10.1 on approach course 233. If you’ve navigated to this point by GPS you should be on centerline. If you instead navigate to METMA which is the FAF for the RNAV approach for runway 23L you are indeed offset from the VOR course (but correctly aligned with the runway).

@cromsan, Was the course knob set to 233°? I would actually fly this approach entirely in GPS / FMS mode, and never change the #1 CDI over to green needles (VOR). Much more precise that way. (To be legal you technically have to display the VOR somewhere, so could have a simple bearing pointer displayed, or over on the right side #2 instruments - at least with FAA regs. Not certain about EASA)

1 Like

Sorry, my Arrival was BIKM1G, not ABIG1A.
And at USR (map VFR msfs), I do what I say: change in Active Nav, FMS to VOR 1 and as I see I go to the right, turn again to FMS to land.
I have not use D10.1 (IAF in Navigraph), I use USR (that don´t appear in Navigraph, only in map VFR msfs), very near to final course of 233º.

I’m not familiar with point USR, looking at the identifier it must be either a VOR or NDB. I have been flying in and out of Dusseldorf in real life but I don’t recall this point. That could explain the behavior, is this point even on the extended centerline? If you would use METMA (FAP for runway 23L) you should need a left turn for the VOR approach inbound radial of 233. As said before the approach should be slightly offset since the DUS VOR is located in between the two runways so don’t expect to end up on the extended centerline while flying the VOR approach. Could also be something wrong in FS2020 of course.

Edit: I just gave it a try and it seems to work well, approaching slightly offset as it should. I couldn’t find the point you were mentioning and I noticed the NAV mode on the G1000 reacts very aggressively to even the slightest CDI displacement when engaged, I intially thought it was going to turn 180 degrees around but it eventually settled.

1 Like

Same for EASA, legally you need to crosscheck with the VOR / ADF overlay.

I think USR just means a user waypoint, I tend to see these when the approach is added to the FMS. I think it may just be a way to get the AP to follow a curved path onto final.

1 Like

Good one, that might be