Chapter 140: The Weight of Water
Shergill Shipyard, Visakhapatnam28 December 1974 — 08:00 Hours
The Bay of Bengal on a December morning had the colour of old pewter — not storm-grey, not the brilliant blue of the tourist brochures, but the honest working grey of a sea that had been doing something complicated for a very long time and saw no reason to apologise for it. The Visakhapatnam harbour curved away from the shipyard's main gate in both directions, a crescent of sheltered water that had been serving its function since the British found it useful and had continued serving it since independence with the reliable indifference of geography.
Karan had been in the yard since six.
He walked the fabrication halls before the first shift arrived — the specific habit of a man who had learned that the truest picture of any facility came in the hour before it was performing for anyone. The halls smelled of cutting oil and welded metal and something indefinably industrial that had no name but was recognisable in every serious manufacturing building he had ever entered. Six dry docks, four wet berths, eleven slipways of varying sizes, two covered fabrication halls, a steel processing plant, a pipe shop that could handle twelve thousand tonnes of plate per year.
He stopped at Slipway 7 for a long time.
Slipway 7 was the largest — recently extended to three hundred and ten metres, broad enough to accommodate a ship of one hundred thousand tonnes if the engineering case ever required it. It was currently empty. Most of the yard was occupied with commercial work: two coastal freighters, a bulk carrier on Slipway 3, two dredgers in refit. All of it the bread-and-butter that kept Aditya's accounts in a condition Aditya could live with.
But the slipways Karan was thinking about this morning were empty.
The Navy was due at eight.
It was seven fifty-nine when Vishwakarma appeared at his shoulder, producing the slightly materialised quality that Vishwakarma had always had — as if he had been present for the previous five minutes but had only decided to announce himself now.
"They've been in the car park since seven forty-five," Vishwakarma said.
"I know," Karan said.
"They've been sitting in the vehicles for fourteen minutes."
"Naval officers arrive exactly the right amount before the scheduled time," Karan said. "Never a minute more. It would be eccentric."
"Should we have scheduled for eight-fifteen?"
"Then they'd have been in the car park at eight-oh-one," Karan said. "The differential is a constant of nature."
Vishwakarma considered this with the expression of a man who had been working for Karan for three years and had developed a professional category for observations that were simultaneously accurate and useless.
Below in the car park, three vehicles had disgorged fourteen naval officers with the geometric precision of a service that had been doing drill for generations and couldn't entirely stop even in car parks. Two officers were pointing at Slipway 7. A third had a notebook and appeared to be writing in it.
Admiral S.N. Kohli stood at the front, looking at the yard with the expression of a man conducting an assessment rather than a visit. He was sixty-one, compact, with the specific quality of someone who had spent his career on ships and had developed, from that career, a relationship with the physical world that was unusually precise. He stood with his feet at exactly shoulder width — the habitual stance of a man who had learned to stand on moving surfaces.
"Shall we go down?" Vishwakarma asked.
"Yes," Karan said. "Let's not make them stand in the car park any longer. They've been very restrained about it."
Admiral Kohli's handshake communicated professional courtesy and absolutely nothing else, which was exactly how senior officers shook hands with people whose facilities they were assessing.
"Mr. Shergill," he said.
"Admiral. Welcome to Vizag." Karan paused. "Though I understand you were born here."
"Seventeen years of my career was here," Kohli said. He looked around the entrance lobby — the building's exterior was striped concrete that someone in 1963 had believed was modern, and they had been wrong. "The old yard looked different."
"The old yard was falling apart," Karan said pleasantly.
"Yes," Kohli said. "It was."
Introductions followed. Vice Admiral V.A. Kamath, Flag Officer Eastern Naval Command — a large, deliberate man who communicated that he was listening by being very still. Rear Admiral Mihir Roy, Director of Naval Plans — the look of a man who had been thinking about the Indian Navy's equipment situation for so long that the thinking had become structural. Rear Admiral S.H. Sarma, Director of Naval Construction — who had already been looking at the photos on the lobby wall with the focused attention of a naval architect reading technical documentation. Commodore P.K. Chatterjee, Director of Weapons and Equipment. Captain Ranjit Bhatia, Naval Plans, who was already writing things down and would continue writing things down for the next eight hours with the dedication of a man who believed that the written record was more reliable than human memory, which, in his experience, it was.
Then six more officers whose function was to provide technical depth and who arranged themselves in the rough order in which that depth would be required.
They went upstairs.
The conference room had been organised by Vishwakarma with the clean geometry of someone who had set up many meetings and knew that the physical organisation of a room communicated something about the minds using it. Round table, equal chairs on both sides. The two sets of blueprints were on a separate side table — not on the main table, because putting the blueprints where everyone could see them before sitting down implied that the blueprints were the point of the meeting, whereas the meeting was the point and the blueprints were what the meeting was building toward.
Tea had been provided. This was important. Naval officers expected tea.
Captain Bhatia opened his notebook and positioned his pen.
Admiral Kohli sat, poured his tea, and said: "Before we begin formally."
"Yes," Karan said.
"I want to ask you something that has been discussed at Naval Headquarters for the better part of a year," Kohli said.
"Please."
"In 1971, your company built the S-27 Pinaka. The Air Force had not asked for it. You built it, demonstrated it, and the Air Force bought it."
"Yes," Karan said.
"In 1972, you delivered the Arjun tank prototype to the Army. The Army had not issued a requirement for it. You built it, showed it, and there is now a procurement discussion in progress."
"Yes," Karan said.
"Rather more than that," Kohli said, "but we will not dispute the specific boundary." He paused. He was enjoying this slightly. Not maliciously — the way a man who has thought about a question for a long time enjoys finally asking it to the right person. "Air Force. Army. Small arms. Mr. Shergill, your company has produced defence items for every branch of the Indian armed forces except one."
The room waited.
"We also gave the Navy the S-22 Makara," Karan said.
Kohli looked at him. "You gave us a naval fighter aircraft."
"Yes."
"Which the Navy then had to reorganise its carrier air wing around."
"The Makara is an excellent aircraft," Karan said, with the specific quality of a man who knows he has caused an organisational headache and has decided the best approach is equanimity.
"The Makara is a magnificent aircraft," Kohli said. "It is also an aircraft that arrived before the Navy had a plan for it, the pilot training programme for it, the maintenance infrastructure for it, or the weapons integration protocols for it." He paused. "We spent eight months catching up to something you delivered in four."
"We could have delivered it slower," Karan said.
"No," Kohli said. "No, that would have been worse. If you had delivered it slower, someone would have asked why it was taking so long." He waved his hand in the gesture of a man dismissing a line of reasoning that goes nowhere useful. "The point is: aircraft, tank, rifle, naval fighter. But no ships. The Navy would like to know why."
Roy, across the table, had the quality of a man who had been carrying this question in the form of a professional grievance for a considerable period and was now watching it be addressed in a venue where it had a chance of producing a useful answer.
Karan looked at the Admiral. He had been preparing this answer since 1972, and like all answers that have been prepared for a long time, it had the clarity of something that had been refined to its essential shape.
"Because a ship is not a tank," he said.
The room looked at him. Captain Bhatia's pen was poised.
"I'm aware," Kohli said, with the specific dryness of a man who has commanded warships and does not require this information.
"I know you are," Karan said. "But the distinction matters for the answer, so I should say it before I give the answer." He stood — not for theatre, just because the answer was easier standing up. "The Arjun prototype cost twelve crore rupees to build. That's the complete cost — engine, armour, fire control, the testing programme. It's a significant amount. But it's an amount that Shergill Industries could commit on our own initiative without a government contract, without a grant, without asking permission. We assumed the risk that the Army might not buy it. That risk was bounded."
He looked at Kohli directly.
"The S-27 cost forty crore rupees for the prototype programme. That required us to commit essentially all of our aerospace division's reserve capital for fourteen months before there was a contract. We ran that risk because the programme was eighteen months, the risk was bounded, and one aircraft is buildable at one company's expense."
He paused.
"A frigate costs thirty-five to fifty crore rupees. Not the prototype. The ship. The ship is the prototype. You cannot build half a warship to see if the design works — the first ship of any class is simultaneously the prototype and the production unit, and it takes three to four years from keel-laying to delivery. During those years, the yard's capital is committed, the steel is purchased, the workers are employed, the systems are installed. If the government ultimately does not proceed, or reduces the order, or changes the specification at year two — the company's exposure is not twelve crore that it cannot recover. It is the entire programme cost that it cannot recover."
Rear Admiral Roy said: "The risk is not bounded."
"The risk is not bounded," Karan confirmed. "A tank prototype goes wrong, I have a very expensive piece of armour sitting in the yard. A ship prototype goes wrong—" He spread his hands. "I have a floating object I cannot sell, cannot reconfigure, cannot do anything with, and the company has spent three years building it."
He looked around the room.
"The initiative model that worked for the Air Force and the Army does not work for naval construction. The economics are different. The timelines are different. The capital exposure is categorically different. The reason the Navy has not received ships from Shergill Industries is not that we lack interest in the Navy. It is that naval construction requires a different relationship between the manufacturer and the government — one where the government commits capital and programme intent before the keel is laid, rather than after the prototype lands on their doorstep."
He sat.
"We have been interested in the Navy's requirements since 1972," he said. "We have been building toward this meeting since 1972. We are here now, with designs ready. But we need a partner, not a customer. And partners have conversations before the work begins, not after."
The room was quiet for a moment.
Roy looked at Kohli. Kohli looked at Karan.
"So your position," Kohli said, "is that we failed to have the correct conversation at the correct time."
"My position," Karan said, "is that the conversation is happening now, and we should use it well."
Kamath, who had been still and listening with the contained attention of a large man who processed everything and said little, said: "The S-22 Makara. When you delivered it without being asked."
"Yes," Karan said.
"Did you think about the organisational disruption it would cause?"
A pause.
"Yes," Karan said.
"And you delivered it anyway."
"The aircraft was ready," Karan said. "The Navy needed it. I decided that the organisational disruption of receiving a good aircraft was preferable to the operational cost of not having it."
Kamath looked at him for a long moment. "That," he said, "is a very aeronautical way to think about naval operations."
"I'm learning," Karan said.
"Are you?" Kamath said. And there was something in it — not hostile, almost amused — the expression of a large man deciding whether this twenty-four-year-old was as confident as he appeared or whether the confidence was backed by something.
"Admiral Kohli," Karan said, "the blueprints are on the table behind you. Shall we begin?"
The first blueprint was the Type 28 frigate.
Sarma had been looking at the rolled tubes on the side table with the controlled longing of a naval architect presented with designs he has not seen before, and when Karan said "Rear Admiral Sarma, please" and gestured at the table, Sarma moved to it with a speed that was only slightly faster than professional decorum required.
The general arrangement drawing went down on the table. Sarma looked at it for a long time before saying anything. The others gathered — Kohli and Roy and Chatterjee and the technical officers behind them, arranged in the loose formation of people who are all trying to see the same drawing without admitting they are crowding.
"Length overall: 124 metres," Karan said. "Beam: 13.8 metres. Full load displacement: 3,400 tonnes. Designed endurance: 4,200 nautical miles at 18 knots."
"Maximum speed?" Sarma said.
"28 knots on diesels and gas turbine combined. 20 knots on diesels alone."
Sarma was looking at the hull form. He had the expression of a man reading something in a language he knew well and was checking for errors — the professional attention that was so much more useful than enthusiasm.
"The bow sections," he said. "Moderately fine. Not as fine as a destroyer."
"It's a frigate," Karan said. "Not a destroyer. It doesn't need destroyer performance. It needs to maintain 18 knots in sea state four for four thousand miles. We optimised for sustained endurance rather than sprint speed."
"The freeboard forward," Sarma said. He was measuring with his eyes against the drawing's scale. "That's generous."
"The Bay of Bengal in monsoon season," Karan said. "A ship that's wet forward cannot operate its forward gun effectively. We gave it height forward at the cost of some visual elegance."
"It looks like a ship that means business," Roy said. He had come around to Sarma's side of the table.
"Thank you," Karan said.
"That was not entirely a compliment," Roy said. "I meant it looked slightly aggressive for a frigate."
"I'll take it as a compliment anyway."
Admiral Kohli was looking at the weapons layout drawing, which showed the ship in plan view with the equipment positions marked. He had the expression of a man identifying what was present and what was absent.
"Armament," Kohli said.
"Forward: one 114mm dual-purpose gun," Karan said. "Based on the Vickers Mk 6 design. We are in discussions with Vickers about a licence agreement, though the preference would be a domestic equivalent at 114mm or similar calibre. The gun can engage air targets, surface targets, and provide naval gunfire support."
"Rate of fire?" Chatterjee asked.
"20 rounds per minute. Slower than some, but reliable and maintainable. We are not trying to be the fastest gun in anyone's navy. We are trying to be a gun that works when it is needed."
Chatterjee made a note.
"Missiles," Karan said. "Here is where I want to be honest rather than impressive." He moved to indicate the drawing's mid-section. "The Type 28 carries a twin-launcher system for close air defence — a system in the class of the British Seacat, a short-range surface-to-air missile with four-kilometre range. This is not an impressive capability on paper."
"No," Kohli said.
"It is an honest one," Karan said. "The Seacat equivalent is something we can make work with current Indian electronics and rocket technology. The Astra air-to-air missile, which you have seen over the skies of the Sinai, has a different seeker and booster configuration designed for air launch. A surface-launch version for ship use is in development — but it is in development, it is not in service, and I will not put a weapon system on a ship design that is not in service."
Roy looked at him. "You are telling us the missile is modest."
"I am telling you the missile is real," Karan said. "In five years — if the surface-launch Astra development programme progresses — this ship's launcher can be upgraded to carry that weapon. The mount foundations are specified to accommodate the heavier weapon. But on delivery in 1977, this ship carries a Seacat-class weapon that exists and has been proven."
Kohli looked at the drawing. "Most people presenting new ship designs to the Navy tell us their capabilities are better than they actually are."
"I am aware of this pattern," Karan said.
"You are apparently not following it."
"I am trying to give you a ship you can actually operate rather than a specification document you can admire."
There was a brief silence in which Captain Bhatia wrote something that appeared to be a verbatim transcription of this exchange.
"Anti-submarine weapons," Sarma said, returning to the drawing.
"Two triple torpedo tubes — one per side, amidships. Standard 533mm wire-guided torpedoes." Karan moved to indicate the bow area. "Hull-mounted sonar with a transducer array of 3.8 metres — larger than the Leander-class fitting. The detection range in the mixed-layer conditions of the Bay of Bengal is approximately eight to ten kilometres against a conventional submarine. We also have provision for a variable depth sonar, which would extend detection range below the thermal layer — but the VDS is a follow-on addition, not in the initial fit."
"Why not in the initial fit?" Roy asked.
"Because the variable depth sonar requires winch and handling equipment that adds topweight to the stern," Karan said. "The stability margins of the Type 28 at full load are comfortable but not extravagant. Adding the VDS in the initial fit means either reducing other weight or accepting reduced stability margins. We reduced other weight by making it a planned upgrade rather than a first-of-class fit."
Sarma had been looking at the midship section drawing. "The stability calculation," he said. "You've provided GM figures?"
"Tab 3 of the drawing package," Vishwakarma said. "Metacentric height at full load, light condition, and in the intermediate states. The GM at full load is 1.35 metres. At half-load, 1.58 metres."
Sarma found Tab 3. He looked at the numbers. His expression was that of a man checking arithmetic that he suspects may be correct and is slightly hoping is wrong so he has something to comment on.
"These check," he said, with the mild disappointment of a man whose checks have come out right.
"We ran the hull form through physical model tests at the Calcutta ship model basin," Karan said. "The resistance and stability predictions are from tested results, not from calculations alone."
Roy looked up. "You ran tank tests on a ship you haven't been contracted to build."
"We ran tank tests on a ship we very much hoped to be contracted to build," Karan said. "The tests took eleven weeks. The results convinced us the design was worth presenting to you. If we had waited for a contract before testing, we would now be presenting you an untested design and asking you to trust our calculations."
"Which you wouldn't do," Kohli said.
"Which you shouldn't do," Karan confirmed. "Calculations can be wrong. Physical tests are what they are."
Kamath said, from his position at the edge of the gathering: "How much did the tank tests cost?"
"Eighty lakhs," Karan said.
"You spent eighty lakhs on tests for a ship that didn't exist and might never exist."
"Yes," Karan said.
Kamath looked at him for a moment. "That is either very professional or very optimistic."
"I prefer to think it is both," Karan said. "The optimism provides the motivation. The professionalism ensures the money isn't wasted."
Kamath made a sound that was not quite a laugh but occupied the same territory.
The propulsion question came from Roy, who had been building toward it since Karan mentioned the combined diesel and gas turbine arrangement.
"The propulsion plant," Roy said. "CODAG. Where is the gas turbine coming from?"
Karan looked at him. "This is the part of the presentation where I ask you to come downstairs first."
Kohli raised an eyebrow.
"There is something running in the test bay that is more persuasive than any drawing," Karan said. "If you will give me thirty minutes, we go to the test bay now and come back to the drawings after. The drawings will make more sense after you have heard the engine."
Kohli looked at his watch. He looked at Roy. Roy shrugged, which from Roy communicated agreement.
"Lead the way," Kohli said.
They went downstairs, through the main building, past the storage area, and into the engine test bay.
The Marine Kaveri Mk 1 was at fifty-three hours of its 100-hour test run.
The sound in the test bay was what it was — a deep, sustained presence that communicated power in the physical way that machines with genuine power communicated it, not by being loud but by being present, the way a large animal was present even when it was being quiet. The air was warm. There was a slight heat shimmer above the acoustic enclosure's exhaust outlet.
Lieutenant Commander K.V. Nair was standing beside the instrumentation rack with a clipboard and the expression of a man who had been sitting with a running engine for two days and had developed the specific contentment of someone whose work is going exactly as it should.
He stood straighter when the delegation entered.
"Sir," he said to Kohli. Then he looked at the engine as if reminding himself it was still there. Then back at Kohli. He had the manner of a man who was simultaneously proud and trying not to be obviously proud, which produced a kind of vibrating contained quality that was, in its way, endearing.
Kohli walked to the instrumentation rack. He looked at the readings with the attention of someone who had been a naval engineer before he had been anything else.
Shaft speed: 15,400 rpm. Thrust: 19.8 megawatts. Turbine entry temperature: 1,230 degrees Celsius. Fuel flow: 4.2 kilograms per second. Vibration at all measurement points: within specification.
He was quiet for a long time.
"Fifty-three hours of continuous running," Nair said. He couldn't help it. "The numbers have not declined from hour one."
"The turbine entry temperature," Kohli said. "1,230 degrees. That's hotter than the Olympus runs."
"The Mk 1.5 aircraft engine runs hotter than that," Nair said. "The marine adaptation runs at a slightly lower temperature to extend the hot-section life. We give up approximately four percent thrust efficiency in exchange for ten thousand hours of TBO instead of the aircraft engine's 1,400 hours."
"Ten thousand hours," Roy said.
"Against eight thousand hours for the Olympus," Nair said. "And unlike the Olympus, the Marine Kaveri overhaul happens here. No foreign exchange. No Rolls-Royce scheduling. No waiting for a British technician to have a gap in his diary."
He said the last sentence with the quality of a man who had, at some point in his naval career, waited for a British technician to have a gap in his diary.
Roy made a note. The note appeared to be about the comparative TBO figures. Then he made a second note, which appeared to be about the overhaul location question.
"Is it an aircraft engine with the wings removed," Kamath asked, looking at the test stand, "or is it a marine engine that happens to share components with an aircraft engine?"
"That," Nair said, straightening slightly, "is the correct question." He seemed pleased that someone had asked it. "It is not an aircraft engine in a marine application. The compressor section is derived from the Kaveri Mk 1.5's compressor design, but the pressure ratio has been reduced to improve reliability at constant speed. The combustor has been redesigned for marine fuel — marine diesel rather than aviation kerosene. The turbine blades are different — slightly larger and coated differently for the lower temperature regime. The gearbox is entirely new. The inlet treatment —" He gestured at the enclosure "— includes moisture separation and salt filtration. An aircraft inlet and a marine inlet have completely different requirements."
"How many parts are the same as the aircraft engine?" Kamath asked.
Nair thought for a moment. "Conceptually very similar. Physically — about twenty percent of components are interchangeable with the aircraft engine. The rest are marine-specific."
"So it is a related but distinct engine," Kohli said.
"Yes sir," Nair said. "It is an engine designed for a ship. Which happens to have been designed by people who already knew how to design engines because they had designed one for an aircraft."
Kohli looked at the instrumentation rack one more time. "It is running," he said. "At this moment. In this building."
"Yes sir," Nair said.
"Good," Kohli said. He turned back toward the door. "Let us go upstairs and look at where it goes."
As they were filing out, Chatterjee stopped beside Nair.
"When does the test programme end?" he said.
"One hundred hours," Nair said. "Another forty-seven hours from now."
"And then?"
"Then we shut it down, strip it, measure every significant component for wear, and compare against predictions. If the turbine blades show less than 0.3 millimetres of erosion, the TBO projection holds. If they show more, we revise."
"And if they show more?" Chatterjee asked.
"Then we find out exactly why," Nair said, "and we fix it, and we run another test. That is what test programmes are for." He paused. "I'm not expecting to find more than 0.3 millimetres."
"How confident are you?"
Nair looked at the instrumentation rack. At the numbers that had been holding steady for fifty-three hours.
"Quite," he said.
Lunch was in the yard canteen.
This was deliberately the yard canteen — not a catered room, not a separate dining arrangement, the canteen where the shipyard workers ate. The choice communicated something about what kind of visit this was, and Kohli, who had grown up in Vizag and had eaten in yards like this, recognised the communication and apparently approved of it, because he walked to the serving counter without hesitation and accepted his rice and sambar and vegetables and chapati with the ease of a man who had never believed that rank excused him from eating what was in front of him.
He looked at the tamarind pickle.
"That pickle," said Vishwakarma from the queue behind him, "is made by a man named Murugesan who has been making it since before anyone can remember. It is very sharp."
"I am not frightened of pickle," Kohli said.
He tried the pickle.
He was quiet for approximately four seconds.
"It is quite sharp," he said.
"Yes," Vishwakarma said.
"Also excellent," Kohli said.
Vice Admiral Kamath, seated beside him, watched this exchange with the specific deliberation of a large man deciding whether the outcome justified the risk. The outcome appearing positive, Kamath tried the pickle, inhaled sharply, and then said: "Good."
Rear Admiral Roy had his notebook on the table and was eating with his left hand while doing arithmetic with his right, which was the kind of behaviour that was technically efficient and socially questionable.
"Roy," Kamath said.
"Sir," Roy said, not looking up.
"Put the arithmetic down."
"I'm just checking the cost per tonne of displacement against the—"
"Roy."
A pause.
"Sir," Roy said. He looked at his plate. He put the notebook down. He ate in silence for about thirty seconds, then said: "The cost per tonne is very favourable."
"I'm sure it is," Kamath said. "Eat."
Karan was at the far end of the table listening to this with the quality of someone who finds things funny and has learned to be quiet about it in professional settings. Nair was beside him, eating his second serving of sambar with the conviction of a man who believed in the restorative properties of good food before difficult technical discussions.
Commodore Chatterjee had found his way to Karan's side and appeared to be treating lunch as an extension of the weapons systems briefing.
"The Kaumodaki," Chatterjee said. He had been thinking about this since the morning session, when Karan had mentioned that a naval surface-launch version of the anti-ship missile was in development.
"The Kaumodaki Mk 3," Karan said. "The surface-launch variant."
"Yes," Chatterjee said. "Range?"
"180 kilometres from surface launch," Karan said.
Chatterjee was quiet for a moment. "The Exocet AM39 is being developed by Aerospatiale," he said. "We are told it will have a range of approximately 50 to 70 kilometres."
"Yes," Karan said.
"The Kaumodaki's range is therefore three to four times the Exocet's range."
"On paper, yes," Karan said.
"Is there a 'but' coming?" Chatterjee asked.
"There are several buts," Karan said. He put down his fork. "The Kaumodaki Mk 2 — the air-launched version that the S-22 Makara carries — is a magnificent weapon in the right situation. The surface-launch version inherits both its virtues and its limitations, and the limitations are not small."
Chatterjee looked at him. He had the expression of someone who was expecting the usual promotional approach and was getting something else.
"The Kaumodaki is a large missile," Karan said. "It is 5.4 metres long and weighs 680 kilograms. The Exocet, when it arrives in its sea-launch form, will be approximately 5.8 metres and 660 kilograms — comparable. But the Kaumodaki's seeker and guidance system are optimised for a high-altitude aircraft launch, and the marine version is still inheriting some of that architecture. The seeker works. But it works best when the missile has had thirty seconds to stabilise after launch before beginning its terminal approach."
"The sea-skim phase," Chatterjee said.
"The Kaumodaki comes down to sea-skimming height and then goes to its terminal acquisition," Karan said. "The problem is that at Mach 1.8 — the Kaumodaki's terminal speed — the active radar seeker is working in a thermal boundary layer caused by aerodynamic heating. The seeker can see through the boundary layer. But the thermal noise reduces the seeker's sensitivity at that specific speed regime."
"Which means?"
"Which means the Kaumodaki can miss a target that changes course aggressively in the terminal phase," Karan said. "It is much harder to miss a stationary or predictably moving target. Against a manoeuvring warship that detects the incoming missile and begins emergency evasion at fifteen kilometres — the miss probability increases."
Chatterjee was writing. He had abandoned the pretence that lunch was not a briefing.
"The Exocet," Karan said, "when it enters service, will be slower — subsonic. This sounds like a disadvantage. It is partly an advantage. A subsonic seeker doesn't have the thermal boundary layer problem. The Exocet's terminal seeker will operate in cleaner conditions."
"So the Kaumodaki's speed is both its advantage and its limitation," Chatterjee said.
"Correct. Against a destroyer that doesn't know the missile is incoming until it's at eight kilometres — the Kaumodaki kills it before it can manoeuvre. Against a destroyer that detects the missile at twenty kilometres and executes a hard turn while deploying chaff — the Kaumodaki has a harder problem than the Exocet would."
"You are telling me," Chatterjee said slowly, "that the weapon your company built has a situation-dependent limitation."
"I am telling you that every weapon has a situation-dependent limitation," Karan said. "The Kaumodaki's limitation is specific to reactive targets in the terminal phase at high speed. The Exocet's limitation is that it is slower and therefore more easily intercepted by point defence systems. Different limitations. Different tactical solutions."
He picked up his fork again.
"There is also a logistical consideration," he said. "The Kaumodaki is large. A destroyer carrying a full magazine of Kaumodaki Mk 3 surface-launch versions can carry fewer missiles than a destroyer carrying Exocet. The magazine depth is limited by physical size. You carry six or eight Kaumodakis where you might carry twelve Exocets."
"That is a real constraint," Chatterjee said.
"Yes," Karan said. "It is honest for me to name it. When the Type 41 destroyer specification is finalised — and we will look at the destroyer design this afternoon — the weapons load will need to account for the magazine depth limitation."
Chatterjee looked at him for a long moment. "Mr. Shergill," he said. "Why are you telling me the limitations of your own weapon systems?"
"Because," Karan said, "if I tell you only the advantages and you purchase the ships and deploy them operationally, the limitations will reveal themselves at sea at a moment when it is inconvenient for them to do so. If I tell you the limitations now, you can design the tactics around them before the ships are delivered."
Chatterjee was quiet for a moment. Then he said, with the quality of a man recording something for later use: "This is an unusual approach."
"It is the correct approach," Karan said.
"It is unusual," Chatterjee said again. He was not being critical. He was being accurate.
The afternoon was the destroyer.
Type 41, the drawings said. 142 metres overall. 5,000 tonnes full load displacement. Beam of 15.8 metres. Maximum speed of 30 knots.
Sarma was back at the blueprint table before anyone else had fully settled into their chairs.
"The beam," he said immediately.
"15.8 metres," Karan confirmed.
"That is broader than the Kashin," Sarma said. "The Kashin is 15.8 — actually the Kashin is 15.8, so comparable. The Type 42 destroyer that the British are designing is—"
"Narrower," Karan said. "The Type 42 trades beam for speed. It makes 28 to 30 knots in a more slender hull. The Type 41's beam reflects a different priority — we want internal volume for systems and magazine depth, and we accept the slightly lower top speed of 30 knots."
"The destroyer," Kohli said, from his seat, "is designed as an area air defence ship."
"Yes," Karan said. "It is the ship that sits between the task group and the threat. Between the carrier —" he paused, which was a deliberate pause, because INS Vikrant was aging and everyone in the room knew it, and the pause acknowledged the weight of that without requiring any of them to say it "— and whatever is coming at her."
The pause was noted. Kohli nodded once, which was the kind of nod that meant several things simultaneously.
"The main battery," Roy said.
"One 114mm gun forward and one 40mm Bofors aft for close-in defence," Karan said. "The 114mm is the same Vickers Mk 6 as the frigate. The 40mm Bofors is a proven weapon — it has been in continuous production since the Second World War for good reasons."
"The anti-ship missiles," Chatterjee said.
"Six Kaumodaki Mk 3 in box launchers amidships," Karan said. "I've explained the Kaumodaki's limitations. The launchers are designed to be replaced by whatever improved system is available at the midlife refit."
Chatterjee was writing. His writing had the quality of someone building a very detailed picture.
"Surface-to-air missiles," he said.
"Two twin Seacat launchers — one forward, one aft," Karan said. "Each launcher carries a four-round ready magazine with reload stowage for sixteen missiles per launcher. Short-range close air defence at four kilometres."
Roy made a sound.
"I know," Karan said. "Four kilometres is not impressive."
"Four kilometres against a jet aircraft means the aircraft has already released its weapons," Roy said.
"Yes," Karan said. "It does. The four-kilometre range is for the specific situation of defending against helicopters, slow aircraft, and — most importantly — sea-skimming missiles at close range, where you have detected the missile late and need a last-ditch intercept."
He looked at Roy directly.
"I want to show you where the destroyer's real air defence strength is," he said. "It is not in the Seacat. The Seacat is the final layer. The strength is here." He moved to the electronics fit drawing, which showed the ship in profile with the antenna positions marked.
"The destroyer carries the Thomson-CSF radar," Karan said. "This is a French-designed long-range air search radar. It has a 3-metre antenna on the main mast, 180-kilometre detection range against high-altitude aircraft, and good clutter performance. the electronics capability we have developed for the Netra radar in the S-27 means this is achievable."
"The sonar," Sarma said. He had been looking at the hull section drawing.
"Same hull-mounted array as the frigate but 4.2-metre aperture," Karan said. "The destroyer's primary ASW weapon is the helicopter — we have a larger flight deck and a proper enclosed hangar. The helicopter carries the torpedoes."
"What helicopter?" Kohli asked.
"Sea King or equivalent," Karan said. "The hangar is dimensioned for the Sea King's rotor diameter and fuselage width. If the Navy procures Sea Kings, they go on this ship directly. If the Navy procures the Westland Lynx — which Westland is currently developing — the hangar accommodates it as well."
Kohli nodded. "We have been in discussion with Westland about the Lynx programme."
"The hangar will accommodate it," Karan said. "We designed to the dimensions we knew about and built in a half-metre structural tolerance in each direction."
Sarma had been making marks on the drawings with the methodical precision of a man conducting a systematic review. He had made perhaps twenty marks in the last ten minutes. The marks were a mixture of ticks and asterisks, and the ratio of ticks to asterisks was approximately four to one, which communicated something about the quality of the design.
"The propulsion," he said. "Two Marine Kaveri gas turbines and two Pielstick diesels?"
"Correct," Karan said. "CODAG. The diesels give you 21 knots cruise range. The gas turbines come online for sprint operations. The full 30 knots requires all four units."
"The vibration from the gas turbines," Sarma said. "In the destroyer, where the main mast and the search radar are a direct structural path from the machinery spaces to the antenna—"
"Anti-vibration mounting," Nair said, from the corner of the room where he had been sitting since they came upstairs. "The engine subframe is isolated from the ship's structure by elastomeric mounts. The vibration reaching the hull at full power is within the acceptable limits for the sonar self-noise specification."
Sarma looked at him. "This is the same mounting arrangement you described for the frigate."
"The same principle, different dimensions," Nair said. "The destroyer is heavier, so the mounts are stiffer. The vibration isolation is proportionally maintained."
"Has it been tested?" Sarma asked.
"The mounting arrangement for the destroyer specifically — no," Nair said. "The principle has been tested extensively on the frigate's mounting arrangement, which uses the same design scaled for a smaller ship. The destroyer's mounting is a straight scaling calculation."
"Scaling calculations can be wrong," Sarma said.
"Yes," Nair said. "Which is why the programme includes a prototype mounting system for the destroyer that will be tested at the Gorakhpur engine facility before the production mounts are manufactured. The scale test is scheduled for month nine of the construction programme."
Sarma made a tick. He appeared slightly surprised that there was a tick to make.
The cost question came from Roy, who had been building toward it throughout the afternoon like a man who had promised himself he would ask it properly and at the right time.
"The programme cost," he said. He had his notebook open to a page with numbers on it that he had apparently been computing during the presentation, because the numbers were already there despite the topic not having been formally addressed. "I have been estimating as we went. Six frigates at the range you specified — thirty-five to forty-two crore per frigate. Two destroyers at the upper range — fifty-five to sixty-five crore each."
"Thirty-eight crore per frigate as the production standard," Karan said. "Sixty-one crore per destroyer."
Roy looked at his numbers. "Slightly below my estimate on the frigate, right in the middle on the destroyer."
"We have a detailed cost model," Vishwakarma said. "We can share it."
"I will want to see it," Roy said. "But working from your numbers: six frigates is 228 crore. Two destroyers is 122 crore. Total programme for eight ships: 350 crore rupees."
He looked at Kohli.
"350 crore rupees is nearly the entire 1972 defence capital budget," he said. "For all three services combined."
The number sat in the room. It was a real number and it had weight.
"It is a large sum," Karan said. "The Navy has two options for how to think about it." He stood again. Not for drama — he thought better standing. "Option one: it is an expensive shipbuilding programme. Option two: it is the domestic manufacturing infrastructure for naval construction that India currently does not possess, being built simultaneously with the ships it produces."
Roy looked at him.
"The 350 crore is not only for eight ships," Karan said. "It is for developing the workforce, the supply chain, the quality systems, and the institutional knowledge to build naval vessels in India at scale. The second class of ships after this programme will be significantly cheaper, because the development costs are amortised over this programme. The third class will be cheaper still."
"If there is a second class," Roy said.
"If the Navy orders ships, there will be a second class," Karan said. "Shipyards that are working build the expertise to build more ships. Shipyards that are idle lose the expertise they had. The 350 crore buys both the ships and the permanent capability. That is the true comparison."
Roy was quiet for a moment. He had the expression of a man whose arithmetic had been reconfigured by someone adding a term he had not included.
"The funding mechanism," Kohli said.
"That," Karan said, "is your problem to solve, not mine. What I can offer you is the economic impact analysis that makes the case for treating this as an industrial investment rather than purely a defence expenditure. The employment, the steel demand, the electronics manufacturing, the engineering training — these are real economic multipliers. I can quantify them. Whether the Finance Ministry is willing to fund naval shipbuilding as national infrastructure — that is a political question I am not qualified to answer."
Kohli nodded slowly. "You are suggesting the Finance Ministry should be part of this conversation."
"I am suggesting that the people who fund defence should understand that sometimes defence spending creates economic capability rather than simply consuming it," Karan said. "This programme does both. It should be presented as both."
Kamath, who had been still and listening for most of the afternoon, said: "You have thought about this more than the procurement system typically requires manufacturers to think."
"The procurement system," Karan said, "does not typically require manufacturers to think about how the programme gets funded. I have found that when manufacturers don't think about that question, programmes don't get funded."
Kamath looked at him.
"Since 1972," he said. It was the third time someone in the room had noted this specific year.
"Yes," Karan said.
"You've been thinking about this since the S-22 Makara was delivered," Kamath said.
"I've been thinking about it since I looked at the state of this yard in 1971 and realised that India had a harbour in Vizag and a Navy in Vizag and a shipyard in Vizag and none of the three were speaking to each other in any productive way," Karan said.
Kamath looked at him for a moment with an expression that was slightly more than professional.
"How old are you?" he said.
"Twenty-four," Karan said.
"Twenty-four," Kamath repeated. He said it the way a man said a number that was correct but he did not entirely believe.
It was late afternoon when Rear Admiral Sarma said: "The corvette."
Everyone looked at him. He was still at the blueprint table, still looking at the destroyer drawings, still making marks.
"We have not discussed a corvette," he said.
"We did not prepare a corvette design," Karan said.
"I am aware of that," Sarma said. "I am asking whether one is being worked on."
"A requirements study," Karan said. "We began it in late 1973. It is not a design yet."
"What has the requirements study concluded?"
"That the Navy has a gap in the littoral and near-coastal patrol role," Karan said. "The Gulf of Kutch, the Palk Strait, the Andaman approaches. The frigate is too large for this role — too deep in draft for some of the coastal work, operationally expensive for patrol missions. Something between 800 and 1,400 tonnes displacement, fast, lightly armed with anti-ship missiles and a gun, able to sustain high speed over shorter distances."
"When will the design be ready?" Sarma asked.
"When we have a clear requirement from the Navy," Karan said. "The study has identified what type of capability is needed. Designing the ship requires knowing the specific performance envelope the Navy wants to operate within."
Sarma looked at the destroyer drawing. Then at Karan. "Include a corvette section in the programme definition document," he said. "As a design study with requirements to be defined. I will provide the Naval Construction Directorate's requirements in writing within sixty days of this meeting."
"Understood," Karan said.
"This is the correct order of things," Sarma said, with the quality of a man noting a precedent. "Requirements first, then design. Not the other way around."
"In this case, yes," Karan said.
"In all cases," Sarma said firmly.
"In the cases where there is time to develop requirements before there is urgency," Karan said. "In the cases where the capability gap is already visible and the opportunity to address it is closing — I find that sometimes the design precedes the formal requirement. The Air Force found this unsettling. They bought the aircraft anyway."
Sarma looked at him. "The Navy," he said, "prefers requirements first."
"The Navy," Karan said, "will have requirements first for the corvette. The frigate and the destroyer required urgency."
"What urgency?" Sarma said. "The frigates have not been ordered. There was no deadline."
"INS Vikrant," Karan said.
The room went slightly quiet. Not dramatically — just the particular quality of quietness that settles over a room when something has been said that everyone was thinking but nobody was saying.
"Vikrant's hull was laid down in 1943," Karan said. "She has been running for eleven years. She will run for perhaps another ten. When she reaches the end of her service life, the Indian Navy will either have a replacement under construction or will not have a carrier. The replacement requires ships to operate with it — escort ships that are capable of defending the carrier group, attack ships that are capable of threatening adversary surface groups. Those ships take four to five years to design, build, and commission." He looked at Kohli. "The urgency is that Vikrant's clock is running and the escort force does not yet exist."
Kohli looked at him steadily.
"I was not going to mention the carrier question today," Kohli said.
"I know," Karan said. "But it is the strategic context for why the frigates and destroyers need to be ordered now rather than after another year of study."
"Are you planning to build a replacement carrier?" Kohli asked.
A pause.
"I am planning to be ready to build one," Karan said, "when the Navy requires one."
Kohli's eyes moved to the window, which looked out over the slipways. His gaze settled on Slipway 7 — the longest slipway, the one that had been extended to 310 metres.
"Slipway 7," he said.
"Yes," Karan said.
"That is longer than a frigate requires," Kohli said.
"A frigate requires 135 metres minimum," Karan said. "Slipway 7 is 310 metres."
"A light fleet carrier of the Vikrant's class," Kohli said slowly, "is approximately 213 metres."
"Yes," Karan said.
"Your slipway is designed for a carrier."
"My slipway is capable of building a carrier," Karan said. "Whether it builds one depends on whether the Navy requires one and whether the Navy and government provide the programme."
Kohli looked at the slipway for another moment.
"You built that slipway length in anticipation of an order that doesn't exist," he said.
"I built it to the dimensions that would not limit future capability," Karan said. "Whether the capability is used is a separate question."
Kohli turned back to the table.
"We will discuss the carrier," he said, "after the frigates are in service and this yard has demonstrated that it can build warships to the standard required."
"That is the correct sequence," Karan said.
"I am glad you agree," Kohli said, with the specific dryness of a man who had noticed that Karan had been building toward a carrier conversation for an entire afternoon and had just closed it by agreeing that it should not happen yet.
Captain Bhatia had been writing for eight hours.
He had been so comprehensively silent throughout the day that several members of the Shergill team had, at various points, forgotten he was there — which was both his professional excellence and, in a meeting about ships, somewhat alarming.
He spoke for the first time since his introduction as the afternoon session was moving toward its close.
"The maintenance training programme," he said.
Everyone looked at him. The effect was slightly like a piece of furniture speaking.
"The Type 28 has a hull-mounted sonar, twin torpedo tubes, a Seacat missile system, a gas turbine, two diesel engines, a 114mm gun, and a helicopter," Bhatia said. He was looking at his notebook rather than at the room, the way a man looked at notes he had been building for eight hours and was now prepared to deploy. "A frigate crew is approximately 200 personnel. Each of these systems requires trained maintenance personnel. The Marine Kaveri gas turbine is new. There are no trained Marine Kaveri maintainers in the Indian Navy because the Marine Kaveri has not previously existed."
He looked up.
"How does the Navy train them before the ship is delivered?"
The room was quiet in the way of a room that has had a very good question asked in it.
"The engine test bay," Nair said immediately. He had been waiting for someone to ask a question he could answer. "The Marine Kaveri on the test stand is the training engine. We run a maintenance training programme using the actual engine. The Navy sends marine engineering personnel here for training. They learn the Marine Kaveri from the people who built it, using the engine that runs it."
Bhatia noted this.
"When does the training programme begin?" he said.
"Six months after the contract is signed," Nair said. "That gives us time to develop the curriculum and produce the maintenance documentation. Training runs for eighteen months. First course graduates are available before the first ship is delivered."
"The Seacat missile system," Bhatia said.
"The training for that uses the land-based test installation at Chandipur," Karan said. "The Navy's weapons engineering branch sends people there alongside the development programme. By the time the ship is delivered, the weapons crew have trained on the system."
Bhatia noted this.
"The sonar," he said.
"The sonar training is the most complex problem," Karan said honestly. "The sonar requires qualified operators who can interpret the acoustic picture in Bay of Bengal conditions. The Bay of Bengal's thermal structure is different from the North Atlantic or the Mediterranean — different layer depths, different temperature gradients. We are working with the National Institute of Oceanography to produce Bay of Bengal acoustic data that can be used in sonar operator training."
"The NIO has not been involved in naval training before," Bhatia said.
"They are now," Karan said. "We began the discussion in 1973."
Bhatia looked at his notes for a moment. Then he looked at the room, and his gaze settled on Admiral Kohli.
"All of this," Bhatia said, "should be in the programme definition document."
"It will be," Vishwakarma said.
"It is not currently in the preliminary materials you have provided," Bhatia said.
"The programme definition document is not yet written," Vishwakarma said. "This meeting is part of writing it. The maintenance training, the sonar operator training, the weapons training — these will all be in the document you receive."
Bhatia made a note. It was a very deliberate note, the note of a man who had heard a commitment and was recording it for later verification.
"Two weeks," Kohli said.
Everyone looked at him.
"The programme definition document," he said. "Two weeks."
"Twelve days," Karan said. "With two days for review."
Admiral Kohli looked around the table at his delegation — at Roy's notebooks full of numbers, at Sarma's annotated drawings, at Chatterjee's weapons specifications, at Bhatia's eight hours of notes — and made a small movement that communicated, without words, that the formal business was complete and the summary was about to begin.
"Mr. Shergill," he said. "You have shown us a frigate design that is technically serious, a destroyer design that addresses capabilities the Navy currently lacks, and a propulsion system that is running below this building as we speak. You have been honest about the limitations of your weapons systems, which is unusual. You have thought about the funding mechanism, the training pipeline, the maintenance approach, and the long-term programme structure with a degree of detail that I do not normally encounter from manufacturers at this stage of a programme."
He paused.
"You have also clearly been working toward this meeting since 1972 while the Naval Planning Directorate was wondering why Shergill Industries was ignoring the Navy."
"We were not ignoring the Navy," Karan said. "We were waiting until we had something worth saying."
"And now you do," Kohli said.
"And now we do," Karan said.
Kohli looked at Roy. Roy made a small gesture that communicated something — that the numbers worked, or that the programme was credible, or both.
"I will take this programme to the Ministry," Kohli said. "A programme of this scale requires Cabinet-level approval for the capital allocation. I will recommend that approval be sought. I will represent the capability requirements and the strategic rationale for the programme."
He looked at Karan.
"The programme definition document in two weeks. Naval Construction's independent assessment four weeks after that. If the assessment is satisfactory, I go to the Ministry in March."
"Understood," Karan said.
"And Mr. Shergill." Kohli stood, and with him the table. "The carrier question. We do not discuss it before the frigates are in service."
"Agreed," Karan said.
"But I notice," Kohli said, with the specific dryness he had been deploying throughout the day, "that you have said nothing to suggest you have not already begun thinking about it."
Karan looked at him.
"I will not confirm or deny what is in the design office files," he said.
Kohli looked at the window, at Slipway 7.
Kohli turned back to the room. He had the expression of a man who has spent an entire day discovering that someone else had been several moves ahead of him throughout, and who has decided that this was more useful than alarming.
The delegation left at seven-fifteen.
Karan stood at the third-floor window and watched the vehicles leave with the geometric precision they had arrived with, Captain Bhatia still writing in the last car as it moved through the gate.
Vishwakarma appeared beside him.
"The carrier question," Vishwakarma said.
"He noticed the slipway," Karan said.
"Of course he noticed the slipway," Vishwakarma said. "He is the Chief of Naval Staff. His entire profession is noticing things that are relevant to ships."
"He didn't push it."
"He didn't need to push it," Vishwakarma said. "He understands that the conversation happens when the frigates are in service. He doesn't need to force it today."
He looked at the slipways in the yard lights — yellow and functional, the honest illumination of a place where work happened rather than a place where appearances were managed.
"The programme definition document," he said. "Twelve days."
"We start tomorrow," Karan said. "The frigate section is mostly written from the technical package. The destroyer section needs the cost model revised from today's discussion. The training programme section—"
"Nair will write the propulsion training programme section," Vishwakarma said. "He has been writing it in his head since the question was asked."
"I know," Karan said. "Tell him to write it on paper."
"I'll tell him tonight," Vishwakarma said. "He is still in the engine bay."
"Of course he is," Karan said.
They stood at the window for a moment. Outside, the bay was dark now, the harbour lights making lines on the water, a container ship moving on the northern lane with its navigation lights steady.
"Sarma will give us a credible technical assessment," Vishwakarma said. "Roy will make the numbers work if anyone can make them work. Bhatia will make sure nothing is forgotten."
"I know," Karan said.
"The Admiral will take it to the Ministry."
"He will."
"And then?"
Karan looked at Slipway 7 in the yard lights. At the 310 metres of concrete incline that had been built to a dimension that no current commercial order required and no defence contract yet justified.
"And then," he said, "we start building ships."
The Marine Kaveri Mk 1 completed its 100-hour test on the 30 of December.
Nair shut it down personally, waited for the cooldown cycle to complete, and then began the inspection with the focused attention of a man who has been waiting for a specific number and is about to find out whether the number is correct.
The turbine blades showed 0.22 millimetres of erosion.
The prediction had been 0.30 millimetres maximum.
Nair stood at the inspection table looking at the measurement for a long time. Then he said, to the senior technician assisting him:
"The 10,000-hour projection holds."
The technician, who had been working on the engine for two years and who had perhaps a more personal relationship with it than was professionally standard, made a sound that combined relief with satisfaction in approximately equal measure.
Nair called Karan.
"0.22 millimetres," he said.
"Good," Karan said.
"The TBO projection is confirmed," Nair said.
"Good," Karan said again.
"That's all you're going to say?" Nair said.
"What else should I say?"
"Something more than 'good,'" Nair said. "We have been running this engine for two years. We started from the Kaveri Mk 1.5 and redesigned the combustor and the turbine and the gearbox and the inlet treatment and the anti-vibration mount and we ran it for 100 hours and it came in 26 percent better than the design prediction and you are saying 'good.'"
"It is good," Karan said.
"It is excellent," Nair said.
"Yes," Karan said. "Write the inspection report. Include the phrase '26 percent better than design prediction' in the executive summary. Then send it to Naval Headquarters."
"The report will say 'excellent' in the executive summary," Nair said.
"The report will say what the data says," Karan said. "The data says 0.22 millimetres. Put 0.22 in the executive summary. Let Naval Headquarters draw their own conclusion."
A pause.
"They will conclude that it is excellent," Nair said.
"Yes," Karan said. "And it will be their conclusion, not ours. Which is more useful."
The programme definition document was delivered to Naval Headquarters on 4 March 1974.
It was 231 pages long.
Rear Admiral Sarma's assessment was completed on 26 March. It was 87 pages, which was three pages shorter than Karan had expected and suggested that Sarma had found fewer questions than the design team had anticipated.
The assessment concluded:
The Type 28 and Type 41 designs represent the most technically serious indigenous naval ship programme India has attempted. The propulsion system is a genuine national achievement. The designs are ambitious for a first programme but the technical preparation — tank testing, propulsion testing, sonar compatibility analysis — demonstrates a level of engineering rigour that warrants confidence. Naval Construction recommends programme approval subject to eight technical conditions listed in Appendix C, all of which are resolved by documentation already committed by the contractor.
The contract was signed on 2 May 1974.
Six frigates. Two destroyers. A corvette design study to follow. 394 crore rupees over six years from a dedicated naval modernisation capital fund that the Finance Ministry had agreed to — after three meetings with the Finance Secretary — on the basis that the industrial multiplier from Indian naval construction justified treating the programme as infrastructure investment.
The keel of INS Shivalik, frigate hull F47, was laid on Slipway 7 on the seventh of April 1974.
The keel was set at 0.3 millimetres off centreline. Balakrishna Rao, the yard manager, corrected it to 0.2 millimetres before the ceremony ended, because he had decided that 0.3 was within tolerance but tolerance was not the point.
The point was the ship.
On the morning of the keel-laying, before the ceremony, Karan walked the yard alone.
It was before six. The shift had not started. The slipways were quiet under the pre-dawn, the concrete wet from the night's humidity, the keel blocks on Slipway 7 freshly greased and aligned. Somewhere in the southern fabrication hall, a night-shift welder's torch was still going — the sound of it crossed the yard in the early morning quiet.
He stood at the head of the keel blocks.
He thought about December — about Kohli's question about the carrier, about Sarma's fourteen technical questions, about Roy's arithmetic, about Bhatia spending eight hours writing things down that he would later verify.
He thought about Nair at 0.22 millimetres and the sound of his voice when he said 'excellent' to the empty inspection room.
He thought about the S-27, about the first flight in 1972, about the moment when Rathore had come back from a sortie and said this is a different category of aircraft with the flat precision of a man making a professional assessment rather than a compliment.
He thought about the difference between a tank and a ship.
A tank was a machine. You built it and it worked or it didn't and you fixed the parts that didn't work. A ship was a small society — crew, systems, doctrine, the accumulated knowledge of how to sail and fight and repair and resupply, all of it interdependent, none of it independently sufficient. Building the ship was the beginning of building the society. The training programme, the maintenance schedules, the tactical doctrine, the career structure for the engineers who would spend their professional lives with the Marine Kaveri — all of that grew from the keel being set on this slipway on this morning.
He stood at the head of the keel blocks and looked at the bay.
The bay was grey and pewter in the pre-dawn — not the tourist-brochure colour, the working colour, the colour of a sea that was going about its business and would continue going about its business regardless of what happened on the slipway behind it.
In three years, something built here would go out into that water.
Something with an Indian engine and an Indian radar and Indian men who had been trained on Indian equipment, who knew the Bay of Bengal's thermal structure from the data the National Institute of Oceanography had provided, who had learned the Marine Kaveri's maintenance sequences from Nair's instructors in the test bay below.
The Navy had asked why the company that built aircraft and tanks had not built ships.
The answer had been: because ships require a different kind of partnership.
The partnership had been agreed.
The keel was going in.
The bay went about its business.
The sky lightened.
End of Chapter 140
Ship Specifications — As Presented
Type 28 Shivalik-class Frigate — Unit cost ₹38 crore Length: 124m | Displacement: 3,400t full load | Speed: 28kt max, 20kt diesel-only Propulsion: CODAG — 2× Marine Kaveri Mk 1 gas turbine + 2× Pielstick PA6 diesel Armament: 1× 114mm DP gun, twin Seacat SAM launcher, 2× triple 533mm torpedo tubes Sensors: Fire control director radar, hull-mounted sonar (3.8m array), VDS provision Aviation: 1× medium helicopter (Sea King/Alouette III), enclosed hangar
Type 41 Destroyer — Unit cost ₹61 crore Length: 142m | Displacement: 5,000t full load | Speed: 30kt max Propulsion: CODAG — 4× Marine Kaveri Mk 1 gas turbine + 2× Pielstick PA6 diesel Armament: 1× 114mm DP gun fwd, 1× 40mm Bofors aft, 6× Kaumodaki Mk 3 anti-ship missiles, 2× twin Seacat SAM launchers, 2× triple torpedo tubes Sensors: Thomson-CSF long-range air search radar (180km range), fire control director, hull sonar (4.2m array) Aviation: 1× Sea King-class helicopter, full enclosed hangar
Kaumodaki Mk 3 — Surface-launch anti-ship missile Range: 180km | Speed: Mach 1.8 terminal | Guidance: Inertial midcourse + active radar terminal
Programme Order — Signed 2 January 1974 6 × Type 28 Frigates: ₹228 crore 2 × Type 41 Destroyers: ₹122 crore Corvette design study: Separately funded Total: ₹394 crore over 6 years from dedicated Naval Modernisation Capital Fund