37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1460588 |
Time | |
Date | 201706 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | EIDW.Airport |
State Reference | FO |
Environment | |
Flight Conditions | IMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | B757 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Approach |
Route In Use | STAR OSGAR 1R |
Flight Plan | IFR |
Component | |
Aircraft Component | Tablet |
Person 1 | |
Function | Captain Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Flight Engineer Flight Crew Instrument Flight Crew Multiengine |
Experience | Flight Crew Last 90 Days 200 Flight Crew Total 24000 Flight Crew Type 9000 |
Events | |
Anomaly | Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
While flying osgar 1R star into dublin; ireland; we received short notice clearance to hold at babon fix. Due to short notice; arriving from west; and having our efbs zoomed in to read STAR info; we never saw the babon holding pattern depicted in separate inset on extreme right side of plate. Since no hold was depicted at fix; we queried controller as to what type of pattern he wanted us to fly at babon. He said a standard pattern; so we held on inbound course; right turns. After being vectored shortly after entering the holding; we finally saw the inset with holding pattern at babon. It showed holding on different inbound course from different feeder fix with a left turn. It seemed no loss of separation occurred; as we were actually in the holding airspace for the most part. There is an easy fix: show depicted holding patterns at the fix on the plate. If unable due to [chart] congestion; then a ball note or something similar directing the pilot to look elsewhere would be appropriate. As nice as the efb is; it presents a whole new set of problems. If we'd been using a paper chart; this might not have happened. Though we have been warned about this issue; the combination of having the efb slewed/zoomed in a different direction and the short amount of time set us up for this. Also; even though we queried the controller; he was of no help whatsoever. If he had used the terminology hold as depicted; I'm sure we would have found the appropriate pattern; and this whole occurrence could have been avoided.
Original NASA ASRS Text
Title: B757 Captain reported a track deviation on a holding pattern that was not depicted on the fix and not visible during the close-in EFB view.
Narrative: While flying OSGAR 1R star into Dublin; Ireland; we received short notice clearance to hold at BABON fix. Due to short notice; arriving from west; and having our EFBs zoomed in to read STAR info; we never saw the BABON holding pattern depicted in separate inset on extreme right side of plate. Since no hold was depicted at fix; we queried controller as to what type of pattern he wanted us to fly at BABON. He said a standard pattern; so we held on inbound course; right turns. After being vectored shortly after entering the holding; we finally saw the inset with holding pattern at BABON. It showed holding on different inbound course from different feeder fix with a left turn. It seemed no loss of separation occurred; as we were actually in the holding airspace for the most part. There is an easy fix: show depicted holding patterns at the fix on the plate. If unable due to [chart] congestion; then a ball note or something similar directing the pilot to look elsewhere would be appropriate. As nice as the EFB is; it presents a whole new set of problems. If we'd been using a paper chart; this might not have happened. Though we have been warned about this issue; the combination of having the EFB slewed/zoomed in a different direction and the short amount of time set us up for this. Also; even though we queried the controller; he was of no help whatsoever. If he had used the terminology hold as depicted; I'm sure we would have found the appropriate pattern; and this whole occurrence could have been avoided.
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.