37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1349522 |
Time | |
Date | 201604 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | EISN.ARTCC |
State Reference | FO |
Environment | |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Widebody Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
Route In Use | Oceanic |
Flight Plan | IFR |
Component | |
Aircraft Component | Electronic Flt Bag (EFB) |
Person 1 | |
Function | Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Total 14587 Flight Crew Type 5370 |
Events | |
Anomaly | Deviation - Procedural Published Material / Policy |
Narrative:
We were filed on nat C with a routing of gapli dinim n50w020. While requesting our oceanic clearance and a review of both jepp pro in the ipad and the jepp paper enroute chart seemed to show a disagreement in the labeling of airspace from gapli to dinim. Jepp pro showed that airspace a eggx or shanwick oceanic; jepp at 1/2 chart showed that airspace as shannon domestic ats. Also touching and holding gapli in jepp pro to look under 'usage' jepp pro indicated gapli as the oceanic gateway point; which I believe is incorrect. Where this has a bearing is that if gapli were in fact the oceanic gateway fix for entry into eggx; that would be where we would be using that as the entry point for the oceanic clearance and nat; which it was not. We requested our oceanic with the entry of dinim and received our oceanic clearance properly. We then called shanwick clearance on voice to confirm that dinim was in fact the oceanic entry and were told that dinim was the entry point and gapli was in shannon domestic airspace. It appears according to that information; that jepp pro is not depicting the airspace properly. We also sent an ACARS [company message] to alert the nav database people of the issue; but not sure if they handle jepp pro issues or just aircraft onboard database issues.no deviations; but airspace questions on the disagreements between the paper source doc and jepp pro. There were no enroute NOTAMS indicating an issue to the airspace depiction disagreement; or company NOTAM; or bulletin that was current; that we were aware of.
Original NASA ASRS Text
Title: A Captain flying the NAT C oceanic route westbound discovered the iPad JEPP PRO incorrectly depicted GAPLI as the Oceanic Gateway waypoint when DINIM at the EISN to EGGX airspace transition is the correct Gateway waypoint.
Narrative: We were filed on NAT C with a routing of Gapli Dinim N50W020. While requesting our oceanic clearance and a review of both Jepp Pro in the IPad and the Jepp paper enroute chart seemed to show a disagreement in the labeling of airspace from Gapli to Dinim. Jepp Pro showed that airspace a EGGX or Shanwick Oceanic; Jepp AT 1/2 Chart showed that airspace as Shannon domestic ATS. Also touching and holding Gapli in Jepp Pro to look under 'usage' Jepp Pro indicated Gapli as the Oceanic Gateway Point; which I believe is incorrect. Where this has a bearing is that if Gapli were in fact the Oceanic Gateway fix for entry into EGGX; that would be where we would be using that as the entry point for the oceanic clearance and NAT; which it was not. We requested our oceanic with the entry of Dinim and received our oceanic clearance properly. We then called Shanwick Clearance on voice to confirm that Dinim was in fact the oceanic entry and were told that Dinim was the entry point and Gapli was in Shannon domestic airspace. It appears according to that information; that Jepp Pro is not depicting the airspace properly. We also sent an ACARS [company message] to alert the nav database people of the issue; but not sure if they handle Jepp Pro issues or just aircraft onboard database issues.No deviations; but airspace questions on the disagreements between the paper source doc and Jepp Pro. There were no enroute NOTAMS indicating an issue to the airspace depiction disagreement; or company NOTAM; or bulletin that was current; that we were aware of.
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.