IN Brief:
- QinetiQ has integrated radar equipment for the Royal Navy Type 31 frigate programme at Portsdown Technology Park.
- The shore facility allows mission-system testing before equipment is installed and proven on operational ships.
- The work highlights the production value of land-based integration for radars, combat systems, masts, software, and crew training.
QinetiQ has integrated radar equipment for the Royal Navy’s Type 31 frigate programme at Portsdown Technology Park, bringing a key mission-system risk ashore before it consumes ship time.
The radar installed at the Portsmouth site has been assessed as the Thales NS110 E/F-band air and surface search radar. The Type 31 class will also use the Terma Scanter 6000 I-band radar for air and surface search, navigation, and helicopter control. A safety case is being developed to allow full-power radar transmission, while a decision remains open on whether a representative Type 31 mast will be installed at the site.
The value of the Portsdown work lies in the shift from ship-based troubleshooting to controlled land-based integration. If the first Type 31 frigate had to carry the burden of early radar integration, the programme would risk losing valuable ship availability while engineers worked through interfaces, safety cases, emissions control, software behaviour, power demand, cooling, and operator procedures. Shore testing allows many of those problems to surface earlier.
Modern frigates are integration projects before they are steel products. Hull fabrication and propulsion remain essential, but operational value comes from sensors, combat management systems, communications, electronic warfare equipment, weapons, navigation systems, and data links functioning as a coherent whole. A radar cannot be bolted on and treated as complete. It must feed the combat system, coexist with other emitters, support crew workflows, and remain maintainable through upgrades.
Type 31 has been shaped by the need for an affordable general-purpose frigate alongside the higher-end Type 26 anti-submarine warfare ships. Affordability depends heavily on integration discipline. A lower-cost hull loses much of its advantage if mission systems generate repeated rework, late redesign, or prolonged post-delivery correction. Shore integration is one way to protect the cost model.
Portsdown is therefore part of the production base, even though it is not a shipyard. Land-based integration facilities allow suppliers and operators to connect equipment, refine software, identify incompatibilities, prepare training material, and build confidence before equipment moves to sea. Hardware-in-the-loop laboratories, shore masts, simulation environments, and digital models now sit alongside fabrication halls as essential elements of naval manufacturing.
The mast decision illustrates the level of realism required. Radar performance on a test site is useful, but final ship performance is shaped by antenna placement, mast structure, cable routing, electromagnetic compatibility, vibration, maintenance access, and line-of-sight constraints. A representative mast would increase realism, while also adding cost and complexity. The decision will show how much integration risk the programme is prepared to retire ashore.
Full-power transmission is another practical hurdle. Installing a radar physically is only part of the work. Emissions safety, interference with nearby equipment, personnel exposure, site procedures, and operating controls must all be resolved before realistic testing can begin. These stages can appear slow from outside the programme, but they reduce the likelihood of disruptive discoveries once the equipment is installed on a ship.
The Type 31 radar work also points toward future Royal Navy integration demands. The move toward Common Combat Vessels and hybrid fleet operations will increase the need for shore-based testing because future ships will coordinate crewed platforms, uncrewed vehicles, distributed sensors, and software-defined mission systems. Naval autonomy trials, including maritime networks that connect drones, helicopters, ships, and combat systems, will require similarly controlled integration environments before they are trusted at fleet scale.
Supplier collaboration is strengthened by this kind of facility. Radar suppliers, combat-system teams, QinetiQ engineers, Royal Navy operators, mast designers, and training specialists can work through problems while changes remain manageable. That improves documentation, maintenance procedures, operator interfaces, and software baselines before equipment is exposed to the time pressure of ship trials.
The crew-training benefit should not be overlooked. A shore facility can familiarise operators with radar displays, procedures, limitations, and fault conditions before they embark on the first ships. That reduces the learning curve at sea and helps identify human-machine interface problems while the system can still be altered without major disruption.
Type 31 will be judged partly by delivery pace, but entry into service depends on mission systems that are mature enough to operate without an extended correction phase. Portsdown gives the programme a controlled place to find faults, refine procedures, and train crews before the equipment is fully committed to shipboard operations. The radar may be the visible item, but the deeper production lesson is the test infrastructure around it.
