The FLIGHT Act inserts a new section into 49 U.S.C. chapter 423 that requires covered air carriers to notify passengers when a domestic or international flight experiences a delayed departure or taxi delay of 15 minutes or more. Notifications must be sent by email or text at least once every 15 minutes until the delay ends, include updated estimated departure and arrival times, and offer an opt‑out mechanism specific to that flight.
The bill matters because it converts real‑time operational data into a statutory passenger right. Airlines will need operational and communications systems that deliver repeated, timely updates and manage opt‑outs; regulators and compliance teams will have to decide how to handle enforcement, data accuracy, and situations where passenger contact information is missing or unreliable.
At a Glance
What It Does
Creates 49 U.S.C. §42309 requiring covered air carriers to send email or text notifications to each passenger when a domestic or international flight has a delayed departure or taxi delay of 15 minutes or more. Notifications must occur at least every 15 minutes and include updated estimated departure and arrival times plus a per‑flight opt‑out.
Who It Affects
Applies to 'covered air carriers' under the existing definition in §42307, so major and many regional airlines must update passenger contact capture, messaging platforms, and ground‑operations procedures. DOT rulewriters, airline compliance teams, and airport ground staff will need to coordinate data feeds and notification logic.
Why It Matters
This bill turns frequent operational updates into a legal obligation, potentially raising costs for carriers and shifting expectations for passenger communications. It also creates practical gaps—like enforcement, international data‑sharing, and handling of passengers without contact info—that agencies and carriers will have to resolve.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The FLIGHT Act adds a single, discrete statutory requirement to chapter 423: when a covered air carrier’s flight is delayed on the ground—either a delayed departure or a taxi delay—by 15 minutes or more, the carrier must notify every passenger on the flight. The statute ties the notification trigger and cadence to 15‑minute increments: once the trigger is met, messages must continue at least every 15 minutes until the delay ends.
The bill narrowly prescribes delivery channels (email or text) and message content: carriers must provide updated estimated departure and arrival times where applicable, and they must include a mechanism that lets the passenger opt out of further notifications for that specific flight. The statute applies to both domestic and international operations, and it relies on the existing statutory definition of “covered air carrier” in §42307 rather than crafting a new coverage rule.Mechanically, the requirement forces carriers to connect operational sources of truth (dispatch, ATC updates, gate information) to passenger contact databases and messaging systems so that repeated messages can be generated without manual intervention.
It also creates an operational dependency on having accurate passenger contact details at the time the delay begins; the text does not describe fallback procedures if contact information is missing or invalid.Notably, the text sets the notification obligations but does not include an express civil penalty provision, timetable for regulatory implementation, or detailed privacy safeguards for message content and delivery. That leaves enforcement pathways and technical standards—such as whether SMS consent rules or cross‑border messaging costs influence compliance—to be determined by DOT guidance or subsequent rulemaking.
The Five Things You Need to Know
The bill inserts a new 49 U.S.C. §42309 that triggers when a delayed departure or taxi delay reaches 15 minutes for domestic or international flights.
Once triggered, carriers must send notifications to each passenger at least once every 15 minutes until the delay ends.
Notifications must be delivered by email or text; the statute does not authorize voice calls or airport announcements as substitutes.
Each notification must include updated estimated departure and arrival times (as relevant) and must provide a per‑flight opt‑out mechanism for the passenger.
Coverage is defined by reference to §42307’s definition of a 'covered air carrier'; the bill also makes a clerical amendment to chapter 423’s table of contents.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Short title — 'FLIGHT Act'
This short section gives the Act its name, the Frequent Logistics Information for Grounded and Held Travelers Act (FLIGHT Act). It is a caption only and has no operational effect on duties or enforcement.
Trigger: 15‑minute delay requirement
Adds a new subsection establishing the core duty: when a flight operated by a covered air carrier experiences a delayed departure or taxi delay of 15 minutes or more, the carrier must notify each passenger. The phrase 'domestic or international flight' means the obligation applies to both categories, but the text relies on existing definitions (e.g., 'covered air carrier') to determine which operators are subject.
Cadence: updates at least every 15 minutes
Specifies the minimum frequency of notifications: once every 15 minutes until the delay concludes. That cadence is precise and binding as written, requiring carriers to generate repeated messages during prolonged ground holds; the provision does not create a minimum number of messages before a resolution or allow longer intervals.
Delivery and content requirements, and opt‑out
Requires delivery by email or text message specifically, and requires messages to include updated estimated departure and arrival times as applicable. It also mandates that messages contain a mechanism to let passengers opt out of receiving further notifications for that flight. The statute does not elaborate on opt‑out mechanics (e.g., one‑click, keyword reply) or retention of the opt‑out preference beyond the flight.
Clerical amendment to chapter listing
Updates the chapter 423 table of contents to list the new §42309. This is a non‑substantive, organizational change that makes the new statutory duty discoverable in the U.S. Code's chapter index.
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
- Passengers on delayed flights — They receive frequent, automated updates with new estimated departure/arrival times, reducing uncertainty during ground holds and allowing travelers to make informed decisions about connections, ground transportation, or rebooking.
- Consumer advocates and regulators — The statute codifies a baseline expectation of timely communications, giving advocates and DOT clearer statutory language to rely on when assessing airline practices.
- Frequent business travelers — Regular travelers who provide reliable contact information will get near real‑time status and can adjust itineraries faster, potentially reducing missed connections and associated costs.
Who Bears the Cost
- Airlines (especially regional carriers) — Must integrate real‑time operational feeds with passenger contact databases and messaging systems to automate 15‑minute updates, incurring engineering, messaging, and operational expenses.
- Airline IT and operations teams — Face new implementation and testing demands to ensure notifications reflect accurate ETAs and to prevent message storms or duplicate sends during complex disruptions.
- Carriers and messaging vendors — May face increased SMS costs and consent management burdens, particularly for international flights where cross‑border messaging rates and opt‑in rules vary.
Key Issues
The Core Tension
The central dilemma is fidelity versus feasibility: the bill seeks to guarantee frequent, real‑time transparency to passengers by mandating 15‑minute updates, but that guarantee forces carriers to bear technical, financial, and legal burdens—especially in cross‑border contexts and where passenger contact data are incomplete—while risking information overload that could make messages less useful.
The statute prescribes a fixed cadence and two delivery channels but leaves many implementation details unspecified. It does not set standards for data accuracy (how ETAs are calculated), nor does it state who enforces the requirement or what penalties apply for noncompliance.
That gap means DOT would likely need to issue guidance or a rule to define enforcement mechanisms, acceptable opt‑out designs, and acceptable fallbacks when passenger contact information is missing. International flights raise additional complications: cross‑border SMS costs, local telecommunication consent regimes, and differing time‑of‑day conventions could all affect practical compliance.
Operationally, carriers will need to avoid unintended consequences of high‑frequency messaging—spam‑like behavior, message backlog during network outages, or incorrect ETAs that erode trust. The per‑flight opt‑out protects passengers who prefer fewer messages, but the statute does not say whether opting out affects core operational notices (e.g., gate changes) or how carriers must verify that opt‑outs apply only to that flight.
Finally, privacy and consent laws (including TCPA for texts) intersect with this requirement: carriers must ensure that delivering mandated messages does not violate existing communications statutes or require prior passenger consent beyond what the bill contemplates.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.