General Dynamics' GPS-free receiver navigates on a hypersonic Talon-A flight

The person who reads this announcement most closely is the navigation lead on a weapon program. That person holds a requirement that the munition keep a position fix when GPS is jammed. Matt Elliott, director of the Weapons and Navigation business segment at General Dynamics Mission Systems, described that person's problem. "GPS-denied technology is arguably one of the largest capability gaps across joint forces," he said ^[5].

"General Dynamics Mission Systems is bringing software-defined receiver technology to the fight, allowing programs to continuously outpace the threat with software upgrades instead of requiring new hardware insertions," Elliott said ^[6]. The receiver processes signals on reprogrammable technology, so developers can change navigation features in software as electronic warfare threats evolve ^[8]. The tests so far have shown two things. On the Talon-A flight, radio frequency navigation worked without GPS ^[15]. In an earlier cannon-fired artillery test, the receiver survived strong launch forces and sent signal data to the munition's mission computer ^[10].

Both results are about environment. Hypersonic flight brings fast Doppler shifts, strong acceleration and high heat, and at higher speeds the ionized air around the vehicle can weaken radio signals ^[11]. MO-Nav navigates on radio signals, so that last effect bears on it directly ^[15].

GDMS announced the flight on October 7, 2026 ^[2], but it has not said which satellite constellations or commercial signals the Talon-A flight used, and it has not shared the receiver's size, weight, power needs or navigation accuracy ^[9].

Sort every GPS-alternative receiver on a shortlist along two lines, judged against your own mission profile. One line is whether the vendor has flown or fired it in conditions like yours. The other is whether the vendor has published the performance figures you would budget against. A receiver with both goes into the baseline design. Published figures without a test in your conditions make a bench result, with the flight risk still open. With neither, all you have is the vendor's claim. A test in your conditions without published figures belongs in the integration test plan, with the figures written in as an entry condition.

On GDMS's own account, MO-Nav sits in that last box for gun-launched and hypersonic programs ^[1][10]. For a platform unlike either test, it has neither. I would put it in the first group's test plan now. The tradeoff is schedule: a team that holds integration until the figures arrive gives up the head start of a card that has already been through two hard environments.