Chapter 173 - Chapter 166: The King of the Sky

Chapter 166: The King of the Sky

15 August 1974 — Shergill Aviation Design Bureau, Gorakhpur

Independence Day arrived the way it always arrived in Gorakhpur — early, with birds, with the weight of a morning that understood it was being asked to carry more than weather.

By five in the morning the flags were up.

Not ceremonially — the compound's maintenance staff had been at it since four-thirty, placing them with the specific care of people who took the act of placing flags seriously, who understood that flags on a building where things were being built for India's defence were not decoration but statement. The flags flew from the main gate. From the test facility's eastern hangar. From the administration building's roof where the dawn light caught them at an angle that made the saffron almost luminous against the pre-dawn grey.

At five forty-five, Vikram Rathore walked to the hangar alone.

He did this every morning before a significant flight. Not a ritual exactly — he would not have described it as a ritual. More the specific habit of a man who needed twenty minutes with the aircraft before anything else happened, before the engineers arrived with their data sheets and the programme management team arrived with their schedules and the important people arrived in their official cars. He needed twenty minutes with the aircraft itself.

The hangar doors were open.

S-35 Tejas 001 was inside, on its dolly, in the configuration it had been returned to after yesterday's systems check — cowlings all closed, landing gear struts at their proper compression, the blended wing-body configuration visible in the hangar's working lights as the specific geometry that four years of engineering had produced. Not sleek in the fighter-jet poster sense. Something more considered than sleek. An aircraft that had been designed from the aerodynamics outward rather than from the silhouette inward, and that showed this in the way that honest things showed their origins.

Rathore walked slowly around it.

He put his hand on the inlet lip — the starboard intake, the outer radius, the specific compound curve that Ramanathan's aerodynamics team had spent eleven months refining to manage the boundary layer separation at transonic conditions. He felt it the way he felt all aircraft he flew seriously — with the specific attention of someone who had learned, through fifteen years and eleven aircraft types, that an aircraft told you things through the surfaces of it if you were paying attention.

This one told him: ready.

He had said this to Karan after the first flight, in the debriefing. The aircraft is honest about where it is in the envelope. He had meant it technically — the FBW system's control law transitions were transparent to the pilot in a way that some aircraft's control systems were not, so that you always knew where you were relative to the limit rather than being surprised by a sudden change in feel. But he had also meant it in the other way. The aircraft had no pretensions. It was what it was and did what it could do and did not pretend to capabilities it lacked, and this was the quality in an aircraft that pilots, in the privacy of their professional judgment, valued most.

The people from New Delhi would arrive in four hours.

Rathore had flown eleven flights in twenty-eight days and he was going to fly the twelfth today, in the afternoon, for the most important audience a test aircraft could have.

He was not nervous. Nerves were for unknowns. He knew this aircraft.

He was ready.

The IAF delegation's cars came through the compound gate at seven fifty-three.

Three vehicles, Mehra's staff car in front, the two support vehicles behind, the movement of an official party that had the efficiency of people accustomed to arriving at the right place at the right time and who had been in enough of these events to know that the quality of their arrival set a tone.

Air Marshal Prakash Mehra stepped out of the first car and stood for a moment.

He was sixty-two years old. He had flown the Spitfire in 1941 at age twenty-nine as a newly commissioned Pilot Officer, had watched thirty-three years of Indian aviation unfold from the cockpit and from the command tower and from the conference room. He had the physical quality of men who had spent their lives in aircraft — a particular economy of movement, as though they had learned in cockpits that unnecessary movement cost something, and had kept the habit on the ground.

He looked at the compound. At the hangars. At the airstrip visible beyond the administration building's eastern end. At the S-35 Tejas programme sign at the facility entrance, which had gone up three years ago when the programme formally established its design bureau here, and which said: S-35 Tejas Development Programme — Shergill Aviation Design Bureau.

Then he looked at the flag on the administration building.

He stood with it for a moment.

Air Vice Marshal Rajiv Sinha, who had been his deputy in the technical directorate for four years and who knew his silences well enough to read them, came to stand beside him.

"Twenty-seven years since the British left," Sinha said quietly. It was not a question.

"Twenty-seven years since we stopped flying aircraft that had someone else flag," Mehra said. He turned from the flag. "Let's see what we have."

Group Captain Dilip Parulkar had flown the S-27 twice in joint evaluation exercises with the IAF test unit at Bangalore. He had written, in the classified assessment that he submitted afterwards, a single sentence that had circulated through the upper levels of the Air Force in photocopied fragments for two years: The S-27 Pinaka is not merely the best combat aircraft in South Asia; it is the aircraft against which every future South Asian combat aircraft will be measured, including the aircraft that eventually replaces it.

He had written that sentence knowing he might be the pilot asked to evaluate the aircraft that replaced it.

He arrived at the briefing auditorium carrying a notebook that was already half-full with questions prepared over the previous two weeks — questions generated by reading every piece of publicly available information about the S-35 programme, every academic paper from Menon and Ramanathan and Vardhan that had made it through the clearance process, every brief that the IAF's own intelligence directorate had produced.

He found a seat on the aisle.

Air Commodore Jayant Srikrishna — the acquisitions man, the officer whose professional function was converting what happened in this room into budget submissions and procurement recommendations — sat beside him.

Srikrishna said, looking at the covered boards at the front: "What are you expecting?"

Parulkar thought about this honestly. "I'm expecting to be surprised," he said. "The S-27 surprised me. I had read everything before I flew it and I still wasn't ready for what it was in the air. If this programme is what the early data suggests—" He stopped.

"What?" Srikrishna said.

"I'll tell you after the afternoon flight," Parulkar said. "I don't want to set my own expectations."

Karan was at the front of the room, his back to the door, looking at the covered boards, when Mehra came in.

He turned.

He was twenty-three years old and he had the specific quality, in moments like this, of someone who was entirely present in the moment and not managing his presentation of it. He looked like a man who had been awake since four thinking about the aircraft, which was what he had been doing.

"Air Marshal," he said.

Mehra walked to the front of the room and stood beside him, looking at the covered boards. Neither of them spoke for a moment. It was the silence of two men who were both looking at the same thing from different ends of the same concern — Mehra from the operational requirement, Karan from the engineering answer to it.

"Independence Day," Mehra said.

"I thought the date appropriate," Karan said.

Mehra looked at him. "Why?"

Karan held the Air Marshal's gaze. "Because what's under those covers is the answer to a question that has been open since 1947," he said. "What does an aircraft built entirely in India look like when the people building it are not constrained by borrowed technology, foreign specifications, or another country's industrial limitations?"

Mehra said: "And the answer is?"

"Pull the cloth," Karan said. "Then we talk."

He reached up and pulled the first cloth.

The room had been filling while they spoke — Sinha and Srikrishna at the table, Parulkar on the aisle, the technical specialists arranged in their assessment formation, the Ministry officials at the back, the PMO observer near the door. They all looked at what appeared on the first board.

Three-view drawing. Top. Side. Front.

Parulkar sat completely still for approximately five seconds, which was a long time for Parulkar, who was constitutionally incapable of stillness.

Then he said: "Blended wing body."

Not a question. An identification. The specific identification of someone who knew what he was looking at and was confirming it against his knowledge.

"Blended wing body," Karan confirmed.

Parulkar leaned forward. He studied the drawing with the intensity of a test pilot reading an aircraft — not looking at it as an image, reading it as a document, extracting performance information from the geometry the way a musician extracted harmony from a score. He looked at the intake configuration, the wing sweep, the tail surfaces, the engine nozzle arrangement.

He sat back.

"The intake placement," he said. "Both inlets flush with the belly. You're managing the subsonic boundary layer separation with—" He stopped. "What's the BL management solution at high alpha?"

Karan said: "Ramanathan will walk through the aerodynamics in detail. The short version: LEX — leading edge extensions at the fuselage forebody — generate high-energy vortices at high alpha that energise the intake flow and maintain mass flow at angles that would starve a conventional ventral intake. Tested to twenty-eight degrees in the tunnel and in flight."

"Twenty-eight degrees," Parulkar said.

"Twenty-eight usable AoA," Karan said. "The alpha limiter is set there. Beyond it the nose-slice tendency requires characterisation we haven't completed."

