Federal Register / Vol. 69, No. 201 / Tuesday, October 19, 2004 / Notices 61549

Issued in Des Plaines, Illinois on October 

8, 2004. 

Philip M. Smithmeyer, 

Manager, Chicago Airports Districts Office, 

FAA, Great Lakes Region.

[FR Doc. 04–23382 Filed 10–18–04; 8:45 am] 

BILLING CODE 4910–13–M

DEPARTMENT OF TRANSPORTATION

Federal Aviation Administration 

Notice of Intent To Rule on Application 

04–16–C–00–CHO To Impose and Use 

the Revenue From a Passenger Facility 

Charge (PFC) at CharlottesvilleAlbemarle Airport, Charlottesville, VA

AGENCY: Federal Aviation 

Administration (FAA), DOT.

ACTION: Notice of intent to rule on 

application. 

SUMMARY: The FAA proposes to rule and 

invites public comment on the 

application to impose and use the 

revenue from a PFC at CharlottesvilleAlbemarle Airport (CHO) under the 

provisions of the 49 U.S.C. 40117 and 

part 158 of the Federal Aviation 

Regulations (14 CFR part 158).

DATES: Comments must be received on 

or before November 18, 2004.

ADDRESSES: Comments on this 

application may be mailed or delivered 

in triplicate to the FAA at the following 

address: Washington Airports District 

Office, 23723 Air Freight Lane, Suite 

210, Dulles, Virginia 20166. 

In addition, one copy of any 

comments submitted to the FAA must 

be mailed or delivered to Mr. Bryan O. 

Elliott, Executive Director, 

Charlottesville-Albemarle Airport of the 

Charlottesville-Albemarle Airport 

Authority at the following address: 

Charlottesville-Albemarle Airport 

Authority, Charlottesville-Albemarle 

Airport, 201 Bowen Loop Road, Suite 

200, Charlottesville, Virginia 24012–

1148. 

Air carriers and foreign air carriers 

may submit copies of written comments 

previously provided to the public 

agency full name under § 158.23 of part 

158.

FOR FURTHER INFORMATION CONTACT: Mr. 

Terry J. Page, Manager, Washington 

Airports District Office, 23723 Air 

Freight Lane, Suite 210, Dulles, Virginia 

20166, Telephone: (703) 661–1354. 

The application may be reviewed in 

person at this same location.

SUPPLEMENTARY INFORMATION: The FAA 

proposes to rule and invites public 

comment on the application to impose 

and use the revenue from a PFC at 

Charlottesville-Albemarle Airport under 

the provisions of the 49 U.S.C. 40117 

and part 158 of the Federal Aviation 

Regulations (14 CFR part 158). 

On October 12, 2004, the FAA 

determined that the application to 

impose and use the revenue from a PFC 

submitted by Charlottesville-Albemarle 

Airport Authority was substantially 

complete within the requirements of 

§ 158.25 of part 158. The FAA will 

approve or disapprove the application, 

in whole or in part, no later than 

December 22, 2004.

The following is a brief overview of 

the application. 

Proposed charge effective date:

August 1, 2007. 

Proposed charge expiration date:

August 1, 2015. 

Level of the proposed PFC: $4.50. 

Total estimated PFC revenue:

$5,499,286. 

Brief description of proposed 

projects(s): Air Carrier Debt Service; 

Rehabilitate and Expand General 

Aviation parking Apron; Rehabilitate 

Air Carrier Apron; Project 

Administration Fees. 

Level of the proposed PFC: $4.50. 

Class or classes of air carriers which 

the public agency has requested not be 

required to collect PFCs: Air Tax/

Commercial Operators (ATCO) required 

to file FAA form 1800–31. 

Any person may inspect the 

application in person at the FAA office 

listed above under FOR FURTHER

INFORMATION CONTACT and at the FAA 

regional Airports office located at: 

Federal Aviation Administration, 

Eastern Region, 1 Aviation Plaza, 

Jamaica, New York 11434–4809. 

In addition, any person may, upon 

request, inspect the application, notice 

and other documents germane to the 

application in person at the 

Charlottesville-Albemarle Airport 

Authority.

Issued in Dulles, Virginia on October 12, 

2004. 

Terry J. Page, 

Manager, Washington Airports District Office, 

Eastern Region.

[FR Doc. 04–23385 Filed 10–18–04; 8:45 am] 

BILLING CODE 4910–13–M

DEPARTMENT OF TRANSPORTATION

Federal Aviation Administration 

Notice of Intent to Rule on Application 

04–07–C–00–JNU to Impose and Use 

the Revenue From a Passenger Facility 

Charge (PFC) at Juneau International 

Airport, Juneau, Alaska

AGENCY: Federal Aviation 

Administration (FAA), DOT.

