52358 Federal Register / Vol. 80, No. 167 / Friday, August 28, 2015 / Notices 

a. Meeting Summary June 18, 2015, 

RTCA Paper No. 181–15/PMC–1362 

b. Administrative SC TOR Revisions 

i. SC–224—Airport Security Access 

Control Systems—New Co-Chair 

ii. SC–235—Non-Rechargeable 

Lithium Batteries—New Chair 

3. PUBLICATION CONSIDERATION/

APPROVAL 

a. Final Draft, Revised Document, 

DO–328—Safety, Performance and 

Interoperability Requirements 

Document for Airborne Spacing— 

Flight-deck Interval Management 

(ASPA–FIM), prepared by SC–186 

b. Final Draft, New Document, MOPS 

for Flight-deck Interval 

Management (FIM), prepared by 

SC–186 

c. Final Draft, Revised Document, 

DO–272C—User Requirements for 

Aerodrome Mapping Information, 

prepared by SC–217 

d. Final Draft, Revised Document, 

DO–276B—User Requirements for 

Terrain and Obstacle Data, prepared 

by SC–217 

e. Final Draft, Revised Document, 

DO–291B—Interchange Standards 

for Terrain, Obstacle and 

Aerodrome Mapping Data, prepared 

by SC–217 

f. Final Draft, White Paper, Standards 

Development Activities for using 

Near Real-Time Aircraft-Derived 

Data in Future Applications, 

prepared by Wake Vortex Tiger 

Team 

4. INTEGRATION and COORDINATION 

COMMITTEE (ICC) 

a. ICC Membership—Update/

Approval—Discussion 

5. ACTION ITEM REVIEW 

a. Workshop—Integrated Cockpit— 

Integrated Standards: Cross-Cutting 

Committee—Update 

b. PMC Ad-Hoc to provide SC–225 

perceived shortfalls in DO–311 

revision—Update 

c. PMC Ad-Hoc MASPS vs. guidance 

‘‘discontinuity’’ between RTCA and 

EUROCAE documentation— 

Discussion 

d. Response to Lockheed Martin’s 

input to speed up MOPS in SC–159 

TOR—Discussion 

e. Follow up discussion with FAA on 

cybersecurity concerns to be 

included in SC–159 TOR— 

Discussion 

f. Industry Interest in Runway 

Overrun Alerting—possible new 

Special Committee (SC)— 

Discussion 

g. UPS GPS issue—Update 

6. DISCUSSION 

a. SC–147—MOPS for Traffic Alert 

and Collision Avoidance Systems 

Airborne Equipment—Discussion— 

Revised TOR 

b. SC–217—Aeronautical Databases— 

Discussion—Revised TOR 

c. SC–223—Aeronautical Mobile 

Airport Communication System— 

Discussion—Revised TOR 

d. SC–228—Minimum Operational 

Performance Standards (MOPS) for 

Unmanned Aircraft Systems, initial 

release, MOPS for Unmanned 

Aircraft Systems (UAS) Command 

and Control (C2)—Discussion 

e. SC–228—MOPS for Unmanned 

Aircraft Systems, initial release, 

MOPS for Unmanned Aircraft 

Systems (UAS) Detect and Avoid 

(DAA) Systems—Discussion 

f. SC–228—MOPS for Unmanned 

Aircraft Systems, initial release, 

MOPS for Air-to-Air Radar for 

Detect and Avoid—Discussion 

g. SC–230—Airborne Weather 

Detection Systems—Discussion— 

Revised TOR 

h. SC–234—Portable Electronic 

Devices—Discussion—Status 

Update 

i. Design Assurance Guidance for 

Airborne Electronic Hardware— 

Status—Possible New Special 

Committee to Update RTCA DO– 

254 

j. NAC—Status Update 

k. TOC—Status Update 

l. FAA Actions Taken on Previously 

Published Documents—Report 

m. Special Committees—Chairmen’s 

Reports and Active Inter-Special 

Committee Requirements 

Agreements (ISRA)—Review 

n. European/EUROCAE 

Coordination—Status Update 

o. Planning Forward—Discussion 

7. OTHER BUSINESS 

8. SCHEDULE for COMMITTEE 

DELIVERABLES and NEXT 

MEETING DATE 

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 person 

listed in the FOR FURTHER INFORMATION

CONTACT section. Members of the public 

may present a written statement to the 

committee at any time. 

Issued in Washington, DC, on August 25, 

2015. 

Latasha Robinson, 

Management & Program Analyst, Next 

Generation, Enterprise Support Services 

Division, Federal Aviation Administration. 

[FR Doc. 2015–21418 Filed 8–27–15; 8:45 am] 

BILLING CODE 4910–13–P 

