From NTDS to JADC2: The Unsolved Problems of Multi-Sensor Fusion

Command, Control & Communications C4ISR & Sensor Fusion

What AI Cannot Fix

The Naval Tactical Data System's most intractable operational problems — sensor alignment bias, dynamic navigation error, and multi-sensor track association failure — were substantially ameliorated by the E-2C/D Hawkeye's network-derived registration and the Cooperative Engagement Capability's architectural innovation of distributing raw sensor measurements rather than processed tracks. Neither fully solved the problem, and neither transfers completely to the GPS-denied, multi-domain, multi-service environment that JADC2 requires. The AI system at the top of the processing chain receives a track picture corrupted by errors it cannot see, and generates confident engagement recommendations it cannot qualify.

Stephen L. Pendergast, LT USNR, IEEE Sr. Member (Ret.)  |  Senior Engineer Scientist July 2026 

Sources: GAO, ETHW, IATA, FAA, OPSGROUP, USNI, CSBA, CRS, DOT&E

BLUF — Bottom Line Up Front

The U.S. Navy's Naval Tactical Data System, first deployed in 1961, pioneered multi-ship sensor fusion and encountered three fundamental problems that were never mathematically solved: data association ambiguity in dense contact environments, dynamic sensor alignment bias in azimuth and bearing, and inter-ship coordinate frame misalignment from navigation error. Two intermediate-generation systems substantially ameliorated these problems: the E-2C/D Hawkeye's network-derived registration through the Link 16 Joint Units network, which provided a geometrically distinct high-altitude sensor node enabling inter-platform bias estimation; and the Cooperative Engagement Capability — conceived by Johns Hopkins University Applied Physics Laboratory — which addressed the NTDS double-track problem at its architectural root by distributing unfiltered radar measurements rather than processed tracks, employing Extended Kalman Filter multi-sensor tracking, and implementing precision gridlock for sensor coordinate frame alignment. Together, these systems brought the naval battle group's air defense sensor fusion to fire-control quality within the GPS-available, line-of-sight battle group environment. JADC2 — the Joint All-Domain Command and Control system receiving $1.4 billion or more annually — must extend this solution across all services, all domains, and coalition partners in a GPS-denied peer conflict environment. GPS spoofing and jamming have increased 500% in 2024 alone by some measures, restoring the pre-GPS navigation errors that CEC's gridlock suppressed for airborne sensor contributors. The AI systems now being integrated into JADC2's sensor-to-shooter loops receive a track picture that may be systematically corrupted by these errors — none of which is visible in the track data the AI processes, and none of which current AI systems are designed or tested to detect.

In 1962, the prospective commanding officers of new guided missile frigates — informed that the Naval Tactical Data System was going to be built into their ships — came to the NTDS project office to deliver a message. As the Engineering and Technology History Wiki records it: "No damned computer was going to tell them what to do. For sure, no damned computer was going to fire their nuclear tipped guided missiles."¹ Secretary of the Navy John Connally and Chief of Naval Operations Admiral Arleigh Burke were pushing the NTDS project office to accomplish in five years what would normally take thirteen. They prevailed. The system was fielded. And it immediately encountered the fundamental technical problems that the commanding officers' instincts, if not their stated objections, had correctly anticipated: in a real operational environment with multiple ships, multiple sensors, noisy measurements, and dynamic navigation errors, building a common tactical picture that was reliable enough to act on was harder than any of the system's architects had projected.

Sixty-five years later, the Department of Defense is spending over $1.4 billion annually on JADC2 — Joint All-Domain Command and Control — a program whose ambition is to do what NTDS did for the naval task force, but across all military services, all domains, and in coalition with allies, connected through AI systems that transform sensor data into engagement decisions at machine speed. The commanding officers of 2026 are not objecting. They are requesting the capability. But the technical problems that made NTDS harder than expected — multi-sensor data association in dense environments, dynamic sensor alignment bias, and coordinate frame misalignment from navigation error — have not been solved in the intervening six decades. They have been masked by GPS, and they are about to be unmasked by the adversary.

NTDS: The Original Experiment in Multi-Ship Sensor Fusion

The Naval Tactical Data System was developed beginning in 1956, with major contracts awarded to Sperry Rand's UNIVAC division for the AN/UYK computing systems, Collins Radio for communications, and Hughes Aircraft for displays and radar integration.² The system achieved its first operational deployment in October 1961 aboard USS Oriskany (CVA-34) and USS King (DLG-10), connected by the AN/USQ-55 data link that would evolve into Link 11.³ The vision was straightforward in concept: each ship's sensors would contribute to a common tactical picture shared across the task force, each ship could see what every other ship saw, and weapons assignment could be coordinated across multiple shooters against a common threat picture.

The operational reality was more complex. As the Military History wiki documents, NTDS's two major problems were immediately apparent: "each ship had its own view of the battlespace, independent of the rest of the ships in the task force" — and the system designed to create a common view immediately encountered the technical barriers to doing so reliably.⁴ Those barriers were not software bugs or hardware failures. They were fundamental properties of the sensor fusion problem that the system architects had not fully anticipated.

NTDS's combat debut in Vietnam — aboard PIRAZ (Positive Identification Radar Advisory Zone) ships in the Gulf of Tonkin — demonstrated both its value and its limitations. The PIRAZ ships provided air traffic control, threat warning, and search and rescue coordination for strike packages operating over North Vietnam, crediting NTDS with saving many pilots' lives through precise radar coverage and data link coordination.⁵ But the operational environment also revealed the depth of the multi-sensor correlation problem. Multiple radar systems on different ships, operating with different measurement biases, different navigation errors, and different scan rates, produced contact tracks that were difficult to merge into a coherent common picture. The same physical aircraft appeared as multiple contacts in different ships' track files. The association algorithms of the era — rule-based correlation on range, bearing, and speed — produced systematic errors when contacts were closely spaced, when sensors disagreed, or when navigation biases separated the coordinate frames of different ships' measurements.

The Three Fundamental Problems

I. The Data Association Problem

The data association problem — determining which sensor measurement at the current scan corresponds to which previously established track — is mathematically equivalent to an assignment problem in combinatorial optimization. In a sparse contact environment with well-separated targets and low sensor noise, it is tractable. In the contact densities encountered in the outer air battle, with multiple threat aircraft, friendly strike packages, tankers, and escorting fighters simultaneously in the same radar coverage volume, it is not.

The Mahalanobis distance — the normalized statistical distance between a measurement and a track prediction, accounting for the combined uncertainty from process noise and measurement noise — provides the correct association metric under the assumption that measurement errors are zero-mean and Gaussian. It was the state-of-the-practice approach for track-to-measurement association and was incorporated into NTDS-derived systems through the 1970s, 1980s, and 1990s. Applied to the Linear Assignment Problem via the Hungarian algorithm, it provides the globally optimal one-to-one assignment of measurements to tracks under the Gaussian noise assumption.

Even optimal assignment leaves residual errors in three conditions that operational environments reliably produce. First, when two targets are separated by less than the sensor resolution cell, their measurements merge or cross-contaminate and no association algorithm can correctly assign the measurements independently. Second, when two tracks cross in the observation space, the post-crossing assignment is ambiguous — and the optimal algorithm, by choosing one assignment, is wrong half the time. Track crossing produces the "track swap" pathology, where IFF history, ESM emitter identification, and tactical attributes are assigned to the wrong physical object after the crossing. Third, when targets maneuver outside the assumed motion model, the track prediction diverges from the actual position, increasing the Mahalanobis distance to the correct measurement and potentially causing the track to associate with a nearby false alarm instead.

Joint Probabilistic Data Association, Bar-Shalom and Fortmann's theoretically optimal extension of the Kalman filter to uncertain association environments, addressed the crossing track problem by replacing hard association with probabilistic soft assignment weighted by posterior association probabilities.⁶ It was evaluated seriously for NTDS-derived combat direction systems in the 1990s. Its computational load was the disqualifying factor: in dense contact environments the joint event enumeration is equivalent to computing the permanent of a matrix — a #P-complete problem that scales factorially with cluster size. JPDA delivered optimal decisions too slowly for real-time combat direction system operation during high-intensity threat scenarios. The computational intractability was not a hardware limitation that Moore's Law would resolve — it is a mathematical property of the problem structure that makes exact optimal association computationally intractable in exactly the conditions where it matters most.

II. The Sensor Alignment and Azimuth Bias Problem

Radar azimuth measurement is subject to systematic biases that the Mahalanobis distance metric cannot correctly handle, because the metric assumes zero-mean noise and a bias by definition has a non-zero mean. The sources of azimuth bias in shipboard radar systems include: antenna mount azimuth encoder error, thermal effects on the antenna structure, antenna pedestal leveling error as the ship rolls and pitches, and for AESA systems the phase shifter calibration errors that accumulate with component aging and thermal cycling. These biases are dynamic — they change with temperature, operational conditions, and equipment state — and they are not directly observable from the radar's own measurements.

A 0.5° azimuth bias at 50 nautical miles produces a cross-range position error of nearly a nautical mile. If the Mahalanobis distance metric's measurement noise covariance R characterizes the random radar measurement error as having a standard deviation of 200 feet in cross-range, a bias-induced error of 4,000 feet appears as a 20-sigma event — far outside any reasonable gating threshold. The association algorithm correctly classifies this as a non-association, producing separate track files for what is a single physical contact observed by two differently-biased sensors. The "double track" problem that plagued NTDS operations throughout its history — the same aircraft appearing as two separate contacts in the common tactical picture — was in large part a manifestation of uncalibrated inter-sensor azimuth biases interacting with an association algorithm that had no mechanism to account for systematic measurement offsets.

