Communications Satellite Databases Part I

The 2008 Edition of Communications Satellite Databases

Chapter B: Subsystems and Anomalies

TelAstra, Inc. *Investment Analysis Roger J. Rusch, *Risk Mitigation President *Business Planning P.O. Box 4620 *Appraisals Palos Verdes *International Coordination CA 90274 *Systems Engineering Tel:(310) 373-1925 *Cost Modeling FAX: (310) 373-5539 *Competitive Analysis [email protected] *Regulatory Policy * Page 1 Copyright © 2003 by TelAstra, Inc. Communications Satellite Databases Chapter B COMMUNICATIONS SATELLITE DATABASES Chapter B: Subsystems and Anomalies

TABLE OF CONTENTS PAGE B1.0 Introduction...... 84 B 2.0 Subsystem Cost Breakdown Data...... 85 (55 Programs) B 3.0 Spacecraft Antenna Data ...... 89 (181 Antennas) * Net Antenna Gain Plot and Table of Efficiency...... 98 B 4.0 Microwave Filter Data...... 100 (348 Filter Designs) B 5.0 Power Amplifier Data...... 111 (672 Power Amplifiers) B 6.0 Public Record Satellite Anomaly Database...... 132 (1355 Anomalies, total value $15.07 billion) B 7.0 References To Sources And Related Materials...... 204 B 7.1 Sources For the Data - By Program...... 204 B 7.2 List Of References...... 208 B 8.0 Using the Database Files on A Computer...... 224 Structure of the Databases...... 225

Copyright © 2003 by TelAstra, Inc. Communications Satellite Databases Chapter B 1.0 INTRODUCTION The purpose of this database is to collect a comprehensive set of the pertinent programmatic and technical parameters concerning communications satellites. In most cases a breakdown of price and other technical data is provided. We fill in the confusing and sometimes misleading partial information that is published in the open literature. The intent is to provide purely factual data without making any judgments about programs or contractors. This information could be used to draw conclusions concerning to current market price of satellites, for example. This document will not attempt to project any future developments. The primary basis for the data is publications in the open literature. When published information has not been available, verbal information has been used to make a more complete database. In a few cases data has been estimated based on very direct comparisons to similar programs. The databases will be updated annually. The contents of this report are provided, based on the best available information. Engineering estimates have been made in some cases where explicit, verifiable data was not discovered. Furthermore, data incorporated into the database may reflect the reported parameter at a particular time in the course of a program. Many changes occur and no document of this type can be guaranteed to be 100% accurate in every detail. It is the best we could find or estimate. Better data to improve the accuracy or suggestions concerning the presentation style are solicited so that future editions can be upgraded. TelAstra, Inc. is a California corporation and not associated with Societe Europeene des Satellites SA, the operators of the ASTRA satellite system.

Copyright © 2003 by TelAstra, Inc. Communications Satellite Databases Chapter B 2.0 Subsystem Cost Breakdown Data Trans = Cost of the Communications Transponder. DATABASE EXPLANATION. The Cost Breakdown Database is Power = Cost of the Power Subsystem, including power control displayed in Table I. Each spacecraft program is identified in electronics, batteries, solar arrays and wire harness. alphabetical order. Zeros (0) usually indicates missing data or AOCS = Cost of the Attitude and Orbit Control Subsystem, data which is combined with some other parameter. Cost data is including attitude control electronics, sensors, SADA or BAPTA, not adjusted for inflation. Since the data is very compressed and and momentum wheels. there are many abbreviations, a little clarification is required. In TT&C = Cost of the Telemetry and Command Subsystem, both sequence the columns provide the following information: the digital, radio frequency and antenna elements. PROGRAM = PROGRAM NAME: INT means INTELSAT. In ST/TH = Cost of the Structure and Thermal Subsystems. some cases Arabic and Roman numerals have been exchanged, e.g. COMSTAR 1 is COMSTAR I. PROP = Cost of the Propulsion System, both reaction control and apogee boost. PRIME = CONTRACTOR: TEST = Cost for spacecraft final manufacturing, assembly and BOEG is Boeing final system level testing. EURO is Aerospatiale + MBB/ERNO or EUROSATELLITE. PMGT = The cost of this category includes the program office GEAS is General Electric Astro Space Division and may also include systems engineering and product GRUM is Grumman Aircraft assurance. MATR is MATRA. HAC is General Motors Hughes Electronics Sys Eng = Cost for Systems Engineering. MDAC is McDonnell Douglas R&QA= Cost for Product Assurance. RCA is Astro Division of General Electric Total $ = The total cost estimated or assessed by the manufacturer. ROCK is Rockwell International Fee = Profit or orbital performance payments made at or after YEAR = AWARD YEAR: Year of the contract start or expected delivery. start. Price = The total price paid by a customer to a manufacturer. #S = The number of satellites included in the cost estimate.

