Federal Register / Vol. 65, No. 102 / Thursday, May 25, 2000 / Notices 33869

If questions arise concerning the

precise relationship of specific

properties to noise exposure contours

depicted on a noise exposure map

submitted under section 103 of the Act,

it should be noted that the FAA is not

involved in any way in determining the

relative locations of specific properties

with regard to the depicted noise

contours, or in interpreting the noise

exposure maps to resolve questions

concerning, for example, which

properties should be covered by the

provisions of Title 49. These functions

are inseparable from the ultimate land

use control and planning

responsibilities of local government.

These local responsibilities are not

changed in any way under Part 150 or

through FAA’s review of detailed

overlaying of noise exposure contours

onto the map depicting properties on

the surface rests exclusively with the

airport operator which submitted those

maps, or with those public agencies and

planning agencies with which

consultation is required under Title 49.

The FAA has relied on the certification

by the airport operator, under § 150.21

of FAR Part 150, that the statutorily

required consultation has been

accomplished.

The FAA has formally received noise

compatibility program for AustinBergstrom International Airport, also

effective on May 8, 2000. Preliminary

review of the submitted material

indicates that it conforms to the

requirements for the submittal of noise

compatibility programs, but that further

review will be necessary prior to

approval or disapproval of the program.

The formal review period, limited by

law to a maximum of 180 days, will be

completed on or before November 8,

2000.

The FAA’s detailed evaluation will be

conducted under the provisions of 14

CFR Part 150, section 150.33. The

primary considerations in the

evaluation process are whether the

proposed measures may reduce the level

of aviation safety, create an undue

burden on interstate or foreign

commerce, or be reasonably consistent

with obtaining the goal of reducing

existing noncompatible land uses and

preventing the introduction of

additional noncompatible land uses.

Interested persons are invited to

comment on the proposed program with

specific reference to these factors. All

comments, other than those properly

addressed to local land use authorities,

will be considered by the FAA to the

extent practicable. Copies of the noise

exposure map, the FAA’s evaluation of

the map, and the proposed noise

compatibility program are available for

examination at the following locations:

Federal Aviation Administration,

Airports Division, 2601 Meacham

Boulevard, Fort Worth, Texas 76137

Austin-Bergstrom International Airport,

City of Austin, Aviation Department,

3600 Presidential Blvd., Austin, Texas

78719

Questions may be directed to the

individual named above under the

heading, FOR FURTHER INFORMATION

CONTACT.

Issued in Fort Worth, Texas, May 9, 2000.

Joseph G. Washington,

Acting Manager, Airports Division.

[FR Doc. 00–13181 Filed 5–24–00; 8:45 am]

BILLING CODE 4910–13–M

DEPARTMENT OF TRANSPORTATION

Federal Aviation Administration

Notice of Intent to Rule on Application

To Impose and Use the Revenue From

a Passenger Facility Charge (PFC) at

Fayetteville Regional Airport,

Fayetteville, North Carolina

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 Fayetteville

Regional Airport under the provisions of

the Aviation Safety and Capacity

Expansion Act of 1990 (Title IX of the

Omnibus Budget Reconciliation Act of

1990) (Public Law 101–508) and Part

158 of the Federal Aviation Regulations

(14 CFR Part 158).

DATES: Comments must be received on

or before June 26, 2000.

ADDRESSES: Comments on this

application may be mailed or delivered

in triplicate to the FAA at the following

address: Atlanta Airports District Office,

1701 Columbia Avenue, Suite 2–260,

College Park, GA 30337–2747.

In addition, one copy of any

comments submitted to the FAA must

be mailed or delivered to Mr. Bradley S.

Whited, Airport Director, of the City of

Fayetteville at the following address:

Mr. Bradley S. Whited, Airport Director,

Fayetteville Regional Airport, P.O. Box

64218, Fayetteville, NC 28306.

Air carriers and foreign air carriers

may submit copies of written comments

previously provided to the City of

Fayetteville under section 158.23 of Part

158.

FOR FURTHER INFORMATION CONTACT: Lee

