Chapter 115: The Ship Killer
Location: Shergill Aerospace Missile Division, Hyderabad
Date: 18 April 1973 — 08:15 Hours
The ramjet sat in the assembly cradle like something that had been designed by someone who understood physics at a level that made aesthetics irrelevant.
It was not a beautiful object. Beautiful implied curves, symmetry, proportion. The Kaumodaki ramjet was a cylinder with an intake cone at the front, an exhaust nozzle at the back, and fuel lines running along the exterior in a pattern determined entirely by combustion efficiency and thermal management. It looked brutal and functional in the way that tools designed for a single purpose often did.
Karan stood at the observation gallery above the missile assembly floor, looking down at the first production unit being built.
Captain Ranbir Singh stood beside him — the weapons integration officer who had spent two years turning the Kaumodaki from a promising concept into a functional anti-ship missile, and who now looked at the assembly floor below with the particular attention of someone watching years of development work transition into manufacturing reality.
"First production unit," Singh said. "Assembly started Monday. Ramjet mated to the airframe yesterday. Today is guidance section integration."
Below them, six technicians worked around the missile. Not quickly — quickly was not how you assembled something that carried 178 kilograms of shaped charge explosive and flew at Mach 2.1. Carefully. Methodically. Following procedures that had been written, tested, revised, and finalised over eighteen months of prototype builds.
"How many units are we targeting for the first production run?" Karan asked.
"Forty-eight missiles," Singh said. "Enough to equip two squadrons with full combat load plus training and test allocation." He paused. "Navy requirement is eventually two hundred forty missiles — five missiles per aircraft for forty-eight S-22s. But we're starting with forty-eight to validate the production process and establish the supply chain."
Karan nodded. That was the correct approach. Build enough to prove the manufacturing system worked before committing to volume production.
The Kaumodaki Mk 2 anti-ship missile was a weapon designed specifically for carrier-based aviation. An aircraft carrier without a means of threatening enemy ships at long range was a platform that could be neutralized by surface combatants before it got close enough to act. INS Vikrant needed a missile that could be launched from an S-22 Makara at a distance that kept the aircraft outside the enemy ship's air defense envelope.
The Kaumodaki's specifications reflected this requirement:
Range: 187 kilometers — allowing the launching aircraft to stay well outside typical naval SAM range
Speed: Mach 2.1 terminal phase — covering the final 15-20 kilometers from seeker acquisition to impact in approximately 30 seconds, faster than most ship defense systems could respond
Warhead: 178 kilograms shaped charge explosive — designed to penetrate below the waterline and detonate inside the hull
Guidance: Inertial navigation during cruise phase, active radar seeker for terminal homing
Seeker acquisition range: 15-17 kilometers — the point where the missile's onboard radar detected the target and switched from inertial to terminal guidance
The missile had been prototyped during the 1971 war as a deterrent. The production version — Mk 2 — incorporated eighteen months of refinement.
"Walk me through the assembly process," Karan said.
Singh pulled out a folder with the production flow diagram.
"We start with three major subassemblies manufactured separately: the ramjet propulsion unit from the propulsion facility in Pune, the guidance section from the electronics division here in Hyderabad, and the warhead section from the Nagpur explosives facility."
He traced the flow on the diagram.
"The ramjet arrives as a complete unit — inlet, combustion chamber, fuel injection system, nozzle. We don't assemble ramjets on this floor because they require specialized test equipment. Pune builds and tests them, then ships them here."
"Test criteria at Pune?" Karan asked.
"Static thrust test at full fuel flow," Singh said. "Ramjet has to demonstrate rated thrust for sixty seconds continuous burn. Also thermal cycling — three heat-up and cool-down cycles to verify structural integrity. Only ramjets that pass both tests get shipped."
"Failure rate?"
"Currently about twelve percent," Singh said. "Mostly combustion instability issues — the fuel injection pattern isn't perfect yet. We're working on nozzle design improvements."
"Acceptable for initial production?" Karan asked.
"Acceptable but not ideal," Singh said. "We're targeting eight percent failure rate by mid-year. That's comparable to international ramjet production."
He continued with the assembly flow.
"The guidance section is assembled here in the Hyderabad electronics facility. Inertial navigation system, radar seeker, flight computer, control actuation. This is the most complex subassembly — hundreds of components, mostly from ISMC."
The guidance section was the brain of the missile. The inertial navigation system — INS — used gyroscopes and accelerometers to track the missile's position and velocity from launch. It guided the missile toward the target's predicted location based on the coordinates loaded before launch. At 15-17 kilometers from the target, the active radar seeker activated — sending out radar pulses and detecting reflections from ships in a roughly 3-kilometer diameter search basket. Once the seeker locked onto a target, the missile switched to terminal guidance: flying directly toward the radar return, adjusting course based on real-time seeker data.
The INS had to be accurate enough that after flying 187 kilometers, the missile arrived within the seeker's search basket — currently about 400 meters circular error probable, well within the 3-kilometer basket diameter. The seeker had to distinguish between actual ships and false returns from waves, weather, or chaff. The flight computer had to process all this data and send commands to the control actuators fifty times per second.
"And the warhead section?" Karan asked.
"Arrives from Nagpur as a sealed unit," Singh said. "We don't handle the explosives directly on this floor. Nagpur does the explosive forming, fuzing integration, and sealing. We just mate it to the missile body."
"That's safer," Karan observed.
"Much safer," Singh agreed. "One hundred seventy-eight kilograms of shaped charge is not something you want assembled in a facility that's also doing electronics integration."
He pointed to the assembly floor below.
"Final assembly sequence: Start with the missile airframe — aluminum structure, control surfaces, fins. Mount the ramjet at the rear. Integrate the guidance section at the front. Install fuel tanks in the center body. Route electrical connections between guidance and ramjet. Finally, mate the warhead section between guidance and fuel tanks. Then comes checkout: electrical continuity, control surface movement, INS calibration, seeker function test."
"How long does final assembly take?" Karan asked.
"Currently about sixteen hours per missile," Singh said. "That includes all the checking and testing. We're targeting twelve hours once the workforce has more experience."
"Production rate?"
"At twelve hours per missile with two assembly stations running parallel shifts, we can produce approximately twelve missiles per month. Forty-eight missiles in four months."
Karan did the math. "That puts first squadron full equipment in August. Second squadron in December."
"Correct," Singh said.
Below them, a technician was carefully routing an electrical harness from the guidance section to the ramjet control interface. Another technician verified each connection against a wiring diagram, calling out pin numbers while the first technician confirmed.
Slow. Careful. No shortcuts.
That was how you built weapons that had to work the first time, every time.
10:30 Hours — Guidance Section Testing
The guidance section test facility was a separate building — windowless, temperature-controlled, electromagnetically shielded to prevent interference during seeker testing.
Karan and Singh entered through an airlock that maintained the clean environment inside.
Three guidance sections sat on test benches, technicians working at each station.
At the first bench, a young engineer named Suresh Iyer was running an INS calibration. The guidance section sat in a precision gimbal mount that could rotate it through exact angles while the INS measured its own orientation. The test verified that the gyroscopes and accelerometers were accurately detecting position changes.
"How's the calibration looking?" Singh asked.
Iyer glanced up. "Within spec. Drift rate is point-two degrees per hour, which is acceptable for the one-hundred-eighty-seven-kilometer flight profile."
INS drift was the accumulation of small errors over time. Gyroscopes weren't perfect — they had tiny mechanical imperfections that caused them to gradually lose accuracy. Over a short flight of a few minutes, this drift was negligible. But the Kaumodaki flew for several minutes over 187 kilometers, and during that time the INS had to maintain accurate enough navigation that the missile arrived within the seeker's search basket.
A drift rate of 0.2 degrees per hour meant the INS position error accumulated at about 0.3 meters per kilometer of flight. Over 187 kilometers, that was roughly 56 meters of position error — well within the 400-meter circular error probable specification.
At the second bench, a seeker was being tested in an anechoic chamber — a room whose walls absorbed radar reflections, creating a controlled environment for radar testing.
The seeker sat on a rotating mount. At the far end of the chamber, a target simulator generated radar reflections that mimicked a ship's radar cross-section.
The technician running the test — a woman named Anjali Deshmukh — was cycling through different target ranges and angles, verifying the seeker could acquire and track targets under various conditions.
"Seeker performance?" Singh asked.
"Acquisition at sixteen kilometers," Deshmukh said, reading from her instruments. "Track hold is solid down to one kilometer. False alarm rate is point-three percent — three false detections per thousand scans."
"That's acceptable," Singh said. "Anything concerning?"
"The seeker heating problem is still present," Deshmukh said. "At Mach two-point-one terminal speed, the seeker radome heats significantly from air friction. At temperatures above one hundred twenty Celsius, the seeker's detection range drops from seventeen kilometers to fourteen kilometers."
Karan frowned slightly. "That was identified in the prototype testing."
"It was," Singh confirmed. "The Mk 3 development program addresses it with an improved radome design and active cooling. For now, the Mk 2 has reduced range at high speed, which we accommodate by planning terminal approach profiles that keep the missile slightly below Mach two-point-one until the last few kilometers."
"Workable but not ideal," Karan said.
"Correct," Singh said.
14:00 Hours — Production Quality Meeting
The conference room held twelve people: Singh, Karan, the production manager from the Pune ramjet facility (via telephone), the warhead section lead from Nagpur (also via telephone), three quality control engineers, and several assembly supervisors.
The purpose was straightforward: first production unit was nearly complete, and before they ramped to volume production, every issue needed to be identified and resolved.
"Let's start with the ramjet," Karan said.
The voice from Pune — R. Venkataraman, the propulsion facility manager — came through the speaker clearly.
"Ramjet production has stabilized. First twenty units showed a twelve percent failure rate during thrust testing, primarily combustion instability. We've identified the root cause: fuel injector nozzles are not manufactured to consistent dimensions. We've implemented tighter machining tolerances and inspection. Latest batch of six ramjets: one hundred percent pass rate."
"One hundred percent on six units isn't statistically significant," one of the quality engineers pointed out.
"Agreed," Venkataraman said. "But it's trending correctly. I'm confident we'll hit eight percent failure rate by June."
"What's the cost impact of the tighter tolerances?" Karan asked.
"Approximately eight thousand rupees per ramjet," Venkataraman said. "Increased machining time and higher scrap rate on nozzles that don't meet spec. But that's cheaper than building complete missiles with faulty ramjets."
"Approved," Karan said. "Next: guidance section."
Singh took this one.
"Guidance section assembly is proceeding smoothly. The ISMC chips are reliable — we've had zero semiconductor failures in prototype testing. The seeker acquisition performance meets specification. The INS drift rate is acceptable."
"But?" Karan prompted, because there was always a but.
"But," Singh continued, "we have three concerns. First: the seeker heating issue at Mach two-point-one. Second: the INS accuracy degrades if the missile experiences higher than expected acceleration during launch or maneuvering. Third: we're seeing occasional communication failures between the flight computer and the ramjet control interface — about two percent occurrence rate."
"Address them in order," Karan said.
"Seeker heating is being resolved in Mk 3 development. Mk 2 will fly with operational workarounds."
"INS accuracy under high acceleration is a calibration issue. We're refining the calibration procedure to account for carrier launch conditions — catapult acceleration followed by immediate maneuvering. New calibration procedure will be ready next month."
"Communication failures are intermittent and we're still investigating. Could be electrical connector quality, could be electromagnetic interference from the ramjet ignition. We're running isolation tests this week."
"Timeline to resolution?" Karan asked.
"Two weeks for diagnosis, one week for fix implementation," Singh said. "Three weeks total."
"That delays full production ramp," the production manager noted.
"It prevents building forty-eight missiles with a two percent failure rate," Karan said. "Take the three weeks. Fix it properly."
No one argued.
"Warhead section," Karan said.
The voice from Nagpur — Dr. Ashok Mehta, explosives facility director — was characteristically concise.
"Warhead production is nominal. Shaped charge forming is consistent. Fuzing integration has zero defects across eighteen units. Sealing and environmental protection meet spec. No issues."
"Explosive safety protocols?" Karan asked.
"Full compliance," Mehta said. "Maximum of four warheads in assembly at any time. Separation distance between assembly stations is fifty meters. Personnel exposure time is limited. We've had zero incidents."
"Good," Karan said. "Keep it that way."
16:00 Hours — Test Launch Observation
The test range was two hundred kilometers from Hyderabad, in a remote area of Andhra Pradesh where the government had leased land for weapons testing.
Karan and Singh arrived by helicopter at three-thirty.
The test launch was scheduled for four PM.
At the launch pad, the first production Kaumodaki missile sat on a ground-based test launcher — a steel frame that simulated an aircraft's wing pylon. The missile had been transported here in a sealed environmental container, assembled on-site, fueled, and armed with a live warhead for this test.
This was a full-system test: the missile would launch from the test stand, accelerate under ramjet power, fly a programmed course of 160 kilometers to a target area, acquire a target ship (a decommissioned fishing vessel positioned in a small bay), and complete a full terminal attack profile.
Unlike prototype testing where some elements were simulated, this was as close to operational conditions as possible without actually launching from an aircraft.
Captain Subramaniam from the Navy was present, along with Commander Pillai and two other naval officers. They stood in the observation bunker — a concrete structure eight hundred meters from the launch pad, with thick glass observation windows.
"First production unit full test," Subramaniam said to Karan. "If this works as designed, the Navy will accept delivery of the production batch."
"It will work," Karan said calmly.
Subramaniam smiled slightly. "Confidence is good. Results are better."
The countdown began at T-minus two minutes.
Technicians cleared the launch area. Final electrical connections verified. Ramjet pre-ignition checks complete.
"T-minus one minute," the range controller announced over speakers.
Karan watched the missile. In sixty seconds, everything they'd built — the ramjet, the guidance, the warhead, the years of development — would either work or fail spectacularly.
"T-minus thirty seconds."
Singh stood beside him, hands behind his back, face neutral. But Karan could see the tension in his shoulders.
"T-minus ten... nine... eight..."
The count continued.
"...three... two... one... ignition."
The ramjet lit.
For half a second, there was just flame at the nozzle — orange-white exhaust venting into the open air. Then the missile moved.
Not slowly. The ramjet reached full thrust almost immediately, and the Kaumodaki accelerated off the launcher with violent speed.
Karan felt the pressure wave hit the observation bunker a moment later — a physical thump in his chest from the exhaust shock.
The missile climbed steeply, trailing exhaust, accelerating rapidly.
Within five seconds it had cleared the launch area.
Within ten seconds it was already a kilometer away, pitching over to level flight.
Within twenty seconds it was a distant bright point, visible only by its exhaust trail.
"Telemetry receiving," the range controller said. "Missile is on programmed course. Speed accelerating through Mach one-point-five."
The exhaust trail stretched across the sky — a white line arrow-straight, pointing northeast toward the target area.
"Ramjet performance nominal," the controller continued. "Speed Mach one-point-nine. Altitude four hundred meters. INS navigation tracking correctly."
Time passed. The missile flew.
Three minutes into flight: "Missile approaching terminal phase. Speed Mach two-point-one. Range to target forty kilometers."
The observers couldn't see the missile anymore — it was too far away, too fast, just a data feed on the controller's instruments.
"Seeker activation... now. Seeker has acquired target. Missile switching to terminal guidance."
Karan's attention sharpened. This was the critical moment — when the missile's radar seeker found the target ship and took over guidance from the INS.
"Target lock confirmed. Missile tracking target. Terminal approach initiated."
Twenty seconds of silence.
Then: "Missile impact on target. Warhead detonation confirmed."
In the observation bunker, someone let out a breath they'd been holding.
Subramaniam turned to Karan. "I want to see the target assessment."
17:30 Hours — Target Site
The helicopter flew over the bay where the target ship had been positioned.
What had been a seventy-foot fishing vessel was now broken in two. The missile had struck midships, slightly below the waterline as designed. The shaped charge warhead had penetrated the hull and detonated inside, breaking the keel and ripping the vessel apart.
The aft section was already underwater. The forward section floated at an angle, sinking slowly.
Subramaniam looked down at the wreckage from the helicopter's open door.
"One hit, one kill," he said. His voice carried no emotion, just professional assessment. "Against a ship without active defenses, the Kaumodaki performs exactly as specified."
He turned to Karan.
"How many production missiles can you deliver by August?"
"Forty-eight," Karan said. "First squadron full equipment."
"And the S-22s to carry them?"
"First six aircraft deliver in December. Full squadron strength of twelve aircraft by March next year."
Subramaniam nodded slowly. "Then by March 1974, the Navy will have a carrier-capable strike platform with a credible anti-ship capability." He paused. "For the first time since Independence, INS Vikrant will be able to threaten enemy surface combatants at standoff range."
"That's the capability we built," Karan said quietly.
"Yes," Subramaniam said. "You did."
The helicopter turned back toward Hyderabad.
Below them, the target ship continued its slow descent into the bay, broken by a weapon that had flown true.
That evening — 20:00 Hours
Shergill Residence, Hyderabad
Karan sat in the study of the Hyderabad residence, reviewing the day's test data.
The missile had performed within specification on every measurable parameter:
Launch acceleration: nominal Ramjet ignition and thrust: nominal Flight profile accuracy: within 50 meters of programmed course Terminal speed: Mach 2.1 as designed Seeker acquisition: 16.2 kilometers range Time from seeker acquisition to impact: 32 seconds Warhead penetration and detonation: successful
One hundred percent success on first production unit full test.
That was rare in weapons development. Usually first tests revealed problems that required fixes. This test had validated that two years of prototype development had genuinely worked through the issues.
The phone rang.
He picked it up. "Karan Shergill."
"This is Sam Manekshaw."
Karan sat up slightly. The Chief of Army Staff calling directly was unusual.
"Good evening, sir."
"I heard about today's test from Subramaniam," Manekshaw said. "He called me from the range. He was impressed, and Subramaniam doesn't impress easily."
"The missile performed to specification," Karan said.
"More than that," Manekshaw said. "You've given the Navy a weapon that changes their capability fundamentally. A carrier that can strike ships at two hundred kilometers is a different kind of platform than a carrier that has to close to fifty kilometers."
He paused.
"I'm calling because the Army is interested in a land-based variant. Same missile, launched from trucks instead of aircraft. For coastal defense."
Karan considered this. "The Kaumodaki is designed for aircraft launch. Adapting it for ground launch would require redesigning the boost phase — you'd need a solid rocket booster to get the missile to ramjet ignition speed, since you don't have an aircraft's forward velocity."
"Can it be done?" Manekshaw asked.
"It can be done," Karan said. "But it's not a small modification. It's a year of development work minimum."
"Then start the development work," Manekshaw said. "The Navy isn't the only service that needs to threaten ships at long range. The Army needs coastal defense missiles, particularly for the Andaman and Nicobar Islands."
"I'll begin preliminary design," Karan said.
"Good," Manekshaw said. "One more thing. The rifle production in Amethi — I visited last week. The weapons are exactly what we discussed. Quality is high. Your production manager, Mehta, knows what he's doing."
"I'm glad they meet requirements," Karan said.
"They exceed requirements," Manekshaw said. "Which is better. When you build weapons for the Army, exceed requirements. We remember who does."
He hung up.
Karan set the phone down and sat back in his chair.
Two years ago, the Kaumodaki had been a concept: an anti-ship missile for carrier aviation that didn't exist because India had never built one.
Today, it existed. It worked. The Navy was buying it. The Army wanted a variant.
From concept to operational weapon in two years.
That timeline was faster than most countries achieved. It was possible because the entire supply chain existed: ISMC produced the guidance electronics, the ramjet facility in Pune built the propulsion, the explosives facility in Nagpur manufactured the warhead, the missile assembly line in Hyderabad integrated everything.
Vertical integration.
The same principle that made semiconductors possible, made steel production efficient, made aircraft manufacturing viable.
Control the supply chain. Own the critical technologies. Build the complete system.
The Kaumodaki was one result.
There would be others.
End of Chapter 115