"Ron Rosenfeld" wrote in message =
...
=20
=20
Well, in trying to reproduce that bug, I came across what might be =
another
one in the simulator. The MAP called for a climb and then a turn to a
waypoint. The waypoint which ended the "climb" segment, remained a =
fixed
distance from the aircraft. Hence, we never reached it to be able to =
turn
to the Missed approach holding fix. It didn't seem to matter if the =
unit
was in SUSP or not.
=20
This is version 1.2 of the simulator.
=20
Perhaps you can confirm this, and report it also to your contact.
=20
I'm glad it's not a problem in the real unit, although I have not =
flown a
missed approach with enough knowledge to be sure what was going on. =
Soon,
hopefully.
=20
Thanks.
=20
=20
Ron (EPM) (N5843Q, Mooney M20E) (CP, ASEL, ASES, IA)

No, that's exactly the same bug I meant, Ron.
The shape of the missed approach seems immaterial,
and the Windows simulator seems to continually refresh the distance
and time fields with their original values from the MAP.

According to design, either Un-Suspending *OR* forcing a Direct-To
should make the missed approach function correctly,
but the Windows simulator didn't quite get the SUSP part right.

I'll get back later with something about the bearing to a particular =
point.
I think that's possible, but I'll need to check it first, and I'm going =
out right now.
---JRC--