Antenna = Cost of the Antennas for the satellite.

Copyright © 2003 by TelAstra, Inc. Communications Satellite Databases Chapter B Table 2.1 SUBSYSTEM COST BREAK DOWN Program Contr Award # Anten Trans Power AOCS Teleco Struc. Propul Mfg Admin Syst. Prod Total Fee Total actor year sat nas pond mand therm sion test mgt Eng. assur. cost price ANIK A HAC 1970 3 2 8 2 2 3 6 2 4 6 35 35

Copyright © 2003 by TelAstra, Inc. Communications Satellite Databases Chapter B 3.0 ANTENNA DATA The PROGRAM and CONTRACTOR (Prime) data is defined in the same manner as for the other Databases. High: Freq = This is the high end of the frequency band in MegaHertz (MHz) for which the antenna is designed. Low: Freq = This the low end of the frequency band in MHz for which the antenna is designed. COVERAGE = This is a description of the territory covered by the specific antenna beam. WST means West. GLOBAL EAR means whole Earth coverage. 5.2 means a circular beam 5.2 degrees in diameter. REG or REGN means region. ALAS means Alaska. CONUS means the 48 contiguous states of the United States of America. CNTR or CTR means center. AREA_DEG2 = Cover. Area = This is the coverage area expressed in square degrees as observed from the satellite coordinate system. This parameter relates directly to antenna gain. Configuration = The antenna configuration is a brief description of the type of antenna employed. OFF SET:PAR is a parabolic reflector with an offset feed. HORN/REF is a horn antenna with an end reflector to bend, and sometimes to shape, the beam. CENTER:PAR is a parabolic, or other curved, reflector with a center feed. APERTUR_M2 = Aperture = This item is the aperture diameter or rectangular dimensions of the final radiating surface expressed in meters. NUMB_FEEDS = #Feeds = This is the number of feed horns used to form the primary beam. DIRECTIVIT = DIR = The isotropic gain or directivity of the antenna calculated at the aperture without losses in the feed horns or feed networks in dB. LOSSES = Loss = An estimate of the LOSSES internal to the antenna in dB. EOC_GAINDB = Net Gain = The net Gain of the antenna in dB, including internal losses, the result of the previous two entries. Polar Type= The propagated electromagnetic wave phasing. For linear polarization, V represents Vertical and H is Horizontal. For Circular Polarization, RHCP is Right Hand Circular Polarization and LHCP is Left Hand Circular Polarization. POL_ISO_DB = Polar Isol = The Polarization Isolation expressed in dB at the edge of the beam. Beam Isol = The Beam Isolation expressed in dB at the edge of the beam due to one beam illuminating the same area. ANT_MASS = Mass, Kg = The mass of the antennas in kilograms. In several cases the mass is the sum for a set of antennas of the same type which are fabricated together and radiate through the same aperture.

