Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 17 submissions in the queue.
posted by mrpg on Tuesday January 09 2018, @03:15PM   Printer-friendly
from the :-( dept.

A classified satellite launched by SpaceX on Sunday may be experiencing a classified failure:

Later on Monday afternoon another space reporter, Peter B. de Selding, reported on Twitter that he too had been hearing about problems with the satellite. "Zuma satellite from @northropgrumman may be dead in orbit after separation from @SpaceX Falcon 9, sources say," de Selding tweeted. "Info blackout renders any conclusion - launcher issue? Satellite-only issue? — impossible to draw."

Update: SpaceX said the Falcon 9 rocket performed nominally, but unnamed sources reportedly told the Wall Street Journal that the payload did not separate from the Falcon 9 second stage and that both fell into the ocean:

An expensive, highly classified U.S. spy satellite is presumed to be a total loss after it failed to reach orbit atop a Space Exploration Technologies Corp. rocket on Sunday, according to industry and government officials. Lawmakers and congressional staffers from the Senate and the House have been briefed about the botched mission, some of the officials said. The secret payload—code-named Zuma and launched from Florida on board a Falcon 9 rocket—is believed to have plummeted back into the atmosphere, they said, because it didn't separate as planned from the upper part of the rocket.

The WSJ report has been disputed. Space-Track has catalogued the Zuma payload as USA 280, international designation 2018-001A, catalog number 43098, but that doesn't necessarily mean Zuma survived. CelesTrak lists the status as operational (search 43098 in NORAD Catalog Number field).

If the mission did fail, SpaceX could also blame Northrup Grumman for using their own payload adapter.

Also at CBS News, SpaceFlight Insider, Bloomberg, Popular Mechanics, CNBC, and USA Today.


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 4, Insightful) by Ken_g6 on Tuesday January 09 2018, @04:51PM

    by Ken_g6 (3706) on Tuesday January 09 2018, @04:51PM (#620081)

    If the de-orbit burn for the upper stage was normal [soylentnews.org], I strongly doubt there was trouble with detaching the satellite. First, if they had problems detaching, I would expect them to leave the whole upper stage in orbit for several orbits trying to correct that problem. And second, even if for some reason they didn't try to continue the mission, a de-orbit burn with the satellite attached should have had significantly different characteristics from a normal de-orbit burn.

    Starting Score:    1  point
    Moderation   +2  
       Insightful=1, Interesting=1, Total=2
    Extra 'Insightful' Modifier   0  
    Karma-Bonus Modifier   +1  

    Total Score:   4