IOSA Standards Manual ISM Ed. 11
IOSA Standards Manual ISM Ed. 11
IOSA Standards Manual ISM Ed. 11
11th Edition
NOTICE
DISCLAIMER. The information contained in this
publication is subject to constant review in the light
of changing government requirements and regula-
tions. No subscriber or other reader should act on
the basis of any such information without referring
to applicable laws and regulations and/or without
taking appropriate professional advice. Although
every effort has been made to ensure accuracy, the
International Air Transport Association shall not be
held responsible for any loss or damage caused by
errors, omissions, misprints or misinterpretation of
the contents hereof. Furthermore, the International
Air Transport Association expressly disclaims any
and all liability to any person or entity, whether a
purchaser of this publication or not, in respect of
anything done or omitted, and the consequences
of anything done or omitted, by any such person or
entity in reliance on the contents of this publication.
16 Authority................................................................................................................................... INT 7
3.13 Flight Deck, Passenger Cabin, Supernumerary Compartment Coordination ......................FLT 124
Table 2.10–Guidance Material: Required Aircraft Systems and Equipment ..........................................FLT 170
4.5 Operations Beyond 60 Minutes from an En Route Alternate Airport and Extended
Diversion Time Operations (EDTO) .....................................................................................DSP 78
Appendix A ............................................................................................................................................ A 01
Section 1
Organization and Management System (ORG) ORG 1 to ORG 52 April 2017
Section 2
Flight Operations (FLT) FLT 1 to FLT 176 April 2017
Section 3
Operational Control and Flight Dispatch (DSP) DSP 1 to DSP 98 April 2017
Section 4
Aircraft Engineering and Maintenance (MNT) MNT 1 to MNT 60 April 2017
Section 5
Cabin Operations (CAB) CAB 1 to CAB 70 April 2017
Section 6
Ground Handling Operations (GRH) GRH 1 to GRH 60 April 2017
Section 7
Cargo Operations (CGO) CGO 1 to CGO 32 April 2017
Section 8
Security Management (SEC) SEC 1 to SEC 34 April 2017
• SEC section: Revised wording in multiple provisions to more closely harmonize the elements of SeMS
with the elements of SMS.
• Appendix – Mandatory Observation Checklists added
Introduction
Area Changed Description of Change(s)
1 Purpose • Editorial change: Paragraphs rearranged for improved order.
4 Applicability of ISARPs • Technical change: Paragraph added to explain applicability of aircraft
systems and equipment specifications.
5 Explanation of ISARPs • Technical change: Wording added to address Special Review
Suspension; description of the convention used to identify a
suspended standard or sub-specification(s) within a standard when a
new edition of the ISM is published.
6 Guidance Material • Technical change: Wording added/revised to address General
Guidance.
7 Operational Audit • Editorial change: Sub-header changed to Outsourced Operational
Functions for consistency with other references in the ISM.
8 Safety Management System • Technical change: Note added to explain relationship between safety
and security in the ISM.
13 Conflicting Information • Editorial changes: Wording revised to improve description of potential
conflicts between the DGR and the ISM.
Section 1 (ORG)
Area Changed Description of Change(s)
General (changes that are • None.
applied multiple times)
Standards Eliminated • Two (2): ORG 3.3.4, ORG 3.4.5.
Standards Suspended • One (1): ORG 3.5.5
Standards Added • None.
Recommended Practices • None.
Eliminated
Recommended Practices • None.
Added
Applicability Box • None.
General Guidance • None.
Subsection 1.1 • Editorial change: Wording in title revised; improves description of
ISARPs in subsection.
ORG 1.1.10 Guidance • Technical change: Error corrected (number of ICAO Framework
elements).
ORG 1.3.1 • Editorial change: Wording in note revised for accuracy.
ORG 1.3.1 Guidance • Editorial change: Term added to IRM reference.
• Technical changes: Wording revised to (1) provide expanded
explanation of the flow of responsibilities and accountability within a
management system, and (2) clarify what is meant by “lines” of safety
accountability.
ORG 1.4.1 Guidance • Editorial change: Wording added to provide expanded information
regarding communications methods; relocated from CGO 1.3.1; will be
used as reference in other sections.
ORG 1.4.2 • Editorial change: Wording revised to improve expression of intent.
ORG 1.4.2 Guidance • Technical change: Wording added to describe sources for information
relevant to safety performance.
ORG 1.5.2 • Editorial change: Repeat symbol added (repeated in SEC section)
ORG 1.6.5 Guidance • Technical change: Reference to ORG 3.5.5 deleted; no longer
accurate.
ORG 3.3.2 • Technical change: Sub-spec iii) added; relocated from (eliminated)
ORG 3.3.4.
ORG 3.3.2 Guidance • Editorial change: Wording revised to improve clarity.
• Technical change: Wording added; relocated from (eliminated)
ORG 3.3.4 guidance.
ORG 3.3.4 • Eliminated; Redundant; marked as placeholder (intentionally open);
some deleted material incorporated into ORG 3.3.2 and guidance.
ORG 3.3.13 • Technical change: Wording in note revised; PCO expiry extended.
ORG 3.4.2 • Technical change: Sub-spec iii) added; relocated from (eliminated)
ORG 3.4.5.
ORG 3.4.2 Guidance • Technical change: Wording added; relocated from (eliminated)
ORG 3.4.5 guidance.
• Editorial change: Wording revised to improve clarity.
ORG 3.4.5 • Eliminated; Redundant; marked as placeholder (intentionally open);
some deleted material incorporated into ORG 3.4.2 and guidance.
ORG 3.4.7 Guidance • Editorial change: Wording deleted; redundant.
ORG 3.4.8 Guidance • Editorial change: Wording deleted; redundant.
ORG 3.5.1 • Technical change: Wording added for clarification; contract must
indicate application of measurable specifications, but actual
specifications might not be contained in the contract.
ORG 3.5.1 Guidance • Technical changes: Wording added/revised to provide expanded
information regarding where the actual measurable specifications
might reside.
• Technical change: Note added to define makeup of contract (may
consist of more than one document).
ORG 3.5.2 • Editorial change: Punctuation corrected (comma deleted)
• Technical change: Note added to specify that IOSA/ISAGO registration
as a monitoring method must be used in conjunction with a risk
assessment of the provider.
ORG 3.5.2 Guidance • Technical change: Wording revised to address use of IOSA/ISAGO
registration as a method of monitoring a provider.
• Editorial change: Wording added; relocated with minor editorial
revisions from guidance under ORG 3.5.3 (more appropriate location).
ORG 3.5.3 Guidance • Editorial change: Wording deleted; relocated with minor editorial
revisions to guidance under ORG 3.5.2 (more appropriate location).
ORG 3.5.4 Guidance • Technical change: Wording added; recommendation that wet lease
agreements greater than three months are with an IOSA operator.
ORG 3.5.5 and Guidance • Administrative change: Standard and guidance suspended in
accordance with IOSA Standards Special Review Process.
Section 2 (FLT)
Area Changed Description of Change(s)
General (changes that are • Technical changes: Wording added to guidance to explain terms non-
applied multiple times) normal, abnormal, emergency.
• Editorial changes: Terminology standardized; flight deck entry door
and cabin entry door revised to flight deck door and cabin door.
Standards Eliminated • Twenty-nine (29): FLT 4.3.2, FLT 4.3.3, FLT 4.3.6, FLT 4.3.7,
FLT 4.3.8, FLT 4.3.9, FLT 4.3.10, FLT 4.3.13, FLT 4.3.14,
FLT 4.3.17B, FLT 4.3.18, FLT 4.3.19, FLT 4.3.20A, FLT 4.3.22,
FLT 4.3.23, FLT 4.3.24, FLT 4.3.29, FLT 4.3.31, FLT 4.3.32 <AC>,
FLT 4.3.33, FLT 4.3.34 <AC>, FLT 4.3.35 <AC>, FLT 4.3.36 <AC>,
FLT 4.4.1, FLT 4.4.2, FLT 4.4.3, FLT 4.4.4, FLT 4.5.1, FLT 4.5.2
(all incorporated into Table 2.9)
Standards Suspended • Two (2): Table 9.1, Items xxi (g), Item xxxiv
Standards Added • One (1): FLT 4.3.37 (includes associated tables)
Recommended Practices • Four (4): FLT 4.3.17A, FLT 4.3.20B, FLT 4.3.28, FLT 4.5.3 (all
Eliminated incorporated into Table 2.12)
Recommended Practices • One (1): FLT 4.3.38 (includes associated tables)
Added
Applicability Box • No changes.
Subsection 1.1 • Editorial change: Wording in title revised; consistent with ORG;
improves description of ISARPs in subsection.
FLT 1.2.1 • Technical change: Wording in sub-spec vii) I revised for consistency
with ICAO dangerous goods terminology.
FLT 1.6.1 • Editorial change: Reference changed to Table 1.1.
FLT 1.6.3 Guidance • Editorial change: Wording deleted to harmonize with guidance under
DSP 1.6.3.
FLT 1.10.1 • Technical changes: Wording added (sub-spec v) for consistency with
ORG 3.4.1.
FLT 1.10.3 Guidance • Editorial change: Wording revised to correct grammar.
FLT 1.11.1 • Technical change: Wording added for consistency with change in
ORG 3.5.1.
FLT 1.11.4B • Editorial change: Invalid reference deleted.
FLT 1.12.1 • Editorial change: Wording revised for consistency with ORG 3.1.1.
FLT 1.12.2 Guidance • Editorial change: Wording revised to be more appropriate (potentially).
• Technical changes: Wording added; list of examples of potential
hazards subject to risk assessment expanded.
FLT 2.1.12 Guidance • Technical change: Wording added to explain terminology.
FLT 2.1.35 • Technical changes: Wording revised; sub-spec ii) observation activities
expanded.
FLT 2.1.36 • Editorial change: Wording revised to standardize terminology.
FLT 2.2.17 • Technical change: Wording revised to reflect current terminology.
FLT 2.2.26 Guidance • Technical change: Wording added to explain terminology.
FLT 2.2.31 Guidance • Technical changes: Wording revised description of LOS scenarios
expanded.
• Technical change: Wording added to explain terminology.
FLT 2.2.44 Guidance • Technical change: Wording added to explain terminology.
FLT 2.3.2 Guidance • Technical change: Wording added to explain terminology.
FLT 2.5.1 Guidance • Technical change: Reference to ORG 3.5.5 deleted; no longer
accurate.
FLT 3.3.7 Guidance • Technical change: Wording added to explain terminology.
FLT 3.4.2 • Editorial change: Word added to improve accuracy.
FLT 3.4.3A Guidance • Technical change: Wording revised; title of reference document
updated.
FLT 3.4.3B • Editorial change: Wording revised for accuracy, harmonize with CAB.
FLT 3.4.3B Guidance • Technical change: Wording revised; title of reference document
updated.
FLT 3.4.3C • Editorial change: Wording revised for consistency.
FLT 3.4.3C Guidance • Technical change: Wording revised; title of reference document
updated.
FLT 3.5.3 Guidance • Technical change: Wording added to explain terminology.
FLT 3.7.5 • Technical changes: Wording added to improve expression of intent.
• Editorial change: GM symbol added.
FLT 3.7.5 Guidance • New guidance: IRM reference added.
FLT 3.7.9 • Technical change: Active Implementation expiry revised to 31 August
2018 to coincide with the expiry of ISM 11.
FLT 3.8.7B • Editorial change: Wording revised to clarify intent.
FLT 3.8.7B Guidance • Editorial change: Wording deleted as unnecessary.
FLT 3.8.10 • Technical changes: Invalid references deleted.
FLT 3.8.10 Guidance • Technical change: Reference to CAB provisions deleted; no longer
accurate.
FLT 3.9.3 Guidance • Editorial change: Wording deleted as unnecessary.
FLT 3.9.8 Guidance • Technical changes: Wording added to address information related to
dangerous goods acceptance by flight crew.
• Editorial change: Wording revised for clarity
FLT 3.11.18 Guidance • Technical change: Wording added to explain terminology.
FLT 3.11.20 • Technical change: Wording added to explain terminology.
FLT 3.12.2 • Editorial change: Wording revised to correct typo.
FLT 3.13.3 Guidance • Technical change: Wording added to explain terminology.
FLT 3.13.4 Guidance • Technical change: Wording added to explain terminology.
FLT 3.13.5 Guidance • Technical change: Wording added to explain terminology.
FLT 3.13.6 Guidance • Technical change: Wording added to explain terminology.
FLT 3.13.9 <AC> • Editorial change: Wording rearranged to clarify intent.
FLT 3.13.10 <AC> Guidance • Editorial change: Wording revised for applicability.
FLT 3.13.16 • Editorial change: Invalid references deleted.
FLT 3.13.17 • Editorial changes: References revised.
FLT 3.13.17 Guidance • Editorial changes: References revised.
FLT 3.13.18 • Technical changes: Wording revised, standard restructured to define
and clarify intent; References revised.
FLT 3.13.19 • Editorial change: Invalid references deleted.
FLT 3.14.3 Guidance • Technical change: Wording added to explain terminology.
FLT 3.14.11 • Editorial change: GM symbol added.
FLT 3.14.11 Guidance • New guidance to explain terminology.
FLT 3.14.16 • Technical change: Active Implementation expiry revised to 31 August
2018 to coincide with the expiry of ISM 11.
FLT 3.14.17 • Technical change: Active Implementation expiry revised to 31 August
2018 to coincide with the expiry of ISM 11.
FLT 4.2.2 • Editorial change: Wording in sub-spec vii) deleted as unnecessary.
FLT 4.2.3 • Technical change: Note added to clarify the meaning of en route
emergency airports.
Group placeholder • New placeholder (Intentionally open); reflects elimination of
FLT 4.3.2–4.3.3
Standards Added • Six (6): DSP 3.5.1, DSP 3.5.3, DSP 3.5.4, DSP 4.6.4, DSP 4.6.5,
DSP 4.6.6
Recommended Practices • None.
Eliminated
Recommended Practices • Two (2): DSP 3.5.2, DSP 4.1.3
Added
Applicability Box • Technical changes: Wording added to describe the application of
performance-based methods of conformance in the DSP section.
• Editorial change: Wording revised to eliminate repetition.
Subsection 1.1 • Editorial change: Wording in title revised; consistent with ORG;
improves description of ISARPs in subsection.
DSP 1.3.6 • Technical change: Wording added (new sub-spec vi) to address
changes in Amendment 40 to Annex 6.
• Editorial change: Note added to explain effective date
DSP 1.3.6 Guidance • Editorial change: IRM reference added.
• Technical change: Wording added to explain effective date contained
in sub-spec vi).
DSP 1.6.1 • Editorial change: Reference changed to Table 1.1.
DSP 1.7.4 Guidance • Editorial change: Wording simplified
DSP 1.8.4 Guidance • Editorial change: IRM reference added (repeated to complement new
guidance wording that addresses aircraft tracking).
• Technical change: Wording added to address changes in
Amendment 40 to Annex 6 (retention of aircraft tracking data).
DSP 1.10.1 • Technical changes: Wording added (sub-spec v) for consistency with
ORG 3.4.1.
DSP 1.11.1 • Technical change: Wording added for consistency with change in
ORG 3.5.1.
DSP 1.11.1 Guidance • Technical change: Wording added (in examples) to include aircraft
tracking.
• Editorial change: Reference to ORG 3.5.1 relocated for consistency.
DSP 1.11.3 Guidance • Technical change: Wording added (in examples) to include aircraft
tracking/products.
DSP 1.12.1 • Editorial change: Wording revised for consistency with ORG 3.1.1.
DSP 1.12.1 Guidance • Technical change: Wording added to address performance-based
methods of conformance.
DSP 1.12.2 Guidance • Editorial change: Wording revised to be more appropriate (potentially).
• Technical changes: Wording added; list of examples of potential
hazards subject to risk assessment expanded.
• Technical change: Wording added to address performance-based
methods of conformance.
• Editorial change: Wording relocated for consistency.
DSP 1.12.3 Guidance • Technical change: Wording added to address performance-based
methods of conformance.
DSP 1.12.5 Guidance • Technical change: Wording added to address performance-based
methods of conformance.
DSP 2.5.1 Guidance • Technical change: Reference to ORG 3.5.5 deleted; no longer
accurate.
DSP 3.2.9C • Editorial change: Wording deleted to correct grammar.
Sub-section 3.5 • New sub-section: Title is Aircraft Tracking.
DSP 3.5.1 and Guidance • New standard and guidance: Addresses aircraft tracking in accordance
with Annex 6, Amendment 40A.
DSP 3.5.2 and Guidance • New recommended practice and guidance: Addresses aircraft tracking
in accordance with Annex 6, Amendment 40A.
DSP 3.5.3 and Guidance • New standard and guidance: Addresses aircraft tracking in accordance
with Annex 6, Amendment 40A.
DSP 3.5.4 and Guidance • New standard and guidance: Addresses aircraft tracking in accordance
with Annex 6, Amendment 40A.
DSP 3.7.1 Guidance • Editorial changes: Abbreviation added; ISM references revised for
accuracy.
DSP 4.1.1 • Technical change: Note added to address performance-based
methods of conformance as specified in sub-section 4.6.
DSP 4.1.2 • Technical changes: Sub-spec iv) deleted; note added to address
performance-based methods of conformance as specified in sub-
section 4.6.
DSP 4.1.2 Guidance • Technical changes: Wording deleted as unnecessary, inaccurate.
DSP 4.1.3 and Guidance • New recommended practice and guidance (replaces placeholder) to
address operations with aircraft that have cargo fire suppression time
limits; in accordance with Annex 6, Amendment 40A.
DSP 4.1.4 • Editorial change: PCO symbol deleted from sub-spec iii).
• Technical change: Sub-spec iii) deleted.
• Technical change: Note describing PCO deleted.
• Technical change: Wording revised in note describing performance-
based method of conformance.
DSP 4.1.4 Guidance • Technical changes: Wording related to PCO deleted.
• Technical changes: Wording revised for accuracy.
• Technical change: Wording deleted; no longer accurate.
DSP 4.1.5 • Editorial change: PCO symbols deleted from sub-specs iii) and iv).
• Technical change: Note describing PCOs deleted.
• Technical change: Wording revised in note describing performance-
based method of conformance.
DSP 4.1.5 Guidance • Editorial changes: Wording revised for consistency.
• Technical changes: Wording revised for accuracy.
DSP 4.1.7 • Technical change: AI expiration date extended.
DSP 4.1.7 Guidance • Technical change: Wording revised for accuracy.
DSP 4.3.1 Guidance • Technical change: Wording added/deleted to ensure accuracy.
DSP 4.3.5 • Technical change: Wording revised for accuracy.
• Technical change: Note added to address performance-based
methods of conformance as specified in sub-section 4.6.
DSP 4.3.5 Guidance • Technical changes: Wording revised and deleted for accuracy.
DSP 4.3.6 • Technical change: Wording revised for accuracy, to improve statement
of intent.
• Technical change: Note added to address performance-based
methods of conformance as specified in sub-section 4.6.
DSP 4.3.6 Guidance • Technical changes: Wording revised for accuracy.
DSP 4.3.7 • Technical change: Wording revised in note describing performance-
based method of conformance.
Table 3.4 • Wording added: New sub-spec xix) to addresses aircraft tracking for
search and rescue.
Table 3.5 • Editorial changes: Formatting change for better readibility
Section 4 (MNT)
Area Changed Description of Change(s)
General (changes that are • Editorial changes: Terminology standardized; flight deck entry door
applied multiple times) and cabin entry door revised to flight deck door and cabin door.
Standards Eliminated • None.
Standards Added • None.
Recommended Practices • None.
Eliminated
Recommended Practices • None.
Added
Applicability Box • No changes.
Subsection 1.1 • Editorial change: Wording in title revised; consistent with ORG;
improves description of ISARPs in subsection.
MNT 1.1.3 Guidance • Editorial change: Word revised for accuracy.
MNT 1.3.1 • Technical change: Wording revised to improve accuracy.
MNT 1.3.1 Guidance • Technical changes: Wording revised/added/deleted to improve
accuracy, improve description of intent.
MNT 1.3.3 • Technical changes: Wording/structure revised to more accurately state
intent.
MNT 1.5.1 Guidance • Editorial change: Wording revised for ISM standardization; reference to
ORG 1.4.1 expanded.
MNT 1.6.1 • Editorial change: Reference changed to Table 1.1.
MNT 1.8.1 • Technical changes: Wording revised in sub-specs to more accurately
state intent.
MNT 1.10.1 • Technical change: Wording added (sub-spec v) for consistency with
ORG 3.4.1.
MNT 1.11.2 • Technical change: Wording added to expand intent.
MNT 1.11.2 Guidance • Editorial change: IRM reference added.
• Editorial change: Word revised to improve description of intent.
• Technical change: Wording added to improve description of intent
(examples).
MNT 1.12.1 • Editorial change: Wording revised for consistency with ORG 3.1.1.
MNT 1.12.6 Guidance • Technical change: Reference to ORG 3.5.5 deleted; no longer
accurate.
MNT 2.5.1 • Editorial change: Wording added to improve intent.
MNT 2.5.2 • Technical change: Wording revised to improve accuracy.
• Editorial change: GM symbol added.
MNT 2.5.2 Guidance • New guidance.
MNT 2.9.1 • Editorial changes: Wording revised to improve accuracy and
consistency.
MNT 3.1.2 Guidance • Editorial change: Wording deleted (examples) for accuracy.
MNT 3.2.2 • Technical change: Wording revised to more accurately state intent
(sub-spec iii).
MNT 4.5.1 • Editorial change: Wording revised to improve accuracy.
MNT 4.5.1 Guidance • Technical change: Wording added to explain intent (exception).
GRH 1.10.1 Guidance • Editorial changes: Wording revised to improve verbiage; reference to
ORG 3.5.1 relocated for consistency.
GRH 1.11.1 • Editorial change: Wording revised for consistency with ORG 3.1.1.
GRH 1.11.3 Guidance • Technical change: IGOM reference revised to improve accuracy.
GRH 2.1.2 Guidance • Technical change: Reference to Table 6.1 added.
• Editorial change: Wording deleted (non-relevant).
GRH 2.1.3 • Editorial change: Format correction; bullet symbols converted to lower
Roman numerals in accordance with ISM convention.
• Editorial change: GM symbol added.
GRH 2.1.3 Guidance • New guidance: Provides explanation of intent.
GRH 2.2.3 • Technical changes: Specifications deleted/revised; sub-specs added
to identify operational areas that are included in initial and recurrent
training for ground handling personnel.
• Editorial change: GM symbol deleted.
GRH 2.2.3 Guidance • Eliminated.
GRH 2.2.4 • Technical change: Standard eliminated; replaced by recommended
practice.
• Technical changes: Specifications deleted/revised; sub-specs added
to provide references to tables that address training for specific ground
handling operational functions.
• Editorial change: GM symbol added.
GRH 2.2.4 Guidance • New guidance.
GRH 2.2.5 and Guidance • Eliminated: Specifications incorporated into GRH 2.2.3.
GRH 2.3.1 Guidance • Technical change: Reference to ORG 3.5.5 deleted; no longer
accurate.
GRH 3.1.1 • Technical changes: Wording revised to expand intent; specifications
now address a comprehensive dangerous goods notification system.
GRH 3.1.1 Guidance • Technical changes: Wording added/revised to expand explanatory
information.
GRH 3.1.2 Note • Editorial change: Wording in note revised to improve clarity.
GRH 3.1.2 Guidance • Technical changes: DGR reference revised, IGOM reference added.
GRH 3.1.3 and Guidance • Eliminated. Marked as placeholder (intentionally open); redundant;
addressed in revised GRH 3.1.1.
GRH 3.1.4 and Guidance • Eliminated. Marked as placeholder (intentionally open); redundant;
addressed in revised GRH 3.1.1.
GRH 3.1.5 • Technical change: Wording in sub-spec i) revised for consistency with
current industry terminology.
GRH 3.1.5 Guidance • Technical change: IGOM reference added.
GRH 3.2.2 Guidance • Technical changes: AHM and IGOM references revised.
GRH 3.2.3 Guidance • Technical changes: AHM reference revised.
GRH 3.2.4 Guidance • Technical changes: AHM and IGOM references revised.
GRH 3.2.5 Guidance • Technical changes: IGOM reference revised.
GRH 3.2.6 • Editorial change: Wording in note revised to correct typo.
GRH 3.3.1 Guidance • Technical change: Wording revised to improve intent.
• Technical change: AHM reference revised.
GRH 3.3.2 • Technical changes: Wording revised to improve accuracy.
GRH 3.3.2 Guidance • Technical changes: Wording revised to provide expanded description
of load control system.
• Technical change: AHM reference revised.
GRH 3.3.3 Guidance • Technical changes: AHM and IGOM references revised.
GRH 3.3.6 Guidance • Technical changes: IGOM references revised.
GRH 3.3.7 Guidance • Technical changes: IGOM references revised.
GRH 3.3.8 Guidance • Technical change: DSP reference deleted (inaccurate)
GRH 3.4.1 Guidance • Technical changes: IGOM and AHM references revised.
GRH 3.4.3 Guidance • Technical change: IGOM reference added.
GRH 3.4.4 Guidance • Technical change: one DGR reference deleted.
GRH 3.4.6 Note • Editorial change: Wording in note revised to improve clarity.
GRH 3.4.6 Guidance • Technical change: IGOM reference deleted.
GRH 3.4.10 Guidance • Technical change: DGR reference revised.
GRH 3.4.11 Guidance • Technical change: DGR reference revised.
GRH 3.4.12 • Technical change: Wording revised/added to address the transport of
passenger items in cabin passenger seats; harmonized with
CAB 3.2.3.
GRH 3.4.12 Guidance • Technical changes: Wording revised/added to expand explanation of
intent.
GRH 3.5.1 Guidance • Technical changes: IGOM and AHM references revised.
GRH 3.5.2 Guidance • Technical changes: IGOM and AHM references revised.
GRH 3.5.3 • Technical changes: Wording revised/added to expand and clarify
intent.
• Editorial change: GM symbol deleted.
GRH 3.5.3 Guidance • Eliminated.
GRH 3.6.1 Guidance • Technical change: IGOM reference revised.
GRH 3.6.2 Guidance • Technical change: IGOM reference revised.
GRH 3.6.3 Guidance • Technical change: IGOM reference revised.
GRH 3.6.4 Guidance • Technical change: AHM reference revised.
GRH 3.6.5 Note • Editorial change: Wording in note revised to improve clarity.
GRH 4.1.1 • Editorial change: Wording revised for accuracy.
GRH 4.1.1 Guidance • Technical changes: Wording added to address biofuels and
documentation of procedures.
GRH 4.1.3 Guidance • Technical change: IGOM reference revised.
GRH 4.1.4 Guidance • Technical change: IGOM reference revised.
GRH 4.1.5 Guidance • Technical change: IGOM reference revised.
GRH 4.1.7 Guidance • Technical change: AHM reference revised.
GRH 4.2.1 Guidance • Technical change: SAE reference document replaces AEA document;
consistent with standard that will be used in IFQP starting January
2017.
GRH 4.2.2 Guidance • Technical change: SAE reference document added; consistent with
standard that will be used in IFQP starting January 2017.
GRH 4.2.4 • Technical change: SAE reference added to sub-spec ii); consistent
with standard that will be used in IFQP starting January 2017.
Table 6.1 • New table: Supplements guidance associated with GRH 2.1.2;
addresses safety training for ground handling personnel; specifies
functional groups/typical training curricula.
Table 6.2 • New table: Supplements GRH 2.2.3 (recommended practice); provides
specifications that define a typical curriculum for airside driver training.
Table 6.3 • New table: Supplements GRH 2.2.3 (recommended practice); provides
specifications that define a typical curriculum for load control functional
training.
Table 6.4 • New table: Supplements GRH 2.2.3 (recommended practice); provides
specifications that define a typical curriculum for passenger handling
functional training.
Table 6.5 • New table: Supplements GRH 2.2.3 (recommended practice); provides
specifications that define a typical curriculum for baggage handling
functional training.
Table 6.6 • New table: Supplements GRH 2.2.3 (recommended practice); provides
specifications that define a typical curriculum for aircraft handling and
loading functional training.
Table 6.7 • New table: Supplements GRH 2.2.3 (recommended practice); provides
specifications that define a typical curriculum for passenger boarding
bridge training.
Table 6.8 • New table: Supplements GRH 2.2.3 (recommended practice); provides
specifications that define a typical curriculum for aircraft loading
supervisor training.
Table 6.9 • New table: Supplements GRH 2.2.3 (recommended practice); provides
specifications that define a typical curriculum for aircraft ground
movement functional training.
Table 6.10 • New table: Supplements GRH 2.2.3 (recommended practice); provides
specifications that define a typical curriculum for fueling operations
functional training.
Table 6.11 • New table: Supplements GRH 2.2.3 (recommended practice); provides
specifications that define operational functions/typical curricula for
de/anti-icing functional training.
Section 7 (CGO)
Area Changed Description of Change(s)
General (changes that are • None.
applied multiple times)
Standards Eliminated • None.
Standards Added • None.
Recommended Practices • None.
Eliminated
Recommended Practices • One (1): CGO 3.4.2.
Added
Applicability Box • No changes.
Subsection 1.1 • Editorial change: Wording in title revised; consistent with ORG;
improves description of ISARPs in subsection.
CGO 1.3.1 Guidance • Editorial changes: Wording revised/deleted for ISM standardization;
reference to ORG 1.4.1 expanded.
CGO 1.5.1 • Editorial change: Reference changed to Table 1.1.
CGO 1.9.1 • Technical changes: Wording added (sub-spec v) for consistency with
ORG 3.4.1.
CGO 1.10.1 • Technical changes: Wording added for consistency with ORG 3.5.1.
CGO 1.10.1 Guidance • Editorial change: Reference to ORG 3.5.1 added.
CGO 1.11.1 • Editorial change: Wording revised for consistency with ORG 3.1.1.
CGO 1.11.2 Guidance • Technical changes: list of typical sources of cargo operations hazards
added (similar to lists under FLT 1.12.2 and DSP 1.12.2).
CGO 2.1.4 • Editorial change: Error in provision identifier corrected; reference to
CGO 2.1.1.
CGO 2.2.3 • Editorial change: Wording added; reference to ULDs termed where
applicable.
CGO 2.3.1 Guidance • Technical change: Reference to ORG 3.5.5 deleted; no longer
accurate.
CGO 3.1.4 • Technical changes: Wording revised for accuracy of intent.
CGO 3.2.1 • Editorial changes: Provision restructured to include sub-specs;
wording revised to include DGR abbreviation.
• Technical changes: Wording added (sub-spec ii) to reflect DGR
acceptance checklist identification requirement.
CGO 3.2.3 • Editorial changes: Wording revised to improve statement of intent.
CGO 3.2.3 Guidance • Technical change: Wording deleted as unnecessary.
CGO 3.2.6 Guidance • Editorial change. Wording revised to improve flow.
CGO 3.4.2 and Guidance • New recommended practice and guidance: Addresses
acceptance/handling of time/temperature-sensitive healthcare
products (new separate cargo category; previously included under
perishable cargo).
Section 8 (SEC)
Area Changed Description of Change(s)
General (changes that are • None.
applied multiple times)
Standards Eliminated • None.
Standards Added • Two (2): SEC 1.9.2 (repeat of ORG 1.5.2; not repeated previously in
SEC), SEC 1.12.1 (repeat of ORG 3.1.3; upgraded from recommended
practice to standard in SEC for consistency with ORG 3.1.3).
Recommended Practices • One (1): SEC 1.12.1 (repeat of ORG 3.1.3; upgraded to standard for
Eliminated consistency with ORG 3.1.3).
Recommended Practices • None.
Added
Applicability Box • No changes.
Subsection 1.1 • Editorial change: Wording in title revised; consistent with ORG;
improves description of ISARPs in subsection.
SEC 1.1.1 Guidance • Technical change: Wording added to clarify intent.
SEC 1.1.2 • Technical changes: Wording added to expand statement of intent.
SEC 1.2.1 Guidance • Editorial change: Wording added to provide alternative names for an
AOSP.
SEC 1.3.1 • Technical changes: Wording added to expand intent and for more
consistency with ORG 1.3.1.
SEC 1.3.2 • Technical changes: Wording revised for more consistency with
ORG 1.3.2.
SEC 1.3.3 • Technical changes: Wording revised for more consistency.
SEC 1.4.1 • Technical changes: Wording revised for more consistency with
ORG 1.4.1.
SEC 1.4.1 Guidance • Technical changes: Wording added to expand relevant information and
explanation of intent.
SEC 1.6.1 • Editorial change: Reference changed to Table 1.1.
SEC 1.8.1 • Technical changes: Wording added to expand intent and for more
consistency with ORG 2.2.1.
SEC 1.8.1 Guidance • Editorial change: Word revised to improve flow and correct spelling.
• Editorial change: Wording deleted; relocated into the standard.
SEC 1.9.1 • Editorial change: Abbreviation SeMS replaces existing wording.
SEC 1.9.2 and Guidance • New standard and guidance: Addresses continual improvement of
SeMS; repeat of ORG 1.5.2 (SMS) adapted for application to SeMS.
SEC 1.10.1 • Technical changes: Wording added to expand intent and for more
consistency with ORG 3.4.1.
SEC 1.10.4 • Editorial change: Wording revised to improve statement of intent.
SEC 1.11.1 • Technical changes: Wording added to expand intent and for more
consistency with ORG 3.5.1.
SEC 1.11.1 Guidance • Editorial changes: Wording revised to improvement statement of intent.
SEC 1.12.1 • New standard: Upgraded from recommended practice; consistent with
ORG 3.1.3, which is repeated as a standard in all other ISM sections;
wording/structure tailored for applicability to reporting security issues.
SEC 2.1.1 • Editorial change: Word revised to correct spelling.
SEC 2.1.2 • Editorial changes: Wording revised/added to expand training program
specifications.
• Editorial change: Structure revised to include sub-specifications.
Appendix
Area Changed Description of Change(s)
Appendix • Mandatory Observation Checklists MO-1 to MO-16 added
2 Structure
The ISM is organized as follows:
• Section 1 → Organization and Management System (ORG);
• Section 2 → Flight Operations (FLT);
• Section 3 → Operational Control and Flight Dispatch (DSP);
• Section 4 → Aircraft Engineering and Maintenance (MNT);
• Section 5 → Cabin Operations (CAB);
• Section 6 → Ground Handling Operations (GRH);
• Section 7 → Cargo Operations (CGO);
• Section 8 → Security Management (SEC).
Each section in this Manual is assigned an associated 3-letter identifier (in parentheses above). The
reference number for every standard or recommended practice within a section includes the specific
3-letter identifier for that section (e.g. ORG 1.1.1).
4 Applicability of ISARPs
Applicability Guidance
To provide guidance to operators, an Applicability box is found at the beginning of each section of
this manual. Within the box is a general description of the applicability of the ISARPs contained in the
section.
The applicability of individual standards or recommended practices is always determined by the
auditor. As a means to assist with the interpretation of individual application, many ISARPs begin
with a conditional phrase as described below.
Systemic Applicability
When making a determination as to the applicability of individual ISARPs, it is important to take into
account operations (relevant to the individual standard or recommended practice) that are conducted
within stations and locations throughout the operator's network.
Aircraft Applicability
The ISARPs as published in this version of the ISM are applicable only for the audit of an operator
that operates a minimum of one (i.e. one or more) multi-engine, two-pilot aircraft with a maximum
certificated takeoff mass in excess of 5,700 kg (12,566 lb) to conduct:
• Passenger flights with or without cabin crew.
• Cargo flights with or without the carriage of passengers or supernumeraries.
ISARPs may not be applied or used for the Audit of an operator that either:
• Does not operate a minimum of one aircraft as specified above, or
• Has all aircraft operations conducted by another operator.
ISARPs may not be applied or used for the Audit of operations that are conducted with:
• Aircraft that have a maximum certificated takeoff mass of 5,700 kg (12,566 lb) or less;
• Single engine aircraft;
• Piston engine aircraft;
• Single pilot aircraft;
• Helicopters;
• Seaplanes.
During an audit, ISARPs are applied only to those aircraft that are of the type authorized in the Air
Operator Certificate (AOC) and utilized in commercial passenger and/or cargo operations. Certain
ISARPs are also applicable to non-commercial operations, and such application is indicated in a note
that is part of the standard or recommended practice.
Other owned or leased aircraft that are not of the type authorized in the AOC and/or not utilized in
commercial air transport operations will not be evaluated during an audit. However, the existence of
such aircraft will be referenced with an explanation in the IOSA Audit Report (IAR).
Systems and Equipment Applicability
Aircraft that meet the above-specified aircraft applicability criteria are assessed for conformity with
the applicable aircraft and cabin systems and equipment specifications contained in ISM Section 2
(FLT), Tables 2.9 and 2.12, and in ISM Section 5 (CAB), Tables 5.4 and 5.7.
5 Explanation of ISARPs
ISARPs contained in this manual have been developed for use under the IOSA program and contain
the operational criteria upon which the audits are based. ISARPs are not regulations.
ISARPs Identifiers
All ISM provisions (i.e. the ISARPs) are preceded by an identifier that consists of the three-letter
section abbreviation and a string of three numbers separated by two decimal points (e.g. ORG 1.1.1).
Stabilization of the ISARPs identifiers is an important goal, primarily for facilitating use of the ISARPs
by operators, auditors and others, but also for the purpose of ensuring an accurate statistical basis.
Therefore, when revising the ISM, every effort is made to minimize any re-numbering of the ISARPs.
In certain instances new provisions must be inserted into an existing series of ISARPs. Normally this
is done when it is important that the new provision has a logical locational relationship with another
existing provision. When this occurs, an additional upper-case letter is attached to the identifier of the
applicable provisions as the means of avoiding the re-numbering of other ISARPs that follow in the
series.
For example, when a new FLT provision was developed to address AQP/ATQP, its logical location
was immediately following the existing FLT 2.1.1, which contains the core flight crew training
program specifications. The new provision was inserted immediately under FLT 2.1.1, and the two
provisions became FLT 2.1.1A and FLT 2.1.1B. The addition of upper-case letters to the identifiers of
those two provisions precluded the need to renumber all of the other ISARPs that follow in that
series.
Standards
IOSA Standards are specified systems, policies, programs, processes, procedures, plans, sets of
measures, facilities, components, types of equipment or any other aspect of operations under the
scope of IOSA that have been determined to be an operational necessity, and with which an operator
will be expected to be in conformity at the conclusion of an audit.
Standards always contain the word “shall” (e.g. “The Operator shall have a process…”) in order to
denote that conformance by an operator being audited is a requirement for IOSA registration.
A [PCO] symbol in bold text following a sub-specification within or the last sentence of an IOSA
provision identifies a parallel conformity option (PCO).
A (GM) symbol in bold text following the last sentence of an IOSA provision indicates the existence of
associated guidance material. (Guidance Material is addressed in subsection 6 below.)
A ► symbol at the end of an individual standard or recommended practice in Section 1 (ORG)
indicates the specific provision is repeated almost verbatim in one or more of the other seven
sections of the ISM.
A ◄ symbol at the end of a provision in Sections 2–8 indicates the specific provision is also
contained in Section 1 (ORG) and has been repeated almost verbatim.
A ▲ symbol is the identifier for a paragraph that immediately follows a provision and designates the
provision as eligible for the application of Active Implementation. (Active Implementation is
addressed in subsection 7 below.)
Special Review Suspension
IATA, upon request from an appropriate industry source, may subject the technical specifications
within an IOSA standard to a special review in accordance with the IOSA Standards Special Review
Process. Such process is defined in Section 1 of the IOSA Program Manual (IPM).
When a special review is conducted, the IOSA standard or certain sub-specifications within the IOSA
standard are put under suspension until the special review has been completed.
When a new edition of the ISM is published while a special review is in progress, the suspended
IOSA standard or sub-specification(s) within the IOSA standard will be identified with either of the
following, as appropriate:
• (This standard is currently suspended in accordance with the IOSA Standards Special
Review Process), or
• (This sub-specification is currently suspended in accordance with the IOSA Standards
Special Review Process)
6 Guidance Material
Guidance material is informational in nature and supplements or clarifies the meaning or intent of
certain ISARPs. ISARPs that are self-explanatory do not have associated guidance material.
Guidance material is designed to ensure a common interpretation of specifications in ISARPs and
provide additional detail that assists an operator to understand what is required in order to achieve
conformity. Where applicable, guidance material also presents examples of acceptable alternative
means of achieving conformity.
Guidance material associated with an individual standard or recommended practice is co-located
with the relevant provision and is preceded by the bold sub-heading Guidance.
Additionally, some guidance material relates to an entire ISM section or to a specific grouping of
provisions within a section. Such guidance stands alone in an appropriate location and is preceded
by the bold heading General Guidance.
Audit specifications are contained only in the ISARPs, and never in the guidance material.
7 Operational Audit
During an audit, an operator is assessed against the ISARPs contained in this manual. To determine
conformity with any standard or recommended practice, an auditor will gather evidence to assess the
degree to which specifications are documented and implemented by the operator. In making such an
assessment, the following information is applicable.
Documented
Documented shall mean the specifications in the ISARPs are published and accurately represented
by an operator in a controlled document. A controlled document is subject to processes that provide
for positive control of content, revision, publication, distribution, availability and retention.
Documentation is necessary for an operator to ensure systems, programs, policies, processes,
procedures and plans are implemented in a standardized manner, and to further ensure such
Designation of any IOSA Standard for the application of AI will always be predicated on an up-front
risk analysis that indicates application of AI would not pose an unacceptable safety risk. Additionally,
such designation may include prerequisite conditions that must be satisfied by an operator in order to
be eligible for AI.
An IOSA Standard that has been designated for application of AI will be clearly identified in this
manual, along with prerequisite conditions, if any.
To conform to a standard based on AI, an operator must be able to provide evidence that execution
of an acceptable IAP is underway and material or physical progress toward completion of the plan is
consistent with the planned schedule, as measured against published milestones. If applicable, an
operator must also demonstrate satisfaction of any associated prerequisite conditions.
An operator that provides only an IAP without other demonstrable evidence of having materially or
physically begun execution of the plan does not meet the criteria for conformance based on AI.
10 English Language
English is the official language of the IOSA Program; documents comprising the IOSA
Documentation System are written in International English* in accordance with IATA policy.
The IPM requires auditors to ensure the English language version of this ISM and/or IOSA Checklists
is always used as the basis for a final determination of conformity or nonconformity with ISARPs
during the conduct of an audit. Versions of the ISM or IOSA Checklists that have been translated into
another language are subject to misinterpretation; therefore, any translated IOSA document is
considered an unofficial reference.
* Refer to the IRM for the definition of International English.
* The official reference for International English in accordance with IATA policy is the online Merriam-
Webster Dictionary (http://www.merriam-webster.com).
11 Manual Revisions
Revisions to the ISM are developed and issued in accordance with the IOSA Standards Change
Management process, which is published in the IOSA Program Manual (IPM).
The ISM is normally revised annually. In accordance with IATA policy, a revision to the ISM (other
than a temporary revision) will always result in a new edition of the ISM.
The time period between the issuance of a new edition of the ISM and the effective date of such new
edition is typically four full months.
Should critical issues arise that affect the content of the ISM, a temporary revision (TR) will be
issued.
Usable Edition
For an initial IOSA registration or IOSA registration renewal audit, the operator, in conjunction with
the audit organization (AO), normally determines the edition of the ISM that will be used for an audit.
The Operator has the option to select either:
• The edition that is effective on the day before the on-site phase of the Audit is scheduled to
begin, or
• An edition that has been published prior to the day the on-site phase of the Audit is
scheduled to begin, but has not yet become effective.
12 Modification Status
All changes in this document are listed in the revision highlights table. For easier orientation, the
following symbols identify any changes made within each section:
13 Conflicting Information
IOSA Documentation System
Manuals within the IOSA documentation system are not revised concurrently, thus creating the
potential for conflicting information in different IOSA manuals. In the case of such conflicting
information, the information contained in the manual with the most recent revision date shall be
considered valid.
IATA Dangerous Goods Regulations (DGR)
The DGR is a manual that is published annually and is effective on 1 January of each calendar year.
The ISM is published in April of each calendar year, which creates the potential for conflicting
DGR-ISM requirements. In the case of a DGR-ISM conflict, the requirement contained in the current
effective version of the DGR shall be considered valid.
16 Authority
The IOSA Program operates under the authority of the IATA Operations Committee (OPC) with
reference to the IATA Board of Governors (BoG).
Applicability
Section 1 addresses the organization and management system of an operator for the purpose of ensuring
the safety and security of aircraft operations.
Individual provisions or sub-specifications within a provision that:
• Begin with a conditional phrase (“If the Operator...”) are applicable if the operator meets the
condition(s) stated in the phrase.
• Do not begin with a conditional phrase are applicable to all operators unless determined otherwise
by the Auditor.
Many IOSA standards and recommended practices in this Section 1 (ORG ISARPs) are repeated in one or
more other sections of the ISM (as indicated by the ► symbol). Refer to the IOSA Audit Handbook for
information relevant to the proper internal auditing of repeated ORG ISARPs.
ORG 3.4.6, 3.4.7, 3.4.8 and 3.4.14 in this section are applicable only to an operator that is currently on the
IOSA Registry and is being audited for the purpose of registration renewal.
General Guidance
Definitions of technical terms used in this ISM Section 1, as well as the meaning of abbreviations and
acronyms, are found in the IATA Reference Manual for Audit Programs (IRM).
An effective management system is fully implemented and functional with a clear consistency and
unity of purpose between corporate management and management in the operational areas.
The management system ensures compliance with all applicable standards and regulatory
requirements. In addition to internal standards and regulations of the State, an operator may also be
required to comply with authorities that have jurisdiction over operations that are conducted over the
high seas or within a foreign country.
ORG 1.1.2 (Intentionally open)
ORG 1.1.3 The Operator shall identify one senior management official as the accountable
executive (AE) who is accountable for performance of the management system as specified in
ORG 1.1.1 and:
(i) Irrespective of other functions, is accountable on behalf of the Operator for the
implementation and maintenance of the safety management system (SMS) throughout the
organization;
(ii) Has the authority to ensure the allocation of resources necessary to manage safety and
security risks to aircraft operations;
(iii) Has overall accountability for ensuring operations are conducted in accordance with
conditions and restrictions of the Air Operator Certificate (AOC), and in compliance with
applicable regulations and standards of the Operator. [SMS] (GM)
Auditor Actions
□ Identified senior management official designated as the AE for the conduct of operations.
□ Examined management system structure and organizational lines of accountability.
□ Examined job description of designated AE (focus: accountability/responsibilities are as
specified in the standard).
□ Interviewed AE and/or designated management representative(s).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definitions of Accountability, Accountable Executive (AE), Authority, Aircraft
Operations, Responsibility, Safety Risk Management and Senior Management.
The requirement for an AE is an element of the Safety Policy and Objectives component of the SMS
framework.
The designation of an AE means the accountability for operational quality, safety and security
performance is placed at a level in the organization having the authority to take action to ensure the
management system is effective. Therefore, the AE is typically the chief executive officer (CEO),
although, depending on the type and structure of the organization, it could be a different senior
official (e.g. chairperson/member of the board of directors, company owner).
The AE has the authority, which includes financial control, to make policy decisions, provide
adequate resources, resolve operational quality, safety and security issues and, in general, ensure
necessary system components are in place and functioning properly.
In an SMS, the AE would typically have:
• Ultimate responsibility and accountability for the safety of the entire operation together with
the implementation and maintenance of the SMS;
• Responsibility for ensuring the SMS is properly implemented in all areas of the organization
and performing in accordance with specified requirements.
The AE also is responsible for ensuring the organization is in compliance with requirements of
applicable authorities (i.e. regulations), as well as its own policies and procedures, which may
exceed existing regulations or address areas that are not regulated (e.g. ground handling
operations). An operator's policies and procedures are typically published in its Operations
Manual (OM).
To ensure that the operator continues to meet applicable requirements, the AE might designate a
manager with the responsibility for monitoring compliance. The role of such manager would be to
ensure that the activities of the operator are monitored for compliance with the applicable regulatory
requirements, as well as any additional requirements as established by the operator, and that these
activities are being carried out properly under the supervision of the relevant head of functional area.
Expanded guidance may be found in the ICAO SMM, Document 9859.
ORG 1.1.4 If required by the State of the Operator (hereinafter, the State), the Operator shall have
post holders within the management system that are acceptable to the Authority and have the
accountability for ensuring, in their respective defined operational areas:
(i) The management of safety risks and security threats to aircraft operations;
(ii) Operations are conducted in accordance with conditions and restrictions of the Air Operator
Certificate (AOC), and in compliance with applicable regulations and standards of the
Operator. (GM) ►
Auditor Actions
□ Identified post holders accountable for the conduct of operations.
□ Examined management system structure and organizational lines of accountability.
□ Examined job descriptions of all post holders throughout the organization (focus:
accountability/responsibilities are as specified in the standard).
□ Interviewed AE and/or designated management representative(s).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Post Holder.
Managers in such positions might be referred to as post holders, directors or another title as specified
by each State.
ORG 1.1.5–1.1.9 (Intentionally open)
culture. Ideas for improvement may come from internal and external sources; therefore the
organization would be constantly monitoring all sources and willing to make changes as necessary to
keep the management system refreshed and strongly focused on improving operational quality,
safety and security performance.
Such policy typically commits the organization to:
• Regular review of performance-based indicators by senior management;
• Regular analysis of malfunctions or undesirable operational results;
• Follow-up of corrective actions and their effectiveness in improving operational performance.
The continual improvement policy is typically reviewed periodically to ensure continuing relevance to
the organization.
An SMS, as well as a Quality Management System (QMS) and Security Management System
(SeMS), are integrated components of an operator's overall management system and would typically
be subjected to protocols for continual improvement in accordance with the operator's policy.
A continual improvement policy is normally documented in operations manuals or other controlled
documents and, to enhance effectiveness, communicated and made visible throughout the
organization by disseminating communiqués, posters, banners and other forms of informational
media.
Consistent with the structure and complexity of the operator's organization, the continual
improvement policy may be issued as a stand-alone policy or combined with the safety policy
specified in ORG 1.2.1.
ORG 1.2.3 The Operator shall have a corporate safety reporting policy that encourages personnel
to report hazards to aircraft operations and, in addition, defines the Operator's policy regarding
disciplinary action, to include:
(i) Types of operational behaviors that are unacceptable;
(ii) Conditions under which disciplinary action would not apply. [SMS] (GM)
Auditor Actions
□ Identified/Assessed corporate safety reporting policy (focus: personnel urged to report
operational hazards; definition of disciplinary policy/potential disciplinary actions).
□ Interviewed AE and/or designated management representative(s).
□ Coordinated to verify implementation of safety reporting in all operational areas.
□ Other Actions (Specify)
Guidance
The requirement for an operator to have a safety reporting policy is an element of the Safety Policy
and Objectives component of the SMS framework.
Safety reporting is a key aspect of SMS hazard identification and risk management.
Such a policy is typically documented in operations manuals or other controlled documents.
Consistent with the structure and complexity of the operator's organization, the safety reporting policy
may be issued as a stand-alone policy or combined with the safety policy that is specified in
ORG 1.2.1.
A safety reporting policy encourages and perhaps even provides incentive for individuals to report
hazards and operational deficiencies to management. It also assures personnel that their candid
input is highly desired and vital to safe and secure operations.
The safety reporting policy is typically reviewed periodically to ensure continuing relevance to the
organization.
Refer to ORG 3.1.3, 3.1.4 and 3.1.5, each of which specifies types of safety reporting.
Management positions critical to operational safety or security may require enhanced job
descriptions or terms of reference that reflect specialized requirements inherent in certain key
positions. Such specialized requirements would include any delegation of authority exercised by
personnel on behalf of an authority (e.g. designated or authorized flight examiner).
Compliance with regulatory requirements, as well as internal policies and procedures, is an essential
element of a safe and secure operational environment. The responsibility for ensuring compliance
with both regulatory and internal requirements is specified and assigned within the management
system. Job descriptions, terms of reference and operating manuals are examples of appropriate
locations for documenting management system responsibilities.
Expanded guidance may be found in the ICAO SMM, Document 9859.
ORG 1.3.2 The Operator shall have a process for the delegation of duties within the management
system that ensures managerial continuity is maintained when operational managers, including post
holders, if applicable, are absent from the workplace. (GM) ►
Auditor Actions
□ Identified/Assessed processes for management system delegation of duties (focus: processes
maintain managerial continuity during periods when corporate/operational managers are absent).
□ Interviewed AE and/or designated management representative(s).
□ Coordinated to verify processes for management system delegation of duties in all operational
areas.
□ Examined example(s) of delegation of duties due to absence of managers.
□ Other Actions (Specify)
Guidance
The intent of this provision is for an operator to have a documented process that ensures a specific
person (or perhaps more than one person) is identified to assume the duties of any operational
manager that is or is expected to be away from normal duties. An operator may have nominated
deputies in place or a process for ensuring the appointment of a temporary replacement.
A notification of such delegation of duties may be communicated throughout the management
system using email or other suitable communication medium.
ORG 1.3.3 The Operator shall ensure a delegation of authority and assignment of responsibility
within the management system for liaison with regulatory authorities, original equipment
manufacturers and other operationally relevant external entities. (GM) ►
Auditor Actions
□ Identified corporate management individuals with authority for liaison with regulators/other
external entities.
□ Interviewed AE and/or designated management representative(s).
□ Interviewed selected manager(s) with authority for liaison with regulators/other external entities.
□ Coordinated to identify managers with authority for liaison with external entities in all operational
areas.
□ Other Actions (Specify)
Guidance
To ensure the communication and coordination with external entities is consistent and appropriate,
liaison with operationally relevant external entities is normally controlled through the delegation of
authority and assignment of responsibility to specifically named management personnel. Such
authorities and responsibilities would normally be included in the job descriptions of the applicable
managers.
ORG 1.3.4 (Intentionally open)
ORG 1.3.5 The Operator shall have a policy that informs operational personnel throughout the
organization of their responsibility to comply with the applicable laws, regulations and procedures in
all locations where operations are conducted.
Auditor Actions
□ Identified/Assessed corporate compliance policy (focus: requirement for organizational
compliance with applicable laws/regulations/procedures by operational personnel)
□ Interviewed AE and/or designated management representative(s).
□ Coordinated to verify implementation of compliance policy in all operational areas.
□ Other Actions (Specify)
1.4 Communication
ORG 1.4.1 The Operator shall have a communication system that enables an exchange of
information relevant to the conduct of operations throughout the management system and in all areas
where operations are conducted. (GM) ►
Auditor Actions
□ Identified/Assessed corporate communication system (focus: organizational capability for
communicating information relevant to operations to all personnel).
□ Interviewed AE and/or designated management representative(s).
□ Observed examples of information communication.
□ Interviewed selected management system personnel.
□ Coordinated to verify implementation of communication system in all operational areas.
□ Other Actions (Specify)
Guidance
An effective communication system ensures the exchange of operational information throughout all
areas of the organization, and includes senior managers, operational managers and front line
personnel. To be totally effective, the communication system would also include external
organizations that conduct outsourced operational functions.
Methods of communication will vary according to the size and scope of the organization. However, to
be effective, methods are as uncomplicated and easy to use as is possible, and facilitate the
reporting of operational deficiencies, hazards or concerns by operational personnel.
Specific methods of communication between management and operational personnel could include:
• Email, Internet;
• Safety or operational reporting system;
• Communiqués (e.g. letters, memos, bulletins);
• Publications (e.g. newsletters, magazines)
If email is used as an official medium for communication with operational personnel, the process is
typically formalized by the operator to ensure control and effectiveness.
ORG 1.4.2 The Operator shall have processes for the communication of safety information
throughout the organization to ensure personnel maintain an awareness of operational safety
management. [SMS] (GM)
Auditor Actions
□ Identified/Assessed corporate communication system (focus: organizational capability for
communicating safety information to personnel; information stresses SMS
awareness/operational safety issues).
□ Interviewed AE and/or designated management representative(s).
□ Interviewed selected management system personnel.
□ Observed examples of safety information communication.
Auditor Actions
□ Identified/Assessed standards/processes for maintaining competency of personnel in functions
relevant to safety/security of aircraft operations (focus: standards specify continuing
education/training, meeting technical requirements).
□ Interviewed AE and/or designated management representative(s).
□ Coordinated to verify application of competency standards.
□ Other Actions (Specify)
Guidance
Positions or functions within an airline organization considered “operationally critical” are those that
have the potential to affect operational safety or security. This definition includes management
positions and any positions or functions that may affect the airworthiness of aircraft.
Typically, training programs are implemented to ensure personnel throughout the organization are
qualified and competent to perform individual duties.
Some management positions within airline operations may require an individual to maintain a
technical competency as a requirement for being assigned to the position. For example, it may be
specified that certain management positions within Flight Operations may only be filled by individuals
who are qualified flight crew members. Similar situations could exist within Cabin Operations,
Engineering and Maintenance or other operational disciplines.
In such cases, the job description specifies the requirement for maintaining technical competency,
and adequate opportunity is provided to fulfill the requirement.
ORG 1.6.4 The Operator should have a policy that requires personnel who perform operational
functions critical to the safety of aircraft operations to be physically and medically fit for duty. (GM)
Auditor Actions
□ Identified/Assessed policy that requires personnel in operational functions critical to the safety
of aircraft operations to be physically/medically fit for duty (focus: methods used to determine
physical/medical fitness).
□ Interviewed AE or designated management representative(s).
□ Coordinated to verify policy is implemented in all operational areas.
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Operational Function (Aircraft Operations).
ORG 1.6.5 The Operator shall have a program that ensures personnel are trained and competent
to perform SMS duties. The scope of such training shall be appropriate to each individual's
involvement in the SMS. [SMS] (GM) ►
Note: Conformity with this ORG standard is possible only when the Operator is in conformity with all
repeats of this ORG standard in other ISM sections. Refer to the IAH for information that identifies
such repeats.
Auditor Actions
□ Identified/Assessed requirement for personnel to be trained/competent to perform SMS duties.
□ Interviewed SMS manager and/or designated management representative(s).
□ Examined selected training curricula requirement for personnel to be trained/competent to
perform SMS duties
□ Examined selected management/non-management personnel training records (focus:
completion of SMS training).
□ Coordinated to verify SMS training is implemented in all operational areas.
□ Other Actions (Specify)
Guidance
SMS training is an element of the Safety Promotion component of the SMS framework.
An SMS typically specifies initial and recurrent safety training standards for personnel that perform
operational functions for the operator, to include managers and supervisors, senior managers and
the AE.
The content of such training is appropriate to the individual's responsibilities and involvement in the
SMS, and typically includes or addresses some or all of the following subject areas, as appropriate
for the functions performed by the personnel being trained:
• Organizational safety policies, goals and objectives;
• Organizational safety roles and responsibilities related to safety;
• Basic safety risk management principles;
• Safety reporting systems;
• Safety management support (including evaluation and audit programs);
• Lines of communication for dissemination of safety information;
• A validation process that measures the effectiveness of training;
• Initial indoctrination and, when applicable, recurrent training requirements.
Defined safety objectives typically reflect the service provider's commitment to maintain or
continuously improve the overall effectiveness of its SMS. Such objectives also form the basis for the
setting of safety performance measures as specified in ORG 3.2.1.
Planning processes may be part of, or associated with, the budgetary process, which typically take
place prior to the start of a calendar or fiscal year, and involve decisions that result in a plan for
capital and operating expenditures to support operations.
Expanded guidance regarding the setting of safety objectives may be found in the ICAO SMM,
Document 9859.
To preclude the loss of records due to hardware or software failures, an electronic system is
programmed to create backup files on a schedule that ensures records are never lost. Typically, an
electronic system provides for file backup on a daily basis.
Where necessary, the look and feel of electronic records is similar to that of a paper record.
The retention period for records is defined by the operator and, if applicable, will always be in
accordance with requirements of the Authority.
Hardware and software, when updated or replaced, is retained to enable retrieval of old records.
3 Safety Management
To be effective, reactive and proactive processes are used to acquire information and data, which are
then analyzed to identify existing or predict future (i.e. potential) hazards to aircraft operations.
Examples of processes that typically yield information or data for hazard identification include:
• Confidential or other reporting by personnel;
• Investigation of accidents, incidents, irregularities and other non-normal events;
• Flight data analysis;
• Observation of flight crew performance in line operations and training;
• Quality assurance and/or safety auditing;
• Safety information gathering or exchange (external sources).
Processes would be designed to identify hazards that might be associated with organizational
business changes (e.g. addition of new routes or destinations, acquisition of new aircraft type(s), the
introduction of significant outsourcing of operational functions).
Typically hazards are assigned a tracking number and recorded in a log or database. Each log or
database entry would normally include a description of the hazard, as well as other information
necessary to track associated risk assessment and mitigation activities.
Expanded guidance may be found in the ICAO SMM, Document 9859.
ORG 3.1.2 The Operator shall have a safety risk assessment and mitigation program that includes
processes implemented and integrated throughout the organization to ensure:
(i) Hazards are analyzed to determine corresponding safety risks to aircraft operations;
(ii) Safety risks are assessed to determine the requirement for risk mitigation action(s);
(iii) When required, risk mitigation actions are developed and implemented in operations.
[SMS] (GM) ►
Note: Conformity with this ORG standard is possible only when the Operator is in conformity with all
repeats of this ORG standard in other ISM sections. Refer to the IAH for information that identifies
such repeats.
Auditor Actions
□ Identified/Assessed organizational safety risk assessment/mitigation program (focus: hazards
analyzed to identify/define risk; risk assessed to determine appropriate action; action
implemented/monitored to mitigate risk).
□ Identified/Assessed cross-discipline process for risk assessment/mitigation (focus: all
operational disciplines participate in process).
□ Interviewed SMS manager and/or designated management representative(s).
□ Examined selected records/documents that illustrate organizational integration (focus:
coordinated involvement of all operational disciplines in risk assessment/mitigation program).
□ Examined selected examples of risk assessment/risk mitigation action(s).
□ Coordinated to verify implementation of safety risk assessment/mitigation in all operational
areas.
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Safety Risk Assessment (SRA).
Risk assessment and mitigation is an element of the Safety Risk Management component of the
SMS framework.
To be completely effective, a risk assessment and mitigation program would typically be
implemented in a manner that:
• Is active in all areas of the organization where there is a potential for hazards that could
affect aircraft operations;
• Has some form of central coordination to ensure all existing or potential hazards that have
been identified are subjected to risk assessment and, if applicable, mitigation.
The safety risks associated with an identified existing or potential hazard are assessed in the context
of the potentially damaging consequences related to the hazard. Safety risks are generally
expressed in two components:
• Likelihood of an occurrence;
• Severity of the consequence of an occurrence.
Typically, matrices that quantify safety risk acceptance levels are developed to ensure
standardization and consistency in the risk assessment process. Separate matrices with different risk
acceptance criteria are sometimes utilized to address long-term versus short-term operations.
A risk register is often employed for the purpose of documenting risk assessment information and
monitoring risk mitigation (control) actions.
Expanded guidance may be found in the ICAO SMM, Document 9859.
Operational Reporting
ORG 3.1.3 The Operator shall have an operational safety reporting system that is implemented
throughout the organization in a manner that:
(i) Encourages and facilitates personnel to submit reports that identify safety hazards, expose
safety deficiencies and raise safety concerns;
(ii) Ensures mandatory reporting in accordance with applicable regulations;
(iii) Includes analysis and management action as necessary to address safety issues identified
through the reporting system. [SMS] (GM) ►
Note: Conformity with this ORG standard is possible only when the Operator is in conformity with all
repeats of this ORG standard in other ISM sections. Refer to the IAH for information that identifies
such repeats.
Auditor Actions
□ Identified/Assessed organizational operational safety reporting system (focus: system
urges/facilitates reporting of hazards/safety concerns; includes analysis/action to
validate/address reported hazards/safety concerns).
□ Interviewed SMS manager and/or designated management representative(s).
□ Examined records of selected operational/safety reports (focus: analysis/follow-up to
identify/address reported hazards/safety concerns).
□ Coordinated to verify implementation of operational safety reporting system in all operational
areas.
□ Other Actions (Specify)
Guidance
Safety reporting is a key aspect of SMS hazard identification and risk management.
Frontline personnel, such as flight or cabin crew members and maintenance technicians, are
exposed to hazards and face challenging situations as part of their everyday activities. An
operational reporting system provides such personnel with a means to report these hazards or any
other safety concerns so they may be brought to the attention of relevant managers.
To build confidence in the reporting process and encourage more reporting, an acknowledgement of
receipt is typically provided to each person that submits a report.
An effective system provides for a review and analysis of each report to determine whether a real
safety issue exists, and if so, ensure development and implementation of appropriate action by
responsible management to correct the situation.
Expanded guidance may be found in the ICAO SMM, Document 9859.
ORG 3.1.4 The Operator should have a confidential safety reporting system that is implemented
throughout the organization in a manner that encourages and facilitates the reporting of events,
hazards and/or concerns resulting from or associated with human performance in
operations. (GM) ►
Auditor Actions
□ Identified/Assessed organizational confidential safety reporting system (focus: system
urges/facilitates reporting of events/hazards/safety concerns caused by humans; reporters are
assured confidentiality; includes analysis/action to validate/address reported hazards/safety
concerns).
□ Interviewed responsible management representative(s).
□ Examined records of selected confidential safety reports (focus: assurance of confidentiality,
analysis/follow-up to identify/address reported hazards/safety concerns).
□ Crosschecked to verify implementation of confidential safety reporting system in all operational
areas.
□ Other Actions (Specify)
Guidance
The specified confidential safety reporting system is sometimes referred to as a Confidential Human
Factors (or Incident) Reporting System.
The success of a confidential safety reporting system depends on two fundamentals:
• The ability of the organization to assure absolute protection of a report submitted by any
individual;
• The level to which individuals within the organization exercise their freedom to report actual
or potential unsafe conditions or occurrences.
In certain states, information submitted under a pledge of confidentiality could be subject to laws
protecting such information. Therefore, an operator would typically have procedures in place to
protect report confidentiality (e.g. de-identification).
There is a difference between confidential reporting and anonymous reporting. Confidential reporting
is the preferred system because it permits feedback to the reporter in response to the report. Not only
is the reporter entitled to an explanation, but also such feedback provides excellent incentive for the
submission of future reports.
The effectiveness of a confidential safety reporting system is determined by a basic requirement for
safeguarding safety and risk information. Typically, individuals will continue to provide information
only when there is confidence that such information will be used only for safety purposes and will
never be compromised or used against them.
An effective confidential safety reporting system might typically include:
• A process that provides absolute protection of confidentiality;
• An articulated policy that encourages reporting of hazards and human errors in operations;
• A shared responsibility between the individual flight and cabin crew members (or, if
applicable, respective professional associations) and the organization to promote a
confidential safety reporting system;
• A tracking process of action taken in response to reports;
• A process to provide feedback to the reporter;
• A communication process for ensuring flight and cabin crew members, as well as other
relevant personnel, are informed of potential operating hazards through dissemination of de-
identified report information.
ORG 3.1.5 The Operator should have a non-punitive safety reporting system that is implemented
throughout the organization in all areas where operations are conducted. (GM)
Auditor Actions
□ Identified/Assessed organizational non-punitive safety reporting system (focus: system
urges/facilitates reporting of events/hazards/safety concerns; defines criteria for reporter non-
discipline; includes analysis/action to validate/address reported hazards/safety concerns).
□ Interviewed responsible management representative(s).
□ Examined records of selected non-punitive safety reports (focus: application of reporter non-
discipline criteria; analysis/follow-up to identify/address reported hazards/safety concerns).
□ Crosschecked to verify implementation of non-punitive safety reporting system in all operational
areas.
□ Other Actions (Specify)
Guidance
A non-punitive reporting system might also be referred to as an open reporting system. Such system
might be considered an attribute of a reporting culture.
Front line operational personnel are often in the best position to observe and identify operational
hazards and conditions, including the actions or behavior of other personnel that could lead to
accidents or incidents. Experience has shown that personnel will not provide information if there is
apprehension or fear that such reporting will result in disciplinary action.
To be effective, a non-punitive safety reporting system assures employees that the reporting of
unintentional errors does not result in disciplinary or punitive action being taken against the reporter
or other individuals involved unless such errors result from illegal activity, willful misconduct or other
egregious actions, as defined by the operator. Also, in such a system employees are assured that the
identity or information leading to the identity, of any employee who reports an error under this policy
is never disclosed unless agreed to by the employee or required by law.
A non-punitive safety reporting system is typically documented in operations manuals or other
controlled documents.
Expanded guidance may be found in the ICAO SMM, Document 9859.
effective method to determine if desired safety outcomes are being achieved, and to focus attention
on the performance of the organization in managing operational risks and maintaining compliance
with relevant regulatory requirements.
In addressing operational performance, meaningful measures typically focus on lower level (i.e.
lower consequence) occurrences or conditions that are considered by the operator to be precursors
to serious events. Performance measures may be specific to a certain area of operations or may be
broad and apply to the entire system.
In addressing compliance, meaningful measures, as a minimum, would focus on compliance with
significant regulatory requirements (as determined by the operator) in all operational areas.
Ideally, performance measures are designed to be challenging, which, in turn, enhances the
effectiveness of the risk management system.
Performance measures may be set in almost any operations or maintenance area. Some possible
examples include:
• Flight operations (e.g., takeoff and landing tail strikes, unsatisfactory line or training
evaluations);
• Operational control (e.g., flight diversions due to fuel);
• Engineering and maintenance (in-flight engine shutdowns, aircraft component/equipment
failures);
• Cabin operations (inadvertent slide deployments);
• Ground handling (aircraft damages due to vehicles or equipment);
• Cargo operations (dangerous goods spills);
• Operational security (unauthorized interference or access events).
Expanded guidance may be found in the ICAO SMM, Document 9859.
ORG 3.2.2 The Operator shall have a process to identify changes within or external to the
organization that have the potential to affect the level of safety risks associated with aircraft
operations, and to manage risks that may arise from or are affected by such changes. [SMS] (GM)
Auditor Actions
□ Identified/Assessed organizational change management process (focus: process
identifies/assesses internal/external changes to determine operational safety risk).
□ Interviewed SMS manager and/or designated management representative(s).
□ Examined selected records/documents that show processing of internal/external changes
(focus: assessment of changes to determine safety risk; actions taken to implement/revise
new/existing risk controls).
□ Coordinated to verify implementation of change management process in all operational areas.
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Change Management.
Change management is an element of the Safety Assurance component of the SMS framework.
Change management is considered a proactive hazard identification activity in an SMS.
Change may affect the appropriateness or effectiveness of existing safety risk mitigation strategies.
In addition, new hazards and related safety risks may be inadvertently introduced into an operation
whenever change occurs.
A change management process is designed to ensure risk management is applied to any internal or
external changes that have the potential to affect established operational processes, procedures,
products and services.
Internal changes typically include organizational expansion, contraction or consolidation, new
initiatives, business decisions, as well as the introduction of new or the modification of existing
systems, equipment, programs, products or services.
External changes could include new regulatory requirements or changes to the operating
environment (e.g. new security regulations, amendments to the dangerous goods regulations,
changes to the air traffic control system).
Expanded guidance may be found in the ICAO SMM, Document 9859.
Program Elements
ORG 3.3.10 The Operator shall have a process for the investigation of aircraft accidents and
incidents, to include reporting of events in accordance with requirements of the State. [SMS] (GM)
Auditor Actions
□ Identified/Assessed accident investigation process (focus: process includes compliance with
regulatory accident/incident reporting requirements; output includes final report with
recommendations).
□ Interviewed responsible manager(s).
□ Examined selected accident and incident reports (focus: investigation identifies operational
safety hazards, produces recommendations to prevent recurrence/mitigate risk).
□ Other Actions (Specify)
Guidance
Accident and incident investigation is considered a reactive hazard identification activity in an SMS.
A primary purpose of accident and incident investigation is hazard identification, which is an element
of the Safety Risk Management component of the SMS framework.
Investigations typically result in a report that describes the factors that contributed to the event, which
is then made available to responsible senior operational managers to permit them to evaluate and
implement appropriate corrective or preventive action.
An effective investigation process typically includes:
• Qualified personnel to conduct investigations (commensurate with operation size);
• Procedures for the conduct of investigations;
• A process for reporting investigative results;
• A system for implementing any corrective or preventive action;
• An interface with relevant external investigative authorities (when applicable);
• A process for the dissemination of information derived from investigations.
To ensure awareness among operational personnel, information derived from investigations is
disseminated to relevant areas throughout the organization.
In the event of a major accident, an operator responds to and possibly participates in an investigation
in accordance with provisions contained in ICAO Annex 13. Such capability requires an operator to
maintain an ongoing interface with relevant investigative authorities to ensure preparedness in the
event a major accident occurs.
Expanded guidance may be found in the ICAO SMM, Document 9859.
ORG 3.3.11 The Operator shall have a process for identifying and investigating irregularities and
other non-routine operational occurrences that might be precursors to an aircraft accident or incident.
[SMS] (GM)
Auditor Actions
□ Identified/Assessed process for identification/investigation of irregularities/non-routine
occurrences (focus: process output includes final report with recommendations).
□ Interviewed responsible manager(s).
□ Examined selected irregularity/non-routine occurrence reports (focus: process identifies
operational safety hazards, produces recommendations to mitigate risk).
□ Other Actions (Specify)
Guidance
Investigation of operational irregularities is considered a reactive hazard identification activity in an
SMS.
A primary purpose of investigating non-routine operational occurrences is hazard identification, which
is an element of the Safety Risk Management component of the SMS framework.
The investigation of irregularities or non-routine occurrences is a hazard identification activity. Minor
events, irregularities and occurrences occur often during normal operations, many times without
noticeable consequences. Identifying and investigating certain irregular operational occurrences can
reveal system weaknesses or deficiencies that, if left un-checked, could eventually lead to an
accident or serious incident. These types of events are referred to as accident precursors.
A process to monitor operations on a regular basis permits the identification and capture of
information associated with internal activities and events that could be considered precursors. Such
events are then investigated to identify undesirable trends and determine contributory factors.
The monitoring process is typically not limited to occurrences, but also includes a regular review of
operational threats and errors that have manifested during normal operations. Monitoring of normal
operations can produce data that further serve to identify operational weaknesses and, in turn, assist
the organization in developing system solutions.
As with the investigation of accidents and serious incidents, the investigation of minor internal
occurrences results in a report that is communicated to relevant operational managers for analysis
and the possible development of corrective or preventive action.
Expanded guidance may be found in the ICAO SMM, Document 9859.
ORG 3.3.12 (Intentionally open)
ORG 3.3.13 The Operator shall have a flight data analysis (FDA) program that is non-punitive and
contains adequate safeguards to protect data sources. The program shall include either:
(i) For aircraft of a maximum certified takeoff mass in excess of 27,000 kg (59,525 lb), a
systematic download and analysis of electronically recorded aircraft flight data, or
(ii) For all aircraft, a systematic acquisition, correlation and analysis of flight information derived
from a combination of some or all of the following sources:
(a) Aircraft flight data recorder (FDR) readouts;
(b) Confidential flight and cabin crew operational safety reports;
(c) Flight and cabin crew interviews;
(d) Quality assurance findings;
• A process for applying the output from flight data analysis to the management of risk and
assessment of flight operations performance;
• A process for management of the data, to include security and retention.
All or certain of the elements could be outsourced to an external party; however, the operator would
retain overall responsibility for the maintenance of the program.
The most comprehensive approach to flight data analysis would be a program that includes not only
systematic download and analysis of electronically recorded aircraft flight data (as described above),
but also acquisition, correlation and analysis of flight information derived from other sources (as
described below).
Where appropriate, there might be a formal agreement with applicable labor organizations to ensure
a mutually acceptable and structured approach to the investigation of significant safety events
identified through the FDA program.
Further guidance may be found in the ICAO Safety Management Manual (Doc 9859).
cooperation of the flight crew, systematically gather operational data that can be analyzed and used
to make real improvements to certain areas of the operation. Observers are particularly aware of, and
record, threats and errors that occur in the operating environment.
The Line Operations Safety Audit (LOSA) is a well-known and successful example of a normal line
operations monitoring program.
An acceptable program would have the following characteristics:
• A planned and organized series of observations of flight crew performance during normal line
flights is typically conducted a minimum of once during every four year period.
• Observations are conducted on regular and routine line flights, and the flight crew is advised
and clearly understands that normal line monitoring is not an evaluating, training or checking
activity. The flight crew would be expected to operate as if the observer were not there.
• There is mutual support and cooperation from both the management of the operator and
flight crew members (through their professional association, if applicable).
• Participation from the flight crew is voluntary; observations are not conducted unless
permission is received from the flight crew.
• Data collected from observations are confidential, de-identified and used for safety
enhancement purposes only. Data from an observation are never permitted to be used for
disciplinary action unless there is evidence of willful misconduct or illegal activity.
• Procedures are in place to ensure data from observations are retained in a way that ensures
effective security.
• Objectives of observations are clearly defined, and collected data are always used to
address specific issues that affect flight safety.
• Observers are specifically selected and trained (calibrated) to ensure a high level of
consistency and standardization in the data being collected. Observers are objective,
impartial and have a high level of integrity.
• There is a process in place to ensure data collected from observations are subjected to
analysis from appropriately diverse subject matter experts to ensure consistency and
accuracy.
• Data derived from observations are analyzed and presented in a manner that identifies
potential weakness and permits the operator to develop appropriate action(s) that will
enhance specific aspects of the operation.
• Results from the monitoring program, including the corrective action plan, are communicated
to flight crew members.
Expanded guidance may be found in the ICAO SMM, Document 9859.
Auditor Actions
□ Identified/Assessed quality assurance program (focus: role/purpose within organization/SMS;
definition of audit program scope/objectives; description of program elements/procedures for
ongoing auditing of management system/operational areas).
□ Interviewed SMS manager and/or designated management representative(s).
□ Interviewed quality assurance program manager.
□ Interviewed selected operational managers (focus: interface with quality assurance program).
□ Examined selected audit reports (focus: audit scope/process/organizational interface).
□ Coordinated to verify implementation of quality assurance audit program in all operational
areas.
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definitions of Audit and Quality Assurance.
The quality assurance program comprises two complementary functions: To monitor an operator's
compliance with relevant regulations and standards, as well as to evaluate and continually improve
operational safety performance. Such functions are elements of the Safety Assurance component of
the SMS framework.
In some organizations the quality assurance program may have a different name (e.g. internal audit
program, internal evaluation program).
A robust quality assurance program ensures a scope of auditing that encompasses all areas of the
organization that impact operational quality in terms of safety and/or security. Operational functions
include flight operations, operational control/flight dispatch, maintenance operations, cabin
operations, ground handling and cargo operations.
This provision is designed to permit flexibility in the implementation of the quality assurance program.
The structure and organization of the program within an operator's management system, whether
centralized, non-centralized or a combination thereof, is at the discretion of the operator in
accordance with its corporate culture and regulatory environment.
An effective audit program includes:
• Audit initiation, including scope and objectives;
• Planning and preparation, including audit plan and checklist development;
• Observation and gathering of evidence to assess documentation and implementation;
• Analysis, findings, actions;
• Reporting and audit summary;
• Follow-up and close out.
To ensure auditors gather sufficient evidence to produce realistic assessments during an audit, the
program typically includes guidance that defines the various sampling techniques that are expected
to be used by auditors in the evidence collection phase of the audit.
The audit process typically includes a means whereby the auditor and responsible personnel from
the audited area have a comprehensive discussion and reach agreement on the findings and
corresponding corrective actions. Clear procedures are established to resolve any disagreement
between the auditor and audited area.
All action items require follow-up to ensure closeout within an appropriate period of time.
ORG 3.4.2 The Operator shall appoint a manager with appropriate qualifications, authority and
independence that is responsible for:
(i) The performance of the quality assurance program;
(ii) Ensuring communication and coordination with operational managers in the management of
operational risk;
Auditor Actions
□ Identified/Assessed process for addressing quality assurance audit findings.
□ Interviewed quality assurance program manager.
□ Examined selected audit reports/records (focus: identification of root cause,
development/implementation of corrective action, follow-up to ensure effectiveness).
□ Coordinated to verify implementation of audit findings process in all operational areas.
□ Other Actions (Specify)
Guidance
Certain audit findings might fall under the category of hazards to operations. In such cases, the
hazard would be subject to the risk assessment and mitigation process in the development of
corrective action.
Refer to the IAH for information relevant to auditing under the quality assurance program.
ORG 3.4.4 The Operator shall have a process to ensure significant issues arising from the quality
assurance program are subject to management review in accordance with ORG 1.5.1 and, as
applicable, ORG 1.5.2. [SMS] (GM) ►
Note: Conformity with this ORG standard is possible only when the Operator is in conformity with all
repeats of this ORG standard in other ISM sections. Refer to the IAH for information that identifies
such repeats.
Auditor Actions
□ Identified/Assessed process for management review of quality assurance program issues
(focus: continual improvement of quality assurance program).
□ Interviewed SMS manager and/or designated management representative(s).
□ Interviewed quality assurance program manager.
□ Examined selected records/documents of management review of quality assurance program
issues (focus: specific issues/changes identified/implemented to improve quality assurance
program).
□ Coordinated to verify management review of significant quality assurance issues in all
operational areas.
□ Other Actions (Specify)
Guidance
Management review of significant quality assurance issues supports the continual improvement of
safety performance, which is an element of the Safety Assurance component of the SMS framework.
Such review permits senior management to consider significant issues of non-compliance in areas of
the organization that impact operational safety and security, and to:
• Continually monitor and assess operational safety and security outcomes;
• Ensure appropriate corrective or preventive actions that address the relevant compliance
issues have been implemented and are being monitored for effectiveness;
• Ensure continual improvement of operational safety and security performance.
ORG 3.4.5 (Intentionally open)
ORG 3.4.6 If the Operator is currently on the IOSA Registry, the Operator shall ensure the quality
assurance program as specified in ORG 3.4.1 provides for the auditing of the IOSA Standards and
Recommended Practices (ISARPs) a minimum of once during the IOSA registration period. For
internal audits of the ISARPs, the Operator shall have processes that ensure:
(i) The effective edition of the IOSA Standards Manual (ISM) is utilized;
(ii) Auditor Actions are accomplished by auditors. (GM)
Note: If a new edition of the ISM becomes effective during the first 19 months of the Operator's
24-month IOSA registration period, the Operator shall take into account all changes that might
require additional auditing (e.g. new or significantly revised ISARPs).
Auditor Actions
□ Identified/Assessed processes that ensure auditing of all ISARPs during the IOSA registration
period.
□ Identified/Assessed internal audit processes/procedures (focus: use of effective ISM edition;
auditors accomplish Auditor Actions).
□ Interviewed quality assurance program manager.
□ Interviewed selected internal auditors.
□ Examined selected database records/reports of audits performed against ISARPs (focus:
effective ISM edition used; Auditor Actions accomplished).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definitions of Auditor Actions, IOSA Operator, IOSA Registration Period and
Registration Renewal Audit.
The currently effective edition of the ISM is used for auditing of the ISARPs during the first 19 months
of the IOSA registration period. Use of an ISM edition that becomes effective in the final five (5)
months of the operator's registration period is optional.
To the extent possible, auditing of the ISARPs should be spread out over the full registration period
rather than waiting to conduct all auditing just prior to the registration renewal audit.
Refer to the IAH for information relevant to auditing of the ISARPs under the quality assurance
program.
ORG 3.4.7 If the Operator is currently on the IOSA Registry, the Operator shall have a process for
the production of a Conformance Report (CR) that is certified by the accountable executive (or
designated senior management official) as containing accurate information related to the audit of all
ISARPs as is specified in ORG 3.4.6. The CR shall be submitted in the English language and include
the following:
(i) Completed and signed Declaration of Internal Assessment Completion;
(ii) Record of Internal Auditors;
(iii) Operational Profile;
(iv) List of Document References. (GM)
Note: The specified process for production of a CR shall ensure the Operator's completed CR and
any accompanying documents are submitted to the Audit Organization (AO) no less than 14 days
prior to the start date of the registration renewal audit.
Note: Changes to the CR that occur after submission to the AO do not require a re-submission of the
CR.
Auditor Actions
□ Identified/Assessed process for producing/maintaining Conformance Report.
□ Interviewed AE or designated representative(s).
□ Interviewed quality assurance program manager.
□ Examined Conformance Report (focus: content includes all required information).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Conformance Report.
The IATA CR template contains fields for all information required to be included in the CR, as well as
instructions for completing each of the fields. Completion of the template will result in a Conformance
Report that contains all information necessary to be in conformity with ORG 3.4.7 and ORG 3.4.8.
A signed declaration, as specified in item i), may consist of an electronic signature.
The operational profile, as specified in item iii), is a compilation of information (types of operations
conducted, fleet composition) that is relevant to the audit of the operator. The CR template contains
fields that, once completed with the requested information, define the operational profile of an
operator.
The Conformance Report may also be produced using the operator's current internal database
software. In such case, it will be required that the CR:
• Is produced in an electronic format similar to that of the IATA Conformance Report template;
• Contains, as a minimum, all information specified in ORG 3.4.7 and ORG 3.4.8.
Refer to the IAH for detailed information relevant to production of the Conformance Report.
ORG 3.4.8 If the Operator is currently on the IOSA Registry, the Operator shall ensure the
Conformance Report produced in accordance with ORG 3.4.7 also contains information that is
specific to the audit of each individual IOSA standard and recommended practice, to include:
(i) The alpha-numeric identifier;
(ii) Appropriate documentation reference(s) (from the Operator's documentation system);
(iii) Auditor name(s);
(iv) Audit date(s);
(v) The list of Auditor Actions accomplished by the auditor(s) to assess implementation;
(vi) If applicable, a description of non-conformance(s) and:
(a) The root cause(s) of non-conformance(s);
(b) The corrective action(s) implemented to address non-conformance(s).
(vii) If applicable, a description of non-applicability (N/A);
(viii) The current status of conformance (documented and implemented). (GM)
Note: At the option of the Operator, items iii), iv), v) and, as applicable, vi) may be replaced in the CR
with accurate reference(s) to the location(s) where all such information may be found, either in the
Operator's electronic database as specified in ORG 3.4.14 or in controlled procedural documents
that are defined in audit processes as specified in ORG 3.4.6.
Auditor Actions
□ Identified/Assessed process for producing/maintaining Conformance Report.
□ Interviewed AE or designated representative(s).
□ Interviewed quality assurance program manager.
□ Examined Conformance Report (focus: content includes all required information).
□ Other Actions (Specify)
Guidance
Completion of the IATA Conformance Report Template will result in a Conformance Report that
contains all information necessary to be in conformity with ORG 3.4.7 and ORG 3.4.8.
The listing of Auditor Actions in the CR is indicative of what was done by auditors to gather evidence
that is subsequently subjected to analysis in order to determine whether or not a standard or
recommended practice is documented and implemented by the operator.
If an operator elects to provide references in the CR to electronic database locations or controlled
procedural documents, then all specified information will appear in those referenced locations.
An example of a controlled procedural document is an audit checklist that contains the procedure an
auditor will follow, including the specific Auditor Action steps, when auditing the individual standard or
recommended practice.
Regardless of location (i.e. CR, electronic database, procedural document), the record of Auditor
Actions will show the Auditor Action steps that were accomplished (or, if applicable, not
accomplished) when the individual IOSA standard or recommended practice was audited.
Refer to the IAH for information relevant to production of the Conformance Report.
ORG 3.4.9 (Intentionally open)
Program Elements
ORG 3.4.10 The Operator shall have an audit planning process and sufficient resources, including
auditors as specified in ORG 3.4.12, to ensure audits are:
(i) Scheduled at intervals to meet regulatory and management system requirements;
(ii) Completed within a specified time period. (GM) ►
Auditor Actions
□ Identified/Assessed quality assurance audit planning process (focus: audits
planned/scheduled/completed in order to meet applicable internal/external requirements).
□ Identified/Assessed audit resources (focus: availability of sufficient (auditors/other resources to
accomplish audit plan).
□ Interviewed quality assurance program manager.
□ Crosschecked audit plan with selected audit reports (focus: audits conducted in accordance
with audit plan).
□ Coordinated to verify implementation of audit plan in all operational areas.
□ Other Actions (Specify)
Guidance
The planning process produces a schedule of the audit modules to be conducted within the planning
period (e.g. calendar year) and reflect the status of each audit module, to include the applicable audit
interval (e.g. 12, 24, 36 months), the date of the previous audit and the scheduled due date for the
next audit.
Refer to the IAH for information relevant to planning and resources associated with auditing of the
ISARPs.
ORG 3.4.11 The Operator shall ensure the audit planning process defines the scope of each audit,
as appropriate for the area being audited, and also:
(i) Includes audit objectives that address ongoing compliance with regulatory requirements,
Operator standards and other applicable regulations, rules and standards;
(ii) Considers relevant operational safety or security events that have occurred;
(iii) Considers results from previous audits, including the effectiveness of corrective action that
has been implemented. (GM)
Auditor Actions
□ Identified/Assessed quality assurance audit planning process (focus: audits
planned/scheduled/completed in order to meet applicable internal/external requirements).
□ Interviewed quality assurance program manager.
□ Examined selected audit plans (focus: audit scope/objectives defined; operational
events/previous audits considered).
□ Crosschecked audit plan with selected audit reports (focus: audits conducted in accordance
with audit plan).
□ Other Actions (Specify)
Guidance
The audit scope refers to the breadth of operational disciplines or operational areas covered by an
audit and therefore will vary depending on the focus area for each audit (e.g., flight dispatch function,
dangerous goods handling, ramp handling operations, line maintenance activities).
Audit objectives define tangible achievements expected to result from an audit, normally expressed
as a statement of intent (e.g. to determine compliance with regulatory requirements, to establish
conformity with operator standards, to assess conformity with IOSA standards, to determine
efficiency of operations).
To be effective, auditors prepare for an audit of a particular area of operations by:
• Conducting research into any relevant incidents or irregularities that may have occurred;
• Reviewing reports from previous audits.
Refer to the IAH for information relevant to planning associated with auditing of the ISARPs.
ORG 3.4.12 The Operator shall ensure the quality assurance program utilizes auditors that are
impartial and functionally independent from the operational activities to be audited. (GM)
Auditor Actions
□ Identified/Assessed quality assurance auditor administration program (focus: definition of
selection/qualification criteria for quality assurance program auditors).
□ Interviewed quality assurance program manager.
□ Examined selected individual auditor records (focus: application of selection/qualification
criteria).
□ Crosschecked selected audit reports (focus: appropriately qualified auditors independent from
the activity audited).
□ Interviewed selected quality assurance auditors (focus: verification of individual qualifications).
□ Other Actions (Specify)
Guidance
A quality assurance program is independent in a manner that permits the scheduling and conduct of
audits as deemed appropriate for the size and scope of operations. Functional independence
ensures auditors are not put in a position where their objectivity may be subject to bias due to
conflicting responsibilities.
A code of conduct may be used to enhance the impartiality and independence of auditors. An
effective auditor code of ethics would require auditors:
• To act in a strictly trustworthy and unbiased manner in relation to both the organization to
which they are employed, contracted or otherwise formally engaged and any other
organization involved in an audit performed by them or by personnel under their direct
control;
• To disclose to their employer any relationship they may have with the organization to be
audited before undertaking any audit function in respect of that organization;
• Not to accept any gift, commission, discount or any other profit from the organization audited,
from their representatives, or from any other interested person nor knowingly allow personnel
for whom they are responsible to do so;
• Not to disclose the findings, or any part of them, nor to disclose any other information gained
in the course of the audit to any third party, unless authorized in writing by both the auditee
and the audit organization, if applicable;
• Not to act in any way prejudicial to the reputation or interest of the audit organization; and
• In the event of any alleged breach of this code, to co-operate fully in any formal enquiry
procedure.
An auditor may be considered functionally independent from the operational activities to be audited
when he/she is not responsible for the activity being audited (at the time of the audit). For example, a
flight crew member may audit line flight operations from the flight deck jump seat as an independent
observer (supernumerary), but may not do so when functioning as part of the operating crew (or
functioning as an augmenting crew member).
Refer to the IAH for information relevant to auditor qualification and independence.
ORG 3.4.13 The Operator shall have a training and qualification program that ensures auditors that
conduct auditing under the quality assurance program as specified in ORG 3.4.1:
(i) Have the knowledge, skills and work experience needed to effectively assess areas of the
management system and operations that will be audited;
(ii) Maintain an appropriate level of current audit experience;
(iii) Complete initial and continuing auditor training that provides the knowledge and
understanding necessary to effectively conduct audits against:
(a) Applicable regulations and standards;
(b) If the Operator is currently on the IOSA Registry, the ISARPs.
(iv) Are evaluated on a periodic basis. (GM)
Note: Sub-specification iii) b) is applicable to auditors that may be assigned to conduct internal
auditing against the ISARPs.
Auditor Actions
□ Identified/Assessed auditor training and qualification program.
□ Interviewed quality assurance program manager.
□ Examined selected individual auditor records (focus: completion of initial/continuing
qualification/periodic evaluations, in accordance with program standards).
□ Interviewed selected quality assurance auditors (focus: verification of initial/continuing
qualifications).
□ Crosschecked selected audit reports/records (focus: currency of auditors).
□ Other Actions (Specify)
Guidance
The intent of this standard is for the operator to have a program that ensures all auditors that conduct
auditing under its quality assurance program, including internal auditor personnel (e.g. employees) or
external auditor personnel (e.g. consultants), are trained, evaluated and qualified in accordance with
the criteria specified in this standard.
The delivery of auditor training and evaluation under the operator's program may be accomplished by
the operator or by an external party (or a combination of both) as long as all auditors that conduct
auditing under the operator's quality assurance program are trained, evaluated and qualified in
accordance with the criteria specified in this standard.
Internationally recognized standards published in ISO 19011 provide a reliable guide for the training
and/or certification of auditors utilized in the quality assurance program.
For all auditors that conduct auditing of the management system, and of operations and maintenance
functions for the operator under its quality assurance program as specified in ORG 3.4.1, training and
qualification typically addresses the following subject areas:
• Application of audit principles, procedures and techniques;
• Planning and organizing work effectively;
• Conducting the audit within the agreed timescale;
• Prioritizing and focusing on matters of significance;
• Collecting information (i.e. audit evidence) through effective interviewing, listening, observing
and examination of documents, records and data;
• Understanding the appropriateness and consequences of using sampling techniques for
auditing;
• Verifying the accuracy of collected information;
• Confirming the sufficiency and appropriateness of audit evidence to support audit findings
and conclusions;
• Assessing those factors that can affect the reliability of the audit findings and conclusions;
• Using work documents to record audit activities;
• Preparing audit reports;
• Maintaining the confidentiality and security of information;
• Communicating effectively, either through personal linguistic skills or through an interpreter.
For those auditors assigned to conduct auditing against the ISARPs as specified in ORG 3.4.6,
training and qualification typically addresses the following subject areas:
• IOSA program overview;
• IOSA documentation;
• Understanding the role of the ICAO annexes as the primary source of specifications
contained in the ISARPs;
• Reading and understanding the ISARPs;
• IOSA quality assurance requirements (ORG subsection 3.4);
• Auditor Actions;
• Mandatory observations;
• Root cause analysis;
• Conformance Report (CR);
• Auditing ORG and repeated ORG ISARPs;
• Auditing SMS;
• Auditing quality assurance;
• Assessing outsourced operational functions.
Refer to the IAH-Airlines for information relevant to the training and qualification of auditors that
assess conformity with the ISARPs.
ORG 3.4.14 The Operator shall have an electronic database to ensure the effective management
of information and data associated with audits conducted under the quality assurance program. Such
database shall include:
(i) Information and data derived from audits of the management system, and operations and
maintenance functions, as specified in ORG 3.4.1;
(ii) Information that is specific to the audit of each individual IOSA standard and recommended
practice as specified in ORG 3.4.8. (GM)
▲ An operator may conform to ORG 3.4.14 i) through Active Implementation as long as the
implementation Action Plan (IAP) projects conformance on or before 1 September 2018.
Auditor Actions
□ Identified/Assessed electronic database for management of quality assurance audit data.
□ Interviewed quality assurance program manager.
□ Examined selected database records (focus: content includes information/data specified in ORG
3.4.8).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Database.
A fully completed IATA Conformance Report Template may be considered as a database equivalent
for the purpose of conforming to item ii) of this standard.
Refer to the IAH for information that addresses options for the production and format of the
Conformance Report.
Refer to the ISM Introduction for the description of Active Implementation.
Auditor Actions
□ Identified/Assessed processes for monitoring external service providers that conduct
outsourced operational functions.
□ Interviewed responsible manager(s).
□ Examined selected records/reports resulting from monitoring of service providers (focus:
monitoring process ensures provider is fulfilling applicable safety/security requirements).
□ Coordinated to verify implementation of service provider monitoring in applicable operational
areas.
□ Other Actions (Specify)
Guidance
An operator has a responsibility to ensure outsourced operational functions are conducted in a
manner that meets its own operational safety and security requirements. A monitoring process is
necessary to satisfy that responsibility, and such process would be applicable to any external service
provider that conducts outsourced operational functions, including the parent organization or a
separate affiliate of the operator.
In some regulatory jurisdictions, there may be a regulatory control process that permits certain
organizations to meet rigorous standards and become approved to conduct outsourced operations or
maintenance for an operator. Such regulatory control process would be an acceptable means for
meeting the specification of this provision if it can be demonstrated by the operator that the regulatory
control process:
• Includes ongoing monitoring of the approved service providers;
• Such monitoring is sufficiently robust to ensure the approved service providers fulfill the
operational requirements of the operator on a continuing basis.
Achieving and maintaining IOSA and/or ISAGO registration is a way for an external service provider
to demonstrate fulfillment of requirements that affect the safety and/or security of operations. Thus,
an operator's process that requires such service providers to maintain IOSA and/or ISAGO
registration would be acceptable as a method of monitoring when such registration(s) is/are used in
conjunction with a risk assessment of the provider.
To ensure effective monitoring, consideration is given to a range of internal and external methods for
use in the oversight of external service providers. Methods might include auditing, systematic review
and risk assessment of reported hazards and/or occurrences, monitoring of performance output
(KPIs), reporting and governance processes; monitoring and analysis of targeted risk areas, as well
as the establishment of an effective two-way communication link with the service provider.
Under certain circumstances, operational functions may be involuntarily removed from an operator
and conducted by a governmental or quasi-governmental authority that is not under the control of the
operator (e.g., passenger or baggage security screening at some airports). Under such
circumstances, the operator would have a process to monitor output of the function being conducted
by the authority to ascertain desired results are being achieved.
ORG 3.5.3 The Operator should include auditing as a process for the monitoring of external service
providers in accordance with ORG 3.5.2. (GM)►
Auditor Actions
□ Identified/Assessed auditing processes used for monitoring external service providers that
conduct outsourced operational functions.
□ Interviewed responsible manager(s).
□ Examined selected records/reports resulting from auditing of service providers (focus: audit
process ensures provider is fulfilling applicable safety/security requirements).
□ Coordinated to verify implementation of service provider auditing in applicable operational
areas.
□ Other Actions (Specify)
Guidance
The intent of this provision is for an operator to use, as deemed appropriate for the situation, auditing
as one of the processes for satisfying the requirement for monitoring external service providers (as
specified in ORG 3.5.2).
Both IOSA and ISAGO are audit programs, so, where applicable, the use of IOSA or ISAGO
registration could be considered as an audit process for the purpose of monitoring external service
providers.
ORG 3.5.4 If the Operator satisfies aircraft operational needs through a wet lease agreement with
one or more other operators, the Operator shall have a process to monitor the performance of such
wet lease operators for the purpose of ensuring the operational safety and security needs of the
Operator are being fulfilled. (GM)
Auditor Actions
□ Identified/Assessed process for monitoring safety/security performance of wet lease operators.
□ Interviewed responsible managers.
□ Examined plan for monitoring wet lease operators (focus: includes all applicable wet lease
operators).
□ Examined selected wet lease monitoring reports (focus: monitoring process ensures wet lease
operator is fulfilling applicable safety/security requirements).
□ Other Actions (Specify)
Guidance
Under a wet lease agreement, one operator (the lessee) leases an aircraft from another operator (the
lessor), and the aircraft is operated and supported by the lessor. Typical support functions include
operational control of flights, maintenance of aircraft and/or implementation of security controls.
Typically, the lessee may monitor the performance of the lessor by requesting certification,
conducting inspections and audits, accepting third party audits, flight monitoring or other means.
For wet lease agreements in excess of three months, it is recommended for operators that conduct
passenger flights to wet lease with IOSA-registered operators.
ORG 3.5.5 (This standard is currently suspended in accordance with the IOSA Standards Special
Review Process)
Guidance
This provision applies only to products that are purchased or otherwise acquired from an external
supplier or vendor. Whereas purchasing might be the most typical means of acquiring such products,
other means might be also be used (e.g. lease, barter).
This provision does not apply to outsourced operational functions or services that are provided by an
external organization or service provider (this is addressed in ORG 3.5.1 and 3.5.2).
This provision does not apply to electronic navigation data products utilized in flight (e.g. FMS
database) or for operational control (e.g. flight planning database). The acquisition of such navigation
data products require control procedures, as specified in Sections 2 (FLT) and 3 (DSP).
Following are some examples of products that could have a negative effect on operations if put into
service with substandard quality (i.e. the operator's technical standards are not met):
• Training devices (e.g. simulators, door mock-ups);
• Cabin safety cards or videos;
• Cabin service carts or trolleys;
• Onboard safety equipment (e.g. PBE, life jackets);
• Ground support equipment;
• Operational software, databases (non-navigation);
• Security screening equipment;
• Unit load devices (ULDs).
Part of the process is a method for identifying products that have a direct effect on the safety or
security of operations.
To ensure technical specifications are met, a process may focus on the supplier, the product or a
combination of both.
The process may include an evaluation of suppliers, with the selection of suppliers based on their
ability to supply products in accordance with the operator's requirements and technical specifications.
The use of formal industry supplier audit or evaluation programs is one means for assessing the
abilities of suppliers to deliver quality products, such as the Coordinating Agency for Supplier
Evaluation (CASE).
Implementation of a rigorous receiving inspection process (or equivalent activity) provides another
means of verifying that operationally critical products meet specified technical requirements prior to
such products being put into service.
4 Emergency Response
Guidance
Refer to the IRM for the definition of Emergency Response Plan (ERP).
Emergency response planning is an element of the Safety Policy and Objectives component of the
SMS framework.
An emergency (or crisis) response plan is based upon an assessment of risk appropriate to the size
and type of operations, and includes consideration of a major aircraft accident and other potential
aircraft and/or non-aircraft events that would require a full corporate emergency response.
In some states, emergency or crisis response is assumed by a governmental authority rather than by
the operator. In such case, an emergency response plan focuses on and addresses interaction with
and/or participation in the governmental response to an emergency or crisis.
An effective ERP includes industry best practices and ensure community expectations are
addressed. Additionally, an ERP:
• Specifies general conditions for implementation;
• Provides a framework for an orderly implementation;
• Ensures proper coordination with external entities at all potential locations (refer to
ORG 4.1.4);
• Addresses all potential aspects of an event, including casualties;
• Ensures regulatory requirements associated with specific events are satisfied;
• Provides a scenario for the transition back to normal operations;
• Ensures regular practice exercises as a means to achieve continual improvement (refer to
ORG 4.1.14 and ORG 4.1.15).
ORG 4.1.2 The Operator shall have a designated manager with appropriate qualifications and
authority to manage and be responsible for the development, implementation and maintenance of the
corporate ERP. (GM)
Auditor Actions
□ Identified designated corporate ERP manager.
□ Examined job description of ERP manager (focus: background/duties/responsibilities).
□ Interviewed corporate ERP manager.
□ Other Actions (Specify)
Guidance
The exact title of the manager designated as responsible for the corporate ERP may vary depending
on the organization.
In order to manage a corporate ERP, an individual's qualifications would typically include training and
background experience that ensures the requisite knowledge in emergency response principles.
Such experience and knowledge is necessary, even though various ERP functions are typically
delegated to designated personnel throughout the management system.
ORG 4.1.3 If the Operator has individual departmental or station emergency response plans within
the organization, the Operator shall ensure such individual plans are coordinated with the overall
corporate emergency response plan under the ERP manager. (GM)
Auditor Actions
□ Identified/Assessed process(es) for coordinating departmental/station ERPs.
□ Interviewed designated corporate ERP manager.
□ Examined ERP for selected stations (focus: station ERP is coordinated with corporate ERP).
□ Other Actions (Specify)
Guidance
Certain operational departments might have individual ERPs, especially where departments are
located remotely (e.g. maintenance or cargo). Likewise, station ERPs might be individually tailored to
meet varying requirements at each station. Therefore, coordination is always required to ensure each
individual ERP within an operator's organization contains or addresses the applicable common
elements of the corporate ERP.
ORG 4.1.4 The Operator shall ensure the ERP as specified in ORG 4.1.1 includes provisions for
the appropriate coordination with the emergency response plans of other applicable organizations
relevant to the particular event or crisis. [SMS] (GM)
Auditor Actions
□ Identified/Assessed ERP transition processes (focus: plan includes transition from normal-
emergency/and emergency-normal operations; coordination with relevant external
organizations).
□ Interviewed designated corporate ERP manager.
□ Other Actions (Specify)
Guidance
ERP transition and reporting is an element of the Safety Policy and Objectives component of the
SMS framework.
An ERP typically defines:
• Coordination procedures for action by key personnel;
• External entities that will interact with the organization during emergency situations;
• ERPs of external entities that will require coordination;
• Method(s) of establishing coordination with external ERPs.
Expanded guidance may be found in the ICAO SMM, Document 9859.
ORG 4.1.5–4.1.9 (Intentionally open)
Plan Elements
ORG 4.1.10 The Operator shall have a process in the ERP to provide an accurate manifest to the
appropriate authorities in the event of an aircraft accident. Such manifest shall list crew members,
passengers and cargo, to include dangerous goods.
Auditor Actions
□ Identified/Assessed ERP process for providing accurate manifest to authorities in the event of
aircraft accident.
□ Interviewed designated corporate ERP manager.
□ Identified specific person/function with assigned responsibility for providing accurate manifest to
authorities in the event of aircraft accident.
□ Other Actions (Specify)
ORG 4.1.11 (Intentionally open)
ORG 4.1.12 The Operator shall have published procedures and assigned responsibilities to ensure
a coordinated execution of the corporate ERP. (GM)
Auditor Actions
□ Identified/Assessed procedures/responsibilities for execution of corporate ERP.
□ Interviewed designated corporate ERP manager.
□ Coordinated to verify procedures/assigned responsibilities for ERP execution in all operational
areas.
□ Other Actions (Specify)
Guidance
Personnel are typically assigned with specific responsibilities throughout the organization for the
implementation of procedures associated with the ERP. Such responsibilities and procedures might
include:
• Assemblage of required personnel;
• Travel arrangements, as required;
• Provision of facilities, equipment and other resources;
• Humanitarian and other assistance to individuals involved in the event, as required;
• Management of continuing normal operations;
• Control of areas impacted by the event, as applicable;
• Liaison with relevant authorities and other external entities.
The following areas would normally be considered in developing plans for liaison with external
entities associated with any event:
• Fire;
• Police;
• Ambulance;
• Coast guard and other rescue agencies;
• Hospitals and other medical facilities;
• Medical specialists;
• Civil aviation or defense agencies;
• Poison control centers;
• Chemical or radiation specialists;
• Environmental agencies;
• Insurance companies.
Additionally, contact and arrangements are typically made with certain operational business partners,
including code share and wet lease operators.
ORG 4.1.13 The Operator should ensure all personnel with responsibilities under the ERP are
appropriately trained and qualified to execute applicable procedures. (GM)
Auditor Actions
□ Identified/Assessed training/qualification program for ERP personnel.
□ Interviewed designated corporate ERP manager.
□ Examined training curriculum for ERP personnel (focus: training subjects appropriate for role in
ERP).
□ Examined selected training/qualification records of ERP personnel (focus: completion of ERP
training).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Family Assistance.
Training for personnel with responsibilities under the ERP could be conducted externally or in-house
by an operator's own qualified staff, and would typically include drills, desktop exercises, and/or
simulations. Attendees typically include both management and operational personnel from the
headquarters and, as applicable to the operator's structure, station locations.
Ideally, specific and/or personalized training would also be conducted for key senior managers (e.g.
CEO).
Training programs are generally tailored for personnel based on the role performed under the ERP.
Typically, persons involved in family assistance and crisis communications, as well as members of
the corporate emergency response group or committee (as applicable), would be required to
complete ERP training.
The curriculum for ERP training normally includes general subjects associated with emergency
response management, as well as role-specific subjects that address issues associated with:
• Family assistance/special assistance;
• Cultural sensitivity;
• Telephone enquiry;
• Team call-out and assembly;
• Crash site discipline;
• Effects retrieval.
ORG 4.1.14 The Operator shall ensure the corporate ERP is rehearsed periodically to:
(i) Familiarize personnel with responsibilities and procedures;
(ii) Ensure ready functionality of all equipment and facilities;
(iii) Expose deficiencies in the plan and its execution, and ensure such deficiencies are
addressed. (GM)
Auditor Actions
□ Identified/Assessed plan for corporate ERP rehearsal (focus: definition of rehearsal
type/schedule; rehearsals include use of applicable personnel/facilities/equipment).
□ Interviewed designated corporate ERP manager.
□ Examined selected records of ERP rehearsals (focus: implementation/completion of ERP
rehearsals).
□ Other Actions (Specify)
Guidance
The ERP typically has provisions that ensure all aspects of the ERP are rehearsed or practiced at
regular intervals, and practice exercises include the involvement of all personnel that would be called
upon during an actual emergency or crisis situation. In some locations, the extent of ERP rehearsals
might be limited by the relevant authority. In such cases, a modified rehearsal that ensures overall
ERP readiness in accordance with the specifications stated in this provision is acceptable.
Rehearsal of an ERP typically results in the discovery of, and thus an opportunity to correct,
deficiencies in the plan. Such deficiencies could include outdated contact information (e.g. names,
telephone numbers, email addresses) and/or plan execution discrepancies (e.g. organizational
changes, personnel turnover).
The results of rehearsals or practice exercises are normally recorded and analyzed, and then used
as the basis for continual improvement of the plan (refer to ORG 4.1.15).
ORG 4.1.15 The Operator should have a process for a detailed debriefing and critique whenever
the ERP is executed, either as a rehearsal or in response to an actual event. (GM)
Auditor Actions
□ Identified/Assessed process for debriefing/critique after execution of ERP (focus:
debriefing/critique part of actual/rehearsed ERP implementation).
□ Interviewed designated corporate ERP manager.
□ Examined selected records of detailed debriefing/critique after rehearsal/actual ERP activation.
□ Other Actions (Specify)
Guidance
Such process ensures vital information is communicated to regulatory authorities, corporate
management, operational personnel and the local community whenever the ERP is activated,
whether for an actual event or for a rehearsal.
If recommendations for corrective action or other changes result from activation of the plan, there
should be a process for providing a de-briefing to relevant internal and external entities to ensure
awareness and consideration of such recommendations.
ORG 4.1.16 The Operator should have the ready availability of a facility for use as an emergency
command center with sufficient space, furnishings and equipment to successfully manage the
execution of the corporate ERP.
Auditor Actions
□ Observed/Assessed emergency command center (focus: adequate
space/furnishings/equipment to manage ERP and associated resources).
□ Interviewed designated corporate ERP manager.
□ Other Actions (Specify)
ORG 4.1.17 The Operator should have procedures under the corporate ERP that ensure a central
coordination and control of all communications with external entities. (GM)
Auditor Actions
□ Identified/Assessed ERP procedures for central coordination/control of communications with
external entities.
□ Interviewed designated corporate ERP manager.
□ Other Actions (Specify)
Guidance
A vital aspect of an effective ERP is ensuring a controlled and consistent message to external
entities, especially the news media. The ERP should designate an individual or group as the central
point of control for all external communication. Additionally, authorization and responsibilities should
be assigned to certain personnel within the organization to act as the point(s) of contact for
communication with specified external entities.
ORG 4.1.18 The Operator should have resources immediately available under the corporate ERP
that provide for, in the event of an emergency:
(i) The establishment of local emergency command centers at line stations or remote locations;
(ii) A telephone enquiry center capable of handling the potential volume of calls expected with
emergency events;
(iii) Dedicated equipment and material necessary for successful execution of the corporate
ERP;
(iv) The dispatch on short notice of humanitarian teams to appropriate location(s) to attend to
individuals in need of assistance.
Auditor Actions
□ Identified/Assessed resources available under corporate ERP (focus: local command centers;
adequate communication capability; humanitarian personnel/teams for humanitarian/victim
family assistance).
□ Interviewed designated corporate ERP manager.
□ Observed examples of resources available in the event of ERP activation.
□ Other Actions (Specify)
Applicability
Section 2 addresses safety and security requirements for flight operations, and is applicable to an operator
that utilizes two-pilot, multi-engine aircraft with a maximum certificated takeoff mass in excess of 5,700 kg
(12,566 lbs.) to conduct:
• Passenger flights with or without cabin crew;
• Cargo flights with or without the carriage of passengers or supernumeraries.
Additionally, the IOSA standards and recommended practices (ISARPs) in Section 2 are applicable only to
those aircraft that are of the type authorized in the Air Operator Certificate (AOC) and utilized in
commercial passenger and/or cargo operations unless applicability is extended to encompass non-
commercial operations as stated in a note immediately under the body of the provision.
Individual provisions or sub-specifications within a provision that:
• Begin with a conditional phrase (“If the Operator...”) are applicable if the operator meets the
condition(s) stated in the phrase.
• Do not begin with a conditional phrase are applicable unless determined otherwise by the Auditor.
Individual provisions that contain the <AC> symbol in the reference number are applicable to an operator
that conducts flights with cargo aircraft.
Where an operator outsources flight operations functions to external service providers, an operator retains
responsibility for ensuring the management of safety in the conduct of such operations and must
demonstrate processes for monitoring applicable external service providers in accordance with
FLT 1.11.2.
Some cabin safety specifications applicable to functions or equipment within the scope of flight operations
are located in Section 5 (CAB) of this manual.
General Guidance
The definitions of technical terms used in this ISM Section 2, as well as the list of abbreviations and
acronyms, are found in the IATA Reference Manual for Audit Programs (IRM).
under the supervision of flight operations and flight operations personnel (e.g., development of
procedures, training of personnel, following procedures).
Refer to Guidance associated with ORG 1.1.1 located in ISM Section 1.
FLT 1.1.2 The Operator shall have one or more designated managers in the flight operations
organization that, if required, are post holders acceptable to the Authority, and have the
responsibility, and thus are accountable, for ensuring:
(i) The management and supervision of all flight operations activities;
(ii) The management of safety and security in flight operations;
(iii) Flight operations are conducted in accordance with conditions and restrictions of the Air
Operator Certificate (AOC), and in compliance with applicable regulations and standards of
the Operator. (GM) ◄
Auditor Actions
□ Identified designated/nominated managers for flight operations.
□ Examined job description of manager for flight operations (focus:
authority/accountabilities/responsibilities for flight operations organization).
□ Interviewed responsible manager of flight operations.
□ Interviewed other managers in flight operations.
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definitions of Accountability, Authority, Post Holder and Responsibility.
The term “manager” is generic; the actual title associated with such positions will vary with each
operator.
In some states the individual that fills certain key managerial positions within the flight operations
organization must be nominated and then either accepted or approved by the Authority as specified
in ORG 1.1.4. Managers in such positions might be referred to as post holders, directors or another
title as specified by each State. The specification in item ii) ensures the manager for the flight
operations organization is accountable to senior management for the elements of operational safety
and security specifically related to the conduct or supervision of flight operations. Safety and security
management at this operational level typically occurs within the greater context of the operator's
overall or corporate safety and/or security management plan. For example, the overall requirements
for security of the flight deck would typically be specified in an operator's security plan, but the actual
operational management of flight deck security would occur under the supervision of flight operations
and flight operations personnel (i.e. development of procedures, training of personnel, following
procedures). In this example, in order to conform to the specifications of item ii), the manager of the
flight operations organization would be accountable to senior management for ensuring the day to
day security of the flight deck.
Refer to ORG 1.1.4 located in ISM Section 1.
Threshold times for EDTO are typically calculated in ISA and still air conditions at the one-engine
inoperative cruise speed for aircraft with two turbine engines and at the all-engine operating cruise
speed for aircraft with more than two turbine engines.
The approvals in item vii) e) also typically address the most limiting EDTO significant system time
limitation, if any, and any applicable EDTO certification requirements.
The specification in item vii) h) refers to approvals for a wide range of RNAV and RNP operations that
allow access to RNAV routes and terminal procedures designed with specific RNAV/RNP capabilities
in mind. RNP adds onboard navigation monitoring and alerting to RNAV, and is a statement of the
navigation performance that would be required to operate within a defined airspace. It is important to
note that there are numerous standard RNP levels and associated applications. Equally important is
the prerequisite that any approvals associated with RNAV, which require the maintenance of a
particular RNP, typically associate the RNP level required with the approved application (e.g.
RNP 0.1 to 1.0 for RNP AR Approach segments and RNP 10 for oceanic/remote areas where 50 NM
lateral separation is applied).
□ Examined job description for selected management positions (focus: authority/responsibility for
liaison with external entities).
□ Other Actions (Specify)
Guidance
Refer to Guidance associated with ORG 1.3.3 located in ISM Section 1 regarding the need to
coordinate and communicate with external entities.
The specifications of this provision are intended to ensure ongoing compliance with regulations,
organizational standards and other applicable rules and requirements.
FLT 1.3.5 (Intentionally open)
FLT 1.3.6 The Operator shall assign responsibility to the pilot-in-command (PIC) for:
(i) The safety of all crew members, passengers and/or cargo on board the aircraft when the
doors are closed;
(ii) The operation and safety of the aircraft from the moment the aircraft is ready to move for the
purpose of taking off until the moment it finally comes to rest at the end of the flight and the
engine(s) are shut down;
(iii) Ensuring checklists are complied with. (GM)
Auditor Actions
□ Identified/Assessed documents that assign responsibilities to the PIC.
□ Interviewed responsible manager(s) in flight operations.
□ Interviewed flight/cabin crew members.
□ Observed line flight and flight simulator operations (focus: PIC demonstrates responsibility for
safety of flight; ensures compliance with checklists).
□ Other Actions (Specify)
Guidance
The intent of this provision is to ensure that the specified responsibilities are assigned to the PIC and
such assignment is evident in Operator policies or procedures.
Specifications in item i) and ii) may be satisfied by policies documented in, or referenced in, the OM
that assign responsibilities to the PIC in a manner consistent with regulations of the State and the
intent of the provision. Slight variations in the wording of policies are permissible if the periods of
responsibility as specified in each item are addressed by the operator's policies.
For example, an operator could assign responsibility to the PIC for the safety of passengers from the
time they board the aircraft until they deplane. Such policy would satisfy this provision because it
exceeds the period of PIC responsibility as specified in this provision.
The specification in item iii) may be satisfied by any policy or combination of policies that assign the
responsibility for compliance with standard operating procedures to the PIC.
FLT 1.3.7 The Operator shall ensure, for the duration of each flight, one pilot is designated to act
as PIC. (GM)
Auditor Actions
□ Identified/Assessed documents that describe flight crew composition and/or succession of
command.
□ Interviewed responsible manager(s) in flight operations.
□ Interviewed flight crew members.
□ Observed line flight operations (focus: designation of primary PIC).
□ Other Action (Specify)
Guidance
The specification of this provision is satisfied if one pilot is designated to act as PIC, regardless of
crew configuration or en route crew changes.
The operator may choose to address the specification of this provision as part of a plan for
succession of command in accordance with FLT 1.3.8.
FLT 1.3.8 The Operator shall ensure the duties and responsibilities of flight crew members, to
include a plan for succession of command, are defined and described in the OM. (GM)
Auditor Actions
□ Identified/Assessed OM description of flight crew composition and/or succession of command.
□ Interviewed responsible manager(s) in flight operations.
□ Interviewed flight crew members.
□ Observed line flight operations (focus: flight crew responsibilities/duties performed as defined).
□ Other Action (Specify)
Guidance
Refer to the IRM for the definition of Flight Crew Member.
FLT 1.3.9 The Operator shall have a policy to address willful and deliberate violation of flight
operations organizational policies and/or procedures by flight operations personnel. (GM)
Auditor Actions
□ Identified policy that addresses willful/deliberate violation of flight operations policies/procedures
by flight operations personnel.
□ Interviewed responsible manager(s) in flight operations.
□ Examined selected records of policy enforcement.
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Controlled Document.
Appropriate policy regarding procedure violations typically includes NAA intervention, committee for
case review (operator, trade union or mixed) and/or equivalent types of action.
The specification of this provision is applicable to flight operations personnel and is not restricted only
to flight crew.
The policy may be documented or referenced in the OM or reside in another controlled document
that is available to the flight crew.
FLT 1.3.10 If the Operator utilizes supernumeraries in the passenger cabin or supernumerary
compartment of an aircraft that are required for the safety of operations in accordance with
FLT 2.2.44, the Operator should have policies and procedures that:
(i) Define and describe duties or responsibilities assigned to such personnel that are related to
safety;
(ii) Ensure such supernumeraries do not impede flight crew members in the performance of
their duties;
(iii) If a cabin crew is used, ensure supernumeraries do not impede cabin crew members in the
performance of their duties. (GM)
Auditor Actions
□ Identified/Assessed policies/procedures that define and address the use of supernumeraries.
□ Examined defined duties and responsibilities for supernumeraries.
□ Interviewed responsible manager(s) in flight operations.
Auditor Actions
□ Identified/Assessed operational safety and security coordination process(es).
□ Interviewed responsible manager(s) in flight operations.
□ Examined selected evidence of internal/external coordination.
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definitions of Aircraft Operating Manual (AOM) and Approved Flight Manual.
Some examples of issues that could affect operational safety and security include aircraft
modifications, new equipment, new destinations/routes, or regulatory changes.
The specifications of this provision are satisfied if an operator can demonstrate that a process exists
within the flight operations organization that ensures necessary internal and external coordination.
The coordination processes specified in this provision may occur during meetings or other means of
liaison (e.g. email, memos, conference call).
The specification in item iv) refers to coordination with the following or other appropriate categories of
personnel:
• The operations engineering manager or other person responsible for defining, producing,
customizing and distributing aircraft performance data;
• The manager responsible for defining, producing, customizing and/or distributing route and
airport instructions or information, NOTAMs and FMS databases, if applicable;
• The operations engineering manager or other person in charge of aircraft equipment
specification.
The specification in item iv) typically includes coordination on the following operational safety issues:
• Fleet and cross-fleet standardization;
• Flight deck layout;
• Aircraft avionics, instrumentation, equipment and/or components in accordance with the
provisions of FLT 4.3.1.
The specification in item vi) refers to coordination with respect to staffing necessary to meet operator
requirements.
FLT 1.4.3 The Operator shall have a process to ensure the dissemination of safety-critical
operational information to appropriate personnel within and external to the flight operations
organization, to include:
(i) Airworthiness Directives (ADs);
(ii) Manufacturer bulletins;
(iii) Flight crew bulletins or directives;
(iv) NOTAMs. (GM)
Auditor Actions
□ Identified/Assessed process that ensures the dissemination of safety-critical operational
information.
□ Interviewed responsible manager(s) in flight operations.
□ Interviewed front line personnel.
□ Examined selected evidence of information dissemination.
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definitions of Airworthiness Directive, Flight Crew Bulletin and NOTAM.
The intent of this provision is to ensure a process is in place to disseminate safety critical information
to personnel that require it.
Auditor Actions
□ Identified/Assessed instructor/evaluator/line check airman selection criteria and processes.
□ Interviewed responsible manager(s) in flight operations.
□ Examined selected instructor/evaluator/line check airman candidate screening records.
□ Other Actions (Specify)
Guidance
The intent of this provision is to ensure instructors and evaluators are selected in a manner
consistent with the overall objectives of an operator's training program. To achieve this aim a
selection criteria and processes would typically include:
• Confirmation that a minimum level of experience has been attained;
• A review of the training records of potential selectees;
• Recommendations from Flight Operations management and/or the training department.
FLT 1.5.6 (Intentionally open)
FLT 1.5.7 The Operator should have a procedure for screening or testing prospective flight crew
members for psychoactive substances, unless such screening or testing is performed or prohibited
by the State.
Auditor Actions
□ Identified/Assessed procedure used for screening/testing flight crew members for psychoactive
substances.
□ Interviewed the responsible manager(s) in flight operations.
□ Examined selected records of flight crew screening/testing for psychoactive substances.
□ Other Actions (Specify)
FLT 1.5.8 The Operator shall have a policy that addresses the use of psychoactive substances by
flight crew crewmembers, which, as a minimum:
(i) Prohibits the exercise of duties while under the influence of psychoactive substances;
(ii) Prohibits the problematic use of psychoactive substances;
(iii) Requires that all personnel who are identified as engaging in any kind of problematic use of
psychoactive substances are removed from safety-critical functions;
(iv) Conforms to the requirements of the Authority. (GM)
Auditor Actions
□ Identified/Assessed policy that addresses use of psychoactive substances by flight crew
members.
□ Interviewed responsible manager(s) in flight operations.
□ Interviewed flight crew members (focus: familiarity with psychoactive substance policy).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definitions of Biochemical Testing, Psychoactive Substance and Problematic
Use of Substances.
Operators subject to laws or regulations of the State that preclude the publication of a psychoactive
substance prohibition policy as specified in this provision may demonstrate an equivalent method of
ensuring that personnel engaging in any kind of problematic use of psychoactive substance abuse do
not exercise their duties and are removed from safety-critical functions.
Re-instatement to safety-critical duties could be possible after cessation of the problematic use and
upon determination that continued performance is unlikely to jeopardize safety.
Required manuals and documents may be carried on board by the flight crew. Also, maintenance of
the manuals and documents carried on board by the flight crew may be delegated to the flight crew.
Required onboard manuals and documents may also be contained in an EFB device or system used
in accordance with FLT 3.5.3.
This provision refers to any organized system for documentation retention that contains current
manuals, regulatory publications and other essential documents associated with flight operations.
FLT 1.6.2 (Intentionally open)
FLT 1.6.3 The Operator shall ensure the system for the management and control of flight
operations documentation as specified in ORG 2.1.1 and Table 1.1 addresses documents from
external sources, to include, as a minimum:
(i) As applicable, regulations of the State and of the other states or authorities relevant to
operations;
(ii) As applicable, relevant ICAO International Standards and Recommended Practices;
(iii) Airworthiness Directives;
(iv) As applicable, Aeronautical Information Publications (AIP) and NOTAMS;
(v) Manufacturer's Approved Flight Manual (AFM), including performance data, weight/mass
and balance data/manual, checklists and MMEL/CDL;
(vi) As applicable, other manufacturer's operational communications. (GM)
Auditor Actions
□ Identified/Assessed system(s) for management and control of documentation and data used in
flight operations (focus: system includes management/control of specified documents from
external sources).
□ Interviewed responsible manager(s) in flight operations.
□ Examined selected documents from external sources (focus: application of management/control
elements).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definitions of Aeronautical Information Publication (AIP), Aircraft Operating
Manual (AOM), Approved Flight Manual (AFM), Configuration Deviation List (CDL), Master Minimum
Equipment List (MMEL) and Minimum Equipment List (MEL).
The specification in items i) and ii) refer to relevant regulations, standards and recommended
practices made applicable to the operator by any states or authority with jurisdiction over the
operations of the operator. Applicable authorities typically include those authorities that have
jurisdiction over international operations conducted by an operator over the high seas or over the
territory of a state that is other than the State of the Operator.
The specification in item i) refers to applicable regulations imposed on an operator by the State,
which issues the Air Operator Certificate (AOC), and other states and/or authorities that actively
regulate foreign operators. This may be done through the issuing of an Operational Specification
(OPS SPEC) or specific state legislation.
The specification in item ii) refers to applicable ICAO standards and/or recommended practices that
are referenced in the operator's documentation.
The specification for the manufacturer's AFM in item v) may be replaced by an Aircraft Operating
Manual (AOM) customized by the manufacturer for the specific use in flight operations by an
operator. In such case, the MMEL may also be replaced by an MEL.
The specification in item vi) refers to bulletins or directives distributed by the manufacturer for the
purposes of amending aircraft technical specifications and/or operating procedures.
FLT 1.6.4 The Operator shall ensure documentation used in the conduct or support of flight
operations, including the Operations Manual (OM) and associated revisions:
(i) Contains legible and accurate information;
(ii) Is written in language(s) understood by flight operations personnel;
(iii) Is presented in a format that meets the needs of flight operations personnel;
(iv) If required, is accepted or approved by the Authority. (GM) ◄
Auditor Actions
□ Identified/Assessed system(s) for management/control of content/format of operational
documentation/data used in flight operations.
□ Interviewed responsible manager(s) in flight operations.
□ Examined selected parts of the OM (focus: legibility/accuracy/format; approval as applicable).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definitions of Operations Manual, State Acceptance and State Approval.
The intent of this provision is for an operator to provide operational documentation in a form that is
acceptable to the Authority and useable by all relevant personnel.
Documentation used in the support of flight operations may:
• Exist in electronic form;
• Be issued in more than one language.
FLT 1.6.5 (Intentionally open)
FLT 1.6.6 The Operator shall ensure documents that comprise the onboard library, as specified in
Table 2.1, are carried on board the aircraft for each flight and located in a manner that provides for
access by the flight crew. (GM)
Auditor Actions
□ Identified/Assessed the document that describes the onboard library.
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight operations (focus: content/accessibility of onboard library).
□ Other Actions (Specify)
Guidance
Refer to Table 2.1 for specifications related to accessing performance calculations via telecom
systems (e.g. ACARS) in lieu of onboard documentation.
FLT 1.6.7 (Intentionally open)
FLT 1.6.8 <AC> If the Operator conducts flights with cargo aircraft, the Operator should ensure the
parts of the Operations Manual that address ground handling are on board the aircraft. (GM)
Auditor Actions
□ Identified/Assessed onboard library (focus: includes parts of OM that address ground handling).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight operations (focus: onboard library includes ground handling guidance).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Cargo Aircraft.
The intent of this provision is for an operator to have the specified portions of the OM on board the
aircraft if such documentation would be required for flight crew members or other personnel (flight or
ground) to accomplish their assigned duties. As such, the applicability of the specification is
determined by requirements of the operator or the State.
(ii) The specific parts of the OM relevant to flight crew are clearly identified and defined;
(iii) Any differences from procedures and checklists provided by the manufacturer(s) are based
on operational considerations. (GM)
Auditor Actions
□ Identified/Assessed process used to develop flight crew checklists and procedures.
□ Identified specific parts of OM relevant to flight crew.
□ Interviewed responsible manager(s) ) in flight operations.
□ Observed line flight operations (focus: flight crew use/interpretation of OM and related
checklists).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Human Factors Principles.
The intent of this provision is to ensure procedures and checklists are developed in a manner that
ensures they are useable, identifiable and consistent with manufacturer specifications. Any
deviations from manufacturer procedures or checklists are typically based on operational concerns
identified by the operator.
Human factors principles in document design and checklist usage typically address the following:
• Preparation of documentation in a useable format for information presentation, at the
appropriate reading level and with the required degree of technical sophistication and clarity.
• Improving user performance through the use of effective and consistent labels, symbols,
colors, terms, acronyms, abbreviations, formats and data fields.
• Ensuring the availability and usability of information to the user for specific tasks, when
needed, and in a form that is directly usable.
• Designing operational procedures for simplicity, consistency and ease of use.
• Enabling operators to perceive and understand elements of the current situation and project
them to future operational situations.
• Minimizing the need for special or unique operator skills, abilities, tools or characteristics.
• Assessing the net demands or impacts upon the physical, cognitive and decision-making
resources of the operator, using objective and subjective performance measures.
The specification in item ii) ensures the relevant sections of the OM are clearly identified as the OM
can, in some instances, include sections published for flight operations personnel other than flight
crew. As such, all OM sections need not be provided to the flight crew (e.g., training syllabi are
usually restricted to training/checking personnel).
Refer to FLT 1.6.1 for specifications applicable to all flight operations documentation, including the
OM.
FLT 1.7.5–1.7.6 (Intentionally open)
FLT 1.7.7 The Operator shall have a description of the Operational Flight Plan (OFP) or equivalent
document in the OM, which includes:
(i) An outline of the OFP content;
(ii) Guidance for its use by flight crews. (GM)
Auditor Actions
□ Identified/Assessed description of OFP in OM or equivalent document.
□ Examined selected OFP(s).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Operational Flight Plan (OFP).
Items readily available in other documentation, obtained from another acceptable source or irrelevant
to the type of operation, may be omitted from the OFP.
Refer to DSP 1.7.2 contained in ISM Section 3 for an outline of the OFP content.
Auditor Actions
□ Identified/Assessed process for back-up of electronic flight operations records (focus: system
defines schedule for periodic file backup).
□ Interviewed responsible manager(s) in flight operations.
□ Examined selected record(s) of back-up files for electronic records.
□ Other Actions (Specify)
Guidance
Refer to Guidance associated with ORG 2.2.2 located in ISM Section 1.
Auditor Actions
□ Identified/Assessed quality assurance audit planning process in flight operations (focus: audits
planned/scheduled/completed in order to meet applicable internal/external requirements).
□ Identified/Assessed audit resources (focus: availability of sufficient auditors/other resources to
accomplish audit plan).
□ Interviewed Quality Assurance Program Manager.
□ Crosschecked audit plan with selected audit reports, to verify adherence to plan (focus: audits
conducted in accordance with audit plan).
□ Other Actions (Specify)
Guidance
Refer to Guidance associated with ORG 3.4.10 located in ISM Section 1.
Intervals of surveillance activities typically vary, depending on the operator.
Previous outcomes would typically be considered by the operator when determining audit intervals.
FLT 1.10.3 The Operator shall have a process to ensure significant issues arising from audits of
flight operations functions are subject to management review in accordance with ORG 1.5.1 and, as
applicable, ORG 1.5.2. [SMS] (GM) ◄
Auditor Actions
□ Identified/Assessed process for management review of flight operations quality assurance
issues (focus: continual improvement of quality assurance program).
□ Interviewed responsible quality assurance program manager.
□ Examined selected records/documents of management review of flight operations quality
assurance program issues (focus: specific issues/changes identified and implemented to
improve quality assurance program).
□ Other Actions (Specify)
Guidance
Refer to ORG 1.5.1, 1.5.2, 3.4.4 and associated Guidance located in ISM Section 1.
Significant issues are typically defined by the operator, and are regarded as those issues that could
impact the safety, security and/or quality of flight operations.
FLT 1.10.4 The Operator shall have a process for addressing findings that result from audits of
flight operations functions, which ensures:
(i) Identification of root cause(s);
(ii) Development of corrective action as appropriate to address the finding(s);
(iii) Implementation of corrective action in appropriate operational areas;
(iv) Evaluation of corrective action to determine effectiveness. (GM) ◄
Auditor Actions
□ Identified/Assessed process for addressing/closing flight operations audit findings.
□ Interviewed responsible quality assurance program manager.
□ Examined selected audit reports/records (focus: identification of root cause,
development/implementation of corrective action, follow-up to evaluate effectiveness).
□ Other Actions (Specify)
Guidance
Refer to Guidance associated with ORG 3.4.3 located in ISM Section 1.
Auditor Actions
□ Identified/Assessed acceptance processes for ensuring acquired products used in flight
operations meet technical requirements.
□ Interviewed responsible manager(s) in flight operations.
□ Examined selected product acceptance records (focus: products meet flight operations technical
requirements).
□ Other Actions (Specify)
Guidance
Refer to guidance associated with ORG 3.6.1 located in ISM Section 1.
The specifications of this provision address data or products that directly affect aircraft, flight deck, or
cabin operational safety. Such data or products typically include GPWS terrain and obstacle
databases, airport analysis data, weight/mass and balance data and performance data.
The intent of the monitoring and control specifications of this provision pertaining to data is to ensure
operational data acquired from external suppliers and used for the support of flight operations are
current, accurate and complete.
Electronic navigation data product integrity is addressed in FLT 1.11.4.
FLT 1.11.4A If the Operator utilizes aircraft with electronic navigation data capabilities, the
Operator shall have processes, approved or accepted by the State, if required, which ensure
electronic navigation data products acquired from suppliers, prior to being used as a means for
navigation in operations:
(i) Are assessed for a level of data integrity commensurate with the intended application;
(ii) Are compatible with the intended function of equipment in which it is installed;
(iii) Are distributed in a manner to allow insertion of current and unaltered electronic navigation
data into all aircraft that require it. (GM)
Auditor Actions
□ Identified/Assessed processes for acceptance/internal distribution of electronic navigation data
products.
□ Identified suppliers of electronic navigation data products (focus: suppliers accredited in
accordance with approved/accepted standards of data integrity/quality).
□ Interviewed responsible manager(s) in flight operations.
□ Examined selected product acceptance records (focus: products assessed for data integrity,
currency and compatibility with intended function).
□ Examined selected aircraft data insertion records (focus: current/unaltered data inserted on all
applicable aircraft).
□ Coordinated with MNT auditor (focus: verification of currency of aircraft navigation databases).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Navigation Data Integrity.
The responsibility of ensuring that electronic navigation data is assessed for integrity and is
compatible with its intended application rests with the operator.
Navigation database integrity can be assured by obtaining data from a supplier accredited in
accordance with approved or accepted standards of data integrity and quality. Such standards
include:
• RTCA/DO-200A, Standards for Processing Aeronautical Data, issued 09/28/98;
• RTCA/DO-201A, Standards for Aeronautical Information, issued 04/19/00;
• Advisory Circular (AC) 20-153A, Acceptance of Data Processes and Associated Navigation
Databases, issued 09/20/10;
• Any other State-approved or State-accepted standards of data integrity and quality that
assure navigation database integrity.
The specifications in items i) and ii) may be satisfied by the operator, in accordance with State-
approved or State-accepted methods for assuring data integrity and compatibility, such as:
• Obtaining a letter of acceptance from an applicable authority stating the data supplier
conforms to a recognized standard for data integrity and compatibility that provides an
assurance level of navigation data integrity and quality sufficient to support the intended
application; or
• The existence of operator and flight crew validation processes to determine navigation data
compatibility and accuracy that provide an assurance level of navigation data integrity and
quality sufficient to support the intended application.
Letters of acceptance are approved by the applicable authority (the state where data is sourced or
supplied) and approved or accepted by the State (state in which the data is applied). For example,
the FAA, via a letter of acceptance, attests to the integrity of data from a U.S. supplier. The State
would subsequently approve or accept the FAA letter as the operator's means to assure data
integrity.
The specification in item iii) refers to processes that ensure timely insertion of data and mitigate the
introduction of aeronautical information errors related to the content of navigation databases. The
physical insertion of navigation data into applicable aircraft is addressed in ISM Section 4 (MNT),
Subsection 2, Maintenance Control.
Monitoring and control of electronic navigation data products acquired from suppliers would also be
in accordance with FLT 1.11.3.
FLT 1.11.4B If the Operator utilizes aircraft equipped with a GPWS with a Forward-looking Terrain
Avoidance Function, the Operator should ensure terrain and, if applicable, obstacle data acquired
from an external vendor or supplier is distributed in a manner to allow the timely insertion of current
and unaltered data into all aircraft for which it is required. (GM)
Auditor Actions
□ Identified/Assessed processes for internal distribution of terrain/obstacle data acquired for use
on aircraft with GPWS and FLTA function.
□ Identified suppliers of terrain/obstacle data.
□ Interviewed responsible manager(s) in flight operations.
□ Examined selected terrain/obstacle data insertion records (focus: timely insertion of
current/unaltered data into all applicable aircraft).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of GPWS with a Forward-looking Terrain Avoidance (FLTA)
Function.
The intent of this provision is to ensure operators develop the means to periodically update GPWS
terrain and, if applicable, obstacle databases, for the purposes of reducing false warnings and
ensuring actual hazards are properly identified.
The specifications of this provision refer to:
• Terrain database(s) for all areas of potential operations and surrounding airports of intended
use;
• If an obstacle database is commercially available and obstacle detection/display functionality
is installed, obstacle databases for all areas of potential operations.
FLT 1.11.5 If the Operator has external service providers conduct outsourced flight operations
functions, the Operator should include auditing as a process for the monitoring of external service
providers in accordance with FLT 1.11.2. (GM) ◄
Auditor Actions
□ Identified/Assessed auditing processes used for monitoring external flight operations service
providers.
□ Interviewed responsible manager(s) in flight operations.
□ Examined selected records/reports resulting from auditing of flight operations service providers
(focus: audit process ensures provider is fulfilling applicable safety/security requirements).
□ Other Actions (Specify)
Guidance
Monitoring and control of external organizations typically include random samplings, product audits,
supplier audits, or other similar methods.
Refer to guidance associated with ORG 3.5.3 located in ISM Section 1.
Operational Reporting
FLT 1.12.3 The Operator shall have an operational safety reporting system in the flight operations
organization that:
(i) Encourages and facilitates flight crew members and other flight operations personnel to
submit reports that identify safety hazards, expose safety deficiencies and raise safety
concerns;
(ii) Ensures mandatory reporting in accordance with applicable regulations;
(iii) Includes analysis and flight operations management action as necessary to address safety
issues identified through the reporting system. [SMS] (GM) ◄
Auditor Actions
□ Identified/Assessed operational safety reporting system in flight operations (focus: system
urges/facilitates reporting of hazards/safety concerns; includes analysis/action to
validate/address reported hazards/safety concerns).
□ Interviewed responsible manager(s) in flight operations.
□ Interviewed person(s) that perform operational safety report review/analysis/follow-up in flight
operations.
on the performance of the organization in managing operational risks and maintaining compliance
with relevant regulatory requirements.
Performance measures in flight operations might address, for example, takeoff or landing tail strikes,
unsatisfactory line or training evaluations, unstabilized approaches, runway incursions, or any other
measurable occurrences that are managed by the SMS.
Refer to Guidance associated with ORG 3.2.1 located in ISM Section 1.
Auditor Actions
□ Identified/Assessed flight crew training/qualification program (focus: program includes each
type of aircraft in the fleet).
□ Identified/Assessed AQP/ATQP/EBT elements/regulatory approval (as applicable).
□ Interviewed responsible manager(s) in flight operations.
□ Examined training/qualification course curriculum for selected aircraft types (focus: inclusion of
applicable training/qualification courses for each aircraft type).
□ Examined training/qualification records of selected flight crew members (focus: completion of
applicable training/qualification courses).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definitions of Advanced Qualification Program (AQP), Alternative Training
and Qualification Program (ATQP) and Evidence-based Training (EBT).
The intent of this provision is to ensure an operator's training program contains the elements
necessary to ensure flight crew members are continuously competent to perform assigned duties.
The initial qualification process provided to newly hired crew members typically includes company
indoctrination and initial endorsement on company aircraft types. This presupposes that the newly
hired crew member already holds a commercial flying license.
Initial endorsement training may not be required as part of initial qualification if a newly hired crew
member already holds a type endorsement acceptable to both the State and the Operator. Company
indoctrination training, however, is considered a part of initial qualification.
Continuing qualification includes recurrent or refresher training and also includes any training
necessary to meet recency-of-experience requirements.
Transition (conversion) training refers to an aircraft type qualification training and evaluation program
for each type of aircraft in the fleet and is not required when an operator only utilizes one type of
aircraft.
Specialized training could also include training on a specific type of new equipment (e.g., ACAS).
AQP/ATQP incorporate the elements and specifications contained in FLT 2.1.1B, Table 2.6 and
Table 2.7.
EBT incorporates the elements and specifications contained in FLT 2.1.1B, Table 2.6 and Table 2.8.
Training could be outsourced, in which case services typically range from simple dry lease of a
training device to delegation of all training to an external organization (e.g., Authorized Flight Training
School).
FLT 2.1.1B If the Operator conducts training and evaluation in accordance with an AQP, ATQP or
EBT program, such program shall be approved or accepted by the Authority and incorporate all of the
elements and specifications contained in Table 2.6 and, as applicable, Table 2.7 or Table 2.8. (GM)
Auditor Actions
□ Identified/Assessed flight crew AQP/ATQP/EBT (focus: regulatory approval; requirements for
elements/specifications in accordance with Tables 2.6, 2.7).
□ Interviewed responsible manager(s) in flight operations.
□ Examined selected training/qualification course curricula/syllabi for different aircraft types.
□ Examined selected flight crew member training/qualification records (focus: completion of
AQP/ATQP/EBT elements).
□ Other Actions (Specify)
Guidance
AQP/ATQP incorporate the elements and specifications contained in FLT 2.1.1B, Table 2.6 and
Table 2.7.
EBT incorporates the elements and specifications contained in FLT 2.1.1B, Table 2.6 and Table 2.8.
An operator, in accordance with the requirements of the Authority, typically uses technical guidance
for the development of an AQP, ATQP or EBT program. Such guidance might be derived from one or
more of the following source references, as applicable:
• Office of the Federal Register, (2 October 1990), Special Federal Aviation Regulation 58 -
Advanced Qualification Program, Federal Register, Vol. 55, No. 91, Rules and Regulations
(pp. 40262-40278).
• FAA 14 CFR Part 121, Subpart Y.
• FAA Advisory Circular 120–54A, Advanced Qualification Program (23 June 2006).
• Advisory Circular 120–35B (6 September 1990), Line Operational Simulations, Federal
Aviation Administration, Washington D. C.: U. S. Department of Transportation.
• FAA Advisory Circular 120–51 (3 January 1995), Crew Resource Management Training,
Federal Aviation Administration, Washington D. C.: U. S. Department of Transportation.
• Commission Regulation (EC) No. 859/2008 of 20 August 2008 OPS 1.978 Alternative
Training and Qualification Program (ATQP) and Appendix 1 to OPS 1.978.
• Mangold, S., and Neumeister, D. (1995). CRM in the model AQP: A preview. In R. S. Jensen
and L.A. Rakovan (Eds.), Proceedings of the Eighth International Symposium on Aviation
Psychology (pp 556-561), Columbus; the Ohio State University.
• ICAO Doc 9995 Manual of Evidence-based Training First Edition.
• IATA Evidence-Based Training Implementation Guide July 2013 1st Edition.
• IATA Data Report for Evidence-Based Training August 2014 1st Edition.
• Any equivalent reference document approved or accepted by the Authority for the
development of an advanced training and qualification program designed to conform to the
specifications of Table 2.6 and Table 2.7.
FLT 2.1.2 The Operator shall ensure objectivity is maintained in the training and evaluation
program, and that instructors, evaluators and line check airmen are permitted to perform assigned
activities without inappropriate interference from management and/or external organizations. (GM)
Auditor Actions
□ Identified/Assessed requirement for objectivity in flight crew training/evaluation program.
□ Interviewed responsible manager(s) in flight operations.
□ Interviewed selected instructors/evaluators (focus: evaluation criteria/methodology).
□ Examined selected instructor/evaluator job descriptions.
□ Observed flight simulator operations (focus: objectivity; no undue external interference in
training/evaluation).
□ Other Actions (Specify)
Guidance
The intent of this provision is to ensure an absence of bias in the training and evaluation program that
permits trainees to be objectively assessed against the operating standards set forth by the operator
and/or authority without undue internal or external interference.
Policies and/or procedures used to address objectivity do not apply to ground training courses and
evaluations, but do typically address one or more of the following:
• If applicable, the organizational structure of an operator's training program that ensures flight
crew members are trained and evaluated by separate and distinct departments or individuals
within the training organization;
• The requirements of the State related to the evaluation of pilots to whom an evaluator may
have given flight instruction for a license or rating during Type qualification, Transition
(conversion), Upgrade to PIC and/or Re-qualification;
• The proper conduct of evaluations administered in conjunction with simulator, aircraft and/or
line training, whether conducted or administered by any of the following:
○ Different organizations, or
○ Different individuals than those that conducted the majority of the training, or
○ A common instructor and check airman (e.g. training to proficiency).
• Exceptions that may be appropriate under extenuating circumstances, such as the
introduction of new aircraft types or the management of very small fleets.
FLT 2.1.3 The Operator shall ensure flight crew members receive training that supports the
introduction of:
(i) New policies, rules, instructions and procedures;
(ii) New aircraft types, systems and fleet modifications/upgrades. (GM)
Auditor Actions
□ Identified/Assessed methodology for introduction of specified new elements into flight crew
training/evaluation program.
□ Interviewed responsible manager(s) in flight operations.
□ Examined selected training/qualification course curricula/syllabi (focus: examples of new
elements as specified).
□ Observed flight simulator operations (focus: training/evaluation reflects current
policies/procedures/equipment/aircraft modifications).
□ Other Actions (Specify)
Guidance
This provision is satisfied if a process exists for the introduction into the training program of each
specification that results from the coordination processes required by FLT 1.4.2. Such coordination
processes typically occur:
• Within the training program;
• Between those responsible for the training program and the relevant areas of the
organization in accordance with FLT 1.4.2.
FLT 2.1.4 If the Operator utilizes distance learning and/or distance evaluation in the flight crew
training and qualification program, the Operator shall ensure such training and/or evaluation is
monitored in accordance with FLT 2.1.28 and, if required, is approved or accepted by the State. (GM)
Auditor Actions
□ Identified/Assessed regulatory approval, process for monitoring/continual improvement of
distance learning in flight crew training/evaluation program.
□ Interviewed responsible manager(s) in flight operations.
□ Examined selected distance learning/qualification course development records (focus:
monitoring/continual improvement).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Distance Learning.
Distance learning refers to flight crew training or evaluation that is not conducted in a classroom or
face-to-face with an instructor or evaluator, but rather is conducted through the use of distributed
printed material or electronic media (e.g., Internet, compact disc, etc.).
FLT 2.1.5–2.1.9 (Intentionally open)
Training Manual
FLT 2.1.10 The Operator shall have a Training Manual for the use of flight operations personnel,
which may be issued in separate parts, that contains the details of all relevant training programs,
policies, procedures, requirements and other guidance or information necessary to administer the
Operator's Training Program. The Training Manual shall, as a minimum, be managed and controlled
as specified in FLT 1.6.1, and be in accordance with specifications contained in FLT 1.6.4 and
Table 2.2. (GM)
Auditor Actions
□ Identified/Assessed flight crew training manual, regulatory approval, content in accordance with
Table 2.2.
□ Interviewed the responsible manager(s) in flight operations.
□ Examined selected parts of training manual (focus: content includes
policies/procedures/requirements, other guidance/information necessary to administer the
training/evaluation program.
□ Observed flight simulator operations (focus: simulator training consistent with Training Manual).
□ Other Actions (Specify)
Guidance
The training manual typically applies to instructors, evaluators, line check airmen, flight crew
members, training schedulers, simulator operations personnel, administrative support personnel and
other applicable flight operations personnel.
The training manual may be split among several publications with the relevant parts made easily
accessible to the appropriate personnel.
FLT 2.1.11 (Intentionally open)
FLT 2.1.12 The Operator shall ensure the Training Manual contains standards for flight crew
training and evaluation that have been approved or accepted by the State and include, as a
minimum:
(i) Standardized procedures for training and the conduct of evaluations;
(ii) Standards that ensure piloting technique and the ability to execute normal and non-normal
procedures are checked in a way that demonstrates each pilot's competence;
(iii) A requirement that simulated aircraft, weather and environmental conditions are
standardized and appropriate for the training/evaluation being administered;
(iv) If the Operator conducts training flights, a definition of the conditions and/or maneuvers that
can be safely simulated in the aircraft, as well as the minimum weather and environmental
conditions required to ensure the training/evaluation being administered can be safely and
effectively conducted;
(v) Limits for the number of times maneuvers may be repeated and the evaluation still be
considered acceptable;
(vi) Procedures for remedial training and subsequent evaluation of a flight crew unable to
achieve or maintain required standards. (GM)
Auditor Actions
□ Identified/Assessed flight crew training manual, regulatory approval of standards..
□ Interviewed the responsible manager(s) in flight operations.
□ Examined selected parts of training manual (focus: content includes specified
standards/requirements).
□ Examined training/qualification records of selected flight crew members (focus: application of
training manual standards/requirements in flight crew training).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definitions of Maneuver Tolerances and Training Flights.
The intent of this provision is to ensure that the standards for flight crew training and evaluation are
published or referenced in the Training Manual.
The specifications in item ii) of this provision are normally satisfied by the application of tolerances to
normal and non-normal maneuvers during training and evaluations for the following flight
parameters:
• Heading
• Airspeed
• Height/altitude
• Course tracking
With respect to item iv), operators that conduct training flights and cannot safely train/evaluate a non-
normal maneuver or procedure in an aircraft or in a representative flight simulator as specified in
FLT 2.2.38 may demonstrate an alternative means of conformance in accordance with FLT 2.2.41.
For training and/or evaluations conducted in an aircraft during line operations, maneuver tolerances
normally include allowances for turbulence, aircraft characteristics and passenger comfort.
Remedial training and subsequent evaluation of flight crew unable to achieve or maintain required
standards can be tailored to the needs of the individual concerned.
The terms “normal” and “non-normal/emergency” typically refer to AOM checklists, procedures
and/or maneuvers. The term “non-normal” includes AOM emergency checklists and/or procedures
(i.e. an emergency procedure is a subset of non-normal).
The terms can also be used to describe an event, situation or operation that would be addressed by
normal or non-normal/emergency procedures or checklists. When used in this manner, the terms
may be separated by forward slash marks (e.g. normal/non-normal/emergency).
FLT 2.1.13 (Intentionally open)
FLT 2.1.14 The Operator shall ensure instructors, evaluators, line check airmen and flight crew
members use documents for the conduct of training and evaluation that are authorized by the
Operator for such use. (GM)
Auditor Actions
□ Identified/Assessed requirement for use of authorized documents by instructors/evaluators/line
check airmen/flight crew members in flight crew training/evaluation program.
□ Interviewed the responsible manager(s) in flight operations.
□ Examined selected training/qualification course curricula/syllabi (focus: identification/use of
authorized documents).
□ Observed flight simulator operations (focus: use of authorized documents in training/evaluation).
□ Other Actions (Specify)
Guidance
The intent of this provision is to ensure unauthorized training materials (e.g., handouts, training aids)
are not distributed to or used for the training or evaluation of flight crew members.
FLT 2.1.15–2.1.18 (Intentionally open)
Resources
FLT 2.1.19 The Operator shall ensure instructors, evaluators, line check airmen and flight crew
members (whether employed or contracted), training facilities, devices, equipment and course
materials (whether owned or contracted) are standardized and:
(i) As applicable, have the required certification(s) and approval or acceptance from the State;
(ii) As applicable, meet the required qualification and performance standards of the Operator or
the State;
(iii) Are periodically evaluated to ensure compliance with required qualification and performance
standards.
Auditor Actions
□ Identified/ Assessed standards for evaluation/certification/acceptance/approval of
human/physical resources/facilities for flight crew training/evaluation program.
□ Interviewed the responsible manager(s) in flight operations.
□ Examined selected records associated with training
personnel/facilities/devices/equipment/course materials (focus:
evaluation/certification/acceptance/approval in accordance with applicable standards).
□ Observed flight simulator operations (focus: Instructors/evaluators/facilities/devices meet
required standards).
□ Other Actions (Specify)
FLT 2.1.20 (Intentionally open)
FLT 2.1.21 The Operator shall have sufficient instructors, evaluators, line check airmen and
support personnel to administer the training and evaluation programs in accordance with
requirements of the Operator and/or the State, as applicable.
Auditor Actions
□ Identified/Assessed staffing requirements for instructor/evaluator/line check airman/support
personnel in flight crew training/evaluation program.
□ Interviewed the responsible manager(s) in flight operations.
□ Examined selected personnel staffing records (focus: staffing in accordance with required
levels).
□ Other Actions (Specify)
FLT 2.1.22–2.1.26 (Intentionally open)
Program Improvement
FLT 2.1.27 The Operator shall ensure formal and regular communication occurs between and
among flight operations management, instructors, evaluators, line check airmen and flight crew
members to achieve continual improvement of ground, simulator and aircraft training and line
operations. (GM)
Auditor Actions
□ Identified/Assessed requirements for communication among management/training
personnel/flight crew members for continual improvement in flight crew training/evaluation
program.
□ Interviewed the responsible manager(s) in flight operations.
□ Interviewed selected flight training personnel/flight crew members.
□ Examined selected communication media: (focus: communication for purpose of program
continual improvement).
□ Other Actions (Specify)
Guidance
The intent of this provision is for the operator to ensure a mandate exists, as well the means and
opportunity, for the conduct of regular communications between and among the operational
personnel for the purpose of achieving continual program improvement.
FLT 2.1.28 The Operator shall have processes for ensuring continual improvement of the flight
crew training and evaluation program, to include, as a minimum, the monitoring, recording and
evaluation of results of successful and unsuccessful flight crew evaluations. (GM)
Auditor Actions
□ Identified/Assessed processes for program monitoring, continual improvement of flight crew
training/evaluation program.
□ Interviewed the responsible manager(s) in flight operations.
□ Examined selected records of program monitoring (focus: improvements resulting from
monitoring).
□ Other Actions (Specify)
Guidance
Flight crew operational non-compliances, training deficiencies and evaluation trends (simulator,
aircraft and line operations) are typically used by the training organization for trend analysis and
program improvement.
Grading scale criteria (e.g. numerical, letter grade) provides a means to accurately identify areas for
improvement.
FLT 2.1.29–2.1.34 (Intentionally open)
Auditor Actions
□ Identified/Assessed requirement for initial training program for instructors/evaluators/line check
airmen in flight crew training/evaluation program.
□ Interviewed the responsible manager(s) in flight operations.
□ Examined selected initial training course curricula/syllabi for instructors/evaluators/line check
airmen (focus: specified elements are addressed in initial training for instructors/evaluators/line
check airmen).
□ Other Actions (Specify)
□ Observed flight simulator operations (focus: Instructor/evaluator demonstrates competence to
administer flight training).
Guidance
The specification in item iv) of this provision may be satisfied by an equivalent program that includes
line-oriented simulator sessions and/or completion of the company recurrent training program
administered to line pilots.
The specification in item i), sub-item g), is applicable to operators that conduct training flights.
The specification in item i), sub-item h), would typically require operators that conduct training flights
to specify the actual conditions that will permit such training to be accomplished safely and effectively
in accordance with FLT 2.1.12.
FLT 2.1.36 The Operator shall have a recurrent qualification program for instructors, evaluators,
and line check airmen that, as a minimum, requires participation in:
(i) Standardization meetings as defined by the Operator or the State;
(ii) Training or evaluation sessions (simulator or aircraft) conducted while supervised by an
individual approved by the Operator;
(iii) A State-approved or State-accepted minimum number of training events and/or evaluations
per 12-month period or required participation in a supplementary re-qualification/
recertification program if the minimum number of events are not completed;
(iv) A seat-specific (right or left seat, as applicable) recurrent program for instructors, evaluators,
Line Check Airmen, who perform duties from either pilot station;
(v) If non-line qualified instructors are utilized, a jump seat observation program or equivalent
approved or accepted by the State for non-line qualified instructors to provide familiarity with
current and type-related line operations. (GM)
Auditor Actions
□ Identified/Assessed requirement for recurrent training program for instructors/evaluators/line
check airmen in flight crew training/evaluation program.
□ Interviewed the responsible manager(s) in flight operations.
□ Interviewed selected instructors/evaluators/line check airmen.
□ Examined selected recurrent training course curricula/syllabi for instructors/evaluators/line
check airmen (focus: specified observations/events/seat-specific training are included in
recurrent training).
□ Examined selected instructor/evaluator/line check airman training/qualification records (focus:
completion of applicable formal observations/required events/seat-specific training).
□ Other Actions (Specify)
Guidance
The operator could have different recurrent qualification programs for line check airmen authorized to
conduct line flying under supervision and those who conduct simulator and/or aircraft evaluations.
Instructors, evaluators and line check airmen typically attend a standardization meeting at least once
within the preceding 12 months. Minutes of standardization meetings are normally distributed to
instructors, evaluators and line check airmen.
The observations required in conjunction with item ii) are typically conducted at least within the
preceding 12 months for each instructor, evaluator and line check airman, unless a longer interval is
approved or accepted by the Authority.
Simulator observations in conjunction with item ii) typically entail an assessment of the individual
while carrying out the duties for which highest qualified (e.g., instructor or evaluator).
If airline security does not permit line observations, the specification in item v) of this provision may
be satisfied by an equivalent program that includes line-oriented simulator sessions and/or
completion of the company recurrent training program administered to line pilots.
FLT 2.1.37–2.1.44 (Intentionally open)
The specification of this provision is satisfied if an operator provides guidance to instructors and
evaluators when critical components of a training device are fully or partially inoperative. For
example, simulator minimum serviceability requirements typically refer instructors or evaluators to
published company guidance to determine if a certain type of training (such as LOFT/LOS) can be
conducted with simulator components inoperative.
FLT 2.1.47 If the Operator has a zero flight time training (ZFTT) program, the Operator shall ensure
such training program is approved or accepted by the State and:
(i) Is conducted using flight simulators representative of the aircraft flown by the Operator and
qualified to Level C, D or an equivalent;
(ii) Specifies minimum pilot experience requirements for entry into each ZFTT
qualification/training course;
(iii) Each ZFTT qualification/training course is customized as necessary to address pilot
experience, flight crew position and simulator level;
(iv) A demonstration of competency is completed in a flight simulator conforming to the
specifications in item i) under the supervision of an evaluator;
(v) A final demonstration of competency is completed in an aircraft during actual line operations
under the supervision of an evaluator, instructor or current and qualified Pilot-in-Command
(PIC) designated for the purpose by the Operator and/or State. (GM)
Auditor Actions
□ Identified/Assessed program elements for ZFTT in flight crew training/evaluation program;
approval by State.
□ Interviewed responsible manager(s) in flight operations.
□ Examined selected flight crew member training/qualification records (focus: completion of
applicable ZFTT program elements).
□ Observed flight simulator operations (focus: simulators at level to support ZFTT).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definitions of Zero Flight Time Training (ZFTT), Instructor and Flight
Simulator. The latter definition includes descriptions of simulator qualification levels.
The intent of this provision is to define the elements of a ZFTT program, which may be used by an
Operator in conjunction with other training programs to qualify flight crew members (e.g. ZFTT could
be approved for a specific fleet type but not for all fleets).
The specification in item iv) refers to the demonstration of competencies that must be completed in a
qualified simulator as designated for completion during simulator training in an operator's State-
approved or State-accepted ZFTT qualification course.
The specification in item v) refers to the final demonstration of competencies that must be completed
in an aircraft as designated for completion during actual line operations in an operator's State-
approved or State-accepted ZFTT qualification course. Such final demonstration is typically tailored
to account for competencies previously demonstrated as part of simulator training in accordance with
item iv).
The combination of competencies demonstrated in a qualified simulator plus competencies
demonstrated in the aircraft during actual line operations encompasses all of the competencies,
designated for demonstration in an operator's State-approved or -accepted ZFTT qualification
course, as necessary for the release of a ZFTT candidate to unsupervised flying.
Guidance
The principal intent of the specifications of this provision is to ensure flight crew members have a
working knowledge of the emergency and safety equipment required to be on board an aircraft.
Training exercises typically address the operation of safety and emergency equipment carried on the
flight deck, emergency exits and slides, flotation devices (e.g. life rafts, life vests) and locating
equipment (e.g. ELT).
The extent to which training exercises must include the actual use or manipulation of such equipment
is typically determined by the operator in conjunction with requirements of the Authority. Additionally,
since the routine manipulation or use of certain required items may pose an occupational health
hazard, such training is typically accomplished using mock-ups or non-functioning replicas.
Training is applicable to all flight crew members.
Supernumeraries as specified in item ii) are those that are required for the safety of operations in
accordance with FLT 2.2.44.
FLT 2.1.1B addresses overall AQP/ATQP/EBT elements and specifications, as well as Authority
approval/acceptance requirements.
FLT 2.2.9 If the Operator conducts passenger flights with cabin crew, the Operator should ensure
flight crew members participate in joint training activities or exercises with cabin crew members for
the purpose of enhancing onboard coordination and mutual understanding of the human factors
involved in addressing emergency situations and security threats. Such training should be completed
during initial ground training and subsequently during recurrent training either once every 36 months
or, if applicable, in accordance with the continuing qualification schedule as defined in the Operator's
AQP/ATQP/EBT that conforms to the specifications of FLT 2.1.1B. (GM)
Auditor Actions
□ Identified/Assessed requirement for flight-cabin crew joint training activities/exercises in flight
crew training/evaluation program.
□ Identified/Assessed flight crew AQP/ATQP/EBT (if applicable): (focus continuing qualification
recurrent schedule for flight-cabin crew joint training activities/exercises).
□ Interviewed responsible manager(s) in flight operations.
□ Examined selected initial/recurrent training/qualification course curricula/syllabi (focus inclusion
of initial/recurrent flight-cabin crew joint training in activities/exercises as specified).
□ Examined selected flight crew member training/qualification records (focus: completion of flight-
cabin crew joint training activities/exercises).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Passenger Flight.
FLT 2.1.1B addresses overall AQP/ATQP/EBT elements and specifications, as well as Authority
approval/acceptance requirements.
The intent of this provision is that the specified training is delivered jointly to flight and cabin crew
members together in a common location. However, under certain specific conditions, conformity with
this provision may be accomplished through training delivered independently to flight and cabin crew
members under either of the following conditions:
• When approved by the Authority under an AQP, ATQP or EBT program, or
• When the flight crew training and cabin crew training occur at different geographical
locations.
When training is delivered independently under the above conditions, learning objectives are
normally determined jointly through interdepartmental coordination and subsequently incorporated
into the respective flight crew and cabin crew training curricula. It is possible that, although the
learning objectives are determined jointly, the development of curricula and administration of the
training occurs independently within each department.
FLT 2.2.10 The Operator shall ensure flight crew members receive training in all aspects of aircraft
performance during initial ground training. Such training shall include:
(i) Weight/mass and balance;
(ii) Takeoff, climb, cruise, approach and landing performance;
(iii) Obstacle clearance;
(iv) Fuel planning;
(v) Diversion planning;
(vi) Effect of inoperative or missing components (MEL/CDL);
(vii) If applicable, engine-out driftdown. (GM)
Auditor Actions
□ Identified/Assessed requirement for training in aircraft performance in flight crew
training/evaluation program.
□ Interviewed responsible manager(s) in flight operations.
□ Examined selected initial training/qualification course curricula/syllabi (focus: aircraft
performance training; definition of aspects/subjects addressed).
□ Examined selected flight crew member training/qualification records (focus: completion of initial
aircraft performance training).
□ Other Actions (Specify)
Guidance
Training is applicable to all flight crew members.
The specification in item vi) might not apply to ferry flights or maintenance flights.
The specification in item vii) is applicable when engine-out performance is operationally limiting.
FLT 2.2.11 The Operator shall ensure flight crew members complete training and an evaluation in
aircraft systems and limitations, to include a demonstration of competence in the operation of aircraft
systems. Such training and evaluation shall be completed during initial ground training and
subsequently during recurrent training either once every 36 months or, if applicable, in accordance
with the continuing qualification schedule as defined in the Operator's AQP/ATQP/EBT that conforms
to the specifications of FLT 2.1.1B. (GM)
Auditor Actions
□ Identified/Assessed requirement for training/evaluation in aircraft systems/limitations in flight
crew training/evaluation program.
□ Identified/Assessed flight crew AQP/ATQP/EBT (if applicable): (focus continuing qualification
recurrent schedule for training/evaluation in aircraft systems/limitations).
□ Interviewed responsible manager(s) in flight operations.
□ Examined selected initial/recurrent training/qualification course curricula/syllabi (focus:
training/evaluation in aircraft systems limitations/operation).
□ Examined selected flight crew member training/qualification records (focus: completion of
training/evaluation in aircraft systems limitations/operation).
□ Observed flight simulator operations (focus: training/evaluation in flight crew operation of aircraft
systems/limitations).
□ Other Actions (Specify)
Guidance
Training and evaluation is applicable to all flight crew members.
FLT 2.1.1B addresses overall AQP/ATQP/EBT elements and specifications, as well as Authority
approval/acceptance requirements.
FLT 2.2.12 If the Operator transports dangerous goods as cargo, the Operator shall ensure flight
crew members complete training and an evaluation in dangerous goods during initial ground training
and subsequently once during recurrent training either within the 24-month period from the previous
training in dangerous goods or, if applicable, in accordance with the continuing qualification schedule
as defined in the Operator's AQP/ATQP/EBT that conforms to the specifications of FLT 2.1.1B. Such
training shall include:
(i) General philosophy;
(ii) Limitations;
(iii) List of dangerous goods;
(iv) Labeling and marking;
(v) Recognition of undeclared dangerous goods;
(vi) Storage and loading procedures;
(vii) Pilot's notification;
(viii) Provisions for passengers and crew;
(ix) Emergency procedures. (GM)
Auditor Actions
□ Identified/Assessed requirement for training/evaluation in dangerous goods in flight crew
training/evaluation program.
□ Identified/Assessed flight crew AQP/ATQP/EBT (if applicable): (focus continuing qualification
recurrent schedule for training/evaluation in dangerous goods).
□ Interviewed responsible manager(s) in flight operations.
□ Examined selected initial/recurrent training/qualification course curricula/syllabi (focus:
dangerous goods training/evaluation; definition of specific aspects/subjects addressed).
□ Examined selected flight crew member training/qualification records (focus: completion of
training/evaluation in dangerous goods in initial/recurrent training).
□ Other Actions (Specify)
Guidance
Training and evaluation is applicable to all flight crew members.
Recurrent training in dangerous goods is typically completed within a validity period that expires
24 months from the previous training to ensure knowledge is current, unless a shorter period is
defined by a competent authority. However, when such recurrent training is completed within the final
3 months of the 24-month validity period, the new validity period may extend from the month on
which the recurrent training was completed until 24 months from the expiry month of the current
validity period. If such recurrent training is completed prior to the final three months (or 90 days) of
the validity period, the new validity period would extend 24 months from the month the recurrent
training was completed.
FLT 2.1.1B addresses overall AQP/ATQP/EBT elements and specifications, as well as Authority
approval/acceptance requirements.
Guidance may be found in the IATA Dangerous Goods Regulations (DGR) 1.5, Table 1.5.A.
FLT 2.2.13 If the Operator does not transport dangerous goods as cargo, the Operator shall
ensure flight crew members complete training and an evaluation in dangerous goods during initial
ground training and subsequently once during recurrent training either within the 24-month period
from the previous training in dangerous goods or, if applicable, in accordance with the continuing
qualification schedule as defined in the Operator's AQP/ATQP/EBT that conforms to the
specifications of FLT 2.1.1B. Such training shall include:
(i) General philosophy;
(ii) Limitations;
(iii) Labeling and marking;
(iv) Recognition of undeclared dangerous goods;
Guidance
Refer to the IRM for the definitions of CRM, Facilitator, Human Performance, Human Factors
Principles and Threat and Error Management.
CRM training is applicable to all flight crew members.
FLT 2.1.1B addresses overall AQP/ATQP elements and specifications, as well as Authority
approval/acceptance requirement.
FLT 2.2.15 If the Operator utilizes FOO personnel and the Operator's method of Operational
Control requires shared responsibility between an FOO and the PIC, the Operator should ensure
flight crew members complete resource management training that addresses issues of mutual
concern to flight crew members and FOO personnel. Such training should be conducted for the
purposes of enhancing coordination, ensuring a mutual understanding of the human factors involved
in joint operational control and achieving common learning objectives as set out by the appropriate
flight operations and operational control management personnel. (GM)
Auditor Actions
□ Identified/Assessed requirement for resource management training that addresses issues of
mutual concern to flight crew/FOO personnel.
□ Interviewed responsible manager(s) in flight operations.
□ Examined flight crew/FOO training curriculum/syllabus (focus: inclusion of subjects that address
coordination/human factors involved in joint operational control).
□ Examined selected flight crew member training/qualification records (focus: completion of
resource management training for flight crew/FOO personnel).
□ Other Actions (Specify)
Guidance
The intent of this provision is to ensure that resource management issues of mutual concern to both
FOO personnel and flight crew members are addressed for the purposes of enhancing coordination
and to foster a mutual understanding of the human and other factors involved in joint operational
control.
Such training is typically accomplished using common learning objectives determined during
interdepartmental coordination meetings, which are subsequently incorporated into the respective
training curricula. Although the learning objectives are determined jointly, it is possible that the
development of curricula and administration of the training occurs independently within each
department.
The training specified in this provision does not require the physical presence of flight crew members
and FOO personnel at a common training location.
FLT 2.1.1B addresses overall AQP/ATQP/EBT elements and specifications, as well as Authority
approval/acceptance requirements.
FLT 2.2.16A The Operator shall ensure flight crew members complete training and an evaluation in
subjects associated with adverse weather and/or environmental conditions during initial ground
training and subsequently during recurrent training either once every 36 months or, if applicable, in
accordance with the continuing qualification schedule as defined in the Operator's AQP/ATQP/EBT
that conforms to the specifications of FLT 2.1.1B. Such training and evaluation shall address, as
applicable:
(i) Cold weather operations, to include de-/anti-icing policies and procedures;
(ii) Contaminated runway operations;
(iii) Thunderstorm avoidance. (GM)
Auditor Actions
□ Identified/Assessed requirement for training/evaluation in adverse weather/environmental
conditions in flight crew training/evaluation program.
□ Identified/Assessed flight crew AQP/ATQP/EBT (if applicable): (focus continuing qualification
recurrent schedule for training/evaluation in adverse weather/environmental conditions).
□ Interviewed responsible manager(s) in flight operations.
□ Examined selected initial/recurrent training/qualification course curricula/syllabi (focus:
training/evaluation in adverse weather/environmental conditions; definition of aspects/subjects
addressed).
□ Examined selected flight crew member training/qualification records (focus: completion of
training/evaluation in adverse weather/environmental conditions in initial/recurrent training).
□ Observed flight simulator operations (focus: training/evaluation in operations in adverse
weather/environmental conditions).
□ Other Actions (Specify)
Guidance
Training and evaluation is applicable to all flight crew members.
The intent of this provision is to ensure flight crew members receive recurrent training and an
evaluation in the subjects associated with the adverse weather or environmental conditions they may
encounter in operations.
FLT 2.1.1B addresses overall AQP/ATQP/EBT elements and specifications, as well as Authority
approval/acceptance requirements.
FLT 2.2.16B If the Operator conducts operations on routes that traverse active volcanic areas or in
the terminal areas of airports in the vicinity of active volcanoes, the Operator shall ensure flight crew
members complete training and an evaluation in such operations during initial ground training and, if
applicable, in accordance with the continuing qualification schedule as defined in the Operator's
AQP/ATQP/EBT that conforms to the specifications of FLT 2.1.1B. (GM)
Auditor Actions
□ Identified/Assessed requirement for training/evaluation in operations associated with potential
volcanic ash in flight crew training/evaluation program.
□ Identified/Assessed flight crew AQP/ATQP/EBT (if applicable): (focus continuing qualification
recurrent schedule for training/evaluation in operations associated with potential for volcanic
ash).
□ Interviewed responsible manager(s) in flight operations.
□ Examined selected initial/recurrent training/qualification course curricula/syllabi (focus: training
in operations associated with potential for volcanic ash).
□ Examined selected flight crew member training/qualification records (focus: completion of
training/evaluation in operations associated with potential for volcanic ash in initial/recurrent
training).
□ Other Actions (Specify)
Guidance
Training and evaluation is applicable to all flight crew members.
The intent of this provision is to ensure flight crew members receive training and an evaluation in the
subjects associated with the adverse environmental conditions they might encounter in operations, to
include the consequences of an inadvertent entry into a volcanic ash cloud or unanticipated volcanic
eruptions along the route of flight. Such training and evaluation is designed to increase flight crew
awareness and vigilance related to volcanic activity and emphasize the possibility that they may be
the first to observe an eruption or be required to pass information related to a new eruption to the
appropriate authorities for dissemination.
Additional information related to the risk management of flight operations with known or forecast
volcanic ash contamination is contained in ICAO Doc 9974, Flight Safety and Volcanic Ash, First
Edition 2012.
FLT 2.1.1B addresses overall AQP/ATQP/EBT elements and specifications, as well as Authority
approval/acceptance requirements.
FLT 2.2.17 The Operator shall ensure flight crew members complete upset prevention and
recovery training (UPRT) during initial ground training and subsequently during recurrent training
either once every 36 months or, if applicable, in accordance with the continuing qualification
schedule as defined in the Operator's AQP/ATQP/EBT that conforms to the specifications of
FLT 2.1.1B. (GM)
Auditor Actions
□ Identified/Assessed requirement for training in procedures for aircraft upset recovery in flight
crew training/evaluation program.
□ Identified/Assessed flight crew AQP/ATQP/EBT (if applicable): (focus continuing qualification
recurrent schedule for training in procedures for aircraft upset recovery).
□ Interviewed responsible manager(s) in flight operations.
□ Examined selected initial/recurrent training/qualification course curricula/syllabi (focus: training
in procedures for aircraft upset recovery).
□ Examined selected flight crew member training/qualification records (focus: completion of upset
recovery training/evaluation in initial/recurrent training).
□ Observed flight simulator operations (focus: training in upset recovery).
□ Other Actions (Specify)
Guidance
Training is applicable to all pilot crew members and typically addresses pilot flying (PF) and pilot
monitoring (PM) duties.
Aircraft upset recovery training typically includes:
• Upset prevention;
• Factors leading to an upset or loss of control situation;
• Upset situation identification;
• Recovery techniques;
• Emphasis on aerodynamic factors present during the upset and the recovery.
Acceptable means of ground training may include video presentation(s), verbal instruction and/or
group discussion.
FLT 2.1.1B addresses overall AQP/ATQP/EBT elements and specifications, as well as Authority
approval/acceptance requirements.
FLT 2.2.18 If the Operator is authorized to conduct RVSM operations and/or operations in airspace
that requires the maintenance of a particular RNP, the Operator shall ensure flight crew members
complete training and an evaluation in RVSM and/or RNP procedures during initial ground training
and, if applicable, in accordance with the continuing qualification schedule as defined in the
Operator's AQP/ATQP/EBT that conforms to the specifications of FLT 2.1.1B. (GM)
Auditor Actions
□ Identified/Assessed requirement for training in RVSM/RNP procedures in flight crew
training/evaluation program.
□ Identified/Assessed flight crew AQP/ATQP/EBT (if applicable): (focus continuing qualification
recurrent schedule for training in RVSM/RNP).
□ Interviewed responsible manager(s) in flight operations.
□ Examined selected initial/recurrent training/qualification course curricula/syllabi (focus: training
in RVSM/RNP procedures).
□ Observed line flight operations (focus: English language proficiency in communication with
ATC).
□ Other Actions (Specify)
Guidance
The intent of this provision is to ensure a pilot who is required to communicate with air traffic control
in English demonstrates a sufficient level of English language proficiency to ensure effective
communication during the performance of duties.
Such evaluation applies to each operating member of the flight crew, as required by the AFM, whose
duties require communication in English with ATC.
English proficiency requirements do not apply to flight engineers or flight navigators unless their
duties include air/ground communication in English.
A State requirement, as part of flight crew licensing, for an individual to demonstrate expert English
language proficiency may be used to satisfy the specifications of this provision.
FLT 2.2.21 (Intentionally open)
FLT 2.2.22 The Operator shall have a process to ensure flight crew members who conduct flights
into areas where English is required for Air Traffic Control (ATC) communications, and who have not
previously demonstrated expert English language proficiency, receive a periodic evaluation to
demonstrate a minimum level of English language proficiency that is sufficient, as defined by the
Operator and/or the State, to ensure effective communication during the performance of duties. Such
evaluation shall be completed during initial ground training and subsequently once every three (3) to
six (6) years based on the proficiency level of the applicant. (GM)
Auditor Actions
□ Identified/Assessed requirement for English language evaluation for flight crew members that
have not previously demonstrated expert English language proficiency and operate
flights/communicate with ATC in areas where the primary language of ATC is English.
□ Interviewed responsible manager(s) in flight operations.
□ Examined initial training/continuing qualification course curriculum/syllabus (focus:
demonstration of English language proficiency necessary for effective ATC communications,
periodic demonstration every 3-6 years based on demonstrated proficiency level).
□ Examined selected flight crew member training/qualification records (focus: completion of
initial/periodic demonstration of English language proficiency).
□ Other Actions (Specify)
Guidance
The intent of this provision is to ensure a pilot who is required to communicate with air traffic control
in English, periodically demonstrates a sufficient level of English language proficiency to ensure
effective communication during the performance of duties.
Such evaluation applies to each operating pilot member of the flight crew, as required by the AFM.
English proficiency requirements do not apply to flight engineers or flight navigators unless their
duties include air/ground communication.
Periodic demonstration of language proficiency is not required of individuals who have previously
demonstrated an expert level of English language proficiency. Such individuals are those whose
native language is English and those whose native language is not English, but who understand
English and speak English that is easily understood, even if spoken with a dialect or accent.
A State requirement, as part of flight crew licensing, for an individual to demonstrate expert English
language proficiency can be used to satisfy the specifications of this provision.
In order to conform to these specifications, an operator may periodically evaluate Individuals that
have not previously demonstrated expert English language proficiency in accordance with either:
• ICAO Annex 1.2.9.6, 1.2.9.7 and ICAO Annex 1, Attachment 1.1 (ICAO Language
Proficiency Rating Scale), or
Auditor Actions
□ Identified/Assessed requirement for training in normal/non-normal procedures/maneuvers in
flight crew training/evaluation program.
□ Identified/Assessed in flight crew AQP/ATQP/EBT (if applicable): (focus continuing qualification
recurrent schedule for training in normal/non-normal procedures/maneuvers).
□ Interviewed responsible manager(s) in flight operations.
□ Examined selected initial/recurrent training/qualification course curricula/syllabi (focus: training
in normal/non-normal procedures/maneuvers; definition of specific elements/subjects
addressed).
□ Examined selected flight crew member training/qualification records (focus: completion of
initial/recurrent training in the specified normal/non-normal procedures/maneuvers).
□ Observed flight simulator operations (focus: training in normal/non-normal
procedure/maneuvers).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definitions of Pilot Flying (PF) and Pilot Monitoring (PM).
Training is applicable to all flight crew members.
The intent of this provision is to set a training interval for normal and non-normal procedures, and
additionally to ensure the training manual, curricula, lesson plans, or other guidance associated with
such training addresses the specifications in items i) through v).
Division of flight crew duties, transfer of aircraft control, checklist use and prioritization of tasks are in
accordance with the operator's policy for task sharing and as specified in FLT 3.11.18.
Proper use of automation levels is in accordance with the operator's automation policy and as
specified in FLT 3.11.22.
FLT 2.1.1B addresses overall AQP/ATQP/EBT elements and specifications, as well as Authority
approval/acceptance requirements.
Elements of training may be accomplished as part of ground, simulator, aircraft or line training.
The term Pilot Monitoring (PM) has the same meaning as the term Pilot Not Flying (PNF) for the
purpose of applying the specifications of this provision.
The specification in item iv) refers to the following prioritization of tasks during any normal or
abnormal situation or maneuver:
• Aviate: fly the aircraft in accordance with restrictions and limitations set forth in the OM;
• Navigate: guide the aircraft along the intended or appropriate route;
• Communicate: verbalize intentions to other crew members and ATC, as applicable.
The term “abnormal” is used to describe a condition or situation (e.g. abnormal airframe vibration,
abnormal landing configuration).
The terms “normal” and “non-normal/emergency” typically refer to AOM checklists, procedures
and/or maneuvers. The term “non-normal” includes AOM emergency checklists and/or procedures
(i.e. an emergency procedure is a subset of non-normal).
The terms can also be used to describe an event, situation or operation that would be addressed by
normal or non-normal/emergency procedures or checklists. When used in this manner, the terms
may be separated by forward slash marks (e.g. normal/non-normal/emergency).
The term “emergency” used alone refers to declarations and non-AOM procedures.
FLT 2.2.27 The Operator shall ensure flight crew members complete training and, when
applicable, an evaluation, that includes a demonstration of competence in normal and non-normal
procedures and maneuvers, to include, as a minimum, rejected takeoff, emergency evacuation,
engine failure and/or those procedures and maneuvers specified in the Operator's AQP/ATQP/EBT
as approved or accepted by the Authority. Such training and, when applicable, evaluation shall be
accomplished either:
(i) During initial training and subsequently during recurrent training once every 12 months, or
(ii) If applicable, in accordance with an AQP, an ATQP or EBT approved by the Authority that
requires evaluations to be satisfactorily completed within the maximum evaluation period
delineated in, as applicable, Table 2.7 or Table 2.8, and includes a demonstration of
competence in normal and non-normal procedures and maneuvers. (GM)
Auditor Actions
□ Identified/Assessed requirement for training/evaluation including a demonstration of
competence in normal/non-normal procedures/maneuvers in flight crew training/evaluation
program.
□ Identified/Assessed flight crew AQP/ATQP/EBT (if applicable): (focus continuing qualification
recurrent schedule for training/evaluation in normal/non-normal procedures/maneuvers).
□ Interviewed responsible manager(s) in flight operations.
□ Examined selected initial/recurrent training/qualification course curricula/syllabi (focus:
training/evaluation in specified normal/non-normal procedures/maneuvers).
□ Examined selected flight crew member training/qualification records (focus: completion of
initial/recurrent training/evaluation in the specified normal/non-normal procedures/maneuvers).
□ Observed flight simulator operations (focus: training/evaluation in performance of normal/non-
normal procedures/maneuvers).
□ Other Actions (Specify)
Guidance
The intent of this provision is to define the basic initial and subsequent recurrent training and
evaluation cycles that ensure flight crew members are competent to perform normal and non-normal
procedures and maneuvers. It is understood that competence in all potential normal and non-normal
procedures may not be demonstrated annually but in accordance with a schedule that is acceptable
to the Authority.
The modification of qualification intervals in accordance with an AQP, ATQP or EBT program
requires conformity with FLT 2.1.1B.
Training and, when applicable, a demonstration of competence in specified normal and non-normal
procedures and maneuvers is applicable to all pilot crew members.
Training and, when applicable, evaluation is accomplished as part of ground, simulator/aircraft and
line training;
Line training is in normal procedures/maneuvers only.
An evaluation of competence in the normal and non-normal procedures and maneuvers specified is
applicable when such procedures and/or maneuvers are stipulated by the operator and/or State in
conjunction with State-approved or State-accepted training courses that require a method of
evaluation. Such courses typically include:
• Type qualification;
• Transition (conversion);
• Upgrade to PIC;
• Re-qualification;
• Recurrent training.
Operators that conduct training flights and cannot safely train/evaluate a non-normal procedure or
maneuver in an aircraft or in a representative flight simulator as specified in FLT 2.2.38 may
demonstrate an alternative means of conformance in accordance with FLT 2.2.41.
All pilot flight crew members who receive training in the normal and non-normal procedures and
maneuvers specified in this provision also demonstrate competence in such procedures and
maneuvers in accordance with the applicable specifications of FLT 2.3.2.
FLT 2.2.28 The Operator shall ensure flight crew members, prior to an evaluation, are familiar with
those maneuvers and/or malfunctions that might be presented during the evaluation, but are not
given information that reveals the exact sequence and the circumstances under which such
maneuvers or malfunctions will be presented. (GM)
Auditor Actions
□ Identified/Assessed philosophy/requirements for preparing flight crew members for an
evaluation in flight crew training/evaluation program.
□ Interviewed responsible manager(s) in flight operations.
□ Examined guidance for instructors/evaluators (focus: methodology for providing information to
flight crew members in preparation for an evaluation).
□ Observed flight simulator operations (focus: information provided to flight crew members in
preparation for an evaluation).
□ Other Actions (Specify)
Guidance
The specification of this provision is not intended to preclude flight crews from knowing the city pairs
to be flown or the general maneuver requirements prior to the evaluation; however, flight crews would
typically not be provided with the exact evaluation scenario.
Operators that conduct training flights in an aircraft may divulge as much information about the
intended training/evaluation as is necessary to ensure the safety of the planned operation.
FLT 2.2.29 The Operator shall ensure flight crew members, before starting line training, have
successfully completed an Operator proficiency evaluation administered by an Evaluator of the
Operator or a representative of the Authority, and have demonstrated the skill and knowledge level
adequate for operating the aircraft at or above the standards stipulated in the training syllabus. (GM)
Auditor Actions
□ Identified/Assessed requirement for a final evaluation prior to a flight crew member
commencing line flight training.
□ Interviewed responsible manager(s) in flight operations.
□ Examined syllabus for final evaluations of flight crew members prior to line flight training (focus:
demonstration of skill/knowledge adequate to operate the aircraft at or above the standards
stipulated in the training syllabus; definition of evaluation criteria).
□ Examined selected flight crew member training/qualification records (focus: successful
completion of final evaluation conducted by an evaluator prior to commencing line flight training).
□ Other Actions (Specify)
Guidance
An evaluation in conjunction with Initial Type Qualification satisfies the specifications in this provision.
FLT 2.2.30 The Operator shall ensure flight crew members complete training in CRM skills, which
may be accomplished as part of simulator, aircraft and/or line training, as applicable. Such training
shall be completed during initial training and subsequently during recurrent training either once every
12 months or, if applicable, in accordance with the continuing qualification schedule as defined in the
Operator's AQP/ATQP/EBT that conforms to the specifications of FLT 2.1.1B. (GM)
Auditor Actions
□ Identified/Assessed requirements for training in CRM skills in flight crew training/evaluation
program.
□ Identified/Assessed flight crew AQP/ATQP/EBT (if applicable): (focus continuing qualification
recurrent schedule for CRM training).
□ Interviewed responsible manager(s) in flight operations.
□ Examined selected initial/recurrent training/qualification course curricula/syllabi (focus: inclusion
of CRM training in simulator/aircraft or during line flight training).
□ Examined selected flight crew member training/qualification records (focus: completion of
initial/recurrent CRM training).
□ Observed line flight and flight simulator operations (focus: training in application of CRM/TEM
principles/skills).
□ Other Actions (Specify)
Guidance
Training is applicable to all flight crew members.
FLT 2.1.1B addresses overall AQP/ATQP/EBT elements and specifications, as well as Authority
approval/acceptance requirements.
This specification is intended to ensure CRM skills are emphasized during and integrated into
simulator or aircraft training, as applicable, and line training.
FLT 2.2.31 The Operator shall ensure flight crew members complete a Line Operational Simulation
(LOS) profile during initial simulator or aircraft training, and subsequently during recurrent training
either once every 12 months or, if applicable, in accordance with the continuing qualification
schedule as defined in the Operator's AQP/ATQP/EBT that conforms to the specifications of FLT
2.1.1B. Such training shall be:
(i) Approved or accepted by the State;
(ii) Administered real-time in a line environment setting;
(iii) An uninterrupted planned scenario with specific CRM objectives where such skills are
observed and debriefed upon completion. (GM)
Auditor Actions
□ Identified/Assessed requirement for approved LOS in flight crew training/evaluation program.
□ Identified/Assessed flight crew AQP/ATQP/EBT (if applicable): (focus continuing qualification
recurrent schedule for LOS).
□ Interviewed responsible manager(s) in flight operations.
□ Examined criteria for administration of LOS (focus: conducted as uninterrupted scenario in real-
time line environment with planned CRM objectives, CRM skills observed/briefed at completion).
□ Examined selected initial/recurrent training/qualification course curricula/syllabi (focus: inclusion
of LOS in simulator/aircraft or during line flight training).
□ Examined selected flight crew member training/qualification records (focus: completion of LOS
in initial/recurrent training).
□ Observed flight simulator operations (focus: training using LOS profile).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Line Operational Simulation (LOS).
Training and/or evaluation is applicable to flight crew members.
FLT 2.1.1B addresses overall AQP/ATQP/EBT elements and specifications, as well as Authority
approval/acceptance requirements.
SPOT, LOE, and/or LOFT scenarios incorporated into the training program satisfy the specifications
of this provision.
LOS scenarios are as standardized and scripted as possible. A simple menu of expected weather
conditions and/or normal/non-normal procedures/maneuvers would not be acceptable as this would
increase the subjectivity of the presentation.
In the absence of a representative flight simulator, such alternatives typically employ:
• LOS profiles conducted in a generic simulation device or representative flight training device;
• An uninterrupted planned scenario in the aircraft with specific CRM objectives that include
behavioral observation and assessment of crew performance, where such skills are
observed and debriefed upon completion. This requires an operator to specify how the CRM
objectives are set, evaluated and debriefed in a line environment.
The term “abnormal” is used to describe a condition or situation (e.g. abnormal airframe vibration,
abnormal landing configuration).
The terms “normal” and “non-normal/emergency” typically refer to AOM checklists, procedures
and/or maneuvers. The term “non-normal” includes AOM emergency checklists and/or procedures
(i.e. an emergency procedure is a subset of non-normal).
The terms can also be used to describe an event, situation or operation that would be addressed by
normal or non-normal/emergency procedures or checklists. When used in this manner, the terms
may be separated by forward slash marks (e.g. normal/non-normal/emergency).
The term “emergency” used alone refers to declarations and non-AOM procedures.
FLT 2.2.32 The Operator shall ensure flight crew members complete training and, when
applicable, an evaluation, that includes a demonstration of competence, in windshear avoidance and
recovery from predictive and actual windshear. Such training shall be completed during initial ground
and simulator training, and subsequently during recurrent simulator training either once every
36 months or, if applicable, in accordance with the continuing qualification schedule as defined in the
Operator's AQP/ATQP/EBT that conforms to the specifications of FLT 2.1.1B. (GM)
Auditor Actions
□ Identified/Assessed requirement for training/evaluation/demonstration of competence in
windshear avoidance/recovery from predictive/actual windshear in flight crew training/evaluation
program.
□ Identified/Assessed flight crew AQP/ATQP/EBT (if applicable): (focus continuing qualification
recurrent schedule for windshear training/evaluation).
□ Interviewed responsible manager(s) in flight operations.
□ Examined selected initial/recurrent training/qualification course curricula/syllabi (focus:
windshear training/evaluation/demonstration of competence).
□ Examined selected flight crew member training/qualification records (focus: completion of
initial/recurrent windshear training/evaluation.
□ Observed flight simulator operations (focus: training/evaluation in windshear avoidance/recovery
from predictive/actual windshear).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Windshear.
The intent of this provision is to ensure training and evaluation occurs, as applicable, in the
maneuvers specified within the intervals specified. Such training and evaluation can occur in
conjunction with any State-approved or State-accepted training course.
FLT 2.1.1B addresses overall AQP/ATQP/EBT elements and specifications, as well as Authority
approval/acceptance requirements.
Training and, when applicable, an evaluation in the specified normal and non-normal procedures and
maneuvers is applicable to all pilot crew members.
Training is accomplished in a representative flight simulator approved for the purpose by the State.
Such evaluation of competence in the normal and non-normal procedures and maneuvers specified
is applicable when such procedures and/or maneuvers are stipulated by the operator and/or State in
conjunction with State-approved or State-accepted training courses that require a method of
evaluation. Such courses typically include:
• Type qualification;
• Transition (conversion);
• Upgrade to PIC;
• Re-qualification;
• Recurrent training.
Training and evaluation of the non-normal procedures and maneuvers specified in this provision
cannot be safely accomplished in an aircraft on a training flight (see FLT 2.2.38).
Operators that cannot conform to the specifications of this provision due to the non-existence of a
representative flight simulator may demonstrate an alternative means of conforming to these
specifications in accordance with FLT 2.2.41.
The additional ground and line training and evaluation used to satisfy the specifications of this
provision and of FLT 2.2.41 in the absence of a representative flight simulator typically include a
review of:
• Conditions conducive to windshear;
• Effects on aircraft performance;
• Indications of windshear presence;
• Avoidance and recovery techniques;
• Windshear case studies or scenarios.
FLT 2.2.33 The Operator shall ensure flight crew members complete training and an evaluation,
which includes a demonstration of competence in terrain awareness procedures and maneuvers.
Such training shall be completed during initial ground and simulator training and subsequently during
recurrent simulator training either once every 36 months or, if applicable, in accordance with the
continuing qualification schedule as defined in the Operator's AQP/ATQP/EBT that conforms to the
specifications of FLT 2.1.1B. Such training and evaluation shall include:
(i) Knowledge and conduct of associated procedures;
(ii) Response to GPWS alerts and warnings;
(iii) The avoidance of Controlled Flight Into Terrain (CFIT). (GM)
Auditor Actions
□ Identified/Assessed requirement for training/evaluation/demonstration of competence in terrain
awareness procedures/maneuvers in flight crew training/evaluation program.
□ Identified/Assessed flight crew AQP/ATQP/EBT (if applicable): (focus continuing qualification
recurrent schedule for training/evaluation in terrain awareness procedures/maneuvers).
□ Interviewed responsible manager(s) in flight operations.
□ Examined selected initial/recurrent training/qualification course curricula/syllabi (focus:
training/evaluation in terrain awareness procedures/maneuvers; definition of subjects
addressed).
□ Examined selected flight crew member training/qualification records (focus: completion of
initial/recurrent training/evaluation in terrain awareness procedures/maneuvers.
□ Observed line flight and flight simulator operations (focus: terrain awareness
procedures/maneuvers).
□ Other Actions (Specify)
Guidance
The intent of this provision is to ensure training and evaluation occurs, as applicable, in the
maneuvers specified within the intervals specified. Such training and evaluation can occur in
conjunction with any State-approved or State-accepted training course.
FLT 2.1.1B addresses overall AQP/ATQP/EBT elements and specifications, as well as Authority
approval/acceptance requirements.
Training and evaluation in the specified normal and non-normal procedures and maneuvers in a
representative flight simulator approved for the purpose by the State is applicable to pilot crew
members.
Training and evaluation of the non-normal procedures and maneuvers specified in this provision
cannot be safely accomplished in an aircraft on a training flight (see FLT 2.2.38).
Operators that cannot conform to the specifications of this provision due to the non-existence of a
representative flight simulator may demonstrate an alternative means of conforming to these
specifications in accordance with FLT 2.2.41.
The additional ground and line training and evaluation used to satisfy the specifications of this
provision and of FLT 2.2.41 in the absence of a representative flight simulator typically includes a
review of:
• CFIT avoidance techniques;
• CFIT recovery techniques and maximizing aircraft performance;
• GPWS alerts and warnings;
• CFIT case studies or scenarios.
FLT 2.2.34 If the Operator conducts low visibility operations (LVO), the Operator shall ensure flight
crew members complete training and an evaluation that includes a demonstration of competence in
such operations, as well as operations with inoperative ground based and/or aircraft equipment.
Such training shall be completed during initial ground and simulator training and subsequently during
recurrent simulator training either once every 12 months or, if applicable, in accordance with the
continuing qualification schedule as defined in the Operator's AQP/ATQP/EBT that conforms to the
specifications of FLT 2.1.1B. (GM)
Auditor Actions
□ Identified/Assessed requirement for training/evaluation/demonstration of competence in LVO
and/or operations with inoperative ground based/aircraft equipment in flight crew
training/evaluation program.
□ Identified/Assessed flight crew AQP/ATQP/EBT (if applicable): (focus continuing qualification
recurrent schedule for training/evaluation in LVO and/or operations with inoperative ground
based/aircraft equipment).
□ Interviewed responsible manager(s) in flight operations.
□ Examined selected initial/recurrent training/qualification course curricula/syllabi (focus:
training/evaluation in LVO and/or operations with inoperative ground based/aircraft equipment).
□ Examined selected flight crew member training/qualification records (focus: completion of
initial/recurrent training/evaluation in LVO and/or operations with inoperative ground
based/aircraft equipment.
□ Observed flight simulator operations (focus: training in LVO).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Low Visibility Operations (LVO).
FLT 2.1.1B addresses overall AQP/ATQP/EBT elements and specifications, as well as Authority
approval/acceptance requirements.
Training and evaluation in low visibility operations is applicable to all pilot crew members.
For the purposes of this provision, low visibility operations are considered in effect when the Runway
Visual Range (RVR) is below 400 m for takeoff and/or below Category I limits for landing.
Operators that conduct training flights and cannot safely train/evaluate the specified procedures in an
aircraft or in a representative flight simulator as specified in FLT 2.2.38 may demonstrate an
alternative means of conformance in accordance with FLT 2.2.41.
FLT 2.2.35 The Operator shall ensure flight crew members with duties and responsibilities related
to TCAS/ACAS alerting equipment complete training and an evaluation that includes a demonstration
of competence in maneuvers and procedures for the proper response to TCAS/ACAS alerts. Such
training and evaluation shall be completed during initial ground and simulator training and
subsequently during recurrent simulator training either once every 36 months or, if applicable, in
accordance with the continuing qualification schedule as defined in the Operator's AQP/ATQP/EBT
that conforms to the specifications of FLT 2.1.1B. (GM)
Auditor Actions
□ Identified/Assessed requirement for training/evaluation/demonstration of competence in
procedures for proper response to TCAS/ACAS alerts in flight crew training/evaluation program.
□ Identified/flight crew AQP/ATQP/EBT (if applicable): (focus continuing qualification recurrent
schedule for training/evaluation in response to TCAS/ACAS alerts).
□ Interviewed responsible manager(s) in flight operations.
□ Examined selected initial/recurrent training/qualification course curricula/syllabi (focus:
training/evaluation in procedures for proper response to TCAS/ACAS alerts).
□ Examined selected flight crew member training/qualification records (focus: completion of
initial/recurrent training/evaluation in procedures for proper response to TCAS/ACAS alerts).
□ Observed flight simulator operations (focus: training/evaluation in response to TCAS/ACAS
alerts).
□ Other Actions (Specify)
Guidance
The intent of this provision is to ensure training and evaluation occurs, as applicable, in the
maneuvers specified within the intervals specified. Such training and evaluation can occur in
conjunction with any State-approved or State-accepted training course.
FLT 2.1.1B addresses overall AQP/ATQP/EBT elements and specifications, as well as Authority
approval/acceptance requirements.
Training is accomplished in a representative flight simulator approved for the purpose by the State.
TCAS training may be performed without demonstrating capability in a simulator (since many
simulators do not have TCAS capability).
Training and evaluation of the non-normal procedures and maneuvers specified in this provision
cannot be safely accomplished in an aircraft on a training flight (see FLT 2.2.38).
Operators that cannot conform to the specifications of this provision due to the non-existence of a
representative flight simulator may demonstrate an alternative means of conforming to these
specifications in accordance with FLT 2.2.41.
The additional ground and line training and evaluation used to satisfy the specifications of this
provision and of FLT 2.2.41 in the absence of a representative flight simulator typically include a
review of:
• TCAS procedures and alert responses;
• TCAS alerts;
• TCAS case studies or scenarios.
FLT 2.2.36 (Intentionally open)
FLT 2.2.37 If the Operator utilizes pilot flight crew members designated to perform duties from
either control seat, the Operator shall have seat-specific qualification for such flight crew members, to
include training and an evaluation. Such training and evaluation shall be completed during initial
ground and simulator training and subsequently during recurrent simulator training either once every
12 months or, if applicable, in accordance with the continuing qualification schedule as defined in the
Operator's AQP/ATQP/EBT that conforms to the specifications of FLT 2.1.1B. (GM)
Auditor Actions
□ Identified/Assessed requirement for seat-specific qualification of pilot flight crew members
designated to perform duties from either control seat.
□ Identified/Assessed flight crew AQP/ATQP/EBT (if applicable): (focus continuing qualification
recurrent schedule for seat-specific qualification).
□ Interviewed responsible manager(s) in flight operations.
□ Examined selected initial/recurrent training/qualification course curricula/syllabi (focus: seat-
specific training/evaluation for flight crew members designated to perform duties from either
control seat).
□ Examined selected flight crew member training/qualification records (focus: completion of seat-
specific evaluation in initial/recurrent training).
□ Other Actions (Specify)
Guidance
The intent of this provision is to ensure that any pilot designated to perform duties from either control
seat, including takeoffs and landings, completes seat specific qualification.
FLT 2.1.1B addresses overall AQP/ATQP/EBT elements and specifications, as well as Authority
approval/acceptance requirements.
The specifications of this provision typically apply to pilot flight crew members, such as:
• Type Rating Instructors (TRIs)
• Type Rating Examiners (TREs)
• Pilots who are authorized to conduct takeoff and landings from either control seat.
Cruise relief pilots may meet the seat-specific requirements of this provision as part of a State-
approved or State-accepted (cruise relief pilot) qualification program.
Cruise relief pilots are not required to receive recurrent training in both control seats once every
12 months unless required as part of a State-approved or -accepted (cruise relief pilot) qualification
program.
FLT 2.2.38 If the Operator conducts training flights, the Operator shall specify those required
maneuvers and procedures that cannot be safely accomplished in an aircraft, and ensure such
maneuvers and procedures are either trained and evaluated in a representative flight simulator or, if
such a synthetic device does not exist, ensure a demonstration of pilot competence in those
maneuvers and procedures using an alternative means in accordance with FLT 2.2.41. Maneuvers
and procedures that cannot be safely accomplished in an aircraft shall include, as a minimum:
(i) Windshear avoidance and recovery;
(ii) Response to GPWS alerts and warnings and the avoidance of Controlled Flight Into Terrain
(CFIT);
(iii) Response to TCAS/ACAS alerts. (GM)
Note: If a representative flight simulator exists, conformity with FLT 2.2.32, FLT 2.2.33 and
FLT 2.2.35 is required for the Operator to be in conformity with this provision.
Note: If a representative flight simulator does not exist, conformity with FLT 2.2.41 is required for the
Operator to be in conformity with this provision.
Auditor Actions
□ Identified/Assessed designation of required maneuvers/procedures that cannot be
accomplished in an aircraft, requirement for flight crew training/evaluation in such
maneuvers/procedures in an approved representative flight training device, or using alternative
means in accordance with FLT 2.2.41.
□ Interviewed responsible manager(s) in flight operations.
□ Examined aircraft training/qualification curriculum/syllabus (focus: exclusion of specified
maneuvers from aircraft training).
□ Examined selected flight crew member training/qualification records (focus: completion of
specified maneuvers in an approved representative training device or via alternative means).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Flight Simulator.
The intent of this provision is to ensure both of the following:
• The maneuvers and procedures that cannot be safely accomplished in an aircraft are
specified by the operator and include, as a minimum, those maneuvers specified in i), ii)
and iii);
• A demonstration of pilot competence in the specified maneuvers and procedures using either
a representative flight simulator or an alternative means (as specified in FLT 2.2.41) if such
flight simulator does not exist.
Training is accomplished in a representative flight simulator approved for the purpose by the State.
Refer to FLT 2.2.41 if no representative flight simulator exists for the aircraft type.
Refer to FLT 2.2.32, FLT 2.2.33, FLT 2.2.35 and associated Guidance for additional specifications
and information related to the training and evaluation on the specified maneuvers.
FLT 2.2.39 If the Operator conducts training flights and accomplishes training or evaluation related
to a failed or inoperative engine during such flights, the Operator shall ensure engine failures are
simulated for the purpose of accomplishing any maneuvers that involve a failed or inoperative
engine. (GM)
Auditor Actions
□ Identified/Assessed requirement for only simulated engine failure during aircraft training flights.
□ Interviewed responsible manager(s) in flight operations.
□ Examined instructor guidance for aircraft training flights (focus: instructions for simulation of
engine failure for maneuvers that involve failed/inoperative engine).
□ Other Actions (Specify)
Guidance
The intent of this provision is to ensure maneuvers that involve a failed or inoperative engine are
safely accomplished when training in such maneuvers is performed in the aircraft (as required by the
Authority or due to the unavailability of a representative flight simulator approved for the purpose by
the State). In order to ensure maneuvers that involve a failed or inoperative engine are accomplished
safely during training flights, engine failures are typically simulated in a manner that would not
prevent the flight crew from recovering immediate and full control of an engine.
FLT 2.2.40 The Operator shall ensure flight crew members complete training and, when
applicable, an evaluation that includes a demonstration of competence in duties and procedures
related to flight crew incapacitation. Such training and, when applicable, evaluation shall be
completed during initial ground training and subsequently during recurrent training either once every
36 months or, if applicable, in accordance with the continuing qualification schedule as defined in the
Operator's AQP/ATQP/EBT that conforms to the specifications of FLT 2.1.1B. (GM)
Auditor Actions
□ Identified/Assessed requirement for demonstration of competence in duties/procedures related
to flight crew incapacitation in flight crew training/evaluation program.
□ Identified/Assessed flight crew AQP/ATQP/EBT (if applicable): (focus continuing qualification
recurrent schedule for demonstration of competence in duties/procedures related to flight crew
incapacitation).
□ Interviewed responsible manager(s) in flight operations.
□ Examined selected initial/recurrent training/qualification course curricula/syllabi (focus:
evaluation in duties/procedures related to flight crew incapacitation).
□ Examined selected flight crew member training/qualification records (focus: completion of
demonstration of competence in duties/procedures related to flight crew incapacitation in
initial/recurrent training).
□ Other Actions (Specify)
Guidance
The specification of this provision is applicable to all flight crew members.
FLT 2.1.1B addresses overall AQP/ATQP/EBT elements and specifications, as well as Authority
approval/acceptance requirements.
A demonstration of competence in the crew member duties and procedures related to flight crew
incapacitation is applicable when such a demonstration is required by the operator and/or State in
conjunction with State-approved or State-accepted training courses that require a method of
evaluation. Such courses typically include:
• Type qualification;
• Transition (conversion);
• Upgrade to PIC;
• Re-qualification;
• Recurrent.
FLT 2.2.41 If the Operator conducts training flights and is unable to train and evaluate the required
maneuvers and procedures specified in FLT 2.2.38 due to the non-existence of a representative flight
simulator, the Operator shall utilize an alternative means for ensuring a demonstration of pilot
competence in such maneuvers and procedures. Any alternative means shall be approved or
accepted by the State, and require a demonstration of competence through a combination of means,
to include:
(i) The use of generic flight simulators;
(ii) The use of representative and/or generic flight training devices;
(iii) Additional ground and line training and evaluation;
(iv) As applicable, any other means that ensures a demonstration of pilot competence in the
applicable maneuvers and procedures. (GM)
Auditor Actions
□ Identified/Assessed requirement for flight crew demonstration of competence utilizing
alternative means for required maneuvers/procedures that cannot be accomplished in an aircraft
or due to the non-availability of a representative flight training device.
□ Interviewed responsible manager(s) in flight operations.
□ Examined applicable training/qualification curriculum/syllabus (focus: training/evaluation in
designated maneuvers accomplished; definition of acceptable alternative means of training).
□ Examined selected flight crew member training/qualification records (focus: demonstration of
competence in designated maneuvers completed utilizing alternative means).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Flight Training Device (FTD).
The intent of this provision is for the operator to ensure, in the absence of a representative flight
simulator necessary to conform to FLT 2.2.38, that suitable and effective alternatives are utilized for
the training and evaluation of maneuvers and procedures that cannot be safely conducted in an
aircraft.
It is important to note that conformity with this provision requires a combination of alternative training
and evaluation methods to ensure a demonstration of pilot competence (i.e. generic simulators
and/or flight training devices, ground training/evaluation, line training/evaluation, other). This
requirement is based on the presumption that any one method when used alone would be
inadequate to ensure competence in the specified maneuvers as well as associated procedures.
Windshear, GPWS, and TCAS training maneuvers and procedures, as specified in FLT 2.2.38,
cannot be safely accomplished in an aircraft during a training flight or line training.
Refer to FLT 2.2.32, FLT 2.2.33, FLT 2.2.35 and associated Guidance for additional specifications
and information related to the required training and evaluation associated with:
• Windshear avoidance and recovery;
• Response to GPWS alerts and warnings and the avoidance of Controlled Flight Into Terrain
(CFIT);
• Response to TCAS/ACAS alerts.
FLT 2.2.42 If the Operator transports passengers or supernumeraries, the Operator shall ensure
flight crew members complete security training as approved or accepted by the State, and in
accordance with the Operator's security training program as specified in SEC 2.1.1. Such training
shall be completed during initial ground training and subsequently during recurrent training either a
minimum of once every 36 months or, if applicable, in accordance with the continuing qualification
schedule as defined in the Operator's AQP/ATQP/EBT that conforms to the specifications of FLT
2.1.1B. Flight crew security training shall address the following subject areas:
(i) Determination of the seriousness of the occurrence;
(ii) Crew communication and coordination;
(iii) Appropriate self-defense responses;
(iv) Use of non-lethal protective devices assigned to crew members for use as authorized by the
State;
(v) Understanding the behavior of terrorists so as to facilitate the ability to cope with hijacker
behavior and passenger responses;
(vi) Situational training exercises regarding various threat conditions;
(vii) Flight deck procedures to protect the aircraft;
(viii) Aircraft search procedures;
(ix) As practicable, guidance on least-risk bomb locations. (GM)
Note: Flight crew members shall complete initial security training prior to being assigned to
operational duties.
Note: The specifications of this provision are applicable to flight crew members utilized on board an
aircraft during commercial and/or non-commercial operations.
Auditor Actions
□ Identified/Assessed flight crew security training program (focus: approval/acceptance by the
State; meets applicable requirements of other states).
□ Identified/Assessed flight crew AQP/ATQP/EBT (if applicable): (focus continuing qualification
recurrent schedule for flight crew security training).
□ Interviewed responsible manager(s) in flight operations.
□ Examined selected initial/recurrent training/qualification course curricula/syllabi (focus: security
training is included; required subjects are addressed).
compartment in accordance with the specifications of this provision are competent to perform any
assigned duties or functions related to passenger cabin or cargo compartment safety.
An aircraft type-specific training course would typically address any cabin or supernumerary
compartment actions to be taken during normal, abnormal or emergency situations.
The term “abnormal” is used to describe a condition or situation (e.g. abnormal airframe vibration,
abnormal landing configuration).
The terms “normal” and “non-normal/emergency” typically refer to AOM checklists, procedures
and/or maneuvers. The term “non-normal” includes AOM emergency checklists and/or procedures
(i.e. an emergency procedure is a subset of non-normal).
The terms can also be used to describe an event, situation or operation that would be addressed by
normal or non-normal/emergency procedures or checklists. When used in this manner, the terms
may be separated by forward slash marks (e.g. normal/non-normal/emergency).
The term “emergency” used alone refers to declarations and non-AOM procedures.
Refer to FLT 2.4.1 and associated Guidance for additional specifications and information that
addresses special areas, routes route segments and special airports.
FLT 2.1.1B addresses overall AQP/ATQP/EBT elements and specifications, as well as
approval/acceptance requirements of the Authority.
This specification in item v) applies to all candidates for the position of PIC, to include SIC upgrade
candidates and pilots hired directly into PIC positions in operations for the operator.
The training and evaluation specified in this provision is accomplished by pilot flight crew members
as part of; ground training, simulator/aircraft training or line training.
FLT 2.3.2 The Operator shall ensure each pilot flight crew member, in order to maintain
qualification, receives training and, when applicable, successfully completes an evaluation at or
above the standards stipulated in the training syllabus and administered by an Evaluator of the
Operator or a representative of the Authority, and demonstrates piloting technique and competence
to execute emergency procedures and comply with instrument flight rules. Such training and, when
applicable, evaluation shall be conducted in accordance with the requirements of the State and
applicable authorities to ensure evaluations for all pilot flight crew members are conducted utilizing
one or more of the following intervals, as applicable:
(i) For the PIC, twice within any period of one year plus or minus one calendar month from the
original qualification anniversary date or base month, and/or
(ii) For pilot crew members other than the PIC, in accordance with i), or once within any period
of one year plus or minus one calendar month from the original qualification anniversary
date or base month, and/or
(iii) For any pilot crew member participating in an AQP, ETQP or EBT program, once within any
period of one year, or other period approved or accepted by the State, provided such
training and qualification program incorporates all elements and specifications contained in
Table 2.6 and Table 2.7. (GM)
Auditor Actions
□ Identified/Assessed requirement for flight crew continuing qualification that includes a
demonstration of piloting technique and competence to execute emergency procedures and
comply with instrument flight rules; definition of continuing training/evaluation interval(s).
□ Identified/Assessed flight crew AQP/ATQP/EBT (if applicable): (focus continuing qualification
schedule for demonstration of piloting technique and competence to execute emergency
procedures and comply with instrument flight rules).
□ Interviewed responsible manager(s) in flight operations.
□ Examined selected recurrent training/qualification course curricula/syllabi (focus:
training/evaluation in emergency procedures/compliance with instrument flight rules).
□ Examined selected flight crew training/qualification records (focus: completion of continuing
qualification training/evaluation at intervals as specified).
□ Other Actions (Specify)
Guidance
Refer to the IRM for definitions of Base Month, Calendar Month, LOE and Training to Proficiency.
The modification of qualification intervals in accordance with an AQP, ATQP or EBT program
requires conformity with FLT 2.1.1B.
The intent of this provision is to define the conditions necessary for a pilot crewmember to maintain
qualification and to set a basic qualification interval, which may be slightly modified in accordance
with the specifications of the provision or conditions stipulated in guidance material.
The specifications of this provision are minimum requirements and might be exceeded by
requirements of the State or other applicable authorities. The applicable authorities specified in this
provision typically refer to authorities that have jurisdiction over international operations conducted by
an operator over the high seas or the territory of a state that is other than the State of the Operator.
An operator, in accordance with the requirements of the State and other applicable authorities, may
adjust the frequency of evaluations specified in item i) of this provision to minimize overlap, preserve
the original qualification date, and ensure evaluations are completed within the annual cycle set forth
by the operator, State and/or applicable authorities.
Providing a minimum of two simulator training sessions within a thirteen-month period typically
satisfies the requirements of item i) if the interval between training sessions is not less restrictive than
what is specified by the operator, State and/or applicable authorities.
The evaluation cycles specified in items i) and ii) of this provision may be completed in 13 months in
accordance with State requirements that allow such cycle to be adjusted a maximum of plus or minus
one calendar month from the original qualification anniversary date or base month. Such flexibility is
normally incorporated in the training and evaluation program to allow for latitude in the trainee
scheduling process.
The evaluation cycles specified in items i) and ii) of this provision may also be adjusted in accordance
with State requirements that ensure each flight crew member undergoes training and, when
applicable, an evaluation at least every 6 or 12 calendar months, as applicable. If the training and
evaluation, however, is conducted within 3 calendar months prior to the expiry of the 6 calendar
month period in the case of item i), or the 12 calendar months period in the case of item ii), the next
training and evaluation must be completed within 6 or 12 calendar months, respectively, of the
original expiry date of the previous training and evaluation.
Accommodations made to adjust evaluation cycles or frequency may not affect the original
anniversary date or base month when flight crew member qualification was either:
• First established, or
• Re-established following a period of extended absence, and subject to the satisfactory
completion of a training program designed specifically for the re-qualification of flight crew
members following an extended absence.
One of the evaluations specified in item i), in a 12-calendar month period, may be administered by an
instructor, trained and authorized by the operator and the Authority, during the conduct of a simulator
or aircraft training course, approved or accepted by the Authority, for the purpose of maintaining
piloting technique and competence.
One of the evaluations specified in item ii), in a 24-calendar month period, may be administered by
an instructor, trained and authorized by the operator and the Authority, during the conduct of a
simulator or aircraft training course, approved or accepted by the Authority, for the purpose of
maintaining piloting technique and competence.
Simulator or aircraft training courses approved or accepted by the Authority for the purpose of
maintaining piloting technique and competence typically include one or more of the following
elements:
• Training-to-proficiency at the pilot controls of an aircraft or aircraft simulator;
• Appropriate briefings before and after the training;
• LOE utilizing a complete flight crew;
• Maneuvers and procedures (abnormal and emergency) that may occur in line operations.
The term “abnormal” is used to describe a condition or situation (e.g. abnormal airframe vibration,
abnormal landing configuration).
The terms “normal” and “non-normal/emergency” typically refer to AOM checklists, procedures
and/or maneuvers. The term “non-normal” includes AOM emergency checklists and/or procedures
(i.e. an emergency procedure is a subset of non-normal).
The terms can also be used to describe an event, situation or operation that would be addressed by
normal or non-normal/emergency procedures or checklists. When used in this manner, the terms
may be separated by forward slash marks (e.g. normal/non-normal/emergency).
The term “emergency” used alone refers to declarations and non-AOM procedures.
FLT 2.3.3 The Operator shall ensure line training for the second-in-command (SIC) includes an
amount of Pilot Monitoring (PM) and Pilot Flying (PF) duties sufficient to develop and demonstrate
proficiency in such duties. (GM)
Auditor Actions
□ Identified/Assessed requirement for SIC training in PM/PF duties in flight crew line qualification
training/evaluation program.
□ Interviewed responsible manager(s) in flight operations.
□ Examined selected SIC training/qualification records (focus: completion of training/evaluation in
PM/PF duties).
□ Other Actions (Specify)
Guidance
The term Pilot Monitoring (PM) has the same meaning as the term Pilot Not Flying (PNF) for the
purpose of applying the specifications of this provision.
FLT 2.3.4 The Operator shall ensure pilot flight crew members complete an evaluation that
includes a demonstration of knowledge of the operations approved as part of the Air Operator
Certificate (AOC) during initial training and subsequently during recurrent training either once every
12 months or, if applicable, in accordance with the continuing qualification schedule as defined in the
Operator's AQP/ATQP/EBT that conforms to the specifications of FLT 2.1.1B. Such evaluation shall
include a demonstration of knowledge of:
(i) Approaches authorized by the Authority;
(ii) Ceiling and visibility requirements for takeoff, approach and landing;
(iii) Allowance for inoperative ground components;
(iv) Wind limitations (crosswind, tailwind and, if applicable, headwind). (GM)
Auditor Actions
□ Identified/Assessed requirement for flight crew initial/continuing qualification that includes a
demonstration of knowledge of operations approved as part of the AOC.
□ Identified/Assessed flight crew AQP/ATQP/EBT (if applicable): (focus continuing qualification
recurrent schedule for demonstration of knowledge of AOC operations).
□ Interviewed responsible manager(s) in flight operations.
□ Examined flight crew line qualification initial/recurrent curricula/syllabi (focus: evaluation of
relevant operational knowledge; definition of operational areas addressed).
□ Examined selected flight crew training/qualification records (focus: completion of
initial/continuing qualification training/evaluation).
□ Other Actions (Specify)
Guidance
FLT 2.1.1B addresses overall AQP/ATQP/EBT elements and specifications, as well as Authority
approval/acceptance requirements.
The training and evaluation specified in this provision is accomplished by pilot flight crew members
as part of ground, simulator/aircraft or line training.
The specifications of this provision are normally satisfied during line training but can occur elsewhere
in the training program.
The wind limitations specified in item iv) refer to maximum limits that have been demonstrated for
takeoff and landing, as well as limits that have been established for the type of operation being
conducted (e.g., as applicable, automatic landing, HUD/EVS guided, or contaminated runway).
FLT 2.3.5 (Intentionally open)
FLT 2.3.6 The Operator shall ensure pilot flight crew members complete a Command Training and
Evaluation program during initial training and qualification and, if applicable, in accordance with the
continuing qualification curriculum as defined in the Operator's AQP/ATQP/EBT that conforms to the
specifications of FLT 2.1.1B. Such training and evaluation shall be completed prior to a pilot flight
crew member being assigned as PIC in operations. (GM)
Auditor Actions
□ Identified/Assessed requirement for PIC command training/evaluation program.
□ Identified/Assessed flight crew AQP/ATQP/EBT (if applicable): (focus continuing qualification
recurrent schedule for PIC command training/evaluation).
□ Interviewed responsible manager(s) in flight operations.
□ Examined selected flight crew training/qualification records (focus: completion of command
training/evaluation prior to assignment to PIC duties).
□ Other Actions (Specify).
Guidance
FLT 2.1.1B addresses overall AQP/ATQP/EBT elements and specifications, as well as Authority
approval/acceptance requirements.
The specifications of this provision apply to all candidates for the position of PIC, to include SIC
upgrade candidates and pilots hired directly into PIC positions in operations for the operator.
Command training and evaluation is accomplished by pilot flight crew members as part of ground,
simulator/aircraft or line training.
Command training and evaluation programs may be conducted in addition to, and/or in conjunction
with, one or more of the training programs specified in FLT 2.1.1.
The program specified in this provision addresses the technical and non-technical aspects of
command relevant to the operations of the operator, and typically includes:
• Technical seat-specific aircraft training for the aircraft type;
• Basic operator familiarization training in subjects relevant to the PIC;
• Human performance and CRM skill training relevant to command, the relationship with other
crew members and the operation as a whole (e.g. leadership, team building, conflict
resolution, etc.);
• Training in the sections of the OM relevant to command, to include:
○ Authority and responsibilities of the PIC in operations for the operator;
○ Adherence to the limitations of the AOC;
○ Responsibilities relevant to the OFP and ATL;
○ Responsibilities relevant to the reporting of accidents and incidents.
Auditor Actions
□ Identified/Assessed requirement for flight crew training/evaluation in specialized navigation
operations (MNPS/AMU, as applicable).
□ Interviewed responsible manager(s) in flight operations.
□ Examined selected flight crew qualification initial curricula/syllabi (focus: training in relevant
specialized navigation).
□ Examined selected flight crew training/qualification records (focus: completion of
training/evaluation in applicable specialized navigation operations prior to being utilized in such
specialized operations).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definitions of Areas of Magnetic Unreliability (AMU) and Minimum Navigation
Performance Specifications (MNPS).
The training or evaluation specified in this provision is accomplished by flight crew members as part
of the initial ground training, simulator/aircraft training or line training program.
The specifications of this provision apply to pilot flight crew members and, if utilized in conjunction
with such operations, flight navigators.
FLT 2.4.3 If the Operator utilizes flight crew members to concurrently operate aircraft of different
types, or operate variants within one type, the Operator shall have qualification processes that are
approved or accepted by the State and ensure such flight crew members complete training and an
evaluation that emphasizes the differences between aircraft types and variants. Such training and
evaluation shall be completed during initial ground, simulator and line training, and subsequently
during recurrent simulator training either once every 12 months or, if applicable, in accordance with
the continuing qualification schedule as defined in the Operator's AQP/ATQP/EBT that conforms to
the specifications of FLT 2.1.1B. (GM)
Auditor Actions
□ Identified/Assessed requirement for flight crew training/evaluation in differences between
aircraft types/variants (as applicable).
□ Identified/Assessed flight crew AQP/ATQP/EBT (if applicable): (focus continuing qualification
recurrent schedule for training/evaluation in differences between aircraft types/variants).
□ Interviewed responsible manager(s) in flight operations.
□ Examined flight crew line qualification initial/recurrent curricula/syllabi (focus: training/evaluation
in differences between relevant aircraft types/variants).
□ Examined selected flight crew training/qualification records (focus: completion of
training/evaluation in differences between aircraft types/variants).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definitions of Aircraft Type and Aircraft Variant (within Type).
The intent of this specification is to ensure flight crew members are familiarized with the significant
differences in equipment and/or procedures between concurrently operated types or variants.
The determination of variant within type is within the domain of the State as part of flight crew
licensing.
FLT 2.1.1B addresses overall AQP/ATQP/EBT elements and specifications, as well as Authority
approval/acceptance requirements.
Qualification processes are applicable to all flight crew members used in such operations and as
defined in the IRM.
Aircraft differences that require emphasis typically include level of technology, ergonomics,
operational differences and handling characteristics.
3 Line Operations
The existence (and application) of a State common language requirement that satisfies the
specifications of this provision relieves the operator of such a designation in operational
documentation.
FLT 3.3.2 The Operator shall have guidance and criteria that address the pairing of inexperienced
pilot crew members and ensure scheduling processes prevent inexperienced pilot flight crew
members, as defined by the Operator or the State, from operating together. (GM)
Auditor Actions
□ Identified/Assessed guidance/criteria that prohibit pairing of inexperienced pilot flight crew
members.
□ Identified/Assessed tracking/scheduling processes that prevent pairing of inexperienced pilot
flight crew members.
□ Interviewed responsible manager(s) in flight operations.
□ Examined selected flight crew pairing records (focus: inexperienced flight crew members not
paired together).
□ Observed flight crew scheduling operations (focus: scheduling uses guidance/criteria that
prevent pairing of inexperience flight crew members).
□ Other Actions (Specify)
Guidance
The definition of inexperienced pilot flight crew member typically varies depending on the operator or
the State and generally refers to a minimum number of hours in aircraft type after the completion of
initial training/qualification.
The specifications of this provision are intended to preclude two newly trained or inexperienced pilots
from operating together in an aircraft type until they each achieve a level of experience defined by the
operator or the State.
FLT 3.3.3 If the Operator conducts low visibility approaches, the Operator shall define a minimum
level of command experience required for a pilot to be authorized to conduct such approaches as
PIC to approved Operator minima. (GM)
Auditor Actions
□ Identified/Assessed defined minimum level(s) of command experience required for PIC to be
authorized to conduct low visibility approaches to approved minima.
□ Interviewed responsible manager(s) in flight operations.
□ Examined OM guidance/procedures (focus: defined PIC minimum level of command experience
to conduct low visibility approaches to approved minima).
□ Examined selected flight crew training/qualification records (focus: low visibility approach
authorization based on experience level).
□ Other Actions (Specify)
Guidance
For those flight crew members qualified as PIC on aircraft types equipped for low visibility
approaches, the specification for a minimum level of command experience may be replaced by a
State-approved or State-accepted training program on low visibility operations conducted in a
simulator suitable for the purpose.
FLT 3.3.4 The Operator shall ensure flight crew members will not operate an aircraft unless issued
a medical assessment in accordance with requirements of the State; such assessment shall not be
valid for a period greater than 12 months. (GM)
Auditor Actions
□ Identified/Assessed requirement for flight crew members to have valid medical assessment in
accordance with requirements of the State, maximum 12 months validity.
□ Identified/Assessed tracking/scheduling processes that prevent flight crew members from
assignment to flight duty without valid medical assessment.
□ Interviewed responsible manager(s) in flight operations.
□ Examined selected flight crew training/qualification records (focus: existence of valid medical
assessment).
□ Observed flight crew scheduling operations (focus: scheduling tracks/accounts for valid flight
crew member medical assessment).
□ Other Actions (Specify)
Guidance
Requirements of the State and/or an applicable authority that are associated with medical
classifications, aircraft types, flight crew positions and/or licensing could require a more restrictive
assessment interval than specified in this provision. An applicable authority is one that has
jurisdiction over international operations conducted by an operator over the high seas or the territory
of a state that is other than the State of the Operator.
FLT 3.3.5 If the Operator conducts international flight operations, the Operator shall ensure either
of the following apply to flight crew members that operate such flights:
(i) The Operator has a method to prevent such crew members from acting as a pilot after
having attained their 65th birthday, or
(ii) Where laws or regulations of the State do not permit maximum age limits, the Operator has
a method, which is acceptable to the State and other applicable states, for making a
determination that pilot flight crew members are no longer permitted to exercise the
privileges of their pilot license in international operations for the operator. (GM)
Auditor Actions
□ Identified/Assessed requirements/restrictions applicable to use of pilot flight crew members that
have attained 65 years of age.
□ Identified/Assessed tracking/scheduling processes that ensure assignments of PIC and crew
pairing for international flights are in accordance with age limitations/restrictions.
□ Interviewed responsible manager(s) in flight operations.
□ Examined selected flight crew training/qualification records (focus: retention of age
imitations/restrictions).
□ Observed flight crew scheduling operations (focus: scheduling accounts for/complies with
age/other restrictions that prohibit assignment of flight crew member as pilot in international flight
operations).
□ Other Actions (Specify)
Guidance
The intent of this provision is to address pilot flight crew member duty assignments for international
operations when the flight crew includes at least one pilot that has attained 65 years of age.
The specifications of this provision refer to the maximum age(s), as specified by an operator or the
Authority, beyond which pilot privileges are curtailed or cancelled. Such curtailment or cancellation of
privileges is generally associated with flight crew member position and/or flight crew composition.
The specifications in item ii) refer to operators that are subject to laws or regulations of the State that
preclude the specification of maximum age limits for flight crew members to exercise the full
privileges of their pilot license in operations for the operator.
The specifications of this provision may be satisfied by an operator's process for tracking pilot flight
crew member age, if age requirements or limits are specified by the operator or Authority. Such
tracking might be necessary to conform to State requirements when a pilot crew member changes
position or reaches a mandatory age limit.
FLT 3.3.6 (Intentionally open)
FLT 3.3.7 The Operator shall have a process to ensure flight crew member recency-of-experience
requirements are satisfied as follows:
(i) A pilot does not act as PIC or SIC of an aircraft unless either:
(a) On the same type or variant of aircraft within the preceding 90 days (120 days if
under the supervision of an instructor or evaluator), that pilot has operated the flight
controls during at least three takeoffs and landings in the aircraft type or in a flight
simulator approved for the purpose by the appropriate authority, or
(b) On the same type or variant of aircraft within a time period acceptable to the State
and applicable authorities, that pilot has operated the flight controls during the
number of takeoffs and landings in the aircraft type or in a flight simulator approved
for the purpose by the appropriate authority, necessary to conform to a defined
recency of experience schedule approved or accepted by the State and applicable
authorities.
(ii) A pilot does not act in the capacity of a cruise relief pilot unless, within the preceding
90 days, that pilot has either:
(a) Operated as PIC, SIC or cruise relief pilot on the same type or variant of aircraft, or
(b) Completed flying skill refresher training to include normal, abnormal and emergency
procedures specific to cruise flight on the same type of aircraft or in a flight simulator
approved for the purpose, and has practiced approach and landing procedures,
where the approach and landing procedure practice may be performed as the PM.
(iii) A flight engineer does not perform duties in an aircraft unless either:
(a) Within the preceding 6 months, that individual has had at least 50 hours of flight
time as a flight engineer on that aircraft type aircraft, or
(b) Within the preceding 90 days, that individual has operated as a flight engineer on
board that aircraft type or in a simulator of the aircraft type.
(iv) A flight navigator or radio operator does not perform duties in an aircraft unless recency-of-
experience requirements of the Operator and the State have been satisfied.
(v) If a flight crew member does not satisfy recency-of-experience requirements in accordance
with i), ii), iii) or iv), such flight crew member completes re-qualification in accordance with
the Operator's training and evaluation program. (GM)
Auditor Actions
□ Identified/Assessed tracking/scheduling processes that prevent flight crew members from flight
duty assignment unless recency-of-experience qualification requirements are met.
□ Interviewed responsible manager(s) in flight operations.
□ Examined OM guidance/procedures (focus: definition of recency-of-experience qualification
requirements).
□ Examined selected flight crew training/qualification records (focus: satisfaction of recency-of-
experience qualification requirements).
□ Observed flight crew scheduling operations (focus: scheduling tracks/accounts for flight crew
member recency-of-experience qualification requirements).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Cruise Relief Pilot.
The specification in item i) requires the pilots to operate the flight controls: PM duties do not satisfy
recency-of-experience requirements for this specification.
The term Pilot Monitoring (PM) has the same meaning as the term Pilot Not Flying (PNF) for the
purpose of applying the specifications of this provision.
The specification in item i) b) may stipulate the number of takeoffs and landings to be performed
according to a defined schedule in order to establish an equivalent level of recency experience. Such
schedule would not have to adhere exactly to the specification in item i) a) of this provision if the level
of recent experience is acceptable to the State and applicable authorities, and the PIC or SIC, as
applicable, is required to operate the flight controls in order to satisfy recency-of-experience
requirements.
Item v) specifies that a flight crew member whose recency has lapsed for any reason becomes
unqualified, and must be re-qualified by the operator. The requalification program for such a flight
crewmember need not specify the same number of takeoffs and landings as the recency
requirements.
Applicable authorities include those authorities that have jurisdiction over international operations
conducted by an operator over the high seas or the territory of a state that is other than the State of
the Operator.
The term “abnormal” is used to describe a condition or situation (e.g. abnormal airframe vibration,
abnormal landing configuration).
The terms “normal” and “non-normal/emergency” typically refer to AOM checklists, procedures
and/or maneuvers. The term “non-normal” includes AOM emergency checklists and/or procedures
(i.e. an emergency procedure is a subset of non-normal).
The terms can also be used to describe an event, situation or operation that would be addressed by
normal or non-normal/emergency procedures or checklists. When used in this manner, the terms
may be separated by forward slash marks (e.g. normal/non-normal/emergency).
The term “emergency” used alone refers to declarations and non-AOM procedures.
FLT 3.3.8 (Intentionally open)
FLT 3.3.9 The Operator shall have a process to ensure each pilot, prior to being used as a PIC in
operations, is currently qualified for operations into airports of intended landing in areas, on routes or
route segments to be used in operations for the Operator. If an instrument approach is required into
an airport for which the PIC has not made an actual approach, the PIC shall be accompanied by a
pilot flight crew member or pilot observer on the flight deck who is qualified for the airport unless any
of the following conditions exist:
(i) The approach to the airport is not over difficult terrain and the instrument approach
procedures and aids available are similar to those with which the pilot is familiar, and the
normal operating minima are adjusted by a process that adds a margin of safety that is
approved or accepted by the State, or there is reasonable certainty that the approach and
landing can be made in visual meteorological conditions, or
(ii) Descent from the initial approach altitude to landing at the airport can be made by day in
VMC, or
(iii) The operator qualifies the PIC to land at the airport by means of a pictorial representation
approved or accepted the Authority, or
(iv) The airport is adjacent to another airport at which the PIC is currently qualified to land. (GM)
Auditor Actions
□ Identified/Assessed tracking/scheduling processes for ensuring PICs will meet qualification
requirements for airports/areas/routes to be used in operations.
□ Interviewed responsible manager(s) in flight operations.
□ Examined OM guidance/procedures (focus: definition of crew member qualification criteria for
operations into airports/areas/routes used in operations).
□ Observed flight crew scheduling operations (focus: scheduling accounts for PIC qualification on
intended routes/airports).
□ Other Actions (Specify)
Guidance
The specification in item i) may be satisfied by a process, approved or accepted by the State, that:
• Identifies instrument approach procedures that require the application of margins to
operating minima;
• Specifies the operating margin to be applied.
The specification in item iii) may be satisfied by any pictorial representation approved or accepted for
the purpose by the Authority, such as an instrument approach plate or chart.
Refer to FLT 2.4.1 and associated Guidance for additional specifications and information that
addresses special areas, routes, route segments and special airports.
FLT 3.3.10 The Operator shall have a process to ensure a pilot is not utilized as a PIC in
operations that require the application of special skills or knowledge within areas, on routes over
difficult terrain and/or into special airports, as designated by the State or by the Operator, unless,
within the preceding 12 months, that pilot has either:
(i) Made at least one trip as a pilot flight crew member, line check airman or observer on the
flight deck on a route in close proximity and over similar terrain within the specified area(s),
on the specified route and/or into the special airport, as applicable, or
(ii) Fulfilled special line qualification requirements in accordance with FLT 2.4.1. (GM)
Auditor Actions
□ Identified/Assessed tracking/scheduling processes that prevent PICs from flight duty
assignment into airports/areas and on routes/route segments that require special
skills/knowledge, unless qualification requirements have been satisfied.
□ Interviewed responsible manager(s) in flight operations.
□ Examined OM guidance/procedures (focus: definition of PIC qualification criteria for operations
into airports/areas/routes that require special knowledge/skills).
□ Observed flight crew scheduling operations (focus: scheduling tracks/accounts for PIC
qualification for routes/airports that require special knowledge/skills).
□ Other Actions (Specify)
Guidance
Special airport and/or route/area re-qualification (if applicable) could take the form of pictorial review,
simulator training, line check airmen briefing or operation into the airport accompanied by a line
check airman.
The intent of this provision is to ensure the PIC has a level of knowledge of terrain, minimum safe
altitudes, seasonal meteorological conditions, communication and air traffic facilities, services and
procedures, search and rescue services and navigational facilities and procedures, including any
long-range navigation procedures, required for safe operations.
Refer to FLT 2.4.1 and associated Guidance for additional specifications and information that
addresses special areas, routes route segments and special airports.
Auditor Actions
□ Identified/Assessed tracking/scheduling processes that prevent flight crew members from flight
duty assignment unless currently qualified in accordance with Table 2.3 or other applicable
requirements of the State.
□ Interviewed responsible manager(s) in flight operations.
□ Examined process for determining additional flight crew qualification requirements of the State.
□ Examined selected flight crew duty assignment records (focus: satisfaction of applicable
qualification requirements).
□ Observed flight crew scheduling operations (focus: scheduling requires flight crew member
qualification in accordance with Table 2.3 and requirements of State).
□ Other Actions (Specify)
Guidance
The intent of this provision is to ensure flight crew member requirements and related scheduling
processes preclude operation of an aircraft by a flight crew member that is not qualified and current in
accordance with the specifications of the provision.
FLT 3.4.2 The Operator shall have a scheduling policy that ensures flight crew members, prior to
being assigned to duty, will not be adversely affected by factors that could impair human
performance, to include, as a minimum:
(i) Pregnancy;
(ii) Illness, surgery or use of medication(s);
(iii) Blood donation;
(iv) Deep underwater diving;
(v) Fatigue whether occurring in one flight, successive flights or accumulated over a period of
time. (GM)
Auditor Actions
□ Identified/Assessed scheduling policy/process that takes into account factors that could impair
flight crew human performance prior to flight duty assignment.
□ Interviewed responsible manager(s) in flight operations.
□ Examined OM guidance/procedures (focus: definition of factors that impair flight crew human
performance).
□ Examined selected flight crew duty assignment records (focus: examples of application of
human performance factors).
□ Observed flight crew scheduling operations (focus: scheduling accounts for human factors that
could affect crew member performance).
□ Other Actions (Specify)
Guidance
The intent of this provision is to ensure an operator's policies address flight crew member “fitness for
duty.” Such policies typically assign the responsibility to the flight crew member to report and remain
“fit for duty” in accordance with the list of specifications in this provision.
FLT 3.4.3A The Operator shall have a methodology for the purpose of managing fatigue-related
safety risks to ensure fatigue occurring in one flight, successive flights or accumulated over a period
of time does not impair a flight crew member's alertness and ability to safely operate an aircraft or
perform safety-related duties. Such methodology shall consist of:
(i) Flight time, flight duty period, duty period and rest period limitations that are in accordance
with the applicable prescriptive fatigue management regulations of the State, and/or
(ii) If applicable, the Operator's Fatigue Risk Management System (FRMS) approved or
accepted by the State and established in accordance with FLT 3.4.3B. (GM)
Auditor Actions
□ Identified/Assessed requirements/methodology for flight crew fatigue management in
accordance with regulations of State and/or an FRMS.
□ Identified/Assessed FRMS (if applicable): approved/accepted by State, incorporates elements
as specified in FLT 3.4.3B.
□ Identified/Assessed tracking/scheduling processes that take into account flight time/flight duty
period/duty period/rest period limitations in the flight duty assignment of flight crew members.
□ Interviewed responsible manager(s) in flight operations.
□ Examined selected flight crew duty assignment records (focus: examples of application of flight
crew fatigue management limitations).
□ Observed flight crew scheduling operations (focus: scheduling includes management of fatigue-
related safety risk).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definitions of Fatigue and Fatigue Risk Management System (FRMS).
The intent of this provision is to ensure an operator establishes a methodology for the management
of crew member fatigue in a manner that:
• Is based upon scientific principles and knowledge;
• Is consistent with the prescriptive fatigue management and/or FRMS regulations of the State;
• Precludes fatigue from endangering safety of the flight.
Where authorized by the State, the operator may use a Fatigue Risk Management System (FRMS) in
accordance with FLT 3.4.3B alone or in combination with prescriptive flight time, flight duty period,
duty period and rest period limitations as the means for managing fatigue-related risks.
Guidance for the implementation of an FRMS is contained in the IATA/ICAO/IFALPA Fatigue
Management Guide for Airline Operators, 2nd Edition, 2015, and, as applicable, other reference
documents approved or accepted by the State for the purpose of FRMS implementation (e.g. FAA,
AC 120-103A–Fatigue Risk Management Systems for Aviation Safety).
FLT 3.4.3B If the Operator utilizes an FRMS to manage flight crew fatigue-related safety risks, the
Operator shall incorporate scientific principles and knowledge within the FRMS, comply with any
applicable requirements for managing flight crew fatigue as established by the State or Authority and,
as a minimum:
(i) Define and document the FRMS policy;
(ii) Incorporate risk management processes for fatigue hazard identification, risk assessment
and, if required, mitigation;
(iii) Develop and maintain effective FRMS safety assurance processes;
(iv) Establish and implement effective FRMS promotion processes. (GM)
Auditor Actions
□ Identified/Assessed FRMS policy/components/elements, compliance with fatigue risk
management requirements of State/Authority.
□ Identified/Assessed FRMS processes for flight crew fatigue risk management data
collection/analysis/hazard identification, safety risk assessment, safety risk mitigation/control.
□ Interviewed responsible manager(s) in flight operations.
□ Interviewed selected personnel that perform flight crew fatigue safety risk management
functions.
□ Examined selected examples of fatigue risk management (focus: hazard identified, risk
mitigation action implemented).
□ Observed flight crew scheduling operations (focus: scheduling includes management of fatigue-
related safety risk in accordance with an approved FRMS).
□ Other Action (Specify)
Guidance
The intent of this provision is to ensure fatigue occurring either in one flight, successive flights or
accumulated over a period of time does not impair a crew member's alertness and ability to safely
operate an aircraft or perform safety-related duties.
Where authorized by the State, the operator may use an FRMS as a means to determine that
variations from prescriptive fatigue management policies demonstrate an acceptable level of safety.
Guidance for the implementation of an FRMS is contained in the IATA/ICAO/IFALPA Fatigue
Management Guide for Operators, 2nd Edition, 2015, and, as applicable, other reference documents
approved or accepted by the State for the purpose of FRMS implementation (e.g. FAA, AC
120-103A–Fatigue Risk Management Systems for Aviation Safety).
The applicability of this provision is limited to those operations wherein fatigue is managed in
accordance with the FRMS as defined in the operator's FRMS documentation. It is important to note,
however, that an FRMS may be used alone or in combination with prescriptive flight time, flight duty
period, duty period and rest period limitations as the means for managing fatigue related risks.
The components of an effective FRMS as specified in this provision are described in the following
table.
FLT 3.4.3C If the Operator utilizes an FRMS to manage flight crew fatigue-related safety risks, the
Operator should ensure the organizational activities specified in FLT 3.4.3B related to the
management of flight crew fatigue-related risks are integrated with the Operator's organizational
safety management system (SMS) as specified in ORG 1.1.10. (GM)
Auditor Actions
□ Identified/Assessed integration of FRMS elements in organizational SMS.
□ Interviewed responsible manager(s) in flight operations.
□ Interviewed selected personnel that perform flight crew fatigue safety risk management
functions.
□ Examined selected examples of flight crew fatigue-related hazards addressed/analyzed under
organization-wide safety risk assessment/mitigation program.
□ Other Action (Specify).
Guidance
The intent of this provision is to ensure the “tactical” organizational activities specified in FLT 3.4.3B
interface with organizational safety risk management activities. This includes interfaces with SMS
and Quality systems to ensure operational systems and processes are subjected to the
organization's overarching safety and quality assurance processes.
Guidance for the integration of FRMS and SMS is described in the IATA/ICAO/IFALPA Fatigue Risk
Management System (FRMS) Implementation Guide for Operators, 1st Edition, July 2011.
FLT 3.4.4 The Operator shall consider the following as duty time for the purposes of determining
required rest periods and calculating duty time limitations for operating flight crew members:
(i) Entire duration of the flight;
(ii) Pre-operating deadhead time;
(iii) Training periods prior to a flight;
(iv) Administrative or office time prior to a flight (for flight crew members that serve in a
management function);
(v) If required by the State, flight time accrued by flight crew members in operations other than
those of the Operator. (GM)
Auditor Actions
□ Identified/Assessed requirements/criteria used for determination of required rest
periods/calculation of duty time limitations for operating flight crew members.
□ Identified/Assessed processes used to track flight crew compliance with duty time/rest period
limitations.
□ Interviewed responsible manager(s) in flight operations.
□ Examined selected flight crew duty assignment records (focus: application of duty time/rest
period limitations).
□ Observed flight crew scheduling operations (focus: scheduling uses defined criteria for
determining required flight crew rest periods/calculating duty time limitations.
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Deadheading.
The intent of this provision is to ensure an operator considers non-flight duty time, or flight time
accrued in operations other than those of the operator, that is likely to induce fatigue into the
calculation of duty time limitations and the determination of required rest periods.
FLT 3.4.5 (Intentionally open)
FLT 3.4.6 If the Operator utilizes flight crew members that are concurrently qualified to operate
aircraft of different types, or operate variants within one type, and the State specifies unique training
and/or recency requirements for such flight crew members to remain concurrently qualified, the
Operator shall have a scheduling process that addresses such unique requirements, to include, as a
minimum:
(i) Required differences training (between type or variants);
(ii) Recency of experience necessary to maintain currency on all types or variants. (GM)
Auditor Actions
□ Identified/Assessed scheduling processes that address flight crew members concurrently
qualified to operate aircraft of different types/variants within one type.
□ Interviewed responsible manager(s) in flight operations.
□ Interviewed flight crew scheduling personnel.
□ Examined requirements/criteria applicable to concurrently qualified flight crew members (focus:
differences training, recency of experience).
□ Other Actions (Specify)
Guidance
The intent of this provision is to ensure scheduling processes address the unique State requirements
(e.g. recency on each type or variant, or training on each type or variant), if any, that are necessary
for flight crew members to remain concurrently qualified to operate multiple types or variants within
type.
The determination of variant within type is within the domain of the State as part of flight crew
licensing
Guidance
Refer to the IRM for the definition of Aircraft Technical Log (ATL).
FLT 3.5.2 If the Operator utilizes aircraft with electronic navigation data capabilities, the Operator
shall have guidance and procedures for flight crew members to ensure the validity of any electronic
navigation database installed into aircraft navigation equipment. (GM)
Auditor Actions
□ Identified/Assessed OM guidance/procedures for flight crew preflight of aircraft navigation
equipment (focus: validation of any installed navigation databases; definition of validation
criteria).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight operations (focus: flight crew preflight navigation database validation).
□ Other Actions (Specify)
Guidance
Where more than one database is available for use in the aircraft navigation system, an operator can
ensure database validity by providing guidance for the flight crew to select the new database for use
prior to the first flight on the effective date for the new database.
The operator may provide relief in the MEL, permitting flight crew use of a non-current database for a
specified period of time due to database errors or faults.
FLT 3.5.3 If the Operator utilizes electronic flight bag (EFB) devices or systems, the Operator
should have guidance and procedures for flight crew members that address each EFB and the
operations conducted. Such guidance and procedures should address as a minimum:
(i) EFB use during normal and abnormal operations;
(ii) Database currency;
(iii) Operating limitations;
(iv) The remediation of EFB defects and/or errors including MEL processing if applicable;
(v) EFB failures. (GM)
Auditor Actions
□ Identified/Assessed OM guidance/procedures for flight crew use of EFB systems/devices
(focus: definition of areas/conditions/limitations to be addressed in use of EFB).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight operations (focus: flight crew use of EFB systems/devices).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Electronic Flight Bag (EFB).
An EFB may be used in conjunction with traditional hardcopy documents or to ultimately replace the
paper material a pilot is required to carry.
The specification in item i) refers to normal and abnormal operating procedures for all applicable
flight operations with EFBs. Such procedures are typically designed to control additional workloads
created by using EFB devices or systems and also specify times at which the flight crew should not
use them.
The specification in item ii) refers specifically to flight crew validation procedures for EFB databases
(e.g., electronic charts, performance data, etc.). Such validation may also apply to the software
required to display informative documents, such as pre-composed, fixed presentations of data
currently in paper format, if such validation is not accomplished by other means or personnel. The
management and control of such information by the organization, however, is in accordance with
FLT 1.6.1 to 1.6.5 inclusive. Additionally, the oversight and control of third party software is in
accordance with FLT 1.11.3.
The specification in item iii) refers to limitations regarding the use of an EFB. For example, where the
EFB is used for aircraft performance calculations such limitations would typically require procedures
for flight crew members to independently verify input data and crosscheck calculations in a manner
that provides sufficient opportunities for errors to be detected.
The specification in item iv) refers to the procedures for identifying and correcting defects and/or
errors in EFB software or hardware. Such procedures may or may not require processing in
accordance with the MEL depending on the class of EFB in use by the operator and approved by the
Authority.
The specifications in item v) refer to contingency procedures should an EFB or combination of EFBs
lose specific functionality or become unusable.
The term “abnormal” is used to describe a condition or situation (e.g. abnormal airframe vibration,
abnormal landing configuration).
The terms “normal” and “non-normal/emergency” typically refer to AOM checklists, procedures
and/or maneuvers. The term “non-normal” includes AOM emergency checklists and/or procedures
(i.e. an emergency procedure is a subset of non-normal).
The terms can also be used to describe an event, situation or operation that would be addressed by
normal or non-normal/emergency procedures or checklists. When used in this manner, the terms
may be separated by forward slash marks (e.g. normal/non-normal/emergency).
The term “emergency” used alone refers to declarations and non-AOM procedures.
Guidance
Operating minima refer to the limits of usability of an airport for takeoff or landing expressed in terms
of RVR, visibility, cloud condition or decision altitude/height. Operating minima could be affected by
aircraft equipment, flight crew qualifications and airport facilities/environment.
The specification of this provision only refers to the determination of minima related to airport
facilities/environment.
The specification of this provision also applies to the modification of takeoff and approach minima to
allow for airport equipment outages. Examples of airport equipment outages include: runway edge
lights inoperative, center line lights inoperative, etc.
Airports of intended use include: departure alternate, en route alternate, destination and destination
alternate.
FLT 3.6.4 The Operator shall have guidance that enables the flight crew to determine Runway
Visual Range (RVR) requirements for runways of intended use, to include, as a minimum:
(i) Requirement for the availability of RVR reporting in order for CAT II and CAT III approach
and landing operations to be authorized;
(ii) Required minimum RVR values for takeoff and authorized approaches;
(iii) Required minimum RVR values that consider inoperative approach/runway lighting,
inoperative transmissometers or inadequate visual reference. (GM)
Auditor Actions
□ Identified/Assessed OM guidance that specifies takeoff/landing runway visual range (RVR)
requirements/associated limitations for runways of intended use (focus: availability to flight crew;
instructions for use of information in operations).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight and flight simulator operations (focus: determination of airport RVR
requirements/associated limitations).
□ Other Actions (Specify)
Guidance
The means of RVR measurement typically varies depending on the State.
The specification in item iii) may be satisfied by a corrections table or manual corrections for
inoperative equipment applied to published minima.
FLT 3.6.5 The Operator should have guidance that ensures approach and landing operations are
not authorized when the prevailing visibility is below 800 meters or the Converted Meteorological
Visibility (CMV) is below 800 RVR unless RVR reporting is available for the runway of intended
use. (GM)
Auditor Actions
□ Identified/Assessed OM guidance that requires RVR reporting for approach/landing operations
when prevailing visibility is below 800 meters/CMV below 800 RVR (focus: availability of
guidance to flight crew; statement of prohibition).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight and flight simulator operations (focus: determination of approach/landing
RVR requirements).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Converted Meteorological Visibility (CMV).
The intent of this provision is to ensure:
• A conversion of meteorological visibility to RVR (CMV) is not used to establish any required
approach and landing RVR minimum less than 800 meters;
• RVR reporting is required for approach and landing operations to be conducted with any
RVR minima less than 800 meters.
FLT 3.7.3 The Operator shall have guidance that enables the flight crew to prepare and/or accept a
loadsheet with accurate aircraft weight/mass and balance calculations for each flight. Such guidance
shall:
(i) Assign responsibility to the PIC for ensuring the loadsheet content is satisfactory prior to
each flight;
(ii) Incorporate flight crew procedures for preparing or accepting last minute changes (LMC) to
the loadsheet, to include guidance for the maximum allowable difference between planned
and actual weights.
Auditor Actions
□ Identified/Assessed OM guidance/procedures for PIC/flight crew preparation/acceptance of
loadsheet (focus: instructions for determination of accurate loadsheet, preparing/accepting
LMCs, maximum allowable difference between planned/actual weights).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight operations (focus: flight crew preparation/acceptance of accurate
loadsheet).
□ Other Actions (Specify)
FLT 3.7.4 (Intentionally open)
FLT 3.7.5 The Operator shall have a description of the Air Traffic Services (ATS) Flight Plan, as
well as guidance and instructions for its use, that is accessible to the flight crew during flight
preparation and in flight. (GM).
Auditor Actions
□ Identified/Assessed OM description/guidance for preflight use of ATS flight plan (focus:
availability to flight crew; instructions for use of ATS flight plan in preflight preparation).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight operations (focus: accessibility/use of ATS flight plan during flight
preparation).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Air Traffic Services (ATS).
FLT 3.7.6 The Operator shall ensure an Operational Flight Plan (OFP) or equivalent document is
available for the flight crew during flight preparation and accessible to the flight crew during flight.
Auditor Actions
□ Identified/Assessed requirements for availability/accessibility/use of OFP or equivalent
document (focus: availability/accessibility to flight crew prior to/during flight).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight and flight simulator operations (focus: accessibility/use of OFP during flight
preparation and flight).
□ Other Actions (Specify)
FLT 3.7.7 The Operator shall ensure the OFP or equivalent document is accepted and signed,
using either manuscript or an approved electronic method, by the PIC during flight preparation. (GM)
Auditor Actions
□ Identified/Assessed OM guidance/procedures for PIC preflight acceptance of OFP (focus:
instructions for PIC acceptance; requirement for signature/approved electronic method of
acceptance).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight operations (focus: acceptance of OFP during flight preparation).
A PSR may coincide with the Final Decision Point used in Decision Point Planning or the Pre-
determined Point used in Pre-determined Point planning.
Guidance on flight planning methods including planning operations to isolated airports and guidance
related to the determination of a PSR is contained in the ICAO Flight Planning and Fuel Management
Manual (Doc 9976).
(iv) Is correctable in the case of an error provided each correction is identifiable and errors
remain legible.
Auditor Actions
□ Identified/Assessed OM guidance/procedures for use of ATL by flight crew (focus: availability to
flight crew; instructions for entering information in ATL).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight operations (focus: use of ATL).
□ Other Actions (Specify)
FLT 3.8.3 The Operator shall assign the PIC the authority to reject an aircraft prior to departure
of a flight if dissatisfied with any aspect of the airworthiness and/or maintenance status of the
aircraft. (GM)
Auditor Actions
□ Identified/Assessed OM guidance/procedures for acceptance/rejection of aircraft based on
airworthiness assessment (focus: delegation of authority to PIC; instructions for assessment of
airworthiness).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight operations (focus: use of ATL).
□ Other Actions (Specify)
Guidance
The intent of this provision is to ensure that PIC acceptance of an aircraft is based on a review of the
MEL/CDL, ATL and/or any other operator or State-approved sources of technical information
attesting to the mechanical state of the aircraft.
FLT 3.8.4–3.8.5 (Intentionally open)
FLT 3.8.6 The Operator shall ensure, prior to each flight, an exterior aircraft inspection (walk-
around) is performed by a member of the flight crew or delegated to a licensed aircraft maintenance
technician. If delegated, the Operator shall ensure the flight crew is notified prior to flight that the
inspection has been completed.
Auditor Actions
□ Identified/Assessed OM guidance/procedures for aircraft exterior inspection prior to each flight.
(focus: requirement to be conducted by flight crew or delegated to licensed maintenance
technician; requirement for flight crew notification if conducted by maintenance technician).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight operations (focus: aircraft exterior inspection).
□ Other Actions (Specify)
FLT 3.8.7A The Operator shall have guidance, published in the OM or other document(s) available
to the flight crew during flight preparation, that requires an exterior aircraft inspection (walk-around)
that focuses on safety-critical areas of the aircraft and ensures, as a minimum:
(i) Pitot and static ports are not damaged or obstructed;
(ii) Flight controls are not locked or disabled (as applicable, depending on aircraft type);
(iii) Frost, snow or ice is not present on critical surfaces;
(iv) Aircraft structure or structural components are not damaged. (GM)
Auditor Actions
□ Identified/Assessed OM guidance/procedures for aircraft exterior inspection prior to each flight
(focus: instructions for conduct of inspection; definition of safety-critical areas that must be
included).
Guidance
The briefing related to the specification in item ii) also typically addresses any applicable
requirements and restrictions for personnel seated adjacent to cabin emergency exits.
deplaning or cabin evacuation. Such persons are typically positioned near the boarding door(s) when
a passenger boarding bridge is being utilized or, when a boarding bridge is not in use, in the
location(s) most suitable for monitoring the safety of passengers that are embarking, on board or
disembarking the aircraft. Certain aircraft might be small enough to permit a qualified person to
monitor the safety of passengers embarking, on board or disembarking from outside the aircraft.
The specification in item iv) refers to the procedures for establishing a suitable method of
communication, which may be initiated by any applicable person. Acceptable procedural methods of
initiating and maintaining communication may include one or more of the following:
• The use of the aircraft inter-communication system, or;
• Direct person-to-person contact, or;
• Any other method of communication that ensures the flight crew or other suitably qualified
persons are able to expeditiously direct personnel to discontinue fueling operations for any
reason.
The specification in item iv) may be fulfilled by a flight crew member or other suitably qualified person
when aircraft refueling is conducted or supervised by the flight crew.
FLT 3.9.3 If the Operator conducts passenger flights with or without cabin crew, and transports
passengers that require special handling, the Operator shall have a policy and associated
procedures for the acceptance and onboard handling of such passengers by the flight crew. The
policy and procedures shall be in accordance with applicable regulations and as a minimum address,
as applicable:
(i) Intoxicated and/or abusive passengers;
(ii) Passengers with disabilities or reduced mobility;
(iii) Passengers with injuries or illness;
(iv) Infants and unaccompanied children;
(v) Inadmissible passengers;
(vi) Deportees;
(vii) Passengers in custody. (GM)
Auditor Actions
□ Identified/Assessed OM policy/procedures for passengers that require special handling (focus:
description of flight crew actions; definition of types of passengers that require special handling).
□ Interviewed responsible manager(s) in flight operations.
□ Coordinated with cabin/ground operations (focus: complementary policy/procedures for
treatment of special handling passengers).
□ Observed line flight operations (focus: treatment of special handling passengers).
□ Other Actions (Specify)
Guidance
The principle intent of this provision is to ensure the appropriate acceptance and onboard handling of
passengers regardless of aircraft type, crew complement or complexity of the operation. An operator
typically provides guidance to the flight crew, commensurate with any assigned responsibilities
relative to passenger handling, to address the acceptance or non-acceptance of passengers
requiring special handling as defined by this provision. Such guidance also typically defines the
conditions necessary to accept or deny boarding to a passenger.
The specifications in items i), v), vi) and vii) might require guidance in the OM that addresses the
proper use of restraint devices, unless such devices are prohibited by the Authority or their use is
impractical due to lack of appropriate crew members.
FLT 3.9.4 If the carriage of weapons on board an aircraft by law enforcement officers and other
authorized persons acting in the performance of their duties is approved by the Operator, State
and/or other applicable authorities, the Operator shall have a procedure to ensure the PIC is notified
prior to the departure of a flight. Such notification shall include:
(i) The number of authorized armed persons on board the aircraft;
(ii) If permitted by the state(s) involved, the location(s) of such persons. (GM)
Auditor Actions
□ Identified/Assessed OM policy/procedures for carriage of weapons by law enforcement/other
persons as approved by State (focus: flight crew duties/responsibilities; requirement for/content
of notification to flight crew).
□ Interviewed responsible manager(s) in flight operations.
□ Coordinated with cabin/ground operations (focus: complementary policy/procedures for
notification of onboard weapons).
□ Observed line flight operations (focus: notification of onboard weapons).
□ Other Actions (Specify)
Guidance
The term applicable authorities in this provision refers to authorities that have jurisdiction over
international operations conducted by an operator over the high seas or the territory of a state that is
other than the State of the Operator.
FLT 3.9.5 (Intentionally open)
FLT 3.9.6 If the Operator conducts flights from any airport when conditions are conducive to
ground aircraft icing, the Operator shall have de-/anti-Icing policies and procedures published in the
OM or in other documents that are available to the flight crew during flight preparation and accessible
to the flight crew during flight. Such policies and procedures shall address any flight crew duties and
responsibilities related to de-/anti-Icing and include:
(i) Holdover Time tables;
(ii) A requirement for a member of the flight crew or qualified ground personnel to perform a
visual check of the wings before takeoff, if any contamination is suspected;
(iii) A requirement that takeoff will not commence unless the critical surfaces are clear of any
deposits that might adversely affect the performance and/or controllability of the aircraft;
(iv) A statement that delegates authority to the PIC to order De-/Anti-icing whenever deemed
necessary. (GM)
Note: The specifications of this provision are applicable to commercial and/or non-commercial
operations.
Auditor Actions
□ Identified/Assessed OM policy/procedures for aircraft de-/anti-icing of aircraft (focus:
availability/accessibility to flight crew prior to/during flight; description of flight crew
authority/duties/responsibilities; statement that requires critical surfaces to be clear of ice prior to
takeoff).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight operations (focus: operations in ground icing conditions; de-/anti-icing
operations).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definitions of De-/Anti-icing Program and Holdover Time.
The intent of this provision is to ensure flight crew members comply with the clean aircraft concept
prior to takeoff anytime there is a potential for the accretion of ice on aircraft critical surfaces during
ground operations.
Refer to GRH 4.2.1 located in ISM Section 6 for specifications and associated guidance related to the
establishment and maintenance of a De-/Anti-icing Program.
Qualified ground personnel specified in item ii) are typically used to perform a visual wing check in
instances when the wings are not visible to the flight crew from the interior of the aircraft (e.g., cargo
aircraft operations).
The surfaces specified in item iii) include: wings, flight controls, engine inlets, fuselage surfaces in
front of engines or other areas defined in the AOM.
FLT 3.9.7 If the Operator does not conduct flights from any airport when conditions are conducive
to ground aircraft icing, the Operator shall have guidance published in the OM or other document that
is available to the flight crew during flight preparation and accessible to the flight crew during flight.
Such guidance shall include:
(i) A description of meteorological and other conditions that are conducive to ground aircraft
icing and/or the formation of ice on aircraft critical surfaces;
(ii) A prohibition from operating an aircraft from any airport when conditions conducive to
ground aircraft icing exist. (GM)
Note: The specifications of this provision are applicable to commercial and/or non-commercial
operations.
Auditor Actions
□ Identified/Assessed OM guidance that addresses/prohibits operations in ground icing
conditions (focus: availability/accessibility to flight crew prior to/during flight; description of
conditions conducive to ground aircraft icing; statement that prohibits aircraft operations in
conditions conducive to ground icing).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight operations (focus: operations in ground icing conditions).
□ Other Actions (Specify)
Guidance
The intent of this provision is to preclude flight operations from airports when conditions conducive to
ground aircraft icing exist and there is an absence of de-/anti-icing capability and/or appropriate
policies and procedures that will ensure compliance with the clean aircraft concept prior to takeoff.
FLT 3.9.8 If the Operator transports dangerous goods as cargo, the Operator shall ensure
information and guidance that enable the flight crew to carry out duties and responsibilities related to
the transport of dangerous goods is published or referenced in the OM and included in the onboard
library. Such guidance shall include, as a minimum:
(i) General policies and procedures;
(ii) Duties and responsibilities;
(iii) As applicable, preflight acceptance requirements;
(iv) Flight crew written notification requirements;
(v) Dangerous goods incident and/or emergency response procedures. (GM)
Auditor Actions
□ Identified/Assessed OM guidance/procedures associated with transport of dangerous goods
(focus: included in onboard library; description of flight crew duties/responsibilities;
acceptance/notification requirements).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight operations (focus: provision/receipt/acknowledgement of onboard
dangerous goods).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definitions of Dangerous Goods Regulations (DGR) and NOTOC
(Notification to Captain).
An operator, in accordance with requirements of the Authority, typically develops flight crew guidance
related to the transport of dangerous goods based on technical information from one or more source
reference documents, to include:
• IATA Dangerous Goods Regulations (DGR);
• ICAO Doc. 9481 AN/928, Emergency Response Guidance for Aircraft Incidents Involving
Dangerous Goods;
• An equivalent dangerous goods manual, dangerous goods emergency response guide or
other reference document approved or accepted by the Authority for the development of
flight crew guidance related to the transportation of dangerous goods by air.
The specification in item iii) refers to procedures and information formulated to assist each applicable
flight crew member in performing or directly supervising the acceptance of dangerous goods for
transport on an aircraft. Such information might include, but not limited to:
• Details and locations of cargo compartments;
• The maximum quantity of dry ice permitted in each compartment;
• If radioactive materials are to be carried, instructions on loading;
• Dangerous goods reporting requirements.
Item iii) is only applicable to flight crew members assigned such responsibilities by the State or the
operator.
The specification in item iv) refers to PIC and/or flight crew duties and responsibilities related to the
acquisition and review of the NOTOC (Notification to Captain).
FLT 3.9.9 If the Operator does not transport dangerous goods as cargo, the Operator shall have
guidance for the flight crew that includes procedures for response to dangerous goods incidents.
Auditor Actions
□ Identified/Assessed OM guidance/procedures that address response to dangerous goods
incidents (focus: description of flight crew duties/responsibilities in the event of dangerous goods
incidents).
□ Interviewed responsible manager(s) in flight operations.
□ Examined selected flight crew dangerous goods incident reports.
□ Other Actions (Specify)
The specifications of DSP 3.2.9A also refer to the type of flight plan to be filed in instances where
certain portions of a flight will be conducted under VFR. In some cases it may be possible to identify
VFR portions in a predominantly IFR flight plan (e.g. X and Y designation on an ICAO flight plan). In
other cases, an IFR Flight Plan must be filed for all flights and an instrument clearance obtained or
cancelled en route.
FLT 3.10.3 (Intentionally open)
FLT 3.10.4 The Operator shall have guidance that addresses the use of standard radio
phraseology when communicating with ATC, the acceptance and readback of ATC clearances and,
when necessary, the clarification of such clearances to ensure understanding. Such guidance shall
include, as a minimum:
(i) A requirement for the use of the call sign;
(ii) A requirement for at least two flight crew members to monitor and confirm clearances to
ensure a mutual (flight crew) understanding of accepted clearances under circumstances,
as determined by the operator or flight crew, when a missed or misunderstood clearance
could pose a safety risk to the flight;
(iii) A requirement to clarify clearances with ATC whenever any flight crew member is in doubt
regarding the clearance or instruction received. (GM)
Auditor Actions
□ Identified/Assessed OM requirement/guidance for standard radio phraseology in
communication with ATC (focus: instructions/procedures for flight crew communications with
ATC; definition/use of standard phraseology).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight operations (focus: ATC communications; use of standard phraseology).
□ Other Actions (Specify)
Guidance
The intent of this provision is for an operator to have policies and procedures that ensure:
• The use of standard radio phraseology;
• ATC clearances are clearly understood during times of increased operational risk.
The specification in item ii) refers to situations when a missed or misunderstood clearance could
pose a safety risk to the flight (e.g. inadequate terrain clearance, runway incursion, loss of
separation). ATC clearances that have the potential to pose such safety risks, if misunderstood by
the flight crew, typically include the following:
• Heading, altitude/flight level, assigned route/waypoint changes;
• Frequency changes during critical phases of flight;
• Instructions for any operation on or near a runway.
FLT 3.10.5 The Operator shall have guidance that requires the flight crew to maintain a radio
listening watch on the frequencies appropriate for the area of operation and as required by the
applicable authorities. Such guidance shall include, as a minimum, an additional requirement for the
flight crew to monitor:
(i) VHF emergency frequency (121.5 MHz):
(a) On long-range over-water flights or on flights that require the carriage of an
emergency locator transmitter (ELT), except during those periods when aircraft are
carrying out communications on other VHF channels, or when airborne equipment
limitations or flight deck duties do not permit simultaneous guarding of two
channels;
(b) If required by the applicable authorities, in areas or over routes where the possibility
of military intercept or other hazardous situations exist.
(ii) If required by the applicable authorities, the appropriate common frequency used for in-flight
communication in designated airspace without ATC coverage. (GM)
Auditor Actions
□ Identified/Assessed OM requirements/guidance/procedures for monitoring of radio frequencies
appropriate to areas of operations (focus: instructions for flight crew monitoring of radio
frequencies; definition of frequencies to be monitored).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight operations (focus: monitoring of radio frequencies).
□ Other Actions (Specify)
Guidance
Refer to the IRM for definitions of In Flight Broadcast Procedures (IFBP), Long-range Over-water
Flights, Selective Calling (SELCAL) and Satellite Communications (SATCOM).
The intent of this provision is to ensure flight crews maintain a radio listening watch on those VHF
and/or HF frequencies that are appropriate for the area of operation and are in accordance with the
requirements of the applicable authorities.
The specification in item ii) refers to the monitoring of the In Flight Broadcast Procedures (IFBP)
frequency in areas of the world where such procedures are required.
The use of SELCAL or SATCOM could relieve the radio listening watch responsibility of this
provision, but not the requirement for VHF emergency and/or IFBP frequency monitoring.
The continuous monitoring of a company discrete frequency or exclusive dedication of a secondary
radio to ACARs does not take precedence over the monitoring of requirements specified in this
provision.
Applicable authorities include those authorities that have jurisdiction over international operations
conducted by an operator over the high seas or the territory of a state that is other than the State of
the Operator.
FLT 3.10.6 The Operator shall have procedures and/or limitations that address operations into and
out of uncontrolled airspace and/or airports, to include, if applicable, a prohibition if such operations
are not permitted in accordance with restrictions of the AOC or equivalent documents. (GM)
Auditor Actions
□ Identified/Assessed OM procedures/limitations for operations into/out of uncontrolled
airspace/airports (focus: flight crew actions/responsibilities for airspace/airport operations with no
ATC).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight operations (focus: uncontrolled airspace/airport operations)..
□ Other Actions (Specify)
Guidance
The intent of this provision is to ensure procedures and limitations address operations in uncontrolled
airspace or at uncontrolled airports, and include a prohibition for such operations if not authorized by
either the Authority or the operator.
An uncontrolled airport is an airport without an operating control tower.
A controlled airport is an airport with a manned and operating control tower surrounded by controlled
airspace.
Procedures and limitations typically include aircraft position radio broadcast procedures, VFR
weather requirements and the ability to receive ATC clearance within a specified time/distance from
the departure airport.
FLT 3.10.7 The Operator shall have guidance that enables the flight crew to determine differences
in rules and procedures for any airspace of intended use, to include, as a minimum, an explanation
of the differences between prevailing or local airspace rules and ICAO airspace rules, where
applicable. (GM)
Auditor Actions
□ Identified/Assessed OM requirement/guidance for determining differences in rules/procedures
in airspace of intended use (focus: instructions for flight crew determination of airspace
rules/procedures, differences between prevailing/local and ICAO rules).
□ Interviewed responsible manager(s) in flight operations.
□ Other Actions (Specify)
Guidance
The specification of this provision ensures flight crews that operate in airspace(s) with different rules
have those differences explained in the OM.
Airspace(s) of intended use typically includes ICAO, FAA, State or any other local airspace subject to
the operations of the operator.
FLT 3.11.3 The Operator shall have a collision avoidance policy that encourages the flight crew to
maintain vigilance for conflicting visual traffic (“see and avoid”). (GM)
Auditor Actions
□ Identified/Assessed collision avoidance policy that encourages vigilance for conflicting visual
traffic (i.e. “see and avoid") (focus: availability to flight crew; instructions for flight crew traffic
identification/avoidance).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight operations (focus: visual vigilance for conflicting traffic)..
□ Other Actions (Specify)
Guidance
This policy complements TCAS collision avoidance procedures.
FLT 3.11.4 The Operator shall ensure minimum flight altitude information applicable to all phases
of a flight, including guidance that specifies when descent below any applicable prescribed minimum
altitude is permissible, is made available to the flight crew along with instructions for the use of such
information. (GM)
Auditor Actions
□ Identified/Assessed OM guidance that specifies when descent below applicable prescribed
minimum altitude is permissible (focus: availability of minimum altitude information to flight crew
during flight; instructions/procedures for adherence to/descent below minimum altitudes all
phases of flight).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight and flight simulator operations (focus: adherence to minimum altitudes).
□ Other Actions (Specify)
Guidance
Minimum prescribed safety altitudes typically include:
• Minimum Safety Altitude (MSA);
• Minimum Descent Altitude/Height (MDA/H);
• Minimum En route Altitude (MEA);
• Minimum Obstruction Clearance Altitude (MOCA);
• Minimum Off-Route Altitude (MORA);
• Minimum Vectoring Altitude (MVA);
• Any other minimum altitudes prescribed by the Authority.
FLT 3.11.5 The Operator shall have guidance that requires flight crews to monitor meteorological
conditions during the en route phase of flight, to include current weather and forecasts for:
(i) Destination airport;
(ii) Destination alternate airport(s), if applicable;
(iii) En route alternate airports(s), if applicable.
Auditor Actions
□ Identified/Assessed OM requirement/guidance for monitoring meteorological conditions during
the en route phase of flight (focus: instructions for flight crew monitoring of en route
meteorological conditions, current/forecast weather for destination/alternate airports).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight operations (focus: monitoring en route/airport weather conditions).
□ Other Actions (Specify)
FLT 3.11.6 The Operator shall have guidance and procedures to ensure flight crews monitor flight
time and fuel burn for the purposes of identifying trends and for comparison to the OFP. (GM)
Auditor Actions
□ Identified/Assessed OM requirement/guidance for monitoring flight time/fuel burn to identify
trends, for comparison to OFP (focus: instructions/procedure for flight crew monitoring of en
route fuel burn/identifying usage trends/tracking usage against OFP).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight operations (focus: en route fuel monitoring/tracking).
□ Other Actions (Specify)
Guidance
The specifications of this provision ensure fuel and time trends are monitored and compared against
the OFP.
Such guidance and procedures typically address or include:
• An interval, in accordance with operator and/or State requirements, for the flight crew to
record on the OFP the fuel quantity and time over waypoints;
• A description of any equivalent means for monitoring flight progress and/or recording the fuel
quantity over waypoints;
• Equivalent means of recording fuel and time data include FMS, ACARS or other automated
methods for recording data.
FLT 3.11.7 The Operator shall have guidance that requires the PIC to monitor fuel during flight to
ensure a fuel quantity upon landing that is not less than final reserve fuel. (GM)
Auditor Actions
□ Identified/Assessed OM requirement/guidance for monitoring en route fuel to ensure landing
with not less than final reserve fuel (focus: instructions/procedure for flight crew fuel monitoring to
ensure landing with final reserve fuel as specified in DSP 4.3.12).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight operations (focus: en route fuel monitoring/tracking).
□ Other Actions (Specify)
Guidance
Refer to FLT 3.14.16 and FLT 3.14.17 for actions to be taken by the PIC in the event the final reserve
minimum fuel quantity specified in DSP 4.3.12 cannot be protected in flight and preserved upon
landing.
FLT 3.11.8 If the Operator is authorized to conduct RVSM operations and/or RNP operations in
airspace that requires the maintenance of a particular RNP, the Operator shall have guidance that
includes procedures to ensure the proper conduct of such operations. Such guidance shall address,
as a minimum:
(i) Required ground and airborne equipment;
(ii) Operating limitations and procedures;
(iii) As applicable, operating minima. (GM)
Auditor Actions
□ Identified authorization to conduct RVSM/RNP operations in airspace that requires maintenance
of a particular RNP.
□ Identified/Assessed OM guidance/procedures for the conduct of RVSM/RNP operations (focus:
definition of required ground/airborne equipment, operating limitations/procedures, applicable
operating minima).
□ Interviewed responsible manager(s) in flight operations.
Guidance
The intent of item ii) of this provision is to ensure flight crew are knowledgeable about diversion
airport options and prevailing weather conditions appropriate for the type of operation conducted.
The intent of item iii) of this provision is to ensure a larger strategy exists to protect a diversion
regardless of whether the diversion is for technical (airplane system- or engine-related) or non-
technical reasons.
An operator, in accordance with requirements of the Authority, typically uses technical guidance for
the conduct of operations beyond 60 minutes, from a point on a route to an en route alternate airport,
including EDTO. Such guidance might be derived from one or more of the following source
references, as applicable:
• ICAO Annex 6, Amendment 36, Attachment D: Guidance for Operations by Turbine Engine
Aeroplanes Beyond 60 minutes to an En-route Alternate Aerodrome Including Extended
Diversion Time Operations (EDTO);
• ICAO Flight Planning and Fuel Management Manual (Doc 9976);
• FAA Advisory Circular - AC No: 120-42B: Extended Operations (ETOPS and Polar
Operations), Effective 6/13/08;
• EU-OPS AMC 20-6 rev. 2 Effective: 12/23/2010: Extended Range Operation with Two-
Engine Aeroplanes, ETOPS Certification and Operation;
• Any equivalent reference document approved or accepted by the Authority for the purpose of
providing guidance for the conduct of flight operations by turbine engine aircraft beyond
60 minutes to an en-route alternate airport including EDTO.
FLT 3.11.11 If the Operator engages in specialized navigation (MNPS, AMU), the Operator shall
have guidance that includes procedures to ensure the proper conduct of such operations and
addresses, as a minimum:
(i) Required ground and airborne equipment;
(ii) Operating limitations and procedures. (GM)
Auditor Actions
□ Identified authorization to conduct specialized navigation (MNPS/AMU) operations.
□ Identified/Assessed OM guidance/procedures for the conduct of specialized navigation
operations (focus: procedures/limitations for conduct of operations; requirements for
ground/airborne equipment).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight and flight simulator operations (focus: conduct of specialized navigation
operations).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definitions of Areas of Magnetic Unreliability (AMU) and Minimum Navigation
Performance Specifications (MNPS).
FLT 3.11.12–3.11.15 (Intentionally open)
Auditor Actions
□ Identified/Assessed principles of CRM published in OM/other document (focus: availability to
flight crew; requirement for application of CRM in line operations).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight and flight simulator operations (focus: application of CRM principles).
□ Other Actions (Specify)
FLT 3.11.17 The Operator shall have a policy and procedures that define a sterile flight deck during
critical phases of flight, to include:
(i) A protocol for intra-flight deck communication;
(ii) If the Operator conducts passenger flights with cabin crew, a protocol for communication
between the flight crew and cabin crew;
(iii) The mandatory use of headsets and boom microphones for communication with ATC;
(iv) A restriction of flight crew activities to essential operational matters. (GM)
Auditor Actions
□ Identified/Assessed OM policy/requirement/procedures for sterile flight deck (focus: procedures
associated with sterile flight deck; definition of protocols/requirements/restrictions).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight operations (focus: adherence to sterile flight deck).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Sterile Flight Deck and Critical Phase of Flight.
The specifications of this provision require an operator to ensure the OM defines the specific phases
of flight when the operational state of the flight deck is to be “sterile.”
FLT 3.11.18 The Operator shall have a task sharing policy and guidance that defines and
addresses the division of duties related to the performance and prioritization of flight crew member
operational tasks, to include, as a minimum:
(i) Instructions for the use of checklists prior to, during and after all phases of flight, and in
abnormal and emergency situations, to ensure compliance with the procedures contained in
the OM and provisions of the aircraft certificate of airworthiness;
(ii) PM/PF duties for all phases of flight, to include normal, abnormal and emergency situations;
(iii) PM/PF actions during manual and automatic flight;
(iv) Flight and cabin crew duties during situations that require coordination, to include, as a
minimum, emergency evacuation, medical emergency and incapacitated flight crew
member. (GM)
Auditor Actions
□ Identified/Assessed OM policy/requirement/guidance for sharing/prioritization in performance of
flight crew operational tasks (focus: guidance that addresses use of checklists; defines PF/PM
duties/task sharing; defines flight/cabin crew duties/task sharing).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight and flight simulator operations (focus: application of flight crew task
sharing/prioritization).
□ Other Action (Specify)
Guidance
The intent of this provision is to ensure flight crew duties are defined and appropriately divided, and
that compliance with all applicable checklists contained in the AOM, MEL and CDL occurs in
accordance with the operator's task sharing policy.
Elements of task sharing are described in the following table.
Task sharing is observed during most phases of flight and addresses areas such as:
• Philosophy for the use of checklists;
• Performance calculations;
• Automated flight procedures for flight crew;
• Manual flight procedures for flight crew;
• Flight crew briefings;
• Administrative duties at the appropriate times (such as top of descent and prior to
commencing approach).
Task sharing is applicable during emergency situations such as:
• Rejected takeoff;
• Engine failure or fire at V1;
• TCAS/ACAS resolution advisory (RA);
• GPWS Alert;
• Emergency descent.
Task sharing is applicable during emergency situations that require coordination with the cabin crew
such as:
• Emergency evacuation;
• Medical emergency;
• Flight crew member incapacitation.
The term Pilot Monitoring (PM) has the same meaning as the term Pilot Not Flying (PNF) for the
purpose of applying the specifications of this provision.
The term “abnormal” is used to describe a condition or situation (e.g. abnormal airframe vibration,
abnormal landing configuration).
The terms “normal” and “non-normal/emergency” typically refer to AOM checklists, procedures
and/or maneuvers. The term “non-normal” includes AOM emergency checklists and/or procedures
(i.e. an emergency procedure is a subset of non-normal).
The terms can also be used to describe an event, situation or operation that would be addressed by
normal or non-normal/emergency procedures or checklists. When used in this manner, the terms
may be separated by forward slash marks (e.g. normal/non-normal/emergency).
The term “emergency” used alone refers to declarations and non-AOM procedures.
FLT 3.11.19 (Intentionally open)
FLT 3.11.20 The Operator shall have a policy and procedures that require flight crew members to
crosscheck and confirm critical actions during normal, abnormal and emergency situations, to
include:
(i) Aircraft configuration changes (landing gear, wing flaps, speedbrakes);
(ii) Altimeter bug and airspeed bug settings, as applicable;
(iii) Altimeter subscale settings;
(iv) Altitude (window) selections;
(v) Transfer of control of the aircraft;
(vi) Changes to the Automated Flight System (AFS)/Flight Management System (FMS) and
radio navigation aids during the departure and or approach phases of flight;
FLT 3.11.22 The Operator shall have an automation policy with associated guidance and
procedures that address the use of aircraft automated flight and navigation systems, to include:
(i) Flight crew monitoring of the automated flight and navigation systems (AFS) to ensure
appropriate aircraft response to inputs by:
(a) Cross-checking mode control panel status;
(b) Observing the results of any mode changes;
(c) Supervising the resulting guidance and aircraft response.
(ii) The use of a level of automation appropriate for the task, to include manual flight when
aircraft response is not appropriate or adequate.
Auditor Actions
□ Identified/Assessed OM policy/guidance/procedures for use of aircraft automated
flight/navigation systems (focus: instruction/procedures for flight crew use/monitoring of
automation, selection of appropriate mode of flight/navigation automation).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight and flight simulator operations (focus: management of flight automation; use
of level appropriate for conditions).
□ Other Actions (Specify)
FLT 3.11.23 The Operator shall have guidance that defines and specifies the requirements for the
conduct and content of the briefing to be accomplished by the flight crew prior to any departure and
approach. Such briefing shall address and include, as a minimum:
(i) The technical status of the aircraft unless reviewed in conjunction with another checklist or
procedure;
(ii) Normal and non-normal departure and approach considerations;
(iii) A flight deck jump seat occupant safety briefing. (GM)
Auditor Actions
□ Identified/Assessed requirement/guidance for conduct of departure/approach briefing (focus:
instruction/procedures for flight crew departure/approach briefing; definition of purpose/content
of briefings).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight and flight simulator operations (focus: departure/approach briefings).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Jump Seat.
Normal and non-normal departure and approach considerations include, as appropriate for each
phase and each flight:
• Fuel status;
• Airport/taxi diagrams;
• Meteorological conditions;
• NOTAMS;
• LVO procedures;
• Departure/approach charts;
• Minimum safe altitudes and terrain;
• Use of automation;
• Takeoff/landing (flaps, autobrakes and stopping distances);
• Missed approach/go-around and alternates;
• Special conditions and operations (e.g., crew familiarization with the route or airport flown,
hazardous materials, environmental, non-standard noise abatement, etc.).
Non-normal departure/approach considerations include items, such as: engine-out procedures,
mountainous terrain or airspace constraints.
Briefings can be structured in order to encourage crew member feedback/participation.
FLT 3.11.24–3.11.27 (Intentionally open)
Guidance
Refer to the IRM for the definition of Altimeter Reference Setting, which includes definitions for QNE,
QFE and QNH.
Information related to barometric reference setting instructions appropriate for specific areas of
operation can be found in one or more of the following documents:
• ICAO Doc 8168–Procedures for Air Navigation Services–Aircraft Operations (PANS-OPS),
Volume 1, Flight Procedures, Part III, Section 1;
• U.S. Department of Transportation–Federal Aviation Administration–Aeronautical
Information Manual (AIM)–Official Guide to Basic Flight Information and ATC Procedures,
Section 2. Altimeter Setting Procedures;
• The Aeronautical Information Publication (AIP) of the State;
• Any other State-approved or State-accepted altimetry reference.
FLT 3.11.30 The Operator should have guidance and procedures that include a requirement for
barometric altimeters, referenced to QNH, to be used as the sole barometric altitude reference for the
takeoff, approach and landing phases of flight.
Auditor Actions
□ Identified/Assessed OM requirement/guidance/procedures for barometric altimeter referenced
to QNH for takeoff/approach/landing phases of flight (focus: instructions/procedures for flight
crew to set QNH for takeoff/approach/landing).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight and flight simulator operations (focus: use/setting of QNH for
takeoff/approach/landing).
□ Other Actions (Specify)
FLT 3.11.31 If the Operator engages in operations that require metric/imperial (ft) conversions for
barometric altimeter readings, the Operator shall have guidance and procedures that ensure the
proper computation and application of such conversions. (GM)
Auditor Actions
□ Identified/Assessed OM guidance/procedures for metric/imperial (ft) conversions for barometric
altimeter readings (focus: instructions/procedures for flight crew use/application of barometric
altimeter conversions).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight operations (focus: application of barometric altimeter conversion).
□ Other Actions (Specify)
Guidance
The operator may provide tables, charts or other means for completing the required conversion.
FLT 3.11.32 The Operator shall have guidance that enables the flight crew to correct for potential
errors in altimetry and that addresses:
(i) The effects of Outside Air Temperature (OAT) that is significantly lower than standard
temperature;
(ii) Maximum allowable barometric altimeter errors:
(a) Referenced to field elevation;
(b) Compared to other altimeters;
(c) Permissible to meet RVSM limitations. (GM)
Auditor Actions
□ Identified/Assessed OM guidance that addresses avoidance of potential altimetry errors (focus:
instructions/procedures for flight crew avoidance of barometric altimeter errors; definition of
maximum allowable barometric altimeter errors).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight operations (focus: avoidance of barometric altimeter errors).
□ Other Actions (Specify)
Guidance
The intent of this provision is to ensure that potential errors in altimetry are identified and corrected
when necessary.
The specification in item i) refers to temperature compensation corrections applied to ensure
obstacle clearance in conditions of extreme cold (typically starting at -10 C). Such corrections may be
applied manually by the flight crew (e.g. temperature correction charts) or automatically by onboard
systems (e.g. Air Data Computer).
The operator may provide tables, charts or other means to address potential errors in altimetry.
FLT 3.11.33–3.11.37 (Intentionally open)
Auditor Actions
□ Identified/Assessed OM policy/guidance for windshear avoidance/encounter
recovery/response to predictive/reactive alerts (focus: flight crew windshear avoidance/recovery
procedures).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight and flight simulator operations (focus: windshear
awareness/avoidance/recovery).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Airborne Windshear Warning System, which includes definitions
for Predictive Alert and Reactive Alert.
FLT 3.11.40 The Operator shall have guidance that addresses wake turbulence, to include
procedures for encounter avoidance. (GM)
Auditor Actions
□ Identified/Assessed OM guidance for wake turbulence avoidance/encounter recovery (focus:
flight crew wake turbulence avoidance/recovery procedures).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight operations (focus: wake turbulence awareness/avoidance/recovery).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Wake Turbulence.
FLT 3.11.41–3.11.45 (Intentionally open)
□ Observed line flight and flight simulator operations (focus: compliance with wind component
limitations).
□ Other Actions (Specify)
Guidance
The intent of this provision is to ensure the operator provides wind component limitations for the
phases of flight specified in the body of the provision (e.g. maximum crosswind component for
landing). Additionally, the provision ensures the operator provides wind component limitations under
the conditions specified in the sub-specifications (e.g. maximum crosswind component for landing on
a contaminated runway). In either case such values cannot exceed those demonstrated or
recommended by the OEM.
Contaminated runways are typically defined by a specific contaminant type/depth or equivalent
braking action report.
FLT 3.11.48 The Operator shall have guidance that specifies a minimum aircraft height above
ground level (AGL) or above airport level (AAL) for commencing a turn after takeoff. (GM)
Auditor Actions
□ Identified/Assessed OM guidance that specifies a minimum aircraft height above ground level
(AGL)/above airport level (AAL) for commencing a turn after takeoff (focus:
requirement/procedures for flight crew compliance with minimum altitude limitations for turn after
takeoff).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight and flight simulator operations (focus: compliance with turn-after-takeoff
altitude limitations).
□ Other Actions (Specify)
Guidance
Values typically vary depending on the operator, or could include exceptions covering special airport
operations.
FLT 3.11.49 The Operator shall have guidance for the use of oxygen masks, to include a
requirement for the flight crew to use supplemental oxygen whenever, either:
(i) The cabin altitude exceeds 10,000 feet or the cabin atmospheric pressure is less than
700 hPa, or
(ii) If permitted by the State and applicable authorities, the cabin altitude exceeds 10,000 ft. or
the cabin atmospheric pressure is less than 700 hPa for a period in excess of 30 minutes
and for any period the cabin altitude exceeds 13, 000 ft. or the cabin atmospheric pressure
is less than 620 hPa. (GM)
Auditor Actions
□ Identified/Assessed OM requirement/guidance for flight crew use of supplemental oxygen
(focus: requirement/procedures for flight crew use of oxygen masks; definition of conditions that
require use of oxygen).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight and flight simulator operations (focus: flight crew use of oxygen
masks/supplemental oxygen).
□ Other Actions (Specify)
Guidance
Applicable authorities include those authorities that have jurisdiction over international operations
conducted by an operator over the high seas or the territory of a state that is other than the State of
the Operator.
FLT 3.11.50 The Operator shall have guidance that requires flight crews, when operating an
aircraft at low heights AGL, to restrict rates of descent for the purposes of reducing terrain closure
rate and increasing recognition/response time in the event of an unintentional conflict with
terrain. (GM)
Auditor Actions
□ Identified/Assessed OM requirement/guidance for restricting descent rates when operating at
low altitudes (focus: requirement/procedures for flight crew to restrict descent rates at low
altitudes).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight and flight simulator operations (focus: compliance with descent rate
restriction at low altitudes).
□ Other Actions (Specify)
Guidance
The intent of this provision is to preclude CFIT situations when a crew, operating an aircraft at high
rates of descent and temporarily distracted from altitude monitoring by unexpected events, would not
have:
• Sufficient recognition or alert time to realize that terrain is rapidly approaching or;
• Sufficient response time to accomplish an aircraft escape maneuver once potential terrain
conflict is recognized.
The low heights AGL specified in this provision are those altitudes where high descent rates can
result in excessive rates of terrain closure.
Stabilized approach criteria provide conformity with the specifications of this provision for the
approach phase of flight only. The specifications of this provision also require descent rate guidance
be provided for other descents where terrain closure rate could significantly reduce recognition and
response time.
The description of GPWS sink rate mode does not address the specifications of this provision.
FLT 3.11.51 The Operator shall have guidance and applicable data to enable the flight crew to
determine or compute aircraft performance for all phases of the flight. (GM)
Auditor Actions
□ Identified/Assessed OM guidance for use of data to determine/compute aircraft performance for
all phases of the flight (focus: instructions/procedures for flight crew use of aircraft performance
data).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight and flight simulator operations (focus: computation of relevant aircraft
performance).
□ Other Actions (Specify)
Guidance
The specifications of this provision may be satisfied by an automated or electronic means described
in the OM.
FLT 3.11.52 The Operator shall have guidance that addresses the use of flight data recorders
(FDR) and cockpit voice recorders (CVR) to ensure the:
(i) FDR is not intentionally switched off during flight time by the flight crew;
(ii) FDR and/or CVR are only switched off by the flight crew after a flight when required to
preserve data in the event of an accident or serious incident. (GM)
Auditor Actions
□ Identified/Assessed OM guidance that addresses use/control of FDR/CVR, preservation of
FDR/CVR data (focus: instructions/procedures for flight crew for ensuring required preservation
of FDR/CVR data).
□ Interviewed responsible manager(s) in flight operations.
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definitions of Flight Data Recorder (FDR), Cockpit Voice Recorder (CVR),
Accident, Incident and Serious Incident.
The definition of accident, incident or serious incident could vary according to the state.
FLT 3.11.53–3.11.57 (Intentionally open)
□ Observed line flight and flight simulator operations (focus: stabilized approach).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Flight Data Analysis (FDA) Program.
The intent of this provision is for the operator to implement a stabilized approach policy, as well as
have guidance, criteria and procedures that ensure the maintenance of the intended lateral and
vertical flight path during visual approaches and/or as depicted in published approach procedures
without excessive maneuvering. The parameters to be considered at the 1000 ft. AAL and 500 ft.
gates as well as in the definition of a stabilized approach are listed in items iii) through vi) of the
provision.
The specifications in item i) permit an operator, in accordance with operational requirements
approved or accepted by the Authority, to establish stabilization criteria for heights lower than 1000 ft.
AAL, but no lower than 500 ft. AAL (IMC or VMC), for approaches designated by the operator and/or
State where:
• Lower minimum approach stabilization heights are authorized for turbo-propeller aircraft
operations (e.g., 500 feet AAL on VMC/IMC approaches), and/or
• Maneuvering at a lower height AAL is required to meet instrument or other charted approach
constraints (e.g. RNAV/RNP approaches, circling approaches and charted visual
approaches), and/or
• Aircraft are required to comply with ATC speed constraints on final approach, and/or
• Deviations from selected approach stabilization criteria at a height lower than 1000 feet AAL,
but above 500 feet AAL, are operationally required, and the operator can demonstrate pilot
adherence to its stabilized approach policy via a continually monitored, managed and active
flight data analysis (FDA) program.
The criteria used to conform to the specifications in item vi) also typically address the maneuvering
that may be required in accordance with a charted visual or instrument approach procedure.
FLT 3.11.60 The Operator shall have a policy that requires the flight crew to execute a missed
approach or go-around if the aircraft is not stabilized in accordance with criteria established by the
Operator. (GM)
Auditor Actions
□ Identified/Assessed OM policy/requirements for execution of a missed approach/go-around
when approach not stabilized in accordance with established criteria (focus: flight crew
guidance/procedures for execution of a missed approach/go-around).
□ Interviewed responsible manager(s) in flight operations.
□ Examined selected output from FDA/FDM/FOQA program (if applicable) (focus: data that
indicates fleet status of missed approach/go-around from unstabilized approach).
□ Observed line flight and flight simulator operations (focus: missed approach/go-around from
unstabilized approach).
□ Other Actions (Specify)
Guidance
The intent of this provision is for an operator's stabilized approach policy to address the actions to be
taken by the flight crew in the event of deviations from the criteria that define a stabilized approach,
and to designate the minimum altitude at which a go-around must be accomplished if the aircraft is
not stabilized in accordance with the operator's stabilization criteria.
FLT 3.11.61 The Operator shall have a policy and procedures to ensure the flight crew maneuvers
the aircraft so as to touchdown within the touchdown zone or other defined portion of the runway, as
specified by the Operator or the Authority. (GM)
Auditor Actions
□ Identified/Assessed OM policy/procedures for landing aircraft in the defined touchdown zone
(focus: flight crew guidance/procedures for landing aircraft in touchdown zone).
□ Interviewed responsible manager(s) in flight operations.
□ Examined selected output from FDA/FDM/FOQA program (if applicable) (focus: data that
indicates fleet status of landings in the defined touchdown zone).
□ Observed line flight and flight simulator operations (focus: landing in touchdown zone).
□ Other Actions (Specify)
Guidance
The definition of the touchdown zone could vary, depending on the operator.
FLT 3.11.62 The Operator shall have a policy and procedures to ensure the flight crew will not
continue an instrument approach to land at any airport beyond a point at which the limits of the
operating minima specified for the approach in use would be infringed.
Auditor Actions
□ Identified/Assessed OM policy/procedures that address continuation of an instrument approach
to landing beyond limits of specified operating minima (focus: flight crew requirement/procedures
for maintaining adherence to operating minima).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight and flight simulator operations (focus: adherence to approach/landing
operating minima).
□ Other Actions (Specify)
FLT 3.11.63 The Operator shall have a policy and procedures to ensure the flight crew will not
continue an instrument approach beyond a designated point in the approach unless reported
meteorological conditions, including visibility or controlling RVR, are equal to or above those
specified for the approach in use. (GM)
Auditor Actions
□ Identified/Assessed OM policy/procedures that address required meteorological conditions for
continuation of an instrument approach beyond a designated point (focus: flight crew
requirement/procedures for determining/adhering to allowable meteorological conditions for
approach continuation).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight and flight simulator operations (focus: adherence to approach/landing
operating minima).
□ Other Actions (Specify)
Guidance
Designated points in the approach can be defined by the operator or applicable authority (e.g. final
approach fix, outer marker, established on final approach segment).
Applicable authorities include those authorities that have jurisdiction over international operations
conducted by an operator over the high seas or the territory of a state that is other than the State of
the Operator.
FLT 3.11.64 The Operator shall have guidance and procedures for the acceptance of a clearance
for a visual approach and the conduct of a visual approach.
Auditor Actions
□ Identified/Assessed OM guidance/procedures for acceptance of clearance and conduct of a
visual approach (focus: flight crew requirements/procedures for accepting/conducting a visual
approach).
FLT 3.11.67 The Operator shall have guidance, criteria and procedures for the acceptance of a
clearance for an ILS approach and the conduct of any authorized ILS approach, to include:
(i) Minimum meteorological conditions, including the visibility required to continue an approach;
(ii) Operating conditions that require a missed approach to be initiated. (GM)
Auditor Actions
□ Identified/Assessed OM guidance/procedures/criteria for acceptance of clearance and conduct
of an ILS approach (focus: flight crew procedures/definition of criteria for accepting/conducting
an ILS approach).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight and flight simulator operations (focus: ILS approach operations).
□ Other Actions (Specify)
Guidance
The specifications of the provision refer to ILS approaches authorized by the AOC (e.g. CAT I, II, III).
FLT 3.11.68 The Operator should have guidance that requires the flight crew to assess landing
performance prior to arrival at the destination or alternate airport in order to determine that sufficient
landing distance exists for a landing to be accomplished with an adequate safety margin:
(i) On the runway of intended use;
(ii) In the conditions existing at the estimated time of arrival (ETA);
(iii) In the aircraft configuration and with the means of deceleration that will be used for the
landing. (GM)
Auditor Actions
□ Identified/Assessed OM guidance for determination of landing distance with adequate safety
margin on runway of intended use (focus: flight crew procedures for assessing relevant
factors/computing runway landing distance at expected ETA).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight and flight simulator operations (focus: assessment of factors, computation of
landing distance).
□ Other Actions (Specify)
Guidance
The intent of this provision is for an operator to require a landing performance assessment under
conditions distinct from those presumed at time of dispatch. Such an assessment ensures adequate
landing performance under the conditions existing at the ETA, and when necessary enables the flight
crew to make the determination that a landing cannot be accomplished with an appropriate safety
margin.
This provision is not intended to preclude the flight crew from determining the absolute landing
capability of the aircraft during emergencies or abnormal configurations. In these circumstances, the
pilot must calculate and know the actual landing performance capability of the aircraft (without an
added safety margin).
An appropriate safety margin may be defined by the operator or the Authority, and can be expressed
as a fixed distance increment or a percentage increase beyond the actual landing distance required.
Factors that may affect landing performance include, but are not limited to:
• Runway contaminants;
• Runway cutback or reduced runway available;
• Environmental conditions at the ETA (crosswind, tailwind, wind gusts, rain, etc);
• Aircraft equipment outages;
• Flight control malfunctions, engine failures, or other non-normal/emergency events that may
affect landing distance;
FLT 3.12.4 The Operator shall have a policy and procedures to ensure flight crew members are
only permitted to leave their duty stations during flight in the performance of duties or to meet
physiological needs. (GM)
Auditor Actions
□ Identified/Assessed OM policy/procedures that address flight crew members leaving duty
stations during flight (focus: requirement that flight crew member may leave duty station only for
performance of duties/physiological needs).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight operations (focus: crew members leaving duty station).
□ Other Actions (Specify)
Guidance
The specifications of this provision do not apply to crew changes that occur in conjunction with relief
and/or augmented crews.
FLT 3.12.5 The Operator shall have a policy and procedures to ensure pilot flight crew members
do not vacate an aircraft control seat below 10,000 feet (AFE/AAL) for the purposes of transferring
duties to another pilot flight crew member. (GM)
Auditor Actions
□ Identified/Assessed OM policy/procedures that prohibit pilot flight crew members from leaving
aircraft control seat below 10,000 ft for the purpose of transferring duties to another pilot flight
crew member (focus: requirement that vacating control seat for transfer of duties must occur
above 10,000 ft).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight operations (focus: flight crew members transfer of duties).
□ Other Actions (Specify)
Guidance
The specifications of this provision refer to the transfer of duties associated with augmented crews or
crews with multiple pilot flight crew members.
FLT 3.12.6 (Intentionally open)
FLT 3.12.7 The Operator shall have guidance that addresses runway incursions, to include a
description of the flight crew duties, responsibilities, procedures and any other flight crew actions
necessary to prevent, or reduce the risk of, a runway incursion occurring during taxi, takeoff, and
landing. Such guidance shall include:
(i) Instructions for the maintenance of situational awareness by the flight crew while operating
in the airport environment, on the ground and in the air, to ensure an awareness of the
aircraft position relative to the airport surface;
(ii) Operating policies and procedures for use during periods when there is a high risk of an
incursion;
(iii) Specific instructions for the use of onboard equipment and aircraft lighting as a means to
mitigate the risk of an incursion;
(iv) The identification, in documentation available to the flight crew, of areas on the airport
surface that could pose a higher risk of an incursion;
(v) Specific reduced visibility and relevant LVO policies and procedures that minimize the risk of
an incursion. (GM)
Auditor Actions
□ Identified/Assessed OM guidance for runway incursion prevention/risk reduction during
taxi/takeoff/landing phases of flight (focus: definition of flight crew duties/responsibilities/
procedures/actions for runway incursion prevention/risk reduction).
• Methods for maintaining situational awareness at night and during times of reduced visibility;
• A recommendation that checklists be suspended or delayed until the aircraft is stopped;
• If authorized for LVO, methods for maintaining situational awareness during LVO;
• If authorized for LVO, CAT II/III Surface Movement Guidance System (SMGS) procedures.
An operator, in accordance with requirements of the Authority, typically develops flight crew guidance
related to the prevention of runway incursions from one or more source reference documents, to
include:
• ICAO Document 9870, Manual on the Prevention of Runway Incursions;
• European Action Plan for the Prevention of Runway Incursions, Edition 2.0;
• FAA Advisory Circular AC No: 120–74B;
• Runway Safety; A Pilot's Guide to Safe Surface Operations, Second Edition published by
FAA Air Traffic Organization (ATO), Office of Safety Services;
• Communications; A key Component of Safe Surface Operations, Second Edition published
by FAA Air Traffic Organization (ATO), Office of Safety Services;
• Any equivalent reference document approved or accepted by the Authority for the
development of flight crew guidance related to the prevention of runway incursions.
The term “abnormal” is used to describe a condition or situation (e.g. abnormal airframe vibration,
abnormal landing configuration).
The terms “normal” and “non-normal/emergency” typically refer to AOM checklists, procedures
and/or maneuvers. The term “non-normal” includes AOM emergency checklists and/or procedures
(i.e. an emergency procedure is a subset of non-normal).
The terms can also be used to describe an event, situation or operation that would be addressed by
normal or non-normal/emergency procedures or checklists. When used in this manner, the terms
may be separated by forward slash marks (e.g. normal/non-normal/emergency).
The term “emergency” used alone refers to declarations and non-AOM procedures.
FLT 3.13.6 If the Operator transports passengers and/or supernumeraries, the Operator shall have
a policy and/or procedures that provides for announcements to, as applicable, passengers and/or
supernumeraries by either the flight crew or cabin crew to address matters related to safety, including
turbulence and abnormal and emergency situations. (GM)
Note: The specifications of this provision are applicable to commercial and/or non-commercial
operations.
Auditor Actions
□ Identified/Assessed OM policy/procedure for announcements to passengers/supernumeraries
to address safety matters (focus: procedure for flight/cabin crew safety announcements;
definition of situations that require safety announcements).
□ Interviewed responsible manager(s) in flight operations.
□ Coordinated with cabin operations (focus: complementary procedure for safety
announcements).
□ Observed line flight operations (focus: flight/cabin crew safety announcements).
□ Other Actions (Specify)
Guidance
The intent of this provision is to ensure passengers and/or supernumeraries are made aware of
matters related to safety.
The term “abnormal” is used to describe a condition or situation (e.g. abnormal airframe vibration,
abnormal landing configuration).
The terms “normal” and “non-normal/emergency” typically refer to AOM checklists, procedures
and/or maneuvers. The term “non-normal” includes AOM emergency checklists and/or procedures
(i.e. an emergency procedure is a subset of non-normal).
The terms can also be used to describe an event, situation or operation that would be addressed by
normal or non-normal/emergency procedures or checklists. When used in this manner, the terms
may be separated by forward slash marks (e.g. normal/non-normal/emergency).
The term “emergency” used alone refers to declarations and non-AOM procedures.
FLT 3.13.7 (Intentionally open)
FLT 3.13.8 If the Operator transports passengers and/or supernumeraries, the Operator shall have
procedures that ensure the preparation of the cabin or supernumerary compartment prior to takeoff
and landing, and provide for notification to, as applicable, passengers and/or supernumeraries by
either the flight crew or cabin crew:
(i) To prepare for takeoff;
(ii) When in the descent phase of flight;
(iii) To prepare for landing. (GM)
Note: The specifications of this provision are applicable to commercial and/or non-commercial
operations.
Auditor Actions
□ Identified/Assessed OM procedures for preparation of cabin/supernumerary compartment and
notification to passengers/supernumeraries prior to takeoff/landing (focus: flight/cabin crew
procedures for cabin/supernumerary compartment preparation; definition of situations that
require flight/cabin crew notification).
□ Interviewed responsible manager(s) in flight operations.
□ Coordinated with cabin operations (focus: complementary procedures for compartment
preparation/notifications).
□ Observed line flight operations (focus: flight/cabin crew notification prior to takeoff/landing).
□ Other Actions (Specify)
Guidance
The intent of this provision is to ensure cabin or supernumerary compartment readiness under the
conditions specified. Additionally, the provision requires that all applicable personnel are notified
when in the specified phases of flight.
If cabin crew members are not used, preparation of the cabin prior to takeoff and landing would
normally require the flight crew to verify certain conditions are in effect. Items checked by the flight
crew will vary according to aircraft type and equipment carried, but might typically include:
• Passenger seat belts fastened;
• Tray tables and seat backs in a stowed and upright position;
• Cabin baggage and other carry-on items secure in designated areas;
• As applicable, in-flight entertainment system viewing screens off and stowed;
• Galleys and associated equipment stowed or restrained.
FLT 3.13.9 <AC> If the Operator carries cargo on the same deck as the flight deck and/or
supernumerary compartment, the Operator shall have procedures to ensure the 9G restraint system
(cargo net or rigid barrier/bulkhead) and, if applicable, smoke barrier are closed/secured for:
(i) Taxi operations;
(ii) Takeoff;
(iii) Landing. (GM)
Auditor Actions
□ Identified/Assessed OM procedures that address operation of smoke barrier door (focus:
requirement for door closure for taxi/takeoff/landing).
□ Interviewed responsible manager(s) in flight operations.
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definitions of Cargo Restraint System and Smoke Barrier.
FLT 3.13.10 <AC> If the Operator transports radioactive material on cargo aircraft in excess
of the baseline amount prescribed by regulations, the Operator should have a program or
process to ensure flight crew members that operate such flights are not exposed to unsafe levels of
radiation. (GM)
Note: Radioactive material in excess of baseline regulatory amounts is transported under special
arrangement, or exclusive use.
Auditor Actions
□ Identified/Assessed program/processes that address transport of radioactive material (focus:
description of devices/methods used for detecting/monitoring flight crew radiation exposure).
□ Interviewed responsible manager(s) in flight operations.
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definitions of Exclusive Use and Special Arrangement.
An operator, in accordance with requirements of the Authority, typically develops programs related to
the transport of dangerous goods, including radioactive materials, based on technical information
from one or more source reference documents, to include:
• Annex 18 to the Convention on International Civil Aviation (Chicago, 1944) and the current
edition of the associated Technical Instructions for the Safe Transport of Dangerous Goods
by Air (Doc 9284-AN/905), including addenda to the 2013–2014 Technical Instructions.
• The current edition of the IATA Dangerous Goods Regulations (DGR).
• FAA CFR 49, Parts 171–175, as applicable.
• Any equivalent dangerous goods manual or other reference document approved or accepted
by the Authority for the development of radiation protection programs related to the
transportation of dangerous goods by air.
FLT 3.13.11 If the Operator conducts cargo flights and/or passenger flights without cabin crew, and
utilizes aircraft equipped with doors that have an automatic slide or slide/raft deployment system, the
Operator shall have flight crew procedures for arming and disarming such door systems. (GM)
Auditor Actions
□ Identified/Assessed OM procedures for arming/disarming of doors with automatic slide raft
deployment system (focus: flight crew procedures for door arming/disarming).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight operations (focus: arming/disarming of doors).
□ Other Actions (Specify)
Guidance
This standard addresses door systems that are designed to deploy a slide or slide/raft for emergency
evacuation if the door is opened with the system in the armed mode. Such door systems are typically
armed once the door has been closed for flight, and disarmed at the end of a flight and prior to the
door being opened for passenger and/or crew deplaning.
Depending on the type of aircraft and door system, the pack that contains the slide or slide/raft might
be mounted in the door itself, or might be mounted in the fuselage, tail cone or other location.
FLT 3.13.12 If the Operator transports passengers and/or supernumeraries, and does not use a
cabin crew, the Operator shall have flight crew procedures that ensure, as applicable, passengers
and/or supernumeraries have ready access to emergency oxygen. (GM)
Note: The specifications of this provision are applicable to commercial and/or non-commercial
operations.
Auditor Actions
□ Identified/Assessed OM procedures that address passenger/supernumerary ready access to
emergency oxygen (focus: flight crew procedures for ensuring access to oxygen).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight operations (focus: flight crew procedures for ensuring
passenger/supernumerary access to oxygen).
□ Other Actions (Specify)
Guidance
The intent of this provision is to ensure passengers and/or supernumeraries are made aware of
matters related to safety.
FLT 3.13.13 If the Operator transports passengers and/or supernumeraries, and does not use a
cabin crew, the Operator shall have flight crew procedures that ensure, as applicable, passengers
and/or supernumeraries are seated with their seat belts (or, as available, harness or other restraint)
fastened:
(i) During the taxi phases of a flight;
(ii) During the takeoff and landing phases of flight;
(iii) Prior to and/or during turbulence;
(iv) During an emergency situation, if considered necessary.
Note: The specifications of this provision are applicable to commercial and/or non-commercial
operations.
Auditor Actions
□ Identified/Assessed OM procedures for ensuring passengers/supernumeraries are seated with
seat belts/safety harness/other restraint device fastened for defined situations/phases of flight
(focus: flight crew procedures for ensuring passengers/supernumeraries are seated/restrained;
definition of situations/phases of flight that require seating/restraint).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight operations (focus: passengers/supernumeraries seated/restrained).
□ Other Actions (Specify)
Guidance
The intent of this provision is to ensure passengers and/or supernumeraries are made aware of
matters related to safety.
FLT 3.13.14 If the Operator transports supernumeraries in the passenger cabin or cargo
compartment, the Operator shall have guidance and procedures to ensure:
(i) All seats in the cargo compartment are considered emergency exit row seats;
(ii) Supernumeraries meet applicable requirements and restrictions.
Auditor Actions
□ Identified/Assessed OM guidance/requirements/procedures for transport of supernumeraries in
passenger cabin/cargo compartment (focus: requirement/procedure for all cargo compartment
seats to be treated the same as emergency exit row seats; definition of requirements/restrictions
that must be met by supernumeraries).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight operations (focus: procedures for transport of
passengers/supernumeraries).
□ Other Actions (Specify)
FLT 3.13.15 (Intentionally open)
FLT 3.13.16 If the Operator utilizes aircraft equipped with a flight deck door, the Operator shall
have policies and/or procedures that are in accordance with the requirements of the Authority and, as
a minimum, define:
(i) When the flight deck door must remain locked;
(ii) If the Operator conducts passenger flights with cabin crew:
(a) The way the cabin crew notifies the flight crew in the event of suspicious activity or
security breaches in the cabin;
(b) The way cabin crew members gain entry to the flight deck. (GM)
Auditor Actions
□ Identified/Assessed OM policies/procedures that address flight deck security (focus:
requirements for door being locked/unlocked; methods for cabin crew to provide security
notifications; process for cabin crew entry to flight deck).
□ Interviewed responsible manager(s) in flight operations.
Auditor Actions
□ Identified/Assessed OM policies/procedures that address flight deck security (focus:
requirements for door being locked/unlocked; procedures for monitoring area outside door).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight operations (focus: door locked/unlocked; monitoring area outside door).
□ Other Actions (Specify)
Guidance
The principal intent of this provision is to ensure the security of the flight deck by providing the flight
crew with appropriate procedures for use when a reinforced flight deck door is installed.
Procedures related to flight deck security may be considered sensitive information and provided to
relevant personnel in a manner that protects the content from unnecessary disclosure.
The specification in item i) refers to the period when the aircraft is being operated beginning when all
exterior doors are closed for engine start or pushback and ending when the aircraft is parked and any
exterior door is opened for disembarkation.
For monitoring the area outside the flight deck door, a closed circuit television (CCTV) system is an
acceptable method of conformance. However, a CCTV system is not required in order to conform to
this provision. Implementation of other procedural methods in accordance with applicable regulations
is also considered acceptable.
Any means utilized by an operator for such monitoring ensures that the cabin area outside the flight
deck door, and any persons that might be in that area, would be identifiable to the extent necessary
to meet the requirements of this standard.
FLT 3.13.19 If the Operator conducts passenger operations and does not utilize a flight deck door,
the Operator shall have measures in place to ensure unauthorized persons are prevented from
entering the flight deck. (GM)
Auditor Actions
□ Identified/Assessed OM guidance/procedures that address flight deck security (focus:
measures/procedures for flight deck entry control/prevention).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight operations (focus: prevention of unauthorized flight deck entry).
□ Other Actions (Specify)
Guidance
The principal intent of this provision is to ensure the security of the flight deck, and refers specifically
to aircraft that:
• Do not have a flight deck door, or
• Are equipped with flight deck door that cannot be locked, or
• Are equipped with a smoke barrier.
Measures referred to in this provision are in place to address the potential for unauthorized personnel
to gain entry to the flight deck or gain access to the control seats and/or flight controls. Such
measures may include, but are not limited to:
• Defining authorized personnel (e.g. jump-seat occupants, supernumeraries);
• Authorizing personnel for flight deck access;
• Airline Security programs (as defined by the authority);
• Briefings, announcements, placards;
• Any other measure designed to ensure unauthorized personnel are not permitted access to
the flight deck, control seats, or flight controls.
The terms can also be used to describe an event, situation or operation that would be addressed by
normal or non-normal/emergency procedures or checklists. When used in this manner, the terms
may be separated by forward slash marks (e.g. normal/non-normal/emergency).
The term “emergency” used alone refers to declarations and non-AOM procedures.
FLT 3.14.4 If the Operator conducts passenger flights with cabin crew, the Operator shall have
procedures in accordance with FLT 3.11.18, applicable to each aircraft type, that specify the flight
and cabin crew member functions and actions to be executed during a situation requiring an
emergency evacuation.
Auditor Actions
□ Identified/Assessed OM procedures for aircraft emergency evacuation (focus: procedures for
each aircraft type; definition of flight/cabin crew member functions/actions during emergency
evacuation; procedures include sharing/prioritization of tasks).
□ Interviewed responsible manager(s) in flight operations.
□ Coordinated with cabin operations (focus: complementary procedures for emergency
evacuation).
□ Observed line flight and flight simulator operations (focus: flight/cabin crew emergency
evacuation procedures).
□ Other Actions (Specify)
FLT 3.14.5 If the Operator transports passengers and/or supernumeraries, and does not use a
cabin crew, the Operator shall have procedures that are applicable to each aircraft type and:
(i) Specify flight crew functions and actions to be executed during an emergency evacuation;
(ii) Address, as applicable, passengers and/or supernumeraries.
Note: The specifications of this provision are applicable to flight crew members utilized on board an
aircraft during commercial and/or non-commercial operations.
Auditor Actions
□ Identified/Assessed OM procedures for aircraft emergency evacuation (focus: procedures for
each aircraft type; definition of flight crew member functions/actions during emergency
evacuation; procedures for treatment of passengers/supernumeraries).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight operations (focus: flight crew emergency evacuation procedures).
□ Other Actions (Specify)
FLT 3.14.6 The Operator shall have policies and procedures in accordance with FLT 3.11.18,
applicable to each aircraft type, that are to be applied during a situation requiring a rejected takeoff
and address the operational considerations for low speed and high speed rejected takeoffs.
Auditor Actions
□ Identified/Assessed OM policies/procedures that address rejected takeoff (focus: procedures
for each aircraft type; definition of considerations associated with low/high speed rejected
takeoff; procedures include flight crew sharing/prioritization of tasks).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight and flight simulator operations (focus: rejected takeoff
procedures/considerations).
□ Other Actions (Specify)
FLT 3.14.7 The Operator shall have policies and associated procedures accordance with
FLT 3.11.18, applicable to each aircraft type, that are to be applied when an engine failure or fire
occurs after V1.
Auditor Actions
□ Identified/Assessed OM policies/procedures that address engine fire/failure after V1 (focus:
procedures for each aircraft type; flight crew procedures that address engine fire/failure after
takeoff; procedures include flight crew sharing/prioritization of tasks).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight and flight simulator operations (focus: engine fire/failure after V1
procedures).
□ Other Actions (Specify)
FLT 3.14.8 The Operator shall have policies and procedures in accordance with FLT 3.11.18,
applicable to each aircraft type, that are to be applied when a TCAS/ACAS resolution advisory (RA)
is displayed by onboard equipment. Such guidance shall, as a minimum:
(i) Specify a TCAS escape maneuver;
(ii) Require flight crews to follow a TCAS RA guidance even if it conflicts with ATC instructions.
Auditor Actions
□ Identified/Assessed OM policies/procedures that address reaction to display of TCAS/ACAS
resolution advisory (RA) (focus: procedures for each aircraft type; requirement for flight crew to
follow TCAS/ACAS guidance; definition of/procedure for TCAS/ACAS escape maneuver;
procedures include flight crew sharing/prioritization of tasks).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight and flight simulator operations (focus: TCAS/ACAS RA procedures).
□ Other Actions (Specify)
FLT 3.14.9 The Operator shall have policies and procedures in accordance with FLT 3.11.18,
applicable to each aircraft type, that are applied during a GPWS or other terrain avoidance alert
provided by onboard equipment. Such guidance shall, as a minimum, define a CFIT escape
maneuver as an aggressive pitch up maneuver that maximizes the performance of the aircraft.
Auditor Actions
□ Identified/Assessed OM policies/procedures that address reaction to GPWS/terrain avoidance
alert/warning (focus: procedures for each aircraft type; definition of/procedure for aggressive
pitch-up escape maneuver; procedures include flight crew sharing/prioritization of tasks).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight and flight simulator operations (focus: GPWS/terrain alert/warning
procedures).
□ Other Actions (Specify)
FLT 3.14.10 The Operator shall have procedures in accordance with FLT 3.11.18, applicable to
each aircraft type that are to be applied in the event of an emergency descent.
Auditor Actions
□ Identified/Assessed OM procedures that address emergency descent (focus: procedures for
each aircraft type; definition of/procedure for emergency descent maneuver; procedures include
flight crew sharing/prioritization of tasks).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight and flight simulator operations (focus: emergency descent procedure).
□ Other Actions (Specify)
FLT 3.14.11 The Operator shall have guidance and procedures that address abnormal and/or
emergency communication, to include the:
(i) Appropriate use of “PAN PAN” and/or “MAYDAY;”
(ii) Actions to be taken in the event of a complete radio failure (lost communication);
(iii) Interception protocol for civil aircraft intercepted by military aircraft, to include a description
of visual signals used by intercepting and intercepted aircraft. (GM)
Auditor Actions
□ Identified/Assessed OM guidance/procedures that address communications during
abnormal/emergency situations (focus: definition of communication terminology; procedures for
radio failure/lost communication; protocols for intercept by military aircraft).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight and flight simulator operations (focus: abnormal/emergency communication
procedures).
□ Other Actions (Specify)
Guidance
The term “abnormal” is used to describe a condition or situation (e.g. abnormal airframe vibration,
abnormal landing configuration).
The terms “normal” and “non-normal/emergency” typically refer to AOM checklists, procedures
and/or maneuvers. The term “non-normal” includes AOM emergency checklists and/or procedures
(i.e. an emergency procedure is a subset of non-normal).
The terms can also be used to describe an event, situation or operation that would be addressed by
normal or non-normal/emergency procedures or checklists. When used in this manner, the terms
may be separated by forward slash marks (e.g. normal/non-normal/emergency).
The term “emergency” used alone refers to declarations and non-AOM procedures.
FLT 3.14.12 The Operator shall have procedures in accordance with FLT 3.11.18 that are to be
applied by the flight crew in the event of a medical emergency on board the aircraft. If a cabin crew is
used, such procedures shall also address cabin crew duties and ensure flight deck-to-cabin
communication and coordination occurs in accordance with FLT 3.13.3.
Auditor Actions
□ Identified/Assessed OM procedures that address onboard medical emergencies (focus:
procedures include flight/cabin crew communication/coordination, flight crew
sharing/prioritization of tasks).
□ Interviewed responsible manager(s) in flight operations.
□ Coordinated with cabin operations (focus: complementary procedures for onboard medical
emergency).
□ Observed line flight operations (focus: medical emergency procedures).
□ Other Actions (Specify)
FLT 3.14.13 The Operator shall have procedures in accordance with FLT 3.11.18 that are to be
applied by the flight crew in the event of flight crew member incapacitation on board the aircraft. If a
cabin crew is used, such procedures shall also address cabin crew duties and ensure flight deck-to-
cabin communication and coordination occurs in accordance with FLT 3.13.3.
Auditor Actions
□ Identified/Assessed OM procedures that address flight crew incapacitation (focus: procedures
include flight/cabin crew communication/coordination, flight crew sharing/prioritization of tasks).
□ Interviewed responsible manager(s) in flight operations.
□ Coordinated with cabin operations (focus: complementary procedures for flight crew
incapacitation).
□ Observed line flight and flight simulator operations (focus: flight crew incapacitation).
□ Other Actions (Specify)
FLT 3.14.14 The Operator shall have guidance and procedures that ensure the proper reset of
circuit breakers after a system malfunction or trip. Such guidance shall, as a minimum, specify when
and how often tripped circuit breakers may be reset.
Auditor Actions
□ Identified/Assessed OM guidance/procedures that address reset of circuit breakers after
system malfunction/trip (focus: procedures define when/how often tripped circuit breakers may
be reset).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight operations (focus: circuit breaker re-set procedures).
□ Other Actions (Specify)
FLT 3.14.15 The Operator shall have an in-flight fuel management policy that requires the PIC to
request air traffic delay information from ATC when unanticipated circumstances may result in
landing at the destination airport with less than either:
(i) The final reserve fuel plus any fuel required to proceed to an alternate airport, or
(ii) The fuel required to operate to an isolated airport. (GM)
Auditor Actions
□ Identified/Assessed OM policy/procedures for in-flight fuel management (focus: flight crew
procedures for monitoring en route fuel usage/identifying trends; requirement for flight crew to
request airport delay information when trend indicates landing with less than final reserve plus
alternate fuel, or isolated airport fuel).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight and flight simulator operations (focus: in-flight fuel management
procedures).
□ Other Action (Specify)
Guidance
Refer to the IRM for the definition of Fuel (Flight Planning), which includes the definition of Final
Reserve Fuel.
The intent of this provision is to ensure an operator defines the conditions that require the PIC to
request air traffic delay information from ATC. Such operator policy is typically part of the overall in-
flight fuel management strategy to ensure planned reserves are used as intended or required. It also
typifies the beginning of a process that could ultimately preclude a landing with less than final reserve
fuel on board.
It should be noted that the request for air traffic delay information is a procedural means for the flight
crew to determine an appropriate course of action when confronted with unanticipated delays. There
is no specific phraseology recommended for use in this type of communication with ATC as each
situation may be very different.
Guidance on in-flight fuel management and requesting delay information from ATC is contained in
the ICAO Flight Planning and Fuel Management Manual (Doc 9976).
FLT 3.14.16 The Operator shall have an in-flight fuel management policy that requires the PIC to
advise ATC of a minimum fuel state:
(i) When, having committed to land at a specific airport, the PIC calculates that any change to
the existing clearance to that airport may result in landing with less than planned final
reserve fuel;
(ii) By declaring “MINIMUM FUEL.” (GM)
▲ An operator may conform to FLT 3.14.16 ii) through Active Implementation as long as the
implementation Action Plan (IAP) projects conformance on or before 31 August 2018.
Auditor Actions
□ Identified/Assessed OM policy/procedures for in-flight fuel management (focus: flight crew
procedures for monitoring en route fuel usage/identifying trends; requirement for flight crew to
declare minimum fuel when minimum fuel for landing at destination airport might be less than
planned final reserve fuel).
□ Identified/Assessed Active Implementation plan (if applicable).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight and flight simulator operations (focus: in-flight fuel management
procedures).
□ Other Action (Specify)
Guidance
The intent of a “MINIMUM FUEL” declaration is to inform ATC that the flight has committed to land at
a specific airport and any change to the existing clearance may result in landing with less than
planned final reserve fuel. This is not an emergency situation, but rather an indication that an
emergency situation is possible should any additional delay occur.
Active Implementation is applicable to the specification in item ii) for the sole purpose of affording
states the time necessary to implement the standard ICAO phraseology related to minimum fuel
states.
Guidance on in-flight fuel management, including minimum fuel declarations, is contained in the
ICAO Flight Planning and Fuel Management Manual (Doc 9976).
FLT 3.14.17 The Operator shall have an in-flight fuel management policy that requires the PIC to
declare a situation of fuel emergency:
(i) When the calculated usable fuel predicted to be available upon landing at the nearest airport
where a safe landing can be made is less than the planned final reserve fuel;
(ii) By declaring “MAYDAY, MAYDAY, MAYDAY, FUEL.” (GM)
▲ An operator may conform to FLT 3.14.17 ii) through Active Implementation as long as the
implementation Action Plan (IAP) projects conformance on or before 31 August 2018.
Auditor Actions
□ Identified/Assessed OM policy/procedures for in-flight fuel management (focus: flight crew
procedures for monitoring en route fuel usage/identifying trends; requirement for flight crew to
declare an emergency when minimum fuel for landing at nearest airport is calculated to be less
than planned final reserve fuel).
□ Identified/Assessed Active Implementation Plan (if applicable).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight and flight simulator operations (focus: in-flight fuel management
procedures).
□ Other Action (Specify)
Guidance
The intent of this provision is to specify the last procedural step in a series of steps to ensure the safe
completion of a flight. The “MAYDAY, MAYDAY, MAYDAY, FUEL” declaration provides the clearest
and most urgent expression of an emergency situation brought about by insufficient usable fuel
remaining to protect the planned final reserve. It communicates that immediate action must be taken
by the PIC and the air traffic control authority to ensure that the aircraft can land as soon as possible.
It is used when all opportunities to protect final reserve fuel have been exploited and in the judgment
of the PIC, the flight will now land with less than final reserve fuel remaining in the tanks. The word
fuel is used as part of the declaration simply to convey the exact nature of the emergency to ATC.
Active Implementation is applicable to the specification in item ii) for the sole purpose of affording
States the time necessary to implement standard ICAO phraseology related to fuel emergencies.
Guidance on in-flight fuel management including emergency fuel declarations is contained in the
ICAO Flight Planning and Fuel Management Manual (Doc 9976).
FLT 3.15.3 The Operator shall have a policy that assigns responsibility to the PIC for notifying the
nearest authority, by the quickest available means, of any accident or serious incident resulting in
injury, death, or substantial aircraft damage.
Auditor Actions
□ Identified/Assessed policy for flight crew accident/incident reporting (focus: flight crew
responsibility/procedures for reporting accidents/serious incidents to the nearest authority by the
quickest available means).
□ Interviewed responsible manager(s) in flight operations.
□ Interviewed selected flight crew members.
□ Other Actions (Specify)
FLT 3.15.4 The Operator shall have a policy that assigns responsibility to the PIC for:
(i) Notifying the appropriate local authority without delay in the event of any emergency
situation that necessitated action in violation of local regulations and/or procedures;
(ii) Submitting, if required by the state of occurrence, a report to the appropriate local authority
and also to the Authority of the State of the Operator.
Auditor Actions
□ Identified/Assessed policy for flight crew emergency action reporting (focus: flight crew
responsibility/procedures for reporting to the appropriate authorities any emergency situation that
necessitated action in violation of local regulations and/or procedures).
□ Interviewed responsible manager(s) in flight operations.
□ Interviewed selected flight crew members.
□ Other Actions (Specify)
guidance and data shall ensure the flight crew considers all relevant factors affecting aircraft
performance, to include:
(i) Aircraft weight (mass);
(ii) Operating procedures;
(iii) Pressure altitude;
(iv) Temperature;
(v) Wind;
(vi) Runway gradient;
(vii) Runway contaminant/braking action;
(viii) Obstacle data;
(ix) NOTAMs (including airport NOTAMs);
(x) As applicable, MEL/CDL information;
(xi) Aircraft configuration (wing flap setting);
(xii) Anti-ice usage and, when applicable, ice accretion;
(xiii) As applicable, runway length used for aircraft alignment prior to takeoff;
(xiv) As applicable, fuel freeze considerations during extended operations. (GM)
Auditor Actions
□ Identified/Assessed OM guidance/procedures/data for flight crew calculation of aircraft
performance for all phases of flight (focus: performance data provided for all aircraft types; OM
guidance/data incorporates relevant factors/limitations as specified in standard).
□ Interviewed responsible manager(s) in flight operations.
□ Interviewed selected operations engineering personnel (focus: process for development of OM
performance information/data).
□ Observed line flight operations (focus: determination of relevant factors affecting aircraft
performance).
□ Other Actions (Specify)
Guidance
The intent of this provision is to ensure the operator has a process or processes to obtain or
determine the specified performance data for use by flight crew. Such process(s) also address the
maintenance and publication of guidance, procedures, and performance data in the OM.
The specification in item vii) could be defined by a specific contaminant type/depth or equivalent
braking action report.
The specifications in xiii) refers to a determination of the length of the runway available, taking into
account the loss, if any, of runway length due to alignment of the aircraft prior to takeoff.
The specifications in xiv) apply to considerations regarding the use of standard fuel freeze
temperatures, fuel temperature analysis and en route fuel temperature monitoring for the specific
fuels used in operations. Such considerations allow the flight crew to determine the actual fuel freeze
temperature during extended operations (e.g. polar operations) in order to prevent in-flight freezing of
fuel.
FLT 4.1.3 The Operator shall have a process, performed by Operations Engineering, to determine
and maintain guidance, data and procedures in the OM, applicable to each aircraft type, that enable
the flight crew to determine and/or compute en route aircraft engine-out performance. Such
guidance, data and procedures shall include, as a minimum, aircraft engine-out:
(i) Service ceiling;
(ii) Drift down altitudes, as well as specific guidance and procedures that assure terrain
clearance along the route to the destination airport or to an en route alternate airport. (GM)
Auditor Actions
□ Identified OM guidance/procedures/data for flight crew calculation of en route aircraft engine-out
performance (focus: performance data provided for all aircraft types; OM contains engine-out
performance data as specified in standard).
□ Interviewed responsible manager(s) in flight operations.
□ Interviewed selected operations engineering personnel (focus: process for development of OM
performance information/data).
□ Observed line flight operations (focus: use of en route engine-out performance
information/data).
□ Other Actions (Specify)
Guidance
The intent of this provision is to ensure an operator has a process or processes to obtain or
determine the specified performance data for use by flight crew. Such process(s) also address the
maintenance and publication of guidance, procedures, and performance data in the OM.
The specification in item ii) refers to those areas were adequate terrain clearance cannot be assured
at the engine-out service ceiling of the aircraft without following specific guidance and procedures for
drift down.
FLT 4.1.4 The Operator should provide operating instructions, applicable to each aircraft type, that
enable the PIC to determine if the required all-engine climb gradient can be achieved during the
departure phase of flight under the existing conditions. (GM)
Auditor Actions
□ Identified/Assessed OM instructions/data for use by flight crew to determine/achieve safe all-
engine departure climb gradient (focus: performance data provided for all aircraft types).
□ Interviewed responsible manager(s) in flight operations.
□ Observed line flight operations (focus: use of all-engine climb gradient information/data).
□ Other Actions (Specify)
Guidance
The intent of this provision is for the operator to provide instructions for the PIC to determine if all
engine takeoff and departure climb performance is adequate for the planned operation under the
existing conditions. Such instructions typically contain one or more of the following elements:
• Assurances that automated performance and flight planning systems account for minimum
takeoff and departure path climb performance;
• Tailored (e.g. Jeppesen) takeoff performance charts that assure aircraft meet all-engine
minimum climb performance requirements;
• Aircraft manufacturer climb performance charts and instructions for their use;
• A requirement for the PIC to monitor and adjust vertical speed to maintain minimum climb
gradient);
• Specific thrust and/or flight control configuration settings to exceed the minimum climb
gradient performance at airports requiring different climb performance due to terrain, traffic or
other considerations.
In the absence of manufacturer all-engine climb performance data, the specifications of this provision
may be satisfied if the operator provides:
• Guidance that enables the PIC to determine that the aircraft climb performance, in the event
of a critical power unit failure at any point in the takeoff, is sufficient to meet ATC or obstacle
clearance constraints (e.g. minimum vertical speed required to meet climb gradient specified
in a SID), or
• Instructions for the PIC to use FMC predicted altitude information for the purpose of
determining all-engine climb performance, or
• Instructions for the PIC to monitor and adjust vertical speed as necessary to comply with the
departure path.
If available from the manufacturer, the operator would normally include all-engine takeoff climb
gradient information or guidance for calculations in the documentation carried on board the aircraft
for each flight.
Auditor Actions
□ Identified/Assessed process for analysis to identify/address relevant operational factors prior to
conducting operations over new routes/into new airports (focus: analysis includes/addresses
factors as specified in standard).
□ Interviewed responsible manager(s) in flight operations.
□ Interviewed selected operations engineering personnel (focus: process for analysis of new
routes/airports).
□ Examined selected examples of new route/airport analyses.
□ Other Actions (Specify)
Guidance
The specifications in:
• Item vii) refers to a determination if the occurrence of fuel freeze during extended operations
is operationally relevant when planning a new route. If operationally relevant, the
specification vii) of this provision requires the operator to determine and designate the
methods used by the flight crew to determine fuel freeze points in accordance with the
specifications of FLT 4.1.2.
• Item xi) refers to carriage of fuel to respect oxygen requirement after depressurization.
• Item xi) may be satisfied by depressurization routes, charts and/or tables that consider
oxygen requirements over high terrain and fuel burn over remote areas.
• Item xii) may be satisfied by standardized criteria for the determination and classification of
special airports (e.g., EU-OPS).
FLT 4.2.3 If the Operator conducts operations over remote or sparsely populated areas, the
Operator should provide information that identifies and describes en route emergency airports
associated with operations over such areas. (GM)
Note: The en route emergency airports specified in this provision refer to airports that are applicable
to the operation being conducted (i.e. within flying range from the route being flown and potentially
usable for the aircraft type).
Auditor Actions
□ Identified operational routes over remote/sparsely populated areas.
□ Identified/Assessed OM information that identifies en route emergency airports associated with
operations over remote or sparsely populated areas (focus: description of en route emergency
airports).
□ Interviewed responsible manager(s) in flight operations.
□ Other Actions (Specify)
Guidance
The specifications of this provision refer to emergency airports identified and described by the
operator that are not subject to the normal-use specifications of FLT 4.2.1 or the new airport analysis
specifications of FLT 4.2.2.
The intent of this provision is for an operator to provide information that identifies en route emergency
airports that could be considered usable for operations over the routes flown by the operator. It is
recognized that many oceanic areas are “remote or sparsely populated” and beyond the flight range
of any usable mainland or island airports. It is not intended that the specifications of this provision
would apply to those routes (or portions of routes) conducted over oceanic areas that are beyond the
range of any usable emergency airports.
Such information is provided for consideration by the PIC in the event an emergency over such areas
precludes continuation to an en route alternate. Any deficiencies in airport adequacy with respect to
the specifications of FLT 4.2.1 and FLT 4.2.2 are typically identified and described.
FLT 4.2.4 The Operator shall have guidance, data and procedures to enable operations
engineering personnel to determine minimum safe altitudes for all phases of flight. (GM)
Auditor Actions
□ Identified OM information that specifies minimum safe altitudes for all phases of flight (focus:
information addresses all areas/airports used in operations).
□ Interviewed responsible manager(s) in flight operations.
□ Interviewed selected operations engineering personnel (focus: guidance/procedures/data used
to determine minimum safe altitudes).
□ Other Actions (Specify)
Guidance
Minimum safe altitudes (MSAs) are typically established by the states over which flights are
conducted.
MSAs are typically established by the operator through specified methods approved by the State and
included in the OM.
FLT 4.2.5 The Operator shall specify operating minima for each airport of intended use, which shall
not be lower than those established by the state in which the airport is located.
Auditor Actions
□ Identified/Assessed OM information that specifies operating minima for all airports used in
operations (focus: operating minima not lower than minima specified by state of airport location).
□ Interviewed responsible manager(s) in flight operations.
□ Interviewed selected operations engineering personnel (focus: sources of airport operating
minima).
□ Other Actions (Specify)
□ Observed line flight operations or inspected static aircraft (focus: flight deck
instrumentation/navigation/communication systems).
□ Other Actions (Specify)
FLT 4.3.2–4.3.3 (Intentionally open)
FLT 4.3.4 If the Operator utilizes unpressurized aircraft operated at flight altitudes where the cabin
altitude will be greater than 10,000 feet (less than 700 hPa), the Operator shall ensure all such
aircraft are equipped with oxygen storage and dispensing apparatus in accordance with
requirements of the Authority and, as a minimum, also ensures;
(i) The aircraft can continue at a pressure altitude that will allow continued safe flight and
landing;
(ii) An amount of stored supplemental oxygen, in accordance with the requirements of the
Authority, and, as a minimum, to supply:
(a) The flight crew for any period the cabin altitude would be above 10,000 feet;
(b) All aircraft occupants for any period the cabin altitude would be above 15,000 feet;
(c) The flight crew and all aircraft occupants in accordance with a) and b) as
appropriate for the route to be flown. (GM)
Auditor Actions
□ Identified/Assessed oxygen systems for aircraft operated at flight altitudes where cabin altitude
will be greater than 10,000 ft (focus: applicable aircraft have oxygen storage/dispensing
apparatus in accordance with requirements of Authority; stored supplemental oxygen as
specified in standard).
□ Interviewed responsible manager(s) in flight operations.
□ Coordinated with maintenance operations (focus: verification that oxygen systems are in
accordance with certification/regulatory requirements).
□ Other Actions (Specify)
Guidance
The operator, in accordance with the requirements of the Authority, typically uses technical guidance
for the computation of sufficient stored breathing oxygen for unpressurized aircraft derived from any
one of the following sources, as applicable:
• ICAO Annex 6, 4.3.8.1;
• EU-OPS 1.775 and Appendix 1 to EU-OPS 1.775;
• FAR 135.157 (a), FAR 121.327, FAR 121.329;
• Any equivalent reference document approved or accepted by the Authority for the
computation of sufficient stored breathing oxygen for unpressurized aircraft that conforms to
the specifications of this provision.
The specifications of this provision require a minimum amount of oxygen supply be determined
and/or designated by the operator or the Authority.
Flight altitude is equivalent to cabin pressure altitude for the purposes of unpressurized aircraft
oxygen supply calculations.
The specifications in item ii) may require the operator to define depressurization escape routes in the
OM.
FLT 4.3.5 If the Operator utilizes aircraft operated at flight altitudes greater than 10,000 feet (less
than 700 hPa), but pressurized to maintain a cabin altitude of less than 10,000 feet (greater than
700 hPa), the Operator shall ensure all such aircraft can descend to an altitude after a loss of
pressurization that will allow continued safe flight and landing and are equipped with oxygen storage
and dispensing apparatus in accordance with requirements of the Authority and, as a minimum, also
ensures:
(i) The aircraft can continue at a pressure altitude that will allow continued safe flight and
landing;
(ii) An amount of stored supplemental oxygen, in accordance with the requirements of the
Authority, and, as a minimum, to supply:
(a) The flight crew for any period the cabin altitude would be above 10,000 feet;
(b) All aircraft occupants for any period the cabin altitude would be above 15,000 feet;
(c) The flight crew and all aircraft occupants in accordance with a) and b) as
appropriate for the route to be flown.
(iii) For aircraft that do not operate above 25,000 feet, the amount of stored oxygen for aircraft
occupants specified in ii) b) above may be reduced, in accordance with the requirements of
the Authority, if at all points along the route to be flown, the aircraft is able to descend safely
within 4 minutes to a cabin pressure altitude of 15,000 ft. or less. (GM)
Auditor Actions
□ Identified/Assessed oxygen systems for aircraft operated at flight altitudes greater than 10,000
ft, but pressurized to maintain cabin altitude of less than 10,000 ft (focus: applicable aircraft carry
stored supplemental oxygen as specified in standard).
□ Interviewed responsible manager(s) in flight operations.
□ Coordinated with maintenance operations (focus: verification that oxygen systems are in
accordance with certification/regulatory requirements).
□ Other Actions (Specify)
Guidance
The intent of this provision is to define a minimum amount of oxygen supply and should not be
confused with requirements for the use of oxygen as specified in FLT 3.11.49.
The operator, in accordance with the requirements of the Authority, typically uses technical guidance
for the computation of sufficient stored breathing oxygen for pressurized aircraft derived from any
one of the following sources, as applicable:
• ICAO Annex 6, 4.3.8.2;
• EU-OPS 1.770 and Appendix 1 to EU-OPS 1.770;
• FAR 135.157 (b), FAR 121.329, 121.331, and 121.333;
• Any equivalent reference document approved or accepted by the Authority for the
computation of sufficient stored breathing oxygen for pressurized aircraft that conforms to the
specifications of this provision.
The specifications of this provision require a minimum amount of oxygen supply be determined
and/or designated by the operator or the Authority.
The descent specified in item ii) is in accordance with emergency procedures specified in the AFM to
a safe altitude for the route to be flown that will allow continued safe flight and landing.
FLT 4.3.6–4.3.36 (Intentionally open)
FLT 4.3.37 The Operator shall ensure all aircraft in its fleet are equipped with, in accordance with
conditions of applicability, the aircraft systems and equipment specified in Table 2.9. (GM)
Auditor Actions
□ Identified/Assessed installation of aircraft systems/equipment, as applicable.
□ Interviewed responsible manager(s).
□ Coordinated with maintenance operations (focus: verification that lifesaving equipment
type/installation are in accordance with regulatory requirements).
□ Examined records of installation, inspection and/or maintenance of the systems/equipment.
□ Observed line flight operations or inspected static aircraft.
□ Other Actions (Specify)
Guidance
The intent of this provision is that, in accordance with conditions of applicability, the systems and
equipment specified in Table 2.9 are installed on each aircraft type in the operator’s fleet.
The condition of applicability of some system or equipment requirements is predicated on the use of
an aircraft type in a certain type of operation (e.g. long-range over-water flights). Where an operator
has a fleet of an aircraft type of which some are not used in the conditional operation, then the
operator would typically have to demonstrate a segregation system that prevent such aircraft from
being used in the conditional operation.
The operator or the Authority may prescribe additional requirements for aircraft systems or
equipment installation.
FLT 4.3.38 The Operator should ensure all aircraft in its fleet are equipped with, in accordance with
conditions of applicability, the aircraft systems and equipment specified in Table 2.12. (GM)
Auditor Actions
□ Identified/Assessed installation of aircraft systems/equipment, as applicable.
□ Interviewed responsible manager(s).
□ Coordinated with MNT auditors (focus: systems or equipment are in accordance with
certification/regulatory requirements).
□ Examined records of installation, inspection and/or maintenance of aircraft systems/equipment.
□ Observed line flight operations or inspected static aircraft.
□ Other Actions (Specify)
Guidance
The intent of this provision is that, in accordance with conditions of applicability, the systems and
equipment specified in Table 2.9 should be installed on each aircraft type in the operator’s fleet.
The condition of applicability of some system or equipment requirements is predicated on the use of
an aircraft type in a certain type of operation (e.g. long-range over-water flights). Where an operator
has a fleet of an aircraft type of which some are not used in the conditional operation, then the
operator would typically have to demonstrate a segregation system that prevent such aircraft from
being used in the conditional operation.
The operator or the Authority may prescribe additional requirements for aircraft systems or
equipment installation.
Applicability
Section 3 addresses the requirements for operational control of flights conducted by multi-engine aircraft,
and is applicable to an operator that conducts such flights, whether operational control functions are
conducted by the operator or conducted for the operator by an external organization (outsourced). Specific
provisions of this section are applicable to an operator based on the operational system in use, the manner
in which authority is delegated by the operator, and the responsibilities, functions, duties or tasks assigned
to the personnel involved.
The IOSA standards and recommended practices (ISARPs) in Section 3 are applicable only to those
aircraft that are of the type authorized in the Air Operator Certificate (AOC) and utilized in commercial
passenger and/or cargo operations, unless applicability is extended to encompass non-commercial
operations as stated in a note immediately under the body of the provision.
Subsection 4.6 contains provisions that address (optional) performance-based methods for achieving
conformity with eligible alternate airport, fuel planning and EDTO provisions contained in other
subsections. General guidance related to the practical application of performance-based methods and
related provisions prefaces subsection 4.6.
Table 3.1 categorizes the personnel that are delegated the authority to exercise operational control,
assigned the overall responsibility for the overall operational control of a flight, assigned the individual
responsibility to carry out one or more functions, duties or tasks related to the operational control of a flight,
or assigned the duty to provide administrative support to others with responsibilities related to operational
control.
Table 3.5 defines the competencies of operational control personnel appropriate to the assignment of
overall responsibility for operational control and/or to carry out one or more operational control functions,
duties or tasks according to their specific competencies.
All personnel utilized to perform operational control functions as defined in Table 3.1, or that act in a
manner consistent with the functional categories specified in Table 3.1 and the competencies specified in
Table 3.5, irrespective of management or post holder title, are subject to specified training and qualification
provisions in this section relevant to the operational control function performed.
Individual provisions, and/or individual sub-specifications within a provision, that:
• Begin with a conditional phrase (“If the Operator...”) are applicable if the operator meets the
condition(s) stated in the phrase. The conditional phrase serves to define or limit the applicability
of the provision (e.g. “If the operator utilizes…” or “If an FOO or FOA is utilized…”).
• Do not begin with a conditional phrase are applicable to all operators unless determined otherwise
by the Auditor.
• Begin with a conditional phrase that specifies the use of a Flight Operations Officer (FOO) by an
operator are applicable when the operator assigns the FOO, as defined in the IRM and delegated
authority in accordance with Table 3.1, responsibility to carry out operational control functions,
duties or tasks related to all of the competencies of operational control as specified in Table 3.5.
• Begin with a conditional phrase that specifies the use of a Flight Operations Assistant (FOA) by an
operator are applicable when the operator assigns the FOA, as defined in the IRM, responsibility
to carry out operational control functions, duties or tasks related to one or more, but not all,
competencies of operational control as specified in Table 3.5.
• Are applicable to all systems of operational control, but with differences in application to each
system, will have those differences explained in the associated Guidance Material (GM).
• Contain the phrase “personnel responsible for operational control” or “personnel with responsibility
for operational control” refer to any suitably qualified personnel with responsibility for operational
control as designated by the operator, to include the pilot-in-command (PIC) unless otherwise
annotated.
•Contain training and qualification requirements are applicable to personnel, other than the PIC,
that are assigned responsibilities related to the operational control of flights. PIC training and
qualification requirements for all systems of operational control are specified in ISM Section 2
(FLT).
• Are eligible for conformance using performance-based methods contain a note referring to
applicable provisions in subsection 4.
Where operational functions, duties or tasks associated with operational control are outsourced to external
service providers, an operator retains overall responsibility for ensuring the management of safety in the
operational control of flights and must demonstrate processes for monitoring applicable external service
providers in accordance with DSP 1.11.2.
General Guidance
Authority and Responsibility
For the purposes of this section authority is defined as the delegated power or right to command or direct, to
make specific decisions, to grant permission and/or provide approval, or to control or modify a process.
For the purposes of this section responsibility is defined as an obligation to perform an assigned function,
duty, task or action. An assignment of responsibility typically also requires the delegation of an appropriate
level of authority.
Operational Control
Operational control is defined as the exercise of authority to initiate, continue, divert or terminate a flight in the
interest of the safety and security of the aircraft and its occupants. An operator may delegate the authority for
operational control of a specific flight to qualified individuals, but typically retains overall authority to operate
and control the entire operation. An operator may also assign the responsibility to carry out specific
operational control functions, duties, or tasks related to the conduct of each flight to identifiable, qualified and
knowledgeable individual(s), but would remain responsible (and accountable) for the conduct of the entire
operation.
Any individuals delegated the authority to make specific decisions regarding operational control would also
be responsible (and accountable) for those decisions. Additionally, individuals assigned the responsibility to
carry out specific operational control functions, duties, or tasks related to the conduct of each flight are also
responsible (and accountable) for the proper execution of those functions, duties, or tasks. In all cases, the
authority and responsibility attributes of operational control personnel are clearly defined and documented by
the operator, and communicated throughout the organization.
It is important to note that when an operator assigns the responsibility for functions, duties or tasks related to
the initiation, continuation, diversion and termination of a flight to employees or external service providers,
such operator retains full responsibility (and accountability) for the proper execution of those functions, duties
or tasks by ensuring:
• The training and qualification of such personnel meets any regulatory and operator requirements;
• Personnel are performing their duties diligently;
• The provisions of the Operations Manual are being complied with;
• An effective means of oversight is maintained to monitor the actions of such personnel for the
purposes of ensuring operator guidance and policy, as well regulatory requirements, are complied
with.
Authority for the Operational Control of Each Flight
In order to practically exercise operational control of flight operations, an operator typically delegates the
authority for the initiation, continuation, diversion or termination of each flight to qualified individuals. Such
delegation occurs in conjunction with an operator's overall system of operational control as follows:
• Shared systems, wherein operational control authority is shared between the pilot-in-command (PIC)
and a flight operations officer/flight dispatcher (FOO) or designated member of management, such
as the Director of Flight Operations (or other designated post holder);
For example: The FOO (or designated member of management, as applicable) has the authority to
divert, delay or terminate a flight if in the judgment of the FOO, a designated member of management
or the PIC, the flight cannot operate or continue to operate safely as planned or released.
• Non-shared systems, wherein operational control authority is delegated only to the PIC.
For example: Only the PIC has the authority to terminate, delay, or divert a flight if in the judgment of
the PIC the flight cannot operate or continue to operate safely as planned.
Responsibility for Operational Control of Each Flight
While an operator retains full responsibility (and accountability) for the entire operation, the responsibility for
the practical operational control of each flight is typically assigned to qualified individuals. As with the
delegation of authority, the assignment of responsibility related to the operational control of each flight occurs
in conjunction with a system of operational control as follows:
• Shared systems, wherein operational control responsibility for each flight is shared between the PIC
and an FOO, or between the PIC and a designated member of management such as the Director of
Flight Operations (or other designated post holder). In either shared system, the PIC, FOO or
designated member of management, as applicable, may be assisted by other qualified personnel
assigned the individual responsibility (by the operator) to carry out specific operational control
functions, duties or tasks. Such personnel, however, typically do not share operational control
responsibility with the PIC, FOO or designated member of management, as applicable.
For example: The FOO (or designated member of management) and the PIC are jointly responsible
(and accountable) for the functions, duties or tasks associated with the operational control of a flight,
such as pre-flight planning, load planning, weight and balance, delay, dispatch release, diversion,
termination, etc. In such systems, the FOO (or designated member of management) may carry out
such responsibilities unassisted or be assisted by qualified personnel assigned the individual
responsibility (by the operator) to carry out specific operational control functions, duties or tasks.
• Non-shared systems, wherein the PIC is solely responsible for all duties, functions, or tasks
regarding operational control of each flight, and may carry out such responsibilities unassisted or be
assisted by qualified personnel assigned the individual responsibility (by the operator) to carry out
specific operational control functions, duties or tasks.
For example: The PIC is solely responsible (and accountable) for the duties, functions, duties or
tasks associated with the operational control of a flight, and the PIC either acts unassisted or is
assisted by qualified personnel in carrying out functions, duties or tasks such as preflight planning,
load planning, weight and balance, delay, dispatch release, diversion, termination, etc.
Responsibility for Individual Operational Control Functions, Duties, or Tasks
It is important to note that, except for purely non-shared (PIC-only) systems, and as illustrated by the
examples in the previous paragraph, the assignment of responsibilities related to the operational control of
each flight can be further subdivided among a number of qualified and specialized personnel. In such cases,
the responsibility for individual or specific operational control functions, duties or tasks is typically assigned to
FOA personnel who support, brief and/or assist the PIC, FOO personnel and/or designated member(s) of
management, as applicable, in the safe conduct of each flight. Examples of such qualified personnel include
Weather Analysts, Navigation Analysts/Flight Planning Specialists, Load Agents/Planners, Operations
Coordinators/Planners/Controllers, Maintenance controllers and Air Traffic Specialists.
Note: Some operators might choose to assign the responsibility for specialized operational control functions,
such as those described in the example, to fully qualified FOO personnel. In such cases, an FOO, although
qualified in all competencies of operational control, would be functionally acting as an FOA. Therefore, for the
purpose of an audit, FOO personnel acting in this limited capacity are assessed as FOA personnel.
Note: Load Agents/Planners/Controllers who perform load control functions within the scope of ground
handling operations may not be considered FOAs if trained and qualified in accordance with ISM Section 6
(GRH), Subsection 2.1, Training Program.
Administrative Support Personnel
FOA personnel are not to be confused with administrative personnel that lack any operational control
authority, have very limited operational control responsibilities, and who simply provide, collect or assemble
operational documents or data on behalf of the PIC, the FOO, designated member of management or the
operator.
Administrative personnel may be present in any system of operational control, are excluded from the initial
and continuing qualification provisions of this section, and may be qualified as competent through on-the-job
training (OJT), meeting criteria as specified in a job description, or through the mandatory use of written
instruments such as task cards, guidelines, or checklists.
Additional Note
For the purposes of this section, continuing qualification includes recurrent or refresher training as well as any
training necessary to meet recency-of-experience requirements.
Definitions, Abbreviations, Acronyms
Definitions of technical terms used in this ISM Section 3, as well as the meaning of abbreviations and
acronyms, are found in the IATA Reference Manual for Audit Programs (IRM).
(ii) Designated member of management or post holder that has joint authority with the PIC over
the decisions functions, duties or tasks associated with the operational control of each flight;
(iii) Flight operations assistant (FOA) who supports, briefs and/or assists the PIC, FOO, or
designated member of management in the safe conduct of each flight. [SMS] (GM) ◄
Auditor Actions
□ Identified/Assessed defined accountability/authorities/responsibilities for personnel associated
with operational control of flights (focus: definitions for PIC and FOO/FOA/designated
management member positions/functions; communicated throughout organization).
□ Interviewed responsible operational control manager(s).
□ Examined job descriptions of selected operations control personnel (focus: definition of
authority/responsibilities for role/position in operational control system).
□ Other Actions (Specify)
Guidance
Refer to the IRM for definitions of Flight Operations Officer (FOO), Flight Operations Assistant (FOA)
and Post Holder.
The intent of this provision is to ensure the accountability, authorities and responsibilities of
personnel that perform functions relevant to the operational control of flights and the safety of aircraft
operations are communicated throughout the organization(s). The entities that receive such
information are dependent upon the system of operational control but always include the flight
operations organization.
PIC roles and responsibilities are specified in ISM Section 2 (FLT).
Refer to Table 3.1, which contains definitions, duties and responsibilities of relevant operational
control personnel as well as examples of FOAs who might support or assist the FOO, designated
member of management and/or PIC.
The specification in item ii) refers to a designated member of management in a shared system of
operational control (e.g. director of flight operations or other designated post holder).
Refer to the legend of Table 3.1 for examples of FOA personnel who support or assist the FOO
and/or PIC.
The description of duties and responsibilities of an FOO, FOA, and/or designated member of
management typically include a definition of the working relationship with the PIC (e.g. the joint
responsibility of the PIC, FOO and, if applicable, designated member of management in a shared
system of operational control).
Refer to Guidance associated with ORG 1.3.1 located in ISM Section 1 for expanded information
regarding accountability, authority and responsibility as applicable to management and non-
management personnel.
Refer to Guidance associated with ORG 1.4.1 located in ISM Section 1 regarding the need for
internal communication.
DSP 1.3.2 The Operator shall have a process and/or procedure for the delegation of duties within
the management system for operational control that ensures managerial and operational control
continuity is maintained, and responsibility for operational control functions is assumed by qualified
personnel, when:
(i) Managers responsible for operational control are absent from the workplace;
(ii) If utilized in the system of operational control, FOO and/or FOA personnel are absent from
the workplace. (GM) ◄
Auditor Actions
□ Identified/Assessed processes for management system delegation of duties for operational
control personnel (focus: processes maintain managerial continuity during periods when
managers are absent).
□ Interviewed responsible operational control manager(s).
System of
Location System Description
Operational Control
Operational control authority is shared between the PIC
Shared system
(i), (ii) and a flight operations officer/flight dispatcher (FOO) or a
(General)
designated member of management.
The PIC and FOO have joint authority over the decisions
functions, duties or tasks associated with the operational
Full Shared System control of a flight. Such systems are characterized by the
(i)
(PIC and FOO) use of flight monitoring and a dedicated communications
system (voice or electronic) separate from the ATC system
in order to maintain shared authority.
The PIC and FOO have joint authority over all preflight
decisions, functions, duties or tasks associated with the
operational control of a flight, but during flight the PIC has
sole authority. Such systems typically include an agreed
point of transition from joint to sole responsibility (e.g.
Partial Shared pushback or throttle advance for takeoff). This point of
System (PIC and (i) transition also typically coincides with the point when the
FOO) MEL is no longer applicable and flight crews transition to in-
flight procedures. Partial shared systems are characterized
by the use of flight monitoring if required by the Authority or
desired by the Operator, and typically lack the dedicated
communications system necessary to maintain shared
authority in flight.
Functionally equivalent to a full-shared system except that
the PIC and a designated member of management, often
the Director of Flight Operations or any suitably qualified
Shared System (PIC
(ii) and knowledgeable member of management designated by
and Management)
the operator, have joint authority over the decisions,
functions, duties or tasks associated with the operational
control of a flight.
Non-shared system Operational control authority is delegated only to the PIC
Main standard
(General) who may or may not be assisted by other support personnel.
The PIC has sole authority over any and all decisions and
completes all tasks (unassisted) related to the operational
control of each flight. This does not preclude administrative
Non-shared System personnel from providing, collecting or assembling
Main standard
(PIC-only) operational documents or data related to each flight on
behalf of the PIC and as defined in Table 3.1. Such systems
System of
Location System Description
Operational Control
may employ flight monitoring if required by the Authority or
desired by the operator.
The PIC has sole authority over any and all decisions
regarding operational control. However, the PIC is assisted
by others (e.g. FOO, FOA or a member of management)
Non-shared System that lack operational control authority, but are assigned the
Main standard
(PIC-assisted) responsibility to carry out specific functions, duties or tasks,
such as flight planning, flight support, briefing and in-flight
monitoring. Such systems employ flight monitoring if
required by the Authority or desired by the operator.
Note: An FOA can be utilized in combination with FOOs or designated members of management in
all systems of operational control except purely non-shared (PIC-only) systems. If such personnel
are delegated authority in a shared system, however, it would be limited to their specific area of
competency.
Table 3.1 categorizes operational control personnel, defines their authority, identifies their
responsibilities and illustrates the relationship of such responsibilities to the operation as a whole.
DSP 1.3.5 The Operator shall retain the overall responsibility for operational control of each flight
and assign the responsibility to carry out functions, duties or tasks related to the operational control
of each flight only to the PIC, or to a combination of suitably qualified personnel as defined in
Table 3.1, to include the PIC and:
(i) If the Operator has a shared system of operational control responsibility, either of the
following:
(a) An FOO, who shares overall operational control responsibility with the PIC and/or
supports, briefs and/or assists the PIC in the safe conduct of each flight, or
(b) A designated member of management or post holder who shares overall
operational control responsibility with the PIC and/or supports, briefs and/or assists
the PIC or FOO in the safe conduct of each flight.
Note: FOA and/or administrative personnel can be utilized in combination with FOOs and/or
designated members of management in a shared system of operational control, but neither
would share operational control responsibility with the PIC, FOO or designated member of
management.
(ii) If the Operator has a non-shared system of operational control responsibility, one or more of
the following:
(a) An FOO who supports, briefs and/or assists the PIC in the safe conduct of each
flight, or
(b) A designated member of management or post holder who supports, briefs and/or
assists the PIC or FOO in the safe conduct of each flight, or
(c) FOA personnel who support, brief and/or assist the PIC or FOO in the safe conduct
of each flight, and/or
(d) Administrative personnel who do not support, brief and/or assist the PIC or FOO,
but provide, collect or assemble operational documents or data relevant to the
conduct of each flight. (GM)
Note: An operator may choose to assign limited responsibilities to fully qualified FOO
personnel, or to utilize them only to carry out individual or specific operational control
functions, duties or tasks. In such cases, an FOO would be functionally acting as an FOA.
Auditor Actions
□ Identified/Assessed operational control system (focus: operator has overall responsibility for
operational control; responsibilities for individual functions/duties/tasks assigned to positions as
specified in table 3.1.
System of
Operational Item System Description
Control
Shared systems (i) (a), Operational control responsibility is shared between the PIC and an
(General) (i) (b) FOO or designated member of management.
The PIC and FOO are jointly responsible for the decisions,
functions, duties or tasks associated with the operational control of
Full Shared System
(i) (a) a flight. Such systems are characterized by flight monitoring and a
(PIC and FOO)
dedicated communications system (voice or electronic) separate
from the ATC system in order to maintain joint responsibility.
The PIC and FOO are jointly responsible for all preflight
decisions, functions, duties or tasks associated with the operational
Partial Shared control of a flight, but during flight the PIC has sole responsibility.
System (PIC and (i) (a) Such systems are characterized by the use of flight monitoring if
FOO) required by the Authority or desired by the Operator and typically
lack the dedicated communications system necessary to maintain
shared responsibility in flight.
Functionally equivalent to a full-shared system except that the PIC
and a designated member of management, often the Director of
Flight Operations or any suitably qualified and knowledgeable
Shared System member of management designated by the operator are jointly
(PIC and (i) (b) responsible for the functions, duties or tasks associated with the
Management) operational control of a flight. The responsibility to carry out actual
functions, duties or tasks such as flight planning, supporting/
briefing the crew or flight monitoring is typically assigned to other
non-management personnel (e.g. FOOs and/or FOAs).
Non-shared Operational control responsibility is assigned only to the PIC who
(ii) (a)–(d)
Systems (General) may or may not be assisted by other support personnel.
System of
Operational Item System Description
Control
The PIC is solely responsible for completing all tasks (unassisted)
related to the operational control of each flight. This does not
Parent
preclude administrative personnel from providing, collecting or
Non-shared System provision
assembling operational documents or data related to each flight on
(PIC-only) and/or
behalf of the PIC as defined in Table 3.1. Such systems employ
(ii) (d)
flight monitoring if required by the Authority or desired by the
operator.
The PIC is solely responsible for all decisions regarding
operational control. However, the PIC may be assisted by others,
such as an FOA, or an FOO or member of management that
Non-shared System
(ii) (a)–(c) functions as an FOA, who is assigned the responsibility to carry out
(PIC-assisted)
specific functions, duties or tasks, such as flight planning, support,
briefing and in-flight monitoring. Such systems employ flight
monitoring if required by the Authority or desired by the operator.
Note:
• FOOs can be present in shared or non-shared systems of operational control to support,
brief and/or assist the PIC or designated member of management in all competencies of
operational control.
• FOAs can be present in any system of operational control except purely non-shared
(PIC-only) systems, but their responsibilities are limited to their area(s) of expertise.
• FOAs may be assigned specific flight responsibilities depending on area of expertise or
general (non-flight specific) responsibilities in support of other operational control personnel
or functions.
• The responsibilities of administrative personnel utilized in operational control functions are
limited to the provision or collection of operational data.
Table 3.1 categorizes operational control personnel, defines their authority, identifies their
responsibilities and illustrates the relationship of such responsibilities to the operation as a whole.
Table 3.5 defines the competencies of individuals assigned the responsibility for operational control
and/or the responsibility to carry out individual operational control functions, duties or tasks.
When operational control functions are outsourced to external service providers, an operator would
retain overall responsibility for operational control and would ensure such service providers are
subjected to contractual and monitoring processes as specified in DSP 1.11.1 and 1.11.2.
FOO and/or FOA responsibilities for operational control typically begin when assigned a flight during
flight preparation and end after flight termination.
DSP 1.3.6 If an FOO is utilized in the system of operational control, the Operator shall assign
responsibility to such personnel for:
(i) Assisting the PIC in flight preparation and providing required information;
(ii) Assisting the PIC in preparing the operational and ATS flight plans;
(iii) When applicable, signing the operational and ATS flight plans;
(iv) Filing the ATS flight plan with the appropriate ATS unit;
(v) Furnishing the PIC, while in flight, with appropriate information necessary for the safe
conduct of the flight;
(vi) Effective 8 November 2018, notifying the appropriate ATS unit when the position of the
aircraft cannot be determined by an aircraft tracking capability, and attempts to establish
communication are unsuccessful;
(vii) In the event of an emergency, initiating relevant procedures as specified in the OM. (GM)
Note: An operator may choose to assign responsibility for one or more of the specified functions to
an FOA, or the PIC may be assigned the responsibility for filing the flight plan in the case of iv) and/or
for obtaining the necessary information in the case of v).
Auditor Actions
□ Identified/Assessed FOO responsibilities in operational control system (focus: definition of
individual functions/duties/tasks assigned to FOO in specific type of shared/non-shared system
of operational control).
□ Interviewed responsible operational control manager(s).
□ Examined job description for FOO position (focus: position responsibilities appropriate for
assigned functions/duties/tasks in specific type of shared/non-shared system of operational
control).
□ Examined training/qualification records of selected FOO personnel (focus: qualifications
appropriate for assigned responsibilities in operational control system).
□ Observed operational control/flight dispatch operations (focus: assignment of functional
responsibilities/duties to FOO personnel).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Aircraft Tracking.
The effective date and specifications of item vi) of this provision are consistent with ICAO standards
applicable at the time of ISM publication.
The specifications of this provision apply to each FOO qualified in all applicable competencies of
operational control, whether licensed or not, who participates in an approved or accepted system of
operational control and:
• Is delegated authority in accordance with DSP 1.3.4, and/or
• Is assigned the responsibility in accordance with DSP 1.3.5 to carry out operational control
functions, duties or tasks related to all applicable competencies specified in Table 3.5.
The authority and responsibilities of an FOO are defined in Table 3.1.
The specification in item v) may be satisfied by the PIC if such information is available from other
sources that can be accessed while in flight.
DSP 1.3.7 The Operator shall have a process to be used in the event of an emergency situation
that endangers the safety of the aircraft or persons, including those situations that become known
first to the Operator. Such process shall ensure the FOO, FOA or other delegated person:
(i) Initiates emergency procedures, as outlined in the OM, while avoiding taking any action that
would conflict with ATC procedures;
(ii) Notifies the appropriate authorities, without delay, of the nature of the situation;
(iii) Requests assistance, if required;
(iv) Conveys, by any available means, safety-related information to the PIC that may be
necessary for the safe conduct of the flight, including information related to any necessary
amendments to the flight plan. (GM)
Auditor Actions
□ Identified/Assessed OM procedure for implementation of emergency procedures/actions
(focus: definition of operational control positions/persons with assigned responsibility for initiating
emergency procedures/notifying authorities/requesting assistance).
□ Interviewed responsible operational control manager(s).
□ Observed operational control/flight dispatch operations (focus: preparedness to implement
emergency actions).
□ Other Actions (Specify)
Guidance
The specification in item ii) refers to notification to the appropriate authorities without delay and/or
within a period(s) specified by each applicable authority.
Applicable authorities include those authorities that have jurisdiction over international operations
conducted by an operator over the high seas or the territory of a state that is other than the State of
the Operator.
Processes used for operational control of flights in the event of an emergency would typically be
compatible with any operating procedures that have been established by the agencies providing
system services for air traffic control. Such compatibility is necessary to avoid conflict and ensure an
effective exchange of information between the operator and any of the service agencies.
During an operational emergency, the procedures specified in item i) would normally be designed to
not conflict with ATC procedures, such as separation standards, controller instructions, minimum
flight altitude assignments or any other restrictions imposed by ATC. During an emergency, however,
the PIC may exercise emergency authority and take any action necessary in the interest of the safety
of the passengers and aircraft.
It would also be important in this context for the PIC to convey relevant information to the FOO, FOA
or other delegated person during the course of the flight with respect to the emergency situation.
Guidance
Refer to Guidance associated with ORG 1.6.2 located in ISM Section 1.
The operational control positions subject to the specifications of this provision include, as a minimum:
• Managerial personnel, as defined by the operator, required to ensure control and supervision
of flight operations in accordance with DSP 1.1.1;
• Post holders as required by the Authority if applicable;
FOO knowledge, skill and experience requirements are in accordance with DSP 1.5.5 and 1.5.6.
FOA knowledge, skill and experience requirements are in accordance with DSP 1.5.7.
FOO and FOA training requirements are in accordance with the applicable provisions of
Subsection 2, Training and Qualification.
PIC knowledge, skill, experience and training requirements are in accordance with the applicable
provisions of ISM Section 2 (FLT), Subsection 2, Training and Qualification.
DSP 1.5.3 The Operator shall have a process to ensure applicants hired in operational control
functions are required to demonstrate the capability of speaking and reading in a language that will
permit communication with other areas within the organization relevant to operational control.
Auditor Actions
□ Identified/Assessed requirement for language evaluation prior to hiring/selection of operational
control personnel (focus: evaluation of speaking/reading skills; level of proficiency required that
permits communication in subjects relevant to operational control of flights).
□ Identified the language/methodology used for communication with staff in different areas across
the operator's network on matters pertaining to operational control.
□ Interviewed responsible operational control manager(s).
□ Examined language evaluation syllabus (focus: demonstration of speaking/reading language
proficiency).
□ Examined selected operational control personnel selection records (focus: completion of
language evaluation prior to selection).
□ Other Actions (Specify)
DSP 1.5.4 If a licensed FOO is utilized in the system of operational control, the Operator shall
ensure each FOO, prior to being assigned to operational control duties, holds a valid Flight
Operations Officer or Flight Dispatcher license issued or recognized by the State. (GM)
Auditor Actions
□ Identified utilization of FOO in operational control system (focus: applicable to FOO/Flight
Dispatcher function as defined in Table 3.1).
□ Identified regulatory requirement for FOO licensing.
□ Interviewed responsible operational control manager(s).
□ Examined selected FOO personnel selection records (focus: possession of valid license prior to
assignment to perform FOO duties).
□ Observed operational control/flight dispatch operations (focus: valid license for personnel that
perform FOO function as defined in Table 4.1).
□ Other Actions (Specify)
Guidance
The specifications of this provision apply only to each FOO qualified in all applicable competencies of
operational control who participates in an approved or accepted system of operational control and:
• is delegated authority in accordance with DSP 1.3.4, and/or
• Is assigned the responsibility in accordance with DSP 1.3.5 to carry out operational control
functions, duties or tasks related to all applicable competencies specified in Table 3.5, and
(iii) Requires that all personnel who are identified as engaging in any kind of problematic use of
psychoactive substances are removed from safety-critical functions;
(iv) Conforms to the requirements of the Authority. (GM)
Auditor Actions
□ Identified utilization of FOO/FOA/designated management member functions in operational
control system (focus: applicable to FOO/FOA/designated management member functions as
defined in Table 3.1).
□ Identified/Assessed policy regarding use of psychoactive substances by FOO/FOA/designated
management member personnel (focus: definition of specific prohibitions/actions associated with
use of psychoactive substances; policy meets regulatory requirements).
□ Interviewed responsible operational control manager(s).
□ Interviewed selected FOO/FOA/designated management member personnel (focus: familiarity
with psychoactive substance policy).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definitions of Biochemical Testing, Psychoactive Substance and Problematic
Use of Substances.
The specifications of this provision apply to an FOO, designated member of management, FOA or
other persons that are delegated authority and/or assigned responsibilities in accordance with
DSP 1.3.4 and/or DSP 1.3.5, respectively.
Operators subject to laws or regulations of the State that preclude the publication of a psychoactive
substance prohibition policy as specified in this provision may demonstrate an equivalent method of
ensuring that personnel engaging in any kind of problematic use of psychoactive substance abuse do
not exercise their duties and are removed from safety-critical functions.
Re-instatement to safety-critical duties is possible after cessation of the problematic use and upon
determination continued performance is unlikely to jeopardize safety.
Examples of other subjects that might be addressed in a comprehensive and proactive policy
include:
• Education regarding the use of psychoactive substances;
• Identification, treatment and rehabilitation;
• Employment consequences of problematic use of psychoactive substances;
• Biochemical testing;
• Requirements of ICAO and the Authority. (GM)
Additional guidance may be found in the ICAO Manual on Prevention of Problematic use of
Substances in the Aviation Workplace (Doc 9654-AN/945).
The specifications in item i) and ii) refer to the relevant regulations standards and recommended
practices made applicable to the operator by any states or authority with jurisdiction over the
operations of the operator. Applicable authorities typically include those authorities that have
jurisdiction over the international operations conducted by an operator over the high seas or over the
territory of a state that is other than the State of the Operator.
The specification in item i) also refers to applicable regulations imposed on an operator by the State,
which issues the Air Operator Certificate (AOC), and also other states and/or authorities that actively
regulate foreign operators. This may be done through the issuing of an Operational Specification
(OPS SPEC) or specific state legislation.
The specification in item ii) also refers to applicable ICAO standards and/or recommended practices
that are referenced in the operator's documentation.
The specifications of this provision may be satisfied by the flight operations organization
documentation management and control system, if used in conjunction with the operator's system of
operational control.
The specifications in items iii), vi) and vii) refer to relevant manuals, bulletins or directives distributed
by the manufacturer for the purposes of amending aircraft technical specifications and/or operating
procedures.
DSP 1.6.4 The Operator shall ensure documentation used in the conduct or support of operational
control, including the Operations Manual (OM) and associated revisions:
(i) Is identifiable and accessible to operational control personnel;
(ii) Contains legible and accurate information;
(iii) Is written in language(s) understood by operational personnel;
(iv) Is presented in a format that meets the needs of operational control personnel;
(v) Is accepted or approved by the Authority. (GM) ◄
Auditor Actions
□ Identified/Assessed system(s) for management/control of content/format of operational
documentation/data used in operational control system.
□ Interviewed responsible operational control manager(s).
□ Examined selected parts of the OM (focus: legibility/accuracy/format; approval as applicable).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definitions of Operations Manual, State Acceptance and State Approval.
The intent of this provision is for an operator to provide operational documentation in a form that is
acceptable to the Authority and useable by all relevant personnel.
Documentation used in the support of operations control may:
• Exist in paper or electronic form;
• Be issued in more than one language.
Auditor Actions
□ Identified/Assessed operational documents that comprise the OM (focus: external documents
referenced in OM/used by operational control personnel).
□ Interviewed responsible operational control manager(s).
□ Examined selected parts of OM (focus: contents in accordance with in Table 3.2).
□ Other Actions (Specify)
Guidance
The intent of this provision is to ensure operational control personnel are able to find all information
necessary to perform their functions either within the OM or within another document that is
referenced in the OM. The OM is normally identified as a source of operational information approved
or accepted for the purpose by the operator or the State.
Refer to the FLT 1.7.4 and associated guidance for human factors principles observed in the design
of the OM.
DSP 1.7.2 The Operator shall have a description of the Operational Flight Plan (OFP) or equivalent
document that is published in the OM and includes:
(i) Guidance for use by operational control personnel;
(ii) An outline of the content in accordance with specifications in Table 3.3. (GM)
Auditor Actions
□ Identified/Assessed description of OFP in OM.
□ Examined selected OFP(s).
□ Other Action (Specify)
Guidance
Items readily available in other documentation, obtained from another acceptable source or irrelevant
to the type of operation may be omitted from the OFP.
DSP 1.7.3 (Intentionally open)
Auditor Actions
□ Identified the sections of the OM that are relevant to operational control personnel.
□ Interviewed the responsible manager.
□ Interviewed operational control personnel (to ensure they are familiar with the applicable
sections of the OM).
□ Observed front line operational control personnel using the applicable sections of the OM.
□ Other Actions (Specify)
DSP 1.7.4 If an FOO or FOA is utilized in the system of operational control, the Operator shall have
guidance and procedures to enable such personnel, as applicable, to comply with the conditions and
limitations specified in the AOC. (GM)
Auditor Actions
□ Identified utilization of FOO/FOA in operational control system (focus: applicable to
FOO/FOA/designated management member functions as defined in Table 3.1).
□ Identified/Assessed OM guidance/procedures used by FOO/FOA personnel (focus: procedures
ensure compliance with AOC conditions/limitations).
□ Interviewed responsible operational control manager(s).
□ Observed operational control/flight dispatch operations (focus: compliance with AOC
conditions/limitations by FOO/FOA personnel).
□ Other Actions (Specify)
Guidance
The specifications of this provision apply to FOO or FOA personnel who are delegated authority
and/or assigned responsibilities in accordance with DSP 1.3.4 and/or DSP 1.3.5, respectively.
Refer to Guidance associated with FLT 1.2.1 for information on the content of the AOC, to include
conditions and limitations.
The intent of this provision is to ensure conditions and limitations of the AOC are available in
documentation for use, as required, by flight operations officers/flight dispatchers (FOO) and/or flight
operations assistants (FOA).
DSP 1.8.3 If the Operator utilizes an electronic system for the management and control of
operational control records, the Operator shall ensure the system provides for a scheduled
generation of back-up record files. (GM) ◄
Auditor Actions
□ Identified/Assessed process for back-up of electronic operational control records (focus:
system defines schedule for periodic file backup).
□ Interviewed responsible operational control manager(s).
□ Examined selected records of back-up files for electronic records.
□ Other Actions (Specify)
Guidance
Refer to Guidance associated with ORG 2.2.2 located in ISM Section 1.
DSP 1.8.4 The Operator shall have a process or procedures to record and retain operational
information, communications and data for each flight. As a minimum, such retained flight information
and data shall be in accordance with the specifications in Table 3.4 and retained for a period of time
determined by the Operator or the Authority. (GM)
Auditor Actions
□ Identified/Assessed process or procedures for management/control of records in operational
control system (focus: retention of information/data for each flight as specified in Table 3.4).
□ Interviewed responsible operational control manager(s).
□ Examined selected operational control records (focus: information/data for each flight as
specified in Table 3.4).
□ Other Actions (Specify)
Guidance
Operational information and data may be retained by different means (e.g. ACARS logs, paper logs,
manually, computer systems).
Fuel and oil consumption records are typically maintained in accordance with MNT 3.1.1.
The communications typically subject to the record keeping specifications of this provision include
operational voice, text, or data communications to/from:
• Flights from the period beginning at the originating station when flight crew begins their
duties on the flight deck until the flight crew finishes their duties on the flight deck at the
terminating station;
• If applicable, the operations control center.
Aircraft tracking data is typically retained only for the purposes of determining an aircraft's position in
the event of an accident.
DSP 1.8.5 (Intentionally open)
DSP 1.8.6 If an FOO or FOA is utilized in the system of operational control, the Operator shall
ensure training records for such personnel, as applicable, are managed and maintained in
accordance with DSP 1.8.1, to include records that document completion of:
(i) Initial qualification;
(ii) Continuing qualification;
(iii) Competency evaluations. (GM)
Note: Records that document the completion of competency evaluations shall be retained for a
period in accordance with requirements of the Authority, but not less than one year.
Auditor Actions
□ Identified utilization of FOO/FOA in operational control system (focus: applicable to FOO/FOA
functions as defined in Table 3.1).).
Guidance
Refer to Guidance associated with ORG 3.4.10 located in ISM Section 1.
Intervals of surveillance activities might vary depending on the operator.
Previous outcomes would typically be considered in determining audit intervals.
DSP 1.10.3 The Operator shall have a process to ensure significant issues arising from quality
assurance audits of operational control functions are subject to management review in accordance
with ORG 1.5.1 and, as applicable, ORG 1.5.2. [SMS] (GM) ◄
Auditor Actions
□ Identified/Assessed process for management review of operational control quality assurance
issues (focus: continual improvement of quality assurance program).
□ Interviewed responsible quality assurance program manager.
□ Examined selected records/documents of management review of operational control quality
assurance program issues (focus: specific issues/changes identified/implemented to improve
quality assurance program).
□ Other Actions (Specify)
Guidance
Refer to ORG 1.5.1, 1.5.2, 3.4.4 and associated Guidance located in ISM Section 1.
Significant issues would be defined by the operator, but are typically regarded as those issues that
could affect the safety and/or quality of operations.
DSP 1.10.4 The Operator shall have a process for addressing findings that result from audits of
operational control functions, which ensures:
(i) Identification of root cause(s);
(ii) Development of corrective action as appropriate to address the finding(s);
(iii) Implementation of corrective action in appropriate operational areas;
(iv) Evaluation of corrective action to determine effectiveness. (GM) ◄
Auditor Actions
□ Identified/Assessed process for addressing/closing operational control audit findings.
□ Interviewed responsible quality assurance program manager.
□ Examined selected audit reports/records (focus: identification of root cause,
development/implementation of corrective action, follow-up to evaluate effectiveness).
□ Other Actions (Specify)
Guidance
Refer to Guidance associated with ORG 3.4.3 located in ISM Section 1.
DSP 1.11.4 If the Operator utilizes electronic navigation data products for application in operational
control, the Operator shall have processes, approved or accepted by the State, if required, which
ensure such electronic navigation data products acquired from suppliers, prior to being used in
operations:
(i) Are assessed for a level of data integrity commensurate with the intended application;
(ii) Are compatible with the intended function of equipment in which it is installed. (GM)
Auditor Actions
□ Identified/Assessed processes for acceptance of electronic navigation data products acquired
for application in operational control (focus: assessment for data integrity/functionality are
compatible with intended use; processes have regulatory acceptance).
□ Interviewed responsible operational control manager(s).
□ Examined selected product acceptance records (focus: products assessed for data
integrity/functionality).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Navigation Data Integrity.
The responsibility of ensuring electronic navigation data is assessed for integrity and is compatible
with the intended application rests with the operator.
Navigation database integrity can be assured by obtaining data from a supplier accredited in
accordance with approved or accepted standards of data integrity and quality. Such standards
include but are not limited to:
• RTCA/DO-200A, Standards for Processing Aeronautical Data, issued 09/28/98;
• RTCA/DO-201A, Standards for Aeronautical Information, issued 04/19/00;
• Advisory Circular (AC) 20-153, Acceptance of Data Processes and Associated Navigation
Databases, issued 09/20/10.
The specifications in items i) and ii) may be satisfied by an operator, in accordance with State-
approved or -accepted methods for assuring data integrity and compatibility, such as:
• Obtaining a letter of acceptance from an applicable authority stating the data supplier
conforms to a recognized standard for data integrity and compatibility that provides an
assurance level of navigation data integrity and quality sufficient to support the intended
application, or
• The existence of operator validation processes to determine navigation data compatibility
and accuracy that provide an assurance level of navigation data integrity and quality
sufficient to support the intended application.
Monitoring and control of electronic navigation data products acquired from suppliers are also in
accordance with DSP 1.11.3.
DSP 1.11.5 If the Operator has external service providers conduct operational functions associated
with the operational control of flights, the Operator should include auditing as a process for the
monitoring of external service providers in accordance with DSP 1.11.2. (GM) ◄
Auditor Actions
□ Identified/Assessed auditing processes used for monitoring external operational control service
providers.
□ Interviewed responsible operational control manager(s).
□ Examined selected records/reports resulting from auditing of operational control service
providers (focus: audit process ensures provider is fulfilling applicable safety requirements).
□ Other Actions (Specify)
Guidance
Monitoring and control of external organizations by an operator might include random samplings,
product audits, supplier audits, or other similar methods.
Refer to guidance associated with ORG 3.5.3 located in ISM Section 1.
Hazards relevant to the conduct of aircraft operations are potentially associated with:
• Weather (e.g. adverse, extreme and space);
• Geophysical events (e.g. volcanic ash, earthquakes, tsunamis);
• Operations in airspace affected by armed conflict;
• ATM congestion;
• Mechanical failure;
• Geography (e.g. adverse terrain, large bodies of water, polar);
• Airport constraints (e.g. isolated, runway closure, rescue and RFFS capability);
• Alternate airport selection, specification and availability at the estimated time of use;
• Preflight fuel planning and in-flight fuel management;
• Critical fuel scenarios;
• EDTO;
• Performance-based compliance to prescriptive regulations;
• The capabilities of an individual aircraft (e.g. cargo smoke detection, fire suppression
systems, open MEL items);
• Criminal and/or unauthorized activities directed at manned aircraft or in the vicinity of
manned aircraft operations (e.g. laser pointing, unauthorized UAS/RPAS operations);
• Any other condition(s) that would pose a safety risk to aircraft operations (e.g. radiation).
The specifications of this provision may be satisfied by the safety risk assessment and mitigation
program in the flight operations organization if such program includes the operational control system.
Risk assessment and mitigation specific to an operational activity (e.g. alternate airport selection, fuel
planning and/or EDTO) is a risk management process that is central to the performance-based
methods used for development of operational variations in accordance with applicable provisions in
subsection 4.6.
Refer to Guidance associated with ORG 3.1.2 located in ISM Section 1.
Operational Reporting
DSP 1.12.3 The Operator shall have an operational safety reporting system in the organization
responsible for the operational control of flights that:
(i) Encourages and facilitates operational control personnel to submit reports that identify
safety hazards, expose safety deficiencies and raise safety concerns;
(ii) Ensures mandatory reporting in accordance with applicable regulations;
(iii) Includes analysis and operational control management action as necessary to address
safety issues identified through the reporting system. [SMS] (GM) ◄
Auditor Actions
□ Identified/Assessed operational safety reporting system in operational control (focus: system
urges/facilitates reporting of hazards/safety concerns; includes analysis/action to
validate/address reported hazards/safety concerns).
Guidance
Refer to the IRM for the definitions of Safety Assurance and Performance Measures.
Setting performance measures that are consistent with the operator's safety objectives is an element
of the Safety Assurance component of the SMS framework.
Setting performance measures specific to an operational activity (e.g. alternate airport selection, fuel
planning and/or EDTO) is a risk management process that is central to the performance-based
methods used for development of operational variations in accordance with applicable provisions in
subsection 4.6.
By setting performance measures, an operator is able to track and compare its operational
performance against a target (e.g. the performance objective, typically expressed as a rate or
number reduction) over a period of time (e.g. one year). Achievement of the target (or objective)
would represent an improvement in the operational performance. The use of performance measures
is an effective method to determine if desired safety outcomes are being achieved, and to focus
attention on the performance of the organization in managing operational risks and maintaining
compliance with relevant regulatory requirements.
The specifications of this provision may be satisfied by processes in the flight operations organization
if such processes include setting performance measures for the operational control system.
Refer to Guidance associated with ORG 3.2.1 located in ISM Section 1.
Auditor Actions
□ Identified/Assessed process for periodic evaluation of course materials used in training
program for operational control personnel (focus: evaluation addresses compliance with
applicable qualification/performance standards).
□ Interviewed responsible operational control manager(s).
□ Examined selected records of training courseware evaluation (focus: completion of periodic
courseware evaluations).
□ Other Actions (Specify)
Guidance
Such process typically provides for:
• Continual improvement and effectiveness;
• Incorporation of the latest regulatory and operational changes in a timely manner.
DSP 2.1.4–2.1.6 (Intentionally open)
36-month period plus or minus one month from the original qualification anniversary date or base
month. (GM)
Auditor Actions
□ Identified utilization of FOO/FOA in operational control system (focus: applicable to FOO/FOA
functions as defined in Table 3.1).
□ Identified/Assessed recurrent training/evaluation program for FOO/FOA personnel (focus:
curriculum addresses knowledge/proficiency in competencies as specified in Table 3.5; training
interval not greater than 36 months).
□ Interviewed responsible operational control manager(s).
□ Examined training/qualification records of selected FOO/FOA personnel (focus: completion of
recurrent training/evaluation every 36 months).
□ Other Actions (Specify)
Guidance
The specifications of this provision apply to FOO or FOA personnel who are delegated authority
and/or assigned responsibilities in accordance with DSP 1.3.4 and/or DSP 1.3.5, respectively.
Human factors training is accomplished in accordance with DSP 2.2.3.
Dangerous goods training is accomplished in accordance with DSP 2.2.4.
The intent of this provision is to ensure:
• The recurrent training program for FOO personnel addresses all of the competencies that
are relevant to the operations of the operator as specified in Table 3.5;
• The recurrent training program for FOA personnel addresses each of the competencies
relevant to their specific job function and to the operations of the operator as specified in
Table 3.5.
Different methods of conducting recurrent training are acceptable, including formal classroom study,
home study, computer-based training, seminars and meetings. All recurrent training, regardless of
method, is documented and retained in accordance with DSP 1.8.1.
DSP 2.2.3 If an FOO is utilized in the system of operational control, the Operator shall ensure such
personnel receive training in human factors on a frequency in accordance with requirements of the
Authority, if applicable, but not less than once during every 36-month period plus or minus one month
from the original qualification anniversary date or base month. (GM)
Auditor Actions
□ Identified utilization of FOO in operational control system (focus: applicable to FOO function as
defined in Table 3.1).
□ Identified/Assessed human factors training program for FOO personnel (focus: training interval
not greater than 36 months).
□ Interviewed responsible operational control manager(s).
□ Examined training/qualification records of selected FOO personnel (focus: completion of human
factors training every 36 months).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Human Factors.
The specifications of this provision apply to each FOO qualified in all applicable competencies of
operational control, whether licensed or not, who participates in an approved or accepted system of
operational control and:
• Is delegated authority in accordance with DSP 1.3.4, and/or
• Is assigned the responsibility in accordance with DSP 1.3.5 to carry out operational control
functions, duties or tasks related to all applicable competencies specified in Table 3.5.
DSP 2.2.4 If the Operator transports dangerous goods as cargo, and an FOO or FOA is utilized in
the system of operational control with duties or responsibilities related to the carriage of dangerous
goods, the Operator shall ensure such personnel receive training and evaluation in dangerous goods
during initial ground training and subsequently during recurrent training on a frequency in accordance
with requirements of the Authority, if applicable, but not less than once during every 24-month
period. (GM)
Auditor Actions
□ Identified utilization of FOO/FOA in operational control system (focus: applicable to FOO/FOA
functions as defined in Table 3.1).
□ Identified FOO/FOA duties/responsibilities related to transport of dangerous goods.
□ Identified/Assessed dangerous goods training program for FOO/FOA personnel (focus:
curriculum addresses knowledge/proficiency in dangerous goods; training interval not greater
than 24 months).
□ Interviewed responsible operational control manager(s).
□ Examined training/qualification records of selected FOO/FOA personnel (focus: completion of
dangerous goods training every 24 months).
□ Other Actions (Specify)
Guidance
The specifications of this provision apply to FOO or FOA personnel who are delegated authority
and/or assigned responsibilities in accordance with GRH 3.4.2, GRH 3.4.3, DSP 1.3.4 and/or
DSP 1.3.5 respectively, and perform or directly supervise job functions related to the carriage of
dangerous goods as defined by the Authority.
Subjects normally included in dangerous goods training include the following:
• General philosophy;
• Limitations;
• List of dangerous goods;
• Labeling and marking;
• Recognition of undeclared dangerous goods;
• Storage and loading procedures;
• Pilot's notification;
• Provisions for passengers and crew;
• Emergency procedures.
Recurrent training in dangerous goods is typically completed within a validity period that expires
24 months from the previous training to ensure knowledge is current, unless a shorter period is
defined by a competent authority. However, when such recurrent training is completed within the final
3 months of the 24-month validity period, the new validity period may extend from the month on
which the recurrent training was completed until 24 months from the expiry month of the current
validity period. If such recurrent training is completed prior to the final three months (or 90 days) of
the validity period, the new validity period would extend 24 months from the month the recurrent
training was completed.
Refer to the General Guidance at the beginning of this section for additional information regarding the
application of the recurrent training interval.
(i) Assist the PIC in flight preparation and provide the relevant information required;
(ii) File a flight plan with the appropriate ATS unit;
(iii) Furnish the PIC in flight, by appropriate means, with information that may be necessary for
the safe conduct of the flight;
(iv) Initiate, in the event of an emergency, applicable procedures as outlined in the OM. (GM)
Auditor Actions
□ Identified utilization of FOO/FOA/designated management personnel in operational control
system (focus: applicable to FOO/FOA functions as defined in Table 3.1).
□ Identified/Assessed line qualification program for FOO/FOA/designated management
personnel (focus: curriculum includes evaluation of competencies as specified in Table 3.5).
□ Interviewed responsible operational control manager(s).
□ Examined training/qualification records of selected FOO/FOA/designated management
personnel (focus: completion of line qualification prior to operational control duty assignment).
□ Other Actions (Specify)
Guidance
The specifications of this provision apply to designated members of management, as well as FOO or
FOA personnel, who are delegated authority and/or assigned responsibilities in accordance with
DSP 1.3.4 and/or DSP 1.3.5, respectively.
Demonstrations of proficiency are recorded in accordance with DSP 1.8.1.
The intent of this provision is to ensure:
• FOO personnel demonstrate the ability to perform all duty functions;
• FOA personnel demonstrate the ability to perform specific duty functions associated with
their assigned area(s) of responsibility;
• A designated member of management that is directly involved with or directly performs the
functions specified in this provision demonstrates the same functional abilities as specified
for an FOO or FOA. Where the performance of one or more functions specified in this
provision is delegated to others (e.g. to FOOs or FOAs), a designated member of
management would typically demonstrate the knowledge necessary to accept the specified
responsibilities and have an understanding of how such functions are associated with the
operational control of flights.
Item ii) refers to planning activities that involve ATS (e.g. flight plan filing, re-routes during flight,
traffic flow management and/or slot controls).
DSP 2.3.2 (Intentionally open)
DSP 2.3.3 If an FOO is utilized in the system of operational control, the Operator shall ensure such
personnel who have not performed duties as an FOO for a period of 12 consecutive months are not
assigned to perform FOO duties until re-qualified, by demonstrating knowledge and/or proficiency in
accordance with DSP 2.1.1. (GM)
Auditor Actions
□ Identified utilization of FOO in operational control system (focus: applicable to FOO/Flight
Dispatcher functions as defined in Table 3.1).
□ Identified/Assessed re-qualification program for FOO personnel (focus: applicable when FOO
duties have not been performed for 12 months; curriculum addresses knowledge/proficiency in
competencies as specified in Table 3.5).
□ Interviewed responsible operational control manager(s).
□ Examined training/qualification records of selected FOO personnel (focus: completion of re-
qualification prior to re-assignment to operational control duty).
□ Other Actions (Specify)
Guidance
The specifications of this provision apply to each FOO qualified in all applicable competencies of
operational control, whether licensed or not, who participates in an approved or accepted system of
operational control and:
• Is delegated authority in accordance with DSP 1.3.4, and/or
• Is assigned the responsibility in accordance with DSP 1.3.5 to carry out operational control
functions, duties or tasks related to all applicable competencies specified in Table 3.5.
DSP 2.3.4 If an FOO is utilized in the system of operational control, the Operator shall ensure such
personnel are not assigned to FOO duties unless, within the preceding 12 months plus or minus one
month from the original qualification anniversary date or base month, they have either:
(i) Observed one familiarization flight from the flight deck of an aircraft over any area or route
segment where responsibility for operational control will be exercised, or
(ii) If approved by the State and/or if access to the aircraft flight deck is restricted by the
Authority, observed a Line Operational Simulation (LOS) profile accomplished in a
representative flight simulator approved for the purpose by the State, and such profile
addresses the areas or route segments where responsibility for operational control will be
exercised. (GM)
Auditor Actions
□ Identified utilization of FOO in operational control system (focus: applicable to FOO/Flight
Dispatcher functions as defined in Table 3.1).
□ Identified/Assessed flight familiarization program for FOO personnel (focus: flight familiarization
required every 12 months; requires observation over representative area/route during line
flight/simulator LOS).
□ Interviewed responsible operational control manager(s).
□ Examined training/qualification records of selected FOO personnel (focus: completion of flight
familiarization every 12 months).
□ Other Actions (Specify)
Guidance
The specifications of this provision apply to each FOO qualified in all applicable competencies of
operational control, whether licensed or not, who participates in an approved or accepted system of
operational control and:
• Is delegated authority in accordance with DSP 1.3.4, and/or
• Is assigned the responsibility in accordance with DSP 1.3.5 to carry out operational control
functions, duties or tasks related to all applicable competencies specified in Table 3.5.
Operators subject to laws or regulations of the State that prohibit the application of specification i) of
this provision, and that cannot comply with specification ii) of this provision due to the non-existence
of an representative flight training device, may demonstrate an equivalent method of ensuring the
specifications of this provision are satisfied.
The familiarization flight or LOS is typically representative of the operational environment within
which the FOO will be working. Examples of a representative environment include-ultra long haul,
long haul, short haul, over water, mountainous terrain, EDTO, areas of special navigational
requirements, or passenger versus cargo flights.
Familiarization flights typically include at least one takeoff and landing as well as a minimum of 2.5 to
5 hours on the flight deck. If a flight is operating a long-haul segment of more than 5 hours, the FOO
is typically permitted to take a break during the cruise portion of the flight.
An operator, in accordance with the requirements of the State and other applicable authorities, may
adjust the frequency of evaluations specified in this provision to minimize overlap, preserve the
original qualification date and to ensure evaluations are completed within the annual cycle and any
constraints set forth by the operator, State and/or applicable authorities.
3 Line Operations
3.1 General
DSP 3.1.1 (Intentionally open)
DSP 3.1.2 The Operator shall have a process or procedures to ensure the PIC is provided with all
documents, information and data necessary for the safe conduct of the flight. (GM)
Auditor Actions
□ Identified/Assessed operational control process/procedure for provision of documentation to
flight crew (focus: definition of required documents/information/data provided to flight crew).
□ Interviewed responsible operational control manager(s).
□ Observed operational control/flight dispatch operations (focus: PIC provided with
documents/information/data necessary for safe conduct of flight).
□ Other Actions (Specify)
Guidance
The OM typically specifies the documents required by the PIC for the safe conduct of each flight. This
list of required documents may also be replicated on the folder/envelope containing such documents
or displayed in the operational control/flight dispatch center/office for reference purposes.
Additionally, the process or procedures associated with the provision of flight documents typically
includes safeguards to ensure all of the required documents are provided to the PIC prior to each
flight.
DSP 3.2.7 If an FOO or FOA is utilized in the system of operational control, the Operator shall have
a process or procedures to ensure Operator changes in an ATS flight plan that occur prior to
departure are coordinated with the appropriate ATS unit before transmission to the aircraft by the
FOO, FOA or other delegated person. (GM)
Auditor Actions
□ Identified utilization of FOO/FOA in operational control system (focus: applicable to FOO/FOA
functions as defined in Table 3.1).
□ Identified/Assessed process/procedures for coordination of ATC flight plan changes (focus:
FOO/FOA coordinates changes with ATC prior to flight plan transmission to flight crew).
□ Interviewed responsible operational control manager(s).
□ Observed operational control/flight dispatch operations (focus: coordination of changes to ATS
flight plan by FOO/FOA).
□ Other Actions (Specify)
Guidance
The specifications of this provision apply to FOO or FOA personnel who are delegated authority
and/or assigned responsibilities in accordance with DSP 1.3.4 and/or DSP 1.3.5 respectively.
DSP 3.2.8 The Operator shall have guidance and procedures to ensure a flight will not be
commenced unless it has been ascertained, by every reasonable means available, that conditions
and ground facilities required for the flight are adequate for the type of operation. (GM)
Auditor Actions
□ Identified/Assessed guidance/procedures for assessment of required conditions/ground
facilities prior to flight departure (focus: flight planning accounts for adequacy of
conditions/facilities for type of flight operation).
□ Interviewed responsible operational control manager(s).
□ Observed operational control/flight dispatch operations (focus: assessment of relevant
conditions/ground facilities prior to flight departure).
□ Coordinated with flight operations (focus: flight crew preflight assessment of
conditions/facilities).
□ Other Actions (Specify)
Guidance
Areas of operations to be reviewed for adequacy typically include, as applicable:
• Navigation aids;
• Runways, taxiways, ramp areas;
• Curfews;
• PPR (prior permission required);
• Field conditions;
• Lighting;
• ARFF/RFFS (airport rescue and firefighting/rescue and firefighting services);
• Applicable operating minima.
DSP 3.2.9A If the Operator is authorized to conduct certain portions of a commercial flight under
visual flight rules (VFR), the Operator shall have guidance and procedures that:
(i) Specify the type of flight plan to be filed with the appropriate ATS unit;
(ii) Require current meteorological reports, or a combination of current reports and forecasts, to
indicate that meteorological conditions along the portion of the flight to be flown under VFR
will, at the appropriate time, be such as to make compliance with VFR possible. (GM)
Auditor Actions
□ Identified authorization for portions of flights to be conducted under VFR.
□ Identified/Assessed guidance/procedures applicable to conducting portions of flights under
VFR (focus: flight planning accounts for type of flight plan/required meteorological conditions).
□ Interviewed responsible operational control manager(s).
□ Observed operational control/flight dispatch operations (focus: guidance/procedures for control
of flights to be conducted under partial VFR, availability of meteorological reports).
□ Other Actions (Specify)
Guidance
The intent of this provision is to ensure operations that require compliance with VFR are practicable
under the anticipated meteorological conditions.
The specification in item i) refers to the type of flight plan to be filed in instances where certain
portions of a flight will be conducted under VFR. In some cases it may be possible to identify VFR
portions in a predominantly instrument flight rules (IFR) flight plan (e.g. Y and Z designation on an
ICAO flight plan). In other cases, an IFR Flight Plan is normally filed for all flights and an instrument
clearance obtained or cancelled en route in accordance with FLT 3.10.2.
Guidance related to the filing of a composite ICAO flight plan, and the use of the Y designation for
flights initially operated under IFR and Z designation for flights initially operated under VFR, is
contained in Amendment 1 to the Procedures for Air Navigation Services–Air Traffic Management,
Fifteenth Edition (PANS-ATM, Doc 4444).
DSP 3.2.9B The Operator shall have guidance and procedures to ensure a flight to be conducted
in accordance with IFR does not:
(i) Take off from the departure airport unless the meteorological conditions, at the time of use,
are at or above the operator's established airport takeoff operating minima for that
operation; and
(ii) Take off, or continue beyond the point of in-flight re-planning, unless at the airport of
intended landing or at each required alternate airport, current meteorological reports or a
combination of current reports and forecasts indicate that the meteorological conditions will
be, at the estimated time of use, at or above the operator's established airport operating
minima for that operation. (GM)
Auditor Actions
□ Identified/Assessed guidance/procedures for the assessment of airport meteorological
conditions prior to departure of IFR flights (focus: flight planning determines that conditions at
departure/destination/alternate airports meet all applicable requirements).
□ Interviewed responsible operational control manager(s).
□ Observed operational control/flight dispatch operations office (focus: procedures for
monitoring/assessing meteorological conditions for operational airports).
□ Coordinated with flight operations (focus: flight crew assessment of meteorological conditions
for operational airports).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definitions of Alternate Airport and In-flight Re-planning Point.
The intent of this provision is to ensure flights do not takeoff or continue beyond the point of in-flight
re-planning unless the meteorological conditions at each airport specified in i) or ii), are or will be, at
or above the operator's established airport operating minima for the operation at the estimated time
of use.
The specification in item ii) would require the definition and application of alternate airport planning
minima in accordance with DSP 3.2.9C.
DSP 3.2.9C The Operator shall have guidance and procedures, approved or accepted by the
State, for the purposes of determining whether an approach and landing can be safely conducted at
each required alternate airport at the estimated time of use. Such guidance and procedures shall:
(i) Specify the appropriate incremental values for visibility (and ceiling, if required), to be added
to the operator's established airport operating minima;
(ii) Define an appropriate time margin to be applied to the estimated time of arrival for the
purposes of establishing the estimated time of use of an airport and to account for the
uncertainty of flight time estimates or meteorological events. (GM)
Auditor Actions
□ Identified/Assessed guidance/procedures for the application of safety margins in the
assessment/selection of planned alternate airports (focus: flight planning takes into account
defined additives/margins to alternate airport operating minima/times of arrival to account for
forecast uncertainties).
□ Interviewed responsible operational control manager(s).
□ Observed operational control/flight dispatch operations (focus: procedures for
monitoring/assessing approach/landing suitability for planned alternate airport).
□ Coordinated with flight operations (focus: flight crew assessment of suitability of planned
alternate airports).
□ Other Actions (Specify)
Guidance
The intent of this provision is for the operator to have a means to ensure, with a reasonable degree of
certainty, that at the estimated time of use of an alternate airport, the meteorological conditions will
be at or above the operator's established operating minima for an instrument approach. This is
practically accomplished through guidance and procedures for the definition and application of
alternate planning minima.
The additives specified in item i) are typically dependent on the approach facility configuration and
require ceiling be taken into account when the only approaches available are non-precision and/or
circling approaches.
One example of a time margin used to conform to item ii), which is accepted by many national
authorities, is one hour before and after the estimated earliest and latest time of arrival. This may be
reduced in special circumstances, such as when a forecast is only valid for the time of operation of
the airport and does not cover the period before opening.
An operator, in accordance with the requirements of the Authority, typically uses technical guidance
for the development or application of alternate airport planning minima. Such guidance might be
derived from one or more of the following source references, as applicable:
• ICAO Flight Planning and Fuel Management Manual (Doc 9976);
• Commission Regulation EC No. 859/2008 of 20 August 2008.
• Commission Regulation EC No. 965/2012 of 5 October 2012.
• FAA OPSPEC C055 Table.
• Any equivalent reference document approved or accepted by the Authority for the
development or application of alternate planning minima designed to conform to the
specifications of the provision.
DSP 3.2.10 The Operator shall have guidance and procedures to ensure, before a flight is
commenced, oil consumption trends are taken into account and are determined to be such that an
aircraft has sufficient oil to complete each flight. (GM)
Auditor Actions
□ Identified/Assessed guidance/procedures for consideration of oil consumption trends for
planned flights (focus: flight planning takes into account oil consumption trends to ensure flight
completion).
□ Coordinated with ground handling operations (if applicable) (focus: load control personnel are
qualified to perform weight/balance calculations).
□ Other Actions (Specify)
Guidance
Weight and balance calculations may be delegated to a FOO or an appropriately qualified FOA.
The PIC may complete weight and balance calculations, if qualified in accordance with ISM Section 2
(FLT), Subsection 2.1, Training and Evaluation Program.
Load control personnel that perform functions within the scope of ground handling operations may
complete weight and balance calculations if qualified in accordance with ISM Section 6 (GRH),
Subsection 2.1, Training Program.
□ Examined selected flight planning records (focus: consideration of requirement for aircraft
de-/anti-icing operations).
□ Observed operational control/flight dispatch operations (focus: procedures for flights planned to
operate in known/suspected ground icing conditions).
□ Other Actions (Specify)
Guidance
Refer to GRH 4.2.1 located in ISM Section 6 for specifications and associated Guidance related to
the establishment and maintenance of a De-/Anti-icing Program.
Note: Risks associated with variations to the automated reporting interval specifications of this
provision are managed in accordance with DSP 3.5.4.
▲ An operator may conform to DSP 3.5.2 through Active Implementation as long as the
implementation Action Plan (IAP) projects conformance on or before 31 August 2020.
Auditor Actions
□ Identified/Assessed Aircraft tracking capability for duration of applicable flights (focus:
operational control procedures/capability for the determination of aircraft position.
□ Interviewed responsible operational control manager(s).
□ Observed operational control/flight dispatch operations (focus: aircraft tracking process).
□ Coordinated with flight operations (focus: verification of flight crew responsibilities, if any, related
to Aircraft tracking).
□ Other Actions (Specify)
Guidance
The effective date and specifications of this provision are consistent with ICAO standards applicable
at the time of ISM publication.
The intent of this recommendation is to encourage operators to always obtain aircraft position data
under the conditions stipulated. Simply stated, it recommends that four-dimensional aircraft position
information be obtained by the operator using automated reporting means at 15 minute intervals
(4D/15) or less when an ATSU obtains this information at greater than 15 minute intervals. It is
important to note that this is a recommended practice applicable in all areas of operations defined in
the Air Operator Certificate (AOC) and related operations specifications. It is also applicable to a wide
range of aircraft given the low takeoff mass threshold.
An operator may conform to the automation and interval specifications of this provision in accordance
with DSP 3.5.4.
Guidance on aircraft tracking is contained in the ICAO Normal Aircraft Tracking Implementation
Guidelines (Cir 347) scheduled for unedited release in May 2017.
DSP 3.5.3 Effective 8 November 2018, the Operator shall track the position of an aircraft through
automated reporting at least every 15 minutes for the portion(s) of the in-flight operation that is
planned in an oceanic area(s) under the following conditions:
(i) The aircraft has a maximum certificated takeoff mass of over 45 500 kg and a seating
capacity greater than 19;
(ii) Where an Air Traffic Services Unit (ATSU) obtains aircraft position information at greater
than 15 minute intervals. (GM)
Note: For the purpose of aircraft tracking, an oceanic area is defined as the airspace that overlies
waters outside the territory of a state.
Note: Risks associated with variations to the automated reporting interval specifications of this
provision are managed in accordance with DSP 3.5.4.
▲ An operator may conform to DSP 3.5.2 through Active Implementation as long as the
implementation Action Plan (IAP) projects conformance on or before 31 August 2020.
Auditor Actions
□ Identified/Assessed Aircraft tracking capability for duration of applicable flights (focus:
operational control procedures/capability for the determination of aircraft position.
□ Interviewed responsible operational control manager(s).
□ Observed operational control/flight dispatch operations (focus: aircraft tracking process).
□ Coordinated with flight operations (focus: verification of flight crew responsibilities, if any, related
to Aircraft tracking).
□ Other Actions (Specify)
Guidance
The effective date and specifications of item vi) of this provision are consistent with ICAO standards
applicable at the time of ISM publication.
The intent of this provision is to establish an automated aircraft position reporting interval that is to be
maintained in oceanic areas by either the operator or by the relevant ATS unit. Conformance with this
provision would require the operator to determine, prior to flight commencement, whether the
required position information will be obtained by the relevant ATSUs or the tracking responsibility
must be assumed by the operator.
It is important to note that if tracking data becomes unavailable after flight commencement, there is
no implied requirement for the operator to take on the tracking responsibility or have a back-up
means (note use of word “planned” in the body of the provision). Additionally, once airborne, if the
aircraft operates outside of the planned route or area (e.g. unplanned diversion) and 4D/15 position
data cannot be obtained, the operation may continue.
Guidance on aircraft tracking is contained in the ICAO Normal Aircraft Tracking Implementation
Guidelines (Cir 347) scheduled for unedited release in May 2017.
DSP 3.5.4 Effective 8 November 2018, if the Operator assumes the responsibility for aircraft
tracking in accordance with DSP 3.5.2 and/or DSP 3.5.3, the Operator shall ensure risks associated
with any variations to the automated reporting intervals are identified based on the results of a risk
assessment process. Such process shall demonstrate how risks to the operation resulting from such
variations can be managed and shall take into consideration the:
(i) Capability of the operational control systems and processes, including those for contacting
ATS units;
(ii) Overall capability of the aircraft and its systems;
(iii) Available means to determine the position of and communicate with the aircraft;
(iv) Frequency and duration of gaps in automated reporting;
(v) Human factors consequences resulting from changes to flight crew procedures;
(vi) Specific mitigation measures and contingency procedures. (GM)
Note: The risk assessment process specified in this provision is intended to be strategic in nature
and scope. It is not intended, for example, that a specific risk assessment be conducted on a tactical
basis by operational personnel and/or the flight crew. Rather, the process would be used by the
operator to develop mitigations that would be imbedded in policy and procedure (e.g. MEL, theater
specific guidance or other guidance for use by operational personnel) that would in turn allow for
flight commencement (dispatch) in accordance with the risk management outcome(s) of the process.
Auditor Actions
□ Identified use of risk assessment process and/or application of resultant mitigations for
variations to aircraft tracking.
□ Identified applicable processes and procedures for aircraft tracking.
□ Identified/Assessed process for managing risk associated with variations to aircraft tracking
provisions (focus: outcomes of risk assessment process incorporated into policy and procedure.
□ Identified/Assessed guidance/procedures for aircraft tracking (focus: process considers
operational capabilities/reliability associated with determining an aircraft's position).
□ Interviewed responsible operational control manager(s).
□ Examined selected aircraft tracking records.
□ Observed operational control/flight dispatch operations.
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Aircraft Tracking, which includes the definitions of 4D/15 Service
and 4D/15 Tracking.
The effective date and specifications of this provision are consistent with ICAO standards applicable
at the time of ISM publication.
The intent of this provision is to define the criteria that would allow operators under specific
circumstances, to vary from the automated reporting interval(s) specified in DSP 3.5.2 and/or 3.5.3.
Such variations allow for situations where the technical challenges or the duration of exposure may
not warrant and/or support 4D/15 tracking. The provision does not relieve operators of the
responsibility to track their aircraft. It simply defines a risk-based methodology that allows for the
commencement of a flight or series of flights when the recommended or required automated
reporting interval is not achievable in accordance with either DSP 3.5.2 or 3.5.3.
The circumstances when this provision would be applicable include the following singular (i.e. one-
off) or long-term (i.e. continual) scenarios:
• Aircraft equipment failure prior to dispatch (commencement) rendering 4D/15 Tracking
unserviceable;
• Systemic (non-aircraft dependent) failure rendering 4D/15 Tracking unachievable;
• Regular short exposure to lack of 4D/15 coverage (e.g. short A to B flights);
• Temporary airspace closures that may force unequipped aircraft onto routes that would
typically require 4D/15 Tracking;
• Technologically challenging areas (e.g. Polar Routes);
• Other scenarios where, subject to risk assessment results, the technical challenges or the
level of exposure may not warrant (justify) 4D/15 Tracking.
The specifications of this provision allow variations in the means of reporting (e.g. manual vs.
automated) as well as the reporting interval so long as the risks associated with such variations are
appropriately managed.
The specification in item v refers to the hazards (in terms of human factors) associated with making
manual position reports (e.g. HF, VHF, ACARS). Manual position reporting at the 15-minute interval
defined for automated reporting is not considered a viable method to meet tracking requirements as
the additional workload required would distract the flight crew from other duties and have a negative
effect on safety. Additionally, manual position reporting at reduced intervals could introduce a level of
uncertainty regarding accuracy (i.e. introduce a greater potential for error).
Guidance on aircraft tracking is contained in the Normal Aircraft Tracking Implementation Guidelines
(Cir 347) scheduled for unedited release in May 2017.
The specifications of this provision apply to FOO or FOA personnel who participate in an approved or
accepted shared system of operational control and who are delegated authority and/or assigned
responsibilities in accordance with DSP 1.3.4 and/or DSP 1.3.5, as applicable.
FOO or FOA personnel that participate in a partial shared system might lack the dedicated
equipment necessary to maintain shared responsibility in flight.
The communications system can be direct voice or electronic, but an effective system would be
reliable, clear and understandable over the entire route of the flight. An effective system would also
perform adequately and appropriate personnel would be knowledgeable in its use.
DSP 3.6.2 If required by the State, the Operator shall have a system of operational control that
includes flight monitoring for the duration of a flight and ensures timely notification to the Operator by
the PIC of en route flight movement and/or significant deviation from the operational flight plan. (GM)
Auditor Actions
□ Identified regulatory requirement for an operational control system that includes flight
monitoring.
□ Identified/Assessed implementation of flight monitoring for duration of all flights (focus:
operational control procedures/capability for timely PIC communication/notification of en route
flight movement/OFP deviations).
□ Interviewed responsible operational control manager(s).
□ Observed operational control/flight dispatch operations (focus: flight monitoring process;
communication with flight crew).
□ Coordinated with flight operations (focus: verification of flight crew notifications to operational
control).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Flight Monitoring.
DSP 3.6.3 The Operator should have a system of operational control that includes flight monitoring
for the duration of a flight and ensures timely notification to the Operator by the PIC of en route flight
movement and/or significant deviation from the operational flight plan. (GM)
Auditor Actions
□ Identified/Assessed implementation of flight monitoring for duration of all flights (focus:
operational control procedures/capability for timely PIC communication/notification of en route
flight movement/OFP deviations).
□ Interviewed responsible operational control manager(s).
□ Observed operational control/flight dispatch operations (focus: flight monitoring process;
communication with flight crew).
□ Coordinated with flight operations (focus: verification of flight crew notifications to operational
control).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Flight Monitoring.
The intent of this provision is to ensure each flight conducted by the operator is “monitored” by
suitably qualified operational control personnel in accordance with the IRM definition and the
requirements of the applicable Authority.
DSP 3.6.4 If the Operator has a system of operational control that includes automated flight
monitoring, the Operator should have an adequate back-up method of flight monitoring in case of
failure of the automated system. (GM)
Auditor Actions
□ Identified implementation of an automated flight monitoring system.
□ Identified/Assessed implementation of a back-up method of flight monitoring (focus: operational
control plan/procedures/capability for flight monitoring in event of automated system failure;
process for transition from automated system to back-up method).
□ Interviewed responsible operational control manager(s).
□ Observed operational control/flight dispatch operations (focus: back-up flight monitoring
process).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Automated Flight Monitoring System.
DSP 3.6.5A The Operator shall have guidance and procedures to ensure a flight is not continued
toward the airport of intended landing unless the latest available information indicates, at the
expected time of use, a landing can be made either at that airport or at least one destination alternate
airport. (GM)
Auditor Actions
□ Identified/Assessed guidance/procedures for monitoring/assessing conditions at flight
destination/alternate airports (focus: flight continuation permitted only if information indicates
landing can be made at destination/alternate airport).
□ Interviewed responsible operational control manager(s).
□ Observed operational control/flight dispatch operations (focus: monitoring of
destination/alternate airport conditions/information during flight).
□ Other Actions (Specify)
Guidance
The intent of this provision is to ensure personnel with operational control responsibilities have
access to the most current and accurate information available in order to support informed decision-
making related to safe flight completion. This is especially important when the conditions under which
a flight was originally planned have changed after takeoff (e.g. unplanned re-release) or because the
flight was planned with a re-release point (a pre-planned re-release). In either case, the overriding
intent is to ensure operational control personnel, including flight crews, have access to the most
current and accurate information available. Access to such information is typically necessary to
ensure flights do not proceed beyond the last possible point of diversion to an en route alternate
airport (appropriate for the aircraft type) and continue to the destination when, in the opinion of either
the PIC or, in a shared system of operational control, the PIC and FOO it is unsafe to do so.
Information that would be useful in determining whether a landing can be made at the destination or
any required alternate is typically related to:
• Meteorological conditions, both en route and at the airport of intended landing, to include
hazardous phenomena such as thunderstorms, turbulence, icing and restrictions to visibility.
• Field conditions, such as runway condition and availability and status of navigation aids.
• En route navigation systems and facilities status, where possible failures could affect the
safe continuation or completion of the flight.
• En route fuel supply, including actual en route consumption compared to planned
consumption, as well as the impact of any changes of alternate airport or additional en route
delays.
• Aircraft equipment that becomes inoperative, which results in an increased fuel consumption
or a performance or operational decrement that could affect the flight crew's ability to make a
safe landing at an approved airport.
• Air traffic management concerns, such as re-routes, altitude or speed restrictions and
facilities or system failures or delays.
• Security concerns that could affect the routing of the flight or its airport of intended landing.
Refer to Table 2.2 found in ISM Section 2 (FLT) for OM documentation requirements.
DSP 3.6.5B If the Operator selects and specifies en route alternate airports on the OFP, the
Operator shall have guidance and procedures to ensure en route alternate airports selected and
specified on the OFP are available for approach and landing, and the forecast at those airports is for
conditions to be at or above the operating minima approved for the operation. (GM)
Auditor Actions
□ Identified requirement for selection of en route alternate airports.
□ Identified/Assessed guidance/procedures for selection/designation of en route alternate
airports (focus: flight planning includes assessment/selection/designation on OFP of en route
alternate airports with conditions that will permit approach/landing at estimated time of use).
□ Interviewed responsible operational control manager(s).
□ Examined selected OFPs (focus: specification of en route alternate airports).
□ Observed operational control/flight dispatch operations (focus: monitoring of en route airports
conditions/information during flight).
□ Other Actions (Specify)
Guidance
The intent of this provision is for the operator to have a methodology to protect a diversion should a
situation occur that may require an aircraft to divert while en route. For example, such a methodology
typically includes ensuring that operational control personnel and pilots are knowledgeable about
diversion airport alternates, applicable meteorological conditions, and have the means to obtain
information related to the availability of en route alternates.
One way to ensure a reasonable certainty that the weather conditions at a required en route alternate
will be at or above operating minima approved for the operation is through the application and use of
planning minima (at the planning stage) as specified in DSP 3.2.9C. This is done to increase the
probability that a flight will land safely after a diversion to an en route alternate airport.
Refer to Subsection 4.5 for provisions that specify the additional steps necessary to protect an en
route alternate airport when aircraft are engaged in operations beyond 60 minutes (from a point on a
route to an en route alternate airport) or extended diversion time operations (EDTO).
DSP 3.6.5C The Operator shall have procedures to ensure that the inadequacy of any facilities
observed during the course of flight operations is reported to the responsible authority without undue
delay, and to further ensure that information relevant to any such inadequacy is immediately
disseminated to applicable operating areas within the Operator's organization. (GM)
Auditor Actions
□ Identified/Assessed procedures for identifying/reporting inadequacy of relevant/required
facilities during course of flight operations (focus: inadequate facilities reported to responsible
authority/communicated to applicable operating areas within organization).
□ Interviewed responsible operational control manager(s).
□ Examined selected flight records (focus: identification/notification of inadequate facilities).
□ Observed operational control/flight dispatch operations (focus: procedures for reporting of
inadequate facilities observed during flights to applicable authorities/operational areas of
organization).
□ Other Actions (Specify)
Guidance
The specifications of this provision address situations when operational control personnel learn of the
inadequacy of facilities (e.g. navigation aid outages, runway closures) from flight crew reports, ATS,
airport authorities or other credible sources. Operational control personnel would be expected to
convey any safety-critical outages to applicable authorities and relevant operational areas within the
organization.
Applicable authorities include those authorities that have jurisdiction over international operations
conducted by an operator over the high seas or the territory of a state that is other than the State of
the Operator.
DSP 3.6.6 The Operator shall have guidance and procedures to ensure notification to the Operator
when a flight has been completed. (GM)
Auditor Actions
□ Identified/Assessed guidance/procedures for notification of flight completion (focus: operational
control personnel receive notification once flight is completed).
□ Interviewed responsible operational control manager(s).
□ Examined flight records (focus: flight completion notification).
□ Observed operational control/flight dispatch operations (focus: procedures for flight completion
notifications).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definitions associated with Flight Time (Aircraft).
DSP 3.7.2 The Operator shall have guidance and procedures to ensure an FOO, FOA or other
designated personnel notifies the appropriate authority in the quickest manner of any accident
involving an aircraft that results in a fatal or serious injury to any person or substantial damage to the
aircraft or property. (GM)
Auditor Actions
□ Identified/Assessed guidance/procedures for notification to appropriate authority in event of
accident resulting in serious injury/substantial damage (focus: procedures/responsibility for
providing timely accident notification).
□ Interviewed responsible operational control manager(s).
□ Observed operational control/flight dispatch operations (focus: preparedness to provide accident
notification to the appropriate authority).
□ Other Actions (Specify)
Guidance
The intent of this provision is to ensure timely aircraft accident notification to the appropriate authority
by designated personnel utilizing the system specified in DSP 1.4.2 and if applicable, the
specifications of ORG 4.1.17.
DSP 3.7.3 If the Operator transports dangerous goods as cargo, the Operator shall ensure FOO,
FOA and/or other designated operational control personnel:
(i) Have access to the same information pertaining to dangerous goods carried as cargo on
board the aircraft that is provided to the PIC;
(ii) Are assigned the responsibility to provide detailed information without delay about
dangerous goods carried as cargo to emergency services responding to an accident or
serious incident involving the Operator's aircraft. (GM)
Auditor Actions
□ Identified authority for transport of dangerous goods as cargo.
□ Identified/Assessed guidance/procedures for notification to emergency services responding to
an aircraft accident (focus: procedures/responsibility for providing timely dangerous goods
information).
□ Interviewed responsible operational control manager(s).
□ Observed operational control/flight dispatch operations (focus: access to same dangerous
goods information as provided to PIC; preparedness to provide dangerous goods information in
event of accident).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definitions of Dangerous Goods Regulations (DGR) and NOTOC
(Notification to Captain).
The intent of this provision is to ensure:
• Applicable operational control personnel have access to the same dangerous goods
information that has been provided to the PIC;
• The operator assigns an operational control person the responsibility to provide specific
information regarding onboard dangerous goods to emergency services personnel that are
responding to an accident or serious incident involving the operator's aircraft.
An operator, in accordance with requirements of the Authority, typically develops guidance related to
the transport of dangerous goods based on technical information from one or more source reference
documents, to include:
• IATA Dangerous Goods Regulations (DGR);
• An equivalent dangerous goods manual, dangerous goods emergency response guide or
other reference document approved or accepted by the Authority for the development of
flight crew guidance related to the transportation of dangerous goods by air.
The dangerous goods information provided to the PIC is specified in GRH 3.3.4 located in ISM
Section 6.
section 4.6. The specifications in those provisions define the related and interdependent systems,
policies, processes or procedures designed to support the achievement of operational outcomes
equivalent to that of prescriptive compliance. In other words, they allow for variations in “how”
something is achieved as long as “what” is achieved is substantially equal to or better than
prescriptive compliance.
It is important to note that the majority of operators will follow a well-defined and prescriptive
approach to alternate selection, fuel planning and EDTO. There will be cases, however, where
operators that have made significant investments in organizational and operational systems,
advanced technologies and modern aircraft seek to derive greater efficiencies from the inherent
flexibility of performance-based compliance. In such cases, the specifications of sub-section 4.6 are
designed to ensure the operator possesses the capabilities to sustain demonstrable levels of safety
performance that are acceptable to the State and the operator.
Refer to the IRM for the definition of Performance-Based Compliance.
the robustness of any methodologies used for takeoff alternate airport selection is commensurate
with the breadth and complexity of the operation.
DSP 4.1.2 The Operator shall have a system, process, and/or procedures for alternate airport
selection to ensure a takeoff alternate airport selected in accordance with DSP 4.1.1 is located within
a specified flying time from the airport of departure as follows (as applicable to the Operator):
(i) For aircraft with two engines, not more than one hour flying time from the airport of
departure calculated at the single-engine cruise speed, determined from the aircraft
operating manual in ISA and still air conditions using the actual takeoff mass.
(ii) For aircraft with three or more engines, not more than two hours flying time from the airport
of departure calculated at the all-engine operating cruise speed, determined from the aircraft
operating manual in ISA and still air conditions using the actual takeoff mass.
(iii) For aircraft engaged in EDTO (extended diversion time operations) where an alternate
airport meeting the flight time criteria of i) or ii) is not available, the first available alternate
airport located within the maximum diversion flying time approved for the Operator
considering the actual takeoff mass. (GM)
Note: Pre-existing approved EDTO calculations for the determination of threshold distances
substantially similar to those specified in items i), ii) or iii) may be used to conform with maximum
diversion flight time calculations. For example, operators may be authorized by the State to define
diversion distances for each aircraft type, rounded up to easily recalled figures, that are based on
maximum certificated takeoff mass or on takeoff masses largely representative of those used in
operations.
Note: Conformity with the specifications of this provision can be achieved using performance-based
methods in accordance with applicable provisions in subsection 4.6. Such conformance is achievable
irrespective of the specifications of this provision.
Auditor Actions
□ Identified operator procedures for designating destination alternate airports on the OFP.
□ Identified/Assessed system/process/procedures for selection/designation of a takeoff alternate
airport located a specified distance in flying time from the departure airport (focus: flight planning
takes into account regulatory/operational conditions/requirements/factors applicable to the
operator/flight; such conditions/requirements/factors that are considered/assessed in the takeoff
alternate process are defined.
□ Interviewed responsible operational control manager(s).
□ Examined selected OFPs (focus: designation of takeoff alternate airport in accordance with
relevant factors.
□ Identified/Assessed performance-based method(s) used for takeoff alternate airport selection
(if applicable) (focus: method conforms to specifications of DSP 4.6.2 and 4.6.4).
□ Observed operational control/flight dispatch operations (focus: process for selection/designation
of takeoff alternate airports).
□ Coordinated with flight operations (focus: complementary distance criteria for
selection/designation of takeoff alternate airport).
□ Other Actions (Specify)
Guidance
The principal intent of this provision is to address the safety risks associated with continuing a flight to
an alternate airport when a landing as soon as practicable is warranted, but a return to the airport of
departure immediately after takeoff is not possible. As a practical matter, and to limit the exposure to
such risks, this requires the operator to calculate the maximum diversion flight time for each aircraft
type to ensure a takeoff alternate, when required, will be located within a prescribed flight time from
the airport of departure.
An operator may use a system, process, and/or procedures alone or in any combination in order to
fulfill operational requirements related to the selection of alternate airports. In all cases, however, the
robustness of any methodologies used for takeoff alternate airport selection is commensurate with
the breadth and complexity of the operation.
DSP 4.1.3 If the Operator conducts flights with aircraft that have a published cargo compartment
fire suppression time limit, the Operator should have a system, process, and/or procedures for
alternate airport selection to ensure the diversion time to an airport where a safe landing could be
made does not exceed the cargo compartment fire suppression time capability reduced by an
operational safety margin specified by the State. (GM)
Auditor Actions
□ Identified operator procedures for designating destination alternate airports on the OFP.
□ Identified/Assessed system/process/procedures for selection/designation of takeoff, en route
and destination alternate airports located a specified distance in flying time from the planned
route to ensure that the diversion time is within the specified cargo suppression time limit.
□ Interviewed responsible operational control manager(s).
□ Examined selected OFPs (focus: designation of alternate airports is in accordance with relevant
factors to ensure time to specified alternate airport is within the cargo fire suppression time limit).
□ Observed operational control/flight dispatch operations (focus: process for selection/designation
of alternate airports).
□ Coordinated with flight operations (focus: complementary distance criteria for
selection/designation of alternate airports).
□ Other Actions (Specify)
Guidance
The principal intent of this provision is that an operator's alternate airport selection system, process,
and/or procedures ensure aircraft are operated within the specified cargo fire suppression time limit.
Cargo compartment fire suppression time capabilities will be identified in the relevant aircraft
documentation when they are to be considered for the operation.
Fifteen minutes is an operational safety margin commonly specified by the State.
An operator may use a system, process, and/or procedures alone or in any combination to fulfill
operational requirements related to the selection of alternate airports. In all cases, however, the
robustness of any methodologies used for alternate airport selection is commensurate with the
breadth and complexity of the operation.
DSP 4.1.4 The Operator shall have a system, process and/or procedures for alternate airport
selection that takes into account meteorological conditions and relevant operational information to
ensure a minimum of one destination alternate airport is specified on the OFP and the ATS flight
plan, except under one or more of the following conditions (as approved or accepted by the Authority
based on the operations of the Operator):
(i) When, based on the duration of the flight (from the departure airport, or from the point of in-
flight re-planning to the destination), there is reasonable certainty that, at the estimated time
of use of the destination airport:
(a) The approach and landing may be made under visual meteorological conditions
(VMC), as defined by the State;
(b) Separate runways are usable with at least one runway having an operational
instrument approach procedure.
(ii) When, based on the duration of the flight (from the departure airport, or from the point of in-
flight re-planning to the destination airport), there is reasonable certainty that, at the
estimated time of use of the destination airport, the visibility will be at least 3 miles (5 km)
and the ceiling will be at or above one or more of the following prescribed heights, (as
approved or accepted by the Authority based on the operations of the Operator):
(a) The ceiling height for VMC, as defined by the State;
(b) 1,500 feet above the lowest (TERPS) circling MDA, if a circling approach is required
and authorized for that airport;
(c) 2,000 feet or 500 feet above the (PANS-OPS) circling height, whichever is greater;
(d) 2,000 feet or 1,500 feet above the lowest applicable HAT/HAA, whichever is
greater. (GM)
Note: The specifications of this provision are not applicable for flights conducted under isolated
airport operations as specified in DSP 4.1.7.
Note: Conformity with item ii) requires the definition of the ceiling and visibility expected at the
estimated time of use of the destination airport. Other determinants such as flight time (e.g. 6 hours)
or the availability of separate runways may also be used to further limit the instances when a flight
may depart without nominating a destination alternate, but are not required to achieve conformity
with item ii).
Note: Conformity with the specifications of this provision can be achieved using performance-based
methods in accordance with applicable provisions in subsection 4.6. Such conformance is achievable
irrespective of the specifications of this provision.
Auditor Actions
□ Identified regulatory requirements/exceptions for designation of a minimum of one destination
alternate airport.
□ Identified/Assessed system/process/procedures for selection of a minimum of one destination
alternate airport (focus: flight planning takes into account regulatory/operational conditions/
requirements/factors applicable to the operator/flight; such conditions/requirements/factors that
are considered/assessed in the destination alternate airport selection process are defined.
□ Interviewed responsible operational control manager(s).
□ Examined selected OFPs/ATS flight plans (focus: designation of destination takeoff alternate
airport in accordance with relevant factors.
□ Identified/Assessed method(s) of performance-based compliance used for destination takeoff
alternate airport selection (if applicable) (focus: method conforms to the specifications of DSP
4.6.2 and DSP 4.6.4).
□ Observed operational control/flight dispatch operations (focus: process for selection/designation
of destination alternate airport).
□ Coordinated with flight operations (focus: complementary distance criteria for
selection/designation of a minimum of one destination alternate airport).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definitions of Domestic Flight, Isolated Airport, PANS-OPS and TERPS, and
for the abbreviations HAT and HAA.
The principal intent of this provision is to address the safety risks associated with unavailability of the
destination airport. As a practical matter this is typically accomplished by the selection and
specification of alternate airports in accordance with the technical specifications of the provision
and/or to otherwise ensure, to the extent reasonably practicable, that an airport of intended landing
will be available to a flight at the estimated time of use.
Item i) identifies the basic operational specifications for alternate airport selection, although an
operator may conform to a minimum of one of the numbered specifications of the provision and be in
overall conformance with the intent of the entire provision. Individual conformity with items i) and ii) is
“as approved or accepted by the Authority based on the operations of the Operator” and dependent
on many factors including the regulatory environment and the type of operations conducted.
Isolated airport operations, by definition, preclude the designation of a destination alternate airport
and are conducted in accordance with the planning specifications of DSP 4.1.7 and the fuel
specifications of DSP 4.3.11.
For the purposes of item ii), separate runways are two or more runways at the same airport
configured such that if one runway is closed, operations to the other runway(s) can be conducted.
Applicable authorities typically include those authorities that have jurisdiction over international
operations conducted by an operator over the high seas or the territory of a state that is other than
the State of the Operator.
The operator may use a system, process and/or procedures alone or in any combination in order to
fulfill operational requirements related to the selection of alternate airports. In all cases, however, the
robustness of any methodologies used for destination alternate airport selection is commensurate
with the breadth and complexity of the operation.
DSP 4.1.5 The Operator shall have a system, process and/or procedures for alternate airport
selection that takes into account meteorological conditions and relevant operational information to
ensure a second destination alternate airport is specified on the OFP and the ATS flight plan under
one or more of the following conditions (as approved or accepted by the Authority based on the
operations of the Operator):
(i) When, for the destination airport, meteorological conditions at the estimated time of use will
be below the Operator's established airport operating minima.
(ii) When, for the destination airport, meteorological information is not available (unless the
Authority will not permit the initiation of a flight in the absence of such information).
(iii) If the Operator conducts operations to airports with “marginal” meteorological conditions as
defined in the OM, when, for such operations, the meteorological conditions at the estimated
time of use of the destination and first alternate airports will be marginal.
(iv) If the Operator conducts extended over-water operations as defined in the OM, when, for
such operations, the meteorological conditions at the estimated time of use of the
destination airport will be below the Operator's established operating minima for that
operation, unless there is a reasonable certainty that the first alternate airport will be at or
above the Operator's established operating minima at the estimated time of use. (GM)
Note: The specifications of this provision are not applicable for flights conducted under isolated
airport operations as specified in DSP 4.1.7.
Note: Conformity with the specifications of this provision can be achieved using performance-based
methods in accordance with applicable provisions in subsection 4.6. Such conformance is achievable
irrespective of the specifications of this provision.
Auditor Actions
□ Identified regulatory requirements for designation of a second destination alternate airport.
□ Identified/Assessed system/process/procedures for selection of a second destination alternate
airport (focus: flight planning takes into account regulatory/operational conditions/
requirements/factors applicable to the operator/flight; such conditions/requirements/factors that
are considered/assessed in the destination alternate airport selection process are defined).
□ Interviewed responsible operational control manager(s).
□ Examined selected OFPs/ATS flight plans (focus: designation of second destination alternate
airport in accordance with relevant factors).
□ Identified/Assessed method(s) of performance-based compliance used for second destination
alternate airport selection (if applicable) (focus: method conforms to specifications of DSP 4.6.2
and DSP 4.6.4).
Guidance
Operational flight planning normally includes a review of the route of the flight in conjunction with
published aeronautical and terrain data to ensure compliance with the minimum flight altitudes
defined by the operator and/or applicable authorities. The specifications of this provision typically
require a minimum amount of terrain clearance, specified by the operator and/or applicable
authorities along the route of flight to assure continued safe flight and landing.
Applicable authorities include those authorities that have jurisdiction over international operations
conducted by an operator over the high seas or the territory of a state that is other than the State of
the Operator.
DSP 4.2.3 If the Operator utilizes aircraft with three or more engines, the Operator shall have
guidance and procedures for provision of an OFP that ensures aircraft with three or more engines
can either:
(i) If a second engine becomes inoperative en route, continue from the point where two
engines are assumed to fail simultaneously to an en route alternate airport at which the
landing distance specification for alternate airports is complied with and where it is expected
that a safe landing can be made, or
(ii) If a single engine becomes inoperative en route, and for operations conducted in areas of
the world with limited diversion options, the flight is planned with a more distant alternate
than specified in item i) in order to provide for a diversion for any en route contingency that
may limit the planned operation. Such diversion planning shall be conducted in accordance
with the specifications of a program approved or accepted by the State that requires the
Operator to actively manage the risk of subsequent engine failures or other flight limiting
occurrences and:
(a) Contains special considerations for extended range flights conducted over remote
areas designed to prevent the need for a diversion and protect the diversion to an
alternate airport when it cannot be prevented;
(b) Utilizes aircraft designed and manufactured for the intended operation and
maintained to ensure original reliability;
(c) Requires the Operator to implement and maintain a problem reporting, tracking and
resolution system that contains a means for the prompt reporting, tracking and
resolution of specific problems, as designated by the Operator or State, that could
affect the safety of the operation;
(d) Requires a prescribed level of engine reliability, as measured by an in-flight
shutdown rate (IFSD) determined by the Operator or State, where the risk of
independent failures leading to a loss of thrust from two simultaneous engine
failures ceases to limit the operation and other limiting factors come into play;
(e) Designates a maximum diversion distance in cases where a diversion is necessary
for any reason, including limiting airframe systems and reasons that do not have
anything to do with aircraft reliability, such as passenger illness;
(f) Requires the Operator to demonstrate to the applicable authorities that, when
considering the impact of increasing diversion time, the operation can be conducted
at a level of reliability which maintains an acceptable level of risk. [PCO] (GM)
Note: Item ii) is a Parallel Conformity Option [PCO] for item i); in effect until 1 September 2018.
Auditor Actions
□ Identified/Assessed guidance/procedures for consideration of en route engine failure for flights
conducted by three/four-engine aircraft (focus: flight planning takes into account risks associated
with single/dual engine failure/flight diversion; planned route will allow for single/dual engine
failure at any point and continuation to an en route alternate/diversion airport for safe landing;
designated en route alternates/diversion information shown on OFP).
□ Interviewed responsible operational control manager(s).
□ Examined selected OFPs (focus: planned route of flight; en route alternate airports; diversion
information).
□ Observed operational control/flight dispatch operations (focus: process that ensures OFP route
for three/four-engine aircraft permits, in case of one/two engine failure at any point, flight to
proceed to an airport with safe landing).
□ Coordinated with flight operations (focus: complementary criteria for consideration of en route
single/dual engine failure, diversion options).
□ Other Actions (Specify)
Guidance
Operational flight planning normally includes a review of the route of flight along with published
aeronautical information to ensure the designation of appropriate en route alternates that meet all
operational and regulatory requirements.
Applicable authorities as specified in item f) includes those authorities that have jurisdiction over
international operations conducted by an operator over the high seas or the territory of a state that is
other than the State of the Operator.
DSP 4.3.2 The Operator shall have a system, process and/or procedures to ensure the amount of
usable fuel to be carried on an aircraft in accordance with DSP 4.3.1 is, as a minimum, based on the
following data and operating conditions for each planned flight:
(i) Current aircraft-specific data derived from a fuel consumption monitoring program, if
available, or if current aircraft-specific data is not available, data provided by the aircraft
manufacturer;
(ii) The anticipated aircraft mass;
(iii) Notices to Airmen (NOTAM);
(iv) Current meteorological reports, or a combination of current reports and forecasts;
(v) Applicable air traffic services procedures, restrictions and anticipated delays;
(vi) The effects of deferred maintenance items and/or configuration deviations;
(vii) Any other conditions that might cause increased fuel consumption. (GM)
Auditor Actions
□ Identified/Assessed system/process/procedures for planning sufficient usable fuel for safe
completion of all flights (focus: flight planning takes into account operating data/conditions that
might cause/lead to increased fuel consumption; such operating data/conditions that are
considered/assessed in usable fuel calculation process are defined).
□ Interviewed responsible operational control manager(s).
□ Examined fuel policy (focus: guidance for calculation of minimum required departure/dispatch
fuel).
□ Examined selected OFPs (focus: operating factors considered as basis for required
departure/dispatch fuel).
□ Observed operational control/flight dispatch operations (focus: process or procedures that
ensure planned flight usable fuel is based on all relevant data/operating conditions).
□ Coordinated with flight operations (focus: complementary procedures for assessing minimum
required fuel).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of NOTAM (Notice to Airmen).
The intent of this provision is to define the aircraft-specific data, manufacturer data, operating
conditions and other factors that would be considered by an Operator during the pre-flight
computation of the total usable fuel required for a planned flight. When considered in combination
with DSP 4.3.1, this provision helps to form the basic foundation for the means to complete the pre-
flight calculation of usable fuel.
The specification in item i) refers to the process for ensuring actual aircraft fuel use approximates
planned fuel use within an acceptable margin of error. This is practically accomplished by comparing
the achieved in-flight performance of an aircraft to its predicted performance. Variations between the
achieved performance and the predicted performance will result in a variation of the rate of fuel
consumption which is typically accounted for by the operator during flight planning and in flight.
An operator may use a system, process and/or procedures alone or in any combination in order to
fulfill operational requirements related to the implementation of fuel policy. In all cases, however, the
robustness of any such methodologies is commensurate with the breadth and complexity of the
operation.
Guidance on fuel planning including guidance related to the creation and maintenance of fuel
consumption monitoring programs is contained in the ICAO Flight Planning and Fuel Management
Manual (Doc 9976).
DSP 4.3.3–4.3.4 (Intentionally open)
DSP 4.3.5 The Operator shall have a process and/or procedures to ensure the taxi fuel required in
accordance with its fuel policy is the amount of fuel estimated to be consumed before takeoff, taking
into account local conditions at the departure airport and auxiliary power unit (APU) fuel
consumption. (GM)
Note: The Operator has the option of achieving conformity with the specifications of this provision
using performance-based methods in accordance with applicable provisions in subsection 4.6. Such
conformance is achievable irrespective of the specifications of this provision.
Auditor Actions
□ Identified/Assessed process/procedures for calculation of taxi fuel for all flights (focus: flight
planning takes into account operating data/conditions that might cause/lead to increased taxi fuel
consumption; such operating data/conditions that are considered/assessed in taxi fuel
calculation process are defined).
□ Interviewed responsible operational control manager(s).
□ Examined selected OFPs (focus: operating data/conditions used as basis for taxi fuel).
□ Identified/Assessed method(s) of performance-based compliance used for calculation of taxi
fuel (if applicable) (focus: method conforms to specifications of DSP 4.6.2 and 4.6.5).
□ Observed operational control/flight dispatch operations (focus: process or procedures for
calculating planned taxi fuel).
□ Coordinated with flight operations (focus: complementary procedures for assessing taxi fuel in
accordance with fuel policy).
□ Other Actions (Specify)
Guidance
The intent of this provision is to ensure the accurate computation of taxi fuel in order, to the extent
reasonably practicable, protect the remaining elements in the useable fuel equation. To achieve this
aim, the computation of taxi fuel would take into account foreseeable taxi conditions and delays in
order to result in an amount of fuel generally equal to or greater than the actual taxi fuel consumed
before takeoff.
It is important to note that every usable fuel calculation typically takes into account unforeseen as
well as foreseen deviations from the planned operation. Unforeseen taxi delays, for example, may be
addressed by the use of Statistical Taxi Fuel, the uplift of discretionary fuel when deemed necessary
by the PIC, or the partial consumption of contingency fuel. Consuming contingency fuel during taxi,
however, would be carefully considered as its use on the ground may leave the flight crew with fewer
options, once airborne, to compensate for other unforeseen factor(s).
Guidance on fuel planning, including pre-flight fuel calculation examples, is contained in the ICAO
Flight Planning and Fuel Management Manual (Doc 9976).
DSP 4.3.6 The Operator shall have a process and/or procedures to ensure the trip fuel required in
accordance with its fuel policy is the amount of fuel required to enable the aircraft to fly from takeoff,
or from the point of in-flight re-planning, until landing at the destination airport taking into account the
operating conditions specified in DSP 4.3.2. (GM)
Note: Conformity with the specifications of this provision can be achieved using performance-based
methods in accordance with applicable provisions in subsection 4.6. Such conformance is achievable
irrespective of the specifications of this provision.
Auditor Actions
□ Identified/Assessed process/procedures for calculation of trip fuel for all flights (focus: flight
planning takes into account operating data/conditions that might cause/lead to increased trip fuel
consumption; such operating data/conditions that are considered/assessed in trip fuel calculation
process are defined).
□ Interviewed responsible operational control manager(s).
□ Examined selected OFPs (focus: operating data/conditions used as basis for trip fuel).
□ Identified/Assessed method(s) of performance-based compliance used for calculation of trip
fuel (if applicable) (focus: method conforms to specifications of DSP 4.6.2 and DSP 4.6.5).
□ Observed operational control/flight dispatch operations (focus: process or procedures for
calculating plannedtrip fuel).
□ Coordinated with flight operations (focus: complementary procedures for assessing trip fuel in
accordance with fuel policy).
□ Other Actions (Specify)
Guidance
The intent of this provision is to ensure the accurate computation of trip fuel in order, to the extent
reasonably practicable, ensure that the total planned trip fuel burn is greater than or equal to the
actual trip fuel burn.
The specifications of this provision define trip fuel for preflight planning and in-flight re-planning
purposes, as well as to form the basis for the computation of other fuel amounts (e.g., contingency
fuel, additional fuel). In this context, trip fuel is typically computed from either the departure airport or
the point of in-flight re-planning until landing at the destination airport taking into account the
operating conditions of DSP 4.3.2. In the case of in-flight re-planning (planned or unplanned), the
intent of this provision is for the operator to reconsider (re-compute) the trip fuel required from the re-
planning point to the commercial (actual) destination.
Guidance on fuel planning, including pre-flight fuel calculation examples, is contained in the ICAO
Flight Planning and Fuel Management Manual (Doc 9976).
DSP 4.3.7 The Operator shall have a process and/or procedures to ensure the contingency fuel
required in accordance with its fuel policy is the amount of fuel required to compensate for
unforeseen factors that could have an influence on the fuel consumption to the destination airport.
Contingency fuel shall not be lower than any one or more of the following (as approved or accepted
by the Authority based on the operations of the Operator):
(i) Five (5) percent of the planned trip fuel or of the fuel required from the point of in-flight re-
planning based on the consumption rate used to plan the trip fuel, but in any case not lower
than the amount required to fly for five (5) minutes at holding speed at 450 m (1,500 ft)
above the destination airport in standard conditions.
(ii) If approved or accepted by the Authority for domestic operations; an amount of fuel to fly for
45 minutes at normal cruising fuel consumption, including 30 minutes final reserve. [PCO]
(iii) If approved or accepted by the Authority for international operations, an amount of fuel to fly
for 10 percent of the total time required to fly from the airport of departure or the point of in-
flight re-planning to, and then land at, the airport to which it was released or re-released.
[PCO]
(iv) If approved or accepted by the Authority for the purpose of reducing contingency fuel, not
less than three (3) percent of the planned trip fuel or, in the event of in-flight re-planning,
three (3) percent of the trip fuel for the remainder of the flight, provided that an en route
alternate airport is available in accordance with the requirements of the Authority. [PCO]
(v) If approved or accepted by the Authority based on actual fuel consumption data, an amount
of fuel sufficient for 20 minutes flying time based upon the planned trip fuel consumption
provided that the operator has established a fuel consumption monitoring program for
individual aircraft and uses valid data determined by means of such a program for fuel
calculation. [PCO] (GM)
Note: Items ii), iii), iv) and v) are Parallel Conformity Options (PCOs) for item i); in effect until
1 September 2018.
Note: The specifications in item ii) and iii) are only applicable to an operator if the State and/or the
Operator differentiate between domestic and international flights for the purpose of contingency fuel
calculations.
Note: Conformity with the specifications of this provision can be achieved using performance-based
methods in accordance with applicable provisions in subsection 4.6. Such conformance is achievable
irrespective of the specifications of this provision.
Auditor Actions
□ Identified/Assessed process/procedures for calculation of contingency fuel for all flights (focus:
flight planning takes into account unforeseen operating factors that might cause/lead to
increased fuel consumption to the destination airport; such operating factors that are
considered/assessed in contingency fuel calculation process are defined; minimum contingency
fuel amount in accordance with regulatory requirements is defined).
□ Interviewed responsible operational control manager(s).
□ Examined selected OFPs (focus: operating factors used as basis for contingency fuel).
□ Identified/Assessed method(s) of performance-based compliance used for calculation of
contingency fuel (if applicable) (focus: method conforms to specifications of DSP 4.6.1B).
□ Observed operational control/flight dispatch operations (focus: process or procedures for
calculating planned contingency fuel).
□ Coordinated with flight operations (focus: complementary procedures for assessing contingency
fuel in accordance with fuel policy).
□ Other Actions (Specify)
Guidance
The intent of this provision is to ensure fuel is allocated to compensate for unforeseen factors that
could influence fuel burn to the destination airport. Such factors include, for example, deviations of an
individual aircraft from expected fuel consumption data, forecast meteorological conditions expected
taxi times before takeoff or planned routings and cruising altitudes/levels.
From a safety risk management perspective, contingency fuel is used to mitigate the risks associated
with operational factors or hazards that cannot be planned, anticipated, or controlled. The risk
associated with the improper calculation or complete consumption of contingency fuel is that of
creating a low fuel state or a diversion that could subsequently affect Air Traffic Management (ATM)
and other aircraft.
It is important to note that differences in fuel computation terminology may exist from operator to
operator. For example, required contingency fuel may be a component of other fuel reserves
mandated by the Authority. Regardless of the terms used, however, an operator can conform to
items i) through iii) of the provision if the pre-flight computation of usable fuel allocates an equivalent
or greater amount of fuel as specified in items i) through v) and as applicable to the operator in order
to compensate for unforeseen factors that could influence fuel burn to the destination airport.
An operator may conform to a minimum of one of the numbered specifications of the provision and be
in overall conformity with the intent of the entire provision. Individual conformity with items i) through
v), however, is “as approved or accepted by the Authority based on the operations of the Operator”
and dependent on many factors including the regulatory environment and the type of operations
conducted.
The specification in item ii) protects 15 minutes of contingency fuel plus 30 minutes of final reserve
fuel for a combined domestic reserve of 45 minutes.
Examples related to the computation of contingency fuel are contained in the ICAO Flight Planning
and Fuel Management Manual (Doc 9976).
DSP 4.3.8 The Operator shall have a process and/or procedures to ensure, for flights that require a
single destination alternate airport, the destination alternate fuel required in accordance with its fuel
policy is not lower than amount of fuel that will enable the aircraft to complete all of the following:
(i) Perform a missed approach at the destination airport;
(ii) Climb to the expected cruising altitude;
(iii) Fly the expected routing to the destination alternate airport;
(iv) Descend to the point where the expected approach is initiated;
(v) Conduct the approach and landing at the destination alternate airport. (GM)
Note: The specifications of this provision are not applicable for flights conducted under isolated
airport operations as specified in DSP 4.1.7.
Note: The Operator has the option of achieving conformity with the specifications of this provision
using performance-based methods in accordance with applicable provisions in subsection 4.6. Such
conformance is achievable irrespective of the specifications of this provision.
Auditor Actions
□ Identified/Assessed process/procedures for calculation of destination alternate fuel for flights
that require a single destination alternate airport (focus: flight planning takes into account fuel
consumption required to divert from destination airport and proceed to/hold/land at alternate
airport; diversion flight phases that are considered/assessed in single destination alternate fuel
calculation process are defined).
□ Interviewed responsible operational control manager(s).
□ Examined selected OFPs (focus: factors used as basis for single destination alternate fuel).
□ Identified/Assessed method(s) of performance-based compliance used for calculation of single
destination alternate fuel (if applicable) (focus: method conforms to specifications of DSP 4.6.2
and 4.6.5).
Examples of the computation of alternate fuel are contained in the ICAO Flight Planning and Fuel
Management Manual (Doc 9976).
DSP 4.3.10 The Operator shall have a process and/or procedures to ensure, for flights that do not
require a destination alternate airport, a supplemental amount of fuel is carried to provide for
increased fuel consumption during the flight to the destination airport due to unforeseen operational
occurrences. Such supplemental fuel is only required when the contingency fuel calculated in
accordance with DSP 4.3.7 is insufficient to enable the aircraft to hold at an altitude of 450 m
(1,500 ft) above the destination airport for 15 minutes at the holding speed based on standard
conditions. (GM)
Note: The specifications of this provision are not applicable for flights conducted under isolated
airport operations as specified in DSP 4.1.7 and DSP 4.3.11.
Note: The Operator has the option of achieving conformity with the specifications of this provision
using performance-based methods in accordance with applicable provisions in subsection 4.6. Such
conformance is achievable irrespective of the specifications of this provision.
Auditor Actions
□ Identified/Assessed process/procedures for addition of supplemental fuel to provide for
potential increased fuel consumption for flights that do not require a destination alternate airport
(focus: planned supplemental fuel required when contingency fuel is not sufficient to fly at holding
speed for 15 minutes at 450 m/1500 ft above destination airport).
□ Interviewed responsible operational control manager(s).
□ Examined selected OFPs (focus: basis for addition of supplemental fuel).
□ Identified/Assessed method(s) of performance-based compliance used for supplemental fuel (if
applicable) (focus: method conforms to specifications of DSP 4.6.2 and 4.6.5 ).
□ Observed operational control/flight dispatch operations (focus: process or procedures for
calculating planned supplemental fuel for flights that require no destination alternate airport).
□ Coordinated with flight operations (focus: complementary procedures for assessing second
destination alternate fuel in accordance with fuel policy).
□ Other Actions (Specify)
Guidance
From a safety risk management perspective “no-alternate” fuel is intended to mitigate the safety risks
associated with the occurrence of unforeseen operational contingencies associated with no-alternate
operations. The risk associated with the improper calculation or complete consumption of such fuel is
that of creating a low fuel state.
An operator may satisfy the fuel reserve requirements specified in items i) by defining time, speed,
altitude, and/or engine power conditions in accordance with requirements of the Authority that yield
an equivalent or greater amount of fuel.
Examples of the computation of alternate and contingency fuel are contained in the ICAO Flight
Planning and Fuel Management Manual (Doc 9976).
DSP 4.3.11 If the Operator conducts isolated airport operations, the Operator shall have a process
and/or procedures to ensure the isolated airport fuel calculated in accordance with its fuel policy is
not less than the amount of fuel required to fly for two (2) hours at normal cruise consumption above
the isolated destination airport, including the final reserve fuel calculated in accordance with DSP
4.3.12. (GM)
Note: The Operator has the option of achieving conformity with the specifications of this provision
using performance-based methods in accordance with applicable provisions in subsection 4.6. Such
conformance is achievable irrespective of the specifications of this provision.
Auditor Actions
□ Identified conduct of isolated airport operations that preclude selection/designation of
destination alternate airports.
□ Identified/Assessed process/procedures for calculation of isolated airport fuel for flights to
isolated airports (focus: planned isolated airport fuel is the amount of fuel sufficient to fly for two
hours at normal cruise consumption above destination isolated airport, but not less than the
greater of final reserve fuel).
□ Interviewed responsible operational control manager(s).
□ Examined selected OFPs (focus: factors used as basis for isolated airport fuel).
□ Identified/Assessed method(s) of performance-based compliance used for calculation of
isolated airport fuel (if applicable) (focus: method conforms to specifications of DSP 4.6.2 and
4.6.5).
□ Observed operational control/flight dispatch operations (focus: process or procedures for
calculating planned isolated airport fuel).
□ Coordinated with flight operations (focus: complementary procedures for assessing isolated
airport fuel in accordance with fuel policy).
□ Other Actions (Specify)
Guidance
The intent of this provision is to ensure sufficient fuel is uplifted to mitigate the safety risks associated
with isolated airport operations conducted in accordance with DSP 4.1.7, and to protect final reserve
fuel. As such, final reserve fuel must be computed and protected in accordance with DSP 4.3.12
regardless of the method used to compute “isolated airport fuel”
As a practical matter destination airports are typically considered isolated by an authority when the
fuel required to go-around from Decision Altitude/Height (DA/H) or the Missed Approach Point (MAP)
at the destination airport and then divert to the nearest alternate exceeds, for a turbine engine
aircraft, the fuel required to hold at the destination airport for two hours including final reserve fuel
(e.g. 90 minutes hold + 30 minutes Final Reserve).
Examples of the computation of isolated airport fuel are contained in the ICAO Flight Planning and
Fuel Management Manual (Doc 9976).
DSP 4.3.12 The Operator shall have a process and/or procedures to ensure the final reserve fuel
calculated in accordance with its fuel policy is not less than either (as applicable to the Operator):
(i) The amount of fuel required to fly for 30 minutes at holding speed at 450 m (1,500 ft) above
airport elevation in standard conditions, or
(ii) The amount of fuel required to fly for 30 minutes under speed and altitude conditions
specified by the Operator and as approved or accepted by the Authority. [PCO] (GM)
Note: Item ii) is a Parallel Conformity Option [PCO] for item i); in effect until 31 December 2017.
Auditor Actions
□ Identified/Assessed process/procedures for calculation of final reserve fuel for all flights (focus:
planned final reserve fuel is an amount that is not less than fuel to fly for 30 minutes at holding
speed at 450 m/1500 ft or fuel to fly 30 minutes under speed/altitude conditions
approved/accepted by authority).
□ Interviewed responsible operational control manager(s).
□ Examined selected OFPs (focus: factors used as basis for final reserve fuel).
□ Observed operational control/flight dispatch operations (focus: process or procedures for
calculating planned final reserve fuel).
□ Coordinated with flight operations (focus: complementary procedures for assessing final reserve
fuel in accordance with fuel policy).
□ Other Actions (Specify)
Guidance
The intent of this provision is to ensure the allocation of an amount of fuel to be protected in flight and
preserved upon landing at any airport. As such, it represents the last line of defense in a multi-
layered strategy to ensure safe flight completion. It also serves as the demarcation line between
normal and emergency fuel states for the purposes of the fuel state declarations in accordance with
FLT 3.14.17.
An operator may satisfy the final fuel reserve requirements specified in the provision by defining time,
speed, altitude, and/or engine power conditions in accordance with requirements of the Authority that
yield an equivalent or greater amount of fuel.
DSP 4.3.13 The Operator shall have a process and/or procedures to ensure the additional fuel
calculated in accordance with its fuel policy is a supplementary amount of fuel required to be carried
when the sum of the trip fuel, contingency fuel, alternate fuel and final reserve fuel is insufficient to
meet any one of the following conditions (as applicable to the Operator):
(i) Allow the aircraft engaged in EDTO to comply with critical fuel scenario as established by
the State.
(ii) Allow the aircraft flying greater than 90 minutes from an alternate airport to:
(a) Descend as necessary and proceed to an alternate airport in the event of engine
failure or loss of pressurization, whichever requires the greater amount of fuel
based on the assumption that such a failure occurs at the most critical point along
the route;
(b) Fly for 15 minutes at holding speed at 450 m (1,500 ft) above the alternate airport
elevation in standard conditions;
(c) Make an approach and landing at the alternate airport.
(iii) Allow for any additional operational requirements not covered by items i) and ii). (GM)
Note: The Operator has the option of achieving conformity with the specifications of this provision
using performance-based methods in accordance with applicable provisions in subsection 4.6. Such
conformance is achievable irrespective of the specifications of this provision.
▲ An operator may conform to DSP 4.3.13 ii) through Active Implementation as long as the
implementation Action Plan (IAP) projects conformance on or before 31 August 2018.
Auditor Actions
□ Identified/Assessed process/procedures for calculation of additional fuel for all flights (focus:
planned additional fuel is required when the calculated sum of trip fuel/contingency fuel/alternate
fuel/final reserve fuel is insufficient to meet defined operational conditions or, if applicable, when
calculated using performance-based compliance; operational conditions that are
considered/assessed to determine requirement for additional fuel are defined).
□ Interviewed responsible operational control manager(s).
□ Examined selected OFPs (focus: factors used as basis for additional fuel).
□ Identified/Assessed method(s) of performance-based compliance used for calculation of
additional fuel (if applicable) (focus: method conforms to specifications of DSP 4.6.2 and 4.6.5).
□ Observed operational control/flight dispatch operations (focus: process or procedures for
calculating planned additional fuel when required.).
□ Other Actions (Specify)
Guidance
Basic fuel planning, represented by the sum of the trip fuel, contingency fuel, alternate fuel and final
reserve is predicated on the termination of a flight at the destination or destination alternate. As such,
it only takes into account foreseen and unforeseen factors (excluding system failures) that could
influence fuel consumption to the planned destination or destination alternate. The intent of this
provision is to define the “additional fuel” required to protect against the very unlikely event of an
engine failure or de-pressurization at the most critical point in the flight and presumes that the
majority of the fuel used in basic fuel planning will still be available for use in proceeding to an en
route alternate in the event of such an occurrence.
The specification in item i) applies to aircraft engaged in EDTO. It addresses the fuel necessary to
comply with the EDTO critical fuel scenario as established by the State of the Operator. Such
scenarios typically include additional controls to ensure sufficient fuel is uplifted for conditions that
would contribute to increased fuel burn (e.g. to account for icing, errors in wind forecasting,
deterioration in cruise fuel burn performance, and APU use).
The specification in item iii) is subject to Active Implementation and is applicable to an operator
based on the type of operations conducted (e.g. non-EDTO as specified by the Authority and EDTO).
Examples of additional fuel calculations and critical fuel scenarios are contained in the ICAO Flight
Planning and Fuel Management Manual (Doc 9976).
DSP 4.3.14 The Operator shall have a process and/or procedures to provide for the uplift of
discretionary fuel in accordance with its fuel policy, which is the extra amount of fuel to be carried at
the discretion of the PIC, or the PIC and FOO in a shared system of operational control. (GM)
Auditor Actions
□ Identified utilization of FOO in shared operational control system (focus: applicable to
FOO/Flight Dispatcher function as defined in Table 3.1).
□ Identified/Assessed process/procedures for addition of discretionary fuel for all flights (focus:
planned discretionary fuel is designated when requested by PIC, or requested by PIC/FOO in
shared system of operational control).
□ Interviewed responsible operational control manager(s).
□ Examined selected OFPs (focus: basis for addition of discretionary fuel).
□ Observed operational control/flight dispatch operations (focus: process or procedures for uplift of
discretionary fuel when requested by PIC or PIC/FOO).
□ Coordinated with flight operations (focus: procedures for calculating/requesting discretionary
fuel in accordance with fuel policy).
□ Other Actions (Specify)
Guidance
In a shared system of operational control, the PIC and the Flight Dispatcher/Flight Operations Officer
(FOO) share the responsibility to ensure operating limitations are not exceeded and sufficient fuel is
on board the aircraft to complete the planned flight safely.
DSP 4.3.15 (Intentionally open)
DSP 4.3.16 The Operator should have guidance for use by the flight crew and, if applicable, FOO
personnel for the purpose of increasing fuel state awareness and for providing a means for such
personnel to easily determine one approximate final reserve fuel value applicable to each aircraft
type and variant in the Operator's fleet. (GM)
Auditor Actions
□ Identified utilization of FOO in shared operational control system (focus: applicable to
FOO/Flight Dispatcher function as defined in Table 3.1).
□ Identified/Assessed guidance for use by flight crew/FOO personnel for purpose of increasing
fuel state awareness (focus: guidance provides means for PIC/FOO to easily determine an
approximate final reserve fuel value for each aircraft type/variant).
□ Interviewed responsible operational control manager(s).
□ Observed operational control/flight dispatch operations (focus: guidance to increase PIC/FOO
fuel awareness; means for PIC/FOO to easily approximate final reserve fuel).
□ Other Actions (Specify)
Guidance
The intent of this provision is for an operator to provide the means for operational control personnel
and flight crew members to quickly determine an approximate final reserve fuel value (rounded up to
an easily-recalled figure) for each aircraft type and variant in its fleet. Fuel values determined in
accordance with this provision are not intended to be substitutes for the exact values calculated in
accordance with DSP 4.3.12, but rather as a quick reference used to heighten the awareness of
operational control personnel and flight crews during fuel planning and in-flight fuel management
activities.
The specifications of this provision may be satisfied for all personnel involved in fuel planning,
including the flight crew, through the use of tables or charts that represent fuel in the unit of measure
appropriate for the operation and based on data derived from the Approved Flight Manuals (AFM) for
all types and variants used in operations.
Alternatively, the specifications of this provision can be satisfied for the flight crew by Flight
Management Systems that can display the actual final reserve fuel figure.
Examples of final reserve fuel tables or charts are contained in the ICAO Flight Planning and Fuel
Management Manual (Doc 9976).
4.4 Oxygen
DSP 4.4.1 The Operator shall have guidance and procedures to ensure a flight in a pressurized or
unpressurized aircraft is not commenced unless a sufficient amount of stored breathing oxygen is
carried to supply crew members and passengers in accordance with FLT 4.3.4 and FLT 4.3.5. (GM)
Auditor Actions
□ Identified/Assessed guidance/procedures that specify consideration of aircraft oxygen systems
in flight planning process (focus: flight planning takes into account sufficient aircraft stored
breathing oxygen to supply crew/passengers).
□ Interviewed responsible operational control manager(s).
□ Observed operational control/flight dispatch operations (focus: guidance/procedures to ensure
sufficient stored breathing oxygen for planned flight in pressurized/unpressurized aircraft).
□ Coordinated with maintenance operations (focus: verification that aircraft certified/equipped to
meet oxygen requirements).
□ Other Actions (Specify)
Guidance
The intent of this provision is to ensure operational control personnel with responsibilities related to
flight planning or aircraft scheduling are provided with the necessary information regarding oxygen
carriage requirements in order to appropriately match an aircraft to a planned route.
Refer to Guidance associated with FLT 4.3.4 and FLT 4.3.5 located in ISM Section 2.
4.5 Operations Beyond 60 Minutes from an En Route Alternate Airport and Extended
Diversion Time Operations (EDTO)
DSP 4.5.1 If the Operator conducts flight operations beyond 60 minutes from a point on a route to
an en route alternate airport, including EDTO, the Operator shall have a system, process and/or
procedures to ensure such operations are planned and conducted in accordance with operational
requirements and applicable regulations. (GM)
Auditor Actions
□ Identified conduct of flight operations, including EDTO, over routes beyond 60 minutes from
alternate airport.
□ Identified/Assessed system/process/procedures for planning flights conducted over routes
beyond 60 minutes to an alternate airport (focus: flight planning for EDTO takes into account all
applicable regulations/requirements).
Guidance
The intent of item i) of this provision is to ensure operational control personnel and the flight crew are
knowledgeable about diversion airport options and prevailing weather conditions appropriate for the
type of operation conducted.
The intent of item ii) is to ensure a larger strategy exists for two-engine aircraft engaged in EDTO to
protect a diversion regardless of the reason for the diversion (i.e. technical or non-technical reasons).
Guidance related to the identification and/or protection of en route alternate airports is contained in
ICAO Annex 6, Amendment 36, Attachment D and the ICAO Flight Planning and Fuel Management
Manual (Doc 9976).
DSP 4.5.3 If the Operator utilizes aircraft with two engines in EDTO, the Operator shall have
guidance and procedures to select en route alternate airports for such operations, and ensure en
route alternate airports are specified on:
(i) The OFP or other equivalent operational document available to the PIC in flight;
(ii) The ATS flight plan where required by the State or the ATS system in use. (GM)
Auditor Actions
□ Identified the conduct of EDTO utilizing aircraft with two engines.
□ Identified/Assessed guidance/procedures for en route alternate selection/designation for EDTO
conducted with two-engine aircraft (focus: flight planning includes selection/designation of en
route alternate airports; en route alternate airports shown on OFP; shown on ATS flight plan in
accordance with applicable regulatory requirements).
□ Interviewed responsible operational control manager(s).
□ Examined selected EDTO OFPs (focus: designation of en route alternate airports).
□ Observed operational control/flight dispatch operations (focus: guidance/procedures for
selecting en route alternate airports and specifying on OFP and ATS flight plan for two-engine
aircraft EDTO).
□ Other Actions (Specify)
Guidance
The intent of the specification in item i) is to ensure en route alternates, when required, are selected
and subsequently specified on the OFP or other equivalent operational document available to the
PIC in flight.
The intent of the specification in item ii) is to ensure en route alternates, when required for EDTO, are
specified on the ATS flight when required by the State or other applicable authority.
DSP 4.5.4 If the Operator conducts EDTO, the Operator shall have guidance and procedures to
ensure, for aircraft engaged in such operations:
(i) A flight will not proceed beyond the threshold time unless the identified en route alternate
airports are re-evaluated for availability and the most up-to-date information indicates that,
during the estimated time of use, conditions at those airports will be at or above the
Operator's established airport operating minima for the operation;
(ii) If any conditions are identified that would preclude a safe approach and landing at an
identified en route alternate airport during the estimated time of use, an alternative course of
action has been determined. (GM)
Auditor Actions
□ Identified that EDTO is in use.
□ Identified/Assessed guidance/procedures for the monitoring/assessment of en route alternate
airport conditions during the conduct of EDTO (focus: designated en route alternate airports
monitored/assessed during EDTO to verify continuation of planned flight; when conditions make
designated en route alternate unusable, planned flight evaluated for change).
□ Interviewed responsible operational control manager(s).
General Guidance
Operators and authorities are placing increased emphasis on the use of performance-based
methods to comply with prescriptive regulations. Such methods allow for greater operational flexibility
without degrading the safety performance of an operational activity. This presumption is largely
dependent on an operator's organizational and operational capabilities, the results of safety risk
management activities and the safety performance of a specific operational activity with respect to
specified measurable targets.
To account for this potential shift in emphasis, the provisions in this subsection represent options
available to operators that wish to use performance-based methods to conform to selected DSP
provisions that address alternate airport selection, fuel planning, and/or EDTO. The provisions in this
subsection provide the specifications for a performance-based and alternative means of conforming
to selected provisions identified in other subsections (3.5, 4.1 and 4.3) that contain “prescriptive”
specifications to address the above-mentioned operational areas. A note in each applicable provision
in other subsections will indicate their eligibility for conformance using the performance-based
methods addressed in this subsection.
It is important to note that the provisions and specifications set forth in this subsection are entirely
independent of the operational specifications set forth in the prescriptive counterparts in other
subsections. Additionally, it should also be understood that whereas prescriptive provisions typically
detail “how” an operational activity is to be accomplished, performance-based provisions (in this
subsection) focus on “what” must be accomplished by an operator to ensure the operational activity
produces an equivalent safety outcome.
This shift in emphasis from “how” (prescriptive) to “what” (performance-based) would require an
operator to have the capabilities and resources typically attributed to the implementation of a safety
management system (SMS). A fully implemented SMS could, in fact, be readily tailored to identify the
operational hazards associated with a specific operational activity and provide the necessary risk
assessment and mitigation capabilities to ensure an equivalent safety outcome.
It follows then that the determination of whether operators will be able to reach a target level of safety
performance with respect to a specific operational activity is dependent on numerous, and in many
cases, pre-existing organizational, operational and safety risk management capabilities. The
following table provides the context for the use of performance-based methods (i.e. alternative
means) of conformance for selected IOSA standards that address alternate airport selection, fuel
planning, and/or EDTO.
Note: The following table is provided as guidance material and does not introduce new requirements
or specifications. It should be used as an aid in evaluating an operator's ability to achieve conformity
with the provisions contained in this subsection.
DSP 4.6.2 If the Operator uses performance-based methods for achieving conformity with selected
alternate airport selection, fuel planning, and/or EDTO provisions, the Operator shall ensure the
operations or series of operations conducted in accordance with such variations achieve a desired
level of safety through the implementation of risk management processes, to include:
(i) Processes in the flight operations and/or operational control organization that include:
(a) A combination of reactive and proactive methods of hazard identification;
(b) Safety data analysis that identifies existing hazards, and may predict future
hazards, to aircraft operations.
(ii) A risk assessment and mitigation process in the flight operations and/or operational control
organization that specifies processes to ensure:
(a) Hazards identified in conjunction with such operations are analyzed to determine
the corresponding safety risk(s);
(b) Safety risk assessment is accomplished to determine the requirement for risk
mitigation action(s);
(c) When required, risk mitigation actions are developed and implemented.
(iii) The operational reporting system in the flight operations and/or operational control
organization in accordance with FLT 1.12.3 and/or DSP 1.12.3;
(iv) The processes in the flight operations or operational control organization for setting
performance measures as a means for monitoring the safety performance of the operational
activity and to validate the effectiveness of risk controls. (GM)
Note: The provisions in preceding subsections that are eligible for conformance using performance-
based methods in accordance with applicable provisions of this subsection are identified by a note in
the body of the provision.
Note: Although an SMS is not required to support performance-based methods, the subordinate
systems, processes and programs of an existing SMS can be adapted to achieve conformity with the
specifications of this provision.
Note: The development of risk mitigation actions and safety performance monitoring and
measurement is typically an operator responsibility, although in some cases the responsibility of risk
mitigation actions may also be assumed by a relevant authority in conjunction with issuance of an
operational variation (e.g. via OPSPEC, special authorization or other similar regulatory instrument).
In cases where an operator implements this type of variation, the operator still retains the overall
responsibility for safety performance monitoring and measurement of the associated operational
activity, and shall be in conformity with sub-specifications iii) and iv) of this provision to ensure the
desired level of safety is being achieved when the operational variation is in use.
Auditor Actions
□ Identified/Assessed performance-based method(s) of conformance/compliance (focus:
methods include risk management processes: safety/operational data collection/analysis, hazard
identification, risk assessment/mitigation, operational safety reporting, setting performance
measures).
□ Interviewed responsible operational control manager(s).
□ Interviewed selected operational control personnel.
□ Examined selected examples of hazard identification (focus: integration of data/information
collection and analysis into, performance-based methods).
□ Examined selected examples of risk assessment/mitigation (focus: integration of safety risk
assessment/mitigation into performance-based methods).
□ Examined selected operational safety reports (focus: integration of operational safety reporting
into performance-based methods).
Performance-based methods in accordance with this provision are only applicable to the calculation
of taxi fuel, trip fuel, contingency fuel, destination alternate fuel and additional fuel.
Operators using performance-based methods to determine taxi fuel would typically have the
demonstrable capability, using historical data collection and analysis tools, to adjust taxi times to
ensure continuous improvement in preflight taxi fuel calculations.
Operators using performance-based methods to determine contingency fuel would typically have the
demonstrable capability, using historical data collection and analysis tools, to adjust their fuel policy
to ensure continuous improvement in the accuracy and adequacy of contingency fuel calculations.
Examples of performance-based methods and performance measures related to the computation of
contingency fuel are contained in the ICAO Flight Planning and Fuel Management Manual
(Doc 9976).
Guidance on performance-based methods and performance-based compliance to regulation, safety
risk management and the performance of safety risk assessments is contained in the Flight Planning
and Fuel Management Manual (Doc 9976) and the Safety Management Manual (SMM) (Doc 9859).
DSP 4.6.6 If the Operator uses performance-based methods for achieving conformity with selected
provisions that address the conduct of EDTO beyond the time limits of the most time-limited system,
the Operator shall ensure the risk management processes in accordance with DSP 4.6.2 shall, as a
minimum, take into consideration the Operator's organizational and operational capabilities and,
specific to the conduct of EDTO, the:
(i) Overall reliability of the applicable aircraft;
(ii) Reliability of each time limited system;
(iii) Relevant information from the aircraft manufacturer. (GM)
Note: The provisions that address EDTO beyond the time limits of the most time-limited system and
are eligible for conformance using performance-based methods are identified by a note in the body of
the provision.
Auditor Actions
□ Identified use of performance-based method(s) for EDTO flight planning.
□ Identified applicable regulations for EDTO.
□ Identified/Assessed organizational/operational capabilities for managing operational safety risk
in performance-based alternate airport selection (focus: capabilities consistent with applicable
regulatory requirements; capabilities/resources required/used for performance-based EDTO
flight planning are defined).
□ Identified/Assessed guidance/procedures for performance-based EDTO flight planning (focus:
process considers operational capabilities/reliability of aircraft used in EDTO/reliability of time
limited systems/OEM information).
□ Interviewed responsible operational control manager(s).
□ Examined selected EDTO OFPs (focus: aircraft-specific considerations/limitations).
□ Observed operational control/flight dispatch operations (focus: performance-based method for
EDTO flight planning ensures an acceptable level of safety risk).
□ Other Actions (Specify)
Guidance
Performance-based methods for compliance with prescriptive regulations for the conduct of EDTO
are typically approved or accepted by the State.
The intent of this provision is to ensure a performance based methodology exists to address EDTO
beyond the time limits of the most time-limited system.
The organizational and operational capabilities specified in the body of the provision are necessary to
support performance-based methods in general while those specified in items i) through iii) are
specific to aspects of EDTO. A description of the typical relevant organizational and operational
capabilities specified in the body of the provision can be found in the General Guidance at the
beginning of this subsection.
Guidance on performance-based methods and performance-based compliance to regulation, safety
risk management and performing safety risk assessments is contained in the Flight Planning and
Fuel Management Manual (Doc 9976) and the Safety Management Manual (SMM) (Doc 9859).
Applicability
Section 4 is applicable to all operators, and addresses aircraft engineering and maintenance functions
relevant to the airworthiness of the aircraft, engines and components.
Individual provisions or sub-specifications within a provision that:
• Begin with a conditional (“If the Operator...”) are applicable if the operator meets the condition(s)
stated in the phrase.
• Do not begin with a conditional phrase are applicable unless determined otherwise by the Auditor.
An operator may choose to have certain functions within the scope of ground handling operations (e.g.
aircraft loading, aircraft ground handling) performed by maintenance operations personnel. If this situation
exists, the operator must be in conformity with the ISARPs contained in Section 6, Ground Handling
Operations (GRH), that are applicable to the ground handling functions performed by maintenance
operations personnel.
Where an operator outsources the performance of aircraft engineering and maintenance operational
functions to external organizations, the operator retains overall responsibility for ensuring aircraft
airworthiness, and must demonstrate processes for monitoring the applicable external organization(s) in
accordance with MNT 1.11.7.
General Guidance
Definitions of technical terms used in this ISM Section 4, as well as the meaning of abbreviations and
acronyms, are found in the IATA Reference Manual for Audit Programs (IRM).
Auditor Actions
□ Identified/Assessed maintenance management structure and individual manager
appointments.
□ Identified means of ensuring that all maintenance is performed in accordance with the
Maintenance Program and the policies and procedures contained in the MMM
□ Interviewed manager(s) of maintenance operations.
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definitions of EDTO (Extended Diversion Time Operations), Maintenance
Management Manual (MMM) and Maintenance Program.
The management personnel represent the maintenance management structure of the operator and
are responsible for all maintenance functions. Dependent on the size of the operation and the
organizational set up, the maintenance functions may be divided among individual managers or
combined, as applicable to the airline structure.
The actual number of persons employed and their qualifications are dependent upon the tasks to be
performed and thus dependent on the size and complexity of the operation (e.g. route network, line
and/or charter operations, EDTO, fleet composition, aircraft complexity and age), number and
locations of maintenance facilities and the amount and complexity of maintenance contracts.
Consequently, the number of persons needed and their qualifications may differ greatly from one
operator to another and a simple formula covering the whole range of possibilities is not feasible.
MNT 1.1.3 The Operator shall have a manager of maintenance operations that is acceptable to the
Authority, if required, and is responsible, and thus accountable for ensuring:
(i) The management of safety risks in maintenance operations;
(ii) Maintenance operations are conducted in accordance with conditions and restrictions of the
Air Operator Certificate (AOC), and in compliance with applicable regulations and standards
of the Operator. (GM) ◄
Auditor Actions
□ Identified manager for MNT operations.
□ Examined job description of manager for MNT operations (focus: defines
authority/accountability/responsibility for risk management/compliance with AOC requirements).
□ Interviewed manager of MNT operations.
□ Interviewed other managers in MNT operations.
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definitions of Air Operator Certificate (AOC) and Authority.
In most regulatory jurisdictions the individual that is the manager of an operator's maintenance
operations is required to be a post holder that is acceptable to the Authority.
Refer to ORG 1.1.4 located in ISM Section 1.
(ii) Responsibilities for ensuring maintenance operations are conducted in accordance with
conditions and restrictions of the AOC, applicable regulations and standards of the
Operator;
(iii) Lines of accountability throughout maintenance operations, including direct accountability
on the part of senior management for ensuring aircraft airworthiness. [SMS] (GM) ◄
Auditor Actions
□ Identified/Assessed defined accountability/authorities/responsibilities for ensuring aircraft
airworthiness (focus: applicable to management/non-management personnel throughout the
maintenance operations organization).
□ Interviewed MNT operations manager and/or designated management representative(s).
□ Examined job descriptions of selected management/non-management personnel in
maintenance operations.
□ Other Actions (Specify)
Guidance
Refer to Guidance associated with ORG 1.3.1 located in ISM Section 1 for expanded information
regarding accountability, authority and responsibility as applicable to management and non-
management personnel.
MNT 1.2.2 The Operator shall have a process for the delegation of duties within the management
system for maintenance operations that ensures managerial continuity is maintained when
operational managers, including any post holder(s), are absent from the workplace. (GM) ◄
Auditor Actions
□ Identified/Assessed processes for delegation of duties when MNT operations managers are
absent.
□ Interviewed MNT operations manager and/or designated management representative(s).
□ Examined example(s) of delegation of duties due to absence of managers.
□ Other Actions (Specify)
Guidance
Refer to Guidance associated with ORG 1.3.2 located in ISM Section 1.
MNT 1.2.3 The Operator shall ensure a delegation of authority and assignment of responsibility
within the management system for maintenance operations for liaison with regulatory authorities,
original equipment manufacturers (OEMs) and other external entities relevant to maintenance
operations. (GM) ◄
Auditor Actions
□ Identified corporate management individuals with authority for liaison with regulators and other
external entities.
□ Interviewed accountable executive and/or designated management representative(s).
□ Interviewed manager(s) with authority for liaison with regulators and other external entities.
□ Crosschecked to identify managers in operational areas with authority for liaison with regulators
and other external entities.
□ Other Actions (Specify)
Guidance
Refer to Guidance associated with ORG 1.3.3 located in ISM Section 1.
The aircraft is maintained under one approved operator's aircraft maintenance program. When an
operator wishes to change from one approved aircraft maintenance program to another approved
program, a transfer/bridging check/Inspection may need to be performed, as agreed with the
Authority, in order to implement the change.
The operator's aircraft maintenance program typically contains a preface that defines the
maintenance program contents, the inspection standards to be applied, permitted variations to task
frequencies and, where applicable, any procedure to escalate established check/inspection intervals.
A reliability program provides an appropriate means of monitoring the effectiveness of the
maintenance program. Maintenance program optimization relies on implementation of the reliability
program.
Some operator's approved aircraft maintenance programs, not developed from the MRB Process,
use reliability programs as the basis of the approval. The purpose of a reliability program is to ensure
the aircraft maintenance program tasks are effective and carried out at appropriate time intervals.
Actions resulting from the reliability program may result in the escalation or de-escalation, or addition
or deletion, of maintenance tasks, as deemed necessary.
The maintenance program typically contains the following:
• The type/model and registration number of the aircraft, engines and, where applicable,
auxiliary power units (APUs) and propellers;
• The name and address of the operator;
• The operator's reference identification of the program document, the date of issue and issue
number;
• A statement signed by the operator to the effect the specified aircraft is maintained in
accordance with the program and that the program is reviewed and updated as required;
MNT 1.3.2 The Operator shall ensure the design and application of the Maintenance Program
observes human factors principles. (GM)
Auditor Actions
□ Identified an approved maintenance program for each aircraft type.
□ Interviewed responsible manager(s).
□ Examined the process for designing maintenance tasks.
□ Examined selected task cards.
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Human Factors Principles.
Specifically, with respect to observation of human factor principles in design and application of the
maintenance program, the following guidance material provides information regarding the
development of maintenance schedules/programs, including the development of the associated Task
Cards, hereafter referred to as the “Maintenance Item.”
In developing a Maintenance Item, attention is applied to the Human Factors layout of the
Maintenance Item that typically includes, but is not limited to:
• Layout of the Maintenance Item;
• Language used;
• Clear and concise instructions that are as brief and succinct as possible;
• Standardization of all task cards at the beginning to include the appropriate personnel safety
warnings and cautions;
• All notes, warnings and cautions are apparent by the suggested use of boxing, bolding,
italicizing and underlining text;
• Clear instructions for the mechanic/inspector as to where to sign, certify, initial, date the task;
• Where possible, the use of color to display Maintenance Items and task cards;
• Where a Maintenance Item has important graphic details, the graphics are included;
• Full amplification of some tasks rather than referral to a separate document that may distract
the mechanic;
• Referral to the applicable Approved Data.
Guidance material for the application of human factors principles may be found in the ICAO Human
Factors Training Manual, Document 9683.
MNT 1.3.3 The Operator shall ensure amendments to the Maintenance Program:
(i) Are approved by the Authority unless the Operator has been approved to amend the
Maintenance Program without requiring approval of the Authority;
(ii) Are furnished to all organizations and/or persons to whom the Maintenance Program has
been issued.
Auditor Actions
□ Identified/Assessed maintenance program (focus: defines processes for amendment approval
and dissemination).
□ Identified the organizations and/or persons to which the maintenance program(s) are issued.
□ Interviewed responsible manager(s).
□ Examined selected records of recent maintenance program amendments (focus: if applicable,
approval by Authority; dissemination to all program users).
□ Other Actions (Specify)
1.5 Communication
MNT 1.5.1 The Operator shall have a communication system that enables and ensures an effective
exchange of information relevant to operations within the management system for maintenance
operations and with each maintenance organization that performs maintenance for the Operator.
(GM) ◄
Auditor Actions
□ Identified/Assessed system(s) for communicating information relevant to operations within the
MNT operations organization.
□ Interviewed MNT operations manager and/or designated management representative(s).
□ Examined examples of information communication/transfer in MNT operations.
□ Interviewed selected non-management operational personnel in MNT operations.
□ Other Actions (Specify)
Guidance
Refer to Guidance associated with ORG 1.4.1 located in ISM Section 1 for expanded information
regarding methods of communication.
• A statement signed by the operator confirming the MMM and any incorporated documents
identified therein reflect the operator's means of compliance with the Authority requirements;
• A description of the MMM amendment control procedure;
• A means of identifying each page of the MMM. This can be in the form of a list of effective
pages with each page numbered and either dated or marked with a revision number;
• A description of the system used to distribute the MMM, including a distribution list; for non-
scheduled work, temporary copies of the relevant portions of the MMM, or any incorporated
reference, may be sent via facsimile transmission;
• A detailed description of the procedures used to ensure that any maintenance tasks required
by the maintenance schedule, airworthiness directives or any task required for the
rectification of a defect are completed within the required time constraints;
• A description of the evaluation program required by these standards;
• A description of the defect rectification and control procedures, including details of:
– The methods used to detect and report recurring defects;
– The procedures for scheduling the rectification of defects whose repair has been
deferred, if these procedures have not been incorporated into the MEL preamble.
• The procedures used to report service difficulties in accordance with these standards;
• A description of the technical dispatch procedures, including procedures for ferry-flight
authorizations, EDTO (equivalent terms: ETOPS, EROPS, LROPS), all weather operations
and/or any other special operations;
• A description of personnel records to be retained;
• A description of the procedure used to ensure the empty weight and balance of each aircraft
is recorded in accordance with the applicable State of Registry/Authority requirements;
• Maintenance arrangements and a list of all such arrangements, including the procedure used
to communicate to an approved maintenance organization the maintenance requirements for
planned and unforeseen maintenance activities, as well as those mandated by airworthiness
directives;
• Procedure for revising and maintaining the MMM up to date and current;
• Approval of the Authority through approval of the list of effective pages or, in the case of
manuals containing a small number of pages, approval can be identified on each page.
Refer to the Guidance associated with MNT 1.3.2 for information that explains and addresses human
factors principles.
MNT 1.7.2 (Intentionally open)
MNT 1.7.3 The Operator shall ensure the MMM is amended as necessary to keep information
contained therein up to date and to address:
(i) Changes to maintenance or airworthiness requirements;
(ii) Changes in the organization or activities;
(iii) Inadequacies identified through internal or external audit;
(iv) Conformity with applicable requirements.
Auditor Actions
□ Identified the process(es) for amending the MMM.
□ Interviewed responsible manager(s).
□ Examined the MMM for currency.
□ Examined the content of selected amendments to the MMM.
□ Other Actions (Specify)
MNT 1.7.4–1.7.5 (Intentionally open)
MNT 1.7.6 The Operator shall ensure a copy of the current version of the MMM, or relevant
portions thereof, is promptly made available to:
(i) Applicable authorities;
(ii) Each organization or person that performs or certifies maintenance for the Operator;
(iii) All other organizations or persons to whom the MMM has been issued.
Auditor Actions
□ Identified/Assessed the process(es) for dissemination of the MMM.
□ Interviewed responsible manager(s).
□ Examined the distribution list for dissemination of the MMM.
□ Examined selected records of MMM and amendment distribution(s) to organizations/persons
that perform/certify maintenance.
□ Other Actions (Specify)
MNT 1.7.7 If the Operator issues relevant portions of the MMM as specified in MNT 1.7.6, the
Operator shall ensure policies and procedures contained therein are sufficiently comprehensive such
that all relevant guidance and information is available to any maintenance organization or person that
performs maintenance for the Operator under that portion of the manual.
Auditor Actions
□ Identified/Assessed the process(es) for dissemination of the MMM.
□ Interviewed responsible manager(s).
□ Examined the distribution list for dissemination of the MMM to organizations and/or persons.
□ Examined selected records of MMM distribution (portion only) to organizations/persons that
perform maintenance.
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Maintenance Records.
The operator is responsible for the maintenance records of the operator's aircraft irrespective
whether the records are retained at the operator's location, at a maintenance organization or any
other location.
An operator normally receives and retains a completed Certificate of Release to Service from the
maintenance organization. The system for storing such maintenance records is described in the
operator's MMM.
Methods of storing maintenance records acceptable to the Authority are in paper form, in a computer
database or a combination of both methods. Records stored on microfilm or optical disc form are also
acceptable.
For paper systems, use of robust material that can withstand normal handling and filing ensures
records can remain legible throughout the required retention period.
Computer systems normally have at least one back-up system, which is updated within 24 hours of
any maintenance performed. Additionally, each computer terminal normally contains program
safeguards to prevent any alteration of the database by unauthorized personnel.
Microfilming or optical storage of maintenance records may be carried out at any time, and be as
legible as the original record and remain so for the required retention period.
Information on times, dates, cycles referred to as “summary maintenance records” are the records
that give an overall picture on the state of maintenance of the aircraft and any life-limited aircraft
component. The current status of all life-limited aircraft components indicates the component life
limitation, total number of hours, accumulated cycles or calendar time and the number of
hours/cycles/time remaining before the required expiry time of the component is reached.
The current status of Airworthiness Directives (AD) identifies the applicable ADs including revision or
amendment numbers. Where an AD is generally applicable to the aircraft or component type but is
not applicable to the particular aircraft or component, this is identified. The AD status includes the
date on which the AD was accomplished. If the AD is controlled by flight hours or flight cycles, it
includes the aircraft or engine or component total flight hours or cycles, as appropriate. For repetitive
ADs, only the last application is recorded in the AD status. The status also specifies which part of a
multi-part AD has been accomplished and the method, where a choice is available in the AD.
Details of current modifications and repairs require substantiating data supporting compliance with
the airworthiness requirements. This can be in the form of a Supplemental Type Certificate, Service
Bulletin, Structural Repair Manual or similar approved document. If the airworthiness data for
modification and repair is produced by the maintenance organization in accordance with existing
national regulations, all detailed documentation necessary to define the change and its approval are
to be retained. Scheduled maintenance requirements following STC incorporation are required to be
clearly identified as well. The substantiating data may include:
• Compliance program;
• Master drawing or drawing list, production drawings and installation instructions;
• Engineering reports (static strength, fatigue, damage tolerance, fault analysis);
• Ground and flight test program and results;
• Mass and balance change data;
• Maintenance and repair manual supplements;
• Maintenance program changes and instructions for continuing airworthiness;
• Aircraft flight manual supplement.
Maintenance records are required to be stored safely from fire, flood, theft and alteration.
Computer back-up discs and cassettes are to be stored in a different location from those containing
the current working discs and tape cassettes and in a safe environment.
The operator is required to ensure, when a maintenance organization used by the operator
terminates its operation, the maintenance organization returns all retained maintenance records to
the operator.
Refer to guidance associated with ORG 2.2.1 located in ISM Section 1.
MNT 1.8.2 If the Operator utilizes an electronic system for the management of records, the
Operator shall ensure the system provides for a regularly scheduled generation of back-up files for
records associated with maintenance operations. (GM) ◄
Auditor Actions
□ Identified/Assessed management and control system for operational records in MNT
operations.
□ Interviewed responsible management representative(s).
□ Examined selected record(s) of back-up files for electronic records.
□ Other Actions (Specify)
Guidance
Refer to Guidance associated with ORG 2.2.2 located in ISM Section 1.
in their content depending on the complexity and type of maintenance function and/or work they are
supporting (e.g. from substantial maintenance providers as heavy maintenance or engine overhaul to
simple line maintenance tasks or minor component repair tasks). Accordingly, the agreements may
be of an elaborate contractual specification type (like suggested below in this guidance) or be just in
the form of a simple work order issued by the operator to the maintenance provider (within the
framework of a general outsourcing agreement between the two entities or to address a “one-off”
maintenance event).
In all cases, if maintenance is expected to be accomplished in accordance with specific industry
standards, an acceptable agreement identifies and specifies the standards by their exact name. The
wording “measurable standards” included in the provision implies that such standards required by the
function and/or work performed are always specified either explicitly in the agreement or indirectly in
a document that is referenced in the agreement (e.g. reference to data, authorized release
certificate/airworthiness approval tag, audit results). Other measures that might be considered
commercial in nature (e.g. post maintenance event reliability numerical indicators or post
maintenance event number of related reports from pilots/maintenance personnel or any business
type of key performance indicators) would be included in the agreement at the mutual option of the
operator and provider.
The following guidance provides information regarding any maintenance work related to aircraft and
aircraft components carried out for the operator by external organizations (i.e. contractors) under a
formal contract or agreement.
Note: The operator carries the ultimate responsibility for airworthiness and ensures before each flight
that all required maintenance has been properly carried out. This includes all maintenance carried
out by contractors.
The formal maintenance agreement document is not intended to provide detailed work instructions to
the contractor. Rather, such functions would typically be addressed through procedures established
by the operator and contractor.
A Maintenance Agreement typically includes, but is not necessarily limited to:
• An approval process for the contractor by the operator and where applicable the contractors
and/or the operator's Authority;
• A list of facilities where the maintenance is to be carried out, including a list of satellite
facilities that the contractor may use;
• A ‘Statement of Work’ (SOW) for the Maintenance Agreement that contains the detailed
technical requirements, including references to maintenance intervals, manuals,
Airworthiness Directives (ADs), Service Bulletins (SBs) and operator special requirements. A
clear, unambiguous and sufficiently detailed SOW and assignment of responsibilities are
required to ensure no misunderstanding arises between the operator, the contractor and the
operator's Authority that could result in a situation where the work, which has a bearing on
the airworthiness or the serviceability of operator's aircraft, is not properly performed;
• A requirement for the contractor to produce a suitable quality plan for the project;
• Use and control of parts and materials;
• Process for the approval of deviations from maintenance documents;
• A need for an internal evaluation system by the contractor;
• Access by the operator's quality assurance department staff for the purpose of evaluating
ongoing quality;
• A reporting structure that immediately notifies the operator of any significant defects;
• A system of completing, reviewing, retaining maintenance records;
• A system of calibration of tooling and equipment;
• A system of operator supplied product;
• A system of inspecting and testing, i.e., a quality control system;
• A system of handling unsatisfactory product;
• A system of handling, storage, packaging and delivery;
MNT 1.11.7 The Operator shall have monitoring processes to ensure each approved maintenance
organization that performs maintenance for the Operator:
(i) Complies with applicable regulations and safety and quality requirements;
(ii) Has procedures that are acceptable to the Authority granting the approval;
(iii) Performs all maintenance in accordance with requirements of the Operator. (GM) ◄
Auditor Actions
□ Identified/Assessed (focus: monitoring process ensures provider fulfils applicable
safety/security requirements).
□ Interviewed responsible manager(s) in MNT operations.
□ Examined selected records/reports resulting from monitoring of maintenance operations service
providers (focus: monitoring process ensures provider fulfils applicable safety/security
requirements).
□ Observed maintenance outsourcing management (focus: processes for monitoring all AMO
service providers)
□ Other Actions (Specify)
Guidance
Refer to Guidance associated with ORG 3.5.2 located in ISM Section 1.
MNT 1.11.8 The Operator should include auditing as a process for monitoring of each maintenance
organization that performs maintenance for the Operator. (GM) ◄
Auditor Actions
□ Identified/Assessed auditing processes used for monitoring external MNT service providers.
□ Interviewed responsible manager(s) in MNT operations.
□ Examined selected records/reports resulting from auditing of maintenance operations service
providers (focus: audit process ensures provider is fulfilling applicable safety/security
requirements).
□ Observed maintenance outsourcing management (focus: process for auditing AMO service
providers)
□ Other Actions (Specify)
Guidance
The operator establishes a plan acceptable to the State of Registry/Authority to specify when and
how often the operator's maintenance activities are monitored. Reports are produced at the
completion of each monitoring investigation that includes details of discrepancies and non-
compliance with procedures or requirements.
The feedback process addresses who is required to rectify discrepancies and non-compliance in
each particular case and the procedure to be followed, if rectification is not completed within
appropriate timescales. The manager responsible for the maintenance organization is also
responsible for monitoring and ensuring action on any outstanding items.
To ensure effective compliance with the operator's maintenance activities, the following elements
have proven to work well:
• Product sampling: the part inspection of a representative sample of the aircraft fleet;
• Defect sampling: the monitoring of defect rectification performance;
• Concession sampling: the monitoring of any concession allowing extensions to scheduled
maintenance;
• On-time maintenance sampling: the monitoring of maintenance intervals (flying hours,
calendar time, flight cycles) for aircraft and their components;
• Sampling reports of un-airworthy conditions and maintenance errors.
Refer to Guidance associated with ORG 3.5.3 located in ISM Section 1.
Guidance
Refer to the IRM for the definitions of Hazard (Aircraft Operations), Base Maintenance, Line
Maintenance, Risk Management and Safety Risk.
Hazard identification is an element of the Safety Risk Management component of the SMS
framework.
The operator typically applies its safety hazard identification program to the full scope of
maintenance operations associated with maintaining its aircraft, which includes line and base
maintenance.
Refer to Guidance associated with ORG 3.1.1 located in ISM Section 1.
MNT 1.12.2 The Operator shall have a safety risk assessment and mitigation program in
maintenance operations that specifies processes to ensure:
(i) Hazards are analyzed to determine corresponding safety risk(s) to aircraft operations;
(ii) Safety risks are assessed to determine the requirement for risk mitigation action(s);
(iii) When required, risk mitigation actions are developed and implemented in maintenance
operations. [SMS] (GM) ◄
Auditor Actions
□ Identified/Assessed safety risk assessment and mitigation program in MNT operations (focus:
hazards analyzed to identify/define risk; risk assessed to determine appropriate action; action
implemented/monitored to mitigate risk).
□ Identified/Assessed role of maintenance operations in cross-discipline safety risk
assessment/mitigation program (focus: participation with other operational disciplines).
□ Interviewed responsible manager(s) in MNT operations.
□ Interviewed person(s) that perform safety risk assessments in MNT operations.
□ Examined selected records/documents that illustrate risk assessment and resulting risk
mitigation action(s) in MNT operations.
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Safety Risk Assessment (SRA).
Risk assessment and mitigation is an element of the Safety Risk Management component of the
SMS framework.
The operator typically applies its safety risk assessment and mitigation program to the full scope of
maintenance operations associated with maintaining its aircraft, which includes line and base
maintenance.
Refer to Guidance associated with ORG 3.1.2 located in ISM Section 1.
Operational Reporting
MNT 1.12.3 The Operator shall have an operational safety reporting system in maintenance
operations that:
(i) Encourages and facilitates feedback from personnel to report safety hazards, expose safety
deficiencies and raise safety concerns;
(ii) Includes analysis and management action as necessary to address safety issues identified
through the reporting system. [SMS] (GM) ◄
Auditor Actions
□ Identified/Assessed operational safety reporting system in MNT operations (focus: system
urges/facilitates reporting of hazards/safety concerns; includes analysis/action to
validate/address reported hazards/safety concerns).
□ Interviewed responsible manager(s) in MNT operations.
Safety Assurance
MNT 1.12.5 The Operator shall have processes for setting performance measures as a means to
verify the safety performance of maintenance operations and to validate the effectiveness of risk
controls. [SMS] (GM) ◄
Auditor Actions
□ Identified/Assessed program for setting performance measures in MNT operations (focus:
program defines/requires development/application of performance measures; measures used to
track/monitor operational safety performance/validate safety risk controls).
□ Interviewed responsible manager(s) in MNT operations
□ Examined selected performance measures currently being tracked/monitored.
□ Examined selected records/documents that identify tracking of maintenance operations
performance measures (focus: tracking used to assess/monitor operational safety performance,
assess/validate risk control effectiveness).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Safety Assurance.
Setting performance measures that are consistent with safety objectives is an element of the Safety
Assurance component of the SMS framework.
Refer to Guidance associated with ORG 3.2.1A located in ISM Section 1.
SMS Training
MNT 1.12.6 The Operator shall have a program that ensures aircraft engineering and maintenance
personnel are trained and competent to perform SMS duties. The scope of such training shall be
appropriate to each individual's involvement in the SMS. [SMS] (GM) ◄
Note: SMS training is applicable to management and non-management personnel that perform
aircraft engineering and maintenance functions for the Operator.
Auditor Actions
□ Identified/Assessed program for ensuring MNT personnel are trained and competent to perform
SMS duties.
□ Interviewed responsible manager(s).
□ Examined selected initial and recurrent MNT training curricula/syllabi for management/non-
management personnel (focus: training in individually relevant SMS duties/responsibilities).
□ Examined selected MNT management/non-management personnel training records (focus:
completion of SMS training).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Operational Function (Aircraft Operations).
SMS training is an element of the Safety Promotion component of the SMS framework.
Refer to Guidance associated with ORG 1.6.5 located in ISM Section 1.
2 Maintenance Control
MNT 2.3.2 The Operator shall have a process to ensure that no used part is installed on an
aeronautical product unless such part meets the standards of airworthiness applicable to the
installation of used parts and any of the following:
(i) An airworthy part that has been removed from an aircraft for immediate installation on
another aircraft, or
(ii) An airworthy part that has undergone maintenance for which a maintenance release has
been signed by an appropriately rated Approved Maintenance Organization (AMO), or
(iii) An airworthy part that has undergone an approved repair or alteration that restored the
certificated level of airworthiness to a used part. (GM)
Auditor Actions
□ Identified/Assessed the process for managing and controlling used parts and parts installation.
□ Interviewed responsible manager(s).
□ Examined selected parts installed on aircraft for certificates.
□ Observed aircraft part/component installation/replacement (if applicable) (focus: used
part/component being installed meets applicable standards of airworthiness).
□ Observed aircraft parts/components management/handling (focus: control process for ensuring
used parts meet applicable standards of airworthiness).
□ Other Actions (Specify)
Guidance
The operator is responsible for providing an external AMO with approved documentation that
contains information about parts allowed to be installed on its aircraft. Such documentation enables
the external AMO to validate the airworthy condition of the part and its certification for installation on
the aeronautical product being maintained. The “approved documentation” category typically
includes as necessary, without being limited to, any of the following: MMM, IPC (including
Supplements), AD, SB, Work Order, Repair Order, Form 8130-3/EASA Form 1/or equivalent.
MNT 2.3.3 The Operator shall have a process to ensure that no used life-limited part is installed on
an aeronautical product unless such part meets the standards of airworthiness applicable to the
installation of life-limited parts and:
(i) The technical history of the part is available to demonstrate the time in service, as
authorized for that part in the type certificate governing the installation, has not been
exceeded;
(ii) The technical history referred to in sub-paragraph i) is incorporated into the technical record
for the aeronautical product on which the part is installed. (GM)
Auditor Actions
□ Identified/Assessed the process for managing and controlling used life-limited parts and parts
installation.
□ Interviewed responsible manager(s).
□ Interviewed personnel that execute procedures for tracking life-limited parts.
□ Traced the technical history of selected life-limited parts.
□ Observed aircraft part/component installation/replacement (if applicable) (focus: used life-limited
part/component being installed meets applicable standards of airworthiness).
□ Observed aircraft parts/components management/handling (focus: control process for ensuring
used life-limited parts meet applicable standards of airworthiness).
□ Other Actions (Specify)
Guidance
The operator is responsible for providing an external AMO with approved documentation that
contains information about parts allowed to be installed on its aircraft.
In general, it is best for an operator to have a fully traceable history for all life-limited parts. Not all
parts have a fixed life. The life of some parts might be variable depending on the way the part has
been used in the past. For example, load-bearing parts (e.g. landing gear components) that can be
installed on different aircraft types (e.g. A319, A320, A321) will have a shorter life if installed on the
heavier aircraft (as opposed to the same part installed on a lighter aircraft). Therefore, a complete
history of these types of components is critical in knowing exactly when the life of the part will expire.
For parts that have a fixed life (e.g. batteries, slides), traceability to birth is not a requirement.
However, in such cases, it is very important that the operator has documentation that shows clearly
that the used part has not exceeded its airworthiness life limit.
Guidance
In complying with the requirements specified in Table 4.5, an operator would normally be expected to
develop, whenever applicable, the following:
• The list of EDTO Significant Systems/Sub-systems (i.e. the list including, for a given aircraft,
any system/sub-system whose failure or degradation could adversely affect the safety of an
EDTO flight or whose continued functioning is important to the safe flight and landing of an
aircraft during an EDTO diversion).
• The list of maintenance tasks with EDTO significance (i.e. the list of maintenance tasks
affecting any EDTO Significant System/Sub-system).
• The reliability program supplemented, as applicable, to take into account the EDTO
requirements and specific analysis.
• The Engine Condition Monitoring Program (ECMP) including the Oil Consumption Monitoring
Program.
• The APU in-flight Start Program.
• The EDTO aircraft Pre-Departure Service Check (PDSC).
• The list of EDTO Qualified Maintenance Personnel as well as the training program and
qualification procedures of such personnel.
• The procedure to integrate in the MMM all applicable Configuration, Maintenance and
Procedures (CMP) provisions issued by the manufacturer of the aeroplane.
Guidance
The intent of this provision is to ensure a procedure for the insertion of databases for use in aircraft
navigation systems prior to the first flight on the effective date for the new database.
Auditor Actions
□ Identified/Assessed the procedure(s) for transmitting fault/malfunction information to the Type
Certificate Holder.
□ Interviewed responsible manager(s).
□ Examined selected fault/malfunction information reports to the Type Certificate Holder.
□ Other Actions (Specify)
3 Technical Records
Guidance
Item i) is applicable to aircraft that an operator has permanently taken out of service for any reason
(e.g. scrapping).
MNT 3.1.3 The Operator shall have processes to ensure, when an aircraft becomes involved in an
accident or incident, the related flight recorder records and, to the extent possible, the associated
flight recorders are preserved and retained in safe custody pending disposition in accordance with
the appropriate investigation.
Auditor Actions
□ Identified the process(es) for custody of FDR/CVR and retention of associated records after an
aircraft accident.
□ Interviewed responsible manager(s).
□ Interviewed personnel that execute process(es) in the event of an aircraft accident.
□ Other Actions (Specify)
MNT 3.1.4 The Operator shall have processes to ensure applicable aircraft maintenance records
for aircraft currently listed on the AOC:
(i) In the event of a temporary change of operator, are made available to the new operator;
(ii) In the event of a permanent change of operator, transferred to the new operator.
Auditor Actions
□ Identified/Assessed the process(es) for the provision of maintenance records to a new
operator.
□ Interviewed responsible manager(s).
□ Interviewed personnel that execute process(es) for providing maintenance records to a new
operator.
□ Other Actions (Specify)
4 Maintenance Organizations
4.1 Approval
MNT 4.1.1 The Operator shall have a process to ensure an aircraft is not operated unless it is
maintained and released to service by an Approved Maintenance Organization (AMO) that:
(i) Is acceptable to the Authority:
(ii) Has established procedures acceptable to the Authority to ensure maintenance practices
are in compliance with all relevant requirements;
(iii) Maintains the validity of its approval through compliance with the requirements for an
approved maintenance organization acceptable to the Authority. (GM)
Auditor Actions
□ Identified/Assessed the process(es) for the selection of AMOs.
□ Interviewed responsible manager(s).
□ Examined selected AMO selection records.
□ Observed maintenance outsourcing management (focus: requirement that aircraft maintenance
is performed only by an AMO)
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Approved Maintenance Organization (AMO).
MNT 4.1.2 (Intentionally open)
MNT 4.1.3 The Operator shall have a process to ensure each maintenance organization that
performs maintenance for the Operator has an approval document that contains, as a minimum:
(i) The name and location of the AMO;
(ii) The date of issue and period of validity of the approval;
(iii) The scope of the approval. (GM)
Auditor Actions
□ Identified/Assessed the requirement criteria for regulatory approval in the AMO selection
process.
□ Interviewed responsible manager(s).
□ Examined selected AMO selection records.
□ Observed maintenance outsourcing management (focus: process for verifying mandatory
information on AMO approval documents)
□ Other Actions (Specify)
Guidance
The specification in item iii) of this provision is satisfied by the operator ensuring that the AMO
approval document contains the type and level of work required by the operator.
A repair station or Approved Maintenance Organization certificate is usually delivered with ratings in
one or more of the following categories or their equivalents:
• Aircraft;
• Avionics;
• Engine;
• Propeller;
• Structure and Corrosion Protection Control Program;
• Component;
• Welding;
• NDT.
MNT 4.1.4 (Intentionally open)
MNT 4.1.5 If the Operator has maintenance performed outside the State of the Operator by a
maintenance organization that does not hold an approval document issued by the Authority, the
Operator shall have a process to ensure such maintenance organization has been recognized by the
Authority. (GM)
Auditor Actions
□ Identified/Assessed the requirement criteria for regulatory approval in the AMO selection
process.
□ Interviewed responsible manager(s).
□ Examined selected AMO selection records.
□ Observed maintenance outsourcing management (focus: process for verifying State recognition
of foreign AMOs (if applicable)
□ Other Actions (Specify)
Guidance
It is possible for an operator to enter into an arrangement for primary maintenance with an
organization that is not an approved/accepted Maintenance Organization within the State of Registry
when the arrangement is in the interest of the operator by simplifying the management of its
maintenance. In such a situation, the maintenance organization is normally approved under the laws
of a State that has an agreement with the State of Registry of the operator, and the operator applies
its own control processes that ensure the existence of and compliance with the provisions MNT
sub-section 4.
4.2 Management
MNT 4.2.1 The Operator shall have a process to ensure each maintenance organization that
performs maintenance for the Operator has a manager who, if applicable, is acceptable to the
relevant Authority and has responsibility for the management and supervision of the maintenance
organization.
Auditor Actions
□ Identified the requirement criteria for management in the AMO selection process.
□ Interviewed responsible manager(s).
□ Examined selected AMO selection records.
□ Observed maintenance outsourcing management (focus: process for verifying
responsibilities/regulatory acceptance of AMO managers)
□ Other Actions (Specify)
MNT 4.2.2 The Operator shall have a process to ensure each maintenance organization that
performs maintenance for the Operator has appropriate post holders with responsibilities for ensuring
the maintenance organization is in compliance with the requirements for an approved maintenance
organization as accepted by the Authority. (GM)
Auditor Actions
□ Identified/Assessed the requirement criteria for the qualifications of personnel in the AMO
selection process.
□ Interviewed responsible manager(s).
□ Examined selected AMO selection records.
□ Observed maintenance outsourcing management (focus: process for verifying
qualifications/regulatory acceptance of AMO post holder personnel)
□ Other Actions (Specify)
Guidance
The person or persons appointed represent the maintenance management structure of the
organization and responsible for all functions specified in the maintenance organization. The
specified functions may be subdivided under individual managers within smaller maintenance
organizations, ensuring that responsibility for all functions is allocated.
Dependent upon the extent of approval, maintenance organizations typically have, as a minimum,
the following personnel: a base maintenance manager, a line maintenance manager, a workshop
manager and a quality manager, all of whom report to the accountable executive, if applicable. In
small maintenance organizations, subject to approval by the State of Registry/Authority, the
accountable executive may also carry responsibility for other managerial positions. Deputies are
normally appointed for all managerial positions, and procedures make clear who deputizes for any
particular manager in the case of lengthy absence of said manager(s). The length of absence to
justify deputizing is the period beyond which the organization or department cannot function properly
due to such absence.
The accountable executive is responsible for ensuring that all necessary resources are available to
accomplish maintenance to support the organization's maintenance organization approval.
Regardless of the size of the maintenance organization, managers appointed for the combination of
the identified functions would indirectly report to the accountable executive through the base
maintenance manager, line maintenance manager, workshop manager or quality manager, as
appropriate.
Certifying personnel may report to any of the managers specified, depending upon which type of
control the approved maintenance organization uses: licensed engineers, independent inspection or
dual function supervisors. The monitoring of quality compliance remains an independent function.
MNT 4.2.3 The Operator shall have a process to ensure each maintenance organization that
performs maintenance for the Operator has the necessary personnel to plan, perform, supervise,
inspect and release the maintenance work to be performed. (GM)
Auditor Actions
□ Identified/Assessed the requirement criteria for human resources in the AMO selection
process.
□ Interviewed responsible manager(s).
□ Examined selected AMO selection records.
□ Observed maintenance outsourcing management (focus: process for verifying adequacy of
AMO maintenance human resources).
□ Other Actions (Specify)
Guidance
The “necessary personnel” requirement addresses both the number and the (certificated)
qualification/competence of the personnel. Personnel are typically employed or contracted by an
AMO as acceptable to the Authority and in a proportion that ensures organizational stability. The
qualification/competence of the personnel and the number of personnel are normally commensurate
with the scope of approval of the AMO by the Authority. In some cases the process put in place by an
operator could require the AMO to support its “necessary personnel” status with an appropriately
detailed and updated maintenance man-hour plan.
required maintenance has been properly carried out before the issue of the certificate of
release to service;
• A percentage of random audits carried out on a sample basis when maintenance is being
carried out; random audits include audits done during the night for those organizations that
work at night.
Another essential element of the quality system is the quality feedback system. The principal function
of the quality feedback system is to ensure all findings resulting from the independent quality audits
of the organization are properly investigated and corrected in a timely manner:
• Independent quality audit reports are sent to the relevant department(s) for rectification
action proposing target rectification dates;
• Rectification dates are discussed with such department(s) before the quality department or
nominated quality auditor confirms dates in the report;
• The relevant department(s) rectifies findings within agreed rectification dates and informs the
quality department or nominated quality auditor of the completion of such rectifications.
The accountable executive is kept informed of any safety issues and the extent of compliance with
authority requirements. The accountable executive also holds regular meetings with personnel to
check progress on rectification. In large organizations such meetings may be delegated on a day-to-
day basis to the quality manager, subject to the accountable executive meeting at least twice per
year with the senior personnel involved to review the overall performance and receiving at least a half
yearly summary report on findings of non-compliance.
All records pertaining to the independent quality audit and the quality feedback system are retained
for at least two evaluation cycles after the date of closure of the finding to which they refer, or for such
period as to support changes to the audit time periods, whichever is the longer.
Note: The quality feedback system may not be contracted to outside persons.
It is not intended that this QA Program be based on a system of end product inspection, but rather
upon periodic verifications of all aspects of the systems and practices used for the control of
maintenance to ensure compliance with regulations and with the operator's approved procedures.
The aim of the program is to provide an unbiased picture of the AMO's performance to verify that
activities comply with the MPM and confirm that the systems and procedures described in the MPM
remain effective and are achieving the AMO's requirements.
MNT 4.3.2–4.3.4 (Intentionally open)
MNT 4.3.5 The Operator shall have a process to ensure each maintenance organization that
performs maintenance for the Operator has a process for periodic review of the quality assurance
program by the Quality Manager or the person assigned managerial responsibility for the program for
the purpose of ensuring compliance with current requirements of the Maintenance Program and the
MMM.
Auditor Actions
□ Identified/Assessed the requirement criteria for a QA program in the AMO selection and
oversight process(es).
□ Interviewed responsible manager(s).
□ Examined selected AMO oversight/monitoring reports.
□ Observed maintenance outsourcing management (focus: process for verifying AMO conducts
periodic internal review of quality assurance programs).
□ Other Actions (Specify)
MNT 4.3.6 (Intentionally open)
MNT 4.3.7 The Operator shall have a process to ensure each maintenance organization that
performs maintenance for the Operator has a process to immediately report to the Operator any
defects, un-airworthy conditions, failures or malfunctions specified in MNT 2.12.2.
Auditor Actions
□ Identified/Assessed the requirement criteria for a defect reporting in the AMO selection
process.
□ Interviewed responsible manager(s).
□ Examined selected AMO oversight/monitoring reports.
□ Observed maintenance outsourcing management (focus: process to verify AMO provides
mandatory reporting of defects/conditions/failures/malfunctions).
□ Other Actions (Specify)
4.4 Personnel
MNT 4.4.1 The Operator shall have a process to ensure each maintenance organization that
performs maintenance for the Operator utilizes maintenance personnel
(i) That are appropriately licensed and/or authorized to sign the maintenance release;
(ii) Whose competence has been established in accordance with a procedure and to a level
acceptable to the authority granting approval for the maintenance organization. (GM)
Auditor Actions
□ Identified/Assessed the requirement criteria for qualifications of personnel in the AMO selection
process.
□ Interviewed responsible manager(s).
□ Examined selected AMO selection records.
□ Examined selected AMO oversight/monitoring reports.
□ Observed maintenance outsourcing management (focus: process for verifying AMO personnel
are licensed/authorized to sign maintenance release).
□ Observed aircraft part/component installation/replacement (focus: personnel signing
maintenance release are appropriately licensed/authorized).
□ Other Actions (Specify)
Guidance
Licensing typically ensures maintenance personnel have met the basic requirements of an applicable
authority in terms of age, knowledge, experience and, if required, medical fitness and skill, and have
demonstrated the required knowledge and skill in a manner specified by the authority.
Planners, mechanics, specialized services personnel, supervisors and certifying personnel are
typically assessed for competence by an on-the-job evaluation and/or examination relevant to their
particular job or role within the organization before unsupervised work is permitted.
To assist in the assessment of competence, job descriptions are recommended for each job role in
the organization. Basically, the assessment establishes that:
• Planners are able to interpret maintenance requirements into maintenance tasks and have
an appreciation that they have no authority to deviate from the maintenance data;
• Mechanics are able to carry out maintenance tasks to any standard specified in the
maintenance data and notify supervisors of mistakes requiring rectification to meet required
maintenance standards;
• Specialized services personnel are able to carry out specialized maintenance tasks to the
standard specified in the maintenance data and will both inform and await instructions from
their supervisor in any case where it is impossible to complete the specialized maintenance
in accordance with the maintenance data;
• Supervisors are able to ensure that all required maintenance tasks are carried out and where
not completed or where it is evident that a particular maintenance task cannot be carried out
in accordance with the maintenance data, it is be reported to the responsible person for
appropriate action. In addition, for those supervisors who also carry out maintenance tasks,
that they understand such tasks are not to be undertaken when incompatible with their
management responsibilities;
• Certifying personnel are able to determine when the aircraft is or is not ready to be released
to service.
Knowledge of organizational procedures relevant to each individual's particular role in the
organization is important, particularly in the case of planners, specialized services personnel,
supervisors and certifying personnel.
MNT 4.4.2 The Operator shall have a process to ensure each maintenance organization that
performs maintenance for the Operator has a means for providing a positive identification of
maintenance personnel that are approved to perform and certify maintenance.
Auditor Actions
□ Identified/Assessed requirement for identification of personnel approved to perform/certify
maintenance in the AMO selection process.
□ Interviewed responsible manager(s).
□ Examined AMO selection records (focus: process for identifying personnel approved to
perform/certify maintenance).
□ Examined selected AMO oversight/monitoring reports (focus: identification of personnel
approved to perform/certify maintenance).
□ Observed maintenance outsourcing management (focus: process for verifying AMO has positive
identification of maintenance personnel that are approved to perform/certify maintenance).
□ Observed aircraft part/component installation/replacement (focus: personnel are approved to
perform/certify maintenance).
□ Other Actions (Specify)
Guidance
A database, signature roster or other equivalent mechanisms are typically used to identify such
personnel.
Guidance
Refer to the IRM for the definition of Human Performance.
Item ii) refers to the knowledge and skills related to human performance in all maintenance activities
covered under an operator's maintenance program, including those activities performed by an
external AMO. This does not apply if the maintenance provider is under direct coordination with the
operator's MCC.
MNT 4.5.2–4.5.3 (Intentionally open)
MNT 4.5.4 The Operator shall have a process to ensure each maintenance organization that
performs maintenance for the Operator has a training program that provides for continuation training
on an interval not to exceed 36 months, which may be reduced to a lesser interval based on findings
generated by the QA Program. (GM)
Auditor Actions
□ Identified/Assessed the requirement criteria for continuation training of personnel in the AMO
selection process.
□ Interviewed responsible manager(s).
□ Examined selected AMO selection records.
□ Examined selected AMO oversight/monitoring reports.
□ Observed maintenance outsourcing management (focus: process for verifying AMO has
program for continuation training at maximum 36 month interval).
□ Other Actions (Specify)
Guidance
Continuation training is a two-way process to ensure that relevant maintenance personnel remain
current in terms of procedures, human factors and technical knowledge, and that the approved
maintenance organization receives feedback on the adequacy of its procedures and maintenance
instructions. Due to the interactive nature of this training, consideration would be given to the
possibility that such training has the involvement of the quality department to ensure feedback is
actioned. Alternatively, there is a procedure to ensure that feedback is formally passed from the
training department to the quality department to initiate action.
Continuation training would cover changes in relevant State of Registry/Authority requirements,
changes in organization procedures and the modification standard of the products being maintained
plus human factor issues identified from any internal or external analysis of incidents. It would also
address instances where personnel failed to follow procedures and the reasons why particular
procedures are not always followed. In many cases, the continuation training reinforces the need to
follow procedures and ensure that incomplete or incorrect procedures are identified so they can be
corrected. This does not preclude the possible need to carry out a quality audit of such procedures.
The program for continuation training lists all relevant maintenance personnel and when training will
take place, the elements of such training and an indication it was carried out reasonably on time as
planned. Such information is subsequently transferred to the certifying personnel record.
The referenced procedure is specified in the MPM.
Continuation training requirements are intended to apply to personnel performing and certifying
maintenance, as well as to planners, inspectors of incoming goods and other maintenance personnel
that have safety-critical responsibilities.
Refer to the Guidance associated with MNT 1.3.2 for information that explains and addresses human
factors principles.
MNT 4.5.5 The Operator shall have a process to ensure each maintenance organization that
performs maintenance for the Operator has a training and qualification program for auditors used in
the QA Program.
Auditor Actions
□ Identified/Assessed the requirement criteria for the training of QA auditors in the AMO selection
process.
□ Interviewed responsible manager(s).
□ Examined selected AMO selection records.
□ Examined selected AMO oversight/monitoring reports.
□ Observed maintenance outsourcing management (focus: process for verifying AMO has
training/qualification program for quality assurance auditors).
□ Other Actions (Specify)
MNT 4.5.6 The Operator shall have a process to ensure each maintenance organization that
performs maintenance for the Operator has a training program that provides for initial and
continuation training for receiving inspectors.
Auditor Actions
□ Identified/Assessed the requirement criteria for the training of receiving inspectors in the AMO
selection process.
□ Interviewed responsible manager(s).
□ Examined selected AMO selection records.
□ Examined selected AMO oversight/monitoring reports.
□ Observed maintenance outsourcing management (focus: process for verifying AMO has
initial/recurrent training program for receiving inspectors).
□ Other Actions (Specify)
MNT 4.5.7 If the Operator utilizes a maintenance organization that has maintenance personnel taxi
the Operator's aircraft on the movement area of an airport, the Operator shall have a process to
ensure such maintenance personnel are authorized, competent and qualified to conduct aircraft taxi
operations.
Auditor Actions
□ Identified/Assessed the requirement criteria for the qualifications of personnel that taxi aircraft
in the AMO selection process.
□ Interviewed responsible manager(s).
□ Examined selected AMO selection records.
□ Examined selected AMO oversight/monitoring reports.
□ Observed maintenance outsourcing management (if applicable) (focus: process for verifying
training/qualification of AMO personnel authorized to taxi aircraft).
□ Other Actions (Specify)
Auditor Actions
□ Observed/Assessed facilities/equipment/storage/work environment.
□ Observed maintenance outsourcing management (focus: process for verifying adequate AMO
facilities/work environment to perform maintenance).
□ Interviewed MNT operations manager and/or designated management representative(s).
□ Other Actions (Specify)
Guidance
For base maintenance of aircraft, aircraft hangars or equivalent facilities are available, large enough
to accommodate aircraft on planned base maintenance. If the maintenance organization does not
own the hangar, it may be necessary to establish proof of tenancy. In addition, sufficient hangar
space to carry out planned base maintenance will need to be demonstrated by the preparation of a
projected aircraft hangar visit plan, relative to the maintenance program. The aircraft hangar visit plan
is updated on a regular basis. For aircraft component maintenance, aircraft component workshops
are large enough to accommodate the components on planned maintenance.
Aircraft hangar and aircraft component workshop structures would need to be to a standard that
prevents the ingress of rain, hail, ice, snow, wind and dust, and aircraft hangar and aircraft
component workshop floors are sealed to minimize dust generation. Basically, the aircraft hangar
and aircraft component workshop provides protection from the normal prevailing local weather
elements that are expected throughout any 12-month period.
For line maintenance of aircraft, hangars are not essential but access to hangar accommodation is
necessary during inclement weather for minor scheduled work and lengthy defect rectification.
Office accommodation allows incumbents, whether they are management, planning, technical
records, quality or certifying personnel, to carry out their designated tasks in a manner that
contributes to good aircraft maintenance standards. In addition, aircraft maintenance personnel are
provided with an area where they may study maintenance instructions and complete maintenance
records in a proper manner.
Note: It is acceptable to combine any or all of the above requirements into one office subject to the
personnel having sufficient room to carry out assigned tasks.
Hangars used to house aircraft together with office accommodation would be such that the working
environment permits personnel to carry out work tasks in an effective manner.
Temperatures are such that personnel can carry out required tasks without undue discomfort.
Dust and any other airborne contamination are kept to a minimum and not be permitted to reach a
level in the work task area where visible aircraft/component surface contamination is evident.
An adequate level of lighting ensures each inspection and maintenance task can be carried out.
Noise levels are not permitted to rise to the point of distracting personnel from carrying out inspection
tasks. Where it is impractical to control the noise source, such personnel would be provided with the
necessary personal equipment to stop excessive noise causing distraction during inspection tasks.
Where a particular maintenance task requires the application of specific environmental conditions
different to the foregoing, then such conditions would be observed. Such specific conditions are
identified in the approved maintenance instructions.
The working environment for line maintenance is such that the particular maintenance or inspection
task can be carried out without undue distraction. If the working environment deteriorates to an
unacceptable level due to temperature, moisture, hail, ice, snow, wind, light, dust or other airborne
contamination, then the particular maintenance or inspection tasks is suspended until satisfactory
conditions are re-established.
For both base and line maintenance where dust or other airborne contamination results in visible
surface contamination, all susceptible systems are sealed until acceptable conditions are re-
established.
MNT 4.6.2 The Operator shall have a process to ensure each maintenance organization that
performs maintenance for the Operator has the necessary technical data, equipment, tools and
material to perform the work for which the maintenance organization has been approved, to include:
(i) Equipment and tools necessary to comply with the work specified in the agreement between
the Operator and the maintenance organization;
(ii) Sufficient supplies and spare parts to ensure timely rectification of defects with regard to the
Minimum Equipment List (MEL) provisions as specified in the agreement between the
Operator and the maintenance organization. (GM)
Auditor Actions
□ Identified/Assessed the requirement criteria for technical data, equipment, tools and material in
the AMO selection process.
□ Interviewed responsible manager(s).
□ Examined selected AMO selection records.
□ Examined selected AMO oversight/monitoring reports.
□ Observed maintenance outsourcing management (focus: process for verifying adequate AMO
data/equipment/supplies/parts to perform maintenance).
□ Observed aircraft part/component installation/replacement (focus: availability/use of necessary
technical data/equipment/tools/material for maintenance activity being performed).
□ Observed aircraft parts/components management/handling (focus: availability/use of necessary
technical data/equipment/tools/material for management/handling of aircraft parts/components).
□ Other Actions (Specify)
Guidance
Tools and equipment, as specified in the Approved Data, can be made available when needed. Tools
and equipment, which require to be controlled in terms of servicing or calibration to measure
specified dimensions and torque figures, are to be clearly identified and listed in a control register,
including any personal tools and equipment that the organization agrees can be used. Where the
manufacturer specifies a particular tool or equipment, then that tool or equipment is used, unless the
AMO has an approved procedure to determine the equivalency of alternative tooling/equipment and
the procedure documented in the MPM.
The availability of equipment and tools indicates permanent availability except in the case of any tool
or equipment that is so rarely needed that its permanent availability is not necessary.
A maintenance organization approved for base maintenance has sufficient aircraft access equipment
and inspection platforms/docking such that the aircraft may be properly inspected.
The supplies necessary to perform maintenance work refer to readily available raw material and
aircraft components, in accordance with the manufacturer's recommendations, unless the
organization has an established spares provisioning procedure.
MNT 4.6.3 The Operator shall have a process to ensure each maintenance organization that
performs maintenance for the Operator has facilities suitable for the storage of parts, equipment,
tools and material under conditions that provide security and prevent deterioration of and damage to
stored items. Such processes shall ensure:
(i) Clean work areas, including management offices;
(ii) Parts and material properly identified and stored;
(iii) Oxygen and other high-pressure bottles properly identified and stored;
(iv) Flammable, toxic or volatile materials properly identified and stored;
(v) Equipment identified and protected. (GM)
Auditor Actions
□ Identified/Assessed the requirement criteria for facilities in the AMO selection process.
□ Interviewed responsible manager(s).
Guidance
Consideration is typically given to the scope of work of the maintenance organization in determining
the applicability of ESD requirements.
MNT 4.7.4 The Operator shall have a process to ensure each maintenance organization that
performs maintenance for the Operator has a method of storage that assures sensitive parts and
equipment, such as, but not limited to, oxygen system components (oxygen generators and bottles),
O-rings and electrostatic sensitive devices are properly packaged, identified and stored to protect
them from damage and contamination. (GM)
Auditor Actions
□ Identified/Assessed the requirement criteria for the storage of sensitive parts in the AMO
selection process.
□ Interviewed responsible manager(s).
□ Examined selected AMO selection records.
□ Examined selected AMO oversight/monitoring reports.
□ Observed maintenance outsourcing management (focus: process for verifying acceptable AMO
methods for storage of sensitive parts/equipment).
□ Observed aircraft parts/components management/handling (focus: methods for ensuring proper
identification/storage of sensitive aircraft parts/components).
□ Other Actions (Specify)
Guidance
The intent of this provision is to ensure maintenance organizations comply with storage
recommendations from the manufacturers, with particular emphasis on recommendations with
respect to temperature and humidity.
Consideration is to be given to the scope of work of the AMO in determining applicability of specific
handling and/or storage requirements.
MNT 4.7.5 The Operator shall have a process to ensure each maintenance organization that
performs maintenance for the Operator has a process that assures aircraft components and parts are
shipped in suitable containers that provide protection from damage and, when specified by the OEM,
ATA-300 or equivalent containers shall be used.
Auditor Actions
□ Identified the requirement criteria for the shipping of aircraft components and parts in the AMO
selection process.
□ Interviewed responsible manager(s).
□ Examined selected AMO selection records.
□ Examined selected AMO oversight/monitoring reports.
□ Observed maintenance outsourcing management (focus: process for verifying acceptable AMO
methods/containers for shipping aircraft components/parts).
□ Observed aircraft parts/components management/handling (focus: process for ensuring aircraft
parts/components are shipped in suitable containers).
□ Other Actions (Specify)
• A description of the maintenance procedures and the procedures for completing and signing
a maintenance release when maintenance is based on a system other than that of an
approved maintenance organization;
• A description of the procedures for monitoring, assessing and reporting maintenance and
operational experience;
• A description of procedures for assessing continuing airworthiness information and
implementing any resulting actions;
• A description of the procedures for implementing action resulting from mandatory continuing
airworthiness information;
• A description of procedures for ensuring that unserviceable items affecting airworthiness are
recorded and rectified;
• A description of the procedures for advising the State of Registry/Authority/operator of
significant in-service occurrences;
• A table of contents;
• A description of the MPM amendment control procedure;
• A means of identifying each page of the MPM. This can be in the form of a list of effective
pages, with each page numbered and either dated or marked with a revision number;
• A description of the system used to distribute the MPM, including a distribution list; for non-
scheduled work, temporary copies of the relevant portions of the MPM or any incorporated
reference;
• Where the organization uses standards for the performance of elementary work or servicing
different from those recommended by the manufacturer, the identification of those standards;
• Procedures to ensure regulatory information and technical data appropriate to the work
performed are used in respect of elementary work and servicing;
• Details of the methods used to record the maintenance, elementary work or servicing
performed, including the method of recording of defects in the technical record required by
these standards;
• A detailed description of the procedures used to ensure that any maintenance tasks required
by the maintenance schedule, airworthiness directives or any task required for the
rectification of a defect are completed within the required time constraints;
• A description of the evaluation program required by these standards;
• A description of the defect rectification and control procedures, including details of:
– The methods used to detect and report recurring defects;
– The procedures for scheduling the rectification of defects whose repair has been
deferred.
• The procedures used to report service difficulties in accordance with these standards;
• A description of the technical dispatch procedures, including procedures for ferry-flight
authorizations, EDTO (equivalent terms: ETOPS, EROPS, LROPS), all-weather operation or
any other special operation;
• Procedures to ensure that only parts and materials that meet the requirements of the State of
Registry/Authority/operator are used in the performance of elementary work or servicing,
including details of any spare part pool arrangements that have been entered into;
• A description of the methods used to ensure that the personnel authorized to perform
elementary work or servicing are trained as required by the Authority and qualified in
accordance with these requirements, as applicable;
• A description of personnel records to be retained;
• Details of the procedures applicable to maintenance arrangements and a list of all such
arrangements, including the procedure used to communicate to an approved maintenance
organization the maintenance requirements for planned and unforeseen maintenance
activities, as well as those mandated by airworthiness directives;
• Procedure for revising and maintaining the MPM up to date and current;
• Approval of the Authority through approval of the list of effective pages or, in the case of
manuals containing a small number of pages, approval can be identified on each page;
• Procedures used for the storage and control of petroleum, oil and other lubricants, as
required by national regulations.
MNT 4.9.2 The Operator shall have a process to ensure each maintenance organization that
performs maintenance for the Operator has a process to amend the MPM as necessary to keep the
information contained therein up to date.
Auditor Actions
□ Identified/Assessed the requirement criteria for an MPM amendment process in the AMO
selection process.
□ Interviewed responsible manager(s).
□ Examined selected AMO selection records.
□ Examined MPM for currency (if available).
□ Observed maintenance outsourcing management (focus: process for verifying acceptable AMO
MPM amendment process).
□ Other Actions (Specify)
MNT 4.9.3 The Operator shall have a process to ensure each maintenance organization that
performs maintenance for the Operator has a process to furnish copies of all amendments to the
MPM promptly to all organizations or persons to whom the manual has been issued.
Auditor Actions
□ Identified/Assessed the requirement criteria for an MPM distribution process in the AMO
selection process.
□ Interviewed responsible manager(s).
□ Examined selected AMO selection records.
□ Examined selected AMO oversight/monitoring reports.
□ Observed maintenance outsourcing management (focus: process for verifying acceptable AMO
MPM distribution/dissemination processes).
□ Other Actions (Specify)
Auditor Actions
□ Identified the requirement criteria for the production of the maintenance release in the AMO
selection process.
□ Interviewed responsible manager(s).
□ Examined selected AMO selection records.
□ Examined selected AMO oversight/monitoring reports.
□ Observed maintenance outsourcing management (focus: process for verifying AMO production
of completed/signed maintenance release that certifies maintenance performed in accordance
with MPM).
□ Observed aircraft part/component installation/replacement (focus: production of complete
maintenance release for specific maintenance activity being performed).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Maintenance Organization Exposition.
An operator has the option of defining when the revision status of approved data (that was used
during the performance of maintenance) must be included in the maintenance release. The process
that defines such requirement is typically documented in the operator's MMM.
A requirement for the documented revision status to be part of the maintenance release might
depend on the particular approved data that is referenced. For example, if the Aircraft Maintenance
Manual that was used for maintenance is distributed online, there would be an online record of the
revision that was available at the time of maintenance, which might obviate the need for that
information to be documented in the maintenance release. Conversely, the revision status of certain
engineering documents and/or drawings might not be found online or be otherwise available, in
which case the operator could opt to require the revision status to be included in the maintenance
release for the purpose of ensuring traceability.
Aircraft CRS
A Certificate of Release to Service (CRS) is required before flight:
• At the completion of any maintenance package specified by the aircraft operator;
• At the completion of any defect rectification, while the aircraft operates flight services
between scheduled maintenance.
The maintenance package may include any one or a combination of the following elements: a check
or inspection from the operator's aircraft maintenance program, Airworthiness Directives, overhauls,
repairs, modifications, aircraft component replacements and defect rectification.
New defects or incomplete maintenance work orders identified during maintenance are brought to
the attention of the operator for the specific purpose of obtaining agreement to rectify such defects or
complete the missing elements of the maintenance work order. In the case where the aircraft
operator declines to have such maintenance carried out and provided this missing element/defect
does not affect the airworthiness of the aircraft, this fact is entered in the aircraft CRS before issue of
such certificate.
Component CRS
A CRS is necessary at the completion of any maintenance on an aircraft component while off the
aircraft.
The authorized release certificate/airworthiness approval tag constitutes the aircraft component
certificate of release to service when one AMO maintains an aircraft component for another AMO.
When an AMO maintains an aircraft component for use by the organization, an authorized release
certificate/airworthiness approval tag may or may not be necessary, depending upon the
organization's internal release procedures defined in the maintenance organization exposition and
approved by the Authority.
** A signature shall be: (1) traceable to the individual making the entry and (2) either handwritten or
part of an electronic signature system.
Applicability
Section 5 addresses the safety and security requirements associated with the passenger cabin. This
section is only applicable to an operator that conducts passenger flights with or without cabin crew.
Specifications applicable to the carriage of supernumeraries are located in Section 2 (FLT) of this manual.
Individual provisions in this section all begin with a conditional phrase (“If the Operator...”) and are
applicable to an operator that meets the condition(s) stated in the phrase.
Where an operator outsources the performance of cabin operations functions to external service providers,
the operator retains overall responsibility for ensuring the management of safety in such operations, and
must demonstrate processes for monitoring applicable external service providers in accordance with
CAB 1.10.2.
Additional specifications applicable to passenger flights without cabin crew are located in Section 2 (FLT)
of this manual.
General Guidance
Definitions of technical terms used in this ISM Section 5, as well as the meaning of abbreviations and
acronyms, are found in the IATA Reference Manual for Audit Programs (IRM).
Refer to the IATA Cabin Operations Best Practices Guide for practical information and guidance related to
cabin safety policies and procedures, (http://www.iata.org/publications/Documents/cabin-operations-safety-
bp-guide-2015.pdf).
Guidance
Refer to Guidance associated with ORG 1.3.2 located in ISM Section 1.
CAB 1.2.3 If the Operator conducts passenger flights with cabin crew, the Operator shall ensure a
delegation of authority and assignment of responsibility within the management system for liaison
with regulatory authorities, original equipment manufacturers and other external entities relevant to
cabin operations. (GM) ◄
Auditor Actions
□ Identified cabin operations management individuals with authority for liaison with regulators and
other external entities.
□ Interviewed cabin operations manager/designated management representative(s).
□ Examined selected records of liaison with regulators and other external entities.
□ Other Actions (Specify)
Guidance
Refer to Guidance associated with ORG 1.3.3 located in ISM Section 1.
CAB 1.2.4 If the Operator conducts passenger flights with cabin crew, the Operator shall ensure
the duties and responsibilities of cabin crew members are defined and described in the Operations
Manual (OM). (GM)
Auditor Actions
□ Identified/Assessed defined cabin crew member duties and responsibilities in the OM.
□ Interviewed cabin operations manager/designated management representative(s).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definitions of Cabin Crew Member and Operations Manual.
As a minimum, OM documentation describes:
• Duties and responsibilities for cabin crew members, including cabin crew leader, if
applicable;
• Chain and succession of command on board the aircraft.
CAB 1.2.5 If the Operator conducts passenger flights with cabin crew, the Operator shall ensure
cabin crew members maintain familiarity with laws, regulations and procedures pertinent to the
performance of their duties. (GM)
Auditor Actions
□ Identified/Assessed method for ensuring cabin crew members maintain familiarity with
applicable laws, regulation and procedures.
□ Interviewed cabin operations manager/designated management representative(s).
□ Other Actions (Specify)
Guidance
An operator might utilize other methods that complement training to ensure cabin crew members
remain knowledgeable of the laws, regulations, rules, guidelines and other information that is
relevant in the performance of duties. For example, cabin crew members might have destination-
specific information or briefing books that explain the customs and immigration processes associated
with flying into foreign destinations. Additionally, laws, regulations and procedures might be reviewed
to the extent necessary during cabin crew briefings prior to duty assignments.
CAB 1.2.6 If the Operator conducts passenger flights with cabin crew, the Operator shall have a
policy that addresses the use of psychoactive substances by cabin crew members, which, as a
minimum:
(i) Prohibits the exercise of duties while under the influence of psychoactive substances unless
properly prescribed by a physician and accepted by either the Operator or a physician
designated by the Operator;
(ii) Prohibits the problematic use of psychoactive substances;
(iii) Requires personnel who are identified as engaging in any kind of problematic use of
psychoactive substances to be removed from cabin crew operational functions;
(iv) Conforms to the requirements of the Authority. (GM)
Auditor Actions
□ Identified/Assessed policy that addresses use of psychoactive substances by cabin crew
members.
□ Examined regulatory requirement applicable to the use of psychoactive substances by cabin
crew members.
□ Interviewed cabin operations manager/designated management representative(s).
□ Examined process for dealing with cabin crew members identified as using psychoactive
substances.
□ Interviewed non-management cabin crew members.
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definitions of Biochemical Testing, Psychoactive Substances, Problematic
Use of Substances and State.
Operators subject to laws or regulations of the State of the Operator (hereinafter, the State) that
preclude the publication of a psychoactive substance prohibition policy as specified in this provision
may demonstrate an equivalent method of ensuring that personnel engaging in any kind of
problematic use of psychoactive substance abuse do not exercise their duties and are removed from
safety-critical functions.
Re-instatement to safety-critical duties could be possible after cessation of the problematic use and
upon determination that continued performance of such duties is unlikely to jeopardize safety.
Some of the specifications of this provision may be addressed through implementation of a
scheduling policy as specified in CAB 3.1.7.
Examples of other subjects that might be addressed in a comprehensive and proactive policy
include:
• Education regarding the use of psychoactive substances;
• Identification, treatment and rehabilitation;
• Employment consequences of problematic use of psychoactive substances;
• Biochemical testing;
• Requirements of ICAO and the Authority.
Additional guidance may be found in the ICAO Manual on Prevention of Problematic use of
Substances in the Aviation Workplace (Doc 9654-AN/945).
1.3 Communication
CAB 1.3.1 If the Operator conducts passenger flights with cabin crew, the Operator shall have a
communication system that enables and ensures an exchange of information relevant to the conduct
of cabin operations throughout the cabin operations management system and in all areas where
operations are conducted. (GM) ◄
Auditor Actions
□ Identified/Assessed system(s) for communication of information relevant to operations within
the cabin operations organization.
□ Interviewed cabin operations manager/designated management representative(s).
□ Examined examples of information communication/transfer in cabin operations.
□ Interviewed non-management cabin crew members.
□ Other Actions (Specify)
Guidance
Refer to Guidance associated with ORG 1.4.1 located in ISM Section 1 for expanded information
regarding methods of communication.
CAB 1.3.2 If the Operator conducts passenger flights with cabin crew, the Operator shall have
processes to ensure information relevant to cabin crew policies, procedures and responsibilities is
communicated to all cabin crew members, and to ensure essential operational information or
guidance is communicated to the cabin crew prior to each flight. (GM)
Auditor Actions
□ Identified/Assessed process(es) for communication of information relevant
policies/procedures/responsibilities to cabin crew members prior to each flight.
□ Interviewed cabin operations manager/designated management representative(s).
□ Examined examples of information provided to cabin crew members prior to flight.
□ Observed line cabin operations (focus: cabin crew has received essential operational
information/guidance prior to flight).
□ Other Actions (Specify)
Guidance
Processes are in place to ensure information regarding policies, procedures and responsibilities is
made available to cabin crew members on a regular and timely basis. Vehicles for communication
typically include the cabin crew operations manual, operations bulletins, bulletin board notices, safety
bulletins, electronic platforms, electronic computer messages, telephone calls or any other effective
means.
Also, a process is in place to ensure essential information necessary for the safe conduct of a flight is
communicated to the cabin crew prior to the departure of each flight or series of flights. Such process
would include a means for cabin crew members to acknowledge receipt of essential information.
Written or verbal confirmation to a responsible manager that is recorded is considered an acceptable
means of acknowledgement.
CAB 1.4.2 If the Operator conducts passenger flights with cabin crew, the Operator shall ensure
management and non-management positions within the cabin operations organization that require
the performance of functions relevant to the safety or security of cabin operations are filled by
personnel on the basis of knowledge, skills, training and experience appropriate for the
position. (GM) ◄
Auditor Actions
□ Identified/Assessed standards and processes for selection of personnel in functions relevant to
safety/security in cabin operations.
□ Interviewed cabin operations manager/designated management representative(s).
□ Interviewed personnel that perform functions relevant to the safety/security of in cabin
operations.
□ Other Actions (Specify)
Guidance
Refer to Guidance associated with ORG 1.6.2 located in ISM Section 1.
The operational positions subject to the specifications of this provision typically include those
management personnel required to ensure control and supervision of cabin operations in accordance
with CAB 1.1.1, as defined by the operator or Authority.
A corporate personnel selection policy that applies to all operational areas of the organization serves
to satisfy specifications in this provision.
Auditor Actions
□ Identified/Assessed management and control system for documentation used in cabin
operations.
□ Interviewed responsible management representative(s).
□ Examined selected parts of the cabin OM (focus: legibility/accuracy/format; approval as
applicable).
□ Other Actions (Specify)
Guidance
The intent of this provision is for an operator to provide operational documentation in a format that is
acceptable to the Authority and useable by all relevant personnel.
Documentation used in the support of cabin operations may:
• Exist in electronic form;
• Be issued in more than one language.
Guidance
The Operations Manual contains a list of effective pages and, if applicable, displays evidence of
approval or acceptance by the Authority.
The manual (or revisions) is (are) typically accepted or approved, as applicable, prior to issuance to
cabin crew members and before any operational procedures contained in the manual are
implemented.
In some states, the regulatory authority might have a passive process for providing acceptance of the
manual. In such case, the process defines the procedural steps and provides a record of the
completed steps and date of acceptance.
CAB 1.6.3 If the Operator conducts passenger flights with cabin crew, the Operator shall have a
process to ensure cabin crew members are issued or have direct access to, as a minimum, those
parts of the OM that address duties and responsibilities relevant to the safety and security of cabin
operations. (GM)
Auditor Actions
□ Identified/Assessed process(es) for ensuring cabin crew members are issued or have direct
access to relevant parts of cabin OM.
□ Interviewed cabin operations manager and/or designated management representative(s).
□ Examined parts of OM that require direct access by cabin crew members during flight.
□ Observed line cabin operations (focus: cabin crew has direct access to parts of OM with
duties/responsibilities relevant to safety/security of cabin operations).
□ Other Actions (Specify)
Guidance
The specifications in this provision are applicable to the OM whether issued or accessible in paper or
electronic form.
CAB 1.6.4 If the Operator conducts passenger flights with cabin crew, the Operator shall have a
process to ensure holders of the OM enter the most current amendments or revisions into the manual
and maintain the manual in an up-to-date condition. (GM)
Auditor Actions
□ Identified/Assessed process(es) that ensure cabin crew members record/enter
revisions/amendments to OM to maintain up-to-date condition
□ Identified/Assessed process(es) for checking cabin crew member OMs (focus: validation that
OM are maintained in up-to-date condition).
□ Interviewed cabin operations manager/designated management representative(s).
□ Observed line cabin operations (focus: cabin crew member OM amendments/revisions are up to
date).
□ Other Actions (Specify)
Guidance
When the OM is issued in paper form, a process (checking or other methods) is designed to ensure
the manual is kept up to date by individual cabin crew members. For example, a process could be
established whereby a periodic check of the operations manual of each cabin crew member is
conducted on a scheduled basis (e.g. during recurrent training, line evaluation or preflight briefing).
When the OM is made accessible in electronic form, a process (checking or other method) is
designed to ensure the electronically accessed manual is up to date.
The operator is responsible for amending onboard paper or electronic manuals. The cabin crew can
cross check updates to either type of manual during their preflight check to ensure it contains the
most recent updates, revisions and information.
CAB 1.6.5 If the Operator conducts passenger flights with cabin crew, the Operator shall ensure a
minimum of one complete version of the OM as specified in CAB 1.6.1 is accessible on board the
aircraft for passenger flights and located in a manner that provides for:
(i) If used directly for the conduct of cabin operations, immediate access by each cabin crew
member;
(ii) If utilized as a reference document only, unobstructed access by the cabin crew. (GM)
Auditor Actions
□ Identified/Assessed onboard availability/access of OM to cabin crew members.
□ Interviewed cabin operations manager/designated management representative(s).
□ Observed line cabin operations (focus: onboard accessibility of complete version of OM).
□ Other Actions (Specify)
Guidance
The number of complete OMs on board the aircraft would be determined by how the manual is
utilized by the cabin crew. If the complete version of the OM is used directly for the conduct of cabin
operations, it might be necessary to have more than one copy on board, depending on the size of the
aircraft and the number of cabin crew members.
If a practical manual (or QRH) is used by the cabin crew for the conduct of cabin operations, a
minimum of one complete version of the OM would typically be on board the aircraft for use as a
reference document. The flight deck is an acceptable location for the OM as a reference document if
measures are in place that provide for unobstructed access by the cabin crew.
If electronically accessed manuals are provided on board the aircraft, one or more access terminals
or devices would be located so the cabin crew has immediate or unobstructed access, as applicable
to the way the manual is utilized, the size of the aircraft, and the number of cabin crew members. In
addition, it is recommended that operators give consideration to providing applicable back-up
physical (paper) manuals in case of electronic manual malfunction.
CAB 1.6.6 If the Operator conducts passenger flights with cabin crew, the Operator shall ensure
information in the OM pertaining to cabin crew duties and responsibilities is published in the
designated common language(s) of the Operator, as specified in CAB 3.1.3.
Auditor Actions
□ Identified/Assessed use of designated common language(s) to present OM information
pertaining to cabin crew duties/responsibilities.
□ Interviewed cabin operations manager/designated management representative(s).
□ Examined parts of OM published in designated common language.
□ Observed line cabin operations (focus: OM published in designated common language).
□ Other Actions (Specify)
CAB 1.6.7 If the Operator conducts passenger flights with cabin crew, and publishes a practical
manual for use by the cabin crew in the performance of cabin operations duties, the Operator shall
ensure one or more copies of the up-to-date practical manual are on board the aircraft for passenger
flights and located in a manner that provides for immediate access by each cabin crew
member. (GM)
Auditor Actions
□ Identified/Assessed onboard availability/access of practical manual to cabin crew members.
□ Interviewed cabin operations manager/designated management representative(s).
□ Examined practical manual used by cabin crew members.
□ Observed line cabin operations (if applicable) (focus: one or more copies of up-to-date practical
manual on board; cabin crew has immediate access to practical manual).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Practical Manual.
A practical manual (or QRH) is typically required to be in the possession of each individual cabin
crew member, available at each cabin crew station, or otherwise located to ensure immediate access
by each cabin crew member.
Functions that are associated with the aircraft cabin, but would not normally be conducted by the
cabin operations organization (e.g. aircraft catering) are not addressed by this provision.
Refer to Guidance associated with ORG 3.5.1 located in ISM Section 1.
CAB 1.10.2 If the Operator conducts passenger flights with cabin crew, and has external service
providers conduct outsourced cabin operations functions, the Operator shall have a process to
monitor such external service providers to ensure requirements that affect the safety and/or security
of cabin operations are being fulfilled. (GM) ◄
Auditor Actions
□ Identified/Assessed (focus: monitoring process ensures provider fulfils applicable
safety/security requirements).
□ Interviewed responsible manager(s) in cabin operations.
□ Examined selected records/reports resulting from monitoring of cabin operations service
providers (focus: monitoring process ensures provider fulfils applicable safety/security
requirements).
□ Other Actions (Specify)
Guidance
Monitoring and control of external organizations typically includes random sampling, product audits,
supplier audits, or other similar methods.
Refer to Guidance associated with ORG 3.5.2 located in ISM Section 1.
If an operator outsources any cabin operations function(s) to external service providers as specified
in CAB 1.10.1, then the operator would be required to meet the specifications of this provision.
CAB 1.10.3 If the Operator conducts passenger flights with cabin crew, and has external service
providers conduct outsourced cabin operations functions, the Operator should include auditing as a
process for the monitoring of external service providers in accordance with CAB 1.10.2. (GM) ◄
Auditor Actions
□ Identified/Assessed auditing processes used for monitoring external cabin operations service
providers.
□ Interviewed responsible manager(s) in cabin operations.
□ Examined selected records/reports resulting from auditing of cabin operations service providers
(focus: audit process ensures provider is fulfilling applicable safety/security requirements).
□ Other Actions (Specify)
Guidance
Refer to Guidance associated with ORG 3.5.3 located in ISM Section 1.
CAB 1.10.4 If the Operator conducts passenger flights with cabin crew, the Operator should have a
process to ensure equipment or other operational products relevant to the safety of aircraft
operations that are purchased or otherwise acquired from an external vendor or supplier meet the
product technical requirements specified by the Operator prior to being used in the conduct of
operations. (GM) ◄
Auditor Actions
□ Identified/Assessed processes for acceptance of products acquired for use in cabin operations.
□ Interviewed responsible manager(s) in cabin operations.
□ Examined selected product acceptance records (focus: products meet cabin operations
technical requirements).
□ Other Actions (Specify)
Guidance
Refer to Guidance associated with ORG 3.6.1 located in ISM Section 1.
□ Examined selected records/documents that illustrate risk assessment and resulting risk
mitigation action(s) in cabin operations.
□ Other Action (Specify)
Guidance
Refer to the IRM for the definition of Safety Risk Assessment (SRA).
Risk assessment and mitigation is an element of the Safety Risk Management component of the
SMS framework.
Refer to Guidance associated with ORG 3.1.2 located in ISM Section 1.
Operational Reporting
CAB 1.11.3 If the Operator conducts passenger flights with cabin crew, the Operator shall have an
operational safety reporting system in the cabin operations organization that:
(i) Encourages and facilitates cabin operations personnel to submit reports that identify safety
hazards, expose safety deficiencies and raise safety concerns;
(ii) Ensures mandatory reporting in accordance with applicable regulations;
(iii) Includes analysis and cabin operations management action to address safety issues
identified through the reporting system. [SMS] (GM) ◄
Auditor Actions
□ Identified/Assessed operational safety reporting system in cabin operations (focus: system
urges/facilitates reporting of hazards/safety concerns; includes analysis/action to
validate/address reported hazards/safety concerns).
□ Interviewed responsible manager(s) in cabin operations.
□ Interviewed person(s) that perform operational safety report review/analysis/follow-up in cabin
operations.
□ Examined data that confirm an effective cabin operations safety reporting system (focus:
quantity of reports submitted/hazards identified).
□ Examined records of selected cabin operations safety reports (focus: analysis/follow-up to
identify and address reported hazards/safety concerns).
□ Other Actions (Specify)
Guidance
Safety reporting is a key aspect of SMS hazard identification and risk management.
Refer to Guidance associated with ORG 3.1.3 located in ISM Section 1.
CAB 1.11.4 If the Operator conducts passenger flights with cabin crew, the Operator should have a
confidential safety reporting system in the cabin operations organization that encourages and
facilitates the reporting of events, hazards and/or concerns resulting from or associated with human
performance in operations. (GM) ◄
Auditor Actions
□ Identified/Assessed confidential safety reporting system in cabin operations (focus: system
urges/facilitates reporting of events/hazards/safety concerns caused by humans; report/reporters
are de-identified; includes analysis/action to validate/address reported hazards/safety concerns).
□ Interviewed responsible manager(s) in cabin operations.
□ Examined records of selected cabin operations confidential safety reports (focus: report/reporter
de-identification; analysis/follow-up to identify/address reported hazards/safety concerns).
□ Other Actions (Specify)
Guidance
Refer to Guidance associated with ORG 3.1.4 located in ISM Section 1.
Guidance
An operator, in accordance with the requirements of the Authority, typically uses technical guidance
for the development of an AQP. Such guidance might be derived from one or more of the following
source references, as applicable:
• Office of the Federal Register, (2 October 1990), Special Federal Aviation Regulation
58–Advanced Qualification Program, Federal Register, Vol. 55, No. 91, Rules and
Regulations (pp. 40262–40278).
• FAA 14 CFR Part 121, Subpart Y.
• FAA Advisory Circular 120–54A, Advanced Qualification Program (23 June 2006).
• FAA Advisory Circular 120–51 (3 January 1995), Crew Resource Management Training,
Federal Aviation Administration, Washington DC: U.S. Department of Transportation.
• Any equivalent reference document approved or accepted by the Authority for the
development of an advanced training and qualification program designed to conform to the
specifications of Table 5.2 and Table 5.3.
CAB 2.1.2 If the Operator conducts passenger flights with cabin crew, the Operator shall ensure all
cabin crew members complete an initial training course:
(i) As part of the cabin crew qualification process for individuals who have not previously been
qualified as a cabin crew member for the Operator;
(ii) Prior to being assigned duties as a cabin crew member. (GM)
Auditor Actions
□ Identified/Assessed requirements for completion of initial training by cabin crew members.
□ Interviewed responsible manager(s) in cabin operations
□ Examined records of initial training of selected cabin crew members.
□ Other Actions (Specify)
Guidance
An AQP may allow for deviations and/or an abbreviated curriculum for initial/new hire cabin crew
training in a merger or acquisition situation.
CAB 2.1.3 If the Operator conducts passenger flights with cabin crew, the Operator shall ensure all
cabin crew members complete a recurrent training course once every 12 months or, if applicable, in
accordance with the Operator's AQP as specified in CAB 2.1.1B in order to remain qualified to
perform duties as a cabin crew member. (GM)
Auditor Actions
□ Identified/Assessed requirements for completion of recurrent training by cabin crew members.
□ Interviewed responsible manager(s) in cabin operations
□ Examined records of recurrent training of selected cabin crew members.
□ Other Actions (Specify)
Guidance
An operator typically has a process that tracks qualification requirements to ensure cabin crew
members complete recurrent training in a timely manner to remain qualified.
The nominal cycle for the completion of the recurrent training course by each cabin crew member is
12 months and, during that period, each cabin crew member receives training in the subject areas
applicable to the course for that 12-month period.
As a means of ensuring flexibility in the scheduling process, in some regulatory jurisdictions an
operator may be permitted to increase the maximum cycle for the completion of recurrent training by
cabin crew members up to 15 months with no change to the original training anniversary date of each
cabin crew member. Such flexibility, however, would not alter the requirement for a basic 12-month
recurrent training cycle for cabin crew members.
In the event a cabin crew member becomes unqualified for any reason (e.g., extended leave of
absence), completion of re-qualification training would establish a new anniversary date
(superseding the original anniversary date) upon which recurrent training would be based.
An AQP may have an approved extension to the duration of Continuing Qualification cycle if
evidence substantiates the extension maintains or increases the level of safety for the operator. A
Continuing Qualification cycle may be extended up to a maximum of 39 months. Additionally, an
individual crewmember may be assigned an augmented or additional training and/or evaluation
schedule based on performance during training, qualification or in line operations.
CAB 2.1.4 If the Operator conducts passenger flights with cabin crew, the Operator shall have a
cabin crew requalification training course, which shall be completed:
(i) By individuals who have failed to remain qualified as a cabin crew member;
(ii) As part of the process to regain qualification to perform duties as a cabin crew member;
(iii) If applicable, in accordance with the Operator's AQP as specified in CAB 2.1.1B. (GM)
Auditor Actions
□ Identified/Assessed requirements for completion of requalification training by cabin crew
members.
□ Interviewed responsible manager(s) in cabin operations
□ Examined records of requalification training of selected cabin crew members.
□ Other Actions (Specify)
Guidance
An operator typically has a process that tracks qualification requirements to ensure, when cabin crew
members become unqualified for any reason, such crew members complete applicable
requalification training prior to being assigned to perform duties as a cabin crew member.
An AQP typically includes remediation methodology in its approved documentation describing
strategies that will be used to remediate unsuccessful testing, validation, or evaluation. Remediation
may not require completion of a requalification course. An AQP may allow for flexibility of
requalification requirements based on the Qualification Standards and additional parameters set by
the operator. Any deviations from traditional training requirements will be included in its approved
documentation.
CAB 2.1.1B addresses overall AQP elements and specifications, as well as Authority
approval/acceptance requirements.
CAB 2.1.5 If the Operator conducts passenger flights with cabin crew, the Operator shall have
aircraft type training, which shall be completed by cabin crew members as part of the process to
qualify and remain qualified to perform cabin crew duties on each type of aircraft to which they may
be assigned. As a minimum, subjects covered under aircraft type training shall include:
(i) Aircraft systems;
(ii) Exit locations and operation;
(iii) Emergency equipment locations and operation;
(iv) Emergency assignments;
(v) Unique features of the aircraft cabin (as applicable for variants of a common aircraft
type). (GM)
Auditor Actions
□ Identified/Assessed requirements for completion of aircraft type training by cabin crew
members.
□ Interviewed responsible manager(s) in cabin operations
□ Examined course syllabus for aircraft type training of cabin crew members.
□ Examined records of aircraft type training of selected cabin crew members.
□ Other Actions (Specify)
Guidance
An aircraft type training course for cabin crew members would include the description, locations and
operation of an aircraft and its equipment.
Instruction in aircraft systems typically includes:
• Aircraft interior, passenger seats and restraints;
• Crew member seats and restraints;
• Aircraft-specific duties and responsibilities;
• Galley systems;
• Communication systems;
• Lighting systems;
• Oxygen systems.
Instruction on exit locations and operation addresses the types of exits on an aircraft.
Instruction on emergency equipment locations and operation addresses slides, rafts, slide/rafts, ramp
slide/rafts, life jackets and other flotation devices.
Sub-specification iv): The term “emergency assignments” refers to specific duties assigned to cabin
crew members during emergency situations.
A process, in accordance with requirements of the Authority, would be utilized to qualify cabin crew
members that concurrently operate aircraft of different types or operate variants within one aircraft
type. The qualification process would typically address the differences between variants or types.
CAB 2.1.6 If the Operator conducts passenger flights with cabin crew, the Operator shall require
instructors and evaluators that train and/or evaluate cabin crew members to successfully complete
an instructor and/or evaluator training course that ensures such instructors and evaluators have an
adequate level of knowledge and standardization to provide, as applicable, instruction or evaluation
in the cabin crew training program. (GM)
Auditor Actions
□ Identified/Assessed requirements for completion of instructor/evaluator training by
instructors/evaluator that deliver training courses to or evaluate cabin crew members.
□ Interviewed responsible manager(s) in cabin operations
□ Examined course curriculum/syllabus for training of cabin crew training instructors.
□ Examined records of instructor training of selected cabin crew training instructors/evaluators.
□ Other Actions (Specify)
Guidance
The syllabus for the cabin crew instructor training program typically focuses on instruction techniques
and provides the level of technical knowledge relevant to the areas in which the individual instructor
will deliver instruction.
An AQP typically distinguishes between instructor and evaluator duty positions. However, the
instructor/evaluator role may be assumed by the same person. Distinct training is typically provided
focusing on instruction and evaluation techniques.
CAB 2.1.7 If the Operator conducts passenger flights with cabin crew, the Operator shall ensure
cabin crew training courses include testing or evaluation by written, oral or practical means to satisfy
requirements for cabin crew members to demonstrate adequate knowledge, competency and
proficiency to perform duties, execute normal, abnormal and emergency procedures, and operate
emergency and lifesaving equipment. (GM)
Auditor Actions
□ Identified/Assessed policy/requirement for testing/evaluation in training courses for cabin crew
members.
□ Interviewed responsible manager(s) in cabin operations
General Guidance
Many of the provisions of this subsection make reference to cabin crew training conducted in
accordance with an AQP that is approved or accepted by the Authority as specified in CAB 2.1.1B.
If applicable, AQP allows development of proficiency-based training programs that encourage
innovation in the methods and technologies used during instruction and evaluation, as well as in the
efficient management of the training systems. Since these innovations may require some deviations
from traditional regulations, the approved qualification standards may replace the applicable portions
of the existing regulations and/or training guidance. These deviations or variances will be defined in
the approved AQP documentation.
Additionally, an approved AQP Entry Level Analysis may be documented to achieve the most
effective use of training resources. An Entry Level Analysis may also be utilized to identify where
training is not needed or to justify alternative curriculum tracks or modules targeted at expected
differences in entry background.
In an AQP, criticality and currency determination guides how and when training objectives are
trained, validated or evaluated. A task factor analysis will be documented within the approved training
qualification standards.
CAB 2.2.1 If the Operator conducts passenger flights with cabin crew, the Operator shall ensure
cabin crew members receive training or orientation to provide familiarity with basic aviation subjects
relevant to cabin operations and cabin crew duties. Such training or orientation shall be part of the
cabin crew initial training course and, as a minimum, address the following subject areas:
(i) Applicable regulations;
(ii) Aviation terminology;
(iii) Basic theory of flight;
(iv) Relevant aircraft systems;
(v) Altitude physiology;
(vi) Standard operating procedures for cabin operations on the ground and all phases of
flight. (GM)
Auditor Actions
□ Identified/Assessed requirement for completion of training in basic aviation subjects in cabin
crew initial training course.
□ Interviewed responsible manager(s) in cabin operations.
□ Examined curriculum/syllabus of initial training course for cabin crew members.
□ Examined training records of selected cabin crew members.
□ Other Actions (Specify)
Guidance
Training or orientation in aviation subjects typically would address, on a basic level:
• State, international and company-specific regulations;
• Aviation terminology and theory of flight necessary in the performance of cabin duties;
• Basic flight subjects such as major aircraft components, critical surfaces (including
contamination), pressurization system, weight and balance, meteorology, turbulence,
communications equipment and air traffic control;
• Subjects associated with altitude physiology, such as effects of altitude, hypoxia, the aircraft
oxygen system and operation, gas expansion, depressurization and decompression
sickness;
• Philosophy, structure and application of standard operating procedures.
If such training is delivered in a classroom setting, some of the content may be accomplished via
distance and/or e-learning prior to attending the classroom portion.
Under an AQP, initial training may be referred to as indoctrination and qualification training.
CAB 2.2.2 If the Operator conducts passenger flights with cabin crew, the Operator shall ensure
cabin crew members receive training that provides knowledge of safety policies and procedures
associated with the preflight, in-flight and post-flight phases of cabin operations. Such training shall
be included in the cabin crew initial and requalification training courses, and in the recurrent training
course on a frequency in accordance with requirements of the Authority, but not less than once every
24 months or, if applicable, in accordance with the Operator's AQP as specified in CAB 2.1.1B. (GM)
Auditor Actions
□ Identified/Assessed requirement for completion of prefight/in-flight/post-flight safety training for
cabin crew initial/requalification/recurrent training courses.
□ Interviewed responsible manager(s) in cabin operations.
Auditor Actions
□ Identified/Assessed requirement for completion of cabin emergency equipment training in cabin
crew initial/requalification/recurrent training courses (focus: function/operation of equipment).
□ Interviewed responsible manager(s) in cabin operations
□ Examined curriculum/syllabus of initial/requalification/recurrent emergency equipment training
courses for cabin crew members, including regulatory requirement for frequency of recurrent
training courses.
□ Examined training records of selected cabin crew members.
□ Other Actions (Specify)
Guidance
Aircraft type-training courses may include training in the use of specific emergency equipment such
as slides, rafts, slide/rafts and ramp slide/rafts.
CAB 2.2.5 If the Operator conducts passenger flights with cabin crew, the Operator shall ensure
cabin crew members complete practical training exercises consisting of cabin drills and hands-on
operation of cabin equipment. Practical training exercises shall be included in the cabin crew initial
and requalification training courses, and in the recurrent training course on a frequency in
accordance with requirements of the Authority. All focus areas within the scope of practical training
exercises shall be addressed in recurrent training not less than once every 36 months or, if
applicable, in accordance with the Operator's AQP as specified in CAB 2.1.1B. As a minimum, focus
areas within the scope of practical training exercises include:
(i) Cabin exit operations (normal and emergency) for each aircraft and exit type;
(ii) Cabin emergency evacuation;
(iii) If the operator utilizes aircraft equipped with cabin doors that have emergency egress slides:
(a) Initial training: Use of emergency egress slide(s);
(b) Requalification and recurrent training: Use of emergency egress slide(s) in
accordance with requirements of the Authority.
(iv) Firefighting;
(v) Oxygen administration;
(vi) If required, ditching. (GM)
Note: If applicable, cabin crew members may complete practical training exercises through
participation in event management scenarios in accordance with the Operator's AQP as specified in
CAB 2.1.1B.
Auditor Actions
□ Identified/Assessed requirement for completion of practical training exercises (cabin drills and
hands-on operation of cabin equipment) in cabin crew initial/requalification/recurrent training
courses.
□ Interviewed responsible manager(s) in cabin operations.
□ Examined curriculum/syllabus of initial/requalification/recurrent training exercises in courses for
cabin crew members (focus: frequency of exercises/courses and regulatory requirement for
frequency of recurrent training exercises/courses).
□ Examined training records of selected cabin crew members.
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Wet Drill.
Practical training exercises to satisfy this provision typically include procedures associated with the
use of cabin systems and equipment, to include the public address and intercom systems, life-rafts,
life preservers, PBE/smoke hoods, as well as operation of the door(s), deployment and use of
emergency egress slide(s), fighting an actual or simulated fire, operation of hand fire extinguishers,
passenger briefings and in-flight decompression (group drill).
Personal electronic devices powered by rechargeable lithium-ion (LI) batteries are common in the
passenger cabin. The batteries in such devices have the potential for overheating (thermal runaway),
explosion and fire. An operator might consider a practical training exercise that simulates a LI battery
fire in the cabin, thus requiring the cabin crew members to implement firefighting procedures
appropriate for this type of fire.
Hands-on practical training exercises might involve the use of actual aircraft emergency and
lifesaving equipment, or be conducted using realistic and functional simulators or mock-ups.
A requirement for a practical training exercise for ditching is determined by the State. An operator
that conducts over-water and/or long-range over-water flights would typically ensure cabin crew
members complete practical training exercises in ditching.
An operator might elect to include a wet drill as part of initial training as a means of providing hands-
on familiarization with ditching equipment and procedures. A wet drill would require cabin crew
members to go into the water and then climb into a raft, or board a raft in the water directly from an
aircraft exit (with cabin crew members not going into the water).
When utilizing the actual aircraft to conduct training in emergency exit operations, emergency
operation can be simulated by disarming the exits and having the trainee accomplish all steps as
though the door were armed.
Due to challenges and problems associated with using actual aircraft systems, cabin simulators or
training mock-ups are typically utilized to the extent possible. If cabin exit simulators or training mock-
ups are not available, practical hands-on drills are performed on board actual aircraft, which, to
preclude disruption of training, would necessitate a documented program and aircraft schedule.
CAB 2.2.6 If the Operator conducts passenger flights with cabin crew, and utilizes pressurized
aircraft, the Operator shall ensure cabin crew members receive training in high altitude
depressurization. Such training shall be included in the cabin crew initial and re-qualification training
courses, and in the recurrent training course, once every 24 months or, if applicable, in accordance
with the Operator's AQP as specified in CAB 2.1.1B. Training in high altitude depressurization shall
provide:
(i) An understanding of the effects on crew and passengers;
(ii) The knowledge necessary to execute associated emergency procedures. (GM)
Auditor Actions
□ Identified/Assessed requirement for completion of high altitude depressurization training in
cabin crew initial/requalification/recurrent training courses.
□ Interviewed responsible manager(s) in cabin operations.
□ Examined curriculum/syllabus of initial/requalification/recurrent training courses for cabin crew
members (focus: effects on crew and passengers, execution of associated emergency
procedures and frequency of recurrent training courses).
□ Examined training records of selected cabin crew members.
□ Other Actions (Specify)
Guidance
Training in depressurization may be conducted in the classroom, via distance and/or e-learning, as a
practical exercise, or by using a combination of methods.
A video presentation on the effects of hypoxia and a re-enactment of an explosive depressurization
to emphasize the visual effects on the crew and passengers is an example of one means of
presenting depressurization training. A presentation that includes photos, accompanied by a group
discussion, is another example of a means of presenting such material.
CAB 2.2.7 If the Operator conducts passenger flights with cabin crew, the Operator shall ensure
cabin crew members receive training in dangerous goods awareness, recognition and emergency
action. Such training shall be included in the cabin crew initial and re-qualification training courses
and in the recurrent training course on a frequency in accordance with requirements of the Authority,
but all subjects within the scope of dangerous goods training shall be addressed not less than once
within the 24-month period from the previous training in dangerous goods. As a minimum, subjects
within the scope of dangerous goods training include:
(i) General philosophy;
(ii) Limitations;
(iii) Labeling and marking;
(iv) Recognition of undeclared dangerous goods;
(v) Provisions for passengers and crew;
(vi) Emergency procedures. (GM)
Auditor Actions
□ Identified/Assessed requirement for completion of dangerous goods training
(awareness/recognition/emergency action) in cabin crew initial/requalification/recurrent training
courses.
□ Examined regulatory requirement for frequency of training in dangerous goods in cabin crew
recurrent training.
□ Interviewed responsible manager(s) in cabin operations.
□ Examined curriculum/syllabus of initial/requalification/recurrent training courses for cabin crew
members.
□ Examined training records of selected cabin crew members.
□ Other Actions (Specify)
Guidance
This provision specifies the minimum dangerous goods awareness training required for cabin crew
members and is applicable to an operator regardless of whether such operator transports or does not
transport dangerous goods.
Recurrent training in dangerous goods is completed within a validity period that expires 24 months
from the previous training to ensure knowledge is current, unless a shorter period is defined by a
competent authority. However, when such recurrent training is completed within the final 3 months of
the 24-month validity period, the new validity period may extend from the month on which the
recurrent training was completed until 24 months from the expiry month of the current validity period.
If such recurrent training is completed prior to the final three months of the validity period, the new
validity period would extend 24 months from the month the recurrent training was completed.
CAB 2.2.8 If the Operator conducts passenger flights with cabin crew, the Operator shall ensure
cabin crew members receive training in human performance to gain an understanding of the human
factors involved in conducting cabin safety duties and coordinating with the flight crew during the
execution of onboard emergency procedures. Such training shall be included in the cabin crew initial
and re-qualification training courses, and in the recurrent training course, on a frequency in
accordance with requirements of the Authority, but not less than once every 36 months or, if
applicable, in accordance with the Operator's AQP as specified in CAB 2.1.1B. (GM)
Auditor Actions
□ Identified/Assessed requirement for completion of cabin operations human performance
training in cabin crew initial/requalification/recurrent training courses.
□ Interviewed responsible manager(s) in cabin operations.
□ Examined curriculum/syllabus of initial/requalification/recurrent training courses in human
performance for cabin crew members (focus: cabin safety duties, coordination with flight crew
during execution of onboard emergency procedures, regulatory requirements for frequency of
recurrent training courses).
□ Examined training records of selected cabin crew members.
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definitions of Crew Resource management (CRM), Human Factors
Principles and Human Performance.
Training in human performance usually includes basic human factors concepts and crew resource
management (CRM).
CAB 2.2.9 If the Operator conducts passenger flights with cabin crew, and utilizes aircraft that
require more than one cabin crew member, the Operator shall ensure cabin crew members receive
training that provides the necessary awareness of other cabin crew assignments and procedures to
assure fulfillment of all cabin crew duties in the event of an emergency situation. Such training shall
be included in the cabin crew initial and re-qualification training courses and in the recurrent training
course, on a frequency in accordance with requirements of the Authority, but not less than once
every 24 months or, if applicable, in accordance with the Operator's AQP as specified in CAB 2.1.1B.
Auditor Actions
□ Identified/Assessed requirement for completion of cabin crew assignments/procedures
awareness training in cabin crew initial/requalification/recurrent training courses.
□ Interviewed responsible manager(s) in cabin operations
□ Examined curriculum/syllabus of initial/requalification/recurrent training courses for cabin crew
members (focus: awareness of other cabin crew assignments, fulfillment of cabin crew duties
during emergency situations, regulatory requirements for frequency of recurrent training
courses).
□ Examined training records of selected cabin crew members.
□ Other Actions (Specify)
CAB 2.2.10 If the Operator conducts passenger flights with cabin crew, the Operator should
ensure cabin crew members participate in joint training activities or exercises with flight crew
members for the purpose of enhancing onboard coordination and mutual understanding of the
human factors involved in addressing emergency situations and security threats. (GM)
Note: If applicable, cabin-flight crew training as specified in this provision may be accomplished
through activities or exercises delivered independently to cabin and flight crew members in
accordance with the Operator's AQP as specified in CAB 2.1.1B.
Auditor Actions
□ Identified/Assessed requirement for joint cabin crew/flight crew training activities/exercises
□ Interviewed responsible manager(s) in cabin operations.
□ Examined curriculum/syllabus of joint cabin crew/flight crew training activities/exercises (focus:
onboard coordination, mutual understanding of human factors involved in emergencies/security
threats).
□ Examined training records of selected cabin crew members.
□ Other Actions (Specify)
Guidance
Joint training provides a forum to focus on the coordination and communication necessary between
the flight and cabin crews and the subjects associated with emergency procedures, security
procedures and human factors. To the extent possible, such training would include joint practical
training exercises. If such exercises are not possible, joint interactive discussion in the subject areas
is an acceptable alternative.
The intent of this provision is that the specified training is delivered jointly to cabin and flight crew
members together in a common location. However, under certain specific conditions, conformity with
this provision may be accomplished through training delivered independently to cabin and flight crew
members:
• When approved by the Authority under an Advanced Qualification Program (AQP), or
• When the cabin crew training and flight crew training occurs at different geographical
locations or on different training cycles.
When training is delivered independently under the above conditions, learning objectives are
determined jointly through interdepartmental coordination and subsequently incorporated into the
respective cabin crew and flight crew training curricula. It is possible that, although the learning
objectives are determined jointly, the development of curricula and administration of the training
occurs independently within each department.
CAB 2.2.11 If the Operator conducts passenger flights with cabin crew, the Operator shall ensure
cabin crew members receive training that provides knowledge in first aid. Such training shall be
included in the initial and re-qualification training courses and in the recurrent training course, on a
frequency in accordance with requirements of the Authority, but all subjects within the scope of first
aid training shall be addressed not less than once every 36 months or, if applicable, in accordance
with the Operator's AQP as specified in CAB 2.1.1B. As a minimum, subjects within the scope of first
aid training include:
(i) Life-threatening medical emergencies;
(ii) Cardiopulmonary resuscitation (CPR);
(iii) Management of injuries;
(iv) Management of illnesses;
(v) First-aid equipment and supplies;
(vi) If applicable, medical equipment and supplies. (GM)
Auditor Actions
□ Identified/Assessed requirement for completion of first aid training in cabin crew
initial/requalification/recurrent training courses.
□ Interviewed responsible manager(s) in cabin operations.
□ Examined curriculum/syllabus of initial/requalification/recurrent training in first aid for cabin crew
members (focus: scope/content/frequency of training, regulatory requirements for frequency of
recurrent training).
□ Examined training records of selected cabin crew members.
□ Other Actions (Specify)
Guidance
Under an AQP, initial training may be referred to as indoctrination and qualification training.
Training typically provides knowledge and skill in five subject areas appropriate for cabin crew
members. Suggested subject areas are as follows:
1. Altitude physiology (working at altitude):
• Changes in atmospheric pressure;
• Relative hypoxia;
• Trapped gas;
• Decompression sickness;
• Cabin depressurization;
• Hyperventilation;
• Cabin air quality.
2. Travel health:
• Immunization;
• Protection against infectious diseases;
• Circadian rhythm and jet lag;
• Fatigue management;
• Personal safety (e.g. use of alcohol, other drugs, traffic safety).
3. Standards and regulations:
• First aid training and equipment (ICAO standards and/or CAA regulations);
• Reporting of communicable diseases (ICAO standards and WHO International
Health Regulations);
• Aircraft disinfection and disinsection (application of insecticide);
• Biohazard waste disposal.
4. Procedures and resources:
• Seeking medical advice (ground and/or in flight);
• Medical equipment (e.g. first aid kit, medical kit, oxygen);
• Death on board;
• Birth on board;
• Documentation to be completed;
• PIC notification and communication.
5. First aid (problem recognition and management):
• Assessing a casualty;
• Lifesaving procedures:
– Assess ABC (adult, child, infant);
– Choking;
– CPR (practical training);
– Recovery position.
• Medical problems:
– The unconscious (underlying causes);
– Suspected communicable diseases;
– Respiratory disorders (asthma, hyperventilation, chronic lung diseases,
persistent coughing);
– Cardiovascular disorders (angina, heart attack, shock, DVT);
– Abdominal problems (vomiting, diarrhea, pain, heartburn, bleeding);
– Nervous system disorders (headache, seizure, stroke);
– Ear, nose and throat problems such as barotrauma (body damage caused
by pressurization difference) and/or epistaxis (nose bleed);
– Behavioral/psychological disorders (panic attack, alcohol intoxication,
irrational behavior);
– Other problems (diabetes, allergic reaction, pregnancy related).
• Trauma:
– Wounds and bleeding (practical training);
– Burns;
– Head and neck injury;
– Eye injury;
– Musculoskeletal injury;
– Chest and abdominal injury.
Initial training would typically address all the subject areas listed above.
Unless there were changes to the altitude physiology, travel health and regulations components, it
would not be necessary to review these areas each year. However, in the event of changes, cabin
crew members would typically be promptly advised, and such changes may then be addressed
during the next recurrent training.
The procedures, resources and first aid subject areas may be addressed in recurrent training, to
include testing and evaluation. Selected elements included in these subject areas would be
addressed each year in recurrent training such that all elements are addressed during every
36-month period or, if applicable, in accordance with the Operator's AQP.
CPR is a lifesaving procedure that requires practice in order to maintain competence. Therefore, it is
recommended that cabin crew members complete recurrent training in the most current CPR
procedures on an annual basis.
It is recommended that elements chosen to be reviewed each year be built into practical scenarios.
Scenario-based training is advantageous because:
• It requires the crew to function as a team;
• Scenarios might be designed to cover multiple aspects of first aid, as well as subjects from
other areas, such as altitude physiology and regulations;
• It stimulates participation and improves retention.
Other training methods would also be acceptable as long as it can be reasonably established that
cabin crew members have the knowledge and skills to apply first aid and lifesaving procedures at any
given time.
CAB 2.2.12 If the Operator conducts passenger flights with cabin crew, the Operator shall ensure
cabin crew members complete initial and recurrent security training as approved or accepted by the
State, and in accordance with the Operator's security training program as specified in SEC 2.1.1.
Such training shall be completed during initial ground training and subsequently during recurrent
training a minimum of once every 36 months or, if applicable, in accordance with the initial and
continuing qualification curriculum as defined in the Operator's AQP that conforms to the
specifications of CAB 2.1.1B. Cabin crew security training shall address the following subject areas:
(i) Determination of the seriousness of any occurrence;
(ii) Crew communication and coordination;
(iii) Appropriate self-defense responses;
(iv) Use of non-lethal protective devices assigned to crew members for use as authorized by the
State;
(v) Understanding the behavior of terrorists so as to facilitate the ability to cope with hijacker
behavior and passenger responses;
(vi) Situational training exercises regarding various threat conditions;
(vii) Flight deck procedures to protect the aircraft;
(viii) Aircraft search procedures;
(ix) As practicable, guidance on least-risk bomb locations. (GM)
Note: Cabin crew members shall complete initial security training prior to being assigned to
operational duties.
Auditor Actions
□ Identified/Assessed cabin crew security training program (focus: approval/acceptance by the
State; meets applicable requirements of other states).
□ Interviewed responsible manager(s) in cabin operations.
□ Examined selected initial/recurrent training/qualification course curricula/syllabi (focus: security
training is included; required subjects are addressed).
conduct these particular supervisory responsibilities. This activity does not necessarily require the
presence of a cabin crew instructor or evaluator to provide the supervision.
CAB 2.3.3 If the Operator conducts passenger flights with cabin crew, the Operator should ensure
cabin crew members complete supervised line flight experience as part of the cabin crew re-
qualification process and prior to being assigned unsupervised duties on any aircraft requiring more
than one cabin crew member. (GM)
Note: If applicable, supervised line flight experience for cabin crew member requalification may be
accomplished through use of a modified curriculum in accordance with the Operator's AQP as
specified in CAB 2.1.1B.
Auditor Actions
□ Identified/Assessed requirement for completion of supervised line flight experience as part of
cabin crew requalification (focus: completion required prior to being assigned to unsupervised
duties).
□ Interviewed responsible manager(s) in cabin operations.
□ Examined criteria/activities/responsibilities included in supervised line experience
(requalification).
□ Examined training/qualification records of selected cabin crew members (focus: completion of
supervised line experience prior to being assigned to unsupervised duties).
□ Other Actions (Specify)
Guidance
Supervised line flight experience is typically referred to as a familiarization flight.
This provision would be applicable to an operator that has aircraft in its fleet that require two or more
cabin crew members.
Line flight experience for cabin crew members as part of the re-qualification training course may be
conducted under the supervision of cabin crew members assigned cabin leadership responsibilities
in normal line operations (e.g. purser, cabin leader, lead flight attendant, onboard leader or other
similar positions) or specially qualified to conduct these particular supervisory responsibilities. This
activity does not necessarily require the presence of a cabin crew instructor or evaluator to provide
the necessary supervision.
An approved AQP Entry Level Analysis may be documented to achieve the most effective use of
training resources. An Entry Level Analysis may also be utilized to identify where training is not
needed or to justify alternative curriculum tracks or modules targeted at expected differences in entry
background.
CAB 2.3.4 If the Operator conducts passenger flights with cabin crew, the Operator should ensure
cabin crew members receive a periodic line evaluation or check while performing their duties during
line operations. (GM)
Note: If applicable, a periodic line evaluation or check may be accomplished through use of a
modified curriculum in accordance with the Operator's AQP as specified in CAB 2.1.1B.
Auditor Actions
□ Identified/Assessed requirement for completion of periodic line evaluation/check of cabin crew
members.
□ Interviewed responsible manager(s) in cabin operations.
□ Examined process/criteria/content for periodic line evaluation/checks of cabin crew members.
□ Examined training/qualification records of selected cabin crew members.
□ Other Actions (Specify)
Guidance
The line evaluation check of cabin crew members is typically conducted by a cabin crew member
who has been specially qualified and designated to conduct dedicated supervisory activities (e.g.
evaluator, instructor, purser or other similar supervisory position).
The periodic line evaluation or check of cabin crew members is normally conducted using a checklist
that contains the standards for performance that are being evaluated. The results of the evaluation or
check would be recorded on the checklist, which is retained with other cabin crew qualification
records.
3 Line Operations
CAB 3.1.2 If the Operator conducts passenger flights with cabin crew, and utilizes aircraft that
require more than one cabin crew member, the Operator shall ensure designation of a cabin crew
leader who has overall responsibility for the conduct and coordination of normal and emergency
cabin procedures for flights with more than one cabin crew member. (GM)
Auditor Actions
□ Identified/Assessed means of designating cabin crew leaders for flights with more than one
cabin crew member.
□ Interviewed responsible manager(s) in cabin operations.
□ Examined responsibilities cabin crew leaders.
□ Observed line cabin operations (focus: designation of a cabin crew leader).
□ Other Actions (Specify)
Guidance
The position of cabin crew leader might have a different title or name according to the operator (e.g.
purser, lead flight attendant, senior cabin crew member or onboard leader).
The use of selection prerequisites ensures designated cabin crew leaders have a defined amount of
experience as a cabin crew member (e.g. minimum one year of experience) before being assigned to
a leadership position. New operators could be required to establish alternative minimum experience
requirements.
Once selected, cabin crew leaders would receive specialized leadership training in accordance with
applicable regulations and standards of the operator before being assigned to operations.
A replacement plan, approved by the Authority, if applicable, would be necessary to ensure the
leader position is filled when the primary cabin crew leader becomes incapacitated or is otherwise
unable to carry out assigned duties.
CAB 3.1.3 If the Operator conducts passenger flights with cabin crew, the Operator shall have
procedures to ensure communication between the cabin crew and flight crew during line operations
is conducted in the designated common language(s) of the Operator, as specified in FLT 3.1.1. (GM)
Auditor Actions
□ Identified/assessed procedures for use of common language in line operations (focus:
requirement that communication between cabin/flight crew is in designated common
language(s).
□ Interviewed responsible manager(s) in cabin operations.
□ Observed line cabin operations (focus: cabin crew communication with flight crew in designated
common language).
□ Other Actions (Specify)
Guidance
The specifications contained in FLT 3.1.1 require an operator to designate a common language that
is used by flight crew members for communication with the cabin crew during line operations.
In cases when the cabin crew includes members who do not all speak the common language, cabin
crew members would normally be assigned to work positions throughout the cabin to ensure any
communication with the flight crew is conducted by members who speak the common language.
During long haul operations, the crew rest schedule is typically structured so a sufficient number of
cabin crew members who speak the common language are available and in a position to
communicate with the flight crew when necessary.
Refer to FLT 3.1.1 in Section 2 (FLT) of this manual.
CAB 3.1.4A If the Operator conducts passenger flights with cabin crew, the Operator shall have a
methodology for the purpose of managing fatigue-related safety risks to ensure fatigue occurring in
one flight, successive flights or accumulated over a period of time does not impair a cabin crew
member's alertness and ability to perform safety-related cabin duties. Such methodology shall
consist of:
(i) Flight time, flight duty period, duty period and rest period limitations that are in accordance
with the applicable prescriptive fatigue management regulations of the State, and/or,
(ii) If applicable, the Operator's Fatigue Risk Management System (FRMS) approved or
accepted by the State and established in accordance with CAB 3.1.4B. (GM)
Auditor Actions
□ Identified/Assessed operator methodology for the management of fatigue.
□ Identified/Assessed flight time and duty period limitations and rest period limitations as well as
rest periods scheme for cabin crew members.
□ Interviewed responsible manager(s) in cabin operations.
□ Interviewed selected scheduling personnel.
□ Examined selected cabin crew records/rosters (focus: application of fatigue risk management
limitations/restrictions).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Fatigue Risk Management System (FRMS).
The intent of this provision is to ensure an operator establishes a methodology for the management
of cabin crew member fatigue in a manner that:
• Is based upon scientific principles and knowledge;
• Is consistent with the prescriptive fatigue management and/or FRMS regulations of the State;
• Precludes fatigue from endangering safety of the flight.
Where authorized by the State, the operator may use a Fatigue Risk Management System (FRMS) in
accordance with CAB 3.1.4B alone or in combination with prescriptive flight time, flight duty period,
duty period and rest period limitations as the means for managing fatigue-related risks.
Guidance for the implementation of an FRMS is contained in the IATA Fatigue Management Guide
for Airline Operators, 2nd Edition, 2015, and, as applicable, other reference documents approved or
accepted by the State for the purpose of FRMS implementation (e.g. FAA, AC 120-103A–Fatigue
Risk Management Systems for Aviation Safety).
CAB 3.1.4B If the Operator conducts passenger flights with cabin crew and utilizes an FRMS to
manage cabin crew fatigue-related safety risks, the Operator shall incorporate scientific principles
and knowledge within the FRMS, comply with any applicable requirements for managing cabin crew
fatigue as established by the State or Authority and, as a minimum:
(i) Define and document the FRMS policy;
(ii) Incorporate risk management processes for fatigue hazard identification, risk assessment
and, if required, mitigation;
(iii) Develop and maintain effective FRMS safety assurance processes;
(iv) Establish and implement effective FRMS promotion processes. (GM)
Auditor Actions
□ Identified/Assessed FRMS policy/components/elements, compliance with fatigue risk
management requirements of State/Authority.
□ Identified/Assessed FRMS processes for cabin crew fatigue risk management data
collection/analysis/hazard identification, safety risk assessment, safety risk mitigation/control.
□ Interviewed responsible manager(s) in cabin operations.
□ Interviewed selected personnel that perform cabin crew fatigue safety risk management
functions.
□ Examined selected examples of fatigue risk management (focus: hazard identified, risk
mitigation action implemented).
□ Other Action (Specify)
Guidance
The intent of this provision is to ensure fatigue occurring either in one flight, successive flights or
accumulated over a period of time does not impair a cabin crew member's alertness and ability to
safely perform safety-related cabin duties.
Where authorized by the State, the operator may use an FRMS as a means to determine that
variations from prescriptive fatigue management policies demonstrate an acceptable level of safety.
Guidance for the implementation of an FRMS is contained in the IATA Fatigue Management Guide
for Airline Operators, 2nd Edition, 2015, and, as applicable, other reference documents approved or
accepted by the State for the purpose of FRMS implementation (e.g. FAA, AC 120-103A - Fatigue
Risk Management Systems for Aviation Safety).
The applicability of this provision is limited to those operations wherein fatigue is managed in
accordance with the FRMS as defined in the operator's FRMS documentation. It is important to note,
however, that an FRMS may be used alone or in combination with prescriptive flight time, flight duty
period and rest period limitations as the means for managing fatigue related risks.
The components of an effective FRMS as specified in this provision are described in the following
table.
CAB 3.1.4C If the Operator conducts passenger flights with cabin crew and utilizes an FRMS to
manage cabin crew fatigue-related safety risks, the Operator should ensure the organizational
activities specified in CAB 3.1.4B related to the management of cabin crew fatigue-related risks are
integrated with the Operator's organizational safety management system (SMS) as specified in ORG
1.1.10. (GM)
Auditor Actions
□ Identified/Examined operator methodology for the management of fatigue.
□ Identified/Examined system (SMS) structure.
□ Identified/Assessed processes that integrate FRMS with SMS.
□ Interviewed SMS accountable executive and/or designated management representative(s).
□ Interviewed responsible cabin operations manager.
□ Examined selected records/documents that illustrate integration of FRMS in the organization-
wide, cross-discipline safety risk assessment and mitigation program.
□ Other Action (Specify)
Guidance
The intent of this provision is to ensure the “tactical” organizational activities specified in CAB 3.1.4B
interface with organizational safety risk management activities. This includes interfaces with SMS
and Quality systems to ensure operational systems and processes are subjected to the
organization's overarching safety and quality assurance processes.
Guidance for the integration of FRMS and SMS is described in the IATA/ICAO/IFALPA Fatigue
Management Guide for Airline Operators, 2nd Edition, 2015.
CAB 3.1.5 If the Operator conducts passenger flights with cabin crew, the Operator shall have a
process to ensure flight time, flight duty periods and rest periods for cabin crew members are
recorded and retained for a minimum period of time in accordance with applicable regulations. (GM)
Auditor Actions
□ Identified process for retention of duty and rest periods.
□ Interviewed responsible manager(s) in cabin operations.
□ Examined time limits for retention of duty and rest periods.
□ Examined selected records of duty and rest periods.
□ Other Actions (Specify)
Guidance
For each cabin crew member, flight/duty time records would typically consist of:
• The start, duration and end of each flight duty period;
• The start, duration and end of each duty period;
• Rest periods;
• Flight time.
If computer software is used for cabin crew planning and scheduling, the operator would ensure the
software provides appropriate warnings when individual flight segments or series of flight segments
are projected to exceed applicable maximum or minimum limits.
CAB 3.1.6 If the Operator conducts passenger flights with cabin crew, the Operator shall consider
the following as duty time for the purpose of determining required rest periods and calculating duty
time limitations for operating cabin crew members:
(i) Entire duration of the flight;
(ii) Pre-operating deadhead time;
(iii) Training period(s) prior to a flight;
(iv) Administrative or office time prior to a flight (for cabin crew members that serve in a
management function). (GM)
Auditor Actions
□ Identified the means of calculation of duty time limitations for operating cabin crew members.
□ Interviewed responsible manager(s) in cabin operations.
□ Examined criteria for calculating duty time and rest period limits.
□ Examined selected records of duty times and rest periods.
□ Other Actions (Specify)
Guidance
Refer to the IRM of the definition of Deadheading. The intent of this provision is to ensure an operator
considers non-flight duty time that is likely to induce fatigue into the calculation of duty time limitations
and the determination of required rest periods.
CAB 3.1.7 If the Operator conducts passenger flights with cabin crew, the Operator shall have a
policy that ensures cabin crew members, prior to being assigned to duty, will not be affected by
factors that could impair human performance. Such factors include, as a minimum:
(i) Pregnancy;
(ii) Illness, surgery or use of medication(s);
(iii) Blood donation;
(iv) Deep underwater diving. (GM)
Auditor Actions
□ Identified policy that ensures that, prior to being assigned to duty, cabin crew members will not
be affected by factors that could impair human performance.
□ Interviewed responsible manager(s) in cabin operations.
□ Examined selected evidence of implementation of the policy (if available).
□ Other Actions (Specify)
Guidance
The intent of this provision is to ensure an operator's policies address the “fitness for duty” of cabin
crew members. Such policy typically assigns responsibility to the individual cabin crew member to
report and remain “fit for duty” in accordance with the specifications.
• Between the cabin crew and the flight crew (when the flight crew is on board) for the purpose
of ensuring notification when fueling operations are in progress and when a passenger
evacuation is required;
• Between the cabin crew and the flight crew and/or ground handling personnel for the
purpose of ensuring notification when fueling operations must be discontinued for any
reason.
CAB 3.2.3 If the Operator conducts passenger flights with cabin crew, the Operator shall have a
procedure to ensure the cabin crew verifies that:
(i) Passenger and crew baggage in the passenger cabin is securely stowed;
(ii) If applicable, cargo packages and/or passenger items being transported in passenger seats
are properly secured. (GM)
Auditor Actions
□ Identified procedure for cabin crew to verify cabin security (focus: baggage and cargo
packages/passenger items are stowed or properly secured).
□ Interviewed responsible manager(s) in cabin operations.
□ Observed line cabin operations (focus: cabin crew procedure to verify baggage and cargo
packages/passenger items are stowed or properly secured).
□ Other Actions (Specify)
Guidance
The intent of this provision is for an operator to have a procedure for verification by the cabin crew
that all baggage and, if applicable, cargo packages and/or passenger items being transported in
passenger seats are stowed or properly secured.
Some operators might transport smaller cargo packages (e.g. mail, COMAT items) secured in cabin
passenger seats.
Some operators might transport certain passenger items secured in cabin passenger seats. These
types of items are typically large, valuable or fragile articles belonging to passengers that are not
conducive to transport as checked baggage or appropriate for stowage in overhead bins/lockers (e.g.
large musical instruments, certain electronic equipment, prominent trophies, works of art). Such
items might thus be secured and carried in a dedicated cabin passenger seat (which might be
purchased by the passenger-owner for the purpose of transporting the item). Of course, an operator
would typically accept such items in the cabin only if the safety and comfort of other passengers will
not be compromised.
CAB 3.2.4 If the Operator conducts passenger flights with cabin crew, and utilizes aircraft
equipped with cabin doors that have an automatic slide or slide/raft deployment system, the Operator
shall have cabin crew procedures for arming and disarming such door systems. (GM)
Auditor Actions
□ Identified procedures for arming and disarming door systems.
□ Interviewed responsible manager(s) in cabin operations.
□ Observed line cabin operations (focus: cabin crew procedures for arming/disarming applicable
cabin door slides/slide rafts).
□ Other Actions (Specify)
Guidance
This standard addresses door systems that are designed to automatically deploy a slide or slide/raft
for emergency evacuation if the door is opened with the system in the armed mode. Such door
systems are typically armed once the door has been closed for flight, and disarmed at the end of a
flight and prior to the door being opened for passenger and/or crew deplaning.
Depending on the type of aircraft and door system, the pack that contains the slide or slide/raft might
be mounted in the door itself, or might be mounted in the fuselage, tail cone or other location.
CAB 3.2.5 If the Operator conducts passenger flights with cabin crew, the Operator shall require
cabin crew members to be seated with their safety harness fastened:
(i) During the takeoff and landing phases of flight;
(ii) Whenever the pilot-in-command (PIC) so directs. (GM)
Auditor Actions
□ Identified/Assessed requirements and conditions for cabin crew members to be seated with
their safety harness fastened.
□ Interviewed responsible manager(s) in cabin operations.
□ Observed line cabin operations (focus: cabin crew seated/safety harness fastened for
takeoff/landing, when directed by PIC).
□ Other Actions (Specify)
Guidance
The safety harness consists of the seat belt and shoulder straps.
CAB 3.2.6 If the Operator conducts passenger flights with cabin crew, the Operator should require
cabin crew members to be seated with their safety harnesses fastened when the aircraft is taxiing,
except to perform safety-related duties.
Auditor Actions
□ Identified means of ensuring cabin crew are seated with safety harness fastened when aircraft is
taxiing, except to perform safety-related duties.
□ Interviewed responsible manager(s) in cabin operations.
□ Observed line cabin operations (focus: cabin crew seated/safety harness fastened for taxi
operations, except to perform safety duties).
□ Other Actions (Specify)
CAB 3.2.7 If the Operator conducts passenger flights with cabin crew, the Operator shall have
procedures for preparation of the cabin prior to takeoff and landing. (GM)
Auditor Actions
□ Identified/Assessed procedures for cabin preparation prior to takeoff and landing.
□ Interviewed responsible manager(s) in cabin operations.
□ Observed line cabin operations (focus: cabin crew procedures for cabin preparation prior to
takeoff/landing).
□ Other Actions (Specify)
Guidance
Preparation of the cabin prior to takeoff and landing would require the cabin crew to visually verify
certain conditions are in effect. Items checked by the cabin crew will vary according to aircraft type
and equipment carried, but typically include:
• Passenger seat belts fastened;
• Tray tables and seat backs in a stowed and upright position;
• Cabin baggage and other carry-on items secure in designated areas;
• As applicable, in-flight entertainment system viewing screens off and stowed;
• Galleys, service carts/trolleys and associated equipment stowed or restrained.
CAB 3.2.8 If the Operator conducts passenger flights with cabin crew, the Operator shall have
cabin crew procedures for providing passengers with instructions for appropriate action in the case of
an in-flight emergency situation.
Auditor Actions
□ Identified procedures for providing passengers with instructions for in-flight emergency
situations.
□ Interviewed responsible manager(s) in cabin operations.
□ Observed line cabin operations (focus: cabin crew procedures for providing safety instructions to
passengers).
□ Other Actions (Specify)
CAB 3.2.9 If the Operator conducts passenger flights with cabin crew, and utilizes movable carts or
trolleys for passenger service in the aircraft cabin, the Operator shall:
(i) Ensure such carts or trolleys are equipped with braking devices;
(ii) Have a process to ensure braking devices are operative;
(iii) Have procedures to ensure unserviceable carts or trolleys are withdrawn for repair or
replacement. (GM)
Auditor Actions
□ Identified means of ensuring carts/trolleys are equipped with braking devices and undergo
serviceability checks.
□ Interviewed responsible manager(s) in cabin operations.
□ Observed line cabin operations (focus: movable service carts/trolleys have operative braking
devices; procedures for withdrawal or replacement of unserviceable carts/trolleys).
□ Other Actions (Specify)
Guidance
Braking devices on service carts or trolleys would typically be checked prior to the first flight of the
day. If an operator uses external service providers for catering, the operator may delegate the
serviceability of trolleys and service carts to the caterer(s). Under such circumstances, provisions
under CAB 1.10, Outsourcing and Product Control, would be applicable.
Should a cart or trolley become unserviceable during flight (e.g. defective braking device),
procedures would typically ensure the trolley or cart is stowed and not utilized for cabin service.
Additionally, tagging or labeling procedures would be implemented to ensure an unserviceable trolley
or cart is easily identified and will be withdrawn for repair or replacement.
CAB 3.2.10 If the Operator conducts passenger flights with cabin crew, and utilizes movable carts
or trolleys for passenger service in the aircraft cabin, the Operator shall have procedures to ensure
such carts or trolleys are:
(i) Stowed during the takeoff and landing phases of flight;
(ii) Stowed when not in use;
(iii) Stowed if feasible, or secured, during an emergency situation;
(iv) Stowed if feasible, or secured, prior to or during turbulence;
(v) Attended by cabin crew all times when in use, unless the braking device is engaged. (GM)
Auditor Actions
□ Identified/Assessed procedures for stowage of carts/trolleys during
takeoff/landing/emergencies/turbulence.
□ Interviewed responsible manager(s) in cabin operations.
□ Observed line cabin operations (focus: procedures for stowage/securing of movable service
carts/trolleys).
□ Other Actions (Specify)
Guidance
The term stowed means service carts or trolleys are moved into dedicated compartments (or
sleeves) that are designed to lock such equipment in place and prevent any movement within the
cabin.
The term secured means service carts or trolleys are positioned in the cabin, typically with brakes
locked, in a manner that inhibits movement. Such action would be taken only when time constraints
or cabin conditions are such that normal stowage is not feasible.
CAB 3.2.11 (Intentionally open)
CAB 3.2.12 If the Operator conducts passenger flights with cabin crew, and utilizes aircraft with
electrical system circuit breakers that are accessible to cabin crew members, the Operator shall have
procedures that specify limitations for resetting tripped circuit breakers by cabin crew members
during flight. (GM)
Auditor Actions
□ Identified/Assessed procedures specifying limitations for resetting tripped circuit breakers by
cabin crew members during flight.
□ Interviewed responsible manager(s) in cabin operations.
□ Interviewed cabin crew members to confirm awareness of limitations for resetting tripped circuit
breakers.
□ Other Actions (Specify)
Guidance
Procedures and limitations with respect to resetting circuit breakers typically include:
• Authority to reset (normally from the PIC);
• Applicable type of equipment;
• Applicable conditions;
• Number of resets permitted.
CAB 3.3.2 If the Operator conducts passenger flights with cabin crew, and utilizes aircraft
equipped with a flight deck door, the Operator shall have policies and/or procedures that are in
accordance with requirements of the Authority and, as a minimum, define:
(i) When the flight deck door must remain locked;
(ii) The way the cabin crew notifies the flight crew in the event of suspicious activity or security
breaches in the cabin;
(iii) The way cabin crew members gain entry to the flight deck. (GM)
Auditor Actions
□ Identified/Assessed policies and/or procedures for flight deck access that are in accordance
with requirements of the Authority.
□ Interviewed responsible manager(s) in cabin operations.
□ Observed line cabin operations (focus: policies/procedures for cabin-flight crew that address
locking/use of flight deck door, cabin crew entry to flight deck).
□ Other Actions (Specify)
Guidance
The intent of this provision is to ensure the security of the flight deck by providing the flight crew and
cabin crew with complementary policies and/or procedures:
• That ensure the flight crew is notified in the event of suspicious activity or a security breach in
the cabin;
• For use by cabin crew members to gain entry to the flight deck when a lockable door is
installed.
Such policies and/or procedures define the actions necessary to address the specifications of this
provision.
Policies and/or procedures related to flight deck security are considered sensitive information and are
normally provided to relevant personnel in a manner that protects the content from unnecessary
disclosure.
CAB 3.3.3 If the Operator conducts passenger flights with cabin crew, the Operator shall have
procedures for communication and coordination between the cabin crew and flight crew to ensure a
combined and coordinated process in addressing:
(i) Passenger safety information;
(ii) Cabin readiness prior to first aircraft movement, takeoff and landing;
(iii) Arming or disarming of cabin door slides or slide rafts, if applicable;
(iv) Preparation for and an encounter with turbulence;
(v) Medical situations;
(vi) Flight or cabin crew member incapacitation;
(vii) Emergency evacuation;
(viii) Abnormal situations;
(ix) Emergency situations. (GM)
Auditor Actions
□ Identified/Assessed procedures as specified in the standard for communication and
coordination between the cabin crew and flight crew.
□ Interviewed responsible manager(s) in cabin operations.
□ Observed line cabin operations (focus: procedures for cabin-flight crew
communication/coordination to address cabin operational situations).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Sterile Flight Deck.
Communication and coordination between the flight crew and cabin crew might be verbal or non-
verbal and could be included as an integral part of specific normal, abnormal and emergency
procedures.
Procedures normally include a flight and cabin crew coordination briefing prior to each flight
addresses relevant safety subjects (e.g. sterile flight deck, security, aircraft technical issues, flight
crew incapacitation, cabin depressurization, onboard fire, emergency evacuation, forced landing or
ditching.)
Appropriate communication and coordination between the flight and cabin crews ensures cabin door
slides or slide rafts are armed prior to first movement of the aircraft.
CAB 3.3.4 If the Operator conducts passenger flights with cabin crew, the Operator shall have
procedures to ensure the cabin crew provides notification to the flight crew when a safety-related
situation has been identified. (GM)
Auditor Actions
□ Identified procedures to ensure cabin crew notification to the flight crew when a safety-related
situation has been identified.
□ Interviewed responsible manager(s) in cabin operations.
□ Observed line cabin operations (focus: cabin crew procedures for safety notifications to flight
crew).
□ Other Actions (Specify)
Guidance
Examples of safety-related situations that typically require notification to the flight deck include:
• Unruly behavior by passenger(s);
• Injury to passenger or crew member;
• Medical emergencies, use of first aid or medical equipment;
• Fire, smoke or toxic fumes in the cabin;
• Failure of any emergency system or equipment.
In general, any occurrences that could pose danger to the aircraft or its occupants would be
considered reportable to the flight deck.
Procedures typically specify certain critical phases of flight during which the cabin crew is prohibited
from initiating any communication to the flight crew (e.g. takeoff and landing).
CAB 3.3.5 If the Operator conducts passenger flights with cabin crew, the Operator should have a
policy and procedures that define and specify the requirements for standard wording, terminology,
signals and/or verbal commands used for communication between cabin crew and flight crew during
normal, abnormal and emergency situations. (GM)
Auditor Actions
□ Identified/Assessed policy and procedure for a standardized means of communication between
cabin crew and flight crew during normal, abnormal and emergency situations.
□ Interviewed responsible manager(s) in cabin operations.
□ Observed line cabin operations (focus: procedures for standardized cabin-flight crew
communication).
□ Other Action (Specify)
Guidance
The intent of this provision is that communication between cabin crew and flight crew during
abnormal and emergency situations is conducted using standardized methods of communication
identified and defined in documentation available to applicable crew members.
Guidance
A policy and associated procedures typically address the acceptance and onboard handling of
passengers that require special handling, or perhaps the refusal to board certain categories of
passengers. For example, such policy and procedures might specify:
• For intoxicated and/or abusive passengers: PIC authority to refuse carriage, order in-flight
restraint or, depending on the severity of circumstances, divert a flight to an alternate airport
for disembarkation and handover to authorities.
• For passengers with disabilities: Refusal or limitations in accordance with requirements of
the Authority; specialized equipment that would need to be available (e.g. onboard
wheelchair); onboard safety briefing as applicable to the particular passenger's disability.
• If unaccompanied children are accepted: Maximum number, minimum age, any special
arrangement while on board, specific seat allocation.
• If stretchers are accepted: Maximum number, escort requirement, associated equipment that
would need to be available.
• If passengers in custody are accepted: Maximum number, number of escort officers, specific
seat allocation.
CAB 3.4.2 If the Operator conducts passenger flights with or without cabin crew, the Operator shall
have a policy and associated procedures for addressing passengers that exhibit unruly behavior
and/or interfere with a crew member prior to or during flight. Such policy and procedures shall be in
accordance with local laws and regulations, and specify reasonable measures for ensuring
passengers obey lawful commands from the PIC and/or cabin crew for the purpose of securing the
safety of the aircraft, persons on board and their property. As a minimum, the policy and procedures
shall address:
(i) Identification of unruly behavior;
(ii) Conditions under which passengers may be denied boarding, disembarked or restrained in
accordance with the authority of the PIC;
(iii) Reporting of instances of unruly behavior. (GM)
Auditor Actions
□ Identified/Assessed the policy and associated procedures for addressing passengers that
exhibit unruly behavior and/or interfere with a crew member prior to or during flight.
□ Interviewed responsible manager(s) in cabin operations.
□ Observed line cabin operations (focus: procedures for handling of unruly passengers, crew
member interference).
□ Other Actions (Specify)
Guidance
Policy and associated procedures would typically be published to ensure awareness by all applicable
ground and flight personnel.
To ensure procedures are effective, guidelines are typically created to address all aspects of
managing unruly behavior including prevention. For example, because of the increased effect of
alcohol at altitude, guidelines would normally ensure the service of such beverages is carried out in a
reasonable and responsible manner. Additionally, passengers would typically not be permitted to
drink alcohol unless served by the cabin crew; the cabin crew would be attentive to identifying
passengers that might be consuming their own alcohol.
Additional information may be found in the IATA Guidance on Unruly Passenger Prevention and
Management (www.iata.org/cabin-safety).
CAB 3.4.3 If the Operator conducts passenger flights with cabin crew on aircraft with emergency
oxygen systems installed, the Operator shall have cabin crew procedures which ensure delivery of
oxygen to passengers, when required.
Auditor Actions
□ Auditor Actions (action steps to establish specifications are documented and implemented)
□ Identified/Assessed cabin crew procedures that ensure all passengers have ready access to
emergency oxygen.
□ Interviewed responsible manager(s) in cabin operations.
□ Observed line cabin operations (focus: procedures that ensure passengers have ready access
to emergency oxygen).
□ Other Actions (Specify)
CAB 3.4.4 If the Operator conducts passenger flights with cabin crew, the Operator shall have
cabin crew procedures that require all passengers to be seated with their seat belts (or harness or
other restraint provided) fastened:
(i) For the taxi, takeoff and landing phases of a flight;
CAB 3.4.6 If the Operator conducts passenger flights with or without cabin crew, and utilizes
aircraft that have passenger seats adjacent to cabin emergency exits, the Operator shall have
guidance and procedures to ensure passengers seated in such seats meet any applicable
requirements and restrictions.
Auditor Actions
□ Identified/Assessed guidance and procedures to ensure passengers seated in seats adjacent
to cabin emergency exits meet any applicable requirements and restrictions.
□ Observed line cabin operations (focus: procedures that address passengers seated adjacent to
emergency exits).
□ Other Actions (Specify)
CAB 3.4.7 (Intentionally open)
CAB 3.4.8 If the Operator conducts passenger flights with or without cabin crew, the Operator shall
have guidelines and associated procedures to ensure control of the use of portable electronic
devices in the passenger cabin. (GM)
Auditor Actions
□ Identified/Assessed guidelines and associated procedures to ensure control of the use of
portable electronic devices (PEDs) in the passenger cabin.
□ Interviewed responsible manager(s) in cabin operations.
□ Observed line cabin operations (focus: guidance/procedures that address control of PED
usage).
□ Other Actions (Specify)
Guidance
Some portable electronic devices might adversely affect the performance of aircraft systems or
equipment. An operator would typically have published guidelines that define relevant electronic
devices, as well as associated procedures to ensure the use of such devices is controlled.
CAB 3.4.9 (Intentionally open)
CAB 3.4.10 If the Operator conducts passenger flights with cabin crew, the Operator shall have
cabin crew procedures that ensure an announcement is made to passengers for matters related to
safety, including turbulence, normal, abnormal and emergency situations.
Auditor Actions
□ Identified procedures for announcements to passengers for situations as specified in the
standard.
□ Interviewed responsible manager(s) in cabin operations.
□ Observed line cabin operations (focus: procedures for passenger safety announcements as
applicable to the situation).
□ Other Actions (Specify)
CAB 3.4.11 If the Operator conducts passenger flights with cabin crew, the Operator shall have
guidance and associated cabin crew procedures to ensure passengers:
(i) Are informed and receive instruction on all restrictions pertaining to onboard smoking;
(ii) Comply with the Fasten Seat Belt sign and, if applicable, the No Smoking sign.
Auditor Actions
□ Identified guidance and procedures to ensure passengers are informed of all restrictions and
instructions pertaining to on onboard smoking and Fasten Seat Belt/No Smoking signs/.
□ Interviewed responsible manager(s) in cabin operations.
□ Examined documentation of guidelines, PAs, safety video & associated procedure(s).
Auditor Actions
□ Identified/Assessed policy for the acceptance of passengers needing supplementary oxygen
and if applicable, cabin crew procedures for the administration/stowing of supplementary oxygen.
□ Interviewed responsible manager(s) in cabin operations.
□ Interviewed cabin crew members to confirm awareness of the procedures for administration of
oxygen.
□ Other Actions (Specify)
Guidance
A policy would typically define whether the operator does or does not accept passengers with a pre-
existing medical condition that requires the potential need for oxygen. If such passengers are
accepted, it would be normally be necessary to have a process that permits arranging for and
boarding an adequate oxygen supply prior to a flight. Additionally, procedures would be typically
required to ensure:
• The proper administration of such oxygen by crew members when needed;
• Oxygen equipment is properly stowed when not in use or when the seat belt sign is
illuminated.
In some circumstances, if approved by the operator and the Authority, passengers may be allowed to
carry on board and utilize their own oxygen equipment.
If an operator does not accept passengers who have the need for supplementary oxygen, the policy
would clearly state such non-acceptance in order to ensure awareness among applicable passenger
handling personnel.
CAB 3.4.15 If the Operator conducts passenger flights with cabin crew, the Operator shall ensure
the immediate availability of procedures and associated checklist(s), applicable to each aircraft type,
to be used for an in-flight search or inspection to discover concealed weapons, explosives, or other
dangerous devices when sabotage or other type of unlawful interference is suspected. Such
procedures shall contain:
(i) Guidance for the course of action to be taken if a bomb or suspicious object is found;
(ii) Least risk location(s) for a bomb or explosives specific to each aircraft type, if so designated
by the manufacturer. (GM)
Auditor Actions
□ Identified/Assessed procedures the operator utilizes for onboard bomb search or security
inspection when an act of unlawful interference or sabotage is suspected.
□ Examined selected records of completion of security searches, as appropriate.
□ Interviewed responsible manager(s).
□ Other Actions (Specify)
Guidance
In order to address the need to conduct a timely search or inspection of an aircraft, a checklist or
other form of guidance (e.g. Bomb Threat Search Checklist, Aircraft Search Instructions) applicable
to each aircraft type is immediately available, either located on board the aircraft or readily accessible
through other means, for use by the cabin crew or other qualified personnel. Such checklist or
instructions assist qualified personnel in carrying out a systematic search of the flight deck and/or
cabin during flight to identify suspected or potentially dangerous devices or explosives. Instructions,
which are specific to the aircraft type, specify predetermined structurally safe locations to move, if
deemed appropriate, dangerous or potentially explosive articles. (Note: some aircraft types may not
have designated least risk locations.)
The capability to undertake a systematic search for such items on board a cargo aircraft may be
difficult due to limited access to many parts of the aircraft in flight. Opening containers and accessing
pallets of cargo in flight also may not be possible and the availability of flight crew or other trained
personnel to undertake such a search may be limited.
Applicability
Section 6 addresses functions within the scope of ground handling operations and is applicable to an
operator that conducts passenger, cargo and/or combi (combined cargo and passenger) aircraft
operations.
Individual provisions or sub-specifications within a provision that:
• Begin with a conditional phrase (“If the Operator...”) are applicable if the operator meets the
condition(s) stated in the phrase.
• Do not begin with a conditional phrase are applicable unless determined otherwise by the Auditor.
Functions within the scope of ground handling operations include:
• Passenger handling;
• Baggage handling;
• Aircraft ground handling and loading;
• Load control;
• Aircraft fueling;
• Aircraft de-/anti-icing.
In this section, non-revenue cargo is addressed in the same way as revenue cargo for the purposes of
handling loading, securing and transporting. COMAT is non-revenue cargo.
For the purpose of addressing cargo in this section, mail is considered to be an item of cargo. Therefore,
any reference to cargo also includes mail.
Where an operator outsources the performance of ground handling operational functions to external
service providers, the operator retains overall responsibility for ensuring the management of safety in the
conduct of such operations and must demonstrate processes for monitoring applicable external service
providers in accordance with GRH 1.10.2.
General Guidance
Definitions of technical terms used in this ISM Section 6, as well as the meaning of abbreviations and
acronyms, are found in the IATA Reference Manual for Audit Programs (IRM).
Processes and procedures for use in ground handling operations are defined in the IATA Ground Operations
Manual (IGOM), the IATA Airport Handling Manual (AHM), the IATA Dangerous Goods Regulations (DGR)
and in other relevant IATA publications.
GRH 1.1.2 The Operator shall have a manager for ground handling operations that:
(i) Has the authority and is responsible for the management and supervision of functions and
activities within the scope of ground handling operations;
(ii) Is accountable to senior management for ensuring the safety of ground handling operations.
(GM) ◄
Auditor Actions
□ Identified designated/nominated manager for ground handling operations.
□ Examined job description of manager for ground handling operations (focus: defines
authority/accountability/responsibility for risk management/compliance with AOC requirements).
□ Interviewed manager of ground handling operations.
□ Other Actions (Specify)
Guidance
Refer to Guidance associated with ORG 1.1.4 located in ISM Section 1.
1.3 Communication
GRH 1.3.1 The Operator shall have a communication system that enables an effective exchange of
information relevant to the conduct of ground handling operations throughout the management
system for ground handling operations and in areas where ground handling operations are
conducted. (GM) ◄
Auditor Actions
□ Identified/Assessed system(s) for communicating information relevant to operations within the
ground handling operations organization (focus: capability for communicating information
relevant to operations within the ground handling operations organization).
□ Interviewed ground handling operations manager and/or designated management
representative(s).
□ Examined examples of information communication/transfer in ground handling operations.
□ Interviewed selected non-management operational personnel in ground handling operations.
□ Other Actions (Specify)
Guidance
Refer to Guidance associated with ORG 1.4.1 located in ISM Section 1 for expanded information
regarding methods of communication.
organization either uses the OM of the operator or has its own published OM that fulfills operational
safety, security and quality requirements of the operator.
To achieve system-wide standardization, an operator would normally have a control process that
ensures external service providers have operationally relevant parts of the OM available at applicable
locations.
GRH 1.6.3 If the Operator transports dangerous goods as cargo, the Operator shall ensure a
current edition of the IATA Dangerous Goods Regulations (DGR), the ICAO Technical Instructions
for the Safe Transport of Dangerous Goods by Air (Technical Instructions) or equivalent
documentation is accessible at each location where ground handling operations involving the loading
of dangerous goods as cargo are conducted. (GM)
Auditor Actions
□ Identified/Assessed process for ensuring distribution of DGR or equivalent DG documents to all
locations where DG is handled.
□ Interviewed responsible management representative(s).
□ Traced distribution of DGR or equivalent DG documents.
□ Observed accessibility of DGR or equivalent DG documents in areas of operations where
dangerous goods are handled.
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definitions of Dangerous Goods Regulations (DGR) and Technical
Instructions.
Most dangerous goods are typically transported as cargo. However, certain types of dangerous
goods are permitted for transport in passenger or crew baggage. The specifications in this provision
are applicable to an operator that transports dangerous goods as cargo.
Acceptable equivalent documentation would typically contain information derived from the DGR or
Technical Instructions, as well as the dangerous goods policies and procedures specific to the
type(s) of operations being conducted at the location.
GRH 1.6.4 If the Operator transports dangerous goods as cargo, the Operator shall ensure the OM
or an equivalent operational manual contains information that will permit ground handling personnel
to carry out duties and responsibilities with respect to dangerous goods. Such information shall
include, as a minimum:
(i) Action to be taken in the event of emergencies involving dangerous goods;
(ii) Details of the location and identification of cargo holds;
(iii) The maximum quantity of dry ice permitted in each compartment;
(iv) If radioactive material is transported, instructions for the loading of such dangerous goods in
accordance with applicable requirements. (GM)
Auditor Actions
□ Identified/Assessed information in the OM or equivalent document that permits personnel to
carry out duties and responsibilities relevant to dangerous goods handling.
□ Interviewed responsible management representative(s).
□ Interviewed personnel that perform operational functions in ground handling operations.
□ Observed accessibility of DG information on key cargo (dry ice and radioactive material) in
selected areas of operations where personnel carry out dangerous goods handling.
□ Other Actions (Specify)
Guidance
Refer to IGOM 6.4 for guidance that addresses response to dangerous goods events.
Guidance may be found in DGR 9.5 and 10.9.
GRH 1.6.5 If the Operator does not transport dangerous goods, the Operator shall ensure the OM
contains the policies and associated guidance necessary to prevent dangerous goods from being
inadvertently carried or loaded onto the aircraft. (GM)
Auditor Actions
□ Identified/Assessed policies and guidance in the ground handling OM or equivalent manual
necessary to ensure personnel do not inadvertently permit acceptance or transport of dangerous
goods.
□ Interviewed responsible management representative(s).
□ Interviewed personnel that perform operational functions in ground handling operations.
□ Observed availability of policies and guidance that ensures personnel do not inadvertently
permit dangerous goods to be carried or loaded onto the aircraft.
□ Other Actions (Specify)
Guidance
For a dangerous goods “no-carry” operator, guidance in the OM typically addresses vigilance with
respect to hidden or inconspicuous dangerous goods, and includes an indicative list of items that
could contain dangerous goods. Such guidance also typically addresses dangerous goods permitted
in passenger baggage in accordance with operator policy and procedures.
GRH 1.6.6 If the Operator conducts passenger flights, the Operator shall ensure a current edition
of the IATA Dangerous Goods Regulations (DGR), the ICAO Technical Instructions for the Safe
Transport of Dangerous Goods by Air (Technical Instructions) or equivalent documentation is
accessible at locations where passenger check-in and/or boarding operations are conducted. (GM)
Auditor Actions
□ Identified/Assessed process for ensuring distribution of DGR or equivalent DG documents to all
locations where passenger check-in and/or boarding are conducted.
□ Interviewed responsible management representative(s).
□ Traced distribution of DGR or equivalent DG documents to areas where passenger check-in
and/or boarding operations are conducted.
□ Observed accessibility of DGR or equivalent DG documents in areas of operations where
passenger handling operations are conducted.
□ Other Actions (Specify)
Guidance
Most dangerous goods are typically transported as cargo. However, certain types of dangerous
goods are permitted for transport in passenger or crew baggage.
Acceptable equivalent documentation would typically contain information derived from the DGR or
Technical Instructions, as well as the dangerous goods policies and procedures specific to the
type(s) of operations being conducted at the location. For example, at the passenger check-in and
aircraft boarding areas, appropriate company documentation might describe dangerous goods
permitted in passenger and crew baggage. Documentation may also include actions required by
passenger agents with respect to items specifically not permitted in passenger baggage, and contain
examples of dangerous goods hazard labels and procedures for addressing spills and/or leaks of
unidentified substances.
To ensure system-wide standardization, an operator would normally have a control process to
ensure external service providers have the DGR or equivalent documentation available at applicable
locations.
GRH 1.6.7 If the Operator conducts passenger flights, the Operator shall ensure the OM or an
equivalent operational manual contains information that will permit ground handling personnel to
carry out duties and responsibilities with respect to dangerous goods. As a minimum, such
information shall include procedures to alert passengers that certain items of dangerous goods:
(i) Are specifically prohibited in hold baggage;
(ii) Must be removed from cabin baggage when cabin baggage is transported as hold baggage.
(GM)
Auditor Actions
□ Identified/Assessed information in the ground handling OM relevant to personnel alerting
passengers of dangerous goods restrictions and prohibitions.
□ Interviewed responsible management representative(s).
□ Observed personnel advising passengers of DG limits in ground handling operations.
□ Other Actions (Specify)
Guidance
Refer to IGOM 2.5.7 for guidance that addresses dangerous goods in baggage.
GRH 1.6.8 If the Operator conducts passenger flights, the Operator should ensure the OM or an
equivalent operational manual contains information with respect to dangerous goods permitted in
passenger and crew baggage. (GM)
Auditor Actions
□ Identified/Assessed information in the ground handling OM relevant to dangerous goods
permitted in passenger and crew baggage.
□ Interviewed responsible management representative(s).
□ Interviewed line flight and cabin crew members.
□ Other Actions (Specify)
Guidance
Certain items of dangerous goods are permitted in passenger or crew baggage if approved by the
operator. Information contained in the operations manual (or equivalent) would typically address the
following:
• Approval process
It is recommended that a single company policy be set out that identifies the items that have
been approved and the person(s) or department(s) responsible for determining how
dangerous goods in passenger baggage may be approved.
• Communication
It is recommended that the operator define how approvals for dangerous goods requiring
operator approval are communicated to the airport(s) of departure. It is recommended that
operators consider a process where such approval is included in the passenger electronic
record.
• Limitations
The operator manuals should specify any limitations or procedural requirements that may
apply to particular commodities (e.g. inspection at check-in by passenger service agents
and/or security).
• Codeshare
Where the operator has interline agreements with code share and/or alliance partners the
operator should identify what the procedure is for obtaining the approval of the other
airline(s) involved (e.g. by advising the passenger that they must obtain approval from the
other operator).
• Awareness
The operator should ensure that all staff who have an interaction with passengers, (i.e.
reservations agents, passenger service agents, cabin crew and flight crew) are made aware
of the process employed to ensure that the operator approval process remains effective.
Refer to DGR 2.3, which addresses dangerous goods permitted in passenger and crew checked and
cabin baggage.
Refer to IGOM 2.5 for guidance that addresses the carriage of dangerous goods by passengers.
GRH 1.6.9 The Operator should ensure the processes and procedures contained in the OM for the
conduct of ground handling operations are, as a minimum, equivalent to processes and procedures
contained in the IGOM. (GM)
Auditor Actions
□ Identified/Assessed ground handling OM (focus: includes processes/procedures as specified in
the IGOM).
□ Interviewed responsible ground handling management representative(s).
□ Examined selected sections or parts of the ground handling OM (focus: processes/procedures
used by ground handling personnel are equivalent to those specified in the IGOM).
□ Other Actions (Specify)
Guidance
As a best practice, an operator would typically conduct a gap analysis of its OM processes and
procedures to identify the level of equivalency with those in the IGOM.
Processes/procedures in the IGOM have been developed based on industry-accepted practices that
generally provide an acceptable level of safety risk in the conduct of ground handling operations.
Auditor Actions
□ Identified/Assessed management and control system for operational records in ground
handling operations (focus: system defines schedule for periodic file backup).
□ Interviewed responsible management representative(s).
□ Examined record(s) of back-up files for electronic records.
□ Other Actions (Specify)
Guidance
Refer to Guidance associated with ORG 2.2.2 located in ISM Section 1.
Auditor Actions
□ Identified/Assessed process for addressing audit findings within ground handling operations.
□ Interviewed responsible quality assurance program manager.
□ Examined selected audit reports/records (focus: identification of root cause,
development/implementation of corrective action, follow-up to evaluate effectiveness).
□ Other Actions (Specify)
Guidance
Refer to Guidance associated with ORG 3.4.3 located in ISM Section 1.
GRH 1.9.3 The Operator shall have a process to ensure significant issues arising from audits of
functions within the scope of ground handling operations are subject to management review in
accordance with ORG 1.5.1 and, as applicable, ORG 1.5.2. [SMS] (GM) ◄
Auditor Actions
□ Identified/Assessed process for management review of ground handling operations issues
(focus: continual improvement of quality assurance program).
□ Interviewed responsible quality assurance program manager.
□ Examined selected records/documents of management review of ground handling operations
quality assurance program issues (focus: specific issues/changes identified and implemented to
improve quality assurance program).
□ Other Actions (Specify)
Guidance
Refer to Guidance associated with ORG 3.4.4 located in ISM Section 1.
GRH 1.9.4 The Operator shall have an audit planning process and sufficient resources to ensure
audits of ground handling operations are:
(i) Scheduled at intervals to meet regulatory and management system requirements;
(ii) Completed within a specified time period. (GM) ◄
Auditor Actions
□ Identified/Assessed planning process for quality assurance auditing of ground handling
operations (focus: audits planned/scheduled/completed in order to meet applicable
internal/external requirements).
□ Identified/Assessed audit resources (focus: availability of sufficient auditors/other resources to
accomplish audit plan).
□ Interviewed quality assurance program manager.
□ Crosschecked audit plan with selected audit reports, to verify adherence to plan (focus: audits
conducted in accordance with audit plan).
□ Other Actions (Specify)
Guidance
Refer to Guidance associated with ORG 3.4.10 located in ISM Section 1.
Auditor Actions
□ Identified/Assessed processes for contract/agreement production/execution with external
service providers of ground handling operational functions.
□ Interviewed responsible manager(s) in ground handling operations.
□ Examined selected ground handling operations outsourcing contracts/agreements (focus:
inclusion of measurable specifications applicable to external service providers).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definitions of Operational Function (Aircraft Operations) and Outsourcing.
The requirement for a contract or agreement applies to outsourced ground handling functions that
affect the safety and security of operations, including routine aircraft servicing (e.g. potable water)
and special functions such as aircraft fueling and de-/anti-icing.
If a ground handling function is expected to be accomplished in accordance with specific industry
standards, the agreement would normally identify and specify the standards by exact name (e.g.
aircraft fuel shall be delivered in accordance with the standards adopted by the IATA Fuel Quality
Pool).
The AHM contains detailed guidance as well as the standard ground handling agreement (SGHA)
and a service level agreement. Additionally, IATA publishes a standard contract for the delivery of
aircraft fuel.
Refer to Guidance associated with ORG 3.5.1 located in ISM Section 1.
GRH 1.10.2 If the Operator has external service providers conduct outsourced ground handling
operational functions, the Operator shall have processes to monitor such external service providers
to ensure ground handling safety and security requirements are being fulfilled. (GM) ◄
Auditor Actions
□ Identified/Assessed processes used for monitoring external ground handling service providers
(focus: monitoring process ensures provider fulfils applicable safety/security requirements).
□ Interviewed responsible manager(s) in ground handling operations.
□ Examined selected records/reports resulting from monitoring of ground handling operations
service providers (focus: monitoring process ensures provider fulfils applicable safety/security
requirements).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of ISAGO.
Refer to Guidance associated with ORG 3.5.2 located in ISM Section 1.
An external service provider that is on the ISAGO (IATA Safety Audit of Ground Operations) Registry
for a particular station indicates such provider has been audited and is in conformity with ISAGO
standards. The use of the ISAGO program is an acceptable method for certain elements of the
monitoring processes. These elements must be within the scope of the ISAGO Standards Manual
(GOSM).
Other inspection programs that might be considered for use as part of the monitoring of service
providers include, as applicable, the IATA De-Icing/Anti-Icing Quality Control Pool (DAQCP), the
IATA Fuel Quality Pool (IFQP) and the IATA Drinking-Water Quality Pool (IDQP).
GRH 1.10.3 If the Operator has external service providers conduct outsourced ground handling
operational functions, the Operator should ensure auditing is included as a process for the monitoring
of external service providers in accordance with GRH 1.10.2. (GM) ◄
Auditor Actions
□ Identified/Assessed auditing processes used for monitoring external ground handling service
providers.
□ Interviewed responsible manager(s) in ground handling operations.
□ Examined selected reports of audits performed on external ground handling service providers.
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of GOSARPs.
Refer to Guidance associated with ORG 3.5.3 located in ISM Section 1.
An acceptable method of auditing external service providers is the utilization of all, or part of the
ISAGO Standards and Recommended Practices (GOSARPs) as applicable to the scope of the audit
and the functions performed by the external service provider.
Participation in the ISAGO audit pool is an acceptable method for utilization of the GOSARPs and
associated checklists for the audit of external service providers in accordance with GRH 1.10.2.
Refer to the Introduction of the ISAGO Standards Manual (GOSM) for guidance that addresses use
of the GOSARPs and associated checklists.
GRH 1.10.4 The Operator should have a process to ensure products purchased or otherwise
acquired from an external vendor or supplier, which directly affect operational safety or security, meet
the product technical requirements specified by the Operator prior to being used in the conduct of
ground handling operations. (GM) ◄
Auditor Actions
□ Identified/Assessed acceptance processes for ensuring acquired products used in ground
handling operations meet technical requirements.
□ Interviewed responsible manager(s) in ground handling operations.
□ Examined selected product acceptance records (focus: products meet ground handling
operations technical requirements).
□ Other Actions (Specify).
Guidance
Refer to Guidance associated with ORG 3.6.1 located in ISM Section 1.
Operational Reporting
GRH 1.11.3 The Operator shall have an operational safety reporting system for ground handling
operations that:
(i) Encourages and facilitates ground handling operations personnel to submit reports that
identify safety hazards, expose safety deficiencies and raise safety concerns;
(ii) Requires reporting of events that result in aircraft ground damage;
(iii) Includes analysis and ground handling operations management action to address
operational deficiencies, hazards, incidents and concerns identified through the reporting
system. [SMS] (GM) ◄
Auditor Actions
□ Identified/Assessed operational safety reporting system in ground handling operations (focus:
system urges/facilitates reporting of hazards/safety concerns; includes analysis/action to
validate/address reported hazards/safety concerns).
□ Interviewed responsible manager(s) in ground handling operations.
□ Interviewed person(s) that perform operational safety report review/analysis/follow-up in ground
handling operations.
□ Examined data that confirm an effective ground handling operations safety reporting system
(focus: quantity of reports submitted/hazards identified).
□ Examined records of selected ground handling operations safety reports (focus: analysis/follow-
up to identify and address reported hazards/safety concerns).
□ Other Actions (Specify).
Guidance
Safety reporting is a key aspect of SMS hazard identification and risk management.
To enhance industry data usability, it is recommended that ground damage events are reported in
accordance with a formal reporting structure (see GRH 1.11.6).
Refer to IGOM 6.4 for guidance that addresses aircraft damage reporting.
Refer to Guidance associated with ORG 3.1.3 located in ISM Section 1.
GRH 1.11.4 The Operator should have a confidential safety reporting system that encourages and
facilitates the reporting of events, hazards and/or concerns resulting from or associated with human
performance in ground handling operations. (GM) ◄
Auditor Actions
□ Identified/Assessed confidential safety reporting system in ground handling operations (focus:
system urges/facilitates reporting of events/hazards/safety concerns caused by humans;
report/reporters are de-identified; includes analysis/action to validate/address reported
hazards/safety concerns).
□ Interviewed responsible manager(s) in ground handling operations.
□ Examined records of selected ground handling operations confidential safety reports (focus:
report/reporter de-identification; analysis/follow-up to identify/address reported hazards/safety
concerns).
□ Other Actions (Specify)
Guidance
Refer to Guidance associated with ORG 3.1.4 located in ISM Section 1.
reduction) over a period of time (e.g. one year). Achievement of the target (or objective) would
represent an improvement in the operational performance. The use of performance measures is an
effective method to determine if desired safety outcomes are being achieved, and to focus attention
on the performance of the organization in managing operational risks and maintaining compliance
with relevant regulatory requirements.
Performance measures in ground handling operations might address, for example, different types of
aircraft ground damage.
Refer to Guidance associated with ORG 3.2.1A located in ISM Section 1.
GRH 1.11.6 The Operator should have a process to ensure aircraft ground damages are reported
to IATA for inclusion in the Ground Damage Database (GDDB). Such reports should be submitted in
accordance with the formal IATA ground damage reporting structure. (GM)
Auditor Actions
□ Identified/Assessed process for reporting ground damages to IATA for inclusion in GDDB.
□ Interviewed responsible manager(s) in ground handling operations.
□ Examined selected reports of ground damage submitted to IATA using forms from
www.iata.org/gddb.
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of IATA Ground Damage Database (GDDB).
The IATA GDDB has been established as a quality source of defensible data that will support a
performance-based approach to the management of ground handling operations. Data submitted to
IATA for the GDDB is assembled and integrated in a manner that permits, through statistical
analysis, the identification of trends and contributing factors associated with aircraft ground
damages.
Participants that submit data for the GDDB benefit from having access to the analytical results. As a
key component of IATA's Integrated Solution for Ground Operations, such results are used by
various IATA working groups and task forces associated with the Ground Operations and ISAGO
programs, and form the basis for the development of damage prevention strategies and success
measurement metrics.
The assurance of data quality and overall database integrity requires that data is submitted by
participants in a uniform and consistent manner. Therefore, the GDDB includes strict reporting
protocols, including associated definitions and assumptions.
Reporting guidelines and other information can be found online at the IATA Ground Damage
Database page (http://www.iata.org/gddb).
Auditor Actions
□ Identified/Assessed training program for ground handling personnel (focus: ensures completion
of initial/recurrent training for personnel in all ground handling functions; includes processes that
ensure personnel of external service providers complete initial/recurrent training).
□ Interviewed responsible manager(s) in ground handling operations.
□ Examined selected initial/recurrent course curricula/syllabi (focus: includes initial and recurrent
training programs for all personnel that perform ground handling duties/functions).
□ Examined initial and recurrent training records of selected personnel (focus: completion of initial
and recurrent training).
□ Other Actions (Specify).
Guidance
Refer to the Applicability box at the beginning of this section for the functions within the scope of
ground handling operations.
Requirements for initial and recurrent training apply to all personnel that perform duties within the
scope of ground handling operations for the operator, both at the main base and at all other locations.
GRH 2.1.2 The Operator shall have a process to ensure the training programs completed by
ground handling operations personnel in accordance with GRH 2.1.1 provide the knowledge
necessary to perform duties, execute procedures and operate the equipment associated with specific
ground handling functions and responsibilities. Such programs shall include:
(i) Familiarization training on applicable regulations;
(ii) In-depth training on requirements, including policies, procedures and operating practices;
(iii) Training in human factors principles;
(iv) Safety training on associated operational hazards. (GM)
Auditor Actions
□ Identified/Assessed training programs for ground handling operations personnel (focus:
includes programs for personnel in all ground handling operations functions).
□ Interviewed responsible manager(s) in ground handling operations.
□ Examined selected training program records/documents (focus: programs include all specified
training areas as applicable to ground handling operations functions).
□ Other Actions (Specify).
Guidance
Refer to the IRM for the definition of Human Factors Principles.
The AHM contains guidance for the training of ground handling personnel.
Refer to AHM 590, 591 and DGR 1.5, which address dangerous goods training for personnel that
perform load control functions.
Refer to Table 6.1, which contains specifications that define typical safety training for ground
handling personnel.
GRH 2.1.3 The Operator shall have a process to ensure training for personnel that perform
operational duties in functions within the scope of ground handling operations for the Operator:
(i) Includes testing or evaluation by written, oral or practical means, as applicable;
(ii) Requires a demonstration of adequate knowledge, competency and proficiency to perform
duties, execute procedures and/or operate equipment. (GM)
Auditor Actions
□ Identified/Assessed training programs for ground handling operations personnel (focus:
programs include a process for testing/evaluations/demonstrations as specified).
□ Interviewed responsible manager(s) in ground handling operations.
□ Examined selected initial/recurrent course curricula/syllabi (focus: initial and recurrent training
programs include testing/evaluations/demonstrations).
□ Examined initial/recurrent training records of selected personnel (focus:
testing/evaluations/demonstrations as specified completed during initial and recurrent training).
□ Other Actions (Specify).
Guidance
Training is usually divided into theoretical and practical parts, both of which normally include a record
of an evaluation and successful completion of training.
An assessment of knowledge gained from the theoretical part of training is normally accomplished
through use of written or computer-based testing.
Practical training typically includes an on-the-job training phase followed by a demonstration of
competence in the skills that are relevant to the specific ground handling function.
An oral means of assessment may be included as an element of the evaluation included in the
theoretical and/or practical parts of training, but would typically not be used as the sole method of
evaluation.
Records of evaluations for both theoretical and practical training are normally retained to verify
currency in accordance with training program requirements.
GRH 2.1.4 The Operator shall have a process to ensure completion of required training by
personnel that perform operational duties in functions within the scope of ground handling operations
for the Operator is recorded and such records are retained in accordance with GRH 1.7.1.
Auditor Actions
□ Identified/Assessed ground handling operations records system (focus: system includes
training records of personnel that perform ground handling operations duties).
□ Interviewed responsible manager(s) in ground handling operations.
□ Examined initial/recurrent training records of selected personnel (focus: records include
completion of required training).
□ Other Actions (Specify).
GRH 2.1.5 The Operator shall have a process to ensure the training programs completed by
ground handling operations personnel in accordance with GRH 2.1.1 are reviewed and updated to
remain relevant and current.
Auditor Actions
□ Identified/Assessed process for review and update of training programs completed by ground
handling operations personnel.
□ Interviewed responsible manager(s) in ground handling operations.
□ Examined selected training program records/documents (focus: programs have been
periodically reviewed and updated).
□ Other Actions (Specify).
□ Examined training records of selected personnel with applicable operational ground handling
duties.
□ Other Actions (Specify)
Guidance
When an operator does not transport dangerous goods as cargo (i.e. a “no-carry” operator),
dangerous goods training is still required for ground handling personnel to ensure prohibited
dangerous goods are recognized and are not loaded onto an aircraft.
Dangerous goods training would be structured to provide the requisite knowledge to permit ground
handling personnel to recognize prohibited dangerous goods (whether labeled or not labeled),
ensure such dangerous goods are not inadvertently loaded on an aircraft and apply emergency
action in the event of contamination or a spill. The curriculum for dangerous goods training for ground
handling personnel will typically address:
• General philosophy;
• Limitations;
• Labeling and marking;
• Recognition of undeclared dangerous goods;
• Provisions for passengers and crew;
• Emergency procedures.
Refer to DGR 1.5 (Table 1.5.B, Minimum Requirements for Training Curricula for “No-carry”
Operators), for detailed guidance that addresses dangerous goods training and subjects applicable
to specific ground handling functions.
GRH 2.2.3 The Operator shall have a process to ensure initial and recurrent training completed by
applicable ground handling personnel in accordance with GRH 2.1.1 addresses the following areas
of operations, as applicable to ground handling duties or function(s) performed:
(i) Airside Driving;
(ii) Load control;
(iii) Passenger Handling;
(iv) Baggage handling;
(v) Aircraft Handling and Loading;
(vi) Passenger Boarding Bridge;
(vii) Aircraft Loading Supervision;
(viii) Aircraft Ground Movement;
(ix) Cargo and Mail handling;
(x) Fueling Operations;
(xi) De/Anti-Icing Operations;
(xii) Other areas of operations as specified by the Operator.
Auditor Actions
□ Identified/Assessed training program for ground handling personnel (focus: training program
addresses all specified operational areas).
□ Interviewed responsible manager(s) in ground handling operations.
□ Examined selected initial/recurrent training curricula/syllabi (focus: training addresses all
specified operational areas.
□ Examined selected initial and recurrent training records (focus: personnel have completed
training in operational areas applicable to individual duties/functions performed).
□ Other Actions (Specify)
GRH 2.2.4 The Operator should have a process to ensure training for ground handling personnel in
operational areas as specified in GRH 2.2.3 includes elements that address specific ground handling
functions in accordance with the following:
(i) Airside driving as specified in Table 6.2;
(ii) Load control as specified in Table 6.3;
(iii) Passenger handling as specified in Table 6.4;
(iv) Baggage handling as specified in Table 6.5;
(v) Aircraft handling and loading as specified in Table 6.6;
(vi) Passenger boarding bridge operation as specified in Table 6.7;
(vii) Aircraft loading supervision as specified in Table 6.8;
(viii) Aircraft ground movement as specified in Table 6.9;
(ix) Aircraft fueling as specified in Table 6.10;
(x) Aircraft de/anti-icing as specified in Table 6.11;
(xi) Other operational ground handling functions as specified by the Operator. (GM)
Auditor Actions
□ Identified/Assessed training program for ground handling personnel (focus: training addresses
operational functions as specified).
□ Interviewed responsible manager(s) in ground handling operations.
□ Examined selected initial/recurrent training curricula/syllabi (focus: training addresses specific
operational functions).
□ Examined selected initial and recurrent training records (focus: personnel have completed
training in operational functions performed).
□ Other Actions (Specify)
Guidance
Subject areas specified in the tables are typical for training that addresses the various types of
operational functions.
Personnel assigned to perform ground handling duties as defined by the operator may have different
roles and/or functions that can be any combination of the functions specified in the provision.
Guidance
Refer to the IRM for the definition of Operational Function (Aircraft Operations).
SMS training is an element of the Safety Promotion component of the SMS framework.
Refer to Guidance associated with ORG 1.6.5 located in ISM Section 1.
GRH 3.1.2 If the Operator conducts passenger flights, the Operator shall ensure a process is in
place that requires, when dangerous goods not permitted for carriage on board the aircraft are
discovered on the person of or in the baggage of a passenger, a report is made to the appropriate
authority of the state of occurrence. (GM)
Note: The specifications of this provision are applicable to operators that transport, and also to
operators that do not transport, dangerous goods as cargo.
Auditor Actions
□ Identified/Assessed a process to report discovery of prohibited dangerous goods on the person
of or in the baggage of a passenger to the applicable authority.
□ Interviewed responsible manager(s) in ground handling operations
□ Observed passenger/baggage handling operations (focus: process for reporting cases of
prohibited dangerous goods found in the possession of passengers).
□ Other Actions (Specify)
Guidance
Guidance may be found in DGR 2.3 and 9.6.2, and in IGOM 2.5.7.
GRH 3.1.3 – 3.1.4 (Intentionally open)
GRH 3.1.5 If the Operator transports passengers that require special handling, the Operator shall
have a policy and associated procedures for the preflight acceptance and handling of such
passengers by ground passenger handling personnel. Such policy and procedures shall be in
accordance with applicable regulations and, as a minimum, address:
(i) Unruly passengers;
(ii) Passengers with disabilities or reduced mobility;
(iii) Passengers with injuries or illness;
(iv) Infants and unaccompanied children;
(v) Inadmissible passengers;
(vi) Deportees;
(vii) Passengers in custody. (GM)
Auditor Actions
□ Identified/Assessed policy and procedures for passengers requiring the listed categories of
special handling.
□ Interviewed responsible manager(s) in ground handling operations
□ Sampled records of specific cases of handling special needs passengers.
□ Observed passenger/baggage handling operations (focus: policy/procedures for preflight
acceptance of passengers that require special handling).
□ Other Actions (Specify)
Guidance
A policy and associated procedures typically address the acceptance and pre-boarding handling of
passengers that require special handling, or perhaps the refusal to accept certain categories of
passengers. For example, such policy and procedures might include or address the following:
• For intoxicated and/or abusive passengers: Refusal to accept at check-in and, upon
discovery after check-in, refusal to board the aircraft.
• For passengers with disabilities: Acceptance and/or limitations for such acceptance in
accordance with applicable regulations, ground handling and, as applicable, specialized
equipment considerations.
• If unaccompanied children are accepted: Maximum number, minimum age, any special
arrangements once on board, specific seat allocation, ground handling considerations.
• If stretchers are accepted: Maximum number, escort requirement, associated equipment that
would need to be available, ground handling considerations.
• If passengers in custody are accepted: Maximum number, number of escort officers, specific
seat allocation, ground handling considerations.
Refer to IGOM 1.4.
Auditor Actions
□ Identified/Assessed requirement for implementation of safety procedures during
arrival/departure aircraft ground movement operations.
□ Interviewed responsible manager(s) in ground handling operations.
□ Observed aircraft ground handling operations (focus: implementation of safety procedures for
arrival/departure aircraft ground movement operations).
□ Other Actions (Specify)
Guidance
Aircraft ground movement safety procedures typically address:
• Signals used between ground personnel and the flight crew;
• Verbal phraseology used between ground personnel and the flight crew;
• Standard operating procedures in accordance with recommendations of the aircraft
manufacturer(s) for aircraft pushback, power back, power out and/or tow-out, as applicable,
for departure from the parking position, and for aircraft power-in and/or tow-in, as applicable,
for arrival into the parking position.
Refer to IGOM Chapter 4 for safety procedures used in aircraft ground movement operations.
Additional guidance may be found in AHM 4.6.3.
GRH 3.2.4 The Operator shall ensure procedures are in place for an inspection of the aircraft
exterior and adjacent airside areas as appropriate prior to aircraft arrival and departure ground
movement operations. (GM)
Auditor Actions
□ Identified/Assessed inspection procedures for aircraft/adjacent airside areas prior to aircraft
arrival/departure ground movement operations.
□ Interviewed responsible manager(s) in ground handling operations.
□ Examined selected quality control inspection reports (focus: aircraft ground damage prevention).
□ Observed aircraft ground handling operations (focus: aircraft/adjacent airside areas inspected
prior to arrival/departure aircraft ground movement operations).
□ Other Actions (Specify)
Guidance
Inspection procedures typically ensure:
• Surface condition of the apron is adequate to conduct aircraft movement operations;
• The apron is clear of items that might cause aircraft FOD;
• Aircraft servicing doors and panels are closed and secure (departure);
• Power cables and loading bridge are detached (departure);
• Equipment and vehicles are positioned clear of the aircraft movement path;
• Adequate clearance exists between the aircraft and facilities or fixed obstacles along the
aircraft movement path;
• Chocks are removed from all wheels (departure).
Refer to IGOM 4.9.1, 4.9.2, 4.12.3 and 4.12.5 for aircraft exterior and adjacent airside inspection
procedures. Additional guidance may be found in AHM 4.6.3.
GRH 3.2.5 The Operator shall ensure procedures are in place for an inspection of the aircraft
immediately prior to departure for the purpose of identifying, documenting and, as applicable,
reporting external aircraft damage. (GM)
Auditor Actions
□ Identified/Assessed procedures for aircraft inspection immediately prior to departure for the
purpose of identifying/documenting/reporting external aircraft damage.
□ Interviewed responsible manager(s) in ground handling operations.
□ Examined selected quality control inspection reports (focus: aircraft inspection for external
aircraft damage and any damage reports).
□ Observed aircraft ground handling operations (focus: aircraft inspected immediately prior to
departure to identify external ground damage).
□ Other Actions (Specify)
Guidance
To enhance the possibility of identifying all aircraft ground damage, such inspection typically takes
place after most ground handling activities have been completed and at a point just prior to the time
aircraft movement will commence for departure.
External damage deemed to have the potential to compromise the airworthiness of an aircraft
normally would be reported to appropriately qualified maintenance personnel for evaluation and
action, as appropriate.
Refer to IGOM 4.12.5.1 for aircraft pre-departure ground inspection procedures.
GRH 3.2.6 The Operator should have procedures for the opening and closing of aircraft cabin
access doors, which require that GSE or a passenger boarding bridge:
(i) Is positioned at a cabin access door prior to door opening;
(ii) Remains positioned at a cabin access door at all times when such door is open unless an
appropriate fall prevention device is placed across the open door;
(iii) Is removed from a cabin access door immediately after such door is closed. (GM)
Note: The specifications of this provision do not apply to cabin access doors that have integral
airstairs when such doors are open and the integral airstairs are deployed.
Auditor Actions
□ Identified/Assessed procedures for opening/closing of aircraft cabin access doors.
□ Interviewed responsible manager(s) in ground handling operations.
□ Observed aircraft ground handling operations (focus: door opening/closing procedures that
require GSE positioned outside open cabin access door).
□ Other Actions (Specify)
Guidance
Some aircraft types with certain galley configurations require the cabin door to be opened in order to
service the trash bins. For these aircraft, it is allowable to partially open the cabin door (i.e. “crack”
the door) in order to provide sufficient space to allow the servicing of the trash bin. However, the
cabin door is not fully swung open. Once the trash bin service is completed, the cabin door should
then be immediately closed and secured.
GSE or a passenger boarding bridge should not to be removed from a position at an aircraft cabin
access door until either:
• The door has been closed and secured by an authorized person, or
• An appropriate fall prevention device has been placed across an open door.
If an aircraft cabin access door is fitted with integral airstairs, and such airstairs are deployed and in
use, then this provision is not applicable. However, if a cabin access door is equipped with
retractable integral airstairs (e.g. B737), and such airstairs remain retracted when the door is open,
then this provision is applicable.
An appropriate fall prevention device consists of equipment or material, or a combination of both, that
is designed to arrest or prevent the fall of a person from an open door. Examples include an industrial
safety net, catch platform or safety harness system (other than a travel restraint system). The door
strap installed in most aircraft cabin doors is not considered an appropriate fall prevention device.
Guidance
Refer to the IRM for the abbreviations DCS (Departure Control System), DOI (Dry Operating Index)
and DOW (Dry Operating Weight).
The generation of the balance chart (operational limits) is normally accomplished in accordance with
methods defined by the manufacturer’s Weight and Balance Manual or equivalent document, which,
as applicable, is approved by the local authority. Such activity is usually performed by Flight
Operations or Ground Operations, or a combination thereof.
The process for producing weight and balance data and related documentation typically ensures that
weight and balance limits are respected both in normal and in special conditions.
The following are some examples of special conditions:
• Operations with fuel pumps inoperative (MEL);
• Fuel carried as ballast;
• Flight conducted with nonstandard aircraft configuration, nonstandard passenger weights or
other nonstandard conditions;
• Flight operations with one or more cabin doors inoperative that results in passenger
distribution curtailment (MEL).
To ensure aircraft weight and balance data are current and accurate, an operator typically performs
periodic aircraft weighing as recommended by the aircraft manufacturer and approved by the local
authority.
Additionally, an operator would continuously monitor any aircraft weight and balance variations that
result from individual aircraft maintenance activities or modifications (usually accomplished in
accordance with operational bulletins or other similar directives) that change the basic weight and
balance reference data as per tolerances and procedures established and accepted by local
authorities (normally identified as DOW/DOI).
This above monitoring activity is usually performed by flight operations or maintenance operations, or
a combination thereof.
Weight and balance data is typically maintained and updated via the DCS, to include remote central
load control (CLC) or any other available means, and then communicated in a timely manner.
Guidance may be found in AHM 565 (EDP system semi-permanent data exchange) and AHM 562.
GRH 3.3.3 If the Operator conducts passenger flights, the Operator should ensure procedures are
in place within the Load Control system to identify and address passenger loads that do not comply
with conventional aircraft loading weight allowances. (GM)
Auditor Actions
□ Identified/Assessed load control procedure(s) to identify/address passenger loads that do not
comply with conventional aircraft loading weight allowances.
□ Interviewed responsible manager(s) in load control operations.
□ Examined records that confirm application of other than normal/conventional weight allowances.
□ Observed load control operations (focus: load control system includes procedures to
identify/addresses passenger loads outside conventional aircraft load allowances).
□ Other Actions (Specify)
Guidance
Certain passenger groups may fall outside weight allowances (e.g. sports teams, children) normally
applied for weight and balance calculation. Adequate procedures within the system would identify
and account for such load situations to ensure accuracy in aircraft load calculations.
Refer to IGOM 1.4.3.3 for guidance that addresses non-standard passenger loads. Additional
guidance may be found in AHM 531.
GRH 3.3.4 If the Operator transports dangerous goods as cargo, the Operator shall ensure a
process is in place to provide the pilot-in-command (PIC), as soon as practicable prior to departure of
the aircraft, with accurate and legible written information pertaining to dangerous goods on board the
aircraft to be transported as cargo. Such notification shall include the following:
(i) If applicable, Air Waybill number;
(ii) Proper shipping name and/or UN/ID number;
(iii) Class or division, and subsidiary risk(s) corresponding to the label(s) applied, and for
Class 1, the compatibility group;
(iv) If applicable, packing group;
(v) For non-radioactive material, number of packages, exact loading location and, as required,
net quantity or, if applicable, gross weight of each package, except:
(a) For UN 1845: carbon dioxide, solid (dry ice), UN number, proper shipping name,
classification, total quantity in each aircraft hold and offload airport;
(b) For UN 3480 (Lithium ion batteries) and UN 3090 (lithium metal batteries), only the
UN number, proper shipping name, class, total quantity at each loading location,
and whether the package must be carried on a cargo only aircraft need be provided.
UN 3480 (Lithium ion batteries) and UN 3090 (lithium metal batteries) carried under
a State exemption must meet all of the requirements of iv) and v).
(vi) For radioactive material, number and category of packages, overpacks or freight containers,
exact loading location and, as applicable, transport index for each package;
(vii) Any restriction for transport on cargo aircraft only;
(viii) Offload airport;
(ix) If applicable, dangerous goods transported under a state exemption;
(x) If applicable, ULD identification number(s);
(xi) An indication that aircraft loading personnel observed no evidence of damage to or leakage
from packages, or leakage from ULDs, loaded onto the aircraft. (GM)
Auditor Actions
□ Identified/Assessed load control process to provide PIC with information pertaining to onboard
dangerous goods as cargo.
□ Interviewed responsible manager(s) in load control operations
□ Examined documents that confirm dangerous goods information was provided to PIC (e.g.
NOTOC).
□ Observed load control operations (focus: load control system includes process/method for
providing applicable dangerous goods information to PIC).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definitions of NOTOC (Notification to Captain) and State.
Such information is typically presented to the PIC in a notification called the NOTOC (notification to
the captain). The NOTOC contains the detailed information (as specified in this provision) relative to
all dangerous goods loaded on the aircraft as cargo.
Information contained in the NOTOC may also be used:
• For emergency response to an accident or incident involving dangerous goods on board;
• To provide to air traffic services in the event of an in-flight emergency.
In the event the NOTOC is of such a size as to make in-flight radiotelephony transmission
impracticable in an emergency situation, a summary of the information is typically provided to the PIC
(NOTOC Summary), which contains at least the quantities and classes or division of dangerous
goods in each cargo compartment.
Guidance may be found in DGR 9.5 and Table 9.5.A.
GRH 3.3.5 The Operator shall ensure weight and balance records are retained for a period in
accordance with requirements of the regulatory authority, but no less than three months.
Auditor Actions
□ Identified/Assessed means of retention for weight/balance records.
□ Interviewed responsible manager(s) in load control operations.
□ Examined selected weight and balance records.
□ Other Actions (Specify)
GRH 3.3.6 If the Operator conducts passenger flights, the Operator should ensure procedures are
in place for identification and communication to Load Control of:
(i) Hold baggage, individual or cumulative weights, that exceed normal allowances;
(ii) Gate delivery items, including individual or cumulative weights that exceed normal
allowances;
(iii) Other non-normal items that must be considered in the load control process. (GM)
Auditor Actions
□ Identified/Assessed procedures for ensuring identification/communication to Load Control of
non-normal items that must be considered in the load control process.
□ Interviewed responsible manager(s) in load control operations.
□ Examined documents that confirm non-normal items were addressed in the load control
process.
□ Observed load control operations (focus: load control system includes procedures that ensure
Identification/communication of load items that exceed normal weight allowances).
□ Other Actions (Specify)
Guidance
Examples of other non-normal items as specified in item iii) might include musical instruments,
medical equipment, sports equipment and service animals.
Refer to IGOM 1.1, 1.4, 2.1, 2.2 and 2.3 for further guidance that addresses non-normal loads.
GRH 3.3.7 If the Operator transports dangerous goods as cargo, the Operator shall have a process
to ensure a legible copy of the dangerous goods information is provided to the PIC in accordance
with GRH 3.3.4:
(i) Is retained on the ground;
(ii) Includes an indication that the PIC has received the information. (GM)
Auditor Actions
□ Identified/Assessed load control process that ensures dangerous goods information provided to
PIC is retained and includes indication PIC has received the information.
□ Interviewed responsible manager(s) in load control operations.
□ Examined selected retained documents containing dangerous goods information that was
provided to the PIC (e.g. NOTOC).
□ Other Actions (Specify)
Guidance
The intent of item i) is that either the NOTOC or all information that must be included in the NOTOC is
retained for reference.
An indication of receipt by the PIC is typically the PIC's signature.
Refer to IGOM 5.3.3 and 5.6.4 for guidance that addresses the notification to the PIC of onboard
dangerous goods. Additional guidance may be found in DGR 9.5.
GRH 3.3.8 If the Operator transports dangerous goods as cargo, the Operator shall have a process
to ensure the dangerous goods information provided to the PIC in accordance with GRH 3.3.4 is also
made readily available to FOO, FOA or other specifically identified operational control personnel until
the aircraft transporting the dangerous goods has arrived at the destination airport. Operational
control personnel that are provided with such information shall be specifically identified by job title or
function. (GM)
Auditor Actions
□ Identified/Assessed load control process to ensure dangerous goods information provided to
the PIC is made available to applicable operational control personnel.
□ Identified/Assessed job titles and/or functions of responsible personnel.
□ Interviewed responsible manager(s) in load control operations.
□ Examined selected records of dangerous goods information provided to applicable operational
control personnel.
□ Observed load control operations (focus: load control system includes process for providing
applicable dangerous goods information to operational control personnel).
□ Other Actions (Specify)
Guidance
As specified in DSP 3.7.3, designated operational control personnel provide information about
onboard dangerous goods as a way to assist emergency services that respond to an accident or
serious incident involving the operator's aircraft. The intent of this provision is to ensure operational
control personnel have ready access to such information so it can be reported without delay in the
event an accident or serious incident should occur.
Operational control personnel that must have access to such dangerous goods information are
typically identified in the appropriate manual by job position or function.
Refer to DSP 3.7.3 located in ISM Section 3.
GRH 3.4.3 If the Operator transports dangerous goods as cargo, the Operator shall ensure
procedures are in place for the loading and securing of dangerous goods on an aircraft in a manner
that:
(i) Prevents damage to packages and containers during aircraft loading and unloading;
(ii) Provides for separation and segregation in accordance with applicable requirements;
(iii) Prevents any movement in the aircraft. (GM)
Auditor Actions
□ Identified/Assessed procedures for loading/securing dangerous goods on aircraft.
□ Interviewed responsible manager(s) in ground handling operations.
□ Observed aircraft loading operations (focus: procedures for loading/securing dangerous goods
on board an aircraft that prevents damage/provides separation/prevents movement).
□ Interviewed personnel that perform aircraft loading.
□ Other Actions (Specify)
Guidance
Refer to IGOM 4.11.1 and DGR 9.3 for guidance that addresses the loading and securing of
dangerous goods.
GRH 3.4.4 If the Operator transports dangerous goods as cargo, the Operator shall ensure
procedures are in place that assure, when a dangerous goods package or shipment appears to be
damaged or leaking:
(i) The package or shipment is prevented from being loaded into an aircraft;
(ii) If already loaded, the package or shipment is removed from an aircraft;
(iii) In the case of leakage, an evaluation is conducted to identify and prevent from transport any
baggage, cargo, transport devices or other items that may have become
contaminated. (GM)
Auditor Actions
□ Identified/Assessed procedures for handling/addressing leaking/damaged dangerous goods
shipments.
□ Interviewed responsible manager(s) in ground handling operations.
□ Examined records/documents that illustrate handling of leaking/damaged dangerous goods
shipments.
□ Observed aircraft loading operations (focus: procedures for addressing dangerous goods
packages/shipments that appear to be leaking or damaged).
□ Interviewed personnel that perform aircraft loading.
□ Other Actions (Specify)
Guidance
Refer to DGR 9.3, 9.4 and 10.9, which contain guidance that addresses apparent damage to
dangerous goods shipments.
GRH 3.4.5 If the Operator transports dangerous goods as cargo, the Operator shall ensure
procedures are in place that require, when an aircraft has been contaminated by dangerous goods
leakage:
(i) Hazardous contamination is removed from the aircraft without delay;
(ii) In the case of radioactive contamination, arrangements are made to take the aircraft out of
service for evaluation by appropriately qualified personnel.
Auditor Actions
□ Identified/Assessed procedures for addressing aircraft contaminated by leakage of dangerous
goods.
□ Interviewed responsible manager(s) in ground handling operations.
□ Examined guidance/checklists used for dealing with an aircraft contaminated by leakage of
dangerous goods.
□ Other Actions (Specify)
GRH 3.4.6 If the Operator transports revenue or non-revenue cargo, the Operator shall ensure a
process is in place that requires, when undeclared or mis-declared dangerous goods are discovered
in cargo during aircraft loading, a report is made to the appropriate authority of the State of the
Operator (hereinafter “the State”) and state of occurrence. (GM)
Note: The specifications of this provision are applicable to operators that transport, and also to
operators that do not transport, dangerous goods as cargo.
Auditor Actions
□ Identified/Assessed process for reporting undeclared/mis-declared dangerous goods
discovered in cargo during aircraft loading to the appropriate authority.
□ Interviewed responsible manager(s) in ground handling operations.
□ Examined document(s) used for reporting undeclared/mis-declared dangerous goods
discovered in cargo during aircraft loading.
□ Other Actions (Specify)
Guidance
Refer to DGR 9.6 for additional guidance.
GRH 3.4.7 (Intentionally open)
GRH 3.4.8 If the Operator conducts passenger flights, the Operator shall ensure procedures are in
place that prevent shipments labeled “Cargo Aircraft Only” from being loaded onto an aircraft for a
passenger flight.
Auditor Actions
□ Identified/Assessed procedure(s) for preventing shipments with "Cargo Aircraft Only" labels
from being loaded onto aircraft for passenger flight.
□ Interviewed responsible manager(s) in ground handling operations.
□ Examined guidance/checklists used to ensure personnel do not load shipments with "Cargo
Aircraft Only" labels onto aircraft for passenger flight.
□ Interviewed personnel that perform aircraft loading.
□ Other Actions (Specify)
GRH 3.4.9 (Intentionally open)
GRH 3.4.10 If the Operator conducts passenger flights and transports dangerous goods as cargo,
the Operator shall ensure procedures are in place that prevent dangerous goods from being carried
in an aircraft cabin occupied by passengers, except as permitted by the Authority or the IATA
DGR. (GM)
Auditor Actions
□ Identified/Assessed procedure(s) for preventing loading of dangerous goods in an aircraft cabin
occupied by passengers, except as permitted.
□ Interviewed responsible manager(s) in ground handling operations.
attached or secured to a seat or seat/floor structure in a manner that ensures maximum load limits
are observed.
An operator might also use approved restraining nets to cover and secure cargo in passenger seats.
Also, some operators might permit the transport of certain passenger items secured in cabin
passenger seats. These types of items are typically large, valuable or fragile articles belonging to
passengers that are not conducive to transport as checked baggage or appropriate for stowage in
overhead bins/lockers (e.g. large musical instruments, certain electronic equipment, prominent
trophies, works of art). Such items might thus be secured and carried in a dedicated cabin passenger
seat (which might be purchased by the passenger-owner for this purpose).
Loading procedures for any of the above items would typically include access to technical data that
ensures seat load limitations are not exceeded.
A verification that cargo packages or passenger items being transported in passenger seats are
properly secured is accomplished by the cabin crew in accordance with CAB 3.2.3.
GRH 3.4.13 If the Operator conducts passenger flights, but does not transport revenue or non-
revenue cargo, the Operator shall ensure procedures are in place to identify items of cargo that are
not permitted for transport and prevent such items from being loaded onto an aircraft for a passenger
flight.
Auditor Actions
□ Identified/Assessed procedure(s) for identifying/preventing prohibited cargo items from being
loaded onto an aircraft for passenger flights.
□ Interviewed responsible manager(s) in ground handling operations.
□ Examined guidance/checklists used for identifying/preventing prohibited cargo items from being
loaded onto an aircraft for passenger flights.
□ Interviewed personnel that perform aircraft loading.
□ Other Actions (Specify)
Auditor Actions
□ Identified/Assessed procedures for responding to emergency aircraft evacuation during ground
handling operations.
□ Interviewed responsible manager(s) in ground handling operations.
□ Examined guidance/checklists used for response to aircraft evacuation during ground handling
operations.
□ Other Actions (Specify)
Guidance
Refer to IGOM 4.1.1, 4.1.3.7 and 6.7 for guidance that addresses ground handling event response
and reporting. Additional guidance may be found in AHM 633.
GRH 3.6.3 The Operator shall ensure procedures are in place for response to ground handling
incidents. (GM)
Auditor Actions
□ Identified/Assessed procedures for responding to incidents that occur in ground handling
operations.
□ Interviewed responsible manager(s) in ground handling operations.
□ Examined guidance/checklists used for response to incidents in ground handling operations.
□ Examined selected records of responses to ground handling incidents.
□ Other Actions (Specify)
Guidance
Refer to IGOM 6.4 for guidance that addresses ground handling event response and reporting.
GRH 3.6.4 The Operator should ensure a process is in place for the retention of records of
accidents and incidents associated with aircraft ground handling operations. (GM)
Auditor Actions
□ Identified/Assessed process for retention of records of ground handling operations
accidents/incidents.
□ Interviewed responsible manager(s) in ground handling operations.
□ Examined selected records of ground handling operations accidents/incidents.
□ Other Actions (Specify)
Guidance
Refer to AHM 650 for guidance that addresses ground handling event records retention.
GRH 3.6.5 The Operator shall ensure a process is in place that requires dangerous goods
accidents or incidents to be reported to the appropriate authority of the State and the state in which
the accident or incident occurred, and such reports are in accordance with the reporting requirements
of the appropriate authorities. (GM)
Note: The specifications of this provision are applicable to operators that transport, and also to
operators that do not transport, dangerous goods as cargo.
Auditor Actions
□ Identified/Assessed process for reporting dangerous goods accidents/incidents.
□ Interviewed responsible manager(s) in ground handling operations.
□ Examined guidance used for reporting dangerous goods accidents/incidents.
□ Examined selected dangerous goods accident/incident reports.
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of State.
Guidance may be found in DGR 9.6.
3.7 Security
GRH 3.7.1 The Operator shall, as appropriate with the assessed security risk, ensure procedures
are in place for securing an aircraft prior to and during overnight or layover parking. (GM)
Auditor Actions
□ Identified/Assessed procedures for securing of aircraft when parked (at all stations).
□ Interviewed manager/person(s) responsible for parking of aircraft.
□ Observed aircraft being secured.
□ Other Actions (Specify)
Guidance
Securing procedures typically ensure aircraft:
• Are searched prior to parking to ensure no persons are on board;
• Are parked only in secure areas within an airport operating area;
• Are parked under conditions that permit maximum security and protection;
• Doors are closed and locked and steps are removed while parked.
Guidance that addresses aircraft security may be found in AHM 051.
GRH 3.7.2 If the Operator conducts international flights, and if required by the relevant national
authority, the Operator shall ensure procedures are in place for the conduct of an aircraft security
check or an aircraft security search at the originating location of an international flight to ensure no
prohibited items are introduced in the aircraft prior to the departure of an international flight. (GM)
Auditor Actions
□ Identified/Assessed procedures for conducting aircraft security checks for locating prohibited
items.
□ Interviewed responsible manager(s) in ground handling operations.
□ Sampled selected records of previous aircraft security checks for prohibited items.
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of International Flights.
The need for a security check or a security search is typically based upon a security risk assessment
accomplished by the Operator and/or the relevant national authorities.
Trained and competent security personnel, aircraft crew members or other qualified personnel
typically conduct searches and checks of aircraft.
Guidance material is typically made available by the operator for aircraft preflight checks and
searches under normal circumstances, higher threat situations, and emergency situations.
As a general rule, the security checks would include:
• An inspection of the exterior of the aircraft, with special attention to wheel bays and technical
areas;
• A comprehensive inspection of the interior of the aircraft, including the passenger cabin area,
seats, overhead luggage lockers, toilets, galleys and other technical areas such as the flight
deck. The focus is on areas that are readily accessible without the use of common tools. To
facilitate the search, panels that can be sealed are sealed, to show their integrity has not
been compromised.
A security search is a more thorough than a security check, and typically includes an in-depth
inspection of the interior and exterior of the aircraft.
To promote competent security searches, aircraft security search checklists are normally made
available for each type and configuration of aircraft. When the checklist is completed, it is verified by
the person responsible for conducting the inspection and is retained on file at the station where the
inspection took place.
To be effective, aircraft checks and searches are typically carried out in good lighting conditions, or
personnel performing such activities are provided with lighting sufficient for the purpose.
Aircraft access control is typically imposed prior to commencing a search, and the search is normally
conducted with the minimum number of persons on board. Such measures would be taken to ensure
devices are not introduced into the aircraft once it has been cleared. Control of access is then
typically maintained until the aircraft doors are closed prior to flight departure.
GRH 3.7.3 If the Operator conducts international passenger flights that transit an airport that is
deemed by the Operator or the appropriate authority to be under an increased security threat, the
Operator shall ensure procedures are in place to ensure any items left behind by disembarking
passengers from such transit flights are removed from the aircraft or otherwise addressed
appropriately before the flight departure. (GM)
Auditor Actions
□ Identified/Assessed procedures to remove or address items from passengers which are left
behind.
□ Interviewed responsible manager(s) in ground handling operations.
□ Sampled cases in which items were removed or otherwise addressed.
□ Other Actions (Specify)
Guidance
The operator or the State of the Operator, through a threat assessment, will determine which airports
are considered at a higher security threat and require the removal of cabin articles, including carry-on
baggage, at transit stops.
At airports assessed to be under increased threat, measures are typically implemented to search the
cabin during the aircraft transit period to prevent disembarking passengers from leaving any article
on board.
The operator may allow passengers to disembark during the transit period and then have the cabin
searched.
If the operator opts to have transit passengers remain on board the aircraft during the transit stop,
such passengers remaining on board are typically asked to positively identify their belongings,
perhaps by placing them on their laps, while the security check or search is performed.
Any articles found are typically treated as suspect and appropriate measures are taken to remove
them from the aircraft.
□ Examined selected quality control inspection reports (focus: fuel supply quality management).
□ Other Actions (Specify)
Guidance
The intent of this provision is to ensure fuel is stored, handled and serviced in accordance with
accepted standards.
Approved fuel specifications are contained in each aircraft manual.
To ensure fuel corresponds to the specifications and grade of product necessary for the applicable
aircraft type(s), a control process is typically in place at each location where the operator has aircraft
fueling operations. Such process ensures the existence of periodic inspections of critical aspects of
the fuel supply system at each applicable location, to include, as a minimum:
• Fuel facilities;
• Safety and quality procedures;
• Performance levels of personnel.
Processes for ensuring fuel is of the correct grade and free of contamination may be documented in
maintenance, ground operations or flight operations manuals, or in a combination thereof.
If the Operator uses biofuels, additional procedures would typically address the related specific
requirements (i.e. dedicated infrastructures and blending requirements).
Additional guidance may be found in the IFQP (IATA Fuel Quality Pool) Quality and Safety
Procedures and in the ICAO Manual on Civil Aviation Jet Fuel Supply (Doc 9977).
GRH 4.1.2 The Operator shall ensure, during fueling operations with passengers or crew on board
the aircraft, procedures are in place that provide for the designation of a person with responsibility for
fueling operations and specify the method(s) by which that responsible person:
(i) Communicates with the flight crew or other qualified persons on board the aircraft;
(ii) Provides notification to the flight crew or other qualified personnel on board the aircraft
and/or other appropriate personnel engaged in aircraft ground handling activities when
fueling is about to begin and has been completed unless an equivalent procedural means
has been established to ensure the flight and/or cabin crew are aware of fueling operations
and are in a position to effect an expeditious evacuation of the aircraft, if necessary;
(iii) Provides notification to the flight crew or other qualified personnel on board the aircraft when
a hazardous condition or situation has been determined to exist. (GM)
Auditor Actions
□ Identified/Assessed procedures for communication between ground and onboard personnel
during aircraft fueling operations.
□ Interviewed person(s)/manager(s) responsible for fueling operations.
□ Interviewed selected aircraft fueling supervisory personnel.
□ Observed aircraft ground handling operations (focus: establishment of method for ground-
aircraft communication during aircraft fueling operations).
□ Coordinated with flight operations and cabin operations to verify complementary procedures for
communication with ground personnel during aircraft fueling operations.
□ Other Actions (Specify)
Guidance
Ground handling personnel would typically need to have a clear understanding of all required
communication procedures and have the ability to execute such procedures in an expeditious
manner should a dangerous situation develop.
The specification in item ii) may be satisfied by either:
• Equivalent procedural means, acceptable to the State and applicable authorities, that would
permit the flight crew or other qualified persons to be aware of the start and completion of
fueling operations, or
• Procedures established by the operator that would ensure authorized personnel on board the
aircraft are continuously in a position to effect an expeditious evacuation of the aircraft for
any reason, including a fuel spill or fire.
Suitable methods of communication with the flight crew or other qualified persons on board the
aircraft include use of the aircraft inter-communication system, direct person-to-person contact or
other methods that ensure direct and timely communication. Use of the aircraft inter-communication
system to maintain continuous two-way communication during fueling operations is not a
requirement.
Additional guidance may be found in AHM 175 and 631, as well as the ICAO Airport Services
Manual, Document 9137 (ASM), Part 1.
GRH 4.1.3 The Operator shall ensure procedures are in place for fueling operations with
passengers or crew on board the aircraft that provide for, in the event of a fuel spill, immediate and
follow-up actions to assure:
(i) Fueling is stopped;
(ii) Appropriate ground response personnel or airport fire service is summoned, as applicable;
(iii) Notification of the flight crew or other qualified persons on board the aircraft. (GM)
Auditor Actions
□ Identified/Assessed procedures associated with a fuel spill during aircraft fueling operations.
□ Interviewed responsible manager(s) in ground handling operations.
□ Interviewed selected aircraft fueling supervisory personnel.
□ Observed aircraft ground handling operations (focus: implementation of procedures for
addressing fuel spill during aircraft fueling operations)
□ Other Actions (Specify)
Guidance
Refer to IGOM 4.4 for guidance that addresses fuel spillage.
GRH 4.1.4 The Operator should ensure, during fueling operations with passengers or crew on
board the aircraft, procedures are in place that establish a fueling safety zone and specify restrictions
and limitations for the use of devices, conduct of activities and operation of vehicles and ground
support equipment within the safety zone. (GM)
Auditor Actions
□ Identified/Assessed safety procedures for aircraft fueling operations (focus: establishment of
safety zone are included/addressed in fueling procedures.
□ Interviewed responsible manager(s) in ground handling operations.
□ Interviewed selected aircraft fueling supervisory personnel.
□ Observed aircraft ground handling operations (focus: implementation of procedures for
establishing fueling safety zone during aircraft fueling operations).
□ Other Actions (Specify)
Guidance
Procedures typically specify the fueling safety zone as the area within a radius of at least three
meters (ten feet), or as specified by local regulations, from filing and venting points of the aircraft,
hydrant pits, fueling vehicle and its hoses in use.
Limitations and restrictions in a fueling safety zone typically preclude the use or activation of:
• Items that could be sources of ignition or fire (e.g. matches, welding equipment, flashbulbs);
• Portable electronic devices with proper separation distance from aircraft fuel vents and/or
fueling equipment (e.g. mobile telephones, portable radios, pagers).
Refer to IGOM 4.4 for guidance that addresses fueling safety zone. Additional guidance may be
found in AHM 175 and 630, as well as the ICAO ASM, Part 1.
GRH 4.1.5 The Operator shall ensure safety procedures associated with aircraft fueling operations
are in place that assure, during fueling operations with passengers or crew on board the aircraft:
(i) The ground area beneath aircraft exit doors that have been designated for rapid deplaning
or emergency evacuation is kept clear of obstructions;
(ii) Where a boarding bridge is in use, an interior access path is maintained from the aircraft to
the terminal;
(iii) Where a passenger boarding bridge is not in use, aircraft passenger steps or an alternate
means of emergency evacuation is in place. (GM)
Auditor Actions
□ Identified/Assessed safety procedures for aircraft fueling operations (focus: specifications of
this standard are included/addressed in fueling procedures).
□ Interviewed responsible manager(s) in ground handling operations.
□ Interviewed selected aircraft fueling supervisory personnel.
□ Observed aircraft ground handling operations (focus: implementation of safety procedures
during aircraft fueling operations).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Integral Airstairs.
When deployed, integral airstairs are acceptable as an alternate means of emergency evacuation.
Refer to IGOM 4.4 for guidance that addresses fueling safety zone. Additional guidance may be
found in AHM 175 and 630, as well as the ICAO ASM, Part 1.
GRH 4.1.6 The Operator should ensure safety procedures associated with aircraft fueling
operations are in place that assure, during fueling operations with passengers or crew on board the
aircraft:
(i) Establishment of a bonding connection between the fueling vehicle and aircraft to provide
for dissipation of electrical energy that may develop;
(ii) Prohibition from connecting or disconnecting electrical equipment to the aircraft;
(iii) Prevention of damage to the fuel hose;
(iv) Cessation of aircraft fueling when it is determined lightning is a threat. (GM)
Auditor Actions
□ Identified/Assessed safety procedures for aircraft fueling operations (focus: specifications of
this standard are included/addressed in fueling procedures).
□ Interviewed responsible manager(s) in ground handling operations.
□ Interviewed selected aircraft fueling supervisory personnel.
□ Observed aircraft ground handling operations (focus: implementation of safety procedures
during aircraft fueling operations).
□ Other Actions (Specify)
Guidance
Guidance may be found in AHM 175 and 630.
GRH 4.1.7 The Operator shall ensure procedures are in place for summoning the rescue and
firefighting service in the event of a fire or major fuel spill. (GM)
Auditor Actions
□ Identified/Assessed safety procedures for aircraft fueling operations (focus: procedures for
summoning firefighting service are included/addressed in fueling procedures.
□ Interviewed responsible manager(s) in ground handling operations.
GRH 4.2.2 If the Operator has a De-/Anti-icing Program, the Operator shall ensure policies and
procedures are in place that result in:
(i) Standardized methods of fluid application;
(ii) Compliance with specific aircraft limitations;
(iii) A clean aircraft through proper treatment of applicable surfaces. (GM)
Auditor Actions
□ Identified/Assessed policies and procedures for aircraft de-/anti-icing.
□ Interviewed responsible manager(s) in ground handling operations.
□ Examined checklist(s) used for de-/anti-icing operations.
□ Interviewed personnel that perform operational functions in aircraft de-/anti-icing operations.
□ Examined selected quality control inspection reports (focus: aircraft de-/anti-icing operations).
□ Interviewed supervisory personnel for aircraft de-/anti icing operations.
□ Other Actions (Specify)
Guidance
To ensure desired results, an operator's de-/anti-icing program would typically include policies and
procedures that:
• Define equipment for and methods of applying de-icing and anti-icing fluid to produce an
aircraft free of contamination (clean aircraft);
• Specify a sequence for fluid application to the applicable aircraft surfaces and define specific
methods and techniques for applying fluid to each individual surface;
• Provide limitations that are to be observed to successfully complete the process, including
correct fluid mixtures, fluid temperatures and nozzle pressure.
Additional guidance may be found in ICAO Doc 9640-AN/940, Manual of Aircraft Ground
De-icing/Anti-icing Operations, Chapter 11, and in SAE AS6285, Aircraft Ground Deicing/Anti-Icing
Processes.
GRH 4.2.3 If the Operator has a De-/Anti-icing Program, the Operator should have a process to
ensure the availability and use of adequate facilities and equipment for aircraft de-/anti-icing
operations at applicable locations.
Auditor Actions
□ Identified/Assessed requirements for facilities and equipment in de-/anti-icing program.
□ Interviewed responsible manager(s) in ground handling operations.
□ Examined records/documents that specify facilities/equipment at selected airports identified as
having potential for ground icing conditions.
□ Interviewed supervisory personnel for aircraft de-/anti icing operations.
□ Other Actions (Specify)
GRH 4.2.4 If the Operator has a De-/Anti-icing Program, the Operator shall ensure fluids used in
de-icing and anti-icing operations are:
(i) Stored, handled and applied in accordance with criteria established by the Operator, fluid
manufacturer and aircraft manufacturer;
(ii) Manufactured in accordance with SAE specifications. (GM)
Auditor Actions
□ Identified/Assessed process for management/monitoring of de-/anti-icing fluid quality at
applicable locations.
□ Interviewed responsible manager(s) in ground handling operations.
□ Examined records/documents that detail quality management of de-/anti-icing fluids at selected
locations.
□ Examined selected quality control inspection reports (focus: aircraft de-/anti-icing fluid
management).
□ Interviewed supervisory personnel for aircraft de-/anti icing operations.
□ Other Actions (Specify)
Guidance
To be effective, an operator's de-/anti-icing program would typically include policies and procedures
that ensure the following:
• Fluids used in the de-/anti-icing process are manufactured in accordance with ISO
specifications and meet use criteria established by the operator, fluid manufacturer and
aircraft manufacturer;
• The appropriate types of fluids (Types I, II, III or IV) are utilized in the proper manner for
conditions under which de-icing and anti-icing operations are being conducted, each diluted
as required to achieve desired results;
• Fluids are handled in accordance with recommendations of the fluid manufacturer and
effectiveness is not degraded due to contamination.
Additional guidance may be found in ICAO Doc 9640-AN/940, Manual of Aircraft Ground
De-icing/Anti-icing Operations, Chapter 11.
GRH 4.2.5 If the Operator has a De-/Anti-icing Program, the Operator shall ensure procedures are
in place for ground handling personnel to communicate with the flight crew to assure:
(i) The aircraft is properly configured prior to beginning the de-/anti-icing process;
(ii) The flight crew receives all necessary information relevant to fluid(s) applied to the aircraft
surfaces;
(iii) The flight crew receives confirmation of a clean aircraft;
(iv) The flight crew receives an “all clear” signal at the completion of the de-/anti-icing process
and prior to aircraft movement. (GM)
Auditor Actions
□ Identified/Assessed procedures for communication between ground personnel and flight crew
during aircraft de-/anti-icing operations.
□ Interviewed responsible manager(s) in ground handling operations.
□ Examined selected quality control inspection reports (focus: ground-aircraft communication
procedures).
□ Interviewed supervisory personnel for aircraft de-/anti icing operations.
□ Other Actions (Specify)
Guidance
To ensure effective communications during de-/anti-icing operations, an operator's de-/anti-icing
program would typically include policies and procedures that ensure the following:
• All necessary communications between ground handling personnel and the flight crew prior
to and after completion of the de-/anti-icing process are defined;
• Ground handling personnel provide the flight crew with final information that verifies the
aircraft is in compliance with the Clean Aircraft Concept.
Additional guidance may be found in ICAO Doc 9640-AN/940, Manual of Aircraft Ground
De-icing/Anti-icing Operations, Chapter 10.
Subjects Functions
L10 L20 L30 L30B
(i) Common standards, regulations and recommendations X X X X
(ii) Basic knowledge of aircraft performance X X X
(iii) Effects of frost, ice, snow, slush and fluids on aircraft X X X
performance
(iv) Meteorological considerations on ice formation X X X
(v) Basic characteristics of aircraft deicing/anti-icing fluids, X X
including causes and consequences of fluid degradation and
residues
(vi) General techniques for removing deposits of frost, ice, slush X X
and snow from aircraft surfaces and for anti-icing
(vii) Deicing/anti-icing procedures in general and specific measures X X X X
to be performed on different aircraft types and deicing using
hot air
(viii) Aircraft in general and common critical areas X X X X
(ix) Types of checks required X X X
(x) Deicing/anti-icing equipment and facilities operating procedures X X
including actual operation
(xi) Fluid application and limitations of holdover time tables X X
(xii) Deicing/anti-icing codes and communication procedures X X X X
(xiii) Conditions which can lead to the formation of ice on the aircraft X X X
(xiv) Local rules and restrictions X X X X
(xv) Airport operational procedures and ATC X X X X
(xvi) Company and customer procedures X X X X
(xvii) Deicing coordination procedures X
Note: The above training syllabus specifications are derived from SAE AS 6286 as applicable to four
functions that are directly involved in aircraft de-/anti-icing operations. To avoid duplication, syllabus
specifications that are included in other tables in this section have been omitted from this table.
Applicability
Section 7 addresses functions within the scope of cargo operations, and is applicable to an operator that
transports revenue and/or non-revenue cargo. COMAT (Company Material) is non-revenue cargo.
In this section, non-revenue cargo is addressed in the same way as revenue cargo for the purposes of
handling, loading, securing and transporting.
For the purpose of addressing cargo in this section, mail is considered to be an item of cargo. Therefore,
any reference to cargo also includes mail.
Individual provisions in this section begin with a conditional phrase (“If the Operator...”) and are applicable
to an operator that meets the condition(s) stated in the phrase.
Functions within the scope of cargo operations include:
• Cargo acceptance;
• Cargo handling;
• ULD loading/build-up;
• Application of required security measures.
Certain operators, particularly all-cargo operators, might have ground handling operations functions
performed by cargo operations personnel (e.g. aircraft loading, airside operations, load control). Where
this situation exists, the operator must be in conformity with the ISARPs contained in Section 6, Ground
Handling Operations (GRH), that are applicable to the ground handling operations functions performed by
cargo operations personnel.
Where an operator outsources the performance of cargo operations functions to external service
providers, the operator retains overall responsibility for ensuring the management of safety in the conduct
of such operations, and must demonstrate processes for monitoring applicable external service providers
in accordance with CGO 1.10.2.
General Guidance
Definitions of technical terms used in this ISM Section 7, as well as the meaning of abbreviations and
acronyms, are found in the IATA Reference Manual for Audit Programs (IRM).
CGO 1.1.2 If the Operator transports revenue cargo, the Operator shall have a manager for cargo
operations that:
(i) Has the authority and responsibility for the management and supervision of functions and
activities within the scope of cargo operations;
(ii) Is accountable to senior management for ensuring the safety and security of cargo
operations.
Auditor Actions
□ Identified manager for cargo operations.
□ Examined job description of manager for cargo operations (focus: defines
authority/accountability/responsibility for risk management/compliance with AOC requirements).
□ Interviewed manager of cargo operations.
□ Interviewed other managers in cargo operations.
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Post Holder.
Refer to Guidance associated with ORG 1.3.2 located in ISM Section 1.
1.3 Communication
CGO 1.3.1 If the Operator transports revenue cargo, the Operator shall have a communication
system that enables an effective exchange of information relevant to the conduct of cargo operations
throughout the management system for cargo operations and in areas where cargo operations are
conducted. (GM) ◄
Auditor Actions
□ Identified/Assessed system(s) for communicating information relevant to operations within the
cargo operations organization (focus: capability for communicating information relevant to
operations within the cargo operations organization).
□ Interviewed cargo operations manager and/or designated management representative(s).
□ Examined examples of information communication/transfer in cargo operations.
□ Interviewed selected non-management operational personnel in cargo operations.
□ Other Actions (Specify)
Guidance
Refer to Guidance associated with ORG 1.4.1 located in ISM Section 1, for expanded information
regarding methods of communication.
□ Interviewed personnel that perform cargo operations functions relevant to the safety or security
of aircraft operations.
□ Other Actions (Specify)
Guidance
Refer to Guidance associated with ORG 1.6.2 located in ISM Section 1.
A corporate personnel selection policy that applies to all operational areas of the organization serves
to satisfy this requirement.
To ensure the inclusion of all cargo operations, an operator would typically have a process that
ensures specifications in this provision are applied to external cargo operations service providers.
policies, processes, procedures and other information necessary to ensure compliance with
applicable regulations, laws, rules and standards of the Operator. The content of the OM shall
contain standards and guidance that addresses the acceptance, handling, loading, securing and
transporting of cargo as specified in Table 7.1. (GM)
Auditor Actions
□ Identified/Assessed cargo OM or, if applicable, separate documents that comprise the OM.
□ Interviewed responsible management representative(s).
□ Identified standards and guidance in the OM that address acceptance, handling, loading,
securing and transporting of cargo as per Table 7.1.
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of High-risk Cargo.
This provision is applicable to an operator that transports non-revenue cargo. COMAT is non-
revenue cargo.
An OM may include guidance that addresses areas generic to all functions within the scope of cargo
operations; other parts of the manual may be specific to individual operational functions.
Because the scope of cargo operations is broad and varies by operator, rather than publishing a
separate OM dedicated to cargo operations (e.g. a Cargo Operations Manual), an operator might
choose to publish all guidance for cargo operations in a section of an OM that addresses other types
of operations (e.g. maintenance management manual for an operator that transports only COMAT).
An operator could also choose to issue the information in separate documents that are each specific
to the various cargo operations functions (e.g. safety and security, acceptance, physical handling,
documentation, identification, storage and stowage, preparation for flight). Each individual document
would typically contain generic guidance that is applicable to all cargo operations functions (e.g.
organizational policies, general definitions), as well as guidance that is specific to the particular
function or office location (e.g. process descriptions, standard operating procedures, references to
the appropriate regulations and IATA manuals).
If an operator has external organizations conduct cargo operations functions, such an operator would
then be expected to have a monitoring and control process to ensure each external organization
either uses the OM of the operator or has its own published operations manual that fulfills operational
safety, security and quality requirements of the operator.
CGO 1.6.2 If the Operator transports dangerous goods as revenue or non-revenue cargo, the
Operator shall ensure a copy of the current edition of the Dangerous Goods Regulations (DGR) or
the ICAO Technical Instructions for the Safe Transport of Dangerous Goods by Air (Technical
Instructions), including addenda as appropriate, is available at each location where revenue or non-
revenue cargo operations are conducted and dangerous goods are accepted. (GM)
Auditor Actions
□ Identified/Assessed process for ensuring distribution of DGR or appropriate DG documents to
all locations where there is DG acceptance and/or handling.
□ Interviewed responsible management representative(s).
□ Observed cargo acceptance and cargo handling operations (focus: availability/accessibility of
DGR or Technical Instructions where dangerous goods cargo is accepted or handled).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definitions of Airport Handling Manual (AHM), Dangerous Goods Regulations
(DGR), Live Animals Regulations (LAR), Perishable Cargo Regulations (PCR), ULD Regulations
(ULDR) and Unit Load Device.
Cargo operations would include acceptance of any cargo, to include small packages that would be
shipped as cargo.
A monitoring process is typically in place to ensure each external cargo operations service provider
has a copy of the DGR or ICAO Technical Instructions available as specified.
Other relevant manuals, to include the Live Animals Regulations (LAR), Airport Handling Manual
(AHM), Perishable Cargo Regulations (PCR) and ULD Regulations (ULDR), may also be available.
The DGR is based on the ICAO Technical Instructions and is designed for ease of use in operations.
However, in some jurisdictions it may be a requirement to have the ICAO Technical Instructions
available in accordance with local regulations.
When required, DGR addenda are issued to notify of any amendments or corrections to the current
edition of the Dangerous Goods Regulations. It may include any corrigenda issued by ICAO to the
current edition of the Technical Instructions.
CGO 1.6.3 If the Operator transports revenue or non-revenue cargo, but does not transport
dangerous goods, the Operator shall ensure the OM contains the policies and associated guidance
necessary to prevent dangerous goods from being inadvertently accepted for transport and loaded
onto the aircraft. (GM)
Auditor Actions
□ Identified/Assessed information in the cargo OM or equivalent manual necessary to ensure
personnel do not inadvertently permit acceptance or transport of dangerous goods.
□ Interviewed responsible management representative(s).
□ Interviewed personnel that perform operational functions in cargo operations.
□ Other Actions (Specify)
Guidance
For a dangerous goods “no-carry” operator, guidance in the OM typically addresses vigilance with
respect to hidden or inconspicuous dangerous goods, and includes an indicative list of items that
could contain dangerous goods.
CGO 1.6.4 If the Operator transports revenue or non-revenue cargo using Unit Load Devices
(ULDs), the Operator should ensure a copy of the current edition of ULD Regulations (ULDR), or the
OM containing equivalent ULD related content, is available or accessible at each location where
revenue or non-revenue cargo operations are conducted and ULDs are utilized. (GM)
Auditor Actions
□ Identified/Assessed process for ensuring distribution of ULDR or OM containing equivalent
ULD-related content to all locations where revenue or non-revenue cargo operations are
conducted.
□ Interviewed responsible management representative(s).
□ Traced distribution of ULDR or appropriate OM with equivalent content.
□ Observed cargo handling operations (focus: availability/accessibility of ULDR or OM with
equivalent content where cargo operations are conducted and ULDs are utilized.
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Weight and Balance Manual (W&BM).
ULDs are required to meet airworthiness requirements when loaded onto an aircraft, either by
certification or by compliance with the Weight and Balance Manual. Adhering to the ULDR is one
means (but not the only means) that ULD operations may be carried out in compliance with the
requirements of the Weight and Balance Manual.
is in accordance with requirements of the Authority, as applicable, and to ensure operational records
are subjected to standardized processes for:
(i) Identification;
(ii) Legibility;
(iii) Maintenance;
(iv) Retention and retrieval;
(v) Protection and security;
(vi) Disposal or deletion (electronic records). (GM) ◄
Auditor Actions
□ Identified/Assessed management and control system for operational records in cargo
operations (focus: system includes standardized processes as specified in standard).
□ Interviewed responsible management representative(s).
□ Examined examples of operational records in cargo operations.
□ Other Actions (Specify)
Guidance
Refer to Guidance associated with ORG 2.2.1 located in ISM Section 1.
CGO 1.7.2 If the Operator transports revenue cargo and utilizes an electronic system for the
management of records, the Operator shall ensure the system provides for a scheduled generation
of back-up record files. (GM) ◄
Auditor Actions
□ Identified/Assessed management and control system for operational records in cargo
operations (focus: system defines schedule for periodic file backup).
□ Interviewed responsible management representative(s).
□ Examined record(s) of back-up files for electronic records.
□ Other Actions (Specify)
Guidance
Refer to Guidance associated with ORG 2.2.2 located in ISM Section 1.
Auditor Actions
□ Identified/Assessed planning process for quality assurance auditing of cargo operations (focus:
audits planned/scheduled/completed in order to meet applicable internal/external requirements).
□ Identified/Assessed audit resources (focus: availability of sufficient auditors/other resources to
accomplish audit plan).
□ Interviewed quality assurance program manager.
□ Crosschecked audit plan with selected audit reports, to verify adherence to plan (focus: audits
conducted in accordance with audit plan).
□ Other Actions (Specify)
Guidance
Refer to Guidance associated with ORG 3.4.10 located in ISM Section 1.
Guidance
Refer to Guidance associated with ORG 3.5.2 located in ISM Section 1.
CGO 1.10.3 If the Operator transports revenue or non-revenue cargo, and has external service
providers conduct outsourced cargo operations functions, the Operator should include auditing as a
process for the monitoring of external service providers in accordance with CGO 1.10.2. (GM) ◄
Auditor Actions
□ Identified/Assessed auditing processes used for monitoring external cargo operations service
providers.
□ Interviewed responsible manager(s) in cargo operations.
□ Examined selected reports of audits performed on external cargo operations handling service
providers.
□ Other Actions (Specify)
Guidance
Refer to Guidance associated with ORG 3.5.3 located in ISM Section 1.
(iii) When required, risk mitigation actions are developed and implemented in cargo operations.
[SMS] (GM) ◄
Auditor Actions
□ Identified/Assessed safety risk assessment and mitigation program in cargo operations (focus:
hazards analyzed to identify/define risk; risk assessed to determine appropriate action; action
implemented/monitored to mitigate risk).
□ Identified/Assessed role of cargo operations in cross-discipline safety risk
assessment/mitigation program (focus: participation with other operational disciplines).
□ Interviewed responsible manager(s) in cargo operations.
□ Interviewed person(s) that perform cargo operations risk assessment/mitigation.
□ Examined selected records/documents that illustrate risk assessment/mitigation action.
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Safety Risk Assessment (SRA).
Risk assessment and mitigation is an element of the Safety Risk Management component of the
SMS framework.
The potential for hazards is typically associated with the following aspects of cargo handling
operations:
• Acceptance and handling of dangerous goods and other special cargo shipments (e.g.
lithium batteries);
• Application of security controls;
• Protection from acts of unlawful interference;
• Build-up, handling and serviceability of ULDs;
• Operation and serviceability of cargo handling equipment;
• Adequacy of facilities.
Refer to Guidance associated with ORG 3.1.2 located in ISM Section 1.
Operational Reporting
CGO 1.11.3 If the Operator transports revenue cargo, the Operator shall have an operational
safety reporting system in the cargo operations organization that:
(i) Encourages and facilitates cargo operations personnel to submit reports that identify safety
hazards, expose safety deficiencies and raise safety concerns;
(ii) Includes analysis and cargo operations management action to address operational
deficiencies, hazards, incidents and concerns identified through the reporting system.
[SMS] (GM) ◄
Auditor Actions
□ Identified/Assessed documented operational safety reporting system in cargo operations
(focus: system urges/facilitates reporting of hazards/safety concerns; includes analysis/action to
validate/address reported hazards/safety concerns).
□ Interviewed responsible manager(s) in cargo operations.
□ Interviewed person(s) that perform operational safety report review/analysis/follow-up in cargo
operations.
□ Interviewed personnel that perform operational functions in cargo operations.
□ Examined data that confirm an effective cargo operations safety reporting system (focus:
quantity of reports submitted/hazards identified).
Refer to DGR 1.5, which addresses dangerous goods training for personnel that perform cargo
operations functions.
CGO 2.1.3 (Intentionally open)
CGO 2.1.4 If the Operator transports revenue or non-revenue cargo, the Operator shall have a
process to ensure the training programs completed by cargo operations personnel in accordance
with CGO 2.1.1 are reviewed and updated to remain relevant and current.
Auditor Actions
□ Identified/Assessed process for review and update of training program completed by cargo
operations personnel.
□ Interviewed responsible manager(s) in cargo operations.
□ Examined selected training program records/documents (focus: programs have been
periodically reviewed and updated).
□ Other Actions (Specify)
CGO 2.1.5 If the Operator transports revenue or non-revenue cargo, the Operator shall have a
process to ensure training for personnel that perform operational duties within the scope of cargo
operations for the Operator:
(i) Includes testing or evaluation by written, oral or practical means, as applicable;
(ii) Requires a demonstration of adequate knowledge, competency and proficiency to perform
duties, execute procedures and/or operate equipment.
Auditor Actions
□ Identified/Assessed training programs for cargo operations personnel (focus: programs include
a process for testing/evaluations/demonstrations as specified).
□ Interviewed responsible manager(s) in cargo operations.
□ Examined selected initial/recurrent course curricula/syllabi (focus: initial and recurrent training
programs include testing/evaluations/demonstrations).
□ Examined initial/recurrent training records of selected personnel (focus:
testing/evaluations/demonstrations as specified completed during initial and recurrent training).
□ Other Actions (Specify)
CGO 2.1.6 If the Operator transports revenue or non-revenue cargo, the Operator shall have a
process to ensure completion of required training by personnel that perform operational duties within
the scope of cargo operations for the Operator is recorded and such records retained in accordance
with CGO 1.7.1.
Auditor Actions
□ Identified/Assessed cargo operations records system (focus: system includes training records
of personnel that perform cargo operations duties).
□ Interviewed responsible manager(s) in cargo operations.
□ Examined initial/recurrent training records of selected personnel (focus: records include
completion of required training).
□ Other Actions (Specify)
for accepting or handling any cargo complete dangerous goods training, to include initial training and
recurrent training, on a frequency in accordance with CGO 2.2.1. Such training shall address, as a
minimum:
(i) General philosophy;
(ii) Limitations;
(iii) Labeling and marking;
(iv) For personnel that accept cargo, shipper's declarations and other relevant documentation;
(v) Recognition of undeclared dangerous goods;
(vi) Provisions for passengers and/or crew;
(vii) Emergency procedures. (GM)
Auditor Actions
□ Identified/Assessed process for dangerous goods training for cargo operations personnel that
accept/handle cargo.
□ Interviewed responsible manager(s) in cargo operations
□ Examined selected initial/recurrent dangerous goods training curricula/syllabi applicable to
cargo operations personnel that accept/handle cargo.
□ Examined initial/recurrent training records of selected cargo operations personnel that
accept/handle cargo.
□ Other Actions (Specify)
Guidance
When an operator does not transport dangerous goods (i.e. a “no-carry” operator), dangerous goods
training is still required for cargo operations personnel to ensure declared and undeclared dangerous
goods are recognized and prohibited from being carried or loaded onto an aircraft.
Dangerous goods training is structured to provide the requisite knowledge to permit cargo operations
personnel to recognize dangerous goods, whether labeled or not labeled, and to prevent such
dangerous goods from being inadvertently accepted and/or planned for loading into an aircraft.
Refer to DGR 1.5 (Table 1.5.B, Minimum Requirements for Training Curricula for “No-carry”
Operators), for detailed guidance that addresses dangerous goods training and subjects applicable
to specific cargo operations functions.
CGO 2.2.3 If the Operator transports revenue or non-revenue cargo, the Operator shall have a
process to ensure personnel assigned the responsibility for handling or storing such cargo, as well
as, where applicable, the loading of ULDs, receive dangerous goods training, to include initial training
and recurrent training, on a frequency in accordance with CGO 2.2.1. Such training shall address, as
a minimum:
(i) General philosophy;
(ii) Limitations;
(iii) Labeling and marking;
(iv) Recognition of undeclared dangerous goods;
(v) Storage and loading procedures;
(vi) Flight crew notification;
(vii) Provisions for passengers and/or crew;
(viii) Emergency procedures. (GM)
Auditor Actions
□ Identified/Assessed process for dangerous goods training for cargo operations personnel that
handle/store cargo; where applicable, load cargo on/into ULDs.
□ Interviewed responsible manager(s) in cargo operations.
CGO 3.1.4 If the Operator transports revenue cargo, the Operator should have a process to ensure
cargo terminals are equipped with facilities appropriate for storage of dangerous goods and other
special cargo, such as human remains, live animals, perishables, valuable cargo and
pharmaceuticals. (GM)
Auditor Actions
□ Identified/Assessed process that ensures cargo terminals are equipped with facilities
appropriate for storage of special cargo shipments.
□ Interviewed responsible manager(s) in cargo operations
□ Observed cargo handling operations: (focus: existence of facilities for storage of dangerous
goods and other special cargo shipments).
□ Other Actions (Specify)
Guidance
Such items may have separation requirements as specified in the appropriate IATA manual(s) and,
additionally, may be governed by local rules or regulations. Information relative to storage of cargo is
included in the OM.
□ Observed cargo acceptance operations (focus: use of dangerous goods acceptance checklist to
verify package marking/labeling, documentation compliance).
□ Other Actions (Specify)
Guidance
Refer to DGR 9.1.3 for guidance that addresses use of the Dangerous Goods Acceptance Checklist.
CGO 3.2.3 If the Operator transports dangerous goods as revenue or non-revenue cargo, the
Operator shall have procedures to ensure the completed Dangerous Goods Acceptance Checklist
and shipper documentation, to include, if required, the Shipper's Declaration for Dangerous Goods,
and the information provided to the pilot-in-command (PIC), are retained for a minimum period of
three months after the flight on which the dangerous goods were transported. (GM)
Auditor Actions
□ Identified/Assessed procedures for ensuring retention of all applicable dangerous goods cargo
information, including dangerous goods acceptance checklist, shipper documentation and
information to the PIC for a minimum period of three months.
□ Interviewed responsible manager(s) in cargo operations.
□ Examined content of selected records of dangerous goods shipments.
□ Observed cargo acceptance operations (focus: procedures for retention of applicable
information associated with dangerous goods shipments).
□ Other Actions (Specify)
Guidance
A minimum of one copy of each document associated with each dangerous goods shipment is
retained on file for three months or, if required by the State of Flight Departure, a longer period
of time.
CGO 3.2.4 If the Operator transports dangerous goods as revenue or non-revenue cargo, the
Operator shall have procedures to ensure any package, overpack, freight container, or ULD
containing dangerous goods is inspected and is not accepted, unless:
(i) Properly marked and labeled;
(ii) There is no leakage;
(iii) Its integrity has not been compromised. (GM)
Auditor Actions
□ Identified/Assessed procedures for inspection dangerous goods shipments prior to acceptance
for transport.
□ Interviewed responsible manager(s) in cargo operations.
□ Observed cargo acceptance operations (focus: procedures for inspection of dangerous goods
shipments prior to acceptance).
□ Other Actions (Specify)
Guidance
Detailed instructions for acceptance and handling of dangerous goods are contained in DGR
Section 9. This information is not to be interpreted as requiring an operator to accept or transport a
particular article or substance, or as preventing an operator from imposing special requirements on
the transport of a particular article or substance.
CGO 3.2.5 If the Operator transports dangerous goods as revenue or non-revenue cargo on or in
ULDs, the Operator shall have procedures to ensure ULDs containing dangerous goods have a
dangerous goods tag that:
(i) Contains information that is visible and legible;
(ii) Is marked with the class or division number(s) of such dangerous goods;
(iii) If a ULD contains packages bearing a “Cargo Aircraft Only” label, indicates the ULD can
only be loaded onto a cargo aircraft. (GM)
Auditor Actions
□ Identified/Assessed procedures for ensuring ULD containing dangerous goods have a tag in
accordance with applicable requirements.
□ Interviewed responsible manager(s) in cargo operations.
□ Observed cargo acceptance and cargo handling operations (focus: procedures for ensuring
ULDs containing dangerous goods are tagged in accordance with applicable requirements).
□ Other Actions (Specify)
Guidance
The need for procedures would normally apply to any operator that accepts dangerous goods for
transport on or in ULDs to ensure:
• The types of dangerous goods contained in ULDs, as well as any associated restrictions, are
accurately displayed on a ULD tag, which may be placed inside a protective tag holder on the
exterior of the ULD;
• ULDs are only loaded onto aircraft that are compatible with the load and associated
restrictions.
CGO 3.2.6 If the Operator transports dangerous goods as revenue or non-revenue cargo, the
Operator should have a process for retention of the applicable documentation when a dangerous
goods consignment does not pass the acceptance check due to errors or omissions by the shipper.
Such documentation should be retained for a minimum period of three months after the completion of
the acceptance checklist. (GM)
Auditor Actions
□ Identified/Assessed process for retention of documentation for dangerous goods shipments
that do not pass acceptance inspection due to error/omission by shipper.
□ Interviewed responsible manager(s) in cargo operations.
□ Examined selected records of dangerous goods shipments not accepted due to error/omission
by shipper.
□ Observed cargo acceptance operations (focus: process for retention of documentation for
dangerous goods shipments not accepted due to error/omission by shipper).
□ Other Actions (Specify)
Guidance
The intent of this provision is that an operator retains all relevant documentation when a cargo
shipment containing dangerous goods is not accepted (by the operator) due to an error or omission
(by the shipper) in packaging, labeling, marking or documentation.
CGO 3.2.7 (Intentionally open)
CGO 3.2.8 If the Operator transports dangerous goods as revenue or non-revenue cargo, the
Operator shall have a process to ensure, when dangerous goods hazard and handling labels are
found to be missing, illegible or detached from shipments subsequent to the time of acceptance, such
labels are replaced in accordance with the information provided on the Shippers Declaration for
Dangerous Goods. Such requirement for the replacement of labels shall not apply where labels are
found to be missing or illegible at the time of acceptance. (GM)
Auditor Actions
□ Identified/Assessed procedures for ensuring dangerous goods hazard/handling labels are
replaced in accordance with the shipper's declaration when such labels are found to be missing,
illegible or detached.
□ Interviewed responsible manager(s) in cargo operations.
□ Observed cargo acceptance and cargo handling operations (focus: process for replacement of
lost/illegible/detached dangerous goods labels).
□ Other Actions (Specify)
Guidance
Guidance may be found in DGR Section 9.
CGO 3.2.9 If the Operator transports dangerous goods as revenue or non-revenue cargo, the
Operator shall have procedures that ensure English, in addition to the language required by the State
of Origin, is used for markings and transport documents related to the shipment of dangerous
goods. (GM)
Auditor Actions
□ Identified/Assessed procedures for ensuring transport documents/markings for dangerous
goods shipments are in English and language required by State of Origin.
□ Interviewed responsible manager(s) in cargo operations.
□ Examined transport documents/markings associated with selected dangerous goods shipments.
□ Observed cargo acceptance and cargo handling operations (focus: transport
documents/markings for dangerous goods shipments in English and language required by State
of Origin).
□ Interviewed cargo operations personnel that accept/handle dangerous goods shipments.
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of State of Origin.
Guidance may be found in DGR Sections 2 and 7.
CGO 3.2.10 If the Operator transports dangerous goods as revenue or non-revenue cargo, the
Operator shall have procedures that ensure dangerous goods are separated from other cargo or
incompatible materials in accordance with published category restrictions. (GM)
Auditor Actions
□ Identified/Assessed procedures for ensuring dangerous goods are separated from other cargo
or incompatible materials in accordance with published category restrictions.
□ Interviewed responsible manager(s) in cargo operations.
□ Observed cargo handling operations (focus: procedures that ensure dangerous goods
separation from other cargo in accordance with published restrictions).
□ Other Actions (Specify)
Guidance
Loading requirements contained in DGR, 9.3.2 and Table 9.3.A, primarily address dangerous goods
compatibility restrictions on an aircraft. Similar separation requirements are a consideration for
stowage of these materials in the cargo building and during transport to the aircraft.
CGO 3.2.11 If the Operator transports revenue cargo, the Operator shall ensure, at locations
where the operator accepts cargo shipments, notices providing information about dangerous goods
transportation are prominently displayed. (GM)
Auditor Actions
□ Identified/Assessed requirement that ensures notices containing information about dangerous
goods are displayed at locations where cargo shipments are accepted for transport.
□ Interviewed responsible manager(s) in cargo operations.
□ Observed cargo acceptance operations (focus: display of dangerous goods notices).
□ Other Actions (Specify)
Guidance
Where the acceptance of cargo is outsourced to a ground services provider, the provider is
responsible for the display of dangerous goods information notices. However, ultimate responsibility
for the safe transportation of dangerous goods, whether cargo is accepted by the operator or a
ground services provider, always remains with the operator.
CGO 3.2.12 If the Operator transports dangerous goods as revenue or non-revenue cargo, the
Operator shall have procedures to ensure any dangerous goods shipment that appears to be
damaged or leaking:
(i) Is not to be loaded on or into a ULD or delivered to an aircraft;
(ii) Is safely removed from the ULD (or other transport device) by the Provider or other relevant
authority, and safe disposal arranged;
(iii) In the case of leakage, an evaluation is conducted to ensure the remainder of the shipment
is in proper condition for transport by air and that no other package, cargo, ULD, other
transport device has been contaminated or damaged.
Auditor Actions
□ Identified/Assessed procedures for handling/addressing ULDs and leaking/damaged
dangerous goods shipments.
□ Interviewed responsible manager(s) in cargo operations.
□ Examined selected records/documents (focus: handling of leaking/damaged ULDs containing
dangerous goods).
□ Observed cargo handling operations (focus: procedures that address damaged/leaking ULDs
that contain dangerous goods).
□ Other Actions (Specify)
CGO 3.2.13 If the Operator transports dangerous goods as cargo on flights utilizing cargo aircraft,
the Operator shall have procedures to ensure packages or overpacks containing dangerous goods,
and bearing a “Cargo Aircraft Only” label, except those specifically excluded, are transported on
cargo aircraft in accordance with any of the following:
(i) In a Class C compartment, or
(ii) In a ULD container equipped with a fire detection/suppression system equivalent to that
required by the certification requirements of a Class C compartment as determined by the
relevant authority, or
(iii) In such a manner that in the event of an emergency involving such packages or overpacks,
a crew member or other authorized person can access those packages or overpacks, and
can handle and, where size and weight permit, separate such items from other cargo. (GM)
Auditor Actions
□ Identified/Assessed procedure(s) for handling shipments with "Cargo Aircraft Only" labels.
□ Interviewed responsible manager(s) in cargo operations.
□ Observed cargo handling operations (focus: procedures that ensure shipments with "Cargo
Aircraft Only" labels are transported on cargo aircraft in accordance with applicable
requirements).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Cargo Compartment, which includes definitions of compartment
types by classification.
CGO 3.2.14 If the Operator transports dangerous goods as revenue or non-revenue cargo, the
Operator shall have procedures that ensure information on dangerous goods to be loaded on a flight
is communicated to the appropriate person(s) in the load control system. Information to be
communicated shall include the following:
(i) If applicable, Air Waybill number;
(ii) Proper shipping name and/or UN/ID number;
(iii) Class or division, and subsidiary risk(s) corresponding to label(s) applied, and for Class 1,
compatibility group;
(iv) If applicable, packing group;
(v) For non-radioactive material, number of packages, exact loading location and, as
applicable, net quantity or gross weight of each package, except:
(a) For UN 1845, carbon dioxide, solid (dry ice): At the option of the Operator, only the
UN number, proper shipping name, classification, total quantity in each aircraft hold
and offload airport are required;
(b) For UN 3480, (Lithium ion batteries) and UN 3090 (lithium metal batteries): At the
option of the Operator, only the UN number, proper shipping name, class, total
quantity at each loading location, and whether the package must be carried on a
cargo-only aircraft are required. UN 3480 (Lithium ion batteries) and UN 3090
(lithium metal batteries) carried under a State exemption shall meet all requirements
specified in iv) and v).
(vi) For radioactive material, number and category of packages, overpacks or freight containers,
exact loading locations and, as applicable, transport index and dimensions for each
package;
(vii) Any restriction for transport on cargo aircraft only;
(viii) Offload airport;
(ix) If applicable, dangerous goods transported under a state exemption;
(x) If applicable, ULD identification number(s). (GM)
Auditor Actions
□ Identified/Assessed procedure(s) for communication of dangerous goods information to Load
Control.
□ Interviewed responsible manager(s) in cargo operations.
□ Observed cargo handling operations (focus: procedures that ensure dangerous goods cargo
information is communicated to appropriate person(s) in load control system)..
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Load Control.
Certain dangerous goods carried as cargo are not required to appear in the information provided to
the PIC. Refer to DGR, Table 9.5.A.
CGO 3.2.15–3.2.16 (Intentionally open)
CGO 3.2.17 If the Operator transports revenue or non-revenue cargo, the Operator shall have a
process to ensure dangerous goods accidents or incidents are reported to the appropriate authorities
of the State of the Operator and the state in which the accident or incident occurred, and such reports
are in accordance with the reporting requirements of the appropriate authorities.
Auditor Actions
□ Identified/Assessed process for reporting dangerous goods accidents/incidents.
□ Interviewed responsible manager(s) in cargo operations.
□ Examined selected dangerous goods accident/incident reports.
□ Other Actions (Specify)
CGO 3.2.18 If the Operator transports revenue or non-revenue cargo, the Operator shall have a
process to ensure a dangerous goods report is made to the appropriate authorities of the State of the
Operator and the State of Condition Origin:
(i) When undeclared or mis-declared dangerous goods have been discovered in cargo;
(ii) If the Operator transports dangerous goods as cargo, when dangerous goods are
discovered to have been carried when not loaded, segregated, separated and/or secured in
accordance with provisions of the DGR;
(iii) If the Operator transports dangerous goods as cargo, when dangerous goods are
discovered to have been carried as cargo without information as specified in CGO 3.2.14
having been provided to the PIC.
Auditor Actions
□ Identified/Assessed process for reporting dangerous goods discrepancies (as specified)
discovered in cargo.
□ Interviewed responsible manager(s) in cargo operations.
□ Examined document(s) used for reporting dangerous goods discrepancies (as specified)
discovered in cargo.
□ Other Actions (Specify)
CGO 3.3.2 If the Operator transports live animal cargo shipments, the Operator should have
procedures that ensure:
(i) The acceptance and handling of live animals is in accordance with requirements of the Live
Animal Regulations (LAR);
(ii) The IATA Live Animals Acceptance Check List, or equivalent, is utilized for the acceptance
of live animal shipments. (GM)
Auditor Actions
□ Identified/Assessed procedure(s) for acceptance/handling of live animal cargo shipments.
□ Interviewed responsible manager(s) in cargo operations.
□ Observed cargo acceptance and cargo handling operations (focus: live animal cargo
acceptance/handling in accordance with LAR; acceptance checklist is utilized).
□ Other Actions (Specify)
Guidance
The IATA Live Animals Acceptance Checklist is recommended as an effective reference in assisting
shippers, agents and operators in preparing live animal shipments for air transportation.
CGO 3.3.3 If the Operator transports perishable cargo shipments, the Operator should have
procedures that ensure acceptance and handling of perishable cargo shipments is in accordance
with requirements of the Perishable Cargo Regulations (PCR) and other applicable regulations. (GM)
Auditor Actions
□ Identified/Assessed procedure(s) for acceptance/handling of perishable cargo shipments.
□ Interviewed responsible manager(s) in cargo operations.
□ Observed cargo acceptance and cargo handling operations (focus: perishable cargo
acceptance/handling in accordance with PCR/other applicable requirements).
□ Other Actions (Specify)
Guidance
The handling procedures for handling perishable goods and specific responsibilities of an operator
with regard to documentation, packaging and classification are addressed in the PCR. Additional
requirements may be mandated by local regulations.
CGO 3.3.4 If the Operator transports live animal cargo shipments, the Operator should have
procedures that ensure live animal shipments are accompanied by the shipper's certification or
equivalent, as well as other required documents. (GM)
Auditor Actions
□ Identified/Assessed procedure(s) for acceptance of live animal cargo shipments.
□ Interviewed responsible manager(s) in cargo operations.
□ Observed cargo acceptance operations (focus: acceptance procedures that ensure live animal
cargo shipments accompanied by shipper's certification/other required documents).
□ Other Actions (Specify)
Guidance
Documentation required for live animal shipments includes the shipper's certification, air waybill and,
in some situations, CITES (Convention on International Trade in Endangered Species of Wild Fauna
and Flora). Some states have additional requirements, which may include health certificates, export
or import permits. Refer to guidance contained in the LAR, 2.2.
CGO 3.4.2 If the Operator transports time and temperature-sensitive healthcare products (e.g.
pharmaceuticals), the Operator should have procedures that ensure acceptance and handling of
such shipments is in accordance with requirements of the Temperature Control Regulations (TCR)
and other applicable regulations. (GM)
Auditor Actions
□ Identified/Assessed procedure(s) for acceptance/handling of special cargo shipments (focus:
includes procedures for time/temperature healthcare products).
□ Interviewed responsible manager(s) in cargo operations.
□ Observed cargo acceptance and cargo handling operations (focus: procedures for acceptance/
handling in accordance with OM).
□ Interviewed cargo operations personnel that accept/handle special cargo.
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Temperature Control Regulations (TCR).
The procedures for handling time and temperature-sensitive goods, and the specific responsibilities
of an operator regarding documentation, packaging and classification, are addressed in the TCR.
Additional requirements may be mandated by local regulations (e.g. EU GDP, US Pharmacopeia).
Auditor Actions
□ Identified/Assessed procedure(s) for ensuring ULD-related operations are conducted in
accordance with the ULDR or other means acceptable to the Authority.
□ Interviewed responsible manager(s) in cargo operations.
□ Observed cargo handling operations (focus: procedures that ensure ULD-related operations
conducted in accordance with W/B manual/ULDR/other applicable requirements).
□ Other Actions (Specify)
Guidance
All ULDs are required to meet airworthiness requirements when loaded onto an aircraft, either by
certification or by compliance with the Weight and Balance Manual. Adhering to the ULDR is one
means (but not the only means) that ULD operations may be carried out in compliance with the
requirements of the Weight and Balance Manual.
Essential components of ULD operations typically include:
• Minimum training requirements stipulated in the ULDR;
• Continued airworthiness of ULD during operations;
• Limitations applicable to ULDs;
• Adequate supervision and management of all ULD operations.
Guidance may be found in the applicable chapter of the ULDR.
CGO 3.5.2 If the Operator transports revenue or non-revenue cargo utilizing ULDs, the Operator
shall have procedures that ensure ULDs, when accepted and/or loaded for transport, meet safety
requirements pertaining to the loading and securing of cargo. (GM)
Auditor Actions
□ Identified/Assessed procedure(s) for ensuring loaded ULDs meet safety requirements.
□ Interviewed responsible manager(s) in cargo operations.
□ Observed cargo handling operations (focus: procedures for ensuring ULD cargo
loading/securing in accordance with applicable safety requirements).
□ Other Actions (Specify)
Guidance
Detailed instructions for the safe loading and securing of cargo are contained in the ULDR and
address the use of pallets, nets, straps and containers. The ULDR also provides information
regarding ULD limitations.
Each state may have additional or varying regulations and specifications.
Guidance
Refer to the IRM for the definitions of Cargo Restraint System, Combi (Combined Passenger and
Cargo) Aircraft Operations and Supplemental Type Certificate (STC) Holder.
Procedures would typically ensure passengers seated on the same deck and forward of the cargo
are protected through provision of an adequate buffer and/or cargo restraint system.
3.7 Security
CGO 3.7.1 If the Operator transports revenue cargo, the Operator shall ensure security measures
are implemented in cargo facilities in accordance with requirements of the applicable civil aviation
security program. (GM)
Note: This provision is applicable to all facilities where cargo acceptance and/or cargo handling
operations are conducted either by the Operator or by external service providers for the Operator.
Auditor Actions
□ Identified/Assessed processes that ensure implementation of security measures at cargo
facilities (focus: ensures procedures in accordance with the local civil aviation security
program).).
□ Interviewed responsible manager(s).
□ Observed cargo handling operations (focus: implementation of access control measures at
cargo facilities in accordance with applicable security requirements).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Cargo Facility.
The intent of this provision is for the operator to ensure the security of all facilities where cargo
operations are conducted either by the operator or by an external service provider for the operator.
Security measures that address landside and airside facility access for vehicles and personnel, as
well as the protection of cargo so as to prevent acts of unlawful interference, would normally be found
in the applicable civil aviation security program. Such measures address requirements of applicable
regulatory and airport authorities, as appropriate.
CGO 3.7.2 If the Operator transports revenue cargo, the Operator shall ensure procedures are in
place for persons and vehicles with access to security restricted areas (in which there is cargo) to be
subjected to security controls. (GM)
Auditor Actions
□ Identified/Assessed processes that ensure access control procedures are applied to
persons/vehicles with access to security restricted areas that contain known cargo.
□ Interviewed responsible manager(s).
□ Observed cargo handling operations (focus: procedures that ensure persons/vehicles with
access to known cargo are subjected to security controls).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Known Cargo.
The intent of this provision is for an operator to ensure security procedures are applied to persons
and vehicles that have access to security restricted areas where there is cargo (i.e. cargo that has
already been screened or had security controls applied, and/or is under protection to prevent
unlawful interference).
CGO 3.7.3 If the Operator transports revenue or non-revenue cargo, the Operator shall have
processes to ensure cargo is not accepted for transport on an aircraft unless the application of
screening or other security controls is confirmed and accounted for by a regulated agent or an entity
approved by the relevant authority. (GM)
Auditor Actions
□ Identified/Assessed process(es) for ensuring application of screening/security controls for all
cargo.
□ Interviewed responsible manager(s).
□ Examined selected records from regulated agent database.
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definitions of Known Shipper and Regulated Agent.
The term “entity approved by the relevant authority” as used in this provision is non-specific, but
could include, for example, a cargo service provider for the operator or, in certain cases, the operator
itself. As stated, any such entity must be approved by the relevant authority.
Additional guidance may be found in the IATA Security Manual.
CGO 3.7.4 If the Operator transports revenue or non-revenue cargo, the Operator shall have
processes for the acceptance of cargo as follows:
(i) For cargo that can be identified as having the application of screening or other security
controls confirmed or accounted for by a regulated agent or an entity approved by the
relevant authority (known cargo), a process to ensure such cargo is:
(a) Delivered by a regulated agent, a nominated representative of an entity approved
by the relevant authority, or a known representative of the operator;
(b) Free from any signs of tampering;
(c) Accompanied by all required information (paper or electronic) corresponding to the
cargo being delivered, including documentation that details the security status
(e.g. consignment security declaration);
(d) Subjected to additional security controls as required by risk assessment.
(ii) For cargo that cannot be identified as having the application of screening or other security
controls confirmed or accounted for by a regulated agent or an entity approved by the
relevant authority (unknown cargo), a process to ensure such cargo is subjected to
screening or other security controls as accepted by the applicable state. (GM)
Auditor Actions
□ Identified/Assessed process(es) for acceptance of cargo (focus: processes address both
known and unknown cargo).
□ Interviewed responsible manager(s).
□ Examined selected cargo shipment acceptance documents.
□ Observed cargo acceptance operations (focus: acceptance processes for verifying the security
status of known cargo, ensuring application of screening/security control for unknown cargo).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definitions of Known Cargo and Unknown Cargo.
The IATA Security Manual outlines specific provisions covering the basic acceptance of all known
cargo to be carried on commercial passenger flights.
Known cargo, when presented to an operator for transport on an aircraft, has by definition been
subjected to screening or appropriate security controls by a regulated agent, an approved entity or
the operator. An operator, as a minimum, implements the steps specified in this provision to maintain
or protect the “known” status of the shipment from the time the shipment is accepted until it is finally
loaded into an aircraft.
All cargo shipments on which the application of screening or security controls has been confirmed
and accounted for by a regulated agent or approved entity are required to be accompanied by
documentation that states the security status (e.g. consignment security declaration), either in
electronic or paper form.
When cargo has been screened or subjected to other security controls as required by a regulated
agent or an approved entity prior to acceptance by the operator, the operator, among other protective
actions, would typically examine the documentation (e.g. consignment security declaration) and
check the shipment for evidence of tampering prior to loading onto the aircraft.
If for some reason a shipment is not properly maintained or protected in its known status, the
shipment then reverts to unknown cargo. In such case, the operator, in order to return the shipment
to known cargo status, would have to ensure the shipment is again subjected to the application of
screening or other security controls.
CGO 3.7.5 (Intentionally open)
CGO 3.7.6 If the Operator transports revenue or non-revenue cargo, the Operator shall have
processes to ensure cargo for transport on any flight is protected from unauthorized interference from
the point of acceptance after screening or security controls have been applied until departure of the
aircraft.
Auditor Actions
□ Identified/Assessed process(es) for protecting cargo shipments from unauthorized interference
after acceptance.
□ Interviewed responsible manager(s).
□ Observed cargo handling operations (focus: processes that ensure post-acceptance protection
of known cargo from unauthorized interference).
□ Other Actions (Specify)
CGO 3.7.7 If the Operator transports revenue or non-revenue cargo, the Operator shall have a
process to ensure transfer cargo has been subjected to appropriate security controls in accordance
with requirements of the relevant authority before being transported on an international flight. (GM)
Note: Appropriate security controls may have been applied at the point of original uplift.
Auditor Actions
□ Identified/Assessed process(es) to ensure security controls are applied to transfer cargo.
□ Interviewed responsible manager(s).
□ Examined selected records of transfer cargo (focus: verification that security controls have been
applied).
□ Observed cargo handling operations (focus: process to verify appropriate screening/security
controls have been applied to transfer cargo).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Transfer Cargo and Mail.
Applicability
Section 8 addresses the management of operational security in accordance with requirements of an Air
Operator Security Program (AOSP). This section is applicable to all operators.
Individual provisions or sub-specifications within a provision that:
• Begin with a conditional phrase (“If the Operator...”) are applicable if the operator meets the
condition(s) stated in the phrase.
• Do not begin with a conditional phrase are applicable to all operators unless determined otherwise
by the Auditor.
Where operational security functions are outsourced to contracted external service providers, an operator
retains responsibility for the conduct of such functions and will have processes to monitor applicable
external service providers in accordance with SEC 1.11.2 to ensure requirements that affect the security of
operations are being fulfilled.
General Guidance
Definitions of technical terms used in this ISM Section 8, as well as the meaning of abbreviations and
acronyms, are found in the IATA Reference Manual for Audit Programs (IRM).
Auditor Actions
□ Identified individual designated as the head of security.
□ Examined corporate organizational structure.
□ Examined job description of the head of security (focus: functions include
implementation/maintenance of the AOSP).
□ Interviewed responsible manager(s).
□ Other Actions (specify).
Guidance
Refer to the IRM for the definitions of Accountability and Responsibility.
Based on the size, structure and complexity of an operator's organization, the position of head of
security could be filled by a member of senior management that has responsibilities in addition to
security. However the organization is structured, it is important that one senior management official is
the designated focal point for security management on behalf of the operator.
SEC 1.1.3 The Operator shall have a corporate security policy that states the commitment of the
organization to a culture that has security as a fundamental operational priority. Such policy shall be
communicated throughout the organization and commit the organization to:
(i) The provision of resources necessary for the successful implementation of the policy;
(ii) Compliance with applicable regulations and standards of the Operator;
(iii) The promotion of security awareness and the establishment of a security culture;
(iv) The establishment of security objectives and security performance standards;
(v) Continual improvement of the security management system;
(vi) Periodic review of the policy to ensure continuing relevance to the organization. (GM)
Auditor Actions
□ Identified/Assessed corporate security policy (focus: policy identifies security as fundamental
operational priority).
□ Examined examples of security policy communication (focus: policy communicated throughout
organization).
□ Interviewed responsible manager(s).
□ Other Actions (Specify)
Guidance
The security policy of an organization typically expresses the clear and genuine commitment by
senior management to the establishment of a security culture. Such policy also defines the
organization's fundamental approach toward security and how security is expected to be viewed by
employees and external service providers.
Additional elements incorporated into a security policy might include:
• The adoption of industry best practices for security management where warranted;
• Continual management review and improvement of the SeMS and security culture;
• The development of objectives for the measurement of security performance;
• Imperatives for including operational security in the description of duties and responsibilities
of senior and front line management;
• The promotion of a reporting system that encourages the reporting of inadvertent human
error and/or intentional acts of non-compliance;
• Communication processes that ensure a free flow of information throughout the organization.
Auditor Actions
□ Identified/Assessed defined management/non-management authorities and responsibilities
throughout the security management system.
□ Interviewed designated management representative(s).
□ Examined job descriptions of selected management/non-management personnel in security
management.
□ Other Actions (Specify)
Guidance
Refer to Guidance associated with ORG 1.3.1 located in ISM Section 1.
SEC 1.3.2 The Operator shall have a process for delegation of duties and assignment of
responsibilities within the security management system that ensures managerial continuity is
maintained when managers with operational security responsibilities are absent from the workplace.
(GM) ◄
Auditor Actions
□ Identified/Assessed processes for delegation of duties when managers with operational
security responsibilities are absent (focus: processes maintain managerial continuity during
periods when managers are absent).
□ Interviewed designated security management representative(s).
□ Examined selected example(s) of delegation of duties due to absence.
□ Other Actions (Specify)
Guidance
Refer to Guidance associated with ORG 1.3.2 located in ISM Section 1.
Such plan addresses responsibilities associated with management positions (not individuals) under
the AOSP and ensures proper management of operational security functions is always in place.
SEC 1.3.3 The Operator shall ensure a delegation of duties and assignment of responsibility for
liaison with applicable aviation security authorities and other relevant external entities. (GM) ◄
Auditor Actions
□ Identified position(s) with authority for liaison with regulators and other external entities.
□ Interviewed designated management representative(s).
□ Interviewed manager(s) with authority for liaison with regulators and other external entities.
□ Examined job description for selected management positions (focus: authority/responsibility for
liaison with external entities).
□ Other Actions (Specify)
Guidance
Although motives might be different, all stakeholders share a similar interest in ensuring the security
of the aviation industry. However, the potential problem of gaps or overlap in responsibilities and/or
coverage may exist when more than one entity is handling security. It is crucial for state, airport and
airline security officials to establish clear jurisdictional boundaries to ensure all entities understand
where their respective jurisdictions begin and end.
Whereas gaps in security create obvious problems and expose the entire aviation infrastructure to
threats, the presence of unnecessary overlap by different security groups can also lead to problems.
Without proper coordination, the presence of multiple entities providing security services could lead
to inaccurate assumptions that might, in fact, result in unintended gaps in the security web due to a
reduction of services. Also, multiple groups doing the same job could lead to conflicts of authority,
which would detract from the required focus on aviation security.
It is important that there is effective communication between airport security and airline security
management. An Airline Operators Committee typically offers a viable platform for airlines and an
airport authority to express their respective views on security and identify areas of deficiency. Such
committee might also serve as a useful forum for coordination between airlines and airports to
develop and implement a seamless security system with no gaps and appropriate overlap.
With regards to state involvement, the creation of an Airport Security Committee (ASC) might be
suggested since the group would focus solely on security and address only security issues. An ASC
typically reports (formally or informally) to the National Civil Aviation Security Committee.
Air carriers are advised to participate in both the Airline Operators Committee and the ASC, either
directly or via representation by other carriers or stakeholders.
1.4 Communication
SEC 1.4.1 The Operator shall have a communication system that enables an exchange of
operational security information throughout the management system and all areas where operations
are conducted. (GM) ◄
Auditor Actions
□ Identified/Assessed system(s) for communicating information relevant to security operations
(focus: capability for communicating information relevant to operations within the security
organization).
□ Interviewed designated management representative(s).
□ Examined examples of information communication in security operations.
□ Interviewed selected non-management operational personnel in security operations.
□ Other Actions (Specify)
Guidance
The intent of security communication is to foster a positive security culture in which all employees
receive ongoing information on security issues, security metrics, specific security risks existing in the
workplace, and initiatives to address known security issues. Such communication typically conveys
security-critical information, explains why particular actions are taken to improve security, and why
security procedures are introduced or changed.
Security information that is sensitive is typically drafted and circulated in a manner that is in
accordance with applicable security information protocols. Communication of such information is
normally limited only to those with an operational need to know.
Any system would have to be able to address the varying degree of urgency with which security
information needs to be circulated.
Security Intranet Site
A corporate security department website is one method of disseminating security information to
operational personnel. Different levels of access might be required in order to control the access to
restricted information to those with a “need to know.”
Corporate Manual System
An operator's manuals and regulations are the formal system of coordinating and communicating the
policies, procedures and significant guidance necessary to ensure the operator's mission is carried
out in a consistent and integrated manner.
Security Bulletins
Security bulletins, which are typically issued by the corporate security department or by operational
departments within the operator, might specify action and/or contain general information. Issuance of
bulletins electronically (e.g. email) is an efficient means of ensuring all personnel with a “need to
know” are made aware of new or amended security information in a timely manner.
Refer to Guidance associated with ORG 1.4.1 located in ISM Section 1.
SEC 1.9.2 The Operator shall have processes to monitor and assess its SeMS processes in order
to maintain or continually improve the overall effectiveness of the SeMS. (GM) ◄
Auditor Actions
□ Identified/Assessed SeMS review process (focus: processes for monitoring and assessing
SeMS to maintain/improve security performance)
□ Interviewed AE and/or designated management representative(s).
□ Examined selected examples of output from SeMS review process (focus: changes
implemented to maintain/improve organizational security performance).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Safety Management System (SMS)
Monitoring and assessing the effectiveness of SeMS processes would typically be the function of a
strategic committee of senior management officials that are familiar with the workings and objectives
of the SeMS.
Depending on the operator’s organizational structure, the effectiveness of SeMS may be monitored
and assessed by the same executive group that is responsible for the safety management system
(SMS).
Refer to guidance associated with ORG 1.5.2 located in ISM Section 1. Such guidance addresses
continual improvement of SMS, but can be adapted and applied for continual improvement of SeMS.
SEC 1.10.2 The Operator shall have a process for addressing findings resulting from audits of
operational security functions that ensures:
(i) Identification of root cause(s);
(ii) Development of corrective action, as appropriate, to address findings;
(iii) Implementation of corrective action in appropriate operational security area(s);
(iv) Evaluation of corrective action to determine effectiveness. (GM) ◄
Auditor Actions
□ Identified/Assessed process for addressing audit findings within operational security.
□ Interviewed responsible quality assurance program manager.
□ Examined selected audit reports/records (focus: identification of root cause,
development/implementation of corrective action, follow-up to evaluate effectiveness).
□ Other Actions (Specify)
Guidance
Refer to Guidance associated with ORG 3.4.3 located in ISM Section 1.
SEC 1.10.3A The Operator shall have a process to ensure significant issues arising from quality
assurance audits of operational security functions are subject to a regular review by senior security
management. (GM) ◄
Auditor Actions
□ Identified/Assessed process to inform senior security management of significant issues
identified through quality assurance audits (focus: continual improvement of quality assurance
program).
□ Interviewed responsible quality assurance program manager.
□ Examined selected records/documents of management review of security organization quality
assurance program issues (focus: specific issues/changes identified and implemented to
improve quality assurance program).
□ Other Actions (Specify)
Guidance
In order to ensure proper implementation of corrective actions following the identification of gaps or
deficiencies through quality assurance audits, it is important that senior security management is
made aware of overall audit reports and especially of any significant issue(s) identified.
Senior security management officials have the authority and available expertise to quickly resolve
any deficiency in order to prevent re-occurrences and ensure that the corrective actions implemented
are commensurate to the gaps or issues identified.
Auditor recommendations contained in a report provide the basis for possible changes within the
system. However, for various reasons, the adoption or implementation of recommendations made by
auditors may not always be feasible. Therefore, the determination of a need for corrective or
preventive action, and the actual implementation of such action, would typically be coordinated
between the Head of Security (or appointee) and those operational managers directly responsible for
the safety and security of operations.
Refer to Guidance associated with ORG 3.4.4 located in ISM Section 1.
SEC 1.10.3B The Operator shall have an audit planning process and sufficient resources,
including auditors as specified in ORG 3.4.12, to ensure audits are:
(i) Scheduled in accordance with a security risk assessment at intervals to meet regulatory and
management system requirements;
(ii) Completed in accordance with scheduled intervals (subject to a change in risk). (GM)
Auditor Actions
□ Identified/Assessed planning process for quality assurance auditing of security functions.
□ Identified/Assessed resources (human and physical) allocated and available for auditing.
□ Interviewed responsible quality assurance program manager.
□ Crosschecked audit plan with selected audit reports (focus: completion of audits by planned
dates).
□ Other Action (Specify)
Guidance
Refer to Guidance associated with ORG 3.4.10 located in ISM Section 1.
Quality Control
SEC 1.10.4 The Operator shall have a process for conducting regular risk-based or event-driven
security surveys that identify needs and weaknesses of the AOSP, including operational security
procedures and infrastructure. (GM)
Auditor Actions
□ Identified the process of performing security surveys.
□ Interviewed responsible manager(s).
□ Examined selected security questionnaires/reports.
□ Other Actions (Specify)
Guidance
As defined by ICAO, a security survey is an evaluation of security needs, including the identification
of vulnerabilities that could be exploited to carry out an act of unlawful interference. Recommended
corrective actions are developed to address any identified vulnerabilities.
Surveys of security measures are necessary to ensure the adequacy and continued effectiveness of
security programs, and further ensure such measures and procedures remain in compliance with the
appropriate legislation. The scope of such surveys may be limited by state authorities.
SEC 1.10.5 If required and/or authorized by the aviation security authority, the Operator shall have
a process for conducting security tests that assess the effectiveness and proper implementation of
security controls of which the Operator is in direct control. (GM)
Auditor Actions
□ Identified/Assessed process for conducting security tests required and/or authorized by the
aviation security authority.
□ Interviewed responsible manager(s).
□ Examined selected security test result reports, other evidence of evaluation of effectiveness.
□ Other Actions (Specify)
Guidance
A security test is a simulated act of unlawful interference against existing security measures, carried
out covertly by persons using an approved test object concealed in their baggage or on their person.
Similar tests are also sometimes performed on cargo shipments and in aircraft. Tests may be used
for ensuring alertness of security personnel, which might be considered with caution because the
results of testing could degrade the motivation of such personnel.
An effective testing program ensures the administration of tests:
• Are only conducted where permitted by the laws of the state(s) where such tests are
conducted;
• Do not jeopardize the safety of persons;
• Do not jeopardize the safety of aircraft or airport facilities;
Normally, an operator obtains a written undertaking that ensures service providers are familiar and
comply with standards of the operator and local regulatory requirements.
An important aspect to be monitored by the operator would be the security training provided to
personnel of the service provider(s).
The use of a registered ISAGO provider typically signifies that the provider is in conformity with basic
industry security requirements.
Refer to Guidance associated with ORG 3.5.1 located in ISM Section 1.
SEC 1.11.2 If the Operator has external service providers conducting outsourced operational
security functions, the Operator shall have processes to monitor such external service providers to
ensure compliance with either the contract or agreement as specified in SEC 1.11.1, or:
(i) The AOSP of the Operator;
(ii) Requirements of applicable aviation security authorities. (GM) ◄
Auditor Actions
□ Identified/Assessed processes used for monitoring external service providers (focus:
monitoring process ensures provider fulfils applicable safety/security requirements).
□ Interviewed responsible manager(s).
□ Examined selected records/reports of monitoring of external service providers.
□ Other Actions (Specify)
Guidance
The contract and/or agreement may contain those aspects of the Security Program and/or regulatory
requirements to be undertaken by the external service provider. In most cases only one or two
aspects of the AOSP may be involved, which would negate the requirement to provide or monitor
compliance with the entire AOSP.
Examples of activities that might be used to verify such compliance include:
• Periodic quality assurance audits of providers conducted by the operator using either
corporate or local resources;
• Reports submitted to the operator by the provider detailing self-audit schedules and results;
• Quality control functions (e.g. security surveys/tests) conducted jointly by the operator and
provider.
The use of a registered ISAGO provider typically signifies that the provider is in conformity with basic
industry security requirements.
Refer to Guidance associated with ORG 3.5.2 located in ISM Section 1.
SEC 1.11.3 (Intentionally open)
SEC 1.11.4 If the Operator has operational security functions conducted by external organizations
not under the control of the Operator, the Operator should have methods, as permitted by law or the
applicable civil aviation security authority, for the monitoring of such functions to ensure security
controls are implemented to prevent acts of unlawful interference. (GM)
Auditor Actions
□ Identified operational security functions conducted by external organizations not under the
control of the operator.
□ Identified/Assessed methods used by the operator for monitoring functions to ensure that
security controls are implemented.
□ Interviewed responsible manager(s).
□ Examined selected records of monitoring the external organizations that conduct security
functions.
□ Other Actions (Specify)
Guidance
Security procedures may be performed by law enforcement agencies, civil aviation authorities,
airport authorities or other organizations not under the control of or under contract to the operator.
When the operator has no direct authority over the organization performing the security measures, it
may not be permitted to perform oversight activity on the security functions.
If permitted by law or the applicable civil aviation security authority, the operator might assess the
quality of such security procedures through the use of tests, surveys and/or exercises.
This recommended practice is applicable to all security procedures required under the security
program of the State, state of operation or the operator.
Refer to ORG 3.1.3 and ORG 3.1.4 located in ISM Section 1, which address operational safety
reporting systems.
SEC 1.12.2 The Operator should have a process to ensure security incidents and acts of unlawful
interference that have been reported by personnel in accordance with SEC 1.12.1 are reviewed by
operational and security management to ensure:
(i) Root cause is identified;
(ii) Corrective action is determined;
(iii) When applicable, corrective action is implemented and monitored to ensure effectiveness in
preventing future incidents. (GM)
Auditor Actions
□ Identified/Assessed process for reviewing security reports submitted by operational personnel.
□ Interviewed responsible manager(s).
□ Examined selected reports to verify root causes identified, corrective actions
determined/monitored.
□ Other Actions (Specify)
Guidance
An effective system provides for a review and analysis of each report to determine the risk
associated with the reported issue and, where applicable, ensures development and implementation
of appropriate action by responsible management to correct the situation.
The security training program is typically integrated into the normal training curriculum for operational
personnel, and need not be stand-alone training.
The proportion of theoretical and practical training is typically based on requirements of the State. For
certain functions or duties there may not be a practical component.
The scope of recurrent security training, as well as the specific subject matter included, may vary in
accordance with requirements of the applicable authorities and the security policy of the operator.
SEC 2.1.2 If the Operator has operational security functions conducted by external service
providers selected by the Operator (outsourcing), the Operator shall have a process to ensure such
external service providers have a security training program that:
(i) Is acceptable to the Operator;
(ii) Consists of initial and recurrent training; and
(iii) Includes, as appropriate, theoretical and practical training.
Auditor Actions
□ Identified/Assessed process(es) to ensure external service providers have security training
programs.
□ Interviewed responsible manager(s).
□ Examined selected evidence that ensures external service provider(s) have a security training
program.
□ Other Actions (Specify)
SEC 2.1.3 (Intentionally open)
SEC 2.1.4 The Operator shall ensure personnel who perform security functions, crew members
and appropriate operational personnel, as specified in SEC 2.1.1, complete recurrent security
training on a frequency in accordance with requirements of the security program of the State and, if
applicable, other states where operations are conducted or, if there is no regulatory mandate, not
less than once every 36 months. (GM)
Auditor Actions
□ Identified requirements mandating frequency of recurrent training (focus: compliance with
requirements of the State and other relevant states, but not less than once every 36 months).
□ Examined selected recurrent training records, material and schedules.
□ Interviewed responsible manager(s).
□ Other Actions (Specify)
Guidance
The scope of recurrent security training, as well as the specific subject matter included, may vary in
accordance with requirements of the applicable authorities and the security policy of the operator.
SEC 2.1.5 If the Operator manages or operates a security screening system, the Operator shall
ensure personnel who manage or operate the screening system:
(i) Are approved and/or certified in accordance with requirements of the applicable aviation
security authority;
(ii) Complete initial and recurrent training that includes training in the identification of
explosives, weapons or other dangerous items or devices. (GM)
Auditor Actions
□ Identified security screening system(s) managed or operated by operator..
□ Identified/Assessed screener approval/certification program (focus: in compliance with
requirements of all applicable aviation securities authorities).
□ Interviewed responsible manager(s).
Guidance
Security awareness training revolves around ensuring all personnel have a positive attitude about
security. The focus of training to achieve such awareness will vary by region or company and may be
influenced by cultural, religious and other factors. Such training is typically tailored to promote an
organizational security culture and to be effective in the environment in which it is to apply. Some
operators, depending on the individual organizational structure, may find it more appropriate to have
multiple security awareness training courses developed specifically for each operating area. Security
awareness training may be integrated into other job-related training courses (as opposed to a
standalone course).
Typically, operational personnel that complete security awareness training are crew members, front
line ground handling personnel and all personnel that implement security controls.
3 Security Operations
In some environments, it would be prudent not to leave an in-service aircraft unattended. Precautions
may be taken to prevent unauthorized access to aircraft that are not in service and are parked and
unattended. For example, all external doors may be locked, all stairs and loading bridges are
removed (or locked) and any steps left near the aircraft are immobilized.
Passengers boarding or disembarking from flights using the apron are to be supervised when
passing from the terminal building to the aircraft. Such measures are applied whether the passengers
are walking or are being transported in vehicles.
Particular care is taken to ensure only crew members, authorized representatives and officials, and
bona fide passengers are permitted access to the aircraft.
SEC 3.1.3 The Operator shall ensure access control measures are in place to prevent the
introduction of unauthorized weapons, explosives or other dangerous devices or items on board an
aircraft by persons other than passengers. (GM)
Auditor Actions
□ Identified/Assessed process(es) to prevent the introduction of unauthorized weapons,
explosives or other dangerous devices on board an aircraft.
□ Examined records of the capture and prevention of unauthorized weapons, explosives or other
dangerous devices on board an aircraft.
□ Interviewed responsible manager(s).
□ Other Actions (Specify)
Guidance
An effective method to deter or detect illegal access to aircraft is the implementation of frequent but
irregularly timed patrols by security personnel. This is particularly important when operations are at
their lowest levels and aprons and hangar areas are least frequented. Such patrols are normally
conducted by airport personnel.
Additional measures to prevent unauthorized access to passenger aircraft may include:
• Parking aircraft in a well-lit area; adding security lighting, if necessary;
• When possible, parking aircraft in an observable area;
• Parking aircraft away from fences or buildings that might provide easier access;
• For aircraft parked overnight, depending on the assessed risk at the location, applying a
tamper-evident seal to all exterior doors or verifying the identity of all persons who access
the aircraft to ensure a legitimate reason for accessing the aircraft;
• For aircraft parked remotely from a loading bridge:
– Closing all exterior doors and exterior hatches of the aircraft;
– Removing all stairs;
– Ensuring no portable stairs, lift devices or passenger transfer vehicles are in the
immediate vicinity of the aircraft.
• For aircraft parked with access to a loading bridge:
– Closing all exterior hatches of the aircraft;
– Closing all exterior doors of the aircraft not served by a bridge;
– Locking the door between the terminal and the bridge;
– Ensuring no portable stairs, lift devices or passenger transfer vehicles are in the
immediate vicinity of the aircraft;
– Locking or keeping under constant surveillance doors that provide access to the
bridge from the apron or retracting the bridgehead from the aircraft and deactivating
the bridgehead positioning controls.
Technical equipment used for the screening of persons and baggage has certain limitations. Archway
metal detectors and hand-held metal detectors, for example, cannot detect non-metallic weapons
and explosives. Even conventional X-ray equipment does not always image or define explosive
material effectively. To compensate for such limitations, or to introduce a random element into the
selection process, it may be advisable to conduct an additional search of passengers and cabin
baggage after they have been screened. The additional screening can be performed by hand or by
technical means, such as explosive trace detection (ETD), full-body X-ray, explosive particle or vapor
detection portals and/or other approved advanced technological methods.
Specific guidelines and procedures are developed and training given to personnel, for addressing
persons with special needs.
SEC 3.4.2 If the Operator transports supernumeraries, the Operator shall have a process to ensure
such personnel and their personal belongings are subjected to screening or other appropriate
security controls prior to boarding the aircraft. (GM)
Auditor Actions
□ Identified/Assessed process(es) to ensure all supernumeraries and their belongings are
subjected to screening and other appropriate security controls prior to boarding an aircraft.
□ Interviewed responsible manager(s).
□ Observed passenger/baggage handling operations (focus: supernumeraries/personal
belongings are subjected to screening or other security controls prior to aircraft boarding).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Supernumerary.
SEC 3.4.3 If the Operator conducts passenger flights, the Operator shall have a process to ensure
transfer and transit passengers and their cabin baggage either:
(i) Are subjected to screening prior to boarding a passenger aircraft, or
(ii) Have been screened to an appropriate level at the point of origin and subsequently
protected from unauthorized interference from the point of screening at the originating
airport to the departing aircraft at the transfer or transit airport. (GM)
Auditor Actions
□ Identified process(es), when required, to ensure all passengers and their cabin baggage are
screened prior to boarding a passenger aircraft.
□ Identified/Assessed criteria used to determine whether passengers and cabin baggage are re-
screened at the transit/transfer airport or if one-stop-security is applied.
□ Observed screening measures being implemented for transfer and transit passenger and their
cabin baggage, as applicable.
□ Interviewed responsible manager(s).
□ Other Actions (Specify)
Guidance
Refer to the IRM for the definition of Unauthorized Interference.
Transit and transfer passengers and their cabin baggage may not require screening prior to
admission to an airport sterile area if, in the judgment of the appropriate authority for security, the
standard of screening en route and at the airport of embarkation is equal or comparable to that of the
admitting state. However, measures ought to be established to ensure transit or transfer passengers
do not take unauthorized articles on board an aircraft.
SEC 3.4.4 If the Operator conducts passenger flights, the Operator shall have a process to ensure
passengers and their cabin baggage are subjected to additional security controls in accordance with
requirements of the applicable aviation security authority when flights are under an increased
security threat. (GM)
Auditor Actions
□ Identified/Assessed process(es) for ensuring additional security controls for flights under
increased security threat.
□ Observed additional passenger and cabin baggage security measures implemented based on
the various levels of increased security threats.
□ Interviewed responsible manager(s).
□ Other Actions (Specify)
Guidance
In the case of a general (i.e. non-specific) intermediate threat level, in addition to the baseline
passenger and carry-on screening procedures, the following additional measures may be
implemented:
• Continuous random searching of passengers by hand (or by approved technological
methods) either at the departure gate (where airport facilities permit) or other suitable
location(s).
• Continuous random searching of cabin baggage by hand (or by approved technological
means) either at the departure gate (where airport facilities permit) or other suitable
location(s).
In the case of a general (i.e. non-specific) high threat level, additional measures such as the following
may be introduced:
• All departing passengers are searched again by hand or screened with metal detection
equipment at the departure gate before being permitted to board the aircraft;
• All cabin baggage is subjected to an additional search by hand or by X-ray equipment, either
at the departure gate (where airport facilities permit) or other suitable location(s), before
being permitted to be carried on board the aircraft.
If a threat is specific to a certain object (e.g. liquid explosives), then more specific countermeasures
than above would need to be implemented.
To facilitate additional screening, earlier close-out of passenger check-in operations is a
consideration.
SEC 3.4.5 If the Operator conducts passenger flights, the Operator shall have a process to ensure
passengers and their cabin baggage, which have already been subjected to screening, are:
(i) Protected from unauthorized interference from the point of screening until they board a
passenger aircraft;
(ii) Subjected to re-screening if the potential for unauthorized interference has been determined
to exist. (GM)
Auditor Actions
□ Identified/Assessed process(es) to determine if passenger re-screening is required.
□ Identified/Assessed methods used to ensure passengers are protected from unauthorized
interference until they board the aircraft.
□ Identified/Assessed process(es) used to determine if unauthorized interference may have been
possible.
□ Interviewed responsible manager(s).
□ Observed passenger/baggage handling operations (focus: process for protecting
passengers/cabin baggage from unauthorized interference after screening until aircraft
boarding).
□ Other Actions (Specify)
Guidance
For domestic flights, the separation of screened and unscreened passengers and their carry-on
baggage is sufficient.
For international flights, if the design of the airport permits, to ensure separation from departing
passengers who have been subjected to screening, arriving passengers disembark from an aircraft in
accordance with any of the following:
• On a level different from the departure boarding area, or
• Through an area isolated from the departure boarding area; or
• Into an area of the airport dedicated to arriving passengers only.
If physical means to avoid contact between departing and arriving passengers is not possible,
passenger mix may be prevented by restricting access to the departure lounge until all arriving
passengers have cleared the area. This solution may not be possible in large airport terminals with
many gates close to each other.
The major concern regarding the sterility of arriving passengers will most likely be associated with
flights that have originated in states where screening requirements are considered to be inadequate
by the State of Flight Arrival. In order to limit the disruption of passenger flow within a terminal,
consideration might be given to assigning the disembarkation of all such flights to a common sector
or area of the airport or terminal that can be cordoned off and/or monitored by security personnel.
Where passengers are arriving from a state where screening is considered by the State of Flight
Arrival to be equal or better, arriving and departing passengers can mix.
In order to limit the disruption of passenger flow within a terminal, consideration might be given to
assigning the disembarkation of all such flights to a common sector or area of the airport or terminal
that can be cordoned off and/or monitored by security personnel.
SEC 3.4.6 If the Operator conducts passenger flights, the Operator shall have measures
established at each transit airport to protect the aircraft and passenger cabin baggage from
unauthorized interference. (GM)
Auditor Actions
□ Identified/Assessed the process(es) to protect the integrity of the operator security system at
transit airports.
□ Identified the process(es) to ensure the security of aircraft and transit passengers and their
cabin baggage.
□ Observed the presence of security system that protects aircraft and transit passengers and their
cabin baggage.
□ Interviewed responsible manager(s).
□ Other Actions (Specify)
Guidance
Special precautions taken to control transfer and transit passengers and their baggage include
surveillance of transit areas (arrival/departure halls) and baggage storage and sorting areas. Where
transit or transfer passengers have access to hold baggage or baggage collection areas,
re-screening is necessary before re-boarding or having any contact with other screened passengers.
The objective is to ensure transit and transfer passengers do not mix with unscreened passengers.
SEC 3.4.7 The Operator shall have a policy and procedures to refuse transportation to any person
that does not consent to a search of his or her person or property in accordance with the AOSP. (GM)
Auditor Actions
□ Identified/Assessed the policy and procedures used to deny boarding of a passenger refusing
to consent to security searching or other security control.
□ Examined selected documents used when right to deny boarding is communicated to
passengers.
□ Interviewed responsible manager(s).
□ Other Actions (Specify)
Guidance
Persons who refuse to undergo screening before boarding or entering an aircraft are denied boarding
and not allowed to pass the point of search. Additionally, such persons, or others who might be
denied passage for other security reasons, are referred to policing authority officials, if required by
law.
Accordingly, there is usually a well-defined escort policy that is provided to the appropriate
immigration authorities. Females travelling under the provisions of a judicial order may require a
female escorting officer as a member of the escort team.
Special provisions may exist for flights where transportation of multiple inadmissible passengers is
required.
Although a person is involved in travel in response to a judicial or custodial order, while in flight, such
passenger is always under the control of the PIC and crew of the aircraft.
SEC 3.5.2 (Intentionally open)
SEC 3.5.3 If the Operator conducts passenger flights, the Operator shall have a process to ensure
procedures are in place for the notification of the PIC, prior to the commencement of a flight, when
passengers are to be transported who are obliged to travel because they have been the subject of
judicial or administrative proceedings.
Auditor Actions
□ Identified/Assessed process(es) to inform the PIC of the presence of passengers subjected to
administrative or judicial proceedings.
□ Examined selected records of PIC notifications.
□ Interviewed responsible manager(s).
□ Other Actions (Specify)
This provision also refers to a person who is employed by a courier service operator and travels as a
passenger or crew member, and who checks a courier shipment in as hold baggage. Such baggage
is then screened under the same requirements that apply to all hold baggage.
SEC 3.6.2 If the Operator conducts domestic passenger flights, the Operator should have a
process to ensure originating hold baggage is subjected to screening prior to being loaded into an
aircraft for a domestic passenger flight.
Auditor Actions
□ Identified/Assessed process(es) for ensuring all originating checked baggage is subjected to
screening prior to being loaded.
□ Observed the hold baggage screening process.
□ Interviewed responsible manager(s).
□ Observed passenger/baggage handling operations (focus: originating hold baggage is subjected
to screening prior to being loaded onto an aircraft).
□ Other Actions (Specify)
SEC 3.6.3 If the Operator conducts international passenger flights, the Operator shall have a
process to ensure hold baggage is protected from unauthorized interference from the point it is
screened or accepted into the care of the Operator until departure of the international flight
transporting the baggage.
Auditor Actions
□ Identified/Assessed process(es) to ensure screened checked baggage is protected from
unauthorized interference.
□ Observed the protection of hold baggage from unauthorized interference until departure of the
aircraft transporting the baggage.
□ Interviewed responsible manager(s).
□ Observed passenger/baggage handling operations (focus: process for protecting hold baggage
from unauthorized interference after screening or acceptance by the operator, until loaded onto
an aircraft for an international passenger flight).
□ Other Actions (Specify)
SEC 3.6.4 – 3.6.5 (Intentionally open)
SEC 3.6.5 (Intentionally open)
SEC 3.6.6 If the Operator conducts international passenger flights, the Operator shall have a
process to ensure procedures are in place to prevent items of hold baggage from being transported
on such flights unless such items have been:
(i) Individually identified as either accompanied or unaccompanied baggage;
(ii) Subjected to appropriate security controls based on risk assessment. (GM)
Auditor Actions
□ Identified/Assessed process(es) to identify if hold baggage is accompanied or unaccompanied.
□ Identified appropriate security controls performed on unaccompanied checked baggage before
being transported on international flights.
□ Interviewed responsible manager(s).
□ Observed passenger/baggage handling operations (focus: process for ensuring passenger-
baggage reconciliation for international flights).
□ Other Actions (Specify)
Guidance
An operator typically has a system in place to identify a passenger who fails to board a flight after
check-in or fails to re-board a flight at a transit stop. In an effort to reduce the risk, the aviation
industry initially introduced a system where passengers identified their bags before loading. That
system can still be invoked at remote locations, if no other procedure exists.
The intent of this provision is for an operator to have a process to verify and confirm, before a flight
departs, that only the baggage of boarded passengers has been uplifted.
Applicable primarily to flights operated solely for the purpose of transporting passengers on a charter
basis (e.g. executive charters, VIP charters), if permitted by the State, the requirement for passenger
baggage reconciliation procedures may be rescinded. Additionally, as permitted by the State,
baggage reconciliation procedures could be rescinded:
• For specific passengers designated as VIPs (e.g. heads of state) who are being transported
on scheduled passenger flights;
• When baggage and passengers are separated for reasons beyond the control of the
passengers (e.g. mishandled bag, involuntary offloading due to an oversold flight, weather
diversions, operational aircraft change, passenger re-routing, weight restrictions).
SEC 3.6.7 If the Operator conducts international passenger flights, the Operator shall have a
process to ensure procedures are in place to record information associated with international hold
baggage that has met criteria in accordance with SEC 3.6.1 and 3.6.6.
Auditor Actions
□ Identified hold baggage criteria specified in SEC 3.6.1 and 3.6.6.
□ Identified/Assessed process(es) for recording information associated with hold baggage that
has met criteria in accordance with SEC 3.6.1 and 3.6.6.
□ Interviewed personnel that authorize the transport of unaccompanied hold baggage.
□ Interviewed responsible manager(s).
□ Examined selected unaccompanied hold baggage screening records.
□ Other Actions (Specify)
SEC 3.6.8 If the Operator conducts passenger flights, the Operator shall have a process to ensure
secure storage areas have been established where mishandled passenger baggage may be held
until forwarded, claimed or disposed of in accordance with local laws. (GM)
Auditor Actions
□ Identified/Assessed process(es) to provide secure storage of mishandled hold baggage.
□ Interviewed responsible manager(s).
□ Observed passenger/baggage handling operations (focus: secure areas are used for holding
mishandled baggage until forwarded, claimed or disposed of).
□ Other Actions (Specify)
Guidance
Refer to the IRM for definitions of Mishandled Baggage, Unidentified Baggage and Unclaimed
Baggage.
Mishandled baggage is usually the result of the baggage having:
• Been incorrectly tagged;
• Arrived without a tag;
• Missed a connecting flight;
• Been carried on the wrong flight.
Such baggage is held in a locked and secure storage cage or room. Access and key control is
properly supervised and the baggage subjected to additional screening before being loaded into an
aircraft.
Unclaimed baggage is kept for a period of time, as prescribed by the local authority, and disposed of
through that authority as unclaimed property.
The process for forwarding mishandled baggage is described in IATA Resolution 743a.
Preflight Procedures/Activities
Focus of Observation Observed ISARPs Notes/Comments
Use/application of ATL/CDL/MEL; entry of FLT 3.8.1
Yes No
information in accordance with OM FLT 3.8.2
PIC option to reject aircraft for
Yes No FLT 3.8.3
airworthiness/maintenance issues
FLT 3.8.6
Aircraft exterior inspection; safety-critical areas Yes No FLT 3.8.7A
Flight deck emergency equipment/systems
Yes No FLT 3.8.7B
inspection
Cabin emergency equipment/systems inspection Yes No FLT 3.8.8
Cargo/supernumerary compartment(s)
Yes No FLT 3.8.9
inspection (cargo aircraft only)
Validation of navigation database Yes No FLT 3.5.2
Coordination for potential cabin evacuation FLT 3.9.2
Preparation/acceptance of loadsheet Yes No FLT 3.7.3
Flight crew notification of onboard weapons Yes No FLT 3.9.4
Operations in ground icing conditions; FLT 3.9.6
Yes No
de-/anti-icing procedures FLT 3.9.7
Notification/acceptance of onboard dangerous
Yes No FLT 3.9.8
goods
Preflight Preparation
Focus of Observation Observed ISARPs Comments
Preflight preparation duties/responsibilities Yes No FLT 3.5.1
Use/applicability of OFP Yes No FLT 3.7.6
Determination of relevant airport RVR
Yes No FLT 3.6.4
requirements/associated limitations
Determination of relevant approach/landing RVR
Yes No FLT 3.6.5*
requirements
Determination of minimum dispatch/departure
Yes No FLT 3.7.1
fuel
Use/application of ATL/CDL/MEL; entry of
Yes No FLT 3.8.1
information in accordance with OM
* Recommended Practice
Emergency Procedures
Focus of Observation Observed ISARPs Comments
Procedures that specify cabin crew
functions/actions for an emergency, emergency Yes No CAB 3.2.1
evacuation situation
Cabin crew procedures for coordinated/
expeditious cabin evacuation during aircraft Yes No CAB 3.2.2
fueling operations with passengers on board
GSE Operations
Focus of Observation Observed ISARPs Comments
Implementation of safety practices/procedures
Yes No GRH 3.5.1*
for operation of GSE
GSE operated by qualified/authorized personnel Yes No GRH 3.5.2*
GSE is serviceable/in good mechanical
Yes No GRH 3.5.3
condition; completed maintenance recorded
* Recommended Practice