FEMA's Flood Map Revision Notice: What the Record Actually Shows

The cited Federal Register notice, “Changes in Flood Hazard Determinations,” was published at 91 FR 54352 on Aug. 21, 2026, under Docket ID FEMA-2026-0002 and Internal Agency Docket No. FEMA-B-2624. The notice contains listed community entries and states that it does not describe the specific flood-hazard determinations for each community.

This original record-reading guide is a general reading aid, not cited evidence. It does not depict a source record; the article text and source links provide the facts.

Key points

• The record is the Federal Register notice “Changes in Flood Hazard Determinations” at 91 FR 54352, Docket ID FEMA-2026-0002, Internal Agency Docket No. FEMA-B-2624, published Aug. 21, 2026.
• Each listed determination “will be finalized on the dates listed in the table below and revise the FIRM panels and FIS report in effect prior to this determination for the listed communities” (source).
• The current effective community number shown in each row “must be used for all new policies and renewals” (source).
• Any person has “90 days” after the second local newspaper publication to request reconsideration through the community (source).
• The notice states its own scope limit: “the specific flood hazard determinations are not described for each community in this notice” (source).

The record a map revision produces

If a community mentions a LOMR, this Federal Register notice is the dated federal record that revision produces. The notice explains what finalization means for the underlying maps: “These flood hazard determinations will be finalized on the dates listed in the table below and revise the FIRM panels and FIS report in effect prior to this determination for the listed communities” (source). In other words, the table itself — not narrative text elsewhere in the notice — is what fixes the effective date for each community’s revised FIRM panels and Flood Insurance Study (FIS) report.

What each table row must contain

Three identifiers travel together in each community’s row: a case number, a per-community modification (finalization) date, and the current effective community number. The community number carries a specific, binding instruction: “The current effective community number is shown in the table below and must be used for all new policies and renewals” (source). Two example rows from the table: City of Flagstaff, case number 25-09-0680P, finalized Oct. 7, 2026, community number 040020 (source); and City of Phoenix, case number 26-09-0096P, finalized Sep. 25, 2026, community number 040051 (source).

Notice legal basis

The notice grounds its authority in two citations. On the statutory side: “The modifications are made pursuant to section 201 of the Flood Disaster Protection Act of 1973, 42 U.S.C. 4105” (source). On the regulatory side: “The flood hazard determinations are in accordance with 44 CFR 65.4” (source).

The 90-day window to request reconsideration

The notice sets a fixed clock for challenging a listed determination, and it runs from a local publication event rather than from the Federal Register date: “From the date of the second publication of notification of these changes in a newspaper of local circulation, any person has 90 days in which to request through the community that the Assistant Administrator, Federal Insurance Directorate, Resilience reconsider the changes” (source). The request has to go through the community, not directly to FEMA.

What this record does not answer

This notice — and this article — do not say what any specific community’s flood hazard determination actually changed. The notice says so directly: “The specific flood hazard determinations are not described for each community in this notice” (source). That means this record cannot tell a reader whether a specific property floods, whether it sits in a Special Flood Hazard Area, whether flood insurance is needed or advisable for it, or what a flood insurance policy would cost. Anyone looking for that address-level detail needs the community’s own map repository, not this notice. It’s also worth noting that a community can appear more than once in the underlying table, under different case numbers with different dates — Phoenix, for example, has more than one row at community number 040051 — so the case number, not the community name, is what uniquely identifies a given entry; any specific row cited from the table needs its case number alongside it.

Source links

https://www.federalregister.gov/documents/2026/08/21/2026-17072/changes-in-flood-hazard-determinations https://www.govinfo.gov/content/pkg/FR-2026-08-21/html/2026-17072.htm