SS Tilawa was a British India Steam Navigation passenger-and-cargo liner carrying hundreds of passengers, most described in descendant accounts as Indian, on a wartime voyage from Bombay toward Africa. Japanese submarine I-29 sank the ship with two torpedoes in the Indian Ocean around 23 November 1942. The loss is sometimes remembered as the “Indian Titanic,” a later nickname—not the ship’s name, nor a claim that the two disasters were the same.
What was SS Tilawa, and where was it going?
Tilawa was a 10,006-ton passenger-and-cargo liner owned by British India Steam Navigation. The Tilawa1942 descendant archive says it left Bombay on 20 November 1942, bound for Mombasa, Maputo and Durban. Its listed complement was 732 passengers, 222 crew and four gunners: 958 people in all. The archive describes most passengers as Indian nationals.
That voyage took place during the Second World War, when civilian travel across the Indian Ocean unfolded amid military danger. The surviving accounts make clear that Tilawa was not simply a cargo vessel: hundreds of passengers were aboard, travelling toward ports in eastern and southern Africa.
How was Tilawa sunk?
The UK High Court’s 16 December 2020 judgment records that Japanese submarine I-29 sank Tilawa with two torpedoes around 23 November 1942. The wreck and salvage account published by Deep Ocean Search also identifies I-29 and the two torpedoes. The sources establish the attacker and the means of sinking, but do not establish why the submarine attacked.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →#1 Best Overall
How many people died or were rescued?
The historical accounts do not agree on a definitive death toll or rescue count. The High Court judgment records 281 deaths. The Tilawa1942 archive and a 2022 descendant-authored article by Emile Solanki give 280. For survivors, the archive reports 678 rescued, a wreck report says HMS Birmingham picked up 673, and Solanki’s article gives 682. These figures should be attributed to their sources rather than combined into a single settled tally.
| Source | Deaths reported | Rescued or survivors reported |
|---|---|---|
| UK High Court judgment, 2020 | 281 lost | Not stated in the cited judgment account |
| Tilawa1942 descendant archive | 280 | 678 rescued |
| Wreck report | Not stated | 673 survivors picked up by HMS Birmingham |
| Emile Solanki’s descendant-authored article, 2022 | 280 | 682 survivors |
The archive’s listed total of 958 people aboard also does not neatly reconcile with its 678 rescued and the 280 deaths reported by descendant sources, which add to 958, while the High Court’s 281 deaths would make the total 959. Other published rescue counts likewise produce different totals. HMS Birmingham and S.S. Carthage are both identified in accounts of the rescue, and survivors were brought back to Bombay, but the available figures do not settle exactly how many people were aboard, saved or lost.
What do survivor and family accounts say?
The Tilawa1942 archive includes a statement attributed to survivor Chunilal Navsaria: “I was one of the passengers on the board Tilawa that night.” It also preserves accounts narrated by descendants about relatives who died. Those testimonies offer personal glimpses of the disaster, but remembered details from an individual account should not be treated as a verified description of what happened to everyone aboard.
Navsaria’s account
Navsaria’s words are presented by the archive as his own survivor testimony. One passage describes people adrift on a piece of timber before rescue. The account conveys the experience of being left in the water, rather than establishing a ship-wide timeline or a complete count of those who survived that way.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #3
A son’s recollection of his father
Another archive account, attributed to the son of Morar Jivan, recounts his father’s efforts to escape the ship and stay alive in the water. This is a family recollection retold on behalf of a deceased relative, not a first-person statement by Jivan. Keeping that distinction visible respects both the testimony and its limits.
Why was there silver aboard?
Tilawa carried 2,391 silver bars shipped in November 1942. The High Court judgment records that the Government of India had sold the silver to the Government of the Union of South Africa, which the court found owned it when the ship sank. The bars were intended for the South African Mint.
The cargo later became part of a salvage operation. Deep Ocean Search says it began looking for the wreck in 2014, identified an apparent target within three days, and confirmed the wreck using sonar and a remotely operated vehicle. The company says it conducted the recovery from the vessel Seabed Worker in 2017, lifting 2,364 bars one by one. The contractor’s project account is its own description of the operation; the High Court judgment also discusses the 2017 salvage and the claim that 2,364 bars were recovered.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What happened in the legal dispute over the recovered bars?
Argentum Exploration claimed ownership of the recovered silver or, alternatively, a salvage reward. South Africa asserted ownership and sovereign immunity. In its 16 December 2020 judgment, the UK High Court found that South Africa was not entitled to immunity in the action. That ruling addressed immunity; it should not be mistaken for a final resolution of every question about salvage or the reward.
The UK judiciary’s case page records an appeal hearing in March 2022. The appeal’s outcome is not established by the sources cited here, so the dispute should not be described as fully concluded.
Why did I-29 attack Tilawa?
The available accounts do not resolve the submarine’s motive or establish whether its crew knew about the silver. The Tilawa1942 archive raises questions about the attack, the bullion and what happened between the torpedoes; Solanki’s 2022 article likewise says the reason for the attack is unknown. That is the author’s assessment, not proof from Japanese operational records that no motive can ever be established.
Nor do these accounts establish whether Tilawa received a warning, what escort decisions were made, or whether intelligence about the cargo influenced the attack. The silver’s presence aboard is documented; a connection between it and I-29’s decision to fire is not.
How should the “Indian Titanic” nickname be understood?
“Indian Titanic” is a later label used in descendant and press coverage to evoke the scale and human loss of Tilawa’s sinking. It was not the liner’s contemporary name, and the phrase does not make the two sinkings equivalent. For Tilawa, the historical record is best read by distinguishing the court’s findings, the salvage contractor’s account, survivor testimony and family retellings—and by keeping disputed counts and unanswered questions visible.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteQuick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
