When does a supercarrier stop being a shipyard project and start becoming a warship? For the future USS John F. Kennedy, that moment arrived when the 100,000-ton carrier cleared Newport News and entered open water for builder’s trials. Sea time changes everything. Pier-side work can verify installation, alignment, and software behavior in controlled conditions, but the Atlantic adds motion, heat, vibration, salt exposure, and sustained electrical demand. Those forces reveal whether a carrier’s tightly linked systems behave like finished machinery or like a collection of promising subsystems still learning to coexist.
That matters more on a Ford-class carrier than on any recent U.S. flattop. The design’s value is tied to flow: aircraft launched faster, recovered faster, rearmed faster, and turned around with fewer chokepoints below deck. Kennedy carries the same broad ambition as USS Gerald R. Ford, centered on EMALS catapults, Advanced Arresting Gear, and Advanced Weapons Elevators. Those are not isolated gadgets. They are the moving parts of the carrier’s operating rhythm, and the class has already shown how hard it is to make that rhythm reliable under real demand.
Ford’s record explains why Kennedy’s first time at sea is more than a ceremonial milestone. The lead ship demonstrated that breakthrough systems can work and still remain difficult to sustain. Ford’s weapons elevators eventually became operational, but only after years of adjustment. Its flight deck systems have also continued to draw scrutiny. During one deployment period, the carrier completed 8,725 launches and arrested landings, yet official testing still pointed to reliability and maintainability problems with EMALS and AAG. Earlier at-sea operations also showed how fragile that margin could be when EMALS broke during sea trials, cutting into flight activity. That history is why Kennedy’s own trials are less about proving concepts than proving endurance. The question is not whether the systems can perform for a demonstration, but whether they can keep performing without leaning heavily on outside technicians, software workarounds, or long correction cycles between test periods.
Kennedy does arrive with one notable advantage: a different radar path. Instead of the Dual Band Radar fitted to Ford, the ship is being built with the Enterprise Air Surveillance Radar, a SPY-6 family variant. That swap is more than a hardware change on the island. Ford’s radar struggled with availability, and the Navy has already been moving away from that one-off architecture toward a sensor family with broader fleet commonality. In practice, Kennedy benefits from a system line built around shared sustainment, digital processing, and fewer unique support burdens over decades of service.
The shipyard side of the story matters, too. Huntington Ingalls has spent years pushing more work into modular construction and higher levels of pre-outfitting before large sections are lowered into place. That approach is meant to reduce rework and catch conflicts earlier, especially on a ship where electric machinery, software controls, and tight tolerances can turn a small installation problem into a class-wide headache. Kennedy’s first builder’s trials, completed in early February 2026, marked the point where those production lessons met the ocean for the first time.
The schedule shows how demanding that handoff remains. Kennedy is now expected to deliver in March 2027, after delays tied in part to AAG certification and continued elevator work. It is also being prepared to operate the F-35C at delivery, which folds another layer of integration into an already dense test program. And once commissioned, the ship is expected to head west, with Naval Base Kitsap undergoing major electrical upgrades ahead of its arrival as a future homeport. That is why the first voyage is not a finish line. It is the point where the Ford class has to show that hard-earned lessons from the first ship really took hold in the second.
