Rail-corridor BVLOS — Network Rail RTPL, ETSO, evidence pack

Why rail corridors sit in the Specific category by default

The UK Civil Aviation Authority classifies unmanned aircraft operations under the Open, Specific, and Certified categories introduced through the UK-retained version of EU 2019/947. Rail corridors almost always push an operation out of the Open category: the combination of linear BVLOS flight, proximity to third-party infrastructure, and the likelihood of operating over or near people triggers the need for a CAA-issued Operational Authorisation (OA) under the Specific category.

Operators typically pursue one of two routes to that OA: a predefined scenario (PDRA) where one exists and the operation fits within its boundaries, or a full Safety Case submitted under the SORA-derived methodology the CAA applies to bespoke rail missions. The SORA process produces a Ground Risk Class and Air Risk Class that directly inform the liability limit an underwriter will consider adequate — low GRC/ARC combinations attract different terms than high-GRC operations over live track with overhead line equipment (OLE) energised at line voltage.

Brokers should obtain a copy of the issued OA and any attached operating conditions before approaching the market. Underwriters writing rail-corridor BVLOS will treat an OA without attached conditions as an incomplete submission.

Network Rail RTPL — what it means for the insurance submission

Network Rail requires any drone operator working within its managed estate to hold a Rail Track Protection Licence. The RTPL is not an insurance product; it is a contractual and safety-management instrument that sets out the operator's obligations regarding track-access windows, lookout arrangements, line-blockage coordination, and emergency procedures. Underwriters treat the RTPL as a proxy for operational maturity: an operator who has been through the RTPL process has already been assessed against Network Rail's own competency framework.

The evidence pack submitted to insurers should include the current RTPL certificate or letter of authorisation, the associated Method Statement and Risk Assessment (RAMS) accepted by Network Rail, and confirmation of the possession or line-blockage category under which flights will be conducted. Operations conducted under a plain-line possession carry different residual risk profiles than those conducted under a full line blockage, and underwriters will price accordingly.

Where the operator is a subcontractor to a principal contractor holding the RTPL, the submission must clarify the contractual chain, confirm that the subcontractor's operations are within the scope of the principal's RTPL, and identify which entity carries the primary liability exposure. Gaps in that chain are a common cause of coverage disputes after an incident.

• Current RTPL certificate or Network Rail authorisation letter
• Accepted RAMS document referencing the specific drone operation
• Possession or line-blockage category (plain-line, absolute block, PICOP, etc.)
• Contractual chain confirmation where a subcontractor structure applies
• Emergency contact and track-clearance procedure documentation

ETSO compliance and electrification risk

Network Rail's Electrical Technical Standards for Operations govern work in the vicinity of energised OLE and conductor rails. For drone operations, ETSO compliance means the operator has demonstrated that the UAS and its flight envelope will not breach the safe clearance distances from energised equipment, and that the crew has received the appropriate electrical safety briefing and competency sign-off.

From an underwriting perspective, ETSO-compliant operations are materially different from non-electrified-corridor work. The potential for a flyaway or loss-of-link event to result in contact with OLE introduces a catastrophic loss scenario — not just hull loss, but potential disruption to traction power across a wider network section, third-party property damage, and personal injury liability. Underwriters will ask whether the operator's OA explicitly addresses OLE proximity and whether the RAMS has been reviewed by a Network Rail Electrical Control Room (ECR) or equivalent.

Operators who cannot produce ETSO evidence for electrified-corridor work will find the market significantly narrower. Some capacity providers will decline entirely; others will attach exclusions for OLE-related losses or require higher deductibles on autonomous or beyond-visual-line-of-sight segments where pilot intervention is limited.

Building the evidence pack — a broker checklist

A complete evidence pack for a rail-corridor BVLOS submission should be assembled before the first market approach. Underwriters working in this vertical receive incomplete submissions routinely; a well-structured pack moves your client to the front of the queue and signals that the operator runs a professional programme.

The pack should be organised so that the regulatory layer (CAA OA and conditions), the Network Rail layer (RTPL, RAMS, possession category), and the technical layer (UAS specifications, C2 link redundancy, detect-and-avoid capability, data-link frequencies) are each clearly separated. Insurers will also want to see the operator's claims history, crew competency records, and — for BVLOS specifically — the remote pilot station configuration and any detect-and-avoid technology fitted.

Hull values should be stated at replacement cost, not depreciated value, particularly for survey-grade payloads such as LiDAR or thermal imaging systems that are often worth more than the airframe. Liability limits are quoted in GBP and should reflect the contractual minimums in the Network Rail access agreement, which may exceed standard market defaults.

• CAA Operational Authorisation and all attached operating conditions
• SORA output: Ground Risk Class, Air Risk Class, SAIL determination
• Network Rail RTPL certificate and accepted RAMS
• ETSO compliance evidence for electrified corridors
• UAS technical specification: MTOM, C2 redundancy, DAA capability
• Crew competency records and GVC or equivalent qualification evidence
• Claims history (minimum three years where available)
• Hull replacement value including payload systems
• Contractual liability minimum from the Network Rail access agreement

