Welcome to RTCA Program Management Committee Meeting December 13, 2018

Welcome to RTCA Program Management Committee Meeting December 13, 2018

Welcome & Introductions Chair Chris Hegarty, MITRE

Anti-Trust Policy RTCA meetings are conducted in strict compliance with US antitrust laws. Meetings shall not consider, or be used to discuss, agreements on prices, including terms of sale or credit, production plans, marketing strategies or customer potential, or any other element of competition between participants. RTCA staff will suspend any discussion that relates to such matters and the Meeting will proceed only after appropriate limitation of such discussions has been advised and agreed.

Proprietary Policy RTCA develops comprehensive, industry-vetted and endorsed recommendations for the regulatory authorities and the aviation community on issues ranging from technical performance standards to operational concepts for air transportation. Supporting this hallmark of RTCA foundational goals to procure consensus for recommended performance standards, the preferred and highly endorsed method for producing RTCA documents is to do so without reference to proprietary information. Although this type of reference in an RTCA document is not prohibited per se, it is limited to those circumstances where the objective of the document cannot reasonably be attained without the reference(s). Before incorporation into an RTCA document, three tests must be met: 1) A bona fide, public interest basis for the reference and/or usage 2) Evidence that private pecuniary interests have not driven any decision to either include or exclude a system from the market 3) A commitment to license the relevant technology, patent, patent pending, or copyrighted material by completing a Commitment to License (CtL) Early in the development of an RTCA document, if proprietary information is identified as relevant, the participant or the proponent must disclose to the SC leadership and/or Work Group (WG) leadership that they are personally aware that proprietary information is proposed and/or required for compliance with the RTCA document being developed. The content of an RTCA published document is considered RTCA proprietary information. Individuals can request to reference this information by receiving approval from RTCA President. By providing material to the RTCA document, the providing party grants RTCA the nonexclusive, paid-up, worldwide perpetual license Participation in a meeting (including participation via conference telephone or via web cast or similar remote means) shall be deemed to authorize the meeting secretary to record that this proprietary policy has been communicated and accepted.

RTCA Committee Participation Membership Policy To participate on RTCA Committees, an individual s organization is required to be a member of RTCA. Individuals from non-member organizations may apply for membership on a committee, and if accepted, will be required to become an RTCA member. Individuals from Non-RTCA member organizations may attend Committee Plenary meetings that are announced on the web. Non-member attendees have the option of requesting permission to be recognized to speak during the plenary meeting. Meeting summaries and related information from previous plenary meetings will be available to the public via RTCA s website. Documents undergoing final review can be obtained by contacting RTCA. Members of the public may also submit comments on documents undergoing final review.

Sign-in sheets are located outside the door Please sign in via the roster, or Provide your contact details on the new member sheet Facility Layout RTCA Receptionist (Suite 910) Can help with any questions Can summon IT support Meeting tips Please remember to use your microphones Press and release once to activate/deactivate. Do NOT hold the button down The maximum number of mics on at one time is 5 if drops occur, check the number of active mics

Agenda Item 1-B: Welcome New RTCA President and CEO Captain Terry McVenes

Agenda Item 2A: Review / Approve Meeting Summary September 20, 2018 RTCA Paper No. 250/PMC-1813

Agenda Item 2B: Review / Approve Administrative SC TOR Revision SC-135 New Chairman Company and New Secretary SC-209 New Co-Chairman

Agenda Item 3A: Committee Enhanced Flight Vision Systems and Synthetic Vision Systems (EFVS/SVS) SC-213 PMC Meeting December 1, 2018 RTCA Paper No. 281-18/PMC-1820

Committee Membership SC-213 Leadership Co-chairs Patrick Krohn Tim Etherington Government Authorized Representative Trent Prange RTCA Program Director Rebecca Morrison Secretary Thea Feyereisen

Committee Membership SC-213 Participants Avionics manufacturers: Rockwell Collins, Honeywell, Elbit Systems, Thales Group, Latecoere, Esterline CMC, Sierra Nevada Corp, Universal Avionics, Garmin, GE Aviation Aircraft Manufacturers: Airbus, Boeing, Bombardier Aerospace, Dassault, Lockheed Martin, Government: FAA, Transport Canada Airlines: ALPA, Fedex

Document Description This document contains Minimum Aviation System Performance Standards for a Combined Vision System for Helicopter Operations. While RTCA DO-315x / EUROCAE ED-179x and DO-371 / EUROCAE ED-249 documents are not specialized for a particular type of platform or mission, they were mostly written with fixed-wing platforms and operations in mind. The present document is oriented specifically towards helicopter platforms and operations. It defines performance standards for CVS over head down and transparent displays, which intended function is to provide a supplemental view of the external scene and visual references to the pilot. Such a CVS does not provide additional operational credit and is not intended to change the helicopter s existing operational capability or certification basis.

Final Review and Comment Summary Comments Received 131 Editorial 111 Low 86 Medium 13% 21% 8% 27% 31% Editorial Low Medium High Non-Concur 54 High 34 Non-concur 21 from FAA 9 from Honeywell 4 from Boeing All comments either resolved or withdrawn

Non-Concur DO-375 Inputs Definition of Intended Functions (13) Intended functions proposed for IFR flight were deemed not relevant (except for approach/landing) and withdrawn. Others has been clarified to precise the expected situational awareness benefit. Miscellaneous definitions (2) Minimum performances (7) Some proposed requirements where not considered as minimum. It has been made clear that the expected performances are to be determined in accordance with to the intended function. When appropriate, examples of values are indicated for information only. Complements and Clarifications (12) Other 'non-concur' were related to clarifications deemed necessary to avoid misunderstanding.

Conclusions The Committee recommends that the document «Minimum Aviation System Performance Standards for a Combined Vision System for Helicopter Operations.» be published in its current final form The EUROCAE Council is currently reviewing the document for publication as it is a joint document with WG-79 Publication is expected the first week of January

Agenda Item 3B: Aeronautical Databases SC-217 PMC Meeting December 13th, 2018 RTCA Paper No. 282-18/PMC-1821

Committee Membership SC-217 Leadership Co-chairs Brian Gilbert Stephane Dubet Government Authorized Representative Brad Miller RTCA Program Manager Rebecca Morrison Secretary Sasho Neshevski

Committee Membership SC-217 Participants Avionics manufacturers: CMC, Collins, Garmin, GE Aviation, Honeywell, Universal Aircraft Manufacturers: Airbus, Boeing Data Providers: Jeppesen, Lufthansa Systems, Navblue Government: DGAC, FAA, US Air Force International organizations: EASA, EUROCONTROL, Other: JACOBS, MITRE

