Message Name:

FMS ANOMALIES INTERMITTENT FAILURES OR UNEXPECTED FMS BEHAVIOR

• One or more Flight Management System (FMS) erroneously calculate and display incorrect values for distance to destination or waypoint, estimated time enroute to destination or waypoint and estimated fuel remaining, etc
• Dashed-out predicted speed and altitude
• FMS not honoring Flight Plan or Chart; wrong sequencing of waypoints, turn in the wrong direction, improper speed, improper level off, etc
• FMS dropping from Dual to Single Mode, etc

It may happen during a flight, that crew faces a momentary FMS related problem. In those cases it may happen that neither a CAS message, a Flight Management System Control Display Unit (FMS CDU) scratchpad message, nor even no message can be assessed, due to a condition that was rapidly cleared or the message itself did not provide enough information. To better investigate these events, the FMS has an internal Random Access Memory (RAM) that records such events, which can then be downloaded for further analysis by Honeywell the avionics supplier.

Since this RAM memory is not large enough it gets overwritten quite rapidly, and therefore it is recommended to perform a FMS CNTL-D download onto a Upper Sideband (USB) memory stick.

The FMS CNTL-D download can be done in-flight without any effect on the FMS operation. Honeywell recommends that operators obtain the FMS CNTL-D files from the affected FMS or each of them during or immediately after the event, but no later than 20 minutes after the FMS problem occurred.

Unfortunately, due to the low capacity of the FMS RAM memory, in most cases, the FMS downloaded data does not provide usable data because the FMS data associated to that specific event had been overwritten and lost by the time the data is downloaded. This is why it's important to respect this 20 minutes timeline.

As a good practice, flight crews are encouraged to have an empty USB key in the proper FAT format on hand in order to perform FMS CNTL-D downloads. Since each FMS CNTL-D from either FMS CDU 1, 2 or 3 have their own unique file extension name, there's no need to carry more than one (1) empty USB key.

• For Dataloader DL-950 prior to MOD G; use 2G or less USB key with FAT format (FAT16)
• For Dataloader DL-950 MOD G or later; use any size USB with FAT or FAT32.

NOTE: Following feedbacks received from the fleet, USB sticks 4G and above with FAT32 should be preferred with Dataloader DL-950 with Mod G.

• Integrated Avionics Computer (IAC) 1 (A11)
• Integrated Avionics Computer (IAC) 2 (A10)
• Integrated Avionics Computer (IAC) 3 (A12)
• Integrated Avionics Computer (IAC) Battery

Advisory Wire/Service Bulletin:

• AW700-23-0578 - FMS CDU ‘ACARS DMU FAILED’ message observed post Batch 3.3
• AW700-23-0600 - "NEW MESSAGE AVAIL" alerting message on the FMS CDU scratchpad
• AW700-31-0473 - Integrated Avionic Computer (IAC) - No Fault Found (NFF) investigation Conclusions
• AW700-31-0647 - Batch 3.4 Software Upgrade - Availability and Update
• AW700-34-0241 - Data Loader DL-950 Loading Erratic
• AW700-34-0348 - Control Display Unit (CDU-820) - Intermittent Blanking Display and No Fault Found Update
• AW700-34-0449 - Post Batch 3 Upgrade - FMS Performance
• AW700-34-0470 - Pre and Post Batch 3 Upgrade - FMS - Speed Restriction Anomaly
• AW700-34-0481 - Post Batch 3, Batch 3.3 and Batch 3.4 Software Upgrade - FMS settings in FLIGHT CONFIG pages
• AW700-34-0486 - Pre and Post Batch 3 Upgrade - FMS - Change of Destination not allowed when first Leg in Missed Approach Procedure is Type ARC (AF or RF Leg)
• AW700-34-0487 - Flight Management System (FMS) - Duplicate Waypoints in Airway Portion of Aeronautical Operation Control (AOC) and Future Air Navigation System (FANS) Uplink Not Properly Defined
• AW700-34-0488 - Post Batch 3 Upgrade - FMS - Lateral Navigation (LNAV) drops to Roll Mode when aircraft sequences the first Heading to Altitude Termination (VA) Leg on a Standard Instrument Departure (SID)
• AW700-34-0500 - Pre and Post Batch 3 Upgrade - FMS - Control Display Unit (CDU) blanking or characters overlap caused by uplinked flight plan
• AW700-34-0502 - Pre and Post Batch 3 Upgrade - FMS - Lateral Navigation (LNAV) / Guidance issues commanding a turn in an opposite direction
• AW700-34-0507 - Post Batch 3 Upgrade - FMS - Melding of TO Waypoint with Common Waypoint in new Arrival
• AW700-34-0560 - Post Batch 3 and Batch 3.3 Upgrade - FMS - Fly Vectors to Intercept Leg Deleted Resulting in Incorrect Course on Control Display Unit (CDU)
• AW700-34-0561 - Flight Management System - Racetrack Pattern Entry with Course to Fix (CF-CF) Leg Types
• AW700-34-0580 - Flight Management System - Holding Pattern Speed Anticipation Function
• AW700-34-0590 - Post Batch 3 and Batch 3.3 Upgrade - FMS - Incorrect Ceiling Altitude Displayed
• AW700-34-0591 - Flight Management System - Not Honoring Speed Constraint When the TOGA Button is Activated on a Missed Approach and Aircraft is in GA Mode
• AW700-34-0603 - Pre and Post Batch 3 Upgrade - FMS - Incorrect placement of *INT waypoint results in the missing of the waypoint in departure

