Laserfiche WebLink
HOUSEL: Thank you. Is there anyone else that -? <br />YEH: Mr. Chairman, one of the things that we submitted recently was a request for continuance <br />on the contested case hearing in light of some anticipated input that was going to be coming from <br />the State Historic Preservation Division. The reason this application was submitted and at least <br />deemed complete now for the Commission to consider was that on January 26, 2010 – and it’s <br />part of the record – there was a letter from SHPD indicating that they had previously reviewed <br />the project and essentially determined that there was a no-significant-effect determination that <br />allowed this project to proceed forward. Since then, as the Commission may be aware, we have <br />received a letter, I think partially in response to the intervenor’s request for another review from <br />the same agency, from State Historic Preservation Division, requesting that an archaeological <br />inventory survey along with a cultural impact assessment be prepared for the Commission’s <br />consideration. To some extent, it’s not really the way these kinds of procedures usually flow, <br />because once you get a no-effect letter, you get to continue forward. At the same time, the <br />applicant is cognizant in trying to be sensitive to some of the concerns that have been raised by <br />SHPD. And so for that reason, what we did is we are still asking for a continuance of the <br />contested case hearing because we believe that in all fairness to all parties, even though we <br />believe that, from an archaeological inventory standpoint or a cultural impact assessment, that <br />the applicant can still move forward with its proposal, nevertheless, we should vet those issues <br />out and then come back to the Commission with that information. <br />Part of the concern, of course, in this is that it will involve some time issues. At the same time <br />having heard some of the responses from members of the public today, I think it might be a good <br />idea for everybody takes some breathing room to consider some of these issues and to the extent <br />that there is some common ground that can be reached with some of the interest that had been <br />expressed that we at least try to do that. And I’m not going to say that necessarily we’ll be able <br />to accomplish that, but at least try to understand some of those issues further. From real practical <br />standpoint, we’ve had some archaeological assessment going on already. It still does not yet <br />appear to be that there are going to be any significant finds that will result in any probation of the <br />development as opposed to data recovery; we’ll find that out once a report’s done. Once our <br />report’s done, which is probably going to take about a two to three-week period, it then gets <br />submitted to SHPD for its review. That’s where we may find some time delays because, as it’s <br />kind of commonly known, SHPD is understaffed for funding purposes. There are some other <br />issues. And typically, there is a 45-day response period once the AIS or archaeological <br />inventory survey is submitted. Whether SHPD is able to come back in that 45-day period is a <br />big question. We would certainly want them to do that as soon as possible and provide their <br />input. Similarly, on the cultural impact assessment side, that kind of study is not really <br />something that SHPD, even though it has requested it from a regulatory standpoint, is generally <br />involved in reviewing, but we do want to be able to provide it that opportunity. Undertaking that <br />study is kind of a complex set of factors that involves review of archival documents, interviews <br />with witnesses, understanding some of the cultural issues that are prevalent in that area, and then <br />putting that together. That itself will probably take more than the archaeological inventory <br />survey itself, and I’m estimating probably good two, three months perhaps on top of what SHPD <br />has asked for. <br />25 <br />EXHIBIT C <br /> <br />