The line between a demo and a business
Almost every commercially meaningful drone application — package delivery, pipeline patrol, crop monitoring, power line inspection, long linear infrastructure survey — requires flying where the operator cannot see the aircraft. As long as someone must keep eyes on it, you need a person every couple of miles, and the economics never close. Beyond visual line of sight (BVLOS) is the line that separates a demonstration from a product, and it is also where the engineering requirements jump a full level.
Where US rules stand
Routine small-drone commercial flight in the US runs under 14 CFR Part 107, which explicitly requires the remote pilot to maintain visual line of sight with the aircraft. BVLOS therefore requires a waiver of that requirement, applied for through the FAA's online portal with a safety case attached. Separate paths exist for heavier aircraft and for operations that do not fit the small-drone rule at all — exemptions under the statutory authority for public aircraft and special authorizations, and ultimately aircraft type certification for scaled delivery operations. A dedicated rule intended to make BVLOS routine has been working its way through rulemaking, which means the specifics will keep moving; treat any list of requirements as a snapshot and verify current guidance before you file.
Two things are true regardless of the path. Remote identification broadcast requirements apply to the aircraft as a manufacturing matter, not just an operational one — see FAA Remote ID for drones. And the FAA does not approve “a drone.” It approves a system: the aircraft, the operator, the written procedures, the training, and the specific area and mission type.
What changes when the operator cannot see the aircraft
When the pilot has eyes on the aircraft, that person is a safety system. They spot approaching manned traffic, notice the aircraft drifting, and recognize when something is wrong before instruments would. The moment visual contact is gone, every one of those functions has to be performed by the system. Everything the FAA asks for follows from that shift.
Six capabilities the aircraft and ground system need
- Continuous, redundant command-and-control link. Typically cellular or satellite, with a defined behavior on loss of link and a backup path. Link budget, latency, and coverage mapping along the intended route are all part of the safety case.
- Traffic awareness and detect-and-avoid. Receiving position broadcasts from cooperative manned aircraft, and in many cases ground-based or onboard sensing for non-cooperative traffic. Whether your aircraft should also broadcast its own position depends on the airspace and the approval path — verify before designing it in.
- Redundancy in flight-critical systems. Dual position sensors, dual power feeds, sometimes rotor configurations that keep the aircraft controllable after a motor failure. Which redundancy is required scales with what is under the route.
- Trustworthy navigation. The ability to detect that satellite navigation has degraded, been jammed, or been spoofed, and to fail over to an alternate method or a defined safe behavior — not to keep flying confidently on bad data.
- Damage mitigation. Ballistic parachutes, flight-termination systems, and route geometry that keeps the aircraft away from people. This is where a lighter aircraft becomes a regulatory advantage, not just an engineering one.
- Monitoring and supervision tooling. A ground control station that lets one operator supervise the mission — and, in scaled operations, multiple aircraft — with clear alerting and the ability to intervene. See drone development cost for how much of a program budget the ground segment absorbs.
The risk assessment is the central document
Your application succeeds or fails on the safety case. It has to show what could go wrong, how likely it is, and what mitigations reduce the residual risk to an acceptable level — the same structured hazard analysis used in any safety-critical development program. Two parameters dominate the outcome:
- Population density beneath the route. Sparse rural corridors, industrial sites, and controlled areas are approved far more readily than routes over neighborhoods.
- Kinetic energy of the aircraft. Mass and speed determine what happens if it comes down uncommanded.
The practical consequence: reducing aircraft weight is often a regulatory decision, not merely a performance one. That reframes the propulsion and structure tradeoffs entirely — see how to choose drone motors and propellers, where efficiency and mass are the same conversation.
A common shortcut to a first approval is a constrained operation: shielded flight close to a structure you are inspecting, a fixed corridor over your own property, or operations in a defined area with ground observers positioned as mitigation. These get you flying and, more importantly, build the operational record that supports a broader request later.
Airspace management
As the number of aircraft grows, someone has to coordinate them with each other and with manned aviation: filing intent, receiving dynamic authorization, and knowing in real time who is where. For a founder this is an interesting business entry point in its own right — software rather than hardware — and it connects directly to the cloud architecture of a connected fleet. Platform considerations are in AWS IoT vs Azure IoT.
What the approval path costs you in schedule
The regulatory track is usually the critical path of a BVLOS program, not the engineering. Documentation, operator training records, maintenance procedures, insurance, and the iterative back-and-forth on the safety case take real calendar time, and the answer is rarely a simple yes or no on the first submission. Start the process while the aircraft is still in design, and design the aircraft around what the safety case will need to claim — retrofitting redundancy is expensive. Environmental sealing and reliability evidence matter here too; see IP ratings explained for the ingress claims you will have to substantiate, and FCC certification for electronic products for the radio side of the aircraft.
What it unlocks
Clearing this hurdle opens missions that are otherwise impossible: a daily autonomous patrol launched from a docking station with nobody on site, infrastructure inspection along tens of miles of corridor in a single sortie, and rapid response where a vehicle cannot reach. That is why so much of the industry's engineering effort is concentrated precisely here.
This article is general engineering guidance, not legal or regulatory advice. Projects House is an engineering firm; confirm current FAA requirements and your specific obligations with qualified counsel or an aviation regulatory specialist.
Design the aircraft around the approval
Projects House develops unmanned aircraft and their ground systems, and we design with the safety case in view from the start — redundancy, link architecture, weight budget, and termination behavior. If you are planning an operation that only works beyond visual line of sight, describe it through our contact form and we will map the engineering and documentation path. More background is in our drone development section.