Templates Contracts Agreements Commercial Space Launch Services Agreement
Ready to Edit
Commercial Space Launch Services Agreement - Free Editor

COMMERCIAL SPACE LAUNCH SERVICES AGREEMENT


AGREEMENT NO.: [________________________________]

MISSION DESIGNATION: [________________________________]


PARTIES

LAUNCH SERVICE PROVIDER ("Provider"):

Field Details
Legal Entity Name [________________________________]
Principal Office Address [________________________________]
State of Incorporation/Formation [________________________________]
FAA Launch License No. [________________________________]
CAGE Code [________________________________]
DUNS/UEI Number [________________________________]
Primary Contact [________________________________]
Title [________________________________]
Email [________________________________]
Phone [________________________________]

CUSTOMER ("Customer"):

Field Details
Legal Entity Name [________________________________]
Principal Office Address [________________________________]
State of Incorporation/Formation [________________________________]
Country of Incorporation [________________________________]
FCC Space Station License No. (if applicable) [________________________________]
Primary Contact [________________________________]
Title [________________________________]
Email [________________________________]
Phone [________________________________]

EFFECTIVE DATE: [__/__/____]

This Commercial Space Launch Services Agreement ("Agreement") is entered into as of the Effective Date by and between Provider and Customer (each a "Party" and collectively the "Parties").


RECITALS

WHEREAS, Provider holds a valid vehicle operator license issued by the Federal Aviation Administration ("FAA") pursuant to 14 CFR Part 450 and is engaged in the business of providing commercial launch services for the orbital deployment of spacecraft and payloads;

WHEREAS, Customer desires to engage Provider to transport and deploy Customer's Payload (as defined herein) to the Target Orbit (as defined herein) aboard Provider's Launch Vehicle;

WHEREAS, the Parties intend that this Agreement shall govern the terms and conditions of such launch services, including payload integration, launch scheduling, risk allocation, insurance, regulatory compliance, and related matters;

NOW, THEREFORE, in consideration of the mutual covenants and agreements set forth herein, and for other good and valuable consideration, the receipt and sufficiency of which are hereby acknowledged, the Parties agree as follows:


ARTICLE 1 — DEFINITIONS

1.1 The following terms shall have the meanings set forth below when used in this Agreement:

"Acceptance Review" means the formal review conducted by Provider to confirm that the Payload meets all interface, safety, and integration requirements specified in the ICD and is approved for integration with the Launch Vehicle.

"Anomaly" means any deviation from expected performance of the Launch Vehicle or Payload that may affect mission success, safety, or regulatory compliance.

"Applicable Law" means all federal, state, and local laws, regulations, orders, and requirements of the United States, including without limitation the Commercial Space Launch Act (51 U.S.C. Ch. 509), FAA regulations (14 CFR Parts 400-460), ITAR (22 CFR Parts 120-130), EAR (15 CFR Parts 730-774), FCC regulations (47 CFR Part 25), and all applicable international treaties and agreements to which the United States is a party.

"Catastrophic Failure" means the complete loss or destruction of the Launch Vehicle and/or Payload resulting from a launch mishap, including but not limited to launch pad explosion, in-flight breakup, failure to achieve orbit, or uncontrolled reentry.

"Commissioning Phase" means the period beginning upon Payload Separation and ending upon the earlier of (a) Customer's confirmation of successful Payload activation and health check, or (b) [____] hours after Payload Separation.

"Cross-Waiver of Liability" has the meaning set forth in Article 13.

"Dedicated Launch" means a launch in which the Customer's Payload is the sole primary payload aboard the Launch Vehicle.

"Delivery Orbit" means the initial orbit into which the Payload is placed upon separation from the Launch Vehicle or dispenser, as specified in Exhibit B.

"Dispenser" means the mechanical system, adapter, or deployment mechanism used to secure, transport, and release the Payload from the Launch Vehicle upper stage or kick stage.

"Encapsulation" means the process of installing the Payload within the Launch Vehicle fairing or payload compartment.

"Environmental Envelope" means the combined thermal, acoustic, vibration, shock, and electromagnetic environment to which the Payload will be subjected during ground processing, launch, ascent, and deployment, as specified in the ICD.

"FAA" means the Federal Aviation Administration, including the Office of Commercial Space Transportation (AST).

"Flight Termination System" or "FTS" means the safety system used to terminate the flight of the Launch Vehicle in the event of a trajectory deviation or other safety-critical anomaly.

"ICD" or "Interface Control Document" means the technical document specifying the mechanical, electrical, thermal, and data interfaces between the Payload and the Launch Vehicle, as set forth in Exhibit C.

"Integration Services" means the activities performed by Provider to mechanically and electrically mate the Payload with the Launch Vehicle or Dispenser, conduct interface verification testing, and prepare the integrated stack for launch.

"ITAR" means the International Traffic in Arms Regulations, 22 CFR Parts 120-130, administered by the Directorate of Defense Trade Controls ("DDTC") of the U.S. Department of State.

"EAR" means the Export Administration Regulations, 15 CFR Parts 730-774, administered by the Bureau of Industry and Security ("BIS") of the U.S. Department of Commerce.

"Launch" means the placement of the Launch Vehicle in motion for the purpose of flight, including all pre-launch and post-launch activities necessary to accomplish mission objectives.

"Launch Availability Period" or "Launch Window" means the period during which the Launch is scheduled to occur, as specified in Exhibit A and subject to adjustment pursuant to Article 5.

"Launch Campaign" means the sequence of activities beginning with Payload delivery to the Launch Site and concluding with Launch or stand-down, including integration, testing, fueling, countdown, and launch operations.

"Launch Facility" or "Launch Site" means the facility from which the Launch Vehicle is launched, as identified in Exhibit A.

"Launch Vehicle" means the rocket or space transportation system identified in Exhibit A that Provider will use to transport and deploy the Payload.

"Maximum Probable Loss" or "MPL" means the maximum probable loss determination made by the FAA pursuant to 14 CFR Part 440 for the licensed launch activity.

"Mission" means the complete scope of launch services to be performed under this Agreement, from Payload receipt through Payload Separation and confirmation.

"Mission Success" means (a) the Launch Vehicle lifts off from the Launch Site; (b) the Payload is separated from the Launch Vehicle or Dispenser; and (c) the Payload is delivered to an orbit within the Delivery Orbit Accuracy specified in Exhibit B.

"Delivery Orbit Accuracy" means the permissible deviation from the Target Orbit parameters, as specified in Exhibit B.

"Partial Mission Success" means the Launch Vehicle lifts off and the Payload separates from the Launch Vehicle, but the Delivery Orbit deviates from the Delivery Orbit Accuracy beyond the tolerances specified in Exhibit B.

"Payload" means the Customer's spacecraft, satellite, or other object to be transported and deployed by the Launch Vehicle, as described in Exhibit B.

"Payload Separation" means the physical release and deployment of the Payload from the Launch Vehicle upper stage, kick stage, or Dispenser.

"Rideshare Launch" means a launch in which Customer's Payload shares the Launch Vehicle with one or more other payloads from other customers.

"Target Orbit" means the intended orbital parameters for Payload deployment, as specified in Exhibit B, including altitude (apogee/perigee), inclination, right ascension of the ascending node ("RAAN"), and eccentricity.

"Technical Authority" means the individual(s) designated by each Party as authorized to make binding technical decisions regarding Payload integration, launch operations, and mission execution.


ARTICLE 2 — SCOPE OF SERVICES

2.1 Launch Services. Provider shall furnish the following services to Customer (collectively, "Launch Services"):

☐ (a) Transportation of the Payload from the Launch Site to the Delivery Orbit aboard the Launch Vehicle identified in Exhibit A;

☐ (b) Payload Integration Services, including mechanical and electrical mating of the Payload to the Dispenser or Launch Vehicle interface, in accordance with the ICD;

☐ (c) Pre-launch testing and verification of Payload-to-Launch Vehicle interfaces;

☐ (d) Launch Campaign management and coordination;

☐ (e) Mission planning and trajectory design for delivery to the Target Orbit;

☐ (f) Range coordination and launch site operations;

☐ (g) Telemetry data collection and post-flight mission report;

☐ (h) Payload Separation and deployment sequencing;

