Chapter 326: The Weight of Steel
February 1978Nikolayev Black Sea Shipyard, Ukrainian SSR; INS Viraat in transit through the Suez Canal; Visakhapatnam; and the specific, quiet, categorically denied fact of an Indian aircraft carrier making its way through international waters under the flag of a country that had no aircraft carriers
The formal handover ceremony at the Nikolayev Black Sea Shipyard lasted exactly forty-three minutes.
This brevity was highly deliberate. The Soviet Navy's rigid protocol for the formal transfer of a major combatant to a foreign power usually demanded a theatrical, drawn-out affair—the grand flag ceremonies, the endless political readings, and the heavy, choreographed Soviet naval traditions of the commissioning moment. Rear Admiral P.K. Sharma, the man tasked with receiving the leviathan on behalf of the Indian Navy, had been exhaustively briefed on this protocol. He had a carefully vetted, diplomatic response speech folded in his heavy wool jacket pocket.
He never took it out.
The Soviet yard director, Yuriy Petrenko—a hardened, pragmatic man who had been ruthlessly running Nikolayev's major military construction programs since 1971—possessed the specific, paranoid quality of a Soviet industrial manager who was brilliant at building machines and extremely careful about what he said in the presence of anyone outside his trusted inner circle. Petrenko had suggested, in a hushed meeting the previous evening, that the ceremony be conducted with ruthless efficiency.
*"The political officers expect a forty-five-minute spectacle, Admiral,"* Petrenko had said, his careful Russian translated by an interpreter who understood exactly what was being communicated between the lines. *"But the Black Sea wind is unforgiving, and my men have other keels to lay. Let us be comfortably efficient."*
Sharma had perfectly understood the unspoken suggestion. Take the ship quickly, before Moscow's bureaucracy can find a reason to linger.
The ceremony ran forty-three minutes. The crisp Indian tricolor was raised. The heavy crimson flag of the Soviet Union—which had been flying proudly from the ship's massive mast since it was three weeks from completion—was lowered for the final time. The hundreds of Soviet shipyard workers lining the freezing quayside simply turned their backs and marched silently back to their sprawling industrial facilities. The colossal machine of war they had forged out of raw steel was no longer their ship. Their work was done.
Sharma stood alone on the sprawling flight deck of INS Viraat and looked up at the sky above Nikolayev in February 1978.
The sky was grey, but it was grey in the specific, oppressive way that only the Black Sea's winter sky could manage. It wasn't the uniform, washing grey of rain, nor the bruised, violent dark of an impending storm. It was the pale, skeletal grey of a sky suspended above a massive body of freezing water in the dead of winter—a sky just bright enough to cast long, harsh shadows, and cold enough that every breath Sharma took plumed into thick, visible vapor before instantly freezing.
He was fifty-one years old. He had served in the Indian Navy for twenty-nine grueling years. He had walked the decks of every single class of ship the Indian fleet operated, and he had commanded three distinct warships in his career.
But he had never stood on a flight deck of this staggering, terrifying magnitude.
The flight deck of INS Viraat was a sprawling plateau of reinforced non-skid steel, measuring exactly 311 meters long.
He could walk from one end to the other in approximately three minutes at a brisk, disciplined pace. He had done exactly this, twice, the previous morning when the Indian delegation had been permitted on board for the final, unsparing inspection before the handover. He had walked from the bow, staring down at the massive, recessed tracks of the twin steam catapults—the brutal, high-pressure, steam-driven slingshots engineered to violently hurl heavily loaded fighter jets from a standstill to takeoff velocity in a matter of seconds. From there, he had paced all the way to the aft section, where the heavy arresting wires crossed the deck in the exact, unforgiving geometry required to catch incoming aircraft screaming in at high speed, violently hauling them to a controlled, smoking stop within a hundred meters.
He had walked that massive length twice. The second time, he had walked it much more slowly, his boots thudding against the steel, because he was deeply internalizing exactly what this deck represented. He had not stopped thinking about it since.
INS Viraat had been painstakingly forged at the Nikolayev Black Sea Shipyard—formally designated the Order of Lenin Nosenko Shipbuilding Plant. By any metric of sheer industrial tonnage, the length of its dry docks, or the staggering volume of military steel it was currently cutting, it was the largest, most formidable shipyard on the planet.
But the ship had not been built under a standard export contract. It had been constructed under a highly classified, unprecedented agreement signed in March 1975—an agreement whose true architectural depth was not publicly known to anyone outside a specific, terrifyingly small circle of men in New Delhi and Moscow.
The agreement was the ultimate, lethal evolution of the India-Soviet defense cooperation that had existed since the early 1960s. In the bloody aftermath of the 1971 war, that relationship had expanded into a category of ruthless, transactional synergy that vastly exceeded what either party had ever anticipated. The 1971 war had violently demonstrated to the globe exactly what the specific combination of indigenous Indian military brilliance and heavy Soviet supply could produce. Both capitals had drawn specific, binding conclusions from the slaughter.
The Soviet conclusion was that India was an incredibly rare, highly credible partner for serious defense cooperation. India was not an incompetent proxy that merely received expensive equipment and proceeded to lose wars. India was the kind of partner that received Soviet equipment, reverse-engineered it, aggressively improved its lethal margins, and won decisively.
The Indian conclusion was that the Soviet Union possessed the massive, heavy-industrial capability to provide exactly what the Indian Navy desperately needed to fulfill its new strategic mandate. India no longer wanted to merely guard its coastlines; it required a genuine, dominant blue-water force capable of projecting absolute, unyielding maritime hegemony across the entire expanse of the Indian Ocean.
The specific, glaring gap between what the Indian Navy was in 1971, and what India's new superpower status absolutely required it to become, was the fleet aircraft carrier.
They did not need a small carrier. They did not need another INS Vikrant*—the aging, 19,500-tonne British Centaur-class carrier that India had acquired in 1961. The *Vikrant had served heroically through the 1971 war, but it had done so in the specific, highly limited capacity of a platform whose small air wing and severe vulnerability in contested waters were absolute constraints on what the admirals could actually ask it to do. The Vikrant was a brave, useful ship. It was also absolutely not what the Naval War College's post-1971 strategic review demanded.
What the Republic of India required—in the unsparing, exhaustive assessment of the Naval War College—was a supercarrier. A massive, floating fortress capable of operating heavily loaded, fixed-wing strike aircraft from a position of absolute power projection, possessing the survivability, the steam catapults, and the massive air wing size necessary to violently control the sea space for a radius sufficient to protect India's sprawling maritime interests.
The Naval assessment specifically, unapologetically demanded: 70,000 tonnes displacement. 30 to 40 advanced strike aircraft. Twin steam catapults. Speed sufficient to outrun a submarine and operate with a fast task group. Survivability and armor standards consistent with apocalyptic modern naval warfare.
The Soviet Union, at the exact time the Indian assessment was produced, possessed the fierce ambition to build exactly this class of ship. It was designated Project Orel—a massive, catapult-equipped supercarrier designed to finally challenge the American Nimitz-class behemoths.
But ambition in Moscow was currently bleeding to death against reality. The Soviet naval high command was choking on the staggering, crippling financial realities of supercarrier research and development. They had the theoretical blueprints, but they lacked the liquid capital to perfect the steam catapults and pour the steel without bankrupting their other fleet programs.
That was the exact moment Karan Shergill had stepped into the geopolitical void.
The conversation about whether the Soviet Union would build a supercarrier for India did not begin in diplomatic backchannels. It began in a highly secure, smoke-filled room in 1973, in a direct, ruthless negotiation between Karan Shergill and the highest echelon of the Soviet Navy.
Karan had looked at the Soviet Admirals, men who were desperate to see Project Orel survive the Kremlin's budget cuts, and he had offered them an impossible, golden lifeline.
*"We know you cannot afford to finish the Orel project alone,"* Karan had told them, leveraging the vast, rapidly expanding wealth of the Indian state. *"You have the shipyards, and you have the metallurgical genius. But you are bleeding cash on the catapult research and the hull scaling. India will cure that hemorrhage. We will heavily, directly fund the completion of Project Orel."*
The Soviet delegation had been stunned. An Indian state Chief Minister offering to underwrite a highly classified Soviet supercarrier program was an unprecedented breach of Cold War norms.
*"But we do not write blank checks,"* Karan had continued, his voice dropping into the cold, transactional register that had built his industrial empire. *"In exchange for India's massive capital injection, the Nikolayev shipyard will simultaneously build the second hull of the Orel class specifically for the Indian Navy. And the true price of our capital is not just the ship. It is the math. The Soviet Union will execute a complete, unrestricted technology transfer. You will hand over every single structural blueprint, every metallurgical specification, and the complete engineering schematics for the steam catapults. We buy your ship today, so that we can build our own ships tomorrow."*
It was an offer the cash-starved Soviet naval command simply could not refuse. The agreement concluded, in its specific, highly classified terms, in March 1975.
It was, by an astronomical margin, the largest single defense procurement the Republic of India had ever executed.
The specific financial terms were brilliantly structured by Karan to completely avoid the devastating foreign exchange implications that a simple, multi-billion-dollar cash purchase would have triggered in the international markets. Instead, the financial architecture utilized the complex, highly insulated rupee-ruble trade settlements that the Indo-Soviet economic relationship had perfected since the late 1960s.
In practical, physical terms, India was paying for the massive hull of INS Viraat, and the priceless blueprints of Project Orel, directly with oil.
Specifically, the procurement was funded by a dedicated, heavily guarded portion of the massive Andaman basin petroleum revenue. That specific offshore crude had been silently allocated, deep within the classified infrastructure of the national security budget, exclusively to the carrier programme's financing. The millions of barrels of heavy crude that pumped out of the Andaman Sea floor went—through a flawless mechanism of internal accounting that the Finance Ministry had developed under Karan's direction with the Reserve Bank—directly into the Soviet rupee credits that paid the Nikolayev shipyard's massive contract obligations.
The Andaman Sea's oil was literally buying the colossal steel leviathan that would patrol the Andaman Sea.
The sheer, self-sustaining poetry of that geometry had pleased Karan considerably when he had first drafted the financial structure.
The 70,000-tonne leviathan that was now INS Viraat was not a conventional, oil-burning warship. It was a nuclear-powered apex predator.
In the original, bankrupt timeline of the Soviet Union, Project Orel might have been downgraded to steam turbines to save the bleeding Soviet economy. But with Karan Shergill's bottomless industrial capital aggressively underwriting the Nikolayev shipyard, the Indian Navy had demanded the ultimate, uncompromising prize. INS Viraat was powered by twin, highly advanced pressurized water reactors (PWRs) generating a staggering 200,000 shaft horsepower. It possessed a flank speed well in excess of thirty knots, and an operational endurance limited only by the psychological endurance of her crew and the depletion of her aviation ordnance. She could circle the Indian Ocean indefinitely without ever needing to see a refueling tanker.
This terrifying new reality required a completely new breed of sailor. That was the exact reason why one hundred elite Indian naval engineers had just spent fourteen grueling months at the highly classified Sevmash northern shipyard.
Sevmash—a freezing, heavily guarded fortress located in Severodvinsk on the brutal Arctic coast of the Soviet Union—was a completely different facility from Nikolayev. It was the secretive, radioactive womb where the Soviet Navy exclusively built its nuclear-powered submarines and advanced atomic surface combatants.
The Indian engineers had not been sent to the Arctic merely as academic observers for some distant, theoretical domestic carrier program. They had been sent to learn exactly how to tame the nuclear fire that powered the massive hull currently floating in the Black Sea, and to aggressively steal the institutional knowledge required to build India's next generation of domestic atomic carriers today, rather than waiting for 1995.
They had deployed under a highly classified bilateral agreement designated the Soviet-Indian Nuclear Propulsion Technology Exchange Programme. It was a polite, bureaucratic title that radically, deliberately understated what the exchange actually meant.
What it actually meant was this: One hundred elite Indian naval engineers had spent over a year locked inside the world's most advanced nuclear-powered submarine manufacturing facility, painstakingly dissecting the specific, lethal engineering of how you safely commanded a massive vessel whose heartbeat was a controlled atomic chain reaction. They learned the brutal, unforgiving physics of radiation shielding at sea. They studied the claustrophobic requirements of naval reactor design for highly compact installation. And they memorized the terrifying maintenance protocols for a critical system that could never, ever be fully shut down, because the ship's very survival in combat depended entirely on that power remaining unbroken.
They had not physically turned wrenches at Sevmash. They had watched, interrogated, and absorbed. Within the strict, paranoid limits of what their Soviet handlers had been explicitly authorized by the KGB to share, they had received answers. But more importantly, they had been shown just enough of the underlying nuclear architecture to realize exactly what the next classified question was, and the question after that. They rapidly developed the highly specific, restricted technical vocabulary that allowed them to secretly read between the lines of the literature, reverse-engineer the thermodynamic calculations, and prepare to independently operate the massive reactors that would power Indian maritime hegemony.
They had returned to India in December 1977.
Now, in February 1978, they were standing by in Visakhapatnam, aggressively preparing for the arrival of their nuclear behemoth. They carried fourteen months of priceless, highly classified atomic knowledge securely locked in their heads—knowledge that did not officially exist in any published document, forming the absolute, radioactive foundation upon which India's entire future naval supremacy would be built.
Commander Arvind Kumar Nair had led the infiltration team to Sevmash.
He was thirty-eight years old, a native of Cochin, and a brilliant naval engineer officer who had spent twelve years mastering complex propulsion systems aboard Indian Navy vessels. He had been hand-selected to lead the Sevmash mission due to a rare, highly lethal combination of traits: his flawless propulsion engineering background, his fluent, accentless Russian language proficiency—honed during a two-year government scholarship at Moscow's prestigious Bauman Technical University in the late 1960s—and a specific, terrifying quality noted by every commanding officer in his service record.
Nair was not just a mechanic; he was a man who deeply, intuitively understood not just what a piece of complex machinery did, but the foundational, theoretical physics of why it had been designed that way in the first place.
This unique quality—the aggressive comprehension of design intent, rather than mere operational function—was the exact weapon the Sevmash infiltration required. You could teach a competent sailor the operational function of a reactor control panel in six months. But successfully reverse-engineering the design intent of Soviet nuclear shielding required the kind of delicate, deeply probing, highly specific conversations that Nair excelled at.
Nair had ruthlessly organized his 100-engineer team into five specialized strike groups of twenty. Each group was surgically assigned to a specific, critical domain of nuclear propulsion: core reactor design and naval integration, primary radioactive coolant systems, secondary steam generation turbines, high-voltage electrical distribution, and catastrophic emergency fail-safe systems. This strict division of labor had been carefully, diplomatically negotiated with the Soviet liaison officers who managed the programme, who naturally possessed their own strict KGB directives about what the Indian visitors were permitted to learn, and in what sanitized order.
The primary Soviet liaison was a man named Vasily Kozlov. He was a senior, brilliant engineer at Sevmash who had spent fifteen years managing foreign engineering delegations—mostly from the Soviet Union's subservient Warsaw Pact allies, briefly from Egypt in the 1970s, and now, the Indians. Kozlov was a careful, deeply methodical man. He knew perfectly well that the strict authorization for every single piece of information he shared had been agonizingly debated by men in the Kremlin whom he would never meet. His job was to implement the authorization to the letter, not to interpret it.
He had managed the 100 Indian engineers with the specific, paranoid professional attention of a man who was simultaneously generous with what he had been authorized to share, and brutally unyielding about the boundary of that authorization.
Nair had outwardly respected that boundary with flawless discipline. But he had also mastered the dark art of the edge. At every single opportunity that the strict boundary permitted, Nair asked the specific, highly technical question that hovered exactly one millimeter inside the authorized boundary, rather than stepping outside it. It was the kind of question that was technically, legally within the authorized subject matter, but whose answer incidentally, unavoidably illuminated a massive, highly classified engineering principle that the authorization had desperately tried to keep hidden.
It was not just a skill. It was state-sponsored espionage disguised as academic curiosity.
Nair's most significant, highly lucrative conversation at Sevmash had occurred over a drafting table with a senior reactor safety engineer named Dmitri Volkov. Volkov was the man directly responsible for the classified emergency core cooling system design for the brutally fast, titanium-hulled Alfa-class nuclear submarine programme. The conversation had been specifically, legally focused on the metallurgical selection for emergency cooling pipes—a strictly authorized subject.
But it had incidentally, spectacularly illuminated something vastly more valuable. Through Volkov's specific, highly professional manner of explaining his metallurgical rationale, he accidentally revealed the fundamental mathematical principles of compact naval reactor shielding geometry. It was the single most technically sensitive, violently guarded secret in the entire domain of naval nuclear propulsion.
Volkov had been tapping a pencil against a cross-section drawing, explaining a structural decision. *"The radiation shielding must be absolutely sufficient in this specific geometry, Commander, because the crew compartment is located exactly here—"* Volkov had said, explicitly indicating a critical proximity point on the hull. *"And the naval radiation regulations strictly require this specific margin of safety—"* he added, casually stating a highly classified mathematical margin dimension. *"Therefore, the only alloy that physically achieves this margin, at the strict weight the submarine's design allows, is..."*
He had then explained the specific alloy.
Nair had listened with the terrifying, total quality of attention that allowed his brain to instantly process the data. He didn't just learn the alloy. He derived, from those three casually dropped pieces of classified information—the exact hull geometry, the specific margin requirement, and the material density—the underlying, highly secret shielding mathematical formula that the three pieces, taken together, fully determined. Once Nair had the formula, India didn't need to buy Soviet shielding logic. They could engineer their own.
Nair had not written a single word down during the meeting. He hadn't even blinked.
He had waited until that evening, sitting alone in the small, freezing room at the workers' residence facility that the Indian team occupied during the grueling Arctic winter. There, he had painstakingly written the entire mathematical formula into his personal notebook, heavily encoded in a bespoke, unbreakable cipher that he and two of his brightest team members had specifically invented just for this mission.
That unassuming notebook was currently sitting at the bottom of his luggage in Visakhapatnam, bearing a specific, terrifying level of security classification for a piece of documentation that officially did not even exist.
The transit of INS Viraat from the freezing waters of the Black Sea to the tropical humidity of Visakhapatnam required a level of logistical and legal deception that bordered on geopolitical art. Moving a seventy-thousand-tonne nuclear-powered leviathan through the most heavily monitored maritime chokepoints on the planet was not merely a navigation challenge; it was a supreme act of statecraft.
The Bosphorus and the Dardanelles—the narrow, highly congested Turkish straits that connected the Black Sea to the Mediterranean—were strictly governed by an ancient, ironclad treaty regime under the Montreux Convention. The Convention explicitly imposed severe, non-negotiable limitations on aircraft carriers transiting the straits. Under international maritime law, the Montreux Convention rigidly defined aircraft carriers as capital ships, and it established absolute maximum tonnage limits for capital ship transit.
INS Viraat, sitting deep in the water at over 70,000 tonnes, violently exceeded the Montreux Convention's per-vessel limit for capital ship transit.
If it sailed as a warship, Turkey would be legally obligated by NATO to block the strait.
This was a known, fatal constraint, and Karan Shergill had aggressively addressed it during the construction agreement's earliest planning phase.
The brilliant solution was a specific, highly deceptive engineering provision that Director Petrenko's team had seamlessly incorporated into the ship's final fitting-out phase: a full, modular deck reconfiguration. When implemented, this physical disguise legally forced the vessel to be classified, under the Montreux Convention's highly specific, archaic definitions, as something other than an aircraft carrier for the sole purposes of the transit.
The massive reconfiguration involved temporarily unbolting and stowing the modular ski-jump ramp and sealing the massive twin steam catapult tracks. The vast, flat expanse of the 311-meter flight deck was then systematically covered with a heavy, tightly packed cargo pattern of standardized commercial shipping containers. This false cargo deck completely transformed the profile of the ship. It broke up the instantly recognizable, lethal silhouette of a supercarrier, replacing it with the bulky, lumbering, less immediately identifiable profile of a very large bulk cargo carrier operating in some kind of highly unusual configuration.
It was absolutely not perfect. Any competent NATO naval intelligence officer standing on the shores of Istanbul with high-powered binoculars and access to the ship's classified specifications would not be deceived for a second. The deep-draft hull form, the colossal superstructure placement, the island's distinctive, towering character—even completely stripped of its military radar masts and communication antennas—could not be fully disguised by a few hundred painted steel containers.
But the transit through the Bosphorus and the Dardanelles was not primarily a visual deception operation. It was a cold, calculated legal compliance operation. The Turkish maritime authority reviewed the ship's transit documentation. The flawlessly forged documentation described the vessel as a heavily modified general cargo ship undertaking a routine commercial voyage. The documentation was legally issued under a Liberian flag of convenience, shell-registered by a holding company in Geneva specifically for the vessel's week-long transit.
This was the specific, highly cynical category of legal creativity that superpower naval procurement in the Cold War era had perfected as a standard instrument.
The transit happened in the dead of night, in the bitter cold of February, under conditions of extremely low visibility from the shore. The Bosphorus was crossed in four tense hours. The Dardanelles took six. By the time the brilliant Mediterranean sunrise was finally producing enough light for shore observation, INS Viraat was safely in the Aegean Sea, well beyond the strait, legally operating in international waters as a general cargo ship with a Liberian registration.
The Turkish maritime authority had received a polite, standard courtesy notification of transit from the Liberian-registered general cargo vessel General Cargo 47, and they had stamped it and processed it in the normal, unremarkable course of daily business.
Not a single American intelligence satellite was tasked to the Bosphorus during the relevant transit window.
This was absolutely not an accident. The February 1978 Geneva Framework—the massive, global bilateral agreement between the Republic of India and the United States that had formally ended the devastating Indian oil embargo—contained a highly specific, classified annex that was not published, and was strictly not discussed outside the highest security clearance levels of New Delhi and Washington.
The secret annex guaranteed three things.
First, it stated that the United States formally acknowledged India's deep defense cooperation relationship with the Soviet Union as a permanent, established fact, and Washington promised it would not seek to aggressively disrupt existing, already-contracted elements of that relationship.
Second, it stated that the United States military would intentionally blind itself. It would not task signals intelligence or satellite reconnaissance assets against key Indian naval facilities, nor against Indian-associated vessels engaged in transit operations during the calendar year 1978.
Third, it stated that both global powers understood this annex to be a temporary, highly pragmatic arrangement. The long-term bilateral defense and trade relationship they were rapidly developing was expected to make the annex completely unnecessary within three to five years.
The annex was United States National Security Advisor Zbigniew Brzezinski's specific, ruthless contribution to the Geneva Framework. He had fought viciously for it in the internal White House administration reviews. He understood the brutal reality: India possessing a massive, Soviet-built nuclear carrier was already an undeniable fact. The contract had been signed in 1975, the steel was cut, the reactor was hot, and the transfer was happening. The American choice was binary: gracefully acknowledge the fact and build a lucrative relationship forward, or throw a diplomatic tantrum, attempt to block the ship, and accomplish absolutely nothing except confirming to New Delhi that America was an eternal, sworn adversary.
Carter had asked: *"Zbig, what happens when the global press finds out we just let the Indians take delivery of a seventy-thousand-ton Soviet nuclear supercarrier without firing a single diplomatic shot?"*
Brzezinski had leaned over the Resolute Desk, his voice cold and analytical. *"Mr. President, the alternative to not saying anything is saying something, and triggering a geopolitical crisis we will absolutely lose. If we publicly invoke the Montreux Convention and force Turkey to blockade the strait, the ship is forced to turn around. And where does it go? It goes right back to the Soviet Black Sea Fleet. We would literally be handing the Kremlin a fully operational, seventy-thousand-tonne nuclear supercarrier. The USSR would have two of these leviathans prowling the oceans instead of one."*
Brzezinski had tapped his knuckles against the heavy wood of the desk for emphasis. *"And what of New Delhi? Karan Shergill just signed the Geneva treaties and lifted the oil embargo that nearly broke our economy. If we humiliate him on the global stage and actively blockade his multi-billion-dollar flagship, he will tear up those treaties and permanently lock India into a violent, unbreakable military alliance with Moscow. If we try to stop that ship, Mr. President, the Soviet Union gets two carriers instead of one, and the United States gets two global enemies instead of one. Looking the other way while that hull sails quietly to Visakhapatnam is the cheapest strategic survival insurance this administration will ever buy."*
Carter had frowned. *"And the Congressional oversight committees?"*
*"The committees will be briefed in a secure vault,"* Brzezinski had countered smoothly. *"The briefings will note that this administration has made a highly classified strategic determination: avoiding a two-front war against both Moscow and New Delhi fundamentally outweighs the empty gesture of objecting to a carrier transfer that is already physically accomplished."*
Carter had sighed, and accepted the brutal math of the Cold War.
The satellite was not tasked to the Bosphorus.
General Cargo 47 transited smoothly in the dark.
The Mediterranean transit took eleven quiet days.
Rear Admiral P.K. Sharma spent almost every waking hour of them either on the bridge or down on the massive flight deck, walking the ship in the systematic, obsessive way that a new commanding officer familiarized himself with a colossal new command. It was not a tourist's walk. It was an engineer's walk. It was a tactical walk that methodically identified the specific character of each compartment, the hum of the nuclear plant, and each piece of equipment in relation to every other.
He was accompanied for much of this relentless patrol by Captain Sergei Borisov, the Soviet Navy's senior liaison officer for the transfer. Borisov had been the ship's last Soviet commanding officer during its sea trials, and he was now serving as the technical handover lead for the transit. Borisov was fifty-four years old. He possessed the specific, rigid quality of a proud military man doing his professional duty in circumstances that were personally agonizing. He had built a deep, visceral professional relationship with this nuclear leviathan over the three years of its construction. It was the relationship of a captain to a supreme vessel he had fully expected to command in combat—and now he was simply driving it south to hand it to a man who was not him, and who was not Soviet.
But he did his duty flawlessly.
He answered every single technical question Sharma asked. He patiently explained the highly specific, classified idiosyncrasies of the ship's massive nuclear propulsion plant—the reactor's tendency to require a slightly higher primary coolant pressure than the manual suggested during initial startup from cold; the forward damage control system's third distribution valve, which had been known since installation to require a far more violent, deliberate physical operation than its counterparts; the aircraft landing control room's ventilation system, which ran dangerously hot in confined conditions and required the secondary exhaust fan to be engaged hours earlier than the maintenance schedule specified.
These were the vital, life-saving secrets that a colossal warship only revealed to you if you had spent years with it and paid obsessive attention. Borisov had paid attention. And now he was honorably transferring that attention to his Indian counterpart.
Sharma wrote everything down in a heavily encrypted notebook.
On the eighth day of the Mediterranean transit, standing on the catwalk near the island superstructure, Borisov asked Sharma a question that neither of them had expected him to ask.
He said—in careful Russian, which Sharma spoke adequately from his own Moscow attachment years prior—*"Admiral. What specific aircraft do you intend to fly from this deck?"*
Sharma looked out at the sea. *"The first operational squadrons will be flying the S-22 Makara."*
Borisov was quiet for a long moment, the wind whipping at his heavy coat.
*"I have read the classified technical assessments of the Indian S-22,"* Borisov said finally. *"The aircraft is heavy. The deck requirements are fundamentally different from what this ship was originally specified for when we laid the keel."*
*"The steam catapult tracks were recalibrated and the ski-jump angle was heavily modified in the final design phase to perfectly accommodate the S-22's massive take-off performance,"* Sharma corrected him smoothly. *"The arresting wire spacing was also significantly modified for the heavier landing weight."*
*"Yes. I know. I was deeply involved in the intense modification arguments with the Nikolayev engineers,"* Borisov said, his voice carrying a note of professional warning. *"The ship was perfectly designed for lighter Soviet aircraft. The modifications were successfully made. But structural modifications designed to accommodate a radically different aircraft always consume safety margins. What are your margins?"*
*"The safety margins on the twin steam catapult accumulators are exactly twelve percent above the S-22's maximum calculated take-off weight requirement,"* Sharma recited from memory. *"The arresting wire spacing gives us three highly viable wire options for the landing, even in heavy pitch. The touch-down zone marking has been completely re-calibrated for the S-22's faster, heavier approach speed."*
Borisov nodded slowly, processing the math.
*"The margins are acceptable,"* the Soviet Captain conceded. *"But Admiral... the landing pattern in the violent sea states typical of the Bay of Bengal during the monsoon will be vastly different from the freezing Barents Sea. The extreme pitch and heave motion at typical Bay of Bengal sea states, at a carrier's thirty-knot operational speed, will affect the approach stability of a heavy jet differently. Has this been computationally modeled?"*
*"Exhaustively,"* Sharma said. *"By our TACDE team in Visakhapatnam. In direct, daily collaboration with the S-22 programme's lead test pilots."*
Borisov looked down at the massive, steel expanse of the deck. *"Good."*
He looked back at Sharma. *"This ship is a masterpiece, Admiral. It was brilliantly built. The Nikolayev workers—"* he paused, his voice thick with suppressed emotion, *"they built exactly what they were given to build, and they built it to withstand the end of the world."*
He said this with the specific tone of a man who was fiercely, deeply proud of the steel, and utterly heartbroken by the geopolitics that had taken it from him.
*"The ship will serve the Republic of India well, Captain,"* Sharma said respectfully.
*"Yes,"* Borisov whispered. *"I expect it will."*
They stood at the flight deck's port edge in silence, looking out at the Mediterranean. It was a brilliant, quiet blue in February, possessing that specific, pristine Mediterranean clarity that only appeared when the violent winter storms were brewing miles away, rather than directly on top of you.
At Visakhapatnam, the government-operated Naval Shipyard was absolutely not where INS Viraat was going.
The decision regarding exactly where INS Viraat would complete its massive, highly classified Indian refit and electronic integration had been decisively made in 1976, during the construction agreement's earliest planning phase.
The conventional Naval Shipyard at Visakhapatnam possessed the capability to conduct routine, localized maintenance on vessels up to destroyer size. It had extremely limited capability for major combat system installations. It had absolutely zero capability, zero infrastructure, and zero security clearance for the specific, colossal work that INS Viraat required. The massive vessel needed the complete, surgical installation of a hyper-advanced suite of Indian-designed combat systems, radars, encrypted communications equipment, and aviation management systems. This was the grueling work that would seamlessly convert INS Viraat from a Soviet carrier running Soviet brains into an Indian supercarrier running Indian brains.
The Shergill Heavy Industries Visakhapatnam Shipyard was a different beast entirely.
It had not been built from scratch specifically for this arrival. It had been aggressively, ruthlessly acquired by Karan Shergill in 1972, ripped down to the coastal bedrock, and entirely, violently overhauled over the last five years. It was already a bleeding-edge, booming facility, churning out advanced guided-missile destroyers and heavy frigates for the Eastern Fleet at a pace that terrified foreign observers.
But the massive, staggering dry dock extension had been built specifically to the exact specification of a facility capable of swallowing and maintaining the largest naval vessels on earth. The newly reinforced dry dock was 350 meters long—long enough to comfortably accommodate INS Viraat with fifty meters of safety margin to spare. The sheer crane capacity was astronomical: 400 tonnes on the fixed steel gantry cranes, and 100 tonnes on the mobile harbor cranes. The sprawling facilities for precision metalwork, advanced electronic systems installation, and the highly specific, classified requirements of nuclear warship system integration had been relentlessly developed and heavily equipped over five brutal years.
The heavy engineering behind the shipyard had cost Karan Shergill ₹2,800 crore.
The radical design had been executed by a hybrid team that included elite Indian naval architects who had trained at the Naval Construction department, brilliant Indian engineers who had worked at Mazagon Dock, veteran British marine engineers from Swan Hunter—operating under a quiet consultancy relationship with a company that had been building warships for the Royal Navy since 1860—and, since 1976, the specific, invaluable inputs of the Indian engineers who had been secretly attached to Nikolayev, who understood exactly what a facility capable of supporting a 70,000-tonne nuclear carrier needed to look like.
The massive shipyard boasted four immense construction halls, twelve deep-water berths, two colossal dry docks, and a Systems Integration Facility. This facility was the most significant, revolutionary innovation in the entire Visakhapatnam design. It was a massive, electromagnetically shielded building located directly adjacent to the dry dock that allowed highly sensitive electronic systems to be fully configured, powered, tested, and integrated before they were ever lowered into the vessel. This violently reduced the amount of cramped, difficult work done within the ship's steel hull, drastically reducing the time the multi-billion-dollar ship spent helplessly immobilized in the dock.
The Systems Integration Facility was Dr. Sanjay Bose's absolute, unquestioned territory.
Bose was forty years old, a brilliant, intense radar and electronic systems engineer from Calcutta who had been with ISMC's defense electronics division since 1974. He had been appointed in January 1978 as the absolute head of the INS Viraat integration programme. His formal title was Integration Programme Director. His actual, unvarnished role was simple: Gut the Soviet electronics, get the hyper-advanced Indian systems into the nuclear ship in the grueling eighteen months the programme schedule allowed, and ensure they performed to the terrifying specifications that the Naval Staff had demanded. All while managing the specific, agonizing complexity of physically adapting Indian-designed, solid-state equipment to a massive steel platform that had been designed and built to entirely different Soviet standards.
He had been living at Visakhapatnam since September 1977, when the integration programme's detailed design phase had been completed and the massive hardware procurement had violently accelerated.
The vital systems that INS Viraat would receive at Visakhapatnam were the nervous system of the fleet:
The Netra-3 Radar: The third, most lethal generation of the Netra airborne and surface radar family, heavily adapted for the specific, high-stress requirements of carrier-based air traffic control and fleet air defense management. The Netra-3 was derived directly from the S-35's Trinetra system, but it was a massive surface installation, featuring a colossal rotating antenna array on the carrier's island mast platform, and a supercooled processing suite buried deep in the island's combat information center.
The Brahma-16 Combat Management System: Running on ISMC's bleeding-edge Brahma-16 processor, this system flawlessly managed the integrated, real-time picture of surface, air, and submarine contacts for hundreds of miles around the carrier. It provided the God's-eye tactical display from which the Admiral commanding the task group would mercilessly direct the battle. It was the first fully integrated naval battle management system developed entirely indigenously in India, representing five years of obsessive development at the DRDO's naval systems laboratory.
The AkashNet Tactical Communication Suite: Utilizing the same optical and heavily encrypted radio communication architecture that the AkashNet Core ground network used, aggressively adapted for the highly corrosive naval environment. It featured specific, unbreakable requirements for communication security, overcoming the massive challenge of operating in a highly congested maritime electromagnetic environment.
The Ganesh-4 Datalink System: The vital, encrypted ship-to-aircraft communication link that seamlessly connected the carrier's combat management system directly to the S-22 Makaras in its air wing. The Ganesh-4 was absolutely critical. A carrier whose aircraft communication relied on a compromised Soviet system was a carrier whose most critical command-and-control function could be intercepted.
The Aviation Fuel and Weapons Management Systems: The heavily armored systems that managed the highly dangerous, high-pressure flow of highly volatile aviation fuel and heavy ordnance from the ship's deep armored magazines to the aircraft waiting on deck. Converting them from crude Soviet design standards to highly efficient Indian naval standards required massive, dangerous adaptation work.
Bose commanded a brilliant, exhausted engineering team of 340 men at Visakhapatnam working purely on the integration programme.
The Nikolayev-trained engineers comprised 84 of them—the specific 84 of the original 100 who possessed the most relevant, critical skills for the specific combat systems being installed.
The remaining 16 engineers of that elite cohort were currently locked in the vault in Gorakhpur, working entirely on the classified nuclear propulsion programme that was the longer-horizon, world-changing task.
Lieutenant Commander Rohan Mehta was twenty-nine years old, and he had been a rising star in the Indian Navy for seven years.
He had deployed to Nikolayev in February 1977 as part of the elite 100-engineer team, and he had spent fourteen freezing months there in the highly specific assignment that Commander Nair had designated for the team's youngest qualified engineer: the aviation systems group. Specifically, Mehta was obsessively focused on the violent, high-stress mechanics of the steam catapults, the arrested landing system, and the heavy aircraft handling equipment.
The arrested landing system on INS Viraat—the massive hydraulic system that violently caught a screaming aircraft with a thick steel wire and brought it to a smoking stop—was a Soviet design. But it was a Soviet design that served the exact same, brutal function as American or British carrier landing systems. The physical realities derived from being solutions to the exact same, unforgiving physical problem: catching a 25-tonne, fully loaded strike fighter moving at 250 kilometers per hour, and stopping it dead in 100 meters without tearing the aircraft in half or liquefying the pilot's spine.
The brutal physics were universal. The engineering implementations were wildly different.
Mehta had spent three obsessive months specifically dissecting the arresting gear system—its massive hydraulic energy absorbers, its complex wire management system, its deck-level retraction equipment. He had come away fully understanding, in the specific, practical, grease-stained depth that only direct physical exposure to operational equipment provided, exactly what the system's design intent was. He knew its strict maintenance requirements. He knew its specific, fatal failure modes, exactly how they presented, and exactly how to fix them in under three minutes on a pitching deck.
He was currently standing in a massive workshop at Visakhapatnam, deeply embedded in the aviation systems team, painstakingly adapting the arresting gear system's mechanical interfaces to perfectly accommodate the heavier Indian aviation support systems that were replacing the Soviet ones.
The specific, immediate challenge was the heavy crossdeck pendants—the thick steel cables that stretched across the landing deck and violently caught the aircraft's tailhook. The original Soviet crossdeck pendants were manufactured to a highly specific Soviet military metallurgical specification. The Indian specification for the replacement pendants—which would be manufactured entirely domestically by Shergill Steel—was a vastly superior, new specification that the Indian naval standards organization had developed. The two specifications were functionally equivalent in terms of sheer tensile strength and elastic characteristics, but they were radically different in the precise thread form of the massive steel end fittings that physically attached the pendant to the hydraulic arresting gear unit below the deck.
The minute thread form difference required highly complex, custom-machined steel adaptor fittings. If the adaptor failed, the wire snapped, and a pilot died.
Mehta had painstakingly designed the adaptor fittings in January. He had submitted the complex CAD drawings to the precision machining shop at the Visakhapatnam shipyard, which utilized the absolute best, Gorakhpur-made CNC machine tools to carve them out of solid blocks of high-tensile steel. The very first set of heavy prototype fittings had come off the screaming machines in early February, and they were currently locked in the massive hydraulic testing jig that the aviation systems team had built inside the systems integration facility.
He was running the stress tests when the encrypted radio news came that the ship had entered the Red Sea.
He was actively testing them when the news came that the ship had passed through the Suez Canal.
He was pushing them past their failure limits when the news came that the ship was in the Gulf of Aden.
He was standing in the cavernous fitting-out berth—the deep-water berth immediately alongside the systems integration facility where massive preparatory work was done before the ship even entered the dry dock—when the encrypted radio carried the information that INS Viraat was exactly twenty hours away.
He looked down at the gleaming steel adaptor fittings locked in the heavy testing jig.
They had flawlessly passed their extreme tensile strength tests. They had passed their high-torque thread engagement tests. They had survived their violent installation and rapid-removal cycle tests.
They were ready for war.
He wiped the grease from his hands with a rag. He thought: The ship is twenty hours away, and these fittings are ready. This is exactly what we froze for fourteen months in Nikolayev to achieve. We learned what their system was, so that we could violently modify it and build what India needed to make it ours.
He locked down the testing jig.
He went to find Nair, who was somewhere deep in the systems integration facility, aggressively reviewing the combat management system's massive wiring interface drawings for the sixteenth consecutive time.
The arrival of INS Viraat at Visakhapatnam was absolutely not a public event. There were no marching bands, no press photographers, and no politicians.
The colossal ship arrived in the early morning of February 18th, at exactly 0340 hours, in conditions of complete, absolute darkness and a strict, enforced minimum of port activity. The quiet approach had been meticulously planned for this specific time—the dead pre-dawn window when the sprawling harbor's commercial traffic was at its lowest, when the local fishing fleets were at anchor, and when the specific, hazy visibility conditions of a winter night on the Bay of Bengal's coast made the ship's massive approach visible to the harbor's military tracking systems, but entirely invisible to casual observers on the shore.
The sole escort was a single, sleek Indian Navy guided-missile destroyer, INS Godavari. The destroyer had quietly met INS Viraat in international waters, exactly 200 kilometers south of Visakhapatnam, and had seamlessly provided the specific, highly disciplined naval escort that a major capital warship required when entering its home waters for the very first time.
The crew of INS Godavari, standing watch in the freezing night when they first saw INS Viraat emerge from the darkness, had seen the ship's running lights and the colossal, towering profile against the starry sky. The profile was simply unlike any ship profile that the Godavari's battle-hardened crew had ever previously encountered in any naval exercise or operational deployment.
The profile was terrifyingly large.
The Godavari's commanding officer, Commander Krishnamurthy, had been heavily briefed on exactly what he was escorting. He had been told: You will escort a vessel of approximately 70,000 tonnes displacement, nuclear propulsion, into Visakhapatnam harbor for a massive refit at the Shergill shipyard. The vessel will be flying an Indian flag.
He had been told this, and he had understood it academically, as a set of numbers on a page. He had absolutely not fully experienced what 70,000 tonnes of nuclear-powered steel actually looked like from the bridge of a 3,500-tonne destroyer at sea in the pitch dark. When INS Viraat's running lights finally appeared in his binoculars, and his brain desperately processed the sheer, towering angular size of what he was seeing against his calibrated experience of ship sizes, he had physically stopped breathing for a second.
He had picked up the radio handset and transmitted on the encrypted channel: *"INS Godavari to unidentified heavy contact. Proceeding to escort position."*
The deep, calm response crackled back from INS Viraat: *"INS Godavari, this is INS Viraat. Welcome. Please take station exactly one kilometer astern, bearing 180 degrees."*
Krishnamurthy had taken station astern and had faithfully followed the colossal carrier into Visakhapatnam harbor. In the specific, amber light of the harbor's navigation markers, he had seen it. As the ship passed close enough to the headland for the massive harbor arc lights to fully illuminate its armored side, he saw the towering, immense 311-meter length of the flight deck soaring twenty-nine meters above the waterline.
He had lowered his binoculars. He had thought: This is what the Republic of India has now. God help anyone who gets in our way.
Admiral Sharma brought the colossal ship smoothly alongside the Shergill shipyard's massive, reinforced carrier berth—the specific, incredibly deep berth that had been aggressively designed and heavily constructed for exactly this moment—at 0623 hours on February 18th.
The massive, braided steel mooring lines went ashore, hauled by heavy winches. The heavy gangway was lowered with a mechanical whine. The exhausted, triumphant crew of INS Viraat walked down the gangway and stepped onto sovereign Indian soil for the very first time since the ship had sailed from the icy Black Sea.
Among the very first people who came aboard from the dock after the gangway was secured was Commander Nair.
He walked up the gangway with the specific, intense quality of a man who had been violently waiting for this moment for fourteen months. He walked up the gangway with the encrypted notebook tucked safely in the breast pocket of his uniform—the notebook he had been religiously keeping since the freezing nights at Sevmash.
He walked up the gangway and onto the ship that would be the sprawling, nuclear platform on which the knowledge in that notebook would eventually be applied. Not just to operate this specific ship, but because what India learned from operating the nuclear-powered INS Viraat was the absolute foundation on which India's entirely domestic, completely indigenous nuclear carriers would eventually be built.
He walked onto the massive flight deck.
The sun was just coming up to the east, rising brilliantly over the Bay of Bengal, producing the specific, crisp quality of early morning light that the Bay produced in February. It was not cold, and it was not warm; it was the specific, temperate quality of a massive sea that was caught between its summer and winter characters.
Nair stood at the aft end of the flight deck, near the arresting wires, and looked forward along the immense, 311-meter runway of steel.
He thought about the freezing docks of Nikolayev, where the massive hull had been built. He thought about the heavily guarded, radioactive halls of Sevmash, where he and his team had quietly learned the terrifying things that were currently locked in his notebook in cipher. He thought about the 84 brilliant engineers waiting in the systems integration facility, tools in hand, completely ready to begin the grueling eighteen-month work of physically ripping the Soviet nervous system out of the ship and replacing it with India's soul.
He thought about the specific, blunt sentence that Commodore Suresh Pillai—the ruthless man who ran the Shergill Visakhapatnam shipyard and who had been building warships for India for thirty years—had said to him in the intense briefing the previous week, when Pillai had proudly walked him through the sprawling integration facility.
Pillai had swept his arm across the warehouse. *"Everything that can be ready is ready, Nair. The Netra-3 radar is ready. The CMS is ready. The AkashNet suite is ready. The Ganesh-4 datalink is ready. The aviation support systems are ready. Mehta's precision fittings are ready. What is not ready is the ship—because the ship is not here yet."*
Pillai had smiled, a fierce, predatory grin. *"When the ship is here, we begin the surgery."*
The ship was here.
In Gorakhpur, deep within the ISMC technical reading room, the heavily guarded classified document vault contained exactly one physical copy of a highly technical report. It had been meticulously produced by the 16 elite engineers who had been assigned to the Sevmash programme specifically for the nuclear propulsion espionage component.
The report was 340 pages long.
It was written in the specific, dry, highly technical language of systems engineering documentation—the precise language of brilliant men who were flawlessly describing what they had learned in a form that other brilliant engineers could use to build a reactor. It was absolutely not a political document, nor a sweeping strategic assessment. It was an unsparing engineering blueprint.
It meticulously described what a functional naval nuclear propulsion system actually looked like, from the unique perspective of engineers who had been locked inside a facility that built them. It detailed, within the strict bounds of what they had been officially authorized to see—and the massive, classified principles they had independently derived from those glimpses—the highly specific, lethal characteristics of the design, the required metallurgy for the manufacture, and the terrifying maintenance protocols of a naval reactor and its associated safety systems.
The report had been obsessively reviewed by the Director of the Naval Science and Technology Laboratory—the secretive facility that would eventually be entirely responsible for the Indian domestic nuclear propulsion programme—and by the Chief of Naval Staff's office in Delhi.
The Chief of Naval Staff's handwritten annotation on the cover of the review copy was stark and absolute: This is the foundation. Now build the house.
The document was classified at the absolute highest level of state secrecy.
It was locked in the vault at Gorakhpur simply because the Gorakhpur ISMC's world-leading materials and process capabilities—specifically the sub-micron precision manufacturing and the advanced materials science that the facility had aggressively developed over ten years for semiconductor and aerospace applications—were directly, intrinsically relevant to the specific, massive engineering challenges that building a safe naval nuclear reactor would present.
The house was going to take fifteen years of agonizing, brilliant work to build.
But the foundation was securely in the vault.
The massive, surgical work at Visakhapatnam began violently on February 20th.
The integration programme's very first action was the aggressive disembarkation of all Soviet electronic equipment that was being replaced. It was not simply destroyed—it was carefully decommissioned, crated, and respectfully returned to Soviet custody in the exact manner specified in the transfer agreement, because the Soviets had highly legitimate intelligence interests in how their sensitive equipment was handled. Thirteen massive shipping containers of heavy Soviet combat system equipment left the shipyard by the end of the very first week.
The second action was the brutal, exhausting installation of the ship's new power and data infrastructure—the specific, miles-long cable runs and massive fiber-optic distribution architecture that the new, hyper-advanced Indian combat systems required. This was the grueling, unglamorous, back-breaking work of a major electronics integration programme. It was the work that consumed vastly more hours than any other single task, and that would be entirely, completely invisible behind steel bulkheads in the finished product. But it was the exact work that determined whether the finished product actually worked in a firefight.
Mehta spent the entire first month working double shifts on the arresting gear adaptor installation—fitting the heavy steel components he had tested, integrating the complex deck fittings, and running the violent acceptance tests with the massive hydraulic energy absorber operating repeatedly through its full, screaming test cycle.
On February 28th, the very first, domestically forged Indian crossdeck pendant was successfully, flawlessly fitted into the aft arresting gear unit of INS Viraat.
Mehta quietly marked the date in his personal log.
He did not mark it publicly. The entire integration programme was heavily classified, and absolutely no public acknowledgement of the nuclear ship's presence at Visakhapatnam was made by the government.
The ship was simply there. The engineers were aggressively working. The systems were rapidly going in.
In fourteen months, the strict programme schedule dictated, the cutting-edge Indian electronics, the Indian radar, the Indian combat management, the Indian encrypted communication, and the Indian aviation support would be fully alive within the ship. What was going in during these fourteen months was absolutely everything that made the ship a lethal Indian weapon, rather than a Soviet weapon with painted Indian markings.
Dr. Bose had stood before his exhausted team at the massive programme kickoff meeting and delivered their mandate.
*"When this ship finally goes to sea from Visakhapatnam for the first time,"* Bose had said, his voice echoing in the hall, *"the systems that decide what it detects over the horizon, what it communicates to the fleet, what it targets with its missiles, and what it tells the Admiral about the tactical battlespace will be one hundred percent Indian. The massive nuclear propulsion will still be Soviet, yes. But propulsion is merely what takes you to the fight. We are responsible for winning the fight."*
Bose had looked at his men. *"That is what we are building here. Not a slightly modified Soviet carrier. An Indian supercarrier that simply uses a Soviet hull."*
The engineers had received this with the specific, fierce quality of men who completely understood the profound distinction, and believed in it entirely.
The news in the Western press in February 1978 contained absolutely no reference to an Indian nuclear aircraft carrier.
The specific, deafening absence of this critical information from Western press reporting was the direct product of several factors, of which the American intelligence community's forced restraint under the Geneva Framework's annex was the most significant single one. The sprawling American signals intelligence system was the primary, vital source through which Western media received early, "leaked" notification of major naval developments in the Indian Ocean region. When that source was directly ordered by the White House to observe strict restraint, the flow of information to the media that depended on it instantly stopped.
The Soviet press also published absolutely nothing, which was the Soviet state press's normal, paranoid practice with respect to classified naval capabilities.
The Indian press published nothing, which was the Indian press's practice with respect to highly classified national security matters, heavily enforced by the specific, potent combination of patriotic voluntary compliance and the Official Secrets Act's terrifying specific provisions about naval nuclear programmes.
The only vague, highly sanitized references in any public record to the monumental events of February 1978 at the Visakhapatnam waterfront were buried deep in the port authority's mundane vessel registration records—which simply showed the registration of a "very large vessel" to an Indian flag company—and in the Shergill Visakhapatnam Shipyard's internal project register. The register showed the initiation of what was described as a "major naval refit and integration programme" for a vessel that the project register identified only by a cryptic hull number.
The hull number was V-01.
V for Viraat.
01 for the first.
There would be others.
Admiral Sharma spent his entire first week in Visakhapatnam buried in high-level briefings, standing in the systems integration facility, walking the massive ship, and locked in the Naval War College's secure planning section.
He spent almost the entirety of his second week living on the ship.
He was rapidly, obsessively developing his deep understanding of his massive new command in the specific way that a dedicated commanding officer developed true understanding: through the accumulated, exhausting experience of spending time in every single compartment of the vessel, drilling with every department head, and running through every single operational scenario that could be discussed and tabletop-exercised before the real systems were installed and the ship was ready for actual sea operations.
The lethal air wing was not yet aboard. The elite S-22 Makara squadrons that would actively operate from INS Viraat when the ship was finally commissioned were currently stationed at their shore bases. They were relentlessly continuing their training, brutally building their proficiency with the specific, unforgiving demands of carrier aviation—the violent arrested landings, the bone-crushing steam catapult-and-ski-jump launches, the highly complex carrier-controlled approach patterns, and the terrifying night carrier qualification that was the absolute final validation of a carrier pilot's readiness for war.
The air wing would come when the ship was ready to receive them.
The ship would be ready for war in fourteen months.
On the last day of February, Admiral Sharma stood alone on the massive flight deck in the early morning, looking out over the sparkling expanse of the Bay of Bengal.
The Bay was, in late February, in one of its rare, quiet seasons. The violent monsoon was still months away. The sea was flat and glassy enough to show the curvature of the horizon clearly. The horizon, viewed from the towering flight deck of INS Viraat, was approximately 20 kilometers distant—vastly further than from the ground, because the flight deck towered 29 meters above the waterline, and extreme height gave massive range to the horizon.
He thought about the specific 20 kilometers of quiet sea between the ship and the horizon.
He thought: In every single direction, from this steel deck, I can see 20 kilometers.
He thought about a massive carrier strike group operating in the center of the Bay of Bengal. The nuclear carrier positioned safely in the absolute center. The advanced guided-missile destroyers, the heavy frigates, and the silent hunter-killer submarines operating at the outer radius. The S-22 Makara strike aircraft operating at a lethal radius of 500 kilometers from the deck, extending the carrier's eyes and destructive reach to a massive, impenetrable circle that was not 20 kilometers, but 500 kilometers in every direction.
He thought: A nation's maritime boundary is the exact line where that nation's interests end, and the hostile interests of others begin. From this deck, that line is forcefully pushed 500 kilometers away.
He thought: There is no other platform on earth, short of a nuclear ICBM, that can make this absolute statement.
He thought about the brilliant, exhausted men of the integration team—Bose, Mehta, Nair and his 84 engineers, Pillai and the thousands of shipyard workers who were currently pulling miles of cable runs, welding the bracket installations, and executing the unglamorous, foundational work of building a superpower.
He thought: In fourteen months, this leviathan will go to sea. Running with Indian systems, armed with Indian weapons, speaking through Indian communications. Under absolute Indian command. Launching Indian aircraft.
He thought: This is what the Andaman oil bought. It bought the ocean.
He thought about a tiny, dusty village at Ramgarh in Rajasthan—though he did not know that specific village—and the thousand villages exactly like it whose dim lights ran from sputtering diesel generators for only three hours in the evening.
He thought: A nation's true capability is not only measured in its weapons. But its weapons are the specific, undeniable statement that the nation makes to the world about its absolute sovereignty. The statement that this ship makes is the statement that the Republic of India's maritime sovereignty extends to the absolute limits of its air wing's range, and the cruising radius of its nuclear task group.
He had spent twenty-nine years in the Navy preparing his entire life to make this exact statement.
The statement was fourteen months away.
He turned away from the horizon and went below decks, descending into the belly of the ship to the briefing room, where Bose's exhausted integration team was preparing to present the Week 2 progress status.
There was still massive work to do.
There always was.
End of Chapter 327
INS Viraat — Technical Summary (February 1978)
Designation: Indian Naval Ship Viraat (INS Viraat), V-01 Class: Modified Nikolayev Project 11435 / Project Orel (Indian designation: Vishal class) Displacement: 70,400 tonnes full load Length: 311 metres overall Beam: 72 metres (flight deck), 38 metres (waterline) Draft: 10.4 metres Propulsion: Nuclear-powered, 2x Pressurized Water Reactors (PWR), 4-shaft steam turbine, 200,000 shp combined; 30+ knots maximum, 18 knots cruise Endurance: Unlimited (limited only by aviation ordnance and crew supplies) Aircraft capacity: 36 fixed-wing and rotary wing aircraft in standard configuration; 42 maximum Primary aircraft: S-22 Makara naval strike/fighter (ISMC/Shergill Aerospace) Flight deck: 311m x 72m, twin steam catapults forward, ski-jump ramp, 3 arresting gear wires aft Complement: 2,100 (ship's company), 900 (air wing), 400 (flag staff and command); 3,400 total
Indian Systems Integration Programme (February 1978 – April 1979): Programme Director: Dr. Sanjay Bose (ISMC Defence Electronics Division) Key systems: — Netra-3 air/surface search and fire control radar (Shergill/ISMC) — Brahma-16 Combat Management System (ISMC) — AkashNet Tactical Communication Suite (Shergill/ISMC) — Ganesh-4 Ship-Aircraft Datalink (DRDO Naval Systems Lab) — Indian Aviation Support Systems (fuel management, weapons management) — Brahma Medical and Damage Control Management Systems Integration team strength: 340 engineers and specialists Estimated programme duration: 14 months
Sevmash Engineering Programme: Purpose: Technology exposure and espionage for domestic nuclear carrier construction (future programme) Personnel: 100 naval engineer officers in 5 specialist groups Location: Sevmash Northern Shipyard, Severodvinsk, USSR Duration: February 1977 – December 1977 (14 months) Programme lead: Commander Arvind Kumar Nair Output: Classified technical documentation and derived nuclear mathematics (340 pages), held at ISMC Gorakhpur classified vault
US-India Geneva Framework Annex (Classified): Relevant provision: United States to exercise absolute restraint on satellite and signals intelligence tasking against Indian naval facilities and Indian-associated vessels in transit during 1978 calendar year. US rationale (Brzezinski): Strategic interest in forward-looking US-India naval cooperation and future weapons procurement drastically outweighs value of diplomatic gesture regarding an already-accomplished Soviet carrier transfer.
INS Viraat — Transit Route: Nikolayev (Black Sea) → Bosphorus/Dardanelles transit (Montreux Convention provisions; modular deck camouflage, Liberian flag of convenience, night transit) → Mediterranean → Suez Canal → Red Sea → Gulf of Aden → Indian Ocean → Bay of Bengal → Visakhapatnam Total transit distance: approximately 12,400 nautical miles Transit duration: 31 days
Shergill Heavy Industries Visakhapatnam Shipyard: Established: Acquired by Karan Shergill in 1972, heavily overhauled 1972–1977 Dry dock length: 350 metres (world-class, extended specifically for INS Viraat class) Gantry crane capacity: 400 tonnes Systems integration facility: Purpose-built, shielded facility adjacent to dry dock Total investment: ₹2,800 crore (1972–1978) Shipyard managing director: Commodore (Retd.) Suresh Pillai