DRONECOM BMC3 — Operator’s Manual

Purpose

This manual provides operational guidance for the DRONECOM Battle Management, Command, Control, and Communications (BMC3) system. It is intended for watch officers, tactical action officers, and sensor operators responsible for managing carrier strike group operations through the DRONECOM tactical interface.

System Overview

DRONECOM integrates sensor data from organic and networked assets into a unified tactical picture, providing real-time situational awareness across the electromagnetic and acoustic domains. The system supports:

• Sensor management — Configuration and control of active and passive sensor suites across all platforms in the carrier strike group
• Contact tracking — Automated detection, classification, and tracking of air, surface, and subsurface contacts
• Emission control — Platform-level EMCON management to balance situational awareness against emission security
• Force coordination — Drone tasking, weapon assignment, and engagement management through the tactical display

Manual Organization

• Symbology — NTDS tactical symbol reference, affiliation identification, and battle damage assessment indicators
• Sensors — Sensor theory of operation, detection mechanics, EMCON procedures
• Operations — Force employment: mission tasking, doctrine, deck operations, weapons employment, and endurance management
• Platform Reference — Chassis, sensor and warhead datasheets: performance, envelopes, signatures and deck requirements
• Glossary — Acronyms and terminology reference

Conventions

Throughout this manual:

• Own — Platforms organic to or assigned under own command authority
• Allied — Platforms identified as allied via datalink or IFF
• Hostile — Positively identified adversary platforms
• Unknown — Detected contacts with unresolved affiliation
• Neutral — Non-aligned or civilian platforms

Affiliation colors may be adjusted at the operator console to suit individual display requirements.

Sensor and equipment designators follow standard nomenclature (e.g., AN/SPY-310).

Symbology

This chapter describes the NTDS (Naval Tactical Data System) symbology used on the DRONECOM tactical display. Operators must be able to identify contact symbols on sight. Each symbol encodes two properties: the platform classification (what type of contact it is) and the affiliation (its relationship to own forces).

Affiliation

A contact’s affiliation determines its base geometric shape:

• Circle / Arc — Own or Allied. The contact has been positively identified as an own-force or allied platform via IFF or datalink.
• Diamond — Hostile. The contact has been positively identified as an adversary.
• Square — Unknown. The contact has been detected but its affiliation has not yet been resolved.
• Cross — Neutral. The contact has been identified as a non-aligned or civilian platform.

All new contacts begin as Unknown. As sensor data accumulates and IFF identification occurs, affiliation resolves to Own, Allied, Hostile, or Neutral. See the Sensors section for details on IFF mechanics.

Note: Affiliation colors may be adjusted at the operator console. The geometric shapes (circle, diamond, square, cross) provide affiliation identification independent of color.

Symbol Reference

Battle Damage Assessment

Contacts that have been engaged may display BDA (Battle Damage Assessment) overlay decorations. These markings appear on contacts in the Lost state — active contacts do not display BDA indicators.

Heading Vectors

Moving contacts display a heading vector — a line extending from the symbol center in the direction of travel. The vector is shown when the contact’s speed exceeds a minimum threshold; stationary or near-stationary contacts display only the base symbol.

The heading vector shows the direction the contact is travelling in. It updates in real time as the contact changes course.

Contact Classification

The system assigns NTDS classification to detected contacts based on the following rules:

• Elevation-based — Contacts more than 16 ft above the surface are classified as Air. Contacts more than 16 ft below the surface are classified as Subsurface. Contacts within that band are classified as Surface.
• Signature analysis — As sensor data accumulates, the system matches a contact’s measured characteristics — radar cross-section, acoustic profile, observed dimensions — against the platform recognition database. This is how surface contacts are further classified as Command Ship (large displacement, flight deck signature) versus standard surface vessels. Missile and Torpedo contacts are identified by their flight profile and acoustic signature.
• Rotary-wing — Helicopter classification is assigned when the contact’s flight characteristics match a rotary-wing profile (hover capability, low airspeed).
• Dynamic — Classification can change as conditions change. A submarine surfacing transitions from Subsurface to Surface. An initially unclassified Air contact may be reclassified as Helicopter once sufficient flight data is collected.

Sensors

This chapter covers the theory of operation for sensor systems integrated into the DRONECOM tactical display. All contact data presented on the map display — tracks, threat warnings, classifications — originates from the sensor suite. Operators must understand sensor capabilities, limitations, and the tradeoffs involved in emission management to effectively employ the system.

How Detection Works

Every sensor follows the same fundamental process:

1. Energy propagates — either emitted by the sensor (active) or by the target (passive)
2. Signal attenuates with distance — strength decreases as a function of range
3. Detection occurs when the received signal exceeds the sensor’s sensitivity threshold

The critical distinction is between active and passive sensors:

• Passive detection of natural emissions (IR, visual, passive sonar hearing engine noise) — the sensor listens for energy the target produces naturally: thermal signatures, visible light, machinery vibration. Signal strength falls off with the square of distance (1/R²). This is the shortest-range mode but produces no emissions from the receiving platform. Reported on the tactical display as Passive.

• Active detection (radar, active sonar) — the sensor emits its own signal and listens for the return echo. The signal makes a round trip, so strength falls off with the fourth power of distance (1/R⁴). Longer range than passive detection of natural emissions, but the transmission itself is detectable by hostile platforms. Reported on the tactical display as Active return.

• Passive detection of active emissions (RWR hearing a hostile radar, passive sonar hearing a hostile sonar ping) — the sensor detects the powerful transmission of a hostile active sensor. The signal is strong and travels only the one-way path (1/R²), giving this mode the longest detection range of the three. A warning receiver will detect a hostile radar at significantly greater range than that radar can detect a return echo. This asymmetry is the foundation of the active-vs-passive tradeoff covered in the next section. Reported on the tactical display as Active emission.

Active vs Passive — The Core Tradeoff

The central operational tension is situational awareness vs emission security.

When radar is active, detection ranges exceed those of any passive sensor. However, every hostile platform equipped with a Radar Warning Receiver (RWR) will detect those emissions — and because RWR operates on the one-way signal path (1/R²), an RWR can detect a radar transmission from significantly greater range than that radar can detect a return echo.

Operating in passive mode eliminates RWR exposure but limits detection to shorter-range passive sensors — IR, visual, and passive sonar. Coverage is reduced accordingly.

Every engagement involves this decision: activate sensors to establish the tactical picture, or maintain emission security and rely on passive detection.

