BVLOS is where drone economics finally work — one crew, long routes, no windshield — and it's the acronym behind most drone-startup burn rates. The regulation isn't the barrier it was five years ago; the barrier is showing up with an operation designed for approval. Here's the path as flown by teams that got there.
What approval actually consists of
There is no "BVLOS licence". There is an operational authorisation for a specific operation — this aircraft, these routes/areas, these procedures, this crew — whose risk case (usually SORA) happens to include flying beyond sight. Three practical routes:
- STS-02: the pre-packaged BVLOS scenario — sparsely populated area, ≤2 km with airspace observers, C6-marked aircraft, declaration-based. Narrow, but the shortest paper path where it genuinely fits.
- PDRA-based application: EASA's predefined risk assessments for common BVLOS shapes (e.g., rural low-level) — a guided SORA with blanks to fill.
- Full SORA: for operations that don't fit templates — your delivery network, your offshore route. Most flexible, most work.
The technical pillars every BVLOS case stands on
- C2 link you can defend with numbers. Architecture (primary/secondary, dissimilar), coverage evidence along the route, latency and availability statistics from logged flights — the whole BVLOS datalink playbook. "We use LTE" is a sentence; a histogram of 300 route-hours is evidence.
- Lost-link behaviour, designed and demonstrated. Per mission phase, deterministic, matching what your operations manual says — then shown working in flight test, because assessors have learned to ask.
- Containment. The argument that the aircraft stays inside the operational volume even when things fail: geofencing behaviour, flight termination where SAIL demands independence, and honest failure analysis (failsafe engineering).
- Air-risk answer scaled to the airspace. Rural low-level: strategic mitigation, NOTAM discipline, conspicuity (ADS-B in/out considerations), possibly observers. Busier airspace: real detect-and-avoid — a serious engineering program, which is why route choice is DAA strategy for startups. U-space, where deployed, changes this calculus.
- Reliability evidence. Fleet hours, failure tracking, maintenance program — the operational maturity thread that runs through OSOs and, eventually, a LUC.
The staged strategy that keeps working
- Stage 0 — VLOS revenue. Real missions in the Open category or an easy Specific authorisation: builds fleet hours, log discipline, ops manual muscle and cash.
- Stage 1 — EVLOS. Observers extend the range; the paperwork teaches you the authority's expectations at low stakes.
- Stage 2 — BVLOS in a box. One corridor or confined area, chosen for low GRC/ARC (rail, water, industrial land). This authorisation is your template asset.
- Stage 3 — scale by diff. New corridors as amendments/reuses of the approved case; cross-border extension to other member states; operational data compounding into lower assessed risk.
- Stage 4 — LUC. Organisational privileges: self-authorisation within scope. The point where regulatory capability is a moat competitors must spend years replicating.
Timeline and budget honesty
| Item | Realistic figure |
|---|---|
| First rural BVLOS authorisation (application to grant) | 3–9 months with a clean package |
| Evidence flying beforehand | 50–300 flight hours, logged properly |
| Consultant support, first application | €15–60k (buys vocabulary and template, not understanding) |
| Engineering for compliance features | Weeks–months: lost-link logic, containment, logging pipeline |
| Ongoing: ops manual upkeep, occurrence reporting, audits | A part-time role that grows into a job title |
Authorities approve operations they can picture going wrong safely. Every element of your package — route over water, tested link-loss return, parachute evidence, observer procedures — should paint that picture. Startups that treat the NAA as a design-review partner rather than a gate to sneak past consistently report faster, smoother approvals. It's also simply the correct engineering posture: the assessor's questions are your FMEA, free of charge.
Frequently asked questions
Is BVLOS legal in Europe?
Yes — under a Specific-category operational authorisation (SORA-based or via Standard Scenario STS-02) granted by a national aviation authority. Routine BVLOS operations run today across Europe in energy, rail, ports, agriculture and medical logistics.
What are the technical requirements for BVLOS?
No single fixed list — the SORA output defines it — but recurring pillars: a quantified, redundant C2 link, defined and tested lost-link behaviour, containment (geofencing/termination), conspicuity and air-risk mitigation appropriate to the airspace, and evidence of aircraft reliability from structured flight testing.
How long does BVLOS approval take for a startup?
From first application to routine rural BVLOS: commonly 6–18 months including the operational track record building. Teams that stage it — VLOS revenue first, then EVLOS, then confined BVLOS corridors — reach it faster and with a healthier business underneath.
This is independent educational content — not legal, spectrum, conformity-assessment or flight-safety advice. Rules change and differ by country. Verify current requirements with EASA, your national aviation authority, your national spectrum regulator (in Belgium, BIPT) and qualified counsel before you operate or rely on any figure here.