Chapter 121 - Chapter 117: Wings to the Negev

 Chapter 117: Wings to the Negev — The Inspection

Location:Gorakhpur Air Force Station

Date:16 May 1973 — 08:15 Hours

---

The C-130 Hercules transport carrying the Israeli inspection team touched down on Gorakhpur's main runway at eight-fifteen, precisely on schedule.

Karan stood on the apron beside the hangar complex, watching the aircraft taxi toward the designated parking area. Beside him: Air Marshal Pratap Singh, the Indian Air Force officer coordinating the handover; Colonel Vikram Rathore, chief test pilot for the S-27 program; and a cluster of engineers and technicians who had spent the past week preparing twelve aircraft for the most thorough inspection any of them had ever experienced.

"They're bringing serious people," Pratap Singh said, watching the C-130's engines spool down. "Defense Minister Dayan doesn't travel for symbolic visits. If he's here personally, he's here to verify every claim we've made."

"Good," Karan said simply. His tone carried absolute certainty rather than hope. "We built these aircraft to exceed specifications. Let them test everything. The harder they push, the more confident they'll be when they discover it all works exactly as documented."

The rear ramp lowered. Moshe Dayan emerged first, unmistakable with his eye patch and military bearing. Behind him came fifteen people — pilots in flight suits, engineers carrying equipment cases, technical experts with clipboards already in hand.

This wasn't a ceremonial delegation. This was a team assembled to find every flaw, every exaggeration, every weakness.

The Israeli group approached across the apron.

Pratap Singh stepped forward. "Defense Minister Dayan, welcome to Gorakhpur Air Force Station. We're ready for your inspection. Full access to all systems, complete documentation, flight demonstrations—whatever your team requires."

Dayan's handshake was brief, functional. "Air Marshal. Let me introduce my team, and then we begin immediately."

He gestured to the group behind him.

"Colonel Ran Pekker, Israeli Air Force. Test pilot qualified, twenty-two hundred flight hours, combat experience in F-4 Phantoms and Mirages. He'll lead the flight evaluation."

Pekker stepped forward — early forties, lean and weathered, with the particular intensity of someone who understood viscerally that aircraft performance meant life or death.

"Colonel Rathore will be working with you," Pratap Singh said. "Our chief test pilot for the S-27 program. Over three hundred hours on this aircraft across all flight regimes."

Pekker and Rathore assessed each other in the way experienced pilots did — professional evaluation, mutual respect for the craft.

"Three hundred hours is substantial," Pekker said. His English carried a slight accent but was precise. "Looking forward to hearing what you've learned. Then I verify it myself in the air."

"Exactly what test pilots do," Rathore said with a slight smile. "Verify everything personally rather than trust documentation."

Dayan continued introductions. "Major Yair Cohen and Captain David Shimoni, both fighter pilots with combat experience. Behind them: Avi Weiss, avionics engineer who designed systems for the Kfir program. Dr. Shlomo Raviv, propulsion systems specialist—he's worked with every jet engine Israel has operated since 1956. Moshe Karni, weapons integration expert. And eight additional technical specialists."

"Mr. Karan Shergill," Dayan said, turning to Karan. "I understand you'll be personally involved in this inspection, which is unusual. Most defense contractors send technical representatives, not company owners."

"I built these aircraft," Karan said simply. The statement wasn't boastful—it was fact delivered with absolute confidence. "If you have questions about capabilities or design decisions, I answer them directly. It's faster than filtering through layers of engineers, and frankly, I want to see your team's evaluation firsthand. You're assessing my work."

Something in how he said my work caught Dayan's attention. Not 'our company's work' or 'the team's work'—but a personal claim of ownership that spoke to control.

"Fair enough," Dayan said. "Because I have many questions, Mr. Shergill. Israeli pilots will fly these aircraft into combat. Their lives depend on whether your claims are real or exaggerated."

"My claims are conservative compared to actual performance," Karan said, his tone matter-of-fact rather than defensive. "You'll discover that over the next two days. Every specification in your contract documentation understates what these aircraft can do. I prefer to over-deliver rather than over-promise."

The twelve S-27 Pinaka fighters sat in two rows inside the massive hangar, painted in desert camouflage — tan, brown, and pale gray optimized for operations over the Negev and Sinai. On each tail: the blue Star of David marking them as Israeli property.

The sight stopped the Israeli team momentarily.

These weren't prototypes or development aircraft. These were operational combat platforms, fully equipped, weapons-capable, ready for immediate delivery and deployment.

Ran Pekker walked slowly toward the nearest aircraft, studying every line and surface with the practiced eye of someone who'd evaluated dozens of aircraft types and understood how design translated to performance.

"Tailless delta configuration," he said quietly, more to himself than anyone else. "Single engine, but large—very large for a single-engine fighter. Variable-geometry intake for supersonic optimization. Close-coupled canards for enhanced maneuverability. This is sophisticated aerodynamics. Not derivative—this is original engineering."

He looked back at Karan, his expression shifting from casual assessment to focused interest.

"The contract specifications claimed Mach 2.3 maximum speed, thrust-to-weight ratio exceeding 1.0 at combat weight, combat radius 850 kilometers with external tanks, sustained turn rate 9 degrees per second at Mach 0.9. Those are extraordinary claims for a single-engine aircraft. Actually, those specifications exceed most twin-engine fighters currently operational worldwide. Either you've achieved something genuinely revolutionary, or these specifications are marketing fantasy designed to close a sale."

"Test results from over two hundred evaluation flights," Karan said, his voice carrying the weight of certainty rather than salesmanship."1971 War Proved"

"I'll want to see that data in considerable detail," Pekker said. "But more importantly, I want to fly it myself. 

"Then fly it," Karan said simply. "Test it as hard as you want. Push it to limits. I'm confident in what you'll find."

Dayan had moved to examine the engine intake, his technical background as an armor officer not preventing him from understanding basic aerospace engineering principles. "This is the indigenous engine? Not licensed from General Electric or Pratt & Whitney? Not a Soviet design that was modified? This is actually designed and manufactured entirely in India?"

"Completely indigenous," Karan confirmed. "The Kaveri Mark 1.

Dr. Shlomo Raviv, the propulsion specialist, had been standing back observing the exchange. Now he stepped forward, pulling a small notebook from his pocket.

"Mr. Shergill, I'm going to be very direct with you because we don't have time for diplomatic niceties or commercial pleasantries. I've been working with jet engines since before you were born. I've torn down American engines, British engines, French engines, Soviet engines we've captured in combat. I understand what's possible in propulsion systems and what's fundamentally not possible given current technology and materials science. So when you say 'completely indigenous turbofan,' I need specific technical details—starting with basic performance specifications."

"Ask whatever you need," Karan said, completely unfazed by Raviv's directness. If anything, he seemed to prefer it.

"Start with thrust ratings," Raviv said, pen poised over his notebook. "Dry thrust and afterburning thrust. And don't give me rounded marketing numbers that sound impressive. Give me the actual certified test stand measurements with real precision."

"Dry thrust: 82 kilonewtons," Karan said. "Afterburning thrust: 115 kilonewtons. 

Raviv's pen stopped moving completely. He looked up from his notebook slowly, his expression shifting from professional skepticism to genuine disbelief.

"I'm sorry, could you repeat those numbers? I want to make absolutely certain I heard correctly."

"Dry thrust 82 kilonewtons, afterburning 115 kilonewtons," Karan repeated, his tone unchanged. He wasn't emphasizing the numbers for dramatic effect—he was simply stating facts.

Raviv stared at him for a long moment. Then he looked at Dayan, his voice carrying an edge of frustration mixed with confusion.

"Minister, those numbers are impossible. They cannot be correct. There is no engine currently operational anywhere in the world that produces those thrust characteristics in this size and weight class. This violates everything I know about current propulsion technology."

"They're not impossible," Karan said calmly. "They're measured. We have complete test stand data—hundreds of hours of operation, dozens of engines tested, consistent results. The numbers are real."

"Let me explain why I'm skeptical," Raviv said, his voice taking on the patient tone of someone explaining fundamental physics to a student. "The F-4 Phantom that Colonel Pekker flies in Israeli service? Each of its J79 engines produces approximately 52 kilonewtons dry thrust and 79 kilonewtons with afterburner engaged. That's one of the most powerful and proven operational engines in Western inventory, developed over more than a decade of American research and manufacturing. The Mirage's Atar 9C engine—43 kilonewtons dry, 60 kilonewtons with afterburner. The American F-15, which just became operational last year with what is literally the most advanced jet engine in the world? The Pratt & Whitney F100 produces 65 kilonewtons dry thrust, 105 kilonewtons with afterburner."