The Electromagnetic Domain

Four sensor types operate in the electromagnetic spectrum — above the water surface.

Radar — Active. Emits radio energy, detects returns. Provides the longest detection ranges available. Subject to Doppler notching and sea clutter (see Radar Effects and Doppler Processing). At sufficient signal strength, radar can resolve contact affiliation via IFF (Identification Friend or Foe).

RWR (Radar Warning Receiver) — Passive. Detects hostile radar emissions, providing bearing to the transmitting platform. As a passive sensor, RWR is always operational — EMCON state has no effect on it.

IR (Infrared) — Passive. Detects thermal emissions — engine heat, exhaust plumes. Shorter range than radar but produces no emissions. Provides detection without revealing the receiving platform’s position.

Visual — Passive. Detects visible-spectrum signatures. The shortest-range electromagnetic sensor. Produces no emissions.

flowchart LR
    R["Own Radar\n(Active)"]:::own -- "Emission 1/R²" --> RWR["Hostile RWR\n(Passive)"]:::enemy
    R <-. "Pulse out, echo back\nRound trip 1/R⁴" .-> T["Hostile\nPlatform"]:::enemy
    T -- "Thermal 1/R²" --> I["Own IR\n(Passive)"]:::own
    T -- "Visible 1/R²" --> V["Own Visual\n(Passive)"]:::own

    classDef own fill:#062712,stroke:#22c55e,color:#22c55e
classDef enemy fill:#2f0d0d,stroke:#ef4444,color:#ef4444
classDef success fill:#062712,stroke:#22c55e,color:#22c55e
classDef warning fill:#2e2301,stroke:#eab308,color:#eab308
classDef error fill:#2f0d0d,stroke:#ef4444,color:#ef4444
classDef info fill:#282828,stroke:#cccccc,color:#cccccc

Note: Radar emissions detected by a hostile RWR travel the one-way path only — the RWR detects at greater range than the radar can detect a return echo. IR and visual sensors operate independently, detecting the target’s own thermal and visible signatures without producing emissions.

The Acoustic Domain

Two sensor types operate underwater. Electromagnetic sensors cannot penetrate the water surface, so subsurface platforms rely entirely on acoustic detection.

Active Sonar — Emits acoustic pings and listens for echoes. Fourth-power signal falloff, same as radar. The ping itself is detectable by hostile passive sonar — the same tradeoff as radar and RWR, applied to the subsurface domain.

Passive Sonar — Listens for engine noise, machinery vibration, and active sonar pings from other platforms. Square-law falloff. Produces no emissions — the subsurface equivalent of passive electromagnetic operation.

Underwater propagation is further shaped by ocean conditions. Temperature layers, water depth, and convergence zones all modify effective detection ranges beyond the basic signal falloff — a platform operating at optimal depth in favorable conditions may hold contacts that are invisible to one operating identically at the wrong depth. See Acoustic Effects for detail.

Medium Boundaries

The water surface is an absolute boundary for sensor propagation:

• Electromagnetic sensors (radar, RWR, IR, visual) cannot propagate through water. A submerged platform is undetectable by radar regardless of range.
• Acoustic sensors (active and passive sonar) cannot propagate through air. An airborne platform is undetectable by sonar.

This creates two distinct operational domains. A submarine operating silently below the surface exists in a separate detection environment from the air picture above. Maintaining awareness across both domains requires assets in each.

Interpreting Contacts

When sensors detect a target, it appears on the tactical display with the following data:

Track Code — A unique identifier assigned on initial detection (e.g., “T-001”). The track code persists across Lost→re-acquired transitions within an engagement — it is the contact’s identity for as long as it remains on the display. A contact re-detected after expiry is treated as a new track and receives a new code.

NTDS Class — Platform classification based on sensor data and signature analysis. Examples: Air , Surface , Subsurface , Command Ship , Missile , Torpedo . See Symbology for the full reference.

Affiliation — All new contacts begin as Unknown . As signal strength increases within IFF identification range, affiliation resolves to Own , Allied , Hostile , or Neutral . Allied units may also arrive pre-identified on the tactical display via datalink.

Detection Mode — Indicates how the contact was most recently detected:

• Active return — own active sensor (radar or sonar) illuminated the contact and detected the return echo
• Active emission — own passive sensor detected active sensor emissions from the contact (hostile radar or sonar)
• Passive — own passive sensor detected the contact’s natural emissions (thermal, visible, acoustic)

Contact Lifecycle

Contacts progress through three states:

• Active — Currently held by at least one sensor. Position updates continuously.
• Lost — All sensors have lost the contact. Last known position is displayed, decaying over time.
• Expired — The contact has been lost beyond the stale timeout and is removed from the display. A contact detected again after expiry is a new track; it does not recover the prior track code.

A lost contact can be re-acquired if any sensor regains detection before expiry.

stateDiagram-v2
    direction LR
    [*] --> Active : New detection
    Active --> Lost : All sensors lose contact
    Lost --> Active : Re-acquired
    Lost --> Expired : Stale timeout
    Expired --> [*]

    classDef own fill:#062712,stroke:#22c55e,color:#22c55e
classDef enemy fill:#2f0d0d,stroke:#ef4444,color:#ef4444
classDef success fill:#062712,stroke:#22c55e,color:#22c55e
classDef warning fill:#2e2301,stroke:#eab308,color:#eab308
classDef error fill:#2f0d0d,stroke:#ef4444,color:#ef4444
classDef info fill:#282828,stroke:#cccccc,color:#cccccc

    class Active success
    class Lost warning
    class Expired error

EMCON: Emission Control

EMCON (Emission Control) is the primary tool for managing the active-vs-passive tradeoff at the platform level.

Active — All active sensors radiating. Maximum detection capability. The platform is emitting and detectable by hostile passive sensors.

Passive — All active sensors silenced. Detection limited to passive sensors only. The platform produces no sensor emissions.

Per-sensor control — Fine-grained control: radar can be silenced while active sonar remains radiating, or vice versa. Only active sensors can be individually silenced — passive sensors (RWR, passive sonar, IR, visual) are always operational.

EMCON is set per-platform. Placing the carrier in Passive mode silences its radar but has no effect on embarked or deployed assets — each platform manages its own emission state independently.

The Horizon

Earth’s curvature limits the effective range of electromagnetic sensors. A sensor can only detect targets above its geometric horizon — beyond that distance, the curvature of the earth blocks the line of sight.

