12.03.2014 Views

F-22 Plus-Up Environmental Assessment - Joint Base Elmendorf ...

F-22 Plus-Up Environmental Assessment - Joint Base Elmendorf ...

F-22 Plus-Up Environmental Assessment - Joint Base Elmendorf ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

F-<strong>22</strong> <strong>Plus</strong>-<strong>Up</strong> <strong>Environmental</strong> <strong>Assessment</strong><br />

4.0 <strong>Environmental</strong> Consequences<br />

use. None of the training activities within Alaskan SUA would be expected to result in any<br />

changes to airspace management from those existing for the F-<strong>22</strong> training. The mitigations in<br />

the 1995 MOA EIS ROD still apply (Air Force 1995). During studies conducted as part of the<br />

MOA EIS, it was found that dissemination of information is an important element in explaining<br />

airspace management and use.<br />

Alaska residents, including Alaska Natives, have expressed concerns that military aircraft<br />

training could potentially conflict with small aircraft serving communities under special use<br />

airspace. Enhanced F-<strong>22</strong> electronics and situational awareness reduce risks of conflicts with<br />

general aviation. Existing awareness and avoidance procedures implemented by the Air Force,<br />

and standard FAA flight rules are designed to prevent airspace conflicts. These FAA rules<br />

require that all pilots are responsible to apply “see and avoid” techniques when operating an<br />

aircraft. To reduce the potential for airspace conflicts, JBER continues to schedule MFEs in<br />

training airspace to avoid the high recreation period from the 27 th of June to the 11 th of July.<br />

MFEs are also not scheduled during January, September, or December.<br />

4.1.3 No Action<br />

Existing terminal airspace, MOA, range, and other airspace usage would not change with the<br />

No Action. F-<strong>22</strong>s would continue to train from JBER-<strong>Elmendorf</strong> and continue to train in the<br />

airspace as they do today.<br />

4.2 Noise<br />

This section describes noise impacts associated with the proposed F-<strong>22</strong> plus-up in the area near<br />

JBER-<strong>Elmendorf</strong> and in military training airspace units. Impacts are assessed by comparing<br />

noise conditions under the Proposed Action and the No Action Alternative to baseline<br />

conditions.<br />

4.2.1 <strong>Base</strong> <strong>Environmental</strong> Consequences<br />

Noise levels near JBER-<strong>Elmendorf</strong> were calculated using the<br />

established and tested noise program, NOISEMAP. Under the<br />

Proposed Action, all operational procedures currently in effect,<br />

including noise-related operational restrictions, runway usage<br />

patterns, and approach and departure procedures, would remain<br />

in effect. These procedures include use of Runway 34<br />

(northbound crosswind runway) for approximately 25 percent of<br />

The increase of F-<strong>22</strong> aircraft with the<br />

plus-up results in 16.7 percent more<br />

F-<strong>22</strong>s being based at JBER-<br />

<strong>Elmendorf</strong>. The additional personnel<br />

capability at JBER-<strong>Elmendorf</strong> would<br />

be expected to proportionately<br />

increase the F-<strong>22</strong> sorties.<br />

F-<strong>22</strong> departures. The runway typically used for F-<strong>22</strong> arrivals is runway 06 (eastbound main<br />

runway). To represent F-<strong>22</strong> operations under the Proposed Action for the purposes of noise<br />

modeling, current F-<strong>22</strong> aircraft operations were increased by the proportion of additional F-<strong>22</strong><br />

plus-up aircraft. This would result in an average of approximately five additional daily F-<strong>22</strong><br />

sorties.<br />

Page 4-2

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!