E-2D Block II clears critical design review

Northrop Grumman and the US Navy have completed the critical design review for the E-2D Advanced Hawkeye Block II upgrade, allowing the programme to move from system design into physical aircraft modification and flight-test preparation.

The review took place in May and was announced publicly on 17 August by the E-2/C-2 Airborne Command & Control Systems Program Office. Block II is the next development of the aircraft’s Delta System Software Configuration 6 baseline and is intended to provide the computing and software infrastructure for faster insertion of future capabilities.

The upgrade introduces a modernised cockpit architecture, greater computing power, an Open Mission Systems framework, and enhanced cybersecurity. The Navy also expects the changes to address component obsolescence, reduce pilot workload, and improve situational awareness during complex airborne command-and-control missions.

Critical design review is a programme boundary rather than an operational capability declaration. It assesses whether the product baseline is mature enough for implementation, allowing engineers to move from requirements and design definition into the hardware, software, integration, and test work needed to produce a functioning aircraft configuration.

For Block II, that means the programme now moves into physical E-2D retrofits. Flight testing of the upgraded aircraft is scheduled for fiscal year 2029, leaving several years of installation, software integration, ground testing, systems verification, and test preparation before the new baseline is demonstrated in the air.

The E-2D already performs airborne early warning and command-and-control duties for US carrier strike groups, using radar, communications, processing, and operator workstations to build and distribute a wider battlespace picture. Block II does not replace that fundamental role; it changes the digital infrastructure through which future capabilities will be incorporated.

That distinction matters because military aircraft generally remain in service much longer than the computing systems installed inside them. Airframes can retain useful structural and aerodynamic life for decades while processors, displays, network interfaces, software frameworks, and cybersecurity requirements change several times.

When mission systems are tightly tied to proprietary interfaces, replacing an obsolete processor or adding a new application can require substantial redesign around connections created for an earlier generation of hardware. The Navy’s Open Mission Systems approach is intended to reduce some of that engineering burden by defining interfaces through which new hardware and software can be integrated more predictably.

Open architecture does not mean that equipment can be added without qualification or security controls. Aircraft mission systems still have to meet demanding requirements for electromagnetic compatibility, environmental performance, cybersecurity, timing, safety, and reliability. The objective is to reduce unnecessary dependence on bespoke interfaces rather than remove engineering discipline.

That has an industrial consequence as well as a technical one. A more modular baseline can make it easier to introduce components from different suppliers, replace obsolete equipment, and compete some future upgrades without having to reconstruct the complete mission system around each change.

Computing capacity is especially important on the E-2D because its role increasingly involves processing and distributing information rather than merely detecting an airborne target. Carrier groups now draw data from ships, fighters, satellites, sensors, weapons, and uncrewed systems, increasing the volume and complexity of information an airborne command node may be expected to handle.

More connectivity also increases the cybersecurity requirement. An aircraft designed to exchange information across multiple networks has more interfaces to protect, while its software has to remain supportable as threats, standards, and defensive techniques change throughout the platform’s service life.

The Block II cockpit work addresses the human side of the same problem. More data and processing power are useful only if the crew can interpret and act on the resulting information without increasing workload to the point that the technology becomes counterproductive.

The Navy says the modernised cockpit and flight systems are intended to reduce pilot workload and improve situational awareness, while the wider mission-system changes provide the foundation for future command-and-control capability insertion.

Component obsolescence is another practical driver. Electronics manufacturers operate on commercial product cycles much shorter than defence-aircraft lifetimes, which can leave programmes supporting processors, cards, displays, and other hardware long after the original component market has moved on.

An architecture designed to accommodate replacement equipment more readily can therefore reduce sustainment risk even before a new tactical capability is added. Avoiding a major redesign every time a component becomes unavailable can lower the cost and time associated with keeping the fleet technically current.

None of those benefits is guaranteed by completing a design review. The approved architecture still has to survive aircraft installation and test, and programme teams will have to prove that the new computing, cockpit, cyber, and software infrastructure operates correctly alongside existing E-2D systems.

The FY2029 flight-test target provides the next clear programme marker. By then, Block II will have to move from an approved product baseline to an aircraft configuration capable of demonstrating that the new infrastructure works in flight and provides a stable foundation for the upgrades the Navy expects to introduce over the E-2D’s remaining service life.