DEPARTMENT OF TRANSPORTATION 

Federal Aviation Administration 

Agency Information Collection 

Activities: Emergency Clearance: 

Public Information Collection 

Requirements Submitted to the Office 

of Management and Budget (OMB): 

B4UFLY Smartphone App 

AGENCY: Federal Aviation 

Administration (FAA), DOT. 

ACTION: Notice. 

SUMMARY: The Federal Aviation 

Administration (FAA) is announcing an 

opportunity for the public to comment 

on FAA’s intention to collect 

information from the public. In 

accordance with the Paperwork 

Reduction Act of 1995, FAA invites 

public comments about our request to 

the Office of Management and Budget 

(OMB) for approval for an information 

collection. We are requesting an 

emergency review under 5 CFR part 

1320(a)(2)(i) because public harm is 

reasonably likely to result if the normal 

clearance procedures are followed. In 

compliance with the requirement of 

section 3506(c)(2)(A) of the Paperwork 

Reduction Act of 1995, we have 

submitted to the Office of Management 

and Budget (OMB) the following 

requirements for emergency review. 

The FAA has documented over 675 

pilot and law enforcement reports of 

unmanned aircraft ‘events’ in 2015. In 

comparison, the FAA received 238 of 

these reports in the entirety of 2014. 

This increase in reports, particularly in 

close proximity to airports, suggests that 

many unmanned aircraft system (UAS) 

operators are unaware of safety 

guidelines and policies and are unaware 

of the potential hazards these operations 

may pose to manned aircraft operations. 

The FAA’s B4UFLY smartphone app 

will provide situational awareness of 

flight restrictions—including locations 

of airports, restricted airspace, special 

use airspaces, and temporary flight 

restrictions—based on a user’s current 

or planned flight location. The risk 

posed to the National Airspace System 

(NAS) by increasingly unsafe UAS 

operations makes the immediate release 

of this app vital. 

DATES: Written comments should be 

submitted by September 28, 2015. 

ADDRESSES: Interested persons are 

invited to submit written comments on 

the proposed information collection to 

the Office of Information and Regulatory 

Affairs, Office of Management and 

Budget. Comments should be addressed 

to the attention of the Desk Officer, 

Department of Transportation/FAA, and 


Lhorne on DSK5TPTVN1PROD with NOTICES
Federal Register / Vol. 80, No. 167 / Friday, August 28, 2015 / Notices 52359 

sent via electronic mail to oira_

submission@omb.eop.gov, or faxed to 

(202) 395–6974, or mailed to the Office 

of Information and Regulatory Affairs, 

Office of Management and Budget, 

Docket Library, Room 10102, 725 17th 

Street NW., Washington, DC 20503. 

Public Comments Invited: You are 

asked to comment on any aspect of this 

information collection, including (a) 

Whether the proposed collection of 

information is necessary for FAA’s 

performance; (b) the accuracy of the 

estimated burden; (c) ways for FAA to 

enhance the quality, utility and clarity 

of the information collection; and (d) 

ways that the burden could be 

minimized without reducing the quality 

of the collected information. The agency 

will summarize and/or include your 

comments in the subsequent request for 

OMB’s full clearance of this information 

collection. 

FOR FURTHER INFORMATION CONTACT: 

Ronda Thompson at (202) 267–1416, or 

by email at: Ronda.Thompson@faa.gov. 

SUPPLEMENTARY INFORMATION: 

OMB Control Number: 2120–XXXX 

(to be assigned). 

Title: B4UFLY Smartphone App. 

Form Numbers: There are no FAA 

forms associated with this information 

collection. 

Type of Review: Request for 

emergency clearance of a new 

information collection. 

Background: Public Law 112–95, 

Section 336 requires model aircraft 

operators to notify the airport operator 

and air traffic control tower (if one is 

located at the airport) prior to operating 

within 5 miles of an airport. The FAA’s 

B4UFLY smartphone app will provide 

situational awareness of flight 

restrictions—including locations of 

airports, restricted airspace, special use 

airspaces, and temporary flight 

restrictions—based on a user’s current 

or planned flight location. In order to 

maintain NAS safety in proximity to 

airports, air traffic control personnel 

would need certain basic information 

about a UAS operator’s intended flight 

in order to assess whether the UAS may 

disrupt or endanger manned air traffic. 

The data collected by the B4UFLY app 

during the initial 60-day beta test will 

help the FAA determine procedures for 

managing more widespread public use 

of the B4UFLY app. 

Respondents: 1,000 beta test users. 

Frequency: Approximately 5 

submissions per week, per user. 

Estimated Average Burden per 

Response: 2 minutes. 

Estimated Total Annual Burden: 

1,485 hours. 

