Notices. Request for public comment

5,812 words·~26 min read·/register/2008/02/25/08-812

A research copy — for the controlling text, always check the official state or federal source. Not legal advice.

BILLING CODE 8120-08-M DEPARTMENT OF TRANSPORTATION Federal Aviation Administration Public Notice for a Change in Use of Aeronautical Property at St. Marys Municipal Airport, St. Marys, PA AGENCY: Federal Aviation Administration (FAA), DOT. ACTION: Request for public comment. SUMMARY: The Federal Aviation Administration is requesting public comment on the City of St. Marys' request to change a portion 129.2 acres of airport property from aeronautical use to non-aeronautical use.

The requested release is for the purpose of permitting the Airport Owner to sell and convey title of 114.8 acres for industrial/commercial use. The parcel is located south and east of the newly constructed airport access road, and east of the existing “old RR Grade”. The property is currently undeveloped but aeronautical use is shown for it on the Airport Layout Plan. The tract currently consists of wooded land with some open fields and is more particularly described below. The airport has also requested release for the purpose of developing a portion of airport property 14.4 acres as non-aeronautical use to generate revenue for the airport.

The property is currently undeveloped but is now shown as aeronautical land use on the Airport Layout Plan. The tract is more particularly described below. Documents reflecting the Sponsor's request are available, by appointment only, for inspection at the Airport Managers office and at the Pennsylvania Department of Transportation, Bureau of Aviation in the Keystone Building, Harrisburg, PA. DATES: Comments must be received on or before March 26, 2008. ADDRESSES: Documents are available for review at the Airport Manager's office:

Joe Bologna, Manager, St Marys Municipal Airport, 119 Airport Rd., P.O. Box 89, St Marys, PA 15857,

(814)834-4671; and at the Pennsylvania Department of Transportation, Bureau of Aviation: Mr. Brian Gearhart, Engineering Manager, PaDOT Bureau of Aviation, 400 North St., Sixth Floor, Harrisburg, PA 17120,