III. The Navigation Error and Coordinate Frame Misalignment Problem

In the pre-GPS era, shipboard navigation rested on inertial navigation systems whose dominant error source was gyro drift — on the order of 0.01 degrees per hour for quality 1970s-era floating gyroscopes, integrating to approximately one nautical mile of position error per hour between celestial or LORAN fixes. When Ship A with a 1 nautical mile navigation error and Ship B with a 1.5 nautical mile navigation error both tracked the same contact, their measurements of that contact's position were expressed in coordinate frames offset by the vector difference of their navigation errors — up to 2.5 nautical miles in an unknown direction. At the contact ranges relevant to the outer air battle, this inter-ship coordinate frame misalignment was larger than the random sensor measurement noise by factors of ten or more, systematically corrupting every inter-ship association attempt regardless of algorithmic sophistication.

The track registration problem — estimating the inter-ship alignment parameters from the statistical properties of jointly observed contacts — requires simultaneously solving for both the alignment and the association, creating a bootstrapping problem: correct registration requires correct association, and correct association requires correct registration. Expectation-Maximization approaches that iterate between soft association and registration estimation handle this correctly in principle but introduce additional computational load and convergence uncertainty in sparse contact environments where the estimation is ill-conditioned.

What GPS Changed — and What It Left Unchanged

GPS achieving Full Operational Capability in 1995 was a transformative event for the navigation error problem. Modern ring laser gyroscope INS systems, achieving drift rates on the order of 0.0001 degrees per hour, accumulate position errors of hundreds of meters rather than nautical miles between GPS updates spaced days apart. The coordinate frame misalignment that dominated inter-ship association failures in NTDS — the systematic position offsets that no association algorithm could overcome — became smaller than the random sensor measurement noise with GPS-quality navigation. The double-track problem caused by navigation error largely disappeared from the surface ship common picture after GPS became standard.

For shipboard platforms, GPS denial is geometrically bounded by the line-of-sight horizon. A surface-based jammer at 10 meters above sea level has a geometric horizon of approximately 7 nautical miles to a ship's GPS antenna at 20 meters. GPS satellite signals arrive at high elevation angles where ship GPS antennas have their maximum gain, while jamming signals arrive near the horizon where antenna discrimination reduces effective jammer power. Modern ring laser and fiber optic gyro IMUs, achieving drift rates orders of magnitude better than 1970s SINS, require GPS updates only on the order of daily time scales to maintain navigation quality adequate for inter-ship track correlation. Ships close to hostile coasts face more jamming exposure, but the geometry substantially limits shipboard GPS vulnerability compared to airborne platforms.⁷

What GPS did not change was the azimuth bias problem. The sensor-to-platform lever-arm calibration — the precise alignment of each radar's phase center or antenna boresight to the ship's navigation reference frame — remains subject to measurement error at installation and subsequent change from structural flexure, thermal cycling, and equipment aging between calibration events. For a carrier operating at high tempo flight operations, flight deck structural flexure relative to the ship's keel-mounted IMU produces a dynamic sensor-to-platform misalignment that GPS-quality navigation cannot correct because it occurs within the inertial measurement interval. The AESA phased array calibration table that maps commanded phase shifts to actual beam directions degrades with component aging and thermal cycling between depot calibration events. These systematic sensor errors — smaller in modern systems than in 1960s hardware, but not zero — remain invisible to the association algorithm's Mahalanobis distance metric.

The RF Infrastructure Constraint: Why Data Link Architecture Determines Fusion Quality

The sensor fusion architecture of any tactical network is not primarily a software problem. It is a physics and RF engineering problem whose solution space is bounded by what the data link infrastructure can carry between platforms. No algorithm — not Bar-Shalom's EKF, not JPDA, and not any current or foreseeable AI system — can fuse data that the link does not deliver. The evolution from NTDS through CEC to JADC2 is, at its foundation, a succession of data link architectures, each enabling different quality of fusion and each imposing different scalability constraints. Understanding why JADC2 cannot achieve CEC-quality fusion across service boundaries requires understanding precisely what each link generation can and cannot carry.

Link 11: Track Distribution at the Speed of HF

Link 11 (TADIL-A, MIL-STD-6011) defined the NTDS data link standard from the late 1950s through the GPS era. Its architecture reflects the technology available when Ralph Benjamin designed it at the British Admiralty Surface Weapons Establishment: a netted, half-duplex system in which a Net Control Station (NCS) polls each participating unit sequentially in Roll Call mode, each unit transmitting its track messages in its assigned time slot before the NCS polls the next. The protocol operates on two propagation paths with dramatically different characteristics.

The UHF path (225–400 MHz) provides ship-to-ship range of 20 to 30 nautical miles and ship-to-air range of approximately 150 nautical miles, at a data rate of 2,250 bits per second. The HF path (2–30 MHz) uses ground wave propagation to achieve ranges of up to 300 nautical miles for surface-to-surface communications and sky wave propagation for ranges up to 1,000 nautical miles — entirely beyond line of sight, without satellite dependency. The HF path runs at 1,364 bits per second. Individual packets are 30 bits long: 6 bits of error correction and 24 bits of encrypted tactical payload, barely enough to encode a track position, velocity, and identity classification.

The HF surface wave capability was Link 11's most strategically important feature — and the one most completely abandoned in Link 16. A fleet operating with GPS denied and communications satellites jammed or destroyed retains Link 11's HF surface wave BLOS capability without any external infrastructure dependency. The Royal Australian Navy's analysis of the transition from Link 11 to Link 22 notes explicitly: "considering contemporary operations are conducted at increasingly greater ranges and the prospect of operating within a satellite denied environment is also becoming more likely, the use of any TDL that provides for a BLOS capability is invaluable for early warning."^9a Link 11 provided that capability natively, from the ionosphere, with no satellite required.

What Link 11 could not provide was the bandwidth to carry anything other than processed tracks. At 1,364 to 2,250 bits per second, a Link 11 network carrying tracks for 50 contacts across a 20-ship task force operates with update intervals measured in seconds and data compression that strips away almost everything except position and identity. The sensor measurement data, the track quality information, the association history — all discarded before the link, never present in what crosses it. This is the architectural root of the NTDS dual-track problem: the link was only wide enough for the outputs of each ship's tracking processor, not for the inputs.

Link 16: Scale at the Cost of HF and Fixed Capacity

Link 16 (TADIL-J, JTIDS/MIDS, MIL-STD-6016) was designed to overcome Link 11's data rate and jamming resistance limitations. It operates at 960–1,215 MHz (L-band UHF) using frequency-hopping spread spectrum with pseudo-random frequency changes every 13 microseconds — 76,923 hops per second — providing substantially better electronic countermeasures resistance than Link 11's narrowband HF waveform. Typical data rates are 31.6, 57.6, or 115.2 kilobits per second, with the physical waveform capable of exceeding 1 megabit per second in favorable conditions. Link 16 carries J-series messages: structured binary data words encoding track positions, identification, weapons states, and command information. It does not carry raw sensor measurements or dwell data — the message format does not accommodate them.

Link 16's TDMA architecture uses a fixed 12-second frame subdivided into time slots of 7.8125 milliseconds each, with 128 time slots per second total network capacity. Each JTIDS Unit (JU) is assigned specific time slots in a Network Data Load generated by a central net design agency before the mission. The fixed TDMA structure provides deterministic, collision-free access for all participants — but it is pre-planned and static. Adding a new platform mid-mission requires redesigning the NDL and reloading all terminals in the network. Each terminal is limited to a maximum of 128 time slots per second regardless of total network size. Link 16 network capacity is effectively allocated at mission planning time, not adaptively in response to the operational situation. A single Link 16 terminal's maximum throughput is bounded regardless of how many other terminals are operating in the same net.

The critical capability Link 16 sacrificed relative to Link 11 is the HF surface wave BLOS path. Link 16 is a UHF-only system, line of sight only, with no native BLOS propagation mode. The Joint Range Extension Application Protocol (JREAP, MIL-STD-3011) is the only current BLOS extension for Link 16 — and Link 16 via JREAP is the only current joint BLOS tactical data link connecting all services. There is no alternative. JREAP embeds J-series messages inside IP packets over satellite relay links. SAIC alone has fielded over 1,700 JRE systems to DoD, NATO, and allied countries^9b — making JREAP simultaneously the most widely deployed joint BLOS solution and its single critical vulnerability. The satellite infrastructure that JREAP depends upon is what Chinese A2/AD doctrine, Russian EW doctrine, and ASAT operations specifically target as a first-strike priority. Severing JREAP does not merely degrade the joint tactical picture — it eliminates the only BLOS joint data link the U.S. military currently possesses. Joint forces revert to LOS islands, each service operating on its own internal links with no over-the-horizon joint connectivity.

JREAP's latency compounds this concern even when the satellite path is available. Geostationary satellite relay introduces approximately 250–280 milliseconds of one-way propagation delay, producing round-trip latencies of 600–800 milliseconds for JREAP-C TCP/IP implementations before accounting for gateway processing or satellite channel contention. For a target moving at 500 knots — roughly 840 feet per second — a 600-millisecond stale track is already 500 feet from its reported position. JREAP delivers a situational awareness picture, not a fire control quality picture. The AI reasoning layer that processes BLOS JADC2 data through JREAP is processing battle management track data with latency that precludes engagement use, receiving it over a path that peer adversary doctrine is explicitly designed to sever.

The J-Series Format Problem: When the Message Standard Is the Mission

