71474 Federal Register / Vol. 72, No. 241 / Monday, December 17, 2007 / Notices 

security of the SSA workplace and the 

operation of SSA facilities, or 

(b) To assist investigations or 

prosecutions with respect to activities 

that affect such safety and security or 

activities that disrupts the operation of 

SSA facilities. 

8. To the appropriate law enforcement 

official, the Social Security 

Administration (SSA) may disclose 

information regarding a Social Security 

beneficiary, claimant, attorney or nonattorney representative, or 

representative payee who is the subject 

of an outstanding arrest warrant for 

having committed, or having attempted 

to commit, a violent crime for the 

purposes of determining whether SSA 

should include an individual’s 

information in the VIP/CSR System or 

remove an individual’s information 

from the system because he or she no 

longer meets the criteria (i.e., the 

individual is in the custody of law 

enforcement, is no longer a suspect or 

has been exonerated, or is deceased). 

POLICIES AND PRACTICES FOR STORING, 

RETRIEVING, ACCESSING, RETAINING AND

DISPOSING OF RECORDS IN THE SYSTEM: 

STORAGE: 

Records in this system are maintained 

in both electronic and paper form (e.g., 

magnetic tape and disc and microfilm). 

RETRIEVABILITY: 

Records in this system will be 

retrieved by the individual’s SSN and/ 

or name. 

SAFEGUARDS: 

Security measures include the use of 

access codes to enter in the computer 

system, which will maintain the data 

and storage of the computerized records 

in secured areas that are accessible only 

to employees who require the 

information in performing their official 

duties. SSA employees who have access 

to the data will be informed of the 

criminal penalties of the Privacy Act for 

unauthorized access to or disclosure of 

information maintained in the system. 

See 5 U.S.C. 552a(i)(1). 

Contractor personnel and/or alternate 

participants having access to data in the 

system of records will be required to 

adhere to SSA rules concerning 

safeguards, access and use of the data. 

RETENTION AND DISPOSAL: 

Records in the Visitor Intake Process/ 

Customer Service Record (VIP/CSR) 

System ‘‘High Risk’’ file will be retained 

for five years in accordance with 

Section E of NC–47–76–12. The means 

of disposal of the information in the 

Visitor Intake Process/Customer Service 

Record (VIP/CSR) System ‘‘High Risk’’

file will be appropriate to the storage 

medium (e.g., deletion of individual 

electronic records or shredding of paper 

records). Additionally, management 

officials will have the ability to delete 

records from the ‘‘High Risk’’ file 

electronic database. 

SYSTEM MANAGER(S) AND ADDRESS(ES): 

Deputy Commissioner, Office of 

Systems, Social Security 

Administration, 6401 Security 

Boulevard, Baltimore, Maryland 21235. 

NOTIFICATION PROCEDURE(S): 

An individual can determine if this 

system contains a record about him or 

her by writing to the system manager(s) 

at the above address and providing his 

or her name, SSN, or other information 

that may be in the system of records that 

will identify him or her. An individual 

requesting notification of records in 

person should provide the same 

information, as well as provide an 

identity document, preferably with a 

photograph, such as a driver’s license. If 

an individual does not have 

identification documents sufficient to 

establish his or her identity, the 

individual must certify in writing that 

he or she is the person claimed to be 

and that he or she understands that 

knowing and willful request for, or 

acquisition of, a record pertaining to 

another individual under false pretenses 

is a criminal offense. 

If notification is requested by 

telephone, an individual must verify his 

or her identity by providing identifying 

information that parallels the record to 

which notification is being requested. If 

it is determined the identifying 

information provided by telephone is 

insufficient, the individual will be 

required to submit a request in writing 

or in person. If an individual is 

requesting information by telephone on 

behalf of another individual, the subject 

individual must be connected with SSA 

and the requesting individual in the 

same phone call. SSA will establish the 

subject individual’s identity (his or her 

name, SSN, address, date of birth and 

place of birth, along with one other 

piece of information such as mother’s 

maiden name), and ask for his or her 

consent in providing information to the 

requesting individual. 

If a request for notification is 

submitted by mail, an individual must 

include a notarized statement to SSA to 

verify his or her identity or must certify 

in the request that he or she is the 

person claimed to be and that he or she 

understands that the knowing and 

willful request for, or acquisition of, a 

