A B737-700 captain reported missing a crossing restriction after becoming confused by the altimeter ...

Narrative:

We were cleared to 16;000' and then to cross the airway intersection at 11;000. I was late in calling the descent checklist and went to level off at 16;000'. I noticed the yellow box was flashing around the altitude box. I became distracted with the flashing box and had shifted between altitude; standard and back to the altitude setting of 30.43. This; of course; changed the altimeter about four hundred feet every time I switched. I became confused at what was causing the yellow flashing box so I leveled off at 16;000' on altimeter 30.43; but was not positive I was at 16;000'. I then noticed a 'altitude disagree' and checked the first officer's altimeter. It was at 29.43 not 30.43. I had him input 30.43. In the time we were trying to figure out the conflicting signals; I missed the top of descent point for the 11;000' crossing restriction. We then got the call from center; 'you gonna make it at 11;000'' I started a vertical speed descent but was too late. We crossed at about 12;800'. Obviously; calling for the descent checklist passing fl 180 would have rectified this situation; but that one error quickly compounded into several issues at once.

Original NASA ASRS Text

Title: A B737-700 Captain reported missing a crossing restriction after becoming confused by the altimeter display inaccuracy caused by the First Officer's altimeter setting being different from his.

Narrative: We were cleared to 16;000' and then to cross the airway intersection at 11;000. I was late in calling the Descent Checklist and went to level off at 16;000'. I noticed the yellow box was flashing around the altitude box. I became distracted with the flashing box and had shifted between ALT; STD and back to the ALT setting of 30.43. This; of course; changed the altimeter about four hundred feet every time I switched. I became confused at what was causing the yellow flashing box so I leveled off at 16;000' on altimeter 30.43; but was not positive I was at 16;000'. I then noticed a 'ALT DISAGREE' and checked the First Officer's altimeter. It was at 29.43 not 30.43. I had him input 30.43. In the time we were trying to figure out the conflicting signals; I missed the Top of Descent point for the 11;000' crossing restriction. We then got the call from Center; 'You gonna make it at 11;000'' I started a Vertical Speed descent but was too late. We crossed at about 12;800'. Obviously; calling for the Descent Checklist passing FL 180 would have rectified this situation; but that one error quickly compounded into several issues at once.

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

Attributes
ACN	927620
Time
Date	201101
Local Time Of Day	1801-2400
Place
Locale Reference	ZZZ.ARTCC
State Reference	US
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Make Model Name	B737-700
Operating Under FAR Part	Part 121
Flight Phase	Descent
Flight Plan	IFR
Component
Aircraft Component	Altimeter
Person 1
Function	Pilot Flying Captain
Qualification	Flight Crew Air Transport Pilot (ATP)
Experience	Flight Crew Last 90 Days 271 Flight Crew Type 6000
Events
Anomaly	Deviation - Altitude Crossing Restriction Not Met Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy

A B737-700 captain reported missing a crossing restriction after becoming confused by the altimeter display inaccuracy caused by the first officer's altimeter setting being different from his.