Recommended Posts

^ and my guess is there won't be...unless we have an alphabet agency with "issues" with everyone not on their favorites list.

 

Until I see a line item number and the category used, in a particular documented process to present it as an "issue", and with the coherence to defend...it's outright garbage.

 

15 point analysis on last page

 

They have bigger problems than this "issue".

 

:s

a few additions to the collection...

 

 

 

Updated Collector Cards and Bookmarks Available Now!

https://blogs.nasa.gov/commercialcrew/2017/03/29/updated-collector-cards-and-bookmarks-available-now/

 

  • 3 months later...

Hot off the presses: 

 

New Commercial Crew flight test NET dates. SpaceX moves left a month from the last stated estimate of March 2018.

 

Targeted Test Flight Dates

 

SpaceX

Demo Mission 1 (uncrewed): February 2018
Demo Mission 2 (crewed):June 2018

 

Boeing 

Orbital Flight Test: June 2018
Crew Flight Test: August 2018

  • Like 1

The interstage fairing, the circumferential airflow disc, the production issues (out of round clamshells), the RD-180 documentation issues, the risk of using GEM solid boosters (remember the Delta II GPS launch?) etc.

  • Like 1

Had to look that one up.... 

 

a portion of a manned rocket launch trajectory where the premature shutdown of any or all running booster engines will lead to loss of the re-entry vehicle and crew subsequently due to the over temperature or structural loads incurred from the resulting trajectory.  Is that too muddy?  Black zone does not mean what is going to happen in a normal case, only if an engine (or two or three) quits. 

The Falcon 9, because it's so powerful, flies above those zones entirely during flight. It is doing things "the correct way". Likely an orbit of a Dragon 2 when the S2 shuts down after launch will be about the same as a Cargo Dragon headed for the ISS (around 250x250 km parking orbit). No problem. Something goes wrong, they can abort however is appropriate. And there's no issue. We've seen how the S1 comes down a lot when it lands on the ASDS -- same thing applies here and the Dragons (Cargo and V2) can do the same thing during an abort, only they'd land in the drink.

 

Atlas-V/Centaur doesn't have the power to get above the "black zones" until the Centaur is almost 3/4 of the way finished with its' burn. CST is going to be the single heaviest thing the Atlas-V will ever launch, and they're using a flight profile that takes advantage of gravity to assist in getting CST into LEO in order to overcome that lack of power. That's why these "black zones" are coming into question also because there's a chance that CST could slightly contact atmosphere flying horizontally, at near-orbital speeds, still under thrusted power as it's trying to reach orbit. That's a very, very bad thing.

 

Delta-IV Heavy isn't Human-Rated, so they CAN'T use that (otherwise they would have chosen it and not stopped production), nor can it be made Human-Rated.

 

So yeah, there's way more I could go on and on about with this subject, but that's the juicy parts.

Yep. Good at launching satellites. Cargo runs are the limit for the Atlas-V/Centaur.

 

ULA really, really needed Vulcan to be on the 2018 schedule they originally wanted ... then they'd have a contender at least punching in the same weight class as Falcon-9.

2 hours ago, DocM said:

Yup....that's the advantage of having 1.9 million lbf of thrust on tap to MECO vs. Atlas V's 860,000 lbf + 2 boosters lower down.

Correction. 

 

And, the largest payload Atlas V has ever pushed uphill was the Cygnus AO-4 ISS cargo mission: 7,492 kg.

 

Dragon CRS missions run at least  9-10,000 kg, and Crew Dragon much more than that.

Edited by DocM
  • Like 1

Been thinking about this some more today. It's a really, really bad idea to keep CST on Atlas/Centaur. There's almost NO performance margin at all. Remember the LOX oversaturation problem during one of the Cygnus launches near the end of the S1 burn? They nearly lost that payload because there wasn't ANY additional performance in that vehicle to spare, and the Centaur engines are SO underpowered that ULA might as well be using squirrels on treadmills.

 

