Date: 3 February 1974
Location: Mazagon Dock Shipbuilders Limited, Bombay; INS Vikrant, Bombay Harbour
The morning ca to Bombay Harbor with the particular quality of light that only exists at the intersection of industrial infrastructure and salt water—flat, hard, clarifying in the way that removes ambiguity from shapes. At 0547 hours, INS Vikrant sat at anchor three kiloters offshore, her flight deck empty but prepared, her crew at stations they had been rehearsing for six months, waiting for an aircraft that would change what the Indian Navy could do and where it could project force.
Commander Ajit Narayan stood on Vikrant's bridge looking through binoculars at the Mazagon Dock facility onshore. He could see the crowds gathering already—unusual for a military induction ceremony, but this was not a usual induction. The Pri Minister was coming. The man who had protected Shergill Aerospace's Bombay facility when the unions and the bureaucrats had wanted to strangle it was coming. The press was coming from eleven countries. And sowhere in that facility, secured under guard since its arrival by barge three days ago, sat the first operational S-22 Makara configured for carrier operations, waiting to fly from shore to ship in front of everyone who had said it couldn't be done.
Narayan lowered the binoculars. Beside him, Captain Satish Kumar—Vikrant's commanding officer, a man who had spent twenty-three years in the Navy and had seen enough procurent disasters to be professionally skeptical of new aircraft—was reading the morning's operational brief for the fourth ti.
"The wind," Kumar said without looking up from the brief.
"Southwest at eight knots," Narayan confird. "Within paraters. The sea state is two. Vikrant's stabilizers are holding pitch to less than one degree. Weather is clear, visibility unlimited. We're in the window."
"The window assus the aircraft performs as specified," Kumar said. He set the brief down and looked at Narayan. "Shergill's test pilots have flown it. The manufacturer's data says it works. But this is the first ti a naval aviator puts it on Vikrant's deck with the Pri Minister watching from the dock. If it doesn't work—if the approach goes wrong, if the hook misses, if the pilot has to bolter and the aircraft isn't ready for an imdiate go-around—we're not just having an operational incident. We're having a political disaster."
"Commander Vikram non has fifty-three carrier traps," Narayan said. "He's flown the S-22 in simulation for two months and on actual flight tests for three weeks. He knows the aircraft and he knows this ship. If anyone can put it aboard cleanly, it's non."
"Then let's hope non is having a very good day," Kumar said.
At Mazagon Dock's main assembly hangar, the S-22 Makara sat in the center of the floor under work lights that had been on since 0400. The aircraft was painted in the Navy's standard gray-blue sche with the Indian naval ensign on the vertical stabilizer and the number 501 on the nose—the first of an expected seventy-two aircraft that would be delivered over the next two years. The variable-geotry wings were in the forward position—25 degrees of forward sweep, the position for slow flight and carrier approach. The leading edge root extensions ran forward along the fuselage like the particular intent of a predator. The twin Kaveri Mk 1.5 engines sat cold and quiet in their nacelles, waiting.
Commander Vikram non stood beside the nose gear, running through his pre-flight inspection for the third ti. He was forty-one years old, had been flying for the Navy since 1957, had accumulated more carrier traps than any other pilot in the Indian Navy, and had spent the last six months learning to fly an aircraft that was, in almost every asurable way, unlike anything he had flown before. He checked the leading edge extensions for damage, verified the wing sweep chanism housing was clean, confird the hook was properly seated, examined the main gear struts for leaks. Everything he had checked at 0400 and again at 0500 was still exactly as it had been—the aircraft was ready. What he was doing now was not inspection. It was the ritual that pilots perform before they do sothing that might kill them, the physical movent that occupies the body while the mind settles into the particular state required to fly a machine at the edge of its performance envelope from a moving deck in front of an audience.
"Commander non."
non turned. Lieutenant Commander Arun Prakash—his wingman for the last eight years, the pilot who would fly the second S-22 from shore to ship later this morning if non's landing was successful—approached with two cups of chai.
"You've checked that aircraft five tis in three hours," Prakash said, handing non the cup. "It's not going to change between now and launch."
"I know," non said. He took the chai. "But if I'm standing still, I'm thinking about what happens if the approach goes wrong. If I'm moving, I'm thinking about the aircraft. I'd rather think about the aircraft."
"The approach won't go wrong," Prakash said. "You've flown this approach in simulation forty-seven tis. You flew it on the actual aircraft with Shergill's test pilot last week. You know the numbers."
"I know the numbers," non agreed. "The approach speed is 142 knots with full weapons load, 138 knots clean. The angle of attack on final is 8.2 degrees. The hook-to-eye distance is optimized for Vikrant's wire spacing. The FBW handles the glideslope and angle-of-attack hold automatically when I select carrier approach mode. The engines give imdiate throttle response if I need to wave off. I know all of it."
"Then what's the problem?"
"The problem," non said, "is that knowing the numbers and trusting them at 400 feet over Vikrant's deck with the Pri Minister watching are different things." He drank the chai. "The S-22 is a fundantally different aircraft from the Sea Hawk. Different thrust-to-weight, different approach speed, different handling characteristics. The FBW is doing things automatically that I'm used to doing manually. The first ti I trust the automation with my life is this morning, in front of everyone who matters."
Prakash was quiet for a mont. "You've trusted aircraft before."
"I've trusted aircraft I understood," non said. "I understood the Sea Hawk because I'd flown it for twelve years and I knew exactly how it would behave in every situation. I've flown the S-22 for three weeks. That's not the sa."
"Rathore says it's the most honest aircraft he's ever flown," Prakash said. "He says it tells you what it's doing before it does it. He says the FBW makes it easier to fly, not harder."
"Rathore is a test pilot," non said. "Test pilots are insane. They think risk is a recreational activity."
"Rathore is also the man who flew the S-22 to 9G and ca back smiling," Prakash said. "If he says it's honest, it's honest."
non looked at the aircraft. The morning light was coming through the hangar's high windows now, painting the S-22's wings in flat illumination that showed every rivet, every panel line, every surface detail. It was a beautiful aircraft in the particular way that functional things are beautiful—no decoration, no compromise, just the shape that physics and engineering demanded to accomplish the mission. He thought about what that mission was: carrier-based fleet defense and anti-ship strike in the Indian Ocean against threats that included Pakistani and potentially Chinese naval forces. The S-22 had been designed specifically for Vikrant's deck and the operational environnt of the Arabian Sea and Bay of Bengal. Every design decision—the variable geotry wings for slow approach and high-speed dash, the powerful engines for rapid acceleration, the Kaumodaki missile integration for ship-killing capability, the rugged landing gear for carrier impacts—had been made with one purpose: making this aircraft survivable and effective in a role that killed pilots regularly.
The question was whether Shergill Aerospace had succeeded in that design intent or whether the operational reality would reveal problems that testing had missed.
"What ti is the Pri Minister arriving?" non asked.
"0730," Prakash said. "The ceremony starts at 0800. Your launch window opens at 0815. You'll be in the aircraft at 0800 for systems checks and warm-up. Thirty minutes from dock ceremony to launch."
"And Vikrant's ready?"
"Vikrant's been ready since yesterday," Prakash said. "Captain Kumar has the entire air operations team at stations. The landing signals officer is Lieutenant Commander Suresh Pillai—you know him, good man, calm under pressure. The arresting gear has been tested six tis in the last twenty-two hours. The deck crew has rehearsed the landing sequence until they can do it blindfolded. Everything that can be prepared has been prepared."
"Then I suppose all that's left is to actually do it," non said.
"All that's left," Prakash agreed.
They stood there drinking chai and looking at the aircraft while the morning light strengthened and the sounds of the facility waking up surrounded them—trucks moving equipnt, workers arriving for the ceremony, the distant sound of a ship's horn from the harbor. Sowhere in Bombay, the Pri Minister was preparing for the drive to Mazagon Dock. Sowhere on Vikrant, Captain Kumar was running through his own pre-flight rituals. And sowhere in the Shergill Aerospace facility across the city, Karan Shergill was probably already awake, reviewing the sa data non had reviewed, checking the sa numbers, thinking through the sa scenarios.
non finished his chai and handed the cup back to Prakash. "I'm going to walk the aircraft one more ti."
"You've already walked it five tis."
"Then this will be six," non said.
Prakash smiled slightly. "I'll see you at the ceremony."
He left. non returned to the aircraft and began his sixth pre-flight inspection, touching surfaces he had already verified, checking systems he knew were functional, performing the ritual that had kept him alive through seventeen years of carrier aviation by making sure that when he climbed into the cockpit, no surprises were waiting.
At the Shergill Aerospace Bombay facility—the factory that Bal Thackeray had protected and that now employed 4,800 people in advanced manufacturing—Karan stood in the main engineering office reviewing the final configuration data for S-22 serial number 501. Dr. Harsh Vardhan was beside him, having arrived from Gorakhpur the previous evening specifically for this induction. Srinivasa Ramanathan had co as well, and Major Vikram Rathore, and Wing Commander Prabhat Anand. The full core team that had designed the S-22 was present, not because their presence was operationally necessary—the aircraft either worked or it didn't, and their presence wouldn't change that—but because when you build sothing this complex and this important, you want to see it work.
"The modifications from the test articles to serial 501," Vardhan said, reading from the configuration log. "Reinforced nose gear for higher sink rates on carrier landing. Modified brake system with increased thermal capacity. Enhanced corrosion protection on all control surfaces and chanisms. Strengthened wing-sweep actuator housing after the fatigue analysis identified the load concentration issue. Improved pilot visibility with lowered instrunt coaming. All implented, all tested, all verified."
"The engine TBO certification?" Karan asked.
"1,200 hours," Vardhan said. "We gained 100 hours from the original 1,100-hour specification through the improved thermal barrier coating on the high-pressure turbine blades. The Navy accepted 1,200 hours as sufficient for operational deploynt with the understanding that as we accumulate fleet hours, we may extend it further."
"Weapons integration status?"
"Kaumodaki Mk 2 certified for all operational envelopes," Captain Ranbir Singh said from where he stood at the testing station. "Air-to-air missile integration complete—Astra, Python-3 and R-60. The gun—twin 23mm—harmonised and tested. The aircraft is fully operational across its entire mission spectrum."
Karan looked at the configuration data one more ti. He had reviewed this data extensively over the past week, had personally verified the modifications, had flown in the chase aircraft during non's training flights to observe the S-22's behavior. The aircraft was ready. What he felt standing here was not doubt—doubt would have manifested earlier, during design or testing. What he felt was the particular tension that cos from knowing that years of work were about to be validated or invalidated in the next two hours.
"era," he said to his operations director, who had accompanied him from the main office.
era Krishnan—the woman who had been managing Shergill Aerospace's operational complexity for two years and who had a gift for seeing three moves ahead in the particular chess ga of industrial logistics—looked up from her notes.
"Transportation to Mazagon Dock is arranged. We have twelve people attending the ceremony—yourself, Dr. Vardhan, Ramanathan, Rathore, Anand, Singh, and six senior engineers. The vehicles leave at 0700. Arrival at 0730, which gives us thirty minutes before the ceremony begins."
"Security at the facility?"
"Naval security is handling the periter. Shergill security is coordinating with them. No unauthorized access to the hangar or the aircraft. The Pri Minister's security detail did a sweep yesterday afternoon and was satisfied with the arrangents."
"And Thackeray?"
era smiled slightly. "Bal Thackeray's attendance was confird two days ago. He'll be arriving separately with his own security. The Navy was... initially concerned about having a political figure from a regional party at a military induction ceremony. I explained that without Thackeray's intervention in 1970, this facility wouldn't exist and therefore the S-22 wouldn't exist. They beca less concerned."
"Good," Karan said. "What else?"
"Press credentials issued to forty-three journalists from eleven countries. They'll be in a designated area with sight lines to the aircraft but not close enough to interfere with operations. Naval public affairs is handling press coordination. We're providing technical fact sheets but not detailed specifications—performance envelope, weapons capacity, general capabilities. Nothing that compromises operational security."
"The ceremony itself?"
"Admiral Nanda will speak first—brief remarks about the S-22's role in expanding the Navy's operational reach. The Pri Minister will speak second—expected to address strategic autonomy and indigenous defense developnt. You'll speak third—technical overview of the aircraft and acknowledgnt of the team that built it. Then Commander non launches and flies to Vikrant. If the trap is successful, Prakash launches with the second aircraft. Total ceremony ti: forty-five minutes dock-side, then everyone moves to the observation area to watch the carrier operations."
"What if the trap isn't successful?" Karan asked.
era's expression didn't change. "Then Commander non executes a wave-off, goes around, and tries again. If the second attempt fails, the ceremony concludes with acknowledgnt that carrier integration is an iterative process and we'll resolve any issues identified. The press gets a story about challenges in naval aviation. We get ti to fix whatever went wrong. The program continues."
"You've thought this through."
"It's my job to think this through," era said. "But I don't think we're going to need the contingency plan. non is an excellent pilot. The aircraft is sound. It's going to work."
"Your confidence is noted," Karan said.
"My confidence is based on data," era replied. "The sa data you've been reviewing for the past week. The sa data that says this aircraft is ready."
Karan looked at her. era had been with Shergill Aerospace since early 1972, had managed the expansion into Bombay, had coordinated the S-22 production ramp-up, had handled the interface between Shergill's industrial operations and the Navy's procurent bureaucracy. She was right that the data supported confidence. What data couldn't account for was the thousand small things that could go wrong when you flew a complex aircraft from a moving deck—a gust of wind at the wrong mont, a pilot input at the wrong ti, an unforeseen interaction between systems that testing hadn't revealed. The S-22 had been designed to handle those variations, had been tested extensively to verify its handling qualities. But designed and tested were not the sa as proven in operational use.
"We leave at 0700," Karan said. "Make sure everyone's ready."
At 0645, the vehicles began departing from the Shergill Aerospace facility for the short drive to Mazagon Dock. Karan rode in the lead vehicle with Vardhan and Ramanathan. The streets of Bombay at this hour were already busy—the city waking up to its usual chaos of traffic and comrce and human density. They passed through neighborhoods where n were opening shops, where won were buying vegetables from street vendors, where children were walking to school. Normal life, continuing as it always continued, indifferent to the fact that today the Indian Navy was inducting an aircraft that would change its operational doctrine and expand its reach into waters where it had previously been constrained by limited carrier-based strike capability.
"Nervous?" Ramanathan asked.
"No," Karan said.
"Liar," Vardhan said. "You've been reviewing the sa data for a week. You're nervous."
"I'm not nervous about the aircraft," Karan said. "The aircraft works. I'm... aware that we're about to demonstrate it works in front of the Pri Minister and the Chief of Naval Staff and the press from eleven countries. If it works, we validate three years of developnt and open the door to seventy-two aircraft purchases over two years. If it doesn't work, we explain to everyone watching why our testing missed sothing critical. Those are high stakes."
"The aircraft works," Vardhan said. "We've tested every system. We've flown it in every configuration. We've verified the carrier approach mode. It works."
"It works in testing," Karan said. "Today we find out if it works in operational reality."
The vehicle turned onto the road leading to Mazagon Dock. Ahead, they could see the security periter—naval personnel checking credentials, barriers controlling access, the visible manifestation of the Navy taking this ceremony seriously. The vehicle slowed, stopped at the checkpoint. A naval officer approached, examined credentials, verified identities against a list, waved them through.
Inside the periter, the Mazagon Dock facility had been transford. What was normally an industrial workspace—loud, grimy, focused on the practical work of building ships and maintaining infrastructure—had been cleaned, organized, prepared for public presentation. The main hangar where the S-22 sat was open on one side, giving a clear view of the aircraft. A stage had been erected in front of the hangar with microphones and a podium. Seating had been arranged in rows—VIP seating in front, general seating behind, press area to the side with clear sight lines. Naval personnel were everywhere, managing logistics, coordinating security, preparing for the arrival of dignitaries.
Karan stepped out of the vehicle and stood for a mont looking at the S-22 in the hangar. From here—fifty ters away, morning light streaming through the hangar opening—the aircraft had a particular presence. Not aggressive, exactly. Purposeful. It sat there with the quality of a machine that knows what it was built to do and is ready to do it. The variable-geotry wings in their forward sweep position gave it a waiting quality, like a runner at the starting line. The twin engines were massive in their nacelles, visibly powerful even at rest. The naval gray-blue paint sche made it look like it belonged to the sea already, even before it flew.
Vardhan ca to stand beside him. "Three years," he said. "From initial concept to operational induction. Three years."
"Three years," Karan confird. "Most aircraft programs take ten."
"Most aircraft programs don't have you driving them," Vardhan said. "And most aircraft programs don't have a custor who needs the capability urgently enough to accept compressed tilines. We had both."
"We also had a good team," Karan said. "You, Ramanathan, Rathore, Krishnan, all the others. The aircraft exists because the right people did difficult work and did it well."
"I'll make sure they hear you say that in your speech," Vardhan said.
"You do that," Karan said.
More vehicles were arriving now—naval officers, governnt officials, journalists setting up caras and equipnt. The facility was filling with people, the ceremony taking shape. Sowhere in that organized chaos, Admiral Nanda had arrived and was probably reviewing his remarks. Sowhere, the Pri Minister's motorcade was approaching. And sowhere in the hangar, Commander non was running through his final checks on an aircraft that would either validate everything Shergill Aerospace had claid about carrier aviation capability or require significant explanation about why reality differed from specification.
At 0720, a particular quality entered the atmosphere—the shift that happens when very important people are about to arrive and everyone needs to be ready. Security beca more visible. Naval officers straightened uniforms. Journalists checked caras. The background hum of conversation dropped slightly.
At 0728, the Pri Minister's motorcade entered the facility.
Three vehicles—two security escorts and the Pri Minister's car. They moved through the checkpoint with the smooth efficiency of practiced logistics, proceeded directly to the VIP area, stopped. Doors opened. Security personnel erged first, scanning, verifying, establishing periter. Then Indira Gandhi stepped out.
She was sixty-six years old, had been Pri Minister since 1966, had led India through the 1971 war and the liberation of Bangladesh, had made decisions that had permanently altered the strategic balance in South Asia. She wore a dark blue saree and moved with the particular economy of soone who has been in power long enough to be absolutely comfortable with it. Her security detail surrounded her but didn't crowd—they knew their job was protection, not interference.
Karan watched from where he stood near the hangar. The Pri Minister was speaking with Admiral Nanda, who had t her at the vehicle. Their conversation was brief—Nanda gesturing toward the hangar and the S-22, the Pri Minister nodding, asking a question that Karan couldn't hear. Then Nanda was escorting her toward the VIP seating area, introducing her to naval officers along the way.
At 0734, another motorcade arrived.
This one was different—less formal, more energetic. Two vehicles, both carrying the orange flags of Shiv Sena. They entered the facility with the particular confidence of people who know they're welco even if the formal protocols say they shouldn't be. The vehicles stopped near the VIP area. Doors opened.
Bal Thackeray erged.
He was Forty-Eight years old but still carried himself with the physical presence that had made him a force in Bombay politics for decades. He wore white kurta-pajama and his signature sunglasses. His security—Shiv Sena mbers, not formal security personnel—surrounded him with the loyal intensity of n who would fight if asked. He looked at the S-22 in the hangar for a long mont, then turned and saw Karan.
He walked over directly, ignoring protocols, ignoring the naval officers who were trying to escort him to seating. His security followed.
"Shergill," Thackeray said when he arrived.
"Pramukh," Karan said, using the title. "Thank you for coming."
"I told you in 1970 I'd protect this facility," Thackeray said. "That protection included keeping the unions from strangling your work and keeping the bureaucrats from demanding bribes for permits you didn't need. But I also told you I wanted to see what you built. Today I'm seeing it."
He looked at the S-22 again. "That aircraft—it was built here? In Bombay?"
"The final assembly was here," Karan confird. "Components ca from Gorakhpur, from suppliers across India. But the integration, the testing, the final preparation—all done at the Bombay facility. Your facility, in the sense that without your protection, it wouldn't exist."
"How many people work there now?" Thackeray asked.
"4,800," Karan said. "Marathi, Gujarati, others. All doing skilled manufacturing work at wages significantly above the regional average. All building aircraft that will defend India's coast and project power into the Indian Ocean."
"Good," Thackeray said. "I told you pride cos from building things that matter. Your people are building things that matter." He paused. "The Pri Minister is here. I saw her arrive. She knows I'm attending?"
"She knows," Karan said. "The Navy was initially concerned about mixing military ceremony with political attendance. I explained that you were instruntal in making this aircraft possible. They understood."
"Did they understand," Thackeray said, "or did they accept because refusing would create problems they didn't want?"
"Probably the second one," Karan admitted.
Thackeray smiled—the particular smile of a man who understands exactly how power works and enjoys using it. "Good. I'll sit quietly and watch your aircraft fly. Then afterward, you and I will talk about the next factory expansion. If you're building seventy-two of these aircraft, you'll need more capacity."
"I'll need more capacity," Karan agreed.
"Then we'll talk," Thackeray said. He turned and walked toward the VIP seating area, his security following. Naval officers scrambled to accommodate him—finding seating, adjusting arrangents, managing the presence of a regional political figure at a national military ceremony with the grace of people who recognize that so battles aren't worth fighting.
Karan watched him go, then returned his attention to the hangar where Commander non was now visible in the cockpit of the S-22, running through pre-start checks. The ceremony would begin in twenty-six minutes. The flight would happen approximately forty-five minutes after that. Everything was converging on the mont when theory would et reality and Shergill Aerospace's claims about carrier aviation capability would be verified or questioned.
At 0800, the ceremony began.
Admiral Nanda took the podium. He was a quiet man, not given to dramatic speeches, but when he spoke people listened because he had earned respect through forty years of naval service and because when he said sothing was important, it usually was.
"Ladies and gentlen, Pri Minister, distinguished guests," Nanda began. "We are here today to induct into operational service the S-22 Makara, India's first indigenously designed carrier-based fighter aircraft. This aircraft represents a fundantal expansion of the Indian Navy's capability to defend our mariti interests and project power across the Indian Ocean."
He paused, letting that statent sit. The journalists were taking notes. The caras were recording.
"For the past twenty-five years," Nanda continued, "the Indian Navy has operated carrier-based aircraft purchased from Britain—the Sea Hawk, an aircraft designed in the 1940s and reaching the end of its operational life. The Sea Hawk has served honorably, but its limitations have constrained what INS Vikrant could accomplish and where she could operate. Limited range ant Vikrant had to position close to the area of operations. Limited weapons capacity ant we could defend the fleet but not effectively strike enemy naval forces at range. These constraints defined our doctrine and limited our options."
He gestured toward the S-22 in the hangar behind him.
"The S-22 Makara removes those constraints. With a combat radius of 945 kiloters carrying a full weapons load, this aircraft extends Vikrant's operational reach by a factor of three. With the Kaumodaki anti-ship missile integration, it provides ship-killing capability that no carrier-based aircraft in the Indian Ocean currently possesses. With advanced radar and electronic warfare systems, it provides fleet defense that makes Vikrant survivable in contested waters. These are not incrental improvents. This is a fundantal change in what the Indian Navy can do."
More note-taking. More caras focusing on the aircraft.
"I want to acknowledge," Nanda said, "that this aircraft exists because Shergill Aerospace chose to develop it when the governnt had not yet requested it. In 1971, Karan Shergill approached the Navy with a proposal to design a carrier-based fighter specifically for INS Vikrant's deck and the Indian Ocean operational environnt. We were skeptical. Carrier aviation is difficult. Most nations don't attempt it. Those that do usually buy aircraft from established manufacturers rather than designing their own. Mr. Shergill proposed doing what most nations consider too difficult to attempt."
He looked directly at Karan in the audience.
"We gave him access to Vikrant's specifications. We provided operational requirents. We explained what we needed and why we needed it. Then we waited to see if he could deliver. Today, we have the answer to that question."
Nanda stepped back from the podium. Polite applause from the audience.
The Pri Minister stood and approached the podium. The applause continued until she raised her hand slightly—the small gesture that says be quiet now without saying it verbally. The audience quieted.
Indira Gandhi looked at the S-22 for a mont before speaking. When she did speak, her voice carried the particular authority of soone who has made hard decisions and lived with the consequences.
"India's security depends on our ability to defend our interests without asking permission from foreign powers. That principle guided our approach to the 1971 war. That principle guides our approach to defense industrial developnt. And that principle is embodied in the aircraft you see behind ."
She paused.
"For decades after independence, India purchased our weapons from Britain, from the Soviet Union, from other nations who sold us what they deed appropriate for our needs. We operated on their tilines. We accepted their limitations. We built our military doctrine around the capabilities they chose to provide. This approach had one fundantal weakness: the mont our interests diverged from their interests, the supply stopped. We saw this in 1965 when Britain cut off spare parts during the war with Pakistan. We saw it in the reluctance of Western nations to provide advanced technology because they feared how we might use it. We learned that dependence is vulnerability."
The journalists were recording every word. This was the speech that would be quoted in newspapers tomorrow.
"The S-22 represents a different approach," the Pri Minister continued. "It was designed in India, by Indian engineers, for Indian operational requirents. It is built in Indian facilities using Indian manufacturing capability. It will be maintained by Indian technicians using Indian industrial infrastructure. When this aircraft needs repairs or upgrades or modifications, we will not be asking foreign governnts for permission or foreign companies for access. We will be making our own decisions based on our own priorities."
She looked at the audience directly.
"So have questioned whether a private company should be developing weapons for India's military. So have argued that strategic defense capabilities should be the exclusive domain of governnt enterprises. I say this: the question is not who builds the weapons. The question is whether the weapons work and whether they serve India's interests. The S-22 works—the Navy has verified this through extensive testing. It serves India's interests—by extending our operational reach and reducing our dependence on foreign suppliers. Those are the only criteria that matter."
More applause, louder this ti.
"I want to acknowledge Bal Thackeray's presence here today," the Pri Minister said, surprising everyone including Thackeray. "In 1970, when Shergill Aerospace was establishing its Bombay facility, there were significant obstacles—union resistance, bureaucratic barriers, local political opposition. Thackeray Saheb used his influence to remove those obstacles because he understood that manufacturing capability serves Marathi workers and India's interests simultaneously. The S-22 exists in part because he made that judgnt. I wanted to acknowledge it publicly."
Thackeray, from his seat, nodded once. The caras captured it.
"Finally," the Pri Minister said, "I want to speak to the young people watching this ceremony. You live in an India that is building its own aircraft carriers, its own fighter jets, its own missiles. You live in an India that is no longer asking permission to defend itself. The question for your generation is what you will build that my generation cannot yet imagine. The answer to that question will determine what India becos in the twenty-first century."
She stepped back from the podium to sustained applause.
Karan stood and approached the podium. The applause continued briefly then quieted.
He looked at the S-22 for a mont, gathering his thoughts. Then he turned to the audience.
"The S-22 Makara was designed to solve a specific problem," he began. "INS Vikrant operates in the Arabian Sea and Bay of Bengal in conditions that include monsoons, high sea states, crosswinds, and temperatures that range from extre heat to heavy precipitation. Vikrant's flight deck is 213 ters long with a 12-degree ski-jump ramp. The aircraft that would fly from this deck needed to handle these specific conditions while carrying sufficient weapons to conduct fleet defense and anti-ship strike missions at ranges that made Vikrant survivable in contested waters. That was the requirent. Everything else followed from it."
He gestured toward the aircraft.
"The variable-geotry wings—the wings that sweep forward for slow approach and aft for high-speed flight—exist because carrier landing requires slow, controlled approach while anti-ship strike requires the ability to dash at high speed. Fixed wings optimize for one condition or the other. Variable geotry optimizes for both. The twin Kaveri engines exist because carrier operations require redundancy and imdiate throttle response for wave-offs. The strengthened landing gear exists because carrier landings are controlled crashes—the aircraft hits the deck at descent rates that would damage normal landing gear. The comprehensive corrosion protection exists because salt water destroys aircraft, and Vikrant operates in salt water continuously."
The technical audience—the naval officers, the engineers, the people who understood what these design choices ant—were leaning forward. The journalists were taking notes without necessarily understanding why these details mattered.
"Every design decision was made with one question: will this aircraft survive and succeed in the environnt where it will actually operate? Not in theory. Not in testing. In operational reality on Vikrant's deck with real pilots in actual combat. That question drove everything."
He paused.
"I want to acknowledge the team that built this aircraft. Dr. Harsh Vardhan designed the engines. Srinivasa Ramanathan solved the aerodynamics. Major Vikram Rathore flew the test program. Dr. Padma Krishnan made the structure survive carrier impacts. Lieutenant Colonel Amarjit Dhaliwal integrated the electronic warfare systems. Dozens of others whose nas are not in the press releases but whose work is in this aircraft—they are the reason it exists."
He looked at Vardhan and Ramanathan in the audience. "Stand up."
They did, reluctantly. The audience applauded. Karan waited until they sat down.
"In approximately thirty minutes," Karan said, "Commander Vikram non will fly this aircraft from this facility to INS Vikrant, where he will conduct the first operational carrier landing of an S-22. If that landing is successful, Lieutenant Commander Arun Prakash will fly the second aircraft. By the end of today, two S-22s will be aboard Vikrant, and the Indian Navy will have a carrier-based strike capability it has never possessed before. That is the goal. Now we execute."
He stepped back from the podium.
The ceremony concluded. The audience began moving toward the observation area where they would watch the launch and the carrier landing. Naval personnel were coordinating the movent, managing the logistics of relocating several hundred people while maintaining security protocols.
Karan walked to the hangar where Commander non was completing his pre-flight checks.
non saw him approaching and climbed down from the cockpit. They stood facing each other beside the nose gear—the pilot who would fly the aircraft and the designer who had built it.
"How are you feeling?" Karan asked.
"Ready," non said. "I've flown this approach enough tis that I could do it in my sleep. The aircraft is sound. Vikrant is ready. It's going to work."
"You sound confident."
"I am confident," non said. "But I'm also a naval aviator with seventeen years of carrier experience. I know that confidence and capability don't eliminate risk. They just make risk manageable. If sothing goes wrong during the approach—if I get an engine issue, if the wind shifts, if the FBW has a problem—I know how to handle it. I trust the aircraft to do its part. That's enough."
Karan nodded. "The carrier approach mode in the FBW—when you select it, the system automatically manages glideslope and angle of attack. But you can override if you need to. The throttle response is imdiate. If you wave off, the engines give you full power in less than two seconds. You have control."
"I know," non said. "Rathore told the sa thing. He said the aircraft is honest—it tells you what it's doing before it does it. He said to trust it."
"Rathore is correct," Karan said. "The aircraft will tell you if sothing's wrong. Listen to it."
"I will," non said.
They stood there for a mont in the particular silence that exists between people before sothing consequential happens.
"Good luck," Karan said.
"Thank you," non said. "But I'm not relying on luck. I'm relying on engineering."
"Even better," Karan said.
He walked away, leaving non to complete his final preparations.
At 0815, Commander non climbed into the cockpit of S-22 serial number 501 for the last ti before launch. The crew chief helped him strap in—shoulder harness, lap belt, leg restraints, connections for the pressure suit that would keep him conscious at high G. Then the crew chief stepped back and non was alone with the aircraft.
He ran through the startup sequence. Master power on. Hydraulic pressure building. Flight control check—stick movent, rudder pedals, all surfaces responding. Instrunt scan—all readings nominal. Engine start sequence: right engine first, fuel flow established, ignition, the turbine beginning to spin, the sound building from a whine to a roar. Right engine stabilized. Left engine start: sa sequence, sa sound, sa result. Both engines running, all paraters nominal.
Radio check. "Mazagon tower, Makara 501, radio check."
"Makara 501, Mazagon tower, loud and clear."
"Roger. Request taxi for departure, carrier qualification mission."
"Makara 501, cleared to taxi runway 27. Wind southwest at nine knots. Vikrant reports ready to receive. Your deck is green."
"Cleared to taxi runway 27, Makara 501."
non released the brakes and advanced the throttles slightly. The S-22 began to move, rolling forward on the main gear, the nose wheel tracking straight. He could feel the aircraft's mass—heavier than the Sea Hawk, more powerful, more capable. The twin engines provided thrust that made taxiing almost too easy—he had to be careful not to advance the throttles too far or the aircraft would accelerate faster than the taxi speed allowed.
He reached the runway, turned onto the centerline, stopped. Final checks: flight controls, engine paraters, weapons status, fuel load. Everything verified.
"Mazagon tower, Makara 501, ready for departure."
"Makara 501, cleared for takeoff runway 27. Winds now southwest at eight knots. Report Vikrant in sight."
"Cleared for takeoff, Makara 501."
non advanced the throttles to full military power—maximum thrust without afterburner. The engines responded instantly, the sound increasing to the particular roar that ant maximum continuous power. The aircraft wanted to move. He held the brakes until the engines stabilized, verified all paraters one final ti, then released.
The S-22 accelerated down the runway with the particular authority of an aircraft that has more power than it needs. non watched the airspeed indicator climbing—60 knots, 80, 100. At 132 knots, he rotated, pulling the stick back smoothly, and the nose lifted. The aircraft transitioned from ground to air with perfect smoothness, the FBW managing the control inputs to prevent over-rotation. The main gear left the ground. The aircraft was flying.
non raised the landing gear and reduced power to climb power. The S-22 continued accelerating, climbing at 2,000 feet per minute, the coastline falling away below as Bombay Harbor opened ahead.
"Mazagon tower, Makara 501 airborne, climbing to 1,500 feet."
"Makara 501, roger. Contact Vikrant approach on 302.5."
"302.5, Makara 501."
non switched frequencies. "Vikrant approach, Makara 501, airborne from Mazagon, climbing 1,500 feet, inbound for carrier qualification."
"Makara 501, Vikrant approach, radar contact. Vikrant is at your twelve o'clock, range eight nautical miles. Deck is green, winds southwest eight knots, sea state two. Report initial."
"Wilco, Makara 501."
non leveled at 1,500 feet and looked ahead. He could see Vikrant clearly now—the carrier at anchor three kiloters offshore, her flight deck clear and ready, the island structure visible on the starboard side. From here, she looked small, like a model ship on a flat sea. In four minutes, she would look very large and very close as he brought 16 tons of aircraft onto her deck at 138 knots.
He checked his systems one more ti. Engine paraters nominal. Hydraulics good. Flight controls responding. Fuel load confird. The aircraft was ready. He was ready.
He began the descent toward initial approach altitude.
On Vikrant's deck, Lieutenant Commander Suresh Pillai—the landing signals officer—stood in the LSO position on the port side of the landing area with a clear view of the approach path. He had his radio headset on, his Fresnel lens system powered up, and the landing area prepared. The arresting cables were tensioned properly, tested multiple tis. The deck crew was at stations. Captain Kumar was on the bridge watching through binoculars. Everything that could be prepared was prepared.
Pillai's job was simple in concept and difficult in execution: talk non down to a successful trap by providing real-ti corrections to his approach path and catching problems before they beca dangerous. He had done this hundreds of tis with Sea Hawks. This would be his first ti with an S-22.
"Makara 501, Vikrant approach, report initial."
"Vikrant approach, Makara 501, initial, port side, 1,200 feet."
Pillai saw the aircraft now—crossing from right to left at the far end of the carrier, at 1,200 feet altitude, flying parallel to Vikrant's length. non was setting up for the pattern.
"Makara 501, approach looks good. Winds holding southwest at eight knots. You're cleared to break when ready."
"Cleared to break, Makara 501."
The S-22 turned sharply left, rolling into a descending turn that brought it around toward the stern of the carrier. non was flying the pattern by the numbers—exactly the speeds and altitudes they had practiced in simulation. Pillai watched the aircraft complete the turn, roll out on downwind leg, parallel to Vikrant but now flying the opposite direction at 800 feet altitude.
"Makara 501, Vikrant LSO, I have you in sight. Approach looks good. Call your gear."
"Gear coming down, Makara 501."
Pillai watched the landing gear extend—nose gear first, then the main gear, the doors opening, the wheels deploying and locking. The aircraft's configuration changed visibly as the gear ca down, the clean lines interrupted by the extended gear struts. This was the critical mont—when non selected carrier approach mode, the FBW would shift to the automated glideslope and angle-of-attack control.
"Makara 501, three down and locked," non reported. "Carrier approach mode active."
"Roger, 501. You're on glideslope. Call the ball."
The S-22 turned onto final approach—a smooth, controlled turn that aligned the aircraft with Vikrant's landing area. non was descending now, following the glideslope that the FBW was managing automatically. Pillai could see the aircraft clearly through his binoculars—the variable-geotry wings in their forward sweep position, the gear down and locked, the hook extended beneath the tail.
"Vikrant LSO, Makara 501, ball, 4,800 pounds," non called. The ball reference ant he had the Fresnel lens in sight—the visual aid that showed whether he was on the correct glideslope. The fuel load confird he was at the expected weight.
"Roger ball, 501. Looking good. You're on centerline, on glideslope."
Pillai watched the aircraft descend. The approach was textbook—the right altitude, the right speed, the right angle. The FBW was doing exactly what it was designed to do, managing the glideslope and angle of attack automatically while non managed lateral alignnt and made small throttle corrections.
At 400 feet, the aircraft was stable on glideslope.
At 200 feet, non made a small throttle correction—adding power slightly to compensate for a minor sink. The aircraft responded imdiately, the descent rate correcting.
At 100 feet, Pillai could see the aircraft clearly without binoculars. It was lined up perfectly, descending at the correct rate, the wings level.
"Makara 501, you're looking good. Deck is clear. Bring it aboard."
At 50 feet, the aircraft crossed Vikrant's stern, the hook trailing behind ready to catch the wire.
At 20 feet, the main gear was directly over the landing area.
At 10 feet, non cut the throttles to idle.
The S-22 dropped the final few feet and hit Vikrant's deck with the particular violence that defines carrier landings—a controlled crash at 138 knots. The main gear struck the deck with a trendous impact that would have collapsed normal landing gear. The S-22's reinforced gear absorbed it, the oleo struts compressing, the wheels touching and holding. The hook dragged along the deck, caught the number-three wire—the target wire, the one you want—and the arresting cable began pulling back against the aircraft's forward montum.
The deceleration was imdiate and brutal—from 138 knots to zero in less than two seconds, pulling 4Gs backward, throwing non forward against his harness. The engines were at idle, the throttles closed, but even at idle two Kaveri engines produced significant thrust. The arresting cable held, the aircraft decelerated, and exactly 1.8 seconds after touchdown, the S-22 stopped completely, thirty ters from where it had caught the wire.
Pillai keyed his radio. "Makara 501, welco aboard. Nice trap."
On the observation area at Mazagon Dock, the crowd erupted in applause. The Pri Minister was standing, applauding. Admiral Nanda was smiling—a rare sight. Bal Thackeray was on his feet. The journalists were recording everything. And sowhere in that crowd, Karan was watching an aircraft he had designed perform exactly as specified under exactly the conditions it had been built for.
Vardhan, standing beside Karan, said quietly, "It worked."
"Yes," Karan said. "It worked."
On Vikrant's deck, non advanced the throttles slightly and the S-22 rolled backward, the hook releasing from the wire. A deck crew mber was running toward him with hand signals, directing him toward the parking area. non followed the signals, taxiing the aircraft to the designated spot, stopping, and shutting down the engines.
The turbines spun down from their operating speed, the sound decreasing from a roar to a whine to silence. non sat in the cockpit for a mont, his hands still on the controls, feeling the adrenaline starting to fade. Then he opened the canopy and began disconnecting from the aircraft—pressure suit connections, harness, leg restraints, all the interfaces that had linked him to the machine.
The crew chief appeared at the cockpit edge. "How was it, Commander?"
"Perfect," non said. "The aircraft did exactly what it was supposed to do. The approach mode worked flawlessly. The hook caught on first try. It's a good aircraft."
"Then let's get the second one aboard," the crew chief said.
At Mazagon Dock, Lieutenant Commander Arun Prakash was already in the cockpit of S-22 serial number 502, running through his pre-flight sequence. The first trap had been successful. His mission was to confirm that success wasn't a one-ti event—that the S-22 could reliably and repeatedly land on Vikrant's deck under operational conditions.
At 0847, Prakash departed Mazagon on runway 27, climbed to 1,500 feet, and proceeded inbound toward Vikrant. At 0851, he entered the pattern. At 0853, he turned final approach with the gear down and the carrier approach mode active.
Pillai watched the second approach with the sa careful attention he had given the first. Prakash was flying a slightly different profile—approaching from a different angle due to the wind shift, using a marginally different throttle technique. But the result was the sa: at 0854, the S-22 crossed Vikrant's stern, dropped onto the deck, caught the number-two wire, and stopped in less than two seconds.
Two for two. The S-22 had proven it could operate from Vikrant's deck.
On the observation deck, the applause was sustained this ti. The Pri Minister was speaking with Admiral Nanda, clearly pleased. Thackeray was talking to his security detail, gesturing toward the carrier. The journalists were already writing their stories—the headlines practically wrote themselves: "India Inducts Indigenous Carrier Fighter," "Navy Expands Operational Reach," "S-22 Makara Successfully Demonstrates Carrier Operations."
Karan stood watching Vikrant in the distance, watching the second S-22 taxi to its parking spot beside the first. Two aircraft on deck. The beginning of a squadron that would eventually grow to seventy-two aircraft across two years. The beginning of a naval aviation capability that would allow India to project power into waters where it had previously been constrained.
era approached. "The press is asking for technical interviews. Admiral Nanda has approved a brief dia session—fifteen minutes, general questions only, no classified information."
"Set it up," Karan said. "But I want Vardhan and Ramanathan there as well. This wasn't a solo effort."
"I'll coordinate it," era said.
The dia session happened twenty minutes later in a designated area near the hangar. Forty-three journalists with caras, recorders, notebooks. Karan stood at a podium with Vardhan and Ramanathan beside him.
The questions ca rapidly.
"Mr. Shergill, how does the S-22 compare to other carrier-based fighters currently operational?"
"The S-22's combat radius is approximately 945 kiloters with a full weapons load," Karan said. "That's substantially better than the Sea Hawk it replaces and competitive with the best carrier aircraft operating globally. The variable-geotry wings give it performance advantages in both slow-speed carrier operations and high-speed strike missions. The twin-engine configuration provides redundancy and power that single-engine designs cannot match."
"What weapons can it carry?"
"Air-to-air missiles for fleet defense. Anti-ship missiles for strike missions. A twin 23mm cannon for close-range combat. The specific weapons loadout varies depending on the mission profile. The aircraft was designed to be multirole—it can defend the fleet one day and strike enemy ships the next."
"How many aircraft will the Navy purchase?"
"The current contract is for seventy-two aircraft over two years," Karan said. "Deliveries begin in March with two aircraft per month initially, ramping up to six per month by the end of the year."
"What was the biggest technical challenge in developing the S-22?"
Vardhan answered this one. "The variable-geotry wing chanism. Making a wing that can sweep from 25 degrees forward to 68 degrees aft while maintaining structural integrity and surviving carrier landing impacts required solving problems in materials, chanisms, and structural design simultaneously. We tested extensively to verify the design would survive the operational environnt."
"How long did developnt take?"
"Three years from initial concept to operational induction," Karan said. "That's compressed compared to typical fighter developnt programs. We achieved it through focused requirents, rapid iteration, and extensive testing."
"Will the S-22 be offered for export?"
"The Indian Navy has priority on all production for the next two years," Karan said. "After that, we'll consider export opportunities if there's interest from nations operating aircraft carriers. But the imdiate focus is fulfilling the Navy's requirent."
"What's next for Shergill Aerospace?"
Karan paused. This question had layers—the journalist was asking about future products, but the answer had strategic implications.
"We're developing additional variants of existing platforms and exploring new capabilities that address identified gaps in India's defense portfolio. The specifics are not public yet. What I can say is that the sa approach that produced the S-27 and the S-22—understanding operational requirents, designing specifically for those requirents, testing extensively, delivering on schedule—that approach continues."
More questions followed—about production capacity, about supply chains, about workforce training, about quality control. Karan answered them with the practiced efficiency of soone who had been managing press interaction for three years and knew exactly how much information to provide and where to stop.
After fifteen minutes, era ended the session. The journalists dispersed to file their stories. Karan, Vardhan, and Ramanathan walked back toward the hangar where naval personnel were already beginning the process of securing the facility and preparing for the dignitaries to depart.
The Pri Minister was speaking with Admiral Nanda near her vehicle. She saw Karan approaching and gestured for him to join them.
"Mr. Shergill," the Pri Minister said when he arrived. "Congratulations. The demonstration was successful. The Navy has validated your aircraft. You've delivered what you promised."
"Thank you, Pri Minister," Karan said. "The team delivered. I just coordinated the work."
"Don't be modest," the Pri Minister said. "It's not convincing and it's not necessary. You built this aircraft because you recognized a capability gap and decided to fill it. The Navy benefits. India benefits. That's sufficient justification."
She paused, looking at him with the particular assessnt of soone who has spent decades evaluating people and understanding their motivations.
"I've been receiving reports about Shergill Aerospace's expansion plans," she said. "New facilities, increased workforce, additional production capacity. You're planning for growth."
"The market demands it," Karan said. "Between dostic requirents and international orders, current capacity is insufficient. We're expanding to et demand."
"Be careful," the Pri Minister said. "Growth creates complexity. Complexity creates vulnerabilities. You've been successful because you've maintained control of critical operations and protected sensitive technology. As you grow, maintaining that control becos harder."
"I'm aware of the risks," Karan said.
"I hope so," the Pri Minister said. "Because if you lose control—if your technology gets compromised, if your quality degrades, if your industrial security fails—the consequences extend beyond your company. India's defense capability depends on what you build. That's not pressure. That's reality."
"I understand," Karan said.
"Good," the Pri Minister said. She turned to Admiral Nanda. "Admiral, I'll expect regular reports on the S-22's operational performance. Monthly for the first six months, quarterly thereafter. I want to know how the aircraft performs in actual fleet operations, what problems erge, how they're resolved."
"Yes, Pri Minister," Nanda said.
The Pri Minister nodded to both of them and walked toward her vehicle. Her security detail opened the door. She entered. The motorcade departed.
Karan and Nanda stood watching the vehicles leave.
"She's right about the growth risks," Nanda said quietly. "As Shergill Aerospace expands, maintaining the security and quality standards that have defined your work becos more difficult. The Navy is depending on you to maintain those standards."
"I will," Karan said. "Growth won't compromise security or quality. I'm expanding carefully, vetting personnel thoroughly, implenting controls that scale with the organization. The fundantals don't change."
"I hope you're correct," Nanda said. "Because we're placing seventy-two aircraft orders based on the assumption that aircraft number seventy-two will be built to the sa standard as aircraft number one. If that assumption proves wrong, we have a significant problem."
"It won't prove wrong," Karan said.
Nanda looked at him for a mont. "You have a quality I've seen in very few people—absolute confidence that your judgnts are correct. Sotis that quality produces extraordinary results. Sotis it produces disasters. The difference usually becos clear only in hindsight."
"I'm aware of the distinction," Karan said.
"Are you?" Nanda asked. "Because from where I'm standing, you've had three years of success. Three years of everything working exactly as you predicted. That kind of success can create the illusion that failure isn't possible. The illusion is dangerous."
"I don't believe I'm infallible," Karan said. "I believe I'm rigorous. I check assumptions. I test extensively. I verify before committing. The success isn't luck. It's thodology."
"thodology can miss things that luck would catch," Nanda said. "But this is a philosophical discussion, not an operational one. The S-22 works. The Navy is satisfied. Continue doing what you're doing."
He walked toward his own vehicle, leaving Karan standing near the hangar.
Bal Thackeray appeared, having waited for the official dignitaries to depart before approaching.
"The Pri Minister warned you about sothing," Thackeray observed. "I saw her expression. What did she say?"
"She said growth creates complexity and complexity creates vulnerabilities," Karan said. "She's concerned that as Shergill Aerospace expands, we'll lose the control that has kept us secure and effective."
"Is she correct?" Thackeray asked.
"Partially," Karan said. "Growth does create complexity. But complexity can be managed if you plan for it. I'm not expanding blindly. Every facility addition, every new hire, every production increase—all of it is planned with security and quality as primary constraints. We're growing carefully."
"The factory expansion we discussed," Thackeray said. "You'll need another 2,000 workers over the next two years to et the S-22 production schedule. Where are you finding them?"
"Technical training programs," Karan said. "We're running our own training facility now—teaching machining, assembly, quality control, all the skilled trades required for aerospace manufacturing. We hire from that program after people complete training and pass security vetting. It's slower than hiring from the general labor pool but it produces workers who et our standards."
"And the security vetting?" Thackeray asked. "You're checking backgrounds, verifying loyalty?"
"Thoroughly," Karan said. "We use private investigators who specialize in industrial security. They check backgrounds, interview references, verify employnt history, look for financial vulnerabilities that could make soone susceptible to recruitnt by foreign intelligence. Anyone who doesn't pass vetting doesn't get hired regardless of their technical skills."
"That's expensive," Thackeray said.
"It's necessary," Karan said. "The alternative is hiring people quickly and discovering later that soone compromised sensitive technology. That cost is much higher than thorough vetting."
Thackeray nodded slowly. "You think like soone who has sothing to lose. That's good. People who have nothing to lose take stupid risks. People who have everything to lose think carefully before acting."
"I have a great deal to lose," Karan said. "Not just personally. The people who work for Shergill Aerospace, the custors who depend on our aircraft, the country that benefits from indigenous defense capability—all of them have sothing at stake in my decisions. I'm conscious of that."
"Good," Thackeray said. "Then we'll talk next week about the expansion. I'll make sure the permits move quickly and the unions understand that this factory is protected. You make sure the workers you hire are Marathi when possible and that the wages stay competitive."
"They'll be Marathi when qualified candidates are available," Karan said. "And the wages are already 40% above regional averages. I'm not cutting pay to reduce costs."
"Then we have an understanding," Thackeray said.
He walked toward his vehicles, his security following.
Karan stood alone near the hangar for a few minutes, watching the facility slowly return to normal operations. The journalists were gone. The dignitaries were gone. The ceremony was complete. What remained was the operational reality: two S-22s aboard Vikrant, seventy more to be delivered over two years, a production schedule that required expanding capacity and hiring thousands of workers while maintaining security and quality standards that the Pri Minister was now watching carefully.
Vardhan approached. "The team is heading back to the facility. Are you coming with us?"
"In a few minutes," Karan said. "I want to think about sothing first."
"What?"
"The Pri Minister said growth creates vulnerabilities," Karan said. "Nanda said success creates the illusion that failure isn't possible. They're both warning about the sa thing—that the next phase is more difficult than what we've done so far."
"Is it?" Vardhan asked.
"Probably," Karan said. "Building three aircraft that work is engineering. Building seventy-two aircraft that all work identically is industrial managent. The skills are different. The risks are different. The assumption that being good at engineering makes you good at industrial managent is dangerous."
"So what do you do?" Vardhan asked.
"I hire people who are good at industrial managent," Karan said. "I recognize what I don't know and I bring in expertise to fill those gaps. The sa way I brought you in for engines and Ramanathan for aerodynamics and Krishnan for structures—I'm doing that for manufacturing managent, supply chain logistics, quality control at scale. I'm not assuming I can do everything myself."
"That's probably wise," Vardhan said.
"It's necessary," Karan said. "The alternative is trying to manage industrial complexity I don't fully understand and making mistakes that compromise the aircraft. I'd rather acknowledge limitations and compensate for them than pretend they don't exist."
Vardhan looked at the hangar where the S-22 had sat this morning. "Three years ago, you told you wanted to build a carrier-based fighter. I thought you were insane. Today, we inducted that fighter into operational service. Three years from concept to deploynt. That's not normal."
"No," Karan agreed. "It's not normal. It's what happens when you compress tilines, accept risk, and work with people who are willing to solve problems instead of explaining why problems can't be solved. The S-22 exists because the team was willing to do difficult things."
"And now we do it again," Vardhan said. "Seventy-two tis."
"Seventy more tis," Karan corrected. "We've already delivered two."
"Seventy more tis," Vardhan repeated. "That's going to take everything we learned building the first two and then so."
"Yes," Karan said. "Which is why we start planning tomorrow for how to scale production without degrading quality. Today we celebrate. Tomorrow we work."
"Always working," Vardhan said. "You ever rest?"
"When the work is done," Karan said. "Which it never is."
They walked toward the vehicles together. The morning had turned into afternoon, the light changing quality, the temperature rising with typical Bombay humidity. Sowhere on Vikrant, non and Prakash were probably being debriefed by naval officers who wanted to know everything about how the aircraft handled. Sowhere in the Shergill Aerospace facility, production teams were already preparing for the next aircraft delivery. And sowhere in the Ministry of Defense, procurent officers were processing paperwork for seventy more aircraft purchases.
The S-22 had been inducted into service. The capability gap had been filled. India's Navy could now project power into the Indian Ocean at ranges and with weapons that had not been possible before.
What happened next would determine whether that capability beca a sustained advantage or a temporary achievent that degraded over ti as production scaled and complexity grew.
Karan was betting on sustained advantage. He had built an organization designed to maintain standards at scale. He had hired people capable of managing complexity. He had implented controls that would preserve security and quality as production expanded.
Whether those bets proved correct would beco clear over the next two years as seventy more aircraft moved from production to delivery to operational deploynt.
For now, the morning's demonstration had proven one thing: the S-22 worked. It flew from Vikrant's deck. It trapped successfully. It t specifications.
Everything else followed from that foundation.
The vehicles departed Mazagon Dock, returning to the Shergill Aerospace facility where the next aircraft was already in assembly and the one after that was being prepared for component integration. The production line moved forward, continuous and disciplined, building machines that would defend India's mariti interests for the next thirty years.
And on Vikrant's deck, two S-22s sat secured and ready, waiting for the operational missions that would begin in three weeks when the carrier departed Bombay Harbor for her first deploynt with indigenous fighter aircraft aboard.
The sea had accepted its wings.
What remained was to prove those wings were strong enough for the storms ahead.
END OF CHAPTER 144
User Comments
0 comments from readers