Altimeter readout disagrees between aircraft and ARTCC controller.

Attributes
ACN	317034
Time
Date	199509
Day	Mon
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : abq
State Reference	NM
Altitude	msl bound lower : 38400 msl bound upper : 39000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zab tower : sdf
Operator	general aviation : corporate
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Operating Under FAR Part	Part 91
Navigation In Use	Other Other
Flight Phase	cruise other
Route In Use	enroute : direct
Flight Plan	IFR
Person 1
Affiliation	Other
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 125 flight time total : 16000 flight time type : 350
ASRS Report	317034
Person 2
Affiliation	Other
Function	flight crew : first officer
Qualification	pilot : atp pilot : cfi
Experience	flight time last 90 days : 90 flight time total : 15000 flight time type : 140
ASRS Report	316738
Events
Anomaly	altitude deviation : excursion from assigned altitude non adherence : required legal separation other anomaly other
Independent Detector	other flight crewa
Resolutory Action	none taken : anomaly accepted
Consequence	faa : reviewed incident with flight crew
Supplementary
Primary Problem	Aircraft
Air Traffic Incident	other

Narrative:

Aircraft en route from phx to tys climbing to FL390. ZAB gave (3) 10 degree turns (total of 30 degrees) to the left of course due to traffic overtaking us. ZAB then gave clearance to proceed direct to ifi VOR after reaching FL390. When autoplt leveled at FL390, our course was changed to direct ifi. After several ATC frequency changes, and still with ZAB, we were given a telephone number to call at our convenience for ZAB. At that time we did not know the reason for the call. Unable to reach our party while en route, another call was made after reaching tys. While speaking to mr X of ZAB we discovered that ZAB radar was showing our aircraft at FL384 when we reported level at FL390 and changed course for ifi. At that point he said they lost proper separation with other traffic. Our equipment showed us to be at FL390 and we had no previous complaints prior to this leg, nor have we had any since. It has always been the procedure by center if an altitude is not as it should be, they query the aircraft. In our situation, none was made at any time, that I can recall.

Original NASA ASRS Text

Title: ALTIMETER READOUT DISAGREES BTWN ACFT AND ARTCC CTLR.

Narrative: ACFT ENRTE FROM PHX TO TYS CLBING TO FL390. ZAB GAVE (3) 10 DEG TURNS (TOTAL OF 30 DEGS) TO THE L OF COURSE DUE TO TFC OVERTAKING US. ZAB THEN GAVE CLRNC TO PROCEED DIRECT TO IFI VOR AFTER REACHING FL390. WHEN AUTOPLT LEVELED AT FL390, OUR COURSE WAS CHANGED TO DIRECT IFI. AFTER SEVERAL ATC FREQ CHANGES, AND STILL WITH ZAB, WE WERE GIVEN A TELEPHONE NUMBER TO CALL AT OUR CONVENIENCE FOR ZAB. AT THAT TIME WE DID NOT KNOW THE REASON FOR THE CALL. UNABLE TO REACH OUR PARTY WHILE ENRTE, ANOTHER CALL WAS MADE AFTER REACHING TYS. WHILE SPEAKING TO MR X OF ZAB WE DISCOVERED THAT ZAB RADAR WAS SHOWING OUR ACFT AT FL384 WHEN WE RPTED LEVEL AT FL390 AND CHANGED COURSE FOR IFI. AT THAT POINT HE SAID THEY LOST PROPER SEPARATION WITH OTHER TFC. OUR EQUIP SHOWED US TO BE AT FL390 AND WE HAD NO PREVIOUS COMPLAINTS PRIOR TO THIS LEG, NOR HAVE WE HAD ANY SINCE. IT HAS ALWAYS BEEN THE PROC BY CTR IF AN ALT IS NOT AS IT SHOULD BE, THEY QUERY THE ACFT. IN OUR SIT, NONE WAS MADE AT ANY TIME, THAT I CAN RECALL.

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.