The DOT Date Is Feb. 1, 2027. Oct. 19 Moved.

The date on the old card is not the date in the register. This site’s September 17 note treated October 19, 2026 as the day ten delay causes would leave the airline’s column. The Federal Register notice published October 15 delays that effective date to February 1, 2027. If you are standing at a gate this week with a printout that says October 19, you are arguing from a date the department already moved.

The notice is one page. Document 2026-21058, 91 FR 65456, Docket No. DOT-OST-2026-1257. The summary sentence is the one to keep: the Department of Transportation is delaying the effective date of its September 3, 2026 final rule, “Cause of Airline Delay and Cancellation Categories under Section 511(b) of the FAA Reauthorization Act of 2024,” until February 1, 2027. The dates line repeats it. The effective date of the final rule published September 3, 2026, at 91 FR 56588, is delayed until February 1, 2027.

That is a reporting-calendar change. It is not a new right to a hotel, and it is not a repeal of every voucher you have ever been handed. The practical mess is that three clocks now sit on the same rule, and only one of them is the register.

February 1 is the rule. January 1 is the flights.

The September 3 rule had an effective date of October 19, 2026. The October 15 notice says so in the supplementary text, then moves it. The rule amends the Bureau of Transportation Statistics reporting regulation at 14 CFR 234.4. Reporting carriers file the causes of reportable cancellations and delays within 15 days of the end of the month being reported.

On September 21, 2026, Airlines for America asked the department to push the effective date to February 1, 2027, so the new categories would start for flights beginning January 1, 2027. A4A’s reasons, as the notice records them, are operational. The department still had to update the BTS technical reporting directive. Carriers and other industry systems needed time to collect, report, and ingest the new codes. BTS needed time to update its own systems. A4A also called a new calendar year the “natural and logical” date to start applying the updated categories.

The department agreed, and it agreed to the specific shape of that request. The delayed effective date of February 1, 2027 applies to the reporting of delays and cancellations of flights occurring on or after January 1, 2027. Airlines must file their reports for the entire month of January 2027 in a manner that reflects the new causal categories.

Read that twice before you put it in a group chat. A delay on January 15, 2027 is a flight in the new set. The report that describes it is filed within 15 days after January ends, which is after February 1. A delay on December 20, 2026 is not in that set. February 1 is not “the first morning the gate agent uses a new script.” It is the date the reporting requirement, as delayed, takes effect, and the notice ties that requirement to flights from January 1 onward.

MundoNow’s October 17 recap compresses this into two sentences: new reports will include flights from January 1, 2027, and February marks the start of the information requirement. Both halves are in the neighborhood of the register. Neither half is the register. If you need the sentence for a complaint, use the Federal Register wording, not the recap.

The notice also says the September rule required revisions to a BTS information collection, OMB Control No. 2138-0041, and OMB approval of those revisions. The delay, the department writes, gives it more time to get that approval under the Paperwork Reduction Act. That is a paperwork sentence. It is not a promise that every airline’s app will flip a switch on February 1.

Contacts printed on the notice, if you are the person who actually writes letters: Robert Nazareth at the Bureau of Transportation Statistics, 202-934-2413, and Blane Workie at the Office of Aviation Consumer Protection, 202-366-9342. The docket is DOT-OST-2026-1257. FederalRegister.gov labels itself an unofficial XML rendition. The PDF it points to is on govinfo.gov, document 2026-21058 in the October 15, 2026 daily.

The subhead drops the year. The sidebar drops a different date.

USA Today’s October 17 story gets the register right in the body. The rule that was set for October 19 is now delayed to February 1, 2027, according to the October 15 Federal Register. The subhead on the same page stops earlier: travelers now have until February 1 before it takes effect. No year.

February 1 without a year is how a screenshot lies. If someone texts you that line in November 2026, it can be read as three months away or as fifteen months away, and only one of those readings matches the notice. Use the body, or use the register. Do not use the subhead as the date you plan a trip around.

