Video
The Rise & Fall of the Constellation Class: What happened to the FFG-62 Program?
Study The Rise & Fall of the Constellation Class: What happened to the FFG-62 Program?, a Dr. Alex Clarke video from 31 May 2026, with 36 time notes. Topics include Aegis Combat System, Air Defence, Anti-Submarine…
Time notes
- 1:27Constellation's off-the-shelf value problemChapter
Constellation began as a conservative off-the-shelf frigate and drifted toward destroyer-level cost comparisons.
- 3:22Perry class as the basic frigate benchmarkNotable Point
The Oliver Hazard Perry class becomes the baseline for what a numerous, utilitarian US Navy frigate could be.
- 5:39Post-Cold War transformation and the move toward LCSChapter
Technological-transformation ambitions provide the context for replacing a conventional Perry successor with the Littoral Combat Ship.
- 9:27LCS mission overload sets up the next frigate problemChapter
The LCS critique identifies a conflict between close-in rapid-response work and traditional frigate duties.
- 12:14FFG(X)'s initial requirements and deferred growth optionsNotable Point
The capability matrix prompts a debate over immediate requirements, while larger RHIBs remain a future option and the paired helicopters have a clear ASW purpose.
- 14:40VLS and Aegis expectations raise frigate costNotable Point
Missile-system cost includes the sensors and computers behind the launchers, while the requirement tiers give radar priority over ASW sonars.
- 16:26When an escort requirement becomes a picket requirementNotable Point
Carrier-group compatibility and robust independent operations brought picket-like expectations into the FFG(X) requirement.
- 20:22FFG(X) reverses the LCS mission graftChapter
Where LCS had frigate duties added to a littoral ship, FFG(X) added littoral penetration and unmanned-system duties to a frigate.
- 24:50The parent-design competition offered several kinds of risk reductionChapter
The FFG(X) contestants ranged from an American cutter and LCS derivatives to established European frigates with very different strengths.
- 28:44QuestionWhy prefer Type 26 for anti-submarine warfare when FREMM is still in production?AnswerQ&A
Its design concentrates on submarine hunting and accepts compromises elsewhere. FREMM offers greater general-purpose flexibility, while Type 26's ASW advantage remains an on-paper assessment pending service.
- 31:03Why FREMM offered a plausible parent for a large frigate programChapter
FREMM combined a functioning parent design with multi-mission flexibility, advantages that depended on retaining enough of the original ship.
- 33:22European crewing assumptions complicated American adaptationNotable Point
FREMM's crew model and integrated equipment arrangements explain why American adaptation extended beyond replacing individual components.
- 34:31How fleet size can affect naval career prospects and retentionNotable Point
Shrinking fleets can limit promotion prospects and encourage trained personnel to begin a civilian career earlier.
- 44:32Hull changes and the inferred influence of Burke standardsChapter
The hull grew as American systems were incorporated, while the discussion infers that recent destroyer standards shaped the new frigate requirements.
- 49:01Task-group frigates and independent pickets need different designsNotable Point
Light frigates and small light cruisers illustrate how ships with useful formation roles differ from larger vessels expected to hold an outer station.
- 52:01Why construction continues on the first two Constellation hullsNotable Point
Continued work on the first two Constellation hulls was reportedly intended to support the yard while policymakers considered its longer-term use.
- 53:43Small-combatant numbers and a proposed baseline for the successor frigateChapter
The fleet-plan breakdown separates mine-warfare LCS from frigates, while the Legend-derived first flight is interpreted as a step toward a more capable successor.
- 1:00:44Constellation's mission list and the argument for an ASW priorityChapter
The four-mission description prompts a debate over whether ASW should have governed the frigate's design.
- 1:03:01The proposed weapons fit for an ASW-first frigateNotable Point
The proposed alternative combines ASW priority with surface-attack canisters, electronic warfare, and a less extensive initial air-defence fit.
- 1:05:12Combined warfare systems, ship size, and fleet numbersNotable Point
Type 83 and a hypothetical all-third-rate Royal Navy illustrate the technical and force-structure costs of concentrating capability in every ship.
- 1:07:55Point defence, area air warfare, and the meaning of FFGNotable Point
A report footnote's definition of guided-missile ships is compared with the Perry's Cold War launcher and fire-control arrangements.
- 1:10:21Why Constellation invited comparisons with the BurkeNotable Point
Familiar ship labels and systems could obscure a frigate's intended role; a less extensive initial missile fit is proposed as one way to distinguish it.
- 1:11:08Supporting an Aegis air battle and leading oneNotable Point
Constellation is described primarily as an additional missile contributor, with limited independent air-defence capability also acknowledged.
- 1:16:50An unstable procurement drumbeat erodes cost and yard confidenceChapter
Six orders through FY2024 fell short of the earlier nine-ship trajectory, weakening the case for a second yard and a steady production rate.
- 1:19:45Why the first frigate carries design and tooling costsNotable Point
Detailed design, hull tooling, and production learning explain why a lead frigate's estimated price differs from follow-on costs.
- 1:21:24Commonality collapsed as design changes accumulatedChapter
Quoted reporting puts FREMM commonality at about 85 percent initially and roughly 15 percent after extensive alterations.
- 1:26:03How equipment substitutions spread through a parent designNotable Point
Bridge-layout comparisons and American equipment substitutions explain how individually small changes can consume a parent design's expected advantages.
- 1:30:03Construction began before the basic design stabilizedChapter
The quoted June 2025 assessment describes continuing changes to basic arrangements after construction had begun.
- 1:32:28Why high modelling-completion figures did not establish a stable designNotable Point
The diagram distinguishes 3D modelling completion from module construction, exposing the problem of building against a design that keeps changing.
- 1:35:08Weight growth consumes capability reserved for the ship's futureNotable Point
A reported 759-metric-ton increase consumed weight margin intended to accommodate future changes to the ship.
- 1:36:30Requirements control depends on someone empowered to say noNotable Point
The proposed diagnosis is an accumulation of well-intentioned improvements without enough restraint on the initial configuration.
- 1:38:52An early Burke Flight III proposal and the sequencing of improvementsNotable Point
The Burke example distinguishes an early proposed Flight III from the later design and considers when improvements enter a shipbuilding program.
- 1:40:05QuestionWhy was the Constellation program cancelled?AnswerQ&A
The explanation offered is that the design still had not been settled. Known yard constraints contributed to delay, while the first two ships were still expected to be completed.
- 1:44:03Design rights and the value of what a derivative retainsNotable Point
Low commonality prompts a comparison between buying a parent design and learning from another navy's frigate through a fact-finding visit.
- 1:46:01The case for buying a flotilla frigate in numbersNotable Point
The closing argument links the successor's role as a group-operating frigate to sustained orders and enough ships in service.
- 1:47:44QuestionCould the US Navy have selected a parent design for Constellation and honestly retained something close to 85 percent commonality with FREMM?AnswerQ&A
The closing assessment doubts that 85 percent was realistic. About 60 percent is suggested tentatively, with a clean-sheet Perry-style frigate proposed as another possible approach.