Issues to be aware of

Changes in 0.19.11

Issues addressed in 19.11

1.Fixed several errors in the revised Print Trip Kit (changed as a result of a change in the compiler logic)

2.Fixed the UI message that asks if you want to turn off the weather to provide Yes/No logic as before

3.Fixed an out of range issue on certain cases where the CFMU response is nil

4.Fixed an error that occasionally resulted in partial matches of waypoint names being viewed as a full match in evaluating RAD Conditions

5.Fixed an issue where wind epoch was not updating if FPP was left running for an extended time

6.Fixed an issue where the route could get locked (inter process control)

7.The open logs button now opens the FlightPlanPro folder rather than its parent (there is also an emergency start option)

8.The ‘Invalid Authorisation’ message from NWX was identified as some users not having their computer clocks set to GMT + Local time offset

9.Fixed an issue loading some flightplans

10.Fixed an issue where the FPL was not being shown when routing, but was when validating

11.A point where the airway changes (but not level or direction) is now included in the plog

12.Fixed a critical issue in setting the block field for mandatory routes

13.Mandatory routes are now forced to be the full defined segment, the route won’t drop off partway through (although it can still do this on the original link definition)

14.Reduced flickering on Windows and other anomalies generated by the new compiler version

IMPORTANT NOTE - FlightPlanPro uses web services from, and Some people’s antivirus/web security systems are blocking these service calls.  The symptoms are FlightPlanPro being unable to contact the registration server, validation requests timing out or being unable to obtain weather/winds information.  The solution is to whitelist the three URLs above.

  1. Recently some restrictions have been added by CFMU that are not included in the Electronic RAD.  To the extent these involve a level cap or a mandatory routing, FlightPlanPro will not be able to resolve these.

  2. If you get a No Route message, check that the minimum and maximum altitudes are sensible. 

  3. FlightPlanPro should be able to process all Mandatory Route messages.  However, the logic has required extensive testing and reports of any failures to correctly resolve these restrictions will help develop the product

  4. Note, the altitude optimisation uses too much memory and can cause a programme crash on longer routes.

  5. The cloud profile doesn’t always work correctly for routes over 1000 miles.

  6. If you are flying a circular route (same departure/destination), the Notam brief will give an error.

The list of known issues that are being worked on is here

FPP0.19.11 Zero Foot Print

A zip file with the Mac, Windows, Linux programmes and data files ready to be loaded on to a Memory Stick.