Browse Arkansas Code titles and sections

42 U.S.C. § 16616, 16617 — Repealed. Pub. L. 111–314, § 6, Dec. 18, 2010, 124 Stat. 3444

Federal law — U.S. Code and appendices · legal_authorities

42 U.S.C. § 16616, 16617 — Repealed. Pub. L. 111–314, § 6, Dec. 18, 2010, 124 Stat. 3444

### Statutory Notes Section 16613, Pub. L. 109–155, title I, § 103, Dec. 30, 2005, 119 Stat. 2907, related to baselines and cost controls. See [section 30104 of Title 51](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title51-section30104&num=0&edition=prelim), National and Commercial Space Programs. Section 16614, Pub. L. 109–155, title I, § 105, Dec. 30, 2005, 119 Stat. 2912, related to foreign launch vehicles. See [section 30703 of Title 51](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title51-section30703&num=0&edition=prelim). Section 16615, Pub. L. 109–155, title I, § 107, Dec. 30, 2005, 119 Stat. 2912, related to implementation plan describing lessons learned and best practices for major programs and projects. See [section 30501 of Title 51](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title51-section30501&num=0&edition=prelim).

Source: Supplied U.S. Code snapshot — release unconfirmed · 42 U.S.C. § 16616, 16617

Stored review status: release_metadata_unconfirmed. A text match is a research starting point; applicability is not established.

Original supplied file — preserved unchanged

Download original Markdown file

File SHA-256: 7b0fcb994f893f6fff6fbf393bd1e2e654d6d91f646391c6db4de8f43f1010c1. The original may include catalog metadata, neighboring provisions, or embedded records outside this collection's scope. Search shows only the selected federal record. Historical editions and unverified snapshots are not a statement of current law.

Authority boundary: historical or unconfirmed source not current law verified.

Record provenance

Stable record: federal_law:legal_authorities:record_usc_c9e19423bf50f7b2f5f8b2be
Source file: Laws/federal/codes/united-states-code/title-42/section-16616-16617-42-u-s-c-16616-16617-repealed-pub-l-111314-6-dec-18-2010-124-stat-3444--76cf0cef3b.md
Pages: Not recorded – Not recorded
Passage SHA-256: 960dd1e0149760eedcc92d54af2e7159692962029f8f1047e931b194dffb308a

Source location: Title 42, Chapter 150, § 16616, 16617; chapter-150-national-aeronautics-and-space-programs-2005.md

Stored source content

Cross-references

Connections may be documented source relationships, shared citations or nearby passages. Each explains its basis; a connection alone does not establish applicability to your situation.

Federal law — U.S. Code and appendices · legal_authorities

51 U.S.C. § 30104 — Baselines and cost controls

**(a) Definitions.—** In this section: (1) **Development.—** — The term “development” means the phase of a program following the formulation phase and beginning with the approval to proceed to implementation, as defined in the Administration’s Procedural Requirements 7120.5E, dated August 14, 2012. (2) **Development cost.—** — The term “development cost” means the total of all costs, including construction of facilities and civil servant costs, from the period beginning with the approval to proceed to implementation through the achievement of operational readiness, without regard to funding source or management control, for the life of the program. (3) **Life-cycle cost.—** — The term “life-cycle cost” means the total of the direct, indirect, recurring, and nonrecurring costs, including the construction of facilities and civil servant costs, and other related expenses incurred or estimated to be incurred in the design, development, verification, production, operation, maintenance, support, and retirement of a program over its planned lifespan, without regard to funding source or management control. (4) **Major program.—** — The term “major program” means an activity approved to proceed to implementation that has an estimated life-cycle cost of more than $250,000,000. **(b) Conditions for Development.—** (1) **In general.—** — The Administration shall not enter into a contract for the development of a major program unless the Administrator determines that— (A) the technical, cost, and schedule risks of the program are clearly identified and the program has developed a plan to manage those risks; (B) the technologies required for the program have been demonstrated in a relevant laboratory or test environment; and (C) the program complies with all relevant p

Source: Supplied U.S. Code snapshot — release unconfirmed · 51 U.S.C. § 30104

Stored review status: release_metadata_unconfirmed. Explicit cross-reference supplied in source Markdown; currentness and applicability require review.

Federal law — U.S. Code and appendices · legal_authorities

51 U.S.C. § 30703 — Foreign launch vehicles

**(a) Accord With Space Transportation Policy.—** The Administration shall not launch a payload on a foreign launch vehicle except in accordance with the Space Transportation Policy announced by the President on December 21, 2004. This subsection shall not be construed to prevent the President from waiving the Space Transportation Policy. **(b) Interagency Coordination.—** The Administration shall not launch a payload on a foreign launch vehicle unless the Administration commenced the interagency coordination required by the Space Transportation Policy announced by the President on December 21, 2004, at least 90 days before entering into a development contract for the payload. **(c) Application.—** This section shall not apply to any payload for which development has begun prior to December 30, 2005, including the James Webb Space Telescope.

Source: Supplied U.S. Code snapshot — release unconfirmed · 51 U.S.C. § 30703

Stored review status: release_metadata_unconfirmed. Explicit cross-reference supplied in source Markdown; currentness and applicability require review.

Federal law — U.S. Code and appendices · legal_authorities

51 U.S.C. § 30501 — Lessons learned and best practices

**(a) In General.—** The Administrator shall transmit to the Committee on Science and Technology of the House of Representatives and the Committee on Commerce, Science, and Transportation of the Senate an implementation plan describing the Administration’s approach for obtaining, implementing, and sharing lessons learned and best practices for its major programs and projects not later than 180 days after December 30, 2005. The implementation plan shall be updated and maintained to ensure that it is current and consistent with the burgeoning culture of learning and safety that is emerging at the Administration. **(b) Required Content.—** The implementation plan shall contain at a minimum the lessons learned and best practices requirements for the Administration, the organizations or positions responsible for enforcement of the requirements, the reporting structure, and the objective performance measures indicating the effectiveness of the activity. **(c) Incentives.—** The Administrator shall provide incentives to encourage sharing and implementation of lessons learned and best practices by employees, projects, and programs, as well as penalties for programs and projects that are determined not to have demonstrated use of those resources.

Source: Supplied U.S. Code snapshot — release unconfirmed · 51 U.S.C. § 30501

Stored review status: release_metadata_unconfirmed. Explicit cross-reference supplied in source Markdown; currentness and applicability require review.