The JREAP satellite dependency is one constraint on the JADC2 inter-service link. A second constraint, equally fundamental and considerably less discussed, is embedded in the J-series message format itself — the data vocabulary that Link 16 speaks. The J-series Binary Object Model (BOM) messages were designed for joint command and control: providing a common operational picture to commanders who need to see where contacts are, what they are, and what is being done about them. They were not designed to carry sensor contact data for multi-platform fusion. The consequences of this design decision, frozen in place by NATO STANAG standardization across decades and dozens of nations, are precisely the wrong architecture for the fusion role that JADC2 assigns them.

When a radar detects a contact, it generates a measurement in the sensor's native coordinate frame: range, azimuth, and elevation, each with its own characteristic measurement uncertainty. A modern shipboard pulse radar measures range with a standard deviation of tens to a few hundred feet along the radial dimension, but measures azimuth with accuracy that translates to cross-range uncertainty of hundreds to thousands of feet at tactically relevant ranges. This creates an asymmetric measurement uncertainty ellipsoid — very precise radially, much less precise in cross-range — whose shape and orientation carry critical information for any downstream fusion algorithm. The Mahalanobis distance metric requires a full measurement covariance matrix to correctly compute statistical distance between measurements and track predictions. Bar-Shalom's EKF requires it to properly propagate and update the track state covariance. Without it, the filter cannot correctly weight measurements from different sensors, cannot correctly characterize its own uncertainty, and cannot produce reliable association decisions.

J-series geographic coordinate encoding destroys this information permanently. Converting the radar's polar measurement to Latitude/Longitude/altitude and encoding it in a J3.2 Air Track message produces a point position in geographic space. The measurement covariance matrix — the direction and magnitude of the radar's measurement uncertainty — does not survive the conversion. What arrives at the receiving platform is a geographic position and a single integer track quality field: a scalar indicator on a small finite scale that replaces a full 3×3 covariance matrix. The receiving fusion algorithm has no way to recover the original measurement geometry. It cannot know that the geographic position is very accurate in one direction and substantially less accurate perpendicular to it, because the J-series format has no field to carry that information. For a Kalman filter, a scalar quality indicator is not a substitute for a covariance matrix. It is noise from a different domain masquerading as precision.

The navigation error embedding makes this worse. The geographic coordinate conversion uses the reporting platform's own navigation solution. Whatever navigation error exists in that platform's position estimate — GPS-quality in benign conditions, potentially miles of IMU drift in a GPS-denied contested environment — is permanently incorporated into the reported geographic position. The receiving platform cannot correct for it, because the J-series message provides no field for the reporting platform's navigation uncertainty. It is a position report without an error budget. In the GPS-denied peer conflict environment, the navigation error embedded in J-series geographic positions from GPS-denied airborne platforms can exceed the tactical significance threshold for engagement decisions — and that error is invisible to every fusion algorithm downstream.

The message capacity allocation compounds the problem. J-series messages devote substantial bit capacity to identification fields that serve command and control but are irrelevant to sensor fusion: environment, platform type, specific type, activity, modifier, amplification, track quality — fields that allow a commander to understand that Contact 47 is an enemy bomber conducting an attack run, and to assign it correctly on the common operational picture. These fields are operationally essential for their intended purpose. For a fusion algorithm attempting to produce a composite track from measurements contributed by multiple sensors, they consume bits that could carry measurement geometry. The J3.2's geographic position quantization was matched to tactical display resolution requirements, not to radar measurement accuracy or fire control quality requirements. A geographic position encoded at Link 16's position resolution provides adequate fidelity for a human operator's situational awareness picture; it does not provide the input precision that a tracking filter requires to correctly compute innovations.

The STANAG Freeze: A Problem Identified in the 1990s, Unresolved Today

This is not a newly discovered limitation. Engineers working on combat direction systems in the early 1990s identified the J-series format's unsuitability for multi-sensor data fusion — the loss of measurement geometry in geographic coordinate conversion, the inadequacy of scalar quality indicators for Kalman filter applications, the navigation error embedding — and anticipated that the standard would be revised to accommodate fusion requirements as the technology matured. It was not. NATO STANAG standardization creates a coordination and interoperability overhead that makes format revision effectively intractable: any change requires renegotiation across dozens of allied nations, firmware modification in thousands of fielded JTIDS/MIDS terminals of multiple variants across multiple services and nations, and software revision in every combat system — shipboard, airborne, ground-based — that generates and consumes J-series messages. After thirty years of this overhead, the J-series format carries geographic coordinate track positions with scalar quality indicators for the same reason NTDS originally carried track positions rather than raw measurements: the data link was designed for command and control, and changing that design after it becomes embedded across an alliance is effectively impossible at any operationally relevant timescale.

The contrast with CEC's Associated Measurement Report format is sharp and directly relevant to the JADC2 AI's input quality. The AMR carries radar dwell data in the sensor's native measurement coordinates — range, bearing, elevation, Doppler — along with the sensor-specific accuracy parameters that allow the receiving Cooperative Engagement Processor to characterize the measurement uncertainty correctly, apply proper sensor weighting in the fusion step, propagate the measurement covariance through the filter update, and produce a composite track whose stated covariance actually represents the geometric measurement uncertainty of all contributing sensors. This is why CEC achieves fire control quality: not because it has more bandwidth, though it does, but because its data format was designed from the outset for sensor fusion rather than command and control display. The CEC architects at JHU/APL understood in the early 1970s what the Link 16 community has not been able to revise in thirty years of knowing it: the message format determines what fusion is possible.

The practical implication for JADC2's AI layer is more severe than the "track-level versus dwell-level" characterization suggests. The AI at the inter-service JADC2 seam does not receive lower-quality contact data — it receives data in a format that was architected for a categorically different function, that has lost the measurement geometry on which correct fusion depends, that carries embedded navigation errors that are invisible and uncorrectable downstream, and whose format is frozen against any revision by the political and operational overhead of NATO standardization. No AI fusion algorithm can reconstruct a measurement covariance matrix from a scalar quality indicator. No algorithm can recover the reporting platform's navigation uncertainty from a geographic position report that doesn't include it. The fundamental fusion information was discarded before the message was composed, not degraded in transit. The JADC2 AI at the inter-service seam is not fusing sensors. It is reconciling command and control pictures whose measurement provenance has been erased.

The Fifth-Generation Data Link Incompatibility

Beyond JREAP's satellite dependency, the joint data link picture is further fragmented by the incompatibility between fifth-generation platforms and everything else. The F-22 Raptor uses the Intra-Flight Data Link (IFDL) — a low-probability-of-intercept, low-probability-of-detection stealth data link incompatible with Link 16, MADL, and every other tactical data link in the joint inventory. The F-35 uses the Multifunction Advanced Data Link (MADL) — a fast-switching narrow-beam directional link similarly incompatible with Link 16 and IFDL. "The problem today is that Link 16, IFDL, and MADL are not compatible."^9c F-22s cannot communicate with any platform outside their own flight. F-35s cannot communicate directly with F-22s or legacy Link 16 aircraft.

The Air Force's 5th-to-4th Generation Gateway program attempts to bridge these incompatibilities. Its first increment has been demonstrated by Boeing, Lockheed Martin, and Northrop Grumman. Its second increment — providing BLOS access to national data services and multi-level security track fusion — remains under development. When functioning, the gateway translates between link formats at the track message level: the F-35's high-quality MADL sensor data becomes a J-series track message at the gateway output, stripped of the measurement-level precision and uncertainty characterization the MADL format encodes. Another track-level seam, at the point where the most capable fifth-generation sensors connect to the joint picture.

The Peer Conflict Scenario: GPS-Denied, Satellite-Jammed, Link-Fragmented

In the Western Pacific peer conflict environment for which JADC2 is designed, simultaneous application of GPS denial, satellite communications jamming, and ASAT operations produces the following joint C2 picture: The Navy CEC battle group operates within its own LOS dwell-level network — intact but isolated beyond its horizon. Air Force 5th-gen platforms operate on IFDL and MADL, connected to legacy Link 16 forces only through a partially-fielded gateway introducing track-level translation seams. Army forces on SADL and VMF are isolated behind their own service link boundaries. The JREAP satellite relay path — the only current joint BLOS data link — is unavailable because the satellite infrastructure is contested. The AI in JADC2's sensor-to-shooter loop receives whatever the surviving LOS fragments can deliver: a fractured, stale, track-level picture with no CEC-quality data outside the Navy battle group, no BLOS joint connectivity, and no mechanism to flag that its inputs reflect a degraded fragmented network rather than a coherent joint tactical picture. The AI cannot know this from its inputs. It generates confident engagement recommendations regardless.

CEC's Data Distribution System: The High-Bandwidth Directional Architecture and Its Limits

CEC's Data Distribution System represents a fundamentally different RF architecture from either Link 11 or Link 16, specifically designed to carry the bandwidth required for dwell-level radar data distribution. The DDS documentation describes it as "a high capacity, jam resistant, directional system providing high data throughput as well as common time and common positional frame of reference."^9b GlobalSecurity.org documentation confirms that CEC's communications system provides "several orders of magnitude in improvement to bandwidth and electronic countermeasures" compared to Link 11 — meaning at minimum tens of megabits per second, sufficient to carry Associated Measurement Reports (AMRs) encoding the raw radar dwell data from participating sensors in near real time.

CEC achieves this bandwidth through directional beamforming antennas at each equipped unit. Units communicate in pairs during short transmit/receive periods through narrow directional signals. The directional antenna concentrates the transmitted power into a narrow beam toward the receiving unit, achieving the signal-to-noise ratio required for high-data-rate transmission without the radiated power that an omnidirectional antenna would require at the same throughput. Frequency-hopping spread spectrum provides jamming resistance. Internal relays ensure that measurement data originating at one platform reaches all other platforms in the network through a chain of pairwise directional links.