The federalregister.gov page has a second trap, and it is on the document itself. In the details block I read, an “Effective Date” field still shows 2026-09-03. The dates text on the same page says the September 3 rule’s effective date is delayed until February 1, 2027. Those are not two effective dates for the delay. September 3, 2026 is the publication date of the rule being delayed. If a travel blog, or a tired version of me, copies the sidebar field into a caption, the caption will say the delay notice became effective in September. It did not. The operative dates sentence is the one under DATES.

AFAR’s October 15 piece does not make that mistake. Harriet Baskas writes that the change is now scheduled for February 1, 2027, and that it was originally set for October 19, 2026. She also records why the trade group asked: time for the Bureau of Transportation Statistics and industry stakeholders to update technical systems and reporting protocols. That matches the register’s account of the A4A request. AFAR says “till February.” The register says February 1, 2027. Same month. The day is in the notice, not in the paraphrase.

Ten events, and item 10 is not the same sentence everywhere

The register’s delay notice does not reprint the ten events. It says the September rule mandated that ten specific types of events be excluded from the BTS “Air Carrier” causal code, and that a new reporting category would capture those ten. The air carrier code is reserved for circumstances within the carrier’s control. The list itself is in the September rule and in this week’s explainers. I am using AFAR’s October 15 list, and I am marking the one line that does not match a second recap.

AFAR’s ten:

1. Aircraft cleaning necessitated by the death of a passenger.
2. Aircraft damage caused by extreme weather, foreign-object debris, or sabotage.
3. A baggage or cargo loading delay caused by an outage of a bag system not controlled by a carrier or its contractor.
4. Cybersecurity attacks, provided the carrier is following applicable cybersecurity regulations.
5. A shutdown or system failure of government systems that directly affects the ability to conduct flights safely, and is unexpected.
6. Overheated brakes due to a safety incident that led to emergency procedures.
7. Unscheduled maintenance, including work required by an airworthiness directive, that comes up outside a scheduled program and cannot be deferred, or must be fixed before flight.
8. A medical emergency that was not the carrier’s fault.
9. Removal of an unruly passenger.
10. An airport closure due to volcanic ash, wind, or wind shear.

MundoNow’s list, posted October 17 and sourced to USA Today, is the same skeleton with looser wording. Item 1 becomes “cleaning after a passenger’s death.” Item 10 becomes an airport closure due to volcanic ash, wind, or turbulence. Wind shear and turbulence are not interchangeable words if you are asking an agent which code they used. I am not going to average them into “bad air.” If the code on your delay matters, ask for the category name, not a headline’s synonym.

USA Today’s extract names the practical ones without numbering all ten. Disruptions caused by maintenance, crew scheduling, or aircraft cleaning are currently categorized as within a carrier’s control. Starting February 1, 2027, the ten events will be excluded. Erika Josefsson of AirHelp, quoted there, expects the biggest impact from the exclusion of unscheduled maintenance, because that is a common cause of delays. The same story says the rule also clarifies that unruly passengers and government shutdowns are not controllable by the airline. Government shutdowns are Josefsson’s phrasing in that piece. AFAR’s item 5 is a shutdown or system failure of government systems that affects safe operations and is unexpected. I am not folding those into one bullet.

The September post on this site described the October 19 version of the same project, from earlier coverage, as a list that included weather damage, foreign object debris, an unruly passenger, medical emergencies, certain system outages, unscheduled maintenance, and cybersecurity attacks. That older paraphrase is not wrong as a sketch. It is not the list to carry in your pocket after October 15. AFAR’s numbered ten is the list I would screenshot. The register is the document I would cite for the date.

A reporting code is not a voucher statute

This is the sentence the headlines keep sliding past. The notice is about how carriers report causes to BTS, and about a code that is reserved for circumstances within the carrier’s control. Meal vouchers and hotel rooms, in current U.S. practice, are mostly promises in airline customer-service plans, and those plans often fire only when the airline calls the disruption its own.

