By Robbin Laird
Two stories crossed my desk within weeks of each other in September, both about the U.S. Navy’s anti-submarine warfare enterprise, and neither one mentions the other.
But read together, they describe the same institutional problem being solved from opposite ends of the sensor-to-shooter chain: the platforms that deliver ASW sensors and the people, now increasingly the algorithms, who interpret what those sensors hear are both being re-engineered to survive the retirement of a generation and the erosion of a single-platform, single-skillset model of readiness.
The Problem Nobody Chose
The first story is a straightforward Navy news release. In August, a joint Navy-Marine Corps test team flew an MV-22B Osprey off San Clemente Island and used it, for the first time, to perform lot acceptance testing of sonobuoys, the quality-assurance drops that confirm production-run acoustic sensors will perform as expected before they reach the fleet.
That mission has historically belonged to the P-3C Orion, flying out of the Air Test and Evaluation Squadron, using automated launch containers triggered electronically from the cockpit. The Osprey has no such system. Its aircrew instead hand-launched the buoys from the open rear cargo ramp, timing releases manually and slowing the aircraft to match the precision the acoustic test required.
The point of the exercise was not to replace the Orion. It was to prove that the Osprey can serve as what the program manager called a dependable substitute if the primary test platform is unavailable, keeping the sonobuoy delivery pipeline moving rather than letting it depend on a single airframe. As Marine Corps Lt. Col. Brandon Pope put it, the event demonstrated how the Osprey’s range, speed, and versatility can support broader maritime domain awareness and fleet operations, beyond the assault-transport role it was originally built for.
The second story is one I reported myself, from a conversation with Rob Ziemba and Chip Whitfield of Lockheed Martin’s rapid prototyping team for the Navy helicopter program. Their starting point was demographic rather than mechanical: the generation of acoustic sensor operators who could read a spectrogram the way a sommelier reads a wine list is aging out of the fleet, and two decades focused on the Middle East let the passive-acoustic interpretation skillset atrophy.
Their answer is SensorMax, a spectrum foundation model built to do something narrower than a generic large AI model, retrain itself at the edge, in the field, in minutes rather than months, to recognize a new acoustic signature. Whitfield’s own framing was blunt: the goal was to get the expertise of Chris Moon, the instructor who trained nearly every MH-60R sensor operator for forty years, into a box.
Same Diagnosis, Different Layer of the Kill Web
I have spent the better part of a decade arguing, with Ed Timperlake, that the shift from kill chain to kill web is as much an institutional and organizational transformation as a technical one, a move away from dedicated, single-mission platforms and toward distributed, interoperable nodes that can be recombined as the mission demands. These two stories are a small but clean illustration of that argument operating on both sides of the ASW mission at once.
The Osprey test addresses the physical delivery layer. A platform-agnostic approach to sonobuoy quality assurance means the fleet’s acoustic-sensor pipeline no longer has a single point of failure in the P-3C inventory. The SensorMax effort addresses the cognitive layer. A platform-agnostic approach to signal interpretation, Whitfield describes it as retraining the “bloodhound you’ve already got” in the field rather than building a new one from scratch for every new target, means the fleet’s acoustic-sensor interpretation no longer depends on a shrinking pool of career operators whose expertise was never fully captured in a requirements document.
Neither program was conceived with the other in mind, and neither uses kill web language to describe itself.
But both are responses to the same underlying condition: legacy ASW capacity, in platforms and in people, is aging out faster than the traditional acquisition and training pipelines can replace it, and the fix in both cases is to make the mission portable across whatever assets happen to be available rather than reserved for one dedicated system.
Speed as the Real Metric
The SensorMax story also offers something the Osprey story only gestures at: a hard measure of how much latency reduction is achievable once a mission is decoupled from a single platform and a single acquisition timeline. Whitfield’s team took the retrain cycle from 37 minutes on the ground, walking a data locker into a secure room by hand, to two or three model retrains per four-hour flight, with performance improving while the aircraft remained airborne, a compression made possible, both engineers were emphatic, by Lockheed Martin funding the effort itself rather than waiting on a program of record.
That self-funded, iteration-at-the-speed-of-the-exercise posture is the organizational half of the kill web argument I have made elsewhere about mission engineering: the technology only delivers a shortened sensor-to-decision timeline if the institution around it is willing to move at the same pace.
The Osprey test is a more modest step, and its own report frames it that way — a quality-assurance substitute, not a doctrinal shift.
But the underlying logic is identical to the “best of breed, not proprietary lock-in” principle Whitfield described for SensorMax’s sensor and platform partnerships, from Saildrone to Liquid Robotics’ Waveglider. An MH-60R that carries 106 boxes built by 52 different companies and a sonobuoy pipeline that can run through either an Orion or an Osprey are both expressions of the same design instinct: resilience through interoperability rather than resilience through redundancy of a single exquisite system.
Reading Them Together
Taken together, they are a working case study in what it actually looks like when a fleet moves from a kill chain built around dedicated platforms and irreplaceable human expertise toward a kill web built around distributed, recombinable nodes, human and machine alike.
The Navy did not plan for these two stories to be read side by side.
That they nonetheless describe the same transformation, independently and from opposite ends of the ASW mission, is itself evidence that the shift is not a single program’s initiative but a fleet-wide adaptation to a demographic and technological reality no one platform or one generation of operators can outrun.