Wasn't some company already doing that? Designated as a cube launcher if memory serves.
Regarding S2, a M1-D vac is overkill, especially since we are brainstorming about an expendable vehicle here (S2 would have to do less work). That's why I talked about a Kestrel variant. I was thinking of something the size/power of Kestrel2/RD-58MF.
SpaceX presumably abandoned Falcon 1 because there wasn't enough demand for a launcher that size to justify the fixed costs. Now that Falcon 9 is on the verge of reusing its first stage the business case for an expendable Falcon 1 just got even worse. Why design a launch vehicle that's not worth building?
Maybe something from XCOR with a vacuum-optimised nozzle?
I don't think that they would constrain themselves to the given constraints that you provided. I suspect that they would have instead made a two stage rocket, with a single merlin 1d that amounts to being something near a shrunken F9 second stage and a triple sized falcon1 second stage.
It's just interesting because I think it makes an impressive rocket against the small launchers out there like VEGA or LauncherOne.
If the premise is that SpaceX will not be doing this, it would be interesting to think about a startup that purchased M1D engines from SpaceX and licensed the technology required for the remainder of an F1e-like vehicle.In particular I think SpaceX might license Kestrel2 technology. With M1D having maybe twice the thrust of M1A, perhaps the second stage could be powered by dual Kestrel2 engines? How badly would that "blow" the diameter of the vehicle?
Quote from: S.Paulissen on 01/06/2016 02:37 amI don't think that they would constrain themselves to the given constraints that you provided. I suspect that they would have instead made a two stage rocket, with a single merlin 1d that amounts to being something near a shrunken F9 second stage and a triple sized falcon1 second stage.But what you wrote is inside the constraints I gave (save for the different diameter of the 2nd stage). Very cool post btw, thanks for that. What would the total height of the rocket be in your example?
I could see spacex "selling" end-of-life merlins to a subsidiary that would repackage them into expendable low cost launchers. customers would trade reliability for dirt-cheap orbital access. it would be a huge boon for universities and startups.Such a subsidiary would also be a great "minor leagues" for spacex to train up talent.
Quote from: RoboGoofers on 01/06/2016 07:23 pmI could see spacex "selling" end-of-life merlins to a subsidiary that would repackage them into expendable low cost launchers. customers would trade reliability for dirt-cheap orbital access. it would be a huge boon for universities and startups.Such a subsidiary would also be a great "minor leagues" for spacex to train up talent.There's no such thing as an "end-of-life" Merlin engine.Musk has said that there is no limit to how many times a Merlin could be used. After 30 or so firings a few components would have to be replaced, then it could continue to be used.
Quote from: RoboGoofers on 01/06/2016 07:23 pmI could see spacex "selling" end-of-life merlins to a subsidiary that would repackage them into expendable low cost launchers. customers would trade reliability for dirt-cheap orbital access. it would be a huge boon for universities and startups.Such a subsidiary would also be a great "minor leagues" for spacex to train up talent. I couldn't. They expose themselves to a huge liability for little benefit. If the engine isn't OK for a Falcon, it's not OK for anything else except testing.
Quote from: ChrisWilson68 on 01/06/2016 09:02 pmQuote from: RoboGoofers on 01/06/2016 07:23 pmI could see spacex "selling" end-of-life merlins to a subsidiary that would repackage them into expendable low cost launchers. customers would trade reliability for dirt-cheap orbital access. it would be a huge boon for universities and startups.Such a subsidiary would also be a great "minor leagues" for spacex to train up talent.There's no such thing as an "end-of-life" Merlin engine.Musk has said that there is no limit to how many times a Merlin could be used. After 30 or so firings a few components would have to be replaced, then it could continue to be used.Come on host! Let's not let the good become the enemy of the perfect! The elasticity of the market will take some time to create payloads for reusable hardware. SpaceX's entire manifest is probably presumed to be deliverable with new components. That means lots of Merlins are going to be laying around very soon! There are 9 now, could be 18-27 in the next 60 days. That years of launches in the smallsat space.
And SpaceX has plans for those engines. They're not just surplus. Yes, they're going to have a bunch of them accumulating over the next couple of years. But, after that they'll be using them to fly payloads. By the time a new F1-class launcher could be ready, SpaceX will be flying all their engines.
Quote from: Nomadd on 01/06/2016 08:42 pmQuote from: RoboGoofers on 01/06/2016 07:23 pmI could see spacex "selling" end-of-life merlins to a subsidiary that would repackage them into expendable low cost launchers. customers would trade reliability for dirt-cheap orbital access. it would be a huge boon for universities and startups.Such a subsidiary would also be a great "minor leagues" for spacex to train up talent. I couldn't. They expose themselves to a huge liability for little benefit. If the engine isn't OK for a Falcon, it's not OK for anything else except testing.Agreed. This has nothing but downsides for SpaceX. Selling new engines is one thing, but selling used engines is a surefire way to get blamed for every launch mishap.
Quote from: ChrisWilson68 on 01/06/2016 09:44 pmAnd SpaceX has plans for those engines. They're not just surplus. Yes, they're going to have a bunch of them accumulating over the next couple of years. But, after that they'll be using them to fly payloads. By the time a new F1-class launcher could be ready, SpaceX will be flying all their engines.This sounds like a paperwork nightmare, and defeats the idea of scaling up production to reduce per-unit manufacturing costs.
i think they'll just test and fly until they have a clear mean time to failure and then retire them.
but back to the topic, i only mentioned the used merlins because there might be a lot of them sitting around some day that could be used on a reborn F1.
Quote from: Lars-J on 01/06/2016 09:40 pmQuote from: Nomadd on 01/06/2016 08:42 pmQuote from: RoboGoofers on 01/06/2016 07:23 pmI could see spacex "selling" end-of-life merlins to a subsidiary that would repackage them into expendable low cost launchers. customers would trade reliability for dirt-cheap orbital access. it would be a huge boon for universities and startups.Such a subsidiary would also be a great "minor leagues" for spacex to train up talent. I couldn't. They expose themselves to a huge liability for little benefit. If the engine isn't OK for a Falcon, it's not OK for anything else except testing.Agreed. This has nothing but downsides for SpaceX. Selling new engines is one thing, but selling used engines is a surefire way to get blamed for every launch mishap.This is "Blood sucking lawyer 101" basics. Buyer beware. Assignment of risk can easily be transferred to the 3rd party. SpaceX could remove the engine, stick it on a test stand, and certify is still works to spec. and is free from damage per identifiable criteria. Beyond that, the risk has transferred.
Guys..we are theory-crafting about imaginary/alternate reality paper rockets in this thread. The M1-Ds can be brand new, taken from a scrapyard or exchanged for Vermulian Brandy.Back to the topic if we can..<3
Well I took the leap last night to give my best effort at making my own new "Phoenix" F1 class vehicle and testing it out on a simulator linked to by this site in the archives at Silverbird Astronautics.http://www.silverbirdastronautics.com/LVperform.html[...]Here is what the calculations returned:Mission Performance:Launch Vehicle: User-Defined Launch VehicleLaunch Site: Cape Canaveral / KSCDestination Orbit: 185 x 185 km, 45 degEstimated Payload: 1687 kg95% Confidence Interval: 1294 - 2172 kg[...]
what about using 1 or 2 Super Draco engines for the upper stage? they are very lightweight and mostly need a upgrade for space flight via mounting a large bell on this
Quote from: fwskungen on 01/08/2016 11:37 amwhat about using 1 or 2 Super Draco engines for the upper stage? they are very lightweight and mostly need a upgrade for space flight via mounting a large bell on thisOne would do (for the amount of thrust needed), but the Isp would be much worse than what ye olde Kestrel had. Even with a bigger nozzle.
For a Falcon9/Falcon Heavy Payload Assist Module, the idea of using superdraco for the application might have some merit for deep space missions like interplanetary probes, or insertions to GEO. I think though that SpaceX have decided to maximize the Falcon architecture recoverable/re-usable fraction, so a development program like that might be viewed by them as counter-intuitive. For an imaginary F1e, I think that the superdracos' low Isp would help less than a better Kestrel2.
No, it has little merit for a deep space mission. Once you are out of the deep gravity well, Isp is king. Thrust does not matter. So a Draco (or cluster of them) would actually be superior to SuperDraco for the purpose of a final kick stage.
Well now, this is my kind of thread.Quote from: Stan-1967 on 01/07/2016 04:12 pmWell I took the leap last night to give my best effort at making my own new "Phoenix" F1 class vehicle and testing it out on a simulator linked to by this site in the archives at Silverbird Astronautics.http://www.silverbirdastronautics.com/LVperform.html[...]Here is what the calculations returned:Mission Performance:Launch Vehicle: User-Defined Launch VehicleLaunch Site: Cape Canaveral / KSCDestination Orbit: 185 x 185 km, 45 degEstimated Payload: 1687 kg95% Confidence Interval: 1294 - 2172 kg[...]So... assuming I was a billionaire, I had a couple of Mercury style capsules as payloads (m = 1400kg), and a death defying love of Koalas, I could have lunch in Cape Canaveral, get on a Phoenix at 3pm, have breakfast in Taronga zoo, Sydney (at 4pm/8am), get on another Phoenix at 5pm/9am and be back at KSC in time for dinner?
Quote from: Lars-J on 01/08/2016 05:03 pmNo, it has little merit for a deep space mission. Once you are out of the deep gravity well, Isp is king. Thrust does not matter. So a Draco (or cluster of them) would actually be superior to SuperDraco for the purpose of a final kick stage.But if you're going to do all of that, in space, a SRM has much better storability properties, probably weighs less (when you account for the plumbing), and is a known and available quantity already. Just use a Star 48 or equivalent if that's what you want!Really, SuperDracos were designed for a very specific purpose, and trying to use them elsewhere just doesn't make sense at all.
Remembering that this is supposed to be a low-cost launcher and its design should therefore be optimised for cost, not performance, I'd suggest the following design parameters: Common propellant for both stages and using existing equipment where possible.Given the above, how about the following proposal: A 2-stage rocket; both stages keralox with a single M1-D SL engine? The SL version is not as efficient as the Vac in space, but it should be sufficient (it has a vacuum isp of 308 versus 348). It's also lower thrust, which helps with problems of over-acceleration on the second stage (and it can throttle down to 70%).Anyone care to run the numbers?
Quote from: CuddlyRocket on 01/09/2016 02:59 pmRemembering that this is supposed to be a low-cost launcher and its design should therefore be optimised for cost, not performance, I'd suggest the following design parameters: Common propellant for both stages and using existing equipment where possible.Given the above, how about the following proposal: A 2-stage rocket; both stages keralox with a single M1-D SL engine? The SL version is not as efficient as the Vac in space, but it should be sufficient (it has a vacuum isp of 308 versus 348). It's also lower thrust, which helps with problems of over-acceleration on the second stage (and it can throttle down to 70%).Anyone care to run the numbers?Won't work, too much thrust for a merlin on second stage at minimum throttle the upper stage would hit 20gs at burn out.
Quote from: Lars-J on 01/08/2016 05:03 pmNo, it has little merit for a deep space mission. Once you are out of the deep gravity well, Isp is king. Thrust does not matter. So a Draco (or cluster of them) would actually be superior to SuperDraco for the purpose of a final kick stage.Not that I disagree with you, but a Star 48 has an ISP of 292 (see http://forum.nasaspaceflight.com/index.php?topic=33084.msg1109220#msg1109220) which is also really poor. SpaceX built the SuperDraco to essentially compete with an SRM: low ISP, high thrust, quick ignition, non-cryo propellant, with the notable difference being that it can throttle dynamically instead of being stuck with a fixed thrust profile.But if you're going to do all of that, in space, a SRM has much better storability properties, probably weighs less (when you account for the plumbing), and is a known and available quantity already. Just use a Star 48 or equivalent if that's what you want!Really, SuperDracos were designed for a very specific purpose, and trying to use them elsewhere just doesn't make sense at all.
That would be somewhat counter-productive I think. A single m1-d can move..eh...lets say about 70,000kg off the pad for a low TWR. Lets say that S2 is bigger (40 tonnes, including payload). This means that the first stage should weigh about 30 tonnes. M1-d does about 84,000kgf in vacuum (we are still talking about the SL version, not MVac). How much could you feasibly throttle it down before the payload liquefies?
My pony is that is your upper stage is large enough, the situation is no different than what current small F9 payloads experience - such as CASSIOPE, DISCOVR, and now JASON-3 - and somehow those payloads don't seem to "liquefy". You are exaggerating the issue of g-loads at burnout.
Well I took the leap last night to give my best effort at making my own new "Phoenix" F1 class vehicle and testing it out on a simulator linked to by this site in the archives at Silverbird Astronautics.http://www.silverbirdastronautics.com/LVperform.htmlThis was the first time I have ever done an exercise like this. I have watched many other here do similar, some of you are very very good at it. I do not profess to be good at all.My designs started with the specifications for using the Merlin 1D FT engine w/ 756 kN thrust, and building the vehicle around that. I also made an early decision to make the new vehicle with a 2m core, not the 1.7 I believe the old F1 had. I think the Merlin 1D FT is too much rocket to stick on that small a diameter core without getting something too long and bendy.I also wanted to make a better S2, so I selected to use a 100kN Methane upper stage. ( Darma Technolgies CHASE 10 ) I had to guess what a vacuum engine could do for ISP, and guessed 350s.G's at liftoff were set to be 1.18, so the mass of the complete vehicle would then be 65329 kg's.After some iterations on the calculations, my mass distribution is a followsStage 1:Dry mass = 3461 kgPropellant = 55368 kgThrust = 756 kNISP avg = 304Stage 2:Dry mass = 619Propellant = 5881Trust = 100 kNISP = 350Fairing 160 kg
Quote from: Dante80 on 01/09/2016 04:58 pmThat would be somewhat counter-productive I think. A single m1-d can move..eh...lets say about 70,000kg off the pad for a low TWR. Lets say that S2 is bigger (40 tonnes, including payload). This means that the first stage should weigh about 30 tonnes. M1-d does about 84,000kgf in vacuum (we are still talking about the SL version, not MVac). How much could you feasibly throttle it down before the payload liquefies?My pony is that is your upper stage is large enough, the situation is no different than what current small F9 payloads experience - such as CASSIOPE, DISCOVR, and now JASON-3 - and somehow those payloads don't seem to "liquefy". You are exaggerating the issue of g-loads at burnout.
Quote from: Lars-J on 01/09/2016 08:14 pmMy point is that is your upper stage is large enough, the situation is no different than what current small F9 payloads experience - such as CASSIOPE, DISCOVR, and now JASON-3 - and somehow those payloads don't seem to "liquefy". You are exaggerating the issue of g-loads at burnout.I think that its not the same thing man. Running the numbers for a 110+ ton S2 lifted by 9 M-1ds to a 40 ton S2 lifted by one makes me think that the situation is different at S2 burnout with a small payload.
My point is that is your upper stage is large enough, the situation is no different than what current small F9 payloads experience - such as CASSIOPE, DISCOVR, and now JASON-3 - and somehow those payloads don't seem to "liquefy". You are exaggerating the issue of g-loads at burnout.
No, you are not getting what I'm saying. What I am proposing is that the upper stage basically be the F9 upper stage, but slimmed and stretched to F1 diameter, powered by a single M1D. This large upper stage would not have the burnout g-load issue that you are concerned with, since it would have a similar dry weight of the F9 upper stage. But since this stage would not be SSTO, I propose putting it on top of a smaller but same diameter 1st stage, with an M1D at full thrust.
But I understood what you said. That's why S2 is a little bigger than S1 (as you said), and it's less than half the weight of the F9 S2. The diameter is 1.7m.
But since this stage would not be SSTO, I propose putting it on top of a smaller but same diameter 1st stage, with an M1D at full thrust.
Quote from: Dante80 on 01/09/2016 11:03 pmBut I understood what you said. That's why S2 is a little bigger than S1 (as you said), and it's less than half the weight of the F9 S2. The diameter is 1.7m.No, you are still not getting what I mean. The diameter would be 1.7m, but it would contain almost the same amount of propellant as the F9 upper stage. It would be MUCH longer. And due to this non-optimal size, the dry mass of the stage would be the same or likely higher. Therefore no burnout g-load issue.
Quote from: Lars-J on 01/09/2016 11:07 pmQuote from: Dante80 on 01/09/2016 11:03 pmBut I understood what you said. That's why S2 is a little bigger than S1 (as you said), and it's less than half the weight of the F9 S2. The diameter is 1.7m.No, you are still not getting what I mean. The diameter would be 1.7m, but it would contain almost the same amount of propellant as the F9 upper stage. It would be MUCH longer. And due to this non-optimal size, the dry mass of the stage would be the same or likely higher. Therefore no burnout g-load issue.It will take at least 30 meters of 1.7 meter core to hold around 78,500 kg of fuel, which is what the latest F9 S2 reportedly contains. The burn time for a Merlin to go through this fuel will be around 295s. The Merlin 1D at 756 kN cant lift that load of fuel. Merlin Vac manages because it produces 934 kN.
Quote from: S.Paulissen on 01/09/2016 03:55 pmQuote from: CuddlyRocket on 01/09/2016 02:59 pmRemembering that this is supposed to be a low-cost launcher and its design should therefore be optimised for cost, not performance, I'd suggest the following design parameters: Common propellant for both stages and using existing equipment where possible.Given the above, how about the following proposal: A 2-stage rocket; both stages keralox with a single M1-D SL engine? The SL version is not as efficient as the Vac in space, but it should be sufficient (it has a vacuum isp of 308 versus 348). It's also lower thrust, which helps with problems of over-acceleration on the second stage (and it can throttle down to 70%).Anyone care to run the numbers?Won't work, too much thrust for a merlin on second stage at minimum throttle the upper stage would hit 20gs at burn out.Shame! By the way, what is the maximum g at burn out one should aim for?
Or someone could bite the bullet and develop a new small keralox engine!
So, it's a kestrel clone, in performance and mode of operation if not design. The problem with these size of engines (technically just a glorified valve in front of a combustion chamber, not the literal definition of an engine) is that they're too small to lift the size of upper stage needed to best utilize the lift off a Merlin 1d FT.
Quote from: CuddlyRocket on 01/10/2016 01:30 pmOr someone could bite the bullet and develop a new small keralox engine!Like the FRE-1? (thrust: 6,200 lbf, isp: 325 sec)http://www.fireflyspace.com/vehicles/firefly-ahttp://www.fireflyspace.com/news/ournews/first-rocket-engine-test-a-success-for-firefly-space-systemsEdit: actually, those two links disagree on the thrust. the second says 7,000 lbf
For those that are not aware, this is at the SpaceX Wilkie facility which is an annex of Hawthorne which IIRC is tasked with R&D. Here it is on maps. The legs are located on the East side of the building, about half way up. The junkyard is above the North East corner of the building.
Wouldn't make more sense to base this hypothetical new small launcher on Raptor? They would need an engine for the 2nd stage but It would be in a very different performance class compared to Falcon1 while still having a similar level of complexity.
Quote from: Giovanni DS on 04/18/2018 12:28 pmWouldn't make more sense to base this hypothetical new small launcher on Raptor? They would need an engine for the 2nd stage but It would be in a very different performance class compared to Falcon1 while still having a similar level of complexity.A launcher with a 170 ton engine is not most peoples idea of a small launcher.
Falcon 1 doesn't fit that criteria for some people either. Is your goal to just create a hypothetical smallest launcher, or is it to create a hypothetical small launcher that would actually be more compatible with SpaceX efforts going forward? If the latter you base it on Raptor, and it is would still be a very "small" launcher in SpaceX's lineup.