Spurious OVERWNG LOCK Inop Sys Displayed On Ecam: Engineering Support
Spurious OVERWNG LOCK Inop Sys Displayed On Ecam: Engineering Support
Spurious OVERWNG LOCK Inop Sys Displayed On Ecam: Engineering Support
ECAM
Engineering Support
First Issue Date: 22-JUN-2018
Model: Last Publication Date: 12-APR-2019
Manufacturer:
Applicability:
A320 family aircraft equipped with the FWC H2-F10 standard (P/N 350E053022020)
References:
MOD 162159
Background
.
The “OVERWNG LOCK” ECAM Inop Sys has been introduced in the Flight Warning
Computer (FWC) standard H2-F10 (P/N 350E053022020). This Inop Sys is normally
displayed when the Flight Lock Actuator (FLA) installed on emergency over wing door is
detected inoperative. As only A321NEO Airbus Cabin Flex (ACF) aircraft are fitted with
over wing doors, this Inop Sys indication has been developed for this aircraft model only
(A321-200NX).
The “OVERWNG LOCK” Inop Sys display is normally always associated to one of the
following ECAM alerts:
Airbus has identified that the “OVERWNG LOCK” Inop Sys computation logics in FWC H2-
F10 can result in the following incorrect displays:
- the inop sys is displayed on all A320 family aircraft models (not only on A321 ACF)
and/or
- the inop sys is orphan (i.e. not associated to any ECAM alert).
Description
.
The “OVERWNG LOCK” Inop Sys should normally be triggered according to the following
logic:
1. One flight lock actuator is detected faulty. In that case, the Inop Sys is associated with one
“DOOR L(R) (AFT(FWD)) OVERWNG FAULT” alert.
OR
2. EIU 1(2) is detected faulty, or ADR 1(2) is detected faulty or OFF. Indeed, the flight lock
actuators operation is based on EIU and ADR inputs.
However, with the FWC H2-F10 logic, the “OVERWNG LOCK” Inop Sys can be spuriously
triggered on all A320 family aircraft models (not only A321 ACF), in case EIU 1(2) is
detected faulty, or ADR 1(2) is detected faulty or OFF, in flight phase 1 or 10.
In addition, the inop sys is orphan (displayed without any associated ECAM alert) when
displayed due to the “ADR 1 or ADR 2 detected faulty or OFF” condition in flight phase 1
or 10, or due to the “EIU 1 or EIU 2 detected faulty” condition in flight phase 10. Indeed,
the corresponding alerts (NAV ADR 1(2) FAULT and respectively ENG 1(2) EIU FAULT)
are inhibited in flight phases 1 and 10 (respectively flight phase 10 only) as per FWC
design.
Recommendation
On non-ACF aircraft (aircraft models others than A321-200NX), this “OVERWNG LOCK”
Inop Sys is never relevant and can be disregarded.
On A321 ACF aircraft (model A321-200NX), the “OVERWNG LOCK” Inop Sys can be
disregarded only when it is orphan (not associated to any of the above ECAM alerts).
Otherwise, the associated ECAM alert(s) should be handled and the applicable MMEL
item(s) should be applied.
This spurious activation condition is not latched: as soon as EIUs and ADRs are not
detected faulty/OFF anymore, the INOP “OVERWNG LOCK” disappears.
Solution
The OVERWNG LOCK Inop Sys display logic will be reviewed in the FWC standard H2-F12,
which is expected to be certified by end 2019.
Additional Note
N/A