38314 Federal Register / Vol. 65, No. 119 / Tuesday, June 20, 2000 / Notices

between the DOT and the expert’s

evidence. The ALJ will explain in the

decision how he or she resolved the

conflict between the vocational expert’s

evidence and information in the DOT

and will give the reasons for accepting

or rejecting the vocational expert’s

evidence.

We intend to clarify the regulations at

issue in this case, 20 CFR 404.1566 and

416.966, through publication of an SSR

and we may rescind this Ruling when

the clarification is made.

[FR Doc. 00–15426 Filed 6–19–00; 8:45 am]

BILLING CODE 4191–02–F

DEPARTMENT OF TRANSPORTATION

Coast Guard

[USCG 2000–7502]

Merchant Marine Personnel Advisory

Committee

AGENCY: Coast Guard, DOT.

ACTION: Notice of charter renewal.

SUMMARY: The Secretary of

Transportation has renewed the charter

for the Merchant Marine Personnel

Advisory Committee (MERPAC) to

remain in effect for a period of two years

from May 20, 2000, until May 20, 2002.

MERPAC is a federal advisory

committee constituted under 5 U.S.C.

App. 2. Its purpose is to advise the

Coast Guard on matters relating to the

training, qualification, licensing,

certification and fitness of seamen

serving in the U.S. merchant marine.

The charter is available on MERPAC’s

Internet web page at http://

www.uscg.mil/hg/g-m/advisory/

merpac/merpac.htm.

FOR FURTHER INFORMATION CONTACT:

Lieutenant Commander Luke B. Harden,

Acting Executive Director, or Mr. Mark

C. Gould, Assistant to the Executive

Director, Commandant (G–MSO–1), U.S.

Coast Guard, 2100 Second Street SW,

Washington, DC 20593–0001, telephone

202–267–0229.

Dated: June 14, 2000.

Howard L. Hime,

Acting Director of Standards.

[FR Doc. 00–15513 Filed 6–19–00; 8:45 am]

BILLING CODE 4910–15–U

DEPARTMENT OF TRANSPORTATION

Federal Aviation Administration

RTCA, Special Committee 172; Future

Air-Ground Communications in the

VHF Aeronautical Data Band (118–137

MHz)

Pursuant to section 10(a)(2) of the

Federal Advisory Committee Act (Pub.

L. 92–463, 5 U.S.C., Appendix 2), notice

is hereby given for Special Committee

172 meeting to be held July 26–27, 2000,

starting at 9:00 a.m. The meeting will be

held at RTCA, 1140 Connecticut

Avenue, NW., Suite 1020, Washington,

DC 20036.

The agenda will be as follows: July 26:

(1) Plenary Convenes at 9:00 a.m.; (2)

Introductory Remarks; (3) Review and

Approve Agenda; (4) Working Group

(WG)–2, VHF Data Radio Signal-inSpace Minimum Aviation System

Performance Standards, review

comments on final work (written inputs

only) and vote on DO–224A (distributed

in advance).

Note: This is a single-purpose meeting

convened solely for the purpose of

completing the final draft of DO–224A. No

comments will be accepted that were not

submitted for review, in writing, prior to the

meeting. July 27: (5) WG–2/Plenary as

necessary; (6) Other Business; (7) Dates and

Locations of Next Meeting; (8) Closing.

Attendance is open to the interested

public but limited to space availability.

With the approval of the chairman,

members of the public may present oral

statements at the meeting. Persons

wishing to present statements or obtain

information should contact the RTCA

Secretariat, 1140 Connecticut Avenue,

NW., Suite 1020, Washington, DC

20036; (202) 833–9339 (phone); (202)

833–9434 (fax); or http://www.rtca.org

(web site). Members of the public may

present a written statement to the

committee at any time.

Issued in Washington, DC, on June 14,

2000.

Jane P. Caldwell,

Designated Official.

[FR Doc. 00–15537 Filed 6–19–00; 8:45 am]

BILLING CODE 4910–13–M

DEPARTMENT OF TRANSPORTATION

Federal Aviation Administration

RTCA, Special Committee 194; ATM

Data Link Implementation

Pursuant to section 10(a)(2) of the

Federal Advisory Committee Act (Pub.

L. 92–463, 5 U.S.C., Appendix 2), notice

is hereby given for Special Committee

194 meeting to be held July 10–13, 2000,

starting at 9:00 a.m. The meeting will be

held at RTCA, 1140 Connecticut Ave.,

NW, Suite 1020, Washington, DC 20036.

The agenda will include: July 10:

Working Group (WG) 3, Human Factors.

July 11: WG–1, Data Link Ops Concept

& Implementation Plan; WG–3, Human

Factors; WG–4, Service Provider

Interface. July 12: WG–1, Data Link Ops

Concept & Implementation Plan; WG–3,

Human Factors; WG–4, Service Provider

Interface. July 13: Plenary Session: (1)

Welcome and Introductory Remarks; (2)

Review Agenda; (3) Review/Approve of

Previous Meetings; (4) Working Group

Reports; (5) Other Business; (13) Date

and Location of Future Meetings; (14)

Closing.

Attendance is open to the interested

public but limited to space availability.

With the approval of the chairman,

members of the public may present oral

statements at the meeting. Persons

wishing to present statements or obtain

information should contact the RTCA

Secretariat, 1140 Connecticut Avenue,

NW., Suite 1020, Washington, DC.

20036; (202) 833–9339 (phone); (202)

833–9434 (fax); or http://www.rtca.org

(web site). Members of the public may

present a written statement to the

committee at any time.

Issued in Washington, DC, on June 14,

2000.

Jane P. Caldwell,

Designated Official.

[FR Doc. 00–15538 Filed 6–19–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 a Passenger

Facility Charge (PFC) at Monterey

Peninsula Airport, Monterey, CA

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 a PFC at

Monterey Peninsula 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 July 20, 2000.

ADDRESSES: Comments on this

application may be mailed or delivered

in triplicate to the FAA at the following