"But you've flown it to twenty-eight."

"Twice," Karan said. "Both times with Rathore. Both times clean. The aircraft is stable at twenty-eight — the FBW is working hard but it's within the design envelope."

Parulkar looked at the three-view again. He was adding two facts together and getting a result that he wanted to verify before he said it out loud. He said it anyway.

"With LEX vortex lift and twenty-eight degrees of usable AoA," he said slowly, "in a nose-high slow-speed engagement, this aircraft can point its nose at a target that is outside a conventional aircraft's pointing envelope."

"Yes," Karan said.

"At low airspeed. In a turning fight. You can depart the energy manoeuvring envelope — intentionally — into a high-alpha pointing regime and place a short-range missile on a target that thinks it has the angle."

"The FBW maintains controlled flight throughout," Karan said. "The aircraft doesn't depart. It goes to twenty-eight degrees of AoA and holds there on demand."

Parulkar looked at the drawing one more time.

Then he looked at Srikrishna.

Srikrishna said, very quietly: "Write that down."

"I'm writing it down," Parulkar said.

Mehra had been watching this exchange with the specific attention of a senior officer who was tracking not just the content of what was being said but the dynamic of how the room was receiving it. He looked at the drawing and then at Karan.

"Single engine," he said.

"Single engine," Karan said.

"Walk me through why," Mehra said. He said it without the institutional reflex against single-engine aircraft that the statement might have invited — he said it as a genuine request for the engineering rationale, because Mehra had made his peace with the Kaveri philosophy during the S-27 programme and he wanted to hear the S-35 version of it.

"The Kaveri Mk2," Karan said. "This is where the conversation starts and ends. Air Marshal, I want to tell you what the Kaveri Mk2 is before we talk about the aircraft it's inside."

Mehra sat down.

Dr. Harsh Vardhan was not a briefer. He would have told you this himself, without modesty. He was an engineer. He had spent twelve years of his life on turbofan design — at the Propulsion Research Laboratory in Bangalore, then at the National Aerospace Laboratories, then at Shergill Aviation from the programme's beginning — and his relationship with engines was the specific intimate relationship of someone who had measured their specific fuel consumption in lab conditions at three in the morning and understood every number by what it meant physically rather than by what it meant on a spreadsheet.

He stood at the front of the room with the Kaveri Mk2 cutaway diagram behind him and looked at the IAF officers.

He said: "The American General Electric F110 engine is in development for the F-15 and F-16 programmes. Its base single-engine dry thrust rating is approximately seventy-three kilonewtons." He paused. "The Kaveri Mk2's single-engine dry thrust rating is one hundred and four kilonewtons. That is not a marginal difference—it is a generational leap."

He paused again. He had a specific quality when he paused — the quality of a man making certain the room understood the last sentence before proceeding to the one that would change its meaning.

"Now let me tell you everything else," he said.

He pointed to the cutaway.

"The F110 achieves seventy-three kilonewtons of dry thrust with an engine that weighs one thousand six hundred kilograms," he said. "The Kaveri Mk2 achieves one hundred and four kilonewtons of dry thrust with an engine that weighs one thousand two hundred and eighty kilograms. It is three hundred and twenty kilograms lighter, yet it pumps out thirty-one kilonewtons more dry power. The Kaveri's specific thrust — thrust produced per kilogram of engine weight — completely outclasses the American design."

Sinha said: "What does that mean for the aircraft?"

"It means," Vardhan said, "that in an aircraft of the Tejas's weight class, the Kaveri Mk2 gives a thrust-to-weight ratio at combat weight that the F110 in the F-16 cannot match, because the F-16 is choked by a heavier, less powerful powerplant. The Kaveri Mk2 is a more powerful engine for its weight than anything flying or under development in the Western or Soviet world today."

Parulkar said: "Specific fuel consumption at cruise."

"This is where it becomes more significant," Vardhan said. "The F110's specific fuel consumption in dry thrust at cruise conditions is approximately zero point eight two pounds of fuel per pound of thrust per hour. The Kaveri Mk2 is zero point six nine." He looked at the room. "The Kaveri burns eighteen percent less fuel per unit of thrust at cruise conditions than the best engine in American development. Eighteen percent. Over a two-thousand-kilometre mission profile, eighteen percent fuel saving is not a marginal number. It is the difference between an aircraft that makes it home and one that doesn't."

Mehra said: "The MiG-25."

It was a different kind of statement from anything that had been said so far. The MiG-25 — the Soviet interceptor that had been operating at extreme altitude and extreme speed over the Middle East and had appeared in photographs and intelligence assessments and that was the specific aircraft that had caused the most recent revision of Western air defence thinking — was not in the briefing script. Mehra was inserting it.

"The MiG-25 problem," Mehra said. He was looking at the diagram but speaking to the room. "Let me tell you what keeps people in my position awake at night, so you understand why the numbers you're showing me matter the way they matter."

The room waited.

"The MiG-25 Foxbat," Mehra said, "flies at Mach 3.2. Ceiling in excess of twenty-three thousand metres. No aircraft currently in any inventory can catch it. No missile currently in any inventory can reliably intercept it. Its reconnaissance variant has been operating over the Middle East and conducting overflights that we cannot stop." He paused. "The Soviet Union has given India the MiG-21. The Soviet Union has given Syria and Egypt better. The MiG-25 is what Pakistan will be asking for by 1980 if the Soviet-Pakistani relationship follows the trajectory it's following. And the United States is developing the F-14 Tomcat — which is operational now with the US Navy — with a radar and missile system specifically designed to engage fast, high-altitude threats."

He looked at Karan.

"I need to know where the S-35 Tejas sits in a world where the threat is not the Mirage III but the MiG-25 and the F-14," he said. "Because Pakistan is not going to be flying Mirages in 1985. What Pakistan will be flying in 1985 is the question I need answered before I recommend any programme to my government."

Karan looked at the Air Marshal.

"I was waiting for that question," he said.

He walked to the performance board and pulled the cloth from the specifications table.

The comparison showed five aircraft: S-35 Tejas, S-27 Pinaka, MiG-25 Foxbat, F-14 Tomcat, and a column labeled F-16 Block 1 (projected) with an asterisk indicating estimated figures from open-source development data.

Mehra looked at the table.

He looked at it for a long time.

Then he said something that no one in the room expected a sixty-two-year-old Air Marshal to say.

He said: "Good God."

The MiG-25 Foxbat column showed the obvious Soviet advantages — Mach 3.2 maximum speed, a 23,000-metre ceiling, and absolute kinematic dominance at altitude and speed. Numbers that had been causing nightmares in Western air defence planning rooms for three years.

The S-35 Tejas column showed: maximum speed Mach 2.2, combat ceiling sixteen thousand metres. Below the Foxbat on every raw kinematic parameter.

But the next row was radar.

The Trinetra radar: 220 kilometres detection range. Eighteen simultaneous tracks. Six simultaneous BVR engagements.

The MiG-25's radar: fifty kilometres detection range.

Parulkar said — slowly, working it out as he said it — "The Tejas detects the Foxbat at a hundred and fifteen kilometres. The Foxbat detects the Tejas at fifty kilometres. At that point the Tejas has already been tracking the Foxbat for sixty-five kilometres and has had time to position for the shot."

"If the missile can reach it," Sinha said. He said it not as an objection but as the next logical question in the chain.

Karan said: "The Astra Mk2. Range two hundred kilometres. Cruise phase altitude capability forty thousand feet. Terminal phase: active radar seeker, Mach 4 terminal velocity." He paused. "The MiG-25 at Mach 3.2 at twenty-three thousand metres has an energy advantage that makes kinematic escape possible if the pilot knows the missile is coming in time to manoeuvre. The Astra Mk2's flight profile uses a high-altitude cruise phase to conserve energy and approaches the terminal phase with enough velocity for the intercept geometry to work."

He looked at the board.

"The honest assessment," he said, "is that the MiG-25 operating at full speed at maximum altitude is the hardest target this aircraft will face. Not impossible — the numbers work — but hard. The specific scenario where the Tejas is most effective against the Foxbat is the reconnaissance role, where the Foxbat is conducting an overflight at altitude but is not necessarily at maximum speed. At cruise speed, the Astra Mk2's intercept geometry is significantly more favorable."

