News DMSP Flight 13 Satellite Explodes in Orbit

Thunder Chicken

Resident Lua Script Rabble-Rouser
Donator
Joined
Mar 22, 2008
Messages
5,847
Reaction score
5,510
Points
188
Location
Massachusetts
Last edited by a moderator:
It apparently failed around 1715 UTC, which would have put it over the Americas somewhere.

As if that location matters.... how about the Gabbard plot of the debris, how bad is it?
 
Last edited:
That might make life on the ISS interesting.

Depends on the DV relative to the original orbit, that is why I asked for the Gabbard plot... could also be possible that the fragments will need some years before sparsely contributing to the ISS orbit hazards.
 
I had no Idea a "weather" Satellite had so much explosive capacity.
I assume that a substantial portion of the total mass was Binary Hypergolic Fuel?
Is it possible for software to be rewritten to CAUSE such a failure ?
Which reminds me, where is the origin of the hardware components,
I would be worried if it was Taiwan. It would be incomprehensible if it was
from a PRC source.
 
I had no Idea a "weather" Satellite had so much explosive capacity.

Could also just be the batteries, which have also a lot of explosive capacity.

Also fuel tanks of old satellites and rocket stages does not explode because of the remaining fuel inside them, but because the pressurant gas inside got simply heated by sunlight until the pressure inside the tank exceeded the structural limits. Some fuel can also decompose at higher temperatures and contribute to heating and pressure, but that's not needed.
 
Last edited:
I had no Idea a "weather" Satellite had so much explosive capacity.
I assume that a substantial portion of the total mass was Binary Hypergolic Fuel?

A similar satellite, DMPS-F11, exploded in April 2004. Suprisingly, it had been passivated and was non-operative. The only source for the energy aboard that caused the event was (just) 6 kg of hydrazine.

It does not take a lot to make a satellite shed chunks. Those things are fragile.
 
I had no Idea a "weather" Satellite had so much explosive capacity.
I assume that a substantial portion of the total mass was Binary Hypergolic Fuel?
Is it possible for software to be rewritten to CAUSE such a failure ?
Which reminds me, where is the origin of the hardware components,
I would be worried if it was Taiwan. It would be incomprehensible if it was
from a PRC source.

Since it's a DoD bird, I highly doubt it would use foreign components, for exactly that reason.
 
Could also just be the batteries, which have also a lot of explosive capacity.

Also fuel tanks of old satellites and rocket stages does not explode because of the remaining fuel inside them, but because the pressurant gas inside got simply heated by sunlight until the pressure inside the tank exceeded the structural limits. Some fuel can also decompose at higher temperatures and contribute to heating and pressure, but that's not needed.

Especially since these are solar synchronous satellites. They are exposed to solar radiation all the time so they need to reflect/re-radiate all of that heat, plus any produced by the electronics. If the reflective coverings degrade, things can get dangerously hot very quickly.
 
A similar satellite, DMPS-F11, exploded in April 2004. Suprisingly, it had been passivated and was non-operative. The only source for the energy aboard that caused the event was (just) 6 kg of hydrazine.

Why do people always ignore the batteries?

An electrical fire/overheat almost always poses a greater risk of explosion than unburned fuel does.
 
Why do people always ignore the batteries?

An electrical fire/overheat almost always poses a greater risk of explosion than unburned fuel does.

They weren't ignored. :lol:

Can't find the article to link it like I should've done earlier, but the batteries on F11 WERE discharged; that's why the ONLY source of energy onboard was the residual hydrazine.

I'm more interested in how they determined it was 6 kg of that stuff. Ether they knew beforehand, or they figured out how much was still onboard. The former might mean they left that residual inside the satellite's tank and didn't (or couldn't) vent it.

EDIT: found it.
 
Last edited:
Well, whatever the cause of the explosion, I tracked the main body of the satellite this morning. It appears to be rotating at a cadence of about once every 30 seconds judging by the initial interval of the "satellite flares" in brightness that I observed, so about 12 degrees per second rotation.
https://www.youtube.com/watch?v=FBYyTKew1y0
 
Well, whatever the cause of the explosion, I tracked the main body of the satellite this morning. It appears to be rotating at a cadence of about once every 30 seconds judging by the initial interval of the "satellite flares" in brightness that I observed, so about 12 degrees per second rotation.
https://www.youtube.com/watch?v=FBYyTKew1y0

And folks, *this* is why I come to OrbiterForum for my spaceflight information!

Very cool MessierHunter! :cheers:
 
As if that location matters.... how about the Gabbard plot of the debris, how bad is it?

Not so bad.

I gave this a try based on 46 pieces being tracked now and searchable on the Heavens-Above database. This is what I came up with:



Looks like a fairly low energy event with the vast majority of debris staying in a similar orbit as the satellite at just above 800 km.

Here is the Excel file I used to calculate for those interested:
 

Attachments

Not so bad.

I gave this a try based on 46 pieces being tracked now and searchable on the Heavens-Above database. This is what I came up with:

Yeah, that looks like a rather weak fragmentation event, much different than for example a collision of two satellites or a fuel tank explosion.
 
A U.S. National Oceanic and Atmospheric Administration satellite retired in 2014 has suffered an apparent breakup.

Tough break. It might be more difficult for retired satellites to find the right match, but they definitely should keep looking. It's a quality of life issue.
 
Back
Top