Non-availability of liquid Hydrogen reason for GSLV-D3 failure | india | Hindustan Times
Today in New Delhi, India
Jun 23, 2017-Friday
-°C
New Delhi
  • Humidity
    -
  • Wind
    -

Non-availability of liquid Hydrogen reason for GSLV-D3 failure

India's GSLV rocket which was to have tested the indigenous cryogenic engine for the first time failed in its mission due to non-availability of liquid hydrogen supply to the thrust chamber of the main engine, according to ISRO.

india Updated: Jul 09, 2010 19:13 IST

India's GSLV rocket which was to have tested the indigenous cryogenic engine for the first time failed in its mission due to non-availability of liquid hydrogen supply to the thrust chamber of the main engine, according to ISRO.

The third developmental flight of Geosynchronous Satellite Launch Vehicle failed within five minutes after a perfect lift-off from Sriharikota on April 15 this year and the rocket fell into the sea in a setback to India's space programme.

The flight of GSLV-D3 primarily meant for flight testing of indigenously developed Cryogenic Upper Stage (CUS) had failed to achieve the mission objectives following which ISRO had instituted a two-tier process to carry out an in-depth analysis of the flight performance and identify the causes of failure and recommend corrective measures.

As per review of the findings by the Failure Analysis committee--a 'National Group of Eminent Experts'--though the ignition of the CUS main engine and two steering engines were confirmed normal, the thrust build up did not progress as expected "due to non-availability of liquid hydrogen (LH2) suppy to the thrust chamber of the main engine", an ISRO release said today.

Following the review, "a series of confirmatory ground tests are planned", the release said

After incorporating necessary corrective measures, the flight testing of Indigenous Cryogenic Upper Stage on GSLV is targeted within a year.

In the meantime, the next two GSLVs would fly with the available Russian Cryogenic Stages, it said

The failure is attributed to the anomalous stopping of Fuel Booster Turbo Pump (FBTP).The start-up of FBTP was normal. It reached a maximum speed of 34,800 rpm and continued to function as predicted after the start of CUS. However, the speed of FBTP started dipping after 0.9seconds and it stopped within the next 0.6 seconds,it said.

Two plausible scenarios have been identified for failure of FBTP, gripping at one of the seal location and seizure of rotor and a rupture of turbine casing caused probably due to excessive pressure rise and thermal stresses, it said.

As per the review, following a smooth countdown, the lift-off took place at 1627 hrs (IST) as planned. All four liquid strap-on stages (L40), solid core stage (S139), liquid second stage (GS2) functioned normally.

The vehicle's performance was normal up to the burn-out of GS-2, that is, 293 seconds from lift-off.

Altitude, velocity, flight path angle and acceleration profile closely followed the pre-flight predictions. All onboard real time decision-based events were as expected and as per pre-flight simulations, the release said.

The navigation, guidance and control systems using indigenous onboard computer Vikram 1601 as well as the advanced telemetry system functioned flawlessly.

The composite payload fairing of 4 metre diameter inducted first time in this flight, also performed as expected. Performance of all other systems like engine gimbal control systems and stage auxiliary systems was normal,it said

The initial conditions required for start of the indigenous Cryogenic Upper Stage (CUS) were attained as expected and the CUS start sequence got initiated as planned at 294.06 seconds from lift-off.