![]() |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
| Attributes | |
| ACN | 1337278 |
| Time | |
| Date | 201603 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | ZZZ.Airport |
| State Reference | US |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | B737-700 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Parked |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | Tablet |
| Person 1 | |
| Function | Captain |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Experience | Flight Crew Last 90 Days 217 Flight Crew Type 8650 |
| Events | |
| Anomaly | Aircraft Equipment Problem Less Severe Deviation - Procedural Published Material / Policy |
Narrative:
My first officer mentioned something along the lines that he had some issues with his efb and was downloading an app again. Since I had checked and prepared my efb the night before; I thought 'that is strange'; but assumed it was an issue with 'his' efb. Upon arrival at the airport we received a note stating that there had been some issues with the jeppfd-pro update.I went into my duties checking the logbook; briefings; etc. Now; when I finally made it to my seat on the flight deck; I found out I had also been affected. My first officer offered his efb to be used by both of us. We flew into ZZZ; had an aircraft swap; and even the operations manager came up and offered that (based on some document he received) a 'hard reboot' may help. I tried it but it did not work. We took off and after reaching cruise flight I realized that I had incorrectly recalled information; i.e. I was in error thinking a 'loaner' was only required during dual efb failure. Since we were (for all practical purposes) single efb I bought a subscription to company wifi and by the time we landed my efb was 'up to speed.'even though I was 'unequivocally sure' of my thinking; it doesn't hurt; during 'rare' occurrences/events to 'double check' my thinking with our manuals.
Original NASA ASRS Text
Title: B737-700 Captain reported operating several legs with only one operable iPad which was contrary to company procedures.
Narrative: My FO mentioned something along the lines that he had some issues with his EFB and was downloading an App again. Since I had checked and prepared my EFB the night before; I thought 'that is strange'; but assumed it was an issue with 'his' EFB. Upon arrival at the airport we received a note stating that there had been some issues with the JeppFD-Pro update.I went into my duties checking the logbook; briefings; etc. Now; when I finally made it to my seat on the flight deck; I found out I had also been affected. My FO offered his EFB to be used by both of us. We flew into ZZZ; had an aircraft swap; and even the Operations Manager came up and offered that (based on some document he received) a 'hard reboot' may help. I tried it but it did not work. We took off and after reaching cruise flight I realized that I had incorrectly recalled information; i.e. I was in error thinking a 'loaner' was only required during dual EFB failure. Since we were (for all practical purposes) single EFB I bought a subscription to Company WiFi and by the time we landed my EFB was 'Up to Speed.'Even though I was 'unequivocally sure' of my thinking; it doesn't hurt; during 'rare' occurrences/events to 'double check' my thinking with our manuals.
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.