This architecture imposes the scalability constraint you have identified as the critical limitation. The directional antenna requirement means each unit must maintain directional link geometry with its neighbors and relay chain. As network size grows, relay chains lengthen, relay latency accumulates, and the time budget available for fire-control-quality data distribution tightens. Each additional relay hop introduces processing and transmission delay that degrades the timeliness of the distributed measurements — and timeliness is not optional when the data is being used for missile engagement. The practical maximum network size for CEC is constrained to approximately a battle force of less than a dozen units. Beyond that scale, the relay chain latency violates the time budget for fire-control-quality composite tracking.

The Grokipedia description of CEC's adversarial vulnerability is directly related to this architecture: directional antennas provide some resilience against jamming by the narrow beam's geometry, but a sophisticated peer adversary with integrated jamming platforms — as the 2024 Chinese military report documents — can target the relay chain specifically, degrading the distribution network by isolating nodes rather than jamming the entire frequency band. Disrupting one relay node in a chain of four breaks the measurement distribution path to all downstream nodes, fragmenting the fire control picture in ways that the network architecture cannot automatically route around because the directional antenna topology constrains routing options.

The Bandwidth-Scale Tradeoff and Its Implication for JADC2

The data link architecture comparison reveals a fundamental engineering tradeoff that no current tactical data link has resolved:

Link	Data Rate	BLOS Without Satellite	Network Scale	Data Quality	Joint (All Services)
Link 11	1,364–2,250 bps	Yes — HF ground wave 300 nm; sky wave 1,000 nm	~50 units; cycle time grows with N	Track-level only	NATO joint standard
Link 16 (LOS)	31.6–115.2 kbps	No native BLOS; UHF LOS only	Many units; pre-planned fixed TDMA capacity	Track-level J-series only	Only current joint standard — all services, NATO
Link 16 via JREAP	Satellite-limited; 600–800ms+ latency	Yes — but satellite-dependent; single point of failure	Extends Link 16 net globally	Track-level; latency precludes fire control use	Only current joint BLOS link — catastrophically vulnerable to ASAT/jamming
MADL (F-35)	High bandwidth directional LPI/LPD	No — LOS only	Small flight groups only	Sensor-quality within MADL net	F-35 only; gateway to Link 16 partially fielded; track-level at gateway output
IFDL (F-22)	High bandwidth stealth LPI/LPD	No — LOS only	F-22 flight internal only	Sensor-quality within IFDL net	F-22 only; incompatible with everything else; no fielded gateway
CEC DDS	Tens of Mbps; sufficient for dwell-level AMRs	No — LOS directional only	<12 units; relay chain latency constrains scale	Dwell-level radar measurements; fire-control quality	Navy battle group only; no Army/Air Force connection
JADC2 Requirement	Sufficient for multi-domain fusion	Yes — essential; peer targets satellite	Hundreds of nodes, all services, coalition	Dwell-level preferred; track-level minimum	All services, all domains, coalition

No current data link satisfies all requirements simultaneously. The JADC2 requirement row has no matching data link row. This is not a gap that software, AI, or fusion algorithm improvement can close. It is a physical layer constraint compounded by a data format constraint: the only current joint BLOS path carries J-series messages whose geographic coordinate encoding discards the measurement geometry essential for proper fusion, whose scalar quality indicators replace measurement covariance matrices, and whose format is frozen by NATO STANAG standardization against revision. The AI that reasons about the BLOS JADC2 picture operates at the mercy of what JREAP can deliver through a satellite infrastructure designed to be taken down, in a data format designed for command and control display rather than sensor fusion.

The Intermediate Generation: E-2C/D Hawkeye and the Cooperative Engagement Capability

The article's narrative would be incomplete — and unfair to sixty years of naval engineering — without acknowledging the intermediate generation of systems that substantially ameliorated the NTDS multi-sensor correlation problems between the GPS transition and the current JADC2 development. Two developments in particular represent the closest the Navy has come to correctly solving the sensor registration and association problems at an architectural level: the E-2C/D Hawkeye's network-derived registration of participating units in the Link 16 network, and the Cooperative Engagement Capability developed by the Johns Hopkins University Applied Physics Laboratory. Both deserve specific technical treatment because JADC2 inherits their achievements and their limitations simultaneously.

The E-2C/D Hawkeye as Registration Node

The E-2 Hawkeye's contribution to the sensor registration problem flows directly from its geometry. A surface ship's radar is limited to line-of-sight contacts — the geometric horizon restricts its coverage to roughly 20 to 30 nautical miles against low-altitude targets at typical mast heights. The E-2, operating at 25,000 feet, extends the radar horizon to approximately 350 nautical miles and provides 360-degree coverage of the airspace above the task force and the surrounding ocean. This altitude advantage is not merely a surveillance benefit — it is a sensor registration enabler.

When the E-2C's Block 2 aircraft received Joint Tactical Information Distribution System terminals and access to the Link 16 network in the 1980s, they became network registration nodes in a specific and technically important sense.^7a The Hawkeye's sensor observes the same contacts that surface ship radars observe, but from a different geometric vantage point at high altitude. The differences in measured contact positions between the E-2's radar and the surface ships' radars contain information about the inter-platform sensor alignment biases — the same registration information that ground-based track registration algorithms tried to extract from joint contact observations. Because the E-2's navigation was IMU-referenced and its radar geometry from altitude provided contact position fixes with a different error structure than surface ship sensors, the network of Link 16 joint units (JUs) could derive registration corrections by comparing E-2 contact positions with surface ship positions of the same contact — the network-derived registration that directly addressed NTDS's inter-ship coordinate frame misalignment problem.

The E-2D Advanced Hawkeye, entering service in 2014 with IOC in October of that year, extended this capability substantially.^7b The AN/APY-9 AESA radar — operating in UHF band specifically to improve detection of low-observable and sea-skimming threats — provides simultaneous tracking of over 3,000 targets. Integration of Cooperative Engagement Capability, Link 16, and Tactical Targeting Network Technology into a single architecture transformed the E-2D from an airborne early warning aircraft into a network-centric sensor fusion node capable of distributing fire-control-quality data across naval and joint forces. In Operation Epic Fury in 2026, E-2D Hawkeyes provided over-the-horizon targeting data to surface ships through CEC, enabling engagements against Iranian missile systems beyond the horizon of the engaging ships' own radars.^7c The E-2D is now, as one analysis noted, assuming expanded theater-level command and control responsibilities in joint operations as the aging E-3 Sentry fleet diminishes — making its sensor registration and fusion role even more critical to the force.

CEC: The Architectural Breakthrough That Link 11 Could Not Achieve

The Cooperative Engagement Capability represents the most technically sophisticated solution the Navy has fielded to the multi-sensor association and registration problems that plagued NTDS. Conceived by the Johns Hopkins University Applied Physics Laboratory in the early 1970s under the Battle Group Anti-Air Warfare Coordination program, developed through at-sea experiments beginning in 1990, entering engineering and manufacturing development in 1995, and achieving first fleet deployment in 1998, CEC addressed the NTDS correlation problem at its architectural root rather than through algorithmic refinement of the same track-distribution architecture.^7d

William D. O'Neil's definitive National Defense University case study on CEC identifies the core architectural departure with precision: "The key to CEC is the ability to move from track telling to transmitting complete radar data, dwell by dwell."^7e A dwell is a single radar look at a target — which may involve multiple pulses at the same beam position, but represents a pre-filter measurement rather than a processed track estimate. Where Link 11 and the NTDS data link architecture distributed track files — position estimates, velocity estimates, and track attributes generated by each ship's individual tracking software after filtering and association decisions had already been made — CEC distributes radar measurement data at the dwell level, before any of these decisions are applied, to all participating units simultaneously. Each CEC-equipped platform then runs identical tracking algorithms on the same dwell data, producing a truly common track rather than attempting to reconcile separately-maintained track files that have accumulated different processing histories and different systematic biases.

O'Neil identifies three enabling technological factors that made this approach feasible in the 1980s that had not existed earlier: first, increasingly digitized radar receivers that produced measurement data in extractable digital form; second, computerized digital communications permitting far faster transmission without proportional increases in physical bandwidth or transmitter power; and third — most critically — fast computing widely available at each unit, allowing identical algorithms to run at every platform so that each gets the same result and is assured of seeing the same picture as all others. The third factor is what transforms dwell distribution from a data-sharing exercise into a common track picture: without shared algorithms and adequate computing at every node, distributing dwells would merely move the divergent processing problem from the data link to the processing layer.

The significance of the dwell-by-dwell approach for the sensor registration problem cannot be overstated. O'Neil documents the NTDS dual-track consequence directly: "The accuracy with which NTDS could track targets depended critically on the accuracy with which the relative positions of reporting ships could be determined as well as the accuracy with which their radars were aligned and calibrated. Accuracy problems often resulted in dual tracks — two or more reports of the same target could easily be mistaken for different tracks because they appeared in what seemed to be different positions."^7f This is the sensor alignment bias consequence, stated in its operational form. CEC's dwell-level distribution eliminates the dual-track problem at its source: if all platforms process the same measurements through the same algorithms, alignment biases that exist in individual sensors enter the shared processing as known inputs rather than as hidden systematic errors in separately-processed track states.

O'Neil's Track Movie: The Fundamental Problem Stated

