Your team sees what the drone sees, where it's looking, and what it's measuring — inside the same map everyone's already using. No separate app. No extra screen. Just the drone, on the map, with the rest of the team.
Register your drone in FieldOps, connect through DJI Pilot 2, and the bridge handles the rest. Your drone's position, camera aim-point, and health data flow to the shared map in real time. Every responder on the team sees it — not just the pilot.
Live aircraft location visible to every team member on the shared map. See where the drone is, in real time, alongside ground team pins.
Continuous stream of the ground point the LRF is targeting, rendered as a distinct marker. The whole team sees where the camera is pointing.
Three-tier model picker in-app. MQTT credentials provisioned server-side. Account-isolated — your drones are only visible to your team.
Battery, altitude, heading, speed, gimbal angle, remaining flight time — all flowing to the team map.
Registered drones visible to your whole team. Incident command sees who's flying what before the drone leaves the ground.
Live drone video on the shared team map via MapNova — the whole team watches the drone's feed alongside ground pins. Part of the Drone Package.
Drone warnings and errors written to the team's alert feed so everyone knows when something needs attention, not just the pilot. The feed is built; the database rule that lets the team read it is the last step.
Pins dropped in Pilot 2 sync to FieldOps and vice versa. Two-way coordination between the controller and the ground team.
Tap a location on the FieldOps map and the drone autonomously flies there. Ground teams direct the drone without touching the controller.
Visual breadcrumb history of where the drone has been, with trailing fade. See coverage at a glance.
Drone camera feed built directly into FieldOps — no third-party service required. Watch the drone's live video inside the app alongside the shared map. This is separate from the live drone-video stream via MapNova, which is available today.
Pre-planned flight paths pushed to the drone from FieldOps. Plan the mission on the map, send it to the pilot.
DJI's manned-aircraft proximity warning surfaced to the whole team, not just the pilot's controller.
FieldOps connects to DJI Enterprise drones via the DJI Cloud API and DJI Pilot 2. Consumer drones (Mavic, Mini, Air, Avata) use DJI Fly and are not supported.
| Aircraft | Controller | Status |
|---|---|---|
| Matrice 4E / 4T | RC Plus + Pilot 2 | ✓ Verified |
| Matrice 30 / 30T | RC Plus + Pilot 2 | Expected |
| Matrice 300 RTK | RC Plus + Pilot 2 | Expected |
| Matrice 350 RTK | RC Plus + Pilot 2 | Expected |
| Mavic 3 Enterprise (M3E / M3T) | RC Pro + Pilot 2 | Expected |
| Consumer drones (Mavic, Mini, Air, Avata) | DJI Fly | Not Supported |
Tools like DroneSense, FlightHub, and AirHub are built for drone program management — fleet logging, certification tracking, DFR workflows. FieldOps is different. It's an incident operations platform that integrates drone telemetry into the shared map your whole team is already using. The drone is one feed contributing to shared situational awareness — not the product itself.
Drone tracking is the Drone Package on the Command tier. Get set up and connect your first drone in minutes.
Get Started