 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
E175 captain reported that workload and ipad limitations resulted in the aircraft exceeding 50 miles from the coast during a hold.
| Attributes | |
| ACN | 1710375 |
| Time | |
| Date | 201912 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | ZHU.ARTCC |
| State Reference | TX |
| Aircraft 1 | |
| Make Model Name | EMB ERJ 170/175 ER/LR |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Cruise |
| Flight Plan | IFR |
| Person 1 | |
| Function | Pilot Flying Captain |
| Qualification | Flight Crew Instrument Flight Crew Air Transport Pilot (ATP) Flight Crew Multiengine |
| Events | |
| Anomaly | Deviation - Procedural Published Material / Policy Deviation - Procedural FAR |
Narrative:
[Enroute to] iah; we were given new routing to mullt-LINKK1. While enroute; the airport had a 25 kt. Gain over the runway. All arrivals went into holding. We were given direct to mullt; hold as published; leg length our discretion. I opted to do 20 nm legs for passenger comfort since our efc was about 30 minutes away. During holding I was notified from dispatch that we were approximately 60 nm. Offshore. I immediately changed the holding pattern back to 10 miles hoping that would keep us within 50 miles. Before I could query ATC; they gave us vectors to ZZZ-iah. ATC never said anything about us being more than 50 miles offshore. The other factor is our ipads do not have moving maps enabled in jeppfd. If we had that; I would have thought to watch it; and put a 50 mile ring on the moving map. I called my dispatcher after landing in iah; and she told me that we had other flights going over 50 miles offshore due to houston center routing. We were not the only flight. Task saturation was also a factor. I recommend company enable the moving map capability in jeppfd-pro; it would give us much more situational awareness.
Original NASA ASRS Text
Title: E175 Captain reported that workload and iPad limitations resulted in the aircraft exceeding 50 miles from the coast during a hold.
Narrative: [Enroute to] IAH; we were given new routing to MULLT-LINKK1. While enroute; the airport had a 25 kt. gain over the runway. All arrivals went into holding. We were given direct to MULLT; hold as published; leg length our discretion. I opted to do 20 nm legs for passenger comfort since our EFC was about 30 minutes away. During holding I was notified from Dispatch that we were approximately 60 nm. offshore. I immediately changed the holding pattern back to 10 miles hoping that would keep us within 50 miles. Before I could query ATC; they gave us vectors to ZZZ-IAH. ATC never said anything about us being more than 50 miles offshore. The other factor is our iPads do not have moving maps enabled in JeppFD. If we had that; I would have thought to watch it; and put a 50 mile ring on the moving map. I called my Dispatcher after landing in IAH; and she told me that we had other flights going over 50 miles offshore due to Houston Center routing. We were not the only flight. Task saturation was also a factor. I recommend Company enable the moving map capability in JeppFD-Pro; it would give us much more situational awareness.
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.