LSP-PD-120.05_Rev_D-2025-02-03.pdf
PDF 187 KB Posted
- Attached to
- NASA Launch Services II (NLS II) 2026 On-Ramp
- Solicitation number
- RFP10-99-0021-Rev_T
About this file
This is a NASA Launch Services Program policy directive establishing minimum launch vehicle telemetry support requirements for National Launch System II (NLS II) missions on launch day.
The document defines telemetry requirements organized into two categories: Mandatory and Required. Mandatory requirements—which cannot be waived once terminal count begins and have no available mitigations if unsatisfied—include receiving and recording all powered flight phases using the launch vehicle primary propulsion system prior to spacecraft separation for NASA primary spacecraft missions (M1), and receiving and recording contamination and collision avoidance maneuvers utilizing the primary propulsion system for NASA primary spacecraft missions (M2). Required requirements, which have minimal mission impact with available mitigations and may be waived during terminal count by the NASA Launch Manager, include receiving and recording depletion burns for NASA primary spacecraft missions (R1); receiving and recording all powered flight phases for NASA secondary spacecraft missions (R2); receiving and recording primary spacecraft separation (R3); receiving and recording Launch Vehicle High Frequency Environmental Data System for NASA primary spacecraft missions (R4); validating the status of Mandatory and Required downrange sites (R5); and receiving prelaunch telemetry and voice at the NASA primary data station where vehicle engineering consoles are located (R6). The directive specifies that terminal count begins at the start of dynamic launch day operations such as propellant loading or aircraft movement, and that waivers prior to terminal count must be identified at the Flight Readiness Review or closest review thereafter, while waivers issued on launch day must be announced verbally to the launch team by the NASA Launch Manager. This Revision D, approved February 3, 2025, removed exceptions to store and forward telemetry coverage from the previous version.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| FAR 52.222-90.pdf | ||
| 2. Matrix of Changes_Amendment 2.pdf | ||
| 3. RFP10-99-0021 Rev T_Amendment 2.docx | DOCX document | |
| 3. RFP10-99-0021 Rev T_Amendment 1.docx | DOCX document | |
| 2026 On-Ramp Questions and Answers.pdf | ||
| 2. Matrix of Changes_Amendment 1.pdf | ||
| 2. Matrix of Changes.pdf | ||
| 3. RFP10-99-0021 Rev T.pdf |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
National Aeronautics and Space Administration LSP-PD-120.05 John F. Kennedy Space Center, Florida Revision D
Launch Services Program
Launch Telemetry Requirements
Approved: Approved Date: 02/03/2025
Jorge Piquero LSD&R Manager
RELEASED - Printed documents may be obsolete; validate prior to use.RELEASED - Printed documents may be obsolete; validate prior to use.
LSP-PD-120.05
Rev. D
Revision History
Revision Description Date
Basic Basic release April 27, 2005
A Updated job titles & format, enumerated list of requirements, removed "may" from M2, added "for NASA primary SC missions" to R1, added R4, rephrased D3 & added D4 & *note regarding store & forward techniques to Desired, removed words regarding LSP Process Flow for Obtaining Launch Telemetry Support and AVO-format waiver from Waiver Authority, added **note regarding terminal count definition to definition of Mandatory
May 31, 2011
B Added pre-launch requirements, changed definitions to highlight impact of loss of requirement
June 5, 2015
C Updated the Executive Summary on page 3, first sentence to clarify that this document is not applicable to VADR
June 9, 2023
D Remove exception to store and forward telemetry coverage in the Table on page 3.
Feb 03, 2025
RELEASED - Printed documents may be obsolete; validate prior to use.RELEASED - Printed documents may be obsolete; validate prior to use.
EXECUTIVE SUMMARY:
This directive establishes the Launch Services Program policy for minimum launch vehicle telemetry support requirements for the day of launch for NLS II missions. This data is used prior to launch to validate launch vehicle readiness and to assist in anomaly resolution. This data is used during and after launch to verify mission success and spacecraft environmental contractual requirements.
Mandatory
M1 - Receive and record all phases of powered flight utilizing the launch vehicle primary propulsion system prior to spacecraft separation for all NASA primary spacecraft missions.
M2 - Receive and record contamination and collision avoidance maneuvers that utilize the primary propulsion system for all NASA primary spacecraft missions.
Required
R1 - Receive and record depletion burns for NASA primary spacecraft missions
R2 - Receive and record all phases of powered flight utilizing the primary propulsion system prior to spacecraft separation for all NASA secondary spacecraft missions.
R3 - Receive and record primary spacecraft separation.
R4 – Receive and record Launch Vehicle High Frequency Environmental Data System for NASA primary spacecraft missions
R5 – Validate the status of the Mandatory and Required down range sites
R6 – Receive prelaunch telemetry and voice at the NASA primary data station where the NASA vehicle engineering consoles are located.
RELEASED - Printed documents may be obsolete; validate prior to use.RELEASED - Printed documents may be obsolete; validate prior to use.
Definitions:
Required – These requirements have minimal impact to mission success and mitigations are available if they are not satisfied. These requirements may be waived during terminal count by the NLM.
Mandatory – Mandatory – These requirements have an impact to the verification of mission success, and if not satisfied, mitigations are not available. Once within terminal count, a mandatory requirement cannot be waived.In exceptional cases, Mandatory requirements may be changed to Required by the Launch Services NLM prior to entering terminal count.
Secondary Spacecraft Mission - This mission type will be identified in the Launch Service Provider contract.
Terminal Count begins at the start of dynamic launch day operations, such as propellant loading or aircraft movement.
Note: Waivers prior to the terminal count shall be identified in written or verbal format at the
Flight Readiness Review or closest review thereafter. Waivers issued on launch day shall be announced verbally to the launch team by the NLM.
RELEASED - Printed documents may be obsolete; validate prior to use.RELEASED - Printed documents may be obsolete; validate prior to use.
File details come from the government source that posted it. Updated .