(717)705-1260. FOR FURTHER INFORMATION CONTACT: Mr. Brian Gearhart, Engineering Manager PaDOT Bureau of Aviation at the location listed above. SUPPLEMENTARY INFORMATION: Section 125 of the Wendell H. Ford Aviation and Reform Act for the First Century (AIR-21) requires the FAA to provide an opportunity for public notice and comment before the Secretary may waive a sponsor's Federal obligation to use certain airport land for aeronautical use. *St. Marys Airport Land Release Parcel Description:* The land to be released from airport property and federal obligation is generally described as follows. The property in question consists of a total 114.8 acres located south and east of the newly constructed airport access road, and east of the existing “old RR Grade”. To ease location by the public, the 114.8 acres can be broken into a north and south area. *North Area to be Released:* The north area includes 18.9 acres of property is bounded by the new airport access road to the north, Airport Road to the west, an old railroad grade to the south along with fields now or formerly owned by the Benzinger Township Camp Owners Association, and bounded on the east by the west side of the soccer field to remain airport property under a short-term lease. *South Area to be Released:* The remaining south area to be released is east of the existing “old RR Grade''. It includes the wooded area starting at a point approximately 397 feet nearly due east of an old railroad grade and bounded on the west by the fields now or formerly owned by the Benzinger Township Camp Owners Association for a distance of approximately 4,380 feet. The southern border runs nearly due east for a distance of approximately 809 feet. The eastern border consists of a line running nearly due north through the wooded area for a distance of approximately 1957 feet, the eastern border then turns nearly due east for approximately 792 feet, then continues nearly due north for a distance of approximately 693 feet, then turns nearly due east for a distance of approximately 660 feet, then turns nearly due north for a distance of approximately 628 feet, then turns nearly due west for a distance of approximately 1226 feet in the wooded area adjacent to lands now or formerly owned by Charles Sritz and generally along the south edge of cultivated field now or formerly owned by Marshall V. Wolfe, then turns nearly due north along the west edge of the cultivated field for a distance of approximately 388 feet, then turns nearly due west along the wooded area to the east side of the community soccer field, then turns south along the east side of the community soccer field a distance of approximately 438 feet, then nearly due west along the southern side of the community soccer field a distance of approximately 572 feet to generally the northeast corner of the open fields now or formerly owned by the Benzinger Township Camp Owners Association for an area of 95.9 acres more or less. *St. Marys Airport Land Use Change Request Parcel Description:* In addition, the airport has requested a change in land use of two areas from “aeronautical use” to “non-aeronautical”. The two areas will remain airport property and are generally along the south side of the existing airfield. *Western Portion of the Land Use Change:* Starting at the NE corner of the intersection of Airport Road and the new airport access road, then northerly along Airport Road for a distance of approximately 374 feet, then nearly due east a distance of approximately 1,229 feet to near the west side of the existing tee hangar area, then nearly due south a distance of 374 feet, then westerly along the north side of the new airport access road back to the NE corner of Airport Road and said new airport access road for an area of 10.3 acres more or less. *Eastern Portion of the Land Use Change:* Starting at the NE corner of the intersection of Airport Road and the new airport access road, then easterly along Airport Road for a distance of approximately 2,189 feet to the point of beginning being the northeast corner of the eastern parcel on which the airport is requesting a change in land use. Then nearly due south along the farm fence a distance of 438 feet, then nearly due west a distance of 412 feet, then nearly due north a distance of 438 feet, then nearly due east along what would be the north right of way line of the new airport road if extended, a distance of 410 feet back to the point of beginning. Said area containing 4.1 acres more or less. The parcel was acquired without Federal participation. The requested release is for the purpose of both permitting the Sponsor to sell and convey title, and to develop as non-aeronautical the areas described above. The proceeds from the sale of property are to be used for the capital and operating costs of the airport. Interested persons are invited to comment on the proposed release from obligations. All comments will be considered by the FAA to the extent practicable. Issued in Camp Hill, Pennsylvania, February 19, 2008. Lori K. Pagnanelli, Manager, Harrisburg Airports District Office. [FR Doc. E8-3528 Filed 2-22-08; 8:45 am] BILLING CODE 4910-13-P DEPARTMENT OF TRANSPORTATION Federal Motor Carrier Safety Administration Availability of Commercial Driver's License Information System (CDLIS) Modernization Grant Funds AGENCY: Federal Motor Carrier Safety Administration (FMCSA), DOT. ACTION: Notice. SUMMARY: The Federal Motor Carrier Safety Administration (FMCSA) announces the availability of Commercial Driver's License Information System (CDLIS) modernization grant funding as authorized by Section 4123 of the Safe, Accountable, Flexible, Efficient Transportation Equity Act: A Legacy for Users (SAFETEA-LU). This law included an appropriation of $28 million (FY 2006-2009) towards modernization of CDLIS. The FY 2006 and FY 2007 funding of $5 million and $7 million was awarded to the American Association of Motor Vehicle Administrators for development costs. The FY 2008 funding of $8 million being made available in this notice will be awarded to the States. The program is a discretionary grant program that provides funding for States to upgrade their driver licensing information systems to make them compatible with the new modernized CDLIS specifications. The grant funds under this program may be used for personnel, computer hardware and software, publications, testing, training, and quality control. The grant funds may not be used to rent, lease, or buy land or buildings. The agency in each State designated as the primary driver licensing agency responsible for the development, implementation, and maintenance of the Commercial Driver's License

