Narrative:

Sovereign aob 19-05 honeywell epic anomalies - thank goodness I had recently read this aob (aircraft operator bulletin) and was familiar with it; but it still did not eliminate the following event.on [date]; on a flight departing teb; I was pilot monitoring and my co-captain was pilot flying. He loaded the FMS with the RUUDY6 while parked at teb [FBO] ramp. After passenger boarding and crew briefings we taxied to runway 24. My co-captain performed a normal takeoff from runway 24 with the flight director set to navigation mode. Upon positive rate he called for gear up; I began the process of selecting gear up; turning off lights; configuring the fgp with yd (yaw damper) and vs (vertical speed) then cleaning the wing at fra. The pilot flying had come out of takeoff power and had gone to cruise power shortly after calling for gear up; which is reasonable for a departure with a close in level off. Tower switched us to TRACON; and while I was making the switch the pilot flying engaged the autopilot. While in the process of checking in with ny approach 119.2 and about 1;000 feet MSL; I noticed the aircraft start to make a left hand turn just prior to reaching davim. It took me maybe 8-10 secs to recognize that this was the honeywell epic anomaly that I had just read about; so I began to act. Near simultaneously the pilot flying exclaimed something like 'hey why is it turning left.' I hit the heading mode of the flight guidance panel and turned the heading knob to the right to something like 290. I also exclaimed 'turn right; now.' fortunately; the pilot flying was not a 'magenta kid' and had already clicked off the autopilot; rolling the aircraft into a 30 degree right bank and leveling at 1;500 feet MSL. He skillfully handled the aircraft off of autopilot until we were headed in the correct direction and had the situation under control. After all of this; the ready recognition; the quick reaction; the skillful maneuvering; the good crew coordination; it was still not fast enough to keep ny approach from noticing. Shortly after starting our corrective maneuver the controller chimed in stating 'aircraft X; I suggest you turn right to a heading of 300 immediately. Your autopilot is taking you off course.' I could tell; from the tone in his voice that he had seen this before; and he was really quick with a corrective action as well. I don't believe we got far enough off course that it constituted an airspace violation; but still; this needs to be addressed and fixed.the pilot flying and I discussed the event after climbing to altitude and I showed him the aob. He stated that he saw the white/magenta holding pattern appear on the FMS as the aircraft began its left-hand turn. Furthermore; he wasn't sure if the holding pattern had appeared during FMS programming back at [FBO] ramp; and he also was not sure if he had seen it while holding short at the approach end to runway 24 as the aob eludes to. I don't recall seeing the holding pattern depicted either before takeoff. But honestly; this is rather non-standard and I think most pilots would not recognize this anomaly from week to week; and would most likely forget to check for it or just plain miss it. I may go into teb 10 times in a month then not see it again for 6 months. Where else is this going to happen?I've recently returned to the sovereign from two other [aircraft] types. I flew the CE680 for several years and during that time sovereign drivers never had a problem with the ruddy departure while in navigation mode; vertical speed and autopilot. In fact; this was the standard setup during that time-frame. As far as I know this is still the standard both in the simulator and IOE training. I certainly hope no one is going to suggest that we switch to using heading mode for this departure as I'm pretty sure this would lead to far more navigation deviation when crews become distracted with normal close-in departure duties and forget to dial in the heading change at davim. In very short order many of uswould end up over ewr.I'm writing this [report] because this really needs to be addressed and most likely by honeywell and their software developers. What's changed? How has this all of a sudden become a problem? Navigation mode should help simplify departures not add confusion.

Related reports:

Google
 

Original NASA ASRS Text

Title: CE680 Captain reported that a known Honeywell Epic FMC anomaly resulted in a course deviation while on the TEB RUUDY 6 SID.

Narrative: Sovereign AOB 19-05 Honeywell Epic Anomalies - Thank goodness I had recently read this AOB (Aircraft Operator Bulletin) and was familiar with it; but it still did not eliminate the following event.On [date]; on a flight departing TEB; I was Pilot Monitoring and my co-Captain was Pilot Flying. He loaded the FMS with the RUUDY6 while parked at TEB [FBO] ramp. After passenger boarding and crew briefings we taxied to Runway 24. My co-Captain performed a normal takeoff from Runway 24 with the Flight Director set to NAV mode. Upon positive rate he called for gear up; I began the process of selecting gear up; turning off lights; configuring the FGP with YD (Yaw Damper) and VS (Vertical Speed) then cleaning the wing at FRA. The Pilot Flying had come out of takeoff power and had gone to cruise power shortly after calling for gear up; which is reasonable for a departure with a close in level off. Tower switched us to TRACON; and while I was making the switch the Pilot Flying engaged the Autopilot. While in the process of checking in with NY Approach 119.2 and about 1;000 feet MSL; I noticed the aircraft start to make a left hand turn just prior to reaching DAVIM. It took me maybe 8-10 secs to recognize that this was the Honeywell Epic Anomaly that I had just read about; so I began to act. Near simultaneously the Pilot Flying exclaimed something like 'Hey why is it turning left.' I hit the HDG mode of the Flight Guidance Panel and turned the heading knob to the right to something like 290. I also exclaimed 'TURN RIGHT; NOW.' Fortunately; the Pilot Flying was not a 'Magenta Kid' and had already clicked off the autopilot; rolling the aircraft into a 30 degree right bank and leveling at 1;500 feet MSL. He skillfully handled the aircraft off of autopilot until we were headed in the correct direction and had the situation under control. After all of this; the ready recognition; the quick reaction; the skillful maneuvering; the good crew coordination; it was still not fast enough to keep NY Approach from noticing. Shortly after starting our corrective maneuver the controller chimed in stating 'Aircraft X; I suggest you turn right to a heading of 300 immediately. Your Autopilot is taking you off course.' I could tell; from the tone in his voice that he had seen this before; and he was really quick with a corrective action as well. I don't believe we got far enough off course that it constituted an airspace violation; but still; this needs to be addressed and fixed.The Pilot Flying and I discussed the event after climbing to altitude and I showed him the AOB. He stated that he saw the White/Magenta holding pattern appear on the FMS as the aircraft began its left-hand turn. Furthermore; he wasn't sure if the holding pattern had appeared during FMS programming back at [FBO] ramp; and he also was not sure if he had seen it while holding short at the approach end to Runway 24 as the AOB eludes to. I don't recall seeing the holding pattern depicted either before takeoff. But honestly; this is rather non-standard and I think most pilots would not recognize this anomaly from week to week; and would most likely forget to check for it or just plain miss it. I may go into TEB 10 times in a month then not see it again for 6 months. Where else is this going to happen?I've recently returned to the Sovereign from two other [aircraft] types. I flew the CE680 for several years and during that time Sovereign drivers never had a problem with the RUDDY departure while in NAV mode; vertical speed and autopilot. In fact; this was the standard setup during that time-frame. As far as I know this is still the standard both in the simulator and IOE training. I certainly hope no one is going to suggest that we switch to using HDG mode for this departure as I'm pretty sure this would lead to far more NAV deviation when crews become distracted with normal close-in departure duties and forget to dial in the heading change at DAVIM. In very short order many of uswould end up over EWR.I'm writing this [report] because this really needs to be addressed and most likely by Honeywell and their software developers. What's changed? How has this all of a sudden become a problem? NAV mode should help simplify departures not add confusion.

Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.