A wrong altimeter setting led to an altitude deviation overshoot climb altitude.

Attributes
ACN	315052
Time
Date	199509
Day	Sat
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : pxr airport : phx
State Reference	AZ
Altitude	msl bound lower : 8000 msl bound upper : 9000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : phx
Operator	common carrier : air carrier
Make Model Name	B737-300
Operating Under FAR Part	Part 121
Navigation In Use	Other Other
Flight Phase	climbout : intermediate altitude cruise other
Route In Use	departure other departure sid : sid
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : flight engineer pilot : atp
Experience	flight time last 90 days : 250 flight time total : 8000 flight time type : 2000
ASRS Report	315052
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 200 flight time total : 16000 flight time type : 7000
ASRS Report	314857
Events
Anomaly	aircraft equipment problem : less severe altitude deviation : overshoot non adherence : clearance non adherence : published procedure other anomaly other
Independent Detector	other controllera
Resolutory Action	flight crew : became reoriented flight crew : returned to intended course or assigned course other
Consequence	faa : reviewed incident with flight crew
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Departed phx late on scheduled flight. Aircraft (a B737-300) had been in maintenance due to engine overtemps on takeoff during a previous flight. We were rushed to get flight out in addition to having to contend with changes to flight release. On start, engines idled somewhat high, so we were concerned with abnormality possibilities. We were #1 for takeoff when we reached the runway. After takeoff, we could not communication with departure controller. He was busy with a cessna. When we finally got him to respond, he asked us to turn on transponder. We checked transponder on, but he did not respond to our leaving altitude report. At level off (we thought 8000 ft MSL), he asked us to verify altitude. He advised us altimeter 29.85. We discovered altimeters were set at 28.85. This had apparently been done by maintenance to both pilot's altimeters. We immediately reset to 29.85 and descended to 8000 ft. Only possible conflict was a B757 that had us in visual contact. In addition to above, we did have an overtemp on the right engine after takeoff, so we were also concerned with that.

Original NASA ASRS Text

Title: A WRONG ALTIMETER SETTING LED TO AN ALT DEV OVERSHOOT CLB ALT.

Narrative: DEPARTED PHX LATE ON SCHEDULED FLT. ACFT (A B737-300) HAD BEEN IN MAINT DUE TO ENG OVERTEMPS ON TKOF DURING A PREVIOUS FLT. WE WERE RUSHED TO GET FLT OUT IN ADDITION TO HAVING TO CONTEND WITH CHANGES TO FLT RELEASE. ON START, ENGS IDLED SOMEWHAT HIGH, SO WE WERE CONCERNED WITH ABNORMALITY POSSIBILITIES. WE WERE #1 FOR TKOF WHEN WE REACHED THE RWY. AFTER TKOF, WE COULD NOT COM WITH DEP CTLR. HE WAS BUSY WITH A CESSNA. WHEN WE FINALLY GOT HIM TO RESPOND, HE ASKED US TO TURN ON XPONDER. WE CHKED XPONDER ON, BUT HE DID NOT RESPOND TO OUR LEAVING ALT RPT. AT LEVEL OFF (WE THOUGHT 8000 FT MSL), HE ASKED US TO VERIFY ALT. HE ADVISED US ALTIMETER 29.85. WE DISCOVERED ALTIMETERS WERE SET AT 28.85. THIS HAD APPARENTLY BEEN DONE BY MAINT TO BOTH PLT'S ALTIMETERS. WE IMMEDIATELY RESET TO 29.85 AND DSNDED TO 8000 FT. ONLY POSSIBLE CONFLICT WAS A B757 THAT HAD US IN VISUAL CONTACT. IN ADDITION TO ABOVE, WE DID HAVE AN OVERTEMP ON THE R ENG AFTER TKOF, SO WE WERE ALSO CONCERNED WITH THAT.

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.