Codify — Article

Bill requires contingency plans for subsidized Essential Air Service contracts

Mandates non-weather disruption contingency plans in EAS applications, changing selection criteria and creating a 180‑day implementation deadline for DOT.

The Brief

The Essential Air Service Reliability Act of 2025 amends 49 U.S.C. 41733(c) to require that any carrier applying for compensated basic Essential Air Service submit a contingency plan addressing how service to the eligible place will continue in the event of a disruption that is not related to weather. The bill also reorganizes subsection numbering and changes a statutory caption to focus on the rate of compensation.

Why it matters: the change forces DOT to evaluate operational resilience when awarding subsidized routes, which can alter bid pricing, carrier selection, and the balance between cost and reliability for small, remote communities that depend on EAS. The law includes a 180‑day applicability trigger for DOT to implement the new requirement and a conforming statutory edit to 49 U.S.C. 41736(c)(2)(A).

At a Glance

What It Does

The bill inserts a statutory requirement that EAS compensation applications include a contingency plan for maintaining service during non‑weather disruptions and renumbers existing paragraphs while renaming a subsection heading to 'Rate of Compensation.' DOT must apply that new requirement within 180 days of enactment.

Who It Affects

Subsidy-seeking EAS carriers and their bidders, the Department of Transportation's EAS selection process, small and remote communities that receive EAS, and airports and contractors that support emergency operations or substitute service.

Why It Matters

By making operational continuity a formal selection consideration, the statute elevates resilience in procurement decisions and may increase awarded contract costs or change which carriers win awards — shifting tradeoffs between price, redundancy, and market participation.

More articles like this one.

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

Unsubscribe anytime.

What This Bill Actually Does

The core change the bill makes is simple on paper: when a carrier files an application to receive federal compensation for providing Essential Air Service, the application must include a contingency plan that explains how service to the eligible community will continue if a disruption occurs that isn’t caused by weather. The text does not define every term of art; it establishes the requirement and leaves the practical definition and enforcement to DOT rulemaking, guidance, or evaluation during the selection process.

The bill also restructures the existing subsection by renumbering paragraphs and swapping the textual lead-in to make operational requirements a distinct paragraph and to relabel another paragraph to emphasize the statutory 'Rate of Compensation.' A separate short provision requires the Department of Transportation to ensure the contingency‑plan requirement applies within 180 days of the law’s enactment and performs a technical, conforming fix to another cross-reference in chapter 41736.Practically, the new mandate forces applicants to move beyond price and schedule in their proposals: carriers will need to describe how they will maintain service when faced with non‑weather events such as mechanical grounding, crew shortages, maintenance backlogs, supply chain interruptions, or the insolvency of a partner operator. DOT reviewers will gain a statutory basis to treat those operational safeguards as part of the selection calculus, which can influence the design of solicitations, evaluation matrices, and contract clauses requiring performance or backup arrangements.

The statute, however, does not prescribe specific contingency elements or penalties — those implementation details will determine how burdensome the new requirement becomes.

The Five Things You Need to Know

1

The bill amends 49 U.S.C. 41733(c) to require that every application for compensated EAS include a contingency plan covering continuation of service for disruptions not caused by weather.

2

Congress directs the Department of Transportation to make the contingency‑plan requirement effective no later than 180 days after the statute is enacted.

3

The amendment restructures subsection 41733(c) by inserting a new paragraph for the contingency requirement, relabeling the selection considerations paragraph, and renaming an existing paragraph header to 'Rate of Compensation.', The statute leaves the content and enforceability of contingency plans unspecified—DOT will have discretion to define acceptable plans and how they affect awards.

4

A conforming edit changes a cross‑reference in 49 U.S.C. 41736(c)(2)(A) to cite the amended subsection 41733(c) rather than a single paragraph, aligning other statutory references with the new structure.

Section-by-Section Breakdown

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

Section 1

Short title

Designates the act as the 'Essential Air Service Reliability Act of 2025.' This is a conventional labeling provision that has no operational effect but identifies the legislation for codification and citation.

Section 2(a)(1) — Application language

Formalizes 'Application' paragraph

Edits the opening of 49 U.S.C. 41733(c)(1) to label the provision 'APPLICATION,' clarifying that the items that follow govern applications for EAS compensation. The change is organizational, making the statute easier to read and signaling that subsequent requirements pertain specifically to applicants.

Section 2(a)(2)(B) — New contingency requirement

Mandatory contingency plan for non‑weather disruptions

