Quote from: ChrisWilson68 on 08/14/2016 07:28 pmJohn Smith 19 accused me of making a strawman argument. In response, I listed several posts where he and others made the argument I was disputing, showing my argument wasn't a strawman argument.Except the quotes you gave didn't make the argument you claimed they were making. I believe he strawman argument it was claimed you were making was not the pre-cooler is a critical component of SABRE, and SABRE is a critical component of Skylon, but that once the pre-cooler was 'solved' everything else would succeeded if given the specified money. I recognise that it wasn't explicitly stated to be the case, but you'd have to be trolling to insist it was about the pre-cooler.So the first two quotes are about the pre-cooler being important to Skylon, which it is (or at least all versions of the engine so far. Frost control, it seems, was only important to the first three).
John Smith 19 accused me of making a strawman argument. In response, I listed several posts where he and others made the argument I was disputing, showing my argument wasn't a strawman argument.
The third quote is slightly ambiguous - from context I'd say it was SABRE that "it" referred to - but even if "it" was Skylon the "if it performs as expected" as a qualifier to me quite clearly means it isn't taken for granted it would succeed give the required money.
The fourth quote is an opinion about REL's appraisal of their capability to build the engine, not Skylon. Even if it were about Skylon, it makes no claim as to REL's actual ability, only their assessment.
The fifth quote, I think, is the closest to your characterisation, but the first half is again about pre-coolers and the second part says a lot of Sklyon isn't new - not that none of it is new.The sixth quote would only back up your characterisation of the argument if you think John Smith 19 believes SpaceX were guaranteed to succeed, or than managing risk means eliminating it.
I was assuming they were drawing the line right on M5 while in the atmosphere.
[Re: MUSTARD] if 2 stages are not identical you more than double the budget
I can see a TSTO architecture where the staging Mach number is gradually raised, lowering the gross weight of the 2nd stage or increasing its payload up to the structural and thermal limits of the 1st stage carrier. [...]
It just seems like overkill once you've built a fully orbital engine to not use it as such.Looking deeper into it I just can't see the architecture.
I know you hate the launch-vehicle-like-an-aircraft analogy but no one has ever built a large 2 stage cargo aircraft, despite the benefits of an enormous 1st stage to get a heavily loaded (and fueled) 2nd stage off the runway and airborne.
Perhaps we could bypass all this discussion of what people meant in past posts by just asking this question: Do you now agree with this statement: "The pre-cooler was the only significant risk of a technological showstopper for Skylon. I consider the pre-cooler to have been proven and therefor there is not a substantial risk of a showstopper being found that makes Skylon impossible. Given enough time and money, Skylon is highly likely to succeed."If there aren't any people who agree with that statement, we can avoid a whole lot of arguing by agreeing that there are still significant technological unknowns for Skylon that could cause it to be infeasible.
agreeing that there are still significant technological unknowns for Skylon that could cause it to be infeasible.
Can you understand that it is going to be structurally easier on the airframe, and structurally and thermally easier on the TPS, if Skylon was re-entering the atmosphere on a sub-orbital ballistic trajectory at Mach 6 or even Mach 10, compared to coming in at Mach 20+ orbital velocity? Can you understand that "easier on..." also means "easier to design"? And that "easier to design" means "cheaper to design"? And that "cheaper" means both sooner and vaster more likely to be funded.At Mach 6, you are dealing with just 25% of the kinetic energy of Mach 20. At Mach 4, just 10%.The only way for SSTO-Skylon to be cheaper to design and develop than Skylon-as-a-first-stage is if they've zeroed that difference. Not "reduced by", not "optimised for", but zeroed.
I note that this vacancy has been on offer since the end, I think, of July: http://www.reactionengines.co.uk/careers_035markcommsmanager.htmlI'm sure we're all looking forward to seeing it filled :-)
This isn't really news but it's an interesting video about the testing of the ED nozzles:
Eh, no. Because it could be VERY likely that the prospective customer WANTS a TSTO powered by SABRE because he fully understands what he WANTs to get and those pushing SABRE as usable only on an SSTO airframe are unaware of, or just don't care what the CUSTOMER wants or needs. Saying it's illogical[/] is an attempt to 'intimidate' the argument into arriving at the preferred conclusion rather than actually using, you know, 'logic' and more importantly customer/market inputs which may in fact be the opposite of your own!
JS19 and others are simply making some assumptions that not even REL has made based on some assumptions that REL has made which pertain to operations and economics which themselves are based on some limited modeling for a specific outcome. And outcome which actually hasn't reflected the actual market or business planning needs of known users for several decades. REL knows this as they have been playing with words since the start to cover this point which is one of the reasons people have general doubts about how serious REL is and what, exactly, they are attempting to sell.
Eh, again, that's not really accurate as the CoG and CoL shifts are well known and can be effectively countered with a number of configurations. I know you're aware of all the aerospace work on airframe design done over the decades and controllability of the various designs was only an issue with one specific rather recent design concept that started with some fundamental flawed assumptions. (And no we aren't talking NASP as aerodynamically it was fine, the main problems were unrealistic propulsion assumptions and requiring flying inside the atmosphere at Mach-25 in order to 'justify' afore mentioned propulsion system)
Any configuration which places its propulsion system near the CoG/CoL interface tends to negate the severity of the shift during high speed flight in a aerodynamic, lifting trajectory. Most combined cycle propulsion system vehicles are designed in this manner for that reason.
I know this was mentioned but can't find it but that's the main reason the engines are on the wingtips because by placing them there you can in fact simply change certain assumptions and values and arrive at nearly the same outcome at the checkpoints along the flight trajectory without having to make significant changes to the overall "design" which has far to many 'down-stream' effects in any other position. "Skylon" is not an optimized design by any means and as e of pi points out the dry mass is optimistic to say the least, especially for a vehicle that is supposed to be able to be rapidly turned and serviced. Significant mass growth from design to operation is a given unless someone is willing to spend a LOT of money on materials and technology and that's not (as we're all well aware) very often conducive to economic construction or operation.
I seem to recall that the "Skylon" design can handle up to 15% lower engine performance and still be able to meet the given design goals. (I'll be corrected if I'm wrong, probably several hundred times I'm sure ) I thought I'd mentioned this but if so it probably got lost, but while that's a good margin it's actually not the one that people who actually design vehicles tend to be worried about. (A worry but not THE worry in other words)
http://www.sciencedirect.com/science/article/pii/S0094576509004998
Ballpark inert mass growth during development can be anywhere from 10% (highly unlikely) to 50% (same) but is averages around 20% to 30% which also cuts into your margins.
5% engine short-fall and 25% inert mass growth combined means "Skylon" has no payload, not to orbit anyway and there are standardized formulas for figuring a rough set of growth parameters for a vehicle design. I'm betting REL used them too. It doesn't really matter because aerospace designers and manufacturers use them too, for very preliminary designs and they rarely carry over to the actual vehicle.
And the bigger the vehicle the more likely for mass growth is. (Yes in some ways a bigger vehicle can absorb more and it averages out but as always ANY SSTO design is more sensitive to the combined factors. Less than a pure-rocket VTVL SSTO but it is not inconsequential. And yes a two or more stage design is also susceptible to mass growth but it actually starts with higher margins to begin with)
The main point of SSTO has always been based on the idea that a single-stage would be more economic to operate and in fact the amount of payload delivered, and where it is delivered is secondary. That turns out to be quite opposite of the requirements of the people who would be using them though. SSTO's, or pretty much any LEO orbital deliver systems, require to carry or be paired with on-orbit infrastructure, (usually in the form of some sort of Space-Tug or carried propulsion stage, Skylon's US, Shuttle Centaur, Shuttle Agene and PAM being examples) to meet market/customer requirements while, (obviously) multi-stage vehicles have this capability inherent. This is why straight up comparisons rarely work.
Your premise would seem to be fundamentally flawed. Nothing in JS19's post shows that SABRE is "stupid" to use in a TSTO design he simply STATES that it is by inferring it is ONLY capable of being used in that role with no supporting evidence.
(He's also got an issue with inferring that it is the ONLY system capable of doing so which is also unsupported)
Nothing inherent in the SABRE prevents its use in a TSTO vehicle and REL has stated that it's not an optimum solution but have never given the impression that it's "stupid" or impossible. The main issue is that there is an assumption that a TSTO would not use the SABER in a similar manner to an SSTO for portions of the flight.Which parts can SABRE not do?
Further and probably more importantly Alan Bond (and this is NOT a dig or dissing him) is NOT actually a aerodynamics or spacecraft engineer, he's a mechanical and propulsion engineer. Lets be clear at least. No one at REL is in fact an experienced hypersonic aircraft designer or engineer (and there ARE a lot of those around) and the Skylon is "designed" to fulfill a set of criteria based on certain assumptions using the simplest possible vehicle design and standard DSMC modeling without that experience and expertise.
Given the fact that Skylon as designed is only a very low resolution basic vehicle design for calculations of what is possible with the assumed performance of the SABRE engine the work done is sufficient to show that if the all the assumptions hold up the design is probably viable in basic function.
That does not translate to being viable or even desirable until a lot more 'variables' have been defined completely by people who have the applicable skill sets.
QuoteWhen people propose something smart/reasonable alternative to skylon, like different aerodynamic configuration for SSTO craft using SABRE, they are treated wellHave you actually read and understood what that paper is about? First of all it's essentially attempting to use a greatly simplified aero-heating program in place of the standard, more complex one in regards to a "simple" aerodynamic shape as compared to a more "complex" one. (Bottom line is if you're going for very simple and quick calculations as long as you keep in mind the variables and limitations and there are a lot of them, the new program works to a degree) Secondly note that the configuration changes were to make "concessions to ease manufacturing and structural efficiency" but that it is essentially a re-skinned Skylon with more efficient aerodynamic design.The paper doesn't show much new as REL was/is well aware that the Skylon is NOT an optimized design but a general one. It has issues which will require someone with more time, money and engineers to address sufficiently. And once having done so the result may (probably in fact) will look very little like the Skylon as currently designed.Despite the look the cFASST-1 design changes very little of the basic Skylon design and already (this is shown both with the simpler HyFlow and the more complex and encompassing DSMC models) large changes are observed. It is obvious that more fundamental changes using well known high-speed/hypersonic methods will yield equally large changes and efficiencies.For example:Note the engines remain in the same place on cFASST. That is NOT because that is the only place that SABRE will work, nor is it because that position is the perfect position for an air breathing engine because it's very much not. Again it's to keep the calculations and formula simple so there is no need to calculate airframe/engine interaction. Experts are well aware that there are large increases in efficiency when engines and airframe are more integrated than when they are not, but the interaction also gets very complex very quickly. This is not in fact a bad thing as the more integrated the engines/airframe the greater efficiency overall both have. (For example both inlet and exhaust design gets simpler and overall propulsion efficiency increases when you can use the airframe as part of the system. It can cost some complexity in airframe thermal management but it can yield double digit efficiency % in overall performance)
When people propose something smart/reasonable alternative to skylon, like different aerodynamic configuration for SSTO craft using SABRE, they are treated well
None of this precludes the design from being used in a TSTO launch system. The paper notes that "Optimization to include low-speed, low altitude flight will almost inevitably result in a configuration that is at least partially aircraft like and thus a vehicle which geometrically is more complex than space vehicles that have been designed in the past." That's very true but if you follow that logically then the conclusion also follows that something designed to be optimized for one regime will, by it's nature, NOT be optimized for different regimes. So compromises will be required at various points to allow a single airframe to cover all regimes.
Whereas two vehicles both optimized for different regimes can, when used in combination be more efficient than a single vehicle.Staging gets more efficient the higher and faster it's done. A SABRE powered lower stage, air breathing to @Mach-5 before switching to pure rocket can then accelerate outside the effective atmosphere to speeds approaching Mach-10 before releasing a space/very-high hypersonic optimized stage that carries the payload to LEO and beyond. Nothing in the SABRE design prevents this from being possible and it may in fact happen when the actual people who will be building the airframe get done with the trades and design studies.
True, but GTO is only part of the market and it's very challenging. Using the Skylon Upper Stage splits the design problem into the very tough part (Earth to LEO) and the relatively well understood process of going from LEO to GEO.
Fair point I was assuming they were drawing the line right on M5 while in the atmosphere. And I know what happens when you assume. If you want to go higher and above then SABRE would be the option. I was also thinking that this is already covered in the DARPA XS-1 programme. I was also recalling that REL are aware of the results of the cost modelling in the MUSTARD programme, specifically that if 2 stages are not identical you more than double the budget, because not only do you need their development and engineering budgets, you need one to cover the combined interactions of the stages.
I can see a TSTO architecture where the staging Mach number is gradually raised, lowering the gross weight of the 2nd stage or increasing its payload up to the structural and thermal limits of the 1st stage carrier. But a reusable 2nd stage will still need the full orbital rated TPS anyway while an expendable 2nd stage will never give the cost per flight level of a fully reusable system.
That's fair also. It just seems like overkill once you've built a fully orbital engine to not use it as such. Looking deeper into it I just can't see the architecture.
Not going the whole way in a single stage suggests but you are using SABRE suggests you're OK with the engine but don't believe the structure.
The only large reusable high Mach structures I know are the Shuttle, the X37b, X15 and XB70. Except the X37b all have done powered flight inside the atmosphere but only the Shuttle did the whole potential SABRE speed range and only the XB70 could lift its own weight.
If you're that nervous only a rocket would be acceptably safe for the 2nd stage.
It's this mix of optimism and caution that I'm having trouble with.
So an LH2 powered engine is OK.
A truss structure with fibre reinforced glass skin is not OK.
Horizontal separation at high Mach number (that's an assumption but I've hear nothing about a VTO SABRE concept) is OK.
True. I'd never really thought of Skylon's design being selected because it was easy to anlayse. It seemed to address quite a few problems. I don't know about "optimum" but I'd certainly say "Good enough" and given the design goals I think it would be difficult to come up with something that looked much different but still gave undisturbed airflow to the engines and a well balanced design.
AFAIK the perceived advantages are an easier design problem as your design is split in two and you can have more structure and a higher payload fraction. But Skylon was designed to deliver an ELV payload fraction, not the 1% of the Shuttle. For an equal payload I find it very hard to believe a TSTO will be simpler to design, build or test. I doubt it would be cheaper to operate either. The big question is the perception of how risky is the Skylon structural design.
If the design assumptions on Skylon are as conservative as you think that seems unlikely barring (again) the perception that HTOL SSTO is risky and would essentially put the airframer at square 1 in design.
An interesting point. NASA pointed out that SABRE plume heating of the rear fuselage might be an issue, but did you have any others in mind?
GTO was in fact the MAIN mission of the EELV not delivery to LEO which arguably is the main mission of the Skylon design as that's what it's designed to do.
...a whole range of mission requirements were considered and the one that drove all the sizing and mass constraints was launching a comsat on a cryogenic stage. NOT because that was given a priority but because it needed the most, and everything else could live with less. I am sorry John Smith 19 RanulfC you keep assuming comsats were the primary mission they werent, they were just the driving mission among a set of equals.
TBH I sincerely hope so. . I just can't figure out where they want to draw the line that gives you a much better system. The known SoA for powered flight is the X15 but that was designed to operate long enough to soak the whole airframe. I think you could use the same materials (since materials and structure would seem to be the the concern here) to build a SABRE powered 1st stage to go to the X15's top speed. This would have major implications for the size and payload of any 2nd stage.
Care to expand on that? IMHO the economic model is every bit as important as the thermal cycle model.
That's my point. People know this is an issue yet insist on designing vehicles that will have problems and then complain they can't get the design to work.
I think NASA was going to do one of these with the engines half way up the body. Given that they've flagged plume impingement as a potential issue on Skylon I could not see how they'd avoid the rear fuselage getting quite "toasty."
That's certainly been historically true. Manual tracking of part masses meant recalculating a new empty mass would be a major exercise. But with BoM properties in a database (or at this level of fidelity a set of spreadsheets) propagating a part mass change through the design (although not the change on the mass of associated parts) should take seconds, giving an early warning that other part will need to be re-designed or re weighted.
REL treated Skylon as aircraft, so they applied aircraft margins.
With the proviso we're talking VTO TSTO rockets.
REL have been very careful to work with industry standard methods so that anyone looking over their work (like potential investors) can follow the trail from objectives back to how they are going to be carried out. Sadly these include the cost models that predicted SX would have to have spent about $2Bn up to the first F9 flight, but they are the industry standard.
That ability to absorb mass growth would seem to be the virtue of those giant Philip Bono 1960's designs, although drag is a problem if you're going with the idea of a "micro launcher." so somewhere in between seems to be minimum trouble.
I'd point out that REL (as Hempsell said) sized Skylon to do a comm sat mission to orbit. Historically they assumed that the payload would carry it's own engine to handle GTO. Other payloads to LEO would then be free to use the payload for that stage for their own uses. Note it's the end users issue to get such a stage. ESA advised them offering an upper stage would make the system more flexible, and now it's in the development plan.
Looking back it's a question of where you draw line on the stages maximum trajectory. Skylon's "first" stage gets you to orbit (which can be up to 600Km) , which for a lot of Earth Observation payloads would be enough. All other LV get you to maybe M10, but typically their 2nd stage can get you to GTO or even escape. A fairer comparison would be a TSTO just to LEO, then a third stage for anything about that.
A Skylon "first stage" is useful on its own. No other first stage is, unless people were prepared to do significant redesign and take a major cut in payload.
Actually I checked my posts and have not called it stupid. I just could not see why you would. It seemed a "sub optimal" to me. I can now see that an argument can be made but I've also recalled this came up with the question of how much a Skylon could carry sub orbitally. REL reckoned it was 2x their payload to orbit but the separation was quite risky and the payload would need something like 100-1500m/s (IIRC). Hempsell said they discontinued modelling on it as no one seemed that interested and you'd still need to build a Skylon to do it.
That's not quite correct.
Pure rocket could do it if you can get the structural mass down, and that seems very tough.
Anything needing deep pre cooling prior to REL's work I'm very doubtful about due to frost control and anything air breathing will need to have good air breathing Isp to swallow the loss in T/W.
Anything that air breathing and VTO means very low structural weight x (relatively) low T/W --> unlikely despite high AB Isp.
Not stupid, just seemed an odd idea.
I'd be wary of that. Their work on E/D nozzle design (and improvement) and work on the inlets suggests they either have hypersonic experience on staff or access through partner companies.
Which is pretty much SOP for all engineering projects, establishing that a design is possible if "Component X" can deliver these specs.
True, and a bit of a chicken and egg situation. Hopefully BAE will be able to provide some "sanity checking," although I would have expected the ESTECH to identify any issues like this already.
I did not know it was that high. But remember the old rule of software development "Optimization is the root of most evil."
IIRC In the X30 programme "complexity in airframe thermal management" meant a)Building large chunks of design in RCC or b) going with active cooling. AFAIK Skylon aims to make very limited use of either.
Everything has a price. Is that increased efficiency a) Affordable b) Needed ? NASP needed it with an engine T/W ratio of 2:1 but does SABRE?
The inverse problem is IMHO trickier. Ensuring any improvement in a subset of the flight envelope does not make other parts of the envelope worse to the point the design won't work. A TSTO would open up options at the cost of designing 2 vehicles to do so.
With that staging velocity you could consider a very conventional expendable liquid upper stage. One notion I've wondered about would be wrapping 2 half circular wings rounds such a stage on pivoting on a structure like a piano hinge with some kind of "aerospike" or "aerodisk" to improve the aerodynamics of the flat front end. Such an empty stage should begin entry at a very high altitude, but again has all the issues of being back end heavy of the shuttle without it's control surfaces.
Ranulf, I'll pick on a tiny bit of this novel you've written
Quote from: RanulfC on 08/16/2016 05:26 pm GTO was in fact the MAIN mission of the EELV not delivery to LEO which arguably is the main mission of the Skylon design as that's what it's designed to do....by re-quoting Hempsell from 'Thread 4 giving JS19 a jolly-good ticking off :Quote from: Hempsell on 06/19/2014 10:27 am...a whole range of mission requirements were considered and the one that drove all the sizing and mass constraints was launching a comsat on a cryogenic stage. NOT because that was given a priority but because it needed the most, and everything else could live with less. I am sorry John Smith 19 RanulfC you keep assuming comsats were the primary mission they werent, they were just the driving mission among a set of equals.
Lets be clear here, engine performance can be enhanced from 10% to 30% by optimizing the air-flow using the forward and aft airframe for pre-compression and expansion purposes. Controllability and stability can be highly improved by moving the engines from the wing-tips to positions closer to the airframe. Propellant feeding and flow would be far less complex with the engines within the airframe especially at high mach speeds. Airframe and wing stress' and manufacturing complexity are higher with the engines on the wing-tips as opposed to integrated within the airframe. There are high and low speed issues along with manufacturing and operational areas that could be addressed by a different, more integrated airframe and engine assembly.
Quote from: RanulfC on 08/16/2016 05:26 pmLets be clear here, engine performance can be enhanced from 10% to 30% by optimizing the air-flow using the forward and aft airframe for pre-compression and expansion purposes. Controllability and stability can be highly improved by moving the engines from the wing-tips to positions closer to the airframe. Propellant feeding and flow would be far less complex with the engines within the airframe especially at high mach speeds. Airframe and wing stress' and manufacturing complexity are higher with the engines on the wing-tips as opposed to integrated within the airframe. There are high and low speed issues along with manufacturing and operational areas that could be addressed by a different, more integrated airframe and engine assembly.Sounds like making the engines integrated with the airframe for airflow can improve practically everything except ease of analysis and aft-body heating. Might even increase the speed the engines can practically breath air a couple Mach factors. But first prove the engine works as well as projected, then worry about an optimal installation.
Quote from: RanulfC on 08/16/2016 05:26 pmLets be clear here, engine performance can be enhanced from 10% to 30% by optimizing the air-flow using the forward and aft airframe for pre-compression and expansion purposes. Controllability and stability can be highly improved by moving the engines from the wing-tips to positions closer to the airframe. Propellant feeding and flow would be far less complex with the engines within the airframe especially at high mach speeds. Airframe and wing stress' and manufacturing complexity are higher with the engines on the wing-tips as opposed to integrated within the airframe. There are high and low speed issues along with manufacturing and operational areas that could be addressed by a different, more integrated airframe and engine assembly.Sounds like making the engines integrated with the airframe for airflow can improve practically everything except ease of analysis and aft-body heating. Might even increase the speed the engines can practically breath air a couple Mach factors.
But first prove the engine works as well as projected, then worry about an optimal installation.
A good example of taking the spirit of Skylon to one (of many) logical extremes would be sucking in the engines towards the center body and building the intake/nozzle ramps into the body sides (rather than the bottom), making something that looks like a flying axehead. Good illustration of that would SEI's Spiral-1/Sentinel design, in the following PDF on page 13-14.http://www.sei.aero/eng/papers/uploads/archive/SEI_JANNAF_Sentinel_2007.pdfFlying axehead is a simplified approach to getting the aero-integration, but forebody sizing would definitely cause it to mutate due to inlet/forebody interactions if one were to chase a cylindrical nose design.
Bad idea of the day, if using an axehead design with the typical low wing aligned with the bottom of the axehead, would you have a usable busemann supersonic biplane effect if you also had a second wing aligned with the top of the axehead?
I think REL has struck a balance with picking the lower hypersonic end of things which many air-breathing advocates, (I'm looking at the SCramjet folks here ) overdo because they want to get the 'most' use out of the systems rather than looking at the entire mission objectively.
Maybe I should just point out that the AIRFRAME design is what I like not the concept itself?
Quote from: RanulfC on 08/19/2016 05:31 pmI think REL has struck a balance with picking the lower hypersonic end of things which many air-breathing advocates, (I'm looking at the SCramjet folks here ) overdo because they want to get the 'most' use out of the systems rather than looking at the entire mission objectively.In their 1989 Spaceflight article Bond said that was one of the key ideas behind SABRESkylon. Not trying to hang on for just that last extra air breathing Mach number (and its associated friction heating) before shifting to rocket mode and going into a steep climb. It may also be the (rough) limit at which the design of the "spill ramjet," used to burn off the excess Hydrogen, starts to move into less grounded design areas.
QuoteMaybe I should just point out that the AIRFRAME design is what I like not the concept itself? When you wrote "This is one of my favourites" I was sort of wondering what part of it you favored.