37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1185039 |
Time | |
Date | 201406 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZZZ.TRACON |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | B737-300 |
Operating Under FAR Part | Part 121 |
Flight Phase | Descent |
Flight Plan | IFR |
Component | |
Aircraft Component | Tablet |
Person 1 | |
Function | Pilot Not Flying First Officer |
Person 2 | |
Function | Pilot Flying Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Aircraft Equipment Problem Less Severe Deviation - Altitude Overshoot Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance Flight Deck / Cabin / Aircraft Event Other / Unknown |
Narrative:
During a very busy arrival on the RNAV with multiple ATC changes in route/altitude/speed restrictions; the ipad gave 'battery at 10%' message. I elected not to revert to paper publications for two primary reasons: (1) I reasoned the battery would be sufficient to finish the flight; and (2) the arrival had been extremely busy with multiple changes to the 'descend via' clearance on the RNAV arrival; so I felt it was better to be 'in the loop' monitoring the pilot flying and handling radios. The first approach to runway xxl resulted in a go-around. While being vectored downwind for the second approach; the ipad powered down (off). We completed the approach; landing; and taxi to the gate without publications on my side (first officer side). The captain had full use of his ipad. There was an FAA evaluator on board who noticed and commented on the fact that the ipad had powered down prior to landing and that we had to taxi without the use of the first officer's ipad. Preventative measures: (1) place ipad charging system in aircraft. (2) follow company procedures to revert to paper publications when battery charge is low. (3) be cognizant of battery level at all times and extract backup paper publications during non-dynamic flight periods (cruise) if there is any possibility that the ipad battery will expire.
Original NASA ASRS Text
Title: While on a very busy RNAV arrival with multiple speed and altitude changes; a B737-300 Captain manually returned to the 9;000 FT constraint after the FMS failed to level. During the descent; the First Officer's iPad alerted 'Battery at 10%' and then auto-shut down during a second visual approach following a go-around.
Narrative: During a very busy arrival on the RNAV with multiple ATC changes in route/altitude/speed restrictions; the iPad gave 'Battery at 10%' message. I elected not to revert to paper publications for two primary reasons: (1) I reasoned the battery would be sufficient to finish the flight; and (2) the arrival had been extremely busy with multiple changes to the 'descend via' clearance on the RNAV Arrival; so I felt it was better to be 'in the loop' monitoring the pilot flying and handling radios. The first approach to Runway XXL resulted in a go-around. While being vectored downwind for the second approach; the iPad powered down (OFF). We completed the approach; landing; and taxi to the gate without publications on my side (First Officer side). The Captain had full use of his iPad. There was an FAA Evaluator on board who noticed and commented on the fact that the iPad had powered down prior to landing and that we had to taxi without the use of the First Officer's iPad. Preventative Measures: (1) Place iPad charging system in aircraft. (2) Follow Company procedures to revert to paper publications when battery charge is low. (3) Be cognizant of battery level at all times and extract backup paper publications during non-dynamic flight periods (cruise) if there is any possibility that the iPad battery will expire.
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.