Maritime Domain Awareness.

The problem an exclusive economic zone creates

A coastal state’s exclusive economic zone commonly extends 200 nautical miles and can be several times the area of its land territory. It is policed, in most cases, by a handful of patrol vessels.

A patrol boat sees to its horizon — a few tens of miles at best. Sweeping an area that size by sailing across it is arithmetically hopeless, and it is why maritime enforcement without an air component consists largely of responding to reports after the fact.

The purpose of an MDA program is to invert that: know where to send the vessel before it sails.

Why cooperative tracking is not enough

Most large merchant vessels transmit their identity and position continuously, and fishing fleets in many jurisdictions carry mandated monitoring systems. That data is cheap, wide-area and genuinely useful — it accounts for the large majority of legitimate traffic.

Its limitation is definitional. A cooperative system reports vessels that choose to cooperate. Anything conducting illegal fishing, smuggling or unauthorized transhipment simply switches the transmitter off, or spoofs it. So the cooperative picture is best understood as a filter: it tells you what is accounted for, and everything else is what an MDA program exists to find.

How the picture is assembled

Coastal radar covers approaches to ports and chokepoints continuously, and is inexpensive to run once installed. Its range is limited by the horizon and by siting.

Airborne search covers the open zone. A maritime radar sweeps a very large area per sortie and produces contacts; an electro-optical turret is then cued onto the contacts that do not correlate with cooperative reporting, to classify them. This detect-then-identify pattern is the core of the mission and the reason both sensors are carried.

Surface units act. They are the expensive, slow layer and should only be committed against a classified contact with a reason attached.

Fusion correlates all of it, and is where the value is created or lost. A contact that is radar-detected, optically classified and cross-checked against cooperative data is actionable. The same contact in three separate systems is three unrelated observations.

What usually goes wrong

Not sensors. Authorities.

Maritime enforcement almost always crosses a navy, a coast guard, a fisheries authority, a customs service and sometimes a police maritime unit. Each has its own legal powers, its own reporting chain and frequently its own incompatible system.

The recurring failure is that a detection is made by an organization with no power to board, and passed to one that does not receive it in time or does not trust it. The program produces excellent detection statistics and very few prosecutions. Fixing this is a written-agreement problem — who tasks the aircraft, who receives the product, who boards, and what happens when two agencies want the same asset on the same day — and it is worth settling before anything flies.

Choosing the aircraft

Maritime search rewards endurance and a radar, which points at the larger types. But persistence over the near approaches, flown daily from a coastal strip, is often more valuable than a longer sortie flown twice a week, and that points at the cheaper end.

The honest answer is usually a mix: a long-endurance type such as the King Air 350 for open-zone sweeps, and a Caravan or PC-12 working the approaches and the ports at much lower cost per hour. Which balance fits depends on where the traffic actually is, which is the first thing a capability assessment establishes.

Measuring it honestly

Hours flown and contacts detected are inputs. The measures that tell you whether the program works are how many detections were classified, how many classified contacts were intercepted, and how many interceptions resulted in an enforcement action. Programs that report the first pair and not the second are usually collecting well and enforcing badly.