Grand Canyon plans to partially reopen North Rim after last year’s devastating Dragon Bravo Fire
Parts of the Grand Canyon's North Rim closed due to safety concerns related to the Dragon Bravo Fire last year. They could reopen in May.
Watch: Mondays with Meghan: Why does Katie Hobbs not want to debate? | 15 mins
PHOENIX – Grand Canyon National Park officials announced tentative plans Wednesday to reopen popular North Rim points of interest later this year following last year’s devastating Dragon Bravo Fire.
Last year, the Dragon Bravo Fire burned about 145,000 acres. It burned for over two months, making history as the seventh‑largest wildfire in Arizona.
While the North Kaibab Trail and Arizona Trail are usually open to visitors year-round, they are subject to closures due to ice, snow and fire-related damage.
Due to public safety concerns, the National Park Service shut down parts of the Arizona Trail, as well as the entire North Kaibab Trail, a 14-mile path that runs from the canyon’s North Rim to the Colorado River.
However, park officials announced Wednesday that they’re planning a flexible, step‑by‑step approach to reopening the North Rim. They’re aiming to reopen these routes by May 15.
It depends on weather conditions, and they’re still evaluating trail conditions and infrastructure, according to Ed Keable, superintendent of Grand Canyon National Park.
“Our goal is to provide access to the North Rim as quickly and responsibly as possible with an emphasis on safety,” Keable said in the announcement. “We are committed to keeping the public and our partners informed as we learn more about the impacts of winter weather and the Dragon Bravo Fire.”
Park officials said they’ll explain their reopening plans no later than April 1.
Details about Dragon Bravo Fire
Lightning sparked the Dragon Bravo Fire on July 4.
It burned for months, eventually consuming 145,504 acres. It was 100% contained on Sept. 28.
The fire destroyed over 70 structures on the North Rim, including the historic Grand Canyon Lodge.






Comments
0 Comments