Genuine story of submarine PNS Ghazi and the secret behind its sinking (untold real mistary story)

in realstory •  7 years ago 

Screenshot_20180607_120946.png
Thinking back

The sinking of Pakistani submarine PNS Ghazi with 90 men on board in the 1971 Indo-Pak war is viewed as one of the high purposes of India's first-since forever decided military triumph.

Presently with extremely popular Bollywood maker/chief Karan Johar discharging the main look notice of his studio's new motion picture The Ghazi Attack, we figured it may be a decent time to review some history.
Screenshot_20180607_121032.png
The beginnings

In 1971, Indian Navy's Eastern Naval Command under the administration of INS Vikrant (in pic), had viably made a Naval barricade which totally secluded East-Pakistan in Bay of Bengal.

Screenshot_20180607_121048.png
Enter PNS Ghazi

Disappointed with the Naval Blockade, Pakistan chose to send the best submarine in its stock - PNS Ghazi.

PNS Ghazi was appointed with a two-overlap objective. The essential objective was to discover and sink INS Vikrant and the second one was to lay mines on India's Eastern seaboard with or without achieving the essential target.

Screenshot_20180607_121110.png
Ghazi's last voyage

Without PNS Ghazi, Pakistan naval force couldn't meddle with Vikrant's activities in East Pakistan. It was to a great degree hazardous of sending a maturing submarine totally around the subcontinent to assault the foe's lead in it's home waters. Furthermore, Ghazi was by then encountering customary hardware disappointments and support offices at Chittagong were poor.

Overruling these complaints, PNS Ghazi unobtrusively cruised out of the Karachi Harbor on November 14, 1971.

Screenshot_20180607_121130.png
The masterplan

Having cruised the armada away to security, Krishnan reserved in INS Rajput, a maturing WWII destroyer that was really sent to Vishakapatnam for decommissioning. INS Rajput was to put on a show to be INS Vikrant, cruise out of the Vizag port and produce substantial remote activity.

The Indian Navy purposefully broke security by making an unclassified flag as a private Telegram purportedly from one of Vikrant's mariner's getting some information about the welfare of his mom who was "genuinely sick".

Screenshot_20180607_121150.png
Ghazi takes the draw

Ghazi began searching for Vikrant on November 23 off Madras however didn't know that she was 10 days past the point of no return and the Vikrant was quite close to the Andaman islands.

Bad habit Admiral Krishnan sent for Lt.Inder Singh, the Commanding officer of the Rajput for point by point preparation and disclosed to him that a Pakistani submarine had been located off Ceylon and was sure beyond a shadow of a doubt that the submarine would be some place around Madras/Vishakaptanm. He made it clear that once Rajput had finished refueling, she should leave the harbor with every single navigational guide turned off.

Screenshot_20180607_121244.png
The last long periods of Ghazi

INS Rajput cruised out on 2 December and came back to Vishakapatnam on 3 December and again cruised out with a pilot on board, just before the midnight of 3/4 December and on clearing the harbor, continued along the thin passage channel. At the point when the ship was most of the way in the channel, it abruptly jumped out at the Captain that "Imagine a scenario where the Pakistani submarine was holding up outside the harbor and torpedoes us as we land the pilot who was ready, at the Outer Channel Buoy?" He quickly requested to stop motors and landed the pilot.

Screenshot_20180607_121300.png
The hit

In the interim, Ghazi being not able find INS Vikrant around Vishakapatnam continued laying mines the evening of third December when Pakistan flagged the initiation of dangers. Ghazi came up to periscope profundity to build up her naviagtional position which was made extremely troublesome because of the power outage and turning off of every single navigational guide.

Rajput gradually expanded speed to greatest when it achieved the Outer channel float. Now of time, Ghazi saw or heard a destroyer moving toward her at rapid at a relatively proportional course and went into a precarious jump and in the meantime put her rudder hard finished keeping in mind the end goal to escape offshore.

Screenshot_20180607_121316.png
Presently comes the contention

The Captain of Destroyer Rajput saw the aggravation of water caused by the rushed jump and propelled two profundity charges at that position. The charges struck the submarine that was at that point in a lofty plunge making Ghazi hit seabed hard when it bottomed.

The fire spread to where the Mines and torpedoes were put away and these blew the forward structure outward. It is additionally conceivable that the explosion of the charges set off a mine that was being kept in a prepared state close to the torpedo tube. This was Indian Navy's rendition.

Screenshot_20180607_121332.png
Pakistan's version

As the lights shorewards were passed out, PNS Ghazi may have misconceived her position and turned around into her own particular minefield around midnight; around 10-15 minutes before the INS Rajput profundity charging. Along these lines, it was the inadvertent explosion of its own mines that devastated the Ghazi and not INS Rajput's profundity charges.

(Illustrative picture)
Screenshot_20180607_121349.png
No real records yet

Numerous speculations approached since and it happened that maritime specialists likewise devastated records of the sinking of Ghazi.

Whatever caused the Ghazi to detonate, it was by and by, the Indian Navy's creativity and beguiling arranging that made the submarine a take after a preset way which finished in a watery grave for its mariners on board.

Authors get paid when people like you upvote their post.
If you enjoyed what you read here, create your account today and start earning FREE STEEM!
Sort Order:  

Source
There is reasonable evidence that this article has been spun, rewritten, or reworded. Repeatedly posting such content is considered spam.

Spam is discouraged by the community, and may result in action from the cheetah bot.

More information and tips on sharing content.

If you believe this comment is in error, please contact us in #disputes on Discord

  ·  7 years ago Reveal Comment