(CDL)program is eligible to apply for grant funding. The Federal share of the funds is established by SAFETEA-LU as 80 percent. There is a 20 percent matching requirement. The grant period for any grant awarded under this program is effective from the date the agreement is executed until September 30, 2010. Funds are available to any State that is in substantial compliance with the requirements of 49 U.S.C. 31311 and submits a grant proposal that qualifies under the conditions in this notice, including assuming the responsibility of incorporating the new CDLIS specifications and improving its commercial driver licensing system. State grant proposals must include a detailed budget explaining how the funds will be used and how the State will meet the matching requirements. To apply for funding, applicants must register with the grants.gov Web site ( *http://www.grants.gov/applicants/get_registered.jsp* ) and submit an application in accordance with instructions provided. Applications for grant funding must be submitted electronically to the FMCSA through the grants.gov web site. DATES: FMCSA will initially consider funding for applications submitted by April 30, 2008, by qualified applicants. If additional funding remains available, applications submitted after April 30, 2008, will be considered on a case-by-case basis. The grant period is in effect from the date the agreement is executed until September 30, 2010. FOR FURTHER INFORMATION CONTACT: Visit *www.grants.gov.* Information on the grant, application process, and additional contact information is available at that Web site. General information about the CDLIS modernization grant program is available in The Catalog of Federal Domestic Assistance

(CFDA)which can be found on the internet at *http://www.cfda.gov.* The CFDA number for the CDLIS modernization grant program is 20.238. You may also contact Ms. Margaret Jones, Federal Motor Carrier Safety Administration, Office of Safety Programs, CDL Division (MC-ESL), 202-493-0439, 1200 New Jersey Avenue, SE., Suite W65-228, Washington, DC 20590. Office hours are from 8 a.m. to 4:30 p.m., ET, Monday through Friday, except Federal holidays. Issued on: February 15, 2008. William A. Quade, Associate Administrator for Enforcement and Program Delivery. [FR Doc. E8-3413 Filed 2-22-08; 8:45 am] BILLING CODE 4910-EX-P DEPARTMENT OF TRANSPORTATION Federal Transit Administration [Docket No: FTA-2007-0013] National Transit Database: Amendments to Safety & Security Reporting Manual AGENCY: Federal Transit Administration (FTA), DOT. ACTION: Notice of availability of the final 2008 National Transit Database Safety & Security Reporting Manual. SUMMARY: This notice announces the availability of the Federal Transit Administration's

(FTA)*2008 National Transit Database

(NTD)Safety & Security Reporting Manual* . Pursuant to 49 U.S.C. 5335, FTA requires those transit agencies reporting to the NTD from urbanized areas to provide reports within 30 days of a major safety or security incident, and to provide a monthly report on minor safety and security incidents. The *2008 NTD Safety & Security Reporting Manual* details the specific requirements and guidelines for safety and security reporting. On November 21, 2007, FTA published a notice in the **Federal Register** (72 FR 65636) inviting comments on proposed changes to the *2008 NTD Safety & Security Reporting Manual* . This notice provides responses to those comments, and announces the availability of the *2008 NTD Safety & Security Reporting Manual* on the NTD Web site at *http://www.ntdprogram.gov* . DATES: *Effective Date:* February 25, 2008. FOR FURTHER INFORMATION CONTACT: For program issues, John D. Giorgis, Office of Budget and Policy,

(202)366-5430 (telephone);

(202)366-7989 (fax); or *john.giorgis@dot.gov* (e-mail). For legal issues, Richard Wong, Office of the Chief Counsel,

(202)366-0675 (telephone);

(202)366-3809 (fax); or *richard.wong@dot.gov* (e-mail). SUPPLEMENTARY INFORMATION: I. Background The National Transit Database

(NTD)is the Federal Transit Administration's (FTA's) primary database for statistics on the transit industry. Congress established the NTD to “help meet the needs of * * * the public for information on which to base public transportation service planning * * *” (49 U.S.C 5335). Currently, over 650 transit agencies in urbanized areas report to the NTD through an Internet-based reporting system. Since 2002, the NTD has included an expanded Safety & Security Module in order to meet the increased public interest in transit safety and security data. Data from the Safety & Security NTD Module are used by FTA's Office of Safety and Security, the Department of Homeland Security, the National Transportation Safety Board, and in the biennial *United States Department of Transportation Conditions and Performance Report to Congress* . NTD reporters are required to submit a report on major incidents to the Safety & Security Module within 30 days of the incident, and to submit a monthly summary report of minor incidents within 30 days of the end of the month. On November 21, 2007, FTA published a notice in the **Federal Register** (72 FR 65636) inviting comments on proposed changes to the *2008 NTD Safety & Security Manual* . This notice provides responses to those comments, and announces the availability of the *2008 NTD Safety & Security Reporting Manual* on the NTD Web site at *http://www.ntdprogram.gov* . II. Comments and Response to Comments FTA received comments from four respondents on its proposed changes, and responds to the comments in the following order:

