Skip to main content
Skip table of contents

Leica FlightPro 6.2.6 Release Notes

Leica FlightPro 6.2.6 is the recommended release for the flight season 2026 for Leica CityMapper-2 and Leica TerrainMapper-2 systems.

Systems

  • Leica CityMapper-2

  • Leica TerrainMapper-2

Main Features

  • No new features were added in Leica FlightPro 6.2.6 for all systems

Main fixes

  • Flight Execution: FlightPro will correct repeat missed events for Fly missing parts option for image events with errors for systems with LiDAR Unit

  • GNSS/IMU: Fixed the wrong PAV heading values when the real-time trajectory status changes

  • Logging: The PAV log files are again saved to the log folder on the USB connected to the pod after the session when Export thumbnails to external drive option is activated in FlightPro

  • Logging: Session export is now more robust

  • Mass Memory: Prevents losing Mass Memory access when copying log files

  • Performance: Increased internal resources to prevent missing images

  • Performance: Improved system stability

Main Changes

  • Cameras: Improvements in shutter handling

  • Interface: Improved texts for error and warning messages

  • Performance: Operator and pilot can’t select or use the 3D navigation views on an OC60 Operator Console

Known Issues

  • MM30: Formatting of MM30 Mass Memory 7680GB M2 with FlightPro takes nearly an hour on some systems with older software

Upgrade Notes

  • Recommended upgrade path from:

    • Leica FlightPro 6.2.5 for Leica CityMapper-2 and Leica TerrainMapper-2 systems

Workflow requirements

Software

Version

Leica MissionPro

  • 12.8.1 or greater is mandatory for CityMapper-2

  • 12.16.0 or greater is recommended

NovAtel Inertial Explorer

  • 8.80.2305 or greater is mandatory

  • 9.00.0731 or greater is mandatory with All selected for Selected GNSS systems.

  • 11.00.1023 or greater is recommended

HxMap

  • 4.4.0 or greater is mandatory

  • 4.8.2 or greater is recommended

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.