Codify — Article

SPACEPORT Act restructures federal spaceport grant program and reporting duties

Recasts eligible recipients, pushes DOT-led selection criteria and interagency consultation, and requires new reports while authorizing $10M per year for spaceport modernization grants.

The Brief

The SPACEPORT Act updates chapter 511 of Title 51 to modernize the federal grant program that supports space launch and re‑entry infrastructure. It refocuses selection priorities toward civil, national security, and commercial needs and requires the Department of Transportation to craft specific evaluation criteria and consult other agencies before awarding grants.

The bill also mandates a multi‑part report to Congress assessing demand, funding options, and international capabilities, changes who can receive grants, and renames the chapter to emphasize “Space Transportation Infrastructure Modernization.” For practitioners, the measure shifts program governance to DOT, tightens the policy lens on resilience and competitiveness, and creates a recurring congressional reporting obligation that will shape future funding choices.

At a Glance

What It Does

The bill revises statutory definitions of eligible recipients, limits federal contribution to projects to 90% of total cost (subject to a national‑interest waiver), requires DOT to develop specific project selection criteria, and orders interagency consultation with DoD, NASA, and Commerce. It also requires an initial comprehensive report to Congress with updates and authorizes annual appropriations for the program.

Who It Affects

State governments, political subdivisions, airport authorities, and tax‑supported organizations that build or upgrade launch and re‑entry infrastructure; companies that operate launch services; and federal agencies (DOT, DoD, NASA, Commerce) that will participate in project evaluation and consultations.

Why It Matters

The changes tighten federal oversight of spaceport investments, prioritize projects with civil, commercial, and national security value, and create a statutory mechanism for recurring, cross‑agency assessments of demand and funding models — all of which will influence which projects get funded and how local partners plan matching resources.

More articles like this one.

A weekly email with all the latest developments on this topic.

Unsubscribe anytime.

What This Bill Actually Does

The bill rewrites the guardrails around a small federal grant program that finances space launch and re‑entry infrastructure. It broadens who counts as a potential recipient by explicitly including airport authorities and tax‑supported organizations, which can change which local entities can sponsor projects.

Instead of a vague list of considerations, the statute now pushes the Department of Transportation to build clear, ranked selection criteria and to consult with Defense, NASA, Commerce, and other relevant agencies on key technical and security issues.

Financially, the statute caps the federal share at 90 percent of a project’s cost but gives DOT authority to waive that cap in cases the Secretary deems in the national interest. That structure preserves a required local stake in projects while leaving a high ceiling for federal support where national priorities are at play.

The bill also renames the chapter to emphasize ‘infrastructure modernization,’ signaling a policy orientation toward upgrading facilities rather than funding routine maintenance.On information and planning, DOT must deliver a detailed report within two years that evaluates domestic and international demand, proposes legislative and regulatory fixes, explores long‑term funding approaches, and compares U.S. capabilities with foreign investments. The bill then requires a substantive follow‑up at six years and updates every four years thereafter.

Practically, that creates a recurring evidence base that can be used to justify appropriations or reshape program priorities.Finally, the legislation sets an annual authorization level for the program. In practice, the authorized ceiling and the program’s small statutory footprint mean recipients should treat approved grants as partial contributions that will still require local financing strategies, project packaging to meet federal criteria, and coordination with multiple federal stakeholders before award decisions are final.

The Five Things You Need to Know

1

The bill amends paragraph (5) of 51 U.S.C. §51101 to expand the statutory definition of “public agency” to include airport authorities and tax‑supported organizations.

2

It amends 51 U.S.C. §51102(b) to limit federal grants to no more than 90% of a project’s total cost, while giving the Secretary of Transportation authority to waive that limit if doing so is in the national interest.

3

Section 51103(b) is revised so the Secretary of Transportation must develop specific evaluation and selection criteria and consult with the Secretary of Defense, NASA’s Administrator, the Secretary of Commerce, and other appropriate agency heads on certain considerations.

4

The bill requires DOT to submit to Congress, within two years, a report evaluating civil, national security, and commercial space transportation demand, recommending legislative/regulatory changes, examining long‑term funding options, and assessing international capabilities; DOT must update that report at six years and then every four years.

5

It replaces the existing appropriation language at 51 U.S.C. §51105 to authorize up to $10,000,000 per fiscal year for grants under the chapter and renames the chapter to “Space Transportation Infrastructure Modernization Grants.”.

Section-by-Section Breakdown

Every bill we cover gets an analysis of its key sections. Expand all ↓

Section 1

Short title

Provides the Act’s name: the Spaceport Project Opportunities for Resilient Transportation Act, or SPACEPORT Act. This is purely a caption but signals the legislative purpose: resiliency and project opportunity for space transportation infrastructure.

Section 2(a) — Definitions (51 U.S.C. §51101(5))

Who qualifies as a public agency

