| NODIS Library | Program Management(8000s) | Search |

NASA Ball NASA
Procedural
Requirements
NPR 8715.24
Effective Date: September 24, 2021
Expiration Date: September 24, 2026
COMPLIANCE IS MANDATORY FOR NASA EMPLOYEES
Printable Format (PDF)

Subject: Planetary Protection Provisions for Robotic Extraterrestrial Missions

Responsible Office: Office of Safety and Mission Assurance


| TOC | Preface | Chapter1 | Chapter2 | Chapter3 | AppendixA | AppendixB | AppendixC | AppendixD | ALL |

Chapter 3. Planetary Protection Procedural Requirements

3.1 Categorization and Planning

3.1.1 Planetary Protection Categorization for Missions (see Appendix C for further details and example target bodies)

3.1.1.1 The NASA Project Manager, in coordination with the Project-Level SMA TA, shall consult with the PPO regarding planetary protection mission categorization for the primary spacecraft as early as proposal development or architecture formulation but no later than Mission Concept Review (MCR) for assigned missions, and during Pre-Phase A for competed missions.

3.1.1.2 The NASA Project Manager, in coordination with the Project-Level SMA TA, shall consult with the PPO regarding planetary protection mission categorization for confirmed and selectable secondary payloads as early in the formulation process as possible.

Note: Late notification of complex secondary payloads or deployment of multiple SmallSats or CubeSats can add risk for successful outcomes and impact gate reviews of the primary mission.

3.1.1.3 The NASA Project Manager, with concurrence from the PPO, shall obtain preliminary planetary protection mission categorization from the MDAA as early as practical during mission concept development but no later than Mission Concept Review (MCR) for assigned missions, and during pre-Phase A for competed missions.

Note: In response to the planetary protection mission categorization request, the PPO may provide considerations to the project for tailoring of the PP Requirements Document and formulation of the PP Implementation Plan.

3.1.1.4 The NASA Project Manager, with concurrence from the authority defined in Table 3 1, shall obtain final planetary protection mission categorization from the MDAA as early as practical but no later than System Requirements Review (SRR). The final planetary protection mission categorization is documented in the Assurance Implementation Matrix required per NPR 8705.4 or, otherwise, appended to the (Preliminary) Project Plan required by NPR 7120.5.

3.1.1.5 Required elements to support the mission's planetary protection categorization assignment include:

a. Proposed planetary protection mission category.

b. A mission description that identifies:

(1) The target solar system body(ies) and location on the solar system body.

(2) Any other solar system bodies that would be encountered under the proposed spacecraft trajectory.

(3) In-space destinations within the Sun-Earth-Moon family of orbits (e.g., Lagrange points and halo orbits).

c. An overview of the proposed spacecraft hardware and concept of operations.

d. For sample return missions, rationale for proposing restricted or unrestricted sample return.

Note: Missions returning samples to the Earth-Moon system are assigned a categorization for the return phase in addition to the outbound planetary protection mission category.

e. Anticipated secondary payloads with independent propulsive capability.

f. An EOM scenario.

3.1.1.6 If there are any modifications to the required elements of the planetary protection mission categorization request (e.g., mission design or trajectory) after the final planetary protection mission categorization has been obtained, the NASA Project Manager shall reobtain final planetary protection mission categorization from the MDAA with concurrence from the authority defined in Table 3 1.

Table 3 1. Planetary Protection Documentation Authorities

Planetary Protection Documentation1 Planetary Protection Mission Category2
Outbound Inbound
I II III IV V(r) V(u)
Final PP Mission Categorization Concurrence from PPO Concurrence from Chief, SMA based on recommendations from PPO
PP Requirements Document None required Concurrence from PPO Concurrence from Chief, SMA based on recommendations from PPO Refer to outbound planetary protection mission category for concurrence authority
PP Implementation Plan Concurrence from PPO
Pre-Launch PP Report Concurrence from Chief, SMA based on recommendations from PPO
Post-Launch PP Report
Extended Mission PP Report
End of Mission PP Report
1 Some missions may be able to demonstrate compliance with planetary protection requirements with a reduced document set.
2 See Appendix C for further details and example target bodies on Planetary Protection Mission Category definition.

Table 3 2. Planetary Protection Document Schedule

