Professional Documents
Culture Documents
34.36.00049
34.36.00049
Reference: 34.36.00049 Issue date: 17-JUN-2024 Last check date: 17-JUN-2024 Status: Open
A/C type/serie: A300, A300-600, A310, A318, A319, ... ATA: 34-36
Engine manufacturer: Supplier:
Purpose / Reason for revision: Main changes: ADIRU alignment during spoofing - lockup of GLU-920
Engineering Support Status: Open
Revision updates are highlighted in bold blue.
Contents
0. BACKGROUND 2
1. COCKPIT EFFECTS 3
1.1.3 A380 7
1.1.4 A350 10
1.2.1 Navigation 13
1.2.2 Surveillance 15
1.2.3 Communication 16
2. OPERATIONAL CONSIDERATIONS 17
3. MAINTENANCE RECOMMENDATIONS 19
3.2 TRANSIENT SYMPTOMS OBSERVED IN AN AREA NOT KNOWN PREVIOUSLY FOR GPS INTERFERENCE 21
3.3 EFFECTS DURING GPS INTERFERENCE OR SPOOFING EXPOSURE NOT COVERED IN CHAPTER 1 OR EVENTS REQUIRING FURTHER ANALYSIS 23
4. GLOSSARY 24
0. BACKGROUND
On most Airbus aircraft, Global Navigation Satellite System (GNSS1) signals are one of the main inputs used for aircraft positioning and time reference for on-board Communication, Navigation
and Surveillance functions. The Airbus aircraft installations are compliant with applicable regulations and recommended practices on aeronautical usage of GNSS for Communication, Navigation
and Surveillance applications.
Performance (accuracy, integrity, availability and continuity) of the aircraft positioning highly relies on the external GNSS signals. A degradation of the external GNSS signals due to external
or internal Radio Frequency Interferences (also known as “GNSS RFI” or “jamming”2) can lead to a performance degradation of the computed aircraft position. The reception of fake GNSS
signals transmitted with the intention to mislead GNSS receivers (also known as “spoofing”) may also lead to impacts on aircraft.
To ensure the robustness of the Airbus aircraft architecture, the systems also take into account inertial references and/or NAVAIDs (i.e. VOR, DME) to augment and complement the aircraft
position’s accuracy, integrity, availability and continuity.
Therefore, when GNSS signals from the satellite constellation are lost or degraded by interference or spoofing, depending on the duration, aircraft capabilities can be maintained, limited or
lost during the flight. These effects on aircraft capabilities shall be considered in flight crew decisions: for example, assessment of the capability to fly PBN routes, procedures and approaches.
The objective of this article is to clarify the impact of GNSS signal loss, GNSS RFI and GNSS spoofing on aircraft operations, and to provide recommendations on how to handle these events
in the daily aircraft operations.
Note: The STC solutions or cabin impacts (such as BFE in-flight entertainment/connectivity) are not considered in this article.
1. COCKPIT EFFECTS
This chapter covers A300-600, A310 autonomous architecture (i.e. GPS outputs are directly connected to the FMS), and A320, A330, A340, A380 and A350 aircraft in hybrid configuration
(i.e. GPS outputs sent to the IRS which sends a “hybridized” position to the FMS).
These aircraft are fitted with two MMRs, three ADIRUs and two (A300-600/A310/A320/A330/A340/A380) or three (A350) FMS to compute the aircraft position. The A/C position is used by
the FMS for navigation purposes.
1Global Navigation Satellite System (GNSS) refers to a worldwide position and time determination system that includes one or more satellite constellations, aircraft receivers and system integrity monitoring, augmented as
necessary to support required navigation performance for the intended operation. It includes the United States Global Positioning System (GPS) currently used by commercial aircraft, and augmentation systems such as
Satellite Based Augmentation System (SBAS).
2GNSS Radio Frequency Interferences (GNSS RFI): The effect of unwanted energy due to one or a combination of emissions, radiations, or inductions upon reception in the GNSS frequency band (1559 – 1610 MHz). GNSS RFI
may induce a degradation of position performance (such as lower accuracy and integrity) or loss of information.
In case GPS data is lost due to GNSS RFI affecting both MMRs, the aircraft position source will switch to pure IRS and will enter into the so-called coasting mode. If the integrity of GPIRS
data falls below a certain threshold, then the position source will switch to other radio navigation based solutions (from FMS) according to the availability of DME and VOR. If NAVAIDs are
not available, the aircraft position solution will switch to IRS only.
In the case fake GPS data is received due to spoofing, the hybridization within the ADIRS is expected to reject fake GPS data and switch to “coasting mode”.
Besides, MMRs elaborate deviations relative to a flight path and distance to a runway datum point in xLS modes such as FLS, GLS and SLS. In case GPS data is lost due to GNSS RFI affecting
both MMRs, the xLS modes GLS, SLS, FLS using GPS data will not be available.
Important note: The below described effects may be observed if an A/C is operating in an area where RFI are present. Depending on the interference features (and A/C functions), the GPS
receivers may be affected differently leading to the potential appearance of one or several of the effects described below.
ADS-B
OUTstd DO- ADSB light ON In case of spoofing, erroneous GPS parameters may be broadcast.
260B
ADS-C, ADS-C and CPDLC shall be considered as lost if the aircraft time reference
CPDLC is more than +/- 1 s from UTC reference
Aircraft
NAV ADC FM/GPS POS DISAGREE
position
With clock standard APE5100-1, when UTC selector is set on “GPS” and
the GPS 1 does not provide UTC time anymore to the clock, the clock
provides an internal time. The precision of the internal time diverges from
Clock
UTC time. The FMS predictions may also diverge.
(*) Optional function, the effects can be shown only if the option has been selected for a given A/C
(1)Spurious terrain alerts and inconsistent time jump are not systematically observed in GNSS RFI areas. Such events do not occur in case of GPS total loss. Please report
inconsistent information observed in GNSS RFI areas to Airbus to allow a safety analysis and follow-up of the event. Refer to section 3.3 for a list data needed to investigate the
event.
1.1.2 A320 Family / A330 / A340
(*) Optional function, the effects can be shown only if the option has been selected for a given A/C
Only applicable with Honeywell ADIRU Block III, as the computation of the wind speed and direction uses the hybrid GPS/IRS ground speeds (ADIRU standards before Block III
(1)
GPS total loss. Please report inconsistent information to Airbus to allow a safety analysis and follow-up of the event. Refer to section 3.3 for a list data needed to investigate the
event.
(3) Impacts are due to the SATCOM frequency band (1626.5 MHz) close to the GPS L1 frequency band (1575.42 MHz).
(4) Due to the Radio Altimeter rejection by TAWS computer during the ‘RA reasonableness check’ (which uses GPS geometric altitude).
(5) Only applicable with Collins Aerospace MMR GLU-925, P/N 822-1821-430.
Other effects:
(*) Optional function, the effects can be shown only if the option has been selected for a given A/C
Only applicable with Honeywell ADIRU Block III, as the computation of the wind speed and direction uses the hybrid GPS/IRS ground speeds (ADIRU standards before Block III
(1)
Other effects:
- In case of jamming: Data dashed on POSITION/GPS Page of both MFD
- In case of spoofing: GPS Data erroneous on POSITION/GPS Page of both MFD
- Total GPS loss leads to a red flag (“ALT”) on grey background and red scale displayed on PFD, in case no air data are available.
1.1.4 A350
(*) Optional function, the effects can be shown only if the option has been selected for a given A/C
(1)Spurious terrain/obstacle alerts and inconsistent time are not systematically observed in GNSS RFI areas. These events do not occur in case of GPS total loss. Please report
inconsistent information to Airbus to allow a safety analysis and follow-up of the event. Refer to section 3.3 for a list data needed to investigate the event.
(2) Impacts are due to the SATCOM frequency band (1626.5 MHz) close to the GPS L1 frequency band (1575.42 MHz).
(3) Due to the Radio Altimeter rejection by AESS computer during the ‘RA reasonableness check’ (which uses GPS geometric altitude).
(4) ANF applications are hosted in the core software of the CDS outer DUs.
Other effects:
- In case of jamming: Data dashed on POSITION/GNSS Page of both MFD
- In case of spoofing: GPS Data erroneous on POSITION/GNSS Page of both MFD
- Total GPS loss leads to a red flag (“ALT”) on grey background and red scale displayed on PFD, in case no air data are available.
Summary of functional and system effects
The tables below contain the functional and system effects corresponding to cockpit effects described in section 1.1.
Note: These alerts/warnings could arise in case of GNSS RFI, however all of the described functional or system effects may not be observed on every flight impacted by GNSS RFI.
1.1.5 Navigation
A320
SYSTEMS A300-600/A310 A380 A350
A330/A340
All Phases: Loss of GPS and SBAS-based Navigation functions for the duration of the loss.
All Phases: Loss of GPS-
MMR
based Navigation functions. Approach & Landing: Loss of FLS, GLS and
Approach & Landing: Loss of FLS, GLS and SLS deviations.
SLS deviations and SLS deviations.
All Phases: The hybridization between GPS measurements and If GPS data are lost and or rejected for more
IRS data is lost and GPIRS position enters into coasting mode. than 1 hour, then the ADIRU latches the
GPIRS position drifts when not updated via GPS measurements. coasting mode until the end of the flight
No effect. (TFU 34.10.00067).
During alignment: The flight crew needs to enter position manually to align IRS. In case of GPS spoofing, the
IRS may align on the spoofed position. FCOM procedure for cockpit preparation if erroneous GPS
data is observed is available on A320 and under analysis for A330/A340/A350/A380.
All Phases: Clock will not be synchronized with UTC time provided by GPS; Clock is maintained All Phases: Clock will not be synchronized
based on its internal reference. At aircraft power up the UTC displays zero’s in case of with UTC time provided by GPS; Clock is
unavailability of GPS signal. For initialization of the clock the Pilot has to manually input the maintained based on ADIRS clock function.
Clock
time, using SET, INT; if GPS is resumed then change the knob to GPS.
In case of spoofing, date and/or time may
In case of spoofing, date and/or time may be erroneous. be erroneous.
Approach & Landing: GLS Approach & Landing: GLS and SLS
parameters (deviations, course, parameters (deviations, course, and
Approach & Landing: GLS
ISIS N/A and channel) are not available. channel) are not available during approach
deviations are not available.
Aircraft position and velocity and landing. Aircraft position and velocity
coming from MMR is invalid. coming from MMR is invalid.
Approach functions requiring GPS
Approach functions requiring
are not available: GLS, FLS (in Approach functions requiring GPS are not
GPS are not available: GLS,
case of RNAV (GNSS)) and RNP available: SLS, GLS, FLS (in case of RNAV
Flight Guidance FLS (in case of RNAV (GNSS))
AR. (GNSS)) and RNP AR.
FMGC (A320) Approach function receives and RNP AR.
Non availability of Pre-Capture Non availability of Pre-Capture Zone of the
FMGEC (A330/A340) only ILS data Non availability of Pre-
Zone of the LOC Beam in case of LOC Beam in case of NAV PRIMARY loss.
FCGU/PRIM (A380&A350) Capture Zone of the LOC
GPS PRIMARY loss. The functions BTV, ROW/ROPS are not
Beam in case of GPS
The functions BTV, ROW/ROPS available
PRIMARY loss.
are not available.
All Phases: The aircraft position solution will switch from GPIRS to All Phases: The aircraft position provided by
radio NAVAIDs and inertial position. the ADIRU is used irrespective of GPS loss.
Flight Management The aircraft position solution
In case of jamming: GPS data are dashed in the GNSS monitor In case of jamming: GPS data are dashed
FMGC (A320) will switch to radio NAVAIDs
page. in the GNSS monitor page.
FMGEC (A330/A340) or inertial position.
In case of spoofing: GPS Data erroneous on GPS MONITOR In case of spoofing: GPS Data
FMS (A380&A350)
pages of MCDUs erroneous on GPS MONITOR pages of
MCDUs
Approach & Landing: The aircraft position
Airport Navigation Approach & Landing: The aircraft position cannot be computed
used by ANF is provided by ADIRU.
OANS and displayed on the airport moving map.
N/A Loss of support to Airport Navigation,
(A320/A330/A340/A380) Loss of support to Airport Navigation, Runway Approaching
Runway Approaching Advisory, BTV/ROPS
ANF (A350) Advisory and BTV/ROPS (on A380 only) functions from OANS.
and TOS2 functions from ANF.
Table 1.5: Functional and System Effect for Navigation System
Surveillance
The table below contains the functional and system effects corresponding to cockpit effects on the ND, ECAM alerts/status/ INOP sys.
A320
SYSTEMS A300-600/A310 A380 A350
A330/A340
Part of AESS Part of AESS
ATSAW function not available on A380 All Phases: Loss of ATSAW function
All Phases: Loss of ATSAW
TCAS No effect
function(*)
In case of spoofing TCAS may be lost In case of spoofing TCAS may be lost (see
(see ISI 34.48.00034) ISI 34.48.00034)
Part of AESS
All Phases: GPS parameters are invalid within ADS-B OUT All Phases: GPS parameters are invalid within ADS-B OUT messages (position integrity
messages (position integrity tagged as degraded). tagged as degraded).
XPDR Note: A380 and A350 ADS-B function is more robust with respect to A320/A330/A340 as
In case of spoofing: it is based on GPIRS position. GPIRS position enters in coasting mode and can remain
incorrect position sent via ADS-B OUT available longer than GPS position.
On A350, the ADS-B out position will depend on the SBAS activation:
- If SBAS is activated, the ADS-B OUT function is impacted as the transponder
position source is pure GPS data
- If SBAS is NOT activated, the ADS-B OUT function is not impacted as the
transponder position source is GPIRS data. Nevertheless, on long flights, the position
quality indicator could be lowered, due to IRS drifting.
Take-off, en-route & approach:
In case of invalid GPS position,
the TAWS uses the alternate
position computed by the FMS or Part of AESS.
the IRS. All Phases:
No immediate loss thanks to back-up positioning (FMS, IRS) but some degradations may
No effect Approach , Landing & on Ground be expected after certain time :
In case of invalid GPS data, : Loss of ROW/ROP ,RAAS
TAWS the TAD and TCF functions functions(**) – Potential loss of envelope modulation (when position too degraded)
(EGPWS / GPWS) will switch to data from
– Potential loss of predictive terrain alerts and display on ND (when position too
(T2CAS / T3CAS FMS. Loss of terrain function when degraded)
A320/A330/A340) GPS FOMs exceed the current
RNP according to flight phases In case of spoofing basic TAWS modes (1 to 5) may be lost (see ISI 34.48.00034)
1.1.6 Communication
A320
SYSTEMS A300-600/A310 A380 A350
A330/A340
The following articles (referenced across this document) provide additional details on some specific aircraft configurations affected by GNSS interferences:
Technical Follow Up
1. 31.21.00014 “Electrical Clock - Time drift linked to GNSS Radio Frequency Interferences”: for A300/A310/A320/A330/A380 aircraft equipped with clock APE5100-1 or APE5100-3.
2. 34.10.00066 “NAV GNSS 1(2) Rejected by IRS”: for A350 aircraft.
3. 34.36.00.030 “MMR GLU-925: GPS locked after Radio Frequency Interferences (RFI) exposure”: for aircraft equipped with COLLINS Aerospace MMR GLU-925.
4. 34.38.00.002 “Spurious RWY TOO SHORT message due to inaccurate OANC A/C position computation”: for A380 aircraft equipped with OANS standard A5.2 and A6.2.
5. 34.10.00067 “Latched ADIRU coasting mode further to long exposure to RFI”: for A350 aircraft
In Service Information
1. 34.52.00035 “NAV ADS-B RPTG x FAULT in GPS degraded environment”: for A320 and A330 aircraft
2. 46.00.00057 “FSA-NG Time acquisition”: for A350 aircraft.
3. 27.51.00042 Flaps Electrical Control and Monitoring - Consequences of clock adjustment on the WTBs for A330/A340 aircraft
4. 34.48.00034 HONEYWELL - GNSS RFI impact on EGPWS and AESS
5. 34.36.00066 COLLINS AEROSPACE - MMR GLU-920 (P/N 822-1152-1xx) - GPS locked after Radio Frequency Interferences (RFI) exposure
The effects of GNSS RFI detailed in section 1 should be considered in airline’s operations in order to ensure the safe operation of the aircraft.
Refer to the Airbus recommended procedures of the FCOM manual in section:
o A350: NORMAL PROCEDURES - SUPPLEMENTARY PROCEDURES - GNSS INTERFERENCES
o Other programs: NORMAL PROCEDURES - SUPPLEMENTARY PROCEDURES - GPS INTERFERENCES
Note: next FCOM revision for this section will include (from Apr A350/A380, May A320/A330 and Sep A300-600/A310):
A320: Update of the MMR Reset procedure (MMR GLU-920 is now included, addition of NAV ILS X(+Y) FAULT)
In addition, Airbus recommends to perform the following actions after a flight with possible GNSS RFI:
- Flight crew should report possible GNSS RFI and associated cockpit effects to the maintenance team,
- Maintenance team should apply recommended action detailed in section 3 (system tests, data collection, reporting to Airbus engineering or flight operations support),
- Operator should report any identified suspected GNSS RFI events to regional (e.g. ANSPs) and international organizations (e.g. EUROCONTROL’s Voluntary ATM Incident Reporting (EVAIR), refer to
https://www.eurocontrol.int/service/eurocontrol-voluntary-atm-incident-reporting) in order to facilitate and accelerate GNSS RFI event confirmation/resolution, and generate NOTAM to operators’
community.
Airbus has received several event reports from Operators of unexpected TAWS alerts in flight interpreted as undue and potentially linked to GNSS interferences.
The TAWS equipment installed on Airbus fleet have been certified in accordance with the applicable technical/qualification specifications and airworthiness requirements. As an input for the
vertical and horizontal position, the GPS data or Radio Altimeters are used. Nowadays, some context of operations (e.g., military areas) can interfere with the external GPS or Radio Altimeter
signal. These phenomena can generate some undue TAWS alerts.
Airbus, as an aircraft manufacturer, provides in the FCOM a directive procedure in the section PRO-ABN-SURV-[MEM] EGPWS/TAWS WARNINGS that defines how the flight crew has to react
to a real terrain threat. Outside the GNSS interference context, Airbus does not intend to introduce any delay by the introduction of conditions in the application of the TAWS warning
procedure.
Nevertheless, Airbus is well aware that the increasing number of undue predictive TAWS alerts is a significant operational burden for airlines operating the affected airspaces. Airbus
acknowledges the need to support airlines in this challenging context.
The following evolution of the FCOM SUPPLEMENTARY PROCEDURES - GPS INTERFERENCES will be available from next FCOM revision (from Apr A350/A380, May A320/A330 and Sep
A300-600/A310):
TAWS warnings may be considered cautionary during daylight VMC conditions provided the
cause of the warning can be identified immediately.
The basic GPWS modes remain operative. The consequences of the predictive
modes inhibition are described in FCOM/DSC-34-SURV
Note:
In cruise above MSA, the flight crew can set TERR SYS to OFF.
In other flight phases, the operators must perform a safety assessment based
on their knowledge of operations to adapt the procedures and the pilot briefings
to specific routes.
Over areas where undue TAWS alerts are expected, operators shall define an airline policy. For this, operators need to perform a safety assessment based on their knowledge of the context of the operations
(e.g. knowledge of the departure, cruise, approach operations, aircraft lateral and vertical position, consideration of cold weather operations, clear knowledge of the environmental conditions and terrain or
interference threats, etc…). This assessment will allow operators to adapt procedures and pilot briefings to specific routes and airports, such as:
Potentially disregard an anticipated undue TAWS alert: prepare the crew to potential undue alerts at specific locations to avoid delay in procedure application for genuine ones by making
decisions during flight.
Inhibit temporary GPWS predictive modes (TERR PB-SW OFF / TERR SYS OFF on MFD) over areas where predictive Undue TAWS alerts are expected to be recurrent.
Important notes :
Inhibition of GPWS predictive modes implies a deactivation of a Safety Net. Thus, it requires an associated procedure ensuring the reactivation after leaving the affected area in
a timely manner.
GPWS predictive modes inhibition in approach can lead to an increased risk of Mode 2 nuisance TAWS alerts at certain locations (e.g., cliff on the approach path). Further
information is given below in “design specificities”.
The decision to inhibit the predictive GPWS predictive modes must not be based on flight crew judgment only but briefed before the flight.
As the interference threat evolves with time, we recommend updating the threat analysis on a regular basis.
The following design specificities shall be taken into consideration for safety assessment and guidelines definition:
The GPS deselection via MCDU or MFD has not impact on TAWS:
o GPS deselection only inhibits the use of GPS inputs for the navigation data computation. It leads to GPS PRIMARY LOST (NAV PRIMARY LOST on A350). The TAWS system will still
use GPS based data, if available, regardless of the GPS deselection.
GPWS predictive modes, based on a terrain database, use GNSS inputs as primary position source. An inconsistent GNSS position input can lead to an Undue predictive TAWS alert.
GPWS basic modes do not use GNSS based inputs.
These alerts are as per design but not appropriate in the particular context of the A/C flying the published approach path.
3. Maintenance RECOMMENDATIONS
The alerts described in section 1 may point to a real defect of a system. In order to confirm that the events were not due to equipment failure, maintenance actions need to be carried out.
Airbus is currently working on troubleshooting tasks dedicated to handle GNSS RFI events. These tasks are expected to become available in the 2nd half of 2024.
Prior to availability of the above-mentioned troubleshooting tasks and in case of confirmed or suspected GNSS interference in flight, Airbus recommends performing the following actions
once on ground:
Note: The list of associated maintenance tasks references can be found in Table 3.1
1. Reset both MMR 1 and MMR 2 (power off >10 sec)
2. If GPS function is affected:
o Perform MMR 1 and MMR 2 BITE test
o Perform IR system test (Step not applicable to A300-600/A310)
3. If GLS, SLS or FLS functions are affected, perform MMR 1 and MMR 2 BITE test (if not performed in previous step)
4. If ADS-B Out function was affected, perform ATC1 and ATC2 BITE test
5. If OANS function was affected, perform OANS BITE test (Step not applicable to A300-600/A310)
6. If TAWS function was affected, perform
o TAWS BITE test
o A320/A330/A340 family: Reset Honeywell EGPWS
o A350/A380: Reset both Honeywell AESU
7. If ADS-B In (ATSAW) function was affected, perform TCAS BITE test (Step not applicable to A300-600/A310)
8. If ROW/ROP function was affected, perform (Step not applicable to A300-600/A310)
o A320/A330/A340/A350 family: GPWS BITE test
o A380: OANS system test
If all the tests are OK neither further troubleshooting nor LRU removal is required. Please, note that new LRUs will exhibit same behavior when exposed to the same interferences.
Note: With Collins MMR GLU-920, GLU-925 the following faults will be recorded on the PFR if the MMR is not able to track satellites during more than 15 minutes.
- GPS ANTENNA1(43RT1) /COAX CABLE/MMR1(40RT1)) and/or
- GPS ANTENNA2(43RT2) /COAX CABLE/MMR2(40RT2))
In this case, the fault is associated to TSD: “GLS-P NO SATELLITES TRKD” or “GLS-M NO SATELLITES TRKD”.
If triggered over known RFI area, no GPS antenna issue is to be suspected.
With newer MMR standards, Collins GLU-2100 and Honeywell IMMR, no GPS antenna fault is raised with no satellite tracked. After 15 minutes of satellite loss, the following faults are
logged:
- MMR1(40RT1) /SIGNAL IN SPACE FEEDBACK and/or
- MMR2(40RT2) /SIGNAL IN SPACE FEEDBACK
Special cases:
- If the GPS interference is still present on ground, the tests might not pass. In case of known interference on ground, the operator can either move the A/C to a non-affected location or apply MEL for
affected equipment. System’s nominal behavior should be retrieved soon after leaving the interference area.
- Please report the event to AIRBUS if normal system behavior was not recovered after exiting the RFI area.
TRANSIENT SYMPTOMS OBSERVED IN AN AREA NOT KNOWN PREVIOUSLY FOR GPS INTERFERENCE
In case a GNSS RFI is suspected and the area is not known to be affected (no NOTAM entry or previous experience), an analysis needs to be performed in order to confirm the root cause.
The analysis consists in the study of all potential sources of GNSS perturbation: aircraft and/or receiver failure, GNSS constellation anomaly, environment masking, multipath or space
weather. In case all of those potential sources are discarded, then it is likely that a GNSS RFI occurred.
Please report such a case to AIRBUS together with further information in order to allow an assessment of the event and to confirm if it can be linked to RFI or if regular troubleshooting is
required on A/C.
Note for SAR files: SARxx file name contains the date and time of recorded data:
Example: SAR00585810181120043231 –> SAR 58; Date 20 Nov 2018; Time 04:32:31 UTC
Note: Reports of suspected GNSS outage or RFI should be transmitted to international organizations (e.g. EUROCONTROL's Voluntary ATM Incident Reporting (EVAIR), refer to
https://www.eurocontrol.int/service/eurocontrol-voluntary-atm-incident-reporting) or regional ANSPs in parallel of Airbus analysis, in order to produce an additional analysis of the GNSS
signals, accelerate GNSS RFI event confirmation/resolution, and generate NOTAM to operators’ community.
EFFECTS DURING GPS INTERFERENCE OR SPOOFING EXPOSURE NOT COVERED IN CHAPTER 1 OR EVENTS REQUIRING FURTHER ANALYSIS
If an A/L suspects GNSS RFI and observes effects not covered in chapter 1 (or defined in chapter 1, but referring to this section 3.3), we recommend contacting AIRBUS for further event
analysis. For instance, AIRBUS has received reports about different kind of events potentially linked to GNSS RFI exposure such as map shift or ADS-B Out erroneous position.
We recommend A/Ls to provide AIRBUS with the following information along with the event report to help events analysis:
A300 / A310 A320 / A330 / A340 A380 A350
General GPS N/A As minimum information please provide:
analysis Post Flight Report Post Flight Report Post Flight Report
information CMS dump CMS dump
(Equivalent Flight data: Flight data: Flight data: Flight data:
to Table 3.2) - DFDR/QAR - DFDR/QAR - DFDR/QAR - DFDR/QAR
- DAR if customization - SAR 58 (this report - SAR 99 (this report
available including contains useful GPS contains useful GPS
additional GPS/ADIRU information) information)
parameters
Pilot Report: Pilot Report: Pilot Report: Pilot Report:
- Detailed event report - Detailed event report - Detailed event report - Detailed event report
- Picture of FMS CDU - Picture of FMS pages in - POSITION/GPS Page - POSITION/GNSS Page
pages: MCDU: status during events ( status during events (
- GPS MONITOR - GPS MONITOR MFD) MFD)
- POSITION MONITOR - POSITION MONITOR
- - IRS MONITOR
In case of an - Air Traffic Control report together with ADS-B raw data containing position + integrity information (data to be requested
by A/L to authorities, not usually available at A/L level)
ADS-B Out - ATC transponder side in use during events
issue - Was the pilot requested to switch transponder? Did the situation change if done?
In case of Photos/videos of ND showing erroneous weather Photos/videos of ND showing erroneous weather
WXR related display display
issues
Not possible to dump AESU on wing. A/L can contact
Honeywell representatives.
Other N/A FMS dump: FMS dump : FMS dump:
- A320: AMM TASK 22- - AMM TASK 22-70-00- - MP TASK A350-A-22-
70-00-610-006 860-804-A 7X-XX-01003-752A-A
- A330: AMM TASK 22-
70-00-610-008
A/C Aircraft
ACMS Aircraft Condition Monitoring System
ADIRS Air Data and Inertial Reference System
ADIRU Air Data and Inertial Reference Unit
AESS Aircraft Environment Surveillance System
AFN ATC Facilities Notification
ANF Airport Navigation Function
ATSAW Airborne Traffic Situation Awareness
ATSU Air Traffic Service Unit
BTV Brake To Vacate
BUSS Back Up Speed Scale
CFDIU Central Fault Display Interference Unit
CFDS Central Fault Display System
CMC Central Maintenance Computer
CMS Central Maintenance System
DAR Digital AIDS Recorder (A320)
DAR Digital ACMS Recorder (A330/A340/A380)
DBUS Digital Backup Speed
DFDR Digital Flight Data Recorder
DLCS Data Loading Configuration System
DMC Display Management Computer
DME Distance Measuring Equipment
ECAM Electronic Centralized Aircraft Monitoring
EFB Electronic Flight Bag
EGPWC Enhanced Ground Proximity Warning Computer
EGPWS Enhanced Ground Proximity Warning System
EICU EFB interface Control Unit
EIS Electronic Instrument System
EIU Electronic Instrument Unit
EPE Estimated Position Error
EPU Estimated Position Uncertainty
FANS Future Air Navigation System
FDIF Flight Data Interface Function
FLS FMS Landing System
FMC Flight Management Computer
FMG Flight Management Guidance and (Envelope)
(E)C Computer
FMS Flight Management System
FOM Figure Of Merit
FOMAX Flight Operation and MAintenance eXchanger
FWC Flight Warning Computer
FWS Flight Warning System
GBAS Ground Based Augmentation System
GLS GBAS Landing System
GNSS Global Navigation Satellite System
GPIRS GPS and IRS mixed data
GPS Global Positioning System
GPWC Ground Proximity Warning System
HDOP Horizontal Dilution Of Precision
HFOM Horizontal Figure Of Merit
HIL Horizontal Integrity Limit
HIPL Horizontal Integrity Protection Level
HUD Head Up Display
HUDC Head Up Display Computer
IFE In Flight Entertainment
IRS Inertial Reference System
ISIS Integrated Standby Instrument System
LOC Localizer
ELT Emergency Locator Transmitter
MCDU Multipurpose Control Display Unit
MFD Multi Functions Display
MMR Multi-Mode Receiver
ND Navigation Display
NSE Navigation System Error
OANS Onboard Airport Navigation System
PFD Primary Flight Display
PRAIM Predictive Receiver Autonomous Integrity
Monitoring
PRIM PRIMary System
PVT Position, Velocity, Time
RAAS Runway Awareness and Advisory System
RFI Radio Frequency Interference
RNP Required Navigation Performance
RNP AR Required Navigation Performance Authorization
Required
ROPS Runway Overrun Prevention System
ROW Runway Overrun Warning
RVSM Reduced Vertical Separation Minima
SATCOM SATellite COMmunication
SBAS Satellite Based Augmentation System
SCI Secure Communication Interface
SLS SBAS Landing System
TAWS Terrain Avoidance and Warning System
TCAS Traffic Alert and Collision Avoidance System
TOS Take Off Securing
UTC Universal Time Coordinated
VDOP Vertical Dilution Of Precision
VHF Very High Frequency
General Information
Potential impact: Maintenance, Operational Reliability
Key information:
Solution benefit:
First issue date: 22-FEB-2019 Issue date: 17-JUN-2024 Last check date: 17-JUN-2024
Technical parameters
ATA: 34-36
A/C type/serie: A300, A300-600, A310, A318, A319, A320, A321, A330, A340, A350, A380
Engine:
Engine manufacturer:
Fault code/ECAM
warning:
FIN:
Part Number:
Supplier:
Attachments
General:
- ISI_34.36.00049_Summary.docx
Links
Other articles (ISI/TFU):
- 31.21.00014, 34.10.00066, 34.36.00.030, 34.38.00.002, 34.52.00035, 46.00.00057
© Airbus SAS, 2024. All rights reserved. Confidential and proprietary document.The technical information provided in this article is for convenience and information purposes only. It
shall in no case replace the official Airbus technical or Flight Operations data which shall remain the sole basis for aircraft maintenance and operation. These recommendations and
information do not constitute a contractual commitment, warranty or guarantee whatsoever. They shall not supersede the Airbus technical nor operational documentation; should
any deviation appear between this article and the Airbus or airline's official manuals, the operator must ensure to cover it with the appropriate document such as TA, FCD, RDAS.
Access to WISE is supplied by Airbus under the express condition that Airbus hereby disclaims any and all liability for the use made by the user of the information contained in
WISE. It shall be used for the user's own purposes only and shall not be reproduced or disclosed to any third party without the prior consent of Airbus.