Flight Crew Private
Flight Crew Last 90 Days 56.7; Flight Crew Total 660; Flight Crew Type 360
Situational Awareness; Confusion
Aircraft Equipment Problem Less Severe; Airspace Violation All Types; Deviation / Discrepancy - Procedural FAR
Air Traffic Control Issued Advisory / Alert; Flight Crew Requested ATC Assistance / Clarification
Aircraft; Human Factors
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.
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.