Evolved Expendable Launch Vehicle Program
DRAFT ENVIRONMENTAL IMPACT STATEMENT (DEIS)

Chapter 2 - Alternatives Including the Proposed Action

DRAFT ENVIRONMENTAL IMPACT STATEMENT (DEIS)
FOR THE
EVOLVED EXPENDABLE LAUNCH VEHICLE (EELV) PROGRAM
April 1998

2.1.3 Concept A/B

Under Concept A/B, the contractors would use SLC-41 and SLC-37 at Cape Canaveral AS and SLC-3W and SLC-6 at Vandenberg AFB for the EELV system activities, as well as other facilities at both locations.

2.1.3.1 Launch Vehicle Concept.

Under Concept A/B, the launch vehicle system described in Section 2.1.1.1 for Concept A and that described in Section 2.1.2.1 for Concept B would both be utilized.

2.1.3.2 Primary Support Structures.

Structures described in Sections 2.1.1.2 and 2.1.2.2 for Concept A and B, respectively, would be utilized to support Concept A/B activities. If this concept were to proceed, any conflicts in facility usage between the two contractors would be addressed as the EELV program is further defined.

2.1.3.3 Launch Site Operations.

Launch vehicle components would be delivered to the site, and all operations would be conducted as described in Sections 2.1.1.3 and 2.1.2.3 for Concepts A and B, respectively. Quantities of hazardous materials to be utilized would be the same per launch as shown in Tables 2.1-2 and 2.1-6, respectively, for both Concepts A and B. 2.1.3.4 Safety Systems. Concept A/B would be subject to the same rules and policies described in Sections 2.1.1.4 and 2.1.2.4, respectively, for Concepts A and B.

2.1.3.5 Project Location and Access - Cape Canaveral AS.

As described in Section 2.1.1.5 for Concept A and in Section 2.1.2.5 for Concept B, EELV launch operations would be conducted at SLC-41 and SLC-37 at Cape Canaveral AS.

2.1.3.6 Support Structures/Operations - Cape Canaveral AS.

Launch rates associated with Concept A/B are provided in Table 2.1-11. As described in Section 2.1, each contractor is assumed to launch approximately 50 percent of the combined total of EELV flights. No distinction has been made between government and commercial flights. Full staffing to support EELV program operations would be reached in 2003 for Concept A at 150 personnel and in 2007 for Concept B at 440 personnel.

Under Concept A/B, the projected activities associated with EELV would generate the following average utility demands at Cape Canaveral AS during the projected peak launch year (2015): Based upon employment projections and project activities, Concept A/B would generate an average of 1,900 vehicle trips daily, with 390 trips expected to occur during the peak hour.

2.1.3.7 Project Construction Activities - Cape Canaveral AS.

Construction activities described in Sections 2.1.1.7 and 2.1.2.7 for Concept A and B, respectively, would occur under Concept A/B. No additional construction would be required under this concept.

2.1.3.8 Project Location and Access - Vandenberg AFB.

As described in Section 2.1.1.8 for Concept A and in Section 2.1.2.8 for Concept B, EELV launch operations would be conducted at SLC-3W and SLC-6 at Vandenberg AFB.

2.1.3.9 Support Structures/Operations - Vandenberg AFB.

Launch rates associated with Concept A/B are provided in Table 2.1-11. Full staffing to support EELV operations would be reached in 2006 for Concept A at 135 personnel and in 2007 for Concept B at 300 personnel.

Under Concept A/B, the projected activities associated with EELV would generate the following average utility demands at Vandenberg AFB during the projected peak launch year (2007): Based upon employment projections and project activities, Concept A/B would generate an average of 1,300 vehicle trips daily, with 280 trips expected to occur during the peak hour.

2.1.3.10 Project Construction Activities - Vandenberg AFB.

Construction activities described in Sections 2.1.1.10 and 2.1.2.10 for Concept A and B, respectively, would occur under Concept A/B. No additional construction would be required under this concept.