Prove where the drone route stays visible and where terrain breaks it.
SighThor gives drone operators a terrain-aware VLOS and BVLOS planning workflow with multi-observer route analysis and export-ready evidence.
Outputs
PDF, KML, KMZ, CSV
Context
VLOS and BVLOS planning
Audience
Commercial operators and consultants
Drone LOS
Green where the route is visible, red where terrain breaks it
Place pilot and relay observers, analyse multi-segment routes, and export map-backed evidence that shows exactly where the gaps are.
Coverage
96% clear
Blocked segments
1 gap
Max gap
340 m
Export
PDF + KML
Pain Points
Why route visibility analysis is still too manual
Operators often have terrain data, but not a workflow that turns it into route-specific observer evidence.
Feature Deep Dive
What the drone workflow is built to answer
The goal is to make visibility assumptions inspectable before people and equipment are deployed.
Terrain-aware route visibility
The route is segmented by what the observer network can actually see, not by guesswork or line drawings on a flat map.
Multiple observers
Place pilot and relay observers to close gaps and compare route coverage before field deployment.
Blocked segment review
Identify exactly where the route breaks and use that insight to move observers or change operating assumptions.
Evidence exports
Export map-backed PDF, KML, KMZ, CSV, and GeoJSON outputs for mission packs, waiver material, or internal review.
Operational framing
The workflow is oriented around VLOS and BVLOS justification, not generic recreational route planning.
Workflow
Route analysis in four stages
Build the geometry, test the assumptions, refine the observer plan, and export the evidence.
- 01
Create a drone project, navigate to the operating area, and add the route waypoints.
- 02
Place the pilot or ground observers where you expect to maintain visibility.
- 03
Run LOS analysis at the planned altitude and inspect clear versus blocked segments.
- 04
Adjust the observer network or route, then export the evidence package for review.
Regulatory Context
Designed to support evidence-heavy operational review
SighThor is not legal advice, but it is built to produce the route visibility artefacts that teams repeatedly need when documenting higher-friction operations.
FAA Part 107 / future waiver workflows
Use the exported evidence to support visibility reasoning and mission planning conversations for operations in the United States.
UK-SORA and UK CAA operations
The workflow maps cleanly onto UK-style evidence needs where visibility and terrain context must be documented.
EASA SORA-aligned operations
SighThor provides the line-of-sight analysis artefacts that commonly support SORA-style operational planning in Europe.
JARUS-oriented global teams
For operators working across multiple jurisdictions, the route evidence stays consistent even when the paperwork changes.
Comparison
A planning workflow built for route visibility, not just flight admin
SighThor sits in the gap between generic route planners and costly bespoke field surveys.
| Capability | SighThor | Typical alternative |
|---|---|---|
| Terrain-aware observer LOS | Yes. Route coverage is segmented by terrain visibility. | Common flight planning tools usually do not provide this. |
| Multiple observer modelling | Yes. Pilot and relays can be placed and compared. | Often unsupported or manual. |
| Operational evidence exports | PDF, KML, KMZ, CSV, GeoJSON, PNG. | Usually screenshots plus manual notes. |
| Regulatory context | Built around VLOS/BVLOS evidence needs. | Built around flight logging or route management. |
| Consultancy replacement potential | Early viability checks happen in-house before field spend. | External survey or manual review often required. |
Deliverables
Export the route analysis in the formats operations teams already use
The output is structured for mission review, regulator-facing evidence, or customer communication.
Mission review ready
Use it for viability checks, observer placement studies, and waiver support packs.
The export set is intended to reduce the amount of manual map reconstruction and commentary that usually happens after the route is analysed.
Drone Planning CTA
Analyse the route before you spend the field day.
Use SighThor to test observer layouts, expose terrain-driven gaps, and produce the map-backed outputs your team can actually review.