Copyright © 2003 by TelAstra, Inc. Communications Satellite Databases Chapter B TABLE 3.1 SATELLITE ANTENNA CHARACTERISTICS Program Contrac High Low Freq. Coverage Area Deg2 Configure Aperture M2 # Directi Loss EOCG Polar Type Pol Beam Ant tor Freq. Feeds vity es ain db Isol. Isol. Mass AFRISTAR DSI 1510 1470 AFRICA 11 OFFSET:PAR 3.5 3 32 2 31 44

Copyright © 2003 by TelAstra, Inc. Communications Satellite Databases Chapter B 4.0 MICROWAVE FILTER DATA The PROGRAM and CONTRACTOR (Prime) data is defined in the same manner as for the other Databases. High: Freq = This is the high end of the frequency band in MegaHertz (MHz) for which the filter is designed. Low: Freq = This the low end of the frequency band in MHz for which the filter is designed. BW = BANDWIDTH expressed in MHz for the specified filter passband. SPACING = SPA = Center to center SPACING between adjacent filters in MHz. FUNCTION = Location = This is the type of application or location for the filter. Input channel filters handle lower power levels and follow the receivers. Output filters are part of the multiplexers which follow the power amplifiers and combine the signals prior to transmission to the antennas. SHAPE = Analysis Model = The design characteristic or type of filter as expressed by the analytical methods used for the filter design. NUMB_POLES = #P = The number of POLES in each filter. Mode = The electromagnetic or waveguide propagating mode used in the filter cavities. Q = The resonant Q of the filter cavity. MIDBANDLOS = LOS = Midband loss in the filter expressed in dB. GAIN_VAR = VAR = Gain Variation across the channel bandwidth expressed in dB. GAIN_SLOPE = SLP = The GAIN SLOPE across the filter expressed in dB per MHz. GD = GROUP DELAY in nano seconds at the edge of the designated bandwidth. REJECTION = OOB = The OUT OF BAND response or attenuation at frequencies 150% from band center, expressed as dB down. For example, for a nominal 40 MHz bandwidth filter this is the attenuation 30 MHz from band center. Materials = The materials used for filter construction. NO_FILTERS = #F = The number of filters of this type used on each satellite of this design. MASS_EACH = Mass = The nominal mass of each filter expressed in grams. In several cases it is the average of a set of filters across a band.

Copyright © 2003 by TelAstra, Inc. Communications Satellite Databases Chapter B TABLE 4.1 CHARACTERISTICS OF SATELLITE MICROWAVE FILTERS Program Vendor High Low BW Spac Location Analysis Model #P Mode Q Loss VAR SLP GD OOB Materials #F Mass Freq. Freq. e Anik C HAC 12200 11700 54 61 Input dual mode 6 TE113 1100 0.6 1.0 0.1 21 30 Invar 16 0

