FlightSpan 10.16.0 includes two new features, as well as a number of enhancements and bug fixes.
New Features
- Scratch Pad flights, including all associated flight planning, can now be converted to actual flights
- Lowest Safe Altitudes / Minimum En Route Altitudes can now be added to stored routes and displayed on both the Map and the Basic Flight Plan / Nav Log. See the documentation for instructions.
Enhancements
- Checklists no longer overlay tab data; they have been moved to the right of the displayed data. Manually open a checklist from any tab by swiping left from the right edge. See the documentation for details.
- Long checklists are no longer compressed; instead, they are full size and auto scroll down to reveal the additional items that are off the bottom of the page
- Estimated and Actual fuel are now automatically captured and displayed on the Basic Flight Plan / Nav Log
- If you provide takeoff/go-around target power data to FlightSpan Support, it is now displayed on the Takeoff and Landing Performance Tabs
- The Landing Reduce and Takeoff Reduce Runway chart elements now display maximum takeoff weight and maximum landing weight together with the weight reduction amount
- Added the ability to log Holding and Intercepting/Tracking on the IMC and Hood columns on the DFR to facilitate pilot proficiency tracking in FlightSpan Ops
- Where TAFs are available but METARs are not, a white dot is now displayed
- Large NOTAM blocks can now be collapsed
- Runway Chart change history is now hidden by default; tap the Show Change History button to view
- If Zero Fuel Weight is out of limits, it is now displayed with an amber dot on the mini CG graph
- When sending a manifest with pax names that exceed the v2track character limit, all names are now included so you can edit down to the limit
- When sending a manifest with pax names, if the same passenger is listed more than once in FlightSpan Ops, they are only displayed once on the EFB search window
Bug Fixes
- Max Takeoff / Max Ramp arm label mismatch on expanded CG graph
- Cosmetic issue on Max Landing Weight Line in expanded CG graph
- En Route Waypoints inside the distance from home checkpoints were out of order
- Invalid Slope message on Water Runways
- After Landing Checklist Reset after leaving the Post Landing tab
- Load could be created with an empty route
- Block In/Out was not received by FlightSpan Ops if ATD/ATA was missing
- After an initial fuel transaction, subsequent fuel transactions from the same location overwrote the route from previous fuel transactions
- Decoded TAF blocks were sometimes out of order and one line of coded TAF data was sometimes missing