EA32 crew had altitude overshoot.

Attributes
ACN	461360
Time
Date	200001
Day	Fri
Local Time Of Day	1201 To 1800
Place
State Reference	MI
Altitude	msl bound lower : 23600 msl bound upper : 24000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zau.artcc
Operator	common carrier : air carrier
Make Model Name	A320
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	descent : intermediate altitude
Flight Plan	IFR
Aircraft 2
Controlling Facilities	artcc : zau.artcc
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Flight Phase	cruise : level
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 110 flight time total : 19400 flight time type : 1180
ASRS Report	461360
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : instrument pilot : commercial pilot : multi engine
Events
Anomaly	altitude deviation : overshoot conflict : airborne less severe non adherence : clearance non adherence : far non adherence : published procedure non adherence : company policies non adherence : required legal separation
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance controller : issued advisory flight crew : took precautionary avoidance action
Miss Distance	horizontal : 36000 vertical : 600
Supplementary
Problem Areas	Aircraft Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Cleared to FL240 from FL370. While descending, I preset the altimeter setting at dtw of 30.63 but forgot to reset standard (29.92) by pulling the altimeter knob. Normal altitude callouts of 2000 ft above and 1000 ft above were made, but neither the copilot nor I noticed the difference between the 2 altimeters (710 ft). Since my autoplt (#1) was engaged, the aircraft descended below FL240, which the copilot noted and stated. I disconnected the autoplt and started climbing while resetting my altimeter to standard, which read FL236. At this time, center called telling us to turn left to 030 degrees for traffic. I started the turn as we were leveling at FL240. Center asked us to confirm our altitude, which we did, as FL240 and we were then cleared to return to the STAR. There was traffic to our right at FL230, which is the normal altitude for crossing mkg. Being new to the airbus, I've learned that the pull for standard feature of the altimeter needs to be monitored when setting the altimeter above the transition level.

Original NASA ASRS Text

Title: EA32 CREW HAD ALT OVERSHOOT.

Narrative: CLRED TO FL240 FROM FL370. WHILE DSNDING, I PRESET THE ALTIMETER SETTING AT DTW OF 30.63 BUT FORGOT TO RESET STANDARD (29.92) BY PULLING THE ALTIMETER KNOB. NORMAL ALT CALLOUTS OF 2000 FT ABOVE AND 1000 FT ABOVE WERE MADE, BUT NEITHER THE COPLT NOR I NOTICED THE DIFFERENCE BTWN THE 2 ALTIMETERS (710 FT). SINCE MY AUTOPLT (#1) WAS ENGAGED, THE ACFT DSNDED BELOW FL240, WHICH THE COPLT NOTED AND STATED. I DISCONNECTED THE AUTOPLT AND STARTED CLBING WHILE RESETTING MY ALTIMETER TO STANDARD, WHICH READ FL236. AT THIS TIME, CTR CALLED TELLING US TO TURN L TO 030 DEGS FOR TFC. I STARTED THE TURN AS WE WERE LEVELING AT FL240. CTR ASKED US TO CONFIRM OUR ALT, WHICH WE DID, AS FL240 AND WE WERE THEN CLRED TO RETURN TO THE STAR. THERE WAS TFC TO OUR R AT FL230, WHICH IS THE NORMAL ALT FOR XING MKG. BEING NEW TO THE AIRBUS, I'VE LEARNED THAT THE PULL FOR STANDARD FEATURE OF THE ALTIMETER NEEDS TO BE MONITORED WHEN SETTING THE ALTIMETER ABOVE THE TRANSITION LEVEL.

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.