 |
Hitomi and its debris train
(click image to enlarge) |
In a previous post from a few days ago, I discussed the debris shedding event of the Japanese scientific Hitomi/ASTRO-H satellite (2016-012A) on March 26, ~01:42 UT, that is currently in the news. As things have developed, it appears that the picture has become more grimm, as the available data now seem to indicate a real break-up rather than just "some" debris shedding. If true, then Hitomi is beyond saving.
On Friday, JSpOC published the first elements for 10 fragments produced. As part of it, the "A" identity (the largest remaining part of the original satellite body) was shifted to another object: what was assigned to be the remnant of Hitomi in the first few days, turns out to be not, but was the fragment now labelled "L". It was this fragment which was observed tumbling with a periodicity of 11.75 seconds. As it is rather bright, it indicates that Hitomi broke into at least two large pieces (I think it is actually three, as fragment H also seems to be large based on the NDOT/2 value) plus a lot of smaller fragments.
Based on the published elements, I calculated the following approximate delta V's for these fragments based on change in semi-major axis and inclination (velocity in meters per second):
fragment number delta V
A 41337 0.4 m/s
N 41444 0.3 m/s
Q 41446 0.4 m/s
P 41445 0.5 m/s
R 41447 0.5 m/s
L 41442 1.3 m/s
H 41439 1.4 m/s
J 41440 3.9 m/s
G 41438 7.2 m/s
M 41443 12.2 m/s
K 41441 13.7 m/s
Some clustering might be present in these speed data, roughly into three groups: a number of fragments yield low velocities in the range 0.3-0.5 m/s. Fragments L and H have ~1.3-1.4 m/s. And there is a group with high speeds from ~4 to ~14 m/s.
I performed a conjunction analysis using the first two to three published element sets for each fragment, and Rob Matson's COLA software. For a given fragment, I looked for the element sets with small miss distances and relatively low ephemerid ages relative to the calculated conjunction.
The result is in the diagram below. Note that some fragments appear twice in the diagram, as they sometimes yield two equally well fitting close approach times. There clearly is scatter and ambiguity in the results.
The data nevertheless show a clear cluster close to the estimated time that JSpOC published, 01:42 UT on March 26. The strongly deviating times to the right in the diagram are probably inaccurate and concern small fragments with a quick orbit decay (large NDOT/2 value), the reason why they are less accurate.
 |
| click diagram to enlarge |
I find it interesting that the A fragment seems to plot somewhat earlier than all the others, near 01:10 UT, but think it is wisest to chalk this down to orbit inaccuracies.
Ted Molczan has argued for a possible second debris-shedding event at ~02:35 UT, near the next perigee passage. Fragment K, but in my opinion perhaps also P and Q would fit this time (P however also loosely fits to the 01:42 UT cluster. The Q fragment is probably small and has a larger miss-distance in the analysis, so might not be too accurate).
In order to understand what happened to Hitomi/ASTRO-H, a so called "Gabbard diagram" can be helpful. In a Gabbard diagram, the orbital period of each fragment is plotted against the apogee and perigee altitudes. That results in this diagram:
 |
| click diagram to enlarge |
The relative position in the diagram with respect to the original values for Hitomi/ASTRO-H before the event happened (indicated by solid dots, one for apogee and one for perigee), is informative.
Fragments plotting to the right and up of the original position are fragments that were ejected into the direction of the original satellite movement (prograde). They get longer periods and somewhat higher orbital altitudes. Fragments plotting to the left in the diagram, are fragments ejected opposite to the movement of the satellite in its orbit (retrograde). Fragments ejected perpendicular to the plane of movement of the satellite will plot in the vicinity of the original satellite values.
What can be seen in the diagram is that what is presumably the largest remaining object, fragment A, plots just right of the original Hitomi position: orbital period and apogee altitude slightly increased. A few more object plot around the original Hitomi/ASTRO-H values, but most of the fragments plot to the left: their orbital periods and orbital altitudes decreased. This includes the L-fragment, which based on visual observations and the NDOT/2 value relative to other fragments is likely a large fragment, as is probably fragment H.
I interpret this as follows: as indicating breakup from an origin somewhat behind the center of mass of the satellite (with respect to its direction of movement). This gives the heaviest remaining body (the A fragment), predominantly material originally located near/in front of the center of mass, a momentum in the direction of movement. Most other, smaller parts appear to have been predominantly ejected backwards, which is perhaps some indication that predominantly the 'rear' part of the satellite exploded with a notably backwards impulse.
This still says little about the cause of the fragmentation. My primary suspicion is however that either the liquid Helium tank of the Soft X-ray Spectrometer (SXS) situated near the base plate in the middle of the spacecraft exploded, or the nitrogen pressure tank of the thruster system (I am not sure where the latter is situated in the satellite, I have not been able to trace that information so far).
A preliminary analysis suggests that objects G and M will re-enter the Earth's atmosphere somewhere mid-April.
Updates:
[update 4 April 2016, 9:00 UT] My (and Google translate's) Japanese is abysmall, but this Japanese article seems to suggest the Helium tank indeed might be to blame, if I get it right. It also seems to suggest there was an attitude anomaly half a day before the main break-up, around 13:10 UT on March 25th.
[update 5 April 2016 7:30 UT] Thanks to a translation by my friend Ton Kruijer and a Twitter comment by Nobuyuki Kawai: what the Japanese article from the previous update says is that JAXA rules out an impact as the cause and thinks something happened "internally", in the spacecraft. No definite cause is identified, but the article speculates about the battery and Helium tank used for cooling SXS. There are however no clear indications about the cause in the telemetry received before contact was lost.
