1 / 7

SC214/WG78

SC214/WG78. OSA/OPA Team Outbrief. D-RVR. OSD: Reviewed during conduct of OSA/OPA Proposed Changes: Clarify advisory basis and reliance on controller RVR issuance during landing Curtail service during critical phases of flight as is done for D-HZWX

gary
Download Presentation

SC214/WG78

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. SC214/WG78 OSA/OPA Team Outbrief

  2. D-RVR • OSD: Reviewed during conduct of OSA/OPA • Proposed Changes: • Clarify advisory basis and reliance on controller RVR issuance during landing • Curtail service during critical phases of flight as is done for D-HZWX • Periodic Reports to be optional (demand, event, and event/periodic) • Addition of overall min/max thresholds (for all airports) • Add range/resolution for request message parameters (currently missing) • OSA: Reviewed on Tuesday • Changes: • All hazards now SC5 – given service stop at final approach fix (FAF) and hereafter standard decision height and controller issued advisory procedures are in effect • Removed pilot EMM at decision height – service stops at final approach fix • OPA: Reviewed Thursday • Given OSA results, all requirements now operationally driven • Performance like D-OTIS, except for integrity (now only ops driven for D-RVR) • Actions: Analyses of performance for given/planned implementations required to update allocations.

  3. RCP Timing Allocations • D-RVR OPA review resulted in general discussion regarding RCP timing allocations • Concerns over practicality of CSP and Avionic allocations • Concerns over differences between OCR RCP allocations and SC214 Continental Applications • Decision • Attempt to get more practical timing responses from each component representative (ground, CSP, avionics) with rationale for desired allocated – THEN – see how that might impact overall RCP performance • Actions: Assess CPDLC and FIS delays (priority on CPDLC) • CPDLC Timing Assumption: 2KB msg (DM122 or UM266) containing 64 WPT route information with CPDLC application in the FMC • Note – for CSP assessment, will need to add aircraft count, ATS and AOC message traffic assumptions • FIS Timing Assumption: 20KB msg with DFIS application in FMC

  4. Oceanic Integration Status • Safety Requirements • CPDLC SR Comparison: Completed • SC214 to DO306 • Used to develop ‘commonly’ worded requirements • Identified missing requirements (orphans in one or other document) • ADS-C SR Comparison: TBD • ADS-C for Continental only evaluated in context of 4DTRAD which is N/A for oceanic use • Performance Requirements • RCP Timing Comparison: Completed • Assessing changes in component allocations • Considering reduction in quantity of Continental RCP types

  5. Oceanic Integration – Work Needed (1/2) • PR Service provided with AOC • Needed for Continental Airspace? • Is AOC in scope? – Currently included in draft Rev I • No AOC technical allocations in DO-306 – is AOC compliant with SR/PR requirements? • DSC Service • Needed for oceanic, is it needed for continental (ENR?, TMA?, APT?) • OSD and continental and oceanic OSA/OPA needed • FLIPINT (ADS-C not part of 4DTRAD) • OSD and continental OSA/OPA needed before convergence with DO-306 SR/PR • New OCR Needs (New Messages) • New OCR needs will be defined by ICAO-ATM & CNSG Task Force(e.g., OCL/DSC, ADS-C) • Requires OSA/OPA assessment

  6. Oceanic Integration – Work Needed (2/2) • Different Views on OSA Integration • Some wants to have one common SRs in Mainbody, without OHA results (OHs, Effects) comparison and no Tracebility, using Table of Comparison  Incomplete OSA for OCR • Originally: Not only copy SRs, but also incorporation of OCR OHA results for completeness • Environmental/RCP Templates • Should resolve Environment and RCP template approach before further ‘formatting’ incorporation work of OCR SR/PR • Opportunity: Update of OCR OPA items ?? • Concern with existing allocations, e.g., RCP240 flight crew response requirement is 60s at 99.9% (not achievable?) • Ground performance for AOC supported PR may not be achievable

  7. Recommendations/Next Steps • D-HZWX: Defer OSA/OPA until after OSD and associated FIS application is more stable • Oceanic Integration: Defer further document integration until most/all of the following items are addressed/matured: • RCP Template and associated SR/PR requirement presentation • Environment Section • FLIPINT OSD (ADS-C standalone application) is drafted with SC214 OSA/OPA • AOC/PR role clarified • DSC OSD is drafted • Obtain plenary approval over common SR/PR requirement approach • D-RVR: Update OSD, OSA, and OPA based on this week’s work and have revised content for Plenary #11 • Note – OSA/OPA material can be integrated into Rev I draft, but content could be impacted by FIS/Prague meeting outcome • Focus on Rev H OSA/OPA validation progress (VSG activities) • Focus on Rev H Comment/PDR resolution

More Related