Flight Crew Air Transport Pilot (ATP)
Other / Unknown
Aircraft Equipment Problem Less Severe; Deviation - Altitude Crossing Restriction Not Met; Deviation - Altitude Undershoot; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
General None Reported / Taken
Aircraft; Human Factors; Procedure
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!
Reporter states the descent path was captured several minutes after being cleared direct to MSTRD. The managed descent was initiated prior to the top of descent point and the path was captured by the FMGC.  After crossing MAYOS high; the aircraft continued on its descent making all restrictions without alterations.
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.