He pointed directly at the S-27's engine intake, his gesture emphatic. "You're telling me that India—a nation that hasn't historically manufactured advanced jet engines at all—has somehow developed an engine that produces 26% more dry thrust than the F-15's cutting-edge engine and nearly 10% more afterburning thrust than the most advanced American turbofan? An engine that produces over 50% more thrust than proven designs that have been in operational service for over a decade? That's not just incremental improvement—that's revolutionary performance that exceeds anything the Americans or Soviets have fielded."

"Yes," Karan said simply. The single word carried absolute certainty.

"That's not possible," Raviv said flatly, his frustration now evident. "The metallurgy required for those turbine inlet temperatures, the thermodynamic efficiency needed for that specific fuel consumption, the turbine blade cooling technology, the compressor aerodynamic design—you're claiming performance levels that represent breakthroughs in multiple disciplines simultaneously. And you've done this in how long? Three years? Five years? That's not credible, Mr. Shergill. Either you've made a fundamental measurement error in your test stand calibration, or someone has deliberately falsified the data for commercial purposes."

"Three years for the aircraft," Karan said, his voice still completely calm but now carrying a harder edge. "The engine development started in 1970—so three years for the powerplant. And we've achieved exactly what we set out to achieve. The test data exists. The engines exist and operate. They're installed in these twelve aircraft sitting directly in front of you, and they work precisely as specified."

The room went silent. Three years wasn't much better than Raviv's earlier estimate—it was still impossibly fast by conventional development timelines.

Ran Pekker had been listening to this exchange with growing interest. "Dr. Raviv, hypothetically speaking—if those thrust numbers are somehow real, what would that thrust-to-weight ratio mean for aircraft performance?"

"If those numbers are real?" Raviv said, his tone making clear he still didn't believe they were. "It would mean this single-engine fighter would have a thrust-to-weight ratio exceeding any operational fighter aircraft in the world.

"But you don't believe the numbers are real," Pekker observed.

"I believe in physics and materials science," Raviv said. "And physics says you don't develop revolutionary engine technology in three years. The Americans have been developing the F100 engine for over a decade—started in the early 1960s, finally reached operational service in 1972. The Soviets have been working on their advanced turbofan engines for fifteen years or more. This kind of breakthrough would require simultaneous advances in multiple disciplines—materials science, thermodynamics, aerodynamics, manufacturing processes, cooling technology. It's simply not credible that India achieved this in three years."

Avi Weiss, the avionics engineer, spoke up for the first time. "Could they have acquired the technology from somewhere? Stolen designs from American or European manufacturers, purchased blueprints through black market channels, something like that?"

"From whom?" Raviv asked, spreading his hands.

Moshe Dayan had been listening to this technical debate silently. Now he spoke, his voice cutting through the discussion.

"Gentlemen, we have a simple way to resolve this debate rather than arguing about what's theoretically possible. Mr. Shergill, you claim these engines produce 82 kilonewtons dry thrust and 115 kilonewtons with afterburner. You claim you have comprehensive test stand data proving these performance levels. Show us the data immediately.

"I can provide complete test stand data within fifteen minutes," Karan said.

"Then let's see it right now," Dayan said, his tone making clear this was the critical test. "Before we waste more time inspecting an aircraft that might be based on fundamentally false specifications."

-------

09:00 Hours — Engineering Briefing Room

The Israeli team filed into a conference room where three complete sets of bound technical documentation had been prepared. Each set comprised several thousand pages—comprehensive test data, certification reports, engineering analyses, independent verification documents.

Karan opened the first volume directly to a specific section and handed it to Dr. Raviv.

"This is the thrust certification test data," Karan said. "Two hundred pages of measurements from test stand operations conducted here at our Gorakhpur facility. The test facility is approximately two kilometers from this hangar—I can take your entire team there to see it directly if you want to verify the facility exists and is capable of these measurements.

Raviv took the document and began reading immediately, his two assistant engineers looking over his shoulder and taking their own notes.

The room fell completely silent except for the sound of pages turning and occasional pencil scratching on paper.

Raviv's expression shifted progressively as he read—from deep skepticism to confusion to something approaching shock.

"These thrust measurements," he said slowly after perhaps ten minutes, not looking up from the pages. "They're consistent across multiple test runs. Different engines tested, different test dates spanning months, different ambient temperature conditions—but the performance is repeatable within normal measurement variation. That's... that's the signature of real experimental data, not fabricated data. 

He turned to a different section, his hands moving faster now as his interest grew. "The turbine inlet temperature. You're running at 1,450 degrees Celsius. That's extraordinarily hot—hotter than most operational engines dare to run. The F100 runs at about 1,370 degrees Celsius. How are you achieving 1,450 degrees without simply melting the turbine blades in the first few seconds of operation?"

"Advanced blade cooling technology ," Karan said. "The specific technical approaches are proprietary—you're purchasing aircraft, not manufacturing licenses for engine technology."

Raviv's expression flickered with frustration. "Mr. Shergill, I'm trying to assess whether these performance claims are technically credible. Understanding your cooling approaches would help me validate—"

"The validation comes from test data and physical inspection of the hardware," Karan interrupted, his tone polite but absolutely firm. He wasn't being rude—he was simply drawing a clear boundary. 

Dayan spoke up, supporting Karan's position. "That's entirely reasonable, Dr. Raviv. We're purchasing operational aircraft as complete systems, not engine manufacturing technology. 

Raviv nodded reluctantly, understanding the logic even if he wasn't happy about it. He continued reading through the test data.

He examined compressor performance data, bypass ratio specifications, specific fuel consumption rates, weight characteristics, maintenance requirements.

"The bypass ratio is low—0.35 to 1," Raviv observed, making notes. "That's optimized for supersonic performance rather than subsonic fuel efficiency. Makes sense for a fighter application focused on air superiority, but it means this engine will consume fuel significantly faster during subsonic cruise than engines optimized differently."

"Correct," Karan confirmed. "Fuel consumption is approximately 20% higher than engines optimized for subsonic cruise efficiency. But we prioritized thrust and high-speed performance over fuel economy. For the fighter's primary mission profile—supersonic intercepts, air superiority combat, rapid response—the performance tradeoff is absolutely worth the additional fuel consumption."

"Engine weight," Raviv said, checking specifications. "1,850 kilograms for the complete engine including afterburner section. That's heavy for this thrust class. The F100 is lighter by about 200 kilograms."

"Yes," Karan agreed without defensiveness. "We're using some heavier structural components and more robust materials. We could reduce weight further with certain advanced composites and titanium alloys we're still developing, but we chose to prioritize reliability and durability over absolute weight optimization for this first production version. Better to have a slightly heavier engine that works consistently than a lighter engine that breaks."

"First production version?" Raviv looked up sharply, catching the phrasing. 

"This is the Kaveri Mark 1," Karan lied. "It meets all performance requirements for the S-27 fighter and exceeds several of them. But we're already developing (already developed for indian navy) the Kaveri Mark 2 with improved materials, better fuel efficiency, and reduced weight while maintaining the same thrust levels.

The room went absolutely silent.

Ran Pekker spoke quietly, his voice carrying a note of disbelief. "You're not just claiming you've built one advanced engine that somehow matches Western performance. You're saying you have an ongoing engine development program with multiple generations planned and resourced. That's... that's what the Americans do. That's what major aerospace powers with decades of experience and billions in funding do. Not companies that started three years ago."

"India isn't just building one fighter to fill one contract," Karan said, his voice carrying absolute conviction. "We're building sustained aerospace capability that will continue developing for decades. That requires thinking beyond single programs. It requires building the industrial infrastructure, the technical expertise, the testing facilities, the supply chains—everything needed to continue advancing. This isn't a one-time effort. This is the foundation of India's aerospace industry for the next fifty years."

The way he said it—not as aspiration but as established fact—conveyed something that made Dayan study him more carefully. This wasn't a contractor hoping to sell aircraft. This was someone who had built something fundamental and was describing what already existed.

Moshe Dayan had been paging through a different volume of documentation—structural test data for the airframe. He closed it and looked at Karan directly, his single eye assessing.

