Halifax-class frigate
1988 class of Canadian frigates
The Halifax-class frigates are a class of multi-role patrol frigates operated by the Royal Canadian Navy since 1992. The class is the outcome of the Canadian Patrol Frigate Project, which originated in the mid-1970s. HMCS Halifax was the first of twelve Canadian designed and built vessels which combine traditional anti-submarine capabilities with systems to deal with surface and air threats as well. The ships are named after Canadian provincial capitals (St. John's, Halifax, Charlottetown, Fredericton, Québec City, Toronto, Winnipeg, and Regina), the capital of Canada, and the major cities Calgary, Montreal, and Vancouver.
In 2007, the Government of Canada announced a planned refit of the Halifax class which is known as the Halifax Class Modernization Project (HCMP) of which the Frigate Equipment Life Extension (FELEX) project is a part. In November 2008, a Lockheed Martin Canada-led team including Saab AB, Elisra, IBM Canada, CAE Professional Services, L-3 Electronic Systems and xwave, was awarded the contract. The construction phase of the program was completed in November 2016. As of May 2021, the Halifax-class modernization program was being closed out, but full operational capacity was reached on 31 January 2018.
In October 2011 the Canadian government launched the National Shipbuilding Procurement Strategy which aims to replace the Halifax class, as well as the capabilities of the Iroquois-class destroyers, with up to 15 new River-class destroyers.
Begin with the source’s own compact description: “Halifax-class frigate” is 1988 class of Canadian frigates. The dossier treats that line as a proposition to test through Halifax-class, frigate and class, not as a finished interpretation.
Why this record matters
The phrase “1988 class of Canadian frigates” supplies a clear boundary for inquiry. It also exposes the unanswered questions: who defined that boundary, when it became stable and which sources sit outside it.
Vocabulary and entity names are the principal evidence signals here, because they determine the precision of every later search. The source revision retrieved here is dated Sep 9, 2026. The linked authority identifier is Q177552. None of the 1 selected statements returned an explicit reference. The first chronological checks are 1992, 2007, 2008 and 2016.
The absence of detail may reflect summary conventions rather than a lack of surviving documentation. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Halifax-class frigate”, its source revision and the description used here.
- Expand the search: follow Halifax-class frigate primary sources, Halifax-class frigate archive and Halifax-class research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Halifax-class frigate”?
- What terminology or title could unlock a more precise catalogue search?
- Which cited source is closest to the event, object or claim?
Search terms from this dossier
This entry incorporates text from “Halifax-class frigate” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.