☐ (i) Post-separation telemetry confirmation and initial state vector data; and

☐ (j) Such additional services as may be set forth in Exhibit D ("Additional Services").

2.2 Launch Type. This Mission shall be conducted as a:

☐ Dedicated Launch
☐ Rideshare Launch — Primary Payload position
☐ Rideshare Launch — Secondary Payload position
☐ Rideshare Launch — Auxiliary Payload (cubesat/smallsat deployer)

2.3 Rideshare Provisions. If the Mission is a Rideshare Launch:

(a) Provider shall assign Payload deployment sequencing based on mission requirements, orbital mechanics, and the priority of all manifested payloads. Primary Payload requirements shall take precedence over Secondary and Auxiliary Payloads for orbit selection and deployment timing.

(b) Customer acknowledges that the Target Orbit may be constrained by the requirements of the Primary Payload (if Customer is not the Primary Payload customer), and that orbit parameters are subject to optimization for the multi-manifest mission profile.

(c) Provider shall use commercially reasonable efforts to isolate each payload's mechanical, electrical, and electromagnetic environment from other payloads on the Launch Vehicle. Provider shall not be liable for any interference, contamination, or damage arising from the presence of other payloads, except to the extent caused by Provider's gross negligence or willful misconduct.

(d) Each rideshare customer shall execute the Cross-Waiver of Liability set forth in Article 13 with respect to all other manifested payload customers.

(e) In the event of a schedule conflict among rideshare customers, Provider shall resolve such conflicts in its reasonable discretion, giving priority in the following order: (i) Primary Payload; (ii) Secondary Payload(s) by order of contract execution date; (iii) Auxiliary Payloads.

2.4 Exclusions. Unless expressly included in Exhibit D, Launch Services do not include:

(a) Payload design, manufacture, or testing;
(b) Payload transportation to the Launch Site;
(c) Payload licensing (FCC, NOAA, or foreign equivalents);
(d) On-orbit operations, station-keeping, or deorbiting of the Payload;
(e) Frequency coordination or ITU filing services;
(f) Ground station services or mission control for the Payload; or
(g) Procurement of Customer's insurance coverage.


ARTICLE 3 — CONTRACT PRICE AND PAYMENT

3.1 Contract Price. The total price for the Launch Services shall be:

Component Amount (USD)
Base Launch Service Fee $[________________________________]
Integration Services Fee $[________________________________]
Dispenser/Adapter Fee $[________________________________]
Mission-Specific Engineering $[________________________________]
Additional Services (Exhibit D) $[________________________________]
Total Contract Price $[________________________________]

3.2 Payment Schedule. Customer shall pay the Contract Price in accordance with the following milestone schedule:

Milestone Percentage Amount (USD) Due Date
Contract Execution (Non-Refundable Deposit) [____]% $[________________________________] Upon execution
Preliminary Design Review ("PDR") Completion [____]% $[________________________________] [__/__/____]
Critical Design Review ("CDR") Completion [____]% $[________________________________] [__/__/____]
Payload Delivery to Launch Site [____]% $[________________________________] [__/__/____]
Launch Readiness Review ("LRR") Completion [____]% $[________________________________] [__/__/____]
Post-Launch / Mission Completion [____]% $[________________________________] Net [____] days post-Launch

3.3 Late Payment. Any payment not received by its due date shall bear interest at the lesser of (a) [____]% per month or (b) the maximum rate permitted by Applicable Law, calculated from the due date until payment is received.

3.4 Taxes. The Contract Price does not include any sales, use, value-added, excise, or similar taxes. Customer shall be responsible for all such taxes arising from this Agreement, excluding taxes based on Provider's income.

3.5 Currency. All amounts are in United States Dollars unless otherwise specified. Payments shall be made by wire transfer to the account designated by Provider.

3.6 Price Adjustments.

(a) Regulatory Cost Increases. If changes in Applicable Law or regulatory requirements imposed after the Effective Date materially increase the cost of providing Launch Services, Provider may request a price adjustment with documentation of such increased costs. Any adjustment shall be subject to good-faith negotiation between the Parties.

(b) Scope Changes. Any change to the Payload specifications, orbital parameters, or scope of services that materially affects Provider's costs shall be addressed through the Change Order process set forth in Section 4.7.


ARTICLE 4 — PAYLOAD SPECIFICATIONS AND INTEGRATION

4.1 Payload Specifications. Customer shall provide the following Payload specifications no later than [____] days after the Effective Date, subject to updates through the review process:

Parameter Specification
Payload Mass (wet, at separation) [________________________________] kg
Payload Mass (dry) [________________________________] kg
Payload Dimensions (stowed) [________________________________] mm x [________________________________] mm x [________________________________] mm
Payload Dimensions (deployed, if applicable) [________________________________] mm x [________________________________] mm x [________________________________] mm
Center of Gravity (CoG) Location [________________________________]
Moments of Inertia [________________________________]
Payload Power Requirements (pre-separation) [________________________________] W
RF Transmit Frequency/Power [________________________________]
Propellant Type and Volume (if applicable) [________________________________]
Hazardous Materials Classification [________________________________]
Design Lifetime [________________________________] years
Deorbit Capability ☐ Yes ☐ No
Planned Deorbit Timeline [________________________________] years post-mission

4.2 Interface Control Document. The Parties shall jointly develop and agree upon the ICD, attached hereto as Exhibit C, which shall define:

(a) Mechanical interfaces, including separation system, bolt patterns, and adapter specifications;
(b) Electrical interfaces, including umbilical connections, power supply, and command/telemetry links;
(c) Thermal interfaces and constraints;
(d) Contamination control requirements;
(e) Electromagnetic compatibility ("EMC") requirements and RF silence protocols;
(f) Coordinate system definitions; and
(g) Payload accessibility requirements during the Launch Campaign.

4.3 Mission Reviews. The Parties shall conduct the following joint reviews:

Review Target Date Purpose
Mission Kick-Off ("MKO") [__/__/____] Establish mission teams, schedules, and communication protocols
Preliminary Design Review ("PDR") [__/__/____] Review Payload preliminary design for Launch Vehicle compatibility
Critical Design Review ("CDR") [__/__/____] Confirm Payload final design meets ICD requirements
Integration Readiness Review ("IRR") [__/__/____] Verify Payload readiness for integration with Launch Vehicle
Flight Readiness Review ("FRR") [__/__/____] Confirm all systems are go for Launch Campaign
Launch Readiness Review ("LRR") [__/__/____] Final go/no-go determination for Launch

4.4 Payload Delivery. Customer shall deliver the Payload to the Launch Site no later than [____] days prior to the opening of the Launch Availability Period. Payload delivery shall comply with:

(a) Provider's shipping and handling requirements as specified in the ICD;
(b) All applicable hazardous materials transportation regulations (49 CFR);
(c) All export control requirements (ITAR/EAR) applicable to payload transportation; and
(d) Provider's contamination control and cleanroom protocols.

4.5 Integration Operations. Provider shall perform Integration Services in accordance with the ICD and the following provisions:

(a) Provider shall supply the Dispenser or payload adapter as specified in Exhibit A;
(b) Customer's personnel may be present during integration operations, subject to Provider's facility access, safety, and security requirements;
(c) Provider shall conduct fit-check and interface verification testing following mechanical and electrical mating;
(d) Customer shall provide a technically qualified representative ("Customer Technical Authority") to participate in integration reviews and approve integration milestones; and
(e) Provider shall maintain the Payload within the Environmental Envelope at all times following Payload receipt.

4.6 Acceptance Review. Following completion of integration and interface testing, Provider shall conduct an Acceptance Review. Customer's Technical Authority must approve the integration results before proceeding to Encapsulation. If the Acceptance Review reveals non-conformances:

(a) Customer shall, at Customer's expense, correct any Payload-related non-conformances within [____] business days;
(b) Provider shall, at Provider's expense, correct any Launch Vehicle or Dispenser-related non-conformances within [____] business days; and
(c) If non-conformances cannot be corrected within the applicable timeframe, the Parties shall negotiate a revised schedule or scope adjustment in good faith.

4.7 Change Orders. Either Party may request a change to the Payload specifications, mission parameters, or scope of services by submitting a written Change Order Request. The receiving Party shall respond within [____] business days with an assessment of the schedule, cost, and technical impacts of the proposed change. No change shall be effective unless approved in writing by both Parties' authorized representatives.


