Brolin McKay wrote:
We currently have logging as a triage solution with MyFlightBook.
Go to menu/history/(select your previous flight)/export/export to MFB.
You will need a MFB account, but that's how you can do logging (at least until we finish what we're doing with our huge project ;) )
Somehow I completely missed this feature being added, and have never tried it before. I'm an avid MyFlightbook user, but every once in a while I forget to tap the "Engine Start" button to arm it to detect takeoff and landing, and then have to go manually backfill the data...but the worse thing is that those log entries don't capture my GPS flight tracks. It'd be slick if this iFly feature would help (at least partially) save me from those errors.
In fact, the last time I flew I made this error, so I used that as a test for this feature. I fired up my Android tablet, found the past flight in my history, clicked the Export button, and selected "MyFlightbook" from the list of apps presented. MFB asked permission to access my data, which I granted, and it created a "PENDING" flight in my log to go review/update/save.
It was a disappointing experience, though: MFB gave the entry a placeholder title of something like "Created from GPS data", but there was not actually any tracking data included. Probably related, MFB did not pre-fill the route with my origin and destination airports like it would have had it been auto-tracking the actual flight. In fact, the only data that seemed to come over from iFly was the flight start/stop times (which actually landed in the Engine start/stop fields instead of the Flight start/stop fields, so I had to adjust all four of those times manually, anyway).
So this feature did not seem to work well at all, and was disappointing.