Chapter 137: The Iron Doctrine
15 December 1973 — Gorakhpur, Shergill Defence Advanced Projects Division
It had started in December 1971.
Not with a commission. Not with a government order or a defence ministry specification or a formal programme initiation document signed by anyone with the authority to sign such things. It had started the way the S-27 had started — with Karan sitting in his office after midnight, reading something that bothered him, and refusing to accept that the thing bothering him was permanent.
What he had been reading was a Soviet tank manual. Specifically the T-54/55 operator and maintenance manual, which he had obtained through the same informal channels that had given him technical literature on everything else he had ever wanted to understand. The manual was translated — imperfectly, by someone whose Russian was better than their mechanical engineering, and whose mechanical engineering was better than their technical English — and Karan had been reading it with the specific attention he gave to things he knew had limitations that the document would not admit.
The T-54 and T-55 were the tanks that equipped the Indian Army. Had equipped it for years. Were, by most assessments circulating through official Indian military publications, adequate for India's needs — a balanced platform of firepower, protection, and mobility that could be maintained by Indian crews and sustained by the supply relationships with Moscow that had been in place for a decade.
Karan had read the manual and thought about what he knew.
He knew the T-55 was a tank designed in the late 1940s and refined through the 1950s. He knew its 100mm rifled gun was adequate against the tank designs it had been built to fight — itself, primarily, and NATO's early post-war designs — but was increasingly marginal against the newer designs that the 1960s had produced. He knew its armour was rolled homogeneous steel at thicknesses that had made sense when shaped-charge anti-tank weapons were in their early development, and that those weapons had not been standing still while the T-55 aged. He knew its fire control was purely optical — no laser rangefinder, no ballistic computer, limited night vision.
He also knew — in the way that a transmigrant knows things, as specific future-memories rather than projections from present data — what tanks would look like in fifteen years. The Leopard 2. The M1 Abrams. Challenger. Their composite armour that defeated shaped-charge warheads not through thickness but through the specific physics of layered materials of different hardnesses disrupting the penetrator's jet before it could bore through. Their 120mm smoothbore guns firing fin-stabilised rounds that penetrated armour at ranges where the enemy tank was still calculating whether it had been acquired. Their digital fire control systems that eliminated the estimation problem entirely — laser, computer, fire — and could hit a moving target from a moving platform in darkness at two kilometres.
He had known all of this in Dec 1971, sitting with the Soviet manual and the specific dissatisfaction of someone who understands what a tool can do and what it cannot and where the gap between them will eventually express itself.
The 1971 war had ended twelve days before he started reading the manual. The Indian Army had won comprehensively — a thirteen-day campaign that had produced the liberation of Bangladesh and the most complete military victory in the subcontinent's post-independence history. The tanks had performed adequately. The PT-76 light tanks that had crossed rivers in amphibious operations, the Centurions and T-55s that had fought the Pakistani armour, the Vijayanta tanks that had pushed through Pakistani defences — all of them had done what was required.
Adequately.
That word was the problem. Adequately was not the same as decisively. Adequately was not the same as so overwhelming that the outcome was beyond question before the first engagement. Adequately was what you achieved when you had enough of something that was good enough. Decisively was what you achieved when you had something that was categorically better.
The S-27 had been designed to be categorically better than what it would face in the air. That was the design philosophy — not competitive, not comparable, not in the same class. Better in the specific ways that mattered: engagement range, fire control, airframe performance, weapons capability. The S-27 had taken eighteen months from first design to first flight — eighteen months of focused, uncompromising engineering.
Why should a tank be any different?
He had opened a notebook that night — not the leather portfolio he used for business, but a plain composition book, the kind that was sold in every Indian stationery shop for schoolchildren — and had written at the top of the first page:
What would a tank look like if you designed it for the battles India will fight in 1980?
But before he wrote anything else, he had written something more immediate:
What capabilities do we already have that we're not using?
That question had changed everything.
Because the answer was: quite a lot.
The semiconductor division that had developed the laser systems for the Astra missile seeker — those same laser diodes and detectors could be adapted for tank rangefinding. The thermal imaging technology that had been developed for the Trinetra radar's environmental sensors — that could become tank night vision. The depleted uranium penetrator technology that DRDO had developed in 1970-71 for Vijayanta upgrades — that existed, had been tested, and sat unused because the Vijayanta's 105mm gun and fire control couldn't exploit it effectively. The composite armour research that had been done for aerospace applications — ceramic-polymer systems for aircraft panels — transferred directly to tank protection.
India had been developing these technologies in isolation. Nobody had assembled them into a system.
Karan would assemble them into a system.
He had written for two hours that night. And when he was done, he had a list of components that already existed or were within months of existing, and a timeline that was not theoretical.
December 1973 target for final presentation.June 1974 target for rolling prototype.
The same compressed timeline that had produced the S-27 in eighteen months. Not because it was easy. Because it was necessary.
The First Team — Early 1972
The first person he had brought in was not an engineer.
He had brought in Brigadier Harshvardhan Singh, retired, who had spent twenty-two years in the Indian Armoured Corps and who had been, until his retirement in 1970, the Army's principal expert on armoured doctrine and armour employment. Singh was fifty-nine years old, lived in Chandigarh, and had written the Indian Army's most recent armour employment manual — the document that described how Indian tank units should fight, not just what tanks could technically do.
Karan had driven to Chandigarh in January 1972 and had spent a day with Singh at his house. The conversation had not been about technical specifications. It had been about what India's armour needed to be able to do.
"We fight on two frontiers," Singh had said. They were sitting in his garden, which was in the specific state of a military man's retirement garden — organized, functional, without ornament. "Western and northern. The western frontier — Pakistan — is the primary scenario. Terrain from desert to mountains, primarily focused on the Punjab and Rajasthan plains where armour can manoeuvre."
"And the plains favour what?" Karan had asked.
"Mobility and firepower," Singh said. "The tank that wins in the Punjab plains is the one that can move fast, shoot accurately at range, and sustain its crew in the heat and dust of a summer campaign." He paused. "The current T-55 can do all of these things. But not well enough."
"Not well enough against what?" Karan pressed.
"Against the Pakistani Pattons," Singh said. "And against whatever Pakistan acquires next. They lost M47s and M48s in 1965 and 1971. They will re-equip. Possibly with Chinese Type 69s. Possibly with more American equipment if the relationship with Washington recovers. Whatever they get, India needs to be ahead of it."
"Ahead by how much?" Karan asked.
Singh had looked at him with the specific look of a professional being asked to be precise about something he normally framed in general terms. "At least a generation ahead," he said finally. "Not marginally better. A generation ahead. The difference between the Matilda of 1940 and the Sherman of 1943 — not better at the same game, a different game."
That was what Karan had needed to hear confirmed by someone who had spent a career in armour. He had already reached the same conclusion. Singh's experience gave it the operational weight that a twenty-two-year-old industrialist reading about future tanks could not give it alone.
He had offered Singh a consultancy role — formal, paid, with a project description that was deliberately vague: advanced armoured vehicle development advisory. Singh had accepted, partly because the money was genuinely useful on a brigadier's pension, and partly because the conversation in his garden had left him with the feeling that this young man was going to build something whether Singh helped or not, and that it was better to help correctly than to let it proceed without the operational experience that would be needed.
The second person was an engineer. Dr. Anand Krishnaswamy, forty-four years old, formerly with DRDO's Armament Research and Development Establishment in Pune, where he had spent fifteen years working on tank gun and ammunition development. He had left DRDO in 1971 — not fired, not disillusioned in a dramatic way, but simply having concluded that the pace of DRDO's institutional processes was too slow for the work that needed to be done, and that the institutional politics of government research consumed more energy than the research itself.
Karan had read about Krishnaswamy through the armament literature — papers he had published in technical journals, presentations at conferences, patents filed through DRDO that showed a mind working on problems that the institution around him was not fully engaging with. He had contacted Krishnaswamy in March 1972 with a letter that was specific about what he was building and honest about how early the stage was.
Krishnaswamy had written back within a week. The letter said: I have been waiting for this phone call for three years. I expected it to come from government. I should have known it would come from somewhere else.
He joined Shergill Defence in April 1972.
He also brought something with him: the DRDO depleted uranium penetrator project files. The full technical documentation for the DU long-rod penetrators that had been developed in 1970-71 for potential Vijayanta upgrades. The project had been shelved—not because the penetrators didn't work, but because DRDO couldn't get institutional buy-in for the Vijayanta fire control upgrades that would be needed to exploit them.
Krishnaswamy handed Karan the files in his first week.
"This is what exists," he said. "Depleted uranium penetrators. 105mm. Tested at ARDE range in 1971. Penetration performance 40% better than tungsten at equivalent velocities. The technology works. Nobody is using it."
"We'll use it," Karan had said. "In 120mm."
The third person was different from the first two in almost every dimension. He was younger — thirty-one, only eight years older than Karan. He was not a consultant or a former DRDO engineer. He was a serving army officer who had been approached through the quiet back-channel that Karan had been developing since the RAW relationship was established — the channel through which people were identified who had something that no institutional process had captured.
His name was Major Balram Singh Mehta.
He had served in 45 Cavalry, the regiment whose PT-76 light tanks had crossed the rivers of East Pakistan in the 1971 war in the operation that had produced, among its other results, the fall of Dhaka.
What Balram Singh Mehta had done with those PT-76s was what had caught Karan's attention.
The Man from 45 Cavalry
The PT-76 was not, by any sophisticated assessment, a good tank.
It was a Soviet light amphibious tank, designed in the late 1940s and entering Soviet service in 1952. Lightly armoured — its protection would not have stopped the main gun of any tank it was likely to encounter, and would barely stop heavy machine gun fire at close range. Armed with a 76mm gun that was adequate against infantry positions and lightly armoured vehicles but that had no place in a tank-versus-tank engagement against anything built after 1950. Slow by tank standards, unreliable in dusty conditions, mechanically complex in the areas that mattered for amphibious operation.
The Indian Army had PT-76s because amphibious crossing capability was necessary for operations in the river delta terrain of Bengal and Bangladesh, and the PT-76 was what existed to provide it. You used what existed when what existed was what you had.
What Balram Singh Mehta had done with the PT-76 in December 1971 was to make it work considerably better than it had any right to work, through a combination of mechanical modification and tactical innovation that had been improvised in the field and then applied systematically across his squadron.
The modifications were the part that had reached Karan's attention through Brigadier Singh, who had read the after-action reports and had flagged them as worth understanding.
Mehta had modified the flotation system — the PT-76's amphibious capability depended on a flotation collar arrangement that was, in its standard configuration, slow to deploy and unreliable in current. He had redesigned the deployment mechanism using materials sourced from a Dhaka engineering workshop, had made the collar inflation faster and the attachment more secure, and had tested the modification under fire conditions at three river crossings in conditions where a failure would have drowned crew members and tanks simultaneously.
He had modified the gun stabilisation — the PT-76's gun was not stabilised, meaning it could only fire accurately when stationary. Mehta had adapted a stabilisation mechanism from a separate piece of equipment — Karan had read the report and had not been able to determine, from the field report's characteristically imprecise description, exactly what equipment the stabilisation components had come from — and had installed it in his troop's vehicles, giving them a limited but real ability to engage targets while the tank was in slow movement.
And he had modified the communications — the PT-76's radio system was adequate for direct squadron communication but had limited range for coordination with supporting arms. Mehta had reconfigured the antenna systems and power allocation in a way that extended effective range and allowed his squadron to maintain contact with infantry and artillery supports through river crossings where radio contact was normally intermittent.
None of these modifications were in any manual. None of them had been authorised by any engineering authority. All of them had worked.
The after-action report written by Mehta's regimental commander had said, in the specific understated language of Indian Army after-action reporting: Major Mehta's technical innovations to his troop's equipment demonstrated unusual engineering initiative and produced measurable improvements in combat effectiveness. The report had recommended Mehta for an accelerated promotion board and had noted that the modifications deserved examination by DEME — the Directorate of Electrical and Mechanical Engineering — for potential wider application.
DEME had received the report. The examination had not yet occurred by the time Karan read the Brigadier's summary in July 1972.
He had arranged a meeting with Mehta in August of that year.
Mehta was thirty years old at that point — compact, precisely spoken, with the physical quality that armoured corps officers developed from years spent in the confined spaces of tank turrets, which was a certain economy of movement and a certain relationship with noise. He was not tall enough to be inconvenienced by tank hatches but not short enough to feel confined in them. He moved as though he had calculated the space he occupied and was operating within it efficiently.
He had come to the meeting in Gorakhpur in uniform because he was still serving — his leave request had been processed for a standard three-day pass, and he had spent one of those days on a train and another at Shergill Defence's facilities. The third day he would spend on a train back.
Karan had met him in the design workspace — not the finished office spaces but the working space where the armour project's nascent team was beginning to accumulate material. Boards with technical drawings. Reference books on armour development. The composition notebook from November 1971, now extended to three notebooks and supplemented with a set of reference cards that Karan had been compiling on specific technical questions.
Mehta had looked at the boards. Had looked at the reference books — some of which were in Russian, some in German, some in English, all of them technical armour literature that was not easily available unless you had the channels Karan had. He had looked at the composition notebooks, which were closed, and at the reference cards, which were spread across the table.
He had said: "How long have you been working on this?"
"Since DECEMBER 1971," Karan had said.
Mehta had looked at him. "November 1971 was when the war ended."
"Yes," Karan said.
"You started the day the war ended."
"The day I read the T-55 manual," Karan said. "Which was about two weeks after the war ended."
Mehta had looked at the boards again. At the specific technical questions that were written on cards and pinned to one of the boards under the heading Open Problems — Armour: gun calibre, composite armour feasibility, fire control systems, engine options, suspension design for subcontinent terrain.
"You're building it yourself," Mehta said.
"I'm building the capability to build it," Karan said. "Which is different from starting production. Right now we're at the stage of knowing what questions need to be answered before the first drawing is committed."
"Who else is on this?" Mehta asked.
Karan named Brigadier Singh and Krishnaswamy.
Mehta looked at the reference cards for a moment.
"You've been thinking about the gun stabilisation problem," he said. He was looking at a card that said: Gun stabilisation — requirements vs PT-76 actual — what does full stabilisation require?
"I read your after-action report," Karan said. "Your modification to the stabilisation system in the PT-76 — I want to understand the engineering."
"It was improvised," Mehta said. "Not precisely engineered. It worked because the requirement was modest — slow movement, low angles. For a main battle tank fighting from maximum speed, the stabilisation requirement is completely different."
"I know," Karan said. "Which is why I want to talk to the person who understood the basic problem well enough to improvise a partial solution under field conditions. The improvised solution tells me what you understand about the problem. Understanding the problem is the starting point."
Mehta had looked at him for a long moment.
"If I help you with this," Mehta said, "I need to keep serving. I have obligations to my regiment. To my men. The modifications I made in Bangladesh — I made them because my men's lives depended on equipment working. If I help build something better, it's for the same reason."
"I understand that completely," Karan said. "I'm not asking you to leave the Army. I'm asking you to contribute to something that will eventually give your men — and their successors — something better than what they have now."
Mehta had been quiet for a moment.
"The problem with the PT-76 gun stabilisation," he said, "is that the vehicle's suspension is too soft. Full stabilisation requires the platform to be mechanically predictable — the gun and turret sensors can model the platform's motion and correct for it, but only if the motion is within a predictable range. The PT-76's suspension is deliberately soft for the amphibious role — soft suspension reduces the stress on the hull during water entry. But soft suspension means the platform is unpredictable in motion on land."
"So the suspension requirement and the stabilisation requirement are in tension," Karan said.
"Yes," Mehta said. "For a main battle tank that doesn't need to swim, the suspension can be tuned for stabilisation performance. The PT-76 can't do both well simultaneously."
"What suspension geometry allows the best stabilisation performance?" Karan asked.
Mehta had looked at him with an expression that was the beginning of something. "That's a technical question that I've been thinking about since Dhaka," he said.
"Then let's think about it together," Karan said.
That meeting in August 1972 had lasted eleven hours. At the end of it, Mehta had agreed to contribute to the programme as an advisor, with visits to Gorakhpur when leave permitted, and with the understanding that his Army service was primary and his contribution to Shergill Defence's armour programme was secondary.
In practice, "secondary" meant that Mehta spent every leave period in Gorakhpur, had taken to requesting posting assignments that brought him near enough to Gorakhpur to make weekend visits feasible, and had written two hundred pages of technical notes on armour design problems that he passed to the Shergill Defence team through a secure courier arrangement that Karan had established.
He had also, in March 1973, submitted his papers for early release from service — not immediately, not without completing the tour he had committed to, but with a target date of January 1974. He had told his regiment that he was leaving to join private industry, which was true. He had not told his regiment exactly what private industry.
His commanding officer, Colonel Rajbir Singh Sandhu, had processed the paperwork with the specific expression of a commanding officer who has watched a talented officer leave and cannot in good conscience argue against it because the officer in question has made his reasoning clear and the reasoning is sound. Sandhu had written in the service record a comment that was brief and precise: An officer of exceptional technical initiative whose contributions to this regiment's combat effectiveness exceeded the scope of his formal responsibilities. His departure is the Army's loss and represents a resource allocation problem that the Army's institutional structures are not currently designed to solve.
This was, by the standards of Indian Army officer performance evaluation, a notably frank assessment. It said what it meant rather than performing what it was supposed to perform.
Sandhu was right about the resource allocation problem.
The Team by December 1973
By the time Karan returned from Europe in late November 1973, the Shergill Defence armour project had been running for twenty-five months. It had started with a notebook and a brigadier and a DRDO refugee and occasional conversations with a serving army officer who came to Gorakhpur on his leave time. It had become something considerably more structured.
The team was nine people, organized around three technical domains:
Armament and fire control: led by Dr. Anand Krishnaswamy, with two engineers — Vikram Iyer, thirty-one, who had come from the Indian Ordnance Factories Board where he had been working on ammunition development, and Parimal Ghosh, twenty-eight, who had been a graduate student in materials science at IIT Kharagpur and who had joined Shergill Defence directly from his PhD programme on the basis of a conversation with Krishnaswamy at a technical conference.
Ghosh brought with him something critical: his thesis work on thermal imaging detectors. He had been researching cadmium mercury telluride detector arrays for industrial temperature monitoring when Krishnaswamy had contacted him in early 1973 and asked a simple question: Can your detector see a tank at two kilometres?
The answer was yes. With the right optics and the right cooling system, the CMT detector could resolve a tank-sized thermal signature at combat ranges. Ghosh had joined immediately and had spent the past nine months adapting his laboratory system into something that could survive in a tank turret.
Propulsion and suspension: led by Suresh Nair, forty-six, who had spent twenty years with Heavy Vehicles Factory in Avadi where the Vijayanta tank was manufactured under license, and who had left HVF with the specific frustration of an engineer who has spent two decades understanding how to build something and who has not had the authority to improve it. With him: Ravi Shankar Pillai, thirty-four, a mechanical engineer who had worked at DRDO on engine development before joining Shergill Defence, and Dilip Bose, twenty-six, fresh from IIT Bombay's mechanical engineering programme, hired specifically because Nair had read his thesis on tracked vehicle suspension dynamics and had told Karan that this was the best piece of Indian technical work on the subject he had seen in ten years.
Nair's first act upon joining had been to bring something critical: the complete technical documentation for the HVF's indigenous transmission development programme. HVF had been working since 1969 on an Indian-designed automatic transmission for the Vijayanta. The project had been partially successful—the transmission worked, but HVF lacked the political support to get it into production. Nair had copies of all the drawings, all the test data, all the lessons learned.
"This is the foundation," he had told Karan in his first week. "We don't need to license a foreign transmission. We adapt this."
Protection and survivability: the newest domain, established only in mid-1973 when the composite armour question had progressed far enough to need dedicated engineering attention. Led by Colonel (Retired) Harshvardhan Singh, who had moved from advisory role to working team member as the programme's scope had clarified. With him: Dr. Meenakshi Subramaniam, thirty-seven, a materials scientist who had been recruited from Banaras Hindu University where she had been researching ceramic composite materials for aerospace applications.
When Krishnaswamy had first approached her in early 1973 with the composite armour requirement, she had said something that had stuck with Karan: "I've been working on this for three years for aircraft panels. You want it for tanks. The physics is identical. I can have armour panels ready for testing in six months."
She had delivered in five.
And Balram Singh Mehta, who as of December 1973 had completed his Army service in November and was now full-time with Shergill Defence, and who had been physically present in Gorakhpur for the past six weeks conducting the final integration of all the subsystems into the hull and turret design.
The presentation had been twenty-five months in preparation.
Not continuously. There had been weeks when the team was focused on questions that remained unresolved, when the presentation was suspended because presenting unresolved questions was not useful, when the programme went through the specific frustrations of technical work that is ahead of the known solutions. But the arc of those twenty-five months had been continuous — building understanding, eliminating options, committing to approaches that the analysis supported, documenting what was known and what was still open.
The presentation that Karan would receive today was the final design review. Not preliminary. Not conceptual. Final. Because the target was not theoretical anymore.
The target was June 1974. Six months away.
A rolling prototype. Fully integrated systems. Ready for Army trials.
The same timeline that had produced the S-27 in eighteen months. Aggressive. Achievable. Necessary.
15 December 1973 — 08:00 Hours
The design workspace had been reorganized for the presentation.
This was partly practical — the accumulated working material of twenty-five months needed to be organized into a sequence that could be walked through coherently. And partly something beyond practical: there was a quality of occasion to this morning that the team had responded to by making the space reflect it. The boards were in order. The reference materials were stacked neatly. The large-format drawings that had been the product of the past three months — the first real design drawings, as distinct from the sketches and concept illustrations that had preceded them — were hung on the wall in sequence, covered with a piece of cloth until the appropriate moment.
Karan arrived at 08:00 exactly. He was dressed in the kurta-churidar he wore in Gorakhpur — not the formal dark suit of the Delhi meetings, not the factory visit practical clothes, but something in between that was distinctly his working presence in his own facility. He carried the leather portfolio that went everywhere, and he carried a cup of tea that had been handed to him at the building entrance by Surendra Prasad who managed the physical operation of the advanced projects division with the same quiet administrative precision that Vishwakarma applied to the aerospace production facility.
The team was already assembled. They had been there since six — some of them from five. The specific quality of people who have been preparing something for two years and who have arrived for the day of presenting it in the specific combination of readiness and anxiety that such occasions produce.
Karan looked at the room. He looked at the people. He looked at the covered drawings.
"Good morning," he said. He sat down at the end of the table that had been left clear for him — not the head, not a throne, just a clear position from which the whole room was visible and from which questions could go in any direction.
He set the tea on the corner and the portfolio in front of him and looked at Krishnaswamy, who was the nearest to the presentation order, and said: "Begin."
The Armament — Krishnaswamy
Krishnaswamy had the specific quality of a person who has spent fifteen years being frustrated by institutional constraints and who has found, in the freedom of the current programme, something that was producing work he believed in without qualification. He was forty-four but presented as someone who was both older — the weight of his DRDO experience — and younger — the energy of something unconstrained. He moved to the first board without theatrical preparation.
"The gun," he said. "This is the single most important decision in the programme, because every other system is organized around it."
He uncovered the first drawing. It showed a gun cross-section — the barrel, the breech, the chamber geometry, the bore.
"Our recommendation is a 120mm smoothbore," Krishnaswamy said. "I want to explain why this is the right decision in 1973, when most tank guns currently in service are in the 100-105mm range with rifled barrels."
"The German Leopard 1 uses the L7 105mm rifled," Karan said, not as a challenge but as the statement that invited the explanation.
"Yes," Krishnaswamy said. "The L7 is an excellent gun. The current generation of ammunition it fires — APDS, HESH — is effective against current armour at current engagement ranges. The M60 also uses the M68, which is the American L7 derivative. The Soviets use the U-5TS 115mm smoothbore on the T-62. The T-64 uses the 125mm smoothbore."
He paused.
"Rifled versus smoothbore is not primarily a calibre question. It is a projectile design question. A rifled barrel imparts spin to the projectile. Spin stabilises conventional projectiles and allows certain projectile designs — HESH, specifically — to work correctly. But spin is the enemy of the most effective anti-armour projectile design that current physics supports."
He looked at the room.
"The long-rod penetrator," he said. "Also called kinetic energy penetrator. The principle is this: armour is defeated by high-velocity impact. The penetrator — a dense rod of hard material — strikes the armour plate at very high velocity. The kinetic energy of the penetrator is converted to the work of pushing through the armour. The amount of penetration achieved depends primarily on three factors: the penetrator's density, the penetrator's length-to-diameter ratio, and the velocity at impact."
He drew a quick sketch on the board — a long, thin cylinder representing the penetrator, an angled line representing the armour plate, a dotted line showing the penetration path.
"A longer penetrator penetrates more armour for a given velocity. A denser penetrator penetrates more armour. But a long penetrator — the modern term is APFSDS, armour-piercing fin-stabilised discarding sabot — cannot be spin-stabilised. Spin destroys its stability the way spin would destroy a javelin's stability if you tried to throw it like a rifle bullet. The long-rod penetrator must be fin-stabilised — fins at the rear of the penetrator guide it aerodynamically the way a dart is guided."
"Hence smoothbore," Karan said.
"Hence smoothbore," Krishnaswamy confirmed. "A rifled barrel spins the projectile. A smoothbore barrel does not. For long-rod penetrators, smoothbore is the only option. The sabot — the outer sleeve that provides the bore seal and allows the projectile to be propelled by the gun's propellant — separates after the projectile leaves the muzzle, leaving only the fin-stabilised penetrator in flight."
He paused.
"The depleted uranium penetrators that DRDO developed in 1971," Krishnaswamy said, and he pulled out a technical document from his folder. "These were developed for the Vijayanta's 105mm gun. They were never fielded because the Vijayanta's fire control couldn't exploit their performance. But the penetrators work. We have the test data. We have the manufacturing process documentation."
He showed Karan the document. Test results from ARDE's ballistic range, dated March 1971. Depleted uranium long-rod penetrators, 105mm caliber, achieving penetration of 420mm RHA at 1,000 meters.
"For a 120mm smoothbore," Krishnaswamy said, "we scale this up. Longer rod, higher mass, higher sectional density. The projected performance — based on the scaling laws that DRDO's own analysis established — is penetration approaching 550mm RHA at 1,000 meters. That is more than sufficient against any tank currently in service anywhere in the world, and provides margin against future composite armour development."
"What about future tanks?" Karan asked.
Krishnaswamy nodded. This was the question he had been building toward.
"Composite armour," he said. "Which Dr. Subramaniam's team has already solved. When the adversary develops composite armour — which the intelligence suggests will happen in the Soviet Union within five to eight years — the penetration equation changes. Composite armour defeats shaped-charge warheads efficiently and offers improved resistance against kinetic penetrators."
"How does the 120mm smoothbore respond to that development?" Karan pressed.
"By improving the penetrator," Krishnaswamy said. "Two paths. First: longer penetrators, higher L/D ratio. The physics says that penetration scales approximately with L/D ratio and density. If current best is 10:1, future best approaches 20:1. Second path: higher muzzle velocity. Better propellant technology allows higher chamber pressures, which allows higher muzzle velocity, which increases impact energy. The 120mm bore gives us more propellant volume than a 105mm bore, which is part of why 120mm is preferred for next-generation guns — more energy available from the charge."
He moved to the next drawing. A barrel cross-section showing wall thickness and profile.
"The specific barrel design we are recommending is derived from our analysis of German and Soviet approaches, combined with our own materials modelling. We are using a monobloc barrel — one-piece rather than the two-piece autofrettaged design used in some systems — with a specific wall thickness profile that manages the pressure curve of the firing cycle. The bore diameter is 120mm. Barrel length is 5.6 metres — this gives us the muzzle velocity we need with the propellant loads we can achieve with current chemistry."
Karan was looking at the drawing carefully. He had read about the Rheinmetall 120mm that would eventually equip the Leopard 2 and M1 Abrams — the gun that became the NATO standard. The specifications Krishnaswamy was describing were convergent with that design, not identical but within the same parameter space.
"Breech mechanism," Karan said.
Iyer took this question. He was the ammunition specialist on the team, and the breech was where the ammunition loading interface lived.
"Semi-automatic breech," Iyer said. "The case extraction is automatic after firing — the spent case is ejected by the breech mechanism rather than manually removed by the loader. This reduces the reload time compared to manually extracting the case, and reduces the physical strain on the loader, which matters when you've been firing for several hours."
"Autoloader?" Karan asked.
Iyer and Krishnaswamy exchanged a look. This was the question that had generated the most argument within the team over the past six months.
"We recommend manual loading with semi-automatic breech," Krishnaswamy said. "This is the more conservative choice. An autoloader reduces crew from four to three — commander, gunner, driver — by automating the loader's function. The Soviet T-64 and T-72 use autoloaders. The advantage is crew reduction and the possibility of a smaller, lower-profile turret."
"The disadvantage?" Karan asked.
"Reliability," Krishnaswamy said. "Autoloaders are mechanically complex systems that operate in the worst possible mechanical environment — the turret of a tank during combat, where vibration, shock, temperature extremes, and dirt are all present simultaneously. When an autoloader fails, the tank cannot fire until the fault is rectified. When a loader becomes a casualty, the other three crew members can still load the gun manually."
He paused.
"Mehta's view on this is the one that persuaded me," Krishnaswamy said, and looked at Mehta.
Mehta, who had been sitting to one side with the notebook he carried everywhere, looked up. He spoke without standing.
"In Bangladesh," he said, "we had one PT-76 in my troop where the traversing mechanism became difficult to operate after a track mine damaged the turret ring. The gunner and commander worked together to traverse manually. We were still able to engage. A mechanism failure in an autoloader that depends on precise magazine positioning and precise feeding geometry — that's not something you work around in the field under fire. You're done." He paused. "I've seen enough mechanical improvisation in combat conditions to know what can be improvised and what can't. An autoloader failure can't."
Karan absorbed this. "Continue."
"Fire control," Krishnaswamy said, and moved to the next board. This was the most complex section. The drawings showed a system diagram — sensors, computers, displays, stabilisation components, their interconnections.
"The fire control philosophy we are implementing is integrated computational ballistics," Krishnaswamy said. "This exists in laboratory form but not in production anywhere in the world. We are implementing it using technologies we already have."
He pointed to the system diagram.
"Laser rangefinder," he said. "Adapted from the Astra seeker's laser system. Our semiconductor division has been manufacturing laser diodes for the Astra since 1971. The tank rangefinder uses the same diode technology—different wavelength, higher power, ruggedised package. Ghosh's team completed the adaptation in October. We have a working prototype."
Ghosh stood briefly. "The rangefinder achieves 10-meter accuracy at ranges from 400 to 4,000 meters. Response time under 2 seconds. The housing is shock-rated for tank gun firing loads."
"Ballistic computer," Krishnaswamy continued. "Digital processor, adapted from our aerospace avionics. The same computational hardware that processes the Trinetra radar returns. We've written ballistic software that takes inputs from the rangefinder, crosswind sensor, muzzle velocity measurement system, and target motion sensor, and outputs the corrected aim point to the gun."
"Night vision," Karan said.
Ghosh took this. "Thermal imaging. CMT detector array, Stirling cycle cryocooler. The system sees thermal signatures at combat ranges in complete darkness. We have a working gunner's sight. The commander's independent thermal sight is in final assembly."
He pulled out a photograph. It showed a thermal image of a Vijayanta tank at a test range, taken at 1,800 meters in darkness. The image was clear—turret outline, hull, tracks all visible in grey-scale thermal contrast.
"This was taken three weeks ago," Ghosh said. "The sight works."
Karan looked at the image. Looked at Ghosh. "DRDO developed this in 1971 and nobody used it."
"DRDO developed the detector arrays," Ghosh corrected. "I developed the packaging, the optics integration, and the cooling system that makes it work in a tank. The detector was a laboratory curiosity. This is a combat sight."
Karan nodded. "Continue."
"Gun stabilisation," Krishnaswamy said. "Two-axis electrohydraulic. This is where Mehta's experience was critical. The stabilisation system we've designed uses hydraulic actuators to keep the gun aimed at the point the fire control computer specifies, regardless of vehicle motion. The system compensates for platform pitch and roll at frequencies up to 8 Hz, which covers the vehicle motion spectrum we encounter at normal cross-country speeds."
Mehta added: "The stabilisation is the enabling technology for everything else. The laser and computer calculate the correct aim point. The stabilisation keeps the gun pointed at that aim point while the vehicle is moving. Without stabilisation, the fire control is worthless. With stabilisation, we can hit moving targets from a moving platform."
"First-round hit probability," Karan said.
"Against a stationary target at 2,000 metres in daylight with our fire control: above 90%," Krishnaswamy said. "The current best-in-class fire control — the L7 with optical rangefinder, good training — achieves perhaps 60% first-round hit probability under the same conditions. With a moving target and at night, the gap widens dramatically. Our thermal sight and stabilised fire control can engage at night at ranges where the adversary cannot see us."
Karan absorbed this.
"The fire control is the decisive advantage," he said. "Everything else supports this. If we can hit moving targets from a moving platform in darkness at 2,000 metres and the adversary's tank cannot, we win engagements at ranges where the adversary cannot engage us."
He looked at the room.
"This is the same logic as the S-27," he said. "Push the decisive engagement to a range where the engagement is not symmetrical."
The Engine and Transmission — Nair
Suresh Nair had spent twenty years at Avadi watching the Vijayanta be assembled from British-supplied components and manufacturing packages and had developed, through those twenty years, a comprehensive understanding of what was wrong with every engine that had been proposed for Indian armour applications and why none of them was quite right.
He was not a bitter person. He was a precise person. The precision expressed itself in his presentation the way it expressed itself in everything he did — methodically, without waste, stating what was known and what was not with equal clarity.
"Propulsion," he said. He went to the wall where the engine drawings were hung and uncovered the first set. "The fundamental requirement for a main battle tank engine is simple to state and difficult to achieve simultaneously: high power, compact physical envelope, tolerance of extreme operating conditions, reliability over operational life."
He pointed at the power requirement. "The tank we are designing is intended to reach a combat weight of approximately fifty-two tonnes. For the mobility parameters we require — road speed of sixty-five kilometres per hour, cross-country speed of forty-five, gradient climbing capability of sixty percent — we need approximately one thousand horsepower at the shaft."
"Current Indian inventory comparison?" Karan asked.
"The Vijayanta uses a 650 horsepower engine," Nair said. "The T-55 in Indian service uses a 580 horsepower diesel. Neither is adequate for a fifty-two-tonne vehicle at the mobility parameters we specify. The standard calculation — power-to-weight ratio — gives us our requirement: approximately 19 horsepower per tonne for adequate mobility, which means one thousand horsepower for fifty-two tonnes."
He moved to the engine type drawing.
"Multi-fuel diesel," Nair said. "A diesel engine designed and tuned to operate on multiple fuel types — diesel, aviation kerosene, and blended fuels — with modified fuel injection and combustion management to maintain acceptable performance across the fuel range. The rationale: in wartime logistics, tank fuel supply chains are disrupted. A tank that can operate on aviation kerosene drawn from an airfield, or on locally available diesel of variable quality, is more operationally resilient than one limited to military-specification diesel."
"Development state?" Karan asked.
Pillai — the engine specialist — answered this. "We started from HVF's Vijayanta engine work. HVF has been developing a 750-horsepower multi-fuel diesel since 1969. We took their design, scaled it up to 1,050 horsepower, and optimized the combustion chamber for our fuel range."
He showed the timeline chart. "First prototype engine was on our test stand in August 1973. We've completed 400 hours of development running. Current power output: 1,065 horsepower at governed speed. Fuel consumption across diesel, JP-4, and JP-8: within 8% variance. This exceeds our requirements."
"The test stand ran for 400 hours?" Karan said.
"Four hundred hours since August," Pillai confirmed. "The engine works."
"Transmission," Nair said. He moved to the next drawing. "This is where HVF's work was most valuable."
He showed a complex technical drawing—cross-section of an automatic transmission, gears and clutches and hydraulic passages visible in precise detail.
"HVF has been developing an indigenous automatic transmission since 1969," Nair said. "Six forward ranges, two reverse. Designed for the Vijayanta's 650-horsepower engine. The development programme was technically successful—the transmission works and has been tested in prototype Vijayantas at HVF's proving ground. The programme was never put into production because HVF lacks institutional support to transition development projects into production."
"We scaled it," Pillai added. "Strengthened the gear teeth for the higher torque loads from our 1,050-horsepower engine. Upgraded the hydraulic system for faster shift response. The adapted transmission has been on our test stand since September, running with the engine. 180 hours of coupled running. The transmission handles the engine's output correctly."
"You have a working powerpack," Karan said.
"We have a working powerpack," Nair confirmed. "Engine and transmission. Tested. Proven. Ready for installation in the prototype hull."
Karan looked at the timeline on the wall. Engine: August 1973 first run. Transmission: September 1973 first coupled run. It was December now. Four months of testing.
"That's faster than the S-27 engine development," Karan said.
"The S-27 engine was new development from first principles," Nair said. "This engine started from HVF's existing work. We stood on their foundation. That's why we could move quickly."
"Suspension," Karan said.
Dilip Bose stood. "Torsion bar suspension with hydraulic shock absorbers. Seven road wheels per side. Ground clearance 450 millimeters. Progressive-rate torsion bars—the spring rate increases with deflection, giving soft ride at small bumps and preventing bottoming on large obstacles."
He showed test data. "We built a single-wheel test rig in June. We've characterized the suspension response across the full travel range. The progressive rate curve is validated. We have the final drawings ready for prototype manufacture."
"Timeline to prototype running gear?" Karan asked.
"The running gear can be manufactured as soon as the hull is ready," Bose said. "Lead time for the torsion bars is six weeks. Hydraulic dampers are commercial items—two weeks. The road wheels and tracks we can procure from HVF's Vijayanta production line. Assembly and integration: two weeks. Total: ten weeks from authorization to completed running gear ready for installation."
Karan calculated. December now. Ten weeks from authorization: late February 1974. Hull ready: March 1974 if construction started immediately. Running gear installed: March. First movement trials: April.
"Weight budget," Karan said.
Nair went to the board and revealed the chart:
Hull structure: 15.2 tonnesTurret structure: 8.8 tonnesArmour: 6.8 tonnesPowerpack (engine + transmission): 5.4 tonnesRunning gear: 6.1 tonnesSystems (ammunition, fuel, crew equipment, electronics): 4.9 tonnesDesign margin: 4.8 tonnes
Total: 52.0 tonnes
"The design margin," Karan said.
"Four point eight tonnes," Nair confirmed. "This is the mass available for systems growth. We are within the fifty-two-tonne combat weight limit with acceptable margin."
The Armour — Subramaniam
Dr. Meenakshi Subramaniam was, in the context of this room, the person who had delivered the fastest technical breakthrough. She had joined in early 1973 with aerospace ceramic composite expertise. By May 1973, she had armour panels ready for testing.
She stood at the board with the particular confidence of someone who is presenting something she has already proven.
"Armour," she said. "The protection system."
She uncovered the first drawing. A material science cross-section, showing layers of different materials.
"The system we have developed has three functional layers," she said. "The outer layer: high-hardness steel plate. The middle layer: ceramic composite—aluminium oxide bonded in polymer matrix. The inner layer: high-toughness steel backing plate."
She moved to test results.
"Ballistic testing was conducted at ARDE's range in September and October 1973," she said. "We fired current-generation 115mm APFSDS penetrators and RPG-7 shaped charges at our panels."
She showed photographs. Armour panels after testing. The outer steel layer cratered but not fully penetrated. The ceramic layer shattered—as designed—absorbing energy. The backing plate intact, no penetration.
"Against shaped charges: protection equivalent to 520mm RHA at 42% of the mass," she said. "Against kinetic penetrators: 380mm RHA equivalent. This exceeds our requirements."
"Manufacturing?" Karan asked.
"The ceramic composite process is adapted from my aerospace work," Subramaniam said. "We can manufacture panels at the Gorakhpur facility using existing equipment. The steel plates we procure from SAIL. Assembly is bolted—the panels are modular, field-replaceable."
She showed the modular design. Hull panels, turret panels, all designed to be removed and replaced without structural work.
"When threat environment changes," she said, "we replace panels. The tank is upgradable."
"Total armour weight for the full protection package?" Karan asked.
"6.8 tonnes," she said. "Within the 7.4-tonne budget with margin."
The Hull and Turret — Mehta
Mehta stood.
He was the only person in the room who moved to the front with the specific quality of someone who had been in combat and who carried that experience not as trauma or drama but as knowledge.
"The hull and turret design," he said. He stood at the drawings—the final drawings, the ones ready for manufacture.
"Before I get to the specifics," he said, "I want to say something that is not technical. It is about philosophy."
Karan nodded.
"I have been part of this programme since August 1972," Mehta said. "In those sixteen months I have learned what engineering can achieve when the engineering serves the crew rather than the engineering specification. Everything we have designed is designed for four people who will live inside this vehicle in the worst conditions that exist."
He uncovered the first drawing. Turret cross-section showing crew positions.
"The commander's station," Mehta said. "Panoramic sight—360-degree observation, stabilised, thermal channel. The commander can see in all directions, in darkness, without exposing himself."
"The gunner's station," he continued. "Sight positioned for extended observation without neck strain. All controls within arm's reach. The fire control interface—laser button, target designation, weapon select—optimized based on actual firing trials we conducted with Army crews in October."
"The loader's station," he said. "Ammunition stowage arranged for minimum physical strain. The rounds are positioned so extraction force is primarily arm strength, not back. The ammunition handling reduces loader fatigue by approximately 30% compared to current T-55 configuration—measured data from our trials."
"The hull form," he said. He showed the hull cross-section. "Powerpack in rear. Fuel tanks in hull sides and rear—not in crew compartment. Ammunition separated from crew by armoured bulkhead with blow-off panels. Floor escape hatches—two. One under driver, one accessible from turret."
He looked at Karan.
"Everything costs something," Mehta said. "Weight, complexity, manufacturing cost. Every trade-off is justified by crew survivability or crew capability. The trades are correct."
Karan looked at the drawings. At the crew stations marked in precise detail. At the ammunition stowage with its blow-off panels. At the floor hatches that Mehta had insisted on because he had seen crews die without them.
"The trades are correct," Karan agreed.
The Timeline — Karan
There was a pause after Mehta's presentation. The room had the quality of a substantial accumulation of information that needed a moment to settle.
Karan picked up his portfolio and removed the composition notebook — the first one, from November 1971. He opened it to the page where he had written What would a tank look like if you designed it for the battles India will fight in 1980?
He looked at the question for a moment.
Then he looked at the room.
"The target," he said, "is June 1974. Six months from now. A rolling prototype with fully integrated systems ready for Army trials."
The room was very still.
"That timeline was theoretical when we started," Karan continued. "It's not theoretical now. The fire control is working—we have laser rangefinder, ballistic computer, thermal sights. The engine is working—400 hours on the test stand. The transmission is working—180 hours coupled running. The armour is working—ballistic tested and validated. The hull and turret designs are complete—ready for manufacture."
He paused.
"We are not building a technology demonstrator. We are not building a development prototype. We are building the first production-standard Arjuna main battle tank. What goes to Army trials in June is what will go into production if the Army accepts it."
He looked at each person in turn.
"The hull manufacturing starts January 2nd," he said. "Shergill heavy Engineering in Gorakhpur has the contract Lead time: 12 weeks. Hull completion: end of March and We ."
"Turret manufacturing starts January 2nd," he continued. "Same contractor. Lead time: 10 weeks. Turret completion: mid-March."
"Powerpack installation: first week of April. Running gear installation: second week of April. Fire control integration: third week of April. Armour panel installation: final week of April."
"First movement trials: May 1st. Mobility testing: first two weeks of May. Fire control testing: second two weeks of May. Combined trials: first week of June."
"Army demonstration: second week of June."
He let the timeline sit for a moment.
Krishnaswamy spoke first. "The fire control integration is the critical path. If the computer-to-actuator interfaces have problems—"
"Then we fix them in April," Karan said. "We have four weeks allocated for fire control integration. That's double the time the S-27 avionics integration took. The tank fire control is less complex than aircraft avionics—fewer sensors, simpler kinematics, ground-stable platform. If the S-27 avionics integrated in two weeks, the tank fire control integrates in four."
Nair spoke. "The powerpack installation requires custom mounts. If the mounts don't fit—"
"Then we machine them on-site," Karan said. "We have mobile machine tools. We have skilled technicians. We adapt. That's what rapid prototyping means."
Subramaniam spoke. "The armour panels are manufactured and tested. Installation is straightforward. No concern there."
Mehta spoke last. "The crew station fit-check. We need actual crews—Army personnel—to validate the ergonomics before we finalize."
"January," Karan said. "First week. We bring in Army crews for three days. They sit in the mockup hull we've built. They validate every station. We incorporate feedback immediately."
He closed the notebook.
"This timeline is achievable," he said, "because we did the work correctly. We didn't develop technologies—we assembled existing technologies. We didn't invent fire control—we adapted aerospace fire control. We didn't design a new engine—we scaled proven engine work. We didn't research composite armour—we applied existing ceramic composite expertise."
He looked at the room.
"The S-27 took eighteen months because we built everything from first principles. The Arjuna takes twenty-five months because we were smarter about what we built from scratch versus what we assembled from existing work."
He paused.
"The tank needs a name that everyone remembers," he said.
He looked at the composition notebook, at the last page where he had written something last night.
"Arjuna," he said.
The room was silent.
"The greatest archer in the Mahabharata," Karan said. "Who fought from a chariot—the mobile fighting platform of his era. Who combined skill with the right weapons to achieve outcomes that should have been impossible. Who did not win through overwhelming numbers but through precision and training."
He looked at Mehta.
"Is that the right name?" he asked.
Mehta looked at the drawings on the wall. At the cross-section of the hull where the crew stations were marked.
"Arjuna fought alongside his charioteer," Mehta said. "The charioteer was Krishna. The charioteer was the intelligence that made victory possible." He paused. "We are building the chariot. The crew is Arjuna. The fire control system is Krishna."
The room was very still.
"Arjuna," Karan said. He wrote it at the top of the last page. "The Arjuna Main Battle Tank."
He looked at the room.
"January 2nd. Hull and turret manufacturing begins. June 15th. Army demonstration. Six months. The work begins now."
Afternoon
The formal presentation was complete by noon. The team ate together—not a celebration, not yet, but a working lunch where the conversation continued around the table.
Mehta ate quickly, the way soldiers ate. He was at the end of the table beside Bose.
Karan was at the other end, speaking with different team members about specific next steps. With Subramaniam about armour panel manufacturing. With Krishnaswamy about the Army crew validation sessions. With Nair about the TATA Engineering contract.
After the meal, as the team was dispersing to their work, Mehta came to Karan.
"Can we talk for a few minutes?" Mehta said.
They found a quiet corner of the design space.
Mehta was quiet for a moment.
"In Bangladesh," he said finally, "I had twenty-three men under my command. When we crossed the Meghna river at night, in current stronger than expected, we crossed because I had modified the flotation system and the crew trusted the modification."
He paused.
"The tank you are building—the Arjuna—the crews who operate it will trust it. Not because it is invincible. But because it will do what it is supposed to do when it is supposed to do it. The gun will hit what it aims at. The armour will stop what it is supposed to stop. The engine will run when it needs to run. The crew stations will allow four people to function at their limit."
"That is what we're building," Karan said.
"Yes," Mehta said. "I know. I wanted to say it plainly." He paused. "I joined full-time in November. I want to understand what my role is going forward. Not 'advisor.' Not 'operational consultant.' I want to be the person who represents the crew throughout the programme. Every design decision that affects what happens inside the tank—I want to be the one who says whether it serves the crew."
Karan looked at him.
"You're asking to be the crew advocate," Karan said.
"Yes," Mehta said.
"You have the role," Karan said. "Formalize it with Prasad. Title, responsibilities, authority. Make it real."
Mehta nodded.
They stood at the window for a moment. The December afternoon was clear—the winter light of the eastern UP plain, flat and steady.
"When you were in Bangladesh modifying the PT-76," Karan said, "did you know what you were doing was going to work?"
Mehta thought about this. "I knew the engineering was right. Whether it would hold in actual current, in actual darkness—that I could only know by doing it."
"And when it held?" Karan asked.
"When it held," Mehta said, "I felt what I always feel when something works the way you designed it to work. Not surprise. Confirmation." He paused. "That confirmation is what makes the next thing possible."
"The Arjuna will work," Karan said.
Mehta looked at him.
"Yes," he said. "It will."
The Evening — Karan Alone
The team left at varying hours between five and seven. At seven-thirty, Karan was alone in the design space.
He sat in the chair at the end of the table and looked at the boards. At the covered and uncovered drawings. At the whiteboard with Krishnaswamy's fire control diagrams. At the weight budget chart with its 4.8-tonne margin.
He opened the composition notebook to the first page.
What would a tank look like if you designed it for the battles India will fight in 1980?
He read down through the pages. November 1971: exploratory, questioning. 1972: structured, technical. 1973: solutions developed, open questions honestly documented.
The last page had one word at the top now.
Arjuna.
He thought about what he knew about the future. About the Chobham armour development in Britain. About the M1 Abrams and Leopard 2 that would enter service in the late 1970s. About the 120mm Rheinmetall gun that both would carry. About the digital fire control systems.
The Arjuna was converging on all those developments from an independent direction. Not copying. The physics of tank combat pointed toward those solutions regardless of who was working on them.
The Arjuna would be different in specific ways Indian requirements demanded. The weight limit—fifty-two tonnes—lighter than Western designs. The multi-fuel diesel—Indian logistics. The specific composite armour formulation—Indian materials expertise.
But the design philosophy was the same. And the design philosophy was correct.
He turned to a new page and wrote:
The Arjuna will be the tank that Indian crews trust with their lives. It will earn that trust by doing what it is designed to do under the conditions that combat actually produces. The fire control will hit what it aims at. The armour will stop what it is supposed to stop. The engine will run when it needs to run. The crew stations will allow four people to function at their limit.
This is not ambition. This is the specification. Everything else is the work.
He closed the notebook.
He stood, turned off the light, and walked through the December night toward the residence.
The tank existed in the drawings and in working subsystems.
The rest was six months of work.
End of Chapter 137
Arjuna MBT — Final Design Specification, December 1973 (Internal — Shergill Defence Advanced Projects Division)
General Designation: Arjuna Main Battle Tank (MBT) Crew: 4 (Commander, Gunner, Loader, Driver) Combat Weight: 52 tonnes (target) Weight Margin: 4.8 tonnes retained for systems growth
Armament Main Gun: 120mm smoothbore (Shergill Defence design) Ammunition: APFSDS (DU long-rod penetrator, DRDO 1971 technology scaled to 120mm), HEAT-MP, HESH Rate of Fire: 8 rounds per minute (sustained, manual loading with semi-automatic breech) Coaxial: 7.62mm machine gun Anti-aircraft: 12.7mm commander's weapon station Ammunition Stowage: 42 rounds main gun (separated stowage with blow-off panels)
Fire Control (Systems operational as of December 1973) Rangefinder: Laser rangefinder (adapted from Astra seeker laser, operational prototype) Ballistic Computer: Digital, adapted from aerospace avionics (operational) Gun Stabilisation: Two-axis electrohydraulic (operational) Commander's Sight: Panoramic, stabilised, thermal channel (final assembly) Gunner's Sight: Telescopic, stabilised, thermal channel (operational) Night Vision: Thermal imaging—CMT detector array with Stirling cycle cryocooler (combat sight operational, validated December 1973) Fire Control Philosophy: Integrated Computational Ballistics—measured inputs, computed solution, stabilised gun
Armour (Ballistic tested September-October 1973) System: Three-layer composite (high-hardness steel / ceramic-polymer composite / high-toughness steel) Philosophy: Modular, field-replaceable bolted panels Performance: HEAT defeat equivalent to 520mm RHA, KE defeat equivalent to 380mm RHA Weight: 6.8 tonnes Status: Manufacturing ready, ARDE ballistic test validated
Propulsion (Operational as of December 1973) Engine: Multi-fuel diesel, 1,065 horsepower (HVF base design scaled by Shergill/IIT Bombay) Status: 400 hours development running completed (August-December 1973) Transmission: Six-speed automatic (HVF 1969 design, scaled and strengthened by Shergill) Status: 180 hours coupled running with engine (September-December 1973) Power-to-Weight: ~20.5 hp/tonne at combat weight Road Speed: 65 km/h Cross-Country Speed: 45 km/h Range (internal fuel): 450 km tactical reverse speed of around 10 to 16 km/h,
Suspension Type: Torsion bar with hydraulic shock absorbers, progressive-rate springs Road Wheels: 7 per side Ground Clearance: 450mm Status: Single-wheel test rig validated, final drawings complete
Protection — Crew Ammunition stowage: Separated, blow-off panels Floor escape hatches: 2 (driver + crew compartment) Crew station ergonomics: Optimised for sustained operation per Mehta requirements, Army crew validation January 1974
Programme Timeline (Final) Hull manufacturing (Shergill Engineering, Gorakhpur): January 2 - March 31, 1974 Turret manufacturing (Shergill Engineering, Gorakhpur): January 2 - March 15, 1974 Powerpack installation: April 1-7, 1974 Running gear installation: April 8-14, 1974 Fire control integration: April 15-28, 1974 Armour panel installation: April 29 - May 5, 1974 First movement trials: May 1, 1974 Mobility testing: May 1-14, 1974 Fire control testing: May 15-28, 1974 Combined trials: June 1-7, 1974 Army demonstration: June 15, 1974
Programme Leadership Project Director: Karan Shergill Technical Director (Armament): Dr. Anand Krishnaswamy Technical Director (Propulsion): Suresh Nair Armour Development: Dr. Meenakshi Subramaniam Crew Systems/Crew Advocate: Major (Retired) Balram Singh Mehta Senior Operational Advisor: Brig. (Retd.) Harshvardhan Singh Suspension Lead: Dilip Bose Engine Development: Ravi Shankar Pillai Armament Engineering: Vikram Iyer, Parimal Ghosh (Thermal Imaging)