Russian submarine Smolensk
1990 Oscar-II-class submarine
K-410 Smolensk is an Oscar-class submarine in the Russian Navy.
Development and design
The design assignment was issued in 1969. The development of Project 949 was a new stage in the development of APRC-class submarines, which, in accordance with the concept of asymmetric response, were tasked with countering aircraft carrier strike formations. The new missile submarines were to replace the submarines of Projects 659 and 675 and in accordance with the terms of reference surpassed them in all basic parameters - could launch missiles from both surface and underwater position, had less noise, higher underwater speed, three times higher ammunition, missiles with radically improved combat capabilities. Project 949 became the pinnacle and the end of the development of highly specialized submarines (aircraft carrier killers).
In December 2011, they became known that the Rubin Central Design Bureau had developed a modernization project. It is planned to replace the P-700 missiles with the more modern P-800 Oniks missiles from the Caliber family. Modification of launch containers is planned, without alteration of the hull. The modernization of the nuclear submarine of the Northern Fleet will be carried out at the Zvezdochka CS, and the Zvezda shipyard.
The design is double-hulled, with a distance between a light and durable body of 3.5 meters, which provides a significant buoyancy margin, up to 30 %, and provides additional protection against underwater explosions.
The public source identifies “Russian submarine Smolensk” as 1990 Oscar-II-class submarine. This brief keeps that definition visible, then builds a research path around Russian, submarine and Smolensk.
Why this record matters
A short description can identify a subject without explaining its stakes. For “Russian submarine Smolensk”, the useful work is to connect “1990 Oscar-II-class submarine” to the records capable of establishing context and consequence.
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 Dec 16, 2025. The linked authority identifier is Q3811864. None of the 0 selected statements returned an explicit reference. The first chronological checks are 1969 and 2011.
Overview language is designed for orientation and should not be treated as a substitute for the evidence cited beneath it. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. 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 “Russian submarine Smolensk”, its source revision and the description used here.
- Expand the search: follow Russian submarine Smolensk primary sources, Russian submarine Smolensk archive and Russian 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 “Russian submarine Smolensk”?
- What terminology or title could unlock a more precise catalogue search?
- Which institution is responsible for the underlying evidence?
Search terms from this dossier
This entry incorporates text from “Russian submarine Smolensk” 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.