Narrative:

Flight from azo to mke. ATC (ZAU) issued us the crossing restr of 50 NM southeast of bae VOR at 8000 ft. While descending through 9400 ft MSL, chicago asked us to 'verify level at 10000 ft.' we re-idented our crossing restr to chicago, at which time the controller issued 9000 ft traffic at 3 mi moving southeast. Initially we had no contact on the traffic, and immediately climbed to 9500 ft, at which time we visually idented the aircraft. After acknowledging the target to ZAU the controller asked us to maintain visual separation from the aircraft, and maintain 8000 ft. At this time, my first officer and I are not quite sure how this problem arose, but we are confident the error was the issuance of an incorrect crossing altitude restr.

Google
 

Original NASA ASRS Text

Title: COMMUTER GIVEN XING RESTR, THEN ISSUED TFC AT ALT THROUGH WHICH THEY WOULD PASS.

Narrative: FLT FROM AZO TO MKE. ATC (ZAU) ISSUED US THE XING RESTR OF 50 NM SE OF BAE VOR AT 8000 FT. WHILE DSNDING THROUGH 9400 FT MSL, CHICAGO ASKED US TO 'VERIFY LEVEL AT 10000 FT.' WE RE-IDENTED OUR XING RESTR TO CHICAGO, AT WHICH TIME THE CTLR ISSUED 9000 FT TFC AT 3 MI MOVING SE. INITIALLY WE HAD NO CONTACT ON THE TFC, AND IMMEDIATELY CLBED TO 9500 FT, AT WHICH TIME WE VISUALLY IDENTED THE ACFT. AFTER ACKNOWLEDGING THE TARGET TO ZAU THE CTLR ASKED US TO MAINTAIN VISUAL SEPARATION FROM THE ACFT, AND MAINTAIN 8000 FT. AT THIS TIME, MY FO AND I ARE NOT QUITE SURE HOW THIS PROB AROSE, BUT WE ARE CONFIDENT THE ERROR WAS THE ISSUANCE OF AN INCORRECT XING ALT RESTR.

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.