New Rocket Engine Successfully Tested
inetsee writes "XCOR Aerospace announced that their new methane-oxygen rocket engine has been tested successfully. This is reported to be the first successful test of an engine using the combination of methane and oxygen as fuel. The fuel has higher specific impulse than kerosene and oxygen, but until now has been thought to have too much 'technology risk'."
Comment removed based on user account deletion
There hasn't been much use, because rocket design has been on a different track than XCOR. Kerosine engines are primarily used for their high thrust to weight ratios, which help get a rocket off the ground. Once the rocket is in flight, the first stage is usually dropped in favor of a more powerful engine, such as Liquid Hydrogen/Oxygen engines. LHOx has the highest specific impulse of any fuel deployed to date; even more efficient than the methane-oxygen engines they're proposing.
The problem is that XCOR is working on a different track than NASA and the large rocket manufacturers. They're focusing on winged takeoff and landing, where high thrust to weight ratios aren't as important, and can be sacrificed for greater efficiency. (For comparison, the kerosine F-1 engines on the Saturn V produced 1.5 million lbf compared to the 7,500 lbf targetted by this engine.) So the methane-oxy engine development has less to do with politics, and more to do with the practical matters of meeting the targetted design goals.
Javascript + Nintendo DSi = DSiCade
...and the cow jumped (?) over the moon...
NASA only has so much money to spread around to different projects -- and much of where it goes is mandated by congress. Consequently, there's only so much engine research that they can finance.
Methane engines are interesting, but they're no panacea. Methane lines on the spectrum between kerosene (dense, comparatively high temperature, moderate ISP) and hydrogen (sparse, extremely low temperature, high ISP). Specifically:
Hydrogen@20K: 70kg/m^3 (fuel**), 358kg/m^3 (bulk**), 455.9 (ISP sec@100:1/20MPa)
Methane@112K: 423kg/m^3 (fuel), 801kg/m^3 (bulk), 368.3 (ISP sec@100:1/20MPa)
Kerosene-based (RP-1)@298K: 820kg/m^3 (fuel), 1026kg/m^3(bulk), 354.6 (ISP sec@100:1/20MPa)
Note that it's a rather small ISP gain over kerosene -- not close to the performance of hydrogen -- yet its density is halfway between kerosene and hydrogen. While a small gain in ISP can be a big boost in performance, that's a pretty big density hit.
A fuel that I find interesting is propane. While at its boiling point, it's not that interesting:
Propane@231K: 582kg/m^3 (fuel), 905kg/m^3 (bulk), 361.9 (ISP sec@100:1/20MPa)
But cool it to 100K, and you get:
Propane@100K: 782kg/m^3 (fuel), 1014kg/m^3 (bulk), 361.9 (ISP sec@100:1/20MPa)
Not only are these attractive numbers, but since the propane is similar in temperature to the LOX, they can share a common bulkhead. Of course, it can't go too much below that, or its viscosity will rise too much (at 100K, it's similar to kerosene).
To make methane significantly more dense, you have to go pretty darn cold (well below your LOX temps), and it's probably not worth hydrogen complexity for a fuel with an ISP like methane.
** - Fuel density is the density of the fuel alone. Bulk density is the density of the fuel plus stochiametric amounts of liquid O2.
Yes, I've read a poem. Try not to faint.
Sure you could do that... if your goal was to simulate the blast effects of a small nuclear explosion.
Different kind of risk.
The risk being talked about here is program risk... ie... the risk that using unproven technology will result in cost and schedule impacts to the project due to unforeseen problems. Not the risk of things going boom (although that can impact cost and schedule too... XD) Using proven, well-understood technologies reduces risk.
Think of it this way... if you're given a task to develop a program for $C dollars inside of Y months, are you going to use a well-established programming language or are you going to go with some new half-developed (but really nifty) one where you're playing debug the compiler as you work on your project?
Nope. It's so that the hearing impaired can enjoy them, too.