Changelog for October 23, 2026

Welcome to Flightpad’s very first changelog! The app is still in beta, but the App Store release is ready to go! Next week I’ll be at The Airplane Factory building my Sling TSi, so I won’t get much done on Flightpad, but I will be having a great time.

My primary goal is that a pilot using Flightpad is never surprised by important information. We are getting closer!

Summary

This was a big week of general polish and improving NOTAM decoding. I paid close attention to headline parsing, dual filings, and finding discrepancies in the data. I also added a “Send NOTAM Feedback” button when viewing a NOTAM.

Adverse Conditions card on a solid surface — Going through a round of testing, I realized that I still wasn’t leveraging Apple’s UI kit sufficiently. At some point in the near future, I’m going to be adapting the Flightpad UI to work on iPad and the iPhone Duo. Apple’s new design guidelines clearly show that Adverse Conditions should be a glass panel, so now it is!

Adverse Conditions card on Liquid Glass, with airports scrolling beneath it — Going through a round of testing, I realized that I still wasn’t leveraging Apple’s UI kit sufficiently. At some point in the near future, I’m going to be adapting the Flightpad UI to work on iPad and the iPhone Duo. Apple’s new design guidelines clearly show that Adverse Conditions should be a glass panel, so now it is!

Highlights

The NOTAM card is now called “Adverse Conditions”. The card shows more key information and is the obvious target for showing weather events (SIGMETs, AIRMETs, and G-AIRMETs, oh my) and other important flight information.

I’ll write more about how Flightpad determines importance later, but it constructs a corridor connecting each airport in the list, then does a geographical lookup (expanded 50 nm) and finds any key information along that corridor. For a single airport, it’s just a radius, so much simpler!

The Adverse Conditions panel is pinned at the top and the airports scroll beneath it. I’ve added a new “Pin Adverse Conditions” setting. When toggled off, the Adverse Conditions panel scrolls with the airports.

I’ve also cleaned up the text and labeling in the card. Hopefully everything is much easier to read now!
Fields with no METAR data will borrow the nearest reporting station within 25 nm and 1,500 ft of the field’s elevation. For example, Jean Airport (0L7) now borrows weather from Henderson Executive Airport (KHND). When an airport is borrowing weather, Flightpad adds a KHND · 16 nm NE label on the card, header and Weather section. Flightpad won’t assign a flight category for borrowed weather, but runway wind components use the borrowed wind, with a label explaining the source.
There is now a “Send NOTAM feedback” button to report bad or missing info. Please use it!
The FAA contraction’s list and other guidelines use the common-in-America “canceled” spelling, rather than “cancelled” (although “cancelled” appears in plenty of FAA content). Flightpad now consistently uses “canceled” 🇺🇸.

New

Rows under “Also filed as” will open the other filing in its own detail sheet, loading the full record.
You can now delete an Airport List from the Manage sheet (using the built-in edit-mode minus control). Relatedly, there’s now a “Remove Airport” button at the bottom of the airport’s “Add to Lists” sheet. Both require confirmation.
Improved NOTAM schedule parsing means that Flightpad correctly reports when part-day and weekday NOTAMs are in force. As a bonus, in the decoded section, Flightpad reports in local time (“Active until 8 PM”, “Inactive until Mon 8 AM”). Weekday schedules get an easy-to-read Schedule line (“Scheduled Mon–Fri, 8:00 AM – 9:00 PM local time”).
Detangling the confusion around estimated end times! Sometimes an ICAO NOTAM doesn’t report an estimated end time, but the domestic copy includes one. Flightpad now correctly manages these discrepancies and explains them. I’ve also included a countdown, which reads as “Around 6 hours remaining”.

Improved

Duplicate NOTAMs are now collapsed in more cases. For example, in France there are multiple FIRs but when they pass through the FAA, each FIR is a separate NOTAM. This causes a fanout problem where 1 source NOTAM creates 5+ individual FAA NOTAMs. This brought LFPG from 422 records to a more accurate 251. Now procedure amendments the FAA publishes twice (FDC and ICAO) are listed once, and NOTAMs carry their own public number (KMFR 10/011 instead of A0493/26). This makes the NOTAM data much easier to navigate.
Updated the NOTAM plain language decoder to incorporate changes from FAA Order 7930.2U Change 2 (effective Sep 30). More contractions are expanded (LDG, MNT by context, CL, ELEV, HRS, RMK, PSN, HGT, TAX, XNG, FLTCK, REIL and ICAO-only ones); decimal distances read more naturally (“11.0 nautical miles”); state codes like WI and NE are no longer read as “within” and “northeast”. Plain language decoding covers NOTAMs up to a 155 character limit, which covers around 80% of NOTAMs.
Fixed some issues with NOTAM categorization, so that procedures, taxiways, navaids and airport notices no longer land under Runway because they mention a runway (e.g., “TWY C BTN TWY B AND RWY 08/26 CLSD” is a taxiway notice).
NOTAMs at busy airports load 4x-6x faster (KLGA’s load times went from ~3 s to ~0.5 s).
Flightpad generates short titles from the FAA’s standard wording (“TFR 11 nm SE of Seneca, OR”), and adds a chip naming the CFR section ( 91.137(a)(1) , 91.141 , 99.7 ).
Altitudes with no stated datum read MSL (“Surface - 6,100 MSL”), and altitudes read more clearly throughout Flightpad.
Flightpad displays network errors more clearly. A server-side, networking, or decoding failure now shows an error in red with the reason (“Unexpected error · HTTP 503”), apart from the amber “couldn’t check” for being offline. Airports without coverage report “No NOTAMs available for this station” instead of an ambiguous, general error.

Bugs squashed

US fields with a non-ICAO FAA identifier (e.g. 2S0) now get weather, NOTAMs, advisories and station status, and the airport data says whether they have weather reporting. Airport identifiers are such an annoying data problem.
Canceled NOTAMs no longer stay active (the Wawona TFR, KZOA FDC 6/4364, was still shown after it was canceled), and NOTAMs with an estimated end no longer show as permanent.
G-AIRMET reissues no longer appear several times; contour lines (e.g. freezing level) are no longer treated as areas.
NOTAM headlines parse line wraps more accurately, so Flightpad no longer drops text after a line wrap. Previously, some NOTAMs lost their PPR clause, obstacles lost their height, and some procedure amendments lost their procedure and minimums.