(a)Injury Threshold;

(b)Fire Threshold;

(c)Data Continuity;

(d)Acts of God; and

(e)Other Comments.

(a)*Injury Threshold.* All four comments objected to FTA's proposal to simplify the injury threshold for filing an incident report. Previously, the injury threshold for filing an incident report was two or more injuries requiring immediate medical transportation away from the scene, or one or more injuries requiring immediate medical transportation away from the scene in the case of incidents at grade crossings or along rail right-of-ways. FTA proposed simplifying this threshold to being simply one or more injuries requiring immediate medical transportation away from the scene. Three comments objected that this reduced threshold would significantly increase reporting burden for simple slips and falls, of which a transit agency may have dozens during a given month. One comment objected that this reduced threshold would require reporting of an incident, “even if the operator avoids an accident and someone falls out of his or her seat and claims to be hurt * * *,” and cited this as an additional example of the increased reporting burden that would result from this proposal. *FTA Responds:* Based on these comments, FTA agrees to exempt slips, falls, and electric shocks from the reduced injury threshold. Transit agencies will simply report the total number of injuries resulting from slips, falls, and electric shocks to transit customers, workers, and other persons, and the total number of occurrences of these incidents. This is the same as the existing reporting requirements. FTA, however, will proceed with the simplified single-injury threshold for other incidents, including collisions, fires, and security incidents. In particular, a collision will now require an incident report if it results in one or more injuries requiring immediate medical transport away from the scene, regardless of location. FTA notes that the increased reporting burden of this requirement is offset somewhat by raising the property damage threshold from $7,500 to $25,000, which is the threshold used by FTA's State Safety Oversight Program. In the case where “an operator avoids an accident and someone falls out of his or her seat and claims to be hurt * * *,” FTA will update the *2008 NTD Safety & Security Reporting Manual* to reflect that such injuries may be classified as a “fall.” Thus, such an incident would not require filing an incident report. FTA also notes that injuries are not reported to the NTD on the basis of passenger claims of injury; an injury is only reported to the NTD when it results in immediate medical transportation away from the scene.

(b)*Fire Threshold.* Two comments objected to FTA's proposal to require an incident report for all fires requiring suppression on the basis that this would be a significant increase in reporting burden. *FTA Responds:* Based on these comments, FTA drops its proposal to require an incident report for all fires requiring suppression. Rather, FTA will require an incident report only for those fires that meet the established threshold criteria of: • One or more fatalities; • One or more injuries requiring immediate medical transportation away from the scene; • Property damage greater than or equal to $25,000; or • An evacuation for life safety reasons. For fires that require suppression, but which do not meet one of the established threshold criteria, transit agencies will simply report a summary total each month for each of four location categories. These four categories are:

(1)In transit vehicles;

(2)in revenue facilities;

(3)in non-revenue facilities; and,

(4)on right-of-way. This is similar to the existing reporting requirements, except for the increased property damage threshold and the lower injury threshold.

(c)*Data Continuity.* Two comments objected to FTA's proposal on the grounds that it would create discontinuous safety and security data for transit. Three areas of discontinuity were cited in the comments:

(1)Data for injuries;

(2)data for fatalities; and,

(3)data for major incidents. Additionally, one comment expressed concern that FTA's proposal would cause transit to appear less safe. *FTA Responds:* FTA notes that while it is changing the injury threshold for filing an incident report, it is not changing the definition of an injury. Summary totals have previously been collected for injuries and incidents that did not require transit agencies to file a major incident report. As such, this proposal will not impact the continuity of data on total transit injuries. FTA also notes that while it will be including suicides in the definition of fatalities, it has previously collected data on all fatalities, including suicides. As such, FTA will take great care to ensure that it always uses continuous data series in reporting transit fatalities. FTA will also continue to make available detailed transit fatality data, which will allow data users to exclude suicides from their analysis of transit fatalities. FTA does note that these changes will cause some difficulty in assembling continuous data on the total number of major transit incidents. Based on previously filed major incident reports, however, FTA does hope to assemble a continuous data series from 2002—present on major transit incidents. To the extent that discontinuous data series on major transit incidents do result from these changes, FTA believes that the negative impacts of discontinuity are more than offset by the benefits to transit agencies of reduced reporting requirements. The reduced reporting requirements will apply to incidents that produce no fatalities and injuries, and between the old threshold of $7,500 in property damage and the new threshold of $25,000 in property damage.

