Narrative:

Missed crossing restr. We received and acknowledged a restr to cross 90 mi south of chicago at FL240. FL240 was armed and as the PF I decided to stay at altitude as long as possible in the interest of fuel conservation. However, I made the mistake of using the distance to go to destination in computing the top of descent. This distance included the ILS runway 27L approach and was considerably longer than the straight line distance to ord. Normally I would never use the GPS distance for any crossing calculation as it is not what the crossing is based on. For some reason, I focused on it and did not revisit the top of descent calculation until it was too late to make the crossing. We were approximately FL265 at 90 mi south of ord. Supplemental information from acn 488051: ZAU gave us instructions to cross 90 NM south of ord at FL240. We were at FL330 and approximately 130 NM out when we received the restr. We crossed 90 mi south of ord at approximately FL290. Apparently the captain was using the mileage off the GPS. He was in the map mode and I was raw data. I did not notice the problem until about 97 NM out. Although I was preparing the cockpit for descent and looking over the approach, I realize now that I was counting on the captain to make the altitude crossing and did not supply the necessary backup for him. Not real swift for someone with my time in the aircraft. I will take this as a serious wake-up call.

Related reports:

Google
 

Original NASA ASRS Text

Title: MD80 CREW DID NOT COMPLY WITH ATC ISSUED XING RESTR IN ZAU CLASS A AIRSPACE.

Narrative: MISSED XING RESTR. WE RECEIVED AND ACKNOWLEDGED A RESTR TO CROSS 90 MI S OF CHICAGO AT FL240. FL240 WAS ARMED AND AS THE PF I DECIDED TO STAY AT ALT AS LONG AS POSSIBLE IN THE INTEREST OF FUEL CONSERVATION. HOWEVER, I MADE THE MISTAKE OF USING THE DISTANCE TO GO TO DEST IN COMPUTING THE TOP OF DSCNT. THIS DISTANCE INCLUDED THE ILS RWY 27L APCH AND WAS CONSIDERABLY LONGER THAN THE STRAIGHT LINE DISTANCE TO ORD. NORMALLY I WOULD NEVER USE THE GPS DISTANCE FOR ANY XING CALCULATION AS IT IS NOT WHAT THE XING IS BASED ON. FOR SOME REASON, I FOCUSED ON IT AND DID NOT REVISIT THE TOP OF DSCNT CALCULATION UNTIL IT WAS TOO LATE TO MAKE THE XING. WE WERE APPROX FL265 AT 90 MI S OF ORD. SUPPLEMENTAL INFO FROM ACN 488051: ZAU GAVE US INSTRUCTIONS TO CROSS 90 NM S OF ORD AT FL240. WE WERE AT FL330 AND APPROX 130 NM OUT WHEN WE RECEIVED THE RESTR. WE CROSSED 90 MI S OF ORD AT APPROX FL290. APPARENTLY THE CAPT WAS USING THE MILEAGE OFF THE GPS. HE WAS IN THE MAP MODE AND I WAS RAW DATA. I DID NOT NOTICE THE PROB UNTIL ABOUT 97 NM OUT. ALTHOUGH I WAS PREPARING THE COCKPIT FOR DSCNT AND LOOKING OVER THE APCH, I REALIZE NOW THAT I WAS COUNTING ON THE CAPT TO MAKE THE ALT XING AND DID NOT SUPPLY THE NECESSARY BACKUP FOR HIM. NOT REAL SWIFT FOR SOMEONE WITH MY TIME IN THE ACFT. I WILL TAKE THIS AS A SERIOUS WAKE-UP CALL.

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