The bill amends 49 U.S.C. 47114(d)(4) to let the Secretary of Transportation use a State's highway construction specifications for building or improving airfield pavement at nonprimary airports that serve aircraft with a gross weight of 60,000 pounds or less. That substitution is allowed only after the State notifies the Secretary of its intent and the Secretary determines the highway specifications will not negatively affect safety.
The change applies to projects funded under the amended subsection and an identified related funding clause.
This is a targeted deregulatory move aimed at lowering costs and aligning airport pavement work with existing State highway procurement and design practices at smaller airports. It shifts certain technical decisions from a uniform federal standard toward a case-by-case FAA safety determination, which matters for airport owners, State DOTs, contractors, and FAA program managers responsible for federally assisted projects and long-term pavement performance.
At a Glance
What It Does
The bill allows the FAA to accept State highway pavement specifications instead of federal airport pavement standards for construction or improvement projects at qualifying nonprimary airports, when the State notifies the Secretary and the Secretary concludes safety won’t be compromised. The permission applies only to projects funded under the referenced subsections of 49 U.S.C. 47114.
Who It Affects
Nonprimary airport sponsors, State departments of transportation, and contractors who build pavement at airports will see the most immediate change. The FAA’s engineering and grant-management teams will absorb new review responsibilities for safety determinations tied to pavement standards.
Why It Matters
By enabling highway specs at smaller airports, the bill can reduce design and construction costs, speed procurement, and leverage State contracting capacity; but it also replaces a one-size-fits-all federal technical baseline with an FAA safety assessment that will determine whether divergent highway practices are acceptable for aircraft operations.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The Airport Regulatory Relief Act revises federal law to permit a State’s highway pavement specifications to be used for airfield pavement projects at nonprimary airports that serve aircraft with gross weights up to 60,000 pounds. The change is not automatic: a State must notify the Secretary of Transportation that its nonprimary airports intend to adopt highway specifications, and the Secretary must first decide that doing so won’t harm safety.
The statutory text ties this authority to projects carried out with funds available under the amended subsection and an identified related funding clause.
Practically, this means airport sponsors and State DOTs can propose pavement designs rooted in highway engineering—thickness tables, material specifications, compaction requirements, and testing regimes—rather than being constrained to current federal airport pavement criteria for certain federally-funded projects. The Secretary’s review is the safety gate: the FAA will need criteria and evidence to evaluate whether highway-derived designs accommodate aircraft load characteristics, tire pressures, and operational needs at the specific airport.For small and rural airports, the expected upside is lower upfront design and construction costs and simpler procurement because many States already maintain highway specification libraries and contracting systems.
For the FAA and airport engineers, the bill creates a new technical review workload and a potential need for guidance on when highway criteria are equivalent to—or unacceptable compared with—airport pavement standards. The law leaves open what data will satisfy the Secretary’s safety finding and how long-term performance and maintenance obligations will be tracked under grant conditions.The statute also sets a clear scope: the permission is limited to “nonprimary” airports and aircraft whose gross weight does not exceed 60,000 pounds.
That weight threshold excludes larger regional jets and most commercial airliners, focusing the change on general aviation, many turboprops, and smaller business jets. The provision therefore targets a narrow slice of airport pavement work where highway-style practice may be more readily adapted to aircraft loading profiles.
The Five Things You Need to Know
The bill amends 49 U.S.C. 47114(d)(4) to let the Secretary use State highway specifications for airfield pavement at nonprimary airports serving aircraft ≤ 60,000 lbs, subject to State notice and an FAA safety finding.
The permission applies only to projects funded under the subsection amended and the specific related funding clause referenced in the statute, so federal funds are still implicated.
States must affirmatively notify the Secretary that nonprimary airports in the State intend to use highway specifications; there is no automatic or blanket statewide approval without notice.
The Secretary (i.e.
FAA) must determine that the highway specifications “will not negatively affect safety,” creating a discretionary, safety-based review prior to allowing highway standards on a given project.
The exception is limited by airport type (nonprimary) and an explicit aircraft gross-weight cap—60,000 pounds—so it does not apply to larger commercial or primary airports.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Short title
Provides the Act’s name: the “Airport Regulatory Relief Act of 2025.” This is a standard naming clause with no operational effect, but it frames the bill as a deregulatory, airport-focused statute for use in legislative text and citations.
Amend 49 U.S.C. 47114(d)(4) to allow State highway specs
Replaces the current paragraph to authorize the Secretary to ‘use the highway specifications of a State’ for airfield pavement construction and improvement at qualifying airports. The change is narrow: it does not rewrite grant conditions generally but inserts a specific substitution authority for pavement specifications within the existing statutory framework that governs airport funding and standards.
Scope: nonprimary airports and 60,000‑pound limit
The amendment confines the substitution to nonprimary airports and explicitly caps the aircraft gross weight at 60,000 pounds. That scope limits the provision to smaller airports and excludes larger commercial operations; in practice, this targets general aviation and many regional operations where pavement loads and operational tempos differ from major airports.
Process: State notice and Secretary safety determination
Two procedural gates control use of highway specifications. First, the State must notify the Secretary that its nonprimary airports intend to use highway standards. Second, the Secretary must evaluate and find that those specifications will not negatively affect safety. The statutory text ties the substitution to specific funding subsections, so federal dollars remain connected to projects using the alternative specifications.
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
- State departments of transportation — They can extend existing highway design libraries and contracting practices to airport pavement work, reducing duplication and leveraging established procurement and materials-testing capacity.
- Nonprimary airport sponsors (municipalities, counties, airport authorities) — They may see lower design and construction costs, simpler bids, and faster delivery when highway specifications replace federal airport-specific criteria for qualifying projects.
- Highway-focused contractors and suppliers — Firms already certified for State highway work may gain access to airport projects without needing separate airport‑specific certification or to redesign to airport standards.
Who Bears the Cost
- Federal Aviation Administration (FAA) and the Secretary’s engineering teams — The FAA must evaluate State specifications, develop review criteria, and potentially expand oversight and post-construction monitoring to ensure safety over time.
- Nonprimary airport owners in the long term — If highway standards are less well-matched to aircraft tire pressures, concentrated loads, or fuel/resistance requirements, airports may face higher lifecycle maintenance or earlier rehabilitation costs.
- Aircraft operators and insurers — If pavement failures or foreign object debris increase because designs weren’t tailored to aircraft load patterns, operators could face operational disruptions, damage claims, or higher insurance premiums.
Key Issues
The Core Tension
The bill pits cost efficiency and administrative alignment—letting smaller airports rely on State highway practice—against preserving aircraft‑specific pavement standards that are intended to ensure long-term operational safety; the Secretary’s discretionary safety finding is meant to bridge that gap but places the burden of resolving a technical and resource-intensive trade-off on the FAA.
The statute solves a narrow cost-and-capacity problem by permitting substitution of highway specifications, but it leaves significant implementation questions unanswered. The key ambiguity is evidentiary: the bill requires the Secretary to determine that highway specifications "will not negatively affect safety," but it does not state what analytical tests, performance metrics, or documentation the Secretary should rely on.
Will the FAA require full aircraft load equivalency analyses, accelerated pavement testing, or only engineering judgments? The absence of a prescribed standard invites uneven application across States and possible disputes over what counts as a sufficient safety showing.
Another unresolved issue is lifecycle performance and grant compliance. Highway pavement designs are optimized for vehicle axle loads, load repetitions, and maintenance cycles that differ from aircraft operations.
The bill does not address whether projects using highway specifications will carry specific maintenance covenants, accelerated inspection regimes, or differing useful-life assumptions under grant assurances. There are also practical administrative costs: FAA will need guidance, training, and possibly new staff to handle technical reviews and post-construction monitoring, which could offset some of the up-front savings that motivated the change.
Finally, the 60,000‑pound cutoff and the nonprimary limitation create edge cases. Aircraft or operations that hover near the threshold may create planning uncertainty for airports considering mixed-use pavements.
States with permissive highway specs could push for broad adoption, while tighter FAA interpretation could nullify expected savings—creating legal and operational friction between State ambitions and federal safety prerogatives.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.