On Monday, May 20, 2019 at 4:42:52 PM UTC-4, wrote:
I’ve not heard back from Lxnav yet, but I had a private email from a very smart person that pointed out that both the October 2 and October 4 flights had the clock jump after takeoff but before soaring began. The flight this week had the clock jump a minute or so after soaring began, and thus is likely why OLC flagged this one and not the other two. It appears that the clock jump is 7 to 8 minutes after the unit is turned on. Since I generally do not turn the system on until just before takeoff, it is believed that the system is using an internal clock until it syncs with the gps satellites and then resets the clock which may be different by a couple of seconds. My plan is to turn the 9070 on a few minutes before launch to allow it to sync clocks to see if that helps. It is not clear to me if Dan’s issue is similar to mine or different.

MS

We've established in another thread some months ago that the display of altitudes of a flight within the OLC web page is all messed up if OLC thinks that the flight "started" later, at some higher logged altitude, rather than at the altitude of the declared takeoff airport. (Typically due to the flight recorder not getting a GPS fix - or not being turned on at all - until after takeoff.) I am still of the opinion that this should be considered a bug in OLC, since it can "see" that the start location (lat/lon as well as altitude) is not at the airport. The altitudes inside the flight log file, even as downloaded from OLC, are still OK. Perhaps the time jump, too, makes OLC think it's a new "takeoff", and thus has similar consequences in its display (plus its "implausible" warning).

But I don't quite understand the conjecture that "the system is using an internal clock until it syncs with the gps satellites", because prior to getting a GPS fix the flight recorder shouldn't be recording locations into the flight log either, no?