ACTION: Notice of intent to rule on 

application. 

SUMMARY: The FAA proposes to rule and 

invites public comment on the 

application to impose and use the 

revenue from a PFC at Juneau 

International Airport under the 

provisions of the 49 U.S.C. 40117 and 

Part 158 of the Federal Aviation 

Regulations (14 CFR Part 158).

DATES: Comments must be received on 

or before November 18, 2004.

ADDRESSES: Comments on this 

application may be mailed or delivered 

in triplicate to the FAA at the following 

address: Byron K. Huffman, Manager, 

Alaskan Region Airports Division, 222 

West 7th Avenue, Box 14, Anchorage, 

AK 99513. In addition, one copy of any 

comments submitted to the FAA must 

be mailed or delivered to Mr. Allan A. 

Heese, Airport Manager, of the Juneau 

International Airport at the following 

address: Juneau International Airport, 

1873 Shell Simmons Drive, Juneau, AK 

99801. 

Air carriers and foreign air carriers 

may submit copies of written comments 

previously provided to the Juneau 

International Airport under section 

158.23 of Part 158.

FOR FURTHER INFORMATION CONTACT:

James Lomen, Programming Specialist, 

Alaskan Region Airports Division, AAL610, 222 W 7th Avenue, Box 14, 

Anchorage, AK 99513, (907) 271–5816. 

The application may be reviewed in 

person at this same location.

SUPPLEMENTARY INFORMATION: The FAA 

proposes to rule and invites public 

comment on the application to impose 

and use the revenue from a PFC at 

Juneau International Airport under the 

provisions of the 49 U.S.C. 40117 and 

Part 158 of the Federal Aviation 

Regulations (14 CFR Part 158). 

On October 5, 2004, the FAA 

determined that the application to 

impose and use the revenue from a PFC 

submitted by the City and Borough of 

Juneau, Juneau International Airport, 

Juneau, Alaska was substantially 

complete within the requirements of 

§158.25 of Part 158. The FAA will 

approve or disapprove the application, 

in whole or in part, no later than 

January 5, 2005. 

The following is a brief overview of 

the application. 

Proposed charge effective date:

January 1, 2005. 

Proposed charge expiration date:

November 30, 2009. 

Level of proposed PFC: $4.50. 

Total estimated PFC revenue:

$4,706,313. 

Brief description of proposed projects:

61550 Federal Register / Vol. 69, No. 201 / Tuesday, October 19, 2004 / Notices 

Projects To Impose and Use: Airport 

Improvement Program matching funds 

for: Equipment purchase AIP-35 (Snow 

Brooms, Skidsteer, Command Vehicle, 

Chemical Truck); Departure Area 

Security Improvements (AIP-36); 

Security Upgrades and Equipment 

Phase 2 (AIP-38); Rehabiliate Airport 

Main Entrance Road; Expand Terminal 

Building—Feasibility Study/Planning; 

Construct Taxiway Extensions C1, W2; 

Acquire Airside Vehicles & Equipment; 

Construct Delta-1 Ramp Expansion; 

Acquire Security Vehicle, and 

Rehabilitate West GA Area Paving. Full 

project funding for: Purchase of snow 

removal support vehicle (unit 4) and 

Purchase Land for Airport Expansion. 

Impose-Only Project: Wildlife Hazard 

Management Plan Implementation, 

Phase 1. 

Class or classes of air carriers which 

the public agency has requested not be 

required to collect PFCs: None. 

Any person may inspect the 

application in person at the FAA office 

listed above under FOR FURTHER

INFORMATION CONTACT and at the FAA 

regional Airports office located at: 222 

W 7th Avenue, Anchorage, AK. 

In addition, any person may, upon 

request, inspect the application, notice 

and other documents germane to the 

application in person at Juneau 

International Airport, 1873 Shell 

Simmons Drive, Juneau, AK.

Issued in Anchorage, Alaska, on October 6, 

2004. 

Byron K. Huffman, 

Manager, Airports Division, Alaskan Region.

[FR Doc. 04–23383 Filed 10–18–04; 8:45 am] 

BILLING CODE 4910–13–M

DEPARTMENT OF TRANSPORTATION

Federal Railroad Administration 

[Docket No. FRA–2000–7257; Notice No. 33] 

Railroad Safety Advisory Committee 

(RSAC); Working Group Activity 

Update

AGENCY: Federal Railroad 

Administration (FRA), Department of 

Transportation (DOT).

ACTION: Announcement of Railroad 

Safety Advisory Committee (RSAC) 

Working Group Activities. 

SUMMARY: The FRA is updating its 

announcement of RSAC’s working 

group activities to reflect its current 

status. For additional details on 

completed activities see prior working 

group activity notices (68 FR 25677).

FOR FURTHER INFORMATION CONTACT:

