Say Intentions / 2026

Changelog for October 30, 2026

I was over in Los Angeles working on my Sling TSi this week, so my limited Flightpad time was spent on polish and preparing for the App Store.

Highlights

  • There is now a first-launch disclaimer, reinforcing that the PIC is responsible for decisions. It’s per device, and I can bring it back if the terms or critical information change.

    Before You Fly: information only, data can be late or wrong, the pilot in command is responsible, with an I understand button

  • Significantly improved the API key generation code, which handles retries more sensibly and catches more cases where the key generation could stall and Flightpad gets stuck.

  • Fixed a performance issue with the pinned Adverse Conditions card. A beta tester (thanks Mom!) reported a delay of over a second before a tap responds, and it turns out that ViewThatFits is a bit sensitive. The layout is now calculated better (and is much faster!), which also fixes some other overlapping issues at large text sizes.

New

  • Empty lists give hints on what to do next and make it easier to add an airport. Expect more UX work here!

    All Airports

    Empty All Airports with Find an airport to add and Create a list buttons

    Named list

    Empty named list with a Find an airport to add button

  • Airport and list screens refresh NOTAMs and station status every 5 minutes while Flightpad is open. A failed check keeps the last state.

  • A new “FAA data differs” badge is used when the filed NOTAM’s time differs from the FAA’s structured data, with a note that the filed time is the one that applies. This is an unusual case, found in 5 out of ~72,000 NOTAMs (see FDC 6/1095 for an example).

  • Schedules that cross a daylight saving time change now call it out: KAPC 10/007 reads “Scheduled Mon–Fri, 6:00 AM – 6:00 PM PDT until Oct 30; 5:00 AM – 5:00 PM PST from Nov 2”.

Improved

  • TFR titles now lead with the kind and place, like “VIP Movement TFR Las Vegas, NV” instead of an inscrutably long and useless title. All the named TFRs are supported (e.g., “Disaster/Hazard”).

  • Fixed the language when there aren’t any Adverse Conditions detected. The previous text was misleading. It now says what was actually checked and considered (“Nothing critical found for 4 of 5 airports” or “Nothing critical found at this airport or within 50 nm”).

  • The Adverse Conditions icon now shows the METAR’s sky icon when there are no adverse weather events. Why this wasn’t already in place is beyond me. I make weird choices sometimes.

  • NOTAM altitudes and coordinates now get their own rows to improve readability.

    Before

    NOTAM detail for FDC 6/2074, Selfridge ANGB, with the coordinates, 2 NM radius and Surface – 2,000 ft AGL in a small grey caption under the map

    After

    The same NOTAM with Altitudes (Surface – 2,000 ft AGL) and Location (42°36.1′N 082°49.2′W, 2 NM radius) as rows under the map

  • Flightpad reports estimated times more clearly, especially when only the domestic copy of the NOTAM provides an estimated time. It reads “The domestic copy of this NOTAM, 6/8612, gives this end time as an estimate”. Linked NOTAMs and time discrepancies are described much better.

Fixed

  • Fixed a bug where scheduled closures weren’t being accurately parsed, so airports were being badged as closed after they had opened.
  • Fixed a bug where scheduled airport closures were marking airports closed for the whole date range, so airports showed Closed after they had reopened.
  • Washington, DC SFRA and FRZ notices are now pinned to the DCA VOR/DME. They have no position, so they showed up at New York area airports whenever the 50 nm search touched ▎ Washington Center’s airspace, even though DC is about 170 nm away. They also get ▎ clearer titles: “DC SFRA security instructions”, “DC FRZ security instructions” and “DC SFRA drone (UAS) instructions”.
  • Taxiway closures described relative to a runway (KTEB ‘TWY G EAST OF RWY 01/19 CLSD’) are now taxiway notices, not runway notices.