Document Description Purpose : industry requirements for navigation databases information requirements for users industry recommended basis for Data Quality Requirements (DQRs) to facilitate end user development in support of an intended function Navigation data originators, navigation data providers, and application integrators are expected to use this document when providing those data to system designers and/or users. Scope of this revision Overview of PBN and SWIM concepts in relation to navigation data New applications and related data needs Addition of a Data catalogue Expansion of DQRs New guidance on procedure design and coding

Final Review and Comment Summary Comment Distribution 115 Editorial 58 Low 35 Medium 14% 6% 9% 24% 47% Editorial Low Medium High Non-Concur 16 High 21 Non-concur 2 from EASA 19 from Lufthansa Systems All comments either resolved or withdrawn

Non-Concur DO-201B Inputs NCs were received from two reviewers: EASA and Lufthansa Systems EASA NCs were related to containing requirements and recommendations pertaining to aircraft manufacturers or systems, and not to the origination or processing of Navigation data LSY NCs were related to the data catalog and DQRs: Data elements being scoped to procedure level vs. segment level Consistency between Route vs. Procedure holding data elements Removal of redundant data elements Corrections to reference document sections Definition updates

Non-Concur DO-201B Inputs Comment # Organization Section Page Line # 65 EASA 1.6 5,6 all The title of the section AIRCRAFT EQUIPMENT INFORMATION VULNERABILITIES and the [NAV-D002] seems to be addressing requirement to the aircraft manufacturer. This is not supposed to be covered by this Standard. 68 EASA 2.2.4 14 775 [NAV-R003] is addressing a requirement of the RNP system, 108 Lido 4.1.3.1.2 49 Shouldn't this be segment information? 109 Lido 4.1.3.1.3 49 Shouldn't this be segment information? 110 Lido 4.1.3.1.4 50 Shouldn't this be segment information? 111 Lido 4.1.3.1.5 50 Shouldn't this be segment information? 112 Lido 4.1.3.2.2 50 Shouldn't this be segment information? 113 Lido 4.1.3.2.4 51 Shouldn't this be segment information? 114 Lido 4.1.3.2.5 51 Shouldn't this be segment information? Comment Suggested resolution Comment resolution by WG Remove any requirement which is not pertaining to the origination or processing of navigation data Accepted with modification - This section was only included at the request of RTCA, and is going to be removed after updated guidance from Rebecca. Accept by removing the whole section. Revisit all the document to Accepted with modification - requirement itself to be deleted, eliminate requirements at replace "shall provide" with "provides". in contradiction with the scope not system or aircraft level. The to address requirements for the one identified in this applications themselves comment is only example. Accepted - move into 4.1.3.4 (append to end) Accepted - move into 4.1.3.4 (append to end) Accepted - move into 4.1.3.4 (append to end) Accepted - move into 4.1.3.4 (append to end) Accepted - move into 4.1.3.4 (append to end) Accepted - move into 4.1.3.4 (append to end) Accepted - move into 4.1.3.4 (append to end) and add a new Additional consideration as follows: "This data element is applicable to Preferred Routes only."

Non-Concur DO-201B Inputs Comment # Organisation Section Page 119 Lido 4.1.3.6.2 59 For the Airway segments, a system was used to include a reference to a fix and a name. I propose to use the same concept. Comment Suggested resolution Comment resolution by WG 4.1.3.6.2 Holding Fix Accepted with modification - Add an Definition: Reference to the holding procedure fixadditional consideration to 4.1.3.6.2 Fix: Note: Differs from ICAO PANS-AIM definition clarity. References: ICAO Annex 15 App 1 ENR 3.6 Additional considerations/requirements: N/A 4.1.3.6.3 Name Definition: The coded designators or namecodes of significant point. [ICAO PANS-AIM] References: ICAO Annex 15 App 1 ENR 3.6 ARINC 424, Chapter 5, Section 5.13 "The holding fix may be derived based on source publication location." Remove Position data element 4.1.3.6.3 (remember to remove from DQR table also) Need to remove data catalog fields from 4.1.3.4.2 (From Point) and 4.1.3.4.3 (To Point) - retain definition only, but without "Definition" label. 135 Lido 4.1.5.1.9 73 Is a duplication of the "lines of minima", since the minima lines are provided elsewhere, i.e. 4.1.5.1.12.2, 4.1.5.1.13.2 and 4.1.5.1.14.2 136 Lido 4.1.5.1.10 73 Is a duplication of the "lines of minima", since the minima lines are provided elsewhere, i.e. 4.1.5.1.12.2, 4.1.5.1.13.2 and 4.1.5.1.14.2 Additional considerations/requirements: N/A Remove paragraph, add reference to ARINC 424, Chapter 5, Ref. 5.275 and 5.296 to each of the "Approach Type" paragraphs mentioned. Remove paragraph, add reference to ARINC 424, Chapter 5, Ref. 5.275 and 5.296 to each of the "Approach Type" paragraphs mentioned. Withdrawn Accepted - also remove 4.1.5.1.11, and remove these from DQR tables also Add the following text to Additional considerations for OCA, MDA, DA: "Landing visibility data elements were not included in this document due to the variability of how visibility requirements are applied and the lack of industry consensus in how to define visibility minimums." Remove data element presentation content from 4.1.5.1.12, 4.1.5.1.13 and 4.1.5.1.14

Non-Concur DO-201B Inputs Comment # Organisation Section Page 137 Lido 4.1.5.1.5 72 Aircraft Category on procedure level, I believe this is not required as the same data is added for the segment as well, see 4.1.5.2.2 138 Lido 4.1.5.1.15 78 According to the paragraph number, only one MSA can be provided per procedure, or at least, if more than one are provided, it can not be linked to the correct transition. Comment Suggested resolution Comment resolution by WG Remove 4.1.5.1.5 Accepted - need to move Additional considerations text down to 4.1.5.2.2 In the absence of a gouping on transition, suggest to either move to segment level, or add a link to the transition. Accepted - add Additional consideration stating: "If multiple MSA values apply to a procedure, each value shall [NAV-R011] be provided." 147 Lido 4.1.5.3.3 86 The CRC is part of the RTCA DO229, Remove this paragraph Appendix D FAS DB and therefore included completely in 4.1.5.3.1 150 Lido 4.1.5.4 87 This section would include every fix used in Provide a definition of 4.1.5.4 on any procedures? If this is correct, every line 4807? waypoint also used in the enroute section (4.1.3.5) and every Navaid (4.1.4) must be repeated under 4.1.5.4, except with different attributes? E.G. there is no name field. It seems that only "unnamed" terminal waypoints in ARINC 424 terms are intended to be included here, e.g. "D5.4 XYZ", "Crossing R-270", according the references in 4.1.5.4.1. References in 4.1.5.4.2 would indicate possibly any waypoint/intersection (ARINC 424 EA and PC records), and 4.1.5.4.4 again would indicate also navaids. Where would unconnected fixes be handled which are used for tactical vectoring? Accepted - remember to remove from the DQR table also Accepted - add statement in 4.1.5.4 describing that it is not meant to supersede or duplicate data elements in Navaid and Waypoint sections: "The data elements in this section are not intended to supersede or duplicate data elements in Section 4.1.3.5 Waypoints or Section 4.1.4 Navaids. When used as a Procedure Fix, data quality requirements may differ from those defined in the Waypoint or Navaid tables." Also, add the following footnote to Procedure Fix in Table 4-5: " 2 When a Waypoint or Navaid is used as a Procedure Fix, the DQRs in this table supersede those in Tables 4-3 and 4-4, respectively."