Planetary Protection Documentation Nominal Document Schedule1, 2, 3, 4
MCR SRR MDR PDR CDR SMSR PLAR EOM
PP Mission Categorization5 Preliminary Final
PP Requirements6 Preliminary Baseline
PP Implementation Plan Preliminary Baseline Update
Pre-Launch PP Report Final Report
Post-Launch PP Report Final Report
Extended Mission PP Report Prior to extended mission approval
End of Mission PP Report Final Report
1 Lifecycle based on NPR 7120.5, NASA Space Flight Program and Project Management Requirements (see NPR 7120.5 for additional information).
2 The actual schedule for delivery of these documents is negotiable and is established in the PP Requirements Document.
3 In the case of a significant system or mission change, updates need to be provided in categorization and planning documents at the discretion of the OPP.
4 For restricted sample return missions, see also Section 3.4.4.
5 Alternate document schedules for this deliverable are provided in Section 3.1.1.3.
6 This deliverable schedule is driven by the requirements schedule defined in the NASA Systems Engineering Handbook.

3.1.2 Planetary Protection Requirements Document

3.1.2.1 The NASA Project Manager, with concurrence from the authority defined in Table 3 1, shall establish and document project-level planetary protection requirements consistent with the planetary protection mission categorization covering the project (spacecraft and launch vehicle) life-cycle, including the agreed upon set of accepted standards to achieve compliance, in the Planetary Protection Requirements Document by the schedule provided in Table 3 2.

Note 1: The PP Requirements Document includes an established schedule for the documents required in this directive. Table 3-2 provides a nominal schedule for reviews and documents, but the OPP works with each mission on time needed for reviewing documents prior to concurrence at the life-cycle reviews.

Note 2: Known non-compliances should be addressed by appropriate mitigations that are documented and agreed with the OPP well ahead of the review of the PP Requirements Document.

3.1.2.2 The PP Requirements Document should contain elements that are included in the agreed upon set of accepted standards.

3.1.2.3 The NASA Project Manager shall report planned and actual departures from the baseline PP Requirements Document to the Mission Directorate and the OSMA at Life-Cycle Reviews (LCRs) with any unresolved issues being raised at Key Decision Points (KDPs) throughout the project life-cycle.

3.1.3 Planetary Protection Implementation Plan

3.1.3.1 The NASA Project Manager, with concurrence from the authority defined in Table 3 1, shall specify planetary protection implementation activities in the PP Implementation Plan covering the project life-cycle (spacecraft and launch vehicle) that comply with project-level planetary protection requirements by the negotiated schedule in the PP Requirements Document (nominal schedule of reviews at which the project is expected to report is provided in Table 3 2).

3.1.3.2 The PP Implementation Plan should contain elements that are included in the agreed upon set of accepted standards.

3.1.3.3 The NASA Project Manager shall report planned and actual departures from the baseline PP Implementation Plan to the OSMA at planetary protection status meetings, with elevated reporting at LCRs and KDPs if there is potential to impact compliance of the whole project.

Note: Any departures from the baseline PP Implementation Plan need to be compliant with the PP Requirements Document across the project life-cycle. If these departures deviate from the baseline PP Requirements Document, departures from the baseline PP Requirements Document need to be reported in accordance with paragraph 3.1.2.3.

Note: Projects consult with the OPP to agree to the appropriate number and schedule of the planetary protection status meetings based on mission-specific objectives and design.

3.1.3.4 The NASA Project Manager shall coordinate with the PPO, as part of formulation of the PP Implementation Plan, to define timely independent verification and assurance activities to verify and validate all aspects of planetary protection implementation, including bioburden measurements, modeling assumptions, and other implementation processes used to meet mission-specific standards for biological cleanliness, serving as the technical basis for the Pre Launch PP Report.

3.2 Verification, Assurance, and Pre-Launch Report Activities

3.2.1 The NASA Project Manager, in coordination with the Project-Level SMA TA, shall provide the PPO access to the spacecraft, facilities, and documentation to accommodate planned independent verification and assurance activities as well as anomaly investigations. The NASA Project Manager works with the PPO to plan additional data gathering activities and development of protocols to mitigate risk to planetary protection compliance.

3.2.2 The NASA Project Manager, in coordination with the Project-Level SMA TA, shall notify the PPO of any anomaly events relevant to planetary protection.

Note: The PPO, in coordination with the Project-Level SMA TA, decides which anomaly events need to be investigated and formally reported.

3.2.3 The NASA Project Manager, with concurrence from the authority defined in Table 3 1, shall document the project's execution of the planetary protection implementation activities in the Pre-Launch PP Report by the negotiated schedule in the PP Requirements Document (nominal schedule provided in Table 3 2).