(d)*Acts of God.* Two comments requested additional clarification of FTA's proposal to add “Acts of God” as a reportable incident. One comment asked how FTA's proposal for “Acts of God” would relate to various legal definitions for this term. *FTA Responds:* This proposal originated from the experiences of some transit agencies in filing NTD Safety & Security reports. Some agencies have notified NTD staff that they have suffered property damage in excess of the reporting threshold as a result of a severe storm or flood, but have been unable to complete an incident report for this occurrence, as the NTD did not account for such “Acts of God.” As such, FTA is adding this category to allow transit agencies to account for the impacts of “Acts of God” on transit facilities. FTA will make clear in the *2008 NTD Safety & Security Reporting Manual* that it is not FTA's intent to require transit agencies to assess such “Acts of God” as potential contributing factors to a collision.

(e)*Other Comments.* One comment expressed concern about the reporting burden of adding accidents involving non-revenue vehicles and adding hazardous material spills as reportable incidents. One comment expressed concern about FTA collecting information on “light in the eyes” in regard to collisions, and asked if this referred only to sunlight or also to headlights. *FTA Responds:* FTA notes that existing reporting requirements already require an incident report for collisions involving non-revenue vehicles when those collisions exceed the reporting threshold. This is unchanged. FTA also notes that existing reporting requirements required reporting hazardous material spills when such spills resulted in an evacuation for life safety reasons. FTA's proposal only slightly modifies this by requiring a report whenever a hazardous material spill causes “imminent danger to life, health, or the environment, and had special attention given at the time of the incident.” FTA does not believe that clarification of the definition will cause a significant increase in reporting burden from the previous definition. FTA will clarify in the *2008 NTD Safety & Security Reporting Manual* and in the reporting system itself that the question of “light in the eyes” refers to sunlight. Two comments expressed concern about the short lead time between the public notice-and-comment on FTA's proposal and the scheduled implementation of the proposal. *FTA responds:* FTA recognizes the concern of transit agencies to have ample time to review proposed changes to the NTD data collection. FTA will ensure that more lead time is given for public notice-and-comment for future amendments to the *NTD Safety & Security Reporting Manual* , and will allow more time for a collaborative development process with the transit industry. In order to support implementation of the *2008 NTD Safety & Security Reporting Manual* , FTA has scheduled six training sessions around the country to assist transit agencies in implementing the new requirements. Technical assistance is also available to transit agencies at any time through their NTD data validation analyst. The final *2008 NTD Safety & Security Reporting Manual* is available on the NTD Web site at *http://www.ntdprogram.gov* . Issued in Washington, DC, this 20th day of February 2008. James S. Simpson, Administrator. [FR Doc. E8-3517 Filed 2-22-08; 8:45 am] BILLING CODE 4910-57-P DEPARTMENT OF TRANSPORTATION Federal Transit Administration Supplemental Draft Environmental Impact Statement for the Central Corridor Light Rail Transit Project, Located in Minneapolis and Saint Paul, MN AGENCY: Federal Transit Administration (FTA), Department of Transportation (DOT). ACTION: Notice of Intent to prepare a Supplemental Draft Environmental Impact Statement (SDEIS). SUMMARY: The Federal Transit Administration

(FTA)in cooperation with the Metropolitan Council is issuing this notice to advise interested agencies and the public of its intent to prepare a Supplemental Draft Environmental Impact Statement (SDEIS) for the proposed Central Corridor Light Rail Transit

(LRT)Project, located in Minneapolis and Saint Paul, Minnesota (the “Project”). The SDEIS will be prepared in accordance with the National Environmental Policy Act

