Air carrier Captain reported there were multiple taxiways that were closed at IAH but not stated on the ATIS and the traffic cones identifying the closures were unlit.

Date: 2025-11 · Aircraft: Commercial Fixed Wing · Phase: taxi

Anomalies: atc-issue-all-types|deviation-discrepancy-procedural-published-material-policy|ground-event-encounter-other-unknown|no-specific-anomaly-occurred-unwanted-situation

Synopsis

Air carrier Captain reported there were multiple taxiways that were closed at IAH but not stated on the ATIS and the traffic cones identifying the closures were unlit.

Narrative

During our preflight briefing; the FO and I specifically discussed the various taxiway closures identified in the NOTAMs; as well as the possibility of the West 2 standard taxi route. I annotated the listed closures on my FliteDeck (FD) Pro Airport Moving Map (AMM) page with closures in red; and the expected taxi route in yellow. Upon initial contact; Ground Control directed us to taxi via the West 2; hold short of NE." We complied with this direction; and taxied at approximately 10 kt. ground speed; awaiting further instructions. Prior to NF; Ground Control instructed us to "follow Aircraft Y to NA." The aircraft was pretty far ahead; but we saw them take a right turn onto a perpendicular taxiway; towards NA. Using the Traffic (TFC) function of the FD Pro AMM page; I determined that an aircraft was turning right from NB onto WB; and communicated to the FO that we should turn there. As we continued to taxi; we identified an aircraft rapidly taxiing on NE; across Runway 8R. As we approached NE; the crossing aircraft was just clearing the runway; and our aircraft to follow was established well down NA. The FO questioned which taxiway we should take. I slowed my taxi and directed him to ask Ground Control.He informed them that Aircraft Y was too far ahead for us to verify which taxiway they used; and asked if we could just continue to taxi on NB. Ground Control responded that NB was closed ahead; and that we should take WB to NA. This closure was neither present in the NOTAMs; nor was it lit in any way; and we do not recall seeing it listed in the ATIS. Upon taxiing onto WB; we finally saw the unlit traffic cones identifying the closure. We continued taxiing down NA; and upon reaching WP; were surprised to learn that WP was also closed; and also identified by unlit traffic cones. We again slowed; realizing that all of the preceding traffic was lined up on the dashed line establishing the 15R run-up pad. We continued taxiing behind these aircraft until reaching WC."

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.