Module 05 · Before flight

Nav Planner

Trackfusion Nav Planner — ground mission planning

Select the destination and waypoints. Calculate and review the route, then export the flight plan. Nav Planner gives the onboard navigation system a reviewed route to follow.

Desktop plannerQGC .plan import / exportCombined deployment planned
GROUND WORKFLOW

Build and review the flight plan.

Planning stays on the ground. The host autopilot executes the plan, while TrackFusion supplies the aircraft’s navigation estimate.

  1. 01

    Define

    Select the departure, destination and intermediate waypoints. Load terrain and the mission’s planning constraints.

  2. 02

    Calculate

    Generate a route using the selected inputs and aircraft profile.

  3. 03

    Review

    Inspect the route, altitude, endurance estimates and warnings. Adjust the plan before export.

  4. 04

    Export

    Export the reviewed route as a QGroundControl .plan file for the flight-plan handoff.

Current export contains the flight plan. Reference imagery packaging and verified onboard loading are planned Shoal-OS integration steps.

PLANNED MISSION INTEGRATION

One mission. Two onboard handoffs.

A mission package associates the reviewed route with terrain references, thermal reference imagery and payload configuration. Each part goes to the system that uses it.

FLIGHT PLAN → HOST AUTOPILOT

Route and waypoints

The host receives the flight plan and retains flight control. Its route execution uses the accepted navigation updates from the payload.

REFERENCE DATA → PAYLOAD STORAGE

Terrain and imagery

Radar terrain references and thermal imagery are loaded into onboard storage accessible to the fusion pipeline. The board design determines the physical memory arrangement.

Planned deployment management records the package version and confirms loading. The .plan export alone does not provide the reference-data handoff.

Follow the onboard navigation.

Inertial navigation, radar terrain correction and thermal cross-verification.