Narrative:

On the morning of jul/tue, I departed newport news, va (phf) for marion, oh (mnn). An IFR flight plan was filed because IMC existed at phf (cloud layer starting at 2000 ft). Departed phf without problem and norfolk approach reported radar contact. Continued flight through richmond airspace and ZDC airspace without reports of transponder problems. One controller with ZDC requested check altimeter which may have been a sign of a problem. When I changed to clarksburg approach in west virginia, that controller reported that he was not receiving my transponder. He reported that I was only displayed as a primary contact. Next controller with ZOB reported intermittent transponder returns. At some point, I was passed to ZID, that controller reported no transponder returns and that my transponder was inoperative. I would have canceled my IFR flight plan if I was not entering an area of IMC, scattered to broken clouds with bases at 2500 ft approximately, and haze 3-5 mi visibility. This controller changed my routing and later passed me to columbus approach. I do not recall what columbus approach was getting as a transponder return. Later, I was passed to mansfield approach and they reported radar contact, I did not ask if the contact was just a primary or included mode C. Soon after, I had reached mnn and I canceled IFR. Lessons: I should have tried harder to help the ZID controller when he could not make radar contact. I am unclr of what the action would be. This was my first trip into this area of the country and I did not want to give up the IFR clearance. If I was in area local to my home base I think I would have been much more willing to cancel IFR. When radar contact, get more feedback about how my transponder is functioning. Is it a good solid contact or intermittent? What altitude is the transponder reporting?

Google
 

Original NASA ASRS Text

Title: M-20P PLT THOUGHT HE NEEDED TO CANCEL HIS IFR CLRNC WHEN THE ACFT XPONDER BECAME INTERMITTENT.

Narrative: ON THE MORNING OF JUL/TUE, I DEPARTED NEWPORT NEWS, VA (PHF) FOR MARION, OH (MNN). AN IFR FLT PLAN WAS FILED BECAUSE IMC EXISTED AT PHF (CLOUD LAYER STARTING AT 2000 FT). DEPARTED PHF WITHOUT PROB AND NORFOLK APCH RPTED RADAR CONTACT. CONTINUED FLT THROUGH RICHMOND AIRSPACE AND ZDC AIRSPACE WITHOUT RPTS OF XPONDER PROBS. ONE CTLR WITH ZDC REQUESTED CHK ALTIMETER WHICH MAY HAVE BEEN A SIGN OF A PROB. WHEN I CHANGED TO CLARKSBURG APCH IN WEST VIRGINIA, THAT CTLR RPTED THAT HE WAS NOT RECEIVING MY XPONDER. HE RPTED THAT I WAS ONLY DISPLAYED AS A PRIMARY CONTACT. NEXT CTLR WITH ZOB RPTED INTERMITTENT XPONDER RETURNS. AT SOME POINT, I WAS PASSED TO ZID, THAT CTLR RPTED NO XPONDER RETURNS AND THAT MY XPONDER WAS INOP. I WOULD HAVE CANCELED MY IFR FLT PLAN IF I WAS NOT ENTERING AN AREA OF IMC, SCATTERED TO BROKEN CLOUDS WITH BASES AT 2500 FT APPROX, AND HAZE 3-5 MI VISIBILITY. THIS CTLR CHANGED MY ROUTING AND LATER PASSED ME TO COLUMBUS APCH. I DO NOT RECALL WHAT COLUMBUS APCH WAS GETTING AS A XPONDER RETURN. LATER, I WAS PASSED TO MANSFIELD APCH AND THEY RPTED RADAR CONTACT, I DID NOT ASK IF THE CONTACT WAS JUST A PRIMARY OR INCLUDED MODE C. SOON AFTER, I HAD REACHED MNN AND I CANCELED IFR. LESSONS: I SHOULD HAVE TRIED HARDER TO HELP THE ZID CTLR WHEN HE COULD NOT MAKE RADAR CONTACT. I AM UNCLR OF WHAT THE ACTION WOULD BE. THIS WAS MY FIRST TRIP INTO THIS AREA OF THE COUNTRY AND I DID NOT WANT TO GIVE UP THE IFR CLRNC. IF I WAS IN AREA LOCAL TO MY HOME BASE I THINK I WOULD HAVE BEEN MUCH MORE WILLING TO CANCEL IFR. WHEN RADAR CONTACT, GET MORE FEEDBACK ABOUT HOW MY XPONDER IS FUNCTIONING. IS IT A GOOD SOLID CONTACT OR INTERMITTENT? WHAT ALT IS THE XPONDER RPTING?

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.