All EM sensors — radar, RWR, IR, and visual — are subject to horizon limitations. Sonar propagation follows different physical principles and is not horizon-limited.

Three factors determine horizon range:

Sensor altitude — Higher altitude extends the horizon. An airborne sensor platform can detect beyond the horizon that limits a surface-mounted radar. This is a primary motivation for deploying airborne surveillance assets — they extend the detection horizon significantly.

Mast height — Surface platform sensors are mounted on masts above the waterline. Greater mast height extends the sensor horizon. The CV-3000 carrier’s sensors are mounted at a mast height of 30 m, giving its AN/SPY-310 radar a horizon of ~11 NM against a sea-level target.

Target altitude — Horizon range depends on both the sensor height and the target height. Two high-altitude platforms can maintain mutual detection at ranges far exceeding what a surface platform achieves against a sea-skimming target.

Approximate horizon ranges for representative altitudes:

Radar Effects

Near the surface, the sea itself limits what a radar can detect. Understanding this effect is essential for effective sensor employment and tactical positioning.

Sea Clutter

A radar does not see a target against empty sky. It sees the target against whatever else sends back an echo from the same distance. Near the surface, that is the sea. The radar can’t separate echoes that arrive at the same moment from the same direction. So when a target shares the radar’s beam with a patch of sea at the same range, the sea’s echo competes with the target’s, and the target is only detected if it is the stronger of the two.

How strong the sea’s echo is depends on three things:

• The size of the patch. It is as wide as the beam and as deep as the radar’s range resolution. Both grow with poorer equipment: a small antenna has a wider beam and a narrow-bandwidth set has a coarser range cell. The width also grows with range, because every beam spreads with distance.
• The angle the radar looks down at the sea. A beam that skims the surface at a shallow angle is mostly reflected away, like light off calm water, so little of it comes back. A beam that looks steeply down at the sea gets much more back. A ship’s mast radar barely looks down at all, so it sees little sea clutter. An aircraft looking down from altitude sees a great deal.
• Whether the target shares the beam with the sea at all. A target well above the surface at its range is in clear air, with nothing beside it in the beam. The beam is taller at long range, so the band of altitude where a target still shares it with the sea also grows with distance. A target beyond the radar’s horizon has no sea behind it at all, and is seen against empty sky.

The target’s own size matters as much as the sea’s. A large ship out-echoes any patch of sea and is seen through clutter with little loss. A small drone or sea-skimming missile can be buried completely. More transmitter power does not help. It strengthens the sea’s echo exactly as much as the target’s. The equipment-side answers are resolution and Doppler. A larger antenna or a wider-bandwidth set shrinks the patch, and Doppler processing separates a target that is moving toward or away from the radar from the stationary sea.

Sea-skimming missiles and low-flying drones exploit this. They stay low enough to share the beam with the sea, and they are small enough to lose to it. Against an airborne look-down radar, they may not be detected until close range, or until they turn toward the radar and their Doppler shift gives them away.

Surface Search

Pulse-Doppler search (see Doppler Processing) discards everything at the sea’s own Doppler. A ship that is stopped, or steaming across the radar’s line of sight, has no Doppler shift to set it apart, so it is discarded along with the sea.

Radars fitted with surface search close that gap. Alongside their pulse-Doppler search, they judge vessels on the surface by echo strength alone. Surface search uses its own wider-bandwidth waveform, whose finer range cell shrinks the patch of sea a hull competes with. A stopped or crossing ship stays visible, provided its echo is stronger than the sea’s. Each radar’s entry in the Sensors reference states whether it has surface search and the range cell it uses.

Surface search applies only to vessels on the surface. Aircraft and missiles, however low they fly, are still searched by Doppler, so notching an aircraft works the same against either kind of set.

When surface search holds a contact, the detecting sensor’s tooltip shows a Surface search row where the Notching row would be. The figure is how many decibels better surface search did than pulse-Doppler alone would have. It is a comparison and is not added into Net SNR; the Clutter row shows the loss surface search actually took.

Acoustic Effects

Three environmental factors modify sonar detection performance and will vary across operating areas.

Thermocline

A thermocline is a sharp temperature gradient at depth — warmer, lighter water above a boundary layer, colder and denser water below. The acoustic velocity gradient at this boundary refracts sound rays: energy propagating at shallow angles bends away from the layer and stays within the upper water column, while steeper angles cross through.

This refraction creates a shadow zone below the thermocline. A platform operating above the layer and searching for a contact below it — or vice versa — faces significant path loss beyond the basic geometric falloff. The signal must cross the boundary twice to return as an active echo, so active sonar is doubly penalized: signal strength degrades on both outbound and inbound legs.

The geometry is asymmetric. A deep platform has steeper angles to the thermocline at any given horizontal range, allowing it to maintain cross-layer paths where a shallow platform at the same range cannot. In practice, a deep submarine may hold a contact on the far side of the layer that a surface ship’s sonar cannot detect at all.

The principal tactical response is depth management. A platform operating below the thermocline is largely concealed from surface sonar — the layer acts as an acoustic screen. Conversely, a platform searching for deep targets should consider operating at depth to close the angular disadvantage.

Shallow Water Attenuation

In open ocean, acoustic energy propagates with relatively little boundary interaction. In shallow water, the sound channel is bounded above by the surface and below by the seabed, and every reflection at either boundary incurs loss. As depth decreases, the channel height decreases and reflection frequency increases — the signal encounters more boundaries per unit range, accumulating more loss per nautical mile.

When a thermocline is present, the effective channel for below-layer propagation narrows further: the acoustic energy is confined to the region between the thermocline and the seabed rather than the full water column. This narrower channel produces higher attenuation rates than the same depth without a layer.

The practical consequence is that shallow water reduces detection ranges across the board. Platforms operating in deep water benefit from longer channels with fewer reflections; the same platform transiting into a shallower operating area will hold contacts at progressively shorter ranges.

Convergence Zones

In deep water, the temperature and pressure structure of the water column creates a sound velocity minimum at mid-depth — the SOFAR channel. Acoustic energy refracted downward below this minimum is bent back upward by increasing pressure, and refracted upward above it by increasing temperature. Both ray families curve back toward the minimum depth, and when they refocus at the surface they form convergence zones: annular rings of enhanced detection at regular stand-off ranges from the source.