Coverage scope and common policy conditions

A rail-corridor BVLOS programme typically combines hull all-risks cover for the UAS and payload with third-party liability. The liability section should respond to bodily injury and property damage caused to third parties, including Network Rail as a landowner and infrastructure manager — check whether the policy wording treats Network Rail as an insured or as a third party, since some wordings exclude contractual counterparties.

Policies written for this vertical commonly include conditions requiring the operator to maintain the OA in force, to notify the insurer of any material change to the RAMS or possession category, and to comply with all ETSO requirements where electrified infrastructure is involved. Breach of these conditions can void cover, so operators and brokers should ensure the policy schedule accurately reflects the scope of the OA rather than a broader or narrower description.

Grounding clauses — provisions that suspend hull cover when the aircraft is not airworthy or when the OA is suspended — are standard. For fleet programmes covering multiple UAS types operating across different Network Rail regions, the schedule should list each aircraft by serial number and confirm that each is within the scope of the OA.

Placing the risk — market and workflow

Rail-corridor BVLOS is a specialty line that sits outside standard drone market appetite. Brokers should approach Lloyd's syndicates and company-market underwriters with demonstrated UAS rail experience rather than routing through general aviation or commercial combined markets. The underwriting questions will be technical and the turnaround on an incomplete submission will be slow.

Premiums scale with hull value, payload value, BVLOS exposure hours, and the complexity of the OA conditions — operations with a high SAIL determination or with OLE proximity will attract higher rates than straightforward non-electrified inspection work. Deductibles typically rise on autonomous segments and on operations where the remote pilot station is not co-located with the operation.

Once terms are agreed, the policy should be bound before the first operational day on Network Rail infrastructure. Some access agreements require evidence of insurance to be provided to Network Rail's project manager before a possession is granted; confirm this requirement with the operator and ensure the certificate of insurance is worded to satisfy it.

Frequently asked questions

What does a rail-corridor BVLOS policy actually cover?

A correctly structured programme covers hull all-risks for the UAS and its payload (including survey-grade sensors) and third-party liability for bodily injury and property damage arising from the drone operation. The liability section should respond to claims from Network Rail as infrastructure manager as well as from other third parties. Coverage is conditional on the operator maintaining their CAA Operational Authorisation and complying with the RTPL and any ETSO requirements stated in the policy schedule.

Does the operator need a CAA Operational Authorisation before you can quote?

Yes, for any BVLOS operation on or alongside Network Rail infrastructure. Rail corridors fall within the CAA's Specific category under the UK Open/Specific/Certified framework, and an issued OA with attached operating conditions is a minimum underwriting requirement. Operators still in the SORA or PDRA application process can approach the market for indicative terms, but cover cannot be bound until the OA is issued.

What is the RTPL and why do underwriters ask for it?

The Rail Track Protection Licence is a Network Rail instrument that authorises an operator to work within the managed rail estate and sets out the safety-management obligations they must meet. Underwriters treat the RTPL as evidence of operational competency and as confirmation that Network Rail has accepted the operator's RAMS. Without it, the underwriter cannot assess whether the operation has been reviewed against Network Rail's own risk framework, which is a prerequisite for most rail-corridor BVLOS capacity.

How does ETSO compliance affect the terms available?

Operations near energised overhead line equipment or conductor rails introduce a catastrophic loss scenario that narrows available capacity. Underwriters will require evidence that the OA explicitly addresses OLE proximity, that the RAMS has been reviewed by the relevant Electrical Control Room, and that crew have completed the required ETSO safety briefing. Without this evidence, some insurers will decline, and others will attach OLE-related exclusions or require higher deductibles on BVLOS segments.

Can a subcontractor be covered under the principal contractor's RTPL?

Potentially, but the insurance submission must clearly document the contractual chain, confirm that the subcontractor's specific operations fall within the scope of the principal's RTPL, and identify which entity carries the primary liability exposure. Underwriters will not assume coverage extends down a subcontractor chain without explicit confirmation. Where there is any ambiguity, the subcontractor should hold their own liability policy with a cross-liability clause.

What is the broker workflow for placing a rail-corridor BVLOS programme?

Assemble the full evidence pack — CAA OA, SORA outputs, RTPL, accepted RAMS, ETSO compliance evidence, UAS technical specification, crew competency records, claims history, and hull/payload replacement values — before approaching the market. Submit to Lloyd's syndicates or company-market underwriters with specific UAS rail experience. Once indicative terms are received, confirm that the policy wording treats Network Rail correctly (insured or third party), that grounding clauses reflect the OA conditions, and that the certificate of insurance satisfies any Network Rail access-agreement requirements before binding.