M20 pilot experiences a failed fuel gauge and loss of communication with ATC while under VFR flight ...

Narrative:

The day before; the right fuel gauge had indicated 70-100 pounds when it was dry; discovered upon landing. Prior to departing; an abbreviated briefing with WX-brief was obtained for a flight terminating at sdl. No NOTAMS were requested for sjn; just en route weather; tfr's; navaids in operation and winds aloft. After departure; VFR flight following was established with abq center and a squawk code assigned. After several successful handoffs; 20 NM west of tcc VOR; radio contact became scratchy and was lost. I tried contacting FSS and also requested relay of my transmission via an aircraft I could hear communicating with center. None of these were successful. After two hours fuel burn on the right tank it was still showing completely full. Because of the combination of two items; inadequate situational awareness on fuel; and loss of radio contact when a squawk had been assigned; I chose a precautionary landing at sjn; squawked VFR and descended. On final to runway 32 I did see a fluorescent X but it was placed to block the taxiway that enters the departure end of 32; not on the runway itself. I decided it was the taxiway that was unserviceable and completed the landing. After landing I contacted FSS and gave a position report and that I was on the ground in sjn. The briefer advised the runway closure NOTAM had gone into effect midday. Part 91-103 pilots are required to familiarize themselves with all available information concerning the flight prior to every flight. Inadequate radio coverage prevented me getting updated NOTAMS for sjn once a new destination had been chosen. Runway closure was not contained on sjn WX ASOS. Runway closure marker was placed on taxiway not the runway itself. Contributing factors: loss of radio communication with ARTCC combined with unusual readings from fuel gauges after maintenance prompted a precautionary landing.

Original NASA ASRS Text

Title: M20 pilot experiences a failed fuel gauge and loss of communication with ATC while under VFR flight following. Reporter elects to divert to SJN and discovers after landing that Runway 32 is closed.

Narrative: The day before; the right fuel gauge had indicated 70-100 LBS when it was dry; discovered upon landing. Prior to departing; an abbreviated briefing with WX-Brief was obtained for a flight terminating at SDL. No NOTAMS were requested for SJN; just en route weather; TFR's; NAVAIDS in operation and winds aloft. After departure; VFR flight following was established with ABQ Center and a squawk code assigned. After several successful handoffs; 20 NM west of TCC VOR; radio contact became scratchy and was lost. I tried contacting FSS and also requested relay of my transmission via an aircraft I could hear communicating with Center. None of these were successful. After two hours fuel burn on the right tank it was still showing completely full. Because of the combination of two items; inadequate situational awareness on fuel; and loss of radio contact when a squawk had been assigned; I chose a precautionary landing at SJN; squawked VFR and descended. On final to Runway 32 I did see a fluorescent X but it was placed to block the taxiway that enters the departure end of 32; not on the runway itself. I decided it was the taxiway that was unserviceable and completed the landing. After landing I contacted FSS and gave a position report and that I was on the ground in SJN. The briefer advised the runway closure NOTAM had gone into effect midday. Part 91-103 pilots are required to familiarize themselves with all available information concerning the flight prior to every flight. Inadequate radio coverage prevented me getting updated NOTAMS for SJN once a new destination had been chosen. Runway closure was not contained on SJN WX ASOS. Runway closure marker was placed on taxiway not the runway itself. Contributing factors: loss of radio communication with ARTCC combined with unusual readings from fuel gauges after maintenance prompted a precautionary landing.

Data retrieved from NASA's ASRS site as of April 2012 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.

Attributes
ACN	975073
Time
Date	201110
Local Time Of Day	1201-1800
Place
Locale Reference	ZAB.ARTCC
State Reference	NM
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	M-20 F Executive 21
Operating Under FAR Part	Part 91
Flight Phase	Landing
Route In Use	Airway V234
Flight Plan	None
Component
Aircraft Component	Air/Ground Communication
Person 1
Function	Single Pilot
Qualification	Flight Crew Private
Experience	Flight Crew Last 90 Days 88 Flight Crew Total 799 Flight Crew Type 120
Events
Anomaly	Aircraft Equipment Problem Less Severe Deviation - Procedural FAR Deviation - Procedural Published Material / Policy Ground Incursion Runway

M20 pilot experiences a failed fuel gauge and loss of communication with ATC while under VFR flight following. Reporter elects to divert to sjn and discovers after landing that runway 32 is closed.