Narrative:

At about XA45 on xx/sat/95 I called for taxi with falcon ground with code (ATIS). The altimeter setting was 30.00 inches. I also, asked falcon ground for a transponder code and approach frequency to transition phoenix class B airspace to the northwest, destination, lancaster, ca. Falcon ground informed me that they were unable, however, they would expedite a frequency change and advise me of the appropriate approach frequency. After takeoff, I turned northwest and, after a short delay, I called falcon tower for a frequency change which was immediately authorized. After my call to phoenix approach I was given a code and altimeter setting of 29.91 inches and after they established radar contact, they cleared me to 'at or below 5500 ft.' phx approach asked for me to 'say altitude' and I responded '4900 ft for 5500 ft.' phx approach appeared to respond with panic -- that I was 1000 ft higher than I stated, and proceeded to vector me with large heading changes and a reduction to 4000 ft. The controller's apparent panic was further evidenced by the fact that he had already acknowledged our correct aircraft type and call sign mentor call sign and now, was confused, calling us bonanza, and not sure of our call. After several heading changes phoenix approach gave me heading of 280 degrees but before things finally settled down he gave me a phone number to call, then asked me if I wanted flight following. Due to the confusion and potential mode C error, I declined. He transferred me to luke approach after several mins elapsed. Luke cleared me to my requested cruising altitude of 6500 ft and requested that, due to my apparent mode C problem, to turn transponder to mode a. The luke controller was refreshingly calm and the rest of the flight was normal. After arrival at rosamond, ca L00, I called as requested, and talked to the watch supervisor. He said that the problem was related to a possible evasive action, that might have been taken by another aircraft responding to a TCASII alarm. I explained that I was unaware of a mode C problem with the aircraft that I was flying, however I planned to have the encoder checked out. The next day I took the aircraft to a repair station located at california city airport L71. It was determined that although the pilot state check was in compliance, the encoder had drifted off 1400 ft. The encoder was readjusted, and a complete pitotstat was performed. It should be noted that both of the altimeters, were in tolerance. I feel that the phoenix controller should have trusted my altimeter readback, not the mode C.

Google
 

Original NASA ASRS Text

Title: A PVT ACFT'S MODE C MALFUNCTIONED IN CLASS B AIRSPACE. AFTER POSSIBLY CAUSING A TCASII ALERT, AND GREAT CONCERN ON THE ARPT OF THE CTLR, THE MODE C USED WAS DISCONTINUED.

Narrative: AT ABOUT XA45 ON XX/SAT/95 I CALLED FOR TAXI WITH FALCON GND WITH CODE (ATIS). THE ALTIMETER SETTING WAS 30.00 INCHES. I ALSO, ASKED FALCON GND FOR A XPONDER CODE AND APCH FREQ TO TRANSITION PHOENIX CLASS B AIRSPACE TO THE NW, DEST, LANCASTER, CA. FALCON GND INFORMED ME THAT THEY WERE UNABLE, HOWEVER, THEY WOULD EXPEDITE A FREQ CHANGE AND ADVISE ME OF THE APPROPRIATE APCH FREQ. AFTER TKOF, I TURNED NW AND, AFTER A SHORT DELAY, I CALLED FALCON TWR FOR A FREQ CHANGE WHICH WAS IMMEDIATELY AUTHORIZED. AFTER MY CALL TO PHOENIX APCH I WAS GIVEN A CODE AND ALTIMETER SETTING OF 29.91 INCHES AND AFTER THEY ESTABLISHED RADAR CONTACT, THEY CLRED ME TO 'AT OR BELOW 5500 FT.' PHX APCH ASKED FOR ME TO 'SAY ALT' AND I RESPONDED '4900 FT FOR 5500 FT.' PHX APCH APPEARED TO RESPOND WITH PANIC -- THAT I WAS 1000 FT HIGHER THAN I STATED, AND PROCEEDED TO VECTOR ME WITH LARGE HDG CHANGES AND A REDUCTION TO 4000 FT. THE CTLR'S APPARENT PANIC WAS FURTHER EVIDENCED BY THE FACT THAT HE HAD ALREADY ACKNOWLEDGED OUR CORRECT ACFT TYPE AND CALL SIGN MENTOR CALL SIGN AND NOW, WAS CONFUSED, CALLING US BONANZA, AND NOT SURE OF OUR CALL. AFTER SEVERAL HDG CHANGES PHOENIX APCH GAVE ME HDG OF 280 DEGS BUT BEFORE THINGS FINALLY SETTLED DOWN HE GAVE ME A PHONE NUMBER TO CALL, THEN ASKED ME IF I WANTED FLT FOLLOWING. DUE TO THE CONFUSION AND POTENTIAL MODE C ERROR, I DECLINED. HE TRANSFERRED ME TO LUKE APCH AFTER SEVERAL MINS ELAPSED. LUKE CLRED ME TO MY REQUESTED CRUISING ALT OF 6500 FT AND REQUESTED THAT, DUE TO MY APPARENT MODE C PROB, TO TURN XPONDER TO MODE A. THE LUKE CTLR WAS REFRESHINGLY CALM AND THE REST OF THE FLT WAS NORMAL. AFTER ARR AT ROSAMOND, CA L00, I CALLED AS REQUESTED, AND TALKED TO THE WATCH SUPVR. HE SAID THAT THE PROB WAS RELATED TO A POSSIBLE EVASIVE ACTION, THAT MIGHT HAVE BEEN TAKEN BY ANOTHER ACFT RESPONDING TO A TCASII ALARM. I EXPLAINED THAT I WAS UNAWARE OF A MODE C PROB WITH THE ACFT THAT I WAS FLYING, HOWEVER I PLANNED TO HAVE THE ENCODER CHKED OUT. THE NEXT DAY I TOOK THE ACFT TO A REPAIR STATION LOCATED AT CALIFORNIA CITY ARPT L71. IT WAS DETERMINED THAT ALTHOUGH THE PLT STATE CHK WAS IN COMPLIANCE, THE ENCODER HAD DRIFTED OFF 1400 FT. THE ENCODER WAS READJUSTED, AND A COMPLETE PITOTSTAT WAS PERFORMED. IT SHOULD BE NOTED THAT BOTH OF THE ALTIMETERS, WERE IN TOLERANCE. I FEEL THAT THE PHOENIX CTLR SHOULD HAVE TRUSTED MY ALTIMETER READBACK, NOT THE MODE C.

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.