Meeting: RTCA Program Management Committee (PMC), 52357-52358 [2015-21418]

Download as PDF Federal Register / Vol. 80, No. 167 / Friday, August 28, 2015 / Notices subject line if email is used. To help the Commission process and review your comments more efficiently, please use only one method. The Commission will post all comments on the Commission’s Internet Web site (https://www.sec.gov/ rules/sro.shtml). Copies of the submission, all subsequent amendments, all written statements with respect to the proposed rule change that are filed with the Commission, and all written communications relating to the proposed rule change between the Commission and any person, other than those that may be withheld from the public in accordance with the provisions of 5 U.S.C. 552, will be available for Web site viewing and printing in the Commission’s Public Reference Room, 100 F Street NE., Washington, DC 20549 on official business days between the hours of 10:00 a.m. and 3:00 p.m. Copies of the filing also will be available for inspection and copying at the principal office of the MSRB. All comments received will be posted without change; the Commission does not edit personal identifying information from submissions. You should submit only information that you wish to make available publicly. All submissions should refer to File Number SR–MSRB– 2015–08 and should be submitted on or before September 18, 2015. For the Commission, pursuant to delegated authority.25 Robert W. Errett, Deputy Secretary. [FR Doc. 2015–21296 Filed 8–27–15; 8:45 am] BILLING CODE 8011–01–P DEPARTMENT OF TRANSPORTATION Federal Aviation Administration [Summary Notice No. PE–2015–50] Petition for Exemption; Summary of Petition Received; Chevron Aircraft Operations Federal Aviation Administration (FAA), DOT. ACTION: Notice. AGENCY: 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 Lhorne on DSK5TPTVN1PROD with NOTICES SUMMARY: 25 17 CFR 200.30–3(a)(12). VerDate Sep<11>2014 14:19 Aug 27, 2015 Jkt 235001 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–2014–1111 using any of the following methods: • Federal eRulemaking Portal: Go to https://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 https://www.regulations.gov, as described in the system of records notice (DOT/ALL–14 FDMS), which can be reviewed at https://www.dot.gov/ privacy. Docket: Background documents or comments received may be read at https://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–2014–1111. Petitioner: Chevron Aircraft Operations. Section(s) of 14 CFR Affected: § 91.9(a). PO 00000 Frm 00113 Fmt 4703 Sfmt 4703 52357 Description of Relief Sought: Chevron Aircraft Operations (Chevron) requests relief from § 91.9(a), which states that no person may operate a civil aircraft without complying with the operating limitations specified in the approved Airplane or Rotorcraft Flight Manual, markings, and placards, or as otherwise prescribed by the certificating authority of the country of registry. In a letter dated June 24, 2015, Chevron clarified that the specific limitation that it seeks to not comply with is the Agusta Westland AW–139 Rotorcraft Flight Manual, Supplements 12 and 50. These supplements prescribe, in part, a heliport or helideck minimum size limitation of 50 feet by 50 feet or 50 foot diameter. Chevron wishes to operate the AW139 using Category A procedures from a helideck that is smaller than 50 feet by 50 feet or 50 foot diameter for its offshore operations. [FR Doc. 2015–21308 Filed 8–27–15; 8:45 am] BILLING CODE 4910–13–P DEPARTMENT OF TRANSPORTATION Federal Aviation Administration Meeting: RTCA Program Management Committee (PMC) Federal Aviation Administration (FAA), U.S. Department of Transportation (DOT). ACTION: Notice of RTCA Program Management Committee Meeting. AGENCY: The FAA is issuing this notice to advise the public of a RTCA Program Management Committee meeting. DATES: The meeting will be held September 22nd from 8:30 a.m.–4:30 p.m. ADDRESSES: The meeting will be held at RTCA Headquarters, 1150 18th Street NW., Suite 910, Washington, DC 20036, Tel: (202) 330–0680. FOR FURTHER INFORMATION CONTACT: The RTCA Secretariat, 1150 18th Street NW., Suite 910, Washington, DC 20036, or by telephone at (202) 833–9339, fax at (202) 833–9434, or Web site at https:// www.rtca.org or Karan Hofmann, Program Director, RTCA, Inc., khofmann@rtca.org, (202) 330–0680. SUPPLEMENTARY INFORMATION: Pursuant to section 10(a) (2) of the Federal Advisory Committee Act (Pub. L. 92– 463, 5 U.S.C., App.), notice is hereby given for a meeting of the RTCA Program Management Committee. The agenda will include the following: SUMMARY: Tuesday, September 22, 2015 1. WELCOME AND INTRODUCTIONS 2. REVIEW/APPROVE E:\FR\FM\28AUN1.SGM 28AUN1 Lhorne on DSK5TPTVN1PROD with NOTICES 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— VerDate Sep<11>2014 14:19 Aug 27, 2015 Jkt 235001 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 PO 00000 Frm 00114 Fmt 4703 Sfmt 4703 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 Federal Aviation Administration (FAA), DOT. ACTION: Notice. AGENCY: 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 SUMMARY: E:\FR\FM\28AUN1.SGM 28AUN1

Agencies

[Federal Register Volume 80, Number 167 (Friday, August 28, 2015)]
[Notices]
[Pages 52357-52358]
From the Federal Register Online via the Government Publishing Office [www.gpo.gov]
[FR Doc No: 2015-21418]


-----------------------------------------------------------------------

DEPARTMENT OF TRANSPORTATION

Federal Aviation Administration


Meeting: RTCA Program Management Committee (PMC)

AGENCY: Federal Aviation Administration (FAA), U.S. Department of 
Transportation (DOT).

ACTION: Notice of RTCA Program Management Committee Meeting.

-----------------------------------------------------------------------

SUMMARY: The FAA is issuing this notice to advise the public of a RTCA 
Program Management Committee meeting.

DATES: The meeting will be held September 22nd from 8:30 a.m.-4:30 p.m.

ADDRESSES: The meeting will be held at RTCA Headquarters, 1150 18th 
Street NW., Suite 910, Washington, DC 20036, Tel: (202) 330-0680.

FOR FURTHER INFORMATION CONTACT: The RTCA Secretariat, 1150 18th Street 
NW., Suite 910, Washington, DC 20036, or by telephone at (202) 833-
9339, fax at (202) 833-9434, or Web site at https://www.rtca.org or 
Karan Hofmann, Program Director, RTCA, Inc., khofmann@rtca.org, (202) 
330-0680.

SUPPLEMENTARY INFORMATION: Pursuant to section 10(a) (2) of the Federal 
Advisory Committee Act (Pub. L. 92-463, 5 U.S.C., App.), notice is 
hereby given for a meeting of the RTCA Program Management Committee. 
The agenda will include the following:

Tuesday, September 22, 2015

1. WELCOME AND INTRODUCTIONS
2. REVIEW/APPROVE

[[Page 52358]]

    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
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.