AS-102
Launch of AS-102
Mission typeSpacecraft aerodynamics
OperatorNASA
COSPAR ID1964-057A
SATCAT no.883
Mission duration~7 hours, 30 minutes
Orbits completed59
Spacecraft properties
SpacecraftApollo BP-15
Launch mass16,700 kilograms (36,800 lb)
Start of mission
Launch dateSeptember 18, 1964, 16:22:43 (1964-09-18UTC16:22:43Z) UTC
RocketSaturn I SA-7
Launch siteCape Kennedy LC-37B
End of mission
DisposalUncontrolled reentry
Last contactSeptember 18, 1964 (1964-09-19Z) UTC
Decay dateSeptember 22, 1964 (1964-09-23Z) UTC
Orbital parameters
Reference systemGeocentric
RegimeLow Earth orbit
Perigee altitude177 kilometers (96 nmi)
Apogee altitude206 kilometers (111 nmi)
Inclination31.7 degrees
Period88.32 minutes
EpochSeptember 20, 1964[1]
 

AS-102 (also designated SA-7) was the seventh flight of the Saturn I launch vehicle, which carried the boilerplate Apollo spacecraft BP-15 into low Earth orbit.[2] The test took place on September 18, 1964, lasting for five orbits (about seven and a half hours). The spacecraft and its upper stage completed 59 orbits before reentering the atmosphere and crashing in the Indian Ocean on September 22, 1964.

Objectives

AS-102 was designed to repeat the flight of AS-101. It would once again carry a boilerplate Apollo command and service module. The only difference from Boilerplate 13 carried on AS-101 was that on Boilerplate 15, one of the simulated reaction control system thruster quads (attitude control thrusters) was instrumented to record launch temperatures and vibrations.[3]: 103  Another major difference on AS-102 was that the launch escape system (LES) tower would be jettisoned using the launch escape and pitch control motors.[3]: 3 

AS-102 was the first time a Saturn rocket carried the ST-124 programmable guidance computer. Previous launches had used an onboard "black box" that was preprogrammed.[3]: 2  On AS-102 it would be possible to reprogram the computer during flight so that any anomalous behavior could potentially be corrected.

Apollo Command Module boiler plate #15 checked out prior to SA-7 launch on September 18, 1964

Flight

In early July, a small crack in engine number six was found. This meant removing the engine, the first time that the ground crew had to do this with a Saturn rocket. It was then decided to return all eight engines to the manufacturer, which meant a job that would take about ten hours because of the large number of tubes, hoses and wires that connected each engine to the rocket. The replacement delayed the launch by about two weeks, followed by another delay of several days because of Hurricanes Cleo and Dora.[3]: 6 

Launch was on 18 September from Cape Kennedy, Florida just before noon local time. The first stage burned for 147.7 seconds, with separation 0.8 seconds later. The second stage ignited 1.7 seconds later, and the LES jettisoned at 160.2 seconds after launch. It burned until +621.1 seconds with the stage and boilerplate in a 212.66 by 226.50 km orbit.

The flight met all its objectives. The spacecraft continued to transmit telemetry for five orbits and was tracked until re-entry on its 59th orbit over the Indian Ocean.[3]: 103 

The only anomalous event on the flight was the failure to recover the eight film-camera pods. They had landed downrange of the expected area, where Hurricane Gladys ruled out a continued search. However, two of the pods did wash ashore two months later. The pods were covered with barnacles, but the film inside was undamaged.[3]: 3 

References

Public Domain This article incorporates public domain material from websites or documents of the National Aeronautics and Space Administration.

  1. ↑ McDowell, Jonathan. "Satellite Catalog". Jonathan's Space Page. Retrieved October 31, 2013.
  2. ↑ NSSDC: SA-7
  3. 1 2 3 4 5 6 Results of The Seventh Saturn I Launch Vehicle Test Flight SA-7 (Report). NASA. December 30, 1964. Retrieved May 7, 2023.
Wikimedia Commons has media related to Saturn-Apollo 7.

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.