Flood zone X: what a development-site screen still needs

A note that says only “flood zone X” leaves a development team with an incomplete record. Check the map's legend or full hazard subtype, identify the part of the proposed site you inspected, and keep the source product's status with the observation. A Zone X label does not establish that a housing project can be built.

This guide covers the evidence an acquisitions analyst can prepare before further review. It includes two actual FEMA service records that show why the subtype matters, plus a manual flood-map worksheet. The records demonstrate a data distinction; they are not an assessment of a development site.

Keep the detail behind the X label

FEMA's National Flood Insurance Program distinguishes shaded and unshaded Zone X. The letter alone does not preserve that distinction. The same guidance explains that areas outside high-risk zones still have flood risk.

When a map or export reports X, save the legend or full subtype description that accompanies it. If the source only supplies the letter, leave the subtype unresolved and identify the source needed to check it. Do not replace missing information with “no flood risk.”

An actual service extract makes the problem visible. On October 30, 2026, Pillar retrieved one record for each of two deliberately selected subtypes from FEMA's National Flood Hazard Layer, Flood Hazard Zones service:

FLD_AR_ID: 19089C_6083
FLD_ZONE: X
ZONE_SUBTY: AREA OF MINIMAL FLOOD HAZARD
SFHA_TF: F
SOURCE_CIT: 19089C_STUDY1

FLD_AR_ID: 28109C_3
FLD_ZONE: X
ZONE_SUBTY: 0.2 PCT ANNUAL CHANCE FLOOD HAZARD
SFHA_TF: F
SOURCE_CIT: 28109C_STUDY1

Keeping only FLD_ZONE would turn both observations into “X.” Keeping SFHA_TF as well would still leave these two records indistinguishable on those fields. The full ZONE_SUBTY values preserve the difference in the source.

Download the two-record CSV and retrieval notes to inspect the original field values and repeat the bounded queries. These are selected examples, not a representative sample or a count of how often either subtype occurs. Each query returned one record and reported that more matching records existed. No geometry was returned and no parcel overlay or spatial filter was performed. We did not inspect the associated map panels or determine conditions at either location. The retrieval date is not the map's effective date.

Identify the area you actually checked

A point used to locate a property and the boundary of a proposed development answer different questions. Start with the parcel identity and location check, then record the footprint used in the flood-map review.

For an assemblage, list the parcel IDs separately. Also identify the concept layout or project boundary, if one exists, with its revision date. Keep the area searched or displayed separate from the area you have actually examined.

In the worksheet, describe how you compared those boundaries with the flood information. For example, “checked the address pin” records a much narrower observation than “reviewed the boundaries of parcels A and B against the saved map.” Record omitted portions and uncertain matches. An observation at a pin should not silently become a conclusion about every proposed lot or its access route.

The two-record extract above cannot perform this step: it contains attributes without geometry and was not queried for a proposed site. Use it to understand the fields, then obtain and review the appropriate source for the property you are considering.

Preserve the map product and its status

FEMA's Map Service Center training distinguishes effective, preliminary and historic map and study products. Save the product title, panel or study reference, date and stated status you actually reviewed. Record the date you checked it separately.

If another version is available, keep it as another observation with its own status. Document which product supports the current note and which questions a different version raises. A newer-looking file should not silently replace the source behind an earlier decision.

Preserve raw references such as SOURCE_CIT when working with an export. The strings in our sample are not a completed panel lookup or a verified effective date. Put unresolved source details on the follow-up list rather than inferring them from an identifier.

Hand over a question the reviewer can answer

Attach the source capture and boundary record to the worksheet. Name the proposed use and the decision the next review is intended to support. Keep observed map information separate from design assumptions and unanswered questions.

Useful follow-up might ask a reviewer to reconcile the applicable flood products with the current concept boundary, identify missing elevation information, or confirm the requirements relevant to the proposal. Assign an owner and a date for the response. Save the answer with its scope when it arrives.

If the review involves elevations, use the separate NGVD 29 and NAVD 88 comparison guide to prepare the source labels before anyone compares numbers. This article does not supply an elevation conversion, design standard, development permission or insurance determination.

Return the resulting evidence and open questions to the desktop site-screening record. The next person should be able to see the map observation, the part of the site it covers, and what still needs an answer.