[Entering and leaving OFFSET paths]

Well, returning to the path after an offset to the right over the Atlantic ... all went well going east to west but went in an anticlockwise circle when finishing the offset going west to east.

I wonder if the problem only happens when the flight path has a right turn at the waypoint where the offset to the right terminates?

[NAV problem with a small jink in the simbrief produced flightplan]

MSFS2020 A359

Simbrief gave me the following routing from EDDM to RJTT

KIRDI DCT MEDEL DCT STEIN DCT TEGRI DCT DINRO DCT UDROS UM859 KARDE UN644 ROLIN N644 TETRO DCT BARAD M747 SUBUT T923 ERLEV M11 RODAR A909 TUNEK B143 KRS A480 OTBOR N147 GENGA N143 RUDIZ N161 SARIN A368 FKG W188 GOVSA W66 DKO W69 HUR B339 LADIX W34 VAPGU W100 ORAVA W201 UNSEK A326 DONVO G597 AGAVO Y644 EGOBA Y697 LANAT Y71 XAC

There's that little jink between ORAVA and UNSEK over China that the plane wasn't able to follow. It remained in NAV mode but the curved path it set itself meant it ended up going north at ALARA and then circled until I took over and gave it a direct to a subsequent waypoint.

[FMS estimated timings!]

This time it was Singapore to Munich, MSFS 2020, A359

AROSO5B AROSO Y513 KALIL Y504 GUNIP N571 MEKAR/N0500F360 N571 SUGID/N0501F380 N571 MENSA DCT MITIX M557 TUMAK L602 ORSOL/N0489F400 L602 TASMI UL602 GADSI UM860 ODALI UL852 NEGEM L852 KOMAN DCT INVED DCT SUNIS DCT ABRUK DCT VATET DCT REDBU Q112 NAPSA

FMS initially showed sensible timings but in the second half of the journey I noticed that the predicted arrival time had changed from around 04:00 to 07:28. 

T/D no longer shows on list on FMS.

PS On the ground and parked up, clicking on the file in OIS Autosaves caused the screen to go black followed by the message "You overstressed the aircraft ... " and sent me to MSFS Main Menu !!! 

1746392071.bin

[FMS estimated timings!]

Sorry, didn't see this in time to get flight details from Simbrief.

Was in MSFS2020 A359 and this was a flight from KSFO to EDDM.

[FMS estimated timings!]

1.0.8, MSFS2020

How do I explain to the passengers that the computer suggests that the last 160 or so miles of the flight is going to take around 4 hours or more ?!?

[Another Step Climb silliness]

Update: this was the start of major problems with the plane leading to abandonment of the flight. With engines showing near 100% thrust, the plane was unable to maintain speed resulting in an alpha floor situation. I couldn't see a way to reset the situation.

[Another Step Climb silliness]

MSFS2020

ver 1.0.7

Instead of waiting for the programmed waypoint for the step climb to FL400, the FMS has decided that a gradual change is necessary over the next few hours ... which it thinks will only take just a couple of minutes!

Can we get step climb and offset joining/leaving properly coded for this long haul airliner. please?

[Autopilot disconect master alarm]

This used to happen to me ... but since 1.0.7 came out pressing the master caution button DOES silence the alarm.

[Top of Descent time in FMS]

Just switched away to another page on FMS 2 then back to F PLN. That gave a more sensible updated T/D time but it was still out of sequence with the previous and next waypoints.

[Top of Descent time in FMS]

MSFS 2020, version 1.0.7

Top of descent time obviously showing incorrectly in FMS Flight Plan, not agreeing with what's shown on PERF page and not fitting in with waypoint times before and after. In this case, the time shown is one minute after predicted landing!

[Entering and leaving OFFSET paths]

MSFS2020 1.0.7

When entering and leaving an offset segment, the plane can head off in all sorts of directions rather than altering course by the set amount (30 deg default) to the new path.

[Step climb still "strange"]

MSFS2020 1.0.7

The step climbs entered into the FMS aren't properly inserted into the flight plan. In the example shown in the pics, the step climb from F390 to F400 at JOOPY then strangely shows FL389 next to S/C then FL390 at the next waypoint (miles away) before FL400 at the following waypoint.

[Autopilot disconect master alarm]

Yes, same problem ... annoying to have to look down at the Clear button on the pedestal. If it works for me, the jumping outside would be a simpler workaround!

[Passenger numbers]

The total number of passengers agrees with what was expected from Simbrief. However, the cabin crew always find that the number of passengers in the four compartments doesn't agree with that number, usually with 3 extra stowaways! (16+20+91+91 = 218)

Hopefully an easy fix?

[Step climb deletion]

A350 MSFS2020. For today's flight I inserted two step climbs. Upon reaching the first I decided the plane was not ready to climb. Message "Step climb deleted" subsequently seen. But it was the second step climb that was deleted from the list, not the first at the waypoint already passed. Surely incorrect behaviour?

[Swapping active and secondary flight plans]

(MSFS 2020) Update suggested that this was fixed, but swapping active and SEC1 then swapping back led to original full flight plan being lost ... start again!

[Selecting offset and ending offset]

Programming the end waypoint for an offset segment of a flight is usually "interesting" in the FMS, with different waypoint then displayed in the box to the one either selected or "typed" in.

At the end of an offset to the right (by 2 miles for example), the plane turns left to get back on track but then continues left in a full circle!

Has happened multiple times!

[Top of descent calculation]

... has usually been fine but the attached screenshot shows nonsensical time for T/D on today's flight with T/D at 20:54, long after expected landing at 20:36 !