Chapter 265: The View from Langley
January 2, 1977 Washington D.C.; Langley, Virginia; the Pentagon; the State Department
The President-elect had been receiving transition briefings since the second week of December, and on the morning of January 2nd, the briefing scheduled for 0900 in the transition team's borrowed conference room at the Blair House was not, on the printed agenda circulated the previous evening, described as urgent. It was described, in the flat bureaucratic language the outgoing administration's staff had settled into over eight years of practice, as "Southeast Asia — Military Assessment Update."
Jimmy Carter read the agenda over coffee at six that morning and did not think much of it. He had been reading agendas like it for three weeks. Somalia. The Horn of Africa. NATO force modernisation. SALT II's technical annexes. He had trained himself, in his career as a naval officer and then as a nuclear engineer and then as a governor, to read dense technical material without impatience, and he brought that same discipline to the transition briefings, one after another, without expecting any particular one of them to be different from the ones before it.
This one was different, and it took Robert Rosen, the outgoing CIA Director, exactly four sentences to make that clear.
"Mr. President-elect," Rosen said, once the room had settled and the junior staff had been asked to step out, leaving only Rosen, the South Asia desk's senior director Patricia Holsworth, and Carter's own transition national security aide. "I want to walk you through what the Burma operation has told us about the Indian armed forces' actual battlefield performance, as distinct from what we assessed their performance would be before the war started. This is not a new country to you. You have had the standing assessments on India's defence programme since your first briefing in November — the Tejas-M, the work at Gorakhpur, the Arjun tank programme, the naval developments. What I want to give you this morning is the difference between the paper assessment and what has actually happened on a battlefield, because the difference is larger than anyone anticipated, and it changes some of the assumptions embedded in the strategic planning you're about to inherit."
Carter said: "I've read the standing assessment. Competent regional power, substantial indigenous defence industry, nationalist-aligned posture, permanent Security Council seat . What's different?"
Rosen said: "What's different is that for six years the assessment described capability in the abstract — programmes, prototypes, production targets. What we have now is combat data. And the combat data says the abstract assessment was, if anything, conservative."
Holsworth had the folder open before Rosen finished speaking, and she laid the first document on the table — a single page, the Defense Intelligence Agency's preliminary tabulation of the Kabaw Valley armour engagement, dated December 28th and updated twice since.
"The headline figure," she said, "is this. On December 22nd, in the Kabaw Valley, an Indian armoured force built around the Arjun main battle tank engaged a Tatmadaw armoured force built around the T-55 and a small number of Chinese-supplied Type 59s. The engagement lasted under four hours. Indian tank losses: none destroyed outright, a small number requiring field repair to track and running gear. Tatmadaw tank losses: effectively the entire committed force, on the order of a hundred and fifty vehicles, destroyed or abandoned."
Carter looked at the figure for a moment. "We already knew the Arjun was a capable design. That's been in the assessment for two years."
"It has," Rosen said. "What we did not have, until three weeks ago, was proof that the design performed at the level the programme claimed under actual combat conditions, against a live enemy shooting back with real ammunition rather than against a test range target. Every army in the world has paper tanks that look extraordinary on a specification sheet and perform less impressively when someone is actually trying to kill the crew inside them. The Arjun was not a paper tank. It performed at the specification sheet's level, in the field, against live fire, at close range. That is the update. Not that India built a good tank — we knew that. That the tank does, under fire, exactly what four years of Gorakhpur's engineering claimed it would do."
Carter said: "How many of these tanks does India have in service?"
Holsworth said: "Our current estimate, revised as of this month, is approximately two thousand Arjuns fielded across the Indian Army's armoured formations, with production continuing at the Gorakhpur facility at a rate our analysts place between fifty and seventy vehicles a month."
Carter set his coffee down. "Two thousand."
"Two thousand," Holsworth said. "That is not a demonstration fleet or a first-generation trial batch. That is a main battle tank force larger than most NATO members field individually, produced domestically, by a country that built its entire tank industry from nothing in under a decade."
"And Pakistan," Carter said. "What does two thousand Arjuns performing at Kabaw Valley levels mean for the India-Pakistan military balance specifically?"
Rosen was quiet for a moment, and when he answered his tone had the specific flatness of a man stating something the room already understood and did not need convincing of. "Mr. President-elect, I want to be direct with you rather than diplomatic. Nobody in this building, nobody at the Pentagon, and as far as our liaison contacts indicate nobody in Islamabad either, has believed for some years that Pakistan possesses a conventional military option against India that ends in anything other than defeat. That was true before Kabaw Valley. The 1971 war settled the question in the field, and everything India has built since — the Arjun, the Tejas-M, the naval expansion — has widened the gap rather than narrowed it. What Kabaw Valley does is remove the last remaining argument that the gap might be smaller than it looked on paper, because the T-55 and the Type 59 are the same generation of Chinese and Soviet armour that equips a substantial share of Pakistan's own tank corps. If a battalion of them dies in four hours against Arjuns in Burma, there is no honest analytical basis left for assuming a different result on the Punjab plains."
"So this isn't new information about the balance of power," Carter said.
"No, sir," Rosen said. "It's confirmation, at a level of specificity we did not have before, of a conclusion the intelligence community and frankly most of the informed world had already reached. What is new is the confidence interval. Before Kabaw Valley, that conclusion rested on doctrine comparisons and paper specifications. Now it rests on a battlefield result. The conclusion hasn't changed. Our certainty about it has."
Carter turned the page in front of him — the DIA's air campaign summary, dated January 1st, covering the strikes at Magwe and Meiktell and the subsequent air operations over the Sagaing plain and Mandalay.
"The Tejas-M," he said. "Walk me through this one. I recall the aircraft came up in the Mauritius crisis briefings last year — the confrontation with the American task force and the Soviet submarine activity in the Indian Ocean."
"Correct," Holsworth said. "The aircraft is not a surprise to this building in the way the tank's battlefield performance was. We obtained a reasonably detailed operational picture of the Tejas-M's radar performance and its supercruise characteristics during the Mauritius standoff, when Indian Air Force aircraft operated in proximity to both American and Soviet assets and our own electronic support measures, along with signals intelligence shared informally through the Navy's assets in theatre, gave us a working picture of what the airframe could do. We assessed at the time that it was a genuinely first-rate design, competitive with the F-15 in several respects. That assessment has not needed revision. What Burma adds is combat employment data rather than a new baseline — strike accuracy, sortie generation rates, loss rates under actual air defence fire rather than under the controlled conditions of a naval stand-off."
"And the numbers," Carter said.
Rosen took over. "Across the Rangoon strikes and the subsequent close-support and interdiction campaign through the Mandalay operation, the Indian Air Force flew in excess of a thousand strike and support sorties. Confirmed Indian aircraft losses across that entire span: one, a strike aircraft lost over Rangoon in the opening raid to ground fire, credited at the time to Burmese air defence rather than to any Tatmadaw fighter intercept, since the Burmese Air Force's own fighter strength had already been effectively removed from the equation early in the campaign. No Indian aircraft has been lost in air-to-air combat at any point in this war, because the Tatmadaw's air force stopped being able to contest the sky within the first days of the campaign."
Carter said: "So the aircraft we already knew was excellent has now flown a thousand-sortie campaign and lost one airframe."
"That is the figure," Rosen said.
"And what does that tell us about a hypothetical conflict against an air force with rather more capability than Burma's," Carter said. "China. Or a fully mobilised Pakistan Air Force with current-generation Chinese or American types."
"It tells us the airframe and the pilots behind it are not going to be the limiting factor in that hypothetical," Rosen said. "It does not tell us India would achieve a thousand-to-one exchange ratio against a peer air force, and nobody in this building is suggesting that. What it tells us is that the aircraft performs at the level the design promised, that Indian pilot training and command-and-control integration with strike planning is of a professional standard this building did not take for granted three years ago, and that any adversary planning against India's air force is planning against a genuinely first-rate force rather than a developing-country air arm operating imported or licensed equipment beyond its real capacity to employ effectively."
Carter looked at the third document Holsworth had set in front of him — a shorter memorandum, two pages, headed simply Assessment of Indian Military Command Performance, Burma Campaign, prepared jointly by the DIA and the Pentagon's Joint Staff.
"This one is different from the equipment assessments," he said, reading the first paragraph. "This is about how they're running the war."
"It is," Rosen said. "And in some respects it's the assessment I'd ask you to spend the most time with, Mr. President-elect, because equipment performance is a question of engineering, and engineering questions eventually answer themselves one way or another under combat conditions. Command performance is a question of institutions, and institutions are harder to fake and harder to import. You can buy a good tank. You cannot buy a general staff that plans a three-axis assault to collapse a garrison's coherence before it can organise a coordinated defence, or an air campaign that breaks a fortified belt from the air specifically to avoid spending a division's worth of infantry casualties clearing it block by block. Those are choices made by people who understand what war costs and who are choosing, deliberately, to spend material and air power rather than the lives of their own soldiers wherever that trade is available to them."
Carter read further into the memorandum. "The casualty figures."
"Fifteen days into the ground campaign, Indian combat dead across the entire theatre stood at under two hundred men," Holsworth said. "Confirmed Tatmadaw dead in the same period exceeded seven thousand, with several thousand more prisoners taken, a significant proportion of whom surrendered voluntarily rather than being captured in direct combat. That ratio is not produced by courage or by superior individual soldiering alone, though the reports we have suggest the Indian infantry performing the house-to-house and jungle clearance work is of a high professional standard in its own right. It's produced by a command structure that consistently chooses to expend artillery, air power, and armour to protect its infantry rather than the reverse, and that has the industrial base behind it to make that choice sustainable across a five-week campaign rather than for a single opening battle."
Carter set the memorandum down and was quiet for a moment.
"I want to ask the plain question," he said. "Is India, as a military power, now something close to a match for any conventional force in Asia short of the Soviet Union or China itself?"
Rosen did not answer immediately, and when he did, he chose his words with the specific care of a man aware that whatever he said in this room in the next thirty seconds would likely reappear, in one form or another, in a policy document within the month.
"Against any regional power — Pakistan, any Southeast Asian state, any combination of them short of direct great-power intervention — yes, Mr. President-elect. That has been true in a general sense since 1971 and this campaign confirms it in specific, current terms. Against China, the picture is more complicated and depends heavily on the specific theatre — the Himalayan frontier favours the defender in ways that don't map cleanly onto what we've seen in the flat terrain of the Sagaing plain. Against the Soviet Union or ourselves in a hypothetical direct confrontation, no, and nothing in this campaign suggests India is building toward that kind of contest, because nothing about India's stated strategic posture suggests it wants one. What India has built, and what this campaign has demonstrated in the field rather than merely on paper, is the capacity to conduct a decisive, sustained, professionally run conventional military campaign entirely on its own resources, without external material support, against any power in its immediate region. That is not a claim about global military parity. It is a claim about regional military dominance that is now empirically demonstrated rather than merely asserted."
The Joint Chiefs met that same afternoon at the Pentagon, in a session that had been on Harold Brown's calendar as a general transition courtesy call and that turned, within the first twenty minutes, into something closer to the morning's Blair House session in substance if not in form.
General David Jones, the Air Force Chief of Staff, brought his own service's assessment of the Tejas-M's combat record, and it tracked closely with what Rosen and Holsworth had presented that morning — a thousand-plus sorties, a single loss, air superiority established and held for the duration of the campaign without serious contest.
"What I want the transition team to understand," Jones said, to the aide Carter had sent to sit in on the Pentagon session in his stead, "is that this is not a new data point about a country we were uncertain of. This confirms, in combat, what our own analysts concluded from the Mauritius standoff a year ago — that the Indian Air Force is flying a first-rate aircraft, employed by well-trained pilots, under a command structure that plans and executes strike campaigns at a standard we would associate with a major air power, not a developing one."
General Bernard Rogers, the Army Chief of Staff, was blunter about the tank engagement. "I don't think anyone in this building has been under any illusion for some time about what would happen if the Pakistani armoured corps met the Indian Army's current force on a battlefield," he said. "Kabaw Valley isn't a revelation on that point. It's a number. And it's a useful number to have, because now when someone asks us to model a hypothetical India-Pakistan conflict for planning purposes, we have an actual combat exchange ratio between comparable-generation Soviet-pattern armour and the Arjun, rather than an estimate built entirely from specification sheets and doctrine assumptions."
Brown, listening, said: "What I want out of both services by the end of the month is a revised planning assumption, not a revised opinion. I don't need anyone in this room to tell me India can beat Pakistan in a conventional war — that has been the working assumption in every regional contingency plan this building has drafted since 1972, and Burma hasn't changed it, it's confirmed it with harder numbers than we had before. What I need is the downstream analysis: what does an Indian Army with two thousand Arjuns and an Air Force with this sortie-generation and loss-rate profile mean for our own regional force posture, our arms relationships with Pakistan and the Gulf states, and our planning assumptions anywhere India's interests and ours might intersect without being opposed to each other. That's the work. Not re-litigating whether the tank is good. The tank is good. We knew that. Now tell me what it means for what we do next."
At the State Department the following week, Secretary-designate Cyrus Vance's own preparatory session with Holsworth, who had by then been informally attached to the incoming State Department transition team at Vance's specific request, took a similar shape but a different emphasis.
"The military assessment answers what India can do," Vance said, when Holsworth had finished laying out the same combat figures she had given Carter and Rosen. "I want to spend our time on what India is going to do with a demonstrated capability like this. A country doesn't build two thousand tanks and a thousand-sortie air campaign's worth of demonstrated air power and then simply set it aside once the Burma question is settled."
"No," Holsworth said. "And I don't think anyone serious believes India intends to. But the direction that capability points is regional and defensive-strategic rather than expansionist in the sense this building usually worries about. Every application of Indian military power since 1971 — the Bangladesh war, the Mauritius standoff, now Burma — has been in direct response to a security threat or a treaty obligation India judged directly relevant to its own territory, its own citizens, or a partner state it had specific commitments to. "
"That's reassuring in the near term," Vance said. "It's also exactly the kind of pattern that changes once a country's capability outgrows its stated ambitions by a wide enough margin. What does the region look like once every neighbour of India understands, with the same clarity Kabaw Valley has just given us, that there is no realistic conventional check on Indian military action within South Asia short of Chinese or Soviet direct involvement?"
Holsworth considered that for a moment. "It looks like a region where India's diplomatic weight increases considerably faster than its military footprint does, because everyone in it will now calculate their own options against India with the Kabaw Valley numbers in mind rather than against the older, more comfortable assumption of rough parity. Pakistan in particular. Islamabad has known since 1971 that a conventional war with India is not a war it wins. What changes now is that the margin by which it loses has just been demonstrated to be considerably wider than even the 1971 result suggested, and every planning document in Rawalpindi from this point forward has to start from that number rather than from the older one."
Vance said: "Which pushes Pakistan toward what."
"Toward whatever asymmetric or nuclear hedge it can find," Holsworth said, "because a conventional deterrent is no longer a credible option for Islamabad in any scenario analysts there can construct honestly. That's not new thinking prompted by this campaign — Pakistan's strategic planning has been moving in that direction since well before Burma. Burma simply removes any remaining internal argument, within Pakistan's own military establishment, that the conventional gap might still be closable."
Back at the Blair House on the afternoon of January 2nd, once Rosen and Holsworth had finished the formal portion of the briefing, Carter asked the question he had been holding since the morning's session began.
"All of this," he said, "the tank numbers, the sortie rates, the casualty ratios — none of it, as I understand what you've told me, actually surprises this building. It confirms things we already believed. So why did this briefing get put in front of me on my second working day of January instead of folded into the standing India assessment I've already read three times?"
Rosen said: "Because confirmation matters, Mr. President-elect, even when it doesn't change the underlying conclusion. Belief and demonstrated fact carry different weight in a planning document, and they carry very different weight in a negotiation. Before this campaign, if this administration or any other wanted to tell Pakistan, in private, that a conventional war with India was not an option worth contemplating, that was diplomatic judgment resting on assessment. After this campaign, it's a fact resting on a combat record, and facts move policy in ways that assessments alone very often don't. The same is true of anyone else in the region making their own calculations against India — Burma's neighbours, certainly, but also anyone in the Gulf or Southeast Asia thinking about where Indian military and industrial capability is heading over the next decade. We owed you the number, not just the opinion, on your second day in this job, because you are going to be asked to act on it, in one form or another, considerably sooner than most of what's in the standing briefing books."
Carter nodded slowly, turning the DIA's tank memorandum over once more in his hands.
"Two thousand tanks," he said, half to himself. "And they built the factory that makes them from nothing, in under a decade, in a country half of whose analysts three years ago were still writing memoranda wondering whether it could reliably keep the lights on in its own capital."
"Yes, sir," Rosen said.
Carter set the memorandum down on top of the folder and looked up.
"Then let's make sure whatever we do next," he said, "starts from what they've actually done, and not from what we spent the last three years assuming they couldn't."
End of Chapter 265