Highway BVLOS Insurance — National Highways UK

Regulatory Framework: CAA Specific Category and National Highways Permissions

All commercial BVLOS operations in Great Britain fall outside the Open category and require a CAA Specific category authorisation under UK Regulation (EU) 2019/947 as retained in UK law. For highway corridors, that typically means a bespoke Operational Authorisation (OA) rather than a standard scenario (STS), because the combination of BVLOS flight, proximity to moving traffic, and interaction with managed motorway infrastructure places the operation outside any pre-defined STS envelope.

National Highways, as the statutory highways authority for England's motorways and major A-roads, must be engaged separately from the CAA process. Operators are expected to submit a formal request through National Highways' asset protection and network management channels, demonstrating how the UAS operation will interact with — and not compromise — active traffic management systems including VMS gantries, MIDAS loop detectors, and CCTV monitoring infrastructure.

Scotland and Wales have their own trunk road authorities (Transport Scotland and Welsh Government respectively), so operators working across borders need to confirm which authority governs each section of network. Underwriters will ask for copies of all relevant permissions and authority sign-offs before binding cover, because a lapse in any single permission can void the operational basis on which the policy was written.

VMS Interaction: Why It Matters to Underwriters

Variable message signs on smart motorways and all-lane-running sections are not passive infrastructure. They set mandatory speed limits, activate lane closures, and trigger contraflow configurations in real time. A UAS operating in the same corridor — particularly one conducting inspection, survey, or incident-response work — creates a potential conflict between the drone's operational airspace and the dynamic traffic environment that VMS is actively shaping.

Underwriters treat VMS interaction as a material risk factor because a VMS-triggered speed reduction or emergency lane closure can alter the ground risk profile of a flight mid-operation. If a drone is conducting a linear survey at 50 mph corridor speed and VMS drops the limit to 40 mph or closes a lane, the separation distances and ground risk assumptions in the original CONOPS may no longer hold. Operators who have pre-agreed VMS state protocols with National Highways' Regional Control Centres — defining which VMS states permit continued flight and which require an immediate hold or return-to-home — demonstrate a level of operational maturity that underwriters reward with more favourable terms.

Documentation of VMS interaction procedures should be embedded in the Operations Manual submitted to the CAA and shared with the broker at placement. Vague references to 'monitoring traffic conditions' are insufficient; underwriters want to see specific decision gates tied to named VMS states.

• Pre-agreed VMS state thresholds that trigger flight hold or abort
• Named point of contact at the relevant National Highways Regional Control Centre
• Communication protocol (radio channel, direct line, or NTIS data feed) for real-time VMS status
• Contingency procedure if comms with the RCC are lost during flight
• Record-keeping obligations for VMS state log during each sortie

Traffic Management Coordination: The Broker's Checklist

Traffic management coordination for highway BVLOS goes beyond a courtesy notification. National Highways expects operators to integrate with the Traffic Officer Service where lane closures or rolling road blocks are required to create a safe operating window. The cost and logistics of TM support are significant, and underwriters will assess whether the operator has a realistic, costed TM plan or is relying on assumptions that have not been tested with the authority.

For inspection and survey work that can tolerate a planned maintenance window, operators often coordinate with National Highways' planned works programme, slotting BVLOS sorties into existing lane-closure periods. This approach substantially reduces ground risk and is viewed favourably at underwriting because the traffic environment is controlled rather than live. Conversely, incident-response or emergency inspection operations — where the drone is deployed into an unplanned closure — carry a higher dynamic risk profile and require broader policy wording to cover the range of scenarios that may arise.

Brokers placing highway BVLOS programmes should obtain and present the following at submission to avoid mid-quote information requests that delay binding.

• Copy of CAA Operational Authorisation or evidence of OA application stage
• National Highways (or Transport Scotland / Welsh Government) permission or letter of no objection
• CONOPS document including ground risk assessment and VMS interaction protocol
• TM coordination plan — planned works integration or rolling road block specification
• Pilot and remote crew competency evidence (GVC as minimum; additional endorsements where required by OA)
• UAS hull value and payload schedule
• Details of any autonomous or AI-assisted flight modes active during the operation

Hull and Liability Cover: Structuring the Programme

Hull cover for highway BVLOS operations is written on an agreed-value basis, with premiums scaling against hull value, payload value, and the degree of BVLOS exposure — particularly whether operations are conducted over live traffic or within a controlled closure window. Deductibles typically rise where autonomous flight modes reduce direct pilot intervention, reflecting the underwriter's assessment of loss-adjustment complexity if an incident occurs without a pilot actively at the controls.

Third-party liability limits for operations over or adjacent to the strategic road network need to reflect the potential for a single incident to affect multiple vehicles and cause consequential losses well beyond the immediate physical damage. Limits are quoted in GBP, and the appropriate level should be discussed with the broker in the context of the specific corridor, traffic density, and proximity to structures such as bridges, tunnels, and gantries. National Highways' own asset protection requirements may specify a minimum liability figure as a condition of their permission, and the policy must meet or exceed that threshold.

