Search NASASearch

Engineering topics

Kirkpatrick, Paul D.

Publications and source records attributed to Kirkpatrick, Paul D..

The NASA Commercial Crew Program (CCP) Shared Assurance Model for Safety

NASA established the Commercial Crew Program in order to provide human access to the International Space Station and low earth orbit via the commercial (nongovernmental) sector. A particular challenge to NASA is how to determine the commercial provider's transportation system complies with Programmatic safety requirements while at the same time allowing the provider the flexibility to demonstrate compliance. This will be accomplished through the use of Shared Assurance and Risk Based Assessment by NASA thus shifting more responsibility to the Provider. This model will be the focus of this presentation.

Programmatic safety requirements

Proposal for Ground Safety Review Coordination at ISS Launch Sites

As the transportation of ISS payloads and cargo shifts from KSC to other launch sites, close coordination of ground safety review processes would be of benefit to all parties. The benefit would have the launch sites receiving consistent data that would require less effort to review while still meeting their needs. Until recently, ground safety focus for the ISS program has been almost exclusively for prelaunch processing at KSC/post-landing processing at KSC/DFRC Each launch site, used by the ISS Program, has a ground safety review process. Ground safety viewed as local prerogative. Up till now, ground processing has consisted of low risk/low hazard items; but this will not always be the case. Recent coordination issues associated with the ground safety review of ORU's to be processed at Tanegashima for HTV-2, illustrate that IP ground safety review processes are not well understood by the ISS community at large. Confusion for data providers (US only?). Lack of internal review process for data being submitted to launch sites can lead to inconsistent submittals. NCRs/HRs. Majority of IP ground safety requirements are based upon old KHB 1700.7 (now KNPR 8715.3, Chapter 20). Proposals include: Establish a ground safety working group as part of the MS&MAP. Search for efficiencies in requirements and data submittal processes. Document processes in NSTS 13830/SSP 30599. Each launch site report out its payload ground safety status at the F2F (Monthly's as required). Completions/due dates/NCRs/issues/changes. Establish internal processes for review of ground safety submittals.

Kirkpatrick, Paul D.

The Development and Implementation of Ground Safety Requirements for Project Orion Abort Flight Testing - A Case Study

A rigorous set of detailed ground safety requirements is required to make sure that ground support equipment (GSE) and associated planned ground operations are conducted safely. Detailed ground safety requirements supplement the GSE requirements already called out in NASA-STD-5005. This paper will describe the initial genesis of these ground safety requirements, the establishment and approval process and finally the implementation process for Project Orion. The future of the requirements will also be described. Problems and issues encountered and overcame will be discussed.

Kirkpatrick, Paul D.

Ground Safety Issues

In the history of humankind, every space adventure, great or small, has begun on the ground. While this seems to be stating the obvious, mission and flight hardware designers who have overlooked this fact have paid a high price, either in loss or damage to the hardware pre-launch, or in mission failure or reduction. Designers may risk not only their flight hardware, but they may also risk their lives, their co-workers lives and even the general public by not heeding safety on the ground. Their eyes may be on the stars but their feet are on the ground! This discussion applies to all forms of flight hardware from the largest rockets to the smallest spare parts.

Kirkpatrick, Paul D.

Safety Considerations in the Ground Environment

In the history of humankind, every great space adventure has begun on the ground. While this seems to be stating the obvious, mission and spacecraft designers who have overlooked this fact have paid a high price, either in loss or damage to the spacecraft pre-launch, or in mission failure or reduction. Spacecraft personnel may risk not only their flight hardware, but they may also risk their lives, their co-workers lives and even the general public by not heeding safety on the ground. Their eyes may be on the stars but their feet are on the ground! One additional comment: Although the design requirements are very different for human rated and nonhuman rated flight hardware, while on the ground that flight hardware (and its ground support equipment) doesn't care about what it is flying on. On the ground, additional requirements are often levied to protect the work force and general public. (Authors' Note: The source material for this chapter is primarily taken from the Kennedy Space Center Handbook (KHB) 1700.7/45 SW Handbook S-100 Space Shuttle Payload Ground Safety Handbook and the authors' personal experiences.

Kirkpatrick, Paul D.

A Common Approach for the Certifying of International Space Station (ISS) Basic Hardware for Ground Safety

In order to support the International Space Station, as well as any future long term human missions, vast amounts of logistical-type hardware is required to be processed through the various launch sites. This category consists of such hardware as spare parts, replacement items, and upgraded hardware. The category also includes samples for experiments and consumables. One attribute that all these items have is they are generally non-hazardous, at least to ground personnel. Even though the items are non-hazardous, launch site ground safety has a responsibility for the protection of personnel, the flight hardware, and launch site resources. In order to fulfill this responsibility, the safety organization must have knowledge of the hardware and its operations. Conversely, the hardware providers are entitled to a process that is commensurate with the hazard. Additionally, a common system should be in place that is flexible enough to account for the requirements at all launch sites, so that, the hardware provider need only complete one process for ground safety regardless of the launch site.

Kirkpatrick, Paul D.