ARTICLE 5 — LAUNCH SCHEDULE AND DELAYS

5.1 Launch Availability Period. The Launch shall be conducted during the Launch Availability Period specified in Exhibit A:

Parameter Specification
Launch Availability Period Opens [__/__/____]
Launch Availability Period Closes [__/__/____]
Primary Launch Window (daily) [________________________________] UTC to [________________________________] UTC
Backup Launch Window (daily) [________________________________] UTC to [________________________________] UTC
Launch Site [________________________________]

5.2 Schedule Commitment. Provider shall use commercially reasonable efforts to conduct the Launch within the Launch Availability Period. Provider shall provide Customer with schedule updates no less frequently than:

(a) Monthly, beginning [____] months prior to the Launch Availability Period;
(b) Weekly, beginning [____] weeks prior to the Launch Availability Period; and
(c) Daily, during the Launch Campaign.

5.3 Provider-Caused Delays. If Provider delays the Launch beyond the Launch Availability Period for reasons attributable to Provider (excluding Force Majeure events per Article 14), the following provisions shall apply:

(a) Delay of 1-90 days: Provider shall reschedule the Launch at no additional cost to Customer and shall provide a revised Launch Availability Period within [____] business days of the delay determination.

(b) Delay of 91-180 days: In addition to the remedy in (a), Provider shall pay Customer liquidated damages of $[________________________________] per calendar day of delay beyond 90 days, up to a maximum of [____]% of the Contract Price.

(c) Delay exceeding 180 days: Customer may, at its sole option: (i) continue to wait for Launch with liquidated damages continuing to accrue up to the cap; (ii) terminate this Agreement pursuant to Section 16.2 and receive a refund of all amounts paid less the non-refundable deposit and Provider's documented, reasonable costs incurred; or (iii) accept a substitute Launch Vehicle or Launch opportunity offered by Provider, subject to mutual agreement on revised terms.

5.4 Customer-Caused Delays. If Customer delays the Launch due to Payload readiness issues, failure to meet delivery timelines, or other Customer-attributable causes:

(a) Provider shall use commercially reasonable efforts to accommodate the delay within the existing Launch Availability Period;
(b) If the delay extends beyond the Launch Availability Period, Provider shall offer a rescheduled launch, and Customer shall pay a rescheduling fee of $[________________________________] plus any incremental costs incurred by Provider; and
(c) Customer shall remain obligated to make all milestone payments on the original schedule regardless of Customer-caused delays.

5.5 Launch Scrubs and Recycles. Launch scrubs or recycles caused by weather, range safety, or technical anomalies not attributable to a specific Party:

(a) Shall be rescheduled within the Launch Availability Period at no additional cost;
(b) If the Launch Availability Period is exhausted due to scrubs/recycles, the period shall be extended by a period equal to the aggregate delay, at no additional cost to Customer; and
(c) Provider shall provide Customer with a detailed technical briefing within [____] hours of any scrub or recycle event.

5.6 Manifest Prioritization. Provider represents that Customer's Mission is manifested for the Launch Availability Period identified herein. Provider shall not unilaterally remove Customer's Mission from the manifest except:

(a) For safety or regulatory reasons;
(b) As a result of Force Majeure events; or
(c) With Customer's written consent.

If Provider removes Customer from the manifest for reasons other than those in (a) or (b), Customer shall be entitled to the remedies set forth in Section 5.3 as if the removal were a Provider-Caused Delay.


ARTICLE 6 — ORBITAL DEPLOYMENT SPECIFICATIONS

6.1 Target Orbit. Provider shall deploy the Payload to the following Target Orbit:

Parameter Target Value Tolerance (+/-)
Apogee Altitude [________________________________] km [____] km
Perigee Altitude [________________________________] km [____] km
Inclination [________________________________]° [____]°
RAAN (if applicable) [________________________________]° [____]°
Eccentricity [________________________________] [________________________________]
Argument of Perigee (if applicable) [________________________________]° [____]°
Local Time of Ascending Node (if SSO) [________________________________] [________________________________]

6.2 Deployment Sequence. Provider shall deploy the Payload in accordance with the mission profile defined in Exhibit B, including:

(a) Separation altitude, velocity, and attitude;
(b) Separation tip-off rates (angular velocity imparted to Payload at separation) not to exceed: [____]°/sec per axis;
(c) Separation delta-V: [________________________________] m/s (+/- [____] m/s);
(d) Minimum separation distance between Payload and Launch Vehicle upper stage/kick stage at T+[____] seconds: [____] meters;
(e) Post-separation collision avoidance maneuver (if applicable); and
(f) Deployment sequencing relative to other payloads (Rideshare Launch only).

6.3 State Vector Data. Provider shall deliver to Customer the post-separation state vector data (position and velocity in J2000 ECI frame) within [____] hours of Payload Separation, with an accuracy of:

(a) Position: +/- [____] meters; and
(b) Velocity: +/- [____] m/s.

6.4 Mission Success Criteria. Mission Success shall be defined as follows:

(a) Full Mission Success: Payload is separated and delivered within all Delivery Orbit Accuracy tolerances specified in Section 6.1.

(b) Partial Mission Success: Payload is separated but delivered to an orbit outside the Delivery Orbit Accuracy tolerances but still within a usable orbit as mutually determined by the Parties.

(c) Mission Failure: Payload is not separated, is destroyed, or is delivered to an orbit that is not usable.

6.5 Remedies for Orbital Delivery Shortfall.

(a) In the event of Full Mission Success, no additional remedies are due.

(b) In the event of Partial Mission Success attributable to Provider, Provider shall:
☐ (i) Provide a credit of [____]% of the Contract Price toward a future launch; or
☐ (ii) Refund [____]% of the Contract Price; or
☐ (iii) Other remedy as specified: [________________________________]

