HMIS Indus
1934 Grimsby-class sloop-of-war
HMIS Indus was a Grimsby-class sloop of the Royal Indian Navy launched in 1934 and sunk during the Second World War in 1942. She was a slightly enlarged version of other vessels in the Grimsby class. She was named after the Indus River. Indus served mainly as an escort vessel, and she was therefore lightly armed. Her pennant number was changed to U67 in 1940.
History
Indus was a part of the Eastern Fleet during the war.
In March 1942, British Indian Army and British Army troops from Rangoon had to be withdrawn, as they were overwhelmed by the superior numbers as well as the air command of the Japanese. Akyab was the next port to be attacked by the Japanese in April. Despite this, the Flag-Officer-Commanding of the Eastern Fleet refused to withdraw Indus and Sutlej from the anti-infiltration patrol off Akyab.
Fate
On 6 April 1942, Indus was bombed and sunk by Japanese Mitsubishi G3M bombers off Akyab, Burma in position 20°7′N 92°54′E. She suffered 3 direct bomb hits and sank in 35 minutes.
The public source identifies “HMIS Indus” as 1934 Grimsby-class sloop-of-war. This brief keeps that definition visible, then builds a research path around HMIS, Indus and Grimsby-class.
Why this record matters
A short description can identify a subject without explaining its stakes. For “HMIS Indus”, the useful work is to connect “1934 Grimsby-class sloop-of-war” to the records capable of establishing context and consequence.
The record creator and administrative purpose are central evidence, because official documentation reflects both action and institutional priorities. The source revision retrieved here is dated Sep 15, 2026. The linked authority identifier is Q5631035. Authority coordinates are 20.117, 92.900. 1 of 1 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 1934, 1942 and 1940.
Later summaries often reconcile disputed chronology or motive more neatly than the contemporary record permits. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Compare institutional narratives with records created by participants and affected communities. Dates and formal titles are useful anchors, but not substitutes for context.
- Event chronology
- Institutional context
- Locating named record creators
Contemporary correspondence, government or organizational records, oral histories and cited historical scholarship.
Three-step research path
- Establish the record: confirm the title “HMIS Indus”, its source revision and the description used here.
- Expand the search: follow HMIS Indus primary sources, HMIS Indus archive and HMIS research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “HMIS Indus”?
- What chronology connects this entry to wider political or social change?
- Which voices are present, absent or mediated by the institution?
Search terms from this dossier
This entry incorporates text from “HMIS Indus” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.