 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A B737 captain reported technical problems with his ipad.
| Attributes | |
| ACN | 1324855 |
| Time | |
| Date | 201601 |
| Aircraft 1 | |
| Make Model Name | B737 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Parked |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | Tablet |
| Person 1 | |
| Function | Captain |
| Events | |
| Anomaly | Aircraft Equipment Problem Less Severe |
Narrative:
A I am sending this report because it issues related to [the ipad] have been causing distractions (if not a 'threat') both on the ground and in flight over the last 24 hours. Yesterday [the ipad] went into a 'configuring' mode while in flight which made the application unusable (continuing spinning circle for the duration of the flight). Re-powering the ipad was no help. Once on the ground I called the ipad support desk and was told system -wide issues related to the ipad were amounting to a 'complete disaster'. This morning; just prior to pushback; [the ipad] suddenly initiated an update on its own. I received a message when the update initiated stating that [the ipad] was about to begin an update; and asking if I wanted to 'continue' or 'cancel' I selected 'cancel' due to the timing; but this appeared to only cause the download and update to pause; not cancel--rendering the app unusable. I then allowed [the ipad] to update itself; but when that was finally done it needed to download 116 updates. At the rate they were downloading it appeared that the entire process was going to be fairly lengthy. Again; this is not the type of distraction we need right before pushback when there is plenty of other stuff going on in the cockpit. I would like to at least have a modicum of control in deciding when [the ipad] initiates a lengthy update of itself.
Original NASA ASRS Text
Title: A B737 Captain reported technical problems with his ipad.
Narrative: A I am sending this report because IT issues related to [the iPad] have been causing distractions (if not a 'threat') both on the ground and in flight over the last 24 hours. Yesterday [the iPad] went into a 'Configuring' mode while in flight which made the application unusable (continuing spinning circle for the duration of the flight). Re-powering the iPad was no help. Once on the ground I called the iPad Support Desk and was told system -wide issues related to the iPad were amounting to a 'complete disaster'. This morning; just prior to pushback; [the iPad] suddenly initiated an update on its own. I received a message when the update initiated stating that [the iPad] was about to begin an update; and asking if I wanted to 'continue' or 'cancel' I selected 'cancel' due to the timing; but this appeared to only cause the download and update to PAUSE; not cancel--rendering the app unusable. I then allowed [the iPad] to update itself; but when that was finally done it needed to download 116 updates. At the rate they were downloading it appeared that the entire process was going to be fairly lengthy. Again; this is not the type of distraction we need right before pushback when there is plenty of other stuff going on in the cockpit. I would like to at least have a modicum of control in deciding WHEN [the iPad] initiates a lengthy update of itself.
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.