{"text_format":"1","workbook":"xlsx","n_sheets":2,"sheets":["Issue codes+recommendations","Under performing airframes"],"not_rendered":{"charts":0,"images":0,"macros":0,"external_links":0,"defined_names":0,"comments":0,"pivot_tables":0},"unopened":[],"bounds":{"document_bytes":16777216,"sheet_cells":100000,"rows_first":2000,"rows_last":500,"rows_between":2000,"halvings":0,"cell_chars":16384,"cell_head_chars":4096},"cells_cut":0,"cells_raw":0,"read":"whole","date_system":"1900"}

{"sheet":"Issue codes+recommendations","index":0,"n_rows":11,"n_cols":3,"rows_kept":11,"cut":false,"hidden":false,"merged":[]}
[]
["Issue code","Description","Recommendations that apply"]
["(*1)  Delayed reports around VHF/SAT or VHF/VHF transitions.","This issue code is used when ADS-C or CPDLC reports are observed with delays when there is mixed media usage or transitions between stations/paths within the same media, in the sequence of reports before, at or after the delayed reports (ex.: VHF/VHF/SAT/VHF/SAT).","(1) Review \"NAT OPS Bulletin 2019_003: Data Link Performance Improvement Options\" and recommended solutions/actions (Problem/Issue #2).\n"]
["(*2)  Delayed reports via HF media.","This issue code is used when delayed ADS-C or CPDLC reports are observed to be delivered via HF data link (HFDL) or near reports delivered via HFDL. Check whether this appears to be a SATCOM failure with one flight or a period during the flight, or more continuous, intermittent use of HFDL. Potential issue with aircraft media priority settings.","(2) Review \"NAT OPS Bulletin 2019_003: Data Link Performance Improvement Options\" and recommended solutions/actions (Problem/Issue #1, #4, #9).\n(3) Review all Service Information Letters (SILs) and Software Bulletins (SBs) released from Satcom avionics manufacturers, particularly advice on Operator Requirement Table (ORT) set-up.\n(4) Operator should be aware that HFDL DOES NOT meet the RCP/RSP criterias for PBCS operations.\n"]
["(*3) Delayed reports due to Inmarsat satellite to satellite transition (aircraft) or satellite problems (network). ","This issue code is used when ADS-C or CPDLC reports are observed with delays and its noticed that there is a switch sequence between different or same Inmarsat satellite paths (Ex.:  XXF/XXH/XXF/XXH). One known area where this occurs in the NAT is at 30W longitude. If multiple aircraft observed with same issue around same time, may be a network-related issue and ATSP may want to report to FANS-CRA/DLMA.","(3) Review all Service Information Letters (SILs) and Software Bulletins (SBs) released from Satcom avionics manufacturers, particularly advice on Operator Requirement Table (ORT) set-up.\n(5) Check with contracted Data Link Service Provider and Satellite Service Provider for possible coverage problems.\n"]
["(*4) Delayed reports due to Iridium avionics (aircraft) or satellite problems (network). ","This issue code is used when ADS-C or CPDLC reports are observed with delays via Iridium satellite paths (IG1, IGW1). If multiple aircraft observed with same issue around same time, may be a network-related issue and ATSP may want to report to FANS-CRA/DLMA.","(6) Check for SATCOM radio/unit problems.\n"]
["(*5) Reported only on VHF and/or HF.","This issue code is used when delayed ADS-C reports or CPDLC messages are observed via VHF and/or HF only (no SATCOM). This might indicate that SATCOM unit is defective or became unavailable during flight. Check if this issue is observed during one flight or part of one flight only, or whether it is an ongoing problem. If not observed on subsequent flights, the issue may have been addressed.","(7) Operator should not declare PBCS if SATCOM not available.\n(6) Check for SATCOM radio/unit problems.\n(8) Flight crew should inform ATC if SATCOM becomes unavailable during flight.\n"]
["(*6) Poor ACP due to high PORT.","This issue code is used when its found that the delayed CPDLC transactions are caused by high pilot operational response time (PORT).","(9) Review \"NAT OPS Bulletin 2019_003: Data Link Performance Improvement Options\" and recommended solutions/actions (Problem/Issue #6).\n(10) Review procedures to reduce pilot operational response time (PORT) to CPDLC messages.\n"]
["(*7) Aircraft data link connection problems detected.","This issue code is used when we can identify that delays happened on periods that disconnections and reconnections have been performed. Check whether this appears to be a problem with one flight or a period during one flight, or whether it is an ongoing problem. If problem is not observed on later flights, the issue may have been addressed.","(11) Review \"NAT OPS Bulletin 2019_003: Data Link Performance Improvement Options\" and recommended solutions/actions (Problem/Issue #8 unknown cause).\n"]
["(*8) Delays related to specific VHF station.","This issue code is used when the delayed ADS-C reports and CPDLC messages are observed via a specific VHF ground station. If multiple aircraft observed with same issue, ATSP may want to report to FANS-CRA/DLMA as a VHF station issue.","(1) Review \"NAT OPS Bulletin 2019_003: Data Link Performance Improvement Options\" and recommended solutions/actions (Problem/Issue #2).\n"]
["(*9) FMS time before ATC uplink time.  Clock setting not syncronized with GPS. ","This issue code is used when its found that the FMS response time is earlier than the ATC uplink time. According to aircraft manufacturers this happens when clock is set manually and not being set by synchronization with GPS source.","(12) Review procedures for clock settings to be set to GPS clock instead of manual set of clock.\n"]

