Kolesov RD-36
family of Soviet supersonic turbojet engines

The Kolesov RD-36 was a supersonic turbojet engine used on various Soviet aircraft projects.
Design and development
Developed at OKB-36 (P. A. Kolesov) and produced at the Rybinsk Motor-Building Plant, the RD-36-51A engine was developed for the Tu-144D supersonic passenger aircraft. A simplified version with a fixed nozzle for the high-altitude Myasishchev M-17 was designated RD-36-51B. The engine developed a thrust of 7,000 kgf (15,000 lbf; 69,000 N).
The RD36-51A engine passed all state bench and flight tests in 1973–75 (with flight testing on the Tu-144D).
The engine's specifications were:
Maximum thrust at take-off = 20,000 kgf (44,000 lbf; 200,000 N)
Maximum thrust during supersonic cruise = 5,000 kgf (11,000 lbf; 49,000 N) altitude = 18,000 m (59,000 ft), speed = 2,350 km/h (1,460 mph)
Maximum thrust during subsonic cruise= 3,000 kgf (6,600 lbf; 29,000 N) altitude = 11,000 m (36,000 ft), speed = 1,000 km/h (620 mph)
Temperature = 1,355 K (1,082 °C; 1,979 °F)
Diameter = 1,486 mm (58.5 in)
Length = 5,976 mm (235.3 in)
Weight = 3,900 kg (8,600 lb)
For the high-altitude M-17 "Stratosphera" aircraft (NATO reporting name Mystic-A) a single-shaft TRD RD36-51B was created. This was a modified version of the RD36-51A engine with an unregulated nozzle and oxygen supply to the combustion chamber. The engine provided long-duration operation at an altitude of 26,000 m (85,000 ft) at low flight speed (M = 0.6).
P = 7,000 kgf (15,000 lbf; 69,000 N)
With beats. vsl. = 0,88 kg / kgf • h.
Begin with the source’s own compact description: “Kolesov RD-36” is family of Soviet supersonic turbojet engines. The dossier treats that line as a proposition to test through Kolesov, RD-36 and family, not as a finished interpretation.
Why this record matters
The phrase “family of Soviet supersonic turbojet engines” supplies a clear boundary for inquiry. It also exposes the unanswered questions: who defined that boundary, when it became stable and which sources sit outside it.
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 Mar 26, 2026. The linked authority identifier is Q20900407. None of the 0 selected statements returned an explicit reference. The first chronological checks are 1973.
The absence of detail may reflect summary conventions rather than a lack of surviving documentation. 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 “Kolesov RD-36”, its source revision and the description used here.
- Expand the search: follow Kolesov RD-36 primary sources, Kolesov RD-36 archive and Kolesov 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 “Kolesov RD-36”?
- Which institution is responsible for the underlying evidence?
- Which cited source is closest to the event, object or claim?
Search terms from this dossier
This entry incorporates text from “Kolesov RD-36” 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.