A ERO M ÉXICO

1. AEROMÉXICO AMDAR REPORT Learning Experience Ing. Gerardo Méndez November 2011

2. 16-03-11 AeroMexico was invited to participate in the AMDAR Project with CONAGUA, SMN, SENEAM and ARINC. 23-03-11 AeroMexico’s Technical Division officially initiated the evaluation of aircraft system capabilities to meet AMDAR requirements. 02-05-11 AeroMexico develops the first prototype of AMDAR report, called version 1. 10-06-11 The first report was presented to CONAGUA – SMN – SENEAM and feedback was provided regarding the timing and parameters required. 01-07-11 AeroMexico developed a second prototype of AMDAR report according to the requirements and CONAGUA – SMN – SENEAM, but some data was still missing. 04-07-11 AeroMexico looked for support with the AMDAR team and Honeywell in order to solve, update and reconfigure the aircraft databases (ACARS y ACMS). 08-11-01 Finally, AeroMexico has a better product that was called Reporte AMDAR versión 3. Part of this technical experience will be presented by Reynaldo Valladares, AeroMexico’s Avionics Engineer . A learning experience….

3. AMDARAircraft Meteorological Data Relay Prepared by: Reynaldo Valladares López November 2011

4. AMDAR Implementation Process

5. Airframe Selection • B737-700 • Assigned mainly to domestic destinations • 293.1 flight hours per a/c per month • 157.8 cycles per a/c per month

6. Avionics Capabilities Validation Three units can be configured for creating and triggering the messages: • Communications Management Unit • Digital Flight Data Acquisition Unit • Flight Management Computer * Sensors, wiring and parameter broadcast to the 429 bus need to be available CMU / MU DFDAU FMC

7. Message Configuration

8. On-ground Applications ARINC Ground Network Ground Stations ARINC Processor AeroMexico’s ACARS TrafficFlow ARINC Air/Ground Network

9. Top of Climb (TOC) Top of Descent (TOD) Taxi Take-Off Departure En Route Approach Land Taxi 60 sec interval to ON 6 sec interval to 90 secs from OFF 20 sec interval to 510 secs to TOC 3 min. interval to TOD Recommended ARINC 620 Reporting

10. Parameters to be Reported

11. Optional Parameters that can be Considered • Water Vapor Mixing Ratio • Turbulence • Icing These values won’t be reported by AM’s a/c as the fleet is not equipped with the required sensors; aircraft would need to go through a retrofit for installing said sensors.

12. Message Characteristics WXM FI FF1234/AN AAAAAA DT DDL SSS 999999 A99A - 02E07SSSSSSSSA99999A99999999999999A999999999A AA99999A99999999999999A999999999A AA99999A99999999999999A999999999A AA99999A99999999999999A999999999A AA99999A99999999999999A999999999A AA99999A99999999999999A999999999A A

13. Parameters Acquisition FLT No. DEST DEP SAT PA SW Baseline AOC DB SW Baseline FMC CMU WX report enabled in ACARS AOC DB LAT LON DFDAU / ACMS VHF ADC • Issues: • Static Air Temperature – Available in take off phase only • Pressure Altitude – Not available in all phases 429 Bus

14. AOC & ACMS DB SW Modification FLT No. DEST DEP SW Baseline AOC DB SW Baseline FMC LAT LON SAT PA VHF CMU DFDAU / ACMS ADC • Static Air Temperature – Always available • Pressure Altitude – Available 429 Bus

15. ACMS DB SW Customization FDAMS ACMS Reconfiguration Tool Broadcast Output: • SAT Output added from ACMS to ACARS • PA Output added from ACMS to ACARS

16. ACARS AOC DB SW customization ART 758/ATSU Reconfiguration Tool Broadcast Input: • SAT Input added from ACMS to ACARS • PA Input added from ACMS to ACARS

17. Modification Engineering and SW Installation to be scheduled upon completion of Message Configuration.

18. Questions? Thanks for your attention