Almost certainly the issue is that I'm preserving the search (in the address bar, do you see "fq=..." in the URL?) The idea is that you realize "oops, I made a mistake on 5 flights in October of last year", so you search for something that matches those flights, then you edit each flight...
I just coded up a grouping option "Day of year" for the Analysis section on the website. It uses 366 days (so that you can capture how much flying you do on leap-day), but the google chart doesn't quite like 366 data points - it looks like it cuts off at about the end of November. But you can...
Ummm...what's missing? In MyFlightbook.com, Go to Training->Achievements and scroll down. There's a link "View a calendar of your flying" that will draw the calendar with the # of flights on each day, limited to the time range specified in the dropdown for the Flying Stats. And those stats...
Log ground sim time for those flights. (Leave Total Time blank). In the example above, you logged 2 hours of Dual and 2 hours of ground instruction, but I'm populating that column from the "Ground Simulator" field if the type of sim matches the column type (i.e., FFS, in this case). I notice...
Yeah, bad example on my part. Yes, it's complete when the instructor says it is, though I'm having a hard time figuring out how that point doesn't correspond to a flight or ground session (even if there were multiple, and in any order) - and hence to a (dated) entry in the logbook.
My...
Yeah, note too that the endorsement is really the record/affirmation of the flight review, but it's the flight that's controlling. Also could be confusing if you do the flight on Jan 31 and your instructor gives you the endorsement on Feb 1, for example.
Correct - I don't try to parse endorsements because the text can vary. If you add the flight review property to that flight, it will not remove the signature but it will invalidate it. What I suggest doing is either (better) adding the flight review property and asking your instructor to...
Per private conversation, but now sharing with the broader thread: import now accepts (some) non-numeric values for the "Approaches" column. So if it's numeric - great: 4 = "I did 4 approaches" (described elsewhere). Otherwise, if it starts with a number (e.g., "4 ILS-Y-RWY16L@KSEA") or ends...
Send me a sample (myflightbook@gmail.com)? I don't generally detect/import approaches from telemetry data, but maybe I can figure out how to recognize that. Happy Thanksgiving!
Exactly, that's where you do the "join" - the visited table has the airport code, and you can "join" on "route contains". You may get a few misses, though (e.g., PHOG will miss OGG, KSFO will miss SFO), but it should be a decent proxy.
Hmmm...at the moment, probably the easiest way to do that would be in Excel. You'd want to download the visited airports table and the CSV of your flights and I bet you could build a pivottable or use a sumif based on distinct tails. But even then it would be approximate because a simple...
I'm not sure I can do a whole lot better than the graph above - I can only infer flying type based on aircraft type (Boeing 787 is probably not GA, C172 probably is). But here's a quick and dirty query swag based on flights on MyFlightbook since Jan 1 2022 - looks like it's pretty skewed...
Back home now. Can't find my physical keyboard for the iPad (huh, I could swear I had one), but in the debugger this all works fine; I can't seem to reproduce it. can you email me (myflightbook@gmail.com) a crash report and I can try to figure out what the crash is...
Couple of ways.
Download the spreadsheet (Website, go to Logbook->Download) and share that
Or, go to Profile->Preferences->Sharing and you can create a link that you can share and which exposes various aspects (under your control) of your logbook.
Thanks for letting me know. I'm traveling right now without a keyboard for my iOS devices or my Mac, so can't look into this until I get back next week, but I'm tracking it at https://github.com/ericberman/MyFlightbookiOS/issues/281. I'm getting ready to do an update anyhow, so this may be...