Awareness at the edge

About PerimeterScope

PerimeterScope started with Solutions a simple operational question

When a team is operating at a remote airport, supporting disaster response, protecting an area of concern, or coordinating activity in an austere environment, one question matters immediately: what is in the air around us right now? For years, that question has been harder to answer than it should be. Aircraft data may be available, but not always reliably. Drone activity may be present, but often through different tools and different workflows. Public feeds may be incomplete because local infrastructure is damaged or offline. The result is an operational picture that can be fragmented just when teams need it to be clear.

PerimeterScope was built to close that gap. The system was developed by James Lea to help operators see the airspace around them more coherently, with aircraft and drone awareness designed to support the same field decision process rather than living in separate silos. It is a practical response to a practical problem: fragmented awareness creates avoidable uncertainty

About PerimeterScope

The path to PerimeterScope began with FlightOps ADS-B PerimeterScope

Before PerimeterScope included drone awareness, the immediate need was aircraft awareness. Lea realized that disaster support teams needed a better way to see inbound aircraft in real time so they could meet flights on the ramp, coordinate movement, and protect incoming cargo in conditions where confusion can develop quickly. After Hurricane Dorian, he developed a deployable ADS-B receiver package for exactly that purpose.
That concept matured into a field-ready system originally known as FlightOps ADS-B. It was later packaged in a rack-mount Gator case and paired with an Icom A-120 aviation-band radio so teams could not only see aircraft but also communicate with them directly during operations. During AERObridge’s Hurricane Helene response in western North Carolina, the deployed system showed aircraft that were not visible on public aggregation sites because local receivers in the surrounding area were offline.
“What matters in the field is not whether the public internet can see the operation,” Lea said. “What matters is whether the people responsible for the mission can see enough to act safely and confidently.”

About PerimeterScope

Why PerimeterScope matters now

By 2026, the challenge had expanded. Teams no longer needed visibility into aircraft alone. They also needed a practical way to see drone Remote ID broadcasts and understand that activity in the same operational context. In many environments, drones are now part of the same airspace reality as fixed-wing aircraft and helicopters. The problem is that the information often remains separated across different tools, leaving the operator to build the combined picture mentally.
PerimeterScope was created to solve that. The first real-world test took place in March 2026 and worked as expected. The current system displays ADS-B and UAT traffic on one screen and drone Remote ID data on a second screen. A unified display is in development to bring both onto the same screen, reducing fragmentation and making the air picture easier to interpret in real time.
This is not innovation for its own sake. It is a response to a growing operational requirement. Whether the mission is disaster support, infrastructure protection, incident management, or another field operation, teams need to know what aircraft and drones are operating nearby. They also need that information presented in a way that supports action instead of adding complexity.

About PerimeterScope

Built for the field, not just the lab

PerimeterScope reflects the realities of real deployment. The system uses a Peplink modem or router for internet connectivity and can be augmented with a Starlink terminal. That architecture is intentional. In austere environments, connectivity may be limited, degraded, or improvised, so f ield systems have to be designed around resilience from the beginning.
Additional planned capabilities include geofencing and FAA Temporary Flight Restriction import. Those features are important because situational awareness is not just about seeing traffic. It is about understanding activity in context. Operators need to know where their protected area begins and ends, what restrictions are in effect, and whether the movement they are seeing matters to the mission at hand.
“PerimeterScope is being built around a simple idea,” Lea said. “Give the operator a more coherent air picture with the context needed to make the next decision.”
That focus on practical context is one reason the platform stands apart. It is not built around a generic dashboard concept. It is built around what operators actually need when conditions are demanding and margins for error are small.

About PerimeterScope

The need is bigger than one mission set

Although PerimeterScope grew out of disaster response experience, the need it addresses is far broader. Any organization that must understand both manned and unmanned activity in a limited or infrastructure-constrained environment can benefit from a clearer and more dependable operational picture. Public safety agencies, infrastructure protection teams, remote operations, event support environments, and aviation-adjacent field missions all face versions of the same challenge.
PerimeterScope answers that challenge with a field-driven approach. It starts with local awareness. It acknowledges that public visibility can be incomplete. It treats aircraft and drone awareness as parts of the same decision problem. And it continues to evolve toward a unified system that will help operators see more, interpret more, and act with greater confidence.
“A useful field system should lower uncertainty, not add to it,” Lea said. “That is the purpose behind PerimeterScope.”
That is the story behind the platform. It is not simply a technology product. It is the result of real operational lessons, refined into a system built to help teams understand the airspace around them when it matters most.

Fill This Form