Sarancha-class missile boat

The Sarancha class is the NATO reporting name for a hydrofoil missile boat built for the Soviet Navy. The Soviet designation was Project 1240 Uragan (Серия 1240 Ураган- Hurricane).

Class overview
Builders: Almaz, Leningrad
Operators:  Soviet Navy
Built: 1973
In commission: 1977-1990
Completed: 1
Lost: 1
General characteristics
Type: hydrofoil missile boat
Displacement: 280 tons standard, 320 tons full load
Length: 53.6 m
Beam: 31.31 m
Draught: 2.6 M (7.3 m with foils extended)
Propulsion: 4 shafts, 2 gas turbines 30,000 hp (diesel - GT) 2 GTD M-10 (based on NK-12) 2 diesel M-401 (DRA-211) little cruise 3 gas turbogenerators GTG-100 2 diesel generators DG-100
Speed: 58 kn (107 km/h)
Range: 700 nmi (1,300 km)
Complement: 40
Sensors and
processing systems:
Radar: Band Stand, Pop Group, Bass Tilt
Armament: 4 x SS-N-9 anti ship missiles
1 SA-N-4 SAM system (20 re-load missiles)
1- 30mm AK-630 gun system

Design

The boat was a very complex design. Unlike previous Soviet hydrofoil boats the Project 1240 had fully submerged foils with propellers mounted on the after set of foils. The boat achieved a speed of 58 knots (107 km/h) and had a heavy armament. It was deemed too large, complex and expensive for series production and only a prototype boat was built.

Missile boat MRK-5

The MRK-5 (МРК-5) was laid down at the Petrovski plant in Leningrad in 1973 and was on trials until 1977. In 1979, she was transferred to the Black Sea Fleet via Russian inland waterways. She was based in Sevastopol until 1990, when she was decommissioned. In 1992, she was damaged by fire and sunk in shallow water. The wreck was raised and scrapped.

gollark: I can't get around that.
gollark: No, it does.
gollark: - PotatOS uses a single global process manager instance for nested potatOS instances. The ID is incremented by 1 each time a new process starts.- But each nested instance runs its own set of processes, because I never made them not do that and because without *some* of them things would break.- PotatOS has a "fast reboot" feature where, if you reboot in the sandbox, instead of *actually* rebooting the computer it just reinitializes the sandbox a bit.- For various reasons (resource exhaustion I think, mostly), if you nest it, stuff crashes a lot. This might end up causing some of the nested instances to reboot.- When they reboot, some of their processes many stay online because I never added sufficient protections against that because it never really came up.- The slowness is because each event goes to about 200 processes which then maybe do things.
gollark: WRONG!
gollark: It doesn't reuse already allocated IDs.

See also

References

Notes

    Bibliography

    Gardiner, Robert (ed.). Conway's All the World's Fighting Ships 1947–1995. London: Conway Maritime. ISBN 0851776051. OCLC 34284130.CS1 maint: extra text: authors list (link) Also published as Gardiner, Robert; Chumbley, Stephen; Budzbon, Przemysław. Conway's All the World's Fighting Ships 1947–1995. Annapolis, MD: Naval Institute Press. ISBN 1557501327. OCLC 34267261.

    This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.