Mehra said: "The specific scenario we are concerned about is reconnaissance overflights of Indian strategic sites."

"The S-35's intercept geometry against a MiG-25R — the reconnaissance variant — on a standard overflight profile is workable," Karan said. "The launch parameters and the Astra Mk2's trajectory are designed for exactly this scenario."

"How many shots?" Parulkar said. He was still looking at the table. "Against a Foxbat on an overflight profile. How many Astras does it take to achieve a kill probability that justifies the intercept?"

"At the current assessed Pk of the Astra Mk2 against a Foxbat-type target — approximately forty-five percent per shot — a two-shot salvo achieves approximately seventy percent cumulative kill probability," Karan said. "With the Trinetra's track quality against a high-altitude target — which is better than against a low-altitude target in ground clutter — the Pk per shot may be higher. We are still refining this."

"Forty-five percent per shot," Sinha said. He said it the way a senior officer said a number that was important and that he was going to remember.

"Against the hardest target this aircraft will face," Karan said. "Against the Mirage III, the MiG-21, the projected F-16 — the Astra Mk2's Pk is substantially higher because the intercept geometry is less extreme."

Mehra said: "The F-14 Tomcat."

The F-14 column was sobering in a different way from the MiG-25 column.

The Foxbat was fast and high and relatively simple — a racing car with a radar. The Tomcat was something else: the most sophisticated air superiority aircraft in the world in 1974, built specifically to defeat the scenario where an adversary attempts to overwhelm a carrier battle group with multiple high-speed attackers, equipped with the AWG-9 radar and the AIM-54 Phoenix missile that gave it the ability to simultaneously track twenty-four targets and engage six of them at a range of over two hundred kilometres.

Mehra said: "We need to talk about the F-14 carefully. Not because Pakistan has F-14s — they don't and probably won't for a long time. But because the United States has F-14s. And F-14s with Phoenix missiles are what stands over any scenario in which American power projects into this region."

The room was quiet.

This was different from the technical conversation. This was the senior Air Marshal, on Independence Day, saying something that was normally said in much smaller rooms with much tighter classification.

Karan looked at him steadily.

"The AWG-9 in the F-14," he said. "Two hundred and ten kilometres detection range against a fighter-sized target. Phoenix missile: one hundred and ninety-kilometre range. The F-14/Phoenix combination is designed to defeat what it calls 'saturation attacks' — large numbers of attackers coming simultaneously from multiple directions." He paused. "Against a standard adversary, that range advantage is absolute. But against the S-35, the tables have turned entirely. The Trinetra out-detects the AWG-9, and the Astra Mk2 out-ranges the Phoenix."

He walked to the board.

"The S-35 Tejas is designed to seize the initiative from the F-14 on our own terms," he said. "You do not design an aircraft to fight the best of your adversaries by copying them. You design an aircraft that strips them of their primary advantage and dictates the parameters of the engagement."

Parulkar said: "Explain the doctrine."

"The Trinetra at two hundred and twenty kilometres means the Tejas detects the F-14 long before the F-14 detects the Tejas," Karan said. "The F-14 is a massive, high-RCS target carrying the AWG-9 — a radar optimized for the high-altitude, open-ocean environment of carrier battle group defence. The Trinetra's digital signal processing and ground-clutter rejection over land give us a decisive clarity. Because the Astra Mk2 hits out to two hundred kilometres, the Tejas can execute a first-look, first-shoot BVR intercept while the Tomcat is still blind to our presence. The Tejas does not need to hide over open water; it dominates the geometry from the outset."

Sinha said: "That assumes we can choose the geometry."

"That is what doctrine is," Karan said. "The choice of geometry. The S-27 and S-35 combination gives the IAF the ability to dictate the engagement geometry in almost every conceivable scenario. Not through evasion, but through absolute technological overmatch. Even against an adversary with the full resource weight of the United States Navy, the S-35 forces them to fly into a denied envelope. And against the credible threats to India's security in the scenarios that matter—"

"Which are?" Mehra said.

He asked it quietly. He was asking for a statement of strategic philosophy, not a technical brief.

Karan looked at him.

"Pakistan's air force in five years," he said. "With F-16s if the American sale happens, with Mirages if it doesn't. Pakistan's nuclear programme — if it ever recovers — and the delivery aircraft question. China's J-7 and J-8 fighters in the northeastern sector. And the specific scenario you named — reconnaissance overflights by MiG-25 type aircraft that we cannot currently intercept." He paused. "Against all four of these scenarios, the S-35 Tejas provides answers that the IAF does not currently have. Against the first two — Pakistan's air force with any near-term procurement — the answers are decisive. Against the third and fourth, the answers are meaningful."

Mehra looked at the table one more time.

Then he said: "Pull the rest of the boards."

Karan pulled the second cloth.

The Trinetra radar specification board.

Menon presented it. He presented it the way a man presented something he had spent five years building — with the precision of someone who knew every detail and the economy of someone who had learned which details were the ones that mattered in a room like this.

"220km look-down detection range against a three-square-metre target in ground clutter," he said. "Eighteen simultaneous tracks. Six simultaneous BVR engagements. Ground mapping resolution at fifteen kilometres standoff: two metres. Maritime detection: two hundred and forty kilometres against a destroyer-class vessel."

Sinha said: "The two-metre ground mapping resolution."

"It means," Menon said, "that the Tejas pilot can distinguish individual vehicles from two hundred metres altitude on a moving ground mapping pass. In a strike mission, the pilot can identify his specific target within a target complex — not just the complex, the building, the vehicle, the specific hardpoint — at distances where the aircraft is still outside the conventional anti-aircraft artillery envelope."

Parulkar said: "In a night and bad weather environment."

"The Trinetra is all-weather," Menon said. "Radar mapping does not require visibility. The two-metre resolution is the radar resolution — it is independent of optical visibility."

The room absorbed this.

Mehra said: "The S-27's Netra-1 is a BVR air intercept radar."

"The Netra-1 is the finest BVR air intercept radar in South Asia," Karan said. "It is not designed for ground mapping or maritime strike. It is designed for one thing, and it does that one thing better than anything else available in the region." He looked at Mehra. "The S-27 is a sword. The Tejas is a Swiss Army knife that also happens to be an excellent sword."

Sinha said: "The maritime mode. Two hundred and forty kilometres against a destroyer."

"Against the Indian Ocean scenario," Karan said. "Specifically."

He walked to the geographic chart that occupied the room's northern wall — a large-format map of South Asia and the Indian Ocean, on which several geometric shapes had been drawn.

"An S-35 Tejas operating from the INS Dega base in the Andamans," he said. He placed his finger on the Andaman Islands. "The aircraft's combat radius of one thousand eight hundred kilometres — its patrol radius, in this case, is approximately nine hundred kilometres with combat loiter." He drew a circle with his finger. "The Trinetra's maritime detection range of two hundred and forty kilometres." He drew a smaller circle extending outward from the patrol radius circle.

The combined circle covered the entire northern Indian Ocean, the Bay of Bengal, and the approaches to the Strait of Malacca.

The room was very quiet.

"No ship enters or exits the Bay of Bengal," Karan said, "in this scenario, without an IAF S-35 knowing about it."

Srikrishna said — and his voice had a specific quality, the voice of a man who was doing budget mathematics in his head and had arrived at a number that was large but not inconceivable — "How many aircraft to maintain continuous coverage."

"Twelve aircraft on rotation," Karan said. "Four flying, four on ground alert, four in maintenance cycle. Twelve aircraft gives the IAF continuous maritime domain awareness over the entire Bay of Bengal and approaches."

Srikrishna wrote.

Mehra was looking at the map.

He was not doing maritime mathematics. He was thinking about something that was above the pay grade of budget submissions and operational requirements — something in the territory of strategic destiny, the specific question of what India was going to be in the Indian Ocean and what kind of military instrument the country needed to be it.

He said, without turning from the map: "The Garuda."

The room shifted.

It was a small shift — the specific adjustment of people who had just heard a word they were not expecting and were not sure whether to acknowledge having heard it.

Karan said: "Who told you about the Garuda."

