The MyFlightBook thread

Is there not a method to store all your own data in your device, thought I'd read that.
If excessively concerned, one could to a regular dl as a backup.
You can donate to the cause and get a spreadsheet dumped into the cloud provider of your choice, nightly.
 
You can donate to the cause and get a spreadsheet dumped into the cloud provider of your choice, nightly.
And you can manually download your own copy whenever you wish (unless that's changed).
 
Sorry if this has been asked already - but how are flight instructor signatures handled when porting to other e-flightbooks? Does the actual signature image get transferred too?

Let's just say Foreflight or any of the most popular books since I'm sure the answer depends on which software.
 
Sorry if this has been asked already - but how are flight instructor signatures handled when porting to other e-flightbooks? Does the actual signature image get transferred too?

Let's just say Foreflight or any of the most popular books since I'm sure the answer depends on which software.

DCR, I have used three methods of recording endorsements, BFRs etc on MFBP.
1. Uploading an image (jpg) of any sticker, piece of paper etc etc onto my elogbook.
2. Same, with a pdf (which my iphone can apparently generate) from something an instructor emails you
3. You can also send, through the app, a request emailed to your instructor which they can access and then sign on the app.
All are recorded and preserved for years, I just checked.
 
  • Like
Reactions: DCR
Is there not a method to store all your own data in your device, thought I'd read that.
If excessively concerned, one could do a regular dl as a backup.
There are several. If you're using the mobile apps, there's a pack-and-go feature that lets you view your data while offline, but I think you were asking for something a bit more flexible.
For that, you'd use the website. Go to Logbook->Download, and you can download a CSV snapshot of all of your data and optionally a zip file with records of your endorsements and images.
You can also connect MyFlightbook to Dropbox, Box, Google Drive, and One Drive and with the press-of-a-button save the aforementioned CSV and zip files to the respective service. The beauty of the CSV is that you can open it in any spreadsheet program for analysis, or to do a bulk edit, or (gasp) if you decide to move to another service (heaven forbid!) you can use it to import your data into that service.

And of course, Dropbox/Box/Google Drive/One Drive all will sync to your mobile device.

It is, after all, your data...
 
Eric, is there a way to create "airports" only visible to me?

I've recently started flying ultralights. I almost always fly from non-airports. Like a friend's farm, that kind of thing. I could enter the coordinates each time, but that seems like it would be tedious. I'd like to create a user-defined location, like "Bob's Farm" with the coordinates and be able to enter "Bob's Farm" in the route of flight. But if I create it as an airport, then I think that makes it available to everybody, which isn't really necessary or even appropriate.

Is there a way to do this, or something like this, that I'm missing?

Note - this is for manual entering of flights in the log. How would this work for autodetecting? I assume it would find the nearest airport in the database and use that, which also wouldn't really work for my intended use.
 
I had a bad news/good news experience with MFB recently: I went out of town for a checkride, and I left my old paper logbook in the safe at home because I haven't used it in years (you can see where this is going). At the checkride, the DPE asks me for an endorsement that I received before my my original glider solo, 11 years ago, that only exists in my paper logbook. And unfortunately, my instructor was also out of town . . . . But he was able to pull out his phone and do the endorsement right in MFB. :cheers: So MFB saved my butt (and all my old endorsements are now scanned and uploaded).
 
Eric, is there a way to create "airports" only visible to me?

I've recently started flying ultralights. I almost always fly from non-airports. Like a friend's farm, that kind of thing. I could enter the coordinates each time, but that seems like it would be tedious. I'd like to create a user-defined location, like "Bob's Farm" with the coordinates and be able to enter "Bob's Farm" in the route of flight. But if I create it as an airport, then I think that makes it available to everybody, which isn't really necessary or even appropriate.

Is there a way to do this, or something like this, that I'm missing?

Note - this is for manual entering of flights in the log. How would this work for autodetecting? I assume it would find the nearest airport in the database and use that, which also wouldn't really work for my intended use.
Hi, Russ. No, I don't have the notion of private-to-you airports. I actually don't want to have such a feature, for the exact same reason that I don't want private-to-you aircraft: crowd-sourcing of data depends on people creating shared data. If it's private, then the crowd-sourcing will fail.

But there is absolutely nothing wrong with making up codes for your friend's farm and using that. I generally suggest 5- or 6- letter/number codes, so as to avoid naming conflicts with ICAO, FAA, and IATA codes, but go ahead and give that sand bar or field a name. And then, yes, autodetection will work (once the airport database update migrates to the iOS/Android device, which usually takes a few months...)
 
Hi, Russ. No, I don't have the notion of private-to-you airports. I actually don't want to have such a feature, for the exact same reason that I don't want private-to-you aircraft: crowd-sourcing of data depends on people creating shared data. If it's private, then the crowd-sourcing will fail.

But there is absolutely nothing wrong with making up codes for your friend's farm and using that. I generally suggest 5- or 6- letter/number codes, so as to avoid naming conflicts with ICAO, FAA, and IATA codes, but go ahead and give that sand bar or field a name. And then, yes, autodetection will work (once the airport database update migrates to the iOS/Android device, which usually takes a few months...)
Thanks Eric, I'll give it a try.
 
Back
Top