record pertaining to another individual 

under false pretenses is a criminal 

offense. These procedures are in 

accordance with SSA Regulations (20 

CFR 401.40). 

RECORD ACCESS PROCEDURE(S): 

Same as Notification procedure(s). 

Requesters also should reasonably 

specify the record contents they are 

seeking. These procedures are in 

accordance with SSA Regulations (20 

CFR 401.40). 

CONTESTING RECORD PROCEDURE(S): 

Same as Notification procedures. 

Requesters also should reasonably 

identify the record, specify the 

information they are contesting, and 

state the corrective action sought, and 

the reasons for the correction, with 

supporting justification showing how 

the record is untimely, incomplete, 

inaccurate or irrelevant. These 

procedures are in accordance with SSA 

Regulations (20 CFR 401.65). 

RECORD SOURCE CATEGORIES: 

Information in this system of records 

is obtained from information collected 

from individuals interviewed in person 

in SSA FOs, from existing systems of 

records, such as the Claims Folders 

System, 60–0089; Master Beneficiary 

Record, 60–0090, Supplemental 

Security Income Record and Special 

Veterans Benefits, 60–0103; from 

information generated by SSA, such as 

computer date/time stamps at various 

points in the interview process; and 

from law enforcement. 

SYSTEMS EXEMPTED FROM CERTAIN PROVISIONS

OF THE PRIVACY ACT: 

None. 

[FR Doc. E7–24391 Filed 12–14–07; 8:45 am] 

BILLING CODE 4191–02–P 

DEPARTMENT OF TRANSPORTATION 

Federal Aviation Administration 

Noise Exposure Map Notice for Marana 

Regional Airport, Marana, AZ 

AGENCY: Federal Aviation 

Administration, DOT. 

ACTION: Notice. 

SUMMARY: The Federal Aviation 

Administration (FAA) announces its 

determination that the noise exposure 

maps submitted by the Town of Marana, 

Arizona for Marana Regional Airport 

under the provisions of 49 U.S.C. 47501, 

et seq. (Aviation Safety and Noise 

Abatement Act) and 14 CFR part 150 are 

in compliance with applicable 

requirements. 


ebenthall on PROD1PC69 with NOTICES
Federal Register / Vol. 72, No. 241 / Monday, December 17, 2007 / Notices 71475 

DATES: Effective Date: The effective date 

of the FAA’s determination on the noise 

exposure maps is December 7, 2007. 

FOR FURTHER INFORMATION CONTACT: Ms. 

Michelle Simmons, Federal Aviation 

Administration, Los Angeles Airports 

District Office, 15000 Aviation 

Boulevard, Hawthorne, California 

90261, Telephone: 310/725–3614. 

SUPPLEMENTARY INFORMATION: This 

notice announces that the FAA finds 

that the noise exposure maps submitted 

for Marana Regional Airport are in 

compliance with applicable 

requirements of Part 150, effective 

December 7, 2007. Under 49 U.S.C. 

section 47503 of the Aviation Safety and 

Noise Abatement Act (hereinafter 

referred to as ‘‘the Act’’), an airport 

operator may submit to the FAA noise 

exposure maps which meet applicable 

regulations and which depict noncompatible land uses as of the date of 

submission of such maps, a description 

of projected aircraft operations, and the 

ways in which such operations will 

affect such maps. The Act requires such 

maps to be developed in consultation 

with interested and affected parties in 

the local community, government 

agencies, and persons using the airport. 

An airport operator who has submitted 

noise exposure maps that are found by 

FAA to be in compliance with the 

requirements of Federal Aviation 

Regulations (FAR) Part 150, 

promulgated pursuant to the Act, may 

submit a noise compatibility program 

for FAA approval which sets forth the 

measures the operator has taken or 

proposes to take to reduce existing noncompatible uses and prevent the 

introduction of additional noncompatible uses. 

The FAA has completed its review of 

the noise exposure maps and 

accompanying documentation 

submitted by the Town of Marana, 

Arizona. The documentation that 

constitutes the ‘‘Noise Exposure Maps’’

as defined in section 150.7 of Part 150 

includes: ‘‘Exhibit 1–2005 Noise 

Exposure Map,’’ and ‘‘Exhibit 2–2010 

Noise Exposure Map.’’ The Noise 

Exposure Maps contain current and 

forecast information including the 