Expands the statutory definition of “public agency” to explicitly include State agencies, political subdivisions, airport authorities, and tax‑supported organizations. That change clarifies eligible applicants and can broaden which local entities can apply for grants; airport authorities in particular may now be direct recipients rather than relying on another municipal sponsor.

Section 2(b) — Grant limitations (51 U.S.C. §51102(b))

Federal cost share cap and national‑interest waiver

Sets the default federal contribution ceiling at 90% of project cost and creates a waiver if the Secretary finds the higher share is in the national interest. Practically, the cap forces some level of local contribution for most projects while giving DOT flexibility to fund larger shares for projects essential to national security or other high‑priority objectives. The waiver language is administrable by the Secretary but leaves the national‑interest standard undefined in statute, which preserves discretion.

2 more sections
Section 2(c) — Eligibility and selection criteria (51 U.S.C. §51103(b))

DOT‑led criteria and required interagency consultation

Recasts the statutory evaluation factors to emphasize civil, national security, and commercial needs and replaces a general directive with a requirement that DOT develop specific selection criteria. It also amends statutory language to require DOT consult DoD, NASA, Commerce, and other agencies on particular considerations, which institutionalizes interagency input into award decisions and may lengthen pre‑award reviews.

Section 2(d–e) — Reporting and funding (report requirement & 51 U.S.C. §51105)

Mandatory reports to Congress and annual authorization

Mandates a substantive report within two years that evaluates domestic and international demand, offers legislative and regulatory recommendations, examines long‑term funding models, and compares foreign investments; DOT must update this report at six years and every four years thereafter. The bill also sets an annual authorized appropriation of up to $10 million for the grant program, fixing a statutory funding ceiling that will constrain program scale unless changed by later legislation.

At scale

This bill is one of many.

Codify tracks hundreds of bills on Transportation across all five countries.

Explore Transportation in Codify Search →

Who Benefits and Who Bears the Cost

Every bill creates winners and losers. Here's who stands to gain and who bears the cost.

Who Benefits

  • Airport authorities and tax‑supported organizations — the expanded definition lets these entities apply directly for grants, simplifying sponsorship and potentially accelerating project packaging and permitting.
  • State and local governments that host launch sites — inclusion of broader eligibility and a high federal ceiling (90%) can reduce local matching burdens for high‑priority projects and improve access to federal funds.
  • Commercial launch operators — the refocused selection criteria that explicitly value commercial needs increase the likelihood that projects enabling commercial launch operations (pad upgrades, range infrastructure, integration facilities) will score well in DOT evaluations.
  • Federal planners and policymakers — DOT and partner agencies gain a recurring data stream and formal interagency consultation process to align infrastructure investments with civil, commercial, and national security priorities.

Who Bears the Cost

  • State and local sponsors — even with a 90% federal cap, sponsors must still forecast and secure the remaining share and absorb project delivery, permitting, and operational costs not covered by grants.
  • Department of Transportation — DOT takes on new administrative work: drafting selection criteria, running interagency consultations, preparing the mandated reports, and managing waiver decisions without additional statutory staff resources.
  • Department of Defense and other consulted agencies — DoD, NASA, and Commerce will need to provide technical input and review for DOT selection processes, increasing their workload for interagency coordination.
  • Federal budget process — the $10 million annual authorization establishes a modest statutory limit; if program demand exceeds that ceiling, Congress or DOT will face tradeoffs or need to seek larger appropriations.

Key Issues

The Core Tension

The central dilemma is between concentrating federal support to secure national and commercial space capabilities quickly (enabled by a high federal share and waiver authority) and preserving local investment and prudent federal fiscal discipline (enforced by a cap and modest annual authorization); the bill leans toward centralized, discretionary support while leaving the limits of appropriations and procedural transparency unresolved.

Two implementation problems loom. First, the 90% cap plus an undefined “national interest” waiver centralizes powerful discretion in the DOT Secretary; without statutory guidance or a required transparency mechanism for waiver decisions, applicants may face uncertainty about when full federal support is possible.

Second, the authorization of $10 million per year creates a structural constraint: the program’s renamed mission of “infrastructure modernization” suggests larger capital needs than the statutory ceiling will cover, so either appropriations will need to exceed the authorization or only a handful of projects will be funded.

Operationally, the required interagency consultation adds valuable technical and security perspectives but risks slowing project timelines and muddying accountability if agencies offer conflicting guidance. The mandated reporting cadence (initial report at two years, a substantive update at six years, and then every four years) will produce useful strategic guidance but also creates expectations for program evolution that may outpace appropriations or the program’s administrative capacity.

Finally, expanding eligibility to airport authorities and tax‑supported organizations smooths access but shifts how projects are sponsored, financed, and insured — practical details (e.g., procurement rules, liability frameworks) are left for implementing guidance, not the statute.

Try it yourself.

Ask a question in plain English, or pick a topic below. Results in seconds.