The O'Neil document's appendix offers the clearest plain-language statement of the multi-sensor fusion problem in the literature: "In essence, the air defense system gets a series of snapshots of the air action. If snapshots come from one good camera at a rapid, constant rate it is relatively straightforward to merge them into a movie accurately showing the action. But in air defense we usually have only an irregular series of snapshots from various 'cameras' that may introduce serious distortions. The problem is to make a 'track movie' out of these and do so in real time, without significant delay." CEC addresses the distortion problem by ensuring that all platforms are working from the same snapshots before any "animation" decisions are made. JADC2's inter-service interfaces continue to distribute already-animated tracks — the same architecture that NTDS used, at a larger and more complex scale.

CEC's three principal capabilities, illustrated in Figure 1 of the APL Technical Digest and reproduced in the O'Neil document, follow directly from the dwell-level architecture: composite tracking and identification that produces an identical, accurate, comprehensive picture at every participating unit; precision cueing that allows a unit whose radar does not yet hold a target to point its radar precisely to pick it up at the limits of radar visibility, using the composite track data from other units; and coordinated cooperative engagements in which a ship can engage a target it does not hold on its own radar, using fire-control quality data from the composite track. O'Neil notes an additional capability that bears directly on JADC2's challenge: "One interesting CEC potential was that of improving tracking of stealthy targets. Often stealthy aircraft or missiles are much more visible from some angles than others. No one radar is likely to see a stealthy target from a favorable angle for more than a few dwells in succession, but by adding up the contributions of many radars it may be possible to get a solid track."^7g This is the precise technical foundation for the F-35C's role in NIFC-CA — the F-35's low-observable sensors provide dwells from angles unavailable to surface radars, and CEC fuses them into a coherent track through the E-2D relay node.

CEC's Gridlock Function: Registration Solved at the Architecture Level

CEC's gridlock function is the operational implementation of the sensor registration solution that NTDS-era track registration algorithms attempted to achieve analytically. The APL Technical Digest description of CEC processing subfunctions explicitly lists "gridlock" alongside track filtering, track divergence and convergence testing, and sensor interfacing as core CEP functions. Gridlock provides precision synchronization of sensor coordinate frames across all CEC-equipped units — not by estimating and correcting for registration biases after the fact, as classical registration algorithms do, but by maintaining a shared measurement reference frame in real time through the CEC data link. This is the capability that NTDS engineers were trying to achieve: CEC achieved it not by solving the registration estimation problem more cleverly, but by sharing the measurements before registration errors could accumulate. The Cooperative Engagement Processor also performs explicit track divergence and convergence testing — an automated track quality monitor equivalent to Bar-Shalom's innovation sequence assessment — that current JADC2 AI interfaces do not propagate to the reasoning layer.

CEC, Cebrowski, and the SIAP Projection

O'Neil documents a connection between CEC's architecture and the theoretical framework underlying JADC2 that has not received adequate attention in JADC2 acquisition discussions. CEC was, per O'Neil's direct conversations with Vice Admiral Arthur K. Cebrowski, on Cebrowski's mind when he formulated the network-centric warfare concept. As Cebrowski emphasized, CEC enabled units without SPY-1 radars or E-2C airborne radars to have a complete and highly accurate tactical picture and the information necessary for effective weapon engagements — self-synchronization without central direction. This is the NCW concept in operational expression, and it is precisely what JADC2 aspires to achieve across all domains and services.

Writing in 2007, O'Neil projected the trajectory of the Single Integrated Air Picture effort — the DoD's joint air picture program of that era — in terms that read as a description of JADC2: "In the longer run it seems likely that SIAP and CEC will merge into a common all-service joint system operating at the sensor data level."^7h JADC2 is the current iteration of that projected merger. The critical observation for this article is that the merger has not happened at the architectural level O'Neil described. JADC2's inter-service connections operate at the track level — the NTDS-style architecture that distributes processed tracks rather than sensor data — while CEC operates at the dwell level within the battle group. The seam between these two architectures is exactly where JADC2's common picture degrades from CEC-quality to NTDS-quality, and exactly where the AI reasoning layer receives its input. The AI operates on the NTDS-quality output of the inter-service interfaces, not on the CEC-quality dwell data of the intra-battle-group network. This architectural gap is not visible in JADC2 acquisition documents, and it is not addressed in the testing requirements for AI systems integrated into Project Overmatch.

CEC's Integration with NIFC-CA and the Path to JADC2

The Naval Integrated Fire Control-Counter Air architecture — which uses the E-2D as the sensor fusion and fire control node linking F-35C stealth sensors through the Hawkeye to CEC-equipped surface ships for over-the-horizon engagement — represents the mature operational expression of CEC's dwell-level architecture. The F-35C, operating in a low-observable profile, uses its passive sensors to relay dwell-level targeting data to the E-2D, which converts it to CEC-format fire-control-quality composite tracks and distributes them to surface ships for engagement. The engaging ship fires on a target its own radar has never seen, at ranges its own radar could not reach, based on tracks that CEC's gridlock and multi-sensor EKF fusion have made reliable enough for missile engagement.⁷ⁱ This capability — demonstrated operationally in Operation Epic Fury in 2026 — is the highest current expression of the multi-sensor registration problem's partial solution.

CEC's limitations, however, define the gap that JADC2 must bridge. CEC is a line-of-sight system within the battle group — its data link cannot relay beyond the geometric horizon without an airborne relay node. CEC addresses the naval air domain specifically; it was not designed for multi-domain, multi-service, coalition integration at the JADC2 scale. And critically: CEC's gridlock and sensor registration function within the GPS coordinate framework. GPS denial for airborne sensor contributors — the primary adversary electronic warfare strategy in a peer conflict — degrades CEC's inter-unit registration quality for exactly the same geometric reason it degraded NTDS inter-ship registration. The airborne platforms whose dwell data CEC requires for stealthy target tracking and horizon-extension are the same platforms most exposed to GPS denial. The partial solution that CEC achieved for the naval battle group in a GPS-available environment does not fully transfer to the GPS-denied, multi-domain, multi-service environment of JADC2.

The NTDS-to-CEC-to-JADC2 progression is a successive extension of the same problem to larger and more complex sensor networks. O'Neil's 2007 projection — that SIAP and CEC would merge at the sensor data level — remains the correct architectural direction. JADC2 has not achieved it. The inter-service interfaces that connect Army, Air Force, Navy, and coalition sensors in the JADC2 common picture continue to distribute tracks rather than dwells, recreating the NTDS dual-track problem at a joint force scale wherever sensor alignment biases, GPS-denied navigation errors, and association errors accumulate in the track data before it crosses service boundaries. The AI that reasons about this track picture operates on data that has passed through these seams — and it cannot see the quality degradation that crossing them imposed.

JADC2: NTDS at Scale Across All Domains

JADC2 is the Department of Defense's multi-decade program to connect sensors, shooters, and decision-makers across all military domains and services into a unified AI-enabled network. Each service contributes its own program: the Air Force's Advanced Battle Management System (ABMS), the Army's Project Convergence, the Navy's Project Overmatch, and the Space Force's National Defense Space Architecture. The January 2023 GAO report on JADC2 found that DoD had released initial strategy guidance but had not yet defined which existing systems would contribute to JADC2, what future capabilities needed to be developed, or the scope, cost, and schedule of the overall effort.⁸ The 2024 defense budget requested $1.4 billion in research and development funds for JADC2-related programs, with services' contributions growing by over $400 million from 2022 to 2024.⁹

The Navy's Project Overmatch — receiving $226 million in FY2023 and $192 million in FY2024, with $716.7 million planned across the five-year defense program — is described by its program manager, Rear Admiral Doug Small, as "creating a more interoperable force, allowing more pieces of the Navy — more ships, more aircraft, more unmanned systems — to connect with one another." The program's June 2025 announcement of a Maven capability, developed with Palantir, described "a unified tactical display that provides insight on vessels across the world" using artificial intelligence as the fusion and presentation layer.¹⁰

JADC2's sensor integration scope dwarfs NTDS's. Where NTDS connected shipboard radars within a task force via Link 11 at data rates of 1,364 bits per second per track, JADC2 is designed to fuse data from: shipboard AESA radars; airborne early warning aircraft; F-35 and F-22 sensor networks (which the GAO documented as operating on incompatible tactical data links¹¹); space-based sensors from the National Defense Space Architecture; ground-based missile defense radars; unmanned maritime surface and subsurface platforms; and coalition partner systems operating under different data standards and security classification levels. Each sensor contributes measurements in its own coordinate frame, with its own error characteristics, its own update rate, its own latency through the data link, and its own systematic biases.

The F-22/F-35 Interoperability Problem as a Modern NTDS Echo

The F-22 Raptor and F-35 Lightning II were designed with incompatible tactical data links — the F-22 uses IFDL (Intra-Flight Data Link) and the F-35 uses MADL (Multifunction Advanced Data Link), and the two systems cannot communicate directly. As a result, an F-22 and an F-35 operating in the same airspace cannot share track data without an intermediate relay node, introducing latency and potential association errors at the relay point. This is the modern equivalent of NTDS's inter-ship coordinate frame misalignment: sensors that should be contributing to a common picture are operating in different communication frames that require mediation, and that mediation introduces both latency and potential data integrity issues. JADC2's explicit goal of addressing this incompatibility is the same goal that NTDS was designed to solve for radar data — connecting sensors that were designed without interoperability in mind.

The GPS Threat: Return of the Navigation Error

The adversary electronic warfare strategy that most directly unmasks the NTDS-era problems in JADC2 is GPS denial and spoofing — and that strategy has moved from theoretical concern to documented operational practice at an accelerating rate.