Zone geometry is set by the depth of the water. In ~9,800 ft of water the first zone lies ~33 NM from the source, and successive zones repeat at that interval as further ray families refocus; in shallower water the rings close in proportionally — half the depth, half the spacing. Detection within a convergence zone can exceed what range geometry alone would predict — the signal arrives having propagated through the low-loss deep channel rather than suffering shallow-water boundary reflections. Each successive zone is weaker than the one before it, and between zones there is no enhancement at all.

Several conditions limit this effect. Both the transmitting and receiving platforms must be above the thermocline for surface-refracted convergence paths to function; a below-layer platform does not contribute to or benefit from convergence zone propagation. The enhancement also weakens steeply as the water shoals — much faster than the ring spacing shrinks — so zones in moderate depths offer only a marginal detection edge, and in water shallower than ~1,000 ft the column cannot support the channel and no convergence zones form at all. The effect is most operationally significant in deep water, when maneuvering into or out of known zone geometries.

Doppler Processing

Both radar and active sonar use Doppler shift — the frequency change caused by relative motion between the sensor and the target — to separate moving target returns from stationary or slow-moving background returns. A target with significant radial velocity relative to the sensor produces a clear frequency offset and is readily discriminated. A target with near-zero radial velocity relative to the sensor blends into the background.

The underlying principle is identical across domains, but the background environment differs. Radar contends with sea clutter; active sonar contends with reverberation. In both cases, Doppler discrimination is the primary mechanism for extracting target returns from the noise floor.

Radar

Pulse-Doppler radar separates target returns from sea clutter by frequency. A target with high radial velocity toward or away from the radar produces a large Doppler shift and stands out clearly. A target maneuvering to minimize its radial velocity relative to the radar — a technique known as “notching” — causes its return to fall within the clutter rejection filter, where it is indistinguishable from the sea’s returns. Against vessels, a radar with surface search does not rely on Doppler alone.

Aircraft can exploit notching by flying perpendicular to the radar’s line of sight during critical phases of an approach. The effect is transient — the relative geometry between the platform and the radar changes continuously, so sustained notching requires continuous maneuvering to maintain the perpendicular aspect.

Active Sonar

Active sonar pings produce returns from the seabed, sea surface, and volume scatterers throughout the water column — collectively termed reverberation. Doppler discrimination separates moving target echoes from this reverberation background. A target with meaningful closing speed produces an echo offset in frequency from the reverberation, making it detectable. A target with low radial velocity produces an echo at nearly the same frequency as the reverberation returns, rendering detection reverberation-limited.

Unlike radar notching, reverberation limiting is less dependent on deliberate target maneuvering. Any geometry that produces low relative radial velocity — including a target on a parallel course at similar speed — degrades active sonar discrimination.

Sensor Reference

For complete sensor specifications, see the Platform Reference.

Operations

This chapter covers force employment through the DRONECOM tactical display: directing platforms by mission and doctrine, the carrier deck cycle, weapons employment, and endurance management. Where the Sensors chapter explains how the tactical picture is built, this chapter explains how to act on it.

The Command Hierarchy

Deployed platforms are autonomous. The operator does not steer them; the operator assigns objectives and standing rules, and the platforms execute. Command is exercised at two levels:

1. Assignment — a persistent tasking given to a platform or group. Every assignment is built the same way: an anchor — the subject the unit operates relative to, which may be a fixed point, an area, a waypoint path, a friendly unit, or a hostile contact — and what the unit does there. The assignment persists until completed, aborted, or replaced.
2. Doctrine — standing rules that govern how the unit behaves while executing its assignment: how far it leaves its task to fight, which contacts it may fire on, when a weapon is released, whether its active sensors radiate, and whether it brings itself home. Doctrine applies continuously, whatever the assignment.

The intended workflow is command by exception. Doctrine handles routine reactions — a patrolling platform engages or evades per its standing rules without operator intervention. The operator’s attention is reserved for the moments that matter: a deliberate strike, a precise repositioning, an engagement the doctrine would otherwise withhold.

The tactical display reports each unit’s tasking on two lines and no more. MISSION is the commanded intent — the verb the operator assigned. STATUS is what the unit is doing about it right now — the current phase, leg, or reaction. Where the unit is working through a leg or an approach, a single NOW line summarizes the current leg with distance and time to go. There is no order queue to manage: the mission is the whole of what the operator commands, and the status is the whole of what the machine reports back.

Groups

Missions are assigned at the group level. A group has a leader, which executes the mission, and followers, which maintain station on the leader in a designated formation — line abreast, wedge, trail, or echelon, at close, normal, or wide spacing. A platform launched alone is simply a group of one.

Formation spacing is a sensor-signature decision as much as a maneuvering one. A tight formation can register on hostile radar as a single merged contact with an uncertain count — but a weapon fired at a merged track homes on the track’s estimated centroid, and against a tightly packed group that aim point is close to every member. Wider spacing pulls each member away from the centroid, so the same detonation can fall outside every member’s lethal radius — at the cost of presenting the adversary an unambiguous count.

A newly launched group passes through a forming up state — members rendezvous and take station before the assigned mission begins. Throughout its sortie, the group’s mission and current status — FORMING UP, PATROL, ATTACK, Evading, and so on — are reported on the tactical display.

Control groups

Control groups are local selection bookmarks. They are separate from formation Groups and do not change a group’s leader, doctrine, formation, tasking, or membership.

Select own deployed units, stowed units, or a deployed group, then use Ctrl+1 through Ctrl+0 to store that selection. Saving a deployed group records its current members as concrete units; later formation membership changes do not alter the bookmark.

Press 1 through 0 to replace the current selection with the saved units that are still live. Press the same number again within 0.4 seconds to centre the tactical camera on a deployed saved unit. A missing or destroyed unit is removed from its bookmark when recalled. A bookmark containing only stowed units still recalls, but cannot be centred on the map.

A bookmark that holds exactly one deployed Group recalls as that group: its leader is selected and the group panel opens, just as clicking the group’s header does, so the next mission is assigned to the group as a whole. Recalling the members individually would instead detach each follower onto its own mission. If the group has since disbanded, or the bookmark also holds units from outside it, the saved units are recalled individually.

The default bindings are configurable in Settings → Controls → Control groups. Recall does not fire while a modifier is held: Shift, Alt and the platform command key do nothing on a number key, and Ctrl is the assignment.

Missions

A unit is always either under an assignment or Idle. Idle is the absence of an assignment, not a mission of its own: an idle unit loiters, keeps its sensors on the picture, and reacts to threats under the ambient scan described in Doctrine. A unit whose assignment concludes reverts to Idle and awaits reassignment.