Kyker, Manager of Airport Programs,

Atlanta Airports District Office, 1701

Columbia Avenue, Suite 2–260, College

Park, GA 30337–2747, (404) 305–7161.

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

Fayetteville Regional Airport under the

provisions of the Aviation Safety and

Capacity Expansion Act of 1990 (Title

IX of the Omnibus Budget

Reconciliation Act of 1990) Pub. L. 101–

508) and Part 158 of the Federal

Aviation Regulations (14 CFR Part 158).

On May 12, 2000, the FAA

determined that the application to

impose and use the revenue from a PFC

submitted by the City of Fayetteville

was substantially complete within the

requirements of section 158.25 of Part

158. The FAA will approve or

disapprove the application, in whole or

in part, no later than September 8, 2000.

The following is a brief overview of

the application.

PFC Application No.: 00–01–C–00–

FAY.

Level of the proposed PFC: $3.00.

Proposed charge effective date:

September 1, 2000.

Proposed charge expiration date:

October 1, 2002.

Total estimated net PFC revenue:

$942,620.

Brief description of proposed

project(s):

• Airport Entrance Road

• Jetway System Modifications

• Security System Upgrade

• Preplan runway safety areas

• Rehabilitate north general aviation

ramp

• Security system upgrade, Phase II

• Design & construct RSA, Rwy 4

• Acquire land

• Renovate terminal, Ph II

• Construct RSA, Rwy 4, Ph 2

• Land Purchase

• Renovate terminal

• Construct RSA

• Acquire land

• Rehabilitate Runway 10–28

• Acquire land in fee

• Construct fire training facility &

rehabilitate ARFF vehicle Update

Airport Master Plan

• Install taxiway guidance signs &

REILS

• Construct new general aviation area

(design only)

• Acquire sweeper

• Install terminal loading bridges

• Acquire ARFF vehicle

• Construct non-license vehicle road

(design only)

• Taxiway K (design only)

33870 Federal Register / Vol. 65, No. 102 / Thursday, May 25, 2000 / Notices

• Install utilities for general aviation

• Design for Highway 301 Connector

• Acquire land for airport development

• Airport terminal development

• Construct taxiway K (design only)

• Construct GA apron (design only)

• Acquire land for development

• Rehabilitate terminal building

• Install 107.14 security access system

• Construct non-license vehicle road

(NLVR)

• Jet bridge modification

• Construct taxiway K

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.

In addition, any person may, upon

request, inspect the application, notice

and other documents germane to the

application in person at the Federal

Aviation Administration.

Issued in Atlanta, Georgia on May 16,

2000.

Rans D. Black,

Acting Manager, Atlanta Airports District

Office Southern Region.

[FR Doc. 00–13180 Filed 5–24–00; 8:45 am]

BILLING CODE 4910–13–M

DEPARTMENT OF TRANSPORTATION

National Highway Traffic Safety

Administration

Discretionary Cooperative Agreements

To Assist in the Development of Crash

Outcome Data Evaluation Systems

AGENCY: National Highway Traffic

Safety Administration, DOT.

ACTION: Notice of availability;—

discretionary cooperative agreements to

assist in the development and use of

Crash Outcome Data Evaluation

Systems.

SUMMARY: The National Highway Traffic

Safety Administration (NHTSA)

announces a discretionary cooperative

agreement program to assist states in the

development and use of Crash Outcome

Data Evaluation Systems (CODES) and

solicits applications for projects under

this program from states that have not

previously been funded to develop

CODES. Under this program states will

link their existing statewide traffic

records with medical outcome and

charge data. The linked data will be

used to support highway safety

decision-making at the local, regional,

and state levels to reduce deaths, nonfatal injuries, and health care costs

resulting from motor vehicle crashes.

DATES: Applications must be received at

the office designated below on or before

July 24, 2000.

ADDRESSES: Applications must be

submitted to DOT/National Highway

Traffic Safety Administration, Office of

Contracts and Procurement (NAD–30),

ATTN: Lamont O. Norwood/Mr. Mark

Kromer, 400 7th Street SW, Room 5301,