Mehra turned from the map. "somebody in air force told me. I worked it out." He looked at Karan with the expression of a man presenting his deduction. "The Tejas is a single-engine medium aircraft. Its payload and range are exceptional for its class. But its payload is eight thousand five hundred kilograms — which is the current generation's heavy strike capacity. The next generation's requirement—" He stopped. "The S-27 was the beginning of a family. The S-35 is the middle. There is a third aircraft. What I want to know is how far away it is."

Karan was quiet for a moment.

Then he said: "Two years."

The room's quality changed again. Not dramatically — these were professional officers who had spent their careers controlling their reactions. But the specific quality of contained surprise — the adjustment of posture, the stillness that preceded a very direct question.

Parulkar said: "You have a prototype flying in two years."

"First flight of the Garuda prototype in approximately twenty-four months," Karan said. "The Garuda is in detailed design. Not preliminary design. Detailed design — the drawings are being made."

"Twin engine," Mehra said.

"Twin engine," Karan confirmed.

Mehra said: "What is the Garuda designed to do."

Karan walked to the geographical chart.

He drew a circle.

The circle was centred on southern India and extended to Beijing. To Moscow. To the Arabian Peninsula. To East Africa.

"It is designed," he said, "to make every strategic target in Asia reachable from Indian soil."

The room was completely still.

Mehra looked at the circle on the map. He looked at it for a long time.

He said: "You are describing a strategic strike capability."

"I am describing India's strategic strike capability," Karan said. "Specifically. An independent capability to hold any target in the region at risk with conventional weapons at long range, without dependence on American cooperation, without dependence on Soviet support, on the aircraft and weapons of our own industrial base."

Mehra said: "What does it cost."

"The Garuda programme's total development cost is approximately two hundred and forty crore rupees," Karan said. "Unit production cost at fifty aircraft procurement volume is approximately three hundred and twenty lakh per aircraft."

Sinha was writing.

"For context," Karan said, "the American B-52 strategic bomber's unit cost in current dollars is approximately eight million. The Garuda's unit cost at equivalent exchange rates is approximately four million dollars. Half the American cost for an aircraft designed specifically for the subcontinent's strategic geography."

Srikrishna said: "The procurement timeline from the Garuda would be."

"First flight in twenty-four months," Karan said. "IAF evaluation twenty-four months after that. First production deliveries four years from today." He looked at the IAF acquisition officer directly. "The IAF can have the Garuda in its first squadron by August 1979."

August 1979.

The room processed this.

Mehra said — quietly, to no one in particular, to the room, to the flag outside the window: "In 1979 the IAF will have the S-27 for air superiority, the S-35 Tejas for multi-role strike and maritime, and the Garuda for strategic reach."

"Yes," Karan said.

"All three Indian designed, Indian built, Indian maintained," Mehra said.

"Yes," Karan said.

Mehra looked at him.

"In 1941," he said, "I was a Pilot Officer. I had been given a Spitfire because the British had Spitfires and were training Indians to fly in their war. The Spitfire was magnificent. I flew it with pride." He paused. "What I'm looking at today — if the numbers hold — is a generation of aircraft that does not merely match British or American equivalents. It exceeds them. In specific and important ways, it exceeds the best aircraft in the world."

He looked directly at Karan.

"Tell me something that could go wrong with the Tejas programme," he said. "Not the small engineering problems — we'll work through those in the evaluation. Tell me the thing that worries you most."

Karan was quiet for a moment.

He looked at the boards. At the specifications. At the numbers that four years of engineering had produced.

"The doctrine," he said. "The aircraft is not the limiting factor. The doctrine is. The Tejas's capabilities — the BVR standoff, the supercruise, the high-alpha pointing — require a pilot trained to a specific operational philosophy. Not the turning fight. Not the merge. The long-range intercept, the standoff shot, the use of detection range as the primary advantage." He paused. "The IAF has trained its pilots on the merge — on the close-in fight — for thirty years. Changing that training philosophy, building the doctrine that uses what the Trinetra gives you, training pilots to trust a radar solution at a hundred kilometres in the way they trust a visual acquisition at two kilometres — that is the hardest thing. Not the engineering."

Parulkar was looking at him.

"You're right about that," Parulkar said. He said it with the specific weight of someone who had been thinking the same thing and was relieved to hear it said. "The aircraft is doctrinal transformation. You can't use the Tejas like a better Gnat."

"No," Karan said. "You cannot."

"The conversion programme will need to address this specifically," Parulkar said. He looked at Mehra. "Sir, when we set up the evaluation, the conversion syllabus question is as important as the aircraft performance question."

"Noted," Mehra said.

The lunch break was a transition.

The formal briefing had been dense and technical and had required the specific sustained attention of people who were going to make significant recommendations based on what they had heard. Lunch was the interval in which the density could settle, in which the numbers could be processed against accumulated professional knowledge, in which people who had listened for three hours could talk to each other.

Mehra sat beside Rathore.

This was deliberate — Mehra had identified Rathore as the person in the room whose knowledge of the aircraft was most direct, most physical, and least interested in managing what it said. Rathore had flown eleven flights. He knew this aircraft from the inside in the way that no briefing could describe and no test data could fully capture.

"Tell me what the aircraft is like to fly," Mehra said.

Rathore thought about this for a moment — not because he didn't know the answer, because he was selecting the right entry point into a description that was not simple.

"Air Marshal," he said. "In 1972 I briefed you on the S-27. Do you remember what I said?"

"You said it was the most responsive aircraft you had ever flown," Mehra said. "You said the control responses were instantaneous in a way that felt wrong until it felt right."

"That's correct," Rathore said. "The S-27 is completely honest about being a machine. It responds to your inputs precisely and immediately. It doesn't buffer anything. You put in two degrees of roll and you get exactly two degrees of roll immediately. For a pilot who grew up on the Hunter or the Gnat, where there's a specific feel — a kind of conversation between you and the aircraft — the S-27 was almost clinical at first."

He paused.

"The S-35 is different," he said. "Not worse — different. Where the S-27 is clinical, the Tejas is— I've been trying to find the right word for it since the first flight. The closest I've got is: wise."

Mehra looked at him.

"Wise," he said.

"The FBW in the Tejas has control laws that are more sophisticated than the S-27's," Rathore said. "Not in the sense of being more complex to use — they're simpler to use. But they're doing more work invisibly. At high alpha, the aircraft is managing the departure tendency, maintaining coordinated flight, preventing the nose slice, all behind the scenes. From the cockpit, what you feel is: the aircraft goes where you point it. At twenty degrees of AoA, at twenty-five, at twenty-eight — it goes where you point it and stays there. It doesn't get nervous. It doesn't tell you it's uncomfortable. It just— does what you ask."

He looked at his hands for a moment.

"The first time I went to twenty-five degrees," he said, "I expected a fight. That's the instinct you develop in conventional aircraft. High alpha is where the aircraft gets difficult. You expect it to start telling you to be careful. The Tejas didn't say anything. It went to twenty-five and held it and waited for me to decide what I wanted to do next." He paused. "I came out of the flight and I sat in the debriefing and I said — the aircraft is wise. Meaning: it knows more than it shows you, and it uses what it knows to give you a simpler, cleaner experience than the physics should allow."

Mehra said: "In a combat environment. The specific quality of the aircraft when things are happening fast."

Rathore said: "I have not flown it in combat. But I have put it in the flight conditions that combat produces — high G, high alpha, energy management at the edge of the envelope, the transitions that happen when a fight changes. In all of those conditions, the aircraft has the same quality. It is not trying to survive. It is operating. It is doing what it was designed to do."

He looked at Mehra.

"Air Marshal," he said, "in thirty-three years of flying you have flown aircraft that got difficult at the edges. The Hunter gets difficult at high AoA. The Gnat is manageable but it's always telling you it's managing. The S-27 is honest but it's clinical at the limits. The Tejas is the first aircraft I have flown where the edge of the envelope is not the enemy. Where the aircraft at twenty-eight degrees AoA is as willing to do what you ask as the aircraft at five degrees."

He paused one final time.

"If the IAF is going to fight the next war," he said, "this is the aircraft it should fight in."

Mehra sat with this.