Issued in Washington, DC on August 21, 

2015. 

Ronda Thompson, 

FAA Information Collection Clearance 

Officer, IT Enterprises Business Services 

Division, ASP–110. 

[FR Doc. 2015–21415 Filed 8–27–15; 8:45 am] 

BILLING CODE 4910–13–P 

DEPARTMENT OF TRANSPORTATION 

Federal Aviation Administration 

[Summary Notice No. 2015–53] 

Petition for Exemption; Summary of 

Petition Received; American Airlines, 

Inc. 

AGENCY: Federal Aviation 

Administration (FAA), DOT. 

ACTION: Notice. 

SUMMARY: This notice contains a 

summary of a petition seeking relief 

from specified requirements of title 14 

of the Code of Federal Regulations. The 

purpose of this notice is to improve the 

public’s awareness of, and participation 

in, the FAA’s exemption process. 

Neither publication of this notice nor 

the inclusion or omission of information 

in the summary is intended to affect the 

legal status of the petition or its final 

disposition. 

DATES: Comments on this petition must 

identify the petition docket number and 

must be received on or before 

September 17, 2015. 

ADDRESSES: Send comments identified 

by docket number FAA–2015–3491 

using any of the following methods: 

• Federal eRulemaking Portal: Go to 

http://www.regulations.gov and follow 

the online instructions for sending your 

comments electronically. 

• Mail: Send comments to Docket 

Operations, M–30; U.S. Department of 

Transportation (DOT), 1200 New Jersey 

Avenue SE., Room W12–140, West 

Building Ground Floor, Washington, DC 

20590–0001. 

• Hand Delivery or Courier: Take 

comments to Docket Operations in 

Room W12–140 of the West Building 

Ground Floor at 1200 New Jersey 

Avenue SE., Washington, DC, between 9 

a.m. and 5 p.m., Monday through 

Friday, except Federal holidays. 

• Fax: Fax comments to Docket 

Operations at 202–493–2251. 

Privacy: In accordance with 5 U.S.C. 

553(c), DOT solicits comments from the 

public to better inform its rulemaking 

process. DOT posts these comments, 

without edit, including any personal 

information the commenter provides, to 

http://www.regulations.gov, as 

described in the system of records 

notice (DOT/ALL–14 FDMS), which can 

be reviewed at http://www.dot.gov/

privacy. 

Docket: Background documents or 

comments received may be read at 

http://www.regulations.gov at any time. 

Follow the online instructions for 

accessing the docket or go to the Docket 

Operations in Room W12–140 of the 

West Building Ground Floor at 1200 

New Jersey Avenue SE., Washington, 

DC, between 9 a.m. and 5 p.m., Monday 

through Friday, except Federal holidays. 

FOR FURTHER INFORMATION CONTACT: 

Keira Jones (202) 267–4025, Office of 

Rulemaking, Federal Aviation 

Administration, 800 Independence 

Avenue SW., Washington, DC 20591. 

This notice is published pursuant to 

14 CFR 11.85. 

Issued in Washington, DC, on August 25, 

2015. 

Lirio Liu, 

Director, Office of Rulemaking. 

Petition For Exemption 

Docket No.: FAA–2015–3491 

Petitioner: American Airlines, Inc. 

Section(s) of 14 CFR Affected: 

§ 93.123 

Description of Relief Sought: 

American Airlines seeks relief to permit 

American/American Eagle to operate 

two slots to maintain nonstop service 

between Ronald Reagan Washington 

National Airport (DCA) and Lansing, 

Michigan’s Capital Region International 

Airport (LAN) under the terms and 

conditions of Exemption No. 10466. 

[FR Doc. 2015–21309 Filed 8–27–15; 8:45 am] 

BILLING CODE 4910–13–P 

DEPARTMENT OF TRANSPORTATION 

Federal Highway Administration 

Environmental Impact Statement: 

Hidalgo County, Texas 

AGENCY: Texas Department of 

Transportation (TxDOT), Federal 

Highway Administration (FHWA), 

Department of Transportation. 

ACTION: Federal notice of intent to 

prepare an Environmental Impact 

Statement (EIS). 

SUMMARY: Pursuant to 40 CFR 1508.22, 

FHWA, on behalf of TxDOT, is issuing 

this notice to advise the public that an 

EIS will be prepared for a proposed 

transportation project to construct State 

Highway (SH) 68 from Interstate (I)-2/

United States Highway (US) 83 to I– 

69C/US 281 in Hidalgo County, Texas. 

Areas within the study area include the 

cities of Alamo, Pharr, Donna, Edinburg, 

San Juan, and San Carlos. 


Lhorne on DSK5TPTVN1PROD with NOTICES