RussR
En-Route
I've always had a beef with Foreflight logbook generally logging 0.2 to 0.3 more than the actual hobbs or clock time. This is one of the reasons I don't use it, and when students do, I typically edit the time logged to better reflect reality.
But I do use Foreflight's automatic track logging, and recently had a flight that was so ridiculously overestimated I had to look more into it.
We (manually) logged 0.6 from block-out to block-in. Foreflight called it a 1.1. So a 0.5 hour difference, or an over-logging of 83%.
When does Foreflight start and stop logging? I found this, but it's pretty brief and vague.
https://support.foreflight.com/hc/e...ecording-Track-Logs-with-automatic-recording-
As for this flight, it was a post-maintenance check flight. We started engines and sat there for about 20-30 minutes before even releasing brakes. Since we use Foreflight as an EFB, it was open and running this whole time. At some point during this time, Foreflight started auto-logging (Why? How? No idea.). According to its data, it started at 1:54 PM and shows that we didn't start taxiing until 2:11. Tracking during takeoff and flight seems fine.
Then we land and get to the parking spot at 2:48, followed by an immediate, normal shutdown. Foreflight keeps tracking as we sit in the plane for the next 7 minutes and continues to track until I get in my car and make it out of the parking lot at 3:00, at which point it decides that's enough and stops (again, not sure why or how it made that decision).
Foreflight auto-track logging is a great tool for debriefing and such. But for auto-filling a logbook? Bleh.
Does anybody have any more in-depth information on how and why and when it starts and ends auto-track logging?
But I do use Foreflight's automatic track logging, and recently had a flight that was so ridiculously overestimated I had to look more into it.
We (manually) logged 0.6 from block-out to block-in. Foreflight called it a 1.1. So a 0.5 hour difference, or an over-logging of 83%.
When does Foreflight start and stop logging? I found this, but it's pretty brief and vague.
https://support.foreflight.com/hc/e...ecording-Track-Logs-with-automatic-recording-
As for this flight, it was a post-maintenance check flight. We started engines and sat there for about 20-30 minutes before even releasing brakes. Since we use Foreflight as an EFB, it was open and running this whole time. At some point during this time, Foreflight started auto-logging (Why? How? No idea.). According to its data, it started at 1:54 PM and shows that we didn't start taxiing until 2:11. Tracking during takeoff and flight seems fine.
Then we land and get to the parking spot at 2:48, followed by an immediate, normal shutdown. Foreflight keeps tracking as we sit in the plane for the next 7 minutes and continues to track until I get in my car and make it out of the parking lot at 3:00, at which point it decides that's enough and stops (again, not sure why or how it made that decision).
Foreflight auto-track logging is a great tool for debriefing and such. But for auto-filling a logbook? Bleh.
Does anybody have any more in-depth information on how and why and when it starts and ends auto-track logging?