CST isn't a Cygnus. It's far heavier. We're talking Cargo Dragon and a bit type of heavier. Even if they employ a Dual Centaur it's not gonna be enough until 3/4 to 4/5 of the S2 burn is finished before they have enough energy to achieve a minimum orbit, and then again to finalize their parking orbit -- even with their flight profile shenanigans using gravity. That's assuming they don't use up all their fuel just getting there ... otherwise it'll be a short flight.

 

Better way to go, not to mention cheaper, is to just hire SpaceX to tote CST uphill on a Falcon-9. Throw a nice LDSM (Long-Duration Service Module, loosely based on Cygnus tech) full of goodies along with it too. They've been wanting to try out that hardware anyway, why not give ULA more bang for their money? Way, WAY cheaper than an Atlas/Centaur and they can save that rocket for something it was actually designed for.

 

*sigh* Alright. Rant over. Had to get that out of my system. :laugh::rofl:

 

Notable: Boeing will only build 3-4 Starliners total. SpaceX has a Dragon 2 assembly line as it'll be used in at least 2 NASA programs; Commercial Crew and Commercial Resupply Services Round 2 - with Boeing being eliminated from CRS2. The upcoming lunar orbit Deep Space Gateway is a possible third, and there are potential commercial users and the lunar flybys.

 

The Dragon Claw connector attached the solar arrays, thermal radiators and other connectors in the Trunk to the spacecraft.

 

MLqRVIE.thumb.jpg.f34bbc237871a65b85da843f35a6e8af.jpg

 

Edited by DocM

Thanks @DocM. :yes: 

 

What we can glean from this:

 

a.) SpaceX is in it for the long haul with Commercial Crew.

b.) Build quality is excellent ... doesn't get much prettier or tidy than the image above.

c.) Even with reuse, Dragon 2's are going to come off the line as needed for the foreseeable future. Is it the American equivalent of the robust and reliable Soyuz platform? Probably .. lots of room to innovate and improve this platform as technologies evolve.

d.) We haven't heard the last about propulsive landings .. mark my words. That's still gonna be a thing eventually. :D 

e.) Boeing/LockMart/ULA just aren't committed to Commercial Crew now that the "big money" contracts have been reeled in. Years and years of being one of two shows in town (can't forget the Shuttle Program) spoiled 'em. Now they'll go back to doing what they do best - Aircraft and Military Hardware. ULA might get spurred off into its' own entity, but could finally start keeping the money it earns for once. Maybe Bezos can purchase it?

The only way I can see Starliner moving forward is if Boeing gets big bux to modify it with a large unpressurized Trunk, solar arrays (its battery life is only 2-3 days) etc. for use as a Deep Space Gateway taxi/cargo hauler. The rumors were it lost out on a CRS2 contract because it was volume and shape limited inside (acute sidewall angle, like an attic bedroom), had no Trunk outside for unpressurized cargo and was too expensive.

Edited by DocM
  • Like 1

Yeah. Everything including the design working against it, not to mention the just plain awful decisions made in development. "Apollo on steroids" meets "bureaucracy on wheels".

 

While I'm not really opposed to such an approach, the problems that I have with CST are the lack of any meaningful updates to the platform. The design is just about 15 years old -- I remember even in 2001~2002 hearing about Constellation and how new solutions could be applied to existing technologies, etc etc, the Ares launcher, and all that. 

 

The CST is Constellation, rebranded. That's just about it. Not much has changed unless something had to be changed.

 

And what gets me is that it's not even using "common sense" gear. Solar Panels -- surely they would have learned from Apollo? That would almost seem to be a NASA requirement, now. Modularity -- some kind of useful Service Module that can adapt to the mission? Seems like that would be required too; instead, they've got some Cygnus-derivative tech that still needs proving, and my understanding is that it does not provide much more life support than a week ...

 

CST is a mess, and Apollo was a superior product in most ways that mattered. All the CST has going for it is the larger size, relative to the Apollo CM, and a better computer. I'd venture to say that a 2017 model Apollo C+SM would be ounce-for-ounce as good as we'd need it to be until the Dragon 2 was ready.

 

