Narrative:

We experienced a GPS loss of signal/GPS signal interference for 6 minutes near the turkey - iraq border; between otkep and ratvo waypoints at FL370. Our navigation capability remained well within the required rnp (required navigation performance). Initial indications were 'ads-B out left' EICAS (engine indicating and crew alerting system) message and 'inertial' on the navigation display. We complied with the non normal checklist.this was our first experience with a possible GPS jamming event. We referred to bulletin XXX-xx-xx 'GPS loss of signal/GPS signal interference' to troubleshoot and prepare for possible navigation degradation.the GPS returned to normal operation after 6 minutes of signal loss. Communications from the company and crewmembers have identified this route area as typical for GPS interference. After block in we referred to the fom (flight operations manual) X.xx mandatory reports as referenced in the above-mentioned bulletin. The table shows only a [safety report] and security reports are mandatory. The aml (aircraft maintenance logbook) entry box has no 'x.' accordingly; I neglected to make an aml entry regarding the GPS interference.the cause of the loss of GPS was most likely due to jamming and/or interference.neglecting to properly document and communicate the GPS issue was primarily due to my misreading of the GPS bulletin. In a rush to reference the technical part of the bulletin to assist in troubleshooting; I skimmed the administrative paragraphs and missed the 'a detailed aml write up is required for any GPS discrepancies even if the GPS function returns to normal.' I made the mistake of assuming that because the event was not caused by our equipment; an aml entry would not be required. The lack of an aml entry requirement in the fom X.xx table contributed to my error. The bulletin is controlling as it was issued subsequent to the current fom. Additionally; this was our first GPS event experience.our improper assumptions were additional causes. We assumed that a notification to ATC or [the operations center] was not necessary because we never had a loss of navigation capability and we had no aircraft system malfunctions.I believe that we made a wise choice in referring to the bulletin during this short event. However; in the future; after a 'non - normal' event is complete or stabilized; a detailed review of the QRH; bulletin or other source document would be helpful. A slower review during a low workload time would help to avoid this type of mistake. A more detailed review would have led me to make an aml entry; notify ATC and [operations center].additionally; an update to the fom table X.xx for the GPS events would help to prevent this type of error.

Related reports:

Google
 

Original NASA ASRS Text

Title: Air carrier Captain reported a possible GPS jamming event near Iraq. The Captain failed to enter the event in the AML.

Narrative: We experienced a GPS Loss of Signal/GPS Signal Interference for 6 minutes near the Turkey - Iraq border; between OTKEP and RATVO waypoints at FL370. Our navigation capability remained well within the required RNP (Required Navigation Performance). Initial indications were 'ADS-B OUT L' EICAS (Engine Indicating and Crew Alerting System) message and 'Inertial' on the NAV display. We complied with the Non Normal checklist.This was our first experience with a possible GPS jamming event. We referred to Bulletin XXX-XX-XX 'GPS Loss of Signal/GPS Signal Interference' to troubleshoot and prepare for possible navigation degradation.The GPS returned to normal operation after 6 minutes of signal loss. Communications from the company and crewmembers have identified this route area as typical for GPS interference. After block in we referred to the FOM (Flight Operations Manual) X.XX Mandatory Reports as referenced in the above-mentioned Bulletin. The table shows only a [Safety Report] and Security reports are mandatory. The AML (Aircraft Maintenance Logbook) entry box has no 'x.' Accordingly; I neglected to make an AML entry regarding the GPS interference.The cause of the loss of GPS was most likely due to jamming and/or interference.Neglecting to properly document and communicate the GPS issue was primarily due to my misreading of the GPS bulletin. In a rush to reference the technical part of the bulletin to assist in troubleshooting; I skimmed the administrative paragraphs and missed the 'A detailed AML write up is required for any GPS discrepancies even if the GPS function returns to normal.' I made the mistake of assuming that because the event was not caused by our equipment; an AML entry would not be required. The lack of an AML entry requirement in the FOM X.XX table contributed to my error. The bulletin IS controlling as it was issued subsequent to the current FOM. Additionally; this was our first GPS event experience.Our improper assumptions were additional causes. We assumed that a notification to ATC or [the Operations Center] was not necessary because we never had a loss of navigation capability and we had no aircraft system malfunctions.I believe that we made a wise choice in referring to the Bulletin during this short event. However; in the future; after a 'Non - Normal' event is complete or stabilized; a detailed review of the QRH; Bulletin or other source document would be helpful. A slower review during a low workload time would help to avoid this type of mistake. A more detailed review would have led me to make an AML entry; notify ATC and [Operations Center].Additionally; an update to the FOM Table X.XX for the GPS events would help to prevent this type of error.

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.