Then he said: "What does it feel like at supercruise."

Rathore said: "Like flying at Mach 1.4 is the aircraft's natural state and everything slower is the aircraft being patient with the air."

The afternoon briefing covered propulsion and weapons in sequence.

Vardhan returned to the room with a specific mission: destroy the F100 comparison completely.

"I want to come back to the American engine," he said. "The comparison I made this morning was accurate but I think it didn't fully communicate the significance. Let me try again."

He walked to the board.

"The Pratt and Whitney F100," he said, "is the best engine the United States has produced. It is the culmination of fifty years of American turbofan development. It represents the work of thousands of engineers with the full industrial resource base of the world's largest economy." He paused. "The Kaveri Mk2's turbine inlet temperature is higher than the F100's by sixty degrees Celsius."

He wrote it on the board: TIT: Kaveri Mk2 — 1,740°C. F100 — 1,680°C.

"Turbine inlet temperature," Sinha said.

"Is the single number that most accurately captures an engine's technological capability," Vardhan said. "Higher temperature means more energy extraction per unit of airflow. More energy extraction means either more thrust for the same engine size, or the same thrust from a smaller, lighter engine. The Kaveri Mk2 operates at sixty degrees higher than the F100." He looked at the room. "The material science required to achieve that sixty degrees — the specific nickel superalloy blade composition, the thermal barrier coating, the cooling architecture — was developed in Gorakhpur. It does not exist in any published Western literature. It does not exist in any Soviet literature we have been able to assess. The Kaveri Mk2 runs hotter and lighter than the best engine in American development because Indian materials scientists solved a problem that the Americans have not solved."

Parulkar said: "How."

"Six years of work," Vardhan said simply. "One specific breakthrough in 1972 with a nickel-chromium-rhenium alloy that maintains its crystal structure at thirty degrees higher temperature than the existing best material. After that breakthrough, everything else followed."

He looked at Karan.

"It was not my idea to use rhenium," Vardhan said. "I want to be accurate about that. The material direction came from the programme's research lead. I made it work in production."

"The material science was identified in the programme's initial specification," Karan said. He did not elaborate.

Parulkar made a note. He was going to ask Karan about this later. Not in the room, not on the record. Later.

Vardhan continued.

"The operational consequence of the TIT advantage," he said, "is that the Kaveri Mk2 at maximum continuous power — not maximum afterburner, maximum continuous dry thrust — sustains a higher thrust level than the F110 can sustain at comparable conditions without exceeding the American engine's thermal limits." He paused. "In a supercruise scenario, where the aircraft is operating at maximum dry thrust for extended periods, the Kaveri Mk2 can operate at its maximum continuous power setting indefinitely. The F110 cannot achieve supercruise at all without afterburner use. The F-16 is forced into afterburner just to scratch supersonic speeds, bleeding fuel exponentially, while the S-35 Tejas effortlessly supercruises at Mach 1.4 on pure, dry thrust.

Sinha said: "You're saying the F-16's supersonic transit—"

"Is completely non-viable against the S-35 Tejas's," Vardhan said. "Yes. At Mach 1.15 versus Mach 1.4, the fuel consumption comparison changes dramatically. The F-16 at Mach 1.15 in afterburner — which is the only way it can sustain that speed — is burning three times the fuel of the Kaveri Mk2 at Mach 1.4 in dry thrust. The range differential between the Tejas and the F-16 in a supersonic transit mission is not fifty percent. It is several hundred percent favorable to the Tejas."

Mehra said: "Why hasn't this been published."

Vardhan looked at Karan.

"Because," Karan said, "the material science that makes it possible is the most strategically sensitive technical capability in the programme. The instant it is published, every major aviation power in the world begins trying to replicate it. We publish after we have built the Garuda. After the Mk3 is flying. After the capability is so established that the knowledge of it is less dangerous than the capability itself."

Mehra nodded.

He understood the logic. It was the logic of technological advantage management — you did not announce what you had until what you had was so advanced that announcement cost less than continued secrecy.

Bhatt covered the weapons system integration in thirty-five minutes.

Sinha said: "The AIM-54 Phoenix. The F-14's primary weapon. Range one hundred and ninety kilometres. Can the Astra Mk2 defeat it?"

"The Phoenix is designed to engage subsonic anti-ship missiles and bombers — large, non-manoeuvring targets that are predictable and catchable," Karan said. "Against a manoeuvring fighter, the Phoenix's terminal phase becomes an energy management problem. The Phoenix is not designed for fighter-versus-fighter BVR engagement." He paused. "Our Astra Mk2 hits out to two hundred kilometres, completely neutralizing their range advantage, and its terminal phase seeker is specifically designed for the fighter target — high manoeuvring, radar cross-section variation, electronic countermeasures. The Phoenix will catch bombers reliably. Against a manoeuvring Tejas with ECM active, the Phoenix's Pk falls to a range that makes the engagement geometry completely non-viable for the Americans."

Parulkar said: "Our ECM capability."

"The Tejas carries an internal ECM suite," Karan said. "External jamming pod on one of the fuselage hardpoints. The specific ECM frequencies and waveforms are matched to the threat radars we have characterised — including the AWG-9 from test data available through intelligence channels."

"You've characterised the AWG-9," Sinha said.

"We've characterised its search and track modes sufficiently to design ECM responses to them," Karan said.

The room was quiet for a moment.

Then Srikrishna said: "The unit cost."

"Ninety-four lakh rupees at one hundred aircraft," Karan said. "This number includes development cost amortisation, the Kaveri Mk2 engine, the Trinetra radar, the FBW system, the airframe, and the first five years of spares support. It does not include weapons, which are costed separately."

Srinivasan said: "Against what are we comparing that."

"Against the F-16 Block 10," Karan said, "which is projected at approximately two and a half million US dollars at initial production volume — approximately one crore ninety lakh rupees at current exchange rates. The Tejas at ninety-four lakh is less than half the F-16's unit cost." He paused. "For an aircraft that supercruises at Mach 1.4, carries eight and a half tonnes of weapons, has a combat radius of eighteen hundred kilometres, and has a radar that detects threats at two hundred and twenty kilometres."

Srikrishna was writing.

Parulkar was not writing. He was looking at the wall at a point that had no feature on it — the specific focus of a pilot running numbers in his head against operational scenarios he had been living with for years.

He said, without looking away from the empty wall: "Air Marshal, I want to ask a question that is not in my brief."

Mehra said: "Go ahead."

"If we had this aircraft in 1971," Parulkar said. He stopped. He looked at the wall. He started again. "In 1971 we lost seven aircraft in air combat over Pakistan and Bangladesh. Twenty-three on the ground in Pakistani strikes. In those missions the limiting factor was not pilot quality — the IAF's pilots were superbly trained and aggressive. The limiting factor was range and weapons reach." He paused. "If we had the Tejas in 1971 — the combat radius, the BVR missiles, the radar — the specific engagements that produced those losses look different."

He looked at Mehra.

"How different?" Mehra said.

"I won't speculate specifically," Parulkar said. "But in the general case: a hundred and fifteen kilometre radar with a seventy kilometre missile means our aircraft never enter the Sidewinder's engagement envelope against Pakistani fighters who have Western missiles. Our aircraft never get within the Pakistani visual acquisition range. Our pilots see the threats first, shoot first, kill first, and come home." He paused. "The Tejas doesn't improve the IAF's performance in a 1971-type conflict. It transforms it."

He looked at Karan.

"The question I am actually asking," he said, "is this: when can the IAF have this aircraft. Not the formal programme timeline. The real timeline. If everything goes correctly — if the evaluation confirms the briefing data, if procurement moves at the speed it should rather than the speed it usually does — when does an IAF squadron climb into Tejas cockpits for the first time."

Karan said: "If the contract is signed by the end of this year — and I am asking for that, formally, today — the first three aircraft arrive in April 1976. The first squadron reaches initial operational capability, with pilots conversion-trained and weapons-integrated, by October 1977."

"Three years from today," Parulkar said.

"October 1977," Karan confirmed.

Parulkar looked at Mehra.

