Flying a drone along a hundred kilometres of pipeline, or out to an offshore platform, means flying it where the pilot cannot see it. That single step, beyond visual line of sight, is where casual drone work ends and a formal safety case begins. Here is what regulators, including Malaysia’s, actually require.
The Line That Changes Everything
Most commercial drone work happens within visual line of sight, VLOS, where the remote pilot keeps the aircraft in view with the naked eye, no binoculars, no camera feed. That rule is simple and safe, and it caps the useful flight radius at roughly 500 metres. For a great deal of survey work that is fine. For the two jobs that matter most in energy infrastructure, inspecting a long pipeline and reaching an offshore asset, it is a hard ceiling. You cannot keep a drone in sight over a hundred kilometres of right-of-way or several miles out to sea.
Beyond visual line of sight, BVLOS, removes that ceiling and unlocks the operations with real commercial scale: continuous pipeline patrol, powerline and infrastructure survey, and offshore inspection flown from a safe location. But crossing that line moves the operation into a different regulatory world. BVLOS is not a bigger version of VLOS with a longer leash. It is a category that requires you to prove, in advance and in detail, that you can manage the risks created by losing direct sight of the aircraft.
The Safety Case, Not the Licence
The most important thing to understand about BVLOS is that it is authorised on the strength of a demonstrated safety case, not simply a licence or a registration. A pilot certificate lets you fly. A BVLOS approval requires a substantive, written analysis of a specific operation: the risks it creates, the mitigations you will apply, and evidence that those mitigations are robust enough to meet the required safety threshold. The authorisation attaches to the operation, not just the operator.
BVLOS approval is not a bigger licence. It is a demonstrated argument that this specific flight, over this specific ground, is safe, backed by evidence a regulator will test.
The structured method behind that argument is the Specific Operations Risk Assessment, the SORA, developed by the international rulemaking body JARUS and adopted by a growing list of authorities. A SORA analyses a proposed operation from two directions at once, and both have to be answered convincingly before an approval is granted.
Ground risk: What happens if the aircraft comes down uncontrolled. Mitigated by routing over unpopulated areas, geo-fencing the corridor, and measures such as a recovery parachute to limit harm on the ground.
Air risk: The chance of conflict with crewed aviation or other airspace users, from helicopters to light aircraft to other drones. Mitigated by airspace choice, coordination, and detect-and-avoid capability.
The output: Assurance and integrity levels that set how robust the mitigations and the operation must be, driving specific safety objectives the operator has to meet.
The principle: The assessment must be specific to the mission. A pipeline survey, an offshore inspection, and an urban flight create very different hazards and cannot share a generic template.
What the Aircraft and Crew Must Prove
A SORA is only credible if the hardware and the team can actually deliver the mitigations it claims. Two technical capabilities sit at the centre of almost every BVLOS case. The first is detect-and-avoid: since the pilot cannot see the aircraft, something else has to sense other airspace users and keep the drone clear of them. The second is a reliable command-and-control link, because an approval rests on being able to show that the control signal will not simply drop out mid-mission, and that there is a defined, safe response if it does.
Around those sit the rest of the case: contingency and emergency procedures for lost link or failure, competent remote crew trained for the specific operation, and a platform reliable enough to be trusted out of sight. This is where genuine drone training and operational discipline become part of the regulatory argument rather than an afterthought. A regulator granting BVLOS is, in effect, accepting that this operator and this aircraft can be trusted to manage an aircraft-level risk without a person watching it fly.
How It Works in Malaysia
Malaysia is a useful concrete example, because its approach mirrors the global pattern and is directly relevant to regional energy infrastructure work. The Civil Aviation Authority of Malaysia, CAAM, treats a drone as posing the same category of risk as a crewed aircraft, and uses the JARUS SORA framework, with its ground and air risk assessment, to decide BVLOS applications. Standard VLOS rules cap operations at roughly 500 metres, and BVLOS is the exception that has to be justified through that risk assessment.
In practice, pipeline, powerline, and railway monitoring are among the most accessible BVLOS pathways in Malaysia today, precisely because the route is fixed and predictable, can be pre-surveyed, and lets conflicts be assessed in advance. A documented early approval for pipeline inspection mitigated ground risk by planning flights over unpopulated areas and geo-fencing the pipeline corridors, and added a recovery parachute as a further ground-risk measure. The process ran through a pre-application meeting and draft risk assessment, a formal application, document and risk-mitigation review, and a capabilities demonstration as the final step, taking several months from start to approval. CAAM has been working with selected operators through sandboxed BVLOS trials while the wider commercial framework and an unmanned traffic management system develop.
The predictable, pre-surveyed corridor of a pipeline is the easiest BVLOS case to make. Fixed route, known conflicts, unpopulated ground: exactly what a regulator can be shown and satisfied about in advance.
Planning Around the Timeline
The single most common commercial mistake is treating BVLOS approval as a formality that can be arranged at short notice. It cannot. A credible application involves engaging the regulator early, drafting a genuine operation-specific risk assessment, choosing and justifying an airspace pathway, specifying the detect-and-avoid and control-link capabilities, and, in many cases, demonstrating the whole thing before approval is granted. Realistically that is a matter of months, not days, and rushing it produces a weak case that gets sent back.
For an operator planning pipeline or offshore inspection campaigns, the implication is straightforward: the approval is part of the project timeline, not an administrative afterthought. Build the safety case early, invest in the detect-and-avoid and control-link capability the case depends on, train the crew for the specific operation, and engage the regulator before the schedule hardens. The operators who treat BVLOS authorisation as an engineering and planning task, done properly and ahead of time, are the ones flying the long linear and offshore missions while others are still waiting on a rushed application.
Frequently Asked Questions
What does BVLOS mean and why does it need special approval?
BVLOS stands for Beyond Visual Line of Sight, meaning the remote pilot can no longer see the drone with the naked eye, whether because of distance or obstacles. It needs special approval because losing direct sight of the aircraft creates additional risk, so the operator must demonstrate, through a formal safety case, that they can manage the hazards of conflict with other aircraft and of the drone coming down uncontrolled.
What is a SORA?
A SORA, Specific Operations Risk Assessment, is the structured methodology, developed by JARUS and adopted by authorities including Malaysia’s CAAM, used to assess and approve BVLOS operations. It analyses a proposed operation from two directions, ground risk (the consequence if the aircraft comes down) and air risk (conflict with other airspace users), and produces assurance levels that set how robust the mitigations must be. It must be specific to the actual mission.
Why are pipelines a good early BVLOS use case?
Pipeline, powerline, and railway routes are fixed and predictable, which means the corridor can be pre-surveyed, ground risk managed by routing over unpopulated areas and geo-fencing, and airspace conflicts assessed in advance. Because the regulator can be shown a well-defined, controlled operation, these linear-infrastructure missions are among the most accessible BVLOS approvals, and were among the first granted in Malaysia.
How long does BVLOS approval take?
Realistically, months rather than days. A credible application involves early engagement with the regulator, an operation-specific risk assessment, justification of the airspace pathway, specification of detect-and-avoid and control-link capabilities, and often a capabilities demonstration before approval. A documented Malaysian pipeline approval ran through several such stages over several months, so the authorisation should be planned as part of the project timeline.
Sources: Civil Aviation Authority of Malaysia (CAAM), BVLOS approval framework and use of JARUS SORA; Civil Aviation Act 1969 · JARUS, Specific Operations Risk Assessment (SORA) methodology (ground and air risk, assurance and integrity levels) · Documented CAAM BVLOS pipeline approval and process (DroneLife) · CAAM BVLOS pathways and VLOS radius in Malaysia
Continue reading
-
malaysia ASEAN Crew Mobilisation: What Malaysia Actually Requires
-
drones Methane Monitoring by Drone: What Buyers Now Expect
-
offshore The Welder Qualification Test, and Why Yards Fail It
-
drones Drone Inspection: Flare Stacks and Confined Spaces
-
drones Drone Surveys: When Class Accepts One Instead of Staging