Forum Articles/Infoservice/Newsletter:

• Customer Forum & Newsletter-Volume 11, Issue 23 (November 18, 2014) - USB Memory Stick for Download of FMS CNTL-D at right time “Timing is important”
• Customer Forum & Newsletter-Volume 12, Issue 07 (April 7, 2015) - Periodic Erase/Download of the IAC NVM Data
• Customer Forum & Newsletter-Volume 13, Issue 20 (September 27, 2016) - Honeywell DL-950 Data Loader

Honeywell Service Information Letter:

• Honeywell SIL No. D201105000003 Rev 2 - NZ-2000 Navigation Computer, PN 7018879-03XXX, IC-615 Integrated Avionics Computer, PN 7017000-XXXXX, IC-800 Integrated Avionics Computer, PN 7017300 XXXXX; Flight Management System (FMS) CNTL-D and Hyperstart Procedures
• Honeywell SIL No. D201402000051 Rev 2 - Global Express P-2000XP IC-800/IC-810 Integrated Avionics Computer (IAC), Internal Battery Information and Internal Battery Maintenance

NOTE: Operator should evaluate optional maintenance task per the Maintenance Planning Document (MPD) document for IAC Battery replacement every 15 months, where the interval can be adjusted based on operation.

1. When possible, perform the FMS CNTL-D download per table below, through the attached document, or through the HW SIL D201102000003 Rev. 2. This can be done in-flight WITHOUT any effect on the FMS operation. Recommendation is to obtain the FMS CNTL-D from the affected FMS or each of them during or immediately after the event, but no later than 20 minutes after the FMS problem occurred.
   FMS CNTL-D Procedure:

   Step	CDU selection	CDU page
   1	NAV	NAV INDEX 1/2
   2	NEXT	NAV INDEX 2/2
   3	MAINTENANCE (2R)	MAINTENANCE 1/3
   4	NEXT	MAINTENANCE 2/3
   5	SETUP (4L)	FMS SETUP 1/1
   6	ENGR DATA (2R)	ENGINEERING DATA 1/1
   7	DEBUG (1L)	DEBUG MONITOR CNTRL 1/1
   8	DM VAL (not in all applications) (4R)*	SET TO YES
   9	SAVE CTL D (4L)	DEBUG MONITOR CNTRL 1/1
   *NOTE: If DM VAL cannot be seen a (4R), go to step 9.

2. Fill up the General FMS Anomalies-In-Flight Data Collecting Form document and pay attention to any CAS message, FMS CDU scratchpad message. Review PROBLEMS (3R) prompt on all FMSs MAINTENANCE 1/3 page and record any messages (NAV index 2/2 >MAINTENANCE (2R) for each FMS.
3. Perform the actions per the General FMS Anomalies-On Ground Data Collecting Form. If possible, perform the Hyperstart procedure per Honeywell SIL No. D201105000003 Rev 2 or per table below. Hyperstart procedure goal is to reset the IACs internal RAM.
   Hyperstart Procedure:

   Step	CDU selection	CDU page
   1	NAV	NAV INDEX 1/2
   2	NEXT	NAV INDEX 2/2
   3	MAINTENANCE (2R)	MAINTENANCE 1/3
   4	NEXT	MAINTENANCE 2/3
   5	SETUP (4L)	FMS SETUP 1/1
   6	ENGR DATA (2R)	ENGINEERING DATA 1/1
   7	DEBUG (1L)	DEBUG MONITOR CNTRL 1/1
   Put HYPER into the scratchpad
   PUSH DM COMMAND (2R) to put the word HYPER into ------
   Push EXECUTE (3R)

4. Periodic Erase/Download of the IAC NVM Data. Through field experience, intermittent failures have been cleared through IAC NVMs erase. IMT messages associated with intermittent failures can be cleared through IAC NVMs erase. See Observed fault FMS INTERMITTENT FAILURES AND DATABASE LOADING ISSUES for details.
5. Do close out.