OOOI Time Recording Error

[MD82]

I have added my "TIMES" page together with my flight's actual off blocks and airborne times.

- Off blocks time should start recording when the brakes are released with all doors closed. Not after the first engine is started.

- Airborne time correctly starts counting when the main wheel ground sensors release. However,

- For both of these you will get an error as the flight progresses.

I was pushed back at 2200. For the sake of keeping the time stamps correct I started my 1st engine at 2204 (see 1st item above). This means, that at 0929 UTC (as per picture),

- My Block Time should be 11:25 and my Flight Time should be 11:09.

- As per the picture however, my Block Time is 11:12 and my Flight Time is 10:55. Meaning, I have lost 13-14 minutes along the way.

When I look at my OFP times, I see that over TEFFO I had an error of less than 2 minutes. So, I know that there was no SIM freeze somewhere for 13-14 minutes and that it is most probably the counter that is slow. OIS Settings: Time Compression - OFF, Max Compression 2x, MSFS 2024

- To summarize: 1. Off block time starts counting at 1st engine start instead of the first instance of brake release with all doors closed and 2., the Flight Time and Block Time counters seem to run slow.

Edited March 5 by MD82

[MD82]

In the end:

Actual Times: 2200 - 2220 - 1229 - 1235 / Block:                 1435 / Flight:                1409

OFP Times:     2200 - 2220 - 1231 - 1239 / Block:                 1439 / Flight:                 1411

A350 Times:   2204 - 2220 - 1231 - 1239 / Indicated Block: 1411 / Indicated Flight: 1347

So, as you can see the block and flight times sensed is no less than 24 minutes less.

As additional information block fuel used was 102.100 on an OFP value of 99.200. Meaning only a 2900 Kg difference over 14.5 hours. Which is pretty accurate. Meaning that this difference is not due to any unseen freeze or time compression. It was flown fully in real time.

Edited March 5 by MD82

[bintheair]

I can confirm that this is also the case on MSFS 2020.