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

2. 2.Only airway connected navaid and waypoints are considered by the routing engine.  You are unlikely to be able to route directly to an IAF that is not an airway point (i.e one that is part way through a STAR - you will need to route to the end of the STAR)
   

3. 3.Not all SID and STAR enty/exit points are included.  If you get a silly route, compare the ‘known’ SID/STARs to those charted by selecting SID or STAR in the drop downs at the upper left.  The drop down to the right will show a list of all of the entry exit points FPP will consider.  If there are others on the approach plate try routing directly to them.
   

4. 4.If FPP fails to resolve an Off Mandatory route please email the details, this will help further improve the routing logic
   

5. 5.Detail SIDS and STARs remain incomplete in FPP.  If a good route is not developed, it is very likely that a look at the approach plate will identify the correct SID or STAR.
   

6. 6.In Scandinavia, there are some airports with mandatory arrivals defined from an approach waypoint, but there this point can only be accessed via an unpublished DCT.  FPP will not generally get the correct answer on these.  If any of these effect someone’s home airport contact comment@flightplanpro.eu and the database will be updated for your airport.
   

7. 7.The Navlog does not include MSAs for each leg

Copyright ©   2011  

Feedback and Comments