Search results

I love that airport list. Being based near Seattle myself, I've been to every one of them. I actually set a goal for myself 15 (!) years ago to land at every public-use airport in Washington. Did it, and then added Oregon and Hawaii. If you go to the Achievements section on MyFlightbook...

Note that MyFlightbook's visited airports computation will de-dupe by location, so SFO and KSFO are one airport, and if XYZ changes to ABC they will also be grouped together as one.

Log the time in a flight with (a) the sim as the "flight" aircraft, (b) the time of the session in the "Ground Sim" field, and (c) any other fields/properties as appropriate. You are correct you almost certainly can't log it as total time or as PIC time, at least not under FAA rules. The...

Already on my todo list - https://github.com/ericberman/MyFlightbookiOS/issues/171

https://github.com/ericberman/MyFlightbookWeb/issues/

Hi, Tom. Note that I’m traveling and will be very slow to respond to anything over the next few weeks (little internet) you can only edit airports that you’ve added, if it’s “built in” or created by another user, you can’t edit. Note also that I keep old airport codes around as long as...

So there are two pieces here. The first is whether the 20 hours of training must be in a multi-engine aircraft. Subject to the disclaimer that follows: I believe the answer to that is "yes, it does", because it must be done in accordance with 61.107(b)(2), which requires multi-engine. The...

I'm afraid there isn't at the moment. I'm just following usual "accounting" practices of showing all of the various subtotals, followed by the "bottom line" at the ... bottom.

Recording 1 night takeoff will shut off the warning...but then you're not current because you only have 1. You should log 'em. Note that the warning isn't an alert - it doesn't pop-up or interrupt you or anything like that. It simply shows in fine print (not even red) underneath your night...

Not new, but slightly modified a few months ago. PIlots are always lax about recording night takeoffs, so my rule has always been "if I don't see them, assume this pilot doesn't record them and just use landings but give a warning that night takeoffs haven't been found, but if you do see them...

All looks correct to me. 61.57(b) requires 3 full-stop landings AND 3 night takeoffs within the preceding 90 days of flight. If I search in your account for night takeoffs, I see 1 on April 1 and 2 on March 31. So while your 3 full-stop night landings on June 9 gave you 90 days of night...

I've checked in a code fix for the widgets - it wasn't respecting night mode. Maybe will try for an update of the app next week or so.

I was going to say - that looks like black-on-black. I'll have to file a bug to ensure that I handle night mode correctly. Thanks! https://github.com/ericberman/MyFlightbookAndroid/issues/230

Mind trying to set up widgets with the latest build and report back if it works? Thanks!

Huh, just tried on my emulator (running Android 10 on an emulated PIxel) and they work fine. I don't have a physical device with me (won't be home until Monday), but it's working in that. What version android are you running?

Airborne now without my Android; will check later

Yeah, the issue is the translucency over a light colored background image. I should see if I can increase the opacity of that background

Here's how it works: XXX ==> Matches Airport XXX, IF it's a perfect match. E.g., KSFO or SFO both match perfectly to San Francisco International. "Airport" here means Airport, Heliport, or Seaport (i.e., not a navaid or fix) XXX ==> Matches Navaid XXX, IF there is no airport/heliport/seaport...

Just coded up support (web only) for @xxx where xxx is mgrs. Will take it live in a few days.

Nah, the path of least change is to pattern match on the syntax of an MGRS coordinate that is at least a given level of precision (1km?) and then use the CoordinateSharp to convert it to a latitude/longitude for me. No need for a special syntax.