1. NMHS and Airline Responsibilities for AMDAR Programme Implementation & Operation Mexico AMDAR Regional Workshop, 8-10 November 2011 Dean Lockett Observing Systems Division, WMO

2. Content 1.Obligations in developing an AMDAR Programme. 2.Requirements for activating an AMDAR Programme. 3.Obligations for maintaining an AMDAR Programme. 4.Contracts and Agreements.

3. NMHS Obligations in Commencing an AMDAR Programme Ascertain suitability of airline and aircraft: –Generally larger airlines with fleets of 10+ aircraft; –Modern aircraft with suitable avionics: see AMDAR Panel Avionics Survey document. –VHF or Satellite Communications (ACARS). –Aircraft and sensors maintained. Determine fleet requirements for required coverage: See airline route coverage maps See airline schedules

4. USA AMDAR/MDCRS Programme - around 1600 aircraft Courtesy of NOAA/ESRL/GSD

5. European AMDAR Programme (optimised) - around 600 aircraft Courtesy of NOAA/ESRL/GSD

6. Australian AMDAR Programme (optimised) - around 70 aircraft Courtesy of NOAA/ESRL/GSD

7. NMHS Obligations in Commencing an AMDAR Programme Ensure funding available for: –Software development and certification; –Engineering costs for software implementation; –Ongoing communications costs. –Consider optimisation. Develop a Business Case. Contact airline: –Chief pilot; –Flight operations manager; –Head of Engineering Maintenance; –CEO (maybe);

8. Obligations for Activating an AMDAR Programme – Contract /Data Agreement Contract or agreement between NMHS and Airline should be implemented: Meet WMO Resolution 40: Data and products to be exchanged without charge and with no conditions on use: … (3) All available aircraft reports, e.g. data in AMDAR, AIREP codes, etc.; … Preferably, Airline to allow Met. Service ‘ownership’ or joint-ownership of non-airline data. Ensure that data agreement allows use of the data for mandated responsibilities and GTS transmission. NMHS to ensure non-meteorological airline corporate data not divulged as required.

9. Obligations for Activating an AMDAR Programme – Contract /Data Agreement Liability issues: –NMHS should not be responsible for liabilities associated with aircraft function (even related to AMDAR software): Airline responsible for software certification and function. –Airline should not be responsible for liabilities associated with AMDAR data use: NMHS responsible for data quality assurance. Costs: –Generally accepted that costs borne by NMHS should be incremental to Airline: Incremental costs for implementation of software (and sensors); Incremental costs for communications.

10. Obligations for Activating an AMDAR Programme Software: –Developed and implemented to required standard: ARINC 620 Meteorological Report AAA (ACARS ACMS AMDAR) specification –Certified –Gound-tested (e.g. Teledyne Controls) –Flight-tested…

11. Obligations for Activating an AMDAR Programme Software Flight Testing: –Data received…in correct format; –Data quality ok: Check met. parameters against radiosonde, numerical weather model output; Positional information ‘makes sense’; Reports made at expected intervals and frequency.

12. Obligations for Activating an AMDAR Programme Communications links established: –Air-to-ground provided by VHF or Satellite using ACARS (or other) protocols. –VHF comms requires VHF ground network provision. –Gound-to-ground Data Service Provider required. –International DSPs usually SITA or ARINC but other local providers may be utilised. –Messages can be direct to Met. Service or relayed via Airline (other protocols possible such as email, FTP etc).

13. Obligations for Activating an AMDAR Programme Met. Service Data Processing Centre Established: –Reception of messages from Data Service Provider. –Decode messages. –Quality control processes in place (See AMDAR Reference Manual). –Re-encode in format for GTS (FM 42 or BUFR). –Transmit on GTS. –Ability to ‘blacklist’ an aircraft. –Monitor data.

14. Obligations for Maintaining an AMDAR Programme - NMHS Operate a Quality Management System Carry out data quality assurance: –Automated real-time checking. Routine monitoring: –Compare with other upper air systems (radiosonde, NWP, inter-aircraft); –Reports from international monitoring centres; –Identify systemic processing and sensor errors... Maintain AMDAR metadata.

15. Obligations for Maintaining an AMDAR Programme - NMHS Sensor Monitoring:

16. Obligations for Maintaining an AMDAR Programme - NMHS Issues to be reported to the Airline: –Temperature sensor drift; –Faulty accelerometer (large unrealistic values of vertical gust); –Positional errors; –Data processing errors; –Data loss.

17. Obligations for Maintaining an AMDAR Programme - NMHS Maintain metadata: –Record of data quality issues (by aircraft, date/time); –Aircraft lists (by identity, model, type); –Aircraft Sensor details when available; –Software updates and changes; –Software configurations; –WMO in the process of establishing standards.

18. Obligations for Maintaining an AMDAR Programme - Airline Install software into avionics systems; Assist in flight testing process; Ensure avionics systems updates do not disable or adversely affect AMDAR; Allow use/ownership of data for NMHS mandated purposes; Endeavour to rectify sensor issues (within operational constraints); Provision of metadata; Costs at reasonable (incremental) levels.

19. Thank you.