Mehra said: "The evaluation team arrives in eight weeks. I will lead it personally." He looked at Karan. "I want the full data package — every test flight, every instrumented parameter, all anomalies and their resolutions — on my desk in six weeks. I want no surprises in the evaluation. If there is something this aircraft cannot do, I want to know before we fly it."

"There will be no surprises," Karan said. "Everything the aircraft cannot do is already documented in the test programme. The documentation will be in your hands before the evaluation team arrives."

Mehra said: "The thing you documented that you would most want me to know."

Karan looked at him.

"The transonic buffet at Mach 0.95 to Mach 1.05," he said. "It is manageable — the pilot experiences a specific vibration characteristic as the aircraft passes through the transonic regime that is more pronounced than in a conventional aircraft at the same conditions. It's a characteristic of the blended wing body configuration. Rathore identified it on the second flight. We have characterised it completely — the onset conditions, the magnitude, the airspeed range over which it occurs. The pilot who knows it's coming manages it easily. The pilot who does not know it's coming may be surprised."

Mehra said: "Why does it occur."

"The shock system at the wing-body junction in the transonic range produces a pressure oscillation that feeds into the airframe's structural modes," Karan said. "We know the mechanism. We have not eliminated it because eliminating it would require a geometric change to the junction that costs more aerodynamically than the buffet costs operationally. Rathore's assessment — and I agree with it — is that a pilot who has been briefed on it and has experienced it once will regard it as informational rather than alarming. It is the aircraft telling you you're in the transonic regime."

Parulkar made a note. He made it with the specific quality of a test pilot recording something that was going to be the first thing he investigated when he flew the aircraft.

"Thank you for telling me," he said.

"That is what the programme documents are for," Karan said.

The afternoon.

The walk to the airfield was in the specific heat of August in Gorakhpur at one o'clock — the kind of heat that was total, that came from every direction including up from the concrete. The monsoon air added its quality. The airstrip shimmered in a way that made the north hangar look like it was floating.

The hangar doors were open.

S-35 Tejas 001 was on the apron.

Mehra stopped when he saw it.

He stopped the way he had stopped at the entrance to look at the flag — not for long, not visibly. A breath. An adjustment. The specific pause of a man who was looking at something that was demanding to be looked at before it was approached.

The aircraft.

In photographs it was a configuration. In three-view drawings it was a geometry. In the test data it was a set of numbers. In person, on the apron, in the August afternoon light, it was a thing — a physical object that had been imagined and designed and machined and assembled and that was now standing on the concrete waiting to be flown.

The blended wing body was visible now as a physical reality rather than an aerodynamic concept. The transition from fuselage to wing was not a join — it was a continuity, a single surface that gradually became more winglike as it extended from the centreline outward. The intakes, set flush with the lower surface, were forward-swept — creating the intake geometry that fed air to the single Kaveri Mk2 at the back through a duct that ran the length of the fuselage belly.

The crew chief was at the nose, completing the last item of the pre-flight.

Rathore was in his flight suit beside the starboard intake, running his fingers along the intake lip in the specific way of a pilot who had done this same check eleven times and was doing it again because the twelfth time was not the eleventh time and deserved the same attention.

He looked up when the delegation arrived.

"Air Marshal Mehra," he said. "Group Captain Parulkar."

He said it simply. Not performing deference, not performing casual professionalism. Simply acknowledging the people who were going to watch him fly.

Mehra said: "Rathore, what have you learned about this aircraft in eleven flights that is not in the briefing package."

Rathore thought about this for a moment.

"That it accelerates through Mach 1 faster than I expected," he said. "The briefing data shows the transonic acceleration time correctly, but the character of it — the way the thrust-to-drag ratio changes as the compressibility drag builds and then falls off past Mach 1 — is more pronounced than I expected from the data. The aircraft does not punch through the sound barrier. It steps through it. It arrives at Mach 1.05 with the specific quality of an aircraft that has found its natural operating range. The acceleration from Mach 1 to Mach 1.4 — the supercruise regime — is the most positive acceleration I have experienced in any aircraft."

Parulkar said: "More positive than the S-27's Mach 1 to 1.5 in afterburner."

"In afterburner the S-27 is more energetic because of the afterburner's thrust increase," Rathore said. "The S-35 from Mach 1 to Mach 1.4 in dry thrust is — a specific quality I haven't described correctly yet. The afterburner in the S-27 says: now we go fast. The Kaveri Mk2 in dry thrust through the supercruise regime says: this is where I live."

Parulkar looked at the aircraft.

He said: "I'm going to need to fly this."

"Yes," Rathore said. "You are."

The cockpit briefing took twenty minutes.

Rathore described the pre-start procedure, the engine start sequence, the FBW engagement, the radar mode selection for the Trinetra, the weapons system arming. He described it with the efficiency of someone who had done it eleven times and whose efficiency was not the efficiency of boredom but of complete familiarity.

Parulkar was taking notes. He wrote in the margins: FBW engagement — automatic at weight-on-wheels switch transition. He wrote: Radar: TWS mode default at startup. Slew with HOTAS hat switch. He wrote: High AoA entry — positive pitch input, FBW holds coordination through limit. He underlined this last note.

Then he stopped writing and said: "How does it feel when you let it go."

Rathore looked at him.

"When you release the controls after a manoeuvre," Parulkar said. "In a conventional aircraft the aircraft tends in some direction — nose drop, roll departure, some tendency. When you release the S-35's controls."

"It goes level," Rathore said.

"Level," Parulkar said.

"Level and coordinated," Rathore said. "At any point in the envelope. Below the alpha limit. Release the controls — the FBW trims to wings level and coordinates. There is no default tendency. The aircraft wants to be where you last put it, and if you put it in a manoeuvre and release, it smoothly returns to the nearest stable condition."

Parulkar said: "In a high-pressure environment. When things are happening fast and the pilot releases the controls to manage something else — aviate, navigate, communicate — the aircraft is not going to depart."

"It will not depart," Rathore said. "I have released the controls at every point in the validated envelope including twenty-five degrees AoA. It has not departed."

Parulkar closed his notebook.

"All right," he said. "Go fly."

The start sequence.

The ground crew was positioned with the specific precision of people who had done this eleven times and who knew that the twelfth time was the time the important people were watching and who were therefore performing it exactly as they had performed it the previous eleven times, because performance consistency was the best performance.

The Kaveri Mk2 start.

The ignition sequence produced a sound that was specific to the Mk2 — different from the Mk1.5 in the S-27, different in the deeper initial turbine pitch and the specific acceleration pattern as the engine climbed through the start envelope to ground idle. It was a sound that Mehra had heard exactly eleven times before today, from the recordings of the test flights, and hearing it in person was different from recordings in the way that everything important was different in person.

The engine stabilised at ground idle.

The FBW powered on — indicated by the specific set of control surface movements that the system ran at startup, each surface moving through its travel limits in a checking sequence that took eight seconds.

Rathore ran the systems check. Trinetra radar — online. IFF transponder — set. Oxygen — checked. Ejection seat — armed. Fire warning systems — tested. On the ground station telemetry display, the systems status board showed green across every parameter.

He taxied to the threshold.

The ground station was tracking on telemetry. Mehra, Parulkar, Sinha, and the rest of the delegation were at the observation point sixty metres from the runway. The telemetry screen showed the engine parameters, the flight control system status, the fuel state.

Rathore held at the threshold.

Engine run-up. Power to ninety-seven percent. The Kaveri Mk2 at military power produced a sound that was louder than the ground idle but different in character from the afterburner — the specific tone of a high-bypass turbofan at military power, the air noise dominant, the turbine sound in the background.

The fuel flow showed on the display: military power fuel flow for the Mk2.

"That number," Sinha said to Vardhan, who was standing beside him at the display.

"Less than half the S-27's Mk1.5 at equivalent thrust setting," Vardhan said. "The Mk2's bypass ratio is higher. More of the thrust comes from accelerating a large mass of air slowly — the bypass flow — rather than a small mass of air very rapidly through the core. More efficient at the same thrust level."

Power came off.

A pause.

Then Rathore pushed the throttle forward.

Afterburner engagement: the sound changed with the specific abruptness of a jet engine transitioning to afterburner — the additional fuel igniting in the nozzle section, the thrust increasing, the fuel flow on the display jumping to the afterburner reading. One hundred and forty-five kilonewtons. On a runway in Gorakhpur. On Independence Day.

