User manual
Missions, checklists and operation orders
The mission is the dossier that holds everything together: weather, zones, crew, checklists, flights, live streaming and deliveries.
Creating a mission
You set a client (optional), the flight window, the location and the sector. The mission gets a progressive code (MSN-0001…) and becomes the container for everything that follows.
Weather with a traffic-light
On the flight window the mission shows a green/yellow/red traffic-light, hour by hour: wind and gusts (at altitude too), rain, visibility, cloud base, sunrise and sunset, Kp index. Where available, the nearest airport's METAR/TAF are added. The weather report can be attached as a PDF to quotes and invoices as proof of the chosen window.
Geographical zones on the map
You upload your country's ED-269 file of UAS zones (in Italy you download it from the d-flight portal with your operator account) and the mission map shows the zones colored by restriction, actually readable. The per-country guide is on the Zones page: the format is the European standard, fourteen countries already mapped.
Crew: PIC, SPIC and certificate blocking
You assign the roles: PIC and SPIC are unique per mission; observers and GCS operators need no certificate. A pilot with a certificate expired on the mission date cannot be assigned to flying roles: the system says so before, not the incident report after.
Checklists in three phases
Checklists come from templates (pre-flight, pre-takeoff/in-flight, post-flight) and include system auto-checks: valid certificates, weather traffic-light, insurance, charged batteries for the mission's drones, remote controller paired and charged, calibrations. A checklist can be signed only when complete, and the signature stays on record. Signing the post-flight triggers the consequences: batteries and devices switch to "to charge", a reported anomaly opens a maintenance job or an incident.
Operation orders (ODO)
Structured organizations protocol their operation orders (ODO, ODO-2026-001…): category, scenario, validity window, prescriptions. Managers authorize with a signature; missions attach to the ODO and every take-off takes its progressive TO number under that protocol. Closing or revoking an ODO stays tracked.
Rapid activation
For rescue work and recurring operations you create mission templates (location, checklist, drone, main live channel, duration): the Rapid activation button generates a ready mission in thirty seconds, and the live stream attaches itself to the dossier.
SORA
The guided SORA 2.0 assessment (iGRC → mitigations → SAIL → OSOs) produces a decision-support PDF to attach to the mission. It does not replace the formal application to the authority: it prepares it.