The curious case of USA 276 is complicated by the sheer number of “coincidences” that appear to be involved. It is very easy (and dangerous) to descend into conspiracy theory and see everything as related. For example, consider the following summary list of “coincidences.” The quotation marks in this case are to indicate that it is open to debate whether this all is coincidental or not. Some or maybe all of them likely are true coincidences, but I leave it to the reader to decide:

    The “coincidental” similarity of the USA 276 orbit to that of the ISS;

    The launch moment “coincidentally” resulting in a very close encounter a mere month after launch;

    The “coincidence” that the close encounter distance stayed just outside the ISS safety zone, with a small margin only, just enough to avoid safety issues;

    The “coincidence” that the close approach happened around the approach and berthing of a US cargo ship, Dragon CRS-11.

    But there is more:

    When the launch of the Dragon CRS-11 was postponed for technical reasons, “coincidentally” it was decided that another US cargo ship, Cygnus OA-7, was suddenly to be unberthed from the ISS, a month ahead of the original schedule, on what would have been the original arrival date of CRS-11;

    Ball Aerospace, the same company that built USA 276, “coincidentally” also built RAVEN, an instrument to monitor spacecraft approaching the ISS that was “coincidentally” attached to the outside of the ISS only a few months before the USA 276 close encounter;

    As a commenter on my blog remarked, one of the US astronauts on board the ISS during the close approach, US Air Force Colonel Jack D. Fischer, “coincidentally” happens to have a military background in the space intelligence community (he served in the Space and Intelligence Capabilities Office), and his presence on the ISS was “coincidentally” bumped up to the current 51/52 ISS expedition. He originally was scheduled for the later 52/53 expedition: the change in his crew assigment was announced late November 2016.



This is really cookin' my noodles. Something sigint related during the docking/undocking process? (Wow, that's like SoOoO specific!)

^ Gorgeous specimen. The 100% opaque watermark, a pinterest embed, the fact that this image was found by googling "kentucky derby tin foil"... That's gonna derail any comment thread.

But 4srs, I don't think we'll ever know. I've gotten some straight-up threatening mail from a gov't contract ex-employer (that I left on 100% bueno terms) about violating intellectual property ownership laws. If we ignore the fact that all my IP is supposed to be public knowledge anyway, and extrapolate to DoD-level secrecy, I guess things like this can get pretty tight-lipped.

I keep flipping and flopping on how I see the deep state lately.

edit: kleinbl00 hey, I just remembered that you guessed SIGINT last time, right? Sorry, it's a weird time for my brain.

posted by kleinbl00: 17 days ago