Tell it what you want to shoot.
It plans a legal flight.
The agent reads the live forecast and every controlled-airspace distance from your take-off point, then picks a window, states a verdict and writes the pre-flight checklist. Part of the Edge Tracker pipeline — the same flight it plans is the flight whose telemetry becomes data.
Ask the agent
Every number the agent is given — wind, gust, visibility, rain risk, distance to each aerodrome — is computed before the model is called. It chooses and explains; it never invents a figure. This is a planning aid, not an authority. Nothing here replaces Drone Assist, a NOTAM check or the Air Navigation Order on the day.
How it decides
- Compute
Forecast hours, gust peaks, visibility and the great-circle distance to every nearby aerodrome and restriction zone are calculated in code. Facts first, always.
- Choose
The model is handed those facts and the limits that bind this operator, and picks the window that fits. An agent that invented a restriction zone would be a safety defect, so it is never asked to supply one.
- Explain
Verdict, reasoning, the risks specific to that sortie, coaching notes and a checklist marked for the items that are law rather than good practice.
- Fly, then measure
After the flight the SRT telemetry comes back in and is scored for smoothness, turn economy and height compliance — so the plan and the outcome sit in one record.