Adds a new paragraph requiring each compensated EAS application to include a contingency plan to continue air service to the eligible place in the event of a disruption not related to weather. Because the statute sets the requirement but not its elements, DOT will need to decide what a compliant plan looks like (e.g., substitute aircraft, wet‑lease options, cross‑utilization of crews, interline agreements, or other operational redundancies) and how evaluators weigh plans against price and service factors.

4 more sections
Section 2(a)(2)(C) — Considerations

Selection considerations renamed and retained

Relabels the former 'In selecting an applicant' clause as 'CONSIDERATIONS,' maintaining statutory direction that DOT consider certain factors when choosing an applicant. The renaming is structural but accompanies the insertion of the contingency requirement into the list of matters the Secretary will evaluate.

Section 2(a)(3) — Rate of compensation header

Caption change to 'Rate of Compensation'

Changes the caption for what was paragraph (4) to 'RATE OF COMPENSATION,' a cosmetic statutory edit that may influence how DOT frames subsidy determinations but does not itself alter the substance of how rates are established; practical effects will depend on agency guidance and how the caption informs interpretation.

Section 2(b) — Applicability

180‑day implementation deadline for DOT

Directs the Secretary of Transportation to ensure the new contingency‑plan requirement applies no later than 180 days after enactment. This creates a firm timeline for DOT to issue any necessary guidance, revise application forms, and incorporate contingency evaluations into procurement procedures.

Section 2(c) — Conforming amendment

Fixes a cross‑reference in 49 U.S.C. 41736

Edits 49 U.S.C. 41736(c)(2)(A) to replace a narrow paragraph citation with a reference to the amended subsection 41733(c), ensuring other statutory provisions point to the correct, renumbered text after insertion of the new contingency paragraph.

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

  • EAS communities that depend on air links: They gain a statutory push toward greater operational continuity, which reduces the risk of prolonged service gaps when non‑weather disruptions occur.
  • DOT and EAS program managers: The department gets an explicit statutory tool to evaluate resilience and hold carriers to continuity expectations, strengthening oversight and procurement leverage.
  • Airports and ground service providers in remote communities: Fewer service interruptions reduce revenue volatility for local airports and associated vendors that rely on scheduled flights.
  • Passengers on subsidized routes: Improved contingency planning can mean fewer cancellations, faster substitutions, and better information during disruptions.

Who Bears the Cost

  • Small regional and commuter carriers that bid for EAS routes: They must develop, document, and possibly finance redundancy measures or contractual backup arrangements, which can raise bid prices and administrative burdens.
  • Taxpayers (through higher subsidies): If carriers include redundancy costs in proposals, the subsidy required to sustain service could increase, raising program expenditures.
  • Department of Transportation: DOT will need staff time and possibly new rulemaking and oversight processes to define, evaluate, and enforce contingency plans within the 180‑day window.
  • Contract partners and suppliers: Maintenance providers, leasing firms, and wet‑lease partners may face demand for standby capacity or guaranteed services, shifting commercial risk and pricing.

Key Issues

The Core Tension

The central dilemma is between mandating operational resilience to protect vulnerable communities and preserving low‑cost competition: stronger contingency requirements improve reliability but increase carrier costs and may narrow the field of bidders, while lighter requirements keep costs down but risk leaving communities exposed to longer service interruptions.

The statute creates a meaningful policy lever but leaves key implementation choices to DOT. The law mandates contingency plans without specifying what must be in them or how robust they must be, which forces an implementation phase where DOT will define compliance thresholds.

That gap is consequential: narrow guidance could render the requirement largely paper‑based, while strict standards could eliminate low‑cost bidders and increase subsidy spending. Another implementation challenge is verification and enforcement — DOT will need metrics to judge whether a contingency plan is credible and whether carriers follow through under stress, which may require contract modifications, performance bonds, or liquidated damages provisions that the statute does not authorize explicitly.

The amendment also risks altering competitive dynamics in the EAS market. Carriers with larger fleets, access to wet‑lease markets, or deeper balance sheets can propose stronger redundancy, improving their award chances but potentially excluding smaller operators that currently serve many remote communities.

There is also a timing tension: the 180‑day deadline pressures DOT to produce usable guidance quickly, which can lead to either under‑specified rules or burdensome initial requirements. Finally, the statutory focus on non‑weather disruptions leaves open how DOT should treat mixed‑cause events (e.g., a mechanical issue exacerbated by seasonal weather) and how contingency obligations interact with FAA safety regulations, commercial lease agreements, and bankruptcy risk.

Try it yourself.

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