Narrative:

On arrival into ewr; on the FLOSI3 arrival; we were cleared directly to shaff shortly after nelie and cleared to descend to 7;000 feet (after a previous clearance to cross crank at 7;000 feet; so we were on a 'path' (not VNAV path) to be abeam crank at about 7000 feet). Approximately overhead kswf; my ipad page changed from the FLOSI3 to the taxi chart for stewart; uncommanded. All of the 'swiping' in the world did not bring the appropriate page back; so I had to reselect ewr on the upper left and then reselect the FLOSI3 arrival. Fortunately; it was VMC and I had the paper charts open to the ewr section beside me; so there was no pilot error. However; of the 3 ipads in use at that time; only one (mine) auto selected swf (our alternate); so either our efb is 33% reliable or 67% reliable. The ipad is a great tool but it needs to be much more reliable before trusting the safety of our airline and passengers to it. I could probably write a [report] a month for an ipad glitch that I shrug my shoulders over. Sometime this summer; my ipad froze for most of my flight to the west coast because it started some auto update when it sensed the aircraft internet which was intermittent enough to prevent the update from being completed.I should have written a [report] on that; but basically forgot due to thunderstorms and other issues demanding my attention. Other pilots have had experience with various glitches and the one thing that the ipad is doing; is creating a 'normalization of deviance' for how reliable it needs to be.

Google
 

Original NASA ASRS Text

Title: Air carrier Captain reported becoming distracted on approach when the EFB automatically rolled to the alternate airport taxi chart.

Narrative: On arrival into EWR; on the FLOSI3 arrival; we were cleared directly to SHAFF shortly after NELIE and cleared to descend to 7;000 feet (after a previous clearance to cross CRANK at 7;000 feet; so we were on a 'path' (not VNAV path) to be abeam CRANK at about 7000 feet). Approximately overhead KSWF; my iPad page changed from the FLOSI3 to the taxi chart for Stewart; uncommanded. All of the 'swiping' in the world did not bring the appropriate page back; so I had to reselect EWR on the upper left and then reselect the FLOSI3 arrival. Fortunately; it was VMC and I had the paper charts open to the EWR section beside me; so there was no pilot error. However; of the 3 iPads in use at that time; only one (mine) auto selected SWF (our alternate); so either our EFB is 33% reliable or 67% reliable. The iPad is a great tool but it needs to be much more reliable before trusting the safety of our airline and passengers to it. I could probably write a [report] a month for an iPad glitch that I shrug my shoulders over. Sometime this summer; my iPad froze for most of my flight to the west coast because it started some auto update when it sensed the aircraft internet which was intermittent enough to prevent the update from being completed.I should have written a [report] on that; but basically forgot due to thunderstorms and other issues demanding my attention. Other pilots have had experience with various glitches and the one thing that the iPad IS doing; is creating a 'normalization of deviance' for how reliable it needs to be.

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.