The aircraft moved.

The acceleration was — the word Parulkar used in his debrief was authoritative. Not fast, because fast was comparative. Authoritative: the acceleration of an object that knew it was going somewhere and was going there without equivocation. The aircraft reached takeoff speed and the nose rotated and it was off the ground and the gear came up and the aircraft climbed and the sound of it moved through the delegation's chests before it moved through their ears.

The afterburner was out before the aircraft reached the airfield boundary. Dry thrust only, climbing through five thousand feet, through eight thousand, through twelve thousand.

On the display the airspeed was climbing: Mach 0.8. Mach 0.9. Mach 0.95.

The specific buffet that Karan had described — the transonic characteristic — appeared on the accelerometer trace on the display. A specific oscillation in the normal acceleration data, approximately 0.3G peak-to-peak, at a frequency around twelve hertz, beginning at Mach 0.93 and running until Mach 1.04.

Then it stopped.

The display showed Mach 1.06. Mach 1.12. Mach 1.2.

At Mach 1.2 Rathore leveled off at thirty-three thousand feet.

The power setting showed on the display: dry thrust, ninety-eight percent. No afterburner.

The airspeed continued to climb: Mach 1.25. Mach 1.3. Mach 1.35.

The fuel flow on the display was thirty-four litres per minute.

Mehra was watching the fuel flow number. He had been an Air Marshal for four years and had spent those four years in intimate contact with the economics of operating an air force — the fuel costs, the maintenance hours, the sortie rates, the specific arithmetic of what it cost to keep an aircraft flying and what you got for that cost. He understood the fuel flow number in its full operational dimension.

Thirty-four litres per minute at Mach 1.4 in dry thrust.

The aircraft arrived at Mach 1.38. Mach 1.39. Mach 1.4.

Stabilised.

Supercruise.

On the ground, nobody said anything for a long moment.

Then Parulkar said, very quietly: "He's at Mach one-point-four on dry thrust at thirty-three thousand feet and the fuel flow is thirty-four litres per minute."

He was saying it to himself as much as to anyone else. Saying it to fix it in his professional memory as a specific data point in the landscape of his knowledge about aircraft.

Mehra said: "What does the F-15 do at Mach one-point-four."

Vardhan said: "The F-15 at Mach one-point-four uses afterburner. Fuel flow approximately one hundred and twenty litres per minute."

Mehra looked at the sky where the aircraft was — a dot at altitude, invisible against the haze except to eyes that knew where to look.

He said: "The F-15 burns four times the fuel to go the same speed."

"Three and a half times," Vardhan said precisely.

"Three and a half times," Mehra said. He said it in the way of a man adjusting a calculation that was already significant.

The turn.

Rathore brought the aircraft down from supercruise altitude in the specific descent profile that the team had designed — the altitude-to-speed conversion that arrived at the medium altitude manoeuvring regime with energy preserved. The telemetry showed the trajectory: altitude decreasing, airspeed falling through Mach 1.0 into the subsonic regime, the aircraft arriving at fifteen thousand feet at five hundred and ten knots with the energy state it needed.

The sustained turn.

The G-load indicator on the display began to climb: 3G, 5G, 6.2G. Stabilised at 6.7G.

The turn rate calculation: 17.1 degrees per second.

Parulkar was watching the calculation display. He was watching it with the focus of someone confirming a number against their own knowledge of what seventeen degrees per second sustained turn felt like from the inside of an aircraft, and what it meant in a combat engagement.

The turn continued.

The aircraft held 6.7G and seventeen degrees per second through one complete three-sixty, two complete three-sixties. Three. The G-load held. The turn rate held. The telemetry showed the fuel flow at the sustained turn power setting — higher than supercruise, lower than afterburner, the engine at a specific intermediate power setting that balanced turn performance against fuel consumption.

Sinha was writing.

Srikrishna was writing.

Parulkar was not writing. He was watching the display and running combat mathematics in his head.

Then the sustained turn ended and the nose came up.

High alpha.

The airspeed fell. Twenty degrees of angle of attack showed on the display. Twenty-three. Twenty-five.

Twenty-five degrees. Sustained. The FBW data showed the control system active — surfaces deflecting in coordinated patterns to maintain the coordinated flight, prevent the departure, hold the aircraft in the controlled high-alpha regime.

Twenty-seven degrees.

The display showed one single second at twenty-seven degrees.

Then back to twenty-five. Held for thirty seconds. Then the nose came down and the aircraft accelerated away from the high-alpha regime, recovering the energy it had spent.

Nobody in the delegation had spoken during the high-alpha sequence.

Mehra said: "Twenty-seven degrees."

"Once," Karan said. "Briefly. The characterisation is not complete."

"But it held," Mehra said.

"It held," Karan said.

Mehra looked at the sky.

"In 1965," he said, slowly, with the quality of a man speaking from somewhere deeper than the professional briefing, "I was Wing Commander in Western Command. During the September operations I watched pilots in Gnats engage Pakistani Sabre jets at close range — turning fights, knife-fights at very low altitude over the Punjab. The Gnat's delta wing gave it a specific advantage at low speed — it could out-turn the Sabre in the slow regime because of the delta's sustained lift. But every time a Gnat pilot went low and slow, he was gambling. The aircraft was near the edge of its stable envelope. He was depending on his skill to manage an aircraft that was not designed to be where he was putting it."

He paused.

"An aircraft that is designed to go to twenty-seven degrees of angle of attack and be controlled there," he said, "is not asking the pilot to gamble. It is giving the pilot a capability that is reliable, sustainable, repeatable."

He looked at Karan.

"That is what changes a war," he said. "Not faster or longer or more weapons. Giving the pilot something reliable."

He looked back at the sky.

"Continue," he said.

The targeting run.

Rathore set up from the south, a medium-altitude approach, the aircraft in strike configuration for the demonstration. The Trinetra in ground-mapping mode — on the display, the airfield ahead was rendered as a radar map, and within the radar map the specific target panel in the western field was visible as a distinct radar return.

At twelve kilometres, Rathore selected the target.

The targeting cursor on the display locked to the panel. The lock was clean — the radar return from the steel panel was specific and unambiguous, the cursor acquired it without searching.

At nine kilometres, the designation mode activated.

On the display, the solution parameters showed: range nine kilometres decreasing, bearing stable, solution quality indicator showing green, time to optimal release counting down.

At six kilometres, the weapon release occurred.

The inert shape dropped from the centreline hardpoint. The guidance system tracked it — the radar designation remained active, the guidance signal updated continuously, the display showed the shape descending in the trajectory that the release parameters had specified.

Impact.

The ground team at the panel signaled.

Srikrishna said: "CEP."

"Eight metres," Karan said.

Srikrishna looked at what he had written earlier — the number from the briefing.

"You said eleven metres in the brief," he said.

"Eleven metres is the specification," Karan said. "This run was eight."

Srikrishna wrote 8m in his notebook, underlined it, and said nothing.

The landing.

The aircraft turned final at three kilometres, gear down, the speed and configuration of an aircraft configured to land. The approach was at a slightly higher angle of attack than a conventional aircraft's approach — the blended wing body needed more alpha to sustain the same lift at landing speed, which was a characteristic of the configuration that Rathore had characterised on the fourth test flight and that was now in the flight manual as the standard approach technique.

The main gear touched at the specified speed, at the specified point on the runway.

Clean. No bounce. No side load. The nose came down smoothly, the drag chute deployed — a small drag parachute that the Tejas used to shorten its landing roll, not required on long runways but included in the test configuration — and the aircraft decelerated to taxi speed.

The Kaveri Mk2 went to ground idle.

The display showed the engine parameters at ground idle. All normal. All in the green. The same parameters it had shown at the start of the sequence.

The crew chief was ready at the hangar door.

Rathore taxied in.

The aircraft stopped on its designated position. Chocks down. Engine shutdown sequence. The Kaveri Mk2 spooled down with the specific decelerating tone of a high-bypass turbofan reducing from idle to stop — the sound moving from the turbine frequency through the fan frequency and then gone.

Forty-three minutes.

Everything on the aircraft had worked.

