B737-500 crew had track deviation in ZAU class a airspace.

Attributes
ACN	498280
Time
Date	200101
Day	Sat
Local Time Of Day	0601 To 1200
Place
Locale Reference	navaid : rbs.vor
State Reference	IL
Altitude	msl single value : 28000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zau.artcc
Operator	common carrier : air carrier
Make Model Name	B737-500
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	cruise : level
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
Experience	flight time last 90 days : 100 flight time total : 9000 flight time type : 1500
ASRS Report	498280
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 180 flight time total : 11000 flight time type : 2400
ASRS Report	498134
Events
Anomaly	non adherence : clearance non adherence : company policies non adherence : published procedure other anomaly other other spatial deviation
Independent Detector	atc equipment other atc equipment : radar other controllera
Resolutory Action	flight crew : returned to original clearance none taken : detected after the fact
Supplementary
Problem Areas	Company Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Our original dispatch release filed flight plan was 'rbs J19 stl rzc J105 mlc cue act blewe 1 aus.' our filed altitude was FL350. When we received our pre departure clearance over ACARS, we noticed the requested altitude FL280. We then checked our release and saw that we were now on release 3. Our dispatcher sent us the new release with no explanation. We did, however, notice FL280 and additional fuel. Our FMS had already been programmed and verified using the original release. The pre departure clearance showed no amended route. As we passed rbs and turned down J19, ATC told us we should be flying J71. Upon, looking at the pre departure clearance, wre realized release 3 was for a new filed route. We promptly turned and proceeded down J71 to enl and mem. The new route was on the pre departure clearance, but we overlooked it not realizing it being the reason for release 3. Dispatch should have provided us a new release early with the revision why (ie, new route). We should have been more diligent in checking the pre departure clearance against our new release. We were somewhat rushed due to late inbound aircraft and captain doing IOE in inbound aircraft (doing extensive debrief).

Original NASA ASRS Text

Title: B737-500 CREW HAD TRACK DEV IN ZAU CLASS A AIRSPACE.

Narrative: OUR ORIGINAL DISPATCH RELEASE FILED FLT PLAN WAS 'RBS J19 STL RZC J105 MLC CUE ACT BLEWE 1 AUS.' OUR FILED ALT WAS FL350. WHEN WE RECEIVED OUR PDC OVER ACARS, WE NOTICED THE REQUESTED ALT FL280. WE THEN CHKED OUR RELEASE AND SAW THAT WE WERE NOW ON RELEASE 3. OUR DISPATCHER SENT US THE NEW RELEASE WITH NO EXPLANATION. WE DID, HOWEVER, NOTICE FL280 AND ADDITIONAL FUEL. OUR FMS HAD ALREADY BEEN PROGRAMMED AND VERIFIED USING THE ORIGINAL RELEASE. THE PDC SHOWED NO AMENDED RTE. AS WE PASSED RBS AND TURNED DOWN J19, ATC TOLD US WE SHOULD BE FLYING J71. UPON, LOOKING AT THE PDC, WRE REALIZED RELEASE 3 WAS FOR A NEW FILED RTE. WE PROMPTLY TURNED AND PROCEEDED DOWN J71 TO ENL AND MEM. THE NEW RTE WAS ON THE PDC, BUT WE OVERLOOKED IT NOT REALIZING IT BEING THE REASON FOR RELEASE 3. DISPATCH SHOULD HAVE PROVIDED US A NEW RELEASE EARLY WITH THE REVISION WHY (IE, NEW RTE). WE SHOULD HAVE BEEN MORE DILIGENT IN CHKING THE PDC AGAINST OUR NEW RELEASE. WE WERE SOMEWHAT RUSHED DUE TO LATE INBOUND ACFT AND CAPT DOING IOE IN INBOUND ACFT (DOING EXTENSIVE DEBRIEF).

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.