Date: 201504
Local time of day: 0601-1200
Location: ZTL.ARTCC, GA
Flight conditions: VMC
Light: Daylight
Aircraft: Regional Jet 200 ER/LR (CRJ200)
Operator: Air Carrier
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class A ZTL
ATC / advisory: Center ZTL
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Human-Machine Interface; Situational Awareness
Anomaly: Deviation - Altitude Crossing Restriction Not Met; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Air Traffic Control Issued New Clearance; Flight Crew Became Reoriented; Flight Crew Returned To Clearance
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: We were flying to Charlotte and had begun the IVANE5 arrival.  Atlanta Center directed us to cross the fix MAYOS at FL220 and then to descend via the IVANE5 arrival.  The published altitude was FL240--FL260. Shortly thereafter we were assigned a speed at MAYOS and to hold that speed until MAJIC and then resume the published speeds.We reviewed the fixes and speeds together and the Pilot Flying (PF) elected to request 10;000 feet in the altitude pre select; and then use the direct intercept page on the FMS to assist in maintaining the correct descent rates.  We had used this method before the previous two days; however this time there was a change in the published chart crossing (at MAYOS).We crossed MAYOS at the correct altitude and simply fixated on the crossing restriction two [5] fixes down instead of the very next one which was ALSO at FL220 (KIYEN). We descended through that fix at approximately 21;500 feet.  ATC asked us to check out altitude; and said we were below FL220 at KIYEN.   We both immediately caught it and the PF swallowed the descent rate.  ATC said it was fine just to make all the following crossings and then a few minutes later switched us to another controller.   We continued the arrival and landed without further issues.We both monitored the arrival; but at 25 minutes to the destination; I left the radio and made the descent PA.  We had remarked at how challenging the IVANE5 arrival was the following two days and the PF was focused on descending the aircraft.  When I returned to the frequency we both monitored the arrival but missed the fix crossing and very soon after that the Center advised us of our mistake.The crew's efforts to make the crossing restriction were correct but he looked ahead two fixes out and missed the closer one which required a level-off.I could have made the PA before we started the arrival.  We both could have been more vigilant on the arrival.  Although there was a change we should have reviewed the arrival better.During the debrief; we think that the FMS management was fine and the chart usage was fine; but just more attention should have been paid to the change from what was published.More review of STARs in sim checking events is always good because it seems that many airports are using these more and more.




Synopsis: CRJ-200 First Officer describes the events leading up to a missed crossing restriction on the IVANE5 RNAV arrival to CLT.