Rohini (rocket family)
series of sounding rockets developed by India
Rohini is a series of sounding rockets developed by ISRO for meteorological and atmospheric study. These sounding rockets are capable of carrying payloads of 2 to 200 kilograms (4.4 to 440.9 lb) between altitudes of 100 to 500 kilometres (62 to 311 mi). The ISRO currently uses RH-200, RH-300,Mk-II, RH-560 Mk-II and RH-560 Mk-III rockets, which are launched from the Thumba Equatorial Rocket Launching Station (TERLS) in Thumba and the Satish Dhawan Space Centre (SDSC) in Sriharikota.
Various programs such as Equatorial ElectroJet (EEJ), Leonid Meteor Shower (LMS), Indian Middle Atmosphere Programme (IMAP), Monsoon Experiment (MONEX), Middle Atmosphere Dynamics (MIDAS), and Sooryagrahan-2010 have been conducted using the Rohini sounding rocket series. It has been the forerunners for ISRO's heavier and more complex launch vehicles, with continued usage even today for atmospheric and meteorological experiment and research.
Currently, three versions are offered as operational sounding rockets, which cover a payload range of 8-100 Kg and an apogee range of 80-475 km.
Several scientific missions with national and international participation have been conducted using the Rohini sounding rockets.
Brief history
On November 21, 1963, the American Nike-Apache was the first sounding rocket to launch from Thumba. Following that, two-stage rockets from France (Centaure) and Russia (M-100) were launched. In 1967, the Rohini RH-75, an ISRO variant, was launched.
“Rohini (rocket family)” enters the record as series of sounding rockets developed by India. Crown Archives preserves that source wording while asking what Rohini, rocket and family can confirm, complicate or overturn.
Why this record matters
“Rohini (rocket family)” is worth following because a concise public description often conceals a longer documentary argument. Here, Rohini, rocket and family provides the most credible route into that argument.
Vocabulary and entity names are the principal evidence signals here, because they determine the precision of every later search. The source revision retrieved here is dated Sep 22, 2026. The linked authority identifier is Q7359744. None of the 0 selected statements returned an explicit reference. The first chronological checks are 2010, 1963 and 1967.
A concise general-reference account can conceal disagreements about scope, terminology or the weight assigned to individual sources. 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
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Rohini (rocket family)”, its source revision and the description used here.
- Expand the search: follow Rohini (rocket family) primary sources, Rohini (rocket family) archive and Rohini 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 “Rohini (rocket family)”?
- Which institution is responsible for the underlying evidence?
- What terminology or title could unlock a more precise catalogue search?
Search terms from this dossier
This entry incorporates text from “Rohini (rocket family)” 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.