In February 2017, Unmanned Systems and Solutions demonstrated the technology that would become the foundation of our tethered UAS operations in Ball Ground, Georgia. At the time, tethered drones were still unfamiliar to many of the organizations evaluating unmanned aircraft, and much of the conversation naturally centered on what the technology could do. Could an aircraft remain continuously powered from the ground? How much weight could it carry? How high could it operate? Could a tether reliably carry power and data while the aircraft remained airborne for extended periods?
Nine years later, we still care about those questions, but experience has taught us that they are only the beginning of evaluating a tethered UAS.
Since that first demonstration, our systems have been deployed across a wide range of environments and applications. They have supported communications following major hurricanes, operations along the U.S. border, military exercises, major sporting events, telecommunications testing, ISR applications, 5G testing, microwave communications and other field operations. That history includes deployments associated with Hurricanes Maria, Florence, Michael, Ian, Beryl, Helene and Milton, as well as the Maui wildfires, U.S. Air Force and U.S. Army exercises and multiple Department of Homeland Security and Customs and Border Protection operations.
Repeated field experience changes the way you evaluate a system. Specifications remain important, but eventually you stop looking only at whether an aircraft can carry a payload to a certain altitude for a certain amount of time. You begin looking at everything that has to continue working after it gets there.
Flight Time Is Only Valuable When the Payload Remains Useful
One of the biggest changes in our thinking has been how we define endurance. Drone manufacturers understandably talk about flight time because it provides a simple number for comparing aircraft. In the field, however, the amount of time an aircraft can remain airborne is only useful if the capability it carries can remain operational for the same period.
Customers are rarely putting an aircraft in the sky simply because they need a drone at altitude. They need what the aircraft is carrying. That might be an ISR sensor, camera, tactical radio, LTE equipment, networking hardware or another specialized payload. The aircraft is the means of getting that capability to the position where it provides the most value.
This distinction becomes particularly important in heavy-lift operations. Payload weight and endurance are closely connected on a battery-powered aircraft because carrying additional weight requires additional power. An aircraft may technically be capable of lifting a substantial payload, but that specification does not tell an operator how long the aircraft can maintain that payload at altitude under actual operating conditions. The heavier and more capable the payload becomes, the more important that question becomes.
That experience has influenced how we developed the LEAP product line. The LEAP Solo 5K can support up to 21 pounds of customer payload, the LEAP Solo 10K can support up to 50 pounds, and the LEAP Solo 20K is designed to support payloads up to 150 pounds. For us, heavy lift is not simply about proving that an aircraft can get that weight off the ground. The more important objective is keeping the capability represented by that payload available for the duration it is required.
Nine Years in the Field Made Us Think Beyond the Aircraft
The aircraft naturally receives much of the attention in an unmanned system, particularly during demonstrations. Watching a heavy payload rise hundreds of feet above the ground provides an immediate and visible measure of what the system can do. Once the system is being used in the field, however, getting the payload to altitude is only one part of a much larger problem.
If an ISR payload is collecting video, that information needs to reach someone. If communications equipment is being elevated, it needs connectivity to the larger network. The aircraft needs command and control, the payload needs power, data needs a reliable path between the air and the ground, and information may ultimately need to travel far beyond the immediate deployment site.
Over time, this has changed the way we think about the role of the ground station and tether. They cannot simply be accessories supporting the aircraft. They are part of the communications and data architecture of the entire system.
The LEAP tether can provide power while also carrying data, and the ground system can serve as a connection point for backhaul through infrastructure such as LEO and GEO satellite, fiber, microwave and other communications systems. That means the same architecture keeping an aircraft and its payload at altitude can also help move the information generated there to the people and systems that need it.
This is an important distinction because the value of elevation does not end at the payload. Putting a camera, radio or communications package hundreds of feet above the ground can create an enormous advantage, but only if the information or connectivity it provides can be integrated into the rest of the network. Years of field operations have made us think much less about the drone as an isolated aircraft and much more about the complete path from the payload in the air to the end user receiving its information.
Controlled Demonstrations Cannot Reproduce the Real World
We have also learned to place a different value on demonstrations. Testing in controlled environments is essential to development, integration and validation, but a successful demonstration does not necessarily tell you how a system will perform after repeated deployments in changing conditions.
A planned demonstration generally begins with known parameters. The location is selected in advance, the expected duration is understood, the payload is predetermined and the people operating the equipment know what is supposed to happen. Field deployments have a way of changing those assumptions.
Weather can change. A deployment can last longer than expected. Payload requirements can evolve. Equipment may need to be moved and redeployed. Different operators may need to use the same system. Communications infrastructure that was expected to be available may not be available at all. A mission that was originally expected to last several hours may need to continue much longer.
Those variables are particularly important when evaluating systems that depend heavily on batteries. A short demonstration can be designed around the available flight time. A real deployment cannot always be designed around the battery. If the requirement continues, the system has to continue with it.
That difference is one reason our deployment history matters to us. Since 2017, USaS technology has been used during hurricanes, wildfires, military exercises, border operations, telecommunications deployments and major events. Each environment introduces different requirements, and repeated deployments reveal issues that are difficult to reproduce during a controlled test. Real-world experience does not replace engineering and testing, but it provides a different kind of information about what actually matters when the system leaves the test environment.
Some of the Most Valuable Drone Applications Do Not Require the Drone to Go Anywhere
Another lesson has come from watching the broader drone industry pursue greater range and autonomy. There are good reasons for both. Many unmanned missions depend on an aircraft’s ability to travel long distances, cover large areas or operate beyond the immediate location of its operator.
Tethered operations have shown us the other side of that equation. Some applications benefit far more from maintaining the right position than from traveling a long distance.
Temporary communications coverage, persistent ISR, elevated tactical radios, disaster response, border monitoring and event communications all benefit from putting capability at altitude and keeping it there. In those situations, the aircraft does not necessarily create value by traveling from one point to another. It creates value by maintaining elevation, supporting its payload and remaining available for as long as the requirement exists.
That changes the metrics that matter. Range becomes less important while payload capacity, endurance, data throughput, reliability, deployment time and backhaul become more important. A drone designed to travel ten miles and a drone designed to maintain critical infrastructure at 400 feet may both be unmanned aircraft, but they are solving fundamentally different problems.
Recognizing that difference has influenced the development of both our heavy-lift LEAP Solo systems and the smaller LEAP Tactical platform. LEAP Tactical, for example, is designed around mobility and rapid deployment, with the complete system contained in a hardshell case and deployment and retrieval within ten minutes. Its Overwatch configuration can maintain ISR or communications payloads at up to 400 feet AGL, while other configurations extend the concept to pursuit capability or C2 and payload data transmission through a hybrid fiber tether.
The objective is not simply to build another aircraft with a different set of specifications. It is to design the complete system around what the operator needs to accomplish once the aircraft is in position.
The System Matters More Than Any Single Specification
Perhaps the most important lesson from nine years of tethered UAS operations is that no individual specification tells you whether a system will be useful in the field.
Maximum payload does not tell you how long that payload can remain airborne. Maximum altitude does not tell you whether the information collected there can reach a command center. Flight endurance does not tell you how easily the system can be transported and deployed. A high-bandwidth payload is only as useful as the data path supporting it, and an aircraft capable of remaining airborne for an extended period still depends on the equipment and infrastructure on the ground.
These relationships have pushed us toward thinking about tethered UAS as complete systems rather than individual aircraft. Power, payload, tether management, data, C2, backhaul, deployment, retrieval and logistics all influence what the operator can ultimately accomplish.
Nine years ago, we were proving that a tethered drone could keep useful capability in the air for extended periods. Today, the questions we ask are much broader. Can the system keep the required payload operating for as long as it is needed? Can it move the resulting data where it needs to go? Can it adapt when the duration, environment or requirements change? Can it be deployed, operated, retrieved and then do it again somewhere else?
Those questions were not created by a specification sheet. They came from years of putting tethered UAS into the field and seeing what matters after takeoff.
