Narrative:

I am a low time private pilot. On the day of the flight; I was excited to use recently obtained ipad software with moving map; etc. For situational awareness as I am still getting comfortable with an ipad based system vs. Paper maps. I started with a low battery and the ipad was not charging in flight as it should have. Eventually it died. In the few minutes of trying to get it to respond and pull out paper backups; I relied on my eyes to direct my route of flight. There is a southwesterly oriented valley that I gently turned the plane toward...even though I had already plenty of altitude. It just 'felt' like the prudent thing to do. (Who can argue with more altitude over the terrain.) the problem of allowing the plane to change the route of flight along this path was that it directed me toward the floor of the seattle class B at 3;000 ft. Once I realized the problem; I turned southeast to exit the potential problem as rapidly as possible. By my measure; I only avoided the class B airspace by 1 mile. Way too close. There are a number of things that; appear somewhat obvious in retrospect. 1) don't allow electrical devices to lull you into weaker pre-flight planning than you would normally perform. 2) if relying on an electronic device; it is only as good as the battery and operating system running it. 3) don't change the 'plan' because of a minor challenge. (I let my eyes lead me off the planned route of flight that avoided the class B.) 4) use the autopilot when things don't go as planned.

Google
 

Original NASA ASRS Text

Title: C182 pilot reported that an EFB malfunction and loss of situational awareness nearly caused an airspace incursion.

Narrative: I am a low time private pilot. On the day of the flight; I was excited to use recently obtained iPad software with moving map; etc. for situational awareness as I am still getting comfortable with an iPad based system vs. paper maps. I started with a low battery and the iPad was not charging in flight as it should have. Eventually it died. In the few minutes of trying to get it to respond and pull out paper backups; I relied on my eyes to direct my route of flight. There is a southwesterly oriented valley that I gently turned the plane toward...even though I had already plenty of altitude. It just 'felt' like the prudent thing to do. (who can argue with more altitude over the terrain.) The problem of allowing the plane to change the route of flight along this path was that it directed me toward the floor of the Seattle class B at 3;000 ft. Once I realized the problem; I turned southeast to exit the potential problem as rapidly as possible. By my measure; I only avoided the Class B airspace by 1 mile. WAY TOO CLOSE. There are a number of things that; appear somewhat obvious in retrospect. 1) Don't allow electrical devices to lull you into weaker pre-flight planning than you would normally perform. 2) If relying on an electronic device; it is only as good as the battery and operating system running it. 3) Don't change the 'plan' because of a minor challenge. (I let my eyes lead me off the planned route of flight that avoided the class B.) 4) Use the autopilot when things don't go as planned.

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.