Non-Concur DO-201B Inputs Comment # Organisation Section Page 151 Lido 4.1.5.4.1 87 The ARINC 424 reference is to the naming rules that explain how to create a database identifier for ARINC 424 Waypoint (EA and PC records) if a location must be coded having no usable identifier according state source. Does this mean only unnamed waypoints are contained in this section? Comment Suggested resolution Comment resolution by WG Change ARINC 424 reference to: Accepted ARINC 424, Chapter 5, Ref 5.13 152 Lido 4.1.5.4.2 87 If only unnamed locations are included in 4.1.5.4, Remove paragraph, or move it to then this paragraph should be removed, because procedure segment. ATC reporting requirements are not required at unnamed locations. Also, the ARINC 424 reference is to a paragraph describing procedure legs, so it should be included in the procedure segment part, not at the fix part. 153 Lido 4.1.5.4.4 87 The above paragraphs would indicate more that it is waypoints only. This defeintion reads that also navaids are included. Please clarify 156 Lido 4.1.5.6.3 90 Is a Missed Approach Point Helicopter specific? Delete, or if the intention was to have this specificylly, include a text to specify. Withdrawn - superseded by comment resolution of 150 Withdrawn - superseded by comment resolution of 151 Accepted - delete this data element; remember to remove from DQR table as well

Comment # Organisation Section Page Comment 154 Lido 4.1.5.5 87 The section is very different from the enroute holding part. Non-Concur DO-201B Inputs Suggested resolution Copy the enroute holding section after evaluating the above comments Comment resolution by WG Accepted with modification - harmonize these 2 holding pattern sections as follows: Keep Identification, Fix, Inbound Track, Turn Direction, Arc Radius, Speed, Inbound/Outbound Indicator, and RNP from Enroute Keep Time, Distance, Minimum Altitude, and Maximum Altitude from Procedure Harmonize definitions and references between each of the sections: Identification - Keep Route definition, add reference to ICAO PANS OPS Vol II, Part II, Section 6, Chapter 1-1 to Route version Fix - Use definition and references from Route to fully replace those in IFP Inbound Track - IFP inherits Routes definition and references Turn Direction - IFP inherits Routes definition and references Arc Radius - IFP inherits Routes definition and references Speed - Definitions already the same; merge all references from both Routes and IFP in both locations Inbound/Outbound Indicator - Use definition from Routes, references already the same RNP - IFP inherits Routes definition and references and DQR values Distance - Inherit definition from IFP, merge all references from both Routes and IFP in both locations except A424 5.65 Time - Inherit definition from IFP, merge all references from both Routes and IFP in both locations except A424 5.64, and drop "Leg" from data element name (remember to change in DQR table also), make expected resolution 0.1 min for both Minimum Altitude - Change definition in both Routes and IFP to: "Minimum holding level or altitude of the holding procedure. Note: Differs from ICAO PANS-AIM Incomplete", keep references only from Routes in both places, change name of both element to "Minimum Holding Level/Altitude" (remember to change in DQR table), and change Accuracy value to "DV (Altitude: 1 ft, FL: 50m or 100ft)" in both DQR tables Maximum Altitude - Change definition in both Routes and IFP to: "Maximum holding level or altitude of the holding procedure. Note: Differs from ICAO PANS-AIM Incomplete", keep references only from Routes in both places, change name of both element to "Maximum Holding Level/Altitude" (remember to change in DQR table), and change Accuracy value to "DV (Altitude: 1 ft, FL: 50m or 100ft)" in both DQR tables See 119 for explanation why Position is not being kept

Conclusions The SC-217 Committee requests the PMC to approve DO-201B for publication requests that publication be deferred until the ICAO Doc 10066 (PANS-AIM) is published suggests that SC-217 is on hiatus for at least 1 year, until further assessment of the need to develop new standards, e.g. data for UAS/drones/ new entrants (e.g. autonomous vehicles, vertical take off and landing vehicles, etc.) data driven charting to update existing standards (DO-200B, DO-201B, DO-272D, DO-276C, DO-291C, DO-342) to synchronize DO-201() with ARINC 424 ()

Agenda Item 3C: 406MHz Emergency Locator Transmitters (ELT) SC-229 PMC Meeting December 13, 2018 RTCA Paper No. 283-18/PMC-1822

Committee Membership SC-229 Leadership Co-chairs Thomas J. Pack (ACR Electronics) Philippe Plantin de Hugues (BEA) Government Authorized Representative Charise Green - FAA RTCA Program Director Rebecca Morrison Secretary Stuart Taylor (HR Smith)