Copyright © 2003 by TelAstra, Inc. Communications Satellite Databases Chapter B 5.0 POWER AMPLIFIER DATA TWT_EFFIC = TWT Eff = The basic efficiency of a TWT without the electronic power converter or power supply. In this section the same amplifier has been used for several programs in many cases. We have not duplicated all of the data AMP_EFFIC = AMP Eff = The net efficiency for a total power each time the same amplifier appears. We have referenced the amplifier including the power converter. original program which used the amplifier and have given the REDUNDANCY = Redun = The redundancy configuration for power level and model number where appropriate. the complement of power amplifiers. For example, 12/12 means CONTRACTOR = PRIME = The name of the prime contractor that there are 12 amplifiers occupying 12 transponder positions. for the program. In this case if an amplifier fails, a transponder or channel bandwidth cannot be used. 30/24 means that there a 6 reserved VENDOR = The name of the supplier for the power amplifier. amplifiers in case of amplifier failure. HAC EDD or HEDD is Hughes Aircraft Company, Electron Dynamics Division. AEG TELE is AEG Telefunken. SAT_GAIN = GAIN = This is the gain in dB when the amplifier is driven to saturation, rated or maximum power. Normally this is EPC_MFG = Integrator of the entire TWT amplifier and the called saturated gain. From this parameter it is possible to supplier of the electronic power converter. ATES = Alcatel, TTE calculate the power level required to drive the amplifier to = Thomson Tubes Electronics, SS/L = Space Systems Loral. saturation. AMP_TYPE = TYPE = The type of basic amplifier either a AMP_MASS = MASS = The mass of the total amplifier Traveling Wave Tube (TWT) or Solid State Power Amplifier (including power supply) expressed in grams. In some cases (SSPA). only the TWT mass is given with a +P or +PS to indicate that it CATHODE = Refers to the type of cathode used for a TWT. does not include the Power Supply. DISPENSR is a dispenser type. M-DISPEN and B-DISPEN refer CATH_LOAD = LOAD = For TWT this is the Cathode Loading to specific types of dispenser cathodes. Current Density expressed as milliamperes per square COLLECTORS = # = The number of collectors used at the centimeter. anode to recover the electron beam. If a M is shown this refers MODEL = The manufacturers model number. to a Multiple Stage Collector without stating the number of collectors. COMMENTS = Annotation which provides additional information about this particular amplifier. For linear amplifiers states the SAT_POWER = Power = The rated power, usually the nominal linear power rating and the NPR. References to maximum power (saturation), in Watts. amplifiers of identical design used on other programs. (not VOLTAGE = Volt = The maximum voltage for the TWT electron printed out in this listing) beam expressed in volts.

Copyright © 2003 by TelAstra, Inc. Communications Satellite Databases Chapter B TABLE 5.1: CHARACTERISTICS OF SATELLITE POWER AMPLIFIERS Program Contract Vendor Amp High Low Amp Cathode Collect Sat Volts TWT Amp Redund Sat Non Amp Cath Model or Mfg Freq Freq Type ors Power Effic Effic ancy Gain Linear Mass Load ANIK C HAC AEG HSC 12200 11700 TWT Dispens 3 15 2950 43 20/16 56 600+PS 42 TL1201 6

Copyright © 2003 by TelAstra, Inc. Communications Satellite Databases Chapter B 6.0 Public Record Satellite Anomaly Database adjust the transponder price to make the loss come out to the insurance claim value found in the literature. We don't always The Public Record Satellite Anomaly Data Base (PRSADB) was know anomaly cost - sorry. Also note that over the 35 years of started to enable estimation of lower bounds for how often space biz to date there has been considerable dollar inflation. actual geosynchronous satellites have various kinds of This is tracked in one of the other Engineering Consultants' anomalies, and what may influence them. The database now databases. has entries on over 1140 anomalies occuring to a subset of ~300 out of over 600 geosynchronous satellites. Incorporation of Chinese and USSR/CIS spacecraft is challenging. We think we have all the Gorizont, Gals, Ekran, The master data base is currently kept using Reflex 2. The other Express, Luch and Raduga launches. formats provided are translated from the Reflex 2 master. The .XLS file is Excel 3.0 made from the .TXT file. The .WK4 file Be aware that for USSR/CIS spacecraft there may be several is also made this way. In most analyses that the database naming and/or numbering schemes in the literature. So if unsure author does he either uses Reflex 2 or a spreadsheet with the check the launch dates. We use GMT. On launch dates, note .XLS file. that a morning launch in Baikonur may be the previous day in GMT and US time. Similarly for Kourou launches reported by Please note: US sources, it is not unusual for a US source to quote the date The " | " character is the end of field marker for the .TXT file. in their time zone. The .R2D, .DBF, .WK1, .WK4 & .XLS files are "zipped" to Similarly, incorporation of the military programs is still being compress them. Use the PKUNZIP -v function to see how big worked on. Only now, after the end of the cold war and nearly they will be when unzipped. the end of the program, are consistent details that make a little sense (like the satellite designations) coming out. However, it is Possible "ERROR" and "VALUE" indicators in fields come from unlikely that any significant number of anomalies on these Reflex 2's computed fields not computing when there was not programs other than launch failures are going to become public proper input value. We try to remove this after format conversion anytime soon. So it is recommended to please keep this but may have missed some; Sorry. "uneven reporting aspect" in mind in any analyses that use Also, please note that .WK1 and .DBF text field formats are military program data. truncated to 140 characters, wheareas the original .R2D Reflex EXPLANATION OF FIELDS 2.0 text fields are up to 255 characters wide. We are sorry to report this but have not yet found a way around this. This section explains PRSADB data fields using an example Recommended is to import the .WK4, .XLS or .TXT file directly record, reproduced below the way the database adminstrator into your chosen analysis database, spreadsheet or application. might see it in the Reflex 2 record view. Due to user requests we attempt to cost anomalies. For severe There are basically 4 kinds of PRSADB data fields: anomalies there is usually an insurance claim, and one can

