Book One ... the documents
doc 01
Satellite Services Corporation
Transmission to: cosmo communications
... PRIORITY ONE .........
Attention: Ralph Little, Operations Manager
Status: eyes only >SECURE TRANSMISSION KEY>
validation: ******
Subject: satcom04
Date: Saturday September 14
Time: 2314
Copy: JPL Technical Division, Guidance Control
Copy: Goddard Space Flight Centre, Flight Control
Ralph, this is to confirm our conversation of a few minutes ago, we have an on-board Command Data system failure that can only be attributed to your company's failure to adhere to the log-on protocol timetable for satcom04. The protocol states clearly that log-on may only be initiated after SatServices gives you the go-ahead, that is after SatServices has checked and approved all systems as functional.
We have not yet completed systems checks after orbit insertion and we are now not in a position to do so. Your premature access and log-on has caused a complete blockage of all on-board transmissions.
1 ... The Command Data System CATA 0092 is inaccessible. We read full data blockage in the 0092 on-board computer.
2 ... The hard-programmed sequencers for initial Attitude and Articulation Control functioned as programmed and the satellite is in orbit with all three axis in correct attitude.
3 ... We are unable to upload the sequencer programs to enable the dual function telemetry.
4 ... We are working on clearing the blockage but we do not hold our chances of success as being high.
A record of our systems approval protocol is attached for your information.
You will receive further information as soon as we have completed a full evaluation.
Satellite Services
Walter Brown
Tt/wb 0914912315
doc 02
Satellite Services Corporation
Transmission to: cosmo communications
.... PRIORITY ONE.........
Attention: Ralph Little, Operations Manager
Status: eyes only >SECURE TRANSMISSION KEY> validation: ******
Subject: satcom04
Date: Saturday September 14
Time: 2317
Copy: JPL Technical Division, Guidance Control
Copy: Goddard Space Flight Centre, Flight Control
Ralph, the attached protocol is a short version, the rest is more of the same. We have tried for the past 12 minutes to re-establish connection. We have contact but cannot access the on-board services. The systems analysis protocols are continuing, latest report is that there is no further on-board activity but we still cannot connect.
We note your teleconned statement that you have not made log-on contact. We are looking at alternative causes.
Satellite Services
Walter Brown
Tt/wb 0914912318
091491210210 satserv/satcom04
>checkprotocol>trans>initiate
>checkprotocol>trans>initiate>210212
>checkprotocol>trans>initiate>210212>0
>>no connect
retry>checkprotocol>trans>initiate
>checkprotocol>trans>initiate
>checkprotocol>trans>initiate>210222
>checkprotocol>trans>initiate>210222>0
>>>no connect
>stop
system evaluation>vhftraffic source? recvr not resp
>checkprotocol>trans>respond
>checkprotocol>trans>210232>0
>>>>no connect
>stop210232
doc 03
cCom®
COSMO COMMUNICATIONS
Express Message Service
to
Satellite Services
Launch Centre Kourou
from
Ralph Little September 14 2322EST
Att: Walter Brown
Ref: P/1 trans Tt/wb 0914912315 and Tt/wb 0914912318
Security: in clear
Walter as I said on the telephone I am absolutely sure we have not made any transmissions at all to sc4, we do not yet have the pass protocol and await your verification and clearance to communicate.
I certainly do not know what is going on here maybe your systems are unsound. This is something you have to sort out and if this is a d-n-o then you better find a way out.
We are programmed to set up trial transmissions in ten days and sc4 is essential to that.
Let me know if we can do something but first get us a double check report on whats going on.
Little
stRL
0914912322est
doc 04
Satellite Services Corporation
Transmission to: cosmo communications ....PRIORITY ONE.........
Attention: Ralph Little, Operations Manager
Status: eyes only >SECURE TRANSMISSION KEY> validation: ******
Subject: satcom04
Date: Sunday September 15,
Time: 2105
Copy: JPL Technical Division, Guidance Control
Copy: Goddard Space Flight Centre, Flight Control
Ralph, we have tried all possible tests, satcom4 is incommunicado.
As far as we can decipher the CATA 0092 on-board computer has been blocked by a massive input of data that has not been retransmitted and we cannot initiate same. We are still working on this however prospects look bleak.
We have 16K sequencer RAM that is accessible but this is totally inadequate for the uploads necessary.
As JPL supplied the system similar to but upgraded to that used on Galileo we have to understand that the system itself is not the problem. However this is not a radiation hardened system and we may have Single Event Upset such as ion bombardment or some other kind of particle or ion intrusion. Unfortunately and as we all know we do not have any dual redundancy here and for the future we should consider the cost effectiveness of this aspect. SEU's are not uncommon.
There are other launches planned and we will attempt to recover satcom4 as and when there is a workable possibility.
Our program for satcom5 can be brought forward but we have to rethink the access configurations to eliminate a recurrence of this. You will be advised.
We are carrying out further tests to establish the source of the data stream to the on-board services however this is a long project. We are working on system blockers that will shut out all transmissions until we are ready. There is a slight chance of a competitor attempt or maybe a foreign source attempt at sabotage or espionage. We have called our project officer at Defense Satellite Communications Systems to work on this last item. The DSCS will know if there are any extraneous transmissions at this level. Any ideas?
You will get full details at our satcom project meeting tomorrow, let's discuss items in the last para above.
Satellite Services
Walter Brown
Tt/wb 0915912107
doc 05
Satellite Services Corporation
Transmission to: TMOD at JPL Pasadena
Attention: Mark Ripley, External Missions Manager
Status: eyes only >SECURE TRANSMISSION KEY> validation: **
Subject: satcom 04
Date: Monday, September 16
Time: 0930 hrs
Mark, this is to confirm our telecon this morning, we have an on-board system failure on satcom04. We have no details yet but the cause seems to be a massive data transmission from as yet unknown external sources. While we await further information from JPL's Guidance Control Section we are going to advise the Defense Department via Martin Amis at DSCS that we suspect some kind of sabotage attempt and ask them to monitor similar instances and if possible to see what can be done to track the source. They have enough satellites up there and they may also have experienced something similar. Besides that they can get access to Echelon, which is supposed to be able to track and source this kind of thing, isn't it?
In the meantime, we request a placement on the Shuttle Orbital Rendezvous Program for a recovery and communications module exchange. This will naturally take some time but we will have an exchange unit available as of November.
It seems to us to be highest priority to recover the failed module to establish who transmitted the data stream, and therefore a priority placement is requested.Formal application will tabled at the next TMOD External Operations meeting.
Please keep us advised on the program schedules. A partial transcription of the module communication protocol is attached for your information. This is not all of it but contains the critical sequence.
You will receive further information as soon as we have completed a full evaluation.
Satellite Services Laboratories
Walter Brown
Tt/wb 0916910930
091491210210
doc 06
Satellite Services Corporation
Transmission to: Defense Department,
Defense Satellite Communications System
Attention: Director's Office, Martin Amis
Status: eyes only >SECURE TRANSMISSION KEY> validation: ****
Subject: satcom 04
Date: Monday, September 16,
Time: 1030 hrs
Good Morning Martin, good to hear from you this morning that business is rocking along as usual in the DSCS.
As advised and in confirmation of our telecon this morning, we have an on-board system failure on satcom04. We have no details yet but the cause seems to be a massive data transmission from as yet unknown external sources. JPL's Guidance Control Section have been advised, including the fact that we suspect some kind of sabotage attempt.
Due to the form of the failure and its unknown source, we will initiate the required Security Protocol .This should be on the Director's desk later today.
As discussed we will also suggest that DSCS carries out a complete systems check on its own satellites with the view to establishing whether any similar data streams have been detected. We will also request that we be fully informed under full security protocols about any such transmissions. We too have a lot to lose here and we want to find out as soon as possible what is going on.
We acknowledge your promise to put this in action soonest.
I am sure that it will be a good idea for you to be at the next TMOD External Operations Meeting, and hopefully you will have some initial information for us at that time.
A full transcription of the module communication protocol is attached for your information.
You will receive further information as soon as we have completed a full evaluation.
Satellite Services Laboratories
Walter Brown
Tt/wb 0916911030
doc 07
JPL
Telecommunications and Mission Operations Directorate ... TMOD
December 12
Confirmation: Mission Planning, STS Orbital Rendezvous Program (STS-ORP)
SATCOM .. 04
Satellite Recovery and Module Exchange
Confirmation for first in-orbit vehicle rendezvous, Mission date May 05.
Details:
Agency: NASA
Mission Code: STS-49
Payload: Endeavour F01, satcom04 CME
Mass: 14,786 kg
Perigee: 268 km
Apogee: 341 km
Inclination: 28.3 degrees
Period: 90.6 minutes
Duration: 9 days
Crew: Akers, Brandenstein, Chilton, Hieb, Melnik, Thornton, Thuot.
Recover satellite, remove communications module, replace with satcom04 CME, orbital
re-insertion. Satcom04 orbital requirements.
Distribute to:
Operator: Cosmo Communications
Launch Contractor: Satellite Services Laboratories
DSCS: Martin Amis
Directorate Planning Meeting December 12
doc 08
JPL
Telecommunications and Mission Operations Directorate
TMOD
May 14
Confirmation: Mission Completion, STS Orbital Rendezvous Program (STS-ORP)
SATCOM 04
Satellite Recovery and Module Exchange
Confirmation:
satcom04 recovered and CME executed.
satcom04 re-inserted into orbit according to SatServices Mission Planning.
Details:
Agency: NASA
Mission Code: STS-49
Payload: Endeavour F01, satcom04 CME
Mass: 14,786 kg
Perigee: 268 km
Apogee: 341 km
Inclination: 28.3 degrees
Period: 90.6 minutes
Duration: 8.89 days
Crew: Akers, Brandenstein, Chilton, Hieb, Melnik, Thornton, Thuot.
Operational Crew for CME: Thuot, Hieb, Akers.
Distribute to:
Operator: Cosmo Communications
Launch Contractor: Satellite Services Laboratories
DSCS: Martin Amis
Directorate Operations Meeting May 13
doc 09
JPL
Telecommunications and Mission Operations Directorate
TMOD
September 14
To Satellite Services Laboratories, Attention: Walter Brown
Satcom 04
Recovered Communications Module
Walter,
the satcom04 communications module is on its way to you as discussed.
Our people at JPL CalTech in Spacecraft Data Systems Section have made a first analysis of the data contents and can make no sense of it at all. It is not a data format known to us. Do you guys have your own encryption that we dont know about?
Once you have had a look at this effect, whatever it is, would you let us know what it is? It may be of interest to us on other missions. If you cannot decipher the data block, send the whole thing back to me here and I'll get some DSCS experts together to see if they can crack it.
The DSCS has a report on the data stream and I'm sure they would like to look at it for their analysis and for comparison purposes to known foreign data sources.
Let's work together to find out what this is. Please keep me advised of your progress, and let me know if you need some expert help.
Mark Ripley.
Copies to:
Operator: Cosmo Communications
Launch Contractor: Satellite Services Laboratories
DSCS: Martin Amis
doc 10
Directorate of Defense Satellite Communications Service
DSCS
Office of Martin Amis EYES ONLY SECURE TRANSMISSION
June 16
To:
Walter Brown, Director of Operations, Satellite Services Laboratories
Mark Ripley, TMOD Pasadena
Copies to :
Defense Secretary, Pentagon, Washington DC
Security Operations, NASA.
Gentlemen,
recent events revolving around the failure to orbit of satcom04 and the subsequent recovery and analysis of its communications module have included studies of data streams within our own DSCS satellites and those of several cooperational partnerships in Germany, Japan and China.
We have the following:
1: satcom04 failed due to the intrusion of a massive data stream into its on-board computers at orbit insertion completely blocking its communications capabilities.The results from the satcom04 analysis show only that there is a data stream but all efforts have failed to decipher it.
2: analysis of DSCS satellites also reveal several instances of communication problems but for understandable security reasons we can give no further details. We can however say that although there have been several DSCS satellite failures, notably DSCS 2 F5, F6, and F10, there is no reason to believe that these were caused by similar data intrusions.
3: analyses by our cooperational partners have also shown several events of communications failures, notably the following:
With the Russians: Proton 8K82K Mars mission (Fobos 1), and Fobos 2, among others that were launched from Baikonur.
With the Germans: the DBS/DBP Telekom launched from Kourou on Ariane 2, also among others.
Further, COMSAT reports that both Intelsat 5A launched from Kourou, and Intelsat 6 had similar communication failures, as with Orbcomm's first two communication satellites. There is however, no evidence or other reasons to give credence to the idea that these failures stemmed from similar data stream intrusions.
4: A classified Shuttle Mission in xxxx was launched because of several of these failures, in a recovery attempt , but the satcom04 recovery mission in xxxx has been the first successful recovery operation.
Initial analysis of the data stream from satcom04 is inconclusive. Because it is indecipherable the received wisdom is that it is probably a collection of rogue transmissions from an experimental telecommunications service that has become completely garbled through multiple rerouting or bounce effects within and through the upper Earth atmosphere, possibly also connected to solar disturbances.
Our Diplomatic services further advise of no potential that these transmissions have come from a foreign intelligence service.
In view of the above, we see no grounds for further action ourselves at this time. Further, we perceive no security threat at this time.
We have been advised that the Defense Department will continue to monitor extraneous transmissions on an increased priority basis.
We have been further advised that the data from satcom04 will continue to be the subject of intensive investigation at the Jet Propulsion Laboratory's technical services centres.
We understand that the TMOD will work with JPL in this respect.
For the time being, Mark Ripley at TMOD will act as communications monitor with our office and those of Satellite Services Laboratories, and with JPL's technical services.
Thank you for your cooperation in this matter,
DSCS
doc 11
COPY OF EVENT REPORT
ARECIBO Puerto Rico December 15
Transcript of Incident Reports December 14ARECIBO Space Center
Report by Security Guard GordanoAt 1714 hrs December 14 Dr Stone and Professor Hallman passed through the gates on their way down. I entered the log record and looked up to watch them driving down the mountain towards the hairpin over the bridge to the main road. The auto was not going very fast but then it swerved a couple of times and then they lost it, headed across the main road and hit the bank on the other side of the road and stopped.
I called Central at 1718 and reported an accident, thought they better get an EV down there straight away because I couldnt see any movement.
The EV passed through at 1721 and arrived down there at 1724 and after a few minutes they got the two out and in to the EV.
Report by Security Central, Duty Officer Wiles:
Gate Security called in at 1718 reporting an accident at the site road junction with Mountain Road. An Emergency Vehicle was despatched at 1719 and arrived on the scene at 1724. The EV driver Manolo and Paramedic Gonzalez radiod a situation report as follows: The vehicle, a Toyota Land Cruiser from SETI, was crunched into the road bank with not too much damage. Dr Stone who was driving was dazed and had arm injuries and some blood on her face. Prof. Hallman had facial injuries, a blood nose but seemed to be otherwise OK. I authorized immediate transport to Arecibo Town to the Medical Centre Outpatients for medicare.
A recovery vehicle was despatched to recover the SETI vehicle and to return it to the site workshop for possible mechanical checks to establish any mechanical faults. The vehicle's electric system was not functioning. Fotos were taken at the site and are on file, copies attached.
Subsequent vehicle checks reported that the electrical system was in order and there was no evidence to suggest why it was not in order at the scene. Mechanic Roviro supposed a temporary loose battery connection caused by the accident. All mechanicals in order. Repairs were carried out to minor bodywork damage.
Report from ARECIBO Town Medical Centre Outpatients, Med. Superintendent Sister Maria.
Dec.14, 1825 hrs
The Arecibo Space Centre EV arrived at 1827 and PMO Gonzalez reported two injured as a result of a traffic accident at the Site. Two patients were admitted, both ambulant with possible minor injuries and shock.
Dr Avril Stone was admitted with minor facial contusions and a possible left arm fracture. MO Pariso attended. Dr Stone was transferred to Observation and held overnight and released at midday December 15, after interview with Adjutant Garcia.
Professor Richard Hallman was admitted with facial contusions and possible concussion. MA Ferrero attended, MO Pariso carried out receptor tests. Professor Hallman was transferred to Observation and held overnight. Released after further tests and after interview with Adjutant Garcia December 15.
Report by ARECIBO Town Policia, Adjutant Garcia. (translated)
I received a radio call from the Site EV Driver Officer Manolo that there was an accident near to the site on the Mountain Road and that two injured were being brought down town to the Med Centre. I was in attendance at the arrival of the EV and saw that the two injured had minor injuries. Sister Maria advised that both were to be held overnight for observation.
December 15 at 1200 I interviewed Dr Avril Stone and Prof. Hallman, researchers at the Site.
Dr Stone was the driver of the auto and reported "that a very strong gust of wind had hit the auto very hard with a loud noise just as they were crossing the Site Road bridge to Mountain Road and caused the auto to swerve to the right. She tried to correct but the auto skidded on the loose surface at the side and went out of control across the main road into the road bank. She caught her arm in the steering and injured it and her face also hit the steering wheel.
Professor Hallman heard a loud noise but could not see anything as his spectacles dislodged with the violent movement of the auto. He felt another bang as the auto came to a stop and hit his nose on the grab handle on the panel in front.
Sister Maria stated that there was no evidence of alcohol.
Site Security advised by telefon that there was no mechanical fault on the accident vehicle and small damage only. No insurance certificate was required.
No further action.
Filed SecInc 098 12:15:
doc 12
The United States Department of Defense
Personell Diary Notice: Public Distribution
Date: EO
Everett StJohn Hillier
Born September 12, 1952, Phoenix, Arizona.
Profession: Security Management
Transferred from Pine Gap to Defense Satellite Communications Systems on
May 6, xxxx, seconded to Department of Defense effective this day.
Post: Washington, D.C.
Head of Digital Security Operations.
Priority Operations:
Satcomm 04 communications satellite and related commsat failures.
Issued by:
Secretary, Digital Security.
DOD
doc 13
The United States Department of Defense
Head of Digital Security Operations
Day Diary Date: October 21
Classification: none
Subject:
Cosmo Communications Satellite satcom04 recovered digital storage
History:
Recovered May 15 by STS, delivered to JPL Technical Division for analysis.
No analysis possible, unknown code structure.
Returned to Flight Subcontractor Satellite Services Laboratories September 14, xxxx, for further analysis.
No analysis possible, unknown code structure.
Delivered to TMOD Project Liaison Officer M. Ripley, January 12, further delivered to DSCS for code analysis ref>: foreign code sources, no relationships. Delivered to DOD Digital Technical Services January 19, xxxx, for further analysis and comparison to known foreign coding and structure.
No analysis possible, unknown code structure.
Delivered to this office October 21, xxxx, for further action as seems possible.
No priority.
Issued by:
Secretary, Digital Security
