BE35 pilot reports an airspace incursion flying over day due to a GPS malfunction. The runways are d...

Narrative:

I was heading to pennsylvania from colorado and the weather was getting bad and cloud cover was getting bad so I stopped in muncie; in to look at the radar to see if it was better south. Up until then I was on flight following but since the weather was getting bad I decided to head south then east if the weather was looking better. I wasn't on flight following since I wasn't sure I could continue and I was using my GPS for the airspaces. The GPS wasn't looking right however; but I didn't think much about it until I was looking at a runway on my left and right. I was split between dayton and wright-patterson and my GPS wasn't showing I was in their airspace; so I knew I was committed at that point and the GPS was not functioning properly. I quickly got the frequency for columbus approach and called them and they told me that there may have been a problem and they gave me a phone number to call when I landed. I stayed with flight following the remainder of the flight and the GPS started to work when I got to west virginia and has been working correctly ever since. I called the number I was given and talked to the controller but he said someone else may call back but that did not occur. The controller thought that perhaps everything was ok; but I wanted to submit this report.

Original NASA ASRS Text

Title: BE35 pilot reports an airspace incursion flying over DAY due to a GPS malfunction. The runways are detected visually but the airspace is not depicted on the GPS display.

Narrative: I was heading to Pennsylvania from Colorado and the weather was getting bad and cloud cover was getting bad so I stopped in Muncie; IN to look at the radar to see if it was better south. Up until then I was on Flight Following but since the weather was getting bad I decided to head south then east if the weather was looking better. I wasn't on Flight Following since I wasn't sure I could continue and I was using my GPS for the airspaces. The GPS wasn't looking right however; but I didn't think much about it until I was looking at a runway on my left and right. I was split between Dayton and Wright-Patterson and my GPS wasn't showing I was in their airspace; so I knew I was committed at that point and the GPS was not functioning properly. I quickly got the frequency for Columbus Approach and called them and they told me that there may have been a problem and they gave me a phone number to call when I landed. I stayed with Flight Following the remainder of the flight and the GPS started to work when I got to West Virginia and has been working correctly ever since. I called the number I was given and talked to the Controller but he said someone else may call back but that did not occur. The Controller thought that perhaps everything was ok; but I wanted to submit this report.

Data retrieved from NASA's ASRS site as of July 2013 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	1106896
Time
Date	201307
Local Time Of Day	1801-2400
Place
Locale Reference	DAY.Airport
State Reference	OH
Environment
Flight Conditions	Marginal
Light	Daylight
Aircraft 1
Make Model Name	Bonanza 35
Operating Under FAR Part	Part 91
Flight Phase	Cruise
Flight Plan	None
Component
Aircraft Component	GPS & Other Satellite Navigation
Person 1
Function	Single Pilot Pilot Flying
Qualification	Flight Crew Private
Experience	Flight Crew Last 90 Days 56.7 Flight Crew Total 660 Flight Crew Type 360
Events
Anomaly	Aircraft Equipment Problem Less Severe Airspace Violation All Types Deviation - Procedural FAR

BE35 pilot reports an airspace incursion flying over day due to a GPS malfunction. The runways are detected visually but the airspace is not depicted on the GPS display.