Having seen bespoke industrial software up close...
...I hypothesise that there is a fixed-sized data structure with a number of event slots or similar, that can hold 52 days worth of data, and which is supposed to be overwritten in a circular manner.
Only the overwrite code is shit, so you end up with old data presented as current.
This data structure is not persistent between powercycles, hence the instruction to turn the plane off and on again every 51 days.
Or something.