Copyright © 2003 by TelAstra, Inc. Communications Satellite Databases Chapter B 1) Those describing the satellite Xe - Xenon Ion Propulsion 2) Those describing the anomaly BiXion - Bi but also with Xenon Ion Propulsion for 3) Those describing the references to the anomaly stationkeeping 4) Those describing anomaly effect (cost or mission lost) XIPS-25 - The Boeing 25-cm Xenon Ion Propulsion subsystem Fields Describing the Satellite: DLife: Contractor's design life, in years Spacecraft: Name of the satellite; We try to pick the most common name for a given spacecraft. Some satellites have LYear: Launch year been renamed, such as ASC-2, now called Spacenet 4. If LMon: Lauch month unsure, look at Name2 field and the launch date. LDay: Launch day Name2: If the satellite is known by another name, it may be LDate: The above data, in date format here SepMass: The separated mass from the launch vehicle (new for First: This field is a number 1 if this is the first entry for a given 2002) satellite (anomaly or not). If it is not the first entry the field is blank. This field was added so that one can count the number of Pwr: The beginning of life solar array power (meaning changed spacecraft in the database or subsets of it. for 2002; Before it was the power of the anomalous subsystem or unit.) Type: What kind of mission, given as a number from 1 - 12 Fields Describing the Anomaly: Typ: Text explanation of the above mission number Subsys: A number (1-13) for what subsystem caused the Rank: For satellites in a series, which one, in launch order. anomaly Total: How many in that series; Not all may be launched yet. Subsystem: Text, interpreting the above number Spin: 1 for body-spun spacecraft, 0 for body-stabilized Sev: A number (1-8) for how severe the anomaly was Bus: "Brand"/type of (non-payload) supporting platform Severity: Text, interpreting the above number Prop: What kind of propulsion- AYear: Year of anomaly NH3 - Ammonia AMon: Month of anomaly N2H4 - Hydrazine ADay: Day of anomaly Bi - Hydrazine and nitrogen tetroxide (N2O4) oxidizer ADate: Above, in date format Dual - Bi for the apogee burn(s), hydrazine otherwise

Copyright © 2003 by TelAstra, Inc. Communications Satellite Databases Chapter B MDay: Mission day of anomaly = ADate - LDate Ref[4]: "" "" Multi: Multiple occurrences? NRefs: How many references listed Yes if value is 2 or more Ref Date: Earliest reference cited, if not equal to ADate No, if 0 or 1; Plan is to use 1 for things that have AtoRDays: RefDate - ADate recurrences, but this is not completely implemented yet Eclipse: 1 if anomaly happened during eclipse, 0 if not