Committee Membership Avionics manufacturers: ACR Electronics ELTA OROLIA HR Smith ACK Technologies Inc. Radiant Power Corp Honeywell DRS Astronics DME LLC Garmin Ltd Cobham Aerospace Communications L-3 Communications WS Technologies Inc. Thales Group Hensoldt Sensors GmbH Aviation Safety Supplies Ltd Aviage Systems Airlines: Alaska Airlines Aircraft Manufacturers: Boeing Airbus Embraer Dassault Aviation COMAC America Government: Federal Aviation Administration (FAA) European Aviation Safety Agency (EASA) National Oceanic and Atmospheric Administration (NOAA) Air Force Rescue Coordination Center (AFRCC) U.S. Coast Guard (USCG) Bureau d'enquêtes et d'analyses (BEA) Nation Transportation Safety Board (NTSB) NASA Transport Canada International Cospas-Sarsat Programme DGAC (La Direction générale de l'aviation civile) National Research Council of Canada International Air Transport Association

Document Descriptions MOPS DO-204b 406MHz ELT 16 Joint Plenary Sessions US and Europe Two rounds of Pre-FRAC and then a successful FRAC Updated RTCA DO-204b and Harmonized with EUROCAE ED-62b MOPS Addresses: ELT Crashworthiness NASA R&D and Installation Considerations GNSS specifications and Return Link Service (RLS) Conferred with SC-159 Power Sources Primary Lithium 2 nd Gen ELTs (MEOSAR) In Flight Triggered ELT(DT) for GADSS Inter-committee Request (ISRA) to Update DO-227 Primary Lithium Battery MOPS RTCA SC-235 updated and published DO-227a EUROCAE WG-98 Inflight Trigger Criteria ED-237 MASPS FOR CRITERIA TO DETECT IN-FLIGHT AIRCRAFT DISTRESS EVENTS TO TRIGGER TRANSMISSION OF FLIGHT INFORMATION; Published February 2016 EUROCAE Input to Cospas Sarsat Cospas Sarsat created the Distress tracking Correspondence Working Group Transmission characteristics of inflight ELT operation incorporated in C/S T.001, T.018 NASA Publication NASA/TM 2017-219584 Emergency Locator Transmitter Survivability and Reliability Study Crash testing of aircraft and significant simulation.

Final Review and Comment Summary Comments Received 400 Editorial 101 Low 73 Medium 19% 13% 0% 26% 42% Editorial Low Medium High Non-Concur 49 High 1 Non-concur Embraer (FRAC) All comments either resolved or withdrawn

FRAC: Non-Concur DO-204B Inputs Comment 325 Submitted by an Airframe MFG Subject: non-commanded deployment for the ELT system shall be 10-7 FH The contributor felt that probably should be more stringent (10-9 FH) for an Automatic Deployable ELT in certain situations. Resolution: A conference call was setup with the contributor, who had not attended any previous plenary sessions. The rationale for the existing text was outlined and discussed based on past work for of the FDR ED-112 working group. The contributor understood the background and acknowledged that the test in the MOPS could remain as written. The NC was withdrawn.

Conclusions The leadership and members of SC-229 have successfully completed their work as outlined in the Terms of Reference. The team respectfully requests that the RTCA PMC approved the DO-204b MOPS as written. Request that the SC-229 remain in an active monitoring mode. The triggered in flight ELT as originally conceived in the ToR, evolved into the ELT(DT), a solution for ICAO GADSS Autonomous Distress Tracking (ADT). With the ADT mandate approaching in 2021, the SC-229 provides a forum to capture additional work or changes as ADT implementations, test cases, and methods of compliance are encountered. Meet with WG-98 to propose a schedule for meeting over the next year to be available for change requests to DO-204b. Maximize participation by collaborating with other industry meetings ( EUROCAE, AEEC, Cospas-Sarsat to foster involvement and facilitation of the discussion.

Agenda Item 3D: DO-363 Change 1 Delayed until March 2019 PMC

Agenda Item 4: ICC Report to the PMC None for December 13, 2018

Agenda Item 5: CCC Report to the PMC None for December 13, 2018

Agenda Item 6A: DO-374 Changes Prior to Publication Rebecca Morrison, RTCA Program Director

Agenda Item 6B: ICC and CCC Charters Dr. George Ligler, ICC Chairman And Clay Barber, CCC Chairman

Agenda Item 6C: Annual Review of ICC and CCC Membership Dr. George Ligler, ICC Chairman And Clay Barber, CCC Chairman

ICC Membership Dr. George Ligler, ICC Chairman Clay Barber, Garmin Bob Hekl, MITRE Karan Hofmann, RTCA Bob Lee, Collins Aerospace (Replacing RH) Darrell Pennington, ALPA Ron Stroup, FAA 42

CCC Membership Ed Hahn, ALPA Bob Lee, Collins Aerospace (replacing RH) Abe Roman, U.S. Army Melissa Rudinger, AOPA Ron Stroup, FAA Jessie Turner, The Boeing Company Jeff Woods, NATC 43

Agenda Item 6D: Suggested Mapping And CM in Coordination with ICAO Al Secen, RTCA Vice President, Aviation Technology and Standards

Agenda Item 6E: Investigate feasibility of providing redlined version of completed documents Clay Barber, PMC Member and Al Secen, RTCA Vice President, Aviation Technology and Standards

Agenda Item 7A: SC-159 TOR Revision Dr. George Ligler SC-159 Co-Chairman

Agenda Agenda Item 7B: SC-186 Automatic Dependent Surveillance Broadcast (ADS-B) Terms of Reference Rev. 22 Update RTCA Paper No. 275-18/PMC-1817 Jessie Turner The Boeing Company SC-186 Co-chair Copyright 2012 Boeing. All rights reserved. RTCA PMC December 13, 2018

SC-186 Terms of Reference Rev. 22 Changes DELIVERABLES - Deleted Revisions to to clarify deliverable name for DO-260C, DO-282C, DO- 317B Change 1, and DO-317C (Chris Hegarty s comment to Rev. 21 TOR update at Sept. 2018 PMC meeting) - Identified additional tasks required for Aircraft Surveillance Applications (ASA) MOPS (DO-317C) and changed due date from Dec. 2019 to Feb. 2020 Document rationale for using existing Horizontal Figure of Merit (HFOM) metrics for surface applications Update to TCAS bearing validation Correct CDTI Assisted Visual Separation (CAVS) test scenario/vector errors Develop and update the ADS-B velocity error model and Traffic Situational Awareness with Alerts (TSAA) test vectors, as appropriate ENVISIONED USE OF DELIVERABLE(S) The text was revised to show the additional ASA MOPS tasks identified above. ALL PROPOSED TOR CHANGES WERE APPROVED TO MOVE FORWARD TO THE PMC AT THE 70 TH SC-186 PLENARY HELD NOV. 2, 2018 Copyright 2012 Boeing. All rights reserved.

Agenda Item 7C: Committee Enhanced Flight Vision Systems/Synthetic Vision Systems SC-213 TOR Update PMC Meeting December 13, 2018 RTCA Paper No. 285-18/PMC-1824

Committee Membership SC-213 Leadership Co-chairs Tim Etherington Rockwell Collins Patrick Krohn Universal-Elbit Designated Authorized Representative Trent Prange RTCA Program Manager Rebecca Morrison Secretary Thea Feyereisen - Honeywell

Committee Membership SC-213 Participants Around 30 in attendance Avionics manufacturers: At least 5 in active participation Aircraft Manufacturers: 5 in active participation Including Airbus and Boeing Government: Multiple and active participation by EASA, FAA, and NASA Airlines: Occasional participation from ALPA and airline representatives

Document Discussion Terms of Reference Revision 11 DO-315 captured SVS/EVS/EFVS/CVS for current operations DO-315A captured operations to 1000 RVR and use below 100 feet DO-315B captured SVS for Credit DO-341 Captured EFVS down to 300 RVR DO-359 Captured SVGS for Credit DO-371 Captured EFVS for Takeoff DO-375 in approval for CVGS for Helicopters

Document Discussion Terms of Reference Revision 12 Consolidate all guidance material for SVS into one MASPS Consolidate all guidance material for EVS/EFVS into one MAPS Clarify CVS with a place in both documents depending on which source is primary for operational concepts New MASPS will not obsolete current DO guidance No identified need for MOPS

Document Discussion Terms of Reference Revision 12 Aligns work with envisioned AC and eliminates circular references Provides better guidance material as the committee discovered there are more similarities than differences when applied to different operational concepts Facilitates better alignment and incorporation of additional CONOPS

Conclusions RTCA SC-213 recommends continuing work with the two new documents and PMC approving the revised TOR. Additional Guidance material on operations between 1000 RVR and 300 RVR may be developed.

Agenda Item 7D: Standards for Air Traffic Data Communications Services SC-214 PMC Meeting December 13, 2018 RTCA Papers No. 286-16/PMC-1825 Chuck Stewart, SC-214 Chair

Summary of SC-214 TOR Revision 11 SC-214 Plenary #29 approved Revision 11 of SC-214 Terms of Reference (TOR) on September 20, 2018 Revise completion date to modify DO-224E (MASPS) and DO-281D (MOPS) from Apr 2019 to Dec 2020 Add development of new Document DO-XXX to define expected behavior to implementations of Ground Systems providing VDL M2 capability. Editorial revision of text to improve description of VDL M2 connectionless capability and remove text associated with completed deliverables that have been approved for publication at PMC in Sep 2018

Agenda Item 7E: Committee Name SC-216 PMC Meeting Dec 13, 2018 RTCA Paper No. 287-18/PMC-1826 David Pierce, SC-216 Chair

Committee Status SC-216/WG-72 Participants Leadership Dave Pierce, SC-216 Chair Siobvan Nyikos, Secretary Varun Khanna, Government Authorized Representative Karan Hofmann, RTCA Program Director Cyrille Rosay, WG-72 Chair Clive Goodchild, WG-72 Secretary Anna Guegan, EUROCAE Director Technical Programme Participants Around 146 participants from multiple industry stakeholders 1 Plenary to discuss TOR revision and consensus

Activity between April and December Plenary Held a telecons to discuss SC-216 response to new WG- 72 TOR having 4 new deliverables Committee has provided feedback that there is no need to revise DO-355, proposed changes are helpful to the document but not necessary but Committee also wants to remain harmonized Additional telecon discussion simply repeated the same theme and resulted in formal response to WG-72 about our concern with the documents Discussion among SC-216 leadership indicated that we should become active again as the best way to maintain some harmonization

December 4, 2018 Plenary Distributed revised TOR with 2 deliverables The TOR is revised to allow revision of DO-355 to maintain harmonization Information Security Event Management document is less well defined, SC-216 would prefer to borrow much of the processes from current safety reporting, WG-72 intentions seem to lean toward creating a whole new process Received unanimous consensus from committee to request approval from PMC for revised TOR

SC-216 TOR Deliverables Work DO-355 revision with WG-72, with SC-216 placing emphasis on keeping scope to ARAC ASISP Report and notes from DO-356 revision Generate a new Information Security Event Management document for publication, with emphasis placed on borrowing from current processes where possible

The Ask SC-216 unanimously requests PMC to approve the Revised TOR and Joint work with WG-72 Questions?

Agenda Item 7F: Review / Approve SC-228 TOR Revision PMC Meeting December 13, 2018 RTCA Paper No. 228-18/PMC-1827 John R. Moore and Paul McDuffee, SC-228 Co-Chairmen

Motivations for Current TOR Revision Revision 5 was approved at March 2018 PMC meeting It was noted that the changes had not been formally discussed and approved by SC-228 in Plenary session. One key stakeholder had concerns over some specific wording that might imply a broader scope than intended, and that had not been properly reviewed. PMC directed SC-228 formally concur with the Revision 5 changes at a formal Plenary Session, including any applicable adjustments addressing the stakeholder concerns. Revision 6 was approved at June 2018 PMC meeting Editorial changes only (e.g. contact information of chairs). Discussions from Working Group 2 have led to some proposed refinements to Phase 2 scope of work and deliverables. A proposed revision 7 was discussed at SC-228 Fifteenth Plenary 12 July 2018 There was a non-concur from the floor from a key stakeholder, which led to a series of meetings leading to some proposed language to clarify the concerns. An updated proposed revision 7 was consensus approved at SC-228 Sixteenth Plenary meeting 13 September, 2018, with no dissenting voices. 12/13/2018 SC-228 TOR Revision 65

Summary of Proposed DAA Changes Remove reference to Part 91 operations in Class C/B airspace and explicitly differentiate between takeoff/landing and transit operations. This occurs in three places, characterized by the below example. 12/13/2018 SC-228 TOR Revision 66

New Language for DAA MOPS Scope Considerations for DAA MOPS Phase Two Development Experience with the development and implementation of standards reinforces the need to identify areas that require operational evaluation. For example, it is important that phase 2 equipment provide the necessary level of safety for use in all airspace, including the expanded scope of operations into Class B and C airspace. This is crucial because a target level of safety had not been identified nor defined for the DAA system. It must be clear that the standards would ensure that the system would adequately mitigate safety risks of the intended function. It is anticipated the FAA will establish the conditions under which DAA equipment would be sufficient for the intended operation in the National Airspace System (NAS). This may include policy and regulatory changes and the development of advisory materials for the use of the DAA equipment. It is anticipated that the DAA applicant would need to provide validating data that installed DAA equipment will meet its intend performance goals within a given operational environment (i.e. class of airspace) including the validation of a fully functioning and continuously available command and control link (C2) to support the DAA system. This data should demonstrate that operations with a DAA system by a UAS will not degrade the level of safety of other NAS users. It is anticipated the FAA or other safety oversight organizations will conduct a comprehensive operational safety analysis (e.g. Safety Risk Management Panel). The outcome of this safety analysis will be used to determine required equipage and any necessary operational mitigations for the operational implementation of the equipment built based on the DAA MOPS, and subsequent issuance of airworthiness and operational approval. 12/13/2018 SC-228 TOR Revision 67

Summary of Proposed C2 Changes Change Phase 2 SATCOM standard type from MOPS to MASPS and integrate into a single release. There are significant technology / implementation differences (particularly in Ku) in current systems. There is significant concern that any attempt at generating a single MOPS may not be sufficient to permit a create an appropriately scoped TSO. Anticipate applicants will cover SATCOM performance as part of aircraft level certification supported by this MASPS rather than equipment qualification through a TSO. Remove some left over language on a networking standard that was missed with that document was removed a few TOR cycles previously. 12/13/2018 SC-228 TOR Revision 68

Proposed C2 Language Change 12/13/2018 SC-228 TOR Revision 69

Proposed C2 Deliverables Changes Move from technology-specific SATCOM MOPS to technology-agnostic SATCOM MASPS Integrate requirements to enable both Ka and Ku into a single release of the document. Delay schedule for one year (which aligns to the original schedule for the combined document. 12/13/2018 SC-228 TOR Revision 70

Agenda Item 7G: Terrain Awareness and Warning System (TAWS) Lou Volchansky, PMC GAR December 13, 2018

Proposed Committee Federal Aviation Administration Addressing TAWS Inhibit Function Presented to: By: Date: RTCA PMC Lou Volchansky 13 Dec 2018 RTCA Paper No. 304-18/PMC-1838 Federal Aviation Administration

Background Terrain Awareness and Warning System (TAWS) continues to be a valuable tool in reducing controlled flight into terrain (CFIT) However, within the past three years, the air taxi operations in Alaska experienced aircraft losses and fatalities due to CFIT Federal Aviation Administration 73

NTSB Safety Recommendations NTSB Safety Recommendation A-17-035 asked the FAA to: Implement ways to provide effective terrain awareness and warning system (TAWS) protections while mitigating nuisance alerts for single-engine airplanes operated under 14 Code of Federal Regulations Part 135 that frequently operate at altitudes below their respective TAWS class design alerting threshold. NTSB Safety Recommendation A-18-015 asked the FAA to: Modify the terrain awareness and warning system requirements in Technical Standard Order C151 such that, once the alerts are manually inhibited, they do not remain inhibited indefinitely if the pilot does not uninhibit them. Federal Aviation Administration 74

General Aviation Joint Safety Committee GA JSC Controlled Flight Into Terrain (CFIT) Working Group (WG), Safety Enhancement (SE) 9, Output 2: Develop software or hardware solution to un-inhibit TAWS based on time or other appropriate variables in order to minimize the amount of time that TAWS safety benefits are unavailable. FAA to provide approval path for incorporation of auto uninhibit capability. (TSO function, Non-TSO function, STC, Amended STC, etc.) Federal Aviation Administration 75

Request The Federal Aviation Administration (FAA) requests RTCA review National Transportation Safety Board (NTSB) accident reports, recommendations from the General Aviation Joint Safety Committee (GAJSC) CFIT working group, and the current TAWS standard. After reviewing NTSB Safety Recommendations, please determine whether RTCA/DO-367 needs to be updated to prescribe more current system inhibit requirements and TAWS envelope protections, based on current part 135 operating rules Federal Aviation Administration 76

Observations Perhaps no single solution, but is there a suitable combination: Use of Class C TAWS (lower min terrain clearance), Auto-uninhibit, or Reconfiguration of forward looking field of regard Does a new TSO feature best address this issue? Even with a new standard, how best to promote equipage? Federal Aviation Administration 77

Agenda Item 7H: Helicopter Terrain Awareness and Warning System (HTAWS) Lou Volchansky, PMC GAR December 13, 2018

Agenda Item 7I: Discussion FAA Actions on Previously Published Documents RTCA Paper No. 289-18/PMC-1828 Lou Volchansky, PMC GAR December 13, 2018

FAA Published Guidance (Since Previous PMC) RTCA Document Developed By FAA Guidance Approval Date Comment DO-257B, MOPS for the Depiction of Navigational Information on Electronic Maps SC-227 TSO-C165b 28 Nov 2018 Supports updated requirements for the electronic display of an RNP system s outputs IAW DO-236C and DO- 283B. Updates embrace new display technologies and revised human factors considerations.

RTCA Published Documents FAA Pending Guidance RTCA Document Developed By FAA Guidance Planned Release Date Comment DO-311A, MOPS for Rechargeable Lithium Batteries and Battery Systems DO-227A, MOPS for Non- Rechargeable Lithium Batteries SC-225 AC 20-184A December 2018 SC-235 AC 20-192 December 2018 Installation standard for rechargeable lithium batteries Airworthiness installation criteria for non-rechargeable lithium batteries DO-315A, DO-359, MASPS for Synthetic Vision Guidance System, MASPS for Aircraft State Awareness Synthetic Vision Systems SC-213 AC 20-185A December 2018 Consolidates synthetic vision, synthetic vision guidance system, and airplane state awareness guidance DO-315A, MASPS for EVS, SVS, CVS, EFVS SC-213 AC 20-167B January 2019 TSO-C63f January 2019 Consolidates enhanced and combined vision system airworthiness criteria. No new criteria. Aircraft weather radar design approval guidance. DO-220A, Change 1, MOPS for Airborne Weather Radar Systems SC-230 AC 20-182B March 2019 Aircraft weather radar installation guidance. Likely reference for DO-213A, Change 1, MOPS for Nose-Mounted Radomes

Multiple RTCA data comm references from AC 20-140C (see last page of this file) DO-372, Addressing Human Factors/Pilot Interface Issues for Avionics DO-362, Command and Control Data Link MOPS DO-365, Detect and Avoid MOPS Phase I. DO-366, MOPS for Air-to-Air Radar for Traffic Surveillance DO-343A MASPS for AMS(R)S Data and Voice Communications Supporting Required Communications Performance and Required Surveillance Performance SC-214 AC 20-140D February 2019 SC-233 AC March 2019 SC-228 AC 20-187 March 2019 SC-228 AC 20-DAA June 2019 SC-222 None at this time N/A Incorporates clarification memo from Dec 2017 and policy for partial FANS-1/A installations Best practices, informational AC (00- HF) Airworthiness C2 installation guidance. Airworthiness installation of a UAS DAA system Update for SATCOM Performance Class B supporting RCP130 including ground gateway-to-aircraft gateway VPN capability

DO-368, MOPS for GPS/GLONASS (FDMA + Antenna) L1-only Airborne Equipment DO-246E, GNSS- Based Precision Approach Local Area Augmentation System Signal-in- Space Interface Control Document DO-253D, MOPS for GPS Local Area Augmentation System Airborne Equipment DO-356A, Airworthiness Security Methods and Considerations SC-159 None at this time SC-159 None SC-159 TSO-C161b and TSO-C162b September 2019 SC-216 AC September 2019 This document is a reference for DO-253D. It is published by RTCA for the convenience of avionics OEMs. VDB issue being resolved in MOPS. Will incorporate updated GAST-D design standard to support Category II/III operations; maintenance updates to legacy standards. Supports Special Conditions

DO-370, Guidelines for the In Situ Eddy Dissipation Rate (EDR) Algorithm Performance DO-373, MOPS for GNSS Active Antenna in the L1/E1 and L5/E5A Bands DO-230I, Standards for Airport Security Access Control Systems New MOPS to Specify the ACAS X a System and ACAS X a/o Functionality (Class 1 ACAS X & Class 2 ACAS X) SC-206 TBD N/A N/A SC-159 TSO TBD SC-224 N/A N/A SC-147 TSO November 2019 AC February 2020 New TSO. (Need updated interference environment, estimated Q4CY2019) Provides guidance on acquiring and designing systems, testing and evaluating system performance, and operational requirements. Incorporates the latest technological advances. Adds a credentialing operational checklist. Performance standard and installation guidance for Class 1 ACAS X (basic collision avoidance functionality) and Class 2 ACAS X (closely spaced runway operations and do not alert)

SPR for Vision Systems for Takeoff DO-281C, MOPS for aircraft VDL Mode 2 Physical Link and Network Layer SC-213 None N/A SC-214 TSO 2021 Establish safety case for the takeoff operation. SC-214/WG-92/AEEC DLK recommends the MPS defined in TSO/ETSO-C160a not be revised until publication of DO-281D/ED-92D planned in late 2020.

RTCA Documents Pending PMC Approval RTCA Document Developed By Planned FAA Guidance Planned Release Date Comment DO-204B MOPS for 406 MHz ELTs (406 MHz Emergency Locator Transmitters (ELTs)) SC-229 TSO-C126c March 2019 Updated design guidance for ELTs DO-201B User Requirements for Navigation Data SC-217 AC 20-153B Change 1 September 2019 Specifically updates navigation data quality requirements (DQRs). (ICAO PANS-AIM Data Catalog, Doc 10066, publication date unknown.) Recommend Doc 10066 publication precede DO-201B posting. MASPS - Combined Vision System for Helicopter Operations SC-213 AC 20-167C December 2020 CVS installation guidance for helicopters (for situation awareness)

DISCUSSION

Agenda Item 7J: Discussion Special Committee Chair Reports RTCA Paper No. 290-18/PMC-1829 Rebecca Morrison, RTCA Program Director December 13, 2018

Current Document Reviews SC-236/WG-96: MASPS for WAIC Closed SC-228: C2 MOPS update Closed SC-223/WG-108: Document will Open in January SC-222/WG-82: 2 Documents Open until January SC-206: Document will Open in January 89

Agenda Item 7K: Report on RTCA / EUROCAE Cooperation to PMC RTCA Paper No. 291-18/PMC-1830 Rebecca Morrison, RTCA Program Director December 13, 2018

New Documents Released by EUROCAE since Last PMC Standard Title Working Group ED-240A Minimum Aviation System Performance Standards (MASPS) for Remote Tower Optical Systems Date of Publication WG-100 November 2018 ED-357/ DO-374 Safety Performance and Interoperability Requirements Document Defining Takeoff Minima by Use of Enhanced Flight Vision Systems. WG-79/SC-213 October 2018 ER-019 Inputs to RPAS AMC 1309. WG-105 October 2018 ED-92C/ DO-281C Minimum Operational Performance Standard (MOPS) for an Airborne VDL Mode-2 System Operating in the Frequency Range 118-136.975 MHz WG-92/SC-214 September 2018 91

EUROCAE/RTCA Coordination Meeting November 13-14, 2018 Hosted by RTCA Attendees: Dr. Chris Haggerty, chair of the Program Management Committee (PMC) for RTCA, Eric Bouchard, chair of the Tactical Advisory Committee (TAC) for EUROCAE. Christian Schleifer, Secretary General for EUROCAE, Al Secen, Vice President of Aviation Technology Standards for RTCA, Anna Von Groote, Director Technical Programme for EUROCAE, Rebecca Morrison, Program director for RTCA and Sergiu Marzac, Technical Programme Manager for EUROCAE Steve Brown and Terry McVenes also participated Agenda Covered: Discuss the status of the joint programs Presentations on the work that is being done by EUROCAE and RTCA which is non-joint Discussion of specific emerging technologies Review of Memorandum of Cooperation 92

EUROCAE Meetings in 2018 TAC#76 15-16 January 2019, St Denis, France TAC#77 24 April 2019, Toulouse, France 93

DISCUSSION 94

Agenda Item 7L: RTCA Drafting Guides Update Karan Hofmann, Program Director December 13, 2018

Agenda Item 8A: SC-222 AMS(R)S Terms of Reference Revision Request E.F.C. LaBerge, SC-222 Chair RTCA Program Management Committee December 13, 2018 RTCA Paper No. 277-18/PMC-1818 96

Changes to Terms of Reference part 1 Request from Inmarsat, Cobham and Honeywell DO343/ED242 MASPS to update Appendix B to reflect new frequency and power plan for ATCt. DO262/ED243 MOPS to set the terminal spec for SBB terminals for LTE and ATCt resilience DO210 MOPS as Change 5 to set the terminal spec for Classic Aero terminals for LTE and ATCt resilience SC-222 Work on these changes to be complete by December 2019 The November 8 Plenary Approved these changes to the ToR and delegated the wording changes to LaBerge (SC222) / Schlereth (WG82) / Hoffman (RTCA) SC-222 Approved FRAC for MASPS & MOPS for Dec-Jan. Addition editorial changes to table of documents 97

Changes to Terms of Reference part 2 Slight slip in delivery of DO-343B and DO-262D from December 2018 to February 2019 FRAC and Open Comment (Eurocae) is currently in progress on joint documents. Iridium needs to slip by a year, so the wording of items 1) 2) 3) and 4) needs to change. 98

