Launch Services
Range safety, licensing, and launch provider compliance
Launch services involve complex regulatory requirements from FAA licensing to range safety certification. Thalorin supports launch providers with compliance infrastructure addressing the full spectrum of launch requirements, from initial licensing through mission assurance.
The National Space Transportation Policy issued as NSPM-17 on 20 August 2026 revoked Presidential Policy Directive 26 of 21 November 2013 and set the goal that American ranges grow to support more than a thousand launches and reentries every year by 2030. It gives the Secretary of Transportation 180 days to identify potential new launch facility locations and to designate priority space launch corridors, the Secretary of War 180 days to develop Federal range scheduling criteria for commercial users, and asks agencies to develop fair and transparent cost recovery policies for common services and infrastructure.
Underneath the policy, licensing has finished consolidating and started moving again. Legacy authorisations expired no later than 10 March 2026, parts 415, 417, 431 and 435 are now reserved, and one Part 450 vehicle operator licence can cover a portfolio of missions, configurations and sites. Executive Order 14335 of 13 August 2025 then directed the Secretary of Transportation to reevaluate, amend or rescind those same Part 450 requirements. What Part 450 does not contain, before or after that review, is a cybersecurity requirement.
A portfolio licence moves the work from the application to configuration control, and that is the shift providers underestimate. The licence authorises operations that stay inside the flight safety analysis, the hazard analyses and the safety-critical system definitions that justified it. A change to a vehicle, trajectory or site is lawful only if it can be shown against those analyses, and a company treating licensing as a one-time approval reconstructs that link under schedule pressure.
The licensed envelope is the object Thalorin keeps. Configurations, trajectories and sites are held against the analyses that authorised them, so a proposed change is judged inside or outside the envelope before it flies rather than after the fact. Customer-imposed security terms stay attached to the task order that created them, which keeps a requirement written for one national security mission from quietly becoming a company-wide standard that nobody chose and no contract pays for.
Space operations face unique security challenges
Part 450 is the only route now
Legacy authorisations expired no later than 10 March 2026 and parts 415, 417, 431 and 435 are reserved in the code. Procedures, supplier flow-downs and training referencing them point at regulations that no longer exist.
Public risk limits are analysis results
14 CFR 450.101 sets quantitative collective and individual casualty limits for the public, for neighbouring operations personnel and for aircraft. Those are outputs of analysis for a given configuration and trajectory, re-established per operation rather than asserted once.
Two safety authorities on one countdown
The FAA licence and the Federal range's own 91-710 user requirements apply to the same operation with different documentation and different reviewers. Maintaining two unconnected evidence sets multiplies work without improving safety.
Financial responsibility is set by the FAA
Insurance amounts follow the FAA's maximum probable loss determination under 14 CFR part 440, and the agency has up to ninety days from a complete submission. A schedule assuming that figure in advance depends on a number the operator does not set.
How Thalorin helps
FAA launch licensing support
Hold the Part 450 review elements as one state — policy, payload, safety and environmental material plus financial responsibility — so a licence modification draws on current evidence rather than a fresh assembly effort.
Range safety compliance
Map the range's 91-710 user requirements and the 14 CFR part 420 explosive site plan against the Part 450 analyses where they overlap, so one piece of evidence answers both the range safety office and the FAA.
Mission assurance documentation
Generate National Security Space Launch certification evidence and NASA mission assurance deliverables from the same configuration record the flight safety analysis references, so customer packages cannot drift from the licensed vehicle.
Launch site cybersecurity
Scope launch site ground and control systems as an authorisation boundary in their own right, applying DFARS 252.204-7012 where a task order imposes it rather than across the whole site by default.
Payload integration security
Segregate payload data, customer proprietary information and export-controlled technical data per customer, and carry the 14 CFR 450.43 payload review and determination alongside the integration record it depends on.
Commercial launch requirements
Carry the commercial-specific obligations that ride beside the licence — reciprocal waivers of claims under 14 CFR part 440, and the 14 CFR part 460 requirements where a space flight participant is aboard — against the mission that triggers them.
Launch Services: common questions
Can a launch operator still fly under a legacy FAA licence?
No. Licences issued under the old parts remained valid no later than 10 March 2026, five years after Part 450 took effect, and parts 415, 417, 431 and 435 are now reserved in the Code of Federal Regulations. Every FAA launch and reentry licence sits under Part 450. The practical residue is internal rather than regulatory: quality procedures, supplier requirements and training material still cite the retired parts long after the licence itself has moved.
What public risk limits does a Part 450 licence impose?
14 CFR 450.101 sets quantitative criteria per launch or reentry. Collective risk to the public must not exceed an expected casualty figure of one ten-thousandth, with two ten-thousandths for neighbouring operations personnel. Individual risk must not exceed a probability of casualty of one in a million for a member of the public and one in a hundred thousand for neighbouring operations personnel, and the probability of impact with debris capable of causing an aircraft casualty must not exceed one in a million.
Does the FAA regulate cybersecurity for launch vehicles?
Not through the licence. Part 450 governs public safety and contains no cybersecurity requirement for the vehicle, the ground system or the launch site. Security obligations reach launch providers through the customer instead: DFARS clauses and Controlled Unclassified Information handling on National Security Space Launch work, NASA requirements on civil payloads, and range access conditions. Requirements therefore differ per contract, and no single posture satisfies all of them at once.
How is launch insurance determined?
The FAA determines it. Under 14 CFR part 440 the agency calculates the maximum probable loss from covered third-party claims for bodily injury or property damage and from covered damage to government property, then prescribes the required insurance from that figure. It issues the determination no later than ninety days after a licensee submits a complete request and all the information the FAA needs. Maximum probable loss is a probabilistic estimate, not a ceiling on possible loss.
When can the FAA regulate the safety of people on board commercial spacecraft?
Broadly, from 1 January 2028. Under 51 U.S.C. 50905(c) the Secretary may currently propose occupant safety rules only within narrow limits — restricting design features or operating practices that have caused a serious or fatal injury, or contributed to an event posing a high risk of one. From 1 January 2028 the Secretary may propose regulations without regard to those two constraints. Congress has moved that date repeatedly, so treat it as current rather than settled.
Regulatory state described as of August 2026. Requirements change; verify against the current rule before relying on any date above.
Talk to us about Launch Services.
See how one evidence artifact satisfies Launch Services requirements alongside every other framework you carry.