"Mr. Shergill, I'm going to ask you a blunt question, and I want a direct answer. Is the Indian government funding this entire program? Because the capital requirements for what you're describing—comprehensive engine development program with multiple variants, aircraft development, semiconductor manufacturing for avionics, advanced materials science, production facilities, testing infrastructure—we're talking about investment levels measured in billions of dollars. That's not typical private sector activity. That's national-level program funding. So is your government the actual owner here, with you serving as the public face?"

Something shifted in Karan's expression—not defensiveness, but a slight smile that suggested Dayan had asked an interesting question.

"Shergill Group is privately owned and operated," Karan said. "I own it. Not the government. Not state enterprises. Me. The Indian government provides certain support—they award contracts for aircraft procurement, they provide licenses for operating certain facilities, they give access to research institutions and testing ranges. But they don't own the company, they don't direct its operations, and they don't control its decisions."

He paused, then added something that made his relationship with the government clearer.

"There was an attempt in 1971 to bring Shergill Group under government control. During the war with Pakistan, certain ministers thought such critical defense manufacturing should be nationalized—brought under direct state ownership for national security reasons. The Prime Minister was considering it seriously."

"What happened?" Dayan asked, genuinely curious now.

"By the time they seriously considered nationalization, Shergill Group had already grown too large and too integrated to be effectively controlled through government ownership," Karan said, his tone matter-of-fact. "We had vertical integration across too many sectors—steel production, machine tools, semiconductors, aerospace. Nationalizing one part would break the integration that made the whole structure effective. And frankly, the government recognized that I could build and deliver capabilities faster than any state enterprise could. So they chose partnership over control."

"Partnership," Dayan repeated, testing the word. "That's a diplomatic way of describing the relationship."

"It's an accurate way," Karan said, and something in his tone suggested the power dynamic wasn't quite what official descriptions would indicate. "The government needs what I build. I need their contracts and regulatory support. We cooperate because cooperation serves both our interests. But let's be clear, Minister Dayan—when the Prime Minister wants fighters or semiconductors delivered on an urgent timeline, she calls me. Not the other way around. That tells you something about who actually holds leverage in this partnership."

The statement hung in the air. It wasn't boastful—it was a simple statement of fact delivered with complete confidence. But it suggested that Karan's relationship with the Indian government was more complex than a typical contractor-client relationship.

Dr. Raviv had been continuing to read through the engine documentation during this exchange. Now he looked up again, his expression having shifted substantially from his initial skepticism.

"Then let's inspect the hardware immediately," Dayan said.

The Israeli team gathered around aircraft number three, where Indian technicians had already removed engine cowling panels to expose the complete powerplant beneath.

The engine was massive—nearly five meters long, approximately two meters in diameter at the fan face, gleaming under the bright hangar lights. It sat on special access stands, positioned for detailed examination.

Dr. Raviv approached slowly, almost reverently. For an engine specialist, this was like an archaeologist discovering ruins that supposedly shouldn't exist but apparently did.

"The variable-geometry intake system," he said, studying the movable ramps at the front of the engine. "These adjust automatically based on flight conditions?"

"Hydraulically actuated, electronically controlled through the flight control computer," an Indian engineer confirmed. "The system monitors airspeed, altitude, and Mach number continuously. At subsonic speeds, the ramps are fully open for maximum airflow. As you accelerate through transonic and into supersonic flight, they progressively close to slow the incoming air and maintain optimal conditions at the compressor face. It's fully automatic—pilot doesn't need to manage it."

Raviv examined the actuation mechanism carefully—hydraulic cylinders, control linkages, position sensors, feedback systems. He tested the movement by hand, feeling for binding or excessive play in the mechanism.

"Very well manufactured," he said, genuine surprise in his voice. "Smooth operation throughout the range of motion. No obvious weaknesses or poor fitment. This is precision mechanical engineering."

He moved to the fan blades—large titanium components visible through the intake, each blade precisely shaped and positioned.

"These are titanium alloy?" he asked, though he could see they were.

"Titanium-6 aluminum-4 vanadium alloy," the Indian engineer confirmed. "Wide-chord blade design for high airflow capacity. Hollow construction for weight reduction. Each blade is precision-machined from forged billets and individually balanced to extremely tight tolerances."

Raviv pulled out a small flashlight and leaned into the intake, examining the blades closely under bright direct light. He looked at leading edges for damage or manufacturing defects, trailing edges for proper finishing, blade surfaces for quality and consistency.

"I need to remove one of these fan blades and examine it in much more detail," he said, straightening up.

"We have spare blades available for destructive examination," the Indian engineer said. "I'd prefer not to remove blades from an operational engine unless absolutely necessary—it requires complete rebalancing of the entire fan assembly, which is time-consuming and introduces risk of damaging the engine."

"Spare blades are acceptable," Raviv said. "Show me."

An Indian technician wheeled over a specialized cart containing engine components—fan blades, compressor blades, turbine blades, seals, bearings, specialized fasteners. Each component was individually wrapped in protective material and labeled.

Raviv selected a fan blade and carefully unwrapped it. The component was approximately one meter long, gracefully curved with precise aerodynamic shaping, polished titanium gleaming.

He examined it under bright overhead lights, using a magnifying glass to inspect the surface finish in detail. He checked dimensional accuracy with precision calipers at multiple points. He tested the material hardness with a small portable tester.

"This is genuinely high-quality manufacturing," he said finally, making notes in his notebook. "Surface finish is excellent—no tool marks, no irregularities, proper polishing. Dimensional accuracy is within extremely tight tolerances. Material properties match the specifications. This is not crude manufacturing trying to copy Western designs—this is precision aerospace component production that meets or exceeds Western standards."

He set the fan blade aside carefully and picked up a turbine blade—significantly smaller, more geometrically complex, made of nickel-based superalloy rather than titanium.

"This is where it becomes really interesting," Raviv said, his voice taking on greater intensity. 

"The crystal structure of the metal," he said, studying the blade under magnification. "This is directionally solidified?"

"Yes," the Indian engineer confirmed. "Solidification is controlled during the casting process so grain boundaries align parallel to the primary stress direction—along the length of the blade. That eliminates transverse grain boundaries that would be weak points under the combination of thermal and mechanical stress these blades experience."

interior feeding film cooling holes at strategic points on the external surface."

Raviv held the blade up to bright light, trying to see through the metal to visualize the internal passages, though of course the metal was opaque.

Raviv took the sectioned blade and studied it intensely for several minutes. The internal cooling passages were clearly visible—complex three-dimensional channels routed through the blade interior with obvious sophisticated design, feeding multiple film cooling holes at optimized positions on the external surface.

"This is very sophisticated cooling design," Raviv said quietly, almost to himself. "The cooling passages aren't just drilled randomly—they're optimized for thermal protection based on the temperature distribution and heat flux patterns across the blade surface. This level of design requires extensive computational modeling, years of development, probably dozens of prototype iterations to get right."

"Three years of focused development," Karan said. He'd been observing the inspection silently from a few meters away. "We started turbine cooling design in 1970 when we began the engine program. It was the hardest part—harder than the aerodynamics, harder than the compressor design. But we had access to India's best computational capabilities and materials scientists, and we solved it."

"Three years is still remarkably fast for this level of sophistication," Raviv said, but his tone had shifted from skepticism to reluctant acceptance. He continued examining engine components—compressor blades with precise aerodynamic shaping, combustor sections with complex fuel injection systems, turbine disks, specialized bearings, seal assemblies. Each examination revealed high manufacturing quality and sophisticated engineering.

After nearly ninety minutes of detailed inspection, Raviv stepped back from the engine bay and looked at Moshe Dayan.

"My initial assessment was based on the assumption that India couldn't possibly have developed this technology," Raviv said honestly. "That assumption was wrong. The evidence is sitting right here in front of me—real hardware, sophisticated design, high-quality manufacturing. I was wrong to dismiss the claims out of hand based purely on my preconceptions about what should be possible."

Ran Pekker had been listening to Raviv's technical assessment with obvious interest. Now he spoke up.

"Dr. Raviv, if these engines actually produce the claimed thrust—82 kilonewtons dry, 115 kilonewtons with afterburner—what does that mean specifically for fighter performance in air combat?"

"It means this aircraft will comprehensively outperform anything currently in Israeli inventory," Raviv said bluntly, no longer hedging his assessment. "Better acceleration than the F-4 Phantom despite having only one engine instead of two. Significantly better climb rate—probably 30-40% better. Much better sustained turn performance because of the thrust-to-weight advantage—you can maintain energy in turning engagements where conventional designs bleed speed rapidly. Better high-altitude performance. The only area where it might be potentially inferior is range, because single-engine configuration inherently means less total fuel capacity, and this engine is optimized for performance rather than fuel efficiency."

