Laserfiche WebLink
<br />Resolution 2005-040 <br />Page 8 of 61 <br /> <br />As such, the ALUC did not identify any facts to <br />support the premise that this project would <br />result in any interference with the long-range <br />development plans of JWA at either the <br />January 15, 2004 or the March 18, 2004 <br />meetings. <br /> <br />Although the project exceeds the FAR Part 77 <br />obstruction standards, the FAA conducted an <br />Aeronautical.Study of the proposed project and found <br />the project poses no hazard to air navigation. (Exhibit <br />A.) <br /> <br />(1) <br /> <br />d) <br /> <br />(3) <br /> <br />On March 18, 2004, the ALUC reconsidered <br />the conditional approval of this project. Once <br />agein, the staff's recommendation was that the <br />project is consistent with the AELUP, <br />"providing the project complies fully with all <br />conditions required by the FAA," and "provided <br />that a Notice of Airport in Vicinity is provided to <br />all future occupants as specified in JWA <br />AELUP Section 3.3.6." "With all due respect <br />to the Commission and the action it took at its <br />J"nu",ry 15, 2004 meeting to amend the staff <br />recommendation of consistency, staff <br />continues to believe the appropriate <br />recommendation is a finding of consistency <br />with the appropriate FAA conditions relating to <br />lighting and subsequent notice and the state <br />mandated notice of airport in vicinity. . .." <br /> <br />(4) <br /> <br />On March 18, 2004, the ALUC voted to find the <br />project inconsistent with the AELUP. Not only <br />was this finding of inconsistency contrary to <br />staft's recommendation, it was also contrary to <br />ALUC's January 15, 2004 decision that this <br />project was conditionally consistent with the <br />AELUP. The ALUC's March 18,2004 decision <br />was not supported by any findings of facts <br />within the record. <br /> <br />(5) <br /> <br />The FAA Aeronauticai Study considered and <br />analyzed the impact on existing and proposed <br />arriv"l, departure, and en rOMte procedures for <br />aircrqftoperatingunder both visual flight rules <br />(VFR) and instrument flight rules (IFR). <br />