blank2

Follow Us

Teal Group gathers, classifies, and analyzes information from a wide range of sources. Our analysts publish News Briefs several times a year. Subscribe via email to receive each News Brief when it is published or join our mailing list to receive updates quarterly.

View All News Briefs     Subscribe Via Email     Join Mailing List

30 October 2014

So What's Wrong With 40-Year Old Russian Engines?

Marco A. Caceres, Senior Space Analyst

So What's Wrong With 40-Year Old Russian Engines?

The cause of Tuesday's Antares 130 launch failure is not known. The builder and owner of the rocket, Orbital ATK, will lead an investigation of the accident, and it will be assisted by NASA and the FAA. All that is known for sure at this point was tweeted by Orbital ATK: "There has been a vehicle anomaly. The vehicle suffered a catastrophic failure."

Uh, yeah. That much seems painfully self-evident.

So what likely went wrong? Well, we know that the failure occurred 6-10 seconds after liftoff from Launch Pad-0A at the Mid-Atlantic Region Spaceport at Wallops Island, Virginia. We know that the first stage of the Antares is powered by two AJ26 engines, which are fueled by liquid oxygen (LOX) and kerosene (RP-1). We know that the burn time for the first stage is approximately 230-235 seconds, which means that we can exclude any problems with the second stage or the stage separation phase of the flight -- which is often when things tend to go wrong with rocket launches.

So the focus is on the first stage and its two engines. Usually, when a launch goes wrong just a few seconds after liftoff, the problem has something to do with an engine. Perhaps a fuel leak or a clogged fuel line.

For example, the explosion of the Sea Launch Zenit 3SL 3.9 seconds after liftoff on January 30, 2007 was caused by a malfunction of the vehicle's first stage engine, which was believed to have become clogged with debris -- possibly from the engine itself. Note that the failure of a Russian Proton M rocket in 1999 was traced to a second stage fire which was started by a stray aluminum particle in the engine caused by a faulty weld. Poor workmanship.

Another example was the failed launch of SpaceX's Falcon 1 on March 24, 2006, which occurred about 25 seconds after liftoff. An investigation attributed the failure to a fuel leak, which may have been caused by a broken B-nut on the engine's fuel pump inlet pressure transducer. The aluminum nut, designed to hold the fuel pipe fitting in place, is believed to have failed due to "inter-granular corrosion". In other words, stress may have led to structural cracking, which in turn caused fuel to leak onto the engine -- which then, of course, caught fire.

We know that the AJ26 engines were built by the Kuznetsov Design Bureau of Russia in the 1960s. But the engines -- originally designated NK-33 -- were bought by Aerojet Rocketdyne of California in the 1990s and completely refurbished, tested, and qualified, then sold to Orbital ATK. Lots of welding work, replacement of fuel lines, electronics upgrades, steering system modifications, and qualifying for US propellants. So, in essence, what was old was made new. Well, kind of. There's still just no getting around the fact that the engines were first built over 40 years ago.

There's also no getting around the fact that on May 22, 2014, an AJ26 engine undergoing "hot-fire" testing at the NASA Stennis Space Center in Mississippi failed, and may have even exploded. An investigation was conducted, but the results have apparently not been released to the public. But we do know that another AJ26 tested at Stennis in June 2011 also failed and caught fire. According to an article by Chris Bergin on the NASA Spaceflight.com website, "The fire was caused by a kerosene fuel leak in an engine manifold, with the root cause subsequently determined to be stress corrosion cracking of the 40-year old metal."

It will take days, maybe even weeks to determine the exact cause of the failed Antares launch. At the moment, though, it looks to me like that ol' Russian engine's got some issues.

About the Author

Marco A. Cáceres

Marco A. Cáceres

Marco joined Teal Group in March 1990. Previously, he was a market analyst for Jane's Information Group of the UK. As editor of both the Jane's DMS Defense & Aerospace Agencies and DMS Electronic Systems publications, Marco analyzed and wrote about the R&D and procurement activities within the defense- and aerospace-related agencies of the federal government, with a focus on the markets for major electronic warfare (EW) subsystems. Additionally, Marco edited Jane's DMS Budget Intelligence newsletter -- a weekly covering defense budget news.

Teal Group offers online access to all our products through the web. Contact our Sales Staff to obtain a user ID and password for online access. Instructions for accessing the Online Demo are found below. You will only have access to the Online Demo product. You will need Adobe Acrobat Reader to read the reports on the online access site.

logon demoDEMO INSTRUCTIONS

  1. Log on using Demo User ID 2306 and Demo Password teal.
  2. A list of Teal Group Products will appear on the next screen.
  3. You will have access to the online demo and you will be able to see what is available in other services. Accessible reports will appear as clickable text in red under the Title of the Briefing. You will not be able to access reports in unsubscribed services. These report titles will appear as normal text in black.
  4. Click on "Online Demo". The various briefing titles will appear. Click on a section and the sample reports in that section will appear. At this point you can click on the sample report to access the file.

 

To inquire about online access and site licenses please contact Mr. Tim Storey.