Operators running fleet programmes — multiple aircraft deployed across different highway sections under a single OA or a portfolio of OAs — can structure cover on a fleet basis, but each aircraft's operational envelope and the specific highway sections it covers should be scheduled. Underwriters will want to confirm that the TM coordination and VMS protocols documented in the CONOPS apply consistently across the fleet, not just to a lead aircraft.

Common Gaps That Delay or Decline Placements

The most frequent reason a highway BVLOS submission stalls at underwriting is an incomplete or inconsistent CONOPS. Specifically, underwriters flag operations where the ground risk assessment references a generic populated-area model rather than one calibrated to motorway traffic density, vehicle speeds, and the specific geometry of the corridor being flown. A CONOPS written for a rural BVLOS pipeline survey will not transfer to an all-lane-running motorway without significant revision.

A second common gap is the absence of confirmed TM coordination. An operator who states that they 'intend to liaise with National Highways' but cannot produce a confirmed contact or protocol is presenting an unresolved material risk. Underwriters may offer terms conditional on TM confirmation being provided before first flight, but this creates a gap in cover during the period between binding and confirmation — a gap that brokers should flag explicitly to their clients.

Finally, operators who have modified their UAS — particularly those who have integrated third-party detect-and-avoid (DAA) or command-and-control (C2) link equipment — need to confirm that the modification has been assessed within the OA and that the hull insurer has been notified. Unapproved modifications can affect both airworthiness and the validity of the OA, and an insurer who discovers a material modification post-loss will investigate whether it contributed to the incident.

Frequently asked questions

What regulatory authorisation is required before highway BVLOS insurance can be bound?

A CAA Specific category Operational Authorisation is the minimum regulatory requirement for BVLOS flight over the National Highways network in Great Britain. Standard scenarios (STS-01, STS-02) do not cover BVLOS over live traffic environments. In addition, a separate permission or letter of no objection from National Highways (or the relevant trunk road authority in Scotland or Wales) is required. Underwriters will not bind cover without evidence that both the CAA OA and the highways authority permission are in place or formally in progress.

Does a standard commercial drone liability policy cover highway BVLOS operations?

No. Standard Open category or generic commercial drone policies are written for VLOS operations and typically exclude BVLOS flight, operations over or adjacent to live traffic, and any activity requiring a Specific category OA. Highway BVLOS requires a bespoke Specific category programme with policy wording that reflects the OA conditions, the TM coordination protocols, and the VMS interaction procedures documented in the operator's CONOPS. Brokers should confirm exclusion wording in any existing policy before assuming cover extends to highway BVLOS work.

How does VMS interaction affect the scope of cover?

VMS interaction is a material risk factor that underwriters assess at placement. If an operator has pre-agreed VMS state protocols with National Highways' Regional Control Centre — defining which VMS states permit continued flight and which require a hold or abort — this is treated as a positive operational control and reflected in the terms offered. Operations without documented VMS protocols present a higher dynamic risk profile. Any incident that occurs when the operator was flying in a VMS state that their own CONOPS required them to abort will be subject to close scrutiny during claims investigation.

What is the broker workflow for placing a highway BVLOS programme?

Brokers should compile a full submission pack before approaching underwriters. This includes the CAA OA (or application stage evidence), the National Highways permission or letter of no objection, the full CONOPS with ground risk assessment and VMS interaction protocol, the TM coordination plan, pilot and crew competency evidence, a hull and payload schedule, and details of any autonomous or AI-assisted flight modes. Submissions with complete documentation are assessed within the same week. Incomplete submissions are returned for further information, which is the primary cause of placement delays in this vertical.

Are there eligibility requirements related to pilot competency for highway BVLOS cover?

Yes. The CAA's Specific category OA will specify the minimum competency requirements for the remote pilot and any remote crew. The General Visual Line of Sight Certificate (GVC) is typically the baseline, but highway BVLOS operations frequently require additional endorsements or evidence of type-specific training, particularly where the UAS exceeds certain mass thresholds or where autonomous modes are active. Underwriters will review competency evidence as part of the submission and may apply conditions or exclusions where the crew's documented experience does not align with the complexity of the operation.

What happens to cover if National Highways withdraws or suspends its permission mid-programme?

If the highways authority permission is withdrawn or suspended, the operational basis on which the policy was written no longer holds, and the operator must notify the broker immediately. Continuing to fly without a valid highways authority permission would likely constitute a breach of a policy condition and could affect the validity of any subsequent claim. Brokers should ensure that the policy wording includes a notification obligation tied to any change in the status of regulatory permissions, and operators should build a permission-review process into their programme management.