1 / 7

Presented by Rich Rawls The Boeing Company

SC-214 Sub Group 1 Plenary 2 Report Out Brussels Oct 2-4, 2007 Development of SPR for D-HIWAS, D-FLUP, PPD, ITP M&S C&P, PAIRAPP. Presented by Rich Rawls The Boeing Company. Summary of activities. SG-1 conducted 5 Teleconferences (8-1, 8-15, 8-29 & 9-12) Discussions included D-HIWAS

gwen
Download Presentation

Presented by Rich Rawls The Boeing Company

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SC-214 Sub Group 1Plenary 2 Report OutBrussels Oct 2-4, 2007Development of SPR for D-HIWAS, D-FLUP, PPD, ITP M&S C&P, PAIRAPP Presented by Rich Rawls The Boeing Company

  2. Summary of activities • SG-1 conducted 5 Teleconferences • (8-1, 8-15, 8-29 & 9-12) • Discussions included • D-HIWAS • D-FLUP • PPD • ITP

  3. Datalink Hazardous In-flight Weather Advisory Service (D-HIWAS) formally known as D-SIGMET • STATUS: Team needs to complete definition of the Operating Method after Plenary concurrence of the following recommendations. • Identified the presence of Special Committee (SC-206) which is also addressing Weather Services • Action: SC-214 Plenary or possibly PMC needs to coordinate allocation Roles and responsibilities for SC-214 and SC-206 related to Weather Services. • D-HIWAS features lack detailed requirements • Use of CPDLC Free Text to convey D-HIWAS information creates excessive Crew Workload and Confusion and may not be technically possible from the airplane side • Recommend removal of Phase 1 implementation D-HIWAS functionality • D-HIWAS should be implemented as a Flight Information Service (FIS) Message rather than a CPDLC message • Remove CPDLC reference in the D-HIWAS Service description

  4. Datalink Flight Update (D-FLUP) • STATUS: Team needs to complete definition of the Operating Method after Plenary concurrence of the following recommendations • Use of CPDLC Free Text to convey D-FLUP information creates excessive Crew Workload and Confusion and may not be technically possible from the airplane side • Recommend removal of Phase 1 implementation D-HIWAS functionality. • D-FLUP should be implemented as a combination of Flight Information Service (FIS) Messages and AOC messages rather than a CPDLC message • Remove CPDLC reference in the D-FLUP Service description • D-FLUP data exchange should be initiated and defined by the Flightcrew. • An Uplink could be used to identify what data is available. • Information could be encoded with a designator similar to D-ATIS

  5. Pilot Preference Downlinks (PPD) • STATUS: Team needs to complete definition of the Operating Method after Plenary concurrence of the following recommendations • PPD transmission should be executed by the Pilot rather than by Avionics. Data could be populated by the Avionics prior to Pilot transmission. • Remove reference to broadcast transmission. • The PPD Dialogue needs to a Closure Message added when the Pilot determines that the preferences are no longer relevant but he does not have a follow-on preference d/l.

  6. In-Trail Procedures (ITP), Merging and Spacing (M&S) and Crossing and Passing (C&P) • We reviewed the IPT with the assumption that the comments would be relevant to all 3 services. • STATUS: Team needs to complete definition of the Operating Method after Plenary concurrence of the following recommendations. • The ITP service seems to be dependent on ADS-B IN. • These are ADS-B features and implementation should be in conjunction with or completed by the ADS-B subgroup. • The Operating Method currently only requires that the trailing aircraft be aware of and ITP activity. There is concern within the SG that both aircraft in the ITP procedure need to be advised.

  7. General Comments • Is it this Special Committee’s responsibility for correlation and resolving conflict between this SPR and the DO-290 SPR. • The Sub-Group is currently working on completing the Operating Method section of the following functions prior to proceeding with the SPR. Target agreement on Operating Method by Plenary #3. • D-HIWAS, D-FLUP, PPD, ITP, M&S, C&P and PAIRAPP. • Sub-Group needs additional Pilot and Airline input for the proposed new functions. • Need Plenary concurrence that FIS messages be removed from the CPDLC dialouge.

More Related