Tim.

I respectfully disagree with your point of view as what I am experiencing here has nothing to do with bad FSX install.

Yesterday I have made another flight - and I'll do so many as needed to see if and where maybe I'm doing some mistake.

As you probably know, Boeing CDU logical are very similar - for a 73x , 76x or for a 74x. If you learn to use one, you certainly know how to use the others.

My flight: UHMA to PANC - FL310.
BUMUL G212 YUREE H201 OME J111 MIGAN

SID: BUMUL - STAR: TAGER5.MIGAN

I have created my flightplan and imported it to FSX flightplanner. When programming CDU, I imported the flightplan. MIGAN and PANC disappeared. So I inserted them manually.

Bug1: When importing a flightplan, destination airport and last waypoint disappear on LEGS page.

I usually fly on IVAO. Sometimes VATSIM. As you probably know, as you contact ATC at your destination you have information on what runway to land, due to METAR at that moment.

So, inserting arrival information at departing airport is just a guess. Even if you have the METAR at your arrival airport, and let's say, winds are 060º, which runway at PANC - 06L or 06R?

So the final information is inserted on CDU during your approach.

Bug2: If you insert this information during flight, you have a discontinuity, which is expected and very normal to happen. When you copy the next waypoint to scratchpad and then to discontinuity boxes, all your approach disappears, you miss your T/D and FL is set to 310 to the remaining waypoints.

For this flight I pre-set all information on CDU. Selected RWY06L to land at PANC and inserted a few waypoints to make a smooth wind leg and base leg. So I added FROZN, SUPOY and WEWWO waypoints.

I also checked airport charts and adjusted altitude at CI07L to be sure that I'll be at 1600' and catch the glide.

I have also made some adjustments on speed, to make a smooth turn and avoid overshooting the waypoints at the final.

If you don't use VNAV for your descent, I suggest you to try it. That maybe the difference. It also seems you are still learning all the benefits of CDU. That's great. I hope you can fully experience it.

Departure and cruise were fine. At departure, the aircraft followed SID route quite well.

Before descent, I set altitude to 1600' on MCP. At T/D aircraft began it descent as expected. Speedbug at 300 knots. Throttle on idle. N1 displaying about 30% confirming idle.

At 10000' speedbug automatically decreased to 250 knots. CDU displayed 'drag required' message. Speedbrakes at full. The aircraft did not reduced speed until leveled.

Bug3: Speedbrakes seem to be uneffective.

Although VNAV was still activated, the aircraft descended to 1600' not reacting to CDU altitude restrictions at the waypoints.

Bug4: VNAV seems to be uneffective at descent.

At TAGER I set 170 knots on CDU and all the other waypoints assumed correctly this speed. When over HEYEB speedbug increased to 300 knots and also aircraft speed. One or two miles after the waypoint, the speedbug decreased to 170 knots. This also happened when over ANC.

Bug5: Speedbug/throttle strange behaviour

The aircraft followed the route correctly. LNAV works perfect.

Localizer and ILS were correctly captured.

Landing perfect, autobrakes and speedbrakes worked fine.

I apologize for such this long post but I think it is needed, and again with due respect to your opinion, I disagree this aircraft works fine.

I'll wait for some news from dev's and I really hope they can fix the problems many of us are reporting on this forum.

Regards

Schmid.

(oh, please, 'Mr.' is not needed and sounds a little bit of sarcasm.  ;))