Patricia Butera, RSAC Coordinator, 

FRA, 1120 Vermont Avenue, NW., 

Mailstop 25, Washington, DC 20590, 

(202) 493–6212 or Grady Cothen, Acting 

Associate Administrator for Safety, 

FRA, 1120 Vermont Avenue, NW., 

Mailstop 25, Washington, DC 20590, 

(202) 493–6302.

SUPPLEMENTARY INFORMATION: This 

notice serves to update FRA’s last 

announcement of working group 

activities and status reports of May 3, 

2004, (69 FR 24219). The 24th full 

Committee meeting was held September 

22, 2004. 

Since its first meeting in April of 

1996, the RSAC has accepted eighteen 

tasks. Status for each of the tasks is 

provided below: 

Open Tasks 

Task 96–4—Reviewing the 

appropriateness of the agency’s current 

policy regarding the applicability of 

existing and proposed regulations to 

tourist, excursion, scenic, and historic 

railroads. This Task was accepted on 

April 2, 1996, and a Working Group was 

established. The Working Group 

monitored the steam locomotive 

regulations task. Planned future 

activities involve the review of other 

regulations for possible adaptation to 

the safety needs of tourist and historic 

railroads. Contact: Grady Cothen (202) 

493–6302. 

Task 97–1—Developing 

crashworthiness specifications to 

promote the integrity of the locomotive 

cab in accidents resulting from 

collisions. This Task was accepted on 

June 24, 1997. On April 14, 2004, RSAC 

reached consensus on the Notice of 

Proposed Rulemaking (NPRM). The 

NPRM is pending review within the 

Executive Branch. The NPRM is a new 

standard to increase the 

crashworthiness of conventional wideand narrow-nose locomotives and 

codifies requirements for monocoque 

locomotives. Contact: Charles Bielitz 

(202) 493–6314. 

Task 97–2—Evaluating the extent to 

which environmental, sanitary, and 

other working conditions in locomotive 

cabs affect the crew’s health and the safe 

operation of locomotives, proposing 

standards where appropriate. This Task 

was accepted June 24, 1997. 

(Sanitation) (Completed) 

(Noise exposure) On June 27, 2003, 

the full RSAC gave consensus by ballot 

on the NPRM. The NPRM was 

published in the Federal Register on 

June 23, 2004. The comment period 

ended September 21, 2004. The FRA is 

reviewing the comments. 

(Cab Temperature) (Completed)

Note: Additional related topics such as 

vibration may be considered by the Working 

Group in the future. Contact: Jeffrey Horn 

(202) 493–6283.

Task 97–3—Developing event 

recorder data survivability standards. 

This Task was accepted on June 24, 

1997. On November 12, 2003, the RSAC 

gave consensus by ballot on the NPRM. 

The NPRM was published on June 30, 

2004. A public hearing was held 

September 30, and the comment period 

was extended until October 11. Contact: 

Edward Pritchard (202) 493–6247. 

Task 97–4 and Task 97–5—Defining 

Positive Train Control (PTC) 

functionalities, describing available 

technologies, evaluating costs and 

benefits of potential systems, and 

considering implementation 

opportunities and challenges, including 

demonstration and deployment. 

Task 97–6—Revising various 

regulations to address the safety 

implications of processor-based signal 

and train control technologies, 

including communications-based 

operating systems. These three tasks 

were accepted on September 30, 1997, 

and assigned to a single Working Group. 

(Report to the Administrator) A Data 

and Implementation Task Force, formed 

to address issues such as assessment of 

costs and benefits and technical 

readiness, completed a report on the 

future of PTC systems. The report was 

accepted as RSAC’s Report to the 

Administrator at the September 8, 1999, 

meeting. The FRA enclosed the report 

with a letter to Congress signed May 17, 

2000.

(Regulatory development) The 

Standards Task Force, formed to 

develop PTC standards, assisted in 

developing draft recommendations for 

performance-based standards for 

processor-based signal and train control 

systems. The NPRM was approved by 

consensus at the full RSAC meeting 

held on September 14, 2000. The NPRM 

was published in the Federal Register

on August 10, 2001. A meeting of the 

Working Group was held December 4–

6, 2001, in San Antonio, Texas, to 

formulate recommendations for 

resolution of issues raised in the public 

comments. Agreement was reached on 

most issues raised in the comments. A 

meeting was held May 14–15, 2002, in 

Colorado Springs, Colorado, at which 

the Working Group approved creation of 

teams to further explore the ‘‘base case’’

issue. Briefing of the full RSAC on the 

‘‘base case’’ issue was completed on 

May 29, 2002, and consultations 

continued within the working group. 

The full Working Group met October 

22–23, 2002, and again March 4–6, 

2003. Resolution of the remaining issues 

was considered by the Working Group