Dear Sirs,

 

Hope all is well. I have a problem with the FMC and AP in the J41.

 

I have made a FPL through the FMC, where one of the Waypoints was user defined (not offset), I have entered manually

 

POS:

N 48 31.19

W 123 01.27

 

OverFly: YES

 

When flying to this Waypoint, the Autopilot misses it, it flies (EXACTLY) over N 48 31 W123 01, ignoring the decimals (or seconds).

 

Please note that when flying to an existing Database Waypoint this issue doesn't happen.

 

Can anyone help me?

 

Thanks

 

Federico Sucari

From the resolution of your screen shot it is hard to tell what lateral mode your plane is using. If you could post a picture in map mode it might help. Then we could see if your user defined waypoint is even showing up as an active leg.

I fly the TEST leg, reaching waypoint is ignoring the decimals.

 

The lat/lon (above in picture) are the same as thrown by FMC.

 

Federico Sucari

Screenshot of FMC exact moment crossing TEST waypoint

 

Federico Sucari

I found the problem.

 

The FMC doesn't compute the right Lat/Lon when inputed by the pilot.

 

What I did was I created a FPL with a user defined Waypoint. Then I saved it to a RTE file.

 

When I open the RTE file I find that the FMC rounds up the lat/lon to the minute (no seconds!!).

 

For example:

 

If you input the KFHR waypoint by hand through inputing its correct lat/lon, instead of N 48.5220 W 123.0244 (correct lat/lon for KFHR), you get N 48.5167 W 123.0167 (which is rounded to the minute!!).

 

Same when inputting KLAX, instead of right lat/lon the FMC throws N 33.9333 W 118.4000 (same, rounded to the minute)

 

I need PMDG help!

 

Thanks,

 

Federico Sucari

I am in contact with PMDG support team, as it seems to be a Bug in the FMC.

It has a few bugs tbh, certain things make it crash. I've learnt most of the bugbears but it took me 4 attempts to fly yesterday as everytime I looked at the VNAV page it crashed FSX, I think it was something to do with the SID because I looked at the Direct To page and the departure runway appeared twice, so I set it to a waypoint further in my flightplan and the issue stopped. Also it doesn't like having the Arrival page populated without the Approach page being done first, that makes it crash too.

Chris, I am working with the support Desk to fix this. They seem to be good, so may be it is a good idea for you to open a ticket as well?

 

I would like to see this fix.

I'll make a note of the details next time it happens and file a ticket, can't hurt I suppose. I think it was a SID out of Cardiff, the BCN1A (this post is basically a reminder to myself now lol)