Blok DM-03

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Blok DM-03
Manufacturer RKK Energia, JSC Krasnoyarsk Machine-Building Plant (since 1990)[1]
Country of origin Russia
Used on Proton-M
Associated stages
Family Blok D
Derived from Blok DM-2
Blok DM-SL
Comparable Briz-M
Launch history
Status Active
Total launches 3
Successes
(stage only)
1
Failed 1[note 1]
Lower stage
failed
1[note 1]
First flight 5 December 2010
Specifications
Engines RD-58MF
Fuel RP-1/LOX

The Blok DM-03 (Russian: Блок ДМ-03 meaning Block DM-03), GRAU index 11S861-03, is a Russian upper stage used as an optional fourth stage on the Proton-M carrier rocket. Two have been launched, the first in December 2010,[2] however as of July 2013 the stage is yet to be demonstrated in flight as both launches failed before fourth stage ignition, the first as a result of a problem with the Blok DM's fuel load.[3]

Initial versions of the Blok DM-03 are powered by a single RD-58M engine, fueled by RG-1 and oxidised by liquid oxygen. The last evolution is powered by the improved RD-58MF a less powerful but more efficient evolution of the venerable engine. It can carry 25% more propellant than the Blok DM-2, which it replaced as a Proton upper stage for some government launches.[3] However most government launches and all commercial missions use the Briz-M instead. The payloads for the first two Blok DM-03 launches were groups of three Uragan-M satellites for the GLONASS programme, with further missions slated to carry three more Uragan-M satellites, and two Ekspress satellites on separate launches. The Blok DM can inject payloads into orbit more accurately than the Briz-M,[4] making it better suited for launching satellites such as the Uragan-M which lack apogee motors.

When production ended in 2012, five Blok DM-03 stages had been produced by RKK Energia, for use on Proton and potentially Zenit rockets.[3] A new version of the upper stage is expected to be introduced once the five launches are complete;[5] all five DM-03s have been slated for Proton launches between 2010 and 2015. During a November 2014 interview, Vladimir Kolmykov, the Deputy General Director of the Chemical Division of Krasnoyarsk Machine-Building Plant, stated that the production of Block-DM was suspended during that year, but work on the stage and development of the RD-58MF resumed during 2015.[6]


Versions

The development for the 11S861-03 stage is covered under the Dvina-DM (Russian: Двина-ДМ) program. The specifications of this program (Technical requirements on development work «Modernization of the upper stage «DM» for the carrier rocket heavy class») defines three different evolutions of the 11S861-03 stage:[7]

  • 11C861-03 Phase I Version 1: This version main task is the enlargement of the propellant tank with minimum modificaitons. The target performance metric is 3,000 kg (6,600 lb) to GEO and 5,500 kg (12,100 lb) to a 1,500 m/s (4,900 ft/s) GTO. Its improvements is:
    • Increase of tank size to 18.7 m (61 ft).
  • 11C861-03 Phase I Version 2: This version will introduce general performance improvements. The target performance metric is 3,200 kg (7,100 lb) to GEO and 6,000 kg (13,000 lb) to a 1,500 m/s (4,900 ft/s) GTO. Its improvements are:
    • Replacement of the avionics and instrumentation enclosures.
    • The use of advanced control unit.
    • Replacement of the Navigation and Telemetry systems Chezara Kvant-VD (Russian: Чезара Квант-ВД).[8]
    • Adapted for using the Proton-M's fairing type 14S75 of 4,350 mm (171 in).
    • Structural improvements to reduce the dry weight.
  • 11C861-03 Phase II: This change will finally apply the new propulsion unit: The target performance metric is 3,600 kg (7,900 lb) to GEO and 6,600 kg (14,600 lb) to a 1,500 m/s (4,900 ft/s) GTO. Its improvements are:
    • Switch engines to the 11D58MF.
    • Use the main engine for RCS and ullage.
    • Structural weight reduction.