ToR as agreed Unfortunately we missed a few things In particular, the listed documents don t meet the Change vs. Rev number requirements adopted by PMC and Iridium is about a year late, and we forgot DO-210D, Ch 5 99

Editorial changes are in red First column changes comply with PMC guidance Second column changes reflect current Iridium schedule The new documents (3,4,7) are still due in Dec 2019 1) and 2) are currently in FRAC 100

Agenda Item 8B: UTM Discussion Al Secen, RTCA Vice President, Aviation Technology and Standards

Agenda Item 8C: Spectrum Considerations for Aviation Standards Andrew Roy Director of Engineering Aviation Spectrum Resources, Inc. RTCA Paper No. 303-18/PMC-1837 13 Dec 2018 www.asri.aero 102

Scope ICAO policy developments on spectrum Considerations for aviation standards Radio altimeter interference Questions? 13 Dec 2018 www.asri.aero 103

Aviation Spectrum in the US - Recap HF 3-30 MHz VHF 30-300 MHz UHF 300 MHz -3 GHz SHF 3-30 GHz Communications 13 Dec 2018 Navigation Surveillance Supporting Systems www.asri.aero 104

ICAO Spectrum Policy ICAO revising its spectrum policy document ICAO Spectrum Handbook (Doc 9718) Contains ICAO guidance and positions for aviation spectrum ICAO Frequency Spectrum Management Panel (FSMP) initiated rewrite Current document has evolved by committee Splitting existing volumes into more relevant sections Need to apply lessons identified in recent spectrum management activities 13 Dec 2018 www.asri.aero 105