AFAR quotes the department’s own expectation from the underlying rule: “the total value of amenities and compensation currently provided by air carriers to consumers will be reduced.” That expectation is why the date matters to a passenger, even though the notice itself is a reporting delay. If the code that used to say “air carrier” now says “one of the ten,” a plan that keys off “within our control” can stop offering the hotel. The notice does not, in the text I read, order airlines to stop offering hotels. It changes the category the report uses. The plans follow the category. Those are two steps. People write them as one.

Josefsson told USA Today that the categorization affects what assistance you might be entitled to under the airline’s policies: hotels, meals, and transportation back and forth from the airport on a long delay or a cancellation. She told AFAR, in a separate quote, that travelers should not assume a delay that seems like the airline’s fault will be treated that way under the new rule. Mark Dombroff, an aviation attorney at Fox Rothschild, told AFAR the rule “recognizes and acknowledges that airlines should not be penalized when they occur.” He represents airlines. Josefsson works at a firm that pursues compensation claims. Both quotes are useful. Neither quote is the register.

MundoNow says refunds for cancellations remain protected, and it describes a significant-delay refund if you decide not to travel: an expected arrival at least three hours later on a domestic itinerary, or six hours later on an international one. I did not find that refund threshold in the October 15 delay notice. I am not going to promote MundoNow’s FAQ into a sentence from 91 FR 65456. If you need a refund rule, look up the refund rule. If you need the reporting-date change, you are already on the right document.

The United States still does not have a statute, in any of these pieces, that says a three-hour delay automatically buys you a sandwich. The September post on this site said the same thing about the October 19 version. The delay to February does not create the sandwich. It postpones the narrower coding that makes the sandwich less likely.

A canceled return that nobody mentioned is a different failure mode, and it still happens on weeks when no rule is changing. The checkpoint rewrite is the other half of the airport, not this half. Do not file a DOT delay-code complaint because a water bottle slowed you down, and do not skip the written cause code because you are mad about security.

What to do with the three dates

Before January 1, 2027, the old coding is what the register still has in force. If a November or December delay is coded as the airline’s problem, the customer-service plan you already know is the plan to quote. Do not tell the agent the rule “already changed on October 19.” It did not. Do not tell the agent it “does not change until February, so nothing in January counts.” Flights from January 1 are in the set the notice describes, even though the effective date printed on the delay is February 1.

In the terminal, ask for the cause in writing. MundoNow’s practical close is the one worth keeping: request the reason in writing, keep messages and receipts, and ask what the company will cover before you pay for the hotel yourself. That advice does not depend on which of the ten boxes the night falls into. A text that says “mechanical, hotel approved” is worth more than a correct memory of item 7.

If they refuse, write down the words they used. “Unscheduled maintenance,” “aircraft damage,” “unruly passenger,” and “weather” are different rows on AFAR’s list, and only some of them were treated as the airline’s problem under the coding this site described in September. You cannot audit a shrug. You can audit a category name.

Compare the promise to the airline’s own customer-service plan, not to a TikTok of the Federal Register. The plan is what Josefsson is pointing at when she says policies. The register is what tells you when the reported category is supposed to change. If the plan says a controllable overnight delay gets a hotel, and the agent says this overnight delay is now one of the ten, ask them to name the ten. If they cannot name it, you are not yet in a legal argument. You are in a training argument, and a supervisor is the next desk, not a blog.

One more clock, because someone will mix it in. European compensation under the reformed passenger-rights regulation is a different statute, with different hour thresholds and a three-night hotel cap in the Kennedys write-up I set aside. A U.S. domestic ticket delayed in Charlotte is not an EU261 claim because you read a February date. Keep the regimes apart. The September post already walked the U.S. history. This one only moves the date, and it only moves the date the register moved.

If you fly in January 2027, assume the report filed in February will use the new ten, and assume a meal or a hotel still depends on the plan plus the code, not on the fact that you suffered. Pack the snack. Ask for the category. Keep the screenshot of February 1, 2027, not the screenshot that stopped at February 1.