In 2014 RSC Energia designated two versions: 14S48 Persei (Perseus) and 14S49, which incorporated most features of the proposed 11C861-03 Phase II, including the use of nontoxic propellants in auxiliary propulsion systems and new compact flight control system. The 14S48 will use an 11D58M engine, while the 14S49 will apply the new-generation 11D58MF engine.[9]

Launches

s/n Rocket Launch date Payload Outcome Remarks
1L Proton-M[10] 2010-12-05, 10:25:19 UTC[11] Uragan-M No.39
Uragan-M No.40
Uragan-M No.41
Not fired
Cause of failure
Launch failure before Blok DM-03 ignition; Blok DM-03 overfuelled leaving rocket too heavy to achieve parking orbit, reentered before stage 4 ignition
2L[4] Proton-M 2013-07-02, 02:38:22 UTC[12] Uragan-M No.48
Uragan-M No.49
Uragan-M No.50
Not fired Launch failure before Blok DM-03 ignition; first stage guidance failure, loss of control shortly after liftoff
Proton-M 2015-09-14, 19:00 UTC[13] Ekspress-AM8 Successful
Proton-M 2016 Elektro-L No.3 Planned[10]
Proton-M 2016 Uragan-M (x3) Planned[10]

Failures

As of Sep 2015, 3 Proton-M/Blok DM-03 have been launched, of which 2 have failed. In the 2010 failure, the rocket was too heavy to reach orbit and reentered the atmosphere during a coast phase between the end of third stage flight and the beginning of the Blok DM-03's first burn, whilst the 2013 flight failed after the rocket went out of control seconds after liftoff.[12]

The first launch to use the Blok DM-03 was conducted on 5 December 2010, from Site 81/24 at the Baikonur Cosmodrome. The rocket was expected to deploy three Uragan-M satellites for the GLONASS constellation, with the first three stages of the Proton placing the Blok DM and payload into low Earth orbit, and the Blok DM then propelling the satellites into their operational medium Earth orbits. During preparations for launch, the Blok DM-03 was fuelled using instructions intended for the Blok DM-2, which included an instruction to fill the tanks to 90% capacity.[3] Owing to the DM-03's larger tanks, this was more propellant than needed for the mission, and left the rocket too heavy to achieve orbit. The Blok DM, with payload still attached, reentered over the Pacific before the start of its scheduled first burn.[3] Following the failure, the Blok DM-03 was grounded for further tests, with a Proton-M/Briz-M and several smaller Soyuz-2 rockets being used for GLONASS launches over the next 30 months.[4]

The July 2013 flight, which marked the Blok DM-03's return to flight was another GLONASS launch, also conducted from Site 81/24, with liftoff occurring on time at 02:38:22 UTC. The rocket went off course almost immediately, before disintegrating. The payload fairing and upper stage were among the first parts of the rocket to detach. Debris fell around 1,000 metres (3,300 ft) from the launch pad, with the parts of the rocket still intact exploding upon impact. An investigation determined that three first stage yaw sensors had been installed backwards, resulting in the failure of the vehicle's guidance system.[12]

See Also

Footnotes

  1. 1.0 1.1 Although the December 2010 launch failed before the Blok DM-03 was scheduled to perform its part of the flight, the stage's incorrect fuel load was discovered to have caused the failure

References

  1. Lua error in package.lua at line 80: module 'strict' not found.
  2. Lua error in package.lua at line 80: module 'strict' not found.
  3. 3.0 3.1 3.2 3.3 3.4 Lua error in package.lua at line 80: module 'strict' not found.
  4. 4.0 4.1 4.2 Lua error in package.lua at line 80: module 'strict' not found.
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. Lua error in package.lua at line 80: module 'strict' not found.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. Lua error in package.lua at line 80: module 'strict' not found.
  10. 10.0 10.1 10.2 Lua error in package.lua at line 80: module 'strict' not found.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. 12.0 12.1 12.2 Lua error in package.lua at line 80: module 'strict' not found.
  13. Lua error in package.lua at line 80: module 'strict' not found.
  14. Lua error in package.lua at line 80: module 'strict' not found.