YF-75D

YF-75D
Country of originChina
First flightLong March 5 inaugural flight (2016-11-03)
ManufacturerAcademy of Aerospace Liquid Propulsion Technology
Associated LVLong March 5
PredecessorYF-75
StatusIn service
Liquid-fuel engine
PropellantLiquid oxygen / liquid hydrogen
Mixture ratio6.0 (adjustable)
CycleExpander cycle
Configuration
Chamber1
Nozzle ratio80
Performance
Thrust, vacuum88.36 kilonewtons (19,860 lbf)
Chamber pressure4.1 MPa (590 psi)
Specific impulse, vacuum442.6 seconds (4.340 km/s)
Burn time780 seconds (13.0 min)
Used in
Long March 5 H5-2 second stage.
References
References[1][2]

The YF-75D is a cryogenic rocket engine burning liquid hydrogen and liquid oxygen in a closed expander cycle. It is China's third generation of upper stage cryogenic propellant engine, after the YF-73 and the YF-75. It is used in a dual engine mount in the H5-2 second stage of the Long March 5 launch vehicles. Within the mount, each engine can gimbal individually to enable thrust vectoring control.[1][3] As with its predecessor YF-75, the YF-75D can adjust its mixture ratio to optimize propellant consumption. As an additional improvement it can do multiple restarts, against the single one of its predecessor.[1]

The combustion chamber required a redesign to keep the power balance. Since the expander cycle uses the heat extracted from the cooling circuits to drive the turbines, the chamber had to be lengthened and the cooling passages redesigned. The engine uses a redesigned hydrogen turbine. It uses an axial two-staged low pressure ratio subsonic turbine that operates at 65,000 rpm, which is between the second and third critical speed. It rests on dual elastic support dampers around the ceramic ball bearings.[1]

  1. ^ a b c d Cite error: The named reference nan-2013 was invoked but never defined (see the help page).
  2. ^ Cite error: The named reference Development, application, and prospect of expander cycle engine technology was invoked but never defined (see the help page).
  3. ^ Cite error: The named reference sd-lm5 was invoked but never defined (see the help page).