Handbook Rewrite Aiming to make the material more accessible to the reader Often referenced by aviation to protect systems in spectrum discussions Used as a resource by many non-aviation organizations Review of characteristics for ICAO systems Provide all relevant aviation standards for each ICAO system Identify what systems are missing characteristics or parameters Guidance for spectrum in aviation standards Agreement in principle that ICAO should have some guidance to help protect future aviation spectrum Exact implementation has yet to be agreed 13 Dec 2018 www.asri.aero 106

Discussions on Spectrum in Aviation Standards Design complexity vs spectrum usage What are we trying to protect against in the future? How much is enough? What is credible/meets international regulations? Need to fully understand all the relevant the RF parameters of aviation systems Much of the potential spectrum issues are for the adjacent band Full picture that does not leave any ambiguity Assumptions made by manufacturers need to be clear Ability to reference aviation standards in different forums Ability to use different IP in such forums Deconflict different specifications for the same systems 13 Dec 2018 www.asri.aero 107

Radio Altimeter Interference High level of interest in changing the 3.7-4.2 GHz band from SATCOM to 5G US FCC initiated rulemaking proceedings prompted by Congress Radio altimeter operates in the adjacent 4.2-4.4 GHz Adjacent band altimeter RF performance an unknown Theoretical studies indicate high possibility of interference AVSI testing now benchmarking existing avionics to grandfather in performance in ICAO SARPs Short timeline to influence FCC with results Many aviation interests have recommended an FAA assessment 13 Dec 2018 www.asri.aero 108