3.2.4 The Pre-Launch PP Report should contain elements that are included in the agreed upon set of accepted standards.

3.2.5 Considerations that may impact compliance with planetary protection requirements are reported to the applicable SMA TA at Launch Readiness Reviews and Flight Readiness Reviews.

3.3 Post-Launch/End of Mission

3.3.1 The NASA Project Manager, with concurrence from the authority defined in Table 3 1, shall document the project's continued execution of the planetary protection implementation activities in the Post-Launch PP Report by the negotiated schedule in the PP Requirements Document (nominal schedule provided in Table 3 2).

3.3.2 The Post-Launch PP Report should contain elements that are included in the agreed upon set of accepted standards.

3.3.3 During mission operations, the NASA Project Manager, in coordination with the Project-Level SMA TA, shall notify the PPO of any discoveries or anomaly events relevant to planetary protection.

Note: The PPO, in coordination with the Project-Level SMA TA, decides which discoveries or anomaly events need to be reported, investigated, and assessed for modifications to planned operations.

3.3.4 If a project plans to extend its mission past the scheduled EOM or add to the planned set of mission objectives, the NASA Project Manager, with concurrence from the authority defined in Table 3 1, shall document the following in the Extended Mission PP Report by the negotiated schedule in the PP Requirements Document (nominal schedule provided in Table 3 2):

a. Information on the new objectives.

b. Compliance with established and any updated project-level planetary protection requirements.

c. Continued execution of the planned planetary protection implementation activities.

Note: Based on their review of the Extended Mission PP Report, the appropriate authority defined in Table 3 1 may re-categorize the mission, which could require updates to the both the PP Requirements Document and the PP Implementation Plan. The intent is to have an open and transparent discussion of the proposed changes prior to a final decision on planetary protection impact of proposed extended mission.

3.3.5 The Extended Mission PP Report should contain elements that are included in the agreed upon set of accepted standards.

3.3.6 The NASA Project Manager, with concurrence from the authority defined in Table 3 1, shall document the project's continued execution of the planned planetary protection implementation activities in the EOM PP Report by the negotiated schedule in the PP Requirements Document (nominal schedule provided in Table 3 2).

3.3.7 The EOM PP Report should contain elements that are included in the agreed upon set of accepted standards.

3.4 Restricted Sample Return and Containment

3.4.1 For missions conducting restricted sample return preventing harmful biological contamination of Earth's biosphere is the highest priority.

3.4.2 For each restricted sample return mission, the MDAA shall establish and implement a strategy and design concepts to break the chain of contact with the target body, isolate, and robustly contain restricted samples. This strategy should be reviewable at MCR.

3.4.3 The MDAA, in coordination with the Chief, SMA and the PPO, shall negotiate a process to assure the safety and containment of Earth-return samples, governed under PD/NSC-25, Scientific or Technological Experiments with Possible Large-Scale Adverse Environmental Effects and Launch of Nuclear Systems into Space, in consultation with OIIR, relevant U.S. government agencies, and international partners.

3.4.4 The process to assure the safety and containment of Earth-return samples should address:

a. Consideration of PD/NSC-25 and the Procedures for Implementing the National Environmental Policy Act (NEPA), 14 CFR ยง 1216.3.

b. Definition of an appropriate risk posture, comparative or otherwise, to inform decisions regarding the biological containment of returned samples.

c. Development, reporting, independent review, and acceptance by relevant authorities of an assurance case substantiating sufficient biological contamination control, including the information necessary to make informed decisions regarding:

(1) Initiation of return activities to the Earth-Moon system.

(2) Verification and validation of flight system return reliability.

(3) Recommendation to federal authorities for Earth entry and landing of returned samples.

(4) Post-landing assessment and verification of sample containment.

(5) Sample release from containment.

d. Participation by the appropriate federal and international authorities.

e. Presumption that returned samples contain hazardous biological material until the Sample Safety Assessment Report has been completed and reviewed.



| TOC | Preface | Chapter1 | Chapter2 | Chapter3 | AppendixA | AppendixB | AppendixC | AppendixD | ALL |
 
| NODIS Library | Program Management(8000s) | Search |

DISTRIBUTION:
NODIS


This document does not bind the public, except as authorized by law or as incorporated into a contract. This document is uncontrolled when printed. Check the NASA Online Directives Information System (NODIS) Library to verify that this is the correct version before use: https://nodis3.gsfc.nasa.gov.