The mission a unit flies is the combination of its anchor and its standing posture (Doctrine). The operator designates the anchor; posture sets the character of the mission; and the tactical display names each combination with its own verb:

For place and friendly anchors, posture is free: re-posturing a unit re-shapes and re-labels its mission in place, so the same station is a GUARD post under Pursue and an OBSERVE post under Evade. For hostile contacts the direction runs the other way: the operator commands the verb, and the verb carries the posture appropriate to it. Attack presses in; Standoff and Shadow keep their distance and never engage the contact they are holding.

GOTO and HOLD are two ends of the same order. Every movement concludes by taking station at its final waypoint, so a moved unit reads GOTO through its legs and HOLD once it settles — the one label change marks arrival, in step with the status transition to On station. GUARD and OBSERVE name the same station only when the operator has re-postured it into something else.

Station (HOLD · GUARD · OBSERVE)

The unit proceeds to a designated point and holds station there. Fixed-wing aircraft orbit the point at a designated altitude; anything that can stop or hover — ships, submarines, rotary-wing — moves to the point and stays there, returning to station if displaced. Posture sets the character of the post: under Defend the unit holds its station and engages what closes within its reaction envelope; under Pursue it is a guard post, engaging what its envelope admits and pursuing; under Evade it is a silent sentry, reporting what it sees and fleeing what threatens it. A held station is the staging mission — a strike package waiting for its window, a reserve positioned behind a screen.

Area (PATROL · SWEEP · RECON)

The unit orbits a designated center at a designated radius and operating altitude, scanning with whatever sensors doctrine permits. Hostile contacts that enter the unit’s reaction envelope trigger the posture reaction. A patrol (Defend) engages and is leashed to its area: it breaks off a pursuit that leads beyond the envelope measured from the patrol, then resumes the orbit. A sweep (Pursue) accepts the pursuit wherever it leads; a recon (Evade) reports and withdraws. Patrol is the workhorse mission for sustained sensor coverage of an area. A closed waypoint circuit (Movement) is flown the same way — a patrol over a route rather than a circle.

Movement (GOTO)

A movement path is created by designating a point on the tactical display and extended point by point. The unit flies the path one leg at a time and concludes it by taking station at the final waypoint — a moved unit ends its transit somewhere deliberate, holding, not adrift; the mission relabels from GOTO to HOLD as it settles. Closed into a loop, the path becomes a circuit and is flown indefinitely as a patrol. Individual waypoints can be removed, the path can be cut short at any waypoint, and the remaining legs are drawn on the tactical display. Assigning a movement point replaces the unit’s current mission; given to a group leader, the path moves the entire group, followers in formation throughout.

A unit in transit is not defenseless. Each leg runs the same ambient scan and posture reaction as a station: a transiting unit under Defend meets a closing hostile and then resumes the interrupted leg; under Evade it diverts around the threat and comes back to the route. The carrier is the exception — a carrier flies its legs and leaves the fighting to its screen.

Routing is automatic for every leg: the system plans around terrain and coastline, and replans when the route is invalidated. Destinations are validated at assignment — a point a waterborne platform cannot reach is corrected to the nearest navigable water, and a destination whose terrain rises above an airborne platform’s ceiling is refused. Commanded speed and commanded altitude are adjusted independently of the mission — they shape how the platform flies whatever it is doing.

Screening (SCREEN · ESCORT · FOLLOW)

The unit maintains station on a designated friendly platform — typically the carrier. The leader orbits the protected unit at the assigned radius; the radius is also the threat trigger: an inbound contact whose CPA (closest point of approach) against the protected unit falls inside the screen radius is treated as a threat to it. Posture sets the response: a screen (Pursue) intercepts the threat and runs it down; an escort (Defend) engages it but breaks off rather than be drawn away from its charge; a follow (Evade) keeps formation and leaves the fighting to others. The screen engages one threat at a time, taking the contact with the smallest time-to-CPA first. If the protected unit is lost, the screen holds station at the protected unit’s last known position. A screen is the standing answer to the carrier’s vulnerability — it trades a platform’s sortie endurance for reaction time against leakers.

A screening unit that holds an unidentified contact closing on its charge does not wait for identification to arrive on its own: when its sensors can resolve the contact and the platform can run it down, it closes the range until identification resolves, then returns to station — a hostile resolution is engaged on return; anything else is released. The charge’s defence preempts the errand: a confirmed threat to the protected unit ends the interrogation immediately.

Against a contact (ATTACK · STANDOFF · SHADOW)

These missions are commanded directly against a hostile contact, and the verb decides everything. Only Attack engages the anchor.

Designating a hostile contact arms an engagement preview at the cursor: the pending verb, with the alternatives listed beside it and the control that cycles them. The commit takes whichever verb the preview shows — Attack is the first candidate, not the only outcome. Friendly units offer their own cycle the same way.

ATTACK — commit against the contact. The engagement runs the sequence described under Weapons Employment: close, launch, hold custody through flyout, assess.

STANDOFF — hold station against the contact at firing range, without firing. The hold range is the reach of the unit’s best ready weapon, computed continuously on the live geometry — the launcher’s altitude advantage and the contact’s aspect included — so the unit rides the edge of its own firing envelope as the contact moves; an unarmed unit holds at a fixed fallback distance. A threat that presses in is answered by falling back and resuming, never by an unordered attack. The result is a shot held in reserve: the contact stays within reach for an immediate Attack order, and nothing is released until that order comes.

SHADOW — maintain custody of the contact from the outer edge of own sensor detection range. The shadowing unit continuously regulates its distance against measured signal strength — hugging the edge of custody rather than flying a fixed offset — holding the track at minimum exposure. A shadow that is itself threatened falls back, then re-acquires.

The two ranges bracket the approach: a shadow holds the contact at the edge of what it can see, a standoff at the edge of what it can hit.

Recovery (RTB)

The unit returns to a carrier and enters the recovery cycle (Deck Operations). RTB is commanded by the operator or entered automatically under the Auto RTB rule (Doctrine); a recovering unit does not pursue contacts.

Reactive States

Three conditions appear on the tactical display without being assigned — the system enters them in response to events:

A unit whose assignment cannot continue reports an error with the cause — Not Recoverable (the hull has no recovery method; no carrier can take it back aboard) or Cannot Engage (the commanded engagement cannot be carried out). An error state requires operator attention.

Doctrine

