HUD velocity vector not aligned with actual flightpath.

[MR.TX]

On a recent flight I thought it would be a nice idea to give the HUD a try and noticed a rather big issue with it.

I was on an ILS approach into Doha in the A359 and wanted to land the aircraft by hand. Even before attempting to handfly the approach I noticed that although my aircraft was perfectly on the glide slope of the ILS, the velocity vector shown in the HUD was nowhere close to the touch down zone, but rather far above it. I then disconnected the autopilot and aimed the velocity vector right at the TDZ to see what would happen. To no big surprise I noticed that if I would continue to follow the velocity vector, my aicraft would probably crash a mile ahead of the runway into the ground. 

Hopefully this issue can be adressed in the future. 

[foliainfx]

8 hours ago, MR.TX said:

On a recent flight I thought it would be a nice idea to give the HUD a try and noticed a rather big issue with it.

I was on an ILS approach into Doha in the A359 and wanted to land the aircraft by hand. Even before attempting to handfly the approach I noticed that although my aircraft was perfectly on the glide slope of the ILS, the velocity vector shown in the HUD was nowhere close to the touch down zone, but rather far above it. I then disconnected the autopilot and aimed the velocity vector right at the TDZ to see what would happen. To no big surprise I noticed that if I would continue to follow the velocity vector, my aicraft would probably crash a mile ahead of the runway into the ground. 

Hopefully this issue can be adressed in the future. 

The HUD currently is useless for landings, wait till it gets fixed.