This page shows textual changes in the document between the two versions indicated in the dates above. Textual matter removed in the later version is indicated with red strikethrough and textual matter added in the later version is indicated with blue.
The Navy began procuring Constellation (FFG-62) class frigates (FFGs) in FY2020, and a total of six have been procured through FY2024. Current Navy plans call for procuring a total of at least 20 FFG-62s. The Navy's proposed FY2025 budget requests $1,170.4 million (i.e., about $1.2 billion) for the procurement of the seventh ship in the program. The Navy's FY2025 budget submission programs the procurement of an additional six FFG-62s during the period FY2026-FY2029 in annual quantities of 2-1-2-1.
FFG-62s are being built by Fincantieri/Marinette Marine (F/MM) of Marinette, WI. F/MM was awarded a fixed-price incentive (firm target) contract for Detail Design and Construction (DD&C) for up to 10 ships in the program—the lead ship plus nine option ships.
A May 2024 Government Accountability Office (GAO) report on the FFG-62 program states
To reduce technical risk [in the FFG-62 program], the Navy and its shipbuilder [in designing the FFG-62] modified an existing [Italian-French frigate] design to incorporate [U.S.] Navy specifications and weapon systems. However, the Navy's decision to begin construction [of the first FFG-62] before the design was complete is inconsistent with leading ship design practices and jeopardized this approach….
Delays in completing the ship design have created mounting construction delays. The Navy acknowledges that the April 2026 delivery date, set in the contract at award, is unachievable. The lead frigate is forecasted to be delivered 36 months later than initially planned. The program office tracks and reports design progress, but its design stability metric hinges largely on the quantity—rather than quality—of completed design documents. This limits insight into whether the program's schedule is achievable. If the Navy begins construction on the second frigate without improving this metric, it risks repeating the same errors that resulted in construction disruptions and delays with the lead frigate….
The frigate is using a traditional, linear development approach for design and construction. The Navy has historically experienced schedule delays, cost growth, or both in prior shipbuilding programs using this approach. The Navy has incorporated elements of leading practices into its acquisition strategy. However, further incorporating these practices in an updated acquisition strategy could position the program, when contracting for future frigates, to better respond to evolving mission needs.
The FFG-62 program presents several potential oversight issues for Congress, including the following:
This report provides background information and discusses potential issues for Congress regarding the Navy's Constellation (FFG-62) class frigate program, a program to procure a new class of at least 20 guided-missile frigates (FFGs). The Navy began procuring FFG-62 class ships in FY2020, and a total of six have been procured through FY2024. The Navy's proposed FY2025 budget requests $1,170.4 million (i.e., about $1.2 billion) for the procurement of the seventh ship in the program. FFG-62s are being built by Fincantieri/Marinette Marine (F/MM) of Marinette, WI.
Constellation (FFG-62) class program. The Navy began procuring Constellation (FFG-62) class frigates in FY2020. Prior to November 2025, Navy plans called for procuring a total of at least 20. Six were procured through FY2025, including one per year in FY2020-FY2023, two in FY2024, and none in FY2025. The Navy's proposed FY2026 budget did not request the procurement of any additional FFG-62s. FFG-62s are being built by Fincantieri/Marinette Marine (F/MM) of Marinette, WI. The FFG-62 design is derived from the design of an Italian-French frigate. Subsequent to the Navy's April 2020 contract award to F/MM for designing and building up to 10 FFG-62s, the program fell years behind schedule due in large part to delays in completing the FFG-62 design. In June 2025, Secretary of Defense Pete Hegseth (who is using "Secretary of War" as a "secondary title" under Executive Order 14347 dated September 5, 2025) indicated that the FFG-62 program was being reviewed as one of several "difficult decisions" to be made by the Department of Defense (DOD) (which is "using a secondary Department of War designation" under Executive Order 14347) during a review of its acquisition programs. Announced FF(X) program. In a series of announcements from November 25 to December 19, 2025, the Navy stated that it wants to restructure its frigate acquisition effort by (1) truncating the FFG-62 program to no more than two ships and (2) initiating a new program to procure a different class Navy frigates, called FF(X)s, whose design would be based on that of the National Security Cutter (NSC), a frigate-like ship that has been built for the Coast Guard by Huntington Ingalls Industries/Ingalls Shipbuilding (HII/Ingalls) of Pascagoula, MS. Under the Navy's desired new approach, the third through sixth FFG-62s (which have not begun construction) would be cancelled; the first two FFG-62s (construction of which is underway) would remain under review; the first FF(X) would be awarded to HII/Ingalls on a sole-source basis and be launched (i.e., put into the water for the final stages of its construction) by 2028; and one or more additional U.S. shipyards would later be brought into the FF(X) program to expand the FF(X) production rate and compete with HII/Ingalls for future ships in the program. In announcing its desired new approach for acquiring frigates, Secretary of the Navy John Phelan stated that "the Constellation-class frigate was canceled because, candidly, it didn't make sense anymore to build it. It was 80% of the cost of a [larger DDG-51 class] destroyer and 60% of the capability. You might as well build destroyers." The continuation, for now at least, of construction work on the first two FFG-62s reportedly is intended to support F/MM in the near term, while policymakers assess how F/MM's shipbuilding capability could be used over the longer run. As of November 25, 2025, the first ship in the FFG-62 program was reportedly about 12% complete. This report provides background information and discusses potential oversight issues for Congress regarding the Navy's effort to acquire new frigates, including Constellation (FFG-62) class frigates and a type of frigate proposed by the Navy called the FF(X). The Navy began procuring Constellation (FFG-62) class frigates in FY2020. Prior to November 2025, Navy plans called for procuring a total of at least 20. Six were procured through FY2025, including one per year in FY2020-FY2023, two in FY2024, and none in FY2025. The Navy's proposed FY2026 budget did not request the procurement of any additional FFG-62s. FFG-62s are being built by Fincantieri/Marinette Marine (F/MM) of Marinette, WI. The FFG-62 design is derived from the design of an Italian-French frigate. Subsequent to the Navy's April 2020 contract award to F/MM for designing and building FFG-62s, the program fell years behind schedule due in large part to delays in completing the FFG-62 design. In June 2025, Secretary of Defense Pete Hegseth (who is using "Secretary of War" as a "secondary title" under Executive Order 14347 dated September 5, 2025) indicated that the FFG-62 program was being reviewed as one of several "difficult decisions" to be made by the Department of Defense (DOD) (which is "using a secondary Department of War designation" under Executive Order 14347) during a review of its acquisition programs.1 In a series of announcements from November 25 to December 19, 2025, the Navy stated that it wants to restructure its frigate acquisition effort by (1) truncating the FFG-62 program to no more than two ships and (2) initiating a new program to procure a different class Navy frigates, called FF(X)s, whose design would be based on that of the National Security Cutter (NSC), a frigate-like ship that has been built for the Coast Guard by Huntington Ingalls Industries/Ingalls Shipbuilding (HII/Ingalls) of Pascagoula, MS. Under the Navy's desired new approach, the third through sixth FFG-62s (which have not begun construction) would be cancelled; the first two FFG-62s (construction of which is underway) would remain under review; the first FF(X) would be awarded to HII/Ingalls on a sole-source basis and be launched (i.e., put into the water for the final stages of its construction) by 2028; and one or more additional U.S. shipyards would later be brought into the FF(X) program to expand the FF(X) production rate and compete with HII/Ingalls for future ships in the program.2 In announcing its desired new approach for acquiring frigates, Secretary of the Navy John Phelan stated that "the Constellation-class frigate was canceled because, candidly, it didn't make sense anymore to build it. It was 80% of the cost of a [larger DDG-51 class] destroyer3 and 60% of the capability. You might as well build destroyers." 4 The continuation, for now at least, of construction work on the first two FFG-62s reportedly is intended to support F/MM in the near term, while policymakers assess how F/MM's shipbuilding capability could be used over the longer run. 5 As of November 25, 2025, the first ship in the FFG-62 program was reportedly about 12% complete.6The FFG-62 program presents several potential oversight issues for Congress. Congress's decisions on the program could affect Navy capabilities and funding requirementsDelay in Delivery of First Ship
Figures
Appendixes
Summary
Introduction
In discussing its force-level goals and 30-year shipbuilding plans, the Navy organizes its surface combatants into large surface combatants (LSCs), meaning the Navy's cruisers and destroyers, and small surface combatants (SSCs), meaning the Navy's frigates, Littoral Combat Ships (LCSs), mine warfare ships, and patrol craft.17 SSCs are smaller, less capable in some respects, and individually less expensive to procure, operate, and support than LSCs. SSCs can operate in conjunction with LSCs and other Navy ships, particularly in higher-threat operating environments, or independently, particularly in lower-threat operating environments.
The Navy's force of SSCs at the end of FY2023 consisted of 31 ships, including no frigates, 23 LCSs, and 8 mine warfare ships.
The Navy's FY2025 30-year (FY2025-FY2054) shipbuilding plan calls for a future Navy of 381 manned battle force ships, including 73 SSCs, of which 15 are to be LCSs capable of conducting mine warfare operations, plus 58 "FFG / FFG Flt II" ships, meaning 58 frigates and frigates built to a modified (i.e., Flight II) design.28 Under its FY2025 budget submission, the Navy wantswanted to maintain a force of 25 (rather than 15) LCSs. This could imply a total of 48 (rather than 58) frigates.
The Navy's force of SSCs at the start of FY26 consisted of 32 ships, including no frigates, 28 LCSs, and 4 mine warfare ships. The Navy has been retiring its mine warfare ships as LCSs (some of which are to serve as replacement mine countermeasures ships) have entered service. The figure of 32 ships equates to about 44% of the 73-ship force-level goal for SSCs discussed in the previous section.In contrast to cruisers and destroyers, which are designed to operate in higher-threat areas, frigates are generally intended to operate more in lower-threat areasThe Navy reportedly has prepared a new ship force-level objective, referred to as the Golden Fleet, to succeed the 381-ship objective. The composition of this new force-level objective, including the number of frigates and other SSCs, had not been announced as of late December 2025.9
SSC Force at Start of FY2026
since frigates are intended to do so in lower-threat areas, they are equipped with fewer weapons, less-capable radars and other systems, and less engineering redundancy and survivability than cruisers and destroyers.3
The most recent class of frigates operated by the Navy was the Oliver Hazard Perry (FFG-7) class (Figure 1). A total of 51 FFG-7s were procured between FY1973 and FY1984. The ships were built by three shipyards,411 entered service between 1977 and 1989, and were decommissioned between 1994 and 2015. In their final configuration, FFG-7s were about 455 feet long and had full load displacements of roughly 3,900 tons to 4,100 tons. (By comparison, the Navy's Arleigh Burke [DDG-51] class destroyers are about 510 feet long and have full load displacements of roughly 9,700 tons.512) Following their decommissioning, a number of FFG-7s, like certain other decommissioned U.S. Navy ships, have beenwere transferred to the navies of U.S. allied and partner countries.
Figure 1. Oliver Hazard Perry (FFG-7) Class Frigate Source: Photograph accompanying Dave Werner, "Fighting Forward: Last Oliver Perry Class Frigate Deployment," Navy Live, January 5, 2015, accessed September 21, 2017, at http://navylive.dodlive.mil/2015/01/05/fighting-forward-last-oliver-perry-class-frigate-deployment/. FFG-62 Class Program
The FFG-62 program was previouslyearlier known as the FFG(X) program.613 On October 7, 2020, the Navy announced that the first ship in the class, FFG-62,FFG-62 would be named Constellation, in honor of the first U.S. Navy ships authorized by Congress in 1794—the six heavy frigates United States, Constellation, Constitution, Chesapeake, Congress, and President. FFG(X)s henceforth became known as Constellation (FFG-62) class ships.
|
|
FFG-62s (Figure 2, Figure 3, and Figure 4) are Ship Design and Capabilities
FFG-62s (Figure 2) are intended to be multimission small surface combatants capable of conducting anti-air warfare (AAW), anti-surface warfare (ASuW), antisubmarine warfare (ASW), and electromagnetic warfare (EMW) operations. They are to be capable of operating in both blue water (i.e., mid-ocean) and littoral (i.e., near-shore) areas, and capable of operating either independently (when that is appropriate for their assigned missions) or as part of larger Navy formations.
Artist's rendering of F/MM design
At the time of the FFG-62 contract award (see below), the FFG-62 was described as having an estimated full load displacement of about 7,300 or 7,400 tons. As design work on the FFG-62 continued, the ship's estimated full load displacement grew by several hundred tons, to a figure much closer to 8,000 tons. (As noted earlier, by comparison, the Navy's newest DDG-51 class destroyers have full load displacements of roughly 9,700 tons.)The Navy wants
Total Procurement Quantity
Until November 2025, the Navy wanted to procure at least 20 FFG-62s. Navy budget documents, including the FY2025 budget-justification book for Navy's shipbuilding account, describedescribed the FFG-62 program as a 20-ship program.
As discussed earlier, the Navy's FY2025 30-year (FY2025-FY2054) shipbuilding plan calls for a future Navy of 381 manned battle force ships, including 58 "FFG / FFG Flt II" ships, meaning 58 frigates and frigates built to a modified (i.e., Flight II) design.714 The reference to a Flight II design might be interpreted as referring to a modified (i.e., Flight II) version of the FFG-62 design. Such an interpretation would imply a combination of 20 (or more) FFG-62s built to the original (i.e., Flight I) FFG-62 design plus 38 (or fewer) additional FFG-62s built to a modified (i.e., Flight II) FFG-62 design.
As also mentioneddiscussed earlier, under its FY2025 budget submission, the Navy wants to maintain a force of 25 (rather than 15) LCSs. This could imply a total of 48 (rather than 58) frigates.
Table 1 shows programmed and actual annual procurement quantities for the FFG-62 program.
FFG-62s generally have budgeted procurement costs of roughly $1.1 billion to $1.2 billion each. The lead ship in the program has a higher estimated procurement cost ($1,386.7 million, or about $1.4 billion) than the follow-on ships because it is at the top of the production learning curve for the class, and because the lead ship's procurement cost incorporates much of the detailed design/nonrecurring engineering (DD/NRE) costs for the class. (It is a traditional Navy budgeting practice to attach most or all of the DD/NRE costs for a new ship class to the procurement cost of the lead ship in the class.)
Computer rendering of F/MM design as of 2020 |
|
|
FY20 |
FY21 |
FY22 |
FY23 |
FY24 |
FY25 |
FY26 |
FY27 |
FY28 |
FY29 |
||
|
Programmed |
|||||||||||
|
FY20 budget submission |
1 |
2 |
2 |
2 |
2 |
||||||
|
FY21 budget submission |
1 |
1 |
2 |
2 |
3 |
||||||
|
Dec. 9, 2020, document |
1 |
3 |
3 |
4 |
4 |
||||||
|
FY22 budget submission |
1 |
n/a |
n/a |
n/a |
n/a |
||||||
|
FY23 budget submission |
1 |
2 |
1 |
2 |
1 |
||||||
|
FY24 budget submission |
2 |
1 |
2 |
1 |
2 |
||||||
|
FY25 budget submission |
1 |
2 |
1 |
2 |
1 |
FY26 budget submission |
0 |
n/a |
n/a |
n/a |
n/a |
|
Actual |
1 |
1 |
1 |
1 |
2 |
|
|
0 |
||||
Sources: Table prepared by CRS based on Navy's FY2020-FY2025FY2026 budget submissions; December 9, 2020, long-range Navy shipbuilding document; and enacted National Defense Authorization Acts (NDAAs) and DOD Appropriations Acts for FY2020 and subsequent years.
Notes: n/a means not available. DOD's FY2022 budget submission was a single-year budget that did not contain line-item details for subsequent fiscal years.
The Navy's baseline plan for the FFG-62 program envisaged using a single builder at any one time to build FFG-62s, but Navy officials have also spoken about the option of bringing a second shipyard into the program at some point, particularly if annual procurement rates for FFG-62s rise above two ships per year. The Navy's FY2025 30-year (FY2025-FY2054) shipbuilding plan states (emphasis added)
The Navy is mindful that as fleet composition evolves to meet competition and combat requirements, the Navy must examine alternative opportunities within the industrial base. Alternative opportunities include adjusting procurement profiles ensuring stability in shipyard workload to prevent "boom and bust" periods of shipyard activity, and ensuring ample competitive opportunities for current and future platforms (i.e., AS(X), LSM, T-AOL, T-ARC), and a potential FFG 62 second source for construction once the design and technical data package is mature and risks are reduced and validated. These opportunities allow the current industrial base to adapt while maintaining the capacity to deliver the capability the nation needs.8
On November 15, 2024, the Navy released a Sources Sought Request for Information (RFI) "to identify qualified U.S. surface combatant Shipbuilders as sources for future design and/or follow-on construction of the Constellation Class Frigate," inviting "all U.S. surface combatant shipbuilding sources who are interested in the FFG 62 Class ships, to submit written information sufficient to demonstrate their ability to fulfill the Government requirements." Responses to the RFI are due by November 22, 2024.9
In December 2024, a Navy official reportedly stated that having a mature design for the FFG-62 program—something that the Navy reportedly anticipates having by May 2025—"will form the basis of a potential follow-on contract competition [i.e., a potential competition to select a second shipyard] anticipated in" FY2027.10
The Navy's baseline plan for the FFG-62 program envisaged using a single builder at any one time to build FFG-62s, but Navy officials also spoke about the option of bringing a second shipyard into the program at some point, particularly if annual procurement rates for FFG-62s rose above two ships per year.15
As noted earlier, FFG-62s are to be built to a modified version of an existing ship design—an approach, called the parent-design approach, that in theory can reduce design time, design cost, and cost, schedule, and technical risk in building the ship. Industry teams competing for the FFG-62 were required to show that their bid was based on a parent design. The Coast Guard and the Navy are currently using the parent-design approach for the Coast Guard's Polar Security Cutter (PSC) (i.e., heavy i.e., polar icebreaker) program16 and the Navy's medium landing ship (LSM) program.17.11 The parent-design approach has also been used in the past for other Navy and Coast Guard ships, including Navy mine warfare ships1218 and the Coast Guard's new Fast Response Cutters (FRCs).13
Some observers have questioned the value of using parent designs in military shipbuilding programs. A 2015 journal article, for example, states
The U.S. Navy has experimented with many approaches to design and build its ships. Using an existing design as the "parent" design, also referred to as "modified-repeat" design, is on its face an attractive option. Many acquisition executives, program managers and some ship design engineers believe that a design based on a parent has fewer technical risks than a new "clean sheet of paper" design and therefore the time and cost to design and build it will be reduced. They assume early in the ship acquisition program that "the design is mature" and because of that fewer problems will be encountered in completing the design and savings will thus be accrued. Yet, a number of naval ships based on a parent design have in fact experienced unanticipated cost and schedule growth during construction as well as technical problems during their in-service life. The authors will examine some of these ship designs which were based on an existing design and/or prototypes and highlight the fallacies of such beliefs and assumptions.14
Figure 53 shows a U.S. Navy briefing slide summarizing what the U.S. Navy says are the "primary differences between the FFG 62 Class [design] and the FREMM Parent design." The Navy states that the design differences "were proposed by [the shipbuilding firm] Fincantieri and incorporated [into Fincantieri's proposed design for the FFG-62] prior to [the Navy's] contract award [for the FFG-62 program to Fincantieri]."15
21 An August 4, 2021, press report states
The Navy has chosen to elongate and widen the hull of its next-generation Constellation-class frigate relative to the [FREMM] parent design, but the officer overseeing its production says the internal layout will largely remain the same.
"The Italians did a very good job in the design of the internal spaces, and the flow of a lot of those spaces," Capt. Kevin Smith, program manager for the Constellation class, told attendees at the Sea Air Space exposition on Monday [August 2]. "You could say we bought a bigger house, [but] from a modeling and simulation perspective, it's exactly the same."…
While some changes are to be expected to meet the Navy's needs, enlarging the hullform itself has the potential to change where components in the ship must be placed, as well as the overall cost.
Asked about how possible changes in the ship's hull could affect the internal design, Smith said Fincantieri Marinette Marine, the Constellation's prime contractor, worked with Naval Surface Warfare Center Carderock to develop a scale model of the ship and that most elements will stay true to the parent design. He cited the bridge and propulsion plant as areas where the Navy has not made any significant changes to the layout.16
22
Source: Navy briefing slide provided to CRS and Congressional Budget Office (CBO) by Navy Office of Legislative Affairs, August 27, 2021, with accompanying Navy information paper dated August 18, 2021.
An April 2, 2024, press report states: "At one point the Constellation design shared about 85 percent commonality with the original FREMM design, but the alterations have brought that commonality down to under 15 percent, a person familiar with the changes told USNI News."
1723 If the FFG-62 design shares less than 15% commonality with the FREMM design, then some observers might characterize the FFG-62 program as having moved over time toward what might be termed a parent design in name only (PDINO) design approach.18
A Navy official commenting on the FFG-62 program in February 2025 reportedly stated that "[it] turns out modifying someone else's design is a lot harder than it seems," and that "sometimes, you're just better off designing a new ship."1925 Another Navy official, also commenting on the FFG-62 program in February 2025, reportedly stated that "I'll be brutally honest, I don't think people truly understood what it meant to adapt a parent design to Navy requirements."20
As an additionala measure for reducing cost, schedule, and technical risk in the FFG-62 program, the Navy envisagesenvisaged developing no new technologies or systems for FFG-62s—the ships are to use systems and technologies that already exist or are already being developed for use in other programs.
Section 125 of the FY2021 National Defense Authorization Act (H.R. 6395/P.L. 116-283 of January 1, 2021) requires the Navy to commence, prior to the delivery of the first FFG-62, a land-based test program for the FFG-62 engineering plant (i.e., its propulsion system and related machinery). The provision specifies how the test program is to be conducted and requires the Navy to complete the test program not later than the date on which the first FFG-62 is scheduled to be available for tasking by operational military commanders.21
Section 856 of the FY2020 National Defense Authorization Act (S. 1790/P.L. 116-92 of December 20, 2019) states
SEC. 856. APPLICATION OF LIMITATION ON PROCUREMENT OF GOODS OTHER THAN UNITED STATES GOODS TO THE FFG–FRIGATE PROGRAM.
Notwithstanding any other provision of law, amounts authorized to carry out the FFG–Frigate Program may be used to award a new contract that provides for the acquisition of the following components regardless of whether those components are manufactured in the United States:
(1) Auxiliary equipment (including pumps) for shipboard services.
(2) Propulsion equipment (including engines, reduction gears, and propellers).
(3) Shipboard cranes.
(4) Spreaders for shipboard cranes.
Section 8097(b) of the FY2024 DOD Appropriations Act (Division A of H.R. 2882/P.L. 118-47 of March 23, 2024) states
SEC. 8097….
(b) None of the funds provided in this Act for the FFG(X) Frigate program shall be used to award a new contract that provides for the acquisition of the following components unless those components are manufactured in the United States: Air circuit breakers; gyrocompasses; electronic navigation chart systems; steering controls; pumps; propulsion and machinery control systems; totally enclosed lifeboats; auxiliary equipment pumps; shipboard cranes; auxiliary chill water systems; and propulsion propellers: Provided, That the Secretary of the Navy shall incorporate United States manufactured propulsion engines and propulsion reduction gears into the FFG(X) Frigate program beginning not later than with the eleventh ship of the program.
Provisions similar to Section 8097(b) have been included in annual DOD appropriations acts since the FY2020 DOD appropriations act.
Four industry teams competed for the FFG-62 program. On April 30, 2020, the Navy announced that it had awarded the FFG-62 contract to the team led by Fincantieri/Marinette Marine (F/MM) of Marinette, WI. F/MM was awarded a fixed-price incentive (firm target) contract for Detail Design and Construction (DD&C) for up to 10 ships in the programFFG-62s—the lead ship plus nine option ships. The other three industry teams reportedly competing for the program were led by Austal USA of Mobile, AL; General Dynamics/Bath Iron Works (GD/BIW) of Bath, ME; and Huntington Ingalls Industries/Ingalls Shipbuilding (HII/Ingalls) of Pascagoula, MS.
Under the DD&C contract, the Navy has the option of recompeting the program at any point prior to the 10th ship. The Navy also has the option of seeking to convert the DD&C at some point into a multiyear contract known as a block buy contract to procure the ships.22
A June 2, 2021, Navy press release stated
Naval Station Everett23 was designated as the Navy's future homeport for the initial ships of the next generation of guided missile frigates, a new and improved class of small surface combatant ships.
As an important homeport for Navy ships, Naval Station Everett will continue to support the fleet, its service members, and their families.
Everett will serve as As noted earlier, industry teams competing for the FFG-62 were required to show that their bid was based on a parent design. The team led by F/MM based its bid on the Italian-French FREMM frigate. The team led by Austal based its bid on Independence (LCS-2) class Littoral Combat (LCS) design (a design that Austal was building for the U.S. Navy).27 The team led by GD/BIW based its bid on the Spanish Navantia F100 frigate design. At the time of the competition, the team led by HII/Ingalls did not publicly disclose its parent design.28 December 2025 press reports stated that HII now acknowledges that its parent design was the NSC design.29
Home Port for Initial Ships in Class
A June 2, 2021, Navy press release stated that "Naval Station Everett30 was designated as the Navy's future homeport for the initial ships" in the FFG-62 program, serving as "the homeport for 12 Constellation-class Frigates, with a future Navy homeport decision planned for the following ships.24
In January 2024, it was reported that the delivery of the first ship in the program would be delayed by at least one year, primarily due to shortages of workers at F/MM.25
The Navy's FY2025 budget submission, which was submitted to Congress on March 11, 2024, showed the lead ship's scheduled delivery date as December 2027—15 months later than the September 2026 scheduled delivery date shown in the Navy's FY2024 budget submission. The FY2025 budget submission states that delivery dates for the second and subsequent ships in the program are under review.26
On April 2, 2024, as part of an announcement of significant delays to several of its shipbuilding programs caused by shipbuilder workforce challenges, supply chain issues, and other causes, the Navy announced that the estimated delay in the delivery of the first FFG-62 had grown to 36 months. In the Navy's budget submission for FY2020—the submission in which the Navy requested, and Congress funded, the procurement of the first FFG-62—the Navy estimated that the first FFG-62 would have a 72-month period from contract award to delivery, and within that 72-month period, a 48-month period from construction start to delivery. A 36-month delay in the delivery of the first FFG-62 would equate to a 50% addition to the 72-month period and a 75% addition to the 48-month period.
An April 2, 2024, press report about the Navy's announcement stated
During a media roundtable with reporters on Tuesday [April 2], Naval Sea Systems Command chief Vice Adm. James Downey told reporters that the detail design for the frigate—which is based on Fincantieri Marinette Marine's FREMM parent design that's in service with the Italian and French navies—still isn't complete. The goal is to finalize the detail design this year and the service and contractors are nearing 80 percent completion, Downey said.27
"Some of the mix of the contracting roles have changed between prime and sub," Downey told reporters. "And finishing the design has been critical for us. That's why we've co-located the design force from Fincantieri and their sub with the government in a collaboration center up there to finish."
In August of 2022, when the Navy green lit Fincantieri to begin building the first frigate, Rear Adm. Casey Moton, then the program executive officer for unmanned and small combatants, said the detail design was just over 80 percent complete.
Asked what's driving the delays at Marinette, Downey cited the yard's increased workload, difficulty hiring and keeping talent, and the varying stages of the three programs currently under construction there. The yard is finishing the end of the Littoral Combat Ship line, while also building Saudi Arabia's multi-mission surface combatant and the U.S. Navy's new frigate.
Downey said the attrition at Marinette is "significantly different" with the yard building those three programs compared to when it was only building the LCS….
To tackle the workforce shortfalls, the Navy plans to give Marinette $50 million for the surface combatant industrial base.28 The yard is using those funds to incentivize both its blue and white collar workforce with bonuses to stay at Marinette.29
An April 12, 2024, press report stated
The shipyard producing the US Navy's new frigate has been hobbled by a failure to "achieve engineering and skilled workforce levels" for the medium-sized vessel, according to a service document on the project that's now forecast to run as much as three years late.
Fincantieri Marinette Marine has experienced "unprecedented poor workforce retention—high attrition rates," according to an unreleased Navy briefing slide prepared for senior service and Pentagon officials late last month. It spelled out the shipyard's woes in more detail than the publicly released findings of top Navy programs released last week.
The company will require more than 1,600 skilled workers next year, up from more than 900 today, according to the slide….
Navy Secretary Carlos Del Toro acknowledged the frigate builder's retention issue in a brief interview after congressional testimony on Wednesday [April 10]. He said the service has provided incentive fees for workers to stay on the job—$5,000 if they stay a first year and $5,000 "if they stay throughout construction of the first ship," he said. "We've been trying to work with industry to get them to a better place," he said….
Vice Admiral James Downey, head of Naval Sea Systems Command, told reporters last week that in addition to workforce hiring and retention issues, the frigate delay stemmed in part from the ship's incomplete design and to Fincantieri working on three programs simultaneously at its Wisconsin yard, including a vessel for Saudi Arabia.
Fincantieri spokesman Eric Dent said in a statement that "we understand" the 36-month delay is a worst-case scenario.
"We know we are on the clock, so challenge accepted," he said. "We need to improve on a range of workforce issues for sure, and we need a Navy-approved design. We will get there, but we cannot do it alone."30
A May 2024 Government Accountability Office (GAO) report on the FFG-62 program stated
A June 2025 Government Accountability Office (GAO) report—the 2025 edition of an annual GAO report on selected DOD acquisition programs—stated the following regarding schedule delay and other aspects of the FFG-62 program:
Program Performance
Since our last assessment, the program continued to face challenges completing its functional design, which is needed to demonstrate design stability. More than 2 years after beginning lead ship construction, this persistent lack of design stability stalled construction of the lead ship and poses the same risk to initial follow-on ships. The Navy currently plans to deliver the lead frigate in April 2029—3 years later than the original contracted delivery date. The Navy and shipbuilder continue to revise basic design documents, including the ship's general arrangement drawings—the design drawings that all other design aspects are based on—and structural components of the ship. This approach is inconsistent with shipbuilding leading practices, which call for completion of basic and functional design activities prior to construction start.
Further, in response to a recommendation we made in our May 2024 report, the program restructured its functional design metrics to more closely align with actual design progress. As a result, the program concluded that its functional design progress is significantly less than the 92 percent complete it reported in August 2023. As of December 2024, the program reported that the functional design was 70 percent complete, as measured with the restructured design metrics. Although program officials expect to achieve a stable basic and functional design by late spring 2025, the program has yet to achieve its planned rate of design progress to meet this goal.
The frigate design is further complicated by unanticipated weight growth. In October 2024, the Navy reported 759 metric tons of weight growth from initial estimates—nearly a 13 percent increase—due in part to the underestimation of applying Navy technical requirements to a foreign ship design. Navy personnel are working with the shipbuilder to reduce the ship's weight, but weight growth has only become more pronounced over the last year as the program further developed the frigate design. We previously reported that unplanned weight growth during ship construction can compromise ship capabilities, as the fleet seeks to alter and improve initial capabilities over the planned decades-long service life of the ship. Such alterations may leave frigates less combat capable, limit the ability to add capabilities to address evolving threats, and reduce planned service lives.
Leading Product Development Practices
In May 2024, we reported that the frigate program employed a traditional, linear development approach to acquisition, in contrast to leading companies' use of iterative design approaches centered on identifying a minimum viable product to quickly meet users' needs. We recommended that the Navy evaluate ways to incorporate these leading practices into the frigate acquisition strategy prior to the acquisition of an 11th ship. The Navy stated that it is taking steps to implement this recommendation.
Program officials stated that plans for a digital twin and digital thread will not be incorporated into program documentation until 2025. Officials stated that they have encountered challenges with the availability of data, cost of data environments, and finding skilled personnel. Additionally, as we reported in January 2025, the program's documents contain general language about MOSA [modular open system approach] principles but do not address planning elements for modularity.
Other Program Issues
As of November 2024, frigate program officials reported that the shipbuilder had submitted a total of five requests for equitable adjustment, raising the potential of unbudgeted program cost growth, depending on the outcome. Requests for equitable adjustment provide a remedy payable only when unforeseen or unintended circumstances, such as government modification of the contract, cause an increase in contract performance costs. The Navy deemed the total costs of the five requests as not suitable for public release. According to program officials these requests relate to government change orders and significant design changes from the frigate's parent ship design.
Despite the unresolved issues identified above, the Navy has proceeded full steam ahead with the frigate program, exercising options for the fifth and six ships in May 2024. Further, in November 2024, the Navy requested information seeking shipbuilders to serve as a second shipyard for constructing future frigates. In January 2025, the Navy began assessing industry responses to inform future acquisition strategies.
Program Office Comments
We provided a draft of this assessment to the program office for review and comment. The program office provided technical comments, which we incorporated where appropriate. The program office stated that in early spring 2025, it anticipates completing design products needed to support production. According to the program office, the Navy increased its leadership and technical presence at the shipyard, including contracted engineering support personnel. The program office further noted that it continues to work with the shipbuilder on frigate weight reduction and identified potential weight savings to regain service life allowance through a phased implementation across the first three ships. According to the program office, the requests for equitable adjustment are currently under Navy review. In April 2025, the office of DOD's Director, Operational Testing and Evaluation provided comments stating that the start date for the program's operational test should be reflected as the first quarter of fiscal year 2032.
A May 2024 Government Accountability Office (GAO) report on the FFG-62 program stated,To reduce technical risk [in the FFG-62 program], the Navy and its shipbuilder [in designing the FFG-62] modified an existing [Italian-French frigate] design to incorporate [U.S.] Navy specifications and weapon systems. However, the Navy's decision to begin construction [of the first FFG-62] before the design was complete is inconsistent with leading ship design practices and jeopardized this approach. Further, design instability has caused weight growth. The figure shows the frigate's 3D design—a component of design stability—as incomplete over 1 year after construction began.
Delays in completing the ship design have created mounting construction delays. The Navy acknowledges that the April 2026 delivery date, set in the contract at award, is unachievable. The lead frigate is forecasted to be delivered 36 months later than initially planned. The program office tracks and reports design progress, but its design stability metric hinges largely on the quantity—rather than quality—of completed design documents. This limits insight into whether the program's schedule is achievable. If the Navy begins construction on the second frigate without improving this metric, it risks repeating the same errors that resulted in construction disruptions and delays with the lead frigate.
The frigate is using many mission systems already proven on Navy ships. However, the Navy has yet to demonstrate two systems—the propulsion and machinery control systems. A planned update to the frigate test plan—combined with the opportunity afforded by schedule delays—could offer the Navy the chance to conduct land-based testing of these two unproven systems. This testing would reduce the risk of discovering issues after the ship is at sea.
The frigate is using a traditional, linear development approach for design and construction. The Navy has historically experienced schedule delays, cost growth, or both in prior shipbuilding programs using this approach. The Navy has incorporated elements of leading practices into its acquisition strategy. However, further incorporating these practices in an updated acquisition strategy could position the program, when contracting for future frigates, to better respond to evolving mission needs.31
A December 13, 2024, press report states
The Constellation-class frigate's design should be mature enough for the shipbuilder to enter continuous production by May, the Navy's top acquisition executive said this week….
"In the meantime, we've awarded that company a handful of different ships, and we're going to get them to the place where they could build them at speed, knowing that we're significantly delayed in getting the first ship out," Navy assistant secretary for research, development and acquisition Nickolas Guertin said Wednesday [December 11].32
One potential oversight issue for Congress concerns the estimated 36-month delay in the delivery of the first ship in the program. Potential oversight questions for Congress include the following:
Another potential issue for Congress concerns the potential for cost growth in the FFG-62 program, particularly after the first 10 ships in the program, which are to be procured under a fixed-price incentive (firm target) contract. As discussed in greater detail in earlier versions of this CRS report,33 CRS and CBO analyses done in 2020 suggested that if FFG-62s were to wind up costing about the same to construct per thousand tons of displacement as other recent U.S. military surface combatants, then FFG-62s could cost substantially more to build than their budgeted unit procurement costs. The preliminary CRS analysis, done by CRS following the Navy's April 30, 2020, contract award in the FFG-62 program, suggested that if FFG-62s were to wind up costing about the same to construct per thousand tons of displacement as other recent U.S. military surface combatants, then the third and subsequent FFG-62s could cost 17% to 56% more than the budgeted estimates for those ships in the Navy's FY2021 budget submission. A follow-on and more refined analysis of the issue that was done by CBO and released on October 13, 2020,34 and which also compared the Navy's FFG-62 budgeted cost estimate to actual costs for building other recent U.S. military surface combatants, estimated that the first 10 FFG-62s would cost 40% more to build than the Navy estimates. An October 2023 CBO report on the cost of the Navy's FY2024 30-year shipbuilding plan, based on updated Navy and CBO figures, estimated that FFG-62s on average will cost 10% to 20% more than the updated Navy estimates.35
The May 2024 GAO report on the FFG-62 program stated that in October 2023, the FFG-62 shipbuilder reported "unplanned weight growth in the frigate design—an increase of over 10 percent above the shipbuilder's June 2020 weight estimate."36 Since ship procurement costs are generally proportional to ship displacement (i.e., weight), this weight growth suggests a potential for cost growth beyond the above-discussed figures in the 2020 and 2023 CRS and CBO analyses. The May 2024 GAO report stated: "In December 2023, the Navy initiated a separate review of frigate weight growth to assess risk. The Navy disclosed to us in April 2024 that it is considering a reduction in the frigate's speed requirement as one potential way, among others, to resolve the weight growth affecting the ship's design."37
Depending on the exact terms of the fixed-price incentive (firm target) contract that the Navy awarded to F/MM for the first 10 ships in the FFG-62 program, some portion (perhaps much) of any cost growth that might occur on the first 10 FFG-62s could be borne by F/MM rather than the Navy, although F/MM under such a circumstance might also have the option of seeking some form of contractual relief from the Navy, which if granted could shift at least some of the cost growth back to the government.38 If F/MM were to bear most or all of any cost growth that might occur on the first 10 FFG-62s, then cost growth in the FFG-62 program, if it were to occur, might not affect Navy budgeting substantially until the 11th ship in the program. Under the Navy's FY2025 budget submission, the 11th ship in the program is to be the first of the two ships that are programmed for procurement in FY2028.
Potential oversight questions for Congress include the following:
Another issue for Congress is whether and when to introduce a second shipyard into the FFG-62 program. The Navy's FFG-7s, which were procured at annual rates of as high as eight ships per year, were built at three shipyards.
As noted earlier, the Navy's baseline plan for the FFG-62 program envisaged using a single builder at any one time to build FFG-62s, but Navy officials have also spoken about the option of bringing a second shipyard into the program at some point, particularly if annual procurement rates for FFG-62s rise above two ships per year. As also noted earlier, in December 2024, a Navy official reportedly stated that having a mature design for the FFG-62 program—something that the Navy reportedly anticipates having by May 2025—"will form the basis of a potential follow-on contract competition [i.e., a potential competition to select a second shipyard] anticipated in" FY2027.40
In considering whether to build FFG-62s at a single shipyard or at two shipyards, Congress may consider several factors, including but not limited to the annual FFG-62 procurement rate, shipyard production capacities and production economies of scale, the potential costs and benefits in the FFG-62 program of employing recurring competition between multiple shipyards, and how the number of FFG-62 builders might fit into a larger situation involving the production of other Navy and Coast Guard ships, including Navy DDG-51 destroyers, Navy amphibious ships, and Coast Guard Offshore Patrol Cutters (OPCs).41
Another potential oversight issue for Congress—one discussed in this CRS report since April 201942—concerns the number of vertical launch system (VLS) missile tubes in the FFG-62 design. The VLS is the FFG-62's principal (though not only) means of storing and launching missiles. FFG-62s are to each be equipped with 32 Mark 41 VLS tubes. (The Mark 41 is the Navy's standard VLS design.)
Supporters of requiring each FFG-62 to be equipped with a larger number of VLS tubes, such as 48, might argue that FFG-62s are to be roughly three-quarters as large as the Navy's DDG-51 class destroyers, and might therefore be more appropriately equipped with at least 48 VLS tubes, which is one-half the number on recent DDG-51s. They might also argue that in a context of renewed great power competition with potential adversaries such as China, which is steadily improving its naval capabilities,43 it might be prudent to equip each FFG-62 with 48 rather than 32 VLS tubes each, and that doing so might only marginally increase FFG-62 unit procurement costs. They might also argue that equipping each FFG-62 with 48 rather than 32 VLS tubes will permit the Navy to more fully offset a substantial reduction in VLS tubes that the Navy's surface fleet is projected to experience when the Navy's 22 Ticonderoga (CG-47) class cruisers, which are each equipped with 122 VLS tubes, are retired,44 and provide a hedge against the possibility that Navy plans to field VLS tubes on Large Unmanned Surface Vehicles (LUSVs)45 will be slowed or curtailed for technical or other reasons.
Supporters of having each FFG-62 be equipped with 32 VLS tubes might argue that the analyses indicating a need for 32 VLS tubes already took improving adversary capabilities (as well as other U.S. Navy capabilities) into account. They might also argue that FFG-62s, in addition to having 32 VLS tubes, will also to have separate, deck-mounted box launchers for launching 16 anti-ship cruise missiles, as well as a separate, 21-cell Rolling Airframe Missile (RAM) AAW missile launcher; that Navy plans continue to call for eventually deploying additional VLS tubes on LUSVs, which are to act as adjunct weapon magazines for the Navy's manned surface combatants; and that increasing the number of VLS tubes on each FFG-62 from 32 to 48 would increase (even if only marginally) the procurement cost of a ship that is intended to be an affordable supplement to the Navy's cruisers and destroyers.
A May 14, 2019, Navy information paper on the cost impact of expanding the FFG-62 VLS capacity from 32 cells to 48 cells states
To grow from a 32 Cell VLS to a 48 Cell VLS necessitates an increase in the length of the ship with a small beam increase and roughly a 200-ton increase in full load displacement. This will require a resizing of the ship, readdressing stability and seakeeping analyses, and adapting ship services to accommodate the additional 16 VLS cells.
A change of this nature would unnecessarily delay detail design by causing significant disruption to ship designs. Particularly the smaller ship designs. Potential competitors have already completed their Conceptual Designs and are entering the Detail Design and Construction competition with ship designs set to accommodate 32 cells.
The cost is estimated to increase between $16M [million] and $24M [million] per ship. This includes ship impacts and additional VLS cells.46
Compared to an FFG-62 follow-on ship unit procurement cost of roughly $1.1 billion to $1.2 billion, the above estimated increase of $16 million to $24 million would equate to an increase in unit procurement cost of about 1.3% to about 2.2%.47 The estimated figure of $16 million to $24 million, however, dates to 2019. Inflating it to current costs would produce a percentage increase in total ship procurement cost that would be somewhat greater than 1.3% to 2.2%.
Another potential oversight issue for Congress concerns technical risk in the FFG-62 program.
Regarding GAO's perspective on technical risk in the FFG-62 program, see the quoted passage from the May 2024 GAO report on the FFG-62 program that is presented earlier in this CRS report, in the section on the estimated 36-month delay in the delivery of the first FFG-62.
In addition to the above-cited May 2024 GAO report, a June 2024 GAO report—the 2024 edition of GAO's annual report surveying DOD major acquisition programs—stated the following about the FFG-62 program:
Technology Maturity, Design Stability, and Production Readiness
The Navy identified no critical technologies for the frigate program. Frigate capabilities rely predominantly on successful incorporation of mission systems already developed and deployed in the Navy's fleet. For example, the frigate design includes the Enterprise Air Surveillance Radar and Aegis combat system—both currently fielded on other ship classes. Nonetheless, integrating these systems into the frigate design has necessitated changes to the scaling of hardware and development of new software code. The Navy is mitigating resulting integration risk by leveraging data from ongoing tests aboard Gerald R. Ford class aircraft carriers and Arleigh Burke class destroyers, coupled with land-based tests that began in 2023.
While the program is predominately leveraging existing mission systems to mitigate risk, two planned newly developed systems pose high technical and integration risks. The frigate will field new propulsion and machinery control systems never used by the Navy. In response to statute, the Navy is building a Land Based Engineering Site (LBES) to test these systems to mitigate development and integration risks. LBES was not expected to be fully operational prior to the previously forecasted December 2026 delivery date, according to Navy officials.
Completing functional design and 3D modeling continues to take longer than the Navy anticipated and remains incomplete over a year after beginning lead ship construction. As of October 2023, the functional design was 92 percent complete and 3D modeling was 84 percent complete. Program officials stated that they set a goal to complete 80 percent of the functional design by construction start. However, the program's approach is inconsistent with shipbuilding leading practices, which call for completion of these design activities prior to construction start.
Ongoing delays have resulted from challenges adapting a foreign ship design to meet Navy survivability requirements, outstanding vendor-furnished information needed to inform the design, and workforce issues. The Navy increased on-site coordination efforts with its shipbuilder and industry stakeholders to remedy and approve deficient design products, but progress remains limited. As a result, the shipbuilder constructed early modules using an incomplete design and, more recently, slowed construction activities to await design stability.
As a result of the delays, the shipbuilder will not meet either its April 2026 contract delivery date or its more-recently estimated December 2026 delivery date for the lead frigate, according to the program. In December 2023, the Navy reported that the lead ship will be delayed at least 1 year, but an estimated delivery date for the lead and follow-on ships will not be confirmed until the Navy completes an ongoing schedule assessment. In January 2024, the Secretary of the Navy directed a separate assessment of the shipbuilding portfolio due, in part, to concerns with the frigate program.
Software and Cybersecurity
The program is using a modern software development approach, including Agile, DevOps, and DevSecOps to develop, deliver, and test various subsystem software, such as Aegis and the machinery control system.
Initial developmental testing of Aegis software started in August 2023 at land-based test sites, with follow-on tests scheduled to occur every 1 to 3 months. Testing provides system operators with the opportunity to test radar and Aegis equipment on simulators. Machinery control system software development is planned over three software releases, comprised of six builds. The contractor has released four of these builds to date with two more planned to follow, scheduled through January 2025.
The program completed its second cyber tabletop exercise in April 2023. It also plans to conduct a vulnerability identification assessment and adversarial cybersecurity development test and evaluation in April 2024 and April 2025, respectively. Additional cybersecurity tests are planned prior to initial operational capability in 2029.
Program Office Comments
We provided a draft of this assessment to the program office for review and comment. The program office provided technical comments, which we incorporated where appropriate.
The Navy stated that it chartered an independent review team to perform a holistic assessment of the shipbuilder's production schedules, identify key issues, and recommend actions. Additionally, the Navy reported that it increased design and production efforts by bringing in both Navy and contracted engineering design support personnel at the shipbuilder's site to bolster and accelerate design stability completion and ramp-up of production.
In April 2024, after our cutoff date for new information, the Navy announced that the delivery of the lead ship was expected to be delayed approximately 3 years past the April 2026 contract delivery date.48
A January 2024 report from DOD's Director, Operational Test and Evaluation (DOT&E)—DOT&E's annual report for FY2023—stated the following regarding the FFG-62 program:
TEST ADEQUACY
In March 2023, DOT&E published a classified FFG 62 EOA [early operational assessment] report based on evaluations conducted between February 2022 and July 2022 and detailed in the FY22 Annual Report. Evaluations were adequate to determine potential FFG 62 design risks that could affect operational effectiveness and suitability of the delivered ship. The EOA provides the FFG 62 Program with an opportunity to consider modifications to the ship design. The FFG 62 Program will also use the EOA to inform development of the next TEMP [test and evaluation master plan] revision expected to be completed in FY25. The Navy conducted the EOA in accordance with a DOT&E-approved test plan, and it was observed by DOT&E.
In FY23, the Navy conducted testing against a large scale-model of a generic ship incorporating characteristics typical of Navy standard ship structure and a responding mid-deck plate to generate response data for under-bottom explosions. This test was similar to the test detailed in the FY22 Annual Report but focused on different structure response. Data from these tests provide validation data for survivability models used to predict the magnitude and extent of damage from underwater threat weapons. The Navy conducted this test in accordance with the DOT&E-approved test plan, and it was observed by DOT&E.
In FY23, the FFG 62 Program approved the FFG 62 Verification, Validation, and Accreditation (VV&A) Plans for the Advanced Survivability Assessment Program (ASAP) and Navy Enhanced Sierra Mechanics (NESM) M&S [modeling and simulation] tools. These plans are adequate to determine the sufficiency of these M&S within the LFT&E [live fire test and evaluation] test strategy. Further, the Navy continued M&S modification that incorporates new capabilities, including improvements in the blast and whipping codes. The Navy is working closely with DOT&E on the development of M&S plans to support the Detail Design Survivability Assessment Report that the FFG 62 Program expects to publish in FY26.
PERFORMANCE
EFFECTIVENESS
No data are available to determine FFG 62 operational effectiveness due to FFG 62 being in development. However, the FFG 62 design presents risks to operational effectiveness in each of its primary mission areas: air warfare, anti-submarine warfare, and surface warfare. Classified risks to operational effectiveness are in the FFG 62 EOA report. Unclassified risks to operational effectiveness include that the FFG 62 design does not have a tracker illuminator system, which is typically installed on other Aegis platforms, and that the design crew size will be highly reliant on currently unproven system automation and human system interfaces. The Navy acknowledges the risk of the current crewing strategy for FFG 62 and is working with the appropriate stakeholders to mitigate and eliminate the associated risk to mission performance. Further, the FFG 62 Program reports that they currently have sufficient access to technical information on the Thales CAPTAS-4 [variable-depth sonar] needed to effectively integrate it with the AN/SQQ-89(V)16 [undersea warfare] system.
SUITABILITY
No data are available to determine FFG 62 operational suitability due to FFG 62 being in development. Further, reliability, maintainability, and availability data for hull, mechanical, and electrical systems are not yet available to identify associated risk in the FFG 62 design.
SURVIVABILITY
No data are available to determine the cyber survivability of FFG 62 due to its early stage of development. Cyber survivability was not assessed during the EOA.
Insufficient data are available to determine FFG 62 survivability due to ongoing LFT&E. The Navy continued to close outstanding vulnerability knowledge gaps and support validation of survivability M&S through additional large-scale underwater explosion testing in FY23.
RECOMMENDATIONS
The Navy should:
1. Provide an update to the FFG 62 TEMP that includes the strategy to test anti-air warfare mission capability.
2. Continue to monitor the development of the mission system autonomy/automation components in the ship design to minimize risk to mission performance and system maintenance capability, and if necessary, complete a reassessment of the adequacy of crew sizing to allow opportunity to incorporate modifications of the ship design, should additional crewing be required to support all intended missions.49
An April 13, 2022, press report stated
The Navy will begin construction on the first Constellation-class frigate this summer or fall, later than the program's goal to begin construction in April.
The program won't start construction until the critical design review is completed, according to Capt. Kevin Smith, the frigate program manager.
"You may say, 'you've been working on design for a while.' We want to make sure we get it right before we start cutting steel. Lead ships are hard," Smith said last week at the Navy League's Sea-Air-Space conference.50
A March 31, 2022, press report stated
Following an announcement earlier this week that the Navy would cancel a key anti-submarine warfare effort bound for the Littoral Combat Ship, the service today also said it would replace that technology with an alternative system onboard the new Constellation-class frigate.
Rear Adm. Casey Moton, a senior officer overseeing both ship classes, told a small group of reporters that "following an assessment," the Navy chose the CAPTAS-4 variable depth sonar (VDS) made by Advanced Acoustics Concepts, a subsidiary of DRS and Thales, as the new frigate VDS.
"The Navy assessed CAPTAS-4 as a low risk VDS option for FFG-62 due to its proven performance, overall technical readiness level, low risk integration with the SQQ-89 ASW combat system, ability to integrate with the frigate platform design and ability to meet the in-yard need date for FFG-62," Moton said....
The consequences for the last-minute change to the Navy's contract with Raytheon are still being worked out, Moton said, but he added that the company had been "professional" throughout the process to date. The admiral also said he does not anticipate "very much of a change" to the ship's cost as a result of the new VDS.51
A January 2022 press report about whether changes made to FREMM parent design introduce technical risk to the FFG-62 program stated
Experts told Breaking Defense that not all changes [from a parent design] are as inherently risky as they might seem, and the Navy appears to have heeded lessons from previous controversies....
"In terms of changes from a parent design… as you start to drive further away from a parent design, there is the risk of cost increase, especially if you have immature equipment that requires testing or fails testing," said Steven Wills, a Navy strategy and policy expert at CNA, a federally funded research and development center that provides advice to the Pentagon....
When asked this month at the Surface Navy Association's annual symposium about how those changes could impact the program's risk calculus, Capt. Kevin Smith, the Constellation-class program manager, said the parent design is a starting point, but nothing more.
"I think it was clear to everyone in Navy leadership as well as congressional leadership that the parent is there as just that… think of it as a DNA," he said. "But you do have to take US Navy standards and apply those, and also the requirements."...
"The only thing that we've [the Navy] done actually—it's a change to the requirements—is buy American, because that was a statute from Congress," Smith said, referring to legislation mandating certain parts and percentages of US warships be manufactured domestically....
But CNA's Wills said one major difference between the FREMM and the Constellation, the elongated hull form, is not surprising because of differences in how Europeans and the United States go about building warships.
"You don't incur a lot of costs in making the ship bigger. That shouldn't slow you down. That shouldn't cause testing to fail," he said. "You're going to have to buy more steel and there will be some changes. The benefit that they seem to be going for… is they're looking for some additional margins throughout the life of the ship."
Matthew Collette, who teaches naval architecture and marine engineering at the University of Michigan, said fully adopting a parent design without modification is "exceptionally rare" especially for the US Navy, which has developed standards for internal layouts and adheres to congressional policy dictating supply chain options.
"Changing the overall dimensions of the ship is probably lowering the overall risk to the program, not raising it," Collette told Breaking Defense. "Given that we are changing the internals of the design, adhering strictly to the old hull form would actually increase the overall risk to the program, as you end up adding complexity by trying to shoehorn in components in a less-than-ideal layout."
He cited the Ticonderoga-class cruisers and Whidbey Island-class dock landing ships as examples where Navy programs have historically suffered because the service attempted to maintain the ships' external design while altering its internal layout.
Collette said there are three principles a shipbuilding program should follow to reduce the risk of modifying a parent design. The first is choosing proven systems when swapping out components. In the Constellation's case, the Navy has done just that by choosing systems such as Aegis, the Mk 41 Vertical Launching System and the SLQ-32 from the Surface Electronic Warfare Improvement Program.
The second principle is to thoroughly test new components ashore, a requirement Congress codified in law after finding out the Navy failed to do this on other systems that proved troublesome for the Ford.
The last principle is having a completed definition of the parent design, such as a 3D model, a parameter for which Collette and other analysts have no way of assessing from outside the Navy's program office.
"Even with some changes, the program is still benefiting from access to the original design models, and the knowledge gained in building and operating vessels that are highly similar, but no longer exactly the same, to the US Navy variant," Collette said.52
See also the Appendix regarding the Navy's use of a guaranty rather than a warranty in the Detail Design and Construction (DD&C) contract for the first 10 ships in the FFG-62 program.
Table 2 summarizes congressional action on the Navy's FY2025 funding request for the FFG-62 program.
Table 2. Congressional Action on FY2025 Procurement Funding Request
Millions of dollars, rounded to nearest tenth.
|
Authorization |
Appropriation |
||||||
|
Request |
HASC |
SASC |
Enacted |
HAC |
SAC |
Enacted |
|
|
Procurement |
1,170.4 |
0 |
1,220.4 |
50.0 |
0 |
1,270.4 |
233.2 |
|
Advance procurement (AP) |
0 |
37.5 |
0 |
0 |
0 |
0 |
0 |
|
(Procurement quantity) |
(1) |
(0) |
(1) |
(0) |
(0) |
(1) |
(0) |
|
Cost-to-complete funding |
0 |
0 |
0 |
0 |
0 |
700.0 |
400.0 |
Sources: Table prepared by CRS based on FY2025 Navy budget submission, committee and conference reports, and explanatory statements on the FY2025 National Defense Authorization Act and the FY2025 DOD Appropriations Act.
Notes: HASC is House Armed Services Committee; SASC is Senate Armed Services Committee; HAC is House Appropriations Committee; SAC is Senate Appropriations Committee. Cost-to-complete funding, also referred to as completion of prior-year (PY) shipbuilding programs, is funding to cover cost growth on ships procured in prior fiscal years.
The House Armed Services Committee, in its report (H.Rept. 118-529 of May 31, 2024) on H.R. 8070, recommended the funding levels shown in the HASC column of Table 2. The recommended reduction of $1,170.4 million in procurement funding (the entire requested amount) is for "Program delay." The recommended increase of $37.5 million in advance procurement (AP) funding is for "Frigate industrial base and workforce development." (Page 426)
H.Rept. 118-529 states
United States Navy constellation class frigates program
The committee recognizes the importance of frigates to fill a gap in the U.S. Navy's fleet and be capable of conducting anti-air warfare, anti-surface warfare, anti-submarine warfare, and electromagnetic warfare operations in both blue water and littoral areas. The committee recognizes the importance of national security in the proposed selected homeports, Naval Station Everett and Naval Station Mayport. The committee is concerned with the reported 3-year delay in the delivery of the lead ship due to design instability and workforce shortage but remains supportive of the mission and the capability it will bring once delivered to the fleet. (Page 26)
The Senate Armed Services Committee, in its report (S.Rept. 118-188 of July 8, 2024) on S. 4638, recommended the funding levels shown in the SASC column of Table 2. The recommended increase of $50.0 million is for "Small surface combatant shipyard infrastructure and workforce development." (Page 444)
Section 122 of S. 4638 states
SEC. 122. CONSTELLATION-CLASS FRIGATE PROGRAM.
(a) CERTIFICATION REQUIRED.—Upon final approval of 95 percent of all functional design drawings for the Constellation-class frigate program by the designated technical authority, the Secretary of Defense shall certify to the congressional defense committees that such drawings have been so approved.
(b) LIMITATION.—None of the amounts authorized to be appropriated by this Act for fiscal year 2025 may be obligated or expended for a scope of work for the construction of a Constellation-class frigate until after submission of the certification required by subsection (a).
(c) ASSESSMENT AND EVALUATION.—Not later than 30 days after the date on which the Secretary of Defense submits the certification required by subsection (a), the Comptroller General of the United States shall—
(1) assess the Secretary's compliance with this section; and
(2) submit to the congressional defense committees an evaluation of the completeness of the functional design drawings described in such subsection.
Regarding Section 122, S.Rept. 118-188 states
Constellation-class frigate program (sec. 122)
The committee recommends a provision that would prohibit the Secretary of the Navy from obligating or expending any funds authorized for fiscal year 2025 for the construction of a Constellation-class frigate until the Secretary of Defense certifies that 95 percent of functional design drawings have been approved by the designated technical authority. The provision would also require the Comptroller General of the United States to assess the Secretary of Defense's compliance with the requirements and evaluate the completeness of functional design.
The committee notes that six ships have been appropriated for the program, and the keel of the lead ship was laid in the third quarter of fiscal year 2024. In April 2024, the U.S. Navy reported the lead ship to be 3 years behind schedule, a delay with ramifications that are not fully factored into the U.S. Navy's budget justification documents. The second ship is already facing a 2-year construction delay.
The committee recognizes that the shipbuilder is facing labor and supply chain challenges that reflect issues facing the broader industry, particularly given that the shipbuilder's price was formulated prior to the COVID–19 pandemic. Moreover, the shipbuilder has a significant backlog of work in another shipbuilding program whose prime contractor is a separate company, which complicates the prioritization of resources at the shipbuilder for the Constellation-class frigate.
The committee also notes the U.S. Navy's role in the challenges facing the program. In section 123 of the National Defense Authorization Act for Fiscal Year 2017 (P.L. 118-114–328), Congress limited the award of a contract for construction of the prospective frigate class ship until the design reached sufficient maturity and completed a preliminary design review, or demonstrated an equivalent level of design completeness. The U.S. Navy cited the frigate program's use of a parent ship design as an argument for why this requirement had been met. More generally, the U.S. Navy cited the use of a parent design as an important measure for reducing technical, schedule, and cost risk in the program. The winning offeror proposed a design based on the Italian-French Fregata Europea Multi-Missione (FREMM) frigate design, but the content of design of the Constellation-class reportedly has declined over time from being 85 percent common with the FREMM design to being 15 percent common, suggesting that the program has evolved toward what the Congressional Research Service refers to as a "parent design in name only" situation, which can negate much of the potential value of using a parent design.
The scale and scope of these changes call into question the basis of the U.S. Navy's original program justification to Congress and the fixed-price contract awarded to the shipbuilder. If the proposed design was insufficient to meet U.S. Navy standards to the degree suggested by the reported 15 percent commonality figure, then the contract award suggests that there was a severe breakdown between the assumptions of the source selection evaluation board and the senior technical authority. The senior technical authority must ensure clarity of technical standards in the solicitation process, timely feedback for contractor-submitted drawings, and currency and relevancy of technical standards.
Moreover, the senior technical authority is expected to maintain discipline related to design maturity in advance of construction. The Secretary of the Navy certified to Congress that basic and functional design were complete prior to the start of construction in August 2022, but U.S. Navy officials now estimate that such maturity will not be reached until more than 2 years later. The committee believes this constitutes a misrepresentation of the facts certified by the Secretary of the Navy.
The committee affirms its support for the goal of a 381-ship Navy and the role of the Constellation-class frigate in meeting U.S. Navy requirements. The committee appreciates the urgency that the U.S. Navy has demonstrated to surge design support to the Constellation-class builder and looks forward to receiving updated production plans for the program. Moreover, the committee encourages the Secretary of the Navy to consider whether exercising additional fixed priced options on the contract including detail design and construction is in the best interest of the U.S. Navy and the health of the industrial base. (Pages 6-7)
The joint explanatory statement for the House-Senate agreement on H.R. 5009/P.L. 118-159 of December 23, 2024, recommends the funding levels shown in the authorization final column of Table 2. The recommended net reduction of $1,120.442 million in procurement funding includes a reduction of $1,170.442 million (the entire requested amount for the ship that was requested for procurement in FY2025) for "Program delay," and an increase of $50.0 million for "Small surface combatant shipyard infrastructure and workforce development." (Pages 520-521)
Section 129 of H.R. 5009 would prohibit the obligation an expenditure of funds authorized to be appropriated by H.R. 5009 or otherwise made available for FY2025 for the Navy for the construction of a Constellation-class frigate beyond the basic and functional design phase until DOD certifies that 95% of the all basic and functional design drawings for the Constellation-class frigate program have received final approval. Section 129 would also direct GAO to submit an assessment of DOD's compliance with Section 129 and the completeness of the basic and functional design drawings.
Section 1033 requires the Navy to "take such actions as are necessary for the Navy to adopt recommendations 1, 3, 4, and 6 in the report of the Government Accountability Office titled, 'Navy Shipbuilding: Increased Use of Leading Design Practices Could Improve Timeliness of Deliveries', and dated May 2, 2024 (GAO-24-105503)." Regarding Section 1033, the joint explanatory statement states in part:
In addition, we direct the Assistant Secretary of the Navy for Research, Development, and Acquisition, in coordination with the Commander, Naval Sea Systems Command (NAVSEA), to provide a report, not later than one year after the date of the enactment of this Act, to the Committees on Armed Services of the Senate and the House of Representatives that details the following:
(1) All references to external specifications regardless of source—including military specifications, NAVSEA instructions, American Bureau of Shipbuilding and other standards—that were included on the Constellation-class frigate solicitation for detail design and construction;
(2) Which specifications in paragraph (1) allowed for alternative specifications—including alternative specifications conditional on NAVSEA approval;
(3) How many alternative specifications allowed in paragraph (2) were recommended by the awarded contractor in their proposed response to the solicitation for the Constellation-class frigate detail design and construction contract in comparison to how many alternative specifications were ultimately approved by NAVSEA;
(4) An explanation for why such alternative specifications in paragraph (3) were not approved by NAVSEA;
(5) The status of all requests for equitable adjustments [REAs] that the Navy received on the Constellation-class frigate;
(6) An unaltered statement from the awarded contractor of the Constellation-class frigate of the findings provided in paragraphs (1) though (5) above; and
(7) Proposed actions for how best value tradeoffs will be improved in source selections for shipbuilding contracts. (PDF pages 249-250 of 696)
The House Appropriations Committee, in its report (H.Rept. 118-557 of June 17, 2024) on H.R. 8774, recommended the funding levels shown in the HAC column of Table 2. The recommended reduction of $1,170.4 million in procurement funding (the entire requested amount) is for "Program delay." (Page 129)
Section 8093(b) of H.R. 8774, a recurring provision, states
SEC. 8093….
(b) None of the funds provided in this Act for the FFG(X) Frigate program shall be used to award a new contract that provides for the acquisition of the following components unless those components are manufactured in the United States: Air circuit breakers; gyrocompasses; electronic navigation chart systems; steering controls; pumps; propulsion and machinery control systems; totally enclosed lifeboats; auxiliary equipment pumps; shipboard cranes; auxiliary chill water systems; and propulsion propellers: Provided, That the Secretary of the Navy shall incorporate United States manufactured propulsion engines and propulsion reduction gears into the FFG(X) Frigate program beginning not later than with the eleventh ship of the program.
H.Rept. 118-557 states
FRIGATE CONSTRUCTION
The Committee notes that despite findings in the 45-day Shipbuilding Review that show the Constellation-class frigate is at least three years behind schedule, the Navy continues to request funding to construct frigates at a rate that the program has demonstrated it is unable to meet. In addition to the delays found with lead-ship construction, the Committee notes the delivery dates for the three follow-on frigates currently under contract are unknown. The Committee is concerned by persisting design instability for the lead ship that may further impact construction. Therefore, the Committee recommendation provides no funding for the procurement of a frigate in fiscal year 2025. (Page 132)
The Senate Appropriations Committee, in its report (S.Rept. 118-204 of August 1, 2024) on S. 4921, recommended the funding levels shown in the SAC column of Table 2. The recommended increase of $100.0 million in procurement funding is for "Program increase: Frigate industrial base and workforce development." (Page 132) The recommended increase of $700.0 million in cost-to-complete funding is for "Program increase: Frigate 62–67," meaning the fist six ships in the program, which were procured in prior fiscal years. (Page 132) Cost-to-complete funding, also referred to as completion of prior-year (PY) shipbuilding programs, is funding to cover cost growth on ships procured in prior fiscal years.
Section 8093(b) of H.R. 8774, a recurring provision, states
SEC. 8093….
(b) None of the funds provided in this Act for the FFG(X) Frigate program shall be used to award a new contract that provides for the acquisition of the following components unless those components are manufactured in the United States: Air circuit breakers; gyrocompasses; electronic navigation chart systems; steering controls; pumps; propulsion and machinery control systems; totally enclosed lifeboats; auxiliary equipment pumps; shipboard cranes; auxiliary chill water systems; and propulsion propellers: Provided, That the Secretary of the Navy shall incorporate United States manufactured propulsion engines and propulsion reduction gears into the FFG(X) Frigate program beginning not later than with the eleventh ship of the program.
Sections 1404 and 1417 of the Full-Year Continuing Appropriations and Extensions Act, 2025 (H.R. 1968/P.L. 119-4 of March 15, 2025), a full-year continuing resolution (CR), provide the funding figures shown in the appropriation enacted column of Table 2.
As discussed earlier, in June 2025, Secretary of Defense Pete Hegseth indicated that the FFG-62 program was being reviewed as one of several "difficult decisions" to be made by the Department of Defense (DOD) during a review of its acquisition programs. As also discussed earlier, in a series of announcements from November 25 to December 19, 2025, the Navy stated that it wants to restructure its frigate acquisition effort by (1) truncating the FFG-62 program to no more than two ships and (2) initiating a new program to procure a different class Navy frigates, called FF(X)s, whose design would be based on that of the National Security Cutter (NSC), a frigate-like ship that has been built for the Coast Guard by Huntington Ingalls Industries/Ingalls Shipbuilding (HII/Ingalls) of Pascagoula, MS.
Under the Navy's desired new approach, the third through sixth FFG-62s (which have not begun construction) would be cancelled; the first two FFG-62s (construction of which is underway) would remain under review; the first FF(X) would be awarded to HII/Ingalls on a sole-source basis and be launched (i.e., put into the water for the final stages of its construction) by 2028; and one or more additional U.S. shipyards would later be brought into the FF(X) program to expand the FF(X) production rate, competing with HII/Ingalls for future ships in the program.
In announcing its desired new approach for acquiring frigates, Secretary of the Navy John Phelan stated that "the Constellation-class frigate was canceled because, candidly, it didn't make sense anymore to build it. It was 80% of the cost of a [larger DDG-51 class] destroyer and 60% of the capability. You might as well build destroyers." The continuation, for now at least, of construction work on the first two FFG-62s reportedly is intended to support F/MM in the near term, while policymakers assess how F/MM's shipbuilding capability could be used over the longer run. As of November 25, 2025, the first ship in the FFG-62 program was reportedly about 12% complete.
Navy News Release of December 19, 2025A December 19, 2025, Navy news release about its desire to initiate procurement of FF(X)s states:
The Navy announced today its plan to introduce a new class of smaller combatant ships, the FF(X), as a critical component of the Navy's fleet of the future. The FF(X) will be a smaller, more agile surface combatant designed to complement the fleet's larger, multi-mission warships and enhance operational flexibility around the globe.
"To deliver at speed and scale, I've directed the acquisition of a new frigate class based on HII's Legend-Class National Security Cutter design: a proven, American-built ship that has been protecting U.S. interests at home and abroad," said John C. Phelan, Secretary of the Navy. "President Trump and the Secretary of War have signed off on this as part of the Golden Fleet. Our goal is clear: launch the first hull in the water in 2028. To expand capacity and production across our maritime industrial base, we will acquire these ships using a lead yard, and competitive follow-on strategy for multi-yard construction. Shipyards will be measured against one outcome: delivering combat power to the Fleet as fast as possible."
The FF(X) is a highly adaptable vessel. While its primary mission will be surface warfare, its ability to carry modular payloads and command unmanned systems enables it to execute a broad spectrum of operations, making it ready for the challenges of the modern maritime environment.…
"Like the Medium Landing Ship [LSM], leveraging a complete design and production baseline approach will allow the Navy and shipbuilders to reduce costs, schedule and technical risk," said Adm. Daryl Caudle, 34th Chief of Naval Operations. "We know this Frigate design works, we know it operates with the Fleet, and most importantly, we know how to build it now."33A December 19, 2025, press report quoted a "senior official" as stating: "We will initially sole-source the lead ship to Ingalls, but we will move to competition as soon as possible."34
National Security Cutter (NSC) DesignThe NSC program is discussed in detail in a separate CRS report on Coast Guard cutter acquisition programs.35 HII/Ingalls has built 10 NSCs for the Coast Guard; the first was commissioned into service with the Coast Guard in August 2008, and the 10th was commissioned into service with the Coast Guard in April 2024. Congress funded an 11th NSC in FY2018, but in June 2025 it was reported that the Coast Guard and HII/Ingalls had agreed to cancel construction of the ship,36 making the 10th NSC the final one to be built for the Coast Guard.
The NSC design (Figure 4) is substantially smaller than the FFG-62 design. As noted earlier, the full load displacement of the FFG-62 design is close to 8,000 tons. By comparison, the NSC design has a full load displacement of about 4,500 tons.37 Consistent with both its smaller size and Coast Guard (rather than Navy) mission needs, the NSC is less heavily armed than the FFG-62 design. Naval Variants of NSC Design Proposed in Past Years by HII/IngallsHII/Ingalls since at least 2012 has marketed naval variants of the NSC design, which HII/Ingalls has called patrol frigates, for potential export to other countries.38 Some observers have argued that ships based on the NSC design should be procured for the U.S. Navy.39
Figure 4. National Security Cutter
Source: Cropped version of photograph accompanying Huntington Ingalls Industries, "Bertholf (WMSL 750) Builder's Trials," March 22, 2019. The caption to the photograph states that it was taken on December 4, 2007.
Figure 5. Rendering of FF(X) Design
Source: Cropped version of rendering accompanying Sam LaGrone, "SECNAV: New Frigate will be Based on National Security Cutter, First FF(X) to be Built at Ingalls," USNI News, December 19, 2025. The caption to the rendering credits it to the U.S. Navy.
A December 19, 2025, press article quotes a "senior official" as stating: "The [NSC] design [with] little adaptation will meet the CNO's [Chief of Naval Operations'] requirements for a small surface combatant."43 The article also states:
The scaled-back requirements for the new ship class were born from a Navy-led review of what the sea service needs in the short term to support lower-priority missions that tie up more capable warships….
"They looked at what's been going on in U.S. 5th Fleet and 4th Fleet as exemplar areas where this platform would help take the load off of our destroyers so they could focus on some of the higher-end missions," a second senior official told USNI News.
One of the few changes the Navy intends to make to the NSC design is to construct a platform above the open boat deck for containerized mission packages, the officials said. For example, the Army and Lockheed Martin developed the MK-70 Typhon vertical launch system within the dimensions of a 40-foot shipping container. The Navy is developing more containerized packages that can be swapped from ship to ship.
"That'll be something immediately on the first flight of ships that will be available," the first senior official told USNI News. "Those containers could do a host of missions. That's a core element of the future force design. Beyond that … things that are more intrusive to install, like anti-submarine warfare equipment, would be something we would look to do in the future."44
Another December 19, 2025, press article states that the Navy has
made clear that it expects the new frigate design to allow for the integration of new and improved capabilities and functionality down the line.
"The [FF(X)] frigate will follow the same proven approach we've used with the Arleigh Burke destroyers, building it smart from the start, then upgrading it in steps over time, as the threat and technology evolve," Chief of Naval Operations Adm. Daryl Caudle also said in today's video announcement.45
Issues for Congress Regarding Navy's Desired Approach for Frigate AcquisitionIn considering whether to approve, reject, or modify the Navy's desired approach for restructuring its frigate acquisition effort, Congress may consider several potential oversight issues, including but not necessarily limited to those discussed below.
Adequacy of Information Provided to CongressOne potential oversight issue for Congress is whether is whether Congress has adequate information to assess the merits of the Navy's desired new approach to frigate acquisition. Information that could support congressional assessments includes information on
Another potential oversight issue for Congress is what general approach to pursue regarding frigate acquisition.
Overview of Four General ApproachesIn a context of the existing FFG-62 program and a potential successor frigate program, notional general approaches regarding frigate acquisition include but are not necessarily limited to the following four possibilities:
Below are brief discussions of each of these possible approaches.
Under this approach, which might be thought of as the "no frigates" approach, procurement of FFG-62s would be truncated, and no successor frigate program would be initiated. Navy mission needs that were to have been met by procuring frigates would instead be met by increasing planned procurement and force levels of DDG-51 destroyers (i.e., ships larger than frigates) and/or corvette-sized unmanned surface vessels (USVs) (i.e., ships smaller than frigates).46
Supporters of this approach could argue that ending procurement of frigates would ease Navy shipbuilding program management workloads by reducing the number of shipbuilding programs to be managed, and do so at a time when the Navy is facing challenges in executing its shipbuilding programs. They could argue that this approach could increase production and life-cycle O&S economies of scale for DDG-51 destroyers and USVs.
Skeptics of this approach could question whether a combination of DDG-51s and USVs could meet certain mission needs that were to have been met by procuring frigates, because the capabilities of the Navy's future USVs have not been fully defined and proven, and because USVs, as unmanned ships, could be challenged in performing certain day-to-day, noncombat missions that manned frigates would perform.47 They could argue that using destroyers to perform missions that could be adequately performed by frigates would not be cost effective, given the higher procurement and O&S costs of destroyers compared to frigates.
This is the Navy's desired approach. Supporters of this approach could argue, as Secretary of the Navy Phelan has, that the FFG-62 design is no longer cost-effective to pursue as a smaller and individually less expensive complement to the DDG-51 design, because the FFG-62 design has grown during the design process to more than 80% of the size of the DDG-51 design but would provide less than 80% of a DDG-51's capability, and that a successor frigate design could fare better than the FFG-62 design in terms of cost and capability in relation to the cost and capability of the DDG-51 design. They could argue that although limiting FFG-62 procurement to two ships could increase per-ship FFG-62 O&S costs by reducing economies of scale for such costs, the increase will not be onerous. They could argue that the Navy operates other numerically small ship classes (including the three-ship Seawolf [SSN-21] class of attack submarines and the three-ship Zumwalt [DDG-1000] class of destroyers), and that the issue of per-ship FFG-62 O&S costs could be addressed by eventually selling the two FFG-62s to one or two allied or partner navies that might need only one or two such ships to meet their own mission needs.
Skeptics of this approach could argue that the FFG-62 design is the design that the Navy originally selected, following a rigorous source-selection process, as the one that could best meet the Navy's operational requirements for a frigate, and that a successor frigate design might fare no better than the FFG-62 design in terms of cost and capability in relation to the cost and capability of the DDG-51 design. They could argue that while there is less than a 20% difference in the size of a 9,700-ton DDG-51 and an 8,000-ton FFG-62, Navy plans have called for shifting destroyer procurement in the early 2030s from the DDG-51 design to a 14,500-ton next-generation destroyer design called the DDG(X),48 which would establish a larger difference in size between the FFG-62 design and the design of the destroyer that the Navy would be procuring. They could argue that design work on the FFG-62 is progressing toward completion; that truncating FFG-62 procurement to two ships would provide a limited return on the investment of time and funding that the Navy has expended to complete the FFG-62 design (which needs to be completed to support the construction of the first two ships); that it would not be optimal for the Navy to create another case, alongside cases such as the Seawolf and Zumwalt classes, of paying elevated per-ship O&S costs for a numerically limited class of combatant ships; and that there is no guarantee that the Navy would be able to find one or two allied or partner navies willing to buy two FFG-62s unless their purchase price is set substantially below their original procurement costs.
Under this approach, which might be thought of as the "stay the course with the FFG-62 program" approach, the cancellation of the third through sixth FFG-62 would be treated as a pause in FFG-62 procurement that would be intended to permit FFG-62 construction work to catch up with the number of FFG-62s that have been procured, at which point procurement of additional FFG-62s would resume, and a successor frigate program would not be initiated. A pause in FFG-62 procurement could be viewed as similar in some respects to what occurred in the earlier years of the Littoral Combat Ship (LCS) procurement program.49
Since this approach is essentially the obverse of the previous approach, notional arguments for supporters and skeptics of this approach would essentially be the obverse of those outlined above for the previous approach: Supporters of this approach could make arguments similar to those outlined above for skeptics of the previous approach, while skeptics of this approach could make arguments similar to those outlined above for supporters of the previous approach.
Under this approach, which might be thought of as the "procure two frigate classes" approach, the cancellation of the third through sixth FFG-62 would be treated as a pause in FFG-62 procurement, followed by a resumption in FFG-62 procurement at a later point, and an additional frigate program would be initiated, with ships in this additional program being procured in parallel with procurement of FFG-62s. Under this approach, the builder or builders of FFG-62s and the builder or builders of the second type of frigate could compete for contracts to build frigates for the Navy. This approach would be broadly similar to the one the Navy employed for the LCS program, under which two different LCS designs were built at two shipyards, with each shipyard building one of the designs, and the Navy had the option of using competition between the two shipyards in determining who would build the later ships in the program.
Supporters of this approach could argue that that the FFG-62 design is the design that the Navy originally selected, following a rigorous source-selection process, as the one that could best meet the Navy's operational requirements for a frigate,50 but that a second frigate design might be smaller and individually less expensive to procure and operate than the FFG-62 design, permitting it to serve, within the Navy's frigate force, as a less-expensive complement to the Navy's FFG-62s.
Skeptics of this approach could argue that it would increase Navy shipbuilding program management workloads by increasing the number of shipbuilding programs to be managed, and do so at a time when the Navy is facing challenges in executing its shipbuilding programs. They could also argue that building two types of frigates would reduce frigate production and life-cycle O&S economies of scale by dividing frigate acquisition into two programs, and that the reduced economies of scale could, other things held equal, increase per-ship production and life-cycle O&S costs for Navy frigates.
Potential Oversight Questions for CongressPotential oversight questions for Congress regarding what general approach to pursue regarding frigate acquisition include the following:
If the second or fourth general approach outlined in the previous section is pursued, and a new frigate design is consequently to be procured, a follow-on potential oversight issue for Congress would be whether the Navy's desired design—an FF(X) based on the NSC design—is the most cost-effective new design to procure.
Potential Design OptionsPotential options for a new frigate design include but are not necessarily limited to the following:
the Multi-Mission Surface Combatant (MMSC), a variant of the LCS-1 class design with a displacement of more than 3,900 tons,51 four of which F/MM is building for the Royal Saudi Navy (Figure 6);52Figure 6. Multi-Mission Surface Combatant (MMSC)
Source: Cropped version of photograph accompanying "The First MMSC-1 Frigate Built by Fincantieri in the United States for the Royal Saudi Navy Was Launched," Zona Militar, December 29, 2025. A watermark on the photograph with both Arabic and English writing states, in its English portion, "Ministry of Defense."
Figure 7. Mogami-Class Frigate
Source: Cropped version of photograph accompanying Eric Wertheim, "Japan's Multimission Mogami-class Frigates," U.S. Naval Institute Proceedings, September 2023. The caption to the photograph credits the photograph to Arjun Sarup.
General observations that might be made about the above-listed options for a new frigate design include but are not necessarily limited to the following:
Figure 8. Daegu-Class Frigate
Source: Photograph accompanying "Daegu class (FFG-II) Guided Missile Frigate," Seaforces, undated, accessed January 1, 2026. The caption to the photograph credits the photograph to "Republic of Korea Armed Forces/ CC."
Potential oversight questions for Congress regarding options for a new frigate design include the following:
Figure 9. Álvaro de Bazán-class F100 Frigate
Source: Photograph accompanying Defence24, "Navantia Showcasing Its Miecznik Proposal in Warsaw. Aegis offered for Poland," Defence24.com, December 15, 2021. The caption to the photograph credits the photograph to "NATO Maritime Group 2 via US Navy."
A December 22, 2025, blog entry states the following regarding the comparative capabilities of the FFG-62 design and the proposed NSC-based FF(X) design:
The U.S. Navy has confirmed to TWZ [The War Zone] that the armament package for its first "flight" of its new FF(X) frigates will not include a built-in Vertical Launch System (VLS).…
A lack of any type of VLS on the FF(X) design is a glaring omission that can only raise questions about the operational utility and flexibility of the ships. At the same time, the new frigates will be able to carry modular payloads, including containerized missile launchers, on their sterns. The Navy also has an explicit plan to employ the FF(X)s as "motherships" for uncrewed surface vessels (USV), likely offering a distributed arsenal, as well as additional sensors, for the frigates to leverage during operations….
"The initial flight of FF(X) will have a 57mm gun, 2 x 30mm guns, a Mk 49 Rolling Airframe Missile [launcher], various countermeasures, and a flight deck from which to launch helicopters and unmanned systems. Aft of the flight deck, there will be a flexible weapons system, which can accommodate containerized payloads (Counter-UAS [counter-unmanned aerial systems], other missiles)," a Navy spokesperson told TWZ today. "Much like the successful DDG-51 [Arleigh Burke class destroyer] program, we are building this in flights. The frigate will be upgraded over successive flights to evolve and has the space reservations needed to improve capability over time."…
Overall, the Mk 41 VLS requirement was central to the FFG(X) program that led to the Constellation class design. This was viewed as a key element of righting the wrongs of the Navy's chronically underperforming Littoral Combat Ship (LCS) program. The Independence class and Freedom class LCSs both lack a VLS array. In addition, it's worth remembering here that HII's losing FFG(X) bid was notably a Patrol Frigate concept derived from the National Security Cutter that featured a VLS….
Integrating a VLS into future flights of FF(X) frigates is certainly an option, but one that could be complex and costly if the design is not configured to accommodate one to begin with….
Installing missile launchers on the FF(X)'s fantail would give the ships a boost in firepower in the absence of an integrated VLS array. Renderings so far have shown what look to be launchers for up to 16 Naval Strike Missiles (NSM) installed in that position.… There also looks to be space there for a least one containerized Mk 70 Payload Delivery Systems (PDS), another capability the Navy is already acquiring. Each Mk 70 contains a four-cell launcher derived from the Mk 41 VLS, and similarly capable of firing a variety of weapons, including SM-6 multi-purpose missiles and Tomahawk land-attack cruise missiles….
"The FF(X) will be designed to command groups of unmanned vessels, acting as a sort of 'mothership,' providing the commander tailored force packages based upon the weapons and sensors fielded on those unmanned craft," a Navy spokesperson also told TWZ today.
In this way, an FF(X) could still call upon a deeper and more flexible array of weapon options without having to have a VLS integrated directly onto the ship. The uncrewed platforms would also be able to operate across a much broader area than any single crewed frigate and present a different risk calculus for operating in higher-risk environments. All of this would expand the overall reach of the combined force and present targeting challenges for opponents. But there are also substantial development and operational risks with this kind of arrangement. As it sits, this kind of autonomous vessel and manned vessel teaming is still in development. Operationally, leaving the ship without, or with very limited, area defense capability is at odds with many future threat scenarios….
Even with all this in mind, the lack of a VLS still raises significant questions about the FF(X) plans, especially about the ability of the ships to operate more independently. This has been a key issue for the Navy's existing LCS fleets, and one that the Constellation class was supposed to help address….
… While expanded [FF(X)] variants in the future [that are equipped] with VLS arrays and more exquisite combat systems seem like a real possibility, when it comes to installed armament, America's next frigate is set to be just as lightly armed as the LCS that came before it.64
Sole-Source or Competitive Contract Award for First ShipAnother potential oversight issue for Congress is whether a contract to build the first ship of a new frigate design should be awarded on a sole-source basis or competitive basis. As noted earlier, a December 19, 2025, press report quoted a "senior official" as stating: "We will initially sole-source the lead ship to Ingalls, but we will move to competition as soon as possible."65 A potential alternative to a sole-source award for the first ship would be for the government to purchase the data rights to the selected frigate design (if the government does not already own the data rights) and hold a competition among multiple shipbuilders to build the first ship to that design.
Supporters of a sole-source award could argue that it will help reduce the construction timeline for the first ship, and that it is uncertain that holding a competition would have a meaningful impact on reducing contract price. Supporters of a competitive award could argue that a sole-source award would deprive the Navy of an opportunity to use competitive leverage to minimize the contract price, and that having that leverage would be more important than the additional time needed to hold a competition. Potential questions for Congress include the following:
Another potential oversight issue for Congress is whether foreign shipyards should play a role in building frigates for the U.S. Navy. Such a role could involve building either entire frigates or frigate ship sections (sometimes called ship modules or ship blocks) that would be transported to a final-assembly shipyard in the United States. Building ships sections in one yard for transportation to a final assembly yard would be a form of what is referred to as distributed production or federated shipbuilding. The Navy currently uses distributed production/federated shipbuilding for its Virginia- and Columbia-class submarine construction programs.66
As discussed at length in another CRS report, U.S. Navy shipbuilding programs in some cases are being slowed or limited by U.S. shipbuilding industrial base capacity constraints.67 Concerns over this situation are heightened by the pace of China's naval shipbuilding effort.68 President Trump,69 some other U.S. officials,70 and other observers71 have suggested or advocated using foreign shipyards—particularly shipyards in South Korea and/or Japan—to build ships for the U.S. Navy, at least as a stop-gap measure until U.S. shipbuilding capacity constraints can be alleviated. Other observers oppose proposals for using foreign shipyards to build ships for the U.S. Navy.72
10 U.S.C. 8679 prohibits the construction of vessels for U.S. armed forces, or the major components of the hull or the superstructures of such vessels, in foreign shipyards. The statute includes a presidential waiver for the national security interest. The phrase major component of the hull can be viewed as including, among other things, ship sections. The full text of the statute as of January 2, 2026, is as follows:
§8679. Construction of vessels in foreign shipyards: prohibition
(a) Prohibition.-Except as provided in subsection (b), no vessel to be constructed for any of the armed forces, and no major component of the hull or superstructure of any such vessel, may be constructed in a foreign shipyard.
(b) Presidential Waiver for National Security Interest. (1) The President may authorize exceptions to the prohibition in subsection (a) when the President determines that it is in the national security interest of the United States to do so.
(2) The President shall transmit notice to Congress of any such determination, and no contract may be made pursuant to the exception authorized until the end of the 30-day period beginning on the date on which the notice of the determination is received by Congress.
(c) Exception for Inflatable Boats. An inflatable boat or a rigid inflatable boat, as defined by the Secretary of the Navy, is not a vessel for the purpose of the restriction in subsection (a).
In addition to 10 U.S.C. 8679, a recurring provision in the annual DOD Appropriations Act has prohibited funds appropriated each year for the Navy's shipbuilding account—the Shipbuilding and Conversion, Navy (SCN) appropriation account—from being used to build naval vessels or the major components of naval vessels in foreign shipyards or other foreign facilities. The provision has not included a presidential waiver. The phrase major components can be viewed as including, among other things, ship sections. The text of the provision, which appears in the paragraph of the DOD appropriations act that makes appropriations for the SCN account, has been as follows:
… Provided further, That none of the funds provided under this heading [i.e., the heading for the SCN account] for the construction or conversion of any naval vessel to be constructed in shipyards in the United States shall be expended in foreign facilities for the construction of major components of such vessel: Provided further, That none of the funds provided under this heading shall be used for the construction of any naval vessel in foreign shipyards:…
Supporters of having foreign shipyards contribute to the construction of frigates for the U.S. Navy could argue that the Navy's force of 32 small surface combatants (SSCs) at the start of FY2026 is less than half of the Navy's 73-ship force-level goal for such ships; that in light of China's naval shipbuilding effort, closing this shortfall is a matter of some urgency; and that given the time needed to alleviate constraints on U.S. shipbuilding capacity (particularly limits on numbers of available workers and the productivity of recently hired workers), there are few apparent options other than using foreign shipyards for quickly expanding the shipbuilding capacity engaged in building ships for the U.S. Navy. They could argue that involving foreign shipyards in the frigate-building effort could be a stop-gap measure to be employed until U.S. shipbuilding capacity is increased, and that for similar reasons, Finnish shipyards are being brought into the effort to build new icebreakers for the U.S. Coast Guard.73 They could argue that foreign shipyards in some cases have lower shipbuilding costs than U.S. shipyards, due in part to lower labor costs, and that involving foreign shipyards in the U.S. Navy's frigate-building effort could therefore reduce frigate procurement costs for the U.S. Navy.
Skeptics of having foreign shipyards contribute to the construction of frigates for the U.S. Navy could argue that the Navy can use destroyers and other forces to compensate for its current shortfall in SSCs; that the Navy and industry are taking numerous steps to alleviate constraints on U.S. shipbuilding capacity;74 that diverting some of the work involved in building frigates to foreign shipyards could weaken the U.S. shipbuilding industrial base by depriving the U.S. shipbuilding industry of work that would support efforts to alleviate those constraints; that involving foreign shipyards in the frigate-building effort, even if described as a stop-gap measure, could set a precedent for involving foreign shipyards in other U.S. Navy shipbuilding programs, which could further weaken the U.S. shipbuilding industrial base; and that involving foreign shipyards in the frigate-building effort could add to Navy shipbuilding program management workloads, and do so at a time when the Navy is facing challenges in executing its shipbuilding programs.
Unexpended FFG-62 Procurement FundsAnother potential oversight issue for Congress is whether unexpended funds for the FFG-62 program—particularly funds appropriated for procuring the third though sixth FFG-62s—should be rescinded or reprogrammed to other uses, and if the latter, then what those other uses should be. The Navy's FY2026 budget submission shows that a total of about $7.7 billion was appropriated for procurement of FFG-62s through FY2025, including about $5.0 billion for the third through sixth ships in the program. Potential oversight issues for Congress include the following:
Another potential oversight issue for Congress concerns how to support F/MM in the near term, while policymakers assess how F/MM's shipbuilding capability could be used over the longer run. Under the Navy's desired approach for frigate acquisition, construction of the first two FFG-62s, which was underway as of November 2025, would continue but remain under review. As discussed earlier, the continuation, for now at least, of construction work on the first two FFG-62s reportedly is intended to support F/MM in the near term, while policymakers assess how F/MM's shipbuilding capability could be used over the longer run. Other options for supporting F/MM in the near term—which could be pursued either in lieu of or in conjunction with continued construction work on the first two FFG-62s—include but are not necessarily limited to the following:
Continuing construction work on the first two FFG-62s would permit F/MM to fully use materials and components that have been procured for those two ships, and produce two frigates for the Navy, reducing the Navy's shortfall of small surface combatants (SSCs) relative to its stated force-level goal for SSCs. As discussed earlier in this report, a two-ship FFG-62 class could have elevated per-ship life cycle O&S costs due to the limited O&S economies of scale for a two-ship class. As also discussed earlier, the issue of elevated FFG-62 per-ship O&S costs could be addressed by eventually selling the two FFG-62s to one or two allied or partner navies that might need only one or two such ships to meet their own mission needs. Potential oversight questions for Congress include the following:
One potential oversight issue for Congress concerns the estimated delay in the delivery of the first ship in the program. Potential oversight questions for Congress include the following:
Another potential oversight issue for Congress concerns the potential for cost growth in the FFG-62 program, particularly after the first 10 ships in the program, which are to be procured under a fixed-price incentive (firm target) contract. As discussed in greater detail in earlier versions of this CRS report,79 CRS and CBO analyses done in 2020 suggested that if FFG-62s were to wind up costing about the same to construct per thousand tons of displacement as other recent U.S. military surface combatants, then FFG-62s could cost substantially more to build than their budgeted unit procurement costs:
The May 2024 GAO report on the FFG-62 program stated that in October 2023, the FFG-62 shipbuilder reported "unplanned weight growth in the frigate design—an increase of over 10 percent above the shipbuilder's June 2020 weight estimate."82 Since ship procurement costs are generally proportional to ship displacement (i.e., weight), this weight growth suggests a potential for cost growth beyond the above-discussed figures in the 2020 and 2023 CRS and CBO analyses.
Potential Consequences of Cost GrowthDepending on the exact terms of the fixed-price incentive (firm target) contract that the Navy awarded to F/MM for the first 10 ships in the FFG-62 program, some portion (perhaps much) of any cost growth that might occur on the first 10 FFG-62s could be borne by F/MM rather than the Navy, although F/MM under such a circumstance might also have the option of seeking some form of contractual relief from the Navy, which if granted could shift at least some of the cost growth back to the government.83 If F/MM were to bear most or all of any cost growth that might occur on the first 10 FFG-62s, then cost growth in the FFG-62 program, if it were to occur, might not affect Navy budgeting substantially until the 11th ship in the program. Under the Navy's FY2025 budget submission, the 11th ship in the program was scheduled to be the first of the two ships that are programmed for procurement in FY2028.
Potential Oversight QuestionsPotential oversight questions for Congress include the following:
Another potential oversight issue for Congress is whether and when to introduce a second shipyard into the FFG-62 program. The Navy's FFG-7s, which were procured at annual rates of as high as eight ships per year, were built at three shipyards. As noted earlier, the Navy's baseline plan for the FFG-62 program envisaged using a single builder at any one time to build FFG-62s, but Navy officials have also spoken about the option of bringing a second shipyard into the program at some point, particularly if annual procurement rates for FFG-62s rise above two ships per year.
In considering whether to build FFG-62s at a single shipyard or at two shipyards, Congress may consider several factors, including but not limited to the annual FFG-62 procurement rate, shipyard production capacities and production economies of scale, the potential costs and benefits in the FFG-62 program of employing recurring competition between multiple shipyards, and how the number of FFG-62 builders might fit into a larger situation involving the production of other Navy and Coast Guard ships, including Navy DDG-51 destroyers, Navy amphibious ships, and Coast Guard Offshore Patrol Cutters (OPCs).85
Number of VLS TubesAnother potential oversight issue for Congress—one discussed in this CRS report since April 201986—concerns the number of vertical launch system (VLS) missile tubes in the FFG-62 design. The VLS is the FFG-62's principal (though not only) means of storing and launching missiles. FFG-62s are to each be equipped with 32 Mark 41 VLS tubes. (The Mark 41 is the Navy's standard VLS design.)
Supporters of requiring each FFG-62 to be equipped with a larger number of VLS tubes, such as 48, might argue that FFG-62s are to be roughly three-quarters as large as the Navy's DDG-51 class destroyers, and might therefore be more appropriately equipped with at least 48 VLS tubes, which is one-half the number on recent DDG-51s. They might also argue that in a context of renewed great power competition with potential adversaries such as China, which is steadily improving its naval capabilities,87 it might be prudent to equip each FFG-62 with 48 rather than 32 VLS tubes each, and that doing so might only marginally increase FFG-62 unit procurement costs. They might also argue that equipping each FFG-62 with 48 rather than 32 VLS tubes will permit the Navy to more fully offset a substantial reduction in VLS tubes that the Navy's surface fleet is projected to experience when the Navy's 22 Ticonderoga (CG-47) class cruisers, which are each equipped with 122 VLS tubes, are retired,88 and provide a hedge against the possibility that Navy plans to field VLS tubes on Large Unmanned Surface Vehicles (LUSVs)89 will be slowed or curtailed for technical or other reasons.
Supporters of having each FFG-62 be equipped with 32 VLS tubes might argue that the analyses indicating a need for 32 VLS tubes already took improving adversary capabilities (as well as other U.S. Navy capabilities) into account. They might also argue that FFG-62s, in addition to having 32 VLS tubes, will also to have separate, deck-mounted box launchers for launching 16 anti-ship cruise missiles, as well as a separate, 21-cell Rolling Airframe Missile (RAM) AAW missile launcher; that Navy plans continue to call for eventually deploying additional VLS tubes on LUSVs, which are to act as adjunct weapon magazines for the Navy's manned surface combatants; and that increasing the number of VLS tubes on each FFG-62 from 32 to 48 would increase (even if only marginally) the procurement cost of a ship that is intended to be an affordable supplement to the Navy's cruisers and destroyers.
A May 14, 2019, Navy information paper on the cost impact of expanding the FFG-62 VLS capacity from 32 cells to 48 cells states
To grow from a 32 Cell VLS to a 48 Cell VLS necessitates an increase in the length of the ship with a small beam increase and roughly a 200-ton increase in full load displacement. This will require a resizing of the ship, readdressing stability and seakeeping analyses, and adapting ship services to accommodate the additional 16 VLS cells.
A change of this nature would unnecessarily delay detail design by causing significant disruption to ship designs. Particularly the smaller ship designs. Potential competitors have already completed their Conceptual Designs and are entering the Detail Design and Construction competition with ship designs set to accommodate 32 cells.
The cost is estimated to increase between $16M [million] and $24M [million] per ship. This includes ship impacts and additional VLS cells.90
Compared to an FFG-62 follow-on ship unit procurement cost of roughly $1.1 billion to $1.2 billion, the above estimated increase of $16 million to $24 million would equate to an increase in unit procurement cost of about 1.3% to about 2.2%.91 The estimated figure of $16 million to $24 million, however, dates to 2019. Inflating it to current costs would produce a percentage increase in total ship procurement cost that would be somewhat greater than 1.3% to 2.2%.
Technical RiskAnother potential oversight issue for Congress concerns technical risk in the FFG-62 program.
June 2025 and May 2024 GAO Reports
Regarding GAO's perspective on technical risk in the FFG-62 program, see the quoted passages from the June 2025 and May 2024 GAO reports on the FFG-62 program presented earlier in this CRS report.
January 2024 DOT&E ReportA January 2024 report from DOD's Director, Operational Test and Evaluation (DOT&E)—DOT&E's annual report for FY202392—stated the following regarding the FFG-62 program:
TEST ADEQUACY
In March 2023, DOT&E published a classified FFG 62 EOA [early operational assessment] report based on evaluations conducted between February 2022 and July 2022 and detailed in the FY22 Annual Report. Evaluations were adequate to determine potential FFG 62 design risks that could affect operational effectiveness and suitability of the delivered ship. The EOA provides the FFG 62 Program with an opportunity to consider modifications to the ship design. The FFG 62 Program will also use the EOA to inform development of the next TEMP [test and evaluation master plan] revision expected to be completed in FY25. The Navy conducted the EOA in accordance with a DOT&E-approved test plan, and it was observed by DOT&E.
In FY23, the Navy conducted testing against a large scale-model of a generic ship incorporating characteristics typical of Navy standard ship structure and a responding mid-deck plate to generate response data for under-bottom explosions. This test was similar to the test detailed in the FY22 Annual Report but focused on different structure response. Data from these tests provide validation data for survivability models used to predict the magnitude and extent of damage from underwater threat weapons. The Navy conducted this test in accordance with the DOT&E-approved test plan, and it was observed by DOT&E.
In FY23, the FFG 62 Program approved the FFG 62 Verification, Validation, and Accreditation (VV&A) Plans for the Advanced Survivability Assessment Program (ASAP) and Navy Enhanced Sierra Mechanics (NESM) M&S [modeling and simulation] tools. These plans are adequate to determine the sufficiency of these M&S within the LFT&E [live fire test and evaluation] test strategy. Further, the Navy continued M&S modification that incorporates new capabilities, including improvements in the blast and whipping codes. The Navy is working closely with DOT&E on the development of M&S plans to support the Detail Design Survivability Assessment Report that the FFG 62 Program expects to publish in FY26.
PERFORMANCE
EFFECTIVENESS
No data are available to determine FFG 62 operational effectiveness due to FFG 62 being in development. However, the FFG 62 design presents risks to operational effectiveness in each of its primary mission areas: air warfare, anti-submarine warfare, and surface warfare. Classified risks to operational effectiveness are in the FFG 62 EOA report. Unclassified risks to operational effectiveness include that the FFG 62 design does not have a tracker illuminator system, which is typically installed on other Aegis platforms, and that the design crew size will be highly reliant on currently unproven system automation and human system interfaces. The Navy acknowledges the risk of the current crewing strategy for FFG 62 and is working with the appropriate stakeholders to mitigate and eliminate the associated risk to mission performance. Further, the FFG 62 Program reports that they currently have sufficient access to technical information on the Thales CAPTAS-4 [variable-depth sonar] needed to effectively integrate it with the AN/SQQ-89(V)16 [undersea warfare] system.
SUITABILITY
No data are available to determine FFG 62 operational suitability due to FFG 62 being in development. Further, reliability, maintainability, and availability data for hull, mechanical, and electrical systems are not yet available to identify associated risk in the FFG 62 design.
SURVIVABILITY
No data are available to determine the cyber survivability of FFG 62 due to its early stage of development. Cyber survivability was not assessed during the EOA.
Insufficient data are available to determine FFG 62 survivability due to ongoing LFT&E. The Navy continued to close outstanding vulnerability knowledge gaps and support validation of survivability M&S through additional large-scale underwater explosion testing in FY23.
RECOMMENDATIONS
The Navy should:
1. Provide an update to the FFG 62 TEMP that includes the strategy to test anti-air warfare mission capability.
2. Continue to monitor the development of the mission system autonomy/automation components in the ship design to minimize risk to mission performance and system maintenance capability, and if necessary, complete a reassessment of the adequacy of crew sizing to allow opportunity to incorporate modifications of the ship design, should additional crewing be required to support all intended missions.93
Appendix B. Guaranty vs. Warranty in Construction ContractThis appendix presents background information regarding the Navy's use of a guaranty rather than a warranty in the Detail Design and Construction (DD&C) contract for the first 10 ships in the FFG-62 program. An August 2019 GAO report on the FFG-62 program states
The Navy plans to use a fixed-price incentive contract for FFG(X) detail design and construction. This is a notable departure from prior Navy surface combatant programs that used higher-risk cost-reimbursement contracts for lead ship construction. The Navy also plans to require that each ship has a minimum guaranty of $5 million to correct shipbuilder-responsible defects identified in the 18 months following ship delivery. However, Navy officials discounted the potential use of a warranty—another mechanism to address the correction of shipbuilder defects—stating that their use could negatively affect shipbuilding cost and reduce competition for the contract award. The Navy provided no analysis to support these claims and has not demonstrated why the use of warranties is not a viable option. The Navy's planned use of guarantees helps ensure the FFG(X) shipbuilder is responsible for correcting defects up to a point, but guarantees generally do not provide the same level of coverage as warranties. GAO found in March 2016 that the use of a guaranty did not help improve cost or quality outcomes for the ships reviewed. GAO also found the use of a warranty in commercial shipbuilding and certain Coast Guard ships improves cost and quality outcomes by requiring the shipbuilders to pay to repair defects. The FFG(X) request for proposal offers the Navy an opportunity to solicit pricing for a warranty to assess the cost-effectiveness of the different mechanisms to address ship defects.53
As discussed in another CRS report,5495 in discussions of Navy (and also Coast Guard) shipbuilding, a question that sometimes arises is whether including a warranty in a shipbuilding contract is preferable to not including one. The question can arise, for example, in connection with a GAO finding that "the Navy structures shipbuilding contracts so that it pays shipbuilders to build ships as part of the construction process and then pays the same shipbuilders a second time to repair the ship when construction defects are discovered."55
Including a warranty in a shipbuilding contract (or a contract for building some other kind of defense end item), while potentially valuable, might not always be preferable to not including one—it depends on the circumstances of the acquisition, and it is not necessarily a valid criticism of an acquisition program to state that it is using a contract that does not include a warranty (or a weaker form of a warranty rather than a stronger one).
Including a warranty generally shifts to the contractor the risk of having to pay for fixing problems with earlier work. Although that in itself could be deemed desirable from the government's standpoint, a contractor negotiating a contract that will have a warranty will incorporate that risk into its price, and depending on how much the contractor might charge for doing that, it is possible that the government could wind up paying more in total for acquiring the item (including fixing problems with earlier work on that item) than it would have under a contract without a warranty.
When a warranty is not included in the contract and the government pays later on to fix problems with earlier work, those payments can be very visible, which can invite critical comments from observers. But that does not mean that including a warranty in the contract somehow frees the government from paying to fix problems with earlier work. In a contract that includes a warranty, the government will indeed pay something to fix problems with earlier work—but it will make the payment in the less-visible (but still very real) form of the up-front charge for including the warranty, and that charge might be more than what it would have cost the government, under a contract without a warranty, to pay later on for fixing those problems.
From a cost standpoint, including a warranty in the contract might or might not be preferable, depending on the risk that there will be problems with earlier work that need fixing, the potential cost of fixing such problems, and the cost of including the warranty in the contract. The point is that the goal of avoiding highly visible payments for fixing problems with earlier work and the goal of minimizing the cost to the government of fixing problems with earlier work are separate and different goals, and that pursuing the first goal can sometimes work against achieving the second goal.56
DOD's guide on the use of warranties states the following:
Federal Acquisition Regulation (FAR) 46.7 states that "the use of warranties is not mandatory." However, if the benefits to be derived from the warranty are commensurate with the cost of the warranty, the CO [contracting officer] should consider placing it in the contract. In determining whether a warranty is appropriate for a specific acquisition, FAR Subpart 46.703 requires the CO to consider the nature and use of the supplies and services, the cost, the administration and enforcement, trade practices, and reduced requirements. The rationale for using a warranty should be documented in the contract file....
In determining the value of a warranty, a CBA [cost-benefit analysis] is used to measure the life cycle costs of the system with and without the warranty. A CBA is required to determine if the warranty will be cost beneficial. CBA is an economic analysis, which basically compares the Life Cycle Costs (LCC) of the system with and without the warranty to determine if warranty coverage will improve the LCCs. In general, five key factors will drive the results of the CBA: cost of the warranty + cost of warranty administration + compatibility with total program efforts + cost of overlap with Contractor support + intangible savings. Effective warranties integrate reliability, maintainability, supportability, availability, and life-cycle costs. Decision factors that must be evaluated include the state of the weapon system technology, the size of the warranted population, the likelihood that field performance requirements can be achieved, and the warranty period of performance.57
In response to a draft version of GAO's August 2019 report, the Navy stated
As a part of the planning for the procurement of detail design and construction for FFG(X), the Navy determined that a guaranty, rather than a commercial-type warranty, will be implemented for the program. As a part of the FFG(X) detail design and construction request for proposals [RFP] released on June 20, 2019, the Navy asked contractors to include a limit of liability of at least $5 million per ship and a guaranty period of 18 months beyond preliminary acceptance of each ship. Further, the solicitation allows offerors to propose as additional limit of liability amount beyond the required $5 million amount, up to and including an unlimited liability. This arrangement represents an appropriate balance between price considerations and risks, ensuring that the shipbuilder is accountable for the correction of defects that follow preliminary acceptance, while allowing each shipbuilder to use its own business judgement in proposing the value of the limit of liability. The Navy released the solicitation prior to this GAO recommendation and is unable to modify the current solicitation because it would cause an unacceptable delay to the FFG(X) program.
To support the GAO recommendation to request pricing for an unlimited warranty, the Navy will request pricing for unlimited warranty before exercising the first ship option and evaluate the business case.58
Tony Bertuca, "Hegseth Indicates Frigate Program Is on the Chopping Block," Inside Defense, June 12, 2025.
See, for example, U.S. Navy, "Navy Announces New Small Surface Combatant," press release dated December 19, 2025; Huntington Ingalls Industries, "HII to Build Small Surface Combatants for US Navy," news release dated December 19, 2025; Justin Katz, "Navy Announces New Frigate Class, Taps HII to Build Off National Security Cutter," Breaking Defense, December 19, 2025; Sam LaGrone, "SECNAV: New Frigate will be Based on National Security Cutter, First FF(X) to be Built at Ingalls," USNI News, December 19 2025; Joseph Trevithick, "This Will Be The Navy's New FF(X) Frigate," The War Zone, December 19, 2025; Joseph Trevithick, "U.S. Navy Now Wants A New Frigate And Fast," Breaking Defense, December 12, 2025; Justin Katz, "Navy Wants New Frigate in 2028, Says Service's Acquisition Head," Breaking Defense, December 10, 2025; Rich Abott, "Navy "Golden Fleet" Plan To Include Another Frigate, LSM To Avoid Change Orders," Defense Daily, December 9, 2025; Mike Glenn, "Navy Secretary Announces New Frigate Program after Canceling Future Constellation-Class Warships," Washington Times, December 9, 2025; Lauren C. Williams, "And Just Like That, the Navy's Frigate Program Is Back On—Sort Of," Defense One, December 8, 2025; Tom Kington, "US Navy Nixes Constellation Frigate Program after Two Ships Half-Built," Defense News, November 26, 2025; Rich Abott, "Navy Cancels Constellation-Class Frigate, Will Only Retain Two Under Construction," Defense Daily, November 25, 2025; Anthony Capaccio, "Navy Cuts Orders for Frigate Trump Once Touted as 'Beautiful,'" Bloomberg, November 25, 2025; Drew FitzGerald and Lara Seligman, "Navy Scraps Plans for Troubled Warship Design," Wall Street Journal, November 25, 2025; Sam LaGrone, "Navy Cancels Constellation-class Frigate Program, Considering New Small Surface Combatants," USNI News, November 25, 2025.
For more on the DDG-51 class destroyer program, see CRS Report RL32109, Navy DDG-51 and DDG-1000 Destroyer Programs: Background and Issues for Congress, by Ronald O'Rourke.
See, for example, Mike Glenn, "Navy Wants New Frigate in 2028, Says Service's Acquisition Head," Washington Times, December 10, 2025; Rich Abott, "Navy "Golden Fleet" Plan To Include Another Frigate, LSM To Avoid Change Orders," Defense Daily, December 9, 2025; Joseph Trevithick, "U.S. Navy Now Wants A New Frigate And Fast," The War Zone, December 12, 2025.
Sam LaGrone, "Navy Cancels Constellation-class Frigate Program, Considering New Small Surface Combatants," USNI News, November 25, 2025.
Sam LaGrone, "Navy Cancels Constellation-class Frigate Program, Considering New Small Surface Combatants," USNI News, November 25, 2025.
|
See, for example, CRS Report RL32665, Navy Force Structure and Shipbuilding Plans: Background and Issues for Congress, by Ronald O'Rourke. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
U.S. Navy, Report to Congress on the Annual Long-Range Plan for Construction of Naval Vessels for Fiscal Year 2025, March 2024, Table 1 on page 4, column entitled "June 2023 BFSAR [Battle Force Ship Assessment and Requirement] Report. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
10.
See for example, Rich Abott, "Navy 'Golden Fleet' Plan To Include Another Frigate, LSM To Avoid Change Orders," Defense Daily, December 9, 2025. |
Compared to cruisers and destroyers, frigates can be a more cost-effective way to perform missions that do not require the use of a higher-cost cruiser or destroyer. In the past, the Navy's combined force of higher-capability, higher-cost cruisers and destroyers and lower-capability, lower-cost frigates has been referred to as an example of a so-called high-low force mix. High-low mixes have been used by the Navy and the other military services in recent decades as a means of balancing desires for individual platform capability against desires for platform numbers in a context of varied missions and finite resources. Peacetime missions performed by frigates can include, among other things, engagement with allied and partner navies, maritime security operations (such as anti-piracy operations), and humanitarian assistance and disaster response (HA/DR) operations. Intended wartime operations of frigates include escorting (i.e., protecting) military supply and transport ships and civilian cargo ships that are moving through potentially dangerous waters. In support of intended wartime operations, frigates are designed to conduct anti-air warfare (AAW—aka air defense) operations, anti-surface warfare (ASuW) operations (meaning operations against enemy surface ships and craft), and antisubmarine warfare (ASW) operations. U.S. Navy frigates are designed to operate in larger Navy formations or as solitary ships. Operations as solitary ships can include the peacetime operations mentioned above. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
The three shipyards were Bath Iron Works (BIW) of Bath, ME (now referred to as General Dynamics/Bath Iron Works or GD/BIW), Todd Shipyards of Seattle, WA, and Todd Shipyards of San Pedro, CA. Todd Shipyards of Seattle was acquired in 2011 by Vigor Shipyards. (See, for example, "Vigor Shipyards," Wikipedia, edited January 22, 2024.) Todd Shipyards of San Pedro was closed in 1989 following the completion of its FFG-7 construction work. (See, for example, "Todd Pacific Shipyards, Los Angeles Division," Wikipedia, edited January 26, 2023.) |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
This is the displacement for the current (Flight III) version of the DDG-51 design. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
In the designation FFG(X), The designation FF, with two Fs, means frigate in the same way that the designation Some U.S. Navy surface combatants are equipped with a point-defense AAW system, meaning a short-range AAW system that is designed to protect the ship itself. Other U.S. Navy surface combatants are equipped with an area-defense AAW system, meaning a longer-range AAW system that is designed to protect not only the ship itself, but other ships in the area as well. U.S. Navy surface combatants equipped with an area-defense AAW system are referred to as guided-missile ships and have a "G" in their designation. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
U.S. Navy, Report to Congress on the Annual Long-Range Plan for Construction of Naval Vessels for Fiscal Year 2025, March 2024, Table 1 on page 4, column entitled "June 2023 BFSAR [Battle Force Ship Assessment and Requirement] Report. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
See, for example, U.S. Navy, Report to Congress on the Annual Long-Range Plan for Construction of Naval Vessels for Fiscal Year 2025, March 2024, p. 13. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 9. |
"FFG 62 Constellation Class Frigate Program, Sources Sought / Request for Information," published November 15, 2024, at https://sam.gov/opp/5df8c0d9f5da4805a080e066928011f2/view. See also Justin Katz, "State of Play: Industry Readying for Second Chance at US Navy's Frigate Program," Breaking Defense, December 20, 2024. Nick Wilson, "Navy Seeking Shipbuilders for Frigate Design and Construction Work with New RFI," Inside Defense, November 15, 2024; Rich Abott, "Navy Investigates More Frigate Design And Construction Sources Amid Major Delays," Defense Daily, November 19, 2024. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 10. |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
For more on the |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
18.
For more on the LSM program, see CRS Report R46374, Navy Medium Landing Ship (LSM) Program: Background and Issues for Congress, by Ronald O'Rourke. |
The Navy's Osprey (MCM-51) class mine warfare ships are an enlarged version of the Italian Lerici-class mine warfare ships. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
The FRC design is based on a Dutch patrol boat design, the Damen Stan Patrol Boat 4708. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Robert G. Keane Jr. and Barry F. Tibbitts, "The Fallacy of Using a Parent Design: 'The Design Is Mature,'" Transactions (Society of Naval Architects and Marine Engineers [SNAME]), 2015, No. 1 (January): 91-104, with additional discussion from the authors and other commentators on pages 105-122. The quoted passage appears at the start of the article, on page 91, where it forms part of an abstract or summary for the article. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Source: Navy information paper dated August 18, 2021, on differences between FFG-62 design and FREMM parent design, provided to CRS and the Congressional Budget Office (CBO) by Navy Office of Legislative Affairs on August 27, 2021. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Justin Katz, "Navy Says Constellation Hull Change Won't Affect Internal Design," Breaking Defense, August 4, 2021. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Mallory Shelbourne and Sam LaGrone, "Constellation Frigate Delivery Delayed 3 Years, Says Navy," USNI News, April 2 (updated April 3), 2024. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
The phrase parent design in name only (with the resulting acronym PDINO) is only one possible shorthand way of referring to the situation. One possible way to pronounce the acronym PDINO would be pa-DEE-no. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Former Assistant Secretary of the Navy (Research, Development, and Acquisition), as quoted in John Grady, "Navy's Plan for Frigate Parent Design Caused Delays, Former Acquisition Chief Says," USNI News, February 19, 2025. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Captain Andy Gold, program manager for the FFG-62 program within Program Executive Office (PEO) Unmanned and Small Combatants, as quoted in Rich Abott, "Frigate Manager Says Design To Finish This Year, Delays Because Parent Design Mods Not Understood," Defense Daily, January 15, 2025. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
For more on the LCS program, see CRS Report RL33741, Navy Littoral Combat Ship (LCS) Program: Background and Issues for Congress, by Ronald O'Rourke. 28.
|
|
See page 2 and Table 2 (on page 9) of the April 17, 2020, update of this CRS report. 29.
|
|
Joseph Trevithick, "U.S. Navy Now Wants A New Frigate And Fast," The War Zone, December 12, 20205. 30.
|
|
Naval Station Everett is located in Everett, WA, which is on Puget Sound north of Seattle. 31.
|
|
U.S. Navy, "Naval Station Everett Future Homeport for New Constellation Class Frigates," press release dated June 2, 2021. 32.
|
|
Government Accountability Office, Navy Frigate[:] Unstable Design Has Stalled Construction and Compromised Delivery Schedules, GAO-24-106546, May 2024, highlights page. See also Richard Thomas, "Could US Navy's Constellation-Class Frigates Share Littoral Combat Ship Fate?," Naval Technology, June 11, 2024; Joseph Trevithick, "Navy's New Constellation Class Frigate Is A Mess," The War Zone, May 30, 2024. 33.
|
|
U.S. Navy, "Navy Announces New Small Surface Combatant," press release dated December 19, 2025. 34.
|
|
Sam LaGrone, "SECNAV: New Frigate will be Based on National Security Cutter, First FF(X) to be Built at Ingalls," USNI News, December 19, 2025. 35.
|
|
CRS Report R42567, Coast Guard Cutter Procurement: Background and Issues for Congress, by Ronald O'Rourke. 36.
|
|
Sam LaGrone, "Ingalls, Coast Guard Scrap 11th National Security Cutter Over Contract Impasse, Says HII," USNI News, June 5, 2025. 37.
|
U.S. Coast Guard, "National Security Cutter," accessed December 18, 2025, at https://www.dcms.uscg.mil/Our-Organization/Assistant-Commandant-for-Acquisitions-CG-9/Programs/Surface-Programs/National-Security-Cutter/.
38.
|
See, for example, Sam LaGrone, "HII Targets Global Market with New Patrol Frigate," Jane's Defence Weekly, January 13, 2012; Huntington Ingalls Industries, "Ingalls Shipbuilding Highlighting Patrol Frigate Derivative of National Security Cutter at DIMDEX," news release dated March 26, 2012; Mrityunjoy Mazumdar, "Patrol Frigate Concepts from Huntington Ingalls Industries Gain Traction Internationally," Defense Media Network, April 24, 2012; Scott C. Truver, "Payloads over Platforms: Designing the 'Flexible Frigate,'" Naval Engineers Journal, September 2013, pp. 31-38; "Ingalls Shipbuilding Highlights its Patrol Frigate at Sea-Air-Space 2014," Navy Recognition, April 9, 2014; Huntington Ingalls Industries, "Ingalls Shipbuilding Sea Control Frigate," YouTube, April 14, 2014, at https://www.youtube.com/watch?v=5OJZ8eB_mPA&t=6s.
39.
|
|
See, for example, Zachary Howitt, "It's Time for a 'Sea-Control Frigate,'" U.S. Naval Institute Proceedings, April 2014; Dave Majumdar, "Huntington Ingalls Has a New Frigate that Could Give the U.S. Navy Some Impressive Capabilities," National Interest, January 11, 2017; Harold C. Hutchison, "The Coast Guard Could Have the Solution for a Bigger US Navy," We Are the Mighty, November 1, 2018. 40.
|
|
See, for example, the additional renderings shown at Joseph Trevithick, "This Will Be The Navy's New FF(X) Frigate," The War Zone, December 19, 2025. 41.
|
|
See, for example, the discussion of this point in Joseph Trevithick, "This Will Be The Navy's New FF(X) Frigate," The War Zone, December 19, 2025. 42.
|
|
A point-defense AAW system has a range sufficient to defend the ship itself, but not other ships in the area. An area-defense AAW system has a longer range that is sufficient for defending not only the ship itself, but also other ships in the area. In the U.S. Navy, ships capable of firing the Standard Missile interceptor, which is a longer-ranged AAW interceptor, are considered to have an area-defense AAW system and have a G in their designation, while ships that cannot fire the Standard Missile and employ shorter-ranged interceptors, such as the Evolved Sea Sparrow Missile (ESSM) or Rolling Airframe Missile (RAM), are considered to have a point-defense AAW system and do not have a G in their designation. 43.
|
|
Sam LaGrone, "SECNAV: New Frigate will be Based on National Security Cutter, First FF(X) to be Built at Ingalls," USNI News, December 19, 2025. 44.
|
|
Sam LaGrone, "SECNAV: New Frigate will be Based on National Security Cutter, First FF(X) to be Built at Ingalls," USNI News, December 19, 2025. 45.
|
|
Joseph Trevithick, "This Will Be The Navy's New FF(X) Frigate," The War Zone, December 19, 2025. 46.
|
|
For more on the Navy's program for procuring large USVs, see CRS Report R45757, Navy Large Unmanned Surface and Undersea Vehicles: Background and Issues for Congress, by Ronald O'Rourke. 47.
|
|
Potential examples of such missions include engagement with allied and partner navies, humanitarian assistance/disaster response (HA/DR) operations, noncombatant evacuation operations (NEOs), maritime security operations (such as anti-piracy operations), and operations with embarked Coast Guard law-enforcement detachments for fisheries enforcement or interdiction of illegal migrants and illegal drug shipments. 48.
|
|
For more information on the DDG(X) program, see CRS In Focus IF11679, Navy DDG(X) Next-Generation Destroyer Program: Background and Issues for Congress, by Ronald O'Rourke. 49.
|
|
The earlier years of the LCS procurement program included the cancellation of two LCSs funded in FY2006, another two LCSs funded in FY2007, and an LCS funded in FY2008, followed by procurement of additional LCSs through FY2019. For notations of the cancelled LCSs, see note 1 to the second table in the Appendix entitled "Size of the Navy and Navy Shipbuilding Rate" in CRS Report RL32665, Navy Force Structure and Shipbuilding Plans: Background and Issues for Congress, by Ronald O'Rourke; and the note to Table 1 (on page 3) of the December 17, 2019, update (the final update) to CRS Report RL33741, Navy Littoral Combat Ship (LCS) Program: Background and Issues for Congress, by Ronald O'Rourke. 50.
|
|
They could also argue, as skeptics of the second approach (i.e., the Navy's desired approach) could argue, that design work on the FFG-62 is progressing toward completion; that truncating FFG-62 procurement to two ships would provide a limited return on the investment of time and funding that the Navy has expended to complete the FFG-62 design (which needs to be completed to support the construction of the first two ships); that it would not be optimal for the Navy to create another case, alongside cases such as the Seawolf and Zumwalt classes, of paying elevated per-ship O&S costs for a numerically limited class; and that there is no guarantee that the Navy would be able to find one or two allied or partner navies willing to buy two FFG-62s unless their purchase price is set substantially below their original procurement costs. 51.
|
|
Source for displacement figure of more than 3,900 tons: Program Executive Office Unmanned and Small Combatants (PEO USC) Public Affairs, "Navy Cuts Steel on First Multi-Mission Surface Combatant Ship for Saudi Arabia," Naval Sea Systems Command, November 18, 2019, which cites a figure of more than 4,000 metric tons, which equates to more than 3,936 long tons. 52.
|
|
For more on the MMSC, see, for example, "The First MMSC-1 Frigate Built by Fincantieri in the United States for the Royal Saudi Navy Was Launched," Zona Militar, December 29, 2025; Richard Scott, "First Saudi MMSC launched by Fincantieri in Wisconsin," Naval News, December 24, 2025; Chris Cavas, "First Look: Fincantieri Marine Group Production Includes US Navy's Frigate, LCS and Saudi Combatants," Naval News, February 2, 2024; "Multi-Mission Surface Combatant (MMSC)," Naval Technology, July 31, 2020; Sam LaGrone, "Lockheed Awarded $1.96B Construction Contract for Four Saudi Frigates," USNI News, December 20, 2019; Paul McLeary, "Saudis Save Wisconsin Shipbuilder: Fills Gap Between LCS & Frigates At Marinette," Breaking Defense, January 17, 2019; Defense Security Cooperation Agency (DSCA), "Kingdom of Saudi Arabia - Multi-Mission Surface Combatant (MMSC) Ships," news release, October 20, 2015. 53.
|
|
The Navy's 1991 study was called the destroyer variant (DDV) study (or studies). A 1994 journal article about the DDV study states: The Destroyer Variant (DDV) studies were initiated in mid-1991 by OPNAV [the office of the Chief of Naval Operations] to evaluate a variety of potential follow-on destroyer designs covering the spectrum from a non-AEGIS low-end reference [design] ([designated] DDV 1) to a [DDG-51] Flight III lookalike [design] with a 40-foot [hull] plug [i.e., a 40-foot increase in hull length] as a high-end reference [design] ([designated] DDV H).… The acquisition cost of DDV 1 was estimated to be 53 percent of DDV H, while the other non-AEGIS variant costs were between 70 and 87 percent of DDV H. (Robert J. Scott and Kevin E. Moak, "Studies of Helicopter Capable DDG 51 Variants," Naval Engineers Journal, September 1994, p. 34.) For additional mentions of the DDV study, see Donald L. Ewing, et al., "A Surface Combatant for the 21st Century: DDG 51 Flight IIA," Naval Engineers Journal, May 1995, p. 218; George A. Huchting, "Lean and Mean Warship Design," U.S. Naval Institute Proceedings, October 1994; Department of the Navy, Department of the Navy 1992 Posture Statement, A Report by The Honorable H. Lawrence Garrett, III, Secretary of the Navy, Admiral Frank B. Kelso, II, United States Navy, Chief of Naval Operations, and General Carl E. Mundy, Jr., United States Marine Corps, Commandant of the Marine Corps on the Posture and the Fiscal Year 1993 Budget of the United States Navy and The United States Marine Corps, February-March 1992, p. 25; John F. Morton, "The U.S. Navy in 1991," U.S. Naval Institute Proceedings, May 1992; R. K. U. Kihune, "Message for the Fleet Sailor," Surface Warfare, September/ October 1991, p. 1. For blog entries in more recent years that discuss different potential options for a reduced-cost DDG-51 variant, see Craig Hooper, "Time To Consider A Low-End "Littoral Operations Variant" DDG-51?," Next Navy, April 22, 2014; Mike Burleson, "Flight III: Building a Better Burke," New Wars, March 1, 2010. 54.
|
Thirty-one Spruance-class ships were procured for the Navy from FY1970 through FY1978; the ships entered service in 1975-1983 and were decommissioned in 1998-2005. CRS testimony to the Seapower and Projections Forces subcommittee of the House Armed Services Committee in October 2013 discussed the Spruance-class design, stating that it
was criticized as being underarmed for its size—for having something like a frigate's worth of combat systems on a destroyer hull. The criticism arose in part from a Navy decision to make the ship more affordable to procure: The ship was originally designed with both a full-capability ASW [antisubmarine warfare] system and a full-capability AAW [anti-air warfare, aka air defense] system (which, in those pre-Aegis days, was the digital Tartar/SM-2 system). To reduce the ship's procurement cost, the Navy decided that the most important mission need to be met by the ship was ASW. Accordingly, the ship's full-capability ASW system was retained while its AAW system was de-scoped to a less-capable and less-expensive point-defense system. While this contributed to criticism that the ship was underarmed for its size, a decision to retain the full-capability AAW system might well have led to a different criticism—that the ship was insufficiently affordable for the shipbuilding budgets of the day. The de-scoping of the ship's AAW system, as it turned out, left the ship with ample growth margin, which the Navy years later used to install a 61-cell vertical launch system (VLS) on 24 of the 31 DD-963s, giving those ships an additional mission of acting as Tomahawk strike platforms—a mission not originally contemplated for the ships, and one that contributed to the ship's cost effectiveness in their later years of service. (Statement of Ronald O'Rourke, Specialist in Naval Affairs, Congressional Research Service, before the House Armed Services Committee, Subcommittee on Seapower and Projection Forces, on The Navy's FY2014 30-Year Shipbuilding Plan, October 23, 2013, p. 10.) 55.
|
|
Source for figure of 5,400 tons: Joseph Trevithick, "Japan's Futuristic Mogami Frigate Will Be Australia's Next Warship," The War Zone, August 4, 2025, which cites a figure of 5,500 metric tons, which equates to 5,413 long tons. 56.
|
|
Source for figure of 6,100 tons: Joseph Trevithick, "Japan's Futuristic Mogami Frigate Will Be Australia's Next Warship," The War Zone, August 4, 2025, which cites a figure of 6,200 metric tons, which equates to 6,102 long tons. 57.
|
|
For additional discussion of the Mogami-class design and Australia's decision to acquire 11 Mogami-variant ships, see, for example, "Mogami-Class Frigate," Wikipedia, edited December 25, 2025, accessed January 1, 2025; Moyuru Tanaka, "The Mogami: Advancing Australia-Japan Defense Cooperation," Center for Strategic and International Studies (CSIS), November 21, 2025; Iku Tsujihiro and Masashi Murano, "Japan and Australia's Mogami Gamble: A New Role in a Taiwan Strait Contingency," Hudson Institute, September 23, 2025; Joseph Trevithick, "Japan's Futuristic Mogami Frigate Will Be Australia's Next Warship," The War Zone, August 4, 2025; Oliver Parken, "Japan's Futuristic Mogami Frigates: Everything You Need To Know," The War Zone, November 17, 2023; Eric Wertheim, "Japan's Multimission Mogami-class Frigates," U.S. Naval Institute Proceedings, September 2023. 58.
|
|
For more on the Daegu-class design, see "Daegu-Class Frigate," Wikipedia, edited December 27, 2025, accessed January 1, 2026; Eric Wertheim, "South Korea's Future Experimental Frigates," U.S. Naval Institute Proceedings, October 2025; Jamie Chang, "South Korea Commissions Final Daegu-class FFX Batch II Frigate," Naval News, October 24, 2023; "FFX-II (Daegu Class) Multi-Role Frigates," Naval Technology, September 5, 2016. 59.
|
|
For more on the F100 design, see Navantia, "F-100," undated, accessed January 1, 2026; "Álvaro de Bazán-Class Frigate," Wikipedia, edited December 12, 2025, accessed January 1, 2026; Brandon J. Weichert, "Here's How Spain Is Keeping Its F100 Frigates Relevant Through 2045," National Interest, December 15 2025; Ben Werner, "Spanish Shipbuilder Navantia Showcases F-100 Frigate Design," USNI News, January 22, 2019. 60.
|
|
For more on the F110 design, see "F110-Class Frigate," Wikipedia, edited December 16, 2025, accessed January 1, 2026; Navantia, "F-110," undated, accessed January 1, 2026; Xavier Vavasseur, "Spain's Navantia Proposing Two New Frigate Designs to the Hellenic Navy," Naval News, December 4, 2021. |
Regarding Section 125, the conference report (H.Rept. 116-617 of December 3, 2020) on H.R. 6395/P.L. 116-283 of January 1, 2021, states Given that the Constellation-class will play a significant role in the Navy battle force for many decades and the current program of record calls for building 20 frigates, the conferees believe a strong technical foundation for this program is critically important. The conferees note that the winning Constellation-class ship design is based on a foreign design. While recognizing an existing parent design can reduce design, technical, and integration risks, the conferees are concerned that significant risks remain in the FFG-62 program, including: cost realism; shifting to predominantly U.S. component suppliers instead of the mainly foreign suppliers used in the parent vessel design; and a complex Combined Diesel Electric and Gas Hull, Mechanical and Electrical (HM&E) drive train that has not previously been used on U.S. Navy ships. The conferees believe land based engineering and test sites (LBETS) are critical resources for the Department of Defense, particularly for Navy ship HM&E systems.… Since 1972, NSWCPD LBETS testing has reduced the acquisition risk of five of the seven Navy surface combatant classes (Spruance-class, Oliver Hazard Perry-class, Ticonderoga-class, Arleigh Burke-class, and Zumwalt-class).… The littoral combat ship (LCS) classes, the Freedom- and Independence-classes, are the two recent classes that have not had the benefit of a LBETS. Since lead ship deliveries in 2008 and 2010, both LCS classes have encountered significant, costly, and debilitating engineering failures. The conferees believe many of these LCS engineering failures would have been discovered, analyzed, and corrected faster with less negative operational impact had the Navy established a LCS LBETS. Accordingly, the provision would require the Secretary of the Navy to establish a FFG-62 class LBETS as soon as possible.… In addition, the conferees direct the Secretary to submit to the congressional defense committees a plan to implement this section with the budget materials that accompany the President's Budget request for fiscal year 2022. This plan shall include the costs, activities, and test plan necessary to meet the requirements under this section. (Pages 1523-1524) |
| 22. |
For more on block buy contracting, see CRS Report R41909, Multiyear Procurement (MYP) and Block Buy Contracting in Defense Acquisition: Background and Issues for Congress, by Ronald O'Rourke. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 23. |
Naval Station Everett is located in Everett, WA, which is on Puget Sound north of Seattle. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 24. |
U.S. Navy, "Naval Station Everett Future Homeport for New Constellation Class Frigates," press release dated June 2, 2021. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 25. |
Mallory Shelbourne and Sam LaGrone, "First Constellation Frigate Delayed At Least a Year, Schedule Assessment 'Ongoing,'" USNI News, January 11, 2024. See also Megan Eckstein, "Frigate Program Delayed as Shipyard Is a 'Few Hundred' Workers Short," Defense News, January 11, 2024. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 26. |
Department of Defense, Fiscal Year (FY) 2025 Budget Estimates, Navy, Justification Book Volume 1 of 1, Shipbuilding and Conversion, Navy, March 2024, p. 234. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 27. |
As a best practice for shipbuilding, the Navy generally aims for the detail design of a new class of Navy ship to be 80%-85% complete before beginning construction of the first ship in the program. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 28. |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 29. |
Mallory Shelbourne and Sam LaGrone, "Constellation Frigate Delivery Delayed 3 Years, Says Navy," USNI News, April 2 (updated April 3), 2024. See also Megan Eckstein, "US Navy Ship Programs Face Years-Long Delays amid Labor, Supply Woes," Defense News, April 2, 2024. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 30. |
Anthony Capaccio, "US Navy's New Warship Is Plagued by Worker Turnover," Bloomberg, April 12, 2024. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 31. |
Government Accountability Office, Navy Frigate[:] Unstable Design Has Stalled Construction and Compromised Delivery Schedules, GAO-24-106546, May 2024, highlights page. See also Richard Thomas, "Could US Navy's Constellation-Class Frigates Share Littoral Combat Ship Fate?" Naval Technology, June 11, 2024; Joseph Trevithick, "Navy's New Constellation Class Frigate Is A Mess," The War Zone, May 30, 2024. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 32. |
Mallory Shelbourne and Sam LaGrone, "Navy: Constellation Frigate Design Will be Ready in May, Second Yard Could Come in FY 2027," USNI News, December 13, 2024. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 33. |
See, for example, the version dated December 21, 2022, or earlier versions dating back to the version of May 4, 2020. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 34. |
Congressional Budget Office, The Cost of the Navy's New Frigate, October 2020, 11 pp. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
For more on the Alfa 3000, 4000, and 5000 frigate designs, see Navantia, Alfa 4000," undated, accessed January 1, 2026; Alex Luck, "Navantia Presents Revised Alfa 4000 Light Frigate And Smart LPD Concept At Indo Pacific 2025," Naval News, November 11, 2025; Alex Luck, "Navantia Unveils Three New Warships Including Tier-2 Corvette," Naval News, August 11, 2023; Xavier Vavasseur, "Spain's Navantia Proposing Two New Frigate Designs to the Hellenic Navy," Naval News, December 4, 2021. 62.
|
|
For more on the Type 26 and Type 31 frigate designs, see "Type 26 Frigate," Wikipedia, edited December 14, 2025, accessed January 1, 2026; "Type 31 Frigate," edited December 31 2025, accessed January 1, 2026. 63.
|
For more on the MEKO 200 and MEKO 400 frigate designs, see TKMS, "MEKO A-200," undated, accessed January 1, 2026; "MEKO 200," Wikipedia, edited December 31, 2025, accessed January 1, 2026; TKMS, "MEKO A-400 AMD," undated, accessed January 1, 2026.For press reports discussing some of potential options listed here, see Joseph Trevithick, "U.S. Navy Now Wants A New Frigate And Fast," The War Zone, December 12, 2025; Joseph Trevithick, "Japan's Futuristic Mogami Frigate Will Be Australia's Next Warship," The War Zone, August 4, 2025.
64.
|
|
Joseph Trevithick, "Navy's New Frigate Will Not Have A Vertical Launch System For Missiles," The War Zone, December 22, 2025. 65.
|
|
Sam LaGrone, "SECNAV: New Frigate will be Based on National Security Cutter, First FF(X) to be Built at Ingalls," USNI News, December 19, 2025. 66.
|
|
For further discussion, see CRS Report RL32418, Navy Virginia-Class Submarine Program and AUKUS Submarine (Pillar 1) Project: Background and Issues for Congress, by Ronald O'Rourke. 67.
|
|
CRS Report RL32665, Navy Force Structure and Shipbuilding Plans: Background and Issues for Congress, by Ronald O'Rourke. 68.
|
|
For more on China's naval shipbuilding effort, see CRS Report RL33153, China Naval Modernization: Implications for U.S. Navy Capabilities—Background and Issues for Congress, by Ronald O'Rourke. 69.
|
|
See for example, Howard Altman, "Trump Considering Buying Foreign Ships To Make Up Gap With China," The War Zone, April 11, 2025; Song Sang-ho, "Trump Says U.S. May Buy 'Top-Of-The-Line' Ships from 'Close' Countries," Yonhap, April 11, 2025; Oh Sam-Gwon, "Korean Shipbuilders Gear Up as Trump Suggests U.S. May Buy Warships," Korea JoongAng Daily, April 11, 2025; Tom Sharpe, "Trump Plans to Rebuild the US Navy in Korean Shipyards. We Already Know This Works Well," Telegraph (UK), January 9, 2025; Morgan Phillips, "Trump Threatens to Tap Allies for Military Shipbuilding if US Can't Produce," Fox News, January 7, 2025; Joe Gould, "Trump Hints Pentagon Could Lean on Allies to Build Warships," Politico Pro, January 6, 2025. 70.
|
|
See, for example, Daryl Caudle, "Winning the Long Game: Sustaining Sea Power as Our Enduring Advantage," Defense News, December 18, 2025, in which the author—the Chief of Naval Operations—states (emphasis added): "Until American [ship]yards fully recover from workforce shortages, supply chain fragility and lack of automation, we are exploring responsible cooperation with allied shipbuilders in places like South Korea and Japan to bridge near-term gaps in maintenance, repair and production." See also "U.S. Navy Looks to Korean and Japanese Shipyards to Address Submarine and Destroyer Delays," Army Recognition, November 26, 2025; Kim Hyun-soo, "Arms Agency, U.S. Navy Discuss Cooperation on Naval Shipbuilding, MRO," Yonhap, August 8, 2025. 71.
|
|
See, for example, Jennifer Hlad, "Can Partner Nations Help Solve the Navy's Shipbuilding Woes?" Defense One, November 24, 2025; Maritime Executive, "South Korean Yards Want to Build U.S. Navy Ships in Korea," Maritime Executive, November 16, 2025; Jihoon Yu, "ROK–U.S. Shipbuilding Cooperation Matters for Maritime Power," Real Clear World, December 17, 2025; Juliana Liu, "South Korea Is the Answer to America's Naval Problem," Bloomberg, December 4, 2025; Brad Lendon, Gawon Bae, Yoonjung Seo, Mike Valerio, and Charlie Miller, "US Navy Shipbuilding Is 'a Mess.' South Korean companies Think They Can Help Fix It," CNN, updated October 20, 2025; William Hawkins, "Trade Is Not What Matters Most," U.S. Naval Institute Proceedings, July 2025; Namyeon Kwon, "Don't Miss the Boat: Considerations for U.S.-South Korea Maritime Cooperation," Center for Strategic and International Studies (CSIS), June 12, 2025; Steve Forbes, "Making Our Navy Supreme Again," Forbes, May 27, 2025; Arjun Akwei and Jinwan Park, "Trump Wants More Ships? Korea Stands Ready to Help Build Them," The Hill, May 8, 2025; Miyeon Oh and Michael Cecire, "Why the United States, South Korea, and Japan Must Cooperate on Shipbuilding," RAND, May 6, 2025; "South Korea Offers to Build Five Aegis Destroyers per Year to Help the US Counter China at Sea," Army Recognition, April 11, 2025; Fatima Bahtić, "Facing New Realities amid Rising Costs: Could Future US Navy Warships Be Built at Foreign Shipyards?" NavalToday.com, February 17, 2025; Peter Suciu, "The 21st Century U.S. Navy Might Be Built in South Korea," National Interest, January 9, 2025; Brian T. Di Mascio, "Foreign Shipyards Can Help the U.S. Navy Build Its Fleet," U.S. Naval Institute Proceedings, October 2024; Douglas Robb, "Japan, South Korea and the US Should Mirror AUKUS for Destroyers," Defense News, October 5, 2023; Brad Lendon, "These May Be the World's Best Warships. And They're Not American," CNN, June 3, 2023. 72.
|
|
See, for example, Rebecca Grant, "6 Reasons to Say 'No Thanks' to Building U.S. Navy Warships in South Korea," Real Clear Defense, July 30, 2025; Matthew Paxton, "Outsourcing the US Shipyard Industrial Base Will Outsource American Sovereignty," Breaking Defense, August 5, 2024; Shipbuilders Council of America, "'We Stand Ready' Ad Campaign Shows American Shipbuilders Can Deliver the Fleet of the Future," undated, accessed January 4, 2026. 73.
|
|
For more on programs to build new icebreakers for the U.S. Coast Guard, see CRS Report RL34391, Coast Guard Polar Security Cutter (PSC) and Arctic Security Cutter (ASC) Icebreaker Programs: Background and Issues for Congress, by Ronald O'Rourke. 74.
|
|
For more on these steps, see CRS Report RL32665, Navy Force Structure and Shipbuilding Plans: Background and Issues for Congress, by Ronald O'Rourke. 75.
|
|
For more on the DDG-51 program, see CRS Report RL32109, Navy DDG-51 and DDG-1000 Destroyer Programs: Background and Issues for Congress, by Ronald O'Rourke. 76.
|
|
For more on Navy amphibious shipbuilding programs, see CRS Report R43543, Navy LPD-17 Flight II and LHA Amphibious Ship Programs: Background and Issues for Congress, by Ronald O'Rourke. 77.
|
|
For more on the LSM program, see CRS Report R46374, Navy Medium Landing Ship (LSM) Program: Background and Issues for Congress, by Ronald O'Rourke. 78.
|
|
For more on the Navy's USV acquisition effort, see CRS Report R45757, Navy Large Unmanned Surface and Undersea Vehicles: Background and Issues for Congress, by Ronald O'Rourke. 79.
|
|
See, for example, the version dated December 21, 2022, or earlier versions dating back to the version of May 4, 2020. 80.
|
|
Congressional Budget Office, The Cost of the Navy's New Frigate, October 2020, 11 pp. |
Congressional Budget Office, An Analysis of the Navy's Fiscal Year 2024 Shipbuilding Plan, October 2023, Table 8 on pp. 26-27. CBO states that the new estimated difference between CBO and the Navy of 10% to 20%, as opposed to the 40% difference from CBO's October 2020 report, is due to four factors: (1) an increase by the Navy since October 2020 in its estimated costs for building FFG-62s; (2) a decrease by CBO since October 2020 in its estimated costs for building FFG-62s due to an updated treatment of inflation; (3) a shift by CBO from estimating the cost of ships 1 through 10 in CBO's October 2020 report to ships 5 through 20 in CBO's October 2023 report, which among other things eliminated from the analysis the cost of the lead ship, where there is a fairly substantial difference between the CBO and Navy estimates; and (4) the rounding off in CBO's reports of Navy and CBO estimates to the nearest tenth of a billion dollars per ship, which can shift resulting calculations of the percent difference in cost. (Source: CBO telephone call with CRS, November 14, 2023.) |
||||||||||||||||||||||||||
|
Government Accountability Office, Navy Frigate[:] Unstable Design Has Stalled Construction and Compromised Delivery Schedules, GAO-24-106546, May 2024, p. 17. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 37. |
Government Accountability Office, Navy Frigate[:] Unstable Design Has Stalled Construction and Compromised Delivery Schedules, GAO-24-106546, May 2024, p. 18. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
For example, in 2019, Eastern Shipbuilding Group of Panama City, FL, requested and received contractual relief for Offshore Patrol Cutters (OPCs) that it is building for the Coast Guard. The relief was granted under P.L. 85-804 as amended (50 U.S.C. 1431-1435), a law that authorizes certain federal agencies to provide certain types of extraordinary relief to contractors who are encountering difficulties in the performance of federal contracts or subcontracts relating to national defense. ESG reportedly submitted a request for extraordinary relief on June 30, 2019, after ESG's shipbuilding facilities were damaged by Hurricane Michael, which passed through the Florida panhandle on October 10, 2018. For additional discussion of the OPC program, including the contractual relief provided under P.L. 85-804, see CRS Report R42567, Coast Guard Cutter Procurement: Background and Issues for Congress, by Ronald O'Rourke. See also Congressional Budget Office, The Cost of the Navy's New Frigate, October 2020, p. 11. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
For more on the DDG-51 program, see CRS Report RL32109, Navy DDG-51 and DDG-1000 Destroyer Programs: Background and Issues for Congress, by Ronald O'Rourke. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 40. |
Mallory Shelbourne and Sam LaGrone, "Navy: Constellation Frigate Design Will be Ready in May, Second Yard Could Come in FY 2027," USNI News, December 13, 2024. See also Nick Wilson, "Navy Punting LSM Award Due to Pricier-than-Expected Bids," Defense Daily, December 11, 2024, which reports on both the Navy's Medium Landing Ship (LSM) program and the FFG-62 program. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
For more on the DDG-51 program, see CRS Report RL32109, Navy DDG-51 and DDG-1000 Destroyer Programs: Background and Issues for Congress, by Ronald O'Rourke. For more on Navy amphibious shipbuilding programs, see CRS Report R43543, Navy LPD-17 Flight II and LHA Amphibious Ship Programs: Background and Issues for Congress, by Ronald O'Rourke. For more on the OPC program, see CRS Report R42567, Coast Guard Cutter Procurement: Background and Issues for Congress, by Ronald O'Rourke. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
See page 11 of the April 19, 2019, update of this CRS report. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
For more on China's naval |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
See, for example, Megan Eckstein and Joe Gould, "Lawmakers Crunching the Numbers on Potential Surface Navy Additions to FY22 Spending Plan," Defense News, June 17, 2021; Mallory Shelbourne, "Lawmakers Probe Navy's Plan to Decommission Cruisers, Navy Says Cuts Will Save $5B Across FYDP," USNI News, June 17 (updated June 18), 2021; Megan Eckstein, "Lawmakers Are Worried About the US Navy's Spending Plan and a Near-Term China Threat," Defense News, June 15, 2021; Mallory Shelbourne, "CNO Gilday: Flat or Declining Navy Budgets 'Will Definitely Shrink' the Fleet," USNI News, June 15, 2021; Blake Herzinger, "The Budget (and Fleet) That Might Have Been," War on the Rocks, June 10, 2021; David B. Larter, "As the US Navy Scrambles to Field More Missiles in Asia, a Tough Decision Looms for Aging Cruisers," Defense News, April 12, 2021. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
For more on the LUSV program, see CRS Report R45757, Navy Large Unmanned Surface and Undersea Vehicles: Background and Issues for Congress, by Ronald O'Rourke. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Navy information paper entitled "FFG(X) Cost to Grow to 48 cell VLS," dated May 14, 2019, received from Navy Office of Legislative Affairs on June 14, 2019. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
For additional discussion, see Joseph Trevithick and Tyler Rogoway, "Does The Navy's New Constellation Class Frigate Have Enough Vertical Launch Cells?" The Warzone, January 31, 2024. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
93DOT&E's January 2025 report for FY2024 does not include a section on the FFG-62 program. |
Government Accountability Office, Weapon Systems Annual Assessment[:] DOD Is Not Yet Well-Positioned to Field Systems with Speed, GAO-24-106831, June 2024, p. 138. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Director, Operational Test & Evaluation, FY 2023 Annual Report, January 2024, pp. 200-201. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 50. |
Audrey Decker, "Frigate Construction Pushed Back from April Target Start Date," Inside Defense, April 13, 2022. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 51. |
Justin Katz, "Navy to Swap Sonar on New Frigate Following Years of Struggles with Testing," Breaking Defense, March 31, 2022. See also Megan Eckstein, "US Navy to Terminate DART Sonar Development with Raytheon," Defense News, March 31, 2022; Rich Abott, "Navy Cites Reasons For Ditching DART Sonar For LCS, Frigate," Defense Daily, September 1, 2022. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 52. |
Justin Katz, "For Navy's New Frigate, Design Changes Carry Risks and Rewards," Breaking Defense, January 24, 2022. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Government Accountability Office, Guide Missile Frigate[:] Navy Has Taken Steps to Reduce Acquisition Risk, but Opportunities Exist to Improve Knowledge for Decision Makers, GAO-19-512, August 2019, summary page. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
See CRS Report RL32665, Navy Force Structure and Shipbuilding Plans: Background and Issues for Congress, by Ronald O'Rourke. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
See Government Accountability Office, Navy Shipbuilding[:] Past Performance Provides Valuable Lessons for Future Investments, GAO-18-238SP, June 2018, p. 21. A graphic on page 21 shows a GAO finding that the government was financially responsible for shipbuilder deficiencies in 96% of the cases examined by GAO, and that the shipbuilder was financially responsible for shipbuilder deficiencies in 4% of the cases. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
It can also be noted that the country's two largest builders of Navy ships—General Dynamics (GD) and Huntington Ingalls Industries (HII)—derive about 60% and 96%, respectively, of their revenues from U.S. government work. (See General Dynamics, 2016 Annual Report, page 9 of Form 10-K [PDF page 15 of 88] and Huntington Ingalls Industries, 2016 Annual Report, page 5 of Form 10-K [PDF page 19 of 134].) These two shipbuilders operate the only U.S. shipyards currently capable of building several major types of Navy ships, including submarines, aircraft carriers, large surface combatants, and amphibious ships. Thus, even if a warranty in a shipbuilding contract with one of these firms were to somehow mean that the government did not have pay under the terms of that contract—either up front or later on—for fixing problems with earlier work done under that contract, there would still be a question as to whether the government would nevertheless wind up eventually paying much of that cost as part of the price of one or more future contracts the government may have that firm. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Department of Defense, Department of Defense Warranty Guide, Version 1.0, September 2009, accessed July 13, 2017, at https://www.acq.osd.mil/dpap/pdi/uid/docs/departmentofdefensewarrantyguide[1].doc. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Government Accountability Office, Guide Missile Frigate[:] Navy Has Taken Steps to Reduce Acquisition Risk, but Opportunities Exist to Improve Knowledge for Decision Makers, GAO-19-512, August 2019 (revised September 5, 2019 to include an omitted page in the report section, [and] comments from the Department of Defense), pp. 44-45. |