Mission validation guide

Supported ranges, such as altitude and waypoint limits, describe what FlyPath can plan or export. Caution margins are planning prompts. Neither establishes a legal altitude, obstacle clearance, safe battery reserve, or permission to fly.

• Meaning: The area or settings produced no flyable survey route.
• What to do: Check that the boundary is valid and large enough for the chosen altitude, overlap, direction, and margin. A corridor needs a usable centre line and width.
• Recheck: Generate or update the route after editing; an old route is not confirmation.

• Meaning: Estimated overlap between successive images is too low. FlyPath warns below 65% and blocks below 40%. In Semi-auto, overlap depends on speed and the pilot's interval capture setting; Full-auto plans photo actions.
• What to do: Slow down within the aircraft's supported speed range, increase altitude within supported and legal bounds, or use Full-auto with sufficient overlap. Higher altitude changes ground resolution; Full-auto can increase time and waypoint count. If minimum aircraft speed is still too fast, speed alone cannot fix the overlap. Set safe speed appears only when a supported speed can meet the target.
• Recheck: Recalculate and inspect the displayed estimated overlap.

• Meaning: Flight time and battery allowance are estimates from the route and aircraft profile. Near battery limit warns above 85% of the usable allowance; exceeding the modeled allowance blocks export and names the affected flights. Estimated batteries are total modeled survey time divided by that allowance, rounded up; configured flights are separate. Travel and actual conditions may need more capacity.
• What to do: Split the route into flights or revise it. Splitting alone does not prove adequate reserve.
• Recheck: Recalculate, then inspect every flight and its battery estimate.

• Meaning: Each exported flight must fit the supported waypoint limit. Minimum flights is a request; route segments, battery allowance, and the waypoint cap can change the actual count. Flight count adjusted reports the requested and produced counts for a valid result.
• What to do: Adjust Waypoints / flight, split the route, or simplify the survey if a limit is exceeded.
• Recheck: Review the flight list and every planned start point after any split.

• Meaning: For fixed altitude, FlyPath compares sampled ground with each flight's starting ground reference. Clearance below the 30 m caution margin warns; zero or negative clearance is an error. Terrain above flight altitude means sampled ground reaches or exceeds the planned height. The margin is not a certified safety threshold; samples omit trees, buildings, wires, and some ground changes.
• What to do: Revise the route or increase altitude if the required setting is within the supported maximum, currently 150 m. A capped increase cannot resolve a higher required height. Terrain follow may help where available. Check local legal altitude limits independently.
• Recheck: Recalculate and inspect the planned heights and clearance.

• Meaning: Required heights exceed the limit relative to the affected flight's starting ground reference.
• What to do: Splitting at suitable launch references may bring flights within range.
• Recheck: Validate every resulting flight and its planned heights.

• Meaning: Terrain-follow export is blocked until valid data returns. Without terrain follow, ground-clearance checking may be unavailable.
• What to do: Retry after connectivity or terrain service recovery.
• Recheck: Inspect the updated route and terrain result.

Warnings for the selected After mission and Signal lost actions ask you to review what the aircraft will do. Go to setting opens the relevant control; it does not change the choice. Confirm the actual exported behavior and landing location before flight. These warnings appear again in Review and export.

The export review summarizes aircraft, capture mode, altitude, flights, waypoints, and survey time. Its launch assumptions explain the first-waypoint ground reference used for battery and terrain estimates. In Semi-auto, set interval capture before takeoff. Review the exported mission on the intended controller or DJI application, including each waypoint, height, speed, camera action, and safety action.

Connection and terrain messages identify which data could not be loaded. Retry when the connection returns; a terrain-follow mission still requires terrain data before export. If path generation or update fails, use Retry path or Retry update. A previous route may be out of date and cannot stand in for the current settings.

If saving fails, keep your planner tab open and retry after the connection or sign-in is restored. A mission changed elsewhere may need its latest version loaded or a real edit conflict resolved. Export request failures appear in the review dialog, where you can retry the download after recovery. Confirm that errors have cleared and the current route has been recalculated before exporting.