(c) In the event of Mission Failure attributable to Provider, Provider shall:
☐ (i) Provide a re-flight at no additional charge (excluding Customer's costs to procure a replacement Payload) on the next available Launch Vehicle, subject to Section 6.6; or
☐ (ii) Refund [____]% of the Contract Price; or
☐ (iii) Both a partial refund and a discounted re-flight as mutually agreed.

6.6 Re-Flight Provisions. If a re-flight is elected under Section 6.5(c):

(a) Provider shall offer a re-flight opportunity within [____] months of the Mission Failure;
(b) The re-flight shall be subject to the same terms as this Agreement, except as modified by mutual written agreement;
(c) Customer must deliver a replacement Payload meeting the same or substantially similar specifications within [____] months of the Mission Failure;
(d) Provider shall conduct a failure investigation and share findings relevant to the Payload interface with Customer, subject to Provider's proprietary information protections; and
(e) The re-flight obligation shall not apply if the Mission Failure was caused by Customer's Payload, acts of the U.S. Government, or Force Majeure.


ARTICLE 7 — REGULATORY COMPLIANCE AND LICENSING

7.1 Provider Regulatory Obligations. Provider shall obtain and maintain, at its expense:

(a) A valid FAA vehicle operator license (14 CFR Part 450) covering the Launch;
(b) All required range safety approvals and launch site agreements;
(c) Environmental review and compliance documentation required by the National Environmental Policy Act ("NEPA") and FAA regulations;
(d) Any required spectrum authorization for Launch Vehicle telemetry and tracking;
(e) Financial responsibility determinations and insurance as required by 14 CFR Part 440 and 51 U.S.C. § 50914; and
(f) All other federal, state, and local permits and approvals necessary for the Launch.

7.2 Customer Regulatory Obligations. Customer shall obtain and maintain, at its expense:

(a) FCC space station license or experimental authorization for the Payload (47 CFR Part 25), if applicable;
(b) NOAA remote sensing license (15 CFR Part 960), if applicable;
(c) ITU frequency coordination and filing through the appropriate national administration;
(d) Compliance with FCC orbital debris mitigation requirements (47 CFR § 25.114(d)(14)), including the five-year post-mission deorbit rule for LEO satellites;
(e) All export licenses, technical assistance agreements ("TAAs"), or other authorizations required under ITAR or EAR for the Payload and associated technical data;
(f) Any foreign government licenses or approvals required for Payload operations; and
(g) Space debris mitigation plan in compliance with NASA-STD-8719.14 and IADC/UN COPUOS guidelines, if required by the FCC license or other regulatory authority.

7.3 Regulatory Cooperation. Each Party shall cooperate with the other in obtaining required regulatory approvals, including:

(a) Providing technical data and documentation reasonably necessary for the other Party's license applications;
(b) Participating in regulatory reviews, inspections, and audits as required;
(c) Promptly notifying the other Party of any regulatory action, inquiry, or requirement that may affect the Mission; and
(d) Complying with all conditions and requirements imposed by regulatory authorities on the Mission.

7.4 Regulatory Delay or Denial. If a required regulatory approval is denied or materially delayed:

(a) The affected Party shall promptly notify the other Party and provide all available information regarding the denial or delay;
(b) The Parties shall cooperate in good faith to seek reconsideration, appeal, or alternative regulatory approaches;
(c) If the regulatory issue cannot be resolved within [____] days, either Party may terminate this Agreement pursuant to Article 16, and the provisions of Section 16.4 shall govern the financial consequences; and
(d) Neither Party shall be liable for delays or termination caused by regulatory denial, provided the affected Party exercised reasonable diligence in pursuing the required approval.


ARTICLE 8 — EXPORT CONTROL COMPLIANCE

8.1 ITAR/EAR Classification. The Parties acknowledge:

(a) Launch vehicles, spacecraft, and related technical data may be controlled under ITAR (USML Categories IV and XV) or EAR (CCL Categories 9A and 9E);
(b) The export, re-export, or transfer of controlled articles, technical data, or defense services requires prior authorization from the applicable U.S. Government agency (DDTC for ITAR; BIS for EAR); and
(c) Violations of export control laws may result in severe civil and criminal penalties, including imprisonment, fines, debarment, and denial of export privileges.

8.2 Export Control Obligations.

(a) Each Party shall identify the export control classification of its respective articles, technical data, and services relevant to this Agreement.

(b) Neither Party shall export, re-export, or transfer any ITAR-controlled or EAR-controlled articles, technical data, or services to any foreign person, entity, or country without first obtaining all required U.S. Government authorizations.

(c) Provider shall implement and maintain a Technology Control Plan ("TCP") governing foreign person access to controlled technical data and articles at Provider's facilities, including during Payload integration activities.

(d) Customer shall ensure that all Payload-related technical data provided to Provider is properly marked with applicable export control classification and distribution limitations.

(e) Neither Party shall provide access to controlled technical data or articles to nationals of countries subject to U.S. embargo (currently including, but not limited to, Cuba, Iran, North Korea, Syria, and the Crimea/Donetsk/Luhansk regions), or to any person or entity on the OFAC Specially Designated Nationals List, the BIS Entity List, or the DDTC Debarred List.

8.3 Foreign Customer Provisions. If Customer is a foreign person or entity:

(a) Provider shall obtain all required ITAR/EAR authorizations prior to disclosing any controlled technical data or providing any defense services to Customer;
(b) Customer shall not access Provider's controlled technical data, facilities, or operations except as expressly authorized by the applicable export license or agreement;
(c) The Parties shall execute a Technical Assistance Agreement ("TAA") or other required authorization document prior to the exchange of ITAR-controlled technical data; and
(d) Customer shall comply with all end-use, end-user, and retransfer restrictions imposed by U.S. Government export authorizations.

8.4 Personnel Screening. Each Party shall screen all personnel who will have access to export-controlled articles or technical data under this Agreement against applicable restricted party lists and shall maintain records of such screening.


ARTICLE 9 — INSURANCE

9.1 Provider Insurance. Provider shall procure and maintain the following insurance coverage at its expense:

Coverage Type Minimum Coverage
Third-Party Liability (per 51 U.S.C. § 50914 / 14 CFR Part 440) $[________________________________] or MPL amount determined by FAA, whichever is greater
Government Property Liability $[________________________________] or MPL amount determined by FAA, whichever is greater
Workers' Compensation As required by Applicable Law
Commercial General Liability $[________________________________] per occurrence
Aviation/Space Products Liability $[________________________________] per occurrence

9.2 Customer Insurance. Customer shall procure and maintain the following insurance coverage at its expense:

Coverage Type Minimum Coverage
Payload Pre-Launch Insurance (ground risk) $[________________________________] (full replacement value of Payload)
Launch Insurance (flight risk) $[________________________________] (full replacement value of Payload)
In-Orbit Insurance (if applicable) $[________________________________]
Third-Party Liability $[________________________________]
Workers' Compensation As required by Applicable Law

9.3 Insurance Requirements.

(a) All insurance policies required under this Article shall be placed with insurers having an A.M. Best rating of A- VII or higher (or equivalent international rating).

(b) Each Party shall name the other Party, its officers, directors, employees, agents, contractors, and subcontractors as additional insureds on its third-party liability policies, to the extent required by the Cross-Waiver of Liability (Article 13) and Applicable Law.

(c) Each Party shall provide certificates of insurance to the other Party no later than [____] days prior to Payload delivery to the Launch Site, and promptly upon any renewal, modification, or cancellation of coverage.

(d) Insurance policies shall include a waiver of subrogation in favor of the additional insureds consistent with the Cross-Waiver of Liability.

(e) Insurance policies shall not be cancelled or materially modified without [____] days' prior written notice to the other Party.

9.4 Government Indemnification. The Parties acknowledge that pursuant to 51 U.S.C. § 50915, the U.S. Government may provide indemnification for third-party claims arising from licensed launch activities that exceed the required insurance coverage, up to $1.5 billion (as adjusted for inflation) above the MPL amount. This statutory indemnification is:

(a) Subject to Congressional appropriation and may not be available in all cases;
(b) Not a substitute for the insurance requirements of this Agreement; and
(c) Available only for claims arising from licensed launch activities conducted in compliance with the FAA license and Applicable Law.

9.5 Uninsured Risks. Each Party acknowledges that certain risks associated with space launch activities may be uninsurable or may exceed available insurance coverage. Each Party assumes the risk of loss for its own property and personnel to the extent not covered by insurance, subject to the Cross-Waiver of Liability in Article 13.


ARTICLE 10 — SPACE DEBRIS MITIGATION

10.1 Compliance Standards. Both Parties shall comply with applicable space debris mitigation requirements, including:

(a) FCC orbital debris mitigation rules (47 CFR § 25.114(d)(14));
(b) NASA Procedural Requirements for Limiting Orbital Debris (NPR 8715.6B);
(c) NASA Technical Standard for Orbital Debris (NASA-STD-8719.14);
(d) IADC Space Debris Mitigation Guidelines (Rev. 2020);
(e) UN COPUOS Space Debris Mitigation Guidelines (2007); and
(f) Any debris mitigation requirements imposed by the FAA launch license or FCC space station license.

10.2 Provider Debris Mitigation Obligations. Provider shall:

(a) Design and execute the mission to minimize the creation of orbital debris during launch, staging, and deployment;
(b) Implement passivation of the Launch Vehicle upper stage (depletion or safing of residual propellants, pressurants, and batteries) following completion of payload deployment operations;
(c) Execute a deorbit or disposal maneuver for the Launch Vehicle upper stage and kick stage (if applicable) to ensure reentry or graveyard orbit disposal within [____] years following completion of the Mission; and
(d) Provide Customer with documentation of Launch Vehicle debris mitigation measures and planned disposal activities.

10.3 Customer Debris Mitigation Obligations. Customer shall:

(a) Design and operate the Payload in compliance with the FCC five-year post-mission deorbit requirement for LEO satellites (or 25-year guideline for non-FCC-licensed missions), as applicable;
(b) Include a Payload deorbit or disposal plan in the mission documentation provided to Provider;
(c) Implement passivation measures for the Payload at end of mission;
(d) Equip the Payload with collision avoidance capability or coordinate with the U.S. Space Force 18th Space Defense Squadron for conjunction assessment services;
(e) Comply with any debris mitigation plan commitments made to the FCC, FAA, or other regulatory authorities; and
(f) Notify Provider promptly of any Payload fragmentation, collision, or anomaly that may result in the generation of debris.

10.4 Debris Liability. Each Party shall be responsible for any debris generated by its own hardware (Launch Vehicle components for Provider; Payload for Customer), subject to the Cross-Waiver of Liability in Article 13 and the limitations of liability in Article 12.


ARTICLE 11 — CONFIDENTIALITY AND INTELLECTUAL PROPERTY

11.1 Confidential Information. "Confidential Information" means all non-public technical, business, financial, and proprietary information disclosed by one Party ("Discloser") to the other ("Recipient") in connection with this Agreement, including without limitation:

(a) Launch Vehicle design, performance, and operational data;
(b) Payload design, specifications, and operational parameters;
(c) Pricing, financial terms, and business strategies;
(d) Technical data subject to export control restrictions;
(e) Trade secrets, know-how, and inventions; and
(f) Information marked as "Confidential," "Proprietary," or with similar designation.

11.2 Obligations. The Recipient shall:

(a) Use Confidential Information solely for purposes of performing under this Agreement;
(b) Protect Confidential Information with no less than the same degree of care it uses for its own confidential information, and in no event less than reasonable care;
(c) Limit access to Confidential Information to personnel with a need to know who are bound by confidentiality obligations at least as protective as those in this Article; and
(d) Not disclose Confidential Information to any third party without the Discloser's prior written consent, except as required by Applicable Law or regulatory authority (with prior notice to the Discloser to the extent permitted).

11.3 Exclusions. Confidential Information does not include information that:

(a) Is or becomes publicly available through no fault of the Recipient;
(b) Was known to the Recipient prior to disclosure, as documented by contemporaneous records;
(c) Is independently developed by the Recipient without use of the Confidential Information; or
(d) Is rightfully received from a third party without restriction on disclosure.

11.4 Intellectual Property. Each Party retains all right, title, and interest in its pre-existing intellectual property. No license to either Party's intellectual property is granted under this Agreement except as expressly stated herein. Any intellectual property jointly developed in the course of performing this Agreement shall be governed by a separate IP agreement to be negotiated in good faith.

11.5 Survival. The obligations of this Article shall survive termination or expiration of this Agreement for a period of [____] years, or indefinitely for trade secrets and export-controlled technical data.


ARTICLE 12 — LIMITATION OF LIABILITY

12.1 Limitation of Direct Damages. EXCEPT FOR (A) BREACHES OF ARTICLE 8 (EXPORT CONTROL), (B) BREACHES OF ARTICLE 11 (CONFIDENTIALITY), (C) FRAUD OR WILLFUL MISCONDUCT, AND (D) INDEMNIFICATION OBLIGATIONS UNDER ARTICLE 13, NEITHER PARTY'S TOTAL AGGREGATE LIABILITY UNDER THIS AGREEMENT SHALL EXCEED THE TOTAL CONTRACT PRICE PAID OR PAYABLE.

12.2 Exclusion of Consequential Damages. EXCEPT FOR (A) BREACHES OF ARTICLE 8 (EXPORT CONTROL), (B) BREACHES OF ARTICLE 11 (CONFIDENTIALITY), AND (C) FRAUD OR WILLFUL MISCONDUCT, NEITHER PARTY SHALL BE LIABLE TO THE OTHER FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, PUNITIVE, OR EXEMPLARY DAMAGES, INCLUDING WITHOUT LIMITATION LOSS OF REVENUE, LOSS OF PROFITS, LOSS OF BUSINESS, LOSS OF DATA, LOSS OF GOODWILL, OR COST OF PROCUREMENT OF SUBSTITUTE SERVICES, REGARDLESS OF THE THEORY OF LIABILITY (CONTRACT, TORT, STRICT LIABILITY, OR OTHERWISE) AND EVEN IF SUCH PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

12.3 Essential Basis. The limitations and exclusions of liability in this Article reflect the allocation of risk between the Parties and are an essential basis of the bargain between them. The Contract Price reflects this allocation of risk, and neither Party would have entered into this Agreement without these limitations.

12.4 Customer's Maximum Recovery. Notwithstanding any other provision of this Agreement, Customer's sole and exclusive remedies for Mission Failure or Partial Mission Success shall be limited to those set forth in Sections 6.5 and 6.6. In no event shall Provider's total liability for Mission Failure or Partial Mission Success exceed [____]% of the Contract Price paid by Customer.


ARTICLE 13 — CROSS-WAIVER OF LIABILITY AND INDEMNIFICATION

13.1 Cross-Waiver of Liability. Consistent with the reciprocal waiver framework established by 51 U.S.C. § 50914(b) and 14 CFR § 440.17, and reflecting standard practice in the commercial space launch industry, the Parties agree as follows:

(a) Provider's Waiver. Provider, on behalf of itself and its Related Parties (as defined below), hereby waives and releases any and all claims against Customer and Customer's Related Parties for:
- Property damage or loss sustained by Provider or Provider's Related Parties;
- Bodily injury to, or death of, employees or agents of Provider or Provider's Related Parties;
arising from the Launch Services or related activities under this Agreement, regardless of fault or negligence.

(b) Customer's Waiver. Customer, on behalf of itself and its Related Parties, hereby waives and releases any and all claims against Provider and Provider's Related Parties for:
- Property damage or loss sustained by Customer or Customer's Related Parties, including damage to or loss of the Payload;
- Bodily injury to, or death of, employees or agents of Customer or Customer's Related Parties;
arising from the Launch Services or related activities under this Agreement, regardless of fault or negligence.

(c) "Related Parties" means, with respect to each Party: (i) contractors and subcontractors at any tier; (ii) suppliers; (iii) customers of the Party (including, for Provider, other rideshare customers); (iv) officers, directors, employees, and agents; and (v) any person or entity that the Party is required to include in the cross-waiver under its FAA license or other regulatory requirement.

13.2 Scope of Cross-Waiver. The Cross-Waiver of Liability applies to:

(a) All claims arising from Launch Services and related activities, whether based on contract, tort (including negligence and strict liability), statute, or any other legal theory;
(b) Claims for damage to or destruction of the Launch Vehicle, Payload, or any other property;
(c) Claims for bodily injury or death; and
(d) Claims by or against the U.S. Government, to the extent consistent with the FAA license and Applicable Law.

13.3 Exceptions to Cross-Waiver. The Cross-Waiver of Liability does not apply to:

(a) Claims for willful misconduct;
(b) Claims arising from a Party's breach of its intellectual property, confidentiality, or export control obligations under this Agreement;
(c) Claims by third parties who are not Related Parties of either Party; or
(d) Claims for which the Cross-Waiver would be unenforceable under Applicable Law.

13.4 Third-Party Indemnification.

(a) Provider shall indemnify, defend, and hold harmless Customer and Customer's Related Parties from and against any third-party claims for bodily injury, death, or property damage arising from the Launch Services, to the extent such claims arise from Provider's negligence or willful misconduct, and to the extent not covered by the Cross-Waiver or insurance.

(b) Customer shall indemnify, defend, and hold harmless Provider and Provider's Related Parties from and against any third-party claims for bodily injury, death, or property damage arising from the Payload or Customer's activities under this Agreement, to the extent such claims arise from Customer's negligence or willful misconduct, and to the extent not covered by the Cross-Waiver or insurance.

13.5 Flow-Down Requirement. Each Party shall require its Related Parties to agree to the Cross-Waiver of Liability as a condition of their participation in activities under this Agreement. Provider shall include appropriate cross-waiver provisions in all rideshare customer agreements.

13.6 Insurance Subrogation. Each Party shall ensure that its insurance policies include a waiver of the insurer's right of subrogation against the other Party and its Related Parties, consistent with the Cross-Waiver of Liability.


ARTICLE 14 — FORCE MAJEURE

14.1 Definition. "Force Majeure Event" means any event beyond a Party's reasonable control that prevents or materially delays the Party's performance under this Agreement, including but not limited to:

(a) Acts of God, including but not limited to earthquakes, hurricanes, tornadoes, tsunamis, volcanic eruptions, floods, and other natural disasters;
(b) War (declared or undeclared), armed conflict, terrorism, insurrection, civil unrest, or military action;
(c) Embargoes, sanctions, or trade restrictions imposed by any government;
(d) Government actions, including: (i) revocation, suspension, or non-renewal of required licenses or permits (provided the affected Party exercised reasonable diligence); (ii) launch hold-down orders; (iii) range closures by military or government authority; (iv) imposition of new regulatory requirements materially affecting the Mission;
(e) Epidemics, pandemics, or quarantine restrictions;
(f) Space weather events, including solar storms, geomagnetic disturbances, or elevated radiation levels affecting launch or orbital operations;
(g) Orbital debris conjunction events requiring launch delay or mission abort;
(h) Failure or anomaly of U.S. Government-furnished range safety or tracking systems;
(i) Strikes, lockouts, or labor disputes (excluding those involving the affected Party's own employees, unless industry-wide);
(j) Launch Vehicle or Launch Site infrastructure damage caused by events beyond Provider's reasonable control;
(k) Cyberattack, cyber-warfare, or critical infrastructure disruption attributed to state or non-state actors; and
(l) Any other event of similar nature that is beyond the affected Party's reasonable control.

14.2 Notice. The affected Party shall provide written notice of a Force Majeure Event to the other Party within [____] business days of the event's occurrence, including:

(a) A description of the event;
(b) The anticipated duration and impact on performance;
(c) Steps being taken to mitigate the impact; and
(d) An estimated timeline for resumption of performance.

14.3 Consequences. During a Force Majeure Event:

(a) The affected Party's obligations shall be suspended to the extent and for the duration that performance is prevented or delayed;
(b) Neither Party shall be liable for damages resulting from the delay or non-performance;
(c) The affected Party shall use commercially reasonable efforts to mitigate the impact and resume performance as soon as practicable; and
(d) The Launch Availability Period shall be extended by a period equal to the duration of the Force Majeure Event.

14.4 Extended Force Majeure. If a Force Majeure Event continues for more than [____] consecutive days:

(a) Either Party may terminate this Agreement upon [____] days' written notice;
(b) Upon such termination, Provider shall refund to Customer all amounts paid less the non-refundable deposit and Provider's documented, reasonable costs incurred prior to the Force Majeure Event; and
(c) Neither Party shall have any further liability to the other Party arising from such termination.


ARTICLE 15 — REPRESENTATIONS AND WARRANTIES

15.1 Mutual Representations. Each Party represents and warrants to the other that, as of the Effective Date:

(a) It is duly organized, validly existing, and in good standing under the laws of its jurisdiction of formation;
(b) It has full power and authority to enter into this Agreement and perform its obligations hereunder;
(c) The execution and performance of this Agreement do not violate any law, regulation, or agreement to which it is a party or by which it is bound;
(d) It is not subject to any pending or threatened legal proceedings that would materially affect its ability to perform under this Agreement;
(e) It is not included on any U.S. Government restricted party list (OFAC SDN List, BIS Entity List, DDTC Debarred List); and
(f) It shall comply with all Applicable Laws in performing its obligations under this Agreement.

15.2 Provider Representations. Provider further represents and warrants that:

(a) It holds a valid FAA vehicle operator license and all other necessary authorizations for the Launch;
(b) The Launch Vehicle has been designed, manufactured, and tested in accordance with Provider's quality assurance standards and applicable regulatory requirements;
(c) It has the technical capability and experience to perform the Launch Services;
(d) It shall perform the Launch Services in a professional and workmanlike manner, consistent with industry standards for commercial launch services; and
(e) The Environmental Envelope for the Payload, as specified in the ICD, will not be exceeded during normal Launch Vehicle operations.

15.3 Customer Representations. Customer further represents and warrants that:

(a) The Payload has been designed, manufactured, and tested in accordance with Customer's quality assurance standards and applicable regulatory requirements;
(b) The Payload specifications provided to Provider are accurate and complete;
(c) The Payload does not contain any nuclear materials, biological weapons agents, chemical weapons agents, or other materials prohibited by Applicable Law;
(d) The Payload complies with all applicable radio frequency emission standards and will not operate RF transmitters during launch except as authorized in the ICD;
(e) Customer holds or will obtain all necessary licenses and authorizations for the Payload (including FCC, NOAA, and export control authorizations) prior to the Launch; and
(f) The Payload complies with all applicable space debris mitigation requirements.

15.4 Disclaimer. EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHER PARTY MAKES ANY WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. PROVIDER DOES NOT WARRANT THAT THE LAUNCH WILL BE SUCCESSFUL OR THAT THE PAYLOAD WILL BE DELIVERED TO THE EXACT TARGET ORBIT.


ARTICLE 16 — TERMINATION

16.1 Termination by Mutual Agreement. This Agreement may be terminated at any time by mutual written agreement of the Parties, with financial terms as mutually agreed.

16.2 Termination by Customer for Convenience. Customer may terminate this Agreement for convenience upon written notice to Provider, subject to the following termination fees:

Timing of Termination Notice Termination Fee
More than [____] months before Launch Availability Period opens Non-refundable deposit only
[____] to [____] months before Launch Availability Period opens [____]% of Contract Price
[____] to [____] months before Launch Availability Period opens [____]% of Contract Price
Less than [____] months before Launch Availability Period opens [____]% of Contract Price
After Payload delivery to Launch Site 100% of Contract Price

16.3 Termination for Cause. Either Party may terminate this Agreement for cause if the other Party:

(a) Commits a material breach that remains uncured for [____] days after written notice specifying the breach;
(b) Becomes insolvent, files for bankruptcy, or has a receiver or trustee appointed for its assets;
(c) Has its FAA license, FCC license, or other critical regulatory authorization revoked or suspended and fails to obtain reinstatement within [____] days;
(d) Is placed on any U.S. Government restricted party list; or
(e) Violates export control laws in connection with this Agreement.

16.4 Financial Consequences of Termination.

(a) Termination by Customer for Provider's cause: Provider shall refund all amounts paid by Customer less Provider's documented, reasonable costs incurred prior to the effective date of termination, and shall pay any applicable liquidated damages under Section 5.3.

(b) Termination by Provider for Customer's cause: Customer shall pay all amounts due through the termination date, including any applicable termination fees, and Provider shall have no further obligation to perform Launch Services.

(c) Termination for regulatory denial or Force Majeure: As set forth in Sections 7.4 and 14.4, respectively.

16.5 Survival. The following provisions shall survive termination or expiration of this Agreement: Articles 8, 10 (to the extent of ongoing debris mitigation obligations), 11, 12, 13, and this Section 16.5, as well as any provisions that by their nature should survive termination.


ARTICLE 17 — SAFETY AND SECURITY

17.1 Launch Safety. Provider shall implement and maintain a safety program for the Launch Services that complies with:

(a) FAA safety requirements under 14 CFR Part 450, Subpart C;
(b) Range safety requirements of the applicable launch range;
(c) Provider's internal safety standards; and
(d) The flight safety analysis and hazard analysis submitted to the FAA as part of Provider's launch license application.

17.2 Payload Safety. Customer shall ensure that the Payload complies with Provider's payload safety requirements, including:

(a) Pressurized systems shall be designed with appropriate factors of safety and include pressure relief mechanisms;
(b) Propulsion systems and pyrotechnic devices shall incorporate multiple inhibits (safe/arm mechanisms) to prevent inadvertent activation during ground operations and launch;
(c) Batteries shall be designed to prevent thermal runaway and shall comply with Provider's battery safety requirements;
(d) RF transmitters shall remain in a safe or inhibited state during launch phases designated by Provider, unless otherwise authorized;
(e) Deployable mechanisms shall be restrained until Payload Separation; and
(f) All hazardous materials shall be identified and documented in accordance with Provider's safety data requirements.

17.3 Mishap Investigation. In the event of a launch mishap:

(a) Provider shall conduct a mishap investigation in accordance with FAA requirements and Provider's mishap investigation plan;
(b) Provider shall cooperate with any FAA, NTSB, or other governmental investigation;
(c) Provider shall share investigation findings with Customer to the extent relevant to the Payload and permitted by the investigating authority, subject to Provider's proprietary information protections; and
(d) Neither Party shall make public statements regarding the cause of the mishap without the prior written consent of the other Party, except as required by law or regulatory authority.

17.4 Facility Security. During Customer's access to Provider's facilities:

(a) Customer's personnel shall comply with Provider's security requirements, including background checks, badging, and escort protocols;
(b) Customer shall not photograph, video record, or otherwise capture images of Provider's facilities, equipment, or operations except as expressly authorized in writing;
(c) Provider shall implement appropriate physical and information security measures to protect Customer's Payload and Confidential Information; and
(d) All personnel shall comply with applicable ITAR/EAR technology security requirements, including Technology Control Plans.


ARTICLE 18 — DISPUTE RESOLUTION

18.1 Negotiation. The Parties shall attempt to resolve any dispute arising under this Agreement through good-faith negotiations between their designated representatives. Each Party shall designate a senior executive with authority to resolve the dispute within [____] business days of a written dispute notice.

18.2 Mediation. If the dispute is not resolved through negotiation within [____] days, either Party may submit the dispute to mediation administered by [________________________________] in accordance with its mediation rules. The mediation shall take place in [________________________________]. The costs of mediation shall be shared equally.

18.3 Arbitration. If the dispute is not resolved through mediation within [____] days, the dispute shall be finally resolved by binding arbitration administered by [________________________________] under its [________________________________] Rules. The arbitration shall be conducted:

(a) In [________________________________] (location);
(b) Before a panel of [____] arbitrator(s);
(c) The arbitrator(s) shall have experience in aerospace or commercial space transactions;
(d) In the English language;
(e) In accordance with the Federal Arbitration Act (9 U.S.C. §§ 1-16); and
(f) The arbitrator(s) shall issue a reasoned written award.

18.4 Injunctive Relief. Notwithstanding the foregoing, either Party may seek injunctive or other equitable relief in any court of competent jurisdiction to prevent irreparable harm, including breaches of confidentiality, intellectual property, or export control obligations.

18.5 Continued Performance. Unless this Agreement is terminated, the Parties shall continue to perform their respective obligations during the pendency of any dispute.

18.6 Governing Law. This Agreement shall be governed by and construed in accordance with the federal laws of the United States and, to the extent state law applies, the laws of the State of [________________________________], without regard to conflict of laws principles.


ARTICLE 19 — GENERAL PROVISIONS

19.1 Entire Agreement. This Agreement, including all Exhibits, constitutes the entire agreement between the Parties concerning the subject matter hereof and supersedes all prior negotiations, representations, warranties, commitments, offers, and agreements, whether written or oral.

19.2 Amendments. This Agreement may not be amended except by a written instrument signed by authorized representatives of both Parties.

19.3 Assignment. Neither Party may assign this Agreement or any rights or obligations hereunder without the prior written consent of the other Party, except that either Party may assign this Agreement to an affiliate or in connection with a merger, acquisition, or sale of all or substantially all of its assets, provided that the assignee assumes all obligations under this Agreement and is not on any U.S. Government restricted party list.

19.4 Notices. All notices under this Agreement shall be in writing and delivered by: (a) personal delivery; (b) nationally recognized overnight courier; (c) certified mail, return receipt requested; or (d) electronic mail with confirmation of receipt, to the addresses set forth in the Parties section above or as updated by written notice.

19.5 Severability. If any provision of this Agreement is held to be invalid, illegal, or unenforceable, the remaining provisions shall continue in full force and effect, and the Parties shall negotiate in good faith to replace the invalid provision with a valid provision that achieves the original intent.

19.6 Waiver. The failure of either Party to enforce any provision of this Agreement shall not constitute a waiver of that provision or of the right to enforce it at a later time.

19.7 Independent Contractors. The Parties are independent contractors. Nothing in this Agreement creates a partnership, joint venture, agency, or employment relationship between the Parties.

19.8 Third-Party Beneficiaries. Except as expressly provided in the Cross-Waiver of Liability (Article 13) with respect to Related Parties, this Agreement does not create any rights in any third party.

19.9 Counterparts. This Agreement may be executed in counterparts, each of which shall be deemed an original, and all of which together shall constitute one agreement. Electronic signatures shall be deemed original signatures for all purposes.

19.10 Headings. The headings in this Agreement are for convenience only and shall not affect the interpretation of this Agreement.

19.11 Compliance with Anti-Corruption Laws. Each Party represents that it shall comply with all applicable anti-corruption laws, including the U.S. Foreign Corrupt Practices Act (15 U.S.C. §§ 78dd-1 et seq.) and the UK Bribery Act 2010 (to the extent applicable), and shall not make any payment or provide any benefit to any government official or other person for the purpose of obtaining or retaining business or securing an improper advantage.

19.12 Order of Precedence. In the event of a conflict between the main body of this Agreement and any Exhibit, the main body shall control unless the Exhibit expressly states otherwise.


ARTICLE 20 — EXHIBITS

The following Exhibits are attached hereto and incorporated by reference:

Exhibit A — Launch Vehicle and Launch Site Specifications
Exhibit B — Payload and Orbital Deployment Specifications
Exhibit C — Interface Control Document (ICD)
Exhibit D — Additional Services and Pricing
Exhibit E — Insurance Certificates
Exhibit F — Export Control Classification and Authorizations
Exhibit G — Space Debris Mitigation Plans
Exhibit H — Safety Data Package Requirements
Exhibit I — Key Personnel and Technical Authorities


SIGNATURES

IN WITNESS WHEREOF, the Parties have executed this Commercial Space Launch Services Agreement as of the Effective Date.

LAUNCH SERVICE PROVIDER

Field Details
Signature _________________________________________
Printed Name [________________________________]
Title [________________________________]
Date [__/__/____]

CUSTOMER

Field Details
Signature _________________________________________
Printed Name [________________________________]
Title [________________________________]
Date [__/__/____]

EXHIBIT A — LAUNCH VEHICLE AND LAUNCH SITE SPECIFICATIONS

Parameter Specification
Launch Vehicle Designation [________________________________]
Launch Vehicle Configuration [________________________________]
Launch Vehicle Variant/Version [________________________________]
Fairing Diameter (internal usable) [________________________________] m
Fairing Length (internal usable) [________________________________] m
Payload Capacity to Target Orbit [________________________________] kg
Upper Stage/Kick Stage (if applicable) [________________________________]
Launch Site Name [________________________________]
Launch Site Location [________________________________]
Launch Pad Designation [________________________________]
Launch Azimuth Range [________________________________]° to [________________________________]°
Available Inclination Range [________________________________]° to [________________________________]°
Launch Availability Period Opens [__/__/____]
Launch Availability Period Closes [__/__/____]
Primary Daily Launch Window [________________________________] UTC to [________________________________] UTC
FAA Launch License Number [________________________________]
Range Operator [________________________________]

EXHIBIT B — PAYLOAD AND ORBITAL DEPLOYMENT SPECIFICATIONS

Payload Description

Parameter Specification
Payload Name/Designation [________________________________]
Payload Type ☐ Communications ☐ Earth Observation ☐ Scientific ☐ Technology Demonstration ☐ Navigation ☐ Other: [________________________________]
Payload Bus/Platform [________________________________]
Payload Mass (wet, at separation) [________________________________] kg
Payload Mass (dry) [________________________________] kg
Propellant Type [________________________________]
Propellant Mass [________________________________] kg
Stowed Dimensions (L x W x H) [________________________________] mm x [________________________________] mm x [________________________________] mm
Deployed Dimensions [________________________________] mm x [________________________________] mm x [________________________________] mm
Center of Gravity Location X: [____] mm, Y: [____] mm, Z: [____] mm
FCC License Number [________________________________]
ITU Filing Reference [________________________________]
NOAA License Number (if applicable) [________________________________]
Design Lifetime [________________________________] years
Planned Deorbit Method ☐ Propulsive ☐ Drag Device ☐ Natural Decay ☐ N/A (GEO/Graveyard)
Planned Post-Mission Disposal Timeline [________________________________] years

Target Orbit Parameters

Parameter Value Tolerance
Orbit Type ☐ LEO ☐ MEO ☐ GEO ☐ SSO ☐ HEO ☐ GTO ☐ Other: [____]
Apogee Altitude [________________________________] km +/- [____] km
Perigee Altitude [________________________________] km +/- [____] km
Inclination [________________________________]° +/- [____]°
RAAN [________________________________]° +/- [____]°
Eccentricity [________________________________] +/- [________________________________]
Argument of Perigee [________________________________]° +/- [____]°
LTAN (if SSO) [________________________________] +/- [________________________________]

Separation Parameters

Parameter Value
Separation System Type [________________________________]
Separation Mechanism ☐ Clamp Band ☐ Lightband ☐ Motorized ☐ Spring-Loaded ☐ Other: [________________________________]
Separation Velocity [________________________________] m/s +/- [____] m/s
Max Tip-Off Rate [________________________________] °/sec per axis
Separation Confirmation Method ☐ Telemetry Switch ☐ Visual (Camera) ☐ RF Detection ☐ Other: [________________________________]

EXHIBIT C — INTERFACE CONTROL DOCUMENT (ICD)

[To be developed jointly by Provider and Customer and attached as a separate document. The ICD shall address all mechanical, electrical, thermal, contamination, EMC, and data interfaces between the Payload and Launch Vehicle/Dispenser.]


EXHIBIT D — ADDITIONAL SERVICES AND PRICING

Service Description Price (USD)
[________________________________] [________________________________] $[________________________________]
[________________________________] [________________________________] $[________________________________]
[________________________________] [________________________________] $[________________________________]
[________________________________] [________________________________] $[________________________________]
[________________________________] [________________________________] $[________________________________]

EXHIBIT E — INSURANCE CERTIFICATES

[Insurance certificates to be attached upon procurement and updated as required by Article 9.]


EXHIBIT F — EXPORT CONTROL CLASSIFICATION AND AUTHORIZATIONS

Item Classification Jurisdiction Authorization
Launch Vehicle ☐ ITAR (USML Cat. [____]) ☐ EAR (ECCN [________________________________]) ☐ DDTC ☐ BIS License/TAA No.: [________________________________]
Payload ☐ ITAR (USML Cat. [____]) ☐ EAR (ECCN [________________________________]) ☐ DDTC ☐ BIS License/TAA No.: [________________________________]
Technical Data ☐ ITAR ☐ EAR ☐ Publicly Available ☐ DDTC ☐ BIS License/TAA No.: [________________________________]

EXHIBIT G — SPACE DEBRIS MITIGATION PLANS

Provider Debris Mitigation Summary

Component Disposal Method Timeline
First Stage [________________________________] [________________________________]
Second Stage/Upper Stage [________________________________] [________________________________]
Kick Stage (if applicable) [________________________________] [________________________________]
Fairing [________________________________] [________________________________]
Dispenser/Adapter [________________________________] [________________________________]

Customer Debris Mitigation Summary

Parameter Specification
Post-Mission Disposal Method [________________________________]
Estimated Time to Deorbit [________________________________] years
Probability of Successful Disposal [________________________________]%
Collision Avoidance Capability ☐ Yes ☐ No
Passivation Plan [________________________________]
Compliance Standard ☐ FCC 5-Year Rule ☐ NASA 25-Year Guideline ☐ Other: [________________________________]

EXHIBIT H — SAFETY DATA PACKAGE REQUIREMENTS

Customer shall provide the following safety documentation to Provider no later than [____] days prior to Payload delivery:

☐ Payload hazard analysis report
☐ Pressurized systems design and test data
☐ Propulsion system safety data (including propellant MSDS/SDS)
☐ Battery safety test results and thermal runaway analysis
☐ Pyrotechnic device safety data (safe/arm mechanisms, inhibit design)
☐ RF emission characteristics and EMC test results
☐ Structural analysis and test data (random vibration, shock, static loads)
☐ Contamination control plan and outgassing data
☐ Deployable mechanism restraint verification
☐ Failure modes and effects analysis (FMEA)
☐ List of all hazardous materials with quantities and locations
☐ Range safety data as required by the Launch Site range operator


EXHIBIT I — KEY PERSONNEL AND TECHNICAL AUTHORITIES

Provider Key Personnel

Role Name Contact
Program Manager [________________________________] [________________________________]
Technical Authority [________________________________] [________________________________]
Mission Manager [________________________________] [________________________________]
Integration Lead [________________________________] [________________________________]
Safety Officer [________________________________] [________________________________]

Customer Key Personnel

Role Name Contact
Program Manager [________________________________] [________________________________]
Technical Authority [________________________________] [________________________________]
Payload Engineer [________________________________] [________________________________]
Operations Lead [________________________________] [________________________________]
Export Control Officer [________________________________] [________________________________]

SOURCES AND REFERENCES

The following authorities and resources informed the preparation of this Agreement:

  1. Commercial Space Launch Act — 51 U.S.C. Chapter 509 (sections 50901-50923), governing FAA licensing, insurance, and liability framework for commercial space launches.
  2. FAA Vehicle Operator License Requirements — 14 CFR Part 450, establishing safety, environmental, and operational requirements for commercial launch and reentry.
  3. FAA Financial Responsibility Requirements — 14 CFR Part 440 and 51 U.S.C. section 50914, setting mandatory insurance coverage and maximum probable loss determinations, with third-party liability caps of $500 million and government property caps of $100 million (or world market maximum at reasonable cost).
  4. Government Indemnification — 51 U.S.C. section 50915, providing for U.S. Government indemnification of claims exceeding required insurance, up to approximately $1.5 billion (inflation-adjusted), subject to Congressional appropriation.
  5. Cross-Waiver of Liability — 51 U.S.C. section 50914(b) and 14 CFR section 440.17, establishing the reciprocal waiver framework standard in the commercial space launch industry.
  6. ITAR — 22 CFR Parts 120-130, controlling export of defense articles including launch vehicles (USML Category IV) and satellites (USML Category XV).
  7. EAR — 15 CFR Parts 730-774, controlling export of dual-use space-related items (CCL Categories 9A, 9D, 9E).
  8. FCC Orbital Debris Mitigation — 47 CFR section 25.114(d)(14) and FCC Second Report and Order (FCC 22-74), adopting the five-year post-mission deorbit rule for LEO satellites (effective September 2024).
  9. NASA Orbital Debris Standards — NASA-STD-8719.14 and NPR 8715.6B, establishing technical requirements for limiting orbital debris generation.
  10. IADC Space Debris Mitigation Guidelines — Inter-Agency Space Debris Coordination Committee guidelines (2002, Rev. 2020).
  11. UN COPUOS Space Debris Mitigation Guidelines — United Nations Committee on the Peaceful Uses of Outer Space (2007).
  12. ITU Radio Regulations — International Telecommunication Union framework for frequency coordination and satellite network filing.

This template is provided for informational and educational purposes only and does not constitute legal advice. Commercial space launch transactions involve highly specialized federal regulatory regimes, international treaty obligations, export control restrictions, and substantial financial exposure. All parties should retain qualified aerospace counsel, export control counsel, and insurance specialists before executing any launch services agreement.

Provided by ezel.ai

$49 one-time

Need help customizing this document?

Get 3 days of intelligent editing. Tailor every section to your specific case.

AI Legal Assistant
$49 one-time

Need help customizing this document?

Get 3 days of intelligent editing. Tailor every section to your specific case.

See how AI customizes your document (DEMO)

Commercial Space Launch Ser...
All changes saved
Save
Export
Export as DOCX
Export as PDF
Generating PDF...
space_launch_services_agreement_universal.pdf
Ready to export as PDF or Word
AI is editing...

SPACE LAUNCH SERVICES AGREEMENT

GENERAL TEMPLATE


Effective Date: [DATE]
Party A: [PARTY A NAME]
Address: [PARTY A ADDRESS]
Party B: [PARTY B NAME]
Address: [PARTY B ADDRESS]
Governing Law: [GOVERNING STATE]

This document is entered into by and between [PARTY A NAME] and [PARTY B NAME], effective as of the date set forth above, subject to the terms and conditions outlined herein and the laws of [GOVERNING STATE].
Chat
Review

Customize this document with Ezel

$49 one-time · No subscription

  • Deep Legal Knowledge
    Understands case law, statutes, and legal doctrine.
  • Court-Ready Formatting
    Proper captions, certificates of service, and local rule compliance.
  • AI-Powered Editing for 3 Days
    Edit as many times as you need. Tailor every section to your specific case.
  • Export as PDF & Word PRO
    Download your finished document in professional PDF or DOCX format, ready to file or send.
Secure checkout via Stripe
Need to customize this document?