Narrative:

At cruise we briefed a visual approach to runway 26R at atl. In the mcdu runway 26R was in the primary and runway 26L in the secondary. All altitude constraints were in and verified by both crew. We were on the erlin arrival and there is a restr of 14000 ft that we were assigned. Descent was made in the managed mode and this was confirmed by both crew. During descent all parameters were normal and we never received any message. At about 19500 ft we were switched to approach. The first officer checked in and we were assigned runway 27L; the first officer inserted this in the primary flight plan. This was verified and we briefed a visual of runway 27L. The approach checklist was completed. A few seconds later I observed that we were within a mile or 2 of the crossing restr and descending through 16000 ft. V/south was then pulled and 4000 FPM descent was selected. We crossed the fix just slightly below 16000 ft instead of 14000 ft. About a mile past the fix; approach questioned our altitude and assigned us to expedite to 11000 ft. I did this and we were level shortly after. No traffic was observed and no TCAS warnings were received. We both agreed that 14000 ft was on the FCU and that the crossing restr was programmed into the mcdu. We could not discern any reason for the aircraft not to meet restr. We feel that the altitude constraint likely dropped out when the runway change was made. Double check crossing restr when runway changes are made.

Related reports:

Google
 

Original NASA ASRS Text

Title: A319 MISSES CROSSING RESTR AT DALAS ON THE ERLIN ARR INTO ATL AFTER ZTL CTLR CHANGES LNDG TO RWY 27L.

Narrative: AT CRUISE WE BRIEFED A VISUAL APCH TO RWY 26R AT ATL. IN THE MCDU RWY 26R WAS IN THE PRIMARY AND RWY 26L IN THE SECONDARY. ALL ALT CONSTRAINTS WERE IN AND VERIFIED BY BOTH CREW. WE WERE ON THE ERLIN ARR AND THERE IS A RESTR OF 14000 FT THAT WE WERE ASSIGNED. DSCNT WAS MADE IN THE MANAGED MODE AND THIS WAS CONFIRMED BY BOTH CREW. DURING DSCNT ALL PARAMETERS WERE NORMAL AND WE NEVER RECEIVED ANY MSG. AT ABOUT 19500 FT WE WERE SWITCHED TO APCH. THE FO CHKED IN AND WE WERE ASSIGNED RWY 27L; THE FO INSERTED THIS IN THE PRIMARY FLT PLAN. THIS WAS VERIFIED AND WE BRIEFED A VISUAL OF RWY 27L. THE APCH CHKLIST WAS COMPLETED. A FEW SECONDS LATER I OBSERVED THAT WE WERE WITHIN A MILE OR 2 OF THE CROSSING RESTR AND DSNDING THROUGH 16000 FT. V/S WAS THEN PULLED AND 4000 FPM DSCNT WAS SELECTED. WE CROSSED THE FIX JUST SLIGHTLY BELOW 16000 FT INSTEAD OF 14000 FT. ABOUT A MILE PAST THE FIX; APCH QUESTIONED OUR ALT AND ASSIGNED US TO EXPEDITE TO 11000 FT. I DID THIS AND WE WERE LEVEL SHORTLY AFTER. NO TFC WAS OBSERVED AND NO TCAS WARNINGS WERE RECEIVED. WE BOTH AGREED THAT 14000 FT WAS ON THE FCU AND THAT THE CROSSING RESTR WAS PROGRAMMED INTO THE MCDU. WE COULD NOT DISCERN ANY REASON FOR THE ACFT NOT TO MEET RESTR. WE FEEL THAT THE ALT CONSTRAINT LIKELY DROPPED OUT WHEN THE RWY CHANGE WAS MADE. DOUBLE CHK CROSSING RESTR WHEN RWY CHANGES ARE MADE.

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