Recommended Posts

A sh**storm?

Seriously, that could ground Russian vehicles until after the investigation and put even more pressure on Dragon and getting Cygnus flying regularly. An Enhanced Cygnus (stretched, center below) is on for an Atlas V launch November 19, 2015.

Accelerate Dragon 2? Possible, but the flight abort and the IDA docking ports have to fly first.

Cygnus variants

Cygnus-Congigurations.jpg

What would happen if the next Progress fails?

I may be wrong, but I thought there was an "expiry date" for the Russian escape module (ie 200 days for systems use). Could emergency escape also be a problem as well as supply depletion. As a side note, I wonder if Dragon2, in present state of development, could be used in an extreme emergency to rescue crew should an unthinkable event occur..... :(  

Oooops..posted too soon, got DocM reply just as I posted...Cheers... 

For those that missed it, as part of the fall-out from the Progress loss the ISS crewmembers that were supposed to go home today will now be staying an additional couple of weeks untill early June.

Sounds like a weird reaction, if anything, they should leave earlier, since they now have less provisions than expected?!

 

I wonder if Dragon2, in present state of development, could be used in an extreme emergency to rescue crew should an unthinkable event occur..... :( 

As far as I understand they always have enough capsules docked to the ISS to send all the inhabitants home.

If one of them broke, perhaps an emergency solution would be in order, I don't think they have redundancy?

Anyway, the docking port for the Dragon 2 has not been installed yet, and is flying up with the next dragon (1) mission as far as I recall.

But I guess they could always just lay on the floor of the cargo dragon and hope for the best :-P

(Everything is written from memory, so a fact check might be in order, but I have to go to bed now :-P )

 

Sounds like a weird reaction, if anything, they should leave earlier, since they now have less provisions than expected?!

 

As far as I understand they always have enough capsules docked to the ISS to send all the inhabitants home.

If one of them broke, perhaps an emergency solution would be in order, I don't think they have redundancy?

Anyway, the docking port for the Dragon 2 has not been installed yet, and is flying up with the next dragon (1) mission as far as I recall.

But I guess they could always just lay on the floor of the cargo dragon and hope for the best :-P

(Everything is written from memory, so a fact check might be in order, but I have to go to bed now :-P )

 

Thank's for the reply. I went checking on a few sources. I did not know, but at one time a CRV (Crew Return Vehicle) was in the works but was cancelled when Russia paired up with the  ISS, The Soyuz TMA's were now to be used, 3 person each BUT, the capsules do have a "shelf Life" and are rotated out every 6 months due to the corrosive fuel eating tanks, among other things. It would appear to be a real problem as DocM has stated, if a multiple failure or "grounding" of craft were to occur. We definitely need alternate "sources of transport"...Cheers...

Just an amendment to my prior post, I had checked multiple sources but did not know the verification of these sources and did not include them...So with a "grain of salt", it appears that the TMA-M have life support abilities of 30 person days, and 200 day "shelf life". I assume the 30 person days would be 10 days for a 3 person crew. It appears the TMA-M can be used for evacuation with a 3.5 hour return sequence for departure. Surprisingly, there are quite a few "user manuals" available for Progress, Soyuz launchers and TMA-M from sites such as ESA, Arianespace and Russian space sources in pdf format. I have some reading to do....Sorry about the unverified sources...Cheers...

The problem is that you can't really launch new Soyuz to re-crew and serve as lifeboats during an investigation, and another loss of a Progress (or, God forbid, a Soyuz) could cause an extensive grounding.

Depending on the initial 'cause theory,' ex: a guidance or maneuvering system failure, it may even preclude the lifeboats use to return to Earth.

There's a lot of ways this could go to Hell in a handbasket.

Especially with all the static SpaceX and the other "New Generation" companies have been running into trying to get their gear certified and tested. Nobody would like the new systems to be on-line more than they would, but these things take time. Exhaustive testing, retesting, test some more, then prove to the "adults" that you know what you're doing .. it can be tedious and frustrating, but the process is as it is for a reason.

 

After all, as far as the "established space companies" are concerned (ULA, Lockheed/Martin, etc), these new companies are "the new kids" and need to prove themselves.

 

No worries, folks. Things will work out.

With the crew extension, the female record for time in space will be broken But...one TMA-M will be slightly over 200 days....I assume the engineering  safety factor will cover them.

 

Imagine the migraines when OldSpace has to deal with not only SpaceX but Blue Origin, Orbital Sciences and at least 2 other outfits flying affordable launchers.

It will be great to see all the "young guns" revolutionize space travel....Cheers.... :D

Propellant Tanks ruptured on the Soyuz Upper Stage, eh. I knew it was either a fuel/propellant rupture (tanks or lines) or flight computer failure.

 

It took an investigation to get Roscosmos to finally come clean about what happened. Shame on them. They can't not have known about that problem when it occurred.

 

Anyway, they'll find out what went wrong and deal with it. Hopefully in the future they'll be more direct and forthright. This kind of thing can (and WILL) lose business for their organization.

Yep. :( And it's likely that they use those same tanks on all Soyuz-Class craft. Those will need to be checked for integrity before installation, now. Those units that have already been installed will likely need to be removed and inspected in the same fashion.

 

Another Soyuz TMA prepped for flight in a month means that it's going through final certification for flight readiness -- so it's likely that the tanks in that one will have come from the same lot as the ones in Progress that failed. If they don't check those, and there's another failure, Roscosmos will have a massive debacle on their hands, not limited to gross negligence for using them. I truly hope they err on the side of caution, as Russian common sense dictates that they adhere to.

Yep. :( And it's likely that they use those same tanks on all Soyuz-Class craft. Those will need to be checked for integrity before installation, now. Those units that have already been installed will likely need to be removed and inspected in the same fashion.

 

Another Soyuz TMA prepped for flight in a month means that it's going through final certification for flight readiness -- so it's likely that the tanks in that one will have come from the same lot as the ones in Progress that failed. If they don't check those, and there's another failure, Roscosmos will have a massive debacle on their hands, not limited to gross negligence for using them. I truly hope they err on the side of caution, as Russian common sense dictates that they adhere to.

This link is informative...about the Progress composition...

http://www.space.com/12725-russia-progress-cargo-spacecraft-infographic.html

Progress and Soyuz-TMA use much of the same hardware to save on production time & cost. The Soyuz platform is a very flight-proven design, having flown for 30+ years and has been continually upgraded the whole time. But Roscosmos needs to be careful -- they are prudent, common-sense, and quite expert at what they do, and they don't need another accident that potentially takes the lives of three people when it could have been avoided.

 

Those tanks need to be inspected for manufacturing defects -- the entire production run of those tanks using that shipment of materials, personnel, equipment, and installation practices. They need to be absolutely certain the failure won't happen again, because human lives will depend on it. Nothing left to chance.

 

If it turns out that the Progress failure was caused by a strike from a piece of space debris (entirely possible), then the notion of cleaning up launch corridors needs to be revisited.

 

I suppose that's the point I'm trying to make.

I see what you mean. What compounds this even worse is the corrosive fuel generating the "shelf life" for "good tanks". You are right...They need to really put  emphasis on the quality control of these units and do an inspection on all tanks and processes.....cheers...

Those propellants are pretty rough on whatever they are being held in. There are stories about how nasty Hypergolics (in particular) are on storage tanks. The stuff Soyuz uses isn't nearly as extreme, but the metals are subjected to extremes of cold and pressure and become quite brittle if the alloy isn't perfect. Launch forces, not to mention the vibration itself, could easily damage and even outright shatter a tank that isn't up to specs.

 

I'd be very interested in metallurgical testing of those Progress tanks, if they can even find any that survived reentry. I'd bet a box of Twinkies that there are anomalies in the alloy's composition unrelated to reentry heating and seawater. What they CAN do, however, is take a look at the tanks whose alloy was mixed and poured into moulds the same day (preferably within a few hours) as the ones used in Progress and check for any irregularities in the alloy, as well as run full integrity checks on the tanks themselves. They'll likely reproduce the failure on the ground at that point.

 

Cheers!

Those propellants are pretty rough on whatever they are being held in. There are stories about how nasty Hypergolics (in particular) are on storage tanks. The stuff Soyuz uses isn't nearly as extreme, but the metals are subjected to extremes of cold and pressure and become quite brittle if the alloy isn't perfect. Launch forces, not to mention the vibration itself, could easily damage and even outright shatter a tank that isn't up to specs.

 

I'd be very interested in metallurgical testing of those Progress tanks, if they can even find any that survived reentry. I'd bet a box of Twinkies that there are anomalies in the alloy's composition unrelated to reentry heating and seawater. What they CAN do, however, is take a look at the tanks whose alloy was mixed and poured into moulds the same day (preferably within a few hours) as the ones used in Progress and check for any irregularities in the alloy, as well as run full integrity checks on the tanks themselves. They'll likely reproduce the failure on the ground at that point.

 

Cheers!

That would be the way to do it...similar to industrial QC and QA......You are right about the harsh environment those tanks are subjected to.... Makes you wonder about the integrity of the tanks installed on the TMA-M's on the ISS, more so as 200 days approach. I hope the Dragon V2 docking mechanism will be on CRS7...one step closer to an alternate...Cheers... 

  • 4 weeks later...

Russia just completed a surprise launch with same rocket as the Progress failure....

 

 

 

Russia has launched its Soyuz 2-1A rocket in a surprise mission from the Plesetsk cosmodrome at 15:24 UTC. The launch, using a rocket that recently failed during the Progress M-27M mission, was clouded under secrecy due to its payload, the Kobalt-M spy satellite

post-546174-0-97675200-1433662664.jpg

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • XnConvert 1.112 by Razvan Serea  XnConvert is a cross-platform batch image-converter and resizer with a powerful and ease of use experience. All common picture and graphics formats are supported (i.e. JPG, PNG, TIFF, GIF, Camera RAW, JPEG2000, WebP, OpenEXR) as well as supporting over 500 other image formats. Also available within the batch operations include rotating, adding of watermarks, adding of text along with many image-adjustment features such as brightness, shadows and more. Among the features included are: Batch adding of files and folders Support for drag and drop of files Batch rotating, cropping, resizing and more Adding of photo masks Preserving or removing image metadata in conversions Multipage image file support (i.e animated GIF, APNG, TIFF) Command line integration via NConvert Filters - such as 'Blur', 'Gaussian Blur', 'Emboss', "Sharpen' and much more Effects - such as 'Old camera' and much more Download: XnConvert 64-bit | Standalone | ~30.0 MB (Freeware) Download: XnConvert 32-bit | Standalone Links: XnConvert Website | Screenshot | Release Announcement Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Microsoft updates Visual Studio Code with chat cost tracking and multi-agent chats by Paul Hill Microsoft has just launched Visual Studio Code 1.126, its latest weekly release. This time, the company has focused on letting you see the total cost of chat sessions to spot expensive conversations; enabling multiple chats per session that run side-by-side in one agent host Copilot session; and letting you browse new folders safely in restricted mode. We have now reached the stage where free AI in IDEs is coming to an end. To help you keep track of your costs, VS Code now lets you see the entire cost of a chat session, rather than just individual turns. This should give you more transparency about which sessions consume the most credits, so you can better manage your usage over time and spend less. For those of you using the Agents window, you know it is possible to run and manage multiple agent sessions at once. In this update, a Copilot session started from an agent host can hold several chats at once. Explaining how this feature works, Microsoft writes: Finally, from this update forward, Microsoft will remove the pop-up when opening an untrusted folder. When you open a new folder now, it will automatically open in Restricted Mode. You will see a banner that lets you manage the trust level of the folder. Microsoft has made this change so that it’s easier to start inspecting code without giving it trust right away. If you have VS Code, you can check for updates within the app now to get this new version. Otherwise, you can download it from the Visual Studio Code website.
    • Anthropic accuses Alibaba of using 25,000 fake accounts to copy Claude's capabilities by Karthik Mudaliar Anthropic has accused Alibaba of using nearly 25,000 fraudulent accounts to extract capabilities from Claude on a huge scale. According to a report from Reuters, Anthropic told US lawmakers that operators linked to Alibaba and the company’s Qwen AI team generated 28.8 million exchanges with Claude between April 22 and June 5, 2026. That is a lot of Claude conversations, but Anthropic says this was not ordinary chatbot use. The company believes the accounts were part of a coordinated effort to collect answers that could help train or improve rival AI systems. The alleged campaign reportedly focused on some of Claude’s most valuable skills, including software development, multi-step reasoning, and agentic tasks. In practical terms, that means getting an AI model to plan and complete work across several stages rather than simply answering a single question. This is called 'distillation,' where AI companies use outputs from a larger model to train a smaller and cheaper one. The smaller model learns to imitate useful parts of the more capable system without needing the same amount of computing power. The distillation process isn't automatically suspicious, but the problem comes when one company gathers another provider's outputs without permission and at an industrial scale. Also, this does not mean Alibaba obtained Claude’s source code, model weights, or original training data. Instead, Anthropic claims the accounts repeatedly asked Claude carefully designed questions and collected the answers. Those answers could then be used as training material for another model. Anthropic has made similar accusations against DeepSeek, Moonshot AI, and MiniMax earlier this year. As Neowin previously reported, Anthropic said those three companies collectively generated more than 16 million Claude exchanges through roughly 24,000 accounts. Anthropic says the new campaign produced almost twice as many exchanges in a matter of weeks. Anthropic reportedly told lawmakers that the campaign could help Chinese AI developers approach the capabilities of its Mythos Preview model. Mythos is focused on advanced cybersecurity work, including finding and exploiting complex software vulnerabilities. via Reuters | Photo via DepositPhotos.com
    • An Indian manufacturer that assembles roughly one-third of Apple's iPhones and supplies semiconductor components to Tesla confirmed Monday that attackers had stolen and publicly published a 630-gigabyte cache of confidential files — including engineering blueprints stamped "TRADE SECRET," a 52-page quality inspection document for iPhone circuit board components, and cryptographic certificates that security experts say could be weaponized in follow-on attacks. https://www.techtimes.com/articles/319019/20260624/apple-tesla-supplier-tata-electronics-confirms-630-gb-data-theft-iphone-specs-dark-web.htm
  • Recent Achievements

    • Rookie
      krychek57 went up a rank
      Rookie
    • Grand Master
      Jaybonaut went up a rank
      Grand Master
    • One Year In
      Philsl earned a badge
      One Year In
    • Dedicated
      Scoobystu earned a badge
      Dedicated
    • First Post
      Tom Schmidt earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      441
    2. 2
      +Edouard
      176
    3. 3
      PsYcHoKiLLa
      133
    4. 4
      Michael Scrip
      79
    5. 5
      Xenon
      77
  • Tell a friend

    Love Neowin? Tell a friend!