Import Flight Path (Closed Beta)

Have more questions? Submit a request

Note: This feature is currently in Closed Beta. Please reach out to your Customer Success Manager for more information on accessing it.

Overview: What is Recorded Flight?

The Recorded Flight feature allows you to use a flight path recorded in a third-party application, such as DJI Pilot 2 or DJI Flight Hub 2, to create a repeatable flight plan in DroneDeploy.

This feature is designed for complex or highly specific missions that require precision and repeatability, such as inspection, zoom, and thermal tasks, by replaying the exact path and actions recorded by the drone.

Availability: Who has access?

The Import Flight Path feature is currently a Closed Beta.

  • It supports specific DJI drone models.

  • It supports connection to both DJI Docks and RCs (Remote Controllers).

How to use Import Flight Path

Follow these steps to create a Recorded Flight plan in DroneDeploy:

1. Fly and Record Your Mission

  • Use a compatible DJI drone (with RTK enabled for precision and repeatability) to create a waypoint mission in DJI Pilot 2 with Live Recording mode.

  • Fly the complete path, performing the desired actions (photos, video, zoom, gimbal moves, etc.) as needed.

  • Alternatively, create or edit the flight in DJI Flight Hub 2 using all the offline planning tools.

  • Best practice: Use RTK both while flying (recording) and when repeating the mission to ensure accuracy.

2. Export the Flight Path

  • Export the completed mission as a KMZ file from the DJI RC controller or from FlightHub2.

  • For complex media types (e.g., thermal, OGI), verify that your waypoints have the correct action types (photo lens, video lens). DroneDeploy only replays supported action types.

3. Create a Recorded Flight Plan in DroneDeploy

  1. In the DroneDeploy web app, select the Fly tab

  2. Choose the Recorded Flight or Import KMZ option (the entry point may appear under Site Management or a similarly labelled section).

  3. Upload the KMZ file (it must be 20MB or less—see Limitations).
     

    6e352da2-ac9d-4914-8c8a-b2ecfeb25c9f.png
    10db1587-5f43-420c-b8c9-5a277e147fad.png

4. Connect and Validate Your Drone

  1. Ensure the connected drone matches (or is compatible with) the original model used to record the mission.

    • Supported Drones: Mavic 3 Enterprise, Matrice 4 Enterprise, Matrice 30, Matrice 30T, Matrice 300 RTK, Matrice 350 RTK, Matrice 3D, Matrice 3TD, Matrice 4D, Matrice 4TD.

  2. Connect to the dock or RC as required.

  3. DroneDeploy runs a preflight check. If there is a mismatch in aircraft or payload, the system blocks the launch or displays a warning.
    7149f951-c69a-48e1-985a-0cf32e4825f9.png

5. Fly the Mission

  • Launch the flight plan from the DroneDeploy interface.

  • The drone autonomously flies the exact path, triggering the payload and camera actions as recorded.

  • Pause and resume are supported, but multi-battery missions are not supported.

Key Features/Details

  • Precision and Repeatability: The feature uses the exact flight path and recorded actions, which is ideal for change detection and high-accuracy inspection.

  • Third-Party Integration: It allows you to leverage detailed planning tools in third-party software like DJI Pilot 2 and DJI Flight Hub 2.

  • Actions Included: The plan replays recorded actions, including photos, video, zoom, and gimbal movements.

Limitations and Technical Notes

  • File Size: KMZ uploads must be 20MB or less. To avoid upload issues with large missions, consider stripping embedded images from the KMZ file.

  • Drone Uniformity: Use the same make and model of drone that recorded the original flight. Do not upgrade firmware or swap to an incompatible variant without retesting the mission.

  • Chaining Missions: You cannot chain multiple recorded flights. Plan each battery or mission separately and upload individual KMZ files.

  • Offline Functionality: Offline functionality is only supported for Docks. RCs require internet connectivity.

  • Mission Editing: You cannot edit a Recorded Flight plan within DroneDeploy.

Troubleshooting

If uploads fail or media is missing:

  • Check the KMZ for supported action types only.

  • Review drone and payload compatibility.

  • Ensure the file size is within limits and try stripping images if needed.

  • For advanced payloads, confirm whether media is being correctly geotagged and matched to the plan.

FAQs

Q: Can I edit a Recorded Flight plan in DroneDeploy?
A: No. You have two options: you can re-record, export, and upload a new KMZ to change routes or actions, or you can edit the file in DJI Flight Hub 2 and re-export it to upload into DroneDeploy.
e2ead7c9-6684-41b4-99a8-32b2e0c76b17.png

Q: Can I fly a plan with a different drone than was used to record it?
A: Sometimes, but only if the firmware or SDK allows. This practice is not recommended.

Q: Why is the flight altitude wrong?
A: This is likely a mismatch in RTK, the start location, or how altitude is interpreted. Always reference the same base or dock and use RTK.

Q: Does it work offline?
A: Only for Docks currently. RCs require internet connectivity.

Q: Can I chain multiple recorded flights?
A: Currently, this feature is not available. Plan each battery or mission separately and upload individual KMZ files.

Q: Will support expand for new drones and payloads?
A: Yes. The roadmap includes increased support for new DJI models, payloads, and workflows.

V2.2

Articles in this section

Was this article helpful?
0 out of 0 found this helpful