Sub was on a secret mission
Whereabouts of 18 personnel on board still unclear; 16 working outside rescued
♦ Accident happened while loading missiles in the front tube of Sindhurakshak
♦ Missile ripped through sub and hit security wall in the Dockyard, destroying it
As Deputy Chief Fire Officer P S Rahangdale left the Radio Club late on Tuesday night after a gym session, it had seemed like the end of a perfect day off. But just moments later, when he heard a deafening blast and saw a ball of fire rising in the dark sky over the Naval Dockyard, he knew his day had just begun. It was 11.35 pm.
Rahangdale first called the fire control and raised a no. 2 emergency call. His second call was to his boss, Chief Fire Officer Suhas Joshi. He told Joshi that he was reporting back to work and was taking charge of what seemed like a major fire in Naval Dockyard.
Rahangdale's instinct was spot on - it was a major blaze. Two blasts had ripped through a submarine -- INS Sindhurakshak -- at the Naval Dockyard's high-security South Breakwater bay.
The intensity of the blasts was such that it had blown the vessel's nose and sunk it, trapping three commissioned officers and 15 sailors.
Later in the day, Defence Minister A K Antony, who left for Mumbai soon after making a statement in Parliament, would describe the incident as one of the "worst tragedies" Indian defence forces have faced in a long time.
By the time Rahangdale reached the Lion Gate in Colaba, fire engines had reached the spot. What he saw inside, was shocking even for the hardened fireman. Navy vessels which were always docked in a tight order were in disarray and personnel were screaming and running in all directions, trying to avoid the massive flames and to rescue trapped colleagues at the same time. It seemed like a war zone.
First mission
When the blasts took place, Sindhurakshak was being armed for a secret mission, its first after the vessel was retro-fitted in Russia. The three officers and 15 men inside, however, had no idea what the mission was. As per the established naval protocol, the commanding officer would have been handed over a sealed envelope a few hours before the submarine's departure, detailing where he was to head and what the target was.
While the navy remained tight-lipped through Wednesday, Mumbai Mirror has information that things went wrong when the sailors were fitting Klub-class surface-to-air missiles with capability to hit targets within 300 km range. They had to fit 15 missiles in two pods - one carrying eight and the other seven. Sources said the installation of eight missiles was complete, but when the other seven missiles were being fitted, either a small fire or a short-circuit occurred and triggered one of the missiles. The missile went right through the vessel's nose and slammed into the dockyard's security wall, destroying it completely. Within seconds, another missile also caught fire and blew up inside the vessel, causing a massive fire and knocking off a part of the vessel's roof.
Aformer naval officer, who did not wish to be identified, said Klub category missiles are extremely sensitive. "Any mistake in positioning these missiles can trigger a fire and an explosion." Since the missiles pods are located in the front chamber of the submarine, all three officers and fifteen men were present in this small space, involved in the fitting of the ordnance.
While the Navy till late Wednesday evening did not release any names, sources said three officers present in the vessel were - Lieutenant Commander Nikhilesh Pal, Lieutenant Commander Vinay H, and Lieutenant Commander Aloke Kumar. The submarine's commanding officer Commander Rajesh Ramkumar was to join them a few hours before they embarked on the mission.
Sixteen sailors, who were outside the submarine on guard duty, managed to escape by jumping into the sea after the first blast. They were treated at INHS Asvini for minor injuries.
An expert said the damage would have been manifold more had the other missiles in the vessel been triggered too. "The South Breakwater bay had at least three more submarines, several frigates and ships anchored near Sindhurakshak. I would assume the sea water that entered after the submarine's nose and roof was blown off, rendered the rest of the ordnance ineffective," he added.
According to Rahangdale, INS Sindhuratan parked next to Sindhurakshak was on fire when he arrived. "We doused the fire and created a water wall between Sindhuratna and Sindhurakshak, allowing sailors to move the former away."
Eventually, commanders of all ships, frigates and ships were summoned and the entire South Breakwater bay was cleared. It took the city fire brigade and the navy's own fire engines three hours to quell the flames engulfing Sindhurakshak.
Nearly forty divers were summoned from naval centres across the western command and a rescue operation was launched in the night itself. The divers, however, struggled to enter several sections of the vessel as the hatches were fused with the metal around them because of excessive heat.
At the time of going to press, there was no information on whether the divers had managed to enter the submarine.
Since there was also a suspicion of sabotage, an alert was raised and the sea off the Naval dockyard was cleared of all vessels. Even commercial ferries plying tourists from the Gateway were asked to suspend operations temporarily.
Addressing the media after the defence minister's brief statement, Chief of Naval Staff Admiral D K Joshi refused to comment on what could have caused the mishap.
He also refused to speculate on the fate of the 18 men trapped in the gutted submarine. "We hope for the best and prepare for the worst," is all he would say.
Sub was on a secret mission - Mumbai Mirror