NASA Investigation Board Report On The INITIAL FLIGHT ANOMALIES OF SKYLAB 1

CHAPTER VIII : POSSIBLE IMPACT OF COSTS AND SCHEDULES ON THE METEOROID SHIELD

The origin of Skylab in late 1966 -- as an extension of the use of Apollo hardware for experiments in earth orbit imposed an initial environment of limited funding and strong schedule pressures on the program. Skylab, then designated the Apollo Applications Program (AAP), was to "fit in" among the Apollo flights under schedules imposed by the main-line Apollo program. Funding was provided out of the Apollo program and thus the needs of Skylab competed with those of the higher priority Apollo program.

The situation changed in mid 1969 when Skylab became a major line item in its own right and was to use a Saturn-V launch vehicle with a dedicated, dry, OWS. From that point on, increased funding and new flight schedules were established for Skylab. Nonetheless, the original concept of the meteoroid shield was retained when the OWS changed from a Saturn-IB propulsion stage to a dry workshop launched by a Saturn-V. The Board was therefore interested in determining the extent, if any, that either the initial limitation of funds and time, or any subsequent limitations, determined the design or thoroughness of development of the meteoroid shield. This inquiry was limited to the possible effect of funding and schedule of the meteoroid shield as designed and flown on Skylab 1 and did not consider whether meteoroid protection could have or should have been provided in some other way had the program not evolved as it did.

In the Board's review of the evolution of the meteoroid shield from initial design concept. through testing and development. to final assembly for flight, particular attention was devoted to any impacts arising from limitation of funds or time. Extensive discussions were also held with management personnel of MDAC-W, MSFC, JSC and NASA Headquarters on this matter. In no instance could the Board find any evidence that the design or testing of the meteoroid shield was compromised by lack of funds or time. Program personnel, both government and contractor, had full confidence in the basic concept of the MS and thus saw no need to alter the design when the change to a dry, Saturn-V launched OWS occurred. Given the concept that the shield was to be maintained tight to the OWS tank, and thus structurally integrated with the well-established S-IVB structure. the emphasis of testing given to ordnance reliability and shield deployment was considered proper. Neither the records of Skylab nor the memories of key personnel revealed any tests or analyses of the meteoroid shield that were considered desirable at the time and which were precluded by lack of funds or time.


link to the previous pagelink to the index pagelink to the next page