depiction of the airport and its 

boundaries, the runway configurations, 

land uses such as residential, open 

space, commercial/office, community 

facilities, libraries, churches, open 

space, infrastructure, vacant and 

warehouse and those areas within the 

Yearly Day-Night Average Sound Level 

(DNL) 65, 70 and 75 noise contours. 

Estimates for the number of people 

within these contours for the year 2005 

are shown in Table 4B. Estimates of the 

future residential population within the 

2010 noise contours are shown in Table 

4E. Flight tracks for the existing and the 

five-year forecast Noise Exposure Maps 

are found in Exhibits 3D, 3E, and 3F. 

The type and frequency of aircraft 

operations (including nighttime 

operations) are found in Table 3C. The 

FAA has determined that these noise 

exposure maps and accompanying 

documentation are in compliance with 

applicable requirements. This 

determination is effective on December 

7, 2007. 

FAA’s determination on an airport 

operator’s noise exposure maps is 

limited to a finding that the maps were 

developed in accordance with the 

procedures contained in Appendix A of 

FAR Part 150. Such determination does 

not constitute approval of the 

applicant’s data, information or plans, 

or a commitment to approve a noise 

compatibility program or to fund the 

implementation of that program. If 

questions arise concerning the precise 

relationship of specific properties to 

noise exposure contours depicted on a 

noise exposure map submitted under 

section 47503 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 section 

47506 of the Act. 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 noise exposure maps. 

Therefore, the responsibility for the 

detailed overlaying of noise exposure 

contours onto the map depicting 

properties on the surface rests 

exclusively with the airport operator 

that submitted those maps, or with 

those public agencies and planning 

agencies with which consultation is 

required under section 47503 of the Act. 

The FAA has relied on the certification 

by the airport operator, under section 

150.21 of FAR Part 150, that the 

statutorily required consultation has 

been accomplished. 

Copies of the full noise exposure map 

documentation and of the FAA’s 

evaluation of the maps are available for 

examination at the following locations: 

Federal Aviation Administration, 

Planning and Environmental Division, 

APP–400, 800 Independence Avenue, 

SW., Washington, DC 20591. 

Federal Aviation Administration, 

Western-Pacific Region, Airports 

Division, Room 3012, 15000 Aviation 

Boulevard, Hawthorne, California 

90261. 

Federal Aviation Administration, Los 

Angeles Airports District Office, 

Room 3024, 15000 Aviation 

Boulevard, Hawthorne, California 

90261. 

Charles Mangum, Airport Director, 

Marana Regional Airport, 11700 W. 

Avra Valley Road, #91, Marana, 

Arizona 85633–9625. 

Questions may be directed to the 

individual named above under the 

heading FOR FURTHER INFORMATION

CONTACT. 

Issued in Hawthorne, California on 

December 7, 2007. 

Mark A. McClardy, 

Manager, Airports Division, AWP–600, 

Western-Pacific Region. 

[FR Doc. 07–6067 Filed 12–14–07; 8:45 am] 

BILLING CODE 4910–13–M 

DEPARTMENT OF TRANSPORTATION 

Federal Aviation Administration 

[Docket No: FAA–2008–22842] 

Notice of Opportunity To Participate, 

Criteria Requirements and Application 

Procedure for Participation in the 

Military Airport Program (MAP) 

AGENCY: Federal Aviation 

Administration (FAA), Department of 

Transportation (DOT). 

ACTION: Notice of criteria and 

application procedures for designation 

or redesignation, for the fiscal year 2008 

MAP. 

SUMMARY: In anticipation of congress 

enacting an extension of the Airport 

Improvement Program (AIP) the FAA is 

publishing this annual notice. This 

notice announces the criteria, 

application procedures, and schedule to 

be applied by the Secretary of 

Transportation in designating or 

redesignating, and funding capital 

development annually for up to 15 

current (joint-use) or former military 

airports seeking designation or 

redesignation to participate in the MAP. 

While FAA currently has continuing 

authority to designate or redesignate 

airports, FAA does not have authority to 

issue grants for fiscal year 2008 MAP, 

and will not have authority until 

Congress enacts legislation enabling 

FAA to issue grants. 

The MAP allows the Secretary to 

designate current (joint-use) or former 

military airports to receive grants from 


ebenthall on PROD1PC69 with NOTICES