{"sheet":"Under performing airframes","index":1,"n_rows":18,"n_cols":13,"rows_kept":18,"cut":false,"hidden":false,"merged":[[6,0,6,3],[7,0,7,3],[8,0,8,3],[11,4,14,4],[11,5,14,5],[11,1,14,1],[11,0,14,0],[11,2,14,2],[11,3,14,3],[11,6,14,6],[11,7,12,7],[11,8,14,8],[11,12,14,12],[4,0,4,12],[3,0,3,12],[2,0,2,12],[0,0,1,12],[5,4,5,12],[6,4,6,12],[7,4,7,12],[8,4,8,12],[9,4,9,12],[10,0,10,12],[11,11,14,11],[11,9,12,9],[11,10,14,10],[9,0,9,3],[5,0,5,3]]}
["PBCS ATSP Under Performance Report Form "]
[]
["All airframes in this report filed P2/RSP180 in the reporting period"]
["For queries/questions or updates on corrective actions based on a previous reports, please contact the ATSP with all relevant details, including relevant dates, using the emails provided."]
["See explanations and recommendations concerning issue codes in the orange-colored tab."]
["Report Date:",null,null,null,"dd/MM/yyyy"]
["Period of observed under performance:",null,null,null,"<Month> yyyy - <Month> yyyy"]
["Reporting Air Traffic Service Provider (ATSP):",null,null,null,"<ATSP>"]
["Contact email address(es) at Reporting ATSP:",null,null,null,"<email list>"]
["Reporting to Regional Monitoring Agency (RMA):",null,null,null,"<RMA>"]
["PBCS Data"]
["FIR","STATE OF REGISTRY (Optional)","3-Letter Operator ICAO CODE","Airline Operator","4-letter ICAO Aircraft Type","Registration","ADS-C downlink Message Counts","95% RSP 180 Benchmark","CPDLC Transaction Counts","95% RCP 240 Benchmark","# Flights in Period","Issue code(s)","Notes from the ATSP (optional)"]
[]
[null,null,null,null,null,null,null,"ASP",null,"ACP"]
[null,null,null,null,null,null,null,"<=90 sec",null,"<=180 sec"]
["<FIR CODE>","<STATE>","<CODE>","<OPERATOR NAME>","A123","A123BC",123,"91.19%",60,"89.58%",9,"(*1) (*3) "]
["<FIR CODE>","<STATE>","<CODE>","<OPERATOR NAME>","B456","DE456F",99,0.94189999999999996,45,0.70199999999999996,4,"(*4) "]
["<FIR CODE>","<STATE>","<CODE>","<OPERATOR NAME>","A789","GH789I",75.668173416809097,"91.19%",26.661288444619469,"89.58%",9,"(*6)"]