Narrative:

Approaching clt from northeast for the ivane RNAV arrival; washington center cleared us direct to mstrd intersection. We were at FL340. Soon thereafter we were cleared to descend via the ivane arrival landing north clt. We had confirmed all the altitudes and speeds for the arrival as per SOP. Autopilot was in managed speed and managed descent. All crossing points were in magenta. The 'doughnut' on the FMA was showing on descent as well as the prog page on the fmgs screen showed 0 deviation. (On profile descent). We had rechecked the crossing restrictions after activating direct to mstrd intersection to make sure no crossing restrictions had dropped out. Within six miles of the mayos intersection (while still descending) the mayos intersection icon suddenly turned orange. The doughnut and prog page still showed us on correct descent profile; however a quick mental math computation revealed we would not cross mayos between FL260-220 but high! Even with maximum effort descent we still crossed mayos above FL270; 1;800 ft high all while the doughnut and prog page showed us on proper descent profile! The arrival was completed with no further abnormalities. Center did not question our high altitude nor seem aware we had crossed mayos high. There were three airbus pilots (one jumpseat rider) who had no idea why all our aircraft information showed we were on proper descent profile when we were in fact 1;800 ft high at mayos intersection except the sudden orange shade mayos turned too late to make the proper altitude restriction. I could only surmise that by going direct to mstrd intersection to start the arrival could some how cause an aircraft software anomaly. I have been on the airbus about 1 1/2 years and maybe started to trust the logic a little too much. From now on I will be mentally calculating the descent rates to crossing restrictions to back up the logic. Lesson learned!

Related reports:

Google
 

Original NASA ASRS Text

Title: A319 Captain reports missing the crossing restriction at MAYOS during the IVANE 2 RNAV arrival to CLT. The FMGC had been correctly programed and showed on profile until six miles prior to MAYOS when the waypoint turned orange indicating the crossing restriction would not be met.

Narrative: Approaching CLT from northeast for the IVANE RNAV arrival; Washington Center cleared us direct to MSTRD Intersection. We were at FL340. Soon thereafter we were cleared to descend via the IVANE arrival landing north CLT. We had confirmed all the altitudes and speeds for the arrival as per SOP. Autopilot was in managed speed and managed descent. All crossing points were in magenta. The 'doughnut' on the FMA was showing on descent as well as the PROG page on the FMGs screen showed 0 deviation. (On profile descent). We had rechecked the crossing restrictions after activating direct to MSTRD Intersection to make sure no crossing restrictions had dropped out. Within six miles of the MAYOS Intersection (while still descending) the MAYOS Intersection icon suddenly turned orange. The doughnut and PROG page still showed us on correct descent profile; however a quick mental math computation revealed we would not cross MAYOS between FL260-220 but high! Even with maximum effort descent we still crossed MAYOS above FL270; 1;800 FT high all while the doughnut and PROG page showed us on proper descent profile! The arrival was completed with no further abnormalities. Center did not question our high altitude nor seem aware we had crossed MAYOS high. There were three Airbus pilots (one jumpseat rider) who had no idea why all our aircraft information showed we were on proper descent profile when we were in fact 1;800 FT high at MAYOS Intersection except the sudden orange shade MAYOS turned too late to make the proper altitude restriction. I could only surmise that by going direct to MSTRD Intersection to start the arrival could some how cause an aircraft software anomaly. I have been on the Airbus about 1 1/2 years and maybe started to trust the logic a little too much. From now on I will be mentally calculating the descent rates to crossing restrictions to back up the logic. Lesson learned!

Data retrieved from NASA's ASRS site as of July 2013 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.