Comp: Text field about component - not used much in recent Fields describing impact of the anomalies years Add1: Additional number, giving frequency (GHz) if Comp = TWTA Xpdrs: Number of transponder channels on the spacecraft Add2: Text about payload complement or other useful info XPrice: Estimated annual transponder lease rate, in $M/yr. Special: Extra text field, mostly used to explain ADate, the AXpdrs: Number of transponders lost in the anomaly; For some launch vehicle and to give information about insurance kinds of anomalies, this was adjusted to give a representative claims. anomaly cost. See the discussion on values later. Anomaly Description: Text about what happened MFrac: Fraction of the spacecraft's design lifetime lost Cause: More text, about why due to the anomaly; This is computed by the formula Res: Number from 1-8 on resulting action after anomaly Result: Text explanation of above MFrac = (1 - DFrac) * AXpdrs / Xpdrs

ACost: Cost of the anomaly; This is not discounted nor is it Fields Describing the References: corrected for inflation. It is computed by the formula

Ref[1]: Text field for reference AFrac = (1 - DFrac) * DLife * AXpdrs * XPrice Ref[2]: "" ""

Ref[3]: "" ""

Copyright © 2003 by TelAstra, Inc. Communications Satellite Databases Chapter B DFrac: Design life fraction at MDay I-3 C-Band 3.0 I-4 C-Band 1.5 Representative values have been put into the fields. These I>4 C-Band & K-Band 1.0 are the author's best preliminary estimate. Although the author has reasonable communications spacecraft experience, An exception is made for Intelsat 6 C-band transponders, some of the values may be off. It is recommended that the quoted as costing .75/year. user check them where they are critical to his analysis. A final important exception is that when there is a launch failure

For AXpdrs in particular, where having an anomaly at past the and the spacecraft is quoted as being a certain value, the transponder design lifetime would yield a negative cost, AXpdrs was set price is adjusted to get the ACost to match the required value. to 0. Also, lack of eclipse coverage is usually considered as losing 5% of the transponders unless the operator filed a complete Check the Special field for additional information about launch vehicle and insurance. loss with the insurance. Where there is no entry, the value is 0.

Below is a typical REFLEX 2.0 page showing the fields in a form Default assumed transponder prices, in $M/year view.

Domestic US C-Band 1.0 Domestic US Low-Power Ku-Band 1.5 Spacecraft: Oursat Type: 2Typ: Civil Res/ApRank: 2 Total: 3 Medium power Ku-band (US & Japan) 2.0 Name 2 :Yoursat High power Ku-band (Europe) 8.0 LDate: 1-Apr-95Spin: 0Bus: Big DLife: 10.0 Prop: Bi

Arabsat C-Band .5 First: 1 Xpdrs: 24 XPrice: 1 AXpdrs: 1 I-2 C-Band 5.0

Copyright © 2003 by TelAstra, Inc. Communications Satellite Databases Chapter B Subsys: 4 Subsystem: Comm PL Sev: 6 Severity: Subsystem Ref[2]: SatTube Reference Journal, V. 2, Feb. 1998, pp. 4-8. lost

Ref[3]: AYear: 1996 AMon: 6 ADay: 23 ADate: 23-Jun-96 MFrac: 0.037

Ref[4]: LYear: 1995 LMon: 4 LDay:1MDay: 449 DFrac: 0.123 SepMass: 3005 ACost: 8.8

Multi: 0 Eclipse:0 Comp: TWT Pwr: 5000 The PR2002 version of the data base has information on 1146 Add1: 11 Add2: 30/24 50W Ku TWTA's anomalies (as counted by a severity vs subsystem crosstab) but has 1534 Special: ADate from [1] records because not all satellites have reported anomalies.