Doctrine is the set of standing rules carried by every deployed group. Posture, fire control, and emissions are authored as part of each vehicle design and come off the deck with the launch; the remaining rules take their defaults at launch, with the Auto RTB rule derived from the design’s capabilities. All of it is adjustable at any time from the tactical display, and a change applies group-wide.

Posture — how far the unit leaves its task to fight:

Posture is the row selector of the mission table above: re-posturing a unit re-labels its mission in place. Under Defend, the envelope is measured from the unit’s station — its patrol center, its held point, its protected unit — and a pursuit that leads beyond it is broken off. Two exceptions harden the leash: a hostile at point-blank range is engaged regardless of it, and a fast inbound whose closest approach falls inside the station is not released at the boundary — the leash yields to closing geometry, not to distance alone.

The reaction envelope — the range at which a unit reacts is derived, not set. A platform with ready weapons reacts out to the reach of the weapons that can service the target, judged per target class — a drone armed only against surface ships does not divert for an aircraft it cannot touch — and capped by the standoff-fire ceiling. A platform with no serviceable weapon — unarmed, expended, or itself a one-way weapon — defends itself at point-blank range only. The envelope breathes with the magazine: a launcher that expends its last round contracts to point-blank on the spot. The evade reaction is banded the same way from the platform’s own performance: flight begins when a threat closes inside the inner distance and the interrupted task resumes only once it is beyond the outer, the margin between them scaled to what the platform can traverse — so the reaction does not oscillate at the boundary.

Fire control (ROE) — which contacts the unit may engage, displayed as HOLD / TIGHT / FREE:

Engage Unknown trades identification discipline for reaction time. Against an adversary who hides among neutral traffic it invites engagements that cannot be taken back; against a sea-skimming missile it is the difference between a kill and a hit on the carrier.

ROE governs weapons, not survival. A hostile contact is treated as a danger to evade under every ROE, Hold Fire included; an unidentified contact is treated as a danger only when ROE already permits engaging it.

Weapon release (RMAX / NEZ) — when a firing solution is taken:

RMAX takes the earliest shot and the most shots; a target that turns away at speed can outrun the weapon’s remaining flyout, and the round is wasted. NEZ holds the same shot until escape is no longer kinematically possible — it only ever withholds shots RMAX would take, trading volume of fire for certainty of arrival.

Emissions — Radiate or Silent, per the EMCON mechanics covered in Sensors. Doctrine carries the emission state so that a launched group comes off the deck with its emission posture already decided.

Auto RTB — whether the unit turns for home on its own when it can no longer contribute: when fuel runs low (see Endurance and Logistics), and when an engaged group has expended all weapons (see Weapons Employment). With Auto RTB withheld, the unit holds and waits for recall.

Doctrine Gates

When a unit reaches an engagement autonomously — through its ambient scan, a patrol reaction, or a screen trigger — doctrine is enforced before any weapon moves, and a withheld engagement is reported on the tactical display as HOLD FIRE with the reason:

An engagement ordered by the operator carries authority that an autonomous one does not: it bypasses these gates. A platform ordered to attack will attack, regardless of its standing rules. Doctrine constrains the machine, not the operator.

Threat Reflexes

Three warnings cut through the mission whatever the unit is doing: a hostile fire-control lock, a weapon bearing down the unit’s own line, and an inbound missile. A locked unit under Evade breaks immediately; under Defend it breaks only if it has nothing to answer with; under Pursue it presses the attack. A weapon bearing on the unit is always answered with evasion. An inbound missile is engaged when the unit can fight it and evaded when it cannot. In every case the interrupted mission is retained and resumes when the threat clears.

The Ambient Scan

Any deployed platform that is not already engaged — idle, in transit, or on station — continuously scans the team contact picture within its reaction envelope; the carrier alone keeps its sensors on the picture without diverting itself into engagements. ROE filters which affiliations qualify; posture decides the reaction. When several units could take the same contact, effort is distributed force-wide: no contact draws a second defender while another qualifying threat has none; the most imminent threats are covered first; and a contact already engaged at its capacity — two platforms and one committed weapon for an ordinary contact; eight platforms and unrestricted fires for a command ship — is passed over. The result is that a saturation raid is met by a distributed response rather than every defender converging on the lead contact.

Deck Operations

The carrier is the force’s launch, recovery, and servicing facility, and deck throughput is a hard operational constraint. Every airframe in the fight passed through a deck cycle to get there, and must pass through another to refuel and rearm.

Facilities and Pipelines

Each launch and recovery facility is a pipeline of timed phases. A vehicle entering the pipeline occupies each phase in turn; the facility’s character is set by whether its phases are serial (one occupant per phase — a conveyor) or parallel (multiple occupants move through together):

The serial facilities are the bottleneck. An aviation deck moves one airframe per phase: while a drone rides the elevator, the next waits in the hangar. A reversible facility operates in one direction at a time — a deck cycling launches is not simultaneously recovering, and the operator’s launch schedule and recovery demand contend for the same conveyor. Queued launches can be reprioritized, and a pending launch can be canceled even after it has entered the pipeline; a canceled launch returns the vehicle to stowage.

The parallel facilities exist precisely because weapons cannot wait for a conveyor: a VLS salvo or torpedo shot proceeds at volley pace regardless of what the flight deck is doing.

Launch

A launch commits one or more stowed vehicles to a facility pipeline as a group — the first named vehicle becomes the leader. The launch carries the group’s complete tactical configuration so that no follow-up orders are needed:

• an immediate intent — clear the deck and loiter, engage a designated contact, or follow a designated unit;
• an initial mission, entered automatically once the group finishes forming up, with an optional rendezvous waypoint;
• the group’s doctrine and formation;
• for weapons, a trajectory profile (see Weapons Employment).

A launched group is therefore productive from the moment it clears the deck: a screen launched as a screen, a strike launched against its target.

Recovery

A recovering platform proceeds to its assigned carrier and enters the recovery flow for its facility. Aircraft fly a racetrack holding pattern near the carrier and are cleared in turn — fixed-wing airframes descend on a glide approach to the deck; rotary-wing airframes descend overhead. Surface and subsurface vehicles trail the carrier astern, then close for well-deck entry.

Deck capacity is enforced. When the pipeline is full, additional recoveries hold — the display reports holding — deck full. A platform that chose its own recovery carrier (an automatic low-fuel return) will divert from a full deck to another compatible carrier with room. A recovery directed by the operator to a specific carrier is pinned to it and holds until that deck clears: the system assumes the operator named that carrier for a reason.