The FAA documented a 65% increase in GPS signal loss events per 1,000 flights in the first half of 2024 compared to the same period in 2023.¹² OPSGROUP, the international aviation safety organization, estimated a 500% increase in GPS interference events over the course of 2024.¹³ The European Aviation Safety Agency issued a safety bulletin in July 2024 warning of the increasing frequency and multitude of impacts from GPS interference.¹⁴ Estonia's air navigation authority recorded over 600 dangerous GPS incidents in a single month following Russian jamming operations in the Baltic region. Aireon's analysis of aviation GPS anomaly trends through January 2025 showed consistent increases in spoofing indicators — duplicate position reports, position errors exceeding 20 nautical miles, and IPC flag events — distinct from the jamming indicators that had been more stable.¹⁵

The geographic distribution of interference is expanding beyond active conflict zones. The FAA issued NOTAMs in early 2026 advising caution over Mexico, Central America, parts of South America, and portions of the Pacific Ocean, citing potential military activity and GNSS disruption.¹⁶ The Korean Peninsula and areas around Beijing are documented interference hot spots. The Indian-Pakistani border region has emerged as a new GPS denial zone. These are not random electronic noise — they are deliberate denial and deception operations conducted by state actors for strategic purposes.

For airborne military platforms operating in a peer conflict environment, the GPS denial threat is qualitatively more severe than for surface ships. An airborne platform at 20,000 feet has line-of-sight to a surface jammer at roughly 170 nautical miles — ten times the surface horizon. Carrier aircraft operating in the contested airspace around a peer adversary's A2/AD system are exposed to GPS jamming throughout their flight profile. Tactical-grade airborne IMUs, constrained by aircraft size, weight, and power budgets, achieve drift rates of 0.1 to 1 nautical mile per hour — two to three orders of magnitude worse than the navigation-grade ring laser gyro installations on surface ships. An aircraft GPS-denied for 30 minutes in a maneuvering profile may accumulate navigation errors of 1 to 3 nautical miles — recreating the pre-GPS NTDS era navigation uncertainty that systematically corrupted inter-platform track association.

The vertical channel compounds this further. Airborne inertial navigation suffers an inherently unstable vertical channel — aircraft climbing and descending experience vertical accelerations indistinguishable from gravity variations without external reference. GPS stabilizes the vertical channel; GPS denial leaves altitude errors growing at rates that depend on maneuvering history and accelerometer quality. An F/A-18 that has been GPS-denied for 15 minutes in a tactical maneuvering profile may have altitude errors of hundreds of feet and position errors that translate into targeting errors of comparable magnitude.

China's A2/AD GPS Targeting

Chinese People's Liberation Army doctrine explicitly identifies adversary GPS dependency as a primary vulnerability to be exploited in the opening phase of a high-intensity conflict. PLA publications describe comprehensive electronic attack plans targeting GPS reception for both space-based and airborne assets in the Western Pacific theater. The scenario that JADC2 is designed for — a high-intensity conflict in the Western Pacific — is precisely the scenario where GPS denial is most capable, most prepared, and most deliberately targeted. JADC2's sensor fusion architecture was developed primarily in a GPS-available environment. Its performance in the GPS-denied environment that peer adversary doctrine is designed to create has not been publicly characterized by any DOT&E assessment or GAO report reviewed for this article.

The JADC2 Multi-Sensor Correlation Problem: Old Wine in New Architecture

JADC2's vision of fusing sensors across domains, services, and coalition partners introduces versions of all three NTDS problems simultaneously, with geometrically and organizationally greater complexity.

The data association problem operates at larger scale. A JADC2 common tactical picture that incorporates contacts from shipboard radars, airborne AEW, F-35 sensor fusion, unmanned maritime platforms, and space-based sensors contains contacts whose spatial density in contested environments may exceed what any classical assignment algorithm can process in real time. The computational complexity that made JPDA intractable for NTDS-scale contact populations in the 1990s applies at proportionally greater severity for JADC2-scale multi-domain fusion. Modern GPU acceleration has shifted the tractable cluster size substantially, but the fundamental #P-complete scaling of joint event enumeration is unchanged. Dense decoy environments — drone swarms with Luneberg lens reflectors designed to inflate the contact population — exploit this scaling property directly, potentially consuming the fusion system's computational resources during the engagement window.

The sensor alignment problem takes on additional dimensions with heterogeneous multi-modal sensor fusion. Fusing a shipboard AESA radar track with a carrier aircraft's EO/IR track of the same contact requires correctly characterizing the cross-sensor covariance — how errors in the radar's measurement are correlated with errors in the EO/IR system's measurement. These cross-sensor covariances, which describe the statistical relationship between two fundamentally different measurement modalities with different geometry, different error sources, and different reference frames, are among the least well-characterized parameters in any real sensor fusion system. They are not in the calibration data packages for individual sensors, because they are properties of the system-of-systems rather than any individual sensor. In an operational deployment, they are estimated implicitly from track quality statistics — the innovation sequence that Bar-Shalom identified as carrying quality information that higher-level systems typically discard.

The navigation coordinate frame problem is most acute in the GPS-denied airborne sensor scenario, as described above. But it extends to coalition partners as well. An allied navy operating NTDS-derived or NATO-standard sensor systems with different navigation reference architectures may introduce systematic coordinate frame offsets into the JADC2 common picture that the fusion system cannot distinguish from genuine contact position disagreements. Coalition interoperability exercises document navigation frame alignment as a persistent source of track correlation errors that require manual reconciliation during exercises — a labor-intensive process that is not available at machine speed in a real engagement.

What the AI Layer Cannot See

JADC2's AI systems — including the LLM and neural network components being integrated into Project Overmatch through partnerships like Palantir's Maven capability — receive as input the output of the sensor fusion layer: a track picture comprising position estimates, velocity estimates, and associated covariances for each contact, along with attribute data including IFF status, ESM emitter identification, track quality indicators, and tactical context. This is the same information format that NTDS delivered to combat direction operators, now presented to an AI reasoning system rather than a human operator.

What the AI cannot see in this input — because it is not there — is the history of association decisions that produced each track, the sensor alignment calibration state at the time of each measurement, the navigation error accumulation since the last GPS fix for each contributing sensor platform, or the confidence of the track registration algorithm's convergence. A track that has been coherently maintained for 200 scans from a well-calibrated radar with GPS-quality navigation and a correctly estimated azimuth bias looks identical in the track file to a track assembled from the residual association errors of a computationally degraded fusion algorithm processing a decoy-inflated contact environment with GPS-denied airborne sensor contributions. Both tracks have a position, a velocity, a covariance, and attribute data. Neither carries a reliable indicator of its quality as a representation of physical reality.

The AI system generates its engagement recommendation from whichever track picture it receives, with the confidence that its inference statistics produce. If the track picture is corrupted by systematic sensor alignment biases — as it will be in GPS-denied environments where airborne navigation has degraded — the AI's engagement recommendation is based on a falsified representation of the contact's position. If the track identity has been corrupted by a crossing-track swap in the association algorithm — as it will be in dense threat environments with deliberate decoy employment — the IFF and ESM attributes the AI is reasoning about belong to the wrong physical object. The AI cannot know either of these things from the track data it receives, because the information that would reveal them — the association history, the innovation sequence, the registration algorithm's confidence — is not propagated to the AI's input layer.

Bar-Shalom's Innovation Sequence and What JADC2 Discards

Yariv Bar-Shalom's foundational work on tracking and data association identified the innovation sequence — the series of differences between predicted and actual measurements across scans — as the primary carrier of track quality information. A track with consistently large innovations has a model that is wrong: either a bad association or an incorrectly estimated motion model. Using the innovation sequence to detect association errors and flag degraded track quality is mathematically correct and operationally valuable. Modern tracking systems generate this information. JADC2's sensor-to-AI interface typically does not propagate it to the AI reasoning layer — the interface presents processed track state and covariance, discarding the diagnostic information that would tell the AI whether the track is reliable. This is not a design choice made consciously by JADC2 architects — it reflects the historical convention of presenting track data rather than filter internals to decision systems, a convention established before AI systems were expected to make autonomous engagement decisions based on track quality they cannot independently assess.

The Comparison: NTDS Problems versus JADC2 Problems

Problem Dimension	NTDS Era (1960s–1990s)	JADC2 Era (Present)	Trend
Data association scale	N tracks, M measurements, single domain; shipboard radar contacts within task force	Multi-domain, multi-service, coalition; airborne, surface, space, unmanned; decoy-inflated contact populations	Substantially worse
Association algorithm capability	Rule-based correlation; Mahalanobis LAP; JPDA computationally intractable in dense environments	Deep MOT, GLMB filters, GPU-accelerated; better in benign environments, same fundamental scaling limits in dense adversarial environments	Better in typical case; same fundamental limit under adversarial stress
Navigation error — ships	SINS drift ~1 nm/hr; inter-ship misalignment dominant correlation failure; pre-GPS era 1960s–1994	Modern RLG/FOG IMU; daily GPS update adequate; ships geometrically protected from surface jamming; IMU bridge to GPS denial manageable	Substantially better for surface ships
Navigation error — airborne	Periodic INS updates; tactical IMU quality limited; 1-3 nm/hr drift typical	GPS normally available; GPS-denied: tactical IMU 0.1–1 nm/hr; 500% increase in GPS interference 2024; airborne platforms directly threatened by surface jammers at 170 nm LOS	Worse in peer conflict GPS-denied environment
Sensor alignment bias	Mechanical antenna biases; encoder errors; calibrated periodically; known problem	AESA phase calibration drift; carrier structural flexure; multi-modal cross-sensor covariance uncharacterized; coalition partner alignment unknown	Similar magnitude; different sources; harder to characterize across heterogeneous sensors
Sensor interoperability	Homogeneous radar sensors; Link 11 data link; single domain; U.S. only task forces	Radar, EO/IR, ESM, SIGINT, space-based; F-22/F-35 incompatible data links; multi-service; coalition partners with different standards	Substantially more complex
Decision system	Human combat direction operators with track picture; expert judgment about track quality	AI systems receiving processed track picture; no access to association history or filter internals; cannot assess input quality from output data	AI blind to input quality degradation that operators could detect contextually
Adversarial exploitation	Electronic jamming of individual radars; navigation disruption limited by available technology	GPS spoofing/jamming at scale; deliberate track swap attacks via decoys; prompt injection through sensor data manipulation; A2/AD doctrine explicitly targeting GPS dependency	Substantially more sophisticated and deliberate
Consequence of error	Track quality degradation; operator confusion; delayed engagement decisions; fratricide risk managed by human judgment	AI engagement decisions on corrupted track picture; fratricide mechanism through confident wrong recommendations; no human deliberation in compressed decision timelines; accountability vacuum	Categorically more dangerous with autonomous engagement authority