(NEPA)as well as provisions of the Safe, Accountable, Flexible, Efficient Transportation Equity Act: A Legacy for Users (SAFETEA-LU). The SDEIS will evaluate potential changes to the Central Corridor LRT Project since the publication of the April 21, 2006 Alternatives Analysis/Draft Environmental Impact Statement (AA/DEIS) and disclose new information that is being developed during the preliminary engineering process. FOR FURTHER INFORMATION CONTACT: Ms. Marisol Simon, Regional Administrator, Federal Transit Administration (FTA), Region V, 200 West Adams Street, Suite 320, Chicago, Illinois 60606, Telephone:

(312)353-2789. DATES: Written comments on the proposed action should be sent to Ms. Kathryn L. O'Brien, AICP, Project Manager, Central Corridor Project Office, 540 Fairview Ave. North, Suite 200S, Saint Paul, MN 55104, Telephone: 651-602-1927; E-mail: *kathryn.obrien@metc.state.mn.us* and Mr. David Werner at FTA, Region V, 200 West Adams Street, Suite 320, Chicago, Illinois 60606, Telephone:

(312)353-2789; E-mail: *David.Werner@dot.gov* by March 26, 2008. SUPPLEMENTARY INFORMATION: *Background:* The Metropolitan Council is proposing transportation improvements in the Central Corridor linking Minneapolis and Saint Paul. The Central Corridor is 11-miles in length of which 9.8 miles consists of new alignment and 1.2 miles uses the existing Hiawatha LRT alignment in downtown Minneapolis. It will connect the Minneapolis and Saint Paul downtown areas as well as the University of Minnesota and the State Capitol complex. The purpose of the Project is to meet the future transit needs of the Central Corridor and the Region and to support the economic development goals for the Corridor. It allows the opportunity to provide a direct connection to the existing 11.6-mile Hiawatha LRT line in Minneapolis, thereby increasing mobility options within the Region. The AA/DEIS Notice of Intent was published in the **Federal Register** on June 5, 2001 and the notice of the availability of the AA/DEIS for review and comment was published in the **Federal Register** on April 21, 2006. In April 2006, the Central Corridor AA/DEIS was distributed for public review and comment (No. 20060147, ERP No. D-FTA-F40434-MN). The AA/DEIS provided a comprehensive examination of alignments, LRT and Busway/Bus Rapid Transit

(BRT)technologies, and a Baseline Alternative for the Central Corridor. Based on findings from the AA/DEIS and on public and agency input received during the process, the Metropolitan Council adopted a Locally Preferred Alternative