Anomally Description: [1] "bad tube"; [2] failed; Redundancy not available ------The Public Record Satellite Anomaly Database (PRSADB) was Cause: [2] "collector developed short" started to enable an estimation of the lower bounds for how often actual geosynchronous communications satellites have various kinds of anomalies, and what may influence them. Res: 2 Result: Investigation Please note that many anomalies are suppressed either by the satellite owner / operating company, the manufacturer, or both. Competitive pressures are one consideration. Operating NRefs: 2 RefDate: 8/13/96 AtoR_Days: 51 companies are worried that knowledge of failures and anomalies may discourage customers from using their satellite communications networks. Civil governmental customers may Ref[1]: Scavenging Weekly Newsleter, 8/13/96, p. 2 be concerned about public relations and military customers may be concerned about revealing vulnerability on classified or security related matters. Consequently, the best information

Copyright © 2003 by TelAstra, Inc. Communications Satellite Databases Chapter B comes from commercial international programs. Until recently, AYEAR: Year of anomaly some of these programs have not faced competitive pressures. SUBSYS: A number (1-12) for which subsystem caused the Furthermore, the public release of anomaly data may be used anomaly. Also identified by name in the SUBSYSTEM field. as pressure to ensure that the manufacturer takes corrective actions. 1 = Launch Vehicle Also, please note that .DBF text field formats are truncated to 2 = AKM (Apogee Kick Motor) 140 characters, wheareas the origninal text fields may be up to 3 = TCR (Telemetry Command and Ranging) 256 characters wide. We are sorry to report this but have not yet found a way around this. 4 = Comm PL (Communications Payload) Explanation Of Fields 5 = Mechanisms Only five of the 40 fields in this database are printed in the 6 = ACS (Attitude Control Subsystem) following table. There are basically four kinds of PRSADB data 7 = EPS (Electrical Power Subsystem) fields included in the following list: 8 = RCS (Reaction Control Subsystem, e.g. Thrusters, Valves) 1) Those describing the satellite 9 = Thermal 2) Those describing the anomaly 10 = Perigee Kick Motor 3) References to the anomaly 11 = Op error (Operator Error) 4) Those describing anomaly effect (cost or mission lost) 12 = Other SPACECRAFT: Name of the satellite; We try to pick the most ANOMALY_D (Anomaly Description): Brief text about event. common name for a given spacecraft. Some satellites have been renamed, such as ASC-2 is now called Spacenet 4. Look REF_1_: Text field for reference at the launch date if you are not sure. Alternative names are SEV: A number (1-8) which indicates severity of the anomaly. provided in COMMUNICATIONS SATELLITE DATABASES, Also described in the SEVERITY field. Part III. 1 = Unexpected but no impact First: This field is a number 1 if this is the first entry for a given satellite (anomaly or not). If it is not the first entry the field is 2 = Operations Delay blank. This field was added so that one can count the number of 3 = Work Around spacecraft in the database or subsets of it. 4 = Go to Redundant Subsystem LYEAR: Launch year 5 = Subsystem temporarily Disabled

Copyright © 2003 by TelAstra, Inc. Communications Satellite Databases Chapter B 6 = Subsystem Permanently disabled CAUSE: Additional text about cause 7 = Spacecraft Temporarily disabled REF_DATE: Earliest reference cited, if not equal to ADATE 8 = Spacecraft Permanently disabled ATOR_DAYS: REFDATE - ADATE AMON: Month of anomaly RES: Number from 1-8 on resulting action after anomaly. Also ADAY: Day of anomaly see RESULT. ECLIPSE: 1 if anomaly happened during eclipse, 0 if not 1 = None LMON: Launch month 2 = Investigation LDAY: Launch day 3 = Next generation change without delay MDAY: Mission day of anomaly = ADATE - LDATE 4 = Next Satellite change without delay LDATE: The LYEAR LMON LDAY data, in date format 5 = Next satellite change with delay ADATE: AYEAR AMON ADAY, in date format 6 = Reallocation of orbital resources SPECIAL: Extra text field, mostly used to explain ADATE and to 7 = Next Generation change with delay give information about insurance claims. 8 = In Orbit Fix NREFS: How many references listed RESULT: Text explanation of RES SUBSYSTEM: Text, interpreting the SUBSYS number. TYPE: What kind of mission, given as a number from 1 -15. Also SEVERITY: Text, interpreting the SEV number. Reported as see TYP. ERROR in the case of operator error or unknown impact. 1 = Civil Research RANK: Ordinal number for satellites in a series, which one, in 2 = Civil Research / Applications launch sequence. 3 = Civil Applications TOTAL: How many in that series; Not all may be launched yet. 4 = Unused REF_2_: Text field for reference 5 = Unused REF_3_: Text field for reference 6 = Civil / Military Applications MULTI: Multiple occurrences? Yes, if value is 2 or more, No, if 0 7 = Military Research or 1; The Plan is to use 1 for things that have recurrences. This notation is not completely implemented yet. 8 = Unused

