reported Time On Target gets dropped when time passes through 00:00z

[norman99]

Not sure if this is how it's meant to operate or a bug, but I have experienced the following behavior.

 

If the current time is prior to midnight zulu, (such as 23:50:00z), and you set a time on target for a future waypoint that is beyond midnight zulu (such as 00:05:00z), it requires the time to be incorrectly entered as 24:05:00z for the system to give correct speed indications.

 

However, once the actual time passes 00:00:00z, this become invalid, and no longer provides correct speed indications. The time on target then needs to be changes from 24:05:00 to 00:05:00 to work correctly.

 

NATOPS paragraph 24.2.5.3 states valid TOT inputs as 00:00:00 to 23:59:59, so my guess is this is a bug simply due to the calculations not continuing smoothly through midnight zulu. It therefore thinks 00:05:00 is actually in the past up until 23:59:59, hence the need to use 24:05:00 instead, until the actual time has passed midnight.

 

A lot of number in my explanation, but I hope that makes sense.

Edited April 7, 2021 by norman99

[norman99]

Sorry I couldn’t supply one this time but it’s 100% repeatable, so I’ll set one up shortly.

[Harker]

Reproduced. Track attached.

FA-18C_TOT_midnight_ZULU bug.trk

[Elnocho3]

When time is involved, always include a midnight tick-over test

Edited April 7, 2021 by Elnocho3

[norman99]

Looks like @Harker beat me to it re uploading a track. Thanks mate.

[BIGNEWY]

reported for checking.

 

thanks