What does a fifth-generation fighter become when its primary radar is missing? For the F-35, the answer is not a failed aircraft, but a sharply reduced one. New U.S. jets built for the Block 4 era are being accepted in a configuration that keeps them flyable while stripping away the sensor that gives them independent battlefield awareness. Instead of the planned radar, some aircraft will carry ballast in the nose to preserve weight and balance, a workaround confirmed in deliveries starting this fall.
The bottleneck centers on the AN/APG-85, the radar meant to anchor a major step forward in F-35 capability. It is not a simple plug-in replacement for the APG-81 already flying on the jet. The newer array requires a different forward bulkhead, which means aircraft built around the APG-85 cannot just revert to the older radar when the new one falls behind schedule. That design decision has created an unusual result: advanced airframes leaving production lines without the sensor that turns stealth and software into a complete combat system.
Rep. Rob Wittman described the consequence plainly, saying the jets are “going to be produced with ballasts,” creating aircraft “that’s not going to be combat-coded anytime soon.” One source familiar with the issue said, “They can still take delivery of the jet. They can still use it as a flyable asset, [but] obviously not a combat-coded asset. So they can still do limited training with it.”
That limitation matters because radar is not just another onboard component. In a modern fighter, it is central to target detection, track management, missile cueing, and survivability in dense electronic warfare environments. The APG-85 is intended to improve range, tracking, and electronic attack performance as part of the broader Block 4 upgrade path. Breaking Defense also reported that a dual-compatible bulkhead is not expected until Lot 20 deliveries in 2028, leaving an extended gap if radar production and certification continue to lag.
The F-35 can still lean on other sensors and networked data from offboard sources. But that is not the same as carrying its own high-end radar into a contested fight. Stacie Pettyjohn of the Center for a New American Security called a radar-less F-35 “very near-sighted,” noting that datalink-fed awareness adds latency and can be disrupted by jamming. That tradeoff is manageable for training sorties. It is far less attractive for the high-threat missions Block 4 was designed to address, especially as the program positions the F-35 for manned-unmanned teaming operations and a larger command-and-control role.
The deeper engineering story is about concurrency. The F-35 enterprise chose to keep production moving while key upgrades were still maturing, accepting the risk that aircraft could be structurally ready before their most important new subsystems were certified. The Joint Program Office has said that choice was made with full understanding of the risk, and the Marine Corps has argued it avoids years of heavier retrofit work later. Even so, concurrency only works cleanly when hardware, software, and certification timelines stay aligned. On the F-35, radar delays now join the earlier TR-3 software disruption as another reminder that production volume and usable combat capacity are not identical measures.
That is why the current issue stands out beyond the F-35 program itself. It shows how next-generation combat aircraft are no longer defined by stealth shaping alone, but by the timing and integration of sensors, power, cooling, software, and structure. When one of those pieces slips, the aircraft may still fly. It just does not arrive as the warfighting system it was built to become.
