GSFC 5 Space Technology “Tomorrow’s Technology Today” ST5 PDR June 19-20, 2001 Launch Vehicle Services Section 18.0 Clyde Woodall Launch Vehicle Manager

ST5 PDR June 19-20, 2001 GSFC 18-2 Launch Services Agenda Launch Requirements Launch Vehicle (LV) Status LV Study Results Risk Mitigation

ST5 PDR June 19-20, 2001 GSFC 18-3 Launch Requirements (1 of 2) S/C and DS compatible with SPL accommodations on EELVs (MRD ) –S/C and DS design is based on information obtained from Boeing &LM for secondary payload accommodations on the EELVs Access to each S/C on Launch Pad for battery top-off and aliveness test (MRD ) –ST5 evaluating a couple of approaches based on information obtained from Boeing & LM for secondary payload accommodations on the EELVs

ST5 PDR June 19-20, 2001 GSFC 18-4 Launch Requirements (2 of 2) Orbit to expose S/C to radiation environment for instrument validation (MRD ) –ST5 will select a PPL mission that provides a GTO orbit (approx. 200 km X 35,786, 15 to 28º inclination) Orbit to expose S/C to low level magnetic background for science validation (MRD ) –ST5 will select a PPL mission that will provide a GTO orbit

ST5 PDR June 19-20, 2001 GSFC 18-5 LV Status (1 of 2) LV Assignment not obtained Task Order Studies Completed with Boeing & LM –Identified accommodation for generic secondary payloads but used ST5 requirements as the general guideline –Provided SPL interfaces, loads, environments, etc. for EELV flights –Provided estimated costs to fly on EELVs as a secondary payload –Identified potential PPLs (looked at DoD & Commercial launches) –Initial study concluded in April 2001, task order mechanism remains in place to continue discussions with Boeing & LM as required

ST5 PDR June 19-20, 2001 GSFC 18-6 LV Status (2 of 2) Continued to Evaluate Other Ride Opportunities –Contact with the UHF program office and LM Atlas III team Document Status –Generated an LV IRD (draft) for each launch vehicle

ST5 PDR June 19-20, 2001 GSFC 18-7 LV Study Results (1 of 6) SPL Volume Identified ST5 configurations will fit in the available SPL volumes for both the Atlas V and Delta IV configurations Atlas V:Delta IV: Proprietary Information

ST5 PDR June 19-20, 2001 GSFC 18-8 LV Study Results (2 of 6) Mechanical Interfaces –Atlas V configuration will use a C22 adapter with an Auxiliary Adapter Structure (AAS) to interface with the DS/ST5 S/Cs AAS being developed by Space Operations International (SOI) –Delta IV configuration will use the PAF with a Secondary Payload Structure (SPS) to interface with the DS/ST5 S/Cs Boeing looking at the SOI study design for the SPS Proprietary Information

ST5 PDR June 19-20, 2001 GSFC 18-9 LV Study Results (3 of 6) Launch Environment –Boeing & LM provided the environmental loads expected for the EELVs Addressed in the Mechanical/Thermal Presentation Electrical Interfaces –EELVs will provide ordnance signals to deploy ST5 S/C –Atlas V: Provides limited but adequate T-0 wired services for ST5 Requires a separation indicator from ST5 S/C to LV –Delta IV Will provide T-0 services for ST5 S/C as a unique service Does Not require a separation indicator from ST5 S/C to LV

ST5 PDR June 19-20, 2001 GSFC LV Study Results (4 of 6) Mission Design –Provided standard launch ascent profiles for the EELVs –PPL to be deployed first Approximately minutes after launch typically for a GTO mission –LV CCAM and repositioning for ST5 after PPL released –ST5 released sequentially (~1 min. apart) without LV rotating to same deployment position –LV CCAM and repositioning for disposition after ST5 released

