What is changing on October 19?
DOT’s September 3 final rule, 91 FR 56588–56593 amends 14 CFR § 234.4, which governs how reporting carriers code causes of delays and cancellations. It will create a separate “Section 511(b)” category for ten specifically defined events that must not be coded as “Air Carrier” causes. The DOT document page summarizes that purpose. The rule is scheduled to take effect October 19, 2026; it is not yet in effect as of this note’s October 4 verification.
Each listed event has its own conditions. For example, the cybersecurity item requires compliance with applicable cybersecurity rules, and the unscheduled-maintenance item concerns work that cannot be deferred or must be addressed before flight. The full ten-item list and exact wording are in the official final rule.
Three questions, three source paths
1 · Cause reporting
How will the disruption be coded?
Use the Part 234 final rule. It changes the public reporting category for ten qualified causes. A cause code describes reporting; by itself it does not establish whether a changed ticket must be refunded.
2 · Disruption help
What meals, hotel, rebooking, or other help may be offered?
Check the airline’s current customer-service plan and DOT’s cancellation and delay dashboard. Some commitments depend on whether the cause is within the airline’s control. In the final rule, DOT expects the total amenities and noncash compensation supplied under those commitments to fall for some events, but says it cannot reliably estimate the size of the reduction. A particular airline response still depends on its published commitments and the event facts.
3 · Ticket-price refund
Can a traveler decline the changed trip and receive the eligible fare back?
Use the separate Part 260 definitions and § 260.6 refund conditions. For covered U.S. travel, those provisions address a canceled or significantly delayed or changed flight and what the passenger does with an offered alternative. The October 2026 final rule amends Part 234 reporting; its published amendment does not change the Part 260 significance definition or refund conditions. A refund returns the eligible ticket price; it is a different question from meals, hotels, or an extra inconvenience payment.
How to use this source map
For an airline-initiated change, retain the original itinerary, the replacement offer, the airline’s stated reason, and whether any option was accepted or flown. Compare the itinerary against Part 260 for the refund question. Check the airline’s current customer-service plan for disruption assistance. Do not treat a Part 234 cause label or an airline amenity promise as a shortcut for the other question.
Our earlier refund-versus-compensation note explains a separate, withdrawn proposal for additional federal disruption compensation. The October 2026 cause-reporting final rule is a different action.
Method and limits
We compared the September 3 final rule’s summary, preamble and amendatory text with current 14 CFR §§ 260.2 and 260.6 and the DOT dashboard on October 4, 2026. The note addresses U.S. rules for covered flights and the reporting carriers subject to Part 234. It does not review every airline plan, count affected flights, estimate how many travelers will lose an amenity, or decide whether a specific event fits one of the ten defined categories. DOT says the size of the expected amenity reduction cannot be reliably estimated. Sources, interpretations, and airline commitments should be rechecked after October 19.
This is independent educational information, not legal advice or a promise of a refund, rebooking, meal, hotel, or other payment. See our research methodology and corrections process.