Skip to content
Documentation

Platform documentation

How RPAS WILCO works under the hood: data sources, site surveys, logs, roles, geometry and weather.

Platform Overview

Architecture and core modules of the RPAS WILCO platform.

  1. RPAS WILCO is built around four core modules: Flight Planning, Airspace Intelligence, Fleet Management, and Compliance Automation.

  2. Flight Planning handles site surveys, mission scheduling, and pre-flight checklists with automatic NOTAM and METAR integration.

  3. Airspace Intelligence provides real-time Canadian airspace data sourced from NAV CANADA, including controlled zones, restricted areas, and temporary flight restrictions.

  4. Fleet Management tracks drones, pilots, visual observers, and payload operators across your organization.

  5. Compliance Automation generates CARs 901.27-compliant site surveys, flight logs, and incident reports.

Airspace Data Sources

How RPAS WILCO ingests and displays Canadian airspace data.

  1. Airspace boundaries, controlled zones, and restricted areas are sourced from NAV CANADA's Designated Airspace Handbook (DAH).

  2. NOTAMs (Notices to Airmen) are ingested in real time and overlaid on the interactive map, alerting pilots to temporary restrictions or hazards.

  3. METARs and TAFs provide current and forecasted weather conditions at aerodromes, displayed alongside mission planning tools.

  4. CFS (Canada Flight Supplement) charts for aerodromes are available to Pro, Business and Enterprise subscribers.

Site Survey Specification

What a generated site survey contains and how it meets CARs 901.27.

  1. Each site survey PDF includes: mission parameters (pilot, drone, observers), operation area map with markers, airspace classification, active NOTAMs, weather data (METAR/TAF), and a risk assessment.

  2. The map snapshot captures the operation radius, team positions, and any obstacle markers placed during planning.

  3. Surveys automatically pull airspace data for the selected location, including proximity to aerodromes and controlled zones.

  4. All generated surveys are stored in your mission history and can be exported as PDF for regulatory or insurance purposes.

Checklist System

Pre-flight, in-flight, and post-flight checklist architecture.

  1. The default checklist covers pre-flight (drone inspection, battery, propellers, firmware), in-flight (airspace monitoring, communication), and post-flight (landing, power-off, log) phases.

  2. Pro, Business and Enterprise users can design custom checklists via the web dashboard, adding, removing, or reordering sections to match their SOPs.

  3. Checklist timestamps are recorded automatically — "Power on Drone" starts the flight timer, "Power Off Drone" stops it and logs the duration.

  4. Completed checklists are attached to the mission record and can be reviewed alongside site surveys and flight logs.

Flight Log System

Automatic and manual flight logging.

  1. Automatic flight logs are generated when using the checklist — flight time is tracked from drone power-on to power-off.

  2. Manual flight logs can be created for flights conducted outside of RPAS WILCO, preserving a complete pilot logbook.

  3. All flight logs record: date, duration, pilot, drone, and associated mission. Business and Enterprise accounts also log the client and project.

  4. Flight hours are aggregated per pilot and per drone, accessible from the dashboard for reporting and compliance.

User Roles & Permissions

Account roles, team structure, and access levels.

  1. Account Owner — full access to all settings, billing, team management, and missions.

  2. Pilot — can create and conduct missions, complete checklists, and log flights. Starter and Pro accounts support one pilot; Business and Enterprise support multiple.

  3. Visual Observer (VO) — assigned to missions as a crew member. Cannot create missions independently.

  4. Payload Operator (PO) — assigned to missions involving specialized payloads. Cannot create missions independently.

  5. Enterprise Super User — has administrative access across the organization, including team-wide mission creation and reporting.

Geometry: Shapes, Buffers and Import Limits

Reference for geometry types, the path corridor buffer, sync behaviour and file import.

  1. A geometry is a saved map shape held in a per-user library and importable into any mission. Availability is currently open to all account tiers, including free.

  2. Two geometry types exist. A Polygon is a closed area defined by its vertices. A Path is a linear route stored as a centreline.

  3. Paths render an automatic corridor buffer of 40 m around the centreline. The buffer is generated on draw and is not currently configurable.

  4. Geometries can be drawn against contextual map layers: VNC and VTA charts, airspace below and above 700 ft AGL, aerodromes, active wildfires, wildfire hotspots over 24 hours, NOTAMs, population density and national parks.

  5. Vertices placed on a chart layer store the charted coordinates directly, so a traced airspace boundary reproduces that boundary without re-projection.

  6. File import accepts KML and GeoJSON. Imported shapes land in the library as Polygons. Only the first geometry in a multi-shape file is read.

  7. Sync is one-way. Shapes created on web appear on mobile automatically; create, edit and delete operations are web-only, and the mobile library is read-only.

  8. Editing an existing shape is not yet supported on either platform. To change a geometry, delete it and redraw.

  9. Sharing is per-user. A geometry is visible only to the account that created it; organisation-level sharing is not currently available.

Weather Data: Sources, Thresholds and Refresh

Reference for the forecast window, wind safety bands, Kp thresholds and the precipitation logic.

  1. Forecast data comes from Open-Meteo with a 16-day window. Longer horizons are not available.

  2. Cache TTL is one day. A background job refreshes actively-queried grids on a rolling window, so frequently-checked locations stay minutes-fresh.

  3. All values are location-specific to the map centre except geomagnetic Kp, which is a planetary index and identical everywhere.

  4. Wind is reported at four altitudes — 180 m, 120 m, 80 m and 10 m — and colour-tinted by safety band: green under 7 m/s, amber around 11 m/s as a soft limit, red at 14 m/s and above.

  5. Wind is expressed in m/s to match the SI and ICAO / MET conventions used in aerodrome briefings and in Transport Canada thresholds.

  6. The Aviation card reads METAR from the nearest aerodrome within 30 km and derives the standard VFR / MVFR / IFR / LIFR flight category. Beyond 30 km the card is hidden.

  7. Geomagnetic Kp is shown for the current period plus a 3-day forecast at 8-hour cadence. Bands are 0-3 quiet, 4 unsettled, 5 and above storm.

  8. Thunderstorm indication combines CAPE, which describes atmospheric potential, with the forecast weather code, which describes expectation. The lightning icon is suppressed unless low or mid cloud cover reaches 80 percent.

  9. The precipitation indicator triggers on any precipitation category, including light drizzle at 0.5 mm/hour, because rotor water loading, unsealed airframes, gimbal fogging and propeller icing near 0 degrees C all present risk well below the threshold a person would notice.

  10. Cloud cover is reported as HIGH, MID and LOW, ordered most-to-least visible from the ground. A thin LOW layer alongside a precipitation forecast often indicates virga, where the drop evaporates before reaching the surface.

Need more detail on an integration or a workflow? Our team can help.