ST5 PDR June 19-20, 2001 GSFC LV Study Results (5 of 6) Launch Site Processing –Boeing & LM presented typical launch site processing flows envisioned for EELV processing (payload arrival to launch) Denoted where they felt the SPL would fit into the flow of PPL and LV processing which included the following –Mechanical mating –Electrical checkout (Ordnance Umbilical and T-0 umbilical) –“On-Pad” Testing: Aliveness Tests and Battery Top-off –S/C access (Atlas V thru boattail; Delta IV thru 9” access doors) Emphasized that processing was to be done on non-interference basis –ST5 can proceed with launch site planning with this information A detailed timeline will be generated once a PPL rideshare assignment has been made

ST5 PDR June 19-20, 2001 GSFC LV Study Results (6 of 6) Rideshare Candidates –Atlas III/V DoD Missions: SBIRS (GEO), UHF Commercial: None identified to date –Delta IV DoD Missions: WBGF Commercial: Customers being signed but none identified to date LV Study Summary –No Showstoppers have been identified by Boeing or LM that precludes ST5 from being able to fly on an EELV as a secondary payload –Tall Pole: Get permission/assignment to ride with manifested primary payload going to GTO

ST5 PDR June 19-20, 2001 GSFC Risk Mitigation Risk: Getting a Launch Vehicle Assignment Mitigation: –Meet with the AirForce SPO to get acceptance/approval to fly ST5 as a secondary payload on an EELV ST5, KSC, Lockheed Martin, and Boeing Participation Present summary of the LV Study Results Convince SPO that launching ST5 does not compromise the PPL or LV –Continue to work with HQ/K. Poniatowski on getting a signed MOU/MOA in place with the AF/DoD –Continue to work with KSC/Boeing/Lockheed Martin on SPL interfaces and issues

ST5 PDR June 19-20, 2001 GSFC Back Up Charts-Boeing RFAs Delta IV –Additional LV figures –GTO ascent profile –Deployment Scenario –Launch Site Processing Flow

ST5 PDR June 19-20, 2001 GSFC RFAs (Summarized Version) 041: Consider Access Doors on LV –ANS: Depending upon LV, access to ST5 S/C via access doors or thru boat tail. 043: Consider contracting directly with LV contractor once PPL is selected –ANS: ST5 not sure of the latitude we will have to do this. ST5 is the pathfinder mission for a flight on an EELV as a SPL 054A: ID parameters to be checked at the Launch Pad (LP) –ANS: AT-0 interface and parameter listing is in works as the plan is to conduct aliveness test and battery top-off on each S/C prior to launch

ST5 PDR June 19-20, 2001 GSFC RFAs (Summarized Version) 054B: Plan to mate to LV –ANS: Depending upon LV, plan is to mount to adapter which will then be mounted on the PAF or LV Adapter which will then have the PPL mounted to (TBR). The combined payloads will then be tested and encapsulated. 054C: Monitoring of ST5 when on LP –ANS: An aliveness test via a T-0 interface is planned

ST5 PDR June 19-20, 2001 GSFC Delta IV LV Proprietary Information

ST5 PDR June 19-20, 2001 GSFC Delta IV SPL Envelope on PAF Proprietary Information

ST5 PDR June 19-20, 2001 GSFC SPS Interface Plate Proprietary Information

ST5 PDR June 19-20, 2001 GSFC Delta IV Ascend Profile

ST5 PDR June 19-20, 2001 GSFC Delta IV Deployment Scenario ST-5 S/C separation will occur between the end of primary payload CCAM and the initiation of LO 2 depletion blowdown and hydrazine depletion Typical sequence of events –Separate primary payload –Perform primary payload Contamination and Collision Avoidance Maneuver (CCAM) Align to ST5 separation attitude Separate ST5 S/C at one minute intervals Perform ST5 CCAM –LO 2 depletion blowdown –Hydrazine depletion

ST5 PDR June 19-20, 2001 GSFC Delta IV LS Processing Flow Proprietary Information

ST5 PDR June 19-20, 2001 GSFC Delta IV LS Processing Flow Proprietary Information

ST5 PDR June 19-20, 2001 GSFC Delta IV PAF & SPS ST-5 Satellite