Washington, DC 20590. All applications

submitted must include a reference to

NHTSA Cooperative Agreement

Program No. DTNH22–00–H–07212.

Interested applicants should contact Mr.

Norwood to obtain the application

packet. Included in the application

packet are reports about data linkage

and applications for linked data

developed by the CODES project.

FOR FURTHER INFORMATION CONTACT:

General administrative questions may

be directed to Lamont O. Norwood,

Office of Contracts and Procurement.

All questions and requests for copies

may be directed by e-mail at

lnorwood@nhtsa.dot.gov or, by

telephone, at (202) 366–8573.

Programmatic questions relating to this

cooperative agreement program should

be directed to Dennis Utter, CODES

Contracting Officer’s Technical

Representative (COTR), at NHTSA,

Room 6125, (NRD–31) 400 7th Street

SW, Washington, DC 20590, or by email at dutter@nhtsa.dot.gov, or by

telephone at (202) 366–5351.

SUPPLEMENTARY INFORMATION:

Statement of Work

Background

Crash data alone are unable to convey

the magnitude of the medical and

financial consequences of the injuries

resulting from motor vehicle crashes or

the success of highway safety decisionmaking to prevent them. Outcome

information describing what happens to

all persons involved in motor vehicle

crashes, regardless of injury, is needed.

Person-specific outcome information

is collected at the crash scene and en

route by EMS personnel, at the

emergency department, in the hospital,

and after discharge. When these data are

computerized and merged statewide,

they generate a source of populationbased data that is available for use by

state and local traffic safety and public

health professionals. Linking these

records to statewide crash data collected

by police at the scene is the key to

developing relationships among specific

vehicles, crash, and occupant behavior

characteristics and their medical and

financial outcomes.

The feasibility of linking crash and

medical outcome (EMS, emergency

department, hospital discharge, death

certificate, claims, etc.) data was

demonstrated by the CODES project.

This project evolved from the

Intermodal Surface Transportation

Efficiency Act of 1991, which mandated

that NHTSA prepare a Report to

Congress about the benefits of safety belt

and motorcycle helmet use. NHTSA

provided funding to the States of

Hawaii, Maine, Missouri, New York,

Pennsylvania, Utah, and Wisconsin to

link their state data and use the linked

data to analyze the effectiveness of

safety belts and motorcycle helmets.

The Report was delivered to Congress in

February 1996. In 1996, three CODES

states (New York, Pennsylvania, and

Wisconsin) and three states which

linked crash and medical data without

CODES funding (Alaska, Connecticut,

and New Mexico) were awarded

NHTSA research funds to develop statespecific applications for linked data. In

1997, NHTSA awarded grants for

CODES linkage to Connecticut, New

Hampshire, Maryland, North Dakota,

South Dakota, Oklahoma, and Nevada.

Iowa, Kentucky, Massachusetts,

Nebraska, and South Carolina which

were funded to implement the CODES

linkage in 1998. Arizona, Delaware,

Minnesota and Tennessee were funded

in 1999.

The CODES project also demonstrated

that linked data have many uses for

decision-making related to highway

safety and injury control. In addition to

demonstrating the effectiveness of safety

belts and motorcycle helmets in

preventing death, injury, and costs, the

linked data were used to identify

populations at risk for increased

severity or high health care costs, the

impact of different occupant behaviors

on outcome, the safety needs at the

community level, the allocation of

resources for emergency medical

services, the injury patterns by type of

roadway and geographic location, and

the benefits of collaboration on data

quality. When crash, vehicle, and

behavior characteristics were linked to

outcome information, decision-makers

could identify those prevention

programs that had the most impact on

preventing or reducing the medical and

financial costs associated with motor

vehicle crashes.

Data linkage fulfills expanded data

needs without the additional expense

and delay of new data collection. The

linkage process itself provides feedback

about data quality and content problems

which leads to improvement in the state

data. Thus, it is in NHTSA’s interest to

encourage states to qualify for CODES

funding. NHTSA benefits from the

improved quality of the state data, while

the states benefit from state-specific