1 / 24

OSWG

A056 update. OSWG. Mark Patterson, Aviation Safety Inspector FAA, AFS-470. 9 March 2016. FAA A056 Project. Oct 2012 - item 2012-02 opened P lan – update AC/templates; Part 129 OpSpec determination Feb 2014 - Initiated project within DCIT and PARC CWG

roypadilla
Download Presentation

OSWG

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. A056 update OSWG Mark Patterson, Aviation Safety Inspector FAA, AFS-470 9 March 2016

  2. FAA A056 Project • Oct 2012 - item 2012-02 opened • Plan – update AC/templates; Part 129 OpSpec determination • Feb 2014 -Initiated project within DCIT and PARC CWG – Due to domestic data comm implementation timelines • Limited scope revisions (oceanic and domestic data link) • Advisory Circular (AC) 120-70B • OpSpec/ MSpec / LOA templates • Inspector Guidance / Job aid • FAA training modules

  3. FAA A056 Project – Accomplishments • 7 May 2015 – FAA Published Notice 8900.297 • New templates • compliance date: • 12 June 2015 - Parts 121, 125, 135, 91K • 11 Sep 2015 - Part 91 (due to operator / inspector work load) • 3 Aug 2015 – FAA Published AC 120-70C

  4. FAA A003 project - Accomplishments Decision - Part 129 not required new OpSpec • A003 would be used • CAA data link approval / authorization • May 2015 - FAA Published Notice 8900.303 • Revised A003 template • Compliance date: 15 November 2015

  5. FAA recommends closing item 2012-02

  6. FAA recommends opening new A056 item Nov 2016 - NAT plans to implement Performance- based Communication and Surveillance (PBCS) • Along with an RNP requirement, RCP / RSP prescribed for certain services (e.g. RLatSM) FAA data commmaterial needs revised • New AC 90-[PBCS] • OpSpec, MSpec, LOA template revisions • Inspector Guidance / job aid

  7. FAA Data Comm Project – Next Steps Sept 2016 – New AC 90-[PBCS]: • Align FAA policy with ICAO PBCS, including data link (CPDLC and ADS-C) and initial SATVOICE provisions • Initial compliance for operational approval (RCP / RSP) • Continuous performance monitoring (RCP / RSP) • AC 120-70C incorporated (AC 120-70C will be canceled) • PBCS, FANS 1/A, ATN B1, B2 (as available), PDC • Satellite voice (SATVOICE) • Streamlined application process for Part 91 operators • OpSpec/ MSpec / LOA template revisions • Additional guidance / procedures / training material

  8. FAA Data Comm Project – Next Steps Template revisions - table • Add RCP / RSP authorization (400;240;130? / 180) • More avionics capabilities/information (e.g. VDLM0/A/2, software loads, SATVOICE, HFDL) • ICAO aircraft type / ICAO operator identifier • Satellite service provider (INMARSAT, Iridium, etc) • Registration number (in addition to M/M/S)

  9. FAA Data Comm Project – Next Steps Template revisions – verbiage • Authorization to use of data comm where available • No longer a distinction of within vs. outside U.S. • Requirement to use appropriate flight plan codes for RCP/RSP/SATVOICE, etc • OEM software update documentation statements • CSP/Stored Data/SIM Card agreements • Problem Reporting process • Performance Monitoring process

  10. Review of DRAFT Part 121 A056 OpSpec

  11. Review of DRAFT Part 91 A056 LOA

  12. Areas still being developed • Initial PBCS compliance • Performance monitoring • Part 91 streamlined A056 application process

  13. FAA Domestic Data Comm update - Ground • CPDLC-DCL trials complete; transition to operational • Implementation waterfall • Service now operational at 10 airports • SLC, IAH, HOB, MSY, AUS, SAT, SDF, IND, EWR, JFK • End of March add: LAX, LAS, LGA, TEB • By end of 2016: 56 airports planned (total) • Part 91 – no authorization required • Part 91K/121/125/135 – must be annotated in A056 • Part 129 – must be annotated on A003

  14. FAA Domestic Data Comm update – En Route • Fall 2015 – En route trials completed • 2019 - En route services operational

  15. QUESTIONS?

  16. Back-up slides

  17. Monitoring / Compliance possibilities • Current A056 holder • Monitoring program established / identified • Monitoring data reviewed (by fleet) • Good performance - RCP240 / RSP180 authorized • Bad performance - limited to RCP400 / RSP400 • New A056 applicant • Monitoring program established / identified • Initially authorized RCP400 / RSP400 • Monitored until XXX data points verify meeting performance • Credit may be given for same equivalently equipped types • Data drives performance authorization

  18. Initial RCP/RSP Approval - Existing Data Link Approvals(proposed) Using historical operational data – ACP assessed against RCP240 and ASP assessed against RSP180for all operator aircraft types / fleets (distinguishing between different avionics configurations) • At least 100 data points required • If ACP meets at least RCP180 95% and ASP meets at least RSP240 95%: • Operator / aircraft type granted approval for RCP240 / RSP180 • Operator notified to indicate approval status in flight plan • Field 10 → “P2” • Field 18 → “SUR/RSP180” • If ACP does not meet RCP240 95% and / or ASP does not meet RSP180 95%: • Operator / aircraft type granted approval for RCP400 / RSP400 • Operator notified to indicate approval status in flight plan • Field 10 → “P1” or “P3” • Field 18 → “SUR/RSP400” • Operator informed they may still use CPDLC / ADS-C but only for RCP400 / RSP 400 ops • If ACP does not meet RCP240 99.9% at better than 99.0% and / or ASP does not meet RSP180 99.9% at better than 99.0% → operator notified

  19. Initial RCP/RSP Approval - New Data Link Applications(proposed) • Approval exists for same type aircraft (identical configuration) • Operator may be provisionally granted approval for RCP240/ RSP180 • Approval does not exist for same type of aircraft (identical configuration) • Operator / aircraft type granted approval for RCP400 / RSP400 • Once 100 data points accumulated • ACP assessed against RCP240 95% and ASP assessed against RSP180 95% • Depending on results -- Authorization (OpSpec, Mspec, LOA) updated accordingly • Operator notified to indicate approval status in flight plan • Field 10 → “P1”; “P2” or “P3” • Field 18 →“SUR/RSP400” or “SUR/RSP180”

  20. Monitoring / Compliance possibilities • Operator monitoring “program” or “process” • POC identified • Possible FAA website - operators can retrieve compliance info • Proactive investigations? – identify non-compliance issues prior to receiving FAA report (CSP collaboration, etc). • FAA data review (by operator fleet / equipage) • Operator / OEM / (POI) provided details to investigate • Depending on the issue, timeframe given to comply • After date, if still non-compliant - POI notified with latest details -- Possibly change OpSpec / MSpec / LOA • General aviation grouped by fleet • OEM involved in monitoring / investigating

  21. Continued Compliance --- PBCS Monitoring (proposed) Operators with A056 approvals • For all aircraft types (distinguished by avionics configuration) • Semi-annually -- ACP assessed against RCP240; ASP assessed against RSP180 • If determined beneficial, shorter timeframes could be used (eg. quarterly) • Default data set will be 6 months (ensures data currency) • In cases of smaller operations, larger data set will be used as available (1 year, 2 years, etc.) • If ACP does not meet at least RCP240 95% and/or ASP does not meet at least RCP180 95%: • Operator notified of performance deficiency using standardized form and supporting information • Operator given X months to demonstrate ACP of at least RCP240 95% and ASP of at least RSP240 95% • If performance does not improve to required levels: • Operator notified they may still use CPDLC and ADS-C • Approval changed to RCP400/RSP400 • Operator notified to indicate approval status in flight plan (“P” codes and Field 18) • Corrective action taken for incorrect filing of flight plan codes

  22. Aircraft Operator PBCS Monitoring Report – By Fleet Operator ABCDEFG Period 01 Jul to 31 Dec 2014 (6 months) à à FAA ZAK ANSP CTA à à RCP RCP 240 CPDLC Specification Appli cation à à 95% RCP 240 99.9% RCP 240 Color Key RCP PORT benchmark benchmark Transaction Meets criteria à ACP ACTP ACP ACTP PORT Counts (WILCO Under criteria but <=180 sec <=120 sec <=210 sec <=150 sec <=60 sec Received) above 99.0% à End - to - End - to - Pilot Under cri teria à Network Network End End response Aircraft type (ACT)/Equipment type (EQ) 4,362 99.1% 100.0% 99.4% 100.0% 97.1% A332 EQ1 801 97.1% 98.1% 98.1% 98.9% 96.4% B763 EQ1 5,180 98.8% 99.7% 99.2% 99.8% 97.0% Aggregate RSP RSP 180 ADS - C Specification Application à à 95% R S P 180 benchmark 99.9% R S P 180 benchmark Report Counts AS P % <= 90 sec AS P % <= 180 sec Aircraft type (ACT)/Equipment type (EQ) 172,738 98.8% 99.9% A332 EQ1 63,913 93.0 % 97.3% B763 EQ1 236,651 97.2% 99.2% Aggregate Sample operator monitoring report

  23. CPDLC-DCL A056 Ops Approval – Status As of 8 March 2016… A056 applications under review  56

  24. Review of DRAFT AC 90-datacomm

More Related