Servicing

A recovered vehicle is struck below and serviced in sequence — refueling from the carrier’s bunkers, then rearming from the carrier’s magazine inventory — before reporting Ready for relaunch. Both transfers take time proportional to the quantity moved, and refueling draws down the carrier’s own fuel stocks. A vehicle can be launched mid-servicing; it departs with whatever fuel and ordnance it has taken on, and the deficit is the operator’s to manage.

stateDiagram-v2
    direction LR
    Ready --> Pipeline : Launch committed
    Pipeline --> Deployed : Clears the deck
    Pipeline --> Ready : Launch canceled
    Deployed --> Recovering : Recovery (RTB)
    Recovering --> Servicing : Struck below
    Servicing --> Ready : Refueled and rearmed
    Servicing --> Pipeline : Launch mid-servicing

    classDef own fill:#062712,stroke:#22c55e,color:#22c55e
classDef enemy fill:#2f0d0d,stroke:#ef4444,color:#ef4444
classDef success fill:#062712,stroke:#22c55e,color:#22c55e
classDef warning fill:#2e2301,stroke:#eab308,color:#eab308
classDef error fill:#2f0d0d,stroke:#ef4444,color:#ef4444
classDef info fill:#282828,stroke:#cccccc,color:#cccccc

    class Ready success
    class Pipeline warning
    class Recovering warning
    class Servicing warning
    class Deployed info

The cycle, not the inventory, is the true measure of combat power. Twelve airframes with a single serial deck deliver sorties at the deck’s pace; the operator who launches everything at once has also scheduled everything to come home at once.

Weapons Employment

Delivery Models

Two kinds of platform deliver warheads:

• Expendable weapons — missiles and torpedoes. The vehicle is the warhead; the flight is one-way. Launched from VLS cells, torpedo tubes, or the air-launch racks of a carrying platform.
• Launch platforms — armed drones carrying stowed weapons. The platform closes to employment range, releases weapons through its own launch pipeline, observes the result, and can re-attack or return to rearm.

For warhead and chassis specifications, see the Platform Reference.

The Engagement Sequence

An engagement against a contact proceeds through a fixed sequence, reported on the tactical display as the engagement phase:

flowchart LR
    P["Pursuing\n(closing / standoff)"]:::info --> L["Launching\n(weapon in pipeline)"]:::info --> C["Committed\n(weapon airborne)"]:::info --> D["Detonation\nat CPA"]:::info --> B["Awaiting BDA"]:::warning
    B -- "Independent coverage\nconfirms target gone" --> K["Probably Destroyed\n(engagement complete)"]:::success
    B -- "No independent\ncoverage" --> U["Uncertain\n(search orbit around\nlast known position)"]:::warning
    U -- "Target re-detected:\nre-engage" --> P
    D -- "All weapons expended\n(Auto RTB)" --> R["Weapons out\n(return to base\nto rearm)"]:::info

    classDef own fill:#062712,stroke:#22c55e,color:#22c55e
classDef enemy fill:#2f0d0d,stroke:#ef4444,color:#ef4444
classDef success fill:#062712,stroke:#22c55e,color:#22c55e
classDef warning fill:#2e2301,stroke:#eab308,color:#eab308
classDef error fill:#2f0d0d,stroke:#ef4444,color:#ef4444
classDef info fill:#282828,stroke:#cccccc,color:#cccccc

Pursuing. The platform closes on the contact’s track. A launch platform does not fly to the target — it flies to a standoff range and holds there while its weapons do the closing. The standoff distance is regulated continuously against track quality: a strong, reliably-held track lets the platform stand off farther; a weak track pulls it in to preserve custody. The ceiling is the weapon’s own reach.

Launching. When the target is within weapon range, ammunition is available, and the target is not already at its engagement capacity, a weapon is committed to the launch pipeline.

Committed. The weapon is airborne against the contact. The launching platform maintains its standoff and holds custody of the track while the weapon flies out.

Detonation. The weapon detonates at its CPA against the target — the closest point its trajectory achieves. Lethality falls off with miss distance: full warhead effect at zero miss, decreasing to nothing at the edge of the warhead’s lethal radius. A pass outside the lethal radius is a clean miss. Only the engaged contact is affected — there is no area effect against bystanders.

Trajectory Profiles

An expendable weapon shapes its flight path according to a profile chosen at launch (or carried as the design default):

The profile decision is the sensor tradeoff in miniature: terrain-following trades range for surprise, lofting trades surprise for range. See Sea Clutter and The Horizon for the detection mechanics being exploited.

Sensor Custody and the Kill Chain

Weapons are aimed at tracks, not at truth. An engagement names its target by track code, and the weapon homes on the track’s estimated position for as long as the track lives. If sensor custody is lost mid-flight, the weapon dead-reckons on the last known position — against a maneuvering target, a stale track decays into a miss. If the track has expired entirely by the time the weapon arrives, the engagement resolves as a miss regardless of where the target actually is.

The operational consequence: fires are only as good as the sensor picture sustaining them. A launch platform that goes silent after firing, or a supporting sensor platform that loses the target behind terrain, has disarmed its own weapon in flight. Keeping a sensor on the target through weapon flyout is part of the engagement, not an accessory to it.

Battle Damage Assessment

A detonation does not announce its result. The targeted track is marked awaiting BDA, and the assessment is made by independent sensor coverage — sensors other than the weapon’s own seeker, which is destroyed in the detonation. If independent coverage confirms the target gone, the track is assessed Probably Destroyed and the engagement completes. Without independent coverage the assessment is Uncertain: the engaging platform searches an expanding orbit around the last known position to re-acquire or confirm. A target re-detected after engagement is re-engaged.

BDA outcomes are displayed as overlay decorations on the contact symbol — see Symbology for the markings.

With Auto RTB in effect, a platform that has expended all weapons breaks off and returns to base to rearm (weapons out — RTB); a group breaks off only when every surviving armed member is spent and no volley remains in flight. With Auto RTB withheld, the spent unit holds on station and waits for the operator’s recall.

Endurance and Logistics

Fuel

Fuel burn is proportional to thrust demand. A platform cruising at partial throttle burns substantially less than one running at maximum speed; the transit profile is a tradeoff between time-on-station and time-to-station. Every deployed platform’s fuel state is visible on the tactical display.

Bingo Fuel and Automatic Return

