Narrative:

Traveling VFR to mtn. Weather in and around mtn (and baltimore/washington area) was changing constantly from VFR to MVFR to IFR.my plan was to land close to the area; ezf; and reassess my final phase of flight due to weather. As I approached ezf; I was getting VFR metar reports from airports enroute (2w6; cge; esn; W29; and mtn); I decided to proceed. Using foreflight and xm weather for information; as I was nearing ezf; I planned my flight into esn; not realizing I was going to clip the sfra north of R-611A (which I was trying to avoid). Also; on foreflight; I was using the enhanced satellite overlay; which may have obscured the map (still my fault). As I proceeded; I was also monitoring guard; and heard the controller announce my intrusion and orders to egress; which I followed immediately.as I egressed the area; I proceeded south around R-6611a and R-6613a then turned left to proceed to esn; at the heading; it was evident that the cloud deck was low and I turned left to xsa. It also became evident that xsa may not be reachable due to weather even though the AWOS was reporting VFR conditions at the field. At this point; I decided to return to known VFR and I made way to ezf. Upon arrival; I started to look for the FAA contact number but was quickly met by the airport manager; who had the FAA on the phone for me. At this point; I completed their initial inquiry.I did not pick up flight following initially due to the fact I realized my flight could be erratic due to weather and I didn't want to be a burden to the system. In retrospect; I first should have used flight following; I should have also stuck with my original plan to land and reassess.

Google
 

Original NASA ASRS Text

Title: SR-22 pilot reported an airspace incursion during weather deviations while using ForeFlight and XM weather for inflight information.

Narrative: Traveling VFR to MTN. Weather in and around MTN (and Baltimore/Washington Area) was changing constantly from VFR to MVFR to IFR.My plan was to land close to the area; EZF; and reassess my final phase of flight due to weather. As I approached EZF; I was getting VFR METAR reports from airports enroute (2w6; CGE; ESN; W29; and MTN); I decided to proceed. Using ForeFlight and XM weather for information; as I was nearing EZF; I planned my flight into ESN; not realizing I was going to clip the SFRA north of R-611A (which I was trying to avoid). Also; on ForeFlight; I was using the enhanced satellite overlay; which may have obscured the map (still my fault). As I proceeded; I was also monitoring GUARD; and heard the Controller announce my intrusion and orders to egress; which I followed immediately.As I egressed the area; I proceeded south around R-6611a and R-6613a then turned left to proceed to ESN; at the heading; it was evident that the cloud deck was low and I turned left to XSA. It also became evident that XSA may not be reachable due to weather even though the AWOS was reporting VFR conditions at the field. At this point; I decided to return to known VFR and I made way to EZF. Upon arrival; I started to look for the FAA contact number but was quickly met by the airport manager; who had the FAA on the phone for me. At this point; I completed their initial inquiry.I did not pick up flight following initially due to the fact I realized my flight could be erratic due to weather and I didn't want to be a burden to the system. In retrospect; I first should have used flight following; I should have also stuck with my original plan to land and reassess.

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