Chapter 324:The Manduks
(warning - very long chapter pls it can e boring but this is very important chapter and big divergence from original india thats why highly specific and heavily detailed chapter)
May 1978INS Airavata; the beaches of Wheeler Island, Odisha; the Exercise Sagar Yuddh command post at Visakhapatnam; and the specific, extended, unsparing institutional accounting that follows an exercise that revealed more about what a new fighting force does not know than what it does
Major General Abhimanyu Singh Rawat had spent eleven days at the Marine Corps Base in Quantico, Virginia, in November 1976, and those eleven days had violently dismantled everything he thought he understood about the institution he was trying to build.
At forty-six years old, Rawat was a paratrooper by both rigorous training and deeply ingrained temperament. He had spent the first six years of his career bleeding with the 50 Para Brigade, followed by two demanding years commanding the Para Regimental Centre at Bangalore. He possessed the cold, hard operational experience of a man who had spent two decades perfecting the art of throwing soldiers out of perfectly good aircraft and ensuring they fought lethally once they hit the dirt. He was a hardened veteran of the 1971 eastern front, a key architect of the rapid airborne operations that had physically redrawn the map of the subcontinent, and the commanding officer of the very first Para battalion to punch its way into Dhaka.
He hadn't been selected to build the Manduks simply because of that impressive combat record. He had been chosen because of a very specific, brutally honest conversation he'd had with the Chief of Naval Staff in a quiet, wood-paneled office in South Block back in 1975—a conversation in which he had said something the CNS had never expected an Army paratrooper to say.
The Admiral, a veteran sailor deeply skeptical of handing an amphibious mandate to a man used to the sky, had tested him. "Tell me, Rawat," the CNS had asked, leaning back in his heavy leather chair. "What is the fundamental, tactical difference between an air assault and an amphibious assault?"
Rawat hadn't offered a sanitized military-college answer. "The medium is different, Admiral," Rawat had replied smoothly, meeting the older man's gaze. "The sea is not the air. But fundamentally, the brutal mathematics are exactly the same. You are attempting to deliver concentrated combat power to a specific, hostile point from outside that point's normal defensive perimeter. Your primary tactical advantage is the absolute element of surprise. Your primary nightmare is the extreme, naked vulnerability of your force while in transit, right before they hit the ground. But the sea alters the physics in ways the air does not. The sea is slower. It is vastly more visible to coastal radar. But the sea offers you a weapon the air never can: sustained, heavy logistical support. You can put infinitely more weight, armor, and continuous firepower ashore from a naval deck than you ever could dropping from the sky."
The CNS had stared at him for a long, heavy moment, the institutional skepticism slowly draining from his expression.
"You understand the problem, General," the CNS had finally said.
"I understand exactly half the problem, sir," Rawat had corrected him, his voice devoid of any standard inter-service ego. "I understand the drop. I don't yet understand the half that is specifically, culturally naval."
The CNS had smiled a thin, appreciative smile. "That is the most honest thing anyone in army olive-green has said to me about amphibious operations since I took this office."
Eighteen months later, that honesty had secured Rawat a plane ticket. Through a quiet, highly classified bilateral channel facilitated by the new Geneva framework, the Indian government had arranged an unprecedented professional exchange. The man tasked with building India's first genuine, dedicated amphibious combat force was granted eleven days of unrestricted access to the apex predators of the domain: the United States Marine Corps.
Rawat didn't go to Virginia as a tourist. He spent those eleven days aggressively watching, dissecting, and listening. He didn't perform polite enthusiasm for his American hosts, and he didn't waste his time collecting glossy briefing slides. He stood in the freezing rain and watched the Marine Corps move, train, and think. He studied their logistics, their aggressive infantry doctrine, and the staggering scale of their institutional machinery.
The United States Marine Corps in 1976 was a gargantuan, heavily armored leviathan. It boasted 196,000 active-duty personnel. It maintained three massive Marine divisions, three dedicated Marine aircraft wings, three force service support groups, and the deeply entrenched institutional infrastructure of an organization that had been fighting bloody, expeditionary wars at a massive distance from American soil since 1775.
The Marine Corps possessed its own aviation fleet. It operated its own global logistics chain. It drove its own main battle tanks, fired its own heavy artillery, commanded its own combat engineer capability, and fielded its own shadow intelligence organization. It was not a specialized tactical force—it was an entirely self-contained, fully independent army, meticulously configured for amphibious delivery and capable of sustaining massive, apocalyptic operations anywhere on the planet.
The Marine Corps doctrine that Major General Abhimanyu Singh Rawat had spent eleven days studying at Quantico—the heavily redacted red books, the operational manuals, the exhaustive planning guides—was the undeniable doctrine of a global empire's force-in-readiness. It was authored by generals who fully expected to fight viciously in theaters where America had absolutely no pre-positioned forces, no existing friendly infrastructure, and no local allies. It was written for a colossal organization that routinely deployed division-sized forces across the vast, hostile expanse of the Pacific Ocean.
Rawat recognized the lethality of the USMC. But he also recognized the institutional bloat, the bureaucratic arrogance, and the heavy, sluggish inertia of an empire that had grown entirely too comfortable resting on the laurels of its past victories.
India did not need a carbon copy of the American model. India needed something far more terrifying.
As the Third Superpower, the Republic of India was no longer playing defense in its own backyard. The era of merely managing the Indian Ocean was over. Indias economic and industrial empire required a kinetic military vanguard capable of projecting absolute, unyielding power across the globe. India needed a force capable of striking the Persian Gulf, securing the Straits of Malacca, or executing a hostile beachhead on a Pacific island without waiting for diplomatic permission.
The urgency of this requirement was not theoretical. It had been brutally, tragically demonstrated to the Indian high command just weeks after Rawat returned from Quantico.
During the brief, incredibly violent Indo-Burma War that flared between December 1976 and January 1977, the Indian military had identified a critical, potentially war-ending operational window. A massive beach landing on the Burmese coast would have decisively outflanked the enemy's entrenched defensive lines. But the Army high command had frozen.
Paralyzed by a profound lack of amphibious experience, terrified of the chaotic surf-zone logistics, and lacking a dedicated force trained for the brutal water-land interface, the generals had hesitated. They had debated, delayed, and ultimately rejected the beach landing plan entirely. They had opted instead for a slow, grinding, and incredibly bloody overland slog through the dense jungle.
Rawat had watched that hesitation cost Indian lives. It proved exactly what his time at Quantico had taught him: India could not project global power if its generals were terrified of the water.
Rawat had come back from Virginia, and subsequently from the Burmese border, with eleven pages of handwritten notes and one specific, unbreakable conviction: he was going to build something distinctly, lethally Indian.
He was not going to build a small, token Indian Marine Corps. He was not going to build a cheap, stripped-down clone of the USMC at a fraction of the cost. He was going to build something entirely new, designed from absolute first principles for the specific geographic, strategic, and aggressive operational environment of a rising superpower. A fiercely agile, localized strike force that could scale into a global expeditionary hammer, ensuring that the Republic of India would never look at a hostile beach and hesitate again.
He spent four exhausting months writing the foundational doctrine document. In February 1977, the doctrine was approved by the Defence Ministry, bypassing the traditional inter-service squabbles through Karan Shergill's quiet, heavy-handed influence, and submitted directly to Parliament as part of the constituting legislation.
The Manduks Raising Ordinance passed in March 1977.
By May 1978, Rawat had fifteen months of relentless, unsparing building behind him.
The new organization's full, formal designation was the Indian Amphibious Corps (Manduk).
The Sanskrit name—Manduk, meaning frog—had been Rawat's deliberate, fiercely guarded choice. He had aggressively rejected the obvious, romanticized aquatic warriors of ancient mythology, and he had completely discarded the Western-derived "maritime infantry" terminology that would have implied derivation from a foreign, colonial model.
The frog was entirely indigenous. The frog lived comfortably in the violent, shifting interface between the water and the land. The frog was deeply patient, completely still when observing its prey, and explosively, violently fast when it needed to strike. It was found in absolutely every brutal, tropical environment that India's new geopolitical operations were likely to require.
The name had been roundly mocked in three separate, arrogant newspaper columns penned by defense analysts who did not understand the psychology of the soldier. They did not understand that elite military culture was forged in unique names and distinct symbols, and that the choice of an indigenous, earthy name was the very first foundational institutional decision, rather than the last aesthetic one.
Rawat had not responded to the columns. He did not care about the opinions of journalists sitting in air-conditioned newsrooms in Delhi.
He had been building.
The Manduk Corps' command headquarters was established at the Chilika Lake Naval Base, in Odisha. The site had been ruthlessly selected over six highly competitive alternative locations for three specific, unforgiving tactical reasons.
First: Chilika Lake offered a brutal, unforgiving training environment that simply did not exist anywhere else on the subcontinent. It was the largest coastal lagoon in Asia—over a thousand square kilometers of treacherous shallow water, connected to the violent swell of the Bay of Bengal by a narrow, shifting mouth, and surrounded by the specific, exhausting terrain of the Odisha coast. It offered unparalleled opportunities for contested beach landing training, covert small boat operations, complex tidal navigation, and the specific, grueling amphibious skills that required thousands of hours of water-land interface practice in a controlled environment before an operational deployment.
Second: The base's immediate proximity to the Wheeler Island missile test range—the Indian military's primary, state-of-the-art integrated live-fire test facility—provided the Manduk Corps with immediate, unrestricted access to the heavy live-fire and combined-arms training environment that Rawat's lethal doctrine strictly required.
Third: The strategic geographic position on the eastern coast, directly adjacent to the Bay of Bengal, placed the Corps not only within an immediate operational radius of the Andaman and Nicobar Islands, but positioned them as a loaded gun pointed directly at the Malacca Strait and the broader Pacific theater.
The headquarters building at Chilika—a long, imposing, low-slung structure possessing the specific, brutalist utilitarian architectural character that Indian military construction produced—was completed in January 1978 and had been fully operational since February.
The headquarters building was a masterclass in operational efficiency, containing:
The Commandant General's Office: Rawat's personal command center. It was the largest room on the first floor, austere and intimidating. It contained a heavy steel desk, two stiff chairs for visitors, a massive, floor-to-ceiling wall of geopolitical maritime maps, and a framed reproduction of the first page of the Manduk foundational doctrine document.The Operations Directorate: The pulsing nerve center of the headquarters. Staffed by seventeen hand-picked combat officers and thirty support personnel, it was responsible for global operational planning, ruthless exercise design, instantaneous readiness assessment, and the specific administrative intelligence of tracking exactly what kinetic violence his units were capable of unleashing on any given morning.The Doctrine and Training Directorate: In Rawat's specific institutional philosophy, this was the most critical room in the building. An amphibious force that trained wrong trained wrong for years before it discovered what failure looked like in the blood and surf of an actual operation. Staffed by eight officers selected for sheer intellectual rigor alongside their military lethality, their sole task was the continuous, unsparing evolution, testing, and revision of the Manduk operational doctrine.The Logistics Directorate: A sprawling department whose immense complexity reflected the specific, agonizing challenge of sustaining a heavily armed force that lived between the land and the sea, whose supply chain had to seamlessly accommodate the physics of both.The Intelligence Directorate: Small, hyper-focused, and specifically oriented toward the global littoral edge. They mapped the beaches, the port infrastructure, the tidal patterns, and the coastal geography of absolutely every hostile and friendly nation within the vast operational radius that India's new superpower status demanded.The Medical Directorate: Tasked with the specific, grueling challenge of managing the health, trauma care, and combat readiness of a force that permanently trained in freezing water, toxic mud, and the specific, lethal disease environment of coastal and tropical operations.
But it was the final department—The Finance Directorate—that represented the most significant, hard-fought political achievement of the entire Manduk constituting ordinance.
It was the institutional manifestation of Rawat's greatest victory in New Delhi: the establishment of a completely separate, independent budget line for the Manduk Corps. It was not a subsidiary item tucked into the Navy's ledgers, nor a line item begging for scraps from the Army estimates. It was a distinct, sovereign parliamentary appropriation.
The separate budget was the absolute institutional bedrock that made everything else possible.
Rawat had fought for it specifically, violently, and at exhaustive length in the halls of the Defence Ministry.
The conventional, arrogant assumption among the Indian defense bureaucracy had been that an amphibious force should obviously be funded as a minor component of the Navy. The Navy possessed the ships, the bureaucrats argued, therefore the Navy possessed the institutional relationship with the maritime domain. Therefore, an amphibious force was merely a naval logistical function, and should naturally fall under naval command and be funded entirely through the naval budget.
Rawat had argued against this bureaucratic suffocation for six agonizing months before the Manduk Raising Ordinance was even drafted.
During the final, decisive meeting in South Block, Rawat had stood across the table from a deeply skeptical Joint Secretary of Defence.
"The United States Marine Corps is not funded through the US Navy, Secretary," Rawat had stated, his voice ringing with absolute, unyielding authority. "It has its own, sovereign congressional appropriation. And they do not do this because the Marines are inherently better than the Navy, or more important than the Navy. They do it because the Marines are fundamentally different from the Navy. They have entirely different tactical needs and completely different operational requirements."
Rawat had leaned over the polished table, locking eyes with the bureaucrat. "A fighting force that exists as a budget sub-item of another service is a force whose priorities are permanently held hostage by that service's institutional arrogance. If we fall under the Navy, we will never get the specialized landing craft we need, because the Navy will prioritize deep-water frigates. The Manduk Corps must be able to buy exactly what the Manduk Corps needs to slaughter the enemy on the beach, not what the Navy is occasionally willing to spare from its surplus."
The Defence Ministry's Joint Secretary, adjusting his glasses, had sighed heavily. "General Rawat, creating an entirely separate procurement pipeline and a sovereign budget line outside the established tri-service structure... this is administratively incredibly complex."
Rawat had stared at the man with the cold, dead eyes of a combat veteran who had watched men bleed out in the jungles of Burma because bureaucrats were afraid of complexity.
"Yes, Secretary," Rawat had replied, his voice dropping to a dangerous whisper. "So is storming a hostile, fortified beach under heavy artillery fire. Fund my command."
The separate budget line had been established the very next week. The five Project 90 ships of the Indian Navy's amphibious fleet were not merely vessels; they were the sprawling, floating physical infrastructure upon which the entire Manduk doctrine was to be executed. They were the steel beasts designed to carry the wrath of a rising superpower across the oceans.
They had been pressed into service starting in 1976. The first two, INS Airavata and INS Varuna, were completed and launched that year, while the remaining three were commissioned rapidly through the aggressive naval expansion of 1977. By May 1978, all five were fully operational. Each was a staggering 6,200 tonnes of displacement, specifically engineered to embark a lethal landing force of approximately 850 fully equipped Manduks, alongside their supporting heavy weapons, armored vehicles, and logistical supplies. They were designed to deliver that force to any hostile shore on the globe through a coordinated combination of landing craft and the massive, floodable dock well built into the vessel's aft section.
INS Airavata — the lead ship, the flagship, named for the legendary white elephant of Indian mythology, the mount of Indra, the unstoppable vehicle of celestial authority.
INS Varuna — the second ship, named for the ancient sovereign of the seas, the god of water and absolute cosmic order.
INS Sindhu — the third ship, named for the mighty Indus River, the very water that had given the republic its name, the cradle of civilization.
INS Bhairava — the fourth ship, named for the fearsome, annihilating aspect of Shiva, the destroyer-protector, the ultimate guardian of boundaries.
INS Makara — the fifth ship, named for the mythical sea-creature, the vehicle of the river goddess Ganga, the apex predator that thrived perfectly between the river and the sea.
Captain Rajan Nair commanded INS Airavata. He was forty-two years old, a native of Cochin, and a ship handler of extraordinary, almost instinctual skill. He had been hand-selected for the Airavata command specifically because the Project 90 class required a captain deeply comfortable with the specific, agonizing awkwardness of an amphibious assault ship. It was larger and more cumbersome than a sleek frigate, and vastly slower than anything in the blue-water attack fleet. It was explicitly configured to push dangerously close to the water's edge and sit there, highly exposed, to put troops ashore, rather than dancing and fighting in the safety of the open ocean.
The required skills were fundamentally different. The psychological comfort with extreme vulnerability was different. An attack ship captain survived by moving; an amphibious ship captain had to possess the iron nerve to hold a stationary position under potential fire just long enough to disgorge a landing force. It required a man who could look at a threat radar and refuse to flinch.
Nair had exactly the right psychology. He possessed nerves of absolute steel.
He also had, by May 1978, eighteen months of hands-on experience operating the Airavata with the specific, unshakeable conviction that the massive ship was an excellent platform for doing something that nobody in the Indian military had yet fully worked out how to do perfectly.
The ship was ready.
But the question of whether the force was ready was the brutal, unsparing question that Exercise Sagar Yuddh was specifically designed to answer.
Exercise Sagar Yuddh — Naval War — had been meticulously, aggressively planned for eighteen months.
The planning had been conducted simultaneously by the Manduk Corps' Operations Directorate and the Eastern Fleet's Amphibious Squadron, the Naval formation strictly responsible for providing the ships, the heavy naval gunfire support, the air coordination, and the overarching command authority that amphibious operations fundamentally required from the sea.
However, the planning phase had revealed, long before the exercise was actually conducted, the very first category of systemic, bureaucratic friction that the live-fire exercise would ultimately confirm.
The two distinct planning staffs had been operating using entirely different planning horizons, different institutional terminologies, and deeply conflicting assumptions about who was actually in charge of what.
The Manduk Corps doctrine specified a unified, seamless amphibious command structure. In this framework, the Amphibious Task Force Commander — a Naval flag officer — was the overall theater commander from embarkation up to the exact moment the landing force was firmly established ashore. At that precise moment, absolute operational command passed to the Landing Force Commander — a Manduk general officer. This critical transition point was the Operational Transfer of Authority, or OTOA, which Rawat's doctrine defined with surgical, uncompromising precision.
The Eastern Fleet's planning staff, however, operated on an older, more arrogant tradition, derived from the antiquated Army-Navy joint operations doctrine that had governed planning before the Manduks even existed. In that obsolete tradition, the Naval Commander was solely responsible for getting the Army to the beach, acting like an armed ferry service, and the Army was left to figure out everything that happened after they got their boots wet. The OTOA was not a defined, actionable procedure — it was merely a vague, understood assumption.
And in military operations, an understood assumption is a guaranteed point of catastrophic failure.
This was the first problem.
The second problem was radio silence.
The Manduk Corps utilized a hyper-modern, encrypted radio communication suite that had been aggressively specified in the Manduk procurement programme and purchased accordingly. The Navy's Project 90 ships, however, were still using the standard, older naval communication suite. Both were highly competent systems independently, but they shared only approximately forty percent of their operating frequency range, and precisely none of their tactical data network architecture.
A Manduk company commander fighting ashore who desperately needed to talk to INS Airavata for fire support had to route his transmission through a relay station on the beach. That station relayed it to a dedicated naval liaison radio operator embedded with the Manduk force, who then spoke to his counterpart on the ship.
In a perfectly choreographed exercise conducted at a comfortable speed with prepared communications, this clunky chain worked. But in a violently contested environment where the relay station might be taking mortar fire and the liaison operator might be pinned down, the communication chain had three fatal points of failure before a single word reached the ship's guns.
The third problem was the landing craft.
The Project 90 ships' landing craft were strictly naval assets, crewed by naval personnel, and operated according to rigid naval doctrine. Naval doctrine was fundamentally about moving logistics — getting things from ship to shore efficiently and safely. But the Manduk doctrine required landing craft to do something vastly more violent and precise. They had to deliver armed soldiers to a specific coordinate on a highly specific timeline, perfectly synchronized with a suppressing fire plan designed to create a fleeting window of opportunity, and they had to be prepared to recover those soldiers under fire if the assault collapsed.
The timing, in short, was a lethal military function, not a safe logistical one.
The naval landing craft crews were excellent at timing cargo deliveries. They had not been aggressively trained in timing assault deliveries under simulated fire, which required processing wildly different information — enemy fire positions, friendly suppression schedules, planned smoke screens, and specific visual beach markers — and making split-second tactical decisions when the plan inevitably failed upon contact with reality.
The fourth problem was the beach itself.
Wheeler Island, located off the Odisha coast, had been selected as the designated exercise landing site. On paper, it was not a particularly difficult beach. It possessed a moderate surf, no significant natural obstacles, and landing zones wide enough to comfortably accommodate multiple craft simultaneously. The beach reconnaissance had been executed by a specialized Manduk reconnaissance team two weeks prior to the exercise, and the team had submitted a detailed report describing the beach's physical characteristics with perfect accuracy.
What the report had not described, simply because the reconnaissance team had not yet been specifically trained to holistically assess it, was the precise tidal pattern at the exact time of the planned landing. The tidal pattern at Wheeler Island in May, at the planned H-hour, meant that the specific beach gradient would produce conditions in which the heavy landing craft would be violently grounding approximately thirty meters further from the dry beach than the reconnaissance report's distance tables had implied.
Thirty meters.
At a casual walking pace of one meter per second under normal conditions, thirty meters was a mere thirty seconds. But under simulated enemy machine-gun fire, weighed down by heavy body armor, carrying weapons, ammunition, and specialized equipment, while fighting through a pounding surf zone, thirty meters equated to two agonizing, exhausting minutes.
In an opposed amphibious landing, two extra minutes trapped in the surf zone was not a minor inconvenience. It was the specific mathematical quantification of a slaughter.
The beach reconnaissance team had not been provided the tidal tables. Or rather, the tide tables were technically buried somewhere in the massive exercise planning package as a standard supplementary document, but nobody — not the Manduk planning staff, and certainly not the Naval planning staff — had bothered to specifically, mathematically calculate the exact landing craft grounding point at H-hour on May 14th.
Exercise Sagar Yuddh officially commenced at 0430 hours on May 14th.
The full order of battle was a testament to India's growing kinetic reach:
Landing Force: 1st Manduk Brigade, comprising two heavily armed infantry battalions, one specialized support battalion, one reconnaissance company, one signals company, and one combat engineer company — approximately 1,800 Manduks.
Naval Surface Group: INS Airavata (lead ship, Flag), INS Varuna, and INS Sindhu, with the landing force embarked and their respective landing craft complements fueled and loaded. INS Bhairava and INS Makara held position in a logistical support role.
Naval Fire Support: The guided-missile destroyer INS Mysore and the frigate INS Nilgiri, strategically positioned to provide devastating naval gunfire support to the landing elements from their respective offshore fire positions.
Air Coordination: Four IAF helicopters from the Search and Rescue flight based at Bhubaneswar, tasked purely for casualty evacuation and vertical resupply — not for attack.
The glaring absence of dedicated attack helicopters in the exercise order of battle was the most significant, painful gap in the exercise's design. It was a gap that Rawat had explicitly identified during the planning phases. He had accepted it only because seamless attack helicopter integration was a highly advanced capability that the Manduk Corps simply could not yet afford to train for. Trying to force integration before the foundational, gritty amphibious skills were solidly consolidated would have added a layer of distracting complexity that obscured the fundamental problems on the beach.
He would later spend long nights thinking about whether accepting that gap had been the correct decision.
Colonel Sukhwant Singh Dhaliwal, the officer commanding the 1st Manduk Brigade, was a towering, broad-shouldered man from Punjab who had spent fourteen brutal years in the Sikh Light Infantry before transferring his commission to the Manduk Corps during its raising year. He was thirty-eight years old, and he possessed a specific, invaluable psychological quality that Rawat had instantly identified during the selection process. Over the previous fourteen months of building the 1st Brigade, Dhaliwal had confirmed it: he was utterly, coldly comfortable with uncertainty in a way that infantry officers trained in the conventional, rigid army typically were not.
Conventional Indian Army infantry doctrine was entirely about reducing uncertainty through exhaustive planning, endless rehearsal, and the strict, unyielding application of proven procedures. Dhaliwal understood this conventional wisdom perfectly and was highly capable of executing it. But he also understood, from the unique combination of his hard infantry experience and the eighteen months he had spent mastering the specific, chaotic character of amphibious operations, that beach assaults produced an irreducible, terrifying level of uncertainty.
The sea itself was a massive uncertainty generator. The surf was unpredictable. And the enemy, waiting entrenched on the beach with the massive advantage of knowing the ground, owned the initiative. Dhaliwal knew that the force that was more psychologically comfortable with chaos than the enemy was the force that won.
He had briefed his battalion commanders the previous evening, deep in the steel-walled operations center of INS Airavata, with the massive ship already underway and the distant, twinkling lights of the Odisha coast barely visible on the horizon.
*"The plan is as solid as we can mathematically make it,"* Dhaliwal had told them, leaning over the tactical map. *"But make no mistake: the plan is not going to survive first contact with the surf, let alone the enemy. Your job, when the plan inevitably fails, is not to stop your men in the water and wait for my instructions over the radio. Your job is to understand the absolute objective, assess your current, localized situation, make the violent decision that best serves the objective, and execute that decision relentlessly while simultaneously communicating what you have done to the people who need to know."*
He had locked eyes with his officers. *"This is the specific, decisive skill that conventional infantry training actively suppresses, because conventional operations happen on solid ground that generals can safely observe from distant hills. We are going to land on a violently shifting beach that I cannot see from where I will be standing when you are hitting the sand. You are the operational commanders on that beach. Command."*
The battalion commanders — Lieutenant Colonel Arjun Menon of the 1st Manduk Infantry Battalion, and Lieutenant Colonel Paramjeet Singh of the 2nd Manduk Infantry Battalion — had nodded with the specific, tight-lipped expression of officers who completely understood what they were being told, but were not entirely certain they were fully prepared for the reality of executing it.
Paramjeet Singh was the more technically experienced of the two. He was thirty-six, a former rising star in the Army's Corps of Signals before joining the Manduks, and he brought a communications officer's specific, paranoid understanding of the information architecture of combat. He didn't just care about the tactical picture; he cared about how that picture was assembled, transmitted, received, and exactly how it could be corrupted at each fragile stage.
He had asked Dhaliwal the single most important question in the room during the briefing.
*"Colonel,"* Paramjeet had said, tapping the map. *"When the naval gunfire lifts — when the destroyer's fire plan transitions from pre-landing suppression to final protective fires to allow us to cross the beach — exactly how do we confirm the lift? What is the visual or auditory signal? What is the fail-safe procedure if we are in the water and we don't receive that signal?"*
Dhaliwal had looked at him, recognizing the lethal validity of the question.
He had turned to look at the naval liaison officer in the room, Lieutenant Commander Vikram Mehta. Mehta was twenty-nine years old, sharp, and served as the designated, vital communication bridge between the Manduk landing force and the Naval support group offshore.
*"The coordinated fire plan specifically dictates H-minus-two for the final lift of all suppressive fires,"* Mehta had answered confidently. *"The lift is strictly timed on the ship's synchronized clocks."*
Paramjeet's eyes had narrowed. *"So we simply count down to H-minus-two on our watches, and blindly assume the destroyer's guns have stopped firing at the beach we are about to step onto?"*
*"The coordination procedure specifies—"* Mehta started.
*"The coordination procedure specifies that we count to H-minus-two and blindly assume the five-inch guns have stopped,"* Paramjeet interrupted, his voice edged with the cold reality of a man whose troops would be in the blast radius.
Mehta had hesitated. *"Effectively, yes."*
*"And if the massive naval guns have not actually stopped because a timer coordination failed, or a watch is unsynchronized?"* Paramjeet pressed relentlessly.
*"Then the landing force immediately communicates to the fire support coordinator through the naval liaison radio to call a cease-fire,"* Mehta replied.
*"Through the relay station on the beach,"* Paramjeet stated flatly. *"The relay station that is not established yet, because my men and the radio operators are currently wading through chest-deep surf under simulated machine-gun fire."*
Mehta had stared at him, the terrifying gap in the operational logic suddenly dawning on him. *"Yes,"* he admitted after a long, painful pause.
Paramjeet had slowly turned his gaze back to Dhaliwal.
Dhaliwal had not said a word. He had simply picked up his pen and made a stark, heavy note on his operational pad.
The exercise's very first catastrophic problem manifested in the dark, at exactly 0512 hours.
The landing craft carrying the forward reconnaissance element — four fast, highly maneuverable Zodiac rigid inflatable boats packed with the elite Manduk reconnaissance company — had departed the well deck of INS Airavata at 0445, exactly forty-five minutes before H-hour. The reconnaissance company's vital task was to reach the beach well ahead of the main, heavy landing force, confirm the physical landing zone conditions, mark the specific beach sectors with infrared strobes and colored smoke for the incoming landing craft, and aggressively suppress any localized beach obstacles or threat positions with their organic weapons.
The reconnaissance company departed flawlessly on schedule, disappearing into the pitch-black ocean.
At 0512, the radio cracked to life. The senior reconnaissance officer, a seasoned Major named Shivaprakash from Karnataka, transmitted urgently over the net: *"Beach Zone One impassable. Encountering heavy rock bar not on chart. Redirecting force to Zone Two."*
Zone One was the primary, ideal landing zone. Zone Two was the designated alternate. But Zone Two was drastically narrower, possessed significantly higher and more violent surf, and was located two kilometers south of Zone One, shifting the entire axis of the attack.
The fatal error lay in the paper. The chart used by the naval planning staff was the standard, officially issued nautical chart of the Wheeler Island approach. The chart's rock notation was perfectly accurate to the survey date.
The survey date, however, was 1962.
In sixteen years, a submerged bar of rocks that had been safely navigable at high tide in 1962 had slowly transformed, through the relentless, specific geological processes of coastal accretion, into a jagged, hull-tearing feature. It was a feature that the reconnaissance company's Zodiacs slammed into at 0512, in dangerous conditions exactly two hours before high tide.
Shivaprakash professionally transmitted the beach condition report, pivoted his team to mark Zone Two in the dark, but critically, he did not transmit his assessment of the overall physical situation at the new beach.
On the bridge of INS Airavata, the exercise coordinator — Commander Ramesha Babu, a strict naval officer serving as the primary exercise umpire — received the "Zone One impassable" report. He waited for the follow-up communication from INS Airavata's command post that would officially direct the massive fleet of heavy landing craft to pivot to Zone Two.
The follow-up communication was correctly routed through the ship's internal communication system down to the echoing, diesel-choked landing craft bay, where the landing craft crew commanders were conducting their final pre-launch checks. The message was received by the Landing Craft Commander — a veteran Chief Petty Officer named Ramesh Pillai — and acknowledged.
Pillai immediately redirected his craft. But he did not transmit to the infantry that he had redirected his craft. He transmitted the change of coordinates to his platoon of craft strictly on the closed naval craft communication net.
Colonel Dhaliwal, Lieutenant Colonel Menon, and Lieutenant Colonel Paramjeet Singh, standing shoulder-to-shoulder with their heavily armed troops in the cramped, pitching bellies of the landing craft, were entirely isolated on the Manduk tactical infantry net.
They had received the original Zone One marking instructions.
Their heavy craft had already begun moving out of the well deck, blindly following the naval lead craft into the darkness before dawn.
The very first time the Manduk infantry commanders realized that the landing zone had fundamentally changed was when the ramps of the landing craft unexpectedly dropped into the violent surf in a location they were explicitly not supposed to be.
Dhaliwal's landing craft violently grounded on a submerged sandbar at 0559, exactly one minute before H-hour.
The heavy steel ramp slammed down into the ocean. Dhaliwal charged forward, stepping off the ramp expecting water around his shins.
He plunged into the dark water all the way up to his chest.
The freezing, turbulent shock of the Bay of Bengal hit him instantly. He was absolutely not expecting chest-deep water.
The landing zone schematics in the exercise plan had clearly shown a gradual, forgiving beach gradient with a surf zone of approximately ten meters from the safe grounding point to the dry beach.
Dhaliwal wiped the saltwater from his eyes and looked forward. He was seventy meters from the dry beach. The surf zone was not ten meters — it was seventy meters of violent, churning, thigh-crushing water. The specific tidal conditions at H-hour on May 14th at the alternate Zone Two of Wheeler Island had predictably produced a grounding point that stranded the heavy craft far out from the sand.
He stood perfectly still in the churning water for approximately three seconds. It was exactly the time it took his brain to process the terrifying specific information that the chaotic environment was providing him.
Then, he did exactly what the aggressive Manduk doctrine demanded of a Landing Force Commander who encountered a catastrophic reality that did not match the pristine paper plan: he assessed, he decided, and he acted violently.
He assessed: The landing is seventy meters short. The heavily burdened troops will take four to six agonizing minutes to fight through seventy meters of water in full combat kit. The naval fire plan lifted, on schedule, at H-minus-two. The hostile beach has been unsuppressed for over eight minutes. Any defensive machine-gun position on that beach has had eight full minutes to recover from the naval bombardment, reload, and lock onto our coordinates.
He decided: Get every single man ashore as fast as humanly possible. Abandon the staggered wave approach. Establish a violent fire base on the dry beach to cover the follow-on waves before we are slaughtered in the water.
He acted. He lunged forward, beginning his agonizing, chest-deep trudge toward the distant beach, bringing his waterproofed tactical handset to his mouth, transmitting simultaneously to his battalion commanders over the roar of the surf.
What he transmitted was sharp, jagged, and absolute: *"Zone Two. Deep surf. Move fast. The beach is quiet. Move!"*
What he received in return from Menon's battalion, which had grounded thirty seconds later at a slightly different, equally terrible point: *"Understood. Moving."*
What he received from Paramjeet Singh's battalion was a terrifying silence.
The silence stretched for forty-five agonizing seconds. It was the exact time it took Paramjeet to physically fight his way off the submerged ramp of his pitching landing craft, secure his footing in the churning tide, reach a position where his radioman wasn't submerged, and manage his company command net to transmit.
Finally, the radio crackled: *"2 Battalion ashore. Zone Two. South end. Pushing through heavy surf. Moving."*
Dhaliwal was already dragging himself onto the dry beach.
He stood on the dark, wet sand of Wheeler Island at exactly 0603 and stared at the unfolding tactical nightmare.
The situation was bleak: approximately 220 troops of the 1st Manduk Infantry Battalion's lead assault company were ashore, strung out wildly across 120 meters of unforgiving surf zone. They were emerging from the dark water in varying states of disorientation and equipment saturation. The violent wave action and the exhausting chest-deep water transit had produced the specific, dangerous conditions of a force that had physically completed the crossing, but had not yet physiologically and psychologically transitioned from the panicked transit state into a lethal combat state. Men were violently shaking saltwater from the actions of their rifles. Men were desperately checking that their radio sealed bags had actually held. Men were frantically trying to locate their squad leaders in the gloom.
And then, Dhaliwal looked out at the ocean. The next wave of landing craft was already visible on the horizon, gunning their engines, coming in fast.
The next wave was the heavy support elements — the crew-served weapons, the massive crates of additional ammunition, the bulky combat engineer stores. The support elements had been strictly planned to arrive at H-plus-fifteen, giving the infantry time to secure the beachhead.
They were arriving at H-plus-three.
The aggressive surf conditions and the early grounding had compressed the timeline, making the initial landing faster than the rigid naval plan had assumed.
The vulnerable support elements were arriving before the lead infantry company had even established a defensive perimeter on the beach.
This was the second significant exercise event. It was the moment the plan shattered completely.
What occurred on the sands of Wheeler Island between 0603 and 1200 was the specific kind of chaotic, improvised, intensely professionally managed near-disaster that brilliant military exercises produced when they were explicitly designed to find the bleeding edge of a force's capability, rather than to safely demonstrate that capability at a comfortable, staged distance.
The forces ashore did not break. They aggressively organized themselves under simulated fire. The beach was violently secured. The inland tactical objectives were assaulted and taken. The Manduk flag went up at Point Bakul — the designated, heavily fortified exercise end-state position — at exactly 1127 hours.
They were twenty-seven minutes behind schedule.
The landing was not a pristine success. The landing was not a catastrophic failure. The landing was the brutal, unvarnished first time that the Manduk Corps had thrown a full brigade ashore in an opposed, simulated combat exercise and successfully demonstrated that the force could, despite massive planning failures and execution errors, forcefully achieve the tactical objective.
This was the absolute minimum that was required of them to justify their existence.
The maximum that was required of them, however, was the subject of the brutal post-exercise review.
The post-exercise review convened at 1400 hours on May 14th, deep inside the secure exercise command post at Visakhapatnam, to which the senior exercise leadership had rapidly transferred by helicopter while the exhausted landing force was still being re-embarked onto the ships.
The room was a stark, windowless rectangle of the kind that military command posts universally produced: heavy tables arranged in a rigid U shape, massive tactical maps plastered on every inch of the walls, and the specific, heavy atmospheric quality of a room that had been fully operational for twenty consecutive hours. Every single officer present was physically exhausted; several of them were still damp from the surf.
The participants were the architects of the assault: Major General Rawat, Colonel Dhaliwal, Lieutenant Colonel Menon, Lieutenant Colonel Paramjeet Singh, Captain Nair (commanding INS Airavata), Commander Babu (the exercise coordinator), Lieutenant Commander Mehta (naval liaison), Major Prakash Ramachandran (the brilliant intelligence officer from Manduk HQ who had been coldly monitoring the exercise from the command post), the commanding officers of INS Bhairava and INS Makara, the CO of the Manduk signals company, the CO of the Manduk reconnaissance company, and a cadre of senior representatives from the Eastern Fleet's staff.
Vice Admiral Subramaniam Krishnan, Flag Officer Commanding Eastern Fleet, was present in a highly observant capacity. He was fifty-eight years old, a towering figure in naval circles, and had been the flag officer directly responsible for the Project 90 ships since their commissioning. His relationship to the exercise was complex and politically sensitive: he was the Navy's supreme senior officer in the exercise geography, yet the Manduk Corps was explicitly not under his command. The Project 90 ships were Navy assets that had been tasked to the exercise under a delicate joint operations order. It specified a command structure that both he and Rawat had agreed to in principle, but that had, in bloody practice, produced several of the near-fatal coordination failures the exercise had just violently demonstrated.
He sat quietly at the side of the U-shaped table, distinctly not at the head. The head of the table belonged exclusively to Rawat.
Rawat opened the review at exactly 1400 with a stark, blunt statement that the participants had absolutely not expected.
"Before we go through the chronology of errors," Rawat began, his voice commanding absolute silence in the room, "I want to say something that I believe is the most critical context for everything we are about to tear apart in the next forty-eight hours."
He leaned forward, resting his hands on the table.
"This exercise was designed to fail," Rawat stated flatly. "Not to fail by intention — I did not deliberately engineer any of the specific, near-catastrophic failures that occurred on that beach today. But it was designed to fail by nature. It was designed to operate at the absolute, bleeding edge of the Manduk Corps' current kinetic capability, rather than safely within a comfortable distance from it. An exercise that a military unit passes easily teaches us absolutely nothing except how to congratulate ourselves. An exercise that a unit fails comprehensively teaches demoralization without any actual learning. But an exercise that a unit nearly fails... an exercise that ruthlessly exposes every single gap, every assumption, and every weakness, while still demonstrating that the fundamental, lethal capability exists to push through..."
Rawat's eyes swept the room, fierce and proud. "...This is the exercise that teaches an empire how to fight."
He let the words sink in.
"We put 1,800 heavily armed soldiers ashore on a defended beach in adverse, unmapped tidal conditions," Rawat recounted, checking off the obstacles. "We did it with severe communications failures, arrogant planning errors, and dangerous coordination breakdowns across every single operational dimension. And this force still took Point Bakul. Twenty-seven minutes behind schedule, but you took it. That is our foundation. What we are about to spend two days doing is aggressively understanding the steel structure that needs to be built upon that foundation."
He pointed a finger at the center of the table. "I am going to ask each of you to be specific. Not general — ruthlessly specific. Saying 'the communications need improvement' is an observation from a politician, and it produces nothing. Stating 'The transition from naval ship communications to landing force tactical communications produced a fatal nine-minute gap in command and control between H-minus-thirty and H-plus-twenty because the relay station at Zone Two was not established before the lead company landed' — that is an observation that produces lethality. Specificity is the discipline."
"We will work through the exercise chronologically, from the moment the planning process began to the end-state," Rawat declared. "We will identify specific failure points, their specific root causes, and specific, actionable remediation actions. We will not attribute blame in this room. We will attribute responsibility, which is fundamentally different. Blame is about crying over the past. Responsibility is about dictating what happens next."
Rawat looked at an empty chair near the end of the table. He turned his gaze to Lieutenant Commander Mehta.
"Where is Major Shivaprakash?" Rawat demanded.
"The reconnaissance company is still completing the heavy re-embarkation protocols on the Varuna, sir," Mehta answered quickly.
"Get him here immediately," Rawat ordered, his tone brokering no delay. "He has the most important, critical testimony of anyone in this room."
The chronological review began at 1415, and the depth of the inquiry was so exhaustive that they did not even reach the analysis of the beach landing itself until the following morning.
This was not because the planning process had taken that long in execution — the planning process had taken four months. It was because Rawat's specific, unsparing method produced a density of findings that exposed the rot in their shared assumptions.
The very first finding was about the fatal chart.
Commander Babu stood and presented the chart discrepancy: the 1962 nautical chart confidently used by the naval planning staff against the current, jagged reality of Zone One's approach as violently surveyed by the reconnaissance company's Zodiacs. He presented the specific rock notation. He presented the tidal table for May 14th. He presented exactly what a competent navigation officer who had cross-referenced both documents would have immediately concluded.
Rawat looked at the naval contingent. "Who is specifically responsible for verifying that the operational chart is current?"
"In the existing Navy doctrine, General, the naval planning staff is responsible for the nautical chart," Mehta answered formally.
"In the existing Navy doctrine," Rawat repeated, emphasizing the obsolete word. "What does the new Manduk doctrine say?"
There was a heavy, uncomfortable pause in the room.
"The new doctrine does not yet specify who is responsible for chart currency," Rawat answered his own question, exposing his own structural flaw. "This is a massive gap. It will be closed immediately. The Manduk planning staff will henceforth include a dedicated hydrographic element. They will be explicitly responsible for cross-checking all nautical charts used in amphibious planning against the most current surveys available globally, and for flagging any charts that are more than ten years old for physical verification before any operational use."
Rawat turned to Captain Nair. "What is the actual status of the Indian Navy's chart updating programme for the coastal approaches in the Andaman basin?"
"The hydrographic survey is currently underway, General," Nair replied carefully. "However, the Navy's priority is deep-water passages for the submarine and destroyer fleets. The coastal survey — the extremely shallow approaches relevant to amphibious operations — is simply not the priority for the surveyor general."
"It will be," Rawat stated with quiet, absolute authority. "I will raise this directly with the Chief of Naval Staff in Delhi. The shallow coastal approach surveys are as operationally critical for our amphibious power projection as the deep-water surveys are for your surface ship navigation. Without them, we are driving blind into reefs."
He nodded to Babu. "Continue."
The second finding was about the tidal planning disaster.
Major Prakash Ramachandran presented this one. He was thirty-two years old, a brilliant analyst from Trivandrum who had eagerly joined the Manduk Corps after an exemplary background in deep-cover Army intelligence. He had not been wet on the beach; he had been coldly monitoring the entire catastrophe unfold from the digital displays in the command post. His view of the exercise was the clinical view of an intelligence officer watching the plan's execution shatter against the plan's intent.
He had, during the previous afternoon, independently calculated the exact landing craft grounding point at Zone Two at H-hour on May 14th. He had used the exercise tidal tables that were included in the planning package—tables that had miraculously not been applied to Zone Two simply because Zone Two was deemed the 'alternate' landing zone.
"At H-hour on May 14th at Zone Two," Prakash began, his voice calm and precise, "the physical grounding point was exactly sixty-eight meters from the dry beach at the primary marked landing point. The operational plan comfortably assumed a surf zone of ten to fifteen meters. The actual surf zone your men hit was sixty-eight meters."
He tapped his laser pointer against the screen. "The calculation is fundamentally straightforward. The tide table is a publicly available document. The beach gradient is mathematically derivable from the chart. The entire calculation takes twelve minutes for a competent officer."
Prakash looked around the U-shaped table. "This calculation was not done for Zone Two, simply because Zone Two was labeled the alternate. The exhaustive tidal planning was only done for Zone One. When the force pivoted, they pivoted into mathematical blindness."
"The tidal planning for every exercise landing zone — primary, alternate, and contingency — will be conducted as a mandatory, non-negotiable planning step," Rawat decreed, establishing the new law. "The tidal conditions at H-hour at every single potential landing point on a hostile shore are a fundamental planning requirement, not an optional enhancement."
He looked back at Mehta. "What is the name of the planning officer who was responsible for tidal coordination in this specific exercise?"
"Lieutenant Sharma, sir. Naval planning staff," Mehta answered reluctantly.
"Lieutenant Sharma does not bear responsibility for this failure in isolation," Rawat said, completely removing the sting of individual blame. "The established procedure did not require him to do the exhaustive tidal planning for alternate zones. The procedure was lazy. The procedure was wrong. The procedure will be permanently changed. Lieutenant Sharma will be personally shown the change and will be tasked to implement it flawlessly in the next exercise planning cycle."
Rawat looked at his officers, cementing the philosophy. "Note that. It is a procedure failure, not a personnel failure. The response is a severe procedure change, not a personnel action."
The analysis of the communication failure took three exhausting hours.
Mehta presented the complex communication architecture as it was flawlessly drawn on paper, and the chaotic communication architecture as it was violently executed in reality. The massive gap between the two was the specific technical and doctrinal nightmare of how the highly advanced Manduk Corps' tactical communications integrated with the older Naval communications.
Rawat interrupted in the middle of a dense technical schematic. "Let me ask a fundamental, overriding question. Is it actually possible to seamlessly integrate these two completely different systems with our current hardware?"
"It is technically possible, sir," Mehta answered. "But it is expensive. It requires the procurement of dedicated radio gateway equipment to be installed in the naval liaison station to translate the frequencies and encryption."
Rawat looked down the table at the commanding officer of the Manduk signals company, Major Krishnaswami. Krishnaswami had been sitting with the specific, intensely frustrated expression of a highly trained signals officer being forced to listen to a communications analysis being conducted by infantry and naval officers.
"Major Krishnaswami," Rawat prompted. "What is your unvarnished assessment?"
"The gateway equipment exists on the market, sir," Krishnaswami said immediately. "The British use a highly advanced version of this system to seamlessly bridge their naval destroyers and Royal Marine tactical nets. The equipment is commercial off-the-shelf, heavily modified for military encryption. The cost per installation is approximately forty-five lakhs."
"For a full brigade deployment, how many installations do we require?" Rawat asked, his pen ready.
"One per ship in the amphibious group, one per Manduk headquarters element, and one at each infantry company level," Krishnaswami calculated instantly. "For a full brigade landing, that is five ship installations, one brigade HQ, four battalion HQs, and approximately twelve company installations. We are looking at twenty-two installations total, General."
"The total cost."
"Approximately nine point nine crore for the physical gateway equipment, sir. Annual maintenance, encryption upgrades, and training would be approximately one point two crore."
Rawat smoothly wrote the number down on his pad. He didn't blink at the price tag. India was no longer counting pennies for its defense.
"This is an immediate procurement requirement," Rawat ordered. "The Manduk Corps will submit a classified procurement proposal for the complete radio gateway equipment suite within thirty days of this review. The proposal will include the exact technical specification, the vendor assessment, and a rapid implementation timeline."
Rawat looked around the room, his voice deathly serious. "The tactical communication failure in this exercise is the single most operationally significant failure we identified. A kinetic force that cannot communicate reliably with its massive naval support is a force that cannot be adequately supported at the most critical, vulnerable moment of the landing. This is not theoretical war-gaming — we nearly had a full battalion of soldiers trapped in the surf zone without the heavy naval gunfire suppression having lifted correctly, simply because the communication chain was broken. We were incredibly fortunate. And fortunate is not a planning category in my Corps."
Vice Admiral Krishnan spoke for the very first time in the formal review at 0840 on the second day.
He had been present throughout the grueling first day's session. He had contributed specific, vital technical naval clarifications when explicitly asked, but he had notably refrained from offering overarching assessments or observations. He had been quietly, intensely listening to the new paradigm being forged.
He spoke at 0840 because the intense discussion had finally reached the explosive question of command authority during the landing — who was actually responsible for what lethal decisions at what exact point. This was the question where the Admiral's perspective was most directly, politically relevant.
"I want to make an observation about the joint command structure that this exercise has brutally revealed as inadequate," Admiral Krishnan began, his voice commanding the absolute respect of the room. "And I want to make it with the specific, public acknowledgement that the inadequacy is entirely institutional, rather than personal."
He folded his hands on the table. "The joint operations order that governed this exercise specified an Operational Transfer of Authority at the exact point when the landing force was firmly established ashore. The precise timing of that transfer was to be determined by mutual, real-time agreement between the Amphibious Task Force Commander and the Landing Force Commander."
Krishnan looked around the table. "In practice, the Operational Transfer of Authority did not happen. It failed because there was no established, ironclad procedure for it. The two commanders — myself and General Rawat — were not collocated at the critical moment of the assault. The communication between our flagships was delayed. The landing force was actively fighting ashore and conducting kinetic operations without clear, unquestionable authority regarding who was commanding the immense combat power afloat in support."
"This is a structural, fatal failure," Krishnan admitted heavily. "The Manduk doctrine specifies the OTOA clearly. The Navy's operational orders did not incorporate the Manduk doctrine's specific OTOA procedure. The two foundational institutional documents were not harmonized."
The Admiral looked directly at Rawat.
"I am raising this not as a criticism of the Manduk doctrine, General, which I believe is tactically correct, but as a severe criticism of the Navy's arrogant failure to incorporate the Manduk doctrine into its own operational order framework. This is the Navy's institutional gap, and it is one that I will address personally, and forcefully, with the relevant directorates in Delhi."
"Thank you, Admiral," Rawat said sincerely. "I want to add to the Admiral's observation. The OTOA procedure's failure in this exercise reveals a much deeper, more complex institutional question that the Manduk Corps urgently needs to resolve. I want to raise it here because the Admiral's presence makes it possible to raise it productively, rather than as an inter-service grievance."
"Go ahead, General," Krishnan invited.
"The Manduk Corps is a new, aggressively expanding organization. Its doctrine is revolutionary for this region," Rawat stated. "The relationship between the Manduk Corps and the Indian Navy — specifically surrounding amphibious power projection — is the complicated relationship between two proud services with vastly different traditions, different cultures, and entirely different primary missions. The Navy's primary mission is achieving supremacy in the deep sea. The Manduk's primary mission is conquering the violent connection between the sea and the land. These missions are intimately related, but they are not identical."
Rawat leaned forward, referencing the history that had sparked this entire evolution.
"The United States Marine Corps resolved a bloody version of this tension over sixty years, through its specific, hard-fought institutional history. The USMC ultimately established absolute primacy over amphibious doctrine — the doctrine was Marine doctrine, not Navy doctrine. The Navy's role was strictly to deliver the Marines safely to the point where Marine doctrine could be violently applied. The result is an American organization with clear, unquestioned institutional authority over its specific operating domain."
"The Manduk Corps requires a similar, ironclad institutional clarity," Rawat argued. "Not absolute primacy — the Manduk Corps does not have sixty years of institutional history, and we cannot arrogantly claim a primacy we have not yet earned in blood. But we need clarity. The Manduk Corps' doctrine must be the governing, supreme doctrine for amphibious operations. The Navy's role in those operations — which is essential, irreplaceable, and the massive physical basis on which everything the Manduk does at sea depends — should be the flawless provision of the maritime platform, the devastating naval fire support, and the logistics from the sea. But the tactical command of the landing itself, and the operational command once ashore, must be absolutely Manduk."
Rawat let the demand hang in the air. "If the command authority remains ambiguous — if the Navy's operational orders and the Manduk doctrine specify conflicting command arrangements — every single joint exercise will reproduce the chaos we experienced yesterday."
Admiral Krishnan was quiet for a long, heavy moment. He was being asked to formally cede a massive portion of operational control to the Army-derived general sitting across from him.
"This is a conversation that needs to happen at the highest levels of the Chiefs of Staff Committee in Delhi," Krishnan finally said slowly. "I cannot legally make absolute commitments about the Navy's institutional position in amphibious operations from this room in Visakhapatnam. What I can commit to, General, is bringing this specific discussion — the command authority question — directly to the Chief of Naval Staff, accompanied by my personal, forceful recommendation that the Manduk doctrine's command framework be permanently adopted as the joint doctrine for all Indian amphibious operations."
Krishnan looked around the room, his expression grave. "I want to be brutally honest about why this matters to me far beyond the bureaucratic institutional question. We put 1,800 of our soldiers in the dark water yesterday, and they came ashore against a defended beach with inadequate, uncoordinated naval support simply because the bureaucratic command authority for delivering that support was ambiguous. That is absolutely unacceptable. The soldiers who jump into that freezing water deserve to know, with absolute certainty, that the organization has resolved the question of who is responsible for making the naval guns stop so that they can survive crossing the beach."
The room was deathly quiet. The profound respect between the two commanders had just bridged a massive inter-service divide.
"Thank you, Admiral," Rawat said, nodding deeply. "Agreed on every point."
Major Shivaprakash testified on the second morning of the review.
He was twenty-seven years old. He had been operating on the beach since 0445 the previous day. He had been soaking wet for eight straight hours, had been re-embarked on INS Varuna under grueling conditions, and had been brought to Visakhapatnam by a vibrating helicopter. He arrived in the review room at exactly 0930, his eyes hollow with exhaustion. Rawat ordered him to sit down before the young Major had even finished coming to attention.
"Tell me about Zone One, Major," Rawat ordered softly.
"We approached Zone One at planned speed in the Zodiacs, sir," Shivaprakash reported, his voice hoarse. "Exactly forty-five minutes before H-hour, as specified in the ops order. At approximately 800 meters from the beach, we encountered a massive, jagged rock bar that was absolutely not on the charts. The rocks were awash — clearly visible at the surface with the current tidal conditions. The chart showed it as navigable depth. We could not cross the bar without tearing the hulls."
"I transmitted the 'Zone One impassable' message and immediately redirected the element to Zone Two. Zone Two was the specified operational alternate. I marked Zone Two with the infrared strobes and colored smoke exactly as specified."
"Tell me about Zone Two," Rawat prompted.
"Zone Two was clear of obstacles, sir. However, the beach gradient was significantly steeper than Zone One's planned gradient. And the surf was much higher and more violent."
"The surf condition at Zone Two," Rawat pressed. "What was your exact assessment?"
"Moderate, sir. It was manageable in our Zodiacs. But I recognized it would be highly challenging for the heavy LCM landing craft."
"The LCM grounding point," Rawat said, leaning forward. "Where did you assess the LCMs would violently ground at Zone Two?"
Shivaprakash paused, realizing the trap he had fallen into on the beach.
"Further from the dry beach than Zone One's planned position, sir," Shivaprakash admitted.
"How far?"
"I estimate sixty to seventy meters, sir."
"Did you transmit this assessment to the incoming fleet?" Rawat asked, his voice deadly calm.
A heavy pause filled the room.
"No, sir," Shivaprakash said, staring straight ahead.
"Why."
"I transmitted 'Zone impassable, Zone Two marked'. I did not explicitly transmit the deep surf zone depth at Zone Two because the Zone Two beach conditions were technically within the broad exercise parameters as I understood them."
"The reconnaissance company's reporting protocol strictly specifies what critical information it transmits to the fleet," Rawat said.
"Yes, sir. Beach accessible or impassable. Zone marking confirmed. Enemy contact or absence."
"Surf zone depth," Rawat stated.
"Not in the reporting protocol, sir," Shivaprakash confirmed.
Rawat looked at him for a long time.
"The beach reconnaissance reporting protocol does not include surf zone depth as a mandatory, critical reporting item," Rawat stated, verifying the flaw.
"No, sir."
"What specific piece of information would have fundamentally changed the outcome of this exercise if it had been transmitted by you in the dark?"
Another painful pause.
"The surf zone depth at Zone Two, sir," Shivaprakash said quietly. "If that had been transmitted, Colonel Dhaliwal and the landing force could have instantly adjusted their tactical plan for the chest-deep transit."
"The beach reconnaissance reporting protocol will be heavily revised to include surf zone depth, estimated grounding point distance, comprehensive underwater obstacle assessment, and a direct beach gradient comparison to charted conditions as absolute, mandatory reporting items," Rawat dictated. "The revision will be drafted personally by Major Shivaprakash's company, in direct consultation with the doctrine directorate, within thirty days."
Rawat looked at the exhausted Major, completely removing the weight of guilt from the young officer's shoulders.
"Major Shivaprakash. You performed your mission flawlessly under the protocol you were given. The protocol was wrong. That is absolutely not your failure — it is the failure of the doctrine development process that produced the protocol. The revision is your opportunity to correct it."
Rawat offered a rare, sharp nod of approval. "Also: you rapidly redirected to Zone Two and marked it correctly in the pitch dark, fifty-five minutes before H-hour, with absolutely no prior tactical planning for Zone Two's specific, hostile conditions. And your markers held true throughout the entire chaotic landing. That was exceptional work under a very bad situation."
"Thank you, sir," Shivaprakash said, the relief evident in his posture.
The second day's afternoon session addressed the overarching question that Rawat had been systematically building toward since the review's opening: not merely the specific, tactical failures of this particular exercise, but the massive, structural gaps in the Manduk doctrine that the exercise had ruthlessly exposed.
He had explicitly asked Major Prakash Ramachandran to prepare a holistic analysis.
Prakash presented it at 1430 on the second day. His analysis was, true to his specific, razor-sharp intelligence background, both profoundly uncomfortable and vastly more useful than anything else discussed in the two days of review.
"General, Admiral, I want to present what I am defining as the 'Global Expeditionary Gap'," Prakash began, standing beside a large presentation board. "I am not offering this as a criticism of the Manduk doctrine — our doctrine is specifically designed not to be a bloated, slow copy of the USMC doctrine, and I believe that aggressive design decision is correct. We are not building a bloated administrative empire. We are building a hyper-lethal, scalable spearhead. However, I want to offer a structural assessment of where the Manduk Corps' current operational capability sits, relative to the immense global capability that our ambition requires."
Prakash looked around the room. "The Manduk foundational doctrine specifies seven core capabilities. I will brutally assess the current status of each."
"First: Beach Reconnaissance. Required capability — seamless survey of beach conditions, hydrographic data, obstacle identification, and enemy assessment to a standard sufficient to plan a massive brigade landing. Current capability — the company can physically conduct the reconnaissance. But the reporting protocol is inadequate. Furthermore, the hydrographic assessment capability does not exist organically — we are currently dependent on naval data that is not produced specifically for our kinetic operations. Gap assessment: Partial capability, with a specific, highly fixable protocol gap."
"Second: Naval Fire Support Coordination. Required capability — the landing force can independently direct heavy naval gunfire with sufficient precision and timeliness to obliterate enemy positions during the critical surf zone transit. Current capability — the communication system gap prevents real-time coordination. The fire plan is dangerously pre-planned rather than highly responsive. Gap assessment: Significant capability gap requiring immediate, heavy equipment and doctrine solutions."
"Third: Amphibious Assault Delivery. Required capability — deliver a full brigade to a defended beach in conditions up to Sea State 3, with landing craft crewing and timing that flawlessly supports the violent tactical plan. Current capability — the naval landing craft crews are excellently trained in logistics delivery, not assault delivery. The timing protocols for combat assault delivery simply do not exist. Gap assessment: Fundamental training gap in the landing craft community, which is currently a naval training requirement, not a Manduk training requirement."
Prakash paused, looking toward Admiral Krishnan.
"I want to note that this third gap is the one that is most firmly outside the Manduk Corps' direct operational control. The landing craft are naval assets, crewed by naval personnel, trained by naval institutions. The Manduk doctrine specifies exactly what the landing craft need to do in a firefight. The naval training system currently trains landing craft crews to do something entirely different. This is not a Manduk institutional failure — it is a joint institutional failure that requires an immediate, joint solution."
"Noted, Major," Krishnan said from his position at the side. "Continue."
"Fourth: Combined Arms Coordination — air, artillery, and naval fire — during the landing operation," Prakash listed. "Required capability — the landing force can perfectly coordinate simultaneous naval gunfire, attack helicopter fire, and its own organic weapons in support of the beach assault. Current capability — we possess absolutely no attack helicopter capability. We have no heavy organic artillery in the landing force. We have naval gunfire coordination that, as established, has critical, fatal gaps. Gap assessment: The Manduk Corps' combined arms capability is severely below the doctrine's minimum requirement for power projection. This is a massive resource and equipment gap, not a training gap."
"Fifth: Logistics from the Sea. Required capability — the landing force can be sustained from the Project 90 ships indefinitely, through a relentless combination of landing craft resupply and ship-to-shore logistics. Current capability — the logistics company has the excellent procedures and the training. The Project 90 ships have the massive storage and the craning capacity. The gap is purely in the chaotic small craft handover procedures in the surf. Gap assessment: Moderate gap, easily fixable through procedure development."
"Sixth: Medical Support. Required capability — the landing force can provide immediate, life-saving trauma care to casualties in the violent surf zone and during the beach assault, and rapidly evacuate casualties to shipboard surgical capability within the golden hour. Current capability — the medical company's training excellently includes surf zone casualty handling. The evacuation route to the ship's surgical team is clearly defined. The gap is in mass casualty management when the catastrophic casualty rate exceeds the company's handling capacity. Gap assessment: Capability exists for moderate casualty events. Mass casualty capability is dangerously inadequate for a near-peer conflict."
"Seventh: Command and Control. Required capability — the Landing Force Commander can confidently maintain continuous, real-time situational awareness of all units from embarkation through objective. Current capability — the command and control architecture is functioning brilliantly within the landing force itself, but the vital interface with the naval command is not. The OTOA procedure is completely un-implemented. Gap assessment: Significant gap that has been identified and is currently being addressed through the institutional process the Admiral has committed to."
Prakash looked up from his notes, addressing the generals.
"The summary assessment is this: The Manduk Corps has successfully demonstrated the raw, foundational capability to conduct amphibious operations and to violently achieve tactical objectives under highly adverse conditions. The exercise has revealed five specific, glaring gaps. Two are within the Manduk Corps' direct control to address. Two are joint institutional questions requiring immediate Navy cooperation. And one is a massive resource and equipment gap requiring a heavy budget allocation."
"The Manduk Corps," Prakash concluded, "is approximately eighteen months from being fully capable at its current planned force size."
"If every single gap we have identified is aggressively addressed on the strict timeline we are about to specify," Rawat clarified.
"Yes, sir," Prakash agreed.
"What is the operational risk if the gaps are only addressed partially?" Rawat asked, wanting it on the record.
"If the communication gap is not addressed — the radio gateway equipment — the Corps can physically conduct amphibious operations, but cannot be adequately supported by naval fires during the critical landing phase," Prakash warned. "This is an operational risk that I would characterize as unacceptably high for a contested landing against a competent military. It is a suicide run."
"If the landing craft assault delivery training is not addressed, the Manduks will be delivered to the wrong place, at the wrong time, in conditions that the landing craft crews are not mentally equipped to manage. This is exactly the situation we experienced in an attenuated form today."
"If the attack helicopter gap is not addressed, the Corps cannot provide the close air support that suppresses immediate threats that naval gunfire cannot engage — specifically, mobile armor and threats that appear after the initial fire plan has been executed."
"On the OTOA — if the command authority question is not resolved institutionally at the highest level, every joint exercise will reproduce the chaos we had, and an actual combat operation will reproduce it under conditions where confusion costs hundreds of lives."
Prakash stepped back from the board. "The foundational capability exists. The force is incredibly real. The gaps are specific and completely fixable. The only question is the timeline and the political will to spend the resources."
"Thank you, Major," Rawat said.
Rawat stood up and looked around the room, making eye contact with every exhausted, battered officer at the table.
"I want to say something to every officer in this room about what the past two grueling days have meant," Rawat said, his voice echoing with absolute authority.
"When I came back from Quantico in 1976, I had a fierce conviction that copying the United States Marine Corps would be a disaster for India. I want to explain specifically why I believed this."
"The USMC is the finest, most lethal amphibious force in the world," Rawat acknowledged. "It has 200,000 people. It has its own massive aviation wings. It has its own tanks. It has its own heavy artillery. It has sixty years of institutional memory from the bloody Pacific campaigns, Korea, and Vietnam. It is a masterpiece of institutional design that evolved over six decades in response to specific, global operational experience."
"If I had tried to build a cheap copy of the USMC at one-twentieth the scale, I would have built an arrogant institution that was too large and bureaucratic for what India actually needs, and far too small to do what the USMC does. I would have wasted all our procurement budget on aviation that we do not have the pilots to fly, and artillery that we cannot deliver to beaches that are already heavily contested. I would have trained you for massive Pacific island-hopping campaigns, when our operational environment requires something vastly faster and more lethal."
Rawat leaned on the table. "What I tried to build instead is something that does not yet have a name in the international community, because nothing quite like it exists on earth. A fiercely agile amphibious strike force that is light enough to be delivered globally by five ships, that is capable of incredibly sustained, punishing operations in the absolute worst conditions — the heat, the monsoon, the specific coastal geography of South Asia, the Gulf, and East Africa. A force that is institutionally integrated with the Navy from inception, rather than bolted awkwardly onto an existing land army."
"This exercise has told us exactly where we are," Rawat continued. "We are not where we need to be in five specific ways. But we are where we need to be in the two ways that matter more than the five combined."
"We can get ashore. And we can fight like demons when we get there. Everything else is just details."
"Very important, highly lethal details that will take eighteen months of agonizing work to address. But details."
"The review's findings will be compiled into a massive Manduk Corps Improvement Programme that will be submitted to the Defence Ministry within fourteen days. The programme will specify the exact resources required, the unyielding timeline for each improvement, and the strict metrics by which we will aggressively assess whether each improvement has been achieved."
"The next exercise will be in November. Six months," Rawat commanded. "I want to demonstrate in November that the communication gap has been completely closed. That is my specific, personal commitment to this brigade. The others will follow."
He looked at Admiral Krishnan.
"Admiral, I want to formally request that the Eastern Fleet's training programme immediately include one full quarter of dedicated, violent amphibious training per year for the Project 90 ships' crews, with specific, relentless emphasis on assault delivery timing, tidal planning, and flawless OTOA procedures. I will submit this request formally within the week."
"You'll have it, General," Krishnan agreed instantly. "I'll personally task the fleet training officer to coordinate with your doctrine directorate directly. No delays."
"Thank you."
Rawat looked at the room one final time, pride swelling in his chest.
"There is one more thing I want to say before we close this room."
"The men who went into the dark water this morning at Wheeler Island went in chest-deep in the pitch black. They went in with communications that didn't work as planned, under a fire plan they couldn't confirm had lifted, toward a beach that was seventy agonizing meters further than they expected."
Rawat smiled, a grim, terrifying expression.
"They did not stop. They did not wait in the surf for instructions. They moved violently through the water, and they took the beach."
"That is what a Manduk does. The frog lives intimately between the land and the water. The frog moves seamlessly through conditions that stop other things dead in their tracks. The frog is incredibly patient, until it is explosively fast."
"We have a force that can do the thing. We have a young institution that is aggressively learning how to do the thing correctly. Those are not the same, and both of them matter."
"We will close the gap."
The review ended at 1715 on May 15th.
The massive, comprehensive Manduk Corps Improvement Programme was submitted to the Defence Ministry on May 28th, 1978.
It was sixty-three pages long.
Page one was the cover. Page two was the executive summary. Pages three through sixty-three were the ruthlessly specific findings, specific remediation actions, specific resource requirements, specific timelines, and specific metrics that Rawat's specific method strictly required.
The executive summary was two short, blunt paragraphs.
The first paragraph said: Exercise Sagar Yuddh conducted on May 14th, 1978, aggressively demonstrated the foundational capability of the Manduk Corps to conduct amphibious operations and achieve tactical objectives under severe adverse conditions. Five specific, critical gaps were identified in the areas of communication integration with naval support, beach reconnaissance protocols, landing craft assault delivery training, combined arms coordination capability, and joint command authority procedures.
The second paragraph said: These gaps are entirely fixable, with known technical and doctrinal solutions, in eighteen months, with the massive resources specified in this programme. The Manduk Corps requests absolute approval to proceed.
The Defence Ministry approved the programme in its entirety in June.
The advanced radio gateway equipment was ordered, without a budget fight, in July.
The joint OTOA procedure was officially agreed upon at the Chiefs of Staff Committee in September, based entirely on Admiral Krishnan's forceful personal advocacy.
The beach reconnaissance reporting protocol was heavily revised in July, drafted meticulously by Major Shivaprakash's company exactly as specified.
The intense landing craft assault delivery training programme for the Project 90 ships' naval crews was initiated in August.
The attack helicopter question remained temporarily open, a weapon waiting to be forged.
Exercise Sagar Yuddh II was aggressively planned for November.
In the meantime, at the sprawling Chilika Lake base, the Manduks trained.
They trained in the freezing water long before dawn. They trained on the burning beach in the suffocating heat. They trained in the Zodiacs in the violent monsoon surf. They trained in the specific, grueling conditions of the Indian Ocean coastline — the thick heat haze, the extreme seasonal variation, the punishing tidal rhythms of the Bay of Bengal — because their doctrine explicitly stated that a force trained for the brutal environment it would fight in was a force that could focus entirely on slaughtering the enemy, rather than fighting the environment, when the war finally happened.
Every morning, long before the grueling training began, the Manduk day started the exact same way.
The massive unit assembled on the tarmac. The senior NCO — Sergeant Major Baldev Thapa, who was forty-one years old and had served fiercely in the Gurkha Rifles for seventeen bloody years before joining the Manduk Corps, and who was the specific, terrifying repository of the NCO traditions that a new elite unit required from its most senior non-commissioned officer — called the massive formation to attention.
The Manduk Corps flag was raised.
The flag was a field of dark, fathomless blue — the color of the deep ocean. At its center was a brilliant gold frog in profile, its powerful body coiled in the specific, terrifying posture that a frog adopted a fraction of a second before a violent jump. Below the frog was the Sanskrit motto of the Manduk Corps, which Rawat had chosen from the Rigveda in the quiet document-drafting months of 1976. It applied to the frog in the Rigveda's ancient hymn exactly as it applied to the heavily armed Manduks in May of 1978:
Jahanti shaktimu — They release their strength.
The flag went up.
The training began.
There was still work to do.
There always was.
End of Chapter
Manduk Corps — Institutional Summary (May 1978)
Full designation: Indian Amphibious Corps (Manduk) Constituted: March 1977, under the Manduk Raising Ordinance Headquarters: Chilika Lake Naval Base, Odisha Commandant General: Major General Abhimanyu Singh Rawat Budget status: Separate parliamentary appropriation (not subordinate to Naval or Army estimates) Strength (May 1978): Approximately 4,200 all ranks, including the 1st Manduk Brigade and HQ establishment
1st Manduk Brigade: Commander: Colonel Sukhwant Singh Dhaliwal 1st Manduk Infantry Battalion (CO: Lieutenant Colonel Arjun Menon) 2nd Manduk Infantry Battalion (CO: Lieutenant Colonel Paramjeet Singh) Manduk Support Battalion (weapons, logistics, medical) Manduk Reconnaissance Company Manduk Signals Company Manduk Combat Engineer Company
Project 90 Amphibious Ships (Indian Navy): INS Airavata — Lead ship (1976), 6,200 tonnes, 850 troops, Commanding Officer: Captain Rajan Nair INS Varuna — Second ship (1976), 6,200 tonnes INS Sindhu — Third ship (1977), 6,200 tonnes INS Bhairava — Fourth ship (1977), 6,200 tonnes INS Makara — Fifth ship (1977), 6,200 tonnes
Exercise Sagar Yuddh — May 14, 1978: Landing force: 1,800 Manduks, 1st Manduk Brigade Landing zone: Wheeler Island, Odisha Objective achieved: Point Bakul, at H+147 (planned H+120) Gaps identified: Five specific gaps across communication, reconnaissance, landing craft training, command authority, and combined arms Improvement programme submitted: May 28, 1978. Approved: June 1978.