One can only surmise, at this point.

2 hours ago, Unobscured Vision said:

Yeah. Everything including the design working against it, not to mention the just plain awful decisions made in development. 

 

Yup. Some terrible decisions, one being that godawul sidewall angle. OK for crew, stick their tootsies there, but death for cargo packs or the Shuttle style racks which are now the standard.

 

Quote

 

And what gets me is that it's not even using "common sense" gear. Solar Panels -- surely they would have learned from Apollo? 

>

There's been artwork of a Starliner with a Cygnus-based habitat complete with with its propulsion/power bus and arrays, but we'll see how serious that is. Maybe just attach a Cygnus bus to the bottom of the Cygnus service bay

 

cst100_cygnus_bkgtest2.jpg

 

Right now the only item in the options list is a small circular solar array mission kit which folds under the service bay. Not much output at that size. Bottom right.

 

cst100-pdf-details.thumb.jpg.05f06bde7ef13c9678a530989308b89d.jpg

 

  • Like 1

Those aren't even large enough to be useful, not to mention where they're located. I've seen that before and every time I do I keep asking "why". Keep the aft section sun-facing? Yeah, I bet the Retro Package, not to mention everything else in the SM, will appreciate being fried in continuous sunlight like that (radiators or not).

 

So the SM is gonna have thermal issues. It'll barely have a chance to get cooled off before it's right back to sunlight again during orbital ops. Too much of that and it'll start warping, which can throw off the decoupling when they go for reentry. Boomski if it hasn't done so already due to the thermals during orbital ops.

 

Oh, and their elaborate LAS is likely also their Retro Package. Which has been frying and cooling and frying and cooling (etc etc etc) ... nope, nothing could possibly go wrong there either.

 