The Testing Gap That No Program Has Closed

DODD 3000.09 requires that autonomous weapons systems be tested to "function as anticipated in realistic operational environments against adaptive adversaries taking realistic and practicable countermeasures."¹⁷ GPS jamming and spoofing are realistic countermeasures that peer adversaries have demonstrated in operational environments. Dense decoy employment designed to inflate contact populations and exploit association algorithm failure modes is doctrinal for peer adversaries in anti-access/area denial scenarios. Dynamic sensor alignment errors from carrier flight operations, airborne platform GPS denial, and coalition partner coordinate frame misalignment are operational realities of the environment JADC2 is designed for.

No publicly available GAO report, DOT&E assessment, or JADC2 program documentation reviewed for this article describes AI system testing in a GPS-denied, high-jamming, decoy-dense environment representative of peer adversary A2/AD operations. The GAO's January 2023 JADC2 report found that DoD had not yet defined which existing systems would contribute to JADC2 or specified future capability requirements — a finding that precedes any meaningful test and evaluation of system performance under degraded conditions.¹⁸ The Air Force's ABMS, evaluated separately by GAO in 2020, was found to lack the planning and cost analysis necessary to ensure it would not slip behind schedule and incur cost overruns — a finding about program management that does not address operational performance under degraded navigation conditions.¹⁹

The NTDS program encountered its multi-sensor correlation and alignment problems through operational experience — in Vietnam, in fleet exercises, and in the analytical work that motivated the development of JPDA, IMM, and track registration algorithms over the subsequent two decades. The problems were discovered, characterized, and partially addressed through the iteration between operational use and technical research that normal program maturation provides. JADC2's AI systems are being deployed into the processing chain before the equivalent iteration has occurred for the GPS-denied, adversarially complex operational environment — and the AI layer introduces an additional abstraction that makes operational discovery of input quality problems less likely, because the AI produces confident outputs regardless of whether its inputs are reliable.

The sensor fusion problems that made NTDS harder than expected were never solved. They were masked by GPS for thirty years. The adversary knows this. The question is whether JADC2's architects do. — Author's assessment, derived from NTDS operational experience and current JADC2 program documentation

What Should Be Required

The technical requirements implied by this analysis are demanding but specific. They are not arguments against JADC2 — the operational need for multi-domain, multi-service sensor fusion is real and urgent. They are arguments for an honest accounting of what the technology can and cannot do in the operational environment for which it is being developed.

First: GPS-denied operational testing must be a mandatory program requirement. DODD 3000.09's "realistic operational environment" standard cannot be met by testing in GPS-available conditions for a program whose operational scenario explicitly assumes GPS denial. Every AI system in the JADC2 sensor-to-shooter loop must be evaluated against a track picture generated by a sensor fusion layer operating with GPS-denied airborne contributors, realistically-biased sensor alignment errors, and a contact population representative of peer adversary decoy employment doctrine. The tested reliability must meet the system's specified engagement performance threshold under these conditions, not under nominal GPS-available conditions.

Second: Track quality metadata must be propagated to AI reasoning layers. The innovation sequence, association history, registration algorithm confidence, and sensor alignment calibration status — the information that carries the quality of the track picture — must be included in the data provided to AI systems making engagement recommendations. An AI system that cannot receive track quality information cannot assess whether its inputs are reliable enough to support an autonomous engagement decision. The Bar-Shalom innovation sequence is generated within the tracking filter and is available — the engineering decision not to propagate it to higher-level systems was made before AI systems were expected to make autonomous engagement decisions, and it should be revisited.

Third: Adversarial exploitation testing must be included. DODD 3000.09's requirement for testing "against adaptive adversaries taking realistic and practicable countermeasures" must include testing specifically against decoy-induced contact density, deliberate track swap attacks through coordinated close-approach geometries, and GPS spoofing designed to corrupt airborne platform navigation without triggering spoofing detectors. These are not exotic threats — they are documented adversary capabilities that are central to peer adversary A2/AD doctrine.

Fourth: The interoperability testing gap must be closed before not after integration. The F-22/F-35 data link incompatibility, coalition partner coordinate frame misalignment, and multi-modal cross-sensor covariance characterization represent known interoperability problems that introduce systematic errors into the JADC2 common picture. These errors must be characterized through joint testing before AI systems are integrated into the fusion layer, not discovered through operational experience after AI-enabled engagement decisions have been made based on a track picture whose interoperability errors were not characterized.

Conclusion

The Engineering and Technology History Wiki preserves a remark from the NTDS program's earliest operational days that remains instructive sixty-five years later: the title of one chapter is simply "No Damned Computer is Going to Tell Me What to Do." The commanding officers who said that were wrong about NTDS — the system provided genuine operational value and was the direct ancestor of every subsequent naval C2 system including Aegis. But their instinct that the technology needed to earn operational trust through demonstrated performance in realistic conditions before receiving autonomous authority was correct — and it is an instinct that JADC2's acquisition trajectory is not honoring.

The three fundamental problems of NTDS-era multi-sensor fusion — data association ambiguity, sensor alignment bias, and coordinate frame misalignment from navigation error — were not solved. They were masked by GPS. Modern IMUs have extended the time between required GPS updates for surface ships to manageable intervals, and surface ship GPS denial is geometrically bounded. For airborne sensors in a peer conflict GPS-denied environment, the original NTDS-era navigation errors return in their full severity, inflating the inter-platform association failures that GPS had suppressed.

JADC2's AI systems receive a track picture that carries these errors invisibly, compounded by a data format problem that is independent of bandwidth and that no AI algorithm can remedy. J-series messages — the data vocabulary of Link 16 and JREAP — convert radar measurements to geographic coordinates, discarding the measurement covariance matrix that characterizes sensor geometry and replacing it with a scalar quality indicator. The embedded navigation error of the reporting platform enters the geographic position and cannot be corrected downstream because the message format carries no field for reporting platform navigation uncertainty. This is not a limitation that will be fixed: NATO STANAG standardization has frozen the J-series format across dozens of nations and thousands of terminals, and engineers who identified this problem in the 1990s have found it structurally unresolvable in the thirty years since. The JADC2 AI at inter-service seams is not fusing sensors. It is reconciling command and control pictures whose measurement provenance has been erased. No fusion algorithm, however sophisticated, can reconstruct a measurement covariance matrix from a scalar quality indicator.

No publicly available program document, GAO report, or DOT&E assessment documents testing of JADC2 AI systems in this GPS-denied, adversarially complex environment. The same institutional failure that put EMALS in CVN-78 before land-based testing was complete — the organizational priority of fielding capability over demonstrating that the capability works in the operational environment — is operating in JADC2's AI integration program. The discovery that the AI works differently in GPS-denied adversarial conditions will come operationally, at operational cost, from an engagement decision made on a track picture whose corruption the AI could not detect. The NTDS program learned its multi-sensor correlation lessons through decades of operational experience. The pace of JADC2 development is not providing an equivalent learning period before autonomous engagement authority is conferred.

Notes and Sources