Copyright © 2003 by TelAstra, Inc. Communications Satellite Databases Chapter B 9 = Military Applications XPrice: Estimated annual transponder lease rate, in $M/yr. 10= Civil Weather AXpdrs: Number of transponders lost in the anomaly; For some 11= Civil/Military Weather kinds of anomalies, this was adjusted to give a representative anomaly cost. See the discussion on values later. 12= Unused MFrac: Fraction of the spacecraft's design lifetime lost due to 13= Civil Science the anomaly; This is computed by the formula 14= Unused MFrac = (1 - DFrac) * AXpdrs / Xpdrs 15= Military Observation ACost: Cost of the anomaly; This is not discounted nor is it TYP: Text explanation of the above TYPE mission number corrected for inflation. It is computed by the formula: COMP: Component. Text field about component AFrac = (1 - DFrac) * DLife * AXpdrs * XPrice PWR: Power. Number, giving TWT RF power if Comp = TWTA DFrac: Design life fraction at MDay ADD1: Additional number, giving frequency (GHz) if Comp = Assumed Transponder Prices $M/Year TWTA Domestic US C-Band 1 Domestic US Ku-Band Low-Power 1.5 ADD2: Text about payload complement or other useful info US & Japan Ku-band Medium power 2 DLIFE: Design Life. Contractor's stated design life, in years Europe Ku-band High power 8 DFRAC: Design life fraction, MDAY / DLIFE Arabsat C-Band 0.5 INTELSAT-2 C-Band 5 SPIN: 1 for body-spun spacecraft, 0 for body-stabilized INTELSAT-3 C-Band 3 BUS: Brand / Designation of (non-payload) supporting platform INTELSAT-4 C-Band 1.5 INTELSAT-5 & 6* C-Band & K-Band 1 PROP: Identifies propellants or fuel and oxidizer NH3 - Ammonia Representative values have been put into the fields. These are the author's best preliminary estimate. Although the author has N2H4 - Hydrazine reasonable communications spacecraft experience, some of the Bi - Hydrazine and nitrogen tetroxide (N2O4) oxidizer values may be off. It is recommended that the user check them where they are critical to his analysis. Dual - Bi for the apogee burn(s), anhydrous Hydrazine. For AXpdrs in particular, where having an anomaly at past the Fields pertaining to the cost of anomalies. design lifetime would yield a negative cost, AXpdrs was set to 0. Xpdrs: Number of transponder channels on the spacecraft

Copyright © 2003 by TelAstra, Inc. Communications Satellite Databases Chapter B Also, lack of eclipse coverage is usually considered as losing A final important exception is that when there is a launch failure 5% of the transponders. Where there is no entry, the value is 0. and the spacecraft is quoted as being a certain value, the transponder price is adjusted to get the ACost to match the required value.

Public Record Satellite Anomaly Database SPACECRAFT ADATE ANOMALY DESCRIPTION SEVERITY COS CAUSE T Telecom 1B 15-Jan-88 [1] "failure of ...normal and backup attitude control Satellite Permanently 207 [2] "Bus regulation electronics" [3] "power systems." Disabled surge cut electrical supply to the attitude control system"