CST is a bad day waiting for a launch window.

  • 2 weeks later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • i got a better prices on reddit /homelabsales. same drives for $80 less
    • The fact that memory in general is so high I have to take a loan out to build a computer now is just beyond stupid. Who's really to blame here? Low supply or high demand?
    • Display Driver Uninstaller (DDU) 18.1.5.5 by Razvan Serea Display Driver Uninstaller (DDU) is a utility for completely removing AMD/NVIDIA/INTEL graphics drivers and related packages from your system, attempting to eliminate all leftovers (including registry entries, folders and files, driver store). Though AMD/NVIDIA/INTEL drivers can usually be removed via the Windows Control Panel, this uninstaller tool was created for situations where standard uninstall fails, or when you need to fully remove NVIDIA or ATI graphics card drivers. After using this driver cleaner, your system will behave as though it’s the first time you’re installing a new driver—similar to a fresh Windows installation. As with all such tools, we recommend creating a restore point beforehand, allowing you to undo changes if issues arise. If you're having trouble installing an older or newer driver, try it—there are reports that it resolves such problems. Recommended usage: The tool can be used in Normal mode but for absolute stability when using DDU, Safemode is always the best. Make a backup or a system restore (but it should normally be pretty safe). It is best to exclude the DDU folder completely from any security software to avoid issues. You do NOT need to uninstall the driver prior using DDU. Requirements: .NET Framework 4.8 Compatible with Windows 7, 8, 8.1, 10, and 11 (32-bit or 64-bit) Note: Using on Insider Preview builds is at your own risk. Display Driver Uninstaller (DDU) 18.1.5.5 changelog: Added 'Reset to recommended' button for the Options. General fixes and improvements. Download: Display Driver Uninstaller (DDU) 18.1.5.5 | 1.7 MB (Freeware) Download: DDU Portable | 1.2 MB Links: Display Driver Uninstaller Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • WACUP 1.99.51.24568 Preview by Razvan Serea WACUP (WinAmp Community Update Project) is a modern, enhanced version of the classic Winamp music player, designed for better stability, performance, and compatibility. Built for Windows, WACUP retains the familiar Winamp interface while adding 64-bit support, bug fixes, and new features like improved audio format support, customizable skins, and optimized playlist management. Unlike bloated alternatives, WACUP focuses on lightweight performance and regular updates, making it the best choice for fans of the classic Winamp experience. Basically, if you miss the good old days of Winamp and want a modern upgrade that doesn’t mess things up, WACUP is for you! WACUP key features: Classic Winamp Feel – Keeps the familiar interface and functionality. Bug Fixes & Stability – Fixes old Winamp issues and improves performance. 64-Bit Support – Works better on modern systems. More Formats & Plugins – Supports additional audio formats and third-party plugins. Customizable UI – Skins and tweaks for a personalized look. Better Library Management – Improved playlists, media organization, and search. No Bloat – Focuses on performance without unnecessary extras. Regular Updates – Community-driven development with new features and fixes. WACUP 1.99.51.24568 Preview changelog: Fixed a deadlock seen from the recent crash reports when doing some of the drag + drop actions within the media library window Fixed a loading crash seen related to a problem with some of the artwork cache image files being restored which should now be better handled allowing for the bad image to be removed without it failing Fixed a deadlock seen from the recent crash reports when the internal metadata cache clearing is triggered which could block the main ui thread for too long with this now being moved to a background thread Fixed some performance issues with some of the methods related to determining artwork support which mainly affected the local library import / refresh (this is still slower for some compared to other players because there's more data & artwork aspects being checked for which means doing more processing on a single file despite the best of attempts to reduce duplicate / heavy processing where possible) Fixed a crash with the JTFE based missing files hotkey which no one seems to have used for an age for this to appear (maybe it's time to seriously consider stripping out features that aren't being used) Fixed how some of the file types which use extra information to reference their sub-songs is handled which was preventing some from being correctly resolved back to their base file (noticed fixing above) Fixed an issue with the handling of files with underscores in their filepath which wasn't being correctly handled causing some of the filename to be lost when shown as the title if title reading is delayed Fixed a few things that might be behind NotSoDirect not being stable for some setups though am still not certain that the changes done for this are going to fully resolve the problem from the crash reports Fixed the OS toast handling when there's no prior shortcut in the OS start menu to now create the shortcut (needed to allow the yes/no buttons for the new build / post-release toast) to be done as a hidden one so it's less likely to cause annoyance for those not wanting to see it whilst still allowing this less than ideal OS api implementation requirement to be met to avoid toasts without the needed buttons Fixed a regression when moving from taglib1 to taglib2 which broke some of the handling in place to allow for external programs to still access files when wacup has a held open cached instance of the file Everything else Updated cppwinrt (gen_win10shell.dll) to 3.0.260520.1 (26 May 2026) Updated libcurl (libcurl.dll) to 8.2.1 (24 Jun 2026) Updated Monkey's Audio (in_ape.dll) to 13.15 (28 Jun 2026) Updated mpg123 (mpg123.dll) to 1.33.6 (6 Jun 2026) Updated OpenSSL (libcurl.dll) to 3.5.7 (9 Jun 2026) Updated pugixml to 1.16 (16 Jun 2026) Updated taglib (tag2.dll) to 2.3.0 (11 May 2026) Updated vgmstream (in_vgmstream.dll) to the latest Git commit from 28 Jun 2026 Download: WACUP 64-bit | 9.6 MB (Freeware) Download: WACUP 32-bit View: WACUP Website | Screenshots Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Week One Done
      Collagen Project earned a badge
      Week One Done
    • Reacting Well
      Wakeen1966 earned a badge
      Reacting Well
    • Rookie
      Almohandis went up a rank
      Rookie
    • Apprentice
      jahara21 went up a rank
      Apprentice
    • Reacting Well
      NovaEdgeX earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      526
    2. 2
      +Edouard
      265
    3. 3
      PsYcHoKiLLa
      146
    4. 4
      Steven P.
      98
    5. 5
      macoman
      55
  • Tell a friend

    Love Neowin? Tell a friend!