(LPA)for the Central Corridor, namely Light Rail Transit, operating on Washington and University Avenues, on June 28, 2006 (Metropolitan Council Resolution No. 2006-15). *Proposed Changes to the LPA:* A supplemental DEIS is being prepared because key changes to the LPA as previously defined are being considered. In response to comments received on the AA/DEIS and the Project subsequent to the selection of the LPA, several design options for key project elements are being considered. These options reflect conditions that exist within the Corridor, technical and operational constraints, major infrastructure requirements that were not fully documented in the AA/DEIS, physical conditions that have changed within the corridor since the AA/DEIS, and substantive comments received during the AA/DEIS public comment period. The SDEIS will document and disclose potential impacts relating to key project elements that have changed and/or remain uncertain since issuance of the AA/DEIS, including but not limited to: 1. Hiawatha/Central Connection: Alternative alignments connecting to the existing Hiawatha LRT tracks will be evaluated. 2. University of Minnesota Alignment (tunnel vs. at-grade and stations): The LPA included a tunnel, primarily under Washington Avenue, as the preferred alignment alternative through the University of Minnesota campus. The SDEIS will examine the impacts of an at-grade alignment alternative through the East Bank of the University of Minnesota campus and modifications to the tunnel alignment, as well as an alignment change through this segment of the line, largely due to the new University of Minnesota stadium presently under construction on the LPA alignment. 3. Potential Additional Station at Hamline, Victoria or Western: The impact of adding a station to the Central Corridor LRT project at Hamline, Victoria or Western avenues in the City of Saint Paul will be evaluated. 4. Capitol Area Alignment/Stations: Potential changes to the alignment and location of stations within Saint Paul's Capitol Area Architectural and Planning Board area will be documented and disclosed. 5. Downtown Saint Paul alignment/station modifications: Alternative means of accessing Saint Paul's Union Depot, including potential impacts to LRT station location and alignment will be documented and disclosed. 6. Traction power substations: The AA/DEIS discussed the need for traction power substations as part of LRT operations, but did not identify the number or potential location(s) of substations. The SDEIS will document and disclose this information. 7. 3-car train requirement: The impacts of potential 3-car train operations on the Central Corridor will be evaluated. 8. Vehicle maintenance facility: The need for and impacts of constructing a storage and maintenance facility to serve the operational needs of the Central Corridor LRT project will be documented and disclosed. 9. Washington Avenue Bridge: The need for and impacts of modifications and/or improvements required to the Washington Avenue Bridge for LRT purposes will be documented and disclosed. 10. Other key project elements determined through the on-going decision-making process to have potential significant impacts to human and natural environments. *The SDEIS Process and the Role of Participating Agencies and the Public:* The SDEIS will assist the Metropolitan Council, FTA, resource agencies, key project partners and the general public in understanding and resolving key project elements within the context of NEPA. The purpose of the SDEIS process is to explore in a public setting potentially significant effects of implementing proposed changes to the LPA on the physical, human, and natural environment. Areas of investigation include, but are not limited to, land use, historic and archaeological resources, visual and aesthetic qualities, traffic and parking, modification to existing bridges, noise and vibration, environmental justice, regulatory floodway/floodplain encroachments, coordination with transportation and economic development projects, and construction impacts. Other issues to be addressed in the SDEIS include: Natural areas, ecosystems, rare, threatened and endangered species, water resources, air/surface water and groundwater quality, energy, potentially contaminated sites, displacements and relocations, Section 4(f) of the Department of Transportation Act and Section 6(f) of the Land and Water Conservation Fund Act and secondary and cumulative effects. The SDEIS is not intended to repeat all the analyses contained in the project's AA/DEIS. Most analyses would be limited to the study area corresponding to key project elements currently identified and outlined above, as well as other project elements that have yet to be identified and may arise during the current decision-making process. Potential impacts will be evaluated for both the short-term construction period and the long-term effects of operations. Measures to avoid, minimize, or mitigate any significant adverse impacts will be identified. Notices regarding the intent to prepare the SDEIS and soliciting input will be sent to the appropriate Federal, State, and local agencies that have expressed or are known to have an interest or legal role in this proposed action. A comprehensive public involvement program has been developed to engage private organizations, citizens, and interest groups in the process. The program includes an active Community Advisory Committee (CAC), a Business Advisory Council (BAC), a Central Corridor Management Committee

(CCMC)and a Project Advisory Committee (PAC). A Central Corridor project Web site has been created and can be found at: *http://www.metrocouncil.org/transportation/ccorridor/centralcorridor.htm.* Community outreach coordinators are available to work with residents, businesses and interested individuals along the entirety of the corridor at: *http://www.metrocouncil.org/transportation/ccorridor/CCstaff.htm.* Notices of public meetings have been and will continue to be given through a variety of media providing the time and place of the meeting along with other relevant information. When complete, the SDEIS will be distributed and available for public and agency review and comment prior to any public hearings. Following publication, review, and approval of the SDEIS, a Final Environmental Impact Statement

(FEIS)will be prepared and circulated. The FEIS will identify a final preferred alternative and any necessary mitigation commitments. In accordance with 23 CFR 771.105

(a)and 771.133, the Metropolitan Council and FTA will comply with all Federal environmental laws, regulations, and executive orders applicable to the proposed project during the environmental review process to the maximum extent practicable. These requirements include, but are not limited to, the regulations of the Council on Environmental Quality and FTA regulations implementing NEPA (40 CFR Parts 1500-1508, and 23 CFR Part 771), the project-level air quality conformity regulation of the U.S. Environmental Protection Agency

