ED Decision 2014/004/R
Summary of
the guidance items:
|
Item |
ATA |
|
Autopilot |
22-10-1 |
|
Flight Director |
22-10-2 |
|
Navigation Databases (MC) |
22-71-1 |
Aircraft applicability: Aeroplanes & Helicopters
ATA Chapter: 22 Autoflight |
|
|||||
|
|
|
|||||
|
(1) System
& Sequence Numbers |
(2) Rectification
Interval |
|||||
|
ITEM |
|
(3) Number
installed |
||||
|
|
|
|
(4) Number
required for dispatch |
|||
|
|
|
|
|
(5) Remarks
or Exceptions |
||
|
|
|
|
|
|
|
|
|
22-10-1 |
Autopilot (or Autopilot Channel) |
|
|
|
|
|
|
22-10-1A |
(Other than CAT) |
C |
- |
0 |
(M) (O) May be inoperative provided: |
|
|
|
|
|
|
|
(a) Affected autopilot/channel is
deactivated, and (b) Affected autopilot/channel is not
part of the equipment required for intended operation. |
|
|
|
|
|
|
|
Procedures (M) To give guidance on a practical mean
to ensure that the affected autopilot/channel will not engage during the
flight, and (O) To specify any applicable restriction for operations requiring a specific approval (e.g. PBN/MNPS, RVSM, Low Visibility, ETOPS, etc.) |
|
|
22-10-1B |
(CAT) |
C |
- |
1 |
(M) (O) Any in excess of one may be inoperative provided: |
|
|
|
|
|
|
|
(a) Affected
autopilot/channel is deactivated, and (b) Affected
autopilot/channel is not part of the equipment required for intended
operation. |
|
|
|
|
|
|
|
Procedures See 22-10-1A |
|
|
(continued) |
|
|
|
|
||
ATA Chapter: 22 Autoflight |
|
|||||
|
|
|
|||||
|
(1) System
& Sequence Numbers |
(2) Rectification
Interval |
|||||
|
ITEM |
|
(3) Number
installed |
||||
|
|
|
|
(4) Number
required for dispatch |
|||
|
|
|
|
|
(5) Remarks
or Exceptions |
||
|
(continued) |
|
|
|
|
||
|
22-10-1C |
(CAT) |
B |
- |
0 |
(M) (O) May be inoperative provided: |
|
|
|
|
|
|
|
(a) Any increase in crew workload caused
by the affected autopilot/channel has been considered for intended
operation, (b) Operations are conducted under VFR for
single pilot operations, (c) Affected autopilot/channel is deactivated,
and (d) Affected autopilot/channel is not part of the equipment required for intended operation. |
|
|
|
|
|
|
|
Procedures See 22-10-1A |
|
|
22-10-1-1 |
Autopilot Functions/Modes |
|
|
|
|
|
|
22-10-1-1 |
(CAT) |
C |
- |
- |
(M) (O) One or more functions/modes may be inoperative provided: |
|
|
|
|
|
|
|
(a) Any increase in crew workload caused
by the inoperative functions/modes has been considered for intended
operation, (b) Inoperative functions/modes are
deactivated as applicable, (c) Autopilot heading mode and altitude
hold are operative, and (d) Affected functions/modes are not
part of the equipment required for intended operation. |
|
|
|
|
|
|
|
Procedures (M) To
give guidance reference to ensure the affected function of the autopilot are
properly deactivated and do not interact with functions used for the flight. (O) See 22-10-1A |
|
Additional considerations:
If the autopilot or autopilot functions are required to meet airworthiness requirements (e.g. stabilisation function for rotorcraft, single pilot IFR, etc.), this needs to be taken into account as part of the MMEL evaluation and compliance with CS-MMEL requirements has to be demonstrated.
Some autopilot installations are not dependent on flight director being operative, and basic attitude modes may still be available.
For highly integrated systems the autopilot may not function without the flight director, and therefore autopilot inoperative relief would also apply (see guidance item 22-10-2).
If flight director modes of the autopilot are used to show compliance with requirements applicable to the means of measuring and indicating turn and slip, aircraft attitude or stabilised aircraft heading, in combination with instruments, additional restrictions related to the loss of associated indications may be applicable.
For the intended operations, any increase in crew workload caused by the inoperative functions has to be considered. This condition needs to be specified in the MMEL (e.g. number of flights, leg duration, etc.)
Any additional limitations (e.g. flight time) may result from the above review.
Applicable operating minima (e.g. CAT2/CAT3 operations) or navigation specifications (e.g. B-RNAV, RNP) requirements may be specified at the level of the MMEL or refer to appropriate section of AFM or Operations Manual. The above guidance shows these restrictions covered at operational procedures level but having them reflected at dispatch conditions level is also acceptable.
If the aircraft is certified for ETOPS operations, associated restrictions may be included, as appropriate.
The above guidance indicates the need to deactivate the affected autopilot/channel for dispatch. Some autopilot design may not offer the possibility to fully comply with this requirement. Alternate conditions can in these cases be proposed provided adequate safeguards against erratic autopilot behaviour are demonstrated.
22-10-1C:
For single pilot CAT operations, depending on the use of autopilot in routine procedures, the operations may be restricted to day VMC only.
22-10-1-1 sub-item covers failure of functions of the autopilot, which do not lead to the disconnection of the associated autopilot (autopilot channel).
Aircraft applicability: Aeroplanes & Helicopters
ATA Chapter: 22 Autoflight |
|
|||||
|
|
|
|||||
|
(1) System
& Sequence Numbers |
(2) Rectification
Interval |
|||||
|
ITEM |
|
(3) Number
installed |
||||
|
|
|
|
(4) Number
required for dispatch |
|||
|
|
|
|
|
(5) Remarks
or Exceptions |
||
|
|
|
|
|
|
|
|
|
22-10-2 |
Flight Director Symbols (FD Bars) |
|
|
|
|
|
|
22-10-2A |
|
C |
- |
- |
(O) May be inoperative provided: |
|
|
|
|
|
|
|
(a) Affected flight director is not part
of the equipment required for intended operation, and (b) Associated autopilot, if affected, is considered inoperative (Refer to 22-10-1). |
|
|
|
|
|
|
|
Procedures (O) To specify any applicable restriction for operations requiring a specific approval (e.g. PBN/MNPS, RVSM, Low Visibility Operations (LVO), etc.) |
|
Additional considerations:
This item covers display of symbols only (e.g. FD bars).
A shorter rectification interval or a minimum of one FD bars operative may be required based on operational considerations such as the amount of reliance that is placed on the FD and the level of training with the FD inoperative. Additional restrictions due to considerations on the autopilot items may also be applicable in case of integrated architecture.
AFM limitations that may identify any approaches that cannot be flown if the FD is inoperative as a result of certification flight tests have to be taken into account.
Aircraft applicability: Aeroplanes & Helicopters:
ATA Chapter: 22 Autoflight |
|||||
|
(1) System & Sequence Numbers |
(2) Rectification
Interval |
||||
|
ITEM |
|
(3) Number
installed |
|||
|
|
|
|
(4) Number
required for dispatch |
||
|
|
|
|
|
(5) Remarks
or Exceptions |
|
|
22-71-1 |
Navigation Database (MC) |
|
|
|
Note: A database which is out of date is considered to be inoperative. |
|
22-71-1A |
|
C |
- |
0 |
(O) One or more may be inoperative for the intended flight route where conventional (non-RNAV/RNP) navigation is sufficient, provided |
|
|
|
|
|
|
(a) Current aeronautical information (e.g. charts) is available for the entire route and for the aerodromes to be used, and (b) Navigation database information is disregarded, and (c) Radio navigation aids, which are required to be flown for departure, arrival and approach procedures are manually tuned and identified. |
|
|
|
|
|
|
Procedures (O) To give guidance reference to established operator’s procedure to ensure the dispatch conditions requirements are met prior to release of the aircraft. |
|
22-71-1B |
|
C |
- |
1 |
(O) Any in excess of one may be inoperative provided: |
|
|
|
|
|
|
(a) The
operative database must be up to date for routes, departures, arrival and
approach procedures that require the use of navigation Database for
RNAV/RNP, and (b) The
operative database is available and used by the flight crew member(s)
responsible for navigation, and (c) Radio navigation aids, which are required to be flown for departure, arrival and approach procedures are manually tuned and identified. |
|
|
|
|
|
Procedures (O) To give guidance reference to established operator’s procedure to ensure dispatch conditions requirements are met prior to release of the aircraft. |
|
|
(continued) |
|
|
|
|
|
ATA Chapter: 22 Autoflight |
|
|||||
|
|
|
|||||
|
(1) System & Sequence Numbers |
(2) Rectification Interval |
|||||
|
ITEM |
|
(3) Number installed |
||||
|
|
|
|
(4) Number required for dispatch |
|||
|
|
|
|
|
(5) Remarks or Exceptions |
||
|
(continued) |
|
|
|
|
||
|
22-71-1C |
|
A |
- |
0 |
(O) One or more may be out of date for a maximum of 10 calendar days provided: |
|
|
|
|
|
|
|
(a) Area Navigation (RNAV/RNP) departure, arrival and approach procedures are checked not to depend on the data amended in the current database cycle or Conventional (Non-RNAV/RNP) or ANSP assistance are used as an alternative to RNAV/RNP procedures which have been amended in the current database cycle, (b) Before each flight, current aeronautical information is used to verify the database Navigation Fixes, the coordinates, frequencies, status (as applicable) and suitability of Navigation Facilities required for the intended flight route, and (c) Radio navigation aids, which are required to be flown for departure, arrival and approach procedures and which have been amended in the current database cycle, are manually tuned and identified. |
|
|
|
|
|
|
|
Procedures (O) To give guidance reference to established operator’s procedure to ensure the dispatch conditions requirements are met prior to release of the aircraft. |
|
Additional considerations:
The item in the current guidance is separated into two set of provisos:
— 22-71-1B applicable when RNAV/RNP operations are not conducted (C rectification interval), and
— 22-71-1C applicable to operations where RNAV/RNP may be conducted (A rectification interval maximum 10 calendar days). The wording of condition (a) may be customised to the specific types of operations intended to be conducted.
This is to reduce the exposure time for aircraft navigated in RNAV/RNP airspace with downgraded capability due to outdated databases.
Condition (c) is required for system design where the radio navaids are automatically tuned by using the database data.
EASA aircraft dispatch regulations allow for inoperative autopilot, flight director, or navigation databases under specific conditions. Dispatch is permitted with deactivated or non-essential equipment, considering crew workload and operational restrictions like CAT II/III or ETOPS. Outdated navigation databases have limited grace periods if conventional navigation is used and verified.
* Summary by Aviation.Bot - Always consult the original document for the most accurate information.
Loading collections...