Ports run around the clock across a mix of
open water, container yards, cranes, warehouses, fuel facilities and access
roads. Security teams can have strong visibility across gates and ground
operations while still having limited information about low-altitude air
activity above the site.
Airspace monitoring adds another source of
operational information. Depending on the signal, aircraft and sensor
configuration, a monitoring system can help staff identify a broadcast
aircraft, review available location data, receive an alert and compare the
event with approved activity. That context helps a team decide what to check
next.
For ports, the practical question is not
simply whether a sensor can detect a signal. It is whether the available
information reaches the right people, quickly enough, in a format they can use
alongside existing security and operating procedures.
Why low-altitude airspace matters at a port
Port environments are difficult to monitor
with a single tool. Cranes and stacked containers can obstruct sightlines.
Vessels move between berths, maintenance work changes from day to day, and
contractors may carry out approved aerial inspections. Activity can also
approach from the waterfront or adjoining land rather than a main vehicle
entrance.
An airspace monitoring workflow helps the
team distinguish a known operation from an event that needs further review. It
can support checks against scheduled inspections, approved operators,
restricted areas and the port’s incident procedures. It does not replace a
human assessment or establish a person’s identity by itself.
The quality of the resulting picture
depends on the signal being received, aircraft and firmware support, sensor
placement, radio conditions, network connectivity and how the port configures
its monitoring process.
What an airspace monitoring system should provide
Identification and location data
Remote ID broadcasts can provide aircraft
identification and position information, plus other fields where the aircraft
and broadcast support them. Depending on the source, location information may
refer to the aircraft, the control station or the takeoff point. These are
different data points and should not be treated as interchangeable or as
verified personal identity.
A timely track and clear alert
A useful alert should give the operator
enough context to review the event: when it was detected, the available
identity fields, reported position, track history where available and the zone
involved. AirSentinel's datasheets state that live-track delivery is normally
under one second over cellular, subject to configuration and connectivity.
Alert transit and the time a person takes to respond are separate.
Integration with existing operations
Ports may need to share selected
information with a control room, security team or compatible third-party
platform. AirSentinel supports local and cloud JSON APIs. Custom CSV reporting
is available on request, according to the product datasheets. Before deployment,
confirm the fields, update rate, authentication and network requirements with
the integration team.
AirSentinel AMS V10, AMS Pro and AMS Pro Max
The current AMS sensor family includes
three configurations with different sensing capabilities. AMS V10 focuses on
supported Remote ID broadcasts. AMS Pro adds acquisition of supported DJI O1 to
O4 OcuSync and Drone ID signals, including supported aircraft that do not
provide cooperative broadcasts. AMS Pro Max adds advanced signal intelligence
for supported DJI O1 to O4 signals and selected Autel aircraft. Model choice
should follow the aircraft and protocol requirements for the site, not the
model name alone.
|
Specification
|
AMS V10
|
AMS Pro
|
AMS Pro Max
|
|
Primary capability
|
Remote ID across
supported Wi-Fi and Bluetooth broadcasts
|
Supported DJI
O1–O4 OcuSync / Drone ID signal acquisition, including supported
non-cooperative aircraft
|
Advanced signal
intelligence for supported DJI O1–O4 signals and selected Autel aircraft
|
|
Standard antennas
|
4
|
5
|
5
|
|
PoE requirement
|
30 W
|
90 W
|
90 W
|
|
ADS-B option
|
Dual-band 978 /
1090 MHz; adds 2 antennas, 6 total
|
Dual-band 978 /
1090 MHz; adds 2 antennas, 7 total
|
Dual-band 978 /
1090 MHz; adds 2 antennas, 7 total
|
|
Remote ID
|
Core capability;
2.4 and 5.8 GHz supported Wi-Fi and Bluetooth broadcasts
|
Receiver option
available across the AMS family
|
Receiver option
available across the AMS family
|
|
APIs and connectivity
|
LTE, Ethernet,
local and cloud JSON APIs
|
LTE, Ethernet,
local and cloud JSON APIs
|
LTE, Ethernet,
local and cloud JSON APIs
|
|
Enclosure and mounting
|
IP65 enclosure;
rail, pole or wall mounting; fixed or mobile
|
IP65 enclosure;
rail, pole or wall mounting; fixed or mobile
|
IP65 enclosure;
rail, pole or wall mounting; fixed or mobile
|
Shared installation details: the datasheets
list a base enclosure size of 19 × 14 × 8 inches (approximately 483 × 356 × 203
mm), excluding antennas and mounting accessories. The published reference
weight is 17 lb (approximately 7.7 kg) for the stated AMS enclosure
configuration; installed weight varies by model and options. Antenna
arrangement and clearance requirements depend on the configuration.
The datasheets state a typical reception
range of 1 to 12 miles with standard antennas, depending on environment,
aircraft and installation. Treat this as a planning range, not a guaranteed
radius. Confirm the aircraft and firmware support matrix, antenna placement,
site conditions and expected coverage with AirSentinel before procurement.
When AMS V10 is the right fit
AMS V10 is designed for high-density Remote
ID sensing. It receives supported Remote ID broadcasts over Wi-Fi and Bluetooth
in the 2.4 and 5.8 GHz bands. The datasheet lists four standard antennas and a
30-watt Power over Ethernet requirement. It also lists the ability to process
hundreds of simultaneous supported Remote ID targets.
For a port that mainly needs visibility
into supported Remote ID broadcasts, V10 provides a focused starting point. It
can supply aircraft identity and position, plus available control-station or
takeoff location information when the source provides it. The exact fields
depend on the broadcast and aircraft. Review the intended aircraft mix and
coverage objective before deciding that Remote ID alone is sufficient.
When AMS Pro is the right fit
AMS Pro is designed for acquisition of
supported DJI O1 to O4 OcuSync and Drone ID signals, including supported
non-cooperative aircraft. The datasheet lists five standard antennas and a
90-watt Power over Ethernet requirement. For supported aircraft and firmware,
the sensor can provide latitude and longitude; available model, serial number
and additional unencrypted data vary by aircraft and firmware.
Consider AMS Pro when the port’s
requirement extends beyond cooperative broadcasts and includes supported signal
intelligence from compatible DJI aircraft. Ask AirSentinel to validate the
exact aircraft, protocol and firmware matrix for the intended deployment. Do
not assume that every aircraft from a named manufacturer exposes the same
fields.
When AMS Pro Max is the right fit
AMS Pro Max is the advanced
signal-intelligence configuration in the current AMS family. Its datasheet
specifies advanced decryption of supported DJI O1 to O4 signals and selected
Autel aircraft. It uses five standard antennas and requires 90-watt Power over
Ethernet. The datasheet describes expanded signal intelligence for supported
aircraft and protocols.
Pro Max is worth evaluating when the site’s
documented aircraft mix calls for the additional supported signal coverage.
Confirm the supported-aircraft and firmware matrix for the mission before
selecting it. The datasheet does not imply universal compatibility with all DJI
or Autel models, and available data can change with firmware, protocol and
installation conditions.
Shared installation, connectivity and system integration
All three configurations use the AMS
enclosure family. The datasheets describe an IP65-rated, weather-sealed locking
enclosure with rail, pole and wall mounting options. Fixed and mobile
installations are supported, with antennas mounted directly or remotely where
the site design requires it.
The sensor family supports LTE cellular and
Ethernet connectivity, local and cloud API access, and real-time JSON output
for compatible integrations. AirSentinel also describes remote diagnostics and
configuration support for distributed deployments. A port planning several
sensing positions should document network availability, mounting locations,
cable routes, antenna separation and how operators will receive and acknowledge
alerts.
For a configuration that includes ADS-B
reception, the datasheets specify dual-band 978 and 1090 MHz reception and two
additional antennas. The standard antenna count is four for V10 and five for
Pro and Pro Max; with the ADS-B option, the stated totals become six and seven
respectively. Confirm the supplied PoE equipment, installed weight, antenna
clearances and site-specific operating-temperature requirements with
AirSentinel.
AirSentinel states that its sensors are
produced in the United States with American-made and global components. The V10
datasheet lists an NDAA-compliant version as available; the Pro Max datasheet
says an NDAA-compliant version can be produced on request. Confirm the required
configuration and documentation during procurement.
A practical airspace monitoring workflow for port teams
1. Define the operational area
Map the areas where airspace awareness
matters most, such as berths, crane corridors, fuel facilities, maintenance
zones and high-value cargo areas. Identify obstructions and likely sensor
mounting positions.
2. Confirm the aircraft and signal requirements
List known approved aircraft and expected
activity. Match those requirements to the V10, Pro or Pro Max capability
statements, then validate model and firmware support with AirSentinel.
3. Install and test the sensors
Check antenna placement, PoE capacity,
weather exposure, cellular signal or Ethernet availability and the intended
coverage. Validate performance at the actual site rather than relying only on a
published range.
4. Route data to the right teams
Decide who receives alerts, which systems
need JSON data, and how operators record an event. Test connectivity
interruptions and the process for acknowledging an alert.
5. Review each event in context
Compare available identity and location
data with approved operations, schedules, site zones and other relevant
records. Escalate through the port’s established procedures when the event
remains unexplained.
6. Maintain the deployment
Review sensor health, firmware
compatibility, network performance and alert quality. Reassess coverage after
layout changes, construction, new equipment or changes to operating procedures.
Example: reviewing an alert near a container terminal
Suppose a sensor reports aircraft activity
near a crane corridor during a scheduled maintenance window. The operator
checks the time and reported position, compares the available identification
data with the approved inspection schedule, and contacts the relevant
operations lead if the event cannot be matched to an authorised task. The event
record captures the alert, the checks performed and the decision made under
site procedures.
The example illustrates the value of
context, not a guaranteed outcome. A sensor may not receive every broadcast,
and the available identification or location fields depend on the signal
source. The system provides information for the team to assess; it does not
establish intent or replace the port’s decision-making process.
How to choose the right AMS configuration
·
Choose AMS V10 when supported
Remote ID reception is the main requirement and a 30-watt PoE configuration is
preferred.
·
Evaluate AMS Pro when the
requirement includes supported DJI O1 to O4 OcuSync or Drone ID signal
acquisition, including supported non-cooperative aircraft.
·
Evaluate AMS Pro Max when
advanced signal intelligence for supported DJI O1 to O4 signals and selected
Autel aircraft is relevant to the documented aircraft mix.
·
For all models, confirm
aircraft and firmware support, site coverage, available data fields,
connectivity, mounting and power before purchase.
Frequently asked questions
What is airspace monitoring at a port?
It is the use of sensors and software to
observe supported aircraft activity in the low-altitude airspace around port
facilities. Depending on the signal source, it can provide identification
fields, location information, tracks and alerts for authorised teams to review.
What is the difference between AMS V10, AMS Pro and AMS
Pro Max?
AMS V10 focuses on supported Remote ID
broadcasts over Wi-Fi and Bluetooth. AMS Pro acquires supported DJI O1 to O4
OcuSync and Drone ID signals, including supported non-cooperative aircraft. AMS
Pro Max adds advanced signal intelligence for supported DJI O1 to O4 signals
and selected Autel aircraft.
How far can an AMS sensor receive signals?
The datasheets state a 1 to 12 mile
reception range with standard antennas, depending on the environment, aircraft
and installation. This is not a guaranteed radius. Site testing and a coverage
plan are recommended.
How many targets can AMS V10 process?
The V10 datasheet describes hundreds of
simultaneous supported Remote ID targets. Actual reception depends on supported
broadcasts, local conditions and configuration.
What power supply does each AMS model need?
The datasheets specify 30-watt Power over
Ethernet for AMS V10 and 90-watt Power over Ethernet for AMS Pro and AMS Pro
Max. Confirm the supplied equipment and installation requirements with
AirSentinel.
The datasheets list LTE cellular and
Ethernet connectivity, local and cloud API access, and real-time JSON output
for compatible integrations. Confirm the required data fields and integration
details with AirSentinel.
Can a sensor provide a pilot or control-station location?
Available ground-location data depends on
the source. Standard Remote ID may provide control-station position, while
broadcast modules may provide takeoff location. These data points are not
verified personal identity, and availability varies.
Are the AMS sensors suitable for outdoor installation?
The datasheets describe an IP65-rated,
weather-sealed locking enclosure and rail, pole or wall mounting options.
Confirm site-specific operating-temperature requirements, antenna clearances
and installation details with AirSentinel.
Does adding ADS-B change the antenna count?
Yes. The ADS-B option adds two antennas for
dual-band 978 and 1090 MHz reception. The datasheets list six total antennas
for V10 with the option and seven for Pro or Pro Max with the option.
What should a port confirm before ordering?
Confirm the supported aircraft and firmware
matrix, required data fields, expected coverage, sensor locations, PoE supply,
network connectivity, antenna arrangement, installed weight and any required
compliance configuration.
Conclusion
Effective port airspace monitoring depends
on matching sensor capability to the aircraft and signals expected at the site,
then delivering usable information into a clear operating process. AMS V10, AMS
Pro and AMS Pro Max provide three different sensing configurations, from
supported Remote ID broadcasts to more advanced signal intelligence for
specified aircraft and protocols.
Before selecting a model, define the
coverage objective, validate the supported-aircraft and firmware matrix, and
test the planned installation under real site conditions. To review
configuration details or discuss an integration, contact AirSentinel.