1. Engineering and Technology History Wiki. (Last updated May 12, 2021). "First-Hand: No Damned Computer is Going to Tell Me What to DO — The Story of the Naval Tactical Data System, NTDS." [Secretary Connally; Admiral Burke; five-year versus thirteen-year development; commanding officer resistance.] ethw.org
2. Wikipedia contributors. (2025). "Naval Tactical Data System." [Sperry Rand UNIVAC computers; Collins Radio; Hughes Aircraft; AN/UYK-7 computer characteristics; 30-bit word; core memory; 600K ops/second.] wikipedia.org
3. Grokipedia. (January 17, 2026). "Naval Tactical Data System." [October 1961 first deployment USS Oriskany and USS King; Link 11 data link; NATO exports by December 1966.] grokipedia.com
4. Military History Fandom Wiki. "Naval Tactical Data System." [Two major problems: isolated ship views; need for common picture.] military-history.fandom.com
5. Engineering and Technology History Wiki. (May 12, 2021). "First-Hand: The Naval Tactical Data System in Combat — Chapter 7." [PIRAZ operations; pilot rescue missions; operational use in Vietnam; IFF monitoring.] ethw.org
6. Bar-Shalom, Y. & Fortmann, T.E. (1988). Tracking and Data Association. Academic Press, Orlando. [JPDA development; joint event enumeration; Mahalanobis distance; Gaussian measurement noise assumptions; LAP formulation.] ISBN 0-12-079760-7.
7. ADBR (Australian Defence Business Review). (December 23, 2019). "Tech Brief — 'Data Link 101'." [Link 11/16/22 architecture comparison; HF BLOS capability analysis; Australian transition to Link 22; satellite-denied environment concerns; Link 16 fixed TDMA description; JREAP satellite relay limitations.] adbr.com.au; and: Wikipedia contributors. (2025). "MIL-STD-6011." [Link 11 HF 2-30 MHz, UHF 225-400 MHz; HF ground wave 300 nm, sky wave 1,000 nm; UHF 20-30 nm ship-ship, 150 nm ship-air; 1,364 bps HF, 2,250 bps UHF; 30-bit packets; Ralph Benjamin design history.] wikipedia.org; and: Wikipedia contributors. (2025). "Link 16." [960-1215 MHz; 31.6/57.6/115.2 kbps; TDMA 128 time slots per second; 7.8125 ms per slot; JREAP satellite relay for BLOS; J-series messages.] wikipedia.org
8. SAIC. "Joint Range Extension Links Global Military Comms." [JREAP: "For more than 20 years SAIC's Joint Range Extension (JRE) solution has reliably delivered Link 16 and long-haul data and communications exchange"; over 1,700 JRE systems fielded to DoD, NATO, and allied countries; enables tracking data for friendly, adversarial, and unknown contacts globally.] saic.com; and Tonex Training. "JREAP Training." [MIL-STD-3011; J-series messages embedded in IP over satellite; JREAP as sole BLOS solution for Link 16; cybersecurity requirements: "Strong crypto/key management, link authentication, and guard enforcement block spoofing, replay, and cross-domain leakage that can snowball into fratricide or mission aborts."] tonex.com
9. Military Aerospace. "Air Force eyes next-generation tactical data links gateway for jet fighter communications." ["The problem today is that Link-16, IFDL, and MADL are not compatible. Air Force experts have tried to bridge the compatibility gap between the three data links with the first increment of the 5th to 4th Gen Gateway, which has been demonstrated by several contractors, including Boeing, Lockheed Martin, and Northrop Grumman."; second increment providing BLOS and multi-level security track fusion processor still in development.] militaryaerospace.com; and Defense Update. "F-22 Enters the Network — Linking IFDL, TTNT, Link 16." ["As this stealth datalink is incompatible with all other communications devices, Raptors cannot communicate with any friendly aircraft."; BACN relay node as partial solution.] defense-update.com
10. GlobalSecurity.org. "Cooperative Engagement Capability — AN/USG-2(V)." [Block 2 aircraft with JTIDS/Link 16 installation; Link 11 NTDS data link on all E-2C aircraft; JTIDS enables network-derived registration through joint contacts observable from altitude geometry distinct from surface ship geometry.] globalsecurity.org
11. Wikipedia contributors. (2025). "Grumman E-2 Hawkeye." [E-2D first flight August 2007; IOC October 2014; AN/APY-9 UHF AESA radar; integrated CEC, Link 16, TTNT; T4O copilot tactical role; VAW-125 first delivery March 2014.] wikipedia.org
12. Army Recognition. (April 2, 2026). "U.S. Navy Command Aircraft E-2D Hawkeye Central to Air Operations in Epic Fury Over Iran." [AN/APY-9 360° coverage; CEC fire-control-quality track distribution; over-the-horizon targeting; theater C2 role as E-3 Sentry fleet declines; JADC2 integration.] armyrecognition.com
13. Wikipedia contributors. (2025). "Cooperative Engagement Capability." [JHU/APL conception early 1970s; Battle Group AAW Coordination; first at-sea experiment 1990; Navy acquisition program 1992; EMD 1995; first fleet deployment 1998; Raytheon Systems Co. development with JHU/APL.] wikipedia.org
14. O'Neil, W.D. (2007). The Cooperative Engagement Capability (CEC): Transforming Naval Anti-air Warfare. Case Studies in National Security Transformation, Number 11. Center for Technology and National Security Policy, National Defense University, Washington, D.C. [Primary analytical source for CEC section; "dwell by dwell" quotation p. 14; three enabling technological factors p. 15; Track Movie appendix pp. 17-18; VADM Cebrowski NCW connection p. 14; SIAP/CEC merger projection p. 16.] Accession No. ADA471258. apps.dtic.mil
15. O'Neil, op. cit., p. 13. [NTDS dual-track problem: "Accuracy problems often resulted in dual tracks — two or more reports of the same target could easily be mistaken for different tracks because they appeared in what seemed to be different positions."; NTDS handoff problem: "accuracy problems also slowed the handover to the pencil-beam radars of ship and aircraft fire control systems, which might have to search for crucial seconds before finding the target which had been passed."]
16. O'Neil, op. cit., p. 14. [Stealthy target tracking capability of CEC: "Often stealthy aircraft or missiles are much more visible from some angles than others. No one radar is likely to see a stealthy target from a favorable angle for more than a few dwells in succession, but by adding up the contributions of many radars it may be possible to get a solid track."]
17. O'Neil, op. cit., p. 16. ["In the longer run it seems likely that SIAP and CEC will merge into a common all-service joint system operating at the sensor data level." — Projection that JADC2 has not yet fulfilled at the sensor data level for inter-service interfaces.]
18. Army Recognition. (April 2, 2026). "U.S. Navy Command Aircraft E-2D Hawkeye Central to Air Operations in Epic Fury Over Iran." [NIFC-CA architecture; over-the-horizon targeting via CEC; 10,500+ sorties; theater C2 role.] armyrecognition.com
19. Author's assessment based on GPS line-of-sight geometry: surface jammer at 10m ASL, ship GPS antenna at 20m ASL, horizon ~7 nm; ring laser gyro drift rates 0.0001 deg/hr; fiber optic gyro drift rates 0.00001 deg/hr achievable for navigation-grade systems. See also: Honeywell Aerospace. (November 14, 2025). "In GPS Denial: Addressing the Jamming and Spoofing Challenge." [GPS jamming and spoofing now threatening 1,500+ flights daily.] aerospace.honeywell.com
20. Government Accountability Office. (January 13, 2023). "Battle Management: DOD and Air Force Continue to Define Joint Command and Control Efforts." GAO-23-105495. [JADC2 lacks definitions of which systems contribute; no scope, cost, or schedule defined; ABMS two efforts; F-35 prototype plans shifted.] gao.gov
21. Center for Strategic and Budgetary Assessments. (2024). "JADC2 Policy Brief." [FY2024 JADC2 budget request $1.4B R&D; service contributions grew $400M from 2022 to 2024; CSBA program analysis.] csbaonline.org
22. Defense Visual Information Distribution Service. (June 18, 2025). "Commercial Tech Partnerships Drive Unprecedented Progress for Project Overmatch and Navy Capability." [Maven capability with Palantir; unified tactical display; Open DAGIR ecosystem; Project Overmatch FY2023 $226M, FY2024 $192M, five-year $716.7M.] dvidshub.net
23. Wikipedia contributors. (2025). "Joint All-Domain Command and Control." [F-22 IFDL and F-35 MADL incompatible data links; ABMS; Project Convergence; Project Overmatch; National Defense Space Architecture.] wikipedia.org
24. GlobalAir.com. (April 14, 2026). "FAA flags global surge in GPS jamming and spoofing, updates its playbook." [65% increase GPS signal loss per 1,000 flights first half 2024 vs 2023; eight hot spots; FAA GPS Interference Resource Guide v1.1; NOTAMs covering Pacific, Mexico, Central America.] globalair.com
25. OPSGROUP data cited in: Aireon. (May 2025). "Observations of Trends in GPS Anomalies Affecting Aviation." [500% increase in GPS interference events 2024 per OPSGROUP; 80% increase in outage events 2021–2024 other models; EASA safety bulletin July 2024.] aireon.com
26. EASA. (July 2024). GPS Safety Bulletin. Cited in Aireon White Paper, op. cit. [Frequency and multitude of impacts increasing; potential impacts including navigation errors, diversions, potential controlled flight into terrain.]
27. Aireon, op. cit. [GPS anomaly metrics August 2024 through January 2025; spoofing indicators: position errors >20 NM, duplicate reports, IPC flag; jamming indicators: Low PIC, FTC0.] aireon.com
28. FAA GPS Interference Resource Guide v1.1. (December 2025; updated April 2026). Cited in GlobalAir.com, op. cit. [NOTAMs issued January 2026 for Mexico, Central America, portions of Pacific Ocean; Korean Peninsula and Beijing areas documented hot spots.]
29. Department of Defense. (January 25, 2023). DoD Directive 3000.09, Autonomy in Weapon Systems. [Testing requirement: "function as anticipated in realistic operational environments against adaptive adversaries taking realistic and practicable countermeasures."] esd.whs.mil
30. GAO-23-105495, op. cit. [DOD has not defined which existing systems contribute to JADC2; scope, cost, schedule undetermined; House report directed DOD to report on these elements.]
31. FedScoop. (April 17, 2020). "Air Force network of sensors needs better analysis and guidance, watchdog finds." [GAO 2020 report on ABMS; "nontraditional approach"; lacks planning and cost analysis; risk of schedule delays and cost overruns.] fedscoop.com
32. Bar-Shalom, Y. & Kirubarajan, T. (2001). Estimation with Applications to Tracking and Navigation: Theory, Algorithms and Software. John Wiley & Sons. [Innovation sequence as track quality indicator; IMM estimator for maneuvering targets; track registration and bias estimation theory.] ISBN 978-0-471-41655-5.