Post-Flight & Reports

The post-flight workflow is short. Telemetry uploads automatically. Your job is to verify the numbers look right, generate the PDF the farmer or agronomist expects, and flag anything that needs follow-up.

1. Wait for telemetry to upload#

Telemetry is uploaded by the controller after the drone lands. Depending on cellular connectivity in the field, the upload can take from a few seconds to a few minutes.

If, fifteen minutes after landing, you don't see the flight on the Flight Log tab, see Drone offline.

2. Open the Flight Log#

From My Drones → [your drone] → Flight Log:

• Pick a date range with the Start date / End date filters.
• The range can't exceed 92 days (≈ 3 months). For longer reports, generate them in monthly batches.
• Each row shows the flight date, the plot / field plan, the flight time, and the status (Completed / In progress).

Click a row to see the per-flight detail page, including the GPS route on a map.

3. Select flights and generate a report#

1. Check the box next to one or more rows in the Flight Log.
2. Click Generate report.
3. Pick the area unit:
   • Hectares (metric) — area in hectares, application rate in L/ha (spraying) or kg/ha (seeding), swath in meters.
   • Acres (imperial) — area in acres, application rate in gal/ac (spraying) or lb/ac (seeding), swath in feet.
4. The portal renders the PDF on the fly. Click Download report when it's ready.

4. What's in the report#

Each report contains:

• Cover: drone serial, issue date, and the operator's name.
• Flight summary: per-flight start/end times and status.
• Per-flight stats:
  • Flight time
  • Speed (avg / max)
  • Altitude (avg / max)
  • Battery consumed
  • Applied area
  • Applied volume (spraying) or applied seeding (seeding)
  • Efficiency (gal/ac, L/ha, lb/ac, or kg/ha depending on unit + mission type)
  • Swath width
• Flight route map: GPS track per flight with start/end markers.
• Overall KPIs: totals across all selected flights — total area, total volume, average application rate.

5. Reconciling against the prescription plan#

If the flight was driven by a prescription map, compare:

From the report	From the plan
Applied area	Total area of the plot (Map Prescription → Product Estimate)
Applied volume	Required product (Product Estimate)
Efficiency	Avg. rate in the prescription

Small differences (≤ 5%) are normal — they come from overlap on swath edges and from buffer zones around exclusion areas. Larger differences usually indicate either:

• A boundary or exclusion zone was changed after the plan was published.
• The drone aborted a sub-section due to a low-battery RTL.
• The wrong shapefile was loaded onto the controller.

Open the per-flight detail page to see exactly which sub-sections were covered.

6. Common follow-ups#

• Missing flights: see Drone offline.
• Wrong area unit: regenerate the report with the other unit — there's no upload limit.
• Customer wants the raw track: use the per-flight detail page; an export to KML / GeoJSON is on the roadmap.
• Issue noticed during the flight: open a support ticket linked to the drone. See File a Support Ticket.

Next#

• Maintenance & readiness — keep status badges green between missions.
• Flight Records & Reports — the full feature reference for the Flight Log + PDF export.