Once a platform’s fuel drops below a low-fuel threshold, the system begins comparing its remaining range against the distance to the nearest compatible recovery facility, with margin to spare. When remaining range no longer covers the return leg with that margin, the platform is at bingo fuel: the state latches and is cleared only by refueling. With Auto RTB in effect — the default for any platform that is not itself a warhead — a bingo platform abandons its mission and turns for home (bingo fuel — RTB). An engagement is likewise abandoned when fuel can no longer support it (intercept aborted — fuel).

Assigning a new mission to a platform that has turned for home cancels the recovery and withdraws its automatic-return authority for the remainder of the sortie — the system does not fight the operator for the platform. From that point the fuel state is the operator’s responsibility alone.

A platform that exhausts its fuel does not vanish from the air immediately: propulsion fails and onboard systems run on battery reserve. An airborne platform without thrust is lost on surface impact; any platform is lost when the reserve depletes. The reserve interval is brief and is not an endurance margin to be planned against.

Carrier Stocks and Procurement

Servicing draws on the carrier’s finite stocks: refueling depletes bunker fuel, rearming depletes magazine inventory. Stocks are replenished through resupply deliveries ordered against the force’s operating funds, which accrue over the course of the engagement; replacement airframes are produced the same way, with production time scaling with the cost of the design. A fight can therefore be lost logistically long before it is lost tactically — a carrier with an empty bunker is a carrier whose air wing is on a countdown.

The carrier’s INV view presents one total for each munition. The total includes rounds in carrier stores, loaded magazines on the carrier and its stowed platforms, and active transfers.

A queued movement remains shown in, and counted from, its physical source until the deck crew starts it; it is not an extra round. An active movement remains included while the deck crew moves it.

The Purchase Queue accepts whole quantities from 1 through 99. A quantity creates that many separate ordinary orders, each independently visible in the queue and subject to normal construction, delivery, cancellation, and refund behavior.

BUY ONE MORE adds one ordinary order for the inspected carrier. It does not refill to a target count, alter the loadout manifest, or estimate a restock target.

The signature decisions of this system are logistical: when to cycle the deck, how much fuel to spend on transit speed, whether the next sortie launches now with partial fuel or later with full tanks. Firepower decides engagements; the deck cycle decides campaigns.

Platform Reference

Specifications for every chassis and component system in the DRONECOM inventory. Each platform and sensor has a full datasheet in the sections below; the tables on this page are a comparison index. See the Designator Prefixes section of the glossary for an explanation of naming conventions.

Chassis

Sensors

A range shown with a trailing + means the receiver holds that reference platform anywhere in the operating area — the figure is the width of the area, not a limit of the equipment.

Warheads

Chassis

Hull specifications for every platform in the inventory, grouped by operating domain and ordered by procurement cost. Payload budget is the weight available for sensors, ordnance and carried munitions after structure and fuel.

Maximum speed and maximum range are bare-hull figures. A loaded platform is slower, and a platform that spends part of its endurance on station covers less ground than its maximum range suggests.

Fixed-Wing Platforms

MQ-60 Swift

Fixed-wing · Air · Expendable · $337K

RQ-10 Jackal

Fixed-wing · Air · Recoverable · $2M

MQ-450 Panther

Fixed-wing · Air · Recoverable · $6M

MQ-160 Falcon

Fixed-wing · Air · Recoverable · $6M

MQ-220 Lynx

Fixed-wing · Air · Recoverable · $7M

Rotary-Wing Platforms

MH-180 Hornet

Rotary-wing · Helicopter · Recoverable · $5M

Missiles

M-100 Stiletto

Fixed-wing · Missile · Expendable · $180K

M-250 Claymore

Fixed-wing · Missile · Expendable · $197K

M-400 Pike

Fixed-wing · Missile · Expendable · $400K

M-300 Sabre

Fixed-wing · Missile · Expendable · $486K

M-500 Cutlass

Fixed-wing · Missile · Expendable · $936K

Surface Ships

USV-80 Riptide

Surface vessel · Surface · Recoverable · $6M

AFV-100 Driftnet

Surface vessel · Surface · Independent · $7M

ALT-100 Boreal

Surface vessel · Surface · Independent · $13M

ACS-100 Meridian

Surface vessel · Surface · Independent · $13M

USV-200 Surge

Surface vessel · Surface · Recoverable · $18M

Command Ships

AFT-100 Cannery

Surface vessel · Command ship · Independent · $9M

CV-1000 Bastion

Surface vessel · Command ship · Independent · $112M

CV-3000 Citadel

Surface vessel · Command ship · Independent · $146M

Submarines

SS-400 Phantom

Submarine · Subsurface · Recoverable · $18M

SS-800 Specter

Submarine · Subsurface · Recoverable · $20M

Torpedoes

MK-30 Mako

Submarine · Torpedo · Expendable · $156K

MK-55 Hammerhead

Submarine · Torpedo · Expendable · $211K

Sensors

Detection equipment, grouped by propagation medium. A component with more than one detection mode carries one specification group per mode.

Representative detection ranges are free-space figures against a named reference platform. Sensors covers the propagation effects — horizon, clutter, Doppler notching, thermocline and convergence zones — that reduce them in practice.

Electromagnetic Sensors

AN/AAS-20 Pointer

Infrared · $86K

AN/APS-150 Altair

Radar · $142K

AN/APG-15 Setter

Radar · $230K

AN/APG-17 Pointer

Radar · $242K

AN/APS-320 Deneb

Radar · $288K

AN/ALR-60 Bloodhound

RWR · $351K

AN/AAQ-55 Screech

Infrared / Visual · $487K

AN/SAY-25 Lookout

Infrared / Visual · $487K

AN/ALR-20 Asp

RWR · $727K

AN/AAQ-80 Barred

Infrared / Visual · $774K

AN/SPS-90 Vigil

Radar · $1M

AN/APS-440 Polaris

Radar · $1M

AN/APS-660 Vega

Radar · $2M

AN/SPY-310 Sirius

Radar · $2M

AN/ALR-90 Viper

RWR · $4M

AN/SLR-40 Cobra

RWR · $4M

Acoustic Sensors

AN/SQR-45 Lamprey

Passive Sonar · $67K

FF-100 Trawlfinder

Active Sonar · $116K

AN/SQS-30 Barracuda

Active Sonar · $1M

AN/SQS-40 Dolphin

Passive Sonar / Active Sonar · $3M

AN/SQR-70 Narwhal

Passive Sonar · $13M