Summary ICAO policy review on spectrum an ongoing process FSMP meetings planned for Jan and Aug 2019 Consultation needed from standards group to ensure it is practical and accurate Aviation standards will become increasingly important to defend aviation spectrum Should be a complete documentation of all RF elements Including adjacent band operations Radio altimeters an ongoing concern Uncertain outcome at this stage 13 Dec 2018 www.asri.aero 109

Questions? 13 Dec 2018 www.asri.aero 110

Backup Slides 13 Dec 2018 www.asri.aero 111

Regulatory Example of Spectrum Principles FCC has requested comment on Spectrum Principles proposal Still in the whitepaper phase Nine specific guidelines to assist in sharing spectrum Both transmit and receive functions accounted for Build resilience for both current and future spectrum environment Fully disclose the relevant standards Receivers are responsible for mitigating interference outside their assigned channels Use techniques at all layers of the stack to mitigate degradation from interference Minimize transmit energy outside their assigned channels Plan for occasional service degradation or interruption (and not base rules on exceptional events). 13 Dec 2018 www.asri.aero 112

Agenda Item 8D: RTCA SC-159 December 13, 2018 RTCA Paper No. 298-18 PMC-1832 WG2C Appendix F Justification GNSS aided Inertial systems

Background: From SC-159 WG2C Plenary Summary The group favors keeping appendix F with integration method examples Safran has stepped up to do what was required by them to allow their contribution to be included WG2C will provide the justification to the PMC meeting in December as requested December 2018 RTCA SC-159 WG-2C 114