(EPA)(40 CFR part 93), the Section 404(b)(1) guidelines of EPA (40 CFR Part 230), the regulation implementing Section 106 of the National Historic Preservation Act (36 CFR Part 800), the regulation implementing Section 7 of the Endangered Species Act (50 CFR Part 402), Section 4(f) of the DOT Act (23 CFR Section 771.135), and Executive Orders 12898 on Environmental Justice, 11988 on Floodplain Management, and 11990 on Wetlands. Comments and questions concerning the proposed action should be directed to Ms. Kathryn L. O'Brien, AICP, Project Manager, Central Corridor Project Office, 540 Fairview Ave. North, Suite 200S, Saint Paul, MN 55104, Telephone: 651-602-1927; E-mail: *kathryn.obrien@metc.state.mn.us* Dated: February 13, 2008. Marisol Simon, Regional Administrator, FTA Region V. [FR Doc. E8-3525 Filed 2-22-08; 8:45 am] BILLING CODE 4910-57-P DEPARTMENT OF TRANSPORTATION Pipeline and Hazardous Materials Safety Administration Office of Hazardous Materials Safety; Notice of Application for Special Permits AGENCY: Pipeline and Hazardous Materials Safety Administration (PHMSA), DOT. ACTION: List of Applications for Special Permits. SUMMARY: In accordance with the procedures governing the application for, and the processing of, special permits from the Department of Transportation's Hazardous Material Regulations (49 CFR Part 107, Subpart B), notice is hereby given that the Office of Hazardous Materials Safety has received the application described herein. Each mode of transportation for which a particular special permit is requested is indicated by a number in the “Nature of Application” portion of the table below as follows: 1—Motor vehicle, 2—Rail freight, 3—Cargo vessel, 4—Cargo aircraft only, 5—Passenger-carrying aircraft. DATES: Comments must be received on or before March 26, 2008. *Address Comments to:* Record Center, Pipeline and Hazardous Materials Safety Administration, U.S. Department of Transportation, Washington, DC 20590. Comments should refer to the application number and be submitted in triplicate. If confirmation of receipt of comments is desired, include a self-addressed stamped postcard showing the special permit number. FOR FURTHER INFORMATION CONTACT: Copies of the applications are available for inspection in the Records Center, East Building, PHH-30, 1200 New Jersey Avenue, SE., Washington, DC, or at *http://dms.dot.gov.* This notice of receipt of applications for special permit is published in accordance with Part 107 of the Federal hazardous materials transportation law (49 U.S.C. 5117(b); 49 CFR 1.53(b)). Issued in Washington, DC, on February 14, 2008. Delmer F. Billings, Director, Office of Hazardous Materials, Special Permits and Approvals. Application No. Docket No. Applicant Regulation(s) affected Nature of special permits thereof New Special Permits 14640-N Chem Service, Inc. Chester Count, PA 49 CFR 173.4(a)(11) To authorize the transportation in commerce of certain PG I hazardous materials that are not authorized for transportation aboard passenger-carrying aircraft under the small quantity provisions of 49 CFR 173.4. (modes 4, 5) 14641-N Conocophillips Alaska, Inc., Anchorage, AK 49 CFR 172.101 Hazardous Materials Table Column

(9B)To authorize the transportation in commerce by air of certain hazardous materials in packagings that exceed the quantity limit for cargo carrying aircraft. (mode 4) 14642-N MEMC Pasadena, Inc., Pasadena, TX 49 CFR 173.301(f) To authorize the transportation in commerce of certain DOT Specification 3AAX cylinders containing Silicon tetrafluoride without pressure relief devices. (mode 1) 14643-N World Airways, Inc., Peachtree City, GA 49 CFR 175.3(b) To authorize the transportation in commerce of hazardous materials by a US carrier engaged in cargo-only operations entirely outside of the United States without being subject to the US variations in the ICAO Technical Instructions. (mode 4) 14644-N El Aero Services, Inc., Elko, NV 49 CFR 172.101 HMT Column (9B), 172.200, 172.300, 172.400 To authorize the transportation in commerce of certain hazardous materials by cargo aircraft only in remote areas of the US without being subject to hazard communication requirements and quantity limitations. (mode 4) [FR Doc. 08-812 Filed 2-2-08; 8:45am]

Connectionstraces to 4

Traces to 4 documents

U.S. Code

CFR