"But for air superiority combat specifically?" Pekker pressed, clearly thinking about tactical applications.

"For air superiority, this would be the best fighter Israel has ever operated," Raviv said with certainty. "Better than the Mirage III, substantially better than the F-4. The only remaining question is operational reliability—does the engine work consistently over extended service, or does it break frequently? A high-performance engine that's constantly grounded for maintenance is operationally useless regardless of its specifications. But if reliability is acceptable—and their maintenance data suggests it is—this is genuinely game-changing capability."

"We tested extensively before declaring the engine operationally ready," Karan said. "Over 800 hours of ground test stand operation before the first flight test. We deliberately found and fixed problems on the ground in controlled conditions rather than discovering them in the air during flight testing where failures can kill pilots. It's a conservative approach that delayed the program somewhat, but it's paying off in operational reliability."

Avi Weiss, the avionics engineer, had been examining the avionics bay on a different aircraft while Raviv focused on the engine. Now he called out across the hangar:

"Minister Dayan, you need to come see this avionics suite immediately."

The group moved to where Weiss was leaning into an open equipment bay, examining circuit boards and systems racks with obvious interest.

"These core avionics systems are domestically manufactured?" Weiss asked, though his tone suggested he already knew the answer and was impressed.

"Yes," Karan confirmed. "Core systems—the pulse-Doppler radar, navigation system, weapons computer, digital flight control computer, heads-up display—all designed and manufactured at our facilities here in Gorakhpur and at our semiconductor plant. Some peripheral components like certain RF filters and specialized vacuum tubes we currently import, but all critical systems are indigenous."

"This radar system," Weiss said, pointing at a large line-replaceable unit. "What are the detailed specifications?"

"Multimode pulse-Doppler radar," an Indian avionics engineer explained, clearly proud of the system. 

Weiss pulled out the radar unit carefully—it slid out on precision rails for maintenance access. He examined the internal construction, the circuit board layout, the waveguide connections, the component quality.

"These circuit boards use Indian-manufactured semiconductors?" he asked.

"Yes," Karan confirmed. "Our semiconductor facility here in Gorakhpur. Four-micron process technology currently, which is cutting-edge for military applications in 1973. We're transitioning to three-micron process within six months as we refine the manufacturing."

"Four-micron is genuinely cutting-edge," Weiss said, his voice carrying surprise. "That's competitive with the best Western military semiconductor manufacturers. Most people don't realize that military semiconductors often use slightly older process technology than cutting-edge commercial chips because reliability matters more than absolute miniaturization. Four-micron with proper quality control is excellent for military radar applications."

He continued examining the avionics equipment. "The weapons computer—this integrates directly with the radar for targeting?"

"Complete integration," the Indian engineer confirmed enthusiastically. "Radar provides target information—range, bearing, closure rate, altitude. Weapons computer calculates firing solutions for both guns and missiles. Heads-up display shows aiming cues directly to the pilot. For gun employment, we display continuously-computed impact point in the HUD. For missiles, we display launch acceptability region. Pilot just needs to maneuver the aircraft to meet the launch conditions, then fire—the systems handle all the calculations."

"That's fourth-generation fire control architecture," Weiss said. "Most operational fighters don't have this level of systems integration yet. Even the F-15 has less sophisticated integration between radar and weapons."

"We designed all the systems from the ground up to work together as an integrated package," Karan said. "Rather than bolting together separate systems from different manufacturers—which is what typically happens when you're integrating Western and Israeli avionics—we designed everything to share data and coordinate from the beginning. It's one significant advantage of starting completely fresh rather than trying to upgrade legacy platforms with incompatible systems."

Weiss spent another thirty minutes examining avionics systems in detail, asking technical questions, taking extensive notes, occasionally whistling quietly at something he discovered. Finally he turned to Dayan.

"Minister, the avionics suite is substantially more sophisticated than I expected. Genuinely sophisticated, not just adequate. The radar capabilities are impressive—if the detection range performance matches their specifications, which I'll want to verify during flight testing tomorrow, this will provide situational awareness comparable to our most modern Western fighters. The weapons computer integration is modern fourth-generation architecture. The heads-up display is clear and comprehensive. If everything works as documented, this aircraft will have targeting and weapons employment capability that matches or exceeds anything in Israeli inventory."

Moshe Karni, the weapons integration specialist, had been examining the weapons pylons and hardpoints on yet another aircraft. He called the group over, clearly excited about something.

"Look at this hardpoint design," he said, pointing at the weapons pylon attachment mechanism. "This isn't a copy of NATO or French systems. This is completely original engineering, and honestly, it's actually better than standard Western designs."

He demonstrated the mechanism: the pylon could rotate through a 30-degree arc, allowing weapons to be loaded from the side rather than directly beneath the aircraft.

"Standard NATO hardpoints require ground crew to work directly underneath the aircraft when loading heavy weapons," Karni explained to Dayan. "If there's an accident—weapon drops, pylon mounting fails, hydraulic system leaks—ground crew can be seriously injured or killed. It's dangerous and we've lost good people to loading accidents. This design loads weapons from the side at an angle, then the pylon rotates into flight position and locks securely. Much safer for ground crews, and actually faster to load because you can position the loading equipment more effectively."

"And structural strength isn't compromised by this rotating mechanism?" Dayan asked, clearly thinking about combat loads.

"We load-tested the pylons to twelve times expected maximum operational loads," Karan said. "Deliberate over-engineering. Weapon loading and employment is one area where you absolutely don't want to cut safety margins close—stakes are too high."

Karni examined the electrical interfaces for weapon arming and release carefully. "These electrical connections are compatible with standard Western weapons? American missiles, French bombs?"

"We designed specifically for NATO compatibility," Karan confirmed. "The electrical interfaces match NATO standards for most common weapons. Some specific weapons might need simple adapter cables, but basic connectivity is there. For Israeli-specific weapons like Python air-to-air missiles and your locally-manufactured bombs, we'll need to develop full integration—electrical interface adapters, software updates for the weapons computer, flight testing for clearance. That's normal integration work for any new platform."

"How long for Israeli weapons integration?" Karni asked.

"Simple air-to-air missiles like Python—four to six weeks for electrical integration, another four weeks for flight testing and clearance. Guided bombs—two to three months total. Precision-guided munitions with sophisticated seekers could take four to five months for full integration and operational clearance."

The Israeli team worked with methodical professionalism, asking hundreds of detailed technical questions, taking extensive notes and measurements, photographing critical components from multiple angles.

As the afternoon progressed, Karan observed a subtle but definite shift in their demeanor. The initial deep skepticism was progressively giving way to something else—grudging professional respect mixed with genuine disbelief that they were seeing what they were seeing.

At one point during a brief break, Moshe Dayan pulled Karan aside for a private conversation away from the larger group.

"Mr. Shergill, I need to understand something at a strategic level, not technical details—my team is assessing those. How did India develop this capability? I don't mean the engineering specifics. I mean strategically. How did a nation without a meaningful aerospace industry three years ago reach this point? What did we miss in our intelligence assessments? What did Western intelligence services miss?"

Karan considered the question carefully before answering, understanding that his response would shape how Israel viewed India's capabilities going forward.

"What you missed—what everyone missed—was that India had the complete technical foundation but lacked the industrial organization and political will to use it effectively," he said. "We have excellent engineering universities producing thousands of qualified engineers annually. We have research institutions that have been working on advanced technical problems for decades. We have manufacturing capability distributed across various industrial sectors. What we fundamentally lacked was someone to organize all of that capability toward specific concrete goals, and a government willing to support that organization even when it required uncomfortable decisions."

"And you provided that organization," Dayan said, watching him carefully.

"I provided focus and integration," Karan said. "The technical talent existed already. The engineering knowledge existed. The manufacturing experience existed. I simply assembled it effectively, pointed it at clear objectives, and drove execution until we delivered results. Additionally, I had significant advantages—I was starting completely fresh with no legacy systems to maintain, no organizational inertia to overcome, no entrenched bureaucracies to satisfy. I could build exactly what was needed without compromising for political or bureaucratic reasons."

Dayan studied him for a long moment. "You're very young to have built this kind of power."

"I'm twenty-three," Karan said. "But I've been building this since I was Twenty, and I understood power dynamics before that. Age is less relevant than capability and timing."

