An FAA proposed rule published 9 November 2026 is open for comment until 9 December. Nothing changes until a final rule issues, and the packet does not include the operative text.
What happened.
- The FAA published a proposed rule titled "Conditional Expected Casualty Exception for Failures Resulting in an Uncontrolled Atmospheric Return" in the Federal Register on 9 November 2026 at 91 FR 70813.1,3
- The document is a notice of proposed rulemaking (NPRM), not a final rule.3
- The notice states that comments are due 9 December 2026.1
- An official edition of the same document is published on govinfo; the document number 2026-22784 appears in the URLs of the packet's links.1,2,3
- The packet's only dataset record lists zero US payloads in orbit, zero launches in the last 12 months and zero scheduled launches.4
Why it matters.
- What it changes: nothing yet. As an NPRM it is a proposal rather than a final rule, so the immediate effect is a chance to shape the text through comments.1,3
- What it would change is known here only from the title. The title indicates an exception related to conditional expected casualty for failure cases that end in an uncontrolled atmospheric return; its conditions, thresholds and scope are not in the packet and must be read from the official text.1,2
- For whom: by inference from the title, parties subject to FAA requirements whose failure scenarios include an uncontrolled atmospheric return. Who qualifies, and on what terms, cannot be determined from the packet.1,3
- The comment deadline falls 30 days after publication, which is short for a technical topic. Affected parties that need technical analysis in the record have little time to produce it or to seek an extension.1
- The zero-value dataset record cannot be used to size the affected population. It is better treated as a data gap than as a measure of US activity.4
Connections.
- The Federal Register web edition and the govinfo official edition are the same FAA document (number 2026-22784 in the links), at 91 FR 70813.1,2,3
- Publication on 9 November 2026 and the comment due date of 9 December 2026 give a 30-day comment window.1
- The US activity figures in the packet come from a dataset record that draws on GCAT for payloads by owner state and Launch Library 2 for launches. The record reports zero in every category and is a reported record, not a confirmation.4
Vulnerabilities.
- high Evidence gap: the packet has the proposal's title, citation and comment date but not its operative provisions. Any reading of scope, conditions or beneficiaries rests on the title alone until the official text is reviewed.1,2,3
- medium Compressed timeline: a 30-day window limits how much technical evidence can enter the record. That raises the risk that the final conditions reflect a narrow set of inputs.1
- medium Proposal-stage uncertainty: the text can change between NPRM and final rule. Planning that assumes the exception will be available as proposed carries regulatory risk.3
- low Data reliability: the dataset record's all-zero US figures give no basis for estimating how many operators or missions the exception would reach.4
Forecasts.
The FAA extends or reopens the comment period for this proposed rule beyond 9 December 2026.1,3
A 30-day window on a technical topic can prompt extension requests, but the FAA does not always grant them. The packet shows no request or extension so far.
Signposts Extension requests filed in the rulemaking docket · A Federal Register notice extending or reopening the comment period · A public meeting announcement tied to the proposal
The FAA publishes a final rule based on this proposal in the Federal Register.1,3
Final rules typically take considerable time after the comment period closes for comment review and agency clearance, and nothing in the packet sets a target date or indicates the proposal's complexity. A final rule within about a year is possible but less likely than not.
Signposts Volume and tenor of comments filed by 9 December 2026 · The rule's listing and target date in the agency's regulatory agenda · A final rule or supplemental notice citing 91 FR 70813
The FAA formally withdraws the proposed rule.1,3
Withdrawal of a recently published proposal is uncommon without strong opposition or a change in policy direction. The packet shows neither.
Signposts A Federal Register withdrawal notice · Comments raising substantial public-safety objections · A supplemental notice that replaces the proposal with a different approach
Open questions.
- What conditions must be met to qualify for the exception, and what numerical criterion would apply in its place, if any?
- Which vehicles, mission phases and failure modes does the proposal cover, and does it reach existing authorisations or only new applications?
- What analysis or data would an applicant have to submit to show that it qualifies?
- Will the FAA extend the 9 December 2026 comment deadline or hold a public meeting?
- Why does the packet's dataset record show zero US payloads and launches, and what are the correct figures for sizing the affected population?
Sources.
- 1 Conditional Expected Casualty Exception for Failures Resulting in an Uncontrolled Atmospheric Return · FAA · Nov 9, 2026
- 2 Conditional Expected Casualty Exception for Failures Resulting in an Uncontrolled Atmospheric Return (official edition) · FAA · Nov 9, 2026
- 3 Proposed rule (Notice of proposed rulemaking (NPRM)) published in the Federal Register, 91 FR 70813: Conditional Expected Casualty Exception for Failures Resulting in an Uncontrolled Atmospheric Return · FAA · Nov 9, 2026
- 4 United States: 0 payloads in orbit by owner state (GCAT, J. McDowell, CC-BY-4.0); 0 launches in the last 12 months and 0 scheduled (Launch Library 2, by provider or site country) · exojuris-dataset · Nov 17, 2026