A320 flight crew reports inadvertently deleting a crossing restriction on the EAGLE5 RNAV arrival to...

Attributes
ACN	990657
Time
Date	201201
Local Time Of Day	0001-0600
Place
Locale Reference	ZAB.ARTCC
State Reference	NM
Environment
Light	Daylight
Aircraft 1
Make Model Name	A320
Operating Under FAR Part	Part 121
Flight Phase	Descent
Component
Aircraft Component	FMS/FMC
Person 1
Function	Pilot Flying Captain
Qualification	Flight Crew Air Transport Pilot (ATP)
Person 2
Function	First Officer Pilot Not Flying
Experience	Flight Crew Last 90 Days 220 Flight Crew Total 15000 Flight Crew Type 7000
Events
Anomaly	Deviation - Altitude Crossing Restriction Not Met Deviation - Altitude Overshoot Deviation - Procedural Clearance

Narrative:

[We were] cruising at FL240 given the EAGLE5 runway 25L transition. Set final altitude of 4000 MSL in altitude selector and verified by first officer. At indicated top-of-descent point selected managed descent on autopilot and managed the speed. All crossing restrictions had been verified prior to descent. At payso intersection I noticed that we were at FL230 at 270 KIAS instead of the published FL240-FL280. Apparently the crossing restriction in the FMC had been deleted by our new cruise altitude (FL240). I had checked the crossing restrictions on the arrival prior to descending to FL240. When we descended to FL240; that altitude was added as a cruise altitude. I did not notice the restriction at payso intersection had been deleted (apparently automatically). I will be checking each crossing restriction as it comes up on the descent in addition to the normal pre-descent check of all restrictions.

Original NASA ASRS Text

Title: A320 flight crew reports inadvertently deleting a crossing restriction on the EAGLE5 RNAV arrival to PHX; resulting in an early descent below the fix altitude.

Narrative: [We were] cruising at FL240 given the EAGLE5 Runway 25L transition. Set final altitude of 4000 MSL in altitude selector and verified by First Officer. At indicated top-of-descent point selected managed descent on autopilot and managed the speed. All crossing restrictions had been verified prior to descent. At PAYSO Intersection I noticed that we were at FL230 at 270 KIAS instead of the published FL240-FL280. Apparently the crossing restriction in the FMC had been deleted by our new cruise altitude (FL240). I had checked the crossing restrictions on the arrival prior to descending to FL240. When we descended to FL240; that altitude was added as a cruise altitude. I did not notice the restriction at PAYSO Intersection had been deleted (apparently automatically). I will be checking each crossing restriction as it comes up on the descent in addition to the normal pre-descent check of all restrictions.

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.

A320 flight crew reports inadvertently deleting a crossing restriction on the EAGLE5 RNAV arrival to phx; resulting in an early descent below the fix altitude.