B727 crew had altitude overshoot descending in czyz class east.

Attributes
ACN	473468
Time
Date	200005
Day	Sun
Local Time Of Day	1201 To 1800
Place
State Reference	ON
Altitude	msl bound lower : 11000 msl bound upper : 13000
Environment
Flight Conditions	Mixed
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	B727 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	descent : vacating altitude
Route In Use	arrival star : ns
Flight Plan	IFR
Person 1
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 : 8000
ASRS Report	473468
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : multi engine pilot : instrument pilot : commercial
Events
Anomaly	altitude deviation : overshoot non adherence : company policies non adherence : published procedure non adherence : clearance other anomaly other
Independent Detector	other flight crewa other flight crewb
Resolutory Action	none taken : anomaly accepted
Consequence	faa : assigned or threatened penalties
Supplementary
Problem Areas	Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Cruising into toronto, we were level at FL290. We were cleared to 11000 ft and told to follow the profile descent for runways 23 and 24L. The descent profile calls for us to cross waterloo between 17000 ft and 13000 ft and to then cross guelf at 11000 ft. The first officer and I discussed the need to cross waterloo at one of the lower altitudes in the 4000 ft block in order to be able to reach guelf at 11000 ft and 250 KTS. Shortly thereafter, the first officer started his descent. I had set 11000 ft into the altitude alert. During the descent we both forgot about the restr at waterloo and as we were leveling at 11000 ft, 15 DME prior to waterloo, I realized our mistake. No traffic was noted on the TCASII. I asked the controller if there was a problem with our descent. His response was 'no problem, you just got down a little early.' I asked if that would be a problem and he just said 'no.' factors affecting our mistake: 1) my previous trip was a 4-DAY trip that turned into a long 5-DAY trip. My short time off at home didn't allow me time to fully recover. I was tired before I started this trip. 2) the first officer was just returning from 25 days off. 3) we had a 3+ hour situation in chicago. 4) I should have set 13000 ft in the altitude alert until we crossed ywt.

Original NASA ASRS Text

Title: B727 CREW HAD ALT OVERSHOOT DSNDING IN CZYZ CLASS E.

Narrative: CRUISING INTO TORONTO, WE WERE LEVEL AT FL290. WE WERE CLRED TO 11000 FT AND TOLD TO FOLLOW THE PROFILE DSCNT FOR RWYS 23 AND 24L. THE DSCNT PROFILE CALLS FOR US TO CROSS WATERLOO BTWN 17000 FT AND 13000 FT AND TO THEN CROSS GUELF AT 11000 FT. THE FO AND I DISCUSSED THE NEED TO CROSS WATERLOO AT ONE OF THE LOWER ALTS IN THE 4000 FT BLOCK IN ORDER TO BE ABLE TO REACH GUELF AT 11000 FT AND 250 KTS. SHORTLY THEREAFTER, THE FO STARTED HIS DSCNT. I HAD SET 11000 FT INTO THE ALT ALERT. DURING THE DSCNT WE BOTH FORGOT ABOUT THE RESTR AT WATERLOO AND AS WE WERE LEVELING AT 11000 FT, 15 DME PRIOR TO WATERLOO, I REALIZED OUR MISTAKE. NO TFC WAS NOTED ON THE TCASII. I ASKED THE CTLR IF THERE WAS A PROB WITH OUR DSCNT. HIS RESPONSE WAS 'NO PROB, YOU JUST GOT DOWN A LITTLE EARLY.' I ASKED IF THAT WOULD BE A PROB AND HE JUST SAID 'NO.' FACTORS AFFECTING OUR MISTAKE: 1) MY PREVIOUS TRIP WAS A 4-DAY TRIP THAT TURNED INTO A LONG 5-DAY TRIP. MY SHORT TIME OFF AT HOME DIDN'T ALLOW ME TIME TO FULLY RECOVER. I WAS TIRED BEFORE I STARTED THIS TRIP. 2) THE FO WAS JUST RETURNING FROM 25 DAYS OFF. 3) WE HAD A 3+ HR SIT IN CHICAGO. 4) I SHOULD HAVE SET 13000 FT IN THE ALT ALERT UNTIL WE CROSSED YWT.

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.