Justification (1) The justification pertains to appendix F titled INTEGRATIONS METHODS in the new MOPS for GNSS aided inertial systems The FAA (Jeff Meyers) acknowledges that the appendix helps provide context at certification Numerous method are described that help the reader see what already have been considered (prevents reinvention of the wheel) and informs the certification agency what has been investigated as part of the MOPS development The existence of methods capable of meeting the requirements in section 2 provides credibility to the MOPS December 2018 RTCA SC-159 WG-2C 115

Justification (2) It would be unreasonable to specifically exclude a participants authorized example since the RTCA rules allowed inclusion of patented material in examples if it was authorized If the RTCA rule had been stating from the start that no patented methods can be in examples (no exceptions) then all such examples would have been taken out but to leave to the group to exclude a participants authorized example is not a workable plan. December 2018 RTCA SC-159 WG-2C 116

Agenda Item 9: Next Meeting Documents SC-147 (Likely to be delayed): New Document MASPS for Collision Avoidance System Interoperability SC-186: DO-317B Change 1 MOPS for Aircraft Surveillance Applications (ASA) System SC-223: New Document Aviation Profiles for Internet Protocol Suite 117

Agenda Item 9: Next Meeting SC-222: Documents (continued) DO-343B AMS(R)S Data and Voice Communications Supporting Required Communications Performance (RCP) and Requied Performance (RSP) DO-262D MOPS Avionics Supporting Next Generation Satellite Systems SC-228: New Document C2 Link Systems MASPS 118

Agenda Item 9: Next Meeting Documents (continued) SC-234 (Originally): DO-363 Change 1 Guidance for the Development of Portable Electronic Devices (PED) Tolerance for Civil Aircraft SC-236: New Document MASPS for Coexistence of Wireless Avionics Intra-Communication within 4200-4400 MHz 119

Future Meetings PMC: March 21, 2019 June 27, 2019 September 12, 2019 December 19, 2019? 120

December Action Item Review 121

ADJOURN 122

BREAK TIME Back at: 10:05

LUNCH RETURN AT 12:10 EDT 124