Chapter 163: TEJAS FLIGHT
16 July 1974 — Gorakhpur, Shergill Aviation Complex
The hangar doors opened at four forty in the morning.
Karan had called the night shift supervisor at four-fifteen and asked for it. The supervisor — Krishnanand Rao, who had been running night operations for Shergill Aviation for two years and who had learned, in those two years, that Karan's pre-dawn requests were always followed by something that mattered — said, " Yes, sir, " and did it without asking questions. That was what good people did. They understood the shape of a situation and they responded to it correctly.
The aircraft was inside.
Karan parked. He walked to the hangar entrance and stood at the threshold for a moment — the July pre-dawn behind him, warm and damp in the specific way of the Gorakhpur monsoon season when the rains had come through the previous week and the air still held the memory of water — and the lit interior in front of him.
He looked at the S-35 Tejas.
It was, for a long moment, simply the fact of it. The aircraft sat on the hangar floor in the way that aircraft sat when they were ready — not inert, not passive, but charged with a quality that objects had when they had been built for a specific purpose and that purpose was about to be fulfilled. Every line of it was an answer to a question. The blended wing-body where the fuselage grew into the wing without a seam, the underslung inlet below the nose, the twin vertical fins canted outward at the angle that the radar cross-section calculations had specified, the Kaveri Mk2's exhaust nozzle at the tail in its closed ground configuration.
He walked in.
His footsteps on the hangar floor were the only sound. The ventilation systems and the faint hum of the ground power connection and the distant sound of the city waking up beyond the perimeter wall, and his footsteps.
He walked to the nose.
He put his hand on the radome — the composite nose cone that covered the Netra Mk2 radar antenna, smooth and slightly cool to the touch in the July morning before the heat arrived. He stood there with his hand on the nose of the aircraft for a long moment.
He thought about what had happened two weeks ago.
He did not think about it in detail — the details were complete, documented, handled, the kind of thing that was done and was not going to be undone. But the weight of it was still present, the way the weight of certain things was present even after the things themselves were finished. The Bureau was different now. He was different now, in a specific way that he was still understanding.
He took his hand off the radome.
He walked around the aircraft.
He did what he had done before every significant milestone in the Bureau's history — walked the thing alone, without the team, without the ceremony, in the specific privacy of a person who needed to understand what was in front of him before the day's work required him to present it to others.
The inlet lip — the composite layup that the materials team had developed and that Anjali Desai had defended in three consecutive design reviews against arguments for a lighter but less robust configuration. She had been right. She was almost always right about materials, the way people were right about things when they had paid attention to those things long enough to understand them past the point of calculation into something that functioned like instinct.
The cockpit. He climbed the access ladder and looked in through the canopy. The three multifunction displays, dark now. The sidestick on the right console. The head-up display combiner glass in its deployed position. The instrument panel that Rathore had revised seventeen times in the simulator — not the configuration he would have specified from an engineering perspective alone, but the configuration that a pilot needed, which was different, which was the human factors problem that made avionics design either excellent or merely competent.
He climbed down.
He walked to the tail.
He put his hand on the exhaust nozzle and felt the metal cool against his palm and thought about the Kaveri Mk2 that was inside — the engine that Vardhan's team had spent two and a half years developing from the lessons of the Mk1, the engine that had run for the first time in this airframe three months ago and had performed, across forty-three sensor channels, exactly as the design required.
He said: "Hello."
To the aircraft.
In the empty hangar, at four-forty-five in the morning, with nobody watching.
He had said it to the S-27 prototype too, on the morning of its first flight. He would probably say it to the Garuda if he lived long enough to see that morning. It was not a ritual exactly — it was more honest than a ritual, more direct. The aircraft was the accumulated work of hundreds of people. The accumulated intelligence and precision and patience and argument of those hundreds of people had a presence that deserved to be acknowledged.
"Today," he said, to the aircraft.
The team began arriving at six.
Dr. Harsh Vardhan came first, at five fifty-five, which was not quite sunrise but close. He came in his work clothes — not his formal clothes, his actual work clothes — because today was a working day of the specific kind that made any other kind of clothes inappropriate. He walked directly to the aircraft without stopping to speak to anyone, went to the port engine inlet, crouched and looked up the duct with a small flashlight he carried in his jacket pocket.
He stood. He came to where Karan was standing near the tail.
"Inlet looks clean," he said.
"Yes," Karan said.
"Temperature this morning is thirty-one degrees," Vardhan said. "Humidity is high from the monsoon. Density altitude is going to be slightly degraded compared to our performance calculations."
"How much?"
"Three percent degradation in effective thrust," Vardhan said. "It's within the margin. The Mk2's output at this temperature is still above what we need for the flight envelope we're operating in today."
"You've already run the numbers," Karan said.
"I ran them last night," Vardhan said. "And again this morning at five when I woke up because I was running them in my head anyway and decided I might as well be awake." He paused. "The aircraft will fly correctly today. The engine performance at this temperature and humidity is — I'm not going to say exactly what I calculated because then you'll hold me to it. But it will fly correctly."
Karan looked at him. "Harsh."
"Yes."
"Thank you. For the engine."
"That is—" Vardhan stopped. He was not a man who was given to emotional statement. He was precise and technical and measured. He searched for the right word with the care of someone who wanted to say the specific thing. "That is something I didn't know if I would ever see in my professional life," he said. "India building an engine that was worth building."
Karan looked at him.
"It was worth building," Karan said.
"Yes," Vardhan said. "It was."
They stood at the tail of the aircraft in the brightening July morning.
Dr. Satish Vishwakarma arrived at six-fifteen with the pre-flight checklist on his clipboard and the expression of a man who had been carrying a clipboard to important events for thirty years and who had determined that the clipboard was the correct response to important events — not because the information on it was new, which it wasn't, but because walking through the checklist was the act through which anxiety was converted into usefulness, and that conversion was worth doing.
"The avionics startup sequence," he said to Karan. "We're running the full boot sequence at seven-thirty. I want two hours between the boot sequence and engine start. If anything anomalous shows up in the startup, we have time to assess."
"Agreed," Karan said.
"The Netra Mk2 initialization," Vishwakarma said. "Last time we had the mode pointer error. Krishnaswamy's team patched it in March. The patch has been verified in ground test forty-seven times. But today is the first time it's running in the actual airframe with the actual avionics temperature after sitting in this hangar at monsoon humidity."
"You're worried about the temperature effect on the patch," Karan said.
"I'm not worried," Vishwakarma said. "I'm checking. Those are different things."
"What does the temperature analysis show?"
"The patch is in software. Software doesn't care about temperature. The concern would be if the temperature affected the hardware that runs the software — specifically the avionics bay's cooling performance. If the bay temperature is higher than the design spec because of monsoon humidity loading on the cooling system—"
"Then the software runs slower," Karan said.
"Then the software runs slower, which means the initialization sequence takes longer, which means the mode pointer might be in the wrong position for longer at startup. Which the patch was supposed to prevent, but which it was verified to prevent at standard temperature, not at monsoon-elevated temperature." He looked at Karan. "It's probably fine. I want to verify probably."
"How do you verify?"
"By running the startup sequence at seven-thirty and watching the avionics bay temperature telemetry during initialization and comparing it to the standard-temperature verification runs." He made a note on the clipboard. "If the temperature is within two degrees of the verification standard, I'm satisfied. If it's outside that range, we assess."
Karan looked at him. "Satish," he said.
"Yes."
"This aircraft is not going to fail today."
Vishwakarma looked up from the clipboard. "I know that," he said. "I believe that. I have built this aircraft and I know what it is and I believe it will fly correctly today." He paused. "I'm still checking the avionics bay temperature during the startup sequence."
"Good," Karan said.
"Because that is what we do," Vishwakarma said. "We believe in the thing and we check the thing and we fly the thing. The believing and the checking are both necessary."
Karan looked at the aircraft.
"Yes," he said. "They are."
Srinivasa Ramanathan arrived at six-twenty and went directly to the whiteboard that the ground crew had positioned near the hangar's west wall — the board that had the day's flight envelope plotted on it, the performance predictions for each phase of the first flight. He stood in front of the board with his arms crossed and looked at it the way he looked at aerodynamic data, which was the specific focused look of a man reading something in numbers that most people read in words.
He was still looking at it when Karan came to stand beside him.
"The angle of attack limit for today," Ramanathan said without turning. "Twenty-two degrees. We're not going above twenty-two degrees today."
"Rathore agreed to that?" Karan said.
Ramanathan turned to look at him. "Rathore suggested eighteen. I pushed it to twenty-two because the simulator data is very clean at twenty-two and the fly-by-wire protection should be authoritative at that limit. We went back and forth about it for an hour on Thursday."
"Who won?"
"He won on the approach speed," Ramanathan said. "I won on the AoA limit. We each got something. That's how it works."
Karan looked at the board. The flight profile for today: takeoff, initial climb to 5,000 metres, level flight assessment, a series of manoeuvres within the conservative initial envelope, landing. A first flight profile — not exploring the aircraft, exactly, but making the first real contact with it. Introducing the aircraft to its own element.
"The boundary layer transition point on the upper wing surface," Ramanathan said. "I've been thinking about it since Tuesday."
"You're always thinking about the boundary layer," Karan said.
"Because the boundary layer is always the question," Ramanathan said, with the mild impatience of a man who has stated a truth so many times that the need to state it again is itself faintly annoying. "The computational fluid dynamics gives me a transition point at approximately thirty percent chord at the design cruise condition. The wind tunnel confirms this. But the wind tunnel is a wind tunnel and the flight is a flight, and the specific quality of the air in the flight — the turbulence intensity, the atmospheric boundary layer, the temperature gradient, the humidity from the monsoon — none of those are exactly replicated in the tunnel."
"What's the concern?"
"If transition happens earlier than predicted — at twenty-five percent chord instead of thirty — we get more turbulent flow over the upper wing surface, which means more skin friction drag, which means the cruise performance is slightly below the prediction." He paused. "Not enough to matter operationally. Enough to matter for my confidence in the computational model."
"You want to calibrate the model against the first flight data," Karan said.
"I want to know where the transition actually happens in the actual aircraft in the actual air of Gorakhpur on the sixteenth of July 1974," Ramanathan said. "Yes. I want to know the truth of the thing, not the prediction of the thing."
Karan looked at him.
"The truth of the thing," he said.
"Yes," Ramanathan said.
"That's what today is for," Karan said.
Ramanathan looked at the flight profile on the board.
"Yes," he said. "That's what today is for."
Dr. Alok Misra arrived at six-thirty-five, slightly later than the others, and came in with the quality of a man who had been doing something specific on the way rather than simply traveling. He had a small notebook under his arm — his analysis notebook, the one that contained the fly-by-wire control law parameters and the specific numerical signatures of how the flight control system was expected to behave under various loading conditions.
He came to where Karan and Ramanathan were standing.
"The control law," he said. "I made one modification last night."
Karan looked at him. "Last night."
"At nine-thirty," Misra said. "After the final simulation run. I found a parameter in the pitch rate limiting logic at the high-AoA boundary that was set three percent conservative in the simulator baseline. Three percent is fine for simulation. In the actual aircraft, the actual inertia distribution at fuel load, three percent conservative might produce a slight lag in pitch response at the limit that the pilot would feel as — heaviness."
"Rathore noticed this?" Karan said.
"Rathore didn't notice it because the simulator doesn't model the inertia at this fuel state precisely," Misra said. "I noticed it because I was running parameter sensitivity studies and the pitch response at high AoA with the actual fuel mass distribution was — not wrong. Not unsafe. Slightly heavier than I wanted."
"And you changed it at nine-thirty last night," Karan said.
"I changed it at nine-thirty and verified the change against the hardware-in-the-loop simulation and the results were correct and I logged the change in the software control documentation and I am telling you about it now because you should know." He said all of this with the flat directness of someone who does not see any ambiguity in what he has done and is not interested in performing regret he doesn't feel. "The change is correct. The aircraft will respond better for it."
"Did you tell Rathore?" Karan said.
"I'm telling him at seven when he arrives," Misra said. "It will change how the aircraft feels in his hands at the high-AoA end of today's envelope. He should know before he flies."
Karan looked at him.
"Alok," he said.
"Yes."
"If the change had been wrong—"
"It's not wrong."
"If it had been," Karan said, "and you hadn't told anyone until now—"
"I ran forty validation cases," Misra said. "The change is correct. I don't make software changes to flight-critical systems and not verify them." He paused. "I understand the process concern. I am telling you now so that the change is documented in the morning briefing and Rathore knows before he flies. That is the process. I followed it."
Karan looked at him for a moment.
"You are," he said, "the most careful person I have ever worked with."
"Yes," Misra said, without inflection. "I know."
"I mean it as a compliment."
"I know," Misra said again. He opened his notebook. "The roll-yaw coupling at twenty degrees AoA. I want to talk about the expected feel."
Wg Cdr Vikram Rathore arrived at seven in the morning.
He arrived in his flight suit, which was the correct choice in the specific way that all of Rathore's choices tended to be correct — not because he thought carefully about what was correct before making them, but because his understanding of situations was accurate enough that the correct response was usually the obvious one to him. He was flying today. He wore his flight suit. This was simple.
He came in through the main hangar entrance and stopped.
He looked at the aircraft.
He stood in the entrance for a moment — not long, perhaps fifteen seconds — and he was very still in those fifteen seconds in the specific way that pilots were still when they were looking at an aircraft they were going to fly. Not assessing the aircraft. Receiving it. Building the initial contact between the person and the machine that preceded everything else.
Then he came in.
He went to Karan first.
"Morning," he said.
"Morning," Karan said.
"I slept," Rathore said. "Eight hours. I want you to know that because last time—" He stopped. He looked at Karan. "Last time I flew something significant for the first time, you told me afterward that you hadn't slept."
"I slept last night," Karan said.
"Good," Rathore said. He meant it. "You look—" He paused, looking at Karan with the specific attention of someone who read physical states professionally. "You look like someone who has been carrying something for two weeks."
"I have been," Karan said.
"Does it affect today?"
"No," Karan said. "Today is separate."
"Good," Rathore said again. He looked at the aircraft. "She looks ready."
"She is ready," Karan said.
"The way it sits," Rathore said. "Some aircraft, when they're ready, sit differently. The weight distribution is right, the landing gear is in the right position, the whole thing is — balanced. In the way that means it was made correctly." He walked toward the aircraft. "I want to do the external inspection."
"Take your time," Karan said.
Rathore walked around the aircraft. He walked around it slowly, with the specific quality of looking that was different from engineering examination — not checking for defects or verifying specifications, but making the contact that a pilot made with an aircraft before a first flight, the specific getting-to-know-you that preceded everything else.
He stopped at the cockpit.
He climbed the access ladder.
He looked in through the canopy for a long moment without saying anything.
Then he looked down at Karan, who had followed him and was standing at the base of the ladder.
"The sidestick position," Rathore said. "I moved the grip angle two degrees in the last simulator session."
"I know," Karan said. "Anjali updated the manufacturing record."
"The two degrees matters," Rathore said. "It sounds like nothing. But at sustained G — when your arm is tired and you're trying to make a small correction in pitch — two degrees is the difference between a natural input and one that requires conscious muscular effort." He looked at the cockpit. "In combat, at the limit of a sustained turn, the inputs that require conscious muscular effort are the ones that happen too late."
"So the two degrees is a life decision," Karan said.
"The two degrees is a life decision," Rathore confirmed. He was still looking at the cockpit. "The whole aircraft is life decisions. Every parameter. Every interface. Every trade-off between one requirement and another." He paused. "I want to ask you something."
"Ask," Karan said.
"The last two weeks," Rathore said. He said it carefully, the way he said things that he wanted to approach correctly. "I was in the simulator for the final preparation sessions and some of the programme staff seemed—" He stopped. "The atmosphere in the Bureau changed. Something happened."
"Yes," Karan said.
"Does it—" Rathore started.
"The aircraft is clean," Karan said. "The programme is clean. Nothing that happened affects what you're flying today."
Rathore looked at him from the ladder.
"I'm not asking about the aircraft," he said. "I know the aircraft is clean. I know the programme is clean. I've been through every system. I understand what I'm flying." He paused. "I'm asking about you."
Karan looked up at him.
There was a quality to Rathore's attention that was different from the way most people looked at things — the pilot's quality of seeing what was actually there rather than what was expected or comfortable. He had spent twenty years in cockpits training himself to see what the instruments showed rather than what he hoped they showed, and that training had produced a man who applied the same discipline to the people in front of him.
"I'm fine," Karan said.
Rathore was quiet for a moment.
"Karan," he said.
"Yes."
"I've been flying your aircraft for four years," Rathore said. "The S-27 when it was the most advanced aircraft India had ever built and everyone said it couldn't be done. The S-22 Makara, when landing on a carrier was a thing that people in this country had never done. Today this." He looked at the cockpit again. "Every time I got in one of your aircraft, I trusted it because I understood it. Not blindly. I understood the engineering decisions, I understood why each system worked the way it worked, I understood what the aircraft could do and what it was supposed to do and where the edges were." He looked back down at Karan. "I trust you the same way. I trust your judgment the way I trust the aircraft's design. Not blindly. Because I've watched you make decisions for four years and the decisions have been correct."
Karan said nothing.
"Whatever happened," Rathore said, "you handled it correctly. I know that without knowing what it was. Because you handle things correctly. It's who you are." He paused. "So stop carrying it on the day the Tejas flies for the first time. You can pick it back up tomorrow. Today, just let the aircraft be the thing it is."
Karan looked at him.
"I'll try," he said.
"Good," Rathore said. He looked at the cockpit one more time. "The HUD symbology. Misra's final revision — where is the AoA indicator?"
"Upper left of the primary field," Karan said. "Below the altitude tape."
"Show me on the display card," Rathore said.
They went over the HUD layout for twenty minutes, standing at the cockpit ladder, Karan holding the display reference card and Rathore asking precise questions about where each parameter appeared and how it moved with changing conditions. This was the specific work of a pilot and an engineer communicating before a first flight — not the broad strokes, the details, the specific details that determined whether the pilot's attention in the cockpit went to the right place at the right time.
At seven-thirty, the avionics startup sequence.
The ground power unit was connected. Vishwakarma's team was at the avionics bay with the temperature telemetry display. Karan and Rathore and Misra were standing near the cockpit where Rathore had taken his seat for the sequence — not the flight strapping-in, not yet, just the operational position from which the startup was run.
Rathore ran through the checklist with the ground crew chief — a man named Bahadur Singh who had been handling aircraft at the Bureau for three years and who moved around the aircraft with the practiced efficiency of someone who had done this enough times that his body knew where to be.
"Avionics power," Rathore said.
"Avionics power on," Bahadur confirmed.
The displays came to life.
Left MFD: tactical display, initialising — the specific boot sequence graphic, the system checking itself. Centre MFD: navigation and systems. Right MFD: sensor and weapons management.
The head-up display came on: the specific green-white of the S-35's HUD illuminating the combiner glass in the pre-dawn indirect light of the hangar, the initialization text appearing and cycling through its checks.
Vishwakarma, at the avionics bay with the temperature telemetry: "Bay temperature is thirty-three degrees. That's two degrees above the standard verification condition."
He looked at Karan.
Karan looked at him.
"Two degrees above the verification limit," Vishwakarma said. "I said two degrees was my comfort threshold."
"What does it mean for the initialization?" Karan said.
"It means the cooling system is working harder than in standard conditions," Vishwakarma said. "The cooling system is working correctly — the temperature is elevated but stable, it's not rising. The avionics are within their operational temperature range. It means—" He stopped. He was looking at his telemetry display. "It means the initialization is running at standard speed. No degradation." He paused. "The Netra startup sequence is complete. Mode initialisation — correct mode." He looked up. "The patch held. We're clean."
Karan exhaled.
From the cockpit, Rathore said: "The tactical display is showing correct heading and position. The navigation is initialised. The systems are—" A pause. "Alok. Your modification."
"Yes," Misra said from beside the ladder.
"Walk me through it. The pitch rate limiting change."
"At high AoA — above eighteen degrees — the original control law applied a three percent conservative limit on pitch rate response. I removed that conservatism. The response is now closer to what the aerodynamics allow rather than the simulator baseline."
"What will I feel?"
"At twenty degrees AoA in a sustained pull," Misra said, "you'll feel slightly less heaviness in the pitch axis. The aircraft will feel more responsive, less like it's resisting you."
"More like it's helping me," Rathore said.
"Yes," Misra said. "More like it's helping you."
A pause from the cockpit.
"Good," Rathore said. "That's what I wanted."
"I know," Misra said.
Rathore looked over the side of the cockpit at Misra. "You changed flight-critical software the night before the first flight," he said.
"Yes," Misra said.
"That is—" Rathore started.
"Correct," Misra said.
"I was going to say alarming," Rathore said.
"It's alarming only if the change is wrong," Misra said. "The change is not wrong. I ran forty validation cases. The behaviour is what I described."
Rathore looked at him for a moment.
"Alok," he said.
"Yes."
"You have done this exact thing — changed something the night before at the last minute — three times in the programmes I've flown. The S-27 sidestick gain coefficient. The S-22 autothrottle response curve. Now this."
"Yes," Misra said.
"And every time it was correct," Rathore said.
"Yes," Misra said.
"And you knew each time that it was correct before you changed it."
"I believed it was correct," Misra said. "I verified it. The verification confirmed the belief. So yes. I knew."
Rathore looked at him for another moment.
"If you ever believe something is wrong but can't verify it before a first flight," Rathore said, "tell me."
"I would tell you," Misra said.
"Even if it cancelled the first flight."
"Especially if it cancelled the first flight," Misra said, with the flat certainty of someone for whom this was not a question.
Rathore nodded. He looked at the instrument panel in front of him.
"All systems initialised," he said. "Avionics are clean. Ready to proceed to engine start sequence."
Engine start was at nine-fifteen.
The sequence ran as designed. The starter motor engaged, the Kaveri Mk2's core spun up through the rotation curve that Vardhan's team had characterised across sixty-three test cycles, the igniters fired, the fuel-air mixture caught, the engine established.
The sound of the Mk2 at idle was the sound that Karan had first heard in the engine test cell and that had not changed — the turbofan sound with the specific character of this engine, the frequency mix of the fan and the core and the turbine, the way it sat in the chest of people standing on the apron as a physical presence rather than just an acoustic one.
Vardhan was at the propulsion telemetry display with two engineers. He was quiet for thirty seconds after the engine established, reading.
Then he looked at Karan.
He gave a single nod. Not a small nod — a deliberate, complete nod, the nod of a man who has been watching forty-three sensor channels and has found that all forty-three are telling him what he hoped they would tell him.
Karan nodded back.
In the cockpit, Rathore was running through the post-start checks. His voice on the radio was the voice that pilots used in cockpits — not the conversational voice, the specific professional register that was slightly more clipped, slightly more precise, the voice of someone who has shifted modes.
"Oil pressure nominal," Rathore said. "Temperature nominal. Fuel flow nominal. Hydraulic pressure nominal. Flight control power — all four hydraulic circuits confirmed. Fly-by-wire — mode activated, self-test complete, no faults." A pause. "Netra radar — hot standby, mode correct, no faults." Another pause. "Astra weapons management — standby, ready." A longer pause. "Aircraft is ready for taxi."
Karan looked at Ramanathan, who was standing to his left.
"Winds?" he said.
"Northwest at twelve knots," Ramanathan said. "The runway heading is northeast, which gives us roughly forty degrees of crosswind component. About eight knots of crosswind."
"Within limits?" Karan said.
"First flight crosswind limit is fifteen knots for the Tejas," Ramanathan said. "Eight is well within."
"Density altitude?"
"Three hundred and forty metres effective density altitude with this temperature and humidity," Ramanathan said. "Takeoff performance is within spec. The rotation speed will be four knots higher than the standard condition, the liftoff distance is approximately thirty metres longer." He paused. "The runway is two thousand eight hundred metres. We need eleven hundred to lift off. We have significant margin."
"The speed at rotation," Rathore's voice came from the cockpit radio. "I want to confirm — one hundred and forty-eight knots with the density altitude correction."
"One hundred and forty-eight confirmed," Ramanathan said into his radio. "We've updated the performance cards."
"Good," Rathore said. "I want to verify one more time: the rotation technique. Steady pull to fifteen degrees attitude and hold. Not rotating to target AoA, rotating to target attitude and letting the aircraft fly itself off."
"Correct," Karan said. "The aircraft will fly off at fifteen degrees attitude. Don't chase the liftoff. Let it happen."
"Let it happen," Rathore repeated. "Understood." A pause. "The approach to our first assessment manoeuvre — the steady-state turn at twenty degrees AoA. I'll establish the turn, confirm I can maintain altitude, and then assess the pitch response quality in the sustained pull. I'm specifically looking for what Alok described — the reduction in heaviness. If I feel something different from what he described, I'll disengage the manoeuvre and return to level flight."
"And you'll tell me what you felt," Misra said.
"And I'll tell you exactly what I felt," Rathore said. "I'll give you every nuance. I know that's what you need."
"It's what I need," Misra said. "And I'll compare it to the forty validation cases and we'll know whether the model is correct."
"We'll know," Rathore confirmed.
"Clear for taxi," the tower confirmed.
The aircraft began to move.
The taxi from the hangar to the runway threshold took eight minutes.
Karan watched from the observation position — the elevated platform that the Bureau had built at the runway's edge for exactly this purpose, high enough to see the full length of the runway and far enough from the centerline to be outside the noise footprint.
Ramanathan was beside him. Vardhan was at the propulsion monitoring station, headset on, watching the engine telemetry that was being transmitted from the aircraft's flight data system to the ground station in real time. Misra was at the fly-by-wire monitoring station, watching the control surface positions and the flight control computer outputs.
Vishwakarma was beside Karan.
"The taxi looked correct," Vishwakarma said. "The nosewheel steering is responsive. The brakes feel properly bedded. He reported the controls were full and free during the taxi." He had the clipboard. The pre-takeoff checklist. He was going through it line by line even though every line had already been verified and would be verified again before Rathore lined up for takeoff.
"Satish," Karan said.
"Yes."
"What are you actually checking at this point?"
Vishwakarma looked at the clipboard. Then he looked at the aircraft, which was holding at the runway threshold while Rathore completed the final pre-takeoff checks.
"I'm not checking anything specific," he said. "The checks are done. What I'm doing with the clipboard at this point is—" He paused. "I'm keeping my hands occupied so the rest of me can be present without doing something unhelpful with the nervousness."
Karan looked at him.
"You're nervous," he said.
"I'm extremely nervous," Vishwakarma said. "I have built this aircraft. I have checked this aircraft in every detail. I believe absolutely that it is going to perform correctly today. I am also extremely nervous, because this is the first flight of a new aircraft and first flights are things that test what you know against what you don't know yet."
"The things you don't know yet," Karan said.
"Every design has things that are discovered in flight and not in the test cell or the wind tunnel or the simulator," Vishwakarma said. "The specific way the aerodynamics interact with the actual air at altitude. The way the structural resonances feel different from the predictions. The way the pilot integrates with the aircraft's systems in the actual conditions. We know this aircraft very well. We don't know it completely. Today we will learn the parts we don't know completely."
He paused.
"The nervousness," he said, "is appropriate for the situation."
"Yes," Karan said. "It is."
Rathore's voice on the radio: "Ready for takeoff."
The tower: "Tejas Zero-One, cleared for takeoff. Runway two-zero. Winds northwest at twelve knots."
"Tejas Zero-One, rolling," Rathore said.
The engine sound changed.
Not dramatically — the aircraft was not at full power yet, the Mk2 was accelerating through the power range as the throttle advanced — but the quality of the sound changed in the way that a machine's sound changed when it stopped being at rest and started doing its work. The turbofan note deepened and broadened. The aircraft began to move.
It accelerated down the runway.
Karan watched it.
He had watched the S-27 prototype's first takeoff from approximately this position. He had watched the S-22 Makara's first flight. He had watched forty-two S-27 production aircraft fly away from this runway. Each time the watching was different — not because the aircraft were different, though they were, but because the significance of each event was different, and significance changed the quality of watching.
Today the quality of watching was the specific quality of a thing that had been worked toward for two and a half years — from the first design specification to the first drawings to the first model to the wind tunnel to the simulator to the ground tests and now to this — arriving at its moment.
The aircraft reached rotation speed.
Karan saw the nosewheel rise off the runway.
Then the main gear.
The S-35 Tejas was flying.
It was in the air for a long moment before anyone on the observation platform said anything.
Not because there was nothing to say — there was, there was plenty to say, everything that came after the aircraft was airborne was technical and measurable and reportable. But the first moment of a new aircraft in the air was not a technical moment. It was a specific other thing that had no good name. The thing that happened when a thing that had existed only as a description existed now as a physical fact in the physical world.
Vishwakarma set the clipboard down. Just set it on the railing and left it there.
Ramanathan said, very quietly, in Tamil — not translating, just saying the thing in the language in which he thought when thinking was genuine — something that Karan didn't understand but that he understood was the right kind of thing.
Vardhan, at the propulsion station, had his eyes on the engine telemetry and his hand on his radio and was doing his job. But the specific quality of stillness in him — the stillness of someone who was receiving information that was confirming what they had hoped — was visible.
Misra was watching the fly-by-wire outputs. His expression was the same as it always was — flat, focused, reading. But his pen had stopped moving, which was unusual for Misra, whose pen was almost always moving.
Karan watched the aircraft climb away.
The Kaveri Mk2's sound changed as the aircraft climbed — receding, shifting in frequency with the distance, becoming the specific high sound of a jet aircraft in a climb, the characteristic signature of power concentrated into forward thrust.
The aircraft was performing correctly.
He could tell this from the climb angle, which was within the predicted range, and from the absence of anything anomalous. First flights that were going correctly looked like this — steady, controlled, the aircraft doing what it was designed to do without drama or surprise. Drama in a first flight was not a desirable quality.
His radio crackled.
"Tejas Zero-One," Rathore's voice. "Airborne, climbing through two thousand feet. All systems nominal. Engine stable. Flight controls—" A pause. "Flight controls are excellent. The sidestick response is — I need to give you Alok's feedback in real time."
Misra activated his radio. "Go ahead."
"The pitch axis," Rathore said. "Clean. Very clean. There is no heaviness at the stick. The aircraft is responding to pitch inputs at the rate I expect from the angle of attack response, without any lag between input and response. It feels — it feels like what you said it would feel like."
"Describe the specific sensation at the stick," Misra said.
"The stick force gradient in pitch," Rathore said. "In the S-27, at this flight condition, there's a slight stiffening at the top of the pitch range that tells you you're near the limit. In this aircraft, the gradient is smooth all the way to the limit. No artificial stiffening. The limit protection is in the system, not in my hand."
"The control law is providing limit protection through angle-of-attack feedback rather than stick force graduation," Misra said, for the benefit of the record he was keeping. "Does the limit feel abrupt or graduated?"
"Graduated," Rathore said. "Very graduated. I reached the initial AoA limit — I'm at fifteen degrees, I'm not at twenty yet — and I could feel the system beginning to moderate my input. Not stopping it. Moderating. Telling me I'm approaching the boundary without slamming a wall in front of me."
"That's the correct behaviour," Misra said.
"It's better than correct," Rathore said. "It's the right behaviour. The aircraft is talking to me. Not shouting. Talking."
Misra made a note.
"The aircraft tells you the truth," Karan said, into his radio.
A pause.
"Yes," Rathore said. "That is exactly what it's doing."
The flight lasted fifty-three minutes.
In those fifty-three minutes, Rathore explored the initial flight envelope — the conservative first-flight envelope, within which the aircraft could be said to have been introduced to itself rather than fully tested. He flew straight and level at various speeds. He made gentle turns, both directions, noting the roll coordination and the yaw coupling and the way the aircraft balanced the competing demands of roll input and directional stability. He climbed to 5,000 metres and noted the Kaveri Mk2's performance at altitude — the thrust available, the fuel consumption, the way the engine responded to throttle inputs at reduced air density.
He did the AoA assessment.
"At twenty degrees," Rathore said. "Establishing the turn."
His radio transmitted the sound of his breathing — slightly elevated, the physical work of flying a high-G manoeuvre — and the sound of the cockpit.
"Twenty degrees AoA," he said. "Sustained turn. Altitude stable. Fuel flow — nominal. Engine — nominal." A pause. "The pitch response. Alok, the pitch response at twenty degrees in the sustained turn is — the system is doing exactly what you described. No heaviness. The aircraft is in the turn, I'm maintaining the turn with a steady pull, and the effort in my hand is — appropriate. Not too light that I can't feel where I am. Not heavy enough that I'm fighting the aircraft."
"The force level," Misra said. "Quantify if you can."
"Approximately six kilograms at the stick for this turn rate," Rathore said. "I'll give you the precise measurement from the stick force instrumentation when I land. Six kilograms feels right. The S-27 at comparable conditions is around seven and a half. The Tejas is easier to hold."
"Easier means less fatiguing over a long engagement," Karan said.
"Over a thirty-minute air combat, the difference between six and seven and a half kilograms means my arm is significantly less tired when the critical moments happen," Rathore said. "That is an operational advantage, not just a comfort improvement."
"Put that in your debrief notes," Karan said.
"It's already in my head," Rathore said. "It will be in the debrief."
He disengaged the turn. He levelled out.
"Clean-up," he said. "Reducing speed. Setting up for the approach."
Ramanathan activated his radio: "Winds have shifted slightly. Now northwest at nine knots. Crosswind component is seven knots."
"Better," Rathore said. "Thank you."
"The approach speed," Ramanathan said. "One hundred and thirty-eight knots in the current conditions."
"One thirty-eight," Rathore confirmed. "Setting up the approach."
The landing.
Of all the phases of a first flight, the landing was the one that concentrated the watching. The takeoff was the flight beginning — dramatic, visible, charged with the energy of departure. The approach and landing was the flight concluding — and a conclusion was always a test, always the moment at which what had been built was measured against what it was meant to be.
Karan watched the aircraft on final approach.
The S-35 Tejas on approach was a different visual quality from the S-27. The S-27 on approach had the delta wing's characteristic flat attitude — high angle of attack, large wing area catching the air at low speed, the aircraft presenting a large planform to the observer on the ground. The Tejas's blended wing body produced a different sight picture — the fuselage and wing merged into a shape that was lower in aspect ratio, presenting as a more compact object on approach, the aircraft appearing to come down at a slightly different angle.
Rathore's radio: "On final. Runway in sight. Speed one thirty-seven, one knot under target. Power adding slightly."
"Good," Karan said.
"The descent rate is — nominal. I'm on the glideslope. The HUD is showing me everything I need." A pause. "The landing gear feels good. The aircraft is stable in the approach. There's a slight Dutch roll oscillation in gusty conditions — I'm countering it with rudder inputs, it's manageable, I'll note it in the debrief."
"Dutch roll in gusts," Ramanathan said, making a note immediately.
"Manageable," Rathore said again. "Not a problem for operational conditions, might be slightly uncomfortable in turbulence. Worth examining the lateral-directional damping."
"Noted," Ramanathan said.
"Approaching threshold," Rathore said. "Speed one thirty-five. Two knots under."
"Add power," Ramanathan said.
"Adding," Rathore said.
The aircraft crossed the threshold.
Rathore flared — the slight pitch up that slowed the descent rate, the specific technique that converted forward speed into altitude control in the final moments before touchdown. The sink rate decreased. The aircraft settled.
The main gear touched.
The sound was audible from the observation platform — the specific sound of rubber on tarmac, the brief squeal of the tires beginning to roll, the system absorbing the landing load.
The nosewheel touched.
The aircraft was on the ground.
It rolled out — smooth, controlled, the deceleration of the brakes gradually bringing the aircraft to taxi speed.
On the observation platform, nobody said anything for a full three seconds.
Then Vishwakarma said: "Perfect landing."
It was not a compliment to Rathore specifically. It was a statement about the aircraft — that the landing geometry was correct, that the approach characteristics had supported the landing in the way that they were designed to support it, that the aircraft's behaviour in the flare had been what a pilot needed it to be.
Ramanathan said: "The Dutch roll will need attention."
"Yes," Karan said. "We'll look at the lateral damper settings."
"It's not a difficult fix," Ramanathan said. "The yaw damper gain is probably slightly conservative. A thirty percent increase in gain should address the oscillation in gusts without overcorrecting into sluggishness in calm air."
"We'll verify in simulation first," Karan said.
"Obviously," Ramanathan said.
Rathore's radio: "Tejas Zero-One, clear of the runway. Request taxi to the hangar."
Tower: "Tejas Zero-One, taxi approved. Congratulations on a successful first flight."
A brief pause.
Then Rathore's voice: "Thank the team on the ground. This is their aircraft. I just took it for its first walk."
The debrief was in the main conference room, two hours after the landing.
Rathore had come off the aircraft with the specific quality of someone who had just done something significant and was already processing it analytically. Not celebrating — that was not his mode. Processing. The pilot's instinct to convert experience into information was immediate and could not be postponed.
He had given his preliminary verbal debrief to Karan and Ramanathan and Misra on the apron, standing next to the aircraft still with the smell of hot metal from the engine around him. The Dutch roll oscillation. The pitch response confirmation. The stick force gradient. The HUD symbology — specifically that the angle of attack indicator needed to be half a size larger in the primary field because in the sustained turn he had been dividing his attention between it and the altitude tape and the indicator was fractionally too small for comfortable acquisition.
"Half a size larger on the AoA indicator," Misra said, writing.
"In the sustained-turn condition, I want to see it without searching for it," Rathore said. "The altitude tape is a natural visual anchor. The AoA indicator needs to be immediately adjacent and immediately readable. Half a size gives me that."
"That's a symbology change," Misra said.
"I know," Rathore said. "It's also a correct change."
"I agree," Misra said.
In the conference room, the full team was assembled. The engineers from every major discipline — aerodynamics, propulsion, avionics, structures — the programme managers, the test team. Twenty-three people around the table and along the walls.
Karan started the debrief.
"The S-35 Tejas flew its first flight today," he said. "Fifty-three minutes. All primary objectives achieved. The aircraft performed within predicted parameters across the envelope assessed." He looked around the room. "Vikram is going to give us the detailed pilot's assessment. Before he does — I want to say something first."
The room was quiet.
"Two and a half years," Karan said. "From the first specification to today. One hundred and twelve engineers across the design divisions. Thousands of design decisions. Forty-seven aerodynamic iterations. Sixty-three Kaveri test cycles. Twenty-two avionics integration fixes. All of it — every argument, every late night, every compromise that was right and every compromise that was wrong and had to be undone — all of it pointed to today."
He paused.
"The aircraft is honest," he said. "Rathore said it on the radio and it's the right thing to say. The aircraft tells you the truth. It tells the pilot what it's doing and what it's capable of and where the edges are. That honesty is not incidental to what this aircraft is — it is what this aircraft is. Every design decision that the people in this room made, made toward an aircraft that would be honest with the person who flew it." He looked around the room. "You made something honest. That's harder than making something powerful. Powerful is engineering. Honest is engineering and judgment and integrity and the willingness to tell the truth about the aircraft's limitations as well as its capabilities, all the way through the design process."
He let this sit for a moment.
"I want to tell you what happened in this facility two weeks ago," he said.
The room shifted. People who had known something had happened but not what — the atmosphere in the Bureau had communicated that something significant had occurred without communicating the specifics — looked at him.
"An engineer in the avionics integration team attempted to remove classified S-35 technical documentation from this facility for transfer to a foreign intelligence service," Karan said. "He was caught in this building before the transfer happened. The documentation was recovered. The programme is clean."
The room was very quiet.
"I'm telling you this now because you deserve to know," Karan said. "Not the details — the security investigation is ongoing and the details are restricted. But you deserve to know that it happened and that it was caught and that the aircraft you flew today, and the aircraft that the Indian Air Force will eventually fly, is not compromised." He paused. "I am also telling you because the person who caught the attempt was an engineer who noticed something wrong and acted on it immediately. Without that engineer, without that willingness to act on what was seen, this morning might have looked different." He looked around the room. "That engineer is in this room. He knows who he is. He doesn't need to be named. But his action is why today was what it was."
He looked at Rathore.
"Vikram," he said. "The debrief."
Rathore's debrief took an hour and twenty minutes.
He went through every phase of the flight with the methodical precision that test pilots used — not the narrative of an experience but the analytical description of a sequence, each observation categorised and quantified where quantification was possible and described qualitatively where it was not.
He talked about the takeoff — the specific feel of the rotation, the way the aircraft lifted off at exactly the attitude he had been targeting, neither early nor late, the landing gear retracting cleanly, the transition from runway to air happening in the way that a well-designed aircraft transitioned.
He talked about the initial climb — the engine performance, the thrust available, the way the Kaveri Mk2 responded to throttle inputs, the temperature and pressure readings against the predictions.
He talked about the level flight assessment — the drag at cruise speed, which was within two percent of the performance prediction and would require Ramanathan's team to look at the boundary layer transition to understand whether the two percent difference was prediction error or a real aerodynamic phenomenon.
"Two per cent under the prediction," Ramanathan said, making a note. "That means the actual drag is two percent lower than we calculated. The boundary layer is transitioning later than predicted."
"Which means what for the aircraft?" someone asked.
"It means the aircraft is more efficient than we expected," Ramanathan said. "The cruise performance is slightly better than the specification. The range is slightly longer. The fuel consumption is slightly lower. This is not a problem." He paused. "I want to understand why my model was wrong so the model is better for the next aircraft."
Rathore talked about the turning performance — the sustained turn, the AoA assessment, Misra's control law modification and what it felt like.
He talked about the Dutch roll.
"In turbulence or gusting conditions, there is a lateral oscillation — Dutch roll — that I had to counter with active rudder inputs," he said. "The oscillation is small in amplitude, roughly two degrees of roll angle, and the frequency is low enough to manage, but it required my attention. In a non-combat situation, this is merely uncomfortable. In an engagement, where my attention is divided between the tactical situation and flying the aircraft, this oscillation is something I would rather not be managing."
"The yaw damper gain," Ramanathan said. "I believe this is fixable. A thirty percent increase in the yaw damper gain should attenuate the oscillation significantly."
"How confident are you?" Rathore asked.
"I ran a preliminary calculation during the flight," Ramanathan said. "The flight data analysis will confirm. I believe the fix is correct."
"How long to implement and verify?"
"Simulation verification is one week," Misra said. "The software change is straightforward. Flight test verification — one flight, the second test flight, with the modified damper. Two weeks total."
"Then the second test flight is two weeks from today," Rathore said. "With the Dutch roll fix in place."
"And the AoA indicator size change in the HUD," Misra said.
"Yes," Rathore said. "Both changes for the second flight."
The debrief continued.
He talked about the approach and landing. The characteristics that had supported the landing — the stable descent, the clean flare, the touchdown that had been within ten metres of the aim point. He noted that the landing gear energy absorption was correct and that the rollout deceleration was as predicted.
He talked about the overall experience of the aircraft.
"The Tejas is a different aircraft from the S-27," he said. "This is obvious — different design, different mission, different performance envelope. But I want to be specific about how it's different, because how it's different is what matters for how we train pilots to fly it and what we tell the IAF about its operational character."
He looked around the room.
"The S-27 is an aircraft of authority," he said. "It communicates authority. When you're in the S-27, you know you're in something powerful and you feel that power in every input. The aircraft responds to your inputs with a quality of — commitment. It does what you tell it to do with full force."
He paused.
"The Tejas is an aircraft of precision," he said. "It doesn't communicate authority the same way. It communicates accuracy. When you make an input in the Tejas, the aircraft responds precisely — not powerfully in the way the S-27 is powerful, but exactly. The response is exactly what the input required and nothing more. It's more like—" He searched for the word. "It's more like a surgical instrument than a hammer. The S-27 is a hammer. The Tejas is a scalpel."
The room was quiet.
"For the missions the Tejas is designed for," Rathore continued, "precision is what's needed. Close air support, precision strike, the kind of engagement where the specific application of force matters more than the raw magnitude of it. The Tejas is exactly right for those missions." He paused. "The pilot who comes from the S-27 to the Tejas will need time to recalibrate. They'll be looking for the authority and they'll find precision instead and they'll need to understand that precision is not absence of capability, it's a different kind of capability."
He looked at Karan.
"That's what I'd put in the operational conversion training," he said. "Not just the technical differences. The character difference. The aircraft has a character and the character needs to be understood."
Karan was looking at him.
"Write that down exactly as you said it," Karan said. "In the debrief report. Verbatim."
"I will," Rathore said.
"The IAF evaluation team is coming in six weeks," Karan said. "ACM Latif and his team. I want the aircraft's character in the brief they receive. Not just the specifications. The character."
"I'll brief them myself," Rathore said. "It's more convincing from the pilot who flew it."
"Yes," Karan said. "It is."
The debrief ended at two in the afternoon.
The engineers went back to their work — the analysis of the flight data, the simulation verification of the Dutch roll fix, the HUD symbology modification. The Bureau went back to what it was: a place where things were built and checked and improved and built again.
Karan stayed in the conference room after everyone else had left.
He sat at the table.
He thought about the morning.
He thought about standing in the hangar at four-forty-five with his hand on the radome saying hello to the aircraft. He thought about Rathore on the ladder saying stop carrying it today. He thought about Vardhan at the propulsion station nodding — that single complete nod — when the engine data confirmed what the design had promised.
He thought about Patel.
Not with anger — the anger was still there, would be there for a long time, but it had settled into its permanent form, which was not the hot anger of the night but the cold, settled understanding of someone who had done what needed to be done and who was carrying the weight of it without being destroyed by it. The weight was appropriate. The weight was part of the thing.
He thought about what Rathore had said to him on the ladder.
The decisions have been correct.
He thought about the two weeks between July 1st and today. About the changes he had made to the Bureau's security protocols. About the all-hands meeting in which he had told the engineers — without naming names, without details — that the Bureau had been tested and had passed the test, and that the passing had depended on people acting on what they saw rather than looking away. About the two engineers who had been approached and had declined and had said nothing, and what he had done about them: not firing, because firing was wrong, but a hard conversation, a formal counselling, a specific requirement to attend the security awareness programme as instructors rather than as students, because teaching the right behaviour was how you converted shame about having failed to demonstrate it.
He thought about the first flight.
The aircraft was honest. Rathore had said it and it was true. The aircraft told you the truth.
He had built a Bureau that was supposed to tell the truth. The Bureau had been tested — not severely, not catastrophically; the documents had not left, the aircraft was not compromised — but tested. And the truth the Bureau had told was the truth that an engineer had seen something and acted on it, and that the system for catching something had caught it, and that the aircraft flying today was the aircraft that had been designed and built without the damage that the failure had attempted to do.
He sat in the conference room.
He picked up the notebook.
He wrote the date.
He wrote: S-35 Tejas first flight. 16 July 1974. Fifty-three minutes. Aircraft performed within prediction. Dutch roll in gusts to be addressed in simulation and second test flight. HUD AoA indicator to be resized. Kaveri Mk2 performed correctly across all test points.
He wrote: Rathore said the aircraft is a scalpel. He's right. The S-27 is a hammer. The Tejas is a scalpel. Both have their purpose. The precision of the scalpel is harder to build than the force of the hammer.
He wrote: The aircraft tells the truth. This was always the design requirement. It is the design achievement.
He sat with the notebook open for a long moment.
Then he wrote one more thing:
The Bureau was tested. The aircraft is clean. The aircraft flew today because what was built here was built honestly, and honesty is harder to penetrate than security protocols, because honesty is about the character of the people who do the work, and the character of the people in this Bureau — mostly, not perfectly, but mostly — is sound.
He closed the notebook.
He put it in his jacket.
He walked out of the conference room, through the corridor, through the main entrance of the Design Bureau, out into the July afternoon.
The complex was alive around him. The factory buildings. The steel plant. The semiconductor facility. The cranes to the north marking the next expansion. Twelve thousand people doing the work that the complex existed to do.
He walked to the hangar.
The S-35 Tejas was inside. The ground crew was working around it — post-flight inspections, the routine that happened after every flight where the aircraft was examined for evidence of how the flight had treated it, where the data recorder was downloaded and the fuel state was checked and the airframe was inspected for any sign that the loads of flight had produced anything unexpected.
Karan stood in the hangar doorway.
He looked at the aircraft.
The aircraft looked the same as it had at four-forty-five this morning when he had stood here and looked at it before anyone else arrived. The same lines, the same weight distribution, the same composite skin, the same Kaveri Mk2 at the tail.
But it was different now.
It had been in the air. It had flown. It was no longer a thing that was expected to fly — it was a thing that had flown, and the having-flown was permanent, could not be taken back, was part of what the aircraft now was.
He stood there.
He thought: one down. Many to go.
The second test flight in two weeks, with the Dutch roll fix. The third flight expanding the envelope. The fourth flight beginning the weapons system assessment. The long path of a test programme toward the qualification that would allow the aircraft to be handed to the Indian Air Force with the full confidence of a design that had been proven.
And beyond the Tejas — the Makara strike variant development, the Raksha ground strike study, the Garuda whose aerodynamic study had just begun.
The work was enormous.
The work was not finished.
The work would not be finished for a long time.
He thought about this without regret. The work being enormous and unfinished was not a problem. The work being enormous and unfinished was the condition of doing something worth doing. Small things finished quickly. Large things took time. The Tejas had taken two and a half years and had flown today and the programme was not finished — the test programme was just beginning. The Garuda would take seven years to first flight and longer to operational capability and was already begun.
He looked at the aircraft.
He said: "Good first day."
To the aircraft. In the hangar. By himself.
Then he turned and walked out into the July afternoon to do the next thing.
End of Chapter 163
Programme Status — 16 July 1974
S-35 Tejas — First Flight Complete
First flight: 16 July 1974, 53 minutes, all objectives achieved Dutch roll in gusts: yaw damper gain to be increased 30% — simulation verification 1 week, second test flight verification 2 weeks HUD AoA indicator: resize to half-step larger in primary display field — Misra's team, 1 week Kaveri Mk2 performance: all parameters within prediction at temperature/humidity conditions Pilot assessment: "The aircraft tells the truth. It's a scalpel, not a hammer." Boundary layer transition: earlier than predicted — 2% drag reduction vs model. Ramanathan to investigate IAF evaluation: ACM Latif evaluation programme in 6 weeks
Next milestone: Second test flight — 30 July 1974 (Dutch roll fix + HUD modification verification)
Bureau status: Post-security incident. Protocols revised. All-hands briefing complete. Programme clean.