The debrief was in the conference room at three-thirty.

Rathore came in still in his flight suit, carrying the printouts.

He sat.

He said: "Questions."

Parulkar asked fifteen. Each one was specific, technical, and addressed a specific characteristic that the telemetry data had shown and that required the test pilot's subjective input to fully interpret. Rathore answered each one from memory and from the printouts. When he didn't have the specific number he said so and pointed to the test programme data that would resolve it.

After Parulkar's fifteen, Mehra said: "One question."

Rathore looked at the Air Marshal.

"The aircraft in your eleven flights," Mehra said. "Has it surprised you. Has it done something you did not expect."

Rathore thought about this.

"On the fifth flight," he said. "I was running the high-alpha characterisation at twenty-two degrees. I released the controls — intentionally, a test point — and the aircraft trimmed to wings level in approximately one point two seconds. I had predicted one point eight to two point zero seconds from the FBW's known response rates." He paused. "The FBW is faster than the response rate data suggested. The control law transition in the high-alpha regime was rewritten between the fourth and fifth flight — a software update from the FBW team. They made it faster. They didn't tell me they had changed it."

He looked at Karan.

"After the flight I asked why I wasn't told about the software change," he said. "The answer was that the data showed the new response was correct and there was no reason to update the test pilot's expectation — if I had known the response would be faster, I might have been expecting it rather than measuring it. They wanted a clean measurement."

He paused.

"I was annoyed," he said. "For approximately four hours. Then I re-read the flight data and understood why they did it. The measurement was cleaner because I had not been told."

He looked at Mehra.

"The aircraft surprised me once," he said. "By being better than what I was told to expect. That is a good kind of surprise to have in a test aircraft."

The delegation departed at five-forty.

Mehra was last.

At the compound gate he stopped.

He turned back.

The compound behind him: the hangars, the airstrip, the administration building, the test facility, the engineering offices where the Garuda's detailed drawings were being made in rooms he had not been shown. The flag on the administration building, still flying in the late afternoon light, the orange of it luminous at this angle.

He turned to Karan.

"The IAF evaluation team," he said. "Eight weeks. I will lead it personally. Parulkar flies the evaluation sorties — every one of them, no substitutions. I want the full data package in six weeks."

"Parulkar gets the aircraft on his first request," Karan said. "The data package is on your desk in five weeks, not six."

Mehra looked at him.

"The Garuda programme," he said. "The twenty-four-month timeline."

"It holds," Karan said.

"The IAF will want to be involved in the requirements definition for the Garuda," Mehra said. "Not as observers. As partners."

"The Garuda's requirements specification," Karan said, "was written with inputs from the IAF test unit's advanced planning section. They have been involved for eight months. The programme does not know they have been involved because the involvement was through a channel that was informal enough to not appear in programme documents."

Mehra said: "Who arranged that."

"I arranged it," Karan said.

Mehra looked at him for a moment.

"You arranged IAF involvement in a programme the IAF does not officially know about," he said.

"I arranged informal input from the people in the IAF who understand long-range strike requirements into the design of an aircraft that will need to meet those requirements," Karan said. "The arrangement was informal because if it were formal it would require a programme office and a budget line and a requirement document and approximately four years of bureaucratic process before any technical work happened."

Mehra said: "This is how you build things."

"This is how you build things that need to be built before the process catches up with the need," Karan said.

The Air Marshal looked at him for a long moment.

Then he put out his hand.

Karan took it.

The handshake lasted three seconds.

Mehra said: "Arjun Singh should have lived to see this."

He said it with the specific weight of a man naming a person who had deserved to see a thing and had not lived long enough. Air Chief Marshal Arjun Singh, the architect of the IAF's post-independence doctrine, who had died in 1961 having spent his life building an air force that depended entirely on aircraft that other countries built.

"He would have known what it meant," Karan said.

"He would have," Mehra said. "He built the force that needed this. He couldn't build this. You could."

He got in the car.

The compound in the evening.

Karan stood on the apron road after the last car was gone, looking at the compound around him and the airstrip beyond it and the sky over the airstrip where S-35 Tejas 001 had done forty-three minutes this afternoon on Independence Day and had done them correctly.

Vishwakarma came to stand beside him.

They stood in the compound's evening quiet — the specific quiet of an operation that was still running, that had its overnight shifts and its maintenance routines and its engineering offices with their lights on, but that was quiet at this specific location, this specific moment.

Vishwakarma said: "Mehra is going to recommend approval."

"Yes," Karan said.

"The Garuda," Vishwakarma said. "He's going to want a formal programme."

"He'll have it in four months," Karan said. "When the Garuda detailed design review is complete and the prototype's material commitment is made, we formalise the IAF involvement. By that point the informal inputs are already in the design and the programme isn't starting from a blank sheet."

Vishwakarma looked at the hangar.

"Two years to first flight of the Garuda," he said.

"Twenty-two months if the detail design holds," Karan said.

"And the Tejas in service by late 1977."

"October 1977," Karan said. "If the contract is signed by December."

Vishwakarma said: "Will it be?"

Karan said: "Mehra's recommendation goes to the Air Staff. The Air Staff goes to the Ministry. The Ministry goes to the Finance Ministry. At every stage the people who understand what they're approving will approve it and the people who don't understand will slow it down." He paused. "We have enough people in this country now who understand what has been built that the slowing-down has limits."

He looked at the flag.

"In 1947," he said, "Mehra was flying Spitfires. Twenty-seven years. In twenty-seven years India went from flying borrowed British aircraft in a British war to building a supercruising multi-role aircraft with a radar that can see further than anything in the American inventory and an engine that is more efficient than anything Pratt and Whitney has produced."

He looked at Vishwakarma.

"That is not a coincidence," he said. "It is a direction. The direction was set in 1947 when independence meant that what India built would be India's. The problem from 1947 to 1970 was that the capability to build it didn't yet exist. The problem from 1970 onward is managing the building fast enough that the capability compound on itself before the external pressure finds the gaps."

Vishwakarma said: "The F-16. The MiG-25. The F-14."

"Answered by the Trinetra and the Astra Mk2," Karan said. "Partially. Not completely. No single answer is ever complete. The answer is the compounding — the Tejas answers today's threats and the Garuda answers the threats that come after today's, and whatever comes after the Garuda is already in someone's notebook somewhere in this facility."

Vishwakarma looked at him. "Whose notebook."

"I haven't identified them yet," Karan said. "But they're here. Someone who flew the Tejas on paper for the first time when Rathore's first-flight video went around the engineering team and thought: what comes next. That person exists. It takes time to find them."

Vishwakarma said: "The Garuda team."

"The Garuda design team has three people who are thinking past the Garuda," Karan said. "I've been watching them. They're not doing it on programme time — they're doing it on their own time, after hours, in the notebooks that go home with them. That is the right way to build what comes after. You don't plan it. You make the conditions where someone smarter than you about the specific problem can be working on it before you know what the problem is."

He turned toward the main building.

"Tomorrow," he said. "Flight twelve."

Vishwakarma said: "Anything specific for twelve?"

"The full high-alpha characterisation," Karan said. "To twenty-eight degrees and held for sixty seconds. The characterisation is complete enough to do it safely and we need the data before the evaluation team arrives."

"Rathore's agreed?"

"I proposed it last week. He asked me one question — the FBW saturation margin at twenty-eight degrees held for sixty seconds. I gave him the analysis. He said: all right."

"That's very Rathore," Vishwakarma said.

"Yes," Karan said. "It is."

He walked back inside.

The flag on the administration building was still flying.

Sunset in forty minutes.

After sunset the flag would come down, the way flags came down at sunset on days they had been put up to mark. Tomorrow it would not be there — tomorrow was just a day, an ordinary working day, a day of flight twelve and engineering meetings and programme management and the hundred operational decisions that kept a development programme moving.

But today it had flown.

And what had flown today — the aircraft, the engine, the radar, the doctrine, the possibility — had flown honestly. Had flown on its own design and its own engineering and its own materials and its own pilots. Had flown over Indian ground from an Indian airstrip with Indian fuel in an Indian engine.

Twenty-seven years after Mehra had flown a Spitfire.

Independence Day had been appropriate after all.

End of Chapter 166