"And now Israel benefits from what you've built," Dayan said.

"If these aircraft meet your operational requirements," Karan said. "Which they will."

"They will," Dayan agreed, his tone suggesting his assessment had already shifted substantially from skepticism to acceptance. "I've seen enough today to know that these are real capabilities, not marketing exaggerations or technical fantasies. Tomorrow's flight testing will confirm the performance characteristics, but the hardware inspection has already proven these aircraft are serious military systems built to high standards."

---

7:30 Hours — Flight Test Data Review

The Israeli team reconvened in the conference room where complete flight test documentation had been prepared and organized.

Ran Pekker opened the first bound volume and started reading. Within minutes he was completely absorbed, occasionally making notes in margins or cross-referencing different sections of the data.

The room fell silent except for occasional questions from the Israeli team members and detailed answers from Indian engineers.

"This specific flight test on February 14th," Pekker said after approximately thirty minutes of intense reading. "High-altitude supersonic performance evaluation. You reached Mach 2.1 at 45,000 feet according to these measurements. What was the engine temperature margin at that flight condition?"

Colonel Rathore, who had personally flown that specific test flight, answered: "Exhaust gas temperature was 89 percent of maximum certified limit. We had significant thermal margin for sustained cruise at that speed—we could have maintained it longer if fuel quantity had permitted."

"Sustained cruise meaning how long?" Pekker asked, making notes.

"We actually maintained Mach 2.28 for eight continuous minutes during that test flight," Rathore said. "Fuel consumption was high as expected—approximately four times subsonic cruise consumption—but engine temperatures remained stable throughout. No thermal issues, no performance degradation. We could have sustained that speed longer—we ended the supersonic run because we needed to preserve fuel for the return flight and landing, not because of any engine limitations."

Pekker nodded, understanding the operational tradeoff. He turned to another section of the test data.

"Low-speed handling characteristics. The contract specifications claimed good low-speed handling, but tailless delta designs are typically not great at slow speeds because of the inherent aerodynamics. What's the actual approach speed for landing?"

"220 kilometers per hour is our standard approach speed," Rathore said. "We can fly slower—we've tested successfully down to approximately 200 kilometers per hour—but handling becomes less precise and requires more pilot attention below 220. Leading-edge slats deploy automatically based on angle of attack sensors, which significantly helps low-speed lift generation. Hydraulically powered control surfaces provide adequate control authority even at low speeds. Overall handling is stable and predictable for landing operations."

Pekker continued reading systematically for another hour, working through performance data methodically, asking detailed questions about specific test conditions, crosschecking data between related sections.

"You've had one engine failure during the complete testing program?" he asked, finding an incident report dated approximately six months earlier.

"Yes," Rathore confirmed without attempting to hide it. "Single turbine blade failure at 11,000 feet during a high-speed acceleration test. The blade failure was contained within the engine case—didn't puncture through or cause any secondary damage to surrounding systems. The pilot executed a successful single-engine landing without any significant difficulty. We traced the failure to a manufacturing defect in that specific blade—a material inclusion that created a stress concentration point. We improved our quality control procedures for turbine blade manufacturing after that incident, implemented additional inspection steps."

"And no engine failures since that incident?" Pekker asked.

"Zero engine failures in the subsequent 800 flight hours," Rathore said. "The manufacturing process improvements appear to have been highly effective."

"One failure in 1,800 total hours of flight testing is actually quite good reliability for a new engine design," Pekker observed. "The F100 engine in the American F-15 had significantly worse early reliability—multiple failures, several emergency landings, at least one complete loss of an F-15 due to engine failure during testing."

He closed the test data volume and looked at the assembled Israeli team members.

"Gentlemen, I've now reviewed approximately half of the available flight test data in detail. I could spend another full week reading through all the rest of this documentation, but I've seen enough to form a preliminary assessment. Either this aircraft performs exactly as documented across this comprehensive dataset, or India has somehow created the most elaborate, technically consistent, and detailed fraud in aviation history."

"And which do you think it is?" Dayan asked directly.

"It performs as documented," Pekker said without hesitation. "The data is far too consistent, too detailed, too technically coherent to be fabricated. You cannot fake hundreds of individual flights across such diverse conditions and environmental factors and have everything fit together this well with this level of internal consistency. This degree of data integration and cross-correlation only comes from actual systematic flight testing conducted over extended periods."

"So tomorrow you want to fly it yourself," Dayan said.

"Tomorrow I absolutely need to fly it myself," Pekker corrected, emphasis on the word \*need\*. "I trust the data—it's clearly legitimate. But I'm a test pilot. I need to feel the aircraft directly through my own hands and body. I need to know personally how it responds to control inputs, how it handles across different flight regimes, whether the performance I'm reading about in these documents actually translates to real flying qualities that a combat pilot can use tactically."

"Can we schedule three separate evaluation flights tomorrow?" Dayan asked Pratap Singh. "Colonel Pekker, Major Cohen, and Captain Shimoni—I want all three of my pilots to evaluate the aircraft completely independently and provide separate assessments."

"We can definitely schedule that," Pratap Singh confirmed. "0700 hours for Colonel Pekker's flight, 0930 for Major Cohen, 1200 for Captain Shimoni. Each pilot gets complete pre-flight briefing, safety chase aircraft, full test profile including low-speed handling evaluation, high-speed supersonic performance, and combat maneuvering."

"Agreed," Dayan said.

---

The Israeli team gathered in a private conference room for their internal assessment briefing—no Indians present except for Karan, who Dayan had specifically invited to hear their preliminary conclusions.

"First-day assessment impressions," Dayan said, looking around the table at his team. "I want completely honest technical assessments from everyone, not diplomatically softened evaluations. Dr. Raviv, start with your propulsion assessment."

Raviv spoke carefully, clearly organizing his thoughts.

"The engine is real and performs as claimed," he said directly. "I was deeply skeptical this morning—frankly, I thought the thrust specifications were physically impossible given known technology and development timelines. But after personally examining the physical hardware in detail, reviewing the comprehensive test data, and seeing the manufacturing quality firsthand, I'm now convinced. This is a sophisticated, well-designed, high-performance turbofan engine that will produce the claimed thrust levels. The metallurgy is genuinely advanced. The cooling design is sophisticated—more sophisticated than I expected. The manufacturing quality is high—comparable to Western standards. If long-term reliability matches what their short-term operational data suggests—and I have no particular reason to doubt it does—this is a world-class engine that performs at the level of the best Western designs."

"Avi, your avionics assessment?" Dayan asked.

Weiss leaned forward, clearly engaged. "The avionics suite is substantially more capable than I expected before this inspection. The radar system is sophisticated—true multimode capability, pulse-Doppler processing, track-while-scan functionality, look-down/shoot-down capability for engaging low-altitude targets. Maximum detection range claims appear entirely credible based on the antenna aperture size and transmitted power output specifications I examined. The weapons computer integration is genuinely modern—this is fourth-generation fire control architecture that most operational Western fighters don't have yet."

"Overall assessment of the avionics?" Dayan pressed.

"The avionics will work extremely well," Weiss said confidently. "I want to see everything operating during actual flight testing before I make my absolute final judgment, but based on comprehensive hardware inspection and detailed documentation review, this aircraft will provide situational awareness and weapons employment capability that's directly comparable to Western fourth-generation fighters. Possibly better than some Western systems in certain specific areas."

"Moshe, your weapons integration assessment?"

Karni spoke with obvious enthusiasm. "Weapons systems are very well-designed and intelligently implemented throughout.

"We'll need to conduct integration work for Israeli-specific weapons like Python missiles and our locally-manufactured guided bombs," Karni continued. "But that's entirely expected and the timeline they quoted—four to six weeks for air-to-air missiles, two to three months for guided bombs—that's actually faster than typical integration programs. The platform is fundamentally capable and well-designed for weapons employment."

"Colonel Pekker, your overall aircraft design assessment?"

Pekker had been listening to the technical specialists with focused attention throughout. Now he spoke slowly, choosing his words with obvious care to be precise.

"This morning when we arrived, I genuinely thought we were looking at an over-marketed aircraft that would disappoint significantly when tested rigorously against real-world standards. Tonight, after this comprehensive inspection, I honestly think we're looking at the single most capable fighter aircraft that Israel has ever had the opportunity to purchase from any source."

He let that statement settle for a moment before continuing with supporting detail.

"The fundamental design is sophisticated—genuinely sophisticated, not just adequate. The engineering execution is sound throughout every system we examined. The manufacturing quality is consistently high across all components. The test data documentation is comprehensive, detailed, and clearly credible. If this aircraft flies tomorrow performing the way all this documentation suggests it will fly—and I firmly believe it will—then Israel is acquiring a fighter with performance capabilities that exceed the F-4 Phantom substantially, exceed the Mirage III substantially, and honestly rival anything the Americans are currently fielding including the brand-new F-15."

"That's an extremely strong endorsement," Dayan observed.

"It's an evidence-based assessment, not enthusiasm," Pekker said. 

"Acceleration, climb rate, sustained turn capability, energy management in maneuvering combat—all of those critical performance parameters depend fundamentally on thrust-to-weight ratio," Pekker continued with obvious conviction. "This aircraft has the raw power to dominate the performance envelope against any opponent. Add in the sophisticated fourth-generation avionics we examined, the well-designed weapons integration, the proven supersonic capability to Mach 2.3—this is a complete package that will give Israeli pilots decisive advantages."

"Identifiable weaknesses?" Dayan asked.

"Combat radius is somewhat limited by the single-engine configuration and the engine's optimization for performance rather than fuel efficiency," Pekker said. "850 kilometers with external tanks is adequate for all Israeli operational requirements, but it's not long-range strategic capability like the F-4 provides. Also, this is a brand-new design from a new manufacturer—there will inevitably be unknown issues that only emerge during extended operational service that we can't identify during a two-day inspection. But those are entirely acceptable tradeoffs for the performance capability this aircraft delivers."

Dayan looked directly at Karan. "You're hearing these preliminary assessments from my team. These are not final conclusions—final judgment comes after tomorrow's flight testing is complete. But the hardware inspection and comprehensive documentation review have substantially changed my team's assessment from initial skepticism to strongly positive. Do you want to add anything?"

"Only that tomorrow's actual flight evaluation will validate everything the test data shows," Karan said calmly, projecting complete confidence. "The aircraft performs as specified. Your pilots will confirm that directly through their own hands."

Dayan nodded slowly, then said something that caught Karan slightly off guard:

"Mr. Shergill, your personal background includes military service as an Army captain and intelligence operational work in deep cover inside Pakistan for two years from 1968 to 1970. That's extraordinarily difficult and dangerous work. Deep cover operations require specific personal capabilities. The fact that you're sitting here today means you executed that mission successfully and survived extraction."

Karan's expression didn't change noticeably. "India's security situation in the late 1960s required certain operational flexibility in how we deployed national capabilities and personnel."

"Deep cover in Pakistan for two continuous years," Dayan continued, watching him carefully. "That's not routine intelligence work or simple information gathering. That's maintaining false identity under constant scrutiny and suspicion, collecting actionable intelligence without detection, making life-or-death decisions under pressure every single day, executing successful extraction when the mission concludes. Most deep cover operatives who fail that mission end up either dead or in prison being tortured for information. You made consistently good decisions under extraordinary pressure, or you wouldn't be here."

"I had excellent logistical and operational support from RAW," Karan deflected, uncomfortable being the focus. "Deep cover operations require extensive support infrastructure—secure communications, extraction planning, intelligence analysis, emergency protocols. Individual operatives don't succeed alone in a vacuum."

"But they fail alone," Dayan countered directly. "Headquarters can provide all the support infrastructure in the world, but the operative on the ground makes split-second decisions under pressure that ultimately determine mission success or failure. You made consistently good decisions, or you'd be dead."

"Where exactly are you going with this line of discussion, Minister?" Karan asked directly.

"I'm trying to understand what fundamentally drives you as a person," Dayan said. "Most defense contractors are businessmen seeking commercial profit and market share. You've built something far more complex and strategically significant—vertical integration across multiple critical industries, strategic positioning for coming geopolitical shifts, capabilities that serve national objectives well beyond simple commercial returns. That's not business in the normal sense. That's nation-building at the strategic level."

"India needed domestic defense capability," Karan said simply, his tone suggesting this should be obvious. "Someone had to build it. I had the technical understanding, the organizational capability, the necessary resources, and the opportunity. So I built it. Not complicated."

"You essentially appointed yourself to that national role," Dayan observed.

"I identified what needed to be done and had the capability to do it," Karan said, his voice carrying quiet conviction. "Not self-appointment—necessity. India either developed indigenous defense manufacturing capabilities or accepted permanent strategic dependence on foreign suppliers who could cut us off at any time for political reasons. I chose to develop it, and the government chose to support that development because it served their interests."

Dayan studied him intently for a long moment, his assessment clearly going beyond the aircraft being evaluated.

"Israel understands operating from necessity," Dayan said finally. "We've built an entire nation based on that foundation—doing whatever is necessary for survival regardless of whether it's conventional, whether it's comfortable, or whether other nations approve. Perhaps that's the fundamental reason this partnership works so well. We recognize in you something familiar. Someone who does what's genuinely necessary rather than what's easy or comfortable or politically convenient."

He stood, signaling the meeting's conclusion. "Tomorrow, flight testing begins at 0700 hours. Ran, you take the first evaluation flight. Cohen and Shimoni follow at the scheduled times. I want comprehensive reports on handling characteristics across the flight envelope, performance validation against specifications, and combat suitability assessment. If these aircraft are what India claims—and based on today's thorough inspection, I believe they are—we're acquiring something extremely valuable for Israel's security. But we verify everything through actual flight testing before making final determinations."

"Understood completely," Pekker said.

Day Two — 17 May 1973

The sun was just clearing the horizon when the Israeli pilots arrived at the flight line, the early morning air still cool but warming rapidly.

Ran Pekker wore an Indian flight suit—borrowed because his Israeli gear wasn't compatible with the S-27's systems—and carried his helmet under his arm. Behind him, Cohen and Shimoni were similarly equipped.

The twelve S-27 aircraft sat on the apron in two precise rows. Ground crews were conducting final pre-flight checks with practiced efficiency.

Colonel Rathore met Pekker at the aircraft designated for his evaluation flight.

"Good morning, Colonel. Ready to actually fly this aircraft?"

"As ready as I can possibly be without having flown it yet," Pekker said, studying the aircraft with obvious anticipation mixed with appropriate caution. "Beautiful aircraft from an aesthetic perspective. The lines are aggressive—clearly designed for performance first, not visual appeal, but beautiful in that functional engineering way."

"Let's walk through the complete cockpit layout in detail," Rathore said. "I know you reviewed the diagrams and documentation last night, but actually sitting in the seat and physically reaching for controls is fundamentally different than studying drawings."

They climbed the boarding ladder to the cockpit. Pekker settled carefully into the ejection seat, adjusting the harness straps, getting a physical feel for the workspace. His hands moved naturally to where controls should be positioned, verifying their locations matched his mental model.

"Primary flight instruments here," Rathore indicated systematically. "Airspeed indicator, altimeter, attitude indicator, heading indicator. Standard arrangement that should feel familiar from other fighters. Engine instruments here—RPM, exhaust gas temperature, fuel flow, oil pressure, hydraulic pressure. Weapons panel here. Radar display here. Electrical system panel here. Emergency systems here."

Pekker's hands moved over controls without activating them, physically building muscle memory of exact positions.

"Throttle response characteristics?" he asked.

"Responsive but not overly sensitive," Rathore explained. "Throttle movement translates to measurable thrust change within approximately two seconds—quick enough that you feel immediate response, smooth enough that you're not constantly fighting micro-corrections. Afterburner engagement is smooth and progressive—not the harsh sudden kick you get from some older engines. You'll feel the thrust increase definitely, but it's controlled and predictable."

"Flight control system—this uses digital fly-by-wire, correct?" Pekker asked.

"Yes, quadruple-redundant digital fly-by-wire with mechanical backup," Rathore confirmed. 

"I prefer fly-by-wire for modern fighters," Pekker said. "Better handling characteristics across the envelope, especially at high angles of attack where mechanical systems struggle."

They continued for twenty-five minutes—Pekker asking increasingly detailed questions, Rathore providing comprehensive answers based on his 300+ hours of experience in the aircraft.

Finally Pekker said: "I'm ready. Let's start engines and fly this aircraft."

Rathore climbed down from the cockpit, leaving Pekker alone with the machine.

On the ground, a small group had assembled to watch: Karan, Moshe Dayan, Air Marshal Pratap Singh, Dr. Raviv, Avi Weiss, and the other members of the Israeli evaluation team.

Pekker ran through the startup checklist with methodical discipline. Battery on. Hydraulic systems check—pressure building normally in all three independent systems. Flight controls—full stick and rudder movement, watching control surfaces respond correctly outside through the canopy.

Engine start sequence.

The starter motor engaged with a high-pitched mechanical whine. The engine began rotating, accelerating smoothly through the startup regime. Fuel flow initiated automatically at the correct point. Ignition. The exhaust gas temperature gauge rose rapidly as combustion established and stabilized. The mechanical whine transitioned to a deeper, more powerful roar as the engine accelerated through idle speed to stabilized running condition.

All engine instruments settled smoothly into their normal green operating ranges. No warning lights. No abnormal indications of any kind. Just smooth, steady, confidence-inspiring operation.

Pekker sat motionless for a moment in the now-vibrating cockpit, feeling the aircraft intimately through his hands on the controls and his body in the seat—the characteristic idle vibration transmitted through the airframe structure, the steady powerful turbine hum, the small purposeful movements of hydraulic systems automatically maintaining pressure and position.

It felt fundamentally right. Solid. Confidence-inspiring in that subtle way experienced pilots recognized.

He keyed the radio professionally. "Tower, test flight zero-one, ready for taxi."

"Test flight zero-one, cleared to taxi runway two-seven via taxiway alpha. Current winds two-six-zero at eight knots. Altimeter setting three-zero-one-two."

Pekker released brakes and advanced the throttle slightly. The S-27 rolled forward smoothly and responsively, reacting predictably to throttle inputs, steering easily with nose wheel steering and differential braking exactly as briefed.

He taxied deliberately to the runway, turned precisely into takeoff position, and ran through his final pre-takeoff checks with ingrained discipline.

Flight controls: full and completely free movement in all directions—stick full forward, full aft, full left, full right, full rudder deflections. All control surfaces outside responding correctly and smoothly.

Trim: properly set for takeoff configuration—slight nose-up trim to assist rotation.

Engine instruments: all parameters completely normal and stable.

Canopy: locked indication showing positive.

Ejection seat: armed and ready.

Transponder: on and squawking assigned code.

He keyed the radio. "Tower, test flight zero-one, ready for immediate takeoff."

"Test flight zero-one, you are cleared for takeoff runway two-seven. Current winds two-seven-zero at nine knots."

Pekker took one deliberate centering breath, a practiced ritual before committing. This was always the real moment of truth in any first flight—when you committed completely to trusting an unfamiliar aircraft with your life.

Then he smoothly but decisively advanced the throttle to military power—maximum thrust without afterburner engagement.

The S-27 accelerated down the runway with genuinely surprising authority. Strong acceleration pressing him firmly back into the seat, the runway centerline tracking rock-steady beneath the nose, the entire machine feeling powerful and controlled. Sixty knots. Eighty knots. One hundred knots. The acceleration was frankly impressive—noticeably better than the F-4 Phantom on a similar takeoff, and this was a single engine rather than two.

At exactly 140 knots indicated airspeed, he applied smooth back pressure to the stick.

The nose lifted immediately and smoothly, the aircraft responding precisely to his control input without hesitation or uncertainty. The main wheels stayed firmly on the runway for perhaps two more seconds while the wings developed sufficient lift.

Then the characteristic rumbling vibration stopped completely and the S-27 Pinaka was flying, climbing powerfully away from Gorakhpur into the clear morning sky.

Pekker raised the landing gear smoothly—clean retraction with positive indicator lights confirming proper stowage—and retracted flaps to clean configuration. He established a steady climb attitude at 300 knots indicated, letting the aircraft accelerate naturally while climbing.

Passing 5,000 feet altitude. Passing 10,000 feet. The aircraft climbed steadily and powerfully, the vertical speed indicator consistently showing over 8,000 feet per minute. That was genuinely extraordinary climb performance—better than anything he'd experienced in Israeli fighters.

"Very good climb rate," he transmitted, unable to keep slight surprise from his voice. "Genuinely impressive rate of climb."

On the ground, Moshe Dayan looked at Karan. "He sounds surprised by the performance."

"He sounds impressed," Karan corrected. "That's considerably better than mere surprise."

At 15,000 feet, Pekker leveled off smoothly and began systematic evaluation. This was the careful, methodical exploration phase where any good test pilot explored an aircraft's basic handling characteristics thoroughly before attempting anything aggressive or high-risk.

He initiated a gentle turn to the left, banking smoothly to 30 degrees. Bank angle increased predictably and controllably. No tendency whatsoever to over-bank or under-bank. Back pressure required to maintain altitude during the turn felt completely appropriate for the bank angle and airspeed. Perfectly coordinated flight with no adverse yaw requiring compensating rudder input.

Smooth roll reversal to the right, passing through wings-level. Identical response characteristics. Clean, predictable, exactly what he'd expect from a properly-designed modern fighter.

He varied the airspeed systematically: throttle back smoothly to 250 knots, then progressively forward to 400 knots. The aircraft remained completely stable across the entire speed range. No unexpected changes in handling characteristics, no surprising control force variations, no trim changes requiring constant correction.

Then something moderately more aggressive.

He pulled up smoothly into a climbing turn, loading the aircraft progressively to 3 G. Stick forces increased appropriately and predictably with the higher load factor—not too heavy, not too light, just right for good pilot feedback. The aircraft responded immediately and precisely. No buffet, no control degradation, no unpleasant surprises. Just clean, powerful acceleration upward.

Roll inverted at the top of the climb. Pull firmly through back to level flight, completing a smooth barrel roll. The maneuver was controlled, precise, exactly what he had commanded with stick inputs.

Pekker smiled inside his oxygen mask, his assessment already forming.

This was a real fighter. Not a prototype plagued with quirks and developmental problems. Not a design that looked impressive on paper but flew poorly in reality. A real, genuinely capable, properly-developed fighter aircraft that responded exactly as it should.

"Ground, test flight zero-one. Aircraft handling is excellent at moderate speeds and moderate G loading. Very impressive across the board. Proceeding to high-speed evaluation phase."

Pekker had climbed to 40,000 feet and was preparing for high-speed supersonic testing.

At this altitude, the air was extremely thin and bitterly cold, the sky above a deep blue fading toward black, the horizon dramatically curved and impossibly distant. Perfect conditions for supersonic flight testing.

He advanced the throttle progressively to military power and watched the airspeed indicator begin climbing steadily.

400 knots indicated. 450 knots. 500 knots indicated airspeed, which at this extreme altitude corresponded to significantly higher true airspeed. The Mach meter showed steady progression: Mach 0.85, 0.90, 0.95.

Approaching Mach 1—the sound barrier.

The acceleration through the transonic region—that notoriously difficult regime between subsonic and supersonic where shock waves form and dissipate dynamically—was remarkably smooth and controlled. No buffet. No unexpected control issues. No significant drag rise that slowed acceleration. The aircraft transitioned smoothly through Mach 1.0 as if it had been designed specifically and exclusively for that purpose.

Which it had been.

Mach 1.1. Mach 1.2. The acceleration continued smoothly even at military power, no afterburner engaged yet.

At Mach 1.3, Pekker deliberately engaged afterburner.

The afterburner lit with a smooth but distinctly powerful surge of additional thrust. He felt it clearly through the seat—not a harsh jarring jolt, but a definite controlled surge of raw power. The airspeed indicator began climbing noticeably faster.

Mach 1.5. Mach 1.7. Mach 1.9. Mach 2.0—twice the speed of sound.

The acceleration felt relentless and powerful. This was faster than he'd ever flown in any Mirage variant, approaching the absolute maximum speed he'd achieved in the much larger twin-engine F-4 Phantom.

And this incredible performance was from a single engine.

Mach 2.1.

He leveled off precisely at Mach 2.1 and stabilized the aircraft, cruising at 40,000 feet at over twice the speed of sound.

The aircraft was rock-solid stable. No vibration. No buffet. No control issues of any kind. Just smooth, incredibly fast, powerful supersonic flight. The cockpit environment was remarkably quiet except for the steady reassuring hum of systems and occasional radio transmissions.

He maintained the speed for three full minutes, monitoring all instruments with careful disciplined attention. Engine temperature perfectly stable. Fuel flow high but steady and predictable. All systems completely normal across the board.

He keyed the radio, genuinely unable to keep the excitement and amazement completely out of his voice despite his professional training. "Ground, test flight zero-one. Maximum speed achieved at Mach 2.1 exactly as documented in specifications. Aircraft performance is completely nominal at high speed. This is... this is genuinely incredible. I'm flying Mach 2.1 on a single engine. Do you fully understand what that means? This performance is revolutionary."

In the control tower, Dayan looked at Karan with an expression mixing shock and reassessment.

"He sounds absolutely shocked," Dayan observed.

"He should be shocked," Karan said matter-of-factly. "His Mirage III needs two engines to reach Mach 2.1 under ideal conditions. This aircraft achieves it easily on one engine, with thrust reserves remaining. That's not incremental improvement—that's revolutionary capability that changes tactical calculations."

Pekker had descended to 25,000 feet and was now conducting aggressive combat maneuvering evaluation—the kind of violent flying that definitively separated truly capable fighters from merely adequate ones, the kind of flying that determined who survived actual air combat and who didn't.

He rolled the aircraft inverted and pulled hard. 6 G load pressing him forcefully down into the seat, his G-suit inflating automatically to keep blood from pooling in his legs. The aircraft responded cleanly and precisely. No adverse yaw. No control coupling. No unpleasant surprises. Just pure responsive handling exactly as commanded.

He reversed the turn aggressively, rolling rapidly to the opposite direction and pulling again even harder. 7 G now, approaching the realistic limit of what he could physically sustain without losing consciousness. The control forces from the fly-by-wire system were perfectly calibrated—providing good feedback without being excessive. The aircraft went exactly where he commanded it to go without hesitation.

A split-S maneuver: roll inverted, pull through aggressively into a descending turn, deliberately trading altitude for speed and energy, recovering at much lower altitude with kinetic energy preserved.

The S-27 executed it flawlessly, the maneuver smooth, powerful, and precisely controlled.

A maximum-effort barrel roll with the aircraft rotating around its velocity vector while maintaining forward speed. A nearly vertical climb followed by a hammerhead turn, the aircraft hanging momentarily on pure engine thrust before pivoting sharply around. A scissors maneuver that reversed direction multiple times in rapid succession, simulating a desperate defensive engagement against a pursuing enemy fighter.

Every single maneuver was executed cleanly and precisely. The aircraft responded to his inputs without hesitation, without surprises, without the unpredictable dangerous quirks that made some fighters genuinely hazardous to fly aggressively in combat conditions.

He attempted a maximum-performance sustained turn, pulling as hard as he could physically sustain—approaching 8 G. The turn rate was genuinely extraordinary, the aircraft pivoting sharply while impressively maintaining energy rather than bleeding speed. He could feel both his physical limits as a human pilot and the aircraft's aerodynamic limits, but the aircraft provided clear feedback and clear warning well before reaching actually dangerous conditions.

After thirty sustained minutes of aggressive high-G maneuvering—hard turns, vertical climbs, high-speed rolls, every aggressive maneuver he could conceive—Pekker leveled out and took stock of the situation.

He was breathing very hard, sweating profusely inside his flight suit despite the environmental control system. High-G combat maneuvering was physically demanding and exhausting in ways that normal flying simply never was. But the aircraft had performed absolutely perfectly throughout. Better than perfectly—it had exceeded his expectations.

He keyed the radio, his voice clearly showing physical exertion but also unmistakable professional enthusiasm. "Ground, test flight zero-one. Combat maneuvering evaluation phase complete. This aircraft... this aircraft is genuinely exceptional. Better handling characteristics than the Mirage by a substantial margin. Better energy retention than the F-4 Phantom. Turn rate is outstanding. Acceleration is phenomenal. If this represents what you've been manufacturing here, if this is what's available for export sales, then everyone—and I mean everyone—has been dramatically underestimating Indian aerospace capability."

"I'm returning to base now," he continued. "But I'm telling you explicitly right now, before I even land this aircraft: Israel should purchase every single one of these you're willing to sell us. This isn't qualified enthusiasm—this is an unambiguous procurement recommendation."

In the tower, there was a moment of genuinely stunned silence.

Then Moshe Dayan spoke quietly: "Did Colonel Pekker just make an explicit procurement recommendation while still flying the evaluation aircraft?"

"He absolutely did," Pratap Singh confirmed, also somewhat surprised.

"That's completely unprecedented," Dayan said, shaking his head. "Test pilots simply don't make procurement recommendations until after comprehensive evaluation over multiple flights and detailed written reports. They certainly never make them while still actively flying the test aircraft."

"He just flew Mach 2.2 on a single engine and then out-maneuvered every aircraft he's ever flown in actual combat," Karan said simply. "He knows exactly what he's seeing. He knows precisely what it means tactically and strategically. And he knows Israel desperately needs this capability. So he's making the recommendation immediately rather than waiting for bureaucratic processes."

\---

\*\*09:15 Hours — Landing\*\*

The S-27 entered the landing pattern, Pekker flying with the precision and care of someone who'd made literally thousands of landings but treating this first landing in a new type with entirely appropriate caution.

Final approach configuration. Gear down, three positive green lights. Flaps extended to landing position. Airspeed 225 knots, deliberately slightly above the documented approach speed because he was being conservatively careful.

The runway grew progressively larger in the windscreen. Pekker made small precise corrections with stick and throttle, maintaining exact glide slope and runway alignment. The aircraft was completely stable and predictable in approach configuration.

Over the runway threshold. Throttle smoothly back to idle. The runway surface beneath him. Slight progressive back pressure on the stick to flare properly.

The main wheels kissed the runway remarkably smoothly. Pekker deployed the drag chute, applied brakes progressively and carefully, and the S-27 decelerated steadily to safe taxi speed.

"Very nice landing," he transmitted. "Extremely nice."

He taxied back to the apron, shut down the engine properly, and sat in the cockpit for a long moment in the sudden profound silence after flight, processing everything he'd just experienced.

Then he climbed out deliberately, removing his helmet as his feet touched solid ground.

Karan, Dayan, and Rathore were waiting nearby.

Pekker walked toward them steadily, helmet under his arm, still mentally and physically processing what he'd just experienced.

"Well?" Dayan asked directly, though the answer was already obvious from the radio transmissions.

Pekker looked at his Defense Minister with absolute directness. "Minister Dayan, that aircraft is unambiguously the best fighter I have ever flown in my entire career. Better than the Mirage III. Substantially better than the F-4 Phantom. Better, quite frankly, than anything I genuinely thought Israel would ever have realistic access to without purchasing the absolute most advanced American fighters at premium prices."

He turned to face Karan directly. "You dramatically undersold the aircraft's capabilities. Your written specifications were genuinely conservative compared to actual flight performance. The acceleration is phenomenal—substantially better than documented. Climb rate is exceptional. Supersonic performance is outstanding. Combat maneuvering capability is extraordinary. This aircraft will absolutely dominate any Arab fighter it encounters in combat. It will provide Israeli pilots with decisive tactical advantages in air-to-air engagements."

"You're completely certain?" Dayan asked, though the answer was already evident.

"I'm absolutely certain without any qualification," Pekker said. "This aircraft can accomplish everything Israel needs it to accomplish operationally. And it can do it substantially better than any fighter we currently operate.

Dayan's entire posture shifted—visible tension that had been present since their arrival yesterday finally releasing completely.

"That's the strongest unqualified endorsement I've ever heard from you for any aircraft," Dayan said.

"That's because this is objectively the best aircraft I've ever evaluated," Pekker said simply, as if explaining something obvious. "Cohen and Shimoni will fly this afternoon and tomorrow, and they'll inevitably reach exactly the same conclusion I have. This represents game-changing capability for Israel's air force and national security."

He looked at Karan again with obvious respect. "How many of these can you realistically produce?"

"Current production capacity is approximately forty aircraft per year," Karan said. "We're actively expanding to eighty per year by 1975. For Israel's contracted order of forty-eight aircraft—we can deliver in four batches over six months exactly as specified in the contract. If Israel wants additional aircraft beyond the current contract, we can accommodate those orders within our expanded production capacity."

"Israel will definitely want more," Pekker said with absolute confidence. "When word of this aircraft's genuine capabilities reaches Tel Aviv, when Air Force leadership fully understands what we're actually acquiring, there will be immediate substantial pressure for additional purchases. This isn't just replacing aging aircraft—this is a fundamental capability upgrade that changes our tactical options and strategic calculations."

Karan allowed himself a measured smile. "Then we'll be completely ready to discuss additional sales whenever Israel is ready to seriously discuss additional purchases."

End of Chapter 117