ILS plane not flying flight plan

[Hugothester]

@PZL104

As IRL, the button isn’t important.
It’s only the FMA which is essential.

Nope, you can have an issue where the button is turning off but the flight plan showing it as on for example, we need more information to help you.
And according to your title of the thread you are trying to fly an ILS? At FL400? Did you activate the Approach button by any chance?

[willisxdc]

You are confusing me…

Does the AP1 not indicate that the AP is in fact turned on?

This image says to me that …

• Autopilot 1 is engaged.
• Flight Directors 1 and 2 are on
• Autothrottle is engaged

The AP Modes are…

• Speed Selected
• At selected altitude
• NAV mode active.

Question for me is, what NAV source?

[SierraHotel2873]

Stock A320 is only capable of using GPS (not VOR) as nav source afik

[willisxdc]

Well, there you go. Being an old Boeing guy, I probably only have 20 hours on the MSFS A320.

If that IS the case then the issue is weirder (if that’s a word) than I thought.

[FlippinFlow]

What build of FBW are you using? Aren’t they rewriting the whole AP from scratch? I’ve seen some wonky things in the dev build.

[N6722C]

@Sath68

GPS tracking is broken. Sometimes it works, sometimes it doesn’t. Planes can be off for as much as 7 miles from the magenta line.

If you put the FP into LNM, and view your plane also on LNM, it follows the FP.
Its in MSFS, that the magenta line gets curved around Waypoints, and then plane does not follow the MSFS magenta curves.

[PmpMstaSteve]

@willisxdc

and set to the correct waypoint as listed in the FMC. Looking at the wind, I would expect the heading to be pointing right of the desired track but it is heading away from the track, (to the left).

You see that’s my point actually, we aren’t able to see enough detail to see what that waypoint is and if he is in fact heading to the correct waypoint, we can see that the next waypoint is to 112 is 35nm out and he is tracking just right (as you noted he should be with the wind). So AP is engaged and AP is following NAV but the waypoint is not marked as a line, that happens with some of those weird infinite line waypoints. You couldn’t really tell without zooming out or knowing what all those wp’s mean.

[PmpMstaSteve]

And according to your title of the thread you are trying to fly an ILS? At FL400?

He’s not the OP and I already addressed the OPs title is wrong (he obviously confused ILS with IFR) and that is what confused people off the bat.

[Ephedrin87]

That‘s an A320 apparently flying from LAX to LHR at N6235 which should be somewhere south of Island with a 115 HDG but with 4000 something NM to go at 39000 ft at M.84 with 10t of fuel with the altimeter not set to STD (not sure if even possible though in this version)… yes there is something very wrong.

[PZL104]

@SierraHotel2873

Stock A320 is only capable of using GPS (not VOR) as nav source afik

Not sure what you mean. In MSFS the nav source wouldn’t make any difference in determining your posiition.
If you mean nav mode, the real A320 can’t track VORs either.

[PZL104]

@Hugothester

@PZL104

As IRL, the button isn’t important.
It’s only the FMA which is essential.

Nope, you can have an issue where the button is turning off but the flight plan showing it as on

Don’t understand. There’s no AP state info anywhere on the flight plan.

[PZL104]

The real A320 can’t track VORs either. Weird, especially for us oldtimers.

[willisxdc]

So can the Nav source be incorrectly set or switched thus wandering off course with no data?

[PZL104]

The real one uses all sources, GPS, IRS, VOR, DME, but you can’t track a VOR in the ‘classic’ way by pushing the NAV button.

[PZL104]

@willisxdc

So can the Nav source be incorrectly set or switched thus wandering off course with no data?

No, that’s not possible. You can’t switch the nav sources, except during an ILS approach.

That said, I would stay away from the A320, it’s not worth learning everything new and I’ve never met any Boeing pilot who preferred an Airbus over a Boeing.

[Ephedrin87]

Afaik the NEO doesn‘t use INS but… internet disclaimer: „I might be wrong“.

However the FPLN page shows coming from N6240 to N6235 at a (ND) 115HDG. If I remember correctly the airbus‘s terminology translated N6235 to N62‘00.0 W035‘00.0 and London is at around 0Meridian. 35*60NM is something around 2100 so at a heading of 115 there is no way to explain why the FPLN says 4800NM to go. I‘d check my route.

(Abd ask myself why I bring an A320 from LA to London )

Edit: I swear I read „INS“ somewhere… can‘t find it anymore head scratch

[PZL104]

@Ephedrin87

Afaik the NEO doesn‘t use INS but…

What does it use to determine its position? Just to make sure, that’s the same as IRS in MSFS speech.

[Ephedrin87]

Not sure by all means… I thought I read the Neo only used GPS…

[PZL104]

Just checked and the IRSs are used.

Quote from the FCOM.
two GPS receivers, which are connected to the IR part of the ADIRU’s for GP/IR hybrid position calculation.

[Ephedrin87]

IRS is not INS… INS is that vintage monster where you type in your fixes as coordinates and that gives you track error and GS etc… IRS is the reference system with these 3 fast spinning gyros with that horrible sound setting a Boeing pilot learns to ignore like a tinitus runs

No I think the problem of the OP is a faulty route. I‘ve seen issues for example with the Aerosoft A330 incorrectly interpreting the route that was loaded from Simbrief due to this weird Airbus terminology. N6230 can be W030 or E030, if you only get the abbreviation it might draw a line to russia and back.