 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Crj-200 captain reported an efb malfunction while requsting essential navigation information.
| Attributes | |
| ACN | 1568563 |
| Time | |
| Date | 201808 |
| Local Time Of Day | 0001-0600 |
| Environment | |
| Flight Conditions | VMC |
| Light | Dawn |
| Aircraft 1 | |
| Make Model Name | Regional Jet 200 ER/LR (CRJ200) |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Descent |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | Electronic Flt Bag (EFB) |
| Person 1 | |
| Function | Captain Pilot Flying |
| Qualification | Flight Crew Multiengine Flight Crew Air Transport Pilot (ATP) |
| Events | |
| Anomaly | Aircraft Equipment Problem Less Severe Deviation - Procedural Clearance Deviation - Track / Heading All Types |
Narrative:
On our morning flight we were only able to navigate by VOR. We were given a new clearance to fly direct to a specific VOR. While the first officer was getting the clearance I tried to use my efb to locate the VOR frequency. The first officer was still getting the clearance and my jeppesen app froze and then shut off. We were still navigating via the original clearance. The first officer had trouble finding the VOR frequency so we asked ATC for vectors because my jepp app was still loading after about a minute. We got a heading from ATC and flew the heading because my efb failed and the first officer had difficulty finding the frequency. We were in the approach area and I knew there was significantly more traffic around so we were trying to be as quick as possible. We didn't cause any traffic deviations. The cause of the event is that my efb froze and the jepp app shut down for no reason whatsoever. Also the first officer was task saturated by talking to ATC and verifying the clearance and then having to find a VOR frequency quickly. The way to fix this problem is to get an efb that won't have these problems.
Original NASA ASRS Text
Title: CRJ-200 Captain reported an EFB malfunction while requsting essential navigation information.
Narrative: On our morning flight we were only able to navigate by VOR. We were given a new clearance to fly direct to a specific VOR. While the FO was getting the clearance I tried to use my EFB to locate the VOR frequency. The FO was still getting the clearance and my Jeppesen App froze and then shut off. We were still navigating via the original clearance. The FO had trouble finding the VOR frequency so we asked ATC for vectors because my Jepp App was still loading after about a minute. We got a heading from ATC and flew the heading because my EFB failed and the FO had difficulty finding the frequency. We were in the approach area and I knew there was significantly more traffic around so we were trying to be as quick as possible. We didn't cause any traffic deviations. The cause of the event is that my EFB froze and the Jepp app shut down for no reason whatsoever. Also the FO was task saturated by talking to ATC and verifying the clearance and then having to find a VOR frequency quickly. The way to fix this problem is to get an EFB that won't have these problems.
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.