Skip to content

A gradual release of Avioverse begins in October 2026. Request early access →

ORO.FC.232 EBT programme assessment and training topics

ANNEX III (Part-ORO) · Regulation (EU) No 965/2012 · EAR revision 27 Mar 2026

IRImplementing rule

ORO.FC.232EBT programme assessment and training topics

(a)The operator shall ensure that each pilot is exposed to the assessment and training topics.

(b)The assessment and training topics shall be:

(1)derived from safety and operational data that are used to identify the areas for improvement and prioritisation of pilot training to guide in the construction of suitable EBT programmes;

(2)distributed across a 3-year period at a defined frequency;

(3)relevant to the type or variant of aircraft on which the pilot operates.

IR · ORO.FC.232 — Regulation (EU) No 965/2012 · Regulation (EU) 2020/2036 · Air OPS Easy Access Rules · EAR revision 27 Mar 2026

AMCAcceptable means of compliance

AMC1 ORO.FC.232EBT programme assessment and training topics

Show the text

ASSESSMENT AND TRAINING TOPICS Each table of assessment and training topics is specific to the aeroplane generation specified in the title. The component elements in the column headings of the matrix are as follows:

(a)Assessment and training topic. A topic or grouping of topics derived from threats, errors or findings from data analysis, to be considered for assessment and mitigation by training.

(b)Frequency. The priority of the topic to be considered in an EBT programme, according to the evidence derived from a large-scale analysis of operational data, is linked to a recommended frequency. There are three levels of frequency:

(1)A — assessment and training topic to be included with defined scenario elements during every EBT module;

(2)B — assessment and training topic to be included with defined scenario elements during every cycle;

(3)C — assessment and training topic to be included with defined scenario elements at least once in the 3-year period of the EBT programme.

(c)Flight phase for activation. The flight phase for the realisation of the critical threat or error in the assessment and training scenario.

(d)Description (includes type of topic, being threat, error or focus). A description of the training topic.

(e)Desired outcome (includes performance criteria or training outcome). Simple evaluative statements on the desired outcome.

(f)Example scenario elements (guidance material). The example scenario elements address the training topic and detail the threat and/or error that the crew are exposed to.

(g)Competency map. Competencies marked are those considered critical in managing the scenario.

AMC · AMC1 ORO.FC.232 — Regulation (EU) No 965/2012 · ED Decision 2021/002/R · Air OPS Easy Access Rules · EAR revision 27 Mar 2026

AMCAcceptable means of compliance

AMC2 ORO.FC.232EBT programme assessment and training topics

Show the text

GENERATION 4 (JET) — TABLE OF ASSESSMENT AND TRAINING TOPICS

Assessment and training topicFrequencyDescription (includes type of topic, being threat, error or focus)Desired outcome (includes performance criteria OR training outcome)Flight phase activationGuidance material (GM) Example scenario elementsPROCOMFPAFPMLTWPSDSAWWLMKNO
Generation 4 Jet — Recurrent assessment and training matrixCompetency map
Section 1 — Skill retention. Manoeuvres training phase (MT)
MTRejected take-offBRejected take-off after the application of take-off thrust and before reaching V1 (CAT I or above)Demonstrate manual aircraft control skills with smoothness and accuracy as appropriate to the situation. Detect deviations through instrument scanning. Maintain spare mental capacity during manual aircraft control. Maintain the aircraft within the flight envelope. Apply knowledge of the relationship between aircraft attitude, speed and thrust.TOFrom initiation of take-off to complete stop (or as applicable to the procedure)xx
Failure of the critical engine between V1 and V2BFailure of the critical engine (if applicable) from V1 and before reaching V2 in the lowest CAT I visibility or in LVO meteorological (MET) conditions.TOThe manoeuvre is complete at a point when the aircraft is stabilised at normal engine-out climb speed with the correct pitch and lateral control, in trim condition and, as applicable, autopilot engagement. Only one failure of the critical engine between V1 and V2 a year may be done in LVO conditions.xx
Failure of one engine on take-offBFailure of one engine from V1 and before reaching V2 in the lowest CAT I visibility or in LVO MET conditions.TOThe manoeuvre is complete at a point when the aircraft is stabilised in a clean configuration with engine-out procedures completed. Only one failure of the critical engine between V1 and V2 a year may be done in LVO conditions.xx
Failure of one engine above V2 (any segment of the TO) in the lowest CAT I visibility or in LVO MET conditions.The manoeuvre is complete at a point when the aircraft is stabilised in a clean configuration with engine-out procedures completed.xxx
Emergency descentCInitiation of emergency descent from normal cruise altitudeCRZThe manoeuvre is complete once the aircraft is stabilised in emergency descent configuration (and profile). However, if the EBT programme does not include the example scenario element ‘emergency descent’ in the training topic ‘automation management’, the emergency descent procedures should be completed and should not stop once the aircraft is stabilised in emergency descent configuration.xxx
Engine-out approach & landingBWith the critical engine (if applicable) failed, normal landingLDGInitiation in a stabilised engine-out configuration from not less than 3 NM final approach, until completion of roll-outxx
Engine-out approach & go-aroundBWith the critical engine (if applicable) failed, manually flown normal precision approach to DA, followed by a manual go-around — the whole manoeuvre to be flown without visual referenceAPPThis manoeuvre should be flown from intercept to centreline until acceleration after go-around. The manoeuvre is complete at a point when the aircraft is stabilised at normal engine-out climb speed with the correct pitch and lateral control, in trim condition and, as applicable, autopilot engagement (describe generally the critical part of the manoeuvre).xx
Go-aroundAGo-around, all engines operativeAPPHigh energy, initiation during the approach at 150 to 300 m (500 to 1 000 ft) below the missed approach level-off altitudexxx
Initiation of a go-around from DA followed by visual circuit and landingxxx
During flare/rejected landingxxx
Pilot qualification to operate in either pilot’s seatBAs per ORO.FC.235APPComplete the manoeuvres mandated in ORO.FC.235.Intentionally left in blank.
Assessment and training topicFrequencyDescription (includes type of topic, being threat, error or focus)Desired outcome (includes performance criteria OR training outcome)Flight phase activationGuidance material (GM) Example scenario elementsPROCOMFPAFPMLTWPSDSAWWLMKNO
Generation 4 Jet — Recurrent assessment and training matrixCompetency map
Section 2 — Equivalency of approaches relevant to operations. Evaluation phase, manoeuvres training phase or scenario-based training phase (EVAL, MT or SBT)
MTApproach type A or BBApproach type A or B flight method 3DSee equivalency of approaches relevant to operations that place an additional demand on a proficient crewAPPSee equivalency of approaches relevant to operationsxxxxX
Approach type ABApproach type A flight method 2DSee equivalency of approaches relevant to operations that place an additional demand on a proficient crewAPPSee equivalency of approaches relevant to operationsxxxxX
EVAL or SBTApproach type ABApproach type A flight method 3D or 2DSee equivalency of approaches relevant to operations that place an additional demand on a proficient crewAPPSee equivalency of approaches relevant to operationsxxxxX
Approach type BBApproach type B flight method 3DSee equivalency of approaches relevant to operations that place an additional demand on a proficient crewAPPSee equivalency of approaches relevant to operationsxxxxX
Section 3 – Equivalency of approaches under specific approvals and take-off under specific approvals. Evaluation phase, manoeuvres training phase or scenario-based training phase (EVAL, MT or SBT)
MTSPA approach(es)BApproach requiring specific approvalSee equivalency of approaches relevant to operations — specific approvalAPPApproaches flown from FAF to landing or go-aroundxxx
EVAL or SBTSPA approach(es)BApproach requiring specific approvalSee equivalency of approaches relevant to operations — specific approvalAPPApproaches flown from FAF to landing or go-aroundxxx
EVAL, MT or SBTSPA rejected take-off (RTO)BEngine failure after the application of take-off thrust and before reaching V1 (in low-visibility MET conditions, preferably in the lowest approved visibility) Low-visibility RTO is not required under Part SPA but instead in Appendix 9 Section 6. Note: AMC1 SPA.LVO.120 point (f) does not require a low-visibility RTO. RTO is required only in the initial LVO course (point (g)(1)(iii) of AMC1 SPA.LVO.120).Demonstrate manual aircraft control skills with smoothness and accuracy as appropriate to the situation. Detect deviations through instrument scanning. Maintain spare mental capacity during manual aircraft control. Maintain the aircraft within the flight envelope. Apply knowledge of the relationship between aircraft attitude, speed and thrust.TORTO — can be combined with the assessment and training topic ‘surprise’ in EVAL or SBTXX
EVAL, MT or SBTLVTOBNotwithstanding AMC1 SPA.LVO120 point (f)(1) AMC1 SPA.LVO.120 requires SPA manoeuvres in the frequency of the OPC, as OPC is substituted in the EBT programme. Thus, the frequency in EBT is determined in every cycle (B). Low-visibility take-off, preferably in the lowest approved visibility.TOThe manoeuvre is complete at a point when the aircraft is stabilised at normal climb speed with the correct pitch and lateral control, in trim condition and, as applicable, autopilot engagement.xx
Assessment and training topicFrequencyFlight phase activationDescription (includes type of topic, being threat, error or focus)Desired outcome (includes performance criteria OR training outcome)Guidance material (GM) Example scenario elementsPROCOMFPAFPMLTWPSDSAWWLMKNO
Generation 4 Jet — Recurrent assessment and training matrixCompetency map
Section 4 — Training topics with frequency (A) in alphabetical order. Evaluation phase or scenario-based training phase (EVAL or SBT)
EVAL or SBTAdverse weatherAGNDThunderstorm, heavy rain, turbulence, ice build-up to include de-icing issues, as well as high-temperature conditions. The proper use of anti-ice and de-icing systems should be included generally in appropriate scenarios.Anticipate adverse weather. Prepare for suspected adverse weather. Recognise adverse weather. Take appropriate action. Apply the appropriate procedure correctly. Assure aircraft control.Predictive wind shear warning before take-off, as applicablexxx
ALLAdverse-weather scenario, e.g. thunderstorm activity, precipitation, icingxxxx
TOWind shear encounter during take-off, not predictivexxxX
TOPredictive wind shear warning during take-offxxxx
TOCrosswinds with or without strong gusts on take-offxx
CRZTurbulence that increases to severe turbulencexxxx
CRZWind shear encounter scenario during cruisexxxxx
APPReactive wind shear warning during approach or go-aroundxxxx
APPPredictive wind shear warning during approach or go-aroundxxxx
APPThunderstorm encounter during approach or on missed approachxxx
APPIncreasing tailwind on final approach (not reported)xxxx
APPApproach and landing in demanding weather conditions, e.g. turbulence, up and downdrafts, gusts and crosswinds including shifting wind directionsxxx
APPNon-precision approach in cold-temperature conditions, requiring altitude compensation for temperature, as applicable to the typexxx
APP LDGCrosswinds with or without strong gusts on approach, final approach and landing (within and beyond limits)xxx
APPIn approach, unexpected braking action ‘good to medium’ reported by the preceding aircraftxxxx
APPModerate to severe icing conditions during approach effecting aircraft performancexxxx
APPReduced visibility even after acquiring the necessary visual reference during approach, due to rain or fogxxx
EVAL or SBTAutomation managementACLB CRZ DES APPThe purpose of this topic is to encourage and develop effective flight path management through proficient and appropriate use of the flight management system(s), guidance and automation, including transitions between modes, monitoring, mode awareness, vigilance and flexibility needed to change from one mode to another. The means of mitigating errors are included in this topic. The errors are described as mishandled auto flight systems, inappropriate mode selection, mishandled flight management system(s) and inappropriate autopilot usage.Know how and when to use the flight management system(s), guidance and automation. Demonstrate correct methods for engagement and disengagement of the auto flight system(s). Demonstrate appropriate use of flight guidance, auto thrust and other automation systems. Maintain mode awareness of the auto flight system(s), including engagement and automatic transitions. Revert to different modes when appropriate. Detect deviations from the desired aircraft state (flight path, speed, attitude, thrust, etc.) and take appropriate action. Anticipate mishandled auto flight system. Recognise mishandled auto flight system. Take appropriate action if necessary. Restore correct auto flight state. Identify and manage consequences.ACAS warning (resolution advisory), recovery and subsequent engagement of automationxx
ALLFMS tactical programming issues, e.g. step climb, runway changes, late clearances, destination re-programming, executing diversionxxX
CLB CRZ DES APPRecoveries from terrain avoidance warning systems (TAWS), management of energy state to restore automated flightxxx
CLB CRZ DES APPAmendments to ATC cleared levels during altitude capture modes to force mode awareness and interventionxxx
ACAS warning (resolution advisory to level off) during climb or descent; for example, close to the cleared level when the capture mode has already been activated.xxx
TOLate ATC clearance to an altitude below acceleration altitudexxx
TO APPEngine-out special terrain proceduresxxx
CRZForcing autopilot disconnect followed by re-engagement, recovery from lowor high-speed events in cruisexxxx
CLBEngine failure during or after initial climb using automationxx
CRZEngine failure in cruise to onset of descent using automationxx
CRZEmergency descentxxX
DES APPManaging high-energy descent capturing descent path from above (correlation with unstable approach training)xxxX
APPNo ATC clearance received prior to commencement of approach or final descentxxx
APPReactive wind shear and recovery from the consequent high-energy statexxx
APPAutomation fail to capture the approach altitude in descent (e.g. last altitude before the FAP). Ideally, the failure occurs when the workload is high (e.g. configuration of the aircraft for final approach).xxxx
APPNon-precision or infrequently flown approaches using the maximum available level of automationxxX
APPGear malfunction during an approach planned with autoland (including autobrake). Competency FPA may or may not be included depending on the impact of such malfunction on the automation.xxxx
APPATC clearances to waypoints beyond the programmed descent point for a coded final descent point during an approach utilising a final descent that is commanded by the flight management systemxxxX
EVAL or SBTCompetencies —non-technical (CRM)AAPPThis encapsulates the general CRM principles and objectives. It includes communication; leadership and teamwork; problem-solving and decision-making; situation awareness and management of information; and workload management. Emphasis should be placed on the development of leadership, shown by EBT data sources to be a highly effective competency in mitigating risk and improving safety through pilot performance.Exposure to an event or sequence of events to allow the pilot to build awareness of human factors in aviation and the human limitations. This includes the development of the following competencies: Communication: Demonstrate: — effective use of language; — responsiveness to feedback; and — capability to state the plans and resolve ambiguities. Leadership and teamwork: Use appropriate authority to ensure focus on the task. Support others in completing tasks. Problem-solving and decision-making: Detect deviations from the desired state, evaluate problems, identify the risk, consider alternatives and select the best course of action. Continuously review progress and adjust plans. Situation awareness and management of information: Have an awareness of the aircraft state in its environment; project and anticipate changes. Workload management: Prioritise, delegate and receive assistance to maximise focus on the task. Continuously monitor the flight progress.GPS failure prior to commencement of approach associated with position drift and a terrain alertxxxX
DESCabin crew report of water noise below the forward galley indicating a possible toilet pipe leak, with consequent avionics failuresxxx
CRZSmoke removal but combined with a diversion until landing is completed.xxxxxX
GNDApron fuel spillingxxx
CRZImportant water leak in an aircraft galleyxxxx
ALLA relevant number of cabin crew are wounded or incapacitated. Additionally, the cabin crew wounded or incapacitated are the most competent (e.g. senior cabin crew member).xxx
ALLUnruly passenger(s)xx
GNDPassenger oxygen: passenger service unit open and mask falling downxxx
ALLPassenger with medical problems — medical emergencyxx
CRZCredible threat reported to the crew. Stowaway or fugitive on board.xxxx
GNDNo METAR or TAFOR is available for destination due to industrial action at the destination airport.xxxx
CRZCredible bomb threat reported to crewxxxx
CLB DESCredible bomb threat or pressurisation problem, but no quick landing possible (due to weather, terrain or other reasons)xxxx
APPDiversion with low remaining fuel or increased fuel flow due to system malfunctionxxxx
APPACAS warning (resolution advisory) immediately following a go-around, with a descent manoeuvre required. (The RA should be a command for descent when the aircraft is above 1 100 ft AGL.)xxxxX
EVAL or SBTComplianceAALLCompliance failure. Consequences of not complying with operating instructions (e.g. SOPs). This is not intended to list example scenario elements, but instructors should ensure that observed non-compliances are taken as learning opportunities throughout the programme. In all modules of the programme, the FSTD should as far as possible be treated like an aircraft, and non-compliances should not be accepted simply for expediency.Recognise that a compliance failure has occurred. Make a verbal announcement. Take appropriate action if necessary. Restore safe flight path if necessary. Manage consequences.The following are examples of potential compliance failures and are not intended to be developed as scenarios as part of an EBT module: 1. Requesting flap beyond limit speed 2. Flaps or slats in the wrong position for phase of flight or approach 3. Omitting an action as part of a procedure 4. Failing to initiate or complete a checklist 5. Using the wrong checklist for the situationIntentionally blank
EVAL or SBTGo-around managementAAPPAny threat or error that can result in circumstances that require a decision to perform a go-around, in addition to the execution of the go-around. Go-around scenarios should be fully developed to encourage effective leadership and teamwork, in addition to problem-solving and decision-making, plus execution using manual aircraft control or the flight management system(s) and automation as applicable. Design should include the element of surprise, and scenario-based go-arounds should not be predictable and anticipated. This topic is completely distinct from the go-around manoeuvre listed in the MT section that is intended only to practise psychomotor skills and a simple application of the procedures.Adverse-weather scenario leading to a reactive wind shear warning during approachxxxx
APPAdverse-weather scenario leading to a predictive wind shear warning during approach or go-aroundxxxx
APPAdverse-weather scenario, e.g. thunderstorm activity, heavy precipitation or icing forcing decision at or close to DA/MDAxxxx
APPDA with visual reference in heavy precipitation with doubt about the runway surface braking capabilityxxxx
APPAdverse-wind scenario resulting in increasing tailwind below DA (not reported)xxx
APPAdverse-wind scenario including strong gusts and/or crosswind out of limits below DA (not reported)xxx
APPAdverse-wind scenario including strong gusts and/or crosswind out of limits below 15 m (50 ft) (not reported)xxx
APPLost or difficult communications resulting in no approach clearance prior to commencement of approach or final descentxxx
APPBirds: large flocks of birds below DA once visual reference has been establishedxxx
APPSystem malfunction, landing gear malfunction during the approach
EVAL or SBTManual aircraft controlACLB CRZ DES APPControls the flight path through manual controlDemonstrate manual aircraft control skills with smoothness and accuracy as appropriate to the situation. Detect deviations through instrument scanning. Maintain spare mental capacity during manual aircraft control. Maintain the aircraft within the normal flight envelope. Apply knowledge of the relationship between aircraft attitude, speed and thrust.Flight with unreliable airspeed, which may or may not be recoverablexxxX
CLB CRZ DES APPAlternate flight control modes according to malfunction characteristicsxxxX
CLB CRZ DES APPACAS warning (resolution advisory) requires the pilot to descend or ATC calls for immediate descent (preferably during climb which requires a significant change in aircraft attitude).xxx
ACAS warning (resolution advisory) requires the pilot to climb or ATC calls for immediate climb (preferably during descent which requires a significant change in aircraft attitude).xxx
DESTAWS warning when deviating from planned descent routing, requiring immediate responsexxx
TOScenario immediately after take-off which requires an immediate and overweight landingxxxx
TOAdverse wind, crosswinds with or without strong gusts on take-offxx
EVAL or SBTTOAdverse weather, wind shear, wind shear encounter during take-off, with or without reactive warningsxxx
TOEngine failure during initial climb, typically 30-60 m (100-200 ft) (autopilot off)xxxx
CRZWind shear encounter scenario during cruise, significant and rapid change in wind speed or down/updrafts, without wind shear warningxxxxx
APPAdverse weather, wind shear, wind shear encounter with or without warning during approachxxxx
APPAdverse weather, deterioration in visibility or cloud base, or adverse wind, requiring a go-around from visual circling approach, during the visual segmentxxxxxxx
APPInterception of the glide slope from above (correlation with unstable approach training)xxx
APP LDGAdverse wind, crosswinds with or without strong gusts on approach, final approach and landing (within and beyond limits)xxx
APP LDGAdverse weather, adverse wind, approach and landing in demanding weather conditions, e.g. turbulence, up and downdrafts, gusts and crosswinds including shifting wind directionsxxx
APP LDGCircling approach manually flown at night in minimum in-flight visibility to ensure ground reference, minimum environmental lighting and no glide slope guidance lightsXXXX
APP LDGRunway incursion during approach, which can be triggered by ATC at various altitudes or by visual contact during the landing phasexxx
LDGAdverse wind, visibility, type-specific, special consideration for long-bodied aircraft, landing in minimum visibility for visual reference, with crosswindxxxx
LDGSystem malfunction, auto flight failure at DA during a low-visibility approach requiring a go-around flown manuallyxxxx
APP LDGApproach planned with autoland, followed by a failure below 1 000 ft requiring a manual go-around and an immediate landing due to fuel shortagexxxx
TOIn-seat instruction: Insufficient engine failure recovery, forcing the pilot monitoring to take over the flight controlsxxxx
APP LDGIn-seat instruction: Unstable approach on short final or long landing, forcing the pilot monitoring to take over the flight controlsxxxx
EVAL or SBTMonitoring, cross-checking, error management, mismanaged aircraft stateAALLThe scenarios should be realistic and relevant, and should be used for the purpose of demonstration and reinforcement of effective monitoring. Modules in the FSTD should be treated like those in an aircraft so that trainees have the opportunity to develop the competency with the practice of the right techniques and attitudes related to these topics through pilot performance, and that instructors have the opportunity to assess and train these topics in a realistic environment. As shown by the EBT data report, these topics are of key importance to improve safety in operations. In addition, the operator may also use these topics to develop scripted role-playing scenarios in the form of ISI. These scenarios cater for the need to monitor flight path excursions from the instructor pilot (PF), detect errors and make appropriate interventions, either verbally or by taking control as applicable. Demonstration scenarios may also be used. Demonstrated role-play should contain realistic and not gross errors, leading at times to a mismanaged aircraft state, which can also be combined with upset management training.Recognise mismanaged aircraft state. Observe the pilot’s behaviour: how the pilot is mitigating errors, performing cross-checking, monitoring performance and dealing with a mismanaged aircraft state, in order to ensure that observed deviations, errors and mistakes are taken as learning opportunities throughout the programme. Monitor flight path excursions. Detect errors and threats through proper cross-checking performance. Make appropriate interventions either verbally or by taking control if applicable. Take appropriate action if necessary. Restore the desired aircraft state. Identify and manage consequences.Deviations from the flight path, in pitch attitude, speed, altitude, bank anglexx
ALLIn-seat instruction: Simple automation errors (e.g. incorrect mode selection, attempted engagement without the necessary conditions, entering wrong altitude or speed, failure to execute the desired mode) culminating in a need for direct intervention from the pilot monitoring, and where necessary taking control.xx
APPIn-seat instruction: Unstable approach or speed/path/vertical rate not congruent with the required state for the given flight conditionxxxx
LDGIn-seat instruction: Demonstration exercise — recovery from bounced landing, adverse wind, strong gusts during landing phase, resulting in a bounce and necessitating recovery action from the pilot monitoringxxx
Unstable approachADES APPReinforce stabilised approach philosophy and adherence to defined parameters. Encourage go-arounds when crews are outside these parameters. Develop and sustain competencies related to the management of high-energy situations.ATC or terrain-related environment creating a high-energy descent with the need to capture the optimum profile to complete the approach in a stabilised configurationxxx
DES APPATC or terrain-related environment creating a high-energy descent leading to unstable conditions and requiring a go-aroundxxx
APPApproach and landing in demanding weather conditions, e.g. turbulence, up and downdrafts, gusts and crosswinds including shifting wind directionsxxx
APPIncreasing tailwind on final approach (not reported)xxxx
APP LDGCrosswinds with or without strong gusts on approach, final approach and landing (within and beyond limits)xxx
Section 5 — UPRT training topic with frequency (B). Evaluation phase, manoeuvres training phase or scenario-based training phase (EVAL, MT or SBT)
EVAL, MT or SBTUpset prevention trainingBN/ACompliance with AMC1 or AMC2 to ORO.FC.220&230 Include upset prevention elements in Table 1 for the recurrent training programme in at least every cycle, such that all the elements are covered over a period not exceeding 3 years. The elements are numbered with letters from A to I in Table 1 of AMC1 ORO.FC.220&230. Each element is made up of several numbered components. According to the principles of EBT, covering one component should satisfy the requirement to cover the whole element of recognising and preventing the development of upset conditions.Early recognition and prevention of upset conditions. When the differences between LHS and RHS are not significant in the handling of the aircraft, UPRT may be conducted in either seat.See Table 1 of AMC1 ORO.FC.220&230: Elements and respective components of upset prevention training.Intentionally blank
CRZDemonstration of the defined normal flight envelope and any associated changes in flight instruments, flight director systems, and protection systems. This should take the form of an instructor-led exercise to show the crew the points beyond which an upset condition could exist.Xxx
TO APPSevere wind shear or wake turbulence during take-off or approachxxxx
CRZAs applicable and relevant to the aircraft type, demonstration at a suitable intermediate level, with turbulence as appropriate; practise steep turns and note the relationship between bank angle, pitch and stalling speed.Xxx
CRZAt the maximum cruise flight level for the current aircraft weight, turbulence to trigger overspeed conditions (if FSTD capability exists, consider use of the vertical wind component to add realism).Xxxx
CRZAt the maximum cruise flight level for the current aircraft weight, turbulence and significant temperature rise to trigger low-speed conditions (if FSTD capability exists, consider use of the vertical wind component to add realism).XxxX
CRZHigh-altitude ACAS RA (where the RA is required to be flown in manual flight)xxxx
Assessment and training topicFrequencyFlight phase activationDescription (includes type of topic, being threat, error or focus)Desired outcome (includes performance criteria OR training outcome)Guidance material (GM) Example scenario elementsPROCOMFPAFPMLTWPSDSAWWLMKNO
Section 6 — Training topics with frequency (B) in alphabetical order. Evaluation phase or scenario-based training phase (EVAL or SBT)
EVAL or SBTAdverse windBTOAdverse wind/crosswind. This includes tailwind but not ATC mis-reporting of the actual wind.Recognise adverse-wind conditions. Observe limitations. Apply the appropriate procedures. Maintain directional control and safe flight path.Take-off with different crosswind/tailwind/gust conditionsxx
TOTake-off with unreported tailwindxx
TOCrosswinds with or without strong gusts on take-offxx
APPWind exceeding limits on final approach (not reported)xxxx
APPWind exceeding limits on final approach (reported) in manual aircraft controlxxxx
APPIncreasing tailwind on final approach (not reported)xxxx
APPApproach and landing in demanding weather conditions, e.g. turbulence, up and downdrafts, gusts and crosswind including shifting wind directionsxxx
APPAdverse-wind scenario resulting in increasing tailwind below DA (not reported)xxx
APPAdverse-wind scenario including strong gusts and/or crosswind out of limits below DA (not reported)xxx
APPAdverse-wind scenario including strong gusts and/or crosswind out of limits below 15 m (50 ft) (not reported)xxx
APP LDGCrosswind with or without strong gusts on approach, final approach and landing (within and beyond limits)xxx
EVAL or SBTAircraft system malfunctions, including operations under MELBALLAny internal failure(s) apparent or not apparent to the crew Any item cleared by the MEL but having an impact upon flight operations — for instance, thrust reverser locked. Malfunctions to be considered should have one or more of the following characteristics: Immediacy Complexity Degradation of aircraft control Loss of primary instrumentation Management of consequences The operator should vary malfunctions for each characteristic over the EBT cycle. Unless specified otherwise in the operational suitability data, at least one malfunction with each characteristic should be included in every cycle. Combining characteristics should not reduce the number of malfunctions below seven in each cycle. For each crew member, the characteristics of degraded control and loss of instrumentation should be in the role of pilot flying and the others may be in the role of pilot flying or pilot monitoring. For full details, see the malfunction equivalency methodology.Recognise system malfunction. Take appropriate action including correct stop/go decision. Apply the appropriate procedure correctly. Maintain aircraft control. Manage consequences. Apply crew operating procedures where necessary. Respond appropriately to additional system abnormalities associated with MEL dispatch.(i) System malfunctions that require immediate and urgent crew intervention or decision, e.g. fire, smoke, loss of pressurisation at high altitude, failures during take-off, brake failure during landing. (ii) System malfunctions that require complex procedures, e.g. multiple hydraulic system failures, smoke and fumes procedures, major electrical system failure. (iii) System malfunctions that result in significant degradation of flight controls in combination with abnormal handling characteristics, e.g. jammed flight controls, certain degradation of FBW control, jammed horizontal stabiliser; flaps and/or slats locked; other malfunctions that result in degraded flight controls. (iv) System failures that require monitoring and management of the flight path using degraded or alternative displays, unreliable primary flight path information, unreliable airspeed, e.g. flight with unreliable airspeed (v) System failures that require extensive management of their consequences (independent of operation or environment), e.g. fuel leak.Intentionally blank
TOMEL items with crew operating procedures applicable during take-offxX
TOResponse to an additional factor that is affected by an MEL item (e.g. system failure, runway state)xxxX
GNDMalfunction during preflight preparation and prior to departurexxx
CLBMalfunction after departurexxxX
ALLMalfunctions that require immediate attention (e.g. bleed fault during engine start, hydraulic failure during taxi)xxx
CLB CRZFuel leak (management of consequences)xxxX
TOMalfunction on take-off high speed below V1xxx
TOMalfunction on take-off high speed above V1xx
GNDDuring taxi to the runway, a spurious brake temperature announcement. The crew had the correct brake temperature moments before the failure.XXX
TOTyre failure during take-offxxx
TOMalfunction on initial climbxx
APPMalfunction on approachxxx
APPMalfunction on go-aroundxxx
LDGMalfunction during landingxxxxx
Assessment and training topicFrequencyFlight phase activationDescription (includes type of topic, being threat, error or focus)Desired outcome (includes performance criteria OR training outcome)Guidance material (GM) Example scenario elementsPROCOMFPAFPMLTWPSDSAWWLMKNO
EVAL or SBTAircraft system managementBNormal system operation according to defined instructionsThis is not considered as a stand-alone topic. It is linked with the topic ‘compliance’. Where a system is not managed according to normal or defined procedures, this is determined as a non-compliance.See ‘compliance’ topic above. There are no defined scenarios, but the instructor should focus on learning opportunities when system management non-compliances manifest themselves during other scenarios. Underpinning knowledge of systems and their interactions should be developed and challenged, and not merely the application of normal procedures.Intentionally blankX
CRZ APP LDGMinimum fuel, caused by extended delays, weather, etc. where the crew would need to manage a minimum fuel situation.Xxxx
Approach, visibility close to minimumBAPPAny situation where visibility becomes a threatRecognise actual conditions. Observe aircraft and/or procedural limitations. Apply the appropriate procedures if applicable. Maintain directional control and safe flight path.Approach in poor visibilityxxxx
APPApproach in poor visibility with deteriorations necessitating a decision to perform a go-aroundxxx
LDGLanding in poor visibilityxxx
LandingBLDGPilots should have opportunities to practise landings in demanding situations at the defined frequency. Data indicates that landing problems have their roots in a variety of factors, including inappropriate decision-making, in addition to manual aircraft control skills if difficult environmental conditions exist. The purpose of this item is to ensure that pilots are exposed to this during the programme.Landing in demanding environmental conditions, with malfunctions as appropriateThis topic should be combined with the adverse-weather topic, aircraft system malfunctions topic or any topic that can provide exposure to a landing in demanding conditions.Intentionally blank
Runway or taxiway conditionBGND TO LDGContamination or surface quality of the runway, taxiway, or tarmac including foreign objectsRecognise hazardous runway condition. Observe limitations. Take appropriate action. Apply the appropriate procedures correctly. Assure aircraft control.Planned anticipated hazardous conditions with dispatch information provided to facilitate planning and execution of appropriate proceduresxX
GND TO LDGUnanticipated hazardous conditions, e.g. unexpected heavy rain resulting in flooded runway surfacexxx
TOTake-off on runway with reduced cleared width due to snowxxxx
TOStop/go decision in hazardous conditionsxxx
EVAL or SBTSurpriseBTOThe data analysed during the development of the EBT concept indicated substantial difficulties encountered by crews when faced with a threat or error, which was a surprise or an unexpected event. The element of surprise should be distinguished from what is sometimes referred to as the ‘startle factor’ — the latter being a physiological reaction. Wherever possible, consideration should be given towards variations in the types of scenario, times of occurrences and types of occurrence, so that pilots do not become overly familiar with repetitions of the same scenarios. Variations should be the focus of EBT programme design, and not left to the discretion of individual instructors, in order to preserve programme integrity and fairness.Exposure to an unexpected event or sequence of events at the defined frequency in order to build resilience.Rejected takeoffXXX
EVAL or SBTALLIntentionally blankIntentionally blank
EVAL or SBTTerrainBALLAlert, warning, or conflictAnticipate terrain threats. Prepare for terrain threats. Recognise unsafe terrain clearance. Take appropriate action. Apply the appropriate procedures correctly. Maintain aircraft control. Restore safe flight path. Manage consequences.ATC clearance giving insufficient terrain clearancexxxX
ALLDemonstration of terrain avoidance warning systems (TAWS) (this scenario element may be done in an ISI.)xxx
TO CLBEngine failure where performance is marginal leading to TAWS warningxxx
DES APPATC provides a wrong QNHxx
DES‘Virtual mountain’ refers to the surprise element of an unexpected warning. Care should be exercised in creating a level of realism, so this can best be achieved by an unusual and unexpected change of route during the descent.Xxx
Workload, distraction, pressure, stressBALLThis is not considered a topic for specific attention on its own, but more as a reminder to programme developers to ensure that pilots are exposed to immersive training scenarios which expose them to manageable high workload and distractions during the course of the EBT programme, at the defined frequency.Manage available resources efficiently to prioritise and perform tasks in a timely manner under all circumstancesIntentionally blankIntentionally blank
Assessment and training topicFrequencyFlight phase activationDescription (includes type of topic, being threat, error or focus)Desired outcome (includes performance criteria OR training outcome)Guidance material (GM) Example scenario elementsPROCOMFPAFPMLTWPSDSAWWLMKNO
Section 7 — UPRT Upset recovery training topic with frequency (C). Manoeuvres training phase or scenario-based training phase (MT or SBT)
MT or SBTUpset recoveryCN/ACompliance with AMC1 or AMC2 to ORO.FC.220&230 Include the recovery exercises in Table 2 of AMC1 ORO.FC.220&230 for the recurrent training programme, such that all the exercises are covered over a period not exceeding 3 years. According to the principles of EBT, covering one component should satisfy the requirement to cover the whole element of recovery from developed upsets. The same principles apply to the exercises of components 2, 3 and 4 where one exercise may satisfy the requirement to cover the whole component. An aeroplane upset is defined as an undesired aeroplane state in flight characterised by unintentional divergences from parameters normally experienced during line operations or training. An aeroplane upset may involve pitch and/or bank angle divergences as well as inappropriate airspeeds for the conditions.Recognise upset condition. Make timely and appropriate intervention. Take appropriate action. Assure timely and appropriate intervention. (AMC1 ORO.FC.220&230 Table 2 component 1) Assure aircraft control. Maintain or restore a safe flight path. Assess consequential issues. Manage outcomes. Consolidate the summary of aeroplane recovery techniques. (AMC1 ORO.FC.220&230 Table 2 component 5) Note: The operator should assess if the exercises should be practised for the either seat qualification.The example scenario elements may be done in ISI, as non-ISI or a combination of both. If done in ISI: The instructor should position the aircraft within but close to the edge of the validated training envelope before handing control to the trainee to demonstrate the restoration of normal flight. Careful consideration should be given to flying within the validated training envelope.Intentionally blank
Table 2 of AMC1 ORO.FC.220&230: Exercises for upset recovery training
A.Recovery from developed upsets
CLB DES2.Recovery from stall events in the following configurations: take-off configuration, clean configuration low altitude, clean configuration near maximum operating altitude, and landing configuration during the approach phase.xxxx
CRZ3.Recovery from nose high at various bank anglesxxxx
CRZ4.Recovery from nose low at various bank anglesxxxx
CRZ
APPDemonstration at a normal cruising altitude. Set conditions and disable aircraft systems as necessary to enable trainee to perform stall recovery according to OEM instructions.xxx
CLB DESDemonstration at an intermediate altitude during early stages of the approach. Set conditions and disable aircraft systems as necessary to enable trainee to perform stall recovery according to OEM instructions.xxx
Recovery from a wake turbulence position with high-bank anglexxxx
Assessment and training topicFrequencyFlight phase activationDescription (includes type of topic, being threat, error or focus)Desired outcome (includes performance criteria OR training outcome)Guidance material (GM) Example scenario elementsPROCOMFPAFPMLTWPSDSAWWLMKNO
Section 8 — Training topics with frequency (C) in alphabetical order. Evaluation phase or scenario-based training phase (EVAL or SBT)
EVAL or SBTATCCALLATC error. Omission, miscommunication, garbled, poor quality transmission. All these act as distractions to be managed by the crew. The scenarios should be combined, where possible, with others of the same or higher weighting, the principal reason being to create distractions.Respond to communications appropriately. Recognise, clarify and resolve any ambiguities. Refuse or question unsafe instructions. Use standard phraseology whenever possible.ATC role-play: the instructor provides scripted instructions, as a distraction to the crewxxx
ALLController error, provided by the instructor according to a defined scripted scenarioxxxx
ALLFrequency congestion, with multiple aircraft using the same frequencyx
APPDestination temporarily closedxxxx
CRZRescue and firefighting services (RFFS) level reduction at destinationxxx
APPRunway change before the interception of the localiser or similar navigation aid in azimuthxxxx
GND TOStray dogs at the opposite threshold runwayxxx
ALLPoor quality transmissionsx
EVAL or SBTEngine failureCTOAny engine failure or malfunction, which causes loss or degradation of thrust that affects performance. This is distinct from the engine-out manoeuvres described in the MT section above, which are intended only to practise psychomotor skills and reinforce procedures to manage engine failures.Recognise engine failure. Take appropriate action. Apply the appropriate procedure correctly. Maintain aircraft control. Manage consequences.Engine failure or engine malfunction on take-off low speedxxxx
TOEngine failure or engine malfunction on take-off high speed below V1xxxx
TOEngine failure or engine malfunction on take-off above V1xxxx
TOEngine failure or engine malfunction on initial climbxxx
APPEngine malfunctionxxx
CRZEngine failure in cruise (with autopilot)xxx
CRZMultiple engine failure in CRZ (volcanic ash, recoverable). Competency FPM may or may not be included depending on the impact on the automation.xxxx
LDGEngine failure or engine malfunction on landingx
EVAL or SBTFire and smoke managementCGNDThis includes engine, electric, pneumatic, cargo fire, smoke or fumes.Recognise fire, smoke or fumes Take appropriate action. Apply the appropriate procedure correctly. Maintain aircraft control. Manage consequences.Fire in cargo or cabin/cockpit at gatexxxx
GNDFire during taxixxxxX
GNDFire with no cockpit indicationxxxxX
TOTake-off low speedxxxxX
TOFire or smoke on take-off high speed below V1xxxx
TOFire or smoke on take-off high speed above V1xxx
TOFire or smoke on initial climbxxx
CRZCargo compartment fire or avionics compartment firexxx
APPEngine fire in approach (extinguishable)xx
APPEngine fire in approach (non-extinguishable)xxx
CLB CRZ DESLithium battery fire in the cockpit or cabin compartmentxxxxx
APPFlight deck or cabin firexxxX
GNDAny of the example scenario elements above ending in an evacuationxxxx
Loss of communicationsCGNDLost or difficult communications due to either pilot mis-selection or a failure external to the aircraft. This could be for a few seconds or a total loss.Recognise loss of communications. Take appropriate action. Execute the appropriate procedure as applicable. Use alternative ways to communicate. Manage consequences.Loss of communications during ground manoeuvringxx
TOLoss of communications after take-offxxX
APPLoss of communications during approach phase, including go-aroundxxxxX
Assessment and training topicFrequencyFlight phase activationDescription (includes type of topic, being threat, error or focus)Desired outcome (includes performance criteria OR training outcome)Guidance material (GM) Example scenario elementsPROCOMFPAFPMLTWPSDSAWWLMKNO
EVAL or SBTManaging loading, fuel, performance errorsCALLA calculation error by one or more pilots, or someone involved with the process, or the process itself, e.g. incorrect information on the load sheetAnticipate the potential for errors in load/fuel/performance data. Recognise inconsistencies. Manage/avoid distractions. Make changes to paperwork/aircraft system(s) to eliminate error. Identify and manage consequences.This can be a demonstrated error, in that the crew may be instructed to deliberately insert incorrect data — for example, to take off from an intersection with full-length performance information. The crew will be asked to intervene when acceleration is sensed to be lower than normal, and this may be part of the operator procedures, especially when operating mixed fleets with considerable variations in MTOM.xxx
TOWind report with take-off clearance not consistent with prior performance calculation. ATC, cabin crew or other people are pushing crew to take off quickly.xxxx
GNDEnvironmental change during taxi (e.g. heavy rain) not consistent with prior take-off performance calculationxx
GNDFuel ground staff on industrial action. Only limited amount of fuel available, which is below the calculated fuel for the flight.xxxx
GNDAdvise crew that there is a change of the load sheet figures during taxi to the runway. The crew may have limited time due to a calculated take-off time (CTOT) — ATC Slot.xx
GNDBraking action reported ‘medium’. The information is transmitted just before take-off. The flight is subject to a CTOT — ATC slot.xxx
EVAL or SBTNavigationCGNDExternal NAV failure. Loss of GPS satellite, ANP exceeding RNP, loss of external NAV source(s)Recognise a NAV degradation. Take appropriate action. Execute the appropriate procedure as applicable. Use alternative NAV guidance. Manage consequences.External failure or a combination of external failures degrading aircraft navigation performance on groundxxxx
TO CLB APP LDGExternal failure or a combination of external failures degrading aircraft navigation performance in flightxxxx
GNDStandard initial departure change during taxi. The flight may be subject to a CTOT — ATC slot.xxx
APPLoss of runway lighting below decision heightxxx
CRZNo fly zone: when the crew changes control frequency, the new ATCO informs the crew that they are flying over an unannounced ‘no fly zone’ that is not included in the NOTAMs. (To trigger such an event, the context may be as follows: an unexpected military conflict in the territory the aircraft is flying over or the crew is forced to re-route in flight and the new route flies over a city that has an important event such the Olympic games, a G20/G7 submit, or the route is flying near a space rocket launch close to the time of the launch, like the Guiana Space Centre, Cape Cañaveral, etc.).xxx
Operationsor type-specificCALLIntentionally blankIntentionally blankIntentionally blankIntentionally blank
Operations of special airport approvalCAPP LDGSee equivalency of approaches relevant to operations.The operator should comply with the national qualification requirements published in the aeronautical information publication (AIP).Intentionally blankIntentionally blank
Pilot incapacitationCTOConsequences for the non-incapacitated pilotRecognise incapacitation. Take appropriate action including correct stop/go decision. Apply the appropriate procedure correctly. Maintain aircraft control. Manage consequences.During take-offxxxxX
APPDuring approachxxxX
TrafficCCLB CRZ DESTraffic conflict. ACAS RA or TA, or visual observation of conflict, which requires evasive manoeuvringAnticipate potential loss of separation. Recognise loss of separation. Take appropriate action. Apply the appropriate procedure correctly. Maintain aircraft control. Manage consequences.ACAS warning that requires crew interventionxxxx
Dilemma: Visual acquisition of conflicting traffic followed by an ACAS warning (resolution advisory) triggered by the same or other traffic. Even if the traffic is in sight, the pilot should follow the RA.xxx
While in descent, ACAS warning (traffic advisory) of an aircraft below. The crew should not initiate an avoidance manoeuvre based on TA (except decreasing the rate of descent unless otherwise instructed by ATC, etc.). This example scenario can be done during climb with conflicting traffic above.xxx
Wind shear recoveryCTOWith or without warnings including predictive. A wind shear scenario is ideally combined with an adverse-weather scenario containing other elements.Anticipate potential for wind shear. Avoid known wind shear or prepare for suspected wind shear. Recognise wind shear encounter. Take appropriate action. Apply the appropriate procedure correctly. Assure aircraft control. Recognise out of wind shear condition. Maintain or restore a safe flight path. Assess consequential issues and manage outcomes.Predictive wind shear warning during take-offxx
TOWind shear encounter during take-offxxx
TOWind shear encounter after rotationxx
TOPredictive wind shear after rotationxx
APPPredictive wind shear during approachxxx
APPWind shear encounter during go-aroundxxxx
APPWind shear encounter during approachxxx

END GEN4 JET

AMC · AMC2 ORO.FC.232 — Regulation (EU) No 965/2012 · ED Decision 2022/014/R · Air OPS Easy Access Rules · EAR revision 27 Mar 2026

AMCAcceptable means of compliance

AMC3 ORO.FC.232EBT programme assessment and training topics

Show the text

GENERATION 3 (JET) — TABLE OF ASSESSMENT AND TRAINING TOPICS

Assessment and training topicFrequencyDescription (includes type of topic, being threat, error or focus)Desired outcome (includes performance criteria OR training outcome)Flight phase activationGuidance material (GM) Example scenario elementsPROCOMFPAFPMLTWPSDSAWWLMKNO
Generation 3 Jet — Recurrent assessment and training matrixCompetency map
Section 1 — Skill retention. Manoeuvres training phase (MT)
MTRejected take-offBRejected take-off after the application of takeoff thrust and before reaching V1 (CAT I or above)Demonstrate manual aircraft control skills with smoothness and accuracy as appropriate to the situation. Detect deviations through instrument scanning. Maintain spare mental capacity during manual aircraft control. Maintain the aircraft within the flight envelope. Apply knowledge of the relationship between aircraft attitude, speed and thrust.TOFrom initiation of take-off to complete stop (or as applicable to the procedure)xx
Failure of the critical engine between V1 and V2AFailure of the critical engine from V1 and before reaching V2 in the lowest CAT I visibility or in LVO meteorological (MET) conditions.TOThe manoeuvre is complete at a point when the aircraft is stabilised at normal engine-out climb speed with the correct pitch and lateral control, in trim condition and, as applicable, autopilot engagement. Only one failure of the critical engine between V1 and V2 a year may be done in LVO conditions.xx
Failure of one engine on take-offBFailure of one engine from V1 and before reaching V2 in the lowest CAT I visibility or in LVO MET conditions.TOThe manoeuvre is complete at a point when the aircraft is stabilised in a clean configuration with engine-out procedures completed. Only one failure of the critical engine between V1 and V2 a year may be done in LVO conditions.xx
Failure of one engine above V2 (any segment of the TO) in the lowest CAT I visibility or in LVO MET conditions.The manoeuvre is complete at a point when the aircraft is stabilised in a clean configuration with engine-out procedures completed.xxx
Emergency descentCInitiation of emergency descent from normal cruise altitudeCRZThe manoeuvre is complete once the aircraft is stabilised in emergency descent configuration (and profile). However, if the EBT programme does not include the example scenario element ‘emergency descent’ in the training topic ‘automation management’, the emergency descent procedures should be completed and should not stop once the aircraft is stabilised in emergency descent configuration.xxx
Engine-out approach & landingBWith the critical engine (if applicable) failed, normal landingLDGInitiation in a stabilised engine-out configuration from not less than 3 NM final approach, until completion of roll-outxx
Engine-out approach & go-aroundBWith the critical engine (if applicable) failed, manually flown normal precision approach to DA, followed by a manual go-around — the whole manoeuvre to be flown without visual referenceAPPThis manoeuvre should be flown from intercept to centreline until acceleration after go-around. The manoeuvre is complete at a point when the aircraft is stabilised at normal engine-out climb speed with the correct pitch and lateral control, in trim condition and, as applicable, autopilot engagement (describe generally the critical part of the manoeuvre).xx
Go-aroundAGo-around, all engines operativeAPPHigh energy, initiation during the approach at 150 to 300 m (500 to 1 000 ft) below the missed approach level-off altitudexxx
Initiation of a go-around from DA followed by visual circuit and landingxxx
During flare/rejected landingxxx
Pilot qualification to operate in either pilot’s seatBAs per ORO.FC.235APPComplete the manoeuvres mandated in ORO.FC.235.Intentionally left in blank.
Assessment and training topicFrequencyDescription (includes type of topic, being threat, error or focus)Desired outcome (includes performance criteria OR training outcome)Flight phase activationGuidance material (GM) Example scenario elementsPROCOMFPAFPMLTWPSDSAWWLMKNO
Generation 3 Jet — Recurrent assessment and training matrixCompetency map
Section 2 — Equivalency of approaches relevant to operations. Evaluation phase, manoeuvres training phase or scenario-based training phase (EVAL, MT or SBT)
MTApproach type A or BBApproach type A or B flight method 3DSee equivalency of approaches relevant to operations that place an additional demand on a proficient crewAPPSee equivalency of approaches relevant to operationsXXXXX
Approach type ABApproach type A flight method 2DSee equivalency of approaches relevant to operations that place an additional demand on a proficient crewAPPSee equivalency of approaches relevant to operationsXXXXX
EVAL or SBTApproach type ABApproach type A flight method 3D or 2DSee equivalency of approaches relevant to operations that place an additional demand on a proficient crewAPPSee equivalency of approaches relevant to operationsXXXXX
Approach type BBApproach type B flight method 3DSee equivalency of approaches relevant to operations that place an additional demand on a proficient crewAPPSee equivalency of approaches relevant to operationsXXXXX
Section 3 – Equivalency of approaches under specific approvals and take-off under specific approvals. Evaluation phase, manoeuvres training phase or scenario-based training phase (EVAL, MT or SBT)
MTSPA approach(es)BApproach requiring specific approvalSee equivalency of approaches relevant to operations — specific approvalAPPApproaches flown from FAF to landing or go-aroundxxx
EVAL or SBTSPA approach(es)BApproach requiring specific approvalSee equivalency of approaches relevant to operations — specific approvalAPPApproaches flown from FAF to landing or go-aroundxxx
EVAL, MT or SBTSPA Rejected take-off (RTO)BEngine failure after the application of take-off thrust and before reaching V1 (in low-visibility MET conditions, preferably in the lowest approved visibility) Low-visibility RTO is not required under Part SPA but instead in Appendix 9 Section 6. Note: AMC1 SPA.LVO.120 point (f) does not require a low-visibility RTO. RTO is required only in the initial LVO course (point (g)(1)(iii) of AMC1 SPA.LVO.120).Demonstrate manual aircraft control skills with smoothness and accuracy as appropriate to the situation. Detect deviations through instrument scanning. Maintain spare mental capacity during manual aircraft control. Maintain the aircraft within the flight envelope. Apply knowledge of the relationship between aircraft attitude, speed and thrust.TO RTO — can be combined with the assessment and training topic ‘surprise’ in EVAL or SBTXX
EVAL, MT or SBTLVTOBNotwithstanding AMC1 SPA.LVO120 point (f)(1) AMC1 SPA.LVO.120 requires SPA manoeuvres in the frequency of the OPC, as OPC is substituted in the EBT programme. Thus, the frequency in EBT is determined in every cycle (B). Low visibility take-off, preferably in the lowest approved visibilityTOThe manoeuvre is complete at a point when the aircraft is stabilised at normal climb speed with the correct pitch and lateral control, in trim condition and, as applicable, autopilot engagement.xx
Assessment and training topicFrequencyFlight phase activationDescription (includes type of topic, being threat, error or focus)Desired outcome (includes performance criteria OR training outcome)Guidance material (GM) Example scenario elementsPROCOMFPAFPMLTWPSDSAWWLMKNO
Generation 3 Jet — Recurrent assessment and training matrixCompetency map
Section 4 — Training topics with frequency (A) in alphabetical order. Evaluation phase or scenario-based training phase (EVAL or SBT).
EVAL or SBTAdverse weatherAGNDThunderstorm, heavy rain, turbulence, ice build-up to include de-icing issues, as well as high-temperature conditions. The proper use of anti-ice and de-icing systems should be included generally in appropriate scenarios.Anticipate adverse weather. Prepare for suspected adverse weather. Recognise adverse weather. Take appropriate action. Apply the appropriate procedure correctly. Assure aircraft control.Predictive wind shear warning before take-off, as applicablexxx
ALLAdverse-weather scenario, e.g. thunderstorm activity, precipitation, icingxxxx
TOWind shear encounter during take-off, not predictivexxxX
TOPredictive wind shear warning during take-offxxxx
TOCrosswinds with or without strong gusts on take-offxx
CRZTurbulence that increases to severe turbulencexxxx
CRZWind shear encounter scenario during cruisexxxxx
APPReactive wind shear warning during approach or go-aroundxxxx
APPPredictive wind shear warning during approach or go-aroundxxxx
APPThunderstorm encounter during approach or on missed approachxxx
APPIncreasing tailwind on final approach (not reported)xxxx
APPApproach and landing in demanding weather conditions, e.g. turbulence, up and downdrafts, gusts and crosswinds including shifting wind directionsxxx
APPNon-precision approach in cold-temperature conditions, requiring altitude compensation for temperature, as applicable to the typexxx
APP LDGCrosswinds with or without strong gusts on approach, final approach and landing (within and beyond limits)xxx
APPIn approach, unexpected braking action ‘good to medium’ reported by the preceding aircraftxxxx
APPModerate to severe icing conditions during approach effecting aircraft performancexxxx
APPReduced visibility even after acquiring the necessary visual reference during approach, due to rain or fogxxx
EVAL or SBTAutomation managementACLB CRZ DES APPThe purpose of this topic is to encourage and develop effective flight path management through proficient and appropriate use of the flight management system(s), guidance and automation, including transitions between modes, monitoring, mode awareness, vigilance and flexibility needed to change from one mode to another. The means of mitigating errors are included in this topic. The errors are described as mishandled auto flight systems, inappropriate mode selection, mishandled flight management system(s) and inappropriate autopilot usage.Know how and when to use the flight management system(s), guidance and automation. Demonstrate correct methods for engagement and disengagement of the auto flight system(s). Demonstrate appropriate use of flight guidance, auto thrust and other automation systems. Maintain mode awareness of the auto flight system(s), including engagement and automatic transitions. Revert to different modes when appropriate. Detect deviations from the desired aircraft state (flight path, speed, attitude, thrust, etc.) and take appropriate action. Anticipate mishandled auto flight system. Recognise mishandled auto flight system. Take appropriate action if necessary. Restore correct auto flight state. Identify and manage consequences.ACAS warning (resolution advisory), recovery and subsequent engagement of automationxx
ALLFMS tactical programming issues, e.g. step climb, runway changes, late clearances, destination re-programming, executing diversionxxX
CLB CRZ DES APPRecoveries from TAWS, management of energy state to restore automated flightxxx
CLB CRZ DES APPAmendments to ATC cleared levels during altitude capture modes to force mode awareness and interventionxxx
ACAS warning (resolution advisory to level off) during climb or descent; for example, close to the cleared level when the capture mode has already been activated.xxx
TOLate ATC clearance to an altitude below acceleration altitudexxx
TO APPEngine-out special terrain proceduresxxx
CRZForcing autopilot disconnect followed by re-engagement, recovery from lowor high-speed events in cruisexxxx
CLBEngine failure during or after initial climb using automationxx
CRZEngine failure in cruise to onset of descent using automationxx
CRZEmergency descentxxX
DES APPManaging high-energy descent capturing descent path from above (correlation with unstable approach training)xxxX
APPNo ATC clearance received prior to commencement of approach or final descentxxx
APPReactive wind shear and recovery from the consequent high-energy statexxx
APPAutomation fail to capture the approach altitude in descent (e.g. last altitude before the FAP). Ideally, the failure occurs when the workload is high (e.g. configuration of the aircraft for final approach).xxxx
APPNon-precision or infrequently flown approaches using the maximum available level of automationxxX
APPGear malfunction during an approach planned with autoland (including autobrake). Competency FPA may or may not be included depending on the impact of such malfunction on the automation.xxxx
APPATC clearances to waypoints beyond the programmed descent point for a coded final descent point during an approach utilising a final descent that is commanded by the flight management system.xxxX
EVAL or SBTCompetencies — non-technical (CRM)AAPPThis encapsulates the general CRM principles and objectives. It includes communication; leadership and teamwork; problem-solving and decision-making; situation awareness and management of information; and workload management. Emphasis should be placed on the development of leadership, shown by EBT data sources to be a highly effective competency in mitigating risk and improving safety through pilot performance.Exposure to an event or sequence of events to allow the pilot to build awareness of human factors in aviation and the human limitations. This includes the development of the following competencies: Communication: Demonstrate: — effective use of language; — responsiveness to feedback; and — capability to state the plans and resolve ambiguities. Leadership and teamwork: Use appropriate authority to ensure focus on the task. Support others in completing tasks. Problem-solving and decision-making: Detect deviations from the desired state, evaluate problems, identify the risk, consider alternatives and select the best course of action. Continuously review progress and adjust plans. Situation awareness and management of information: Have an awareness of the aircraft state in its environment; project and anticipate changes. Workload management: Prioritise, delegate and receive assistance to maximise focus on the task. Continuously monitor the flight progress.GPS failure prior to commencement of approach associated with position drift and a terrain alertxxxX
DESCabin crew report of water noise below the forward galley indicating a possible toilet pipe leak, with consequent avionics failuresxxx
CRZSmoke removal but combined with a diversion until landing is completed.xxxxxX
GNDApron fuel spillingxxx
CRZImportant water leak in an aircraft galleyxxxx
ALLA relevant number of cabin crew are wounded or incapacitated. Additionally, the cabin crew wounded or incapacitated are the most competent (e.g. senior cabin crew member).xxx
ALLUnruly passenger(s)xx
GNDPassenger oxygen: passenger service unit open and mask falling downxxx
ALLPassenger with medical problems — medical emergencyxx
CRZCredible threat reported to the crew. Stowaway or fugitive on board.xxxx
GNDNo METAR or TAFOR is available for destination due to industrial action at the destination airport.xxxx
CRZCredible bomb threat reported to crewxxxx
EVAL or SBTCLB DESCredible bomb threat or pressurisation problem, but no quick landing possible (due to weather, terrain or other reasons)xxxx
APPDiversion with low remaining fuel or increased fuel flow due to system malfunctionxxxx
APPACAS warning (resolution advisory) immediately following a go-around, with a descent manoeuvre required. (The RA should be a command for descent when the aircraft is above 1 100 ft AGL.)xxxxX
EVAL or SBTComplianceAALLCompliance failure. Consequences of not complying with operating instructions (e.g. SOPs). This is not intended to list example scenario elements, but instructors should ensure that observed non-compliances are taken as learning opportunities throughout the programme. In all modules of the programme, the FSTD should as far as possible be treated like an aircraft, and non-compliances should not be accepted simply for expediency.Recognise that a compliance failure has occurred. Make a verbal announcement. Take appropriate action if necessary. Restore safe flight path if necessary. Manage consequences.The following are examples of potential compliance failures and are not intended to be developed as scenarios as part of an EBT mod: 1. Requesting flap beyond limit speed 2. Flaps or slats in the wrong position for phase of flight or approach 3. Omitting an action as part of a procedure 4. Failing to initiate or complete a checklist 5. Using the wrong checklist for the situationIntentionally blank
EVAL or SBTGo-around managementAAPPAny threat or error that can result in circumstances that require a decision to perform a go-around, in addition to the execution of the go-around. Go-around scenarios should be fully developed to encourage effective leadership and teamwork, in addition to problem-solving and decision-making, plus execution using manual aircraft control or the flight management system(s) and automation as applicable. Design should include the element of surprise, and scenario-based go-arounds should not be predictable and anticipated. This topic is completely distinct from the go-around manoeuvre listed in the MT section that is intended only to practise psychomotor skills and a simple application of the procedures.Adverse-weather scenario leading to a reactive wind shear warning during approachxxxx
APPAdverse-weather scenario leading to a predictive wind shear warning during approach or go-aroundxxxx
APPAdverse-weather scenario, e.g. thunderstorm activity, heavy precipitation or icing forcing decision at or close to DA/MDAxxxx
APPDA with visual reference in heavy precipitation with doubt about the runway surface braking capabilityxxxx
APPAdverse-wind scenario resulting in increasing tailwind below DA (not reported)xxx
APPAdverse-wind scenario including strong gusts and/or crosswind out of limits below DA (not reported)xxx
APPAdverse-wind scenario including strong gusts and/or crosswind out of limits below 15 m (50 ft) (not reported)xxx
APPLost or difficult communications resulting in no approach clearance prior to commencement of approach or final descentxxx
APPBirds: large flocks of birds below DA once visual reference has been establishedxxx
APPSystem malfunction, landing gear malfunction during the approach
EVAL or SBTManual aircraft controlACLB CRZ DES APPControls the flight path through manual controlDemonstrate manual aircraft control skills with smoothness and accuracy as appropriate to the situation. Detect deviations through instrument scanning. Maintain spare mental capacity during manual aircraft control. Maintain the aircraft within the normal flight envelope. Apply knowledge of the relationship between aircraft attitude, speed and thrust.Flight with unreliable airspeed, which may or may not be recoverablexxxX
CLB CRZ DES APPAlternate flight control modes according to malfunction characteristicsxxxX
CLB CRZ DES APPACAS warning (resolution advisory) requires the pilot to descend or ATC calls for immediate descent (preferably during climb which requires a significant change in aircraft attitude)xxx
ACAS warning (resolution advisory) requires the pilot to climb or ATC calls for immediate climb (preferably during descent which requires a significant change in aircraft attitude).xxx
DESTAWS warning when deviating from planned descent routing, requiring immediate responsexxx
EVAL or SBTTOScenario immediately after take-off which requires an immediate and overweight landingxxxx
TOAdverse wind, crosswinds with or without strong gusts on take-offxx
TOAdverse weather, wind shear, wind shear encounter during take-off, with or without reactive warningsxxx
TOEngine failure during initial climb, typically 30-60 m (100-200 ft) (autopilot off)xxxx
CRZWind shear encounter scenario during cruise, significant and rapid change in wind speed or down/updrafts, without wind shear warningxxxxx
APPAdverse weather, wind shear, wind shear encounter with or without warning during approachxxxx
APPAdverse weather, deterioration in visibility or cloud base, or adverse wind, requiring a go-around from visual circling approach, during the visual segmentxxxxxxx
APPInterception of the glide slope from above (correlation with unstable approach training)xxx
APP LDGAdverse wind, crosswinds with or without strong gusts on approach, final approach and landing (within and beyond limits)xxx
APP LDGAdverse weather, adverse wind, approach and landing in demanding weather conditions, e.g. turbulence, up and downdrafts, gusts and crosswinds including shifting wind directionsxxx
APP LDGCircling approach manually flown at night in minimum in-flight visibility to ensure ground reference, minimum environmental lighting and no glide slope guidance lightsXXXX
APP LDGRunway incursion during approach, which can be triggered by ATC at various altitudes or by visual contact during the landing phasexxx
LDGAdverse wind, visibility, type-specific, special consideration for long-bodied aircraft, landing in minimum visibility for visual reference, with crosswindxxxx
LDGSystem malfunction, auto flight failure at DA during a low-visibility approach requiring a go-around flown manuallyxxxx
APP LDGApproach planned autoland, followed by a failure below 1 000 ft requiring a manual go-around and an immediate landing due to fuel shortagexxxx
TOIn-seat instruction: Insufficient engine failure recovery, forcing the pilot monitoring to take over the flight controlsxxxx
APP LDGIn-seat instruction: Unstable approach on short final or long landing, forcing the pilot monitoring to take over the flight controlsxxxx
EVAL or SBTMonitoring, cross-checking, error management, mismanaged aircraft stateAALLThe scenarios should be realistic and relevant, and should be used for the purpose of demonstration and reinforcement of effective monitoring. Modules in the FSTD should be treated like those in an aircraft so that trainees have the opportunity to develop the competency with the practice of the right techniques and attitudes related to these topics through pilot performance, and that instructors have the opportunity to assess and train these topics in a realistic environment. As shown by the EBT data report, these topics are of key importance to improve safety in operations. In addition, the operator may also use these topics to develop scripted role-playing scenarios in the form of ISI. These scenarios cater for the need to monitor flight path excursions from the instructor pilot (PF), detect errors and make appropriate interventions, either verbally or by taking control as applicable. Demonstration scenarios may also be used. Demonstrated role-play should contain realistic and not gross errors, leading at times to a mismanaged aircraft state, which can also be combined with upset management training.Recognise mismanaged aircraft state. Observe the pilot’s behaviour: how the pilot is mitigating errors, performing cross-checking, monitoring performance and dealing with a mismanaged aircraft state, in order to ensure that observed deviations, errors and mistakes are taken as learning opportunities throughout the programme. Monitor flight path excursions. Detect errors and threats through proper cross-checking performance. Make appropriate interventions either verbally or by taking control if applicable. Take appropriate action if necessary. Restore the desired aircraft state. Identify and manage consequences.Deviations from the flight path, in pitch attitude, speed, altitude, bank anglexx
ALLIn-seat instruction: Simple automation errors (e.g. incorrect mode selection, attempted engagement without the necessary conditions, entering wrong altitude or speed, failure to execute the desired mode) culminating in a need for direct intervention from the pilot monitoring, and where necessary taking control.xx
APPIn-seat instruction: Unstable approach or speed/path/vertical rate not congruent with the required state for the given flight conditionxxxx
LDGIn-seat instruction: Demonstration exercise — recovery from bounced landing, adverse wind, strong gusts during landing phase, resulting in a bounce and necessitating recovery action from the pilot monitoringxxx
Unstable approachADES APPReinforce stabilised approach philosophy and adherence to defined parameters. Encourage go-arounds when crews are outside these parameters. Develop and sustain competencies related to the management of high-energy situations.ATC or terrain-related environment creating a high-energy descent with the need to capture the optimum profile to complete the approach in a stabilised configurationxxx
DES APPATC or terrain-related environment creating a high-energy descent leading to unstable conditions and requiring a go-aroundxxx
APPApproach and landing in demanding weather conditions, e.g. turbulence, up and downdrafts, gusts and crosswinds including shifting wind directionsxxx
APPIncreasing tailwind on final approach (not reported)xxxx
APP LDGCrosswinds with or without strong gusts on approach, final approach and landing (within and beyond limits)xxx
Assessment and training topicFrequencyFlight phase activationDescription (includes type of topic, being threat, error or focus)Desired outcome (includes performance criteria OR training outcome)Guidance material (GM) Example scenario elementsPROCOMFPAFPMLTWPSDSAWWLMKNO
Section 5 — UPRT training topic with frequency (B). Evaluation phase, manoeuvres training phase or scenario-based training phase (EVAL, MT or SBT)
EVAL, MT or SBTUpset prevention trainingBN/ACompliance with AMC1 or AMC2 to ORO.FC.220&230 Include upset prevention elements in Table 1 for the recurrent training programme in at least every cycle, such that all the elements are covered over a period not exceeding 3 years. The elements are numbered with letters from A to I in Table 1 of AMC1 ORO.FC.220&230. Each element is made up of several numbered components. According to the principles of EBT, covering one component should satisfy the requirement to cover the whole element of recognising and preventing the development of upset conditions.Early recognition and prevention of upset conditions. When the differences between LHS and RHS are not significant in the handling of the aircraft, UPRT may be conducted in either seat.See Table 1 of AMC1 ORO.FC.220&230: Elements and respective components of upset prevention training.Intentionally blank
CRZDemonstration of the defined normal flight envelope and any associated changes in flight instruments, flight director systems, and protection systems. This should take the form of an instructor-led exercise to show the crew the points beyond which an upset condition could exist.xxx
TO APPSevere wind shear or wake turbulence during take-off or approachxxxx
CRZAs applicable and relevant to the aircraft type, demonstration at a suitable intermediate level, with turbulence as appropriate; practise steep turns and note the relationship between bank angle, pitch and stalling speedxxx
CRZAt the maximum cruise flight level for the current aircraft weight, turbulence to trigger overspeed conditions (if FSTD capability exists, consider use of the vertical wind component to add realism)xxxx
CRZAt the maximum cruise flight level for the current aircraft weight, turbulence and significant temperature rise to trigger low-speed conditions (if FSTD capability exists, consider use of the vertical wind component to add realism)xxxX
CRZHigh-altitude loss of reliable airspeedxxxxx
CRZHigh-altitude ACAS RA (where the RA is required to be flown in manual flight)xxxx
Assessment and training topicFrequencyFlight phase activationDescription (includes type of topic, being threat, error or focus)Desired outcome (includes performance criteria OR training outcome)Guidance material (GM) Example scenario elementsPROCOMFPAFPMLTWPSDSAWWLMKNO
Section 6 — Training topics with frequency (B) in alphabetical order. Evaluation phase or scenario-based training phase (EVAL or SBT)
EVAL or SBTAdverse windBTOAdverse wind/crosswind. This includes tailwind but not ATC mis-reporting of the actual wind.Recognise adverse-wind conditions. Observe limitations. Apply the appropriate procedures. Maintain directional control and safe flight path.Take-off with different crosswind/tailwind/gust conditionsxx
TOTake-off with unreported tailwindxx
TOCrosswinds with or without strong gusts on take-offxx
APPWind exceeding limits on final approach (not reported)xxxx
APPWind exceeding limits on final approach (reported) in manual aircraft controlxxxx
APPIncreasing tailwind on final approach (not reported)xxxx
APPApproach and landing in demanding weather conditions, e.g. turbulence, up and downdrafts, gusts and crosswind including shifting wind directionsxxx
APPAdverse-wind scenario resulting in increasing tailwind below DA (not reported)xxx
APPAdverse-wind scenario including strong gusts and/or crosswind out of limits below DA (not reported)xxx
APPAdverse-wind scenario including strong gusts and/or crosswind out of limits below 15 m (50 ft) (not reported)xxx
APP LDGCrosswind with or without strong gusts on approach, final approach and landing (within and beyond limits)xxx
EVAL or SBTAircraft system malfunctions, including operations under MELBALLAny internal failure(s) apparent or not apparent to the crew Any item cleared by the MEL but having an impact upon flight operations — for instance, thrust reverser locked. Malfunctions to be considered should have one or more of the following characteristics: Immediacy Complexity Degradation of aircraft control Loss of primary instrumentation Management of consequences The operator should vary malfunctions for each characteristic over the EBT cycle. Unless specified otherwise in the operational suitability data, at least one malfunction with each characteristic should be included in every cycle. Combining characteristics should not reduce the number of malfunctions below seven for each cycle. For each crew member, the characteristics of degraded control and loss of instrumentation should be in the role of pilot flying and the others may be in the role of pilot flying or pilot monitoring. For full details, see the malfunction equivalency methodology.Recognise system malfunction. Take appropriate action including correct stop/go decision. Apply the appropriate procedure correctly. Maintain aircraft control. Manage consequences. Apply crew operating procedures where necessary. Respond appropriately to additional system abnormalities associated with MEL dispatch.(i) System malfunctions that require immediate and urgent crew intervention or decision, e.g. fire, smoke, loss of pressurisation at high altitude, failures during take-off, brake failure during landing. (ii) System malfunctions that require complex procedures, e.g. multiple hydraulic system failures, smoke and fumes procedures, major electrical system failure. (iii) System malfunctions that result in significant degradation of flight controls in combination with abnormal handling characteristics, e.g. jammed flight controls, certain degradation of FBW control, jammed horizontal stabiliser; flaps and/or slats locked; other malfunctions that result in degraded flight controls. (iv) System failures that require monitoring and management of the flight path using degraded or alternative displays, unreliable primary flight path information, unreliable airspeed, e.g. flight with unreliable airspeed (v) System failures that require extensive management of their consequences (independent of operation or environment), e.g. fuel leak.Intentionally blank
TOMEL items with crew operating procedures applicable during take-offxX
TOResponse to an additional factor that is affected by an MEL item (e.g. system failure, runway state)xxxX
GNDMalfunction during preflight preparation and prior to departurexxx
CLBMalfunction after departurexxxX
ALLMalfunctions that require immediate attention (e.g. bleed fault during engine start, hydraulic failure during taxi)xxx
CLB CRZFuel leak (management of consequences)xxxX
TOMalfunction on take-off high speed below V1xxx
TOMalfunction on take-off high speed above V1xx
GNDDuring taxi to the runway, a spurious brake temperature announcement. The crew had the correct brake temperature moments before the failure.XXX
TOTyre failure during take-offxxx
TOMalfunction on initial climbxx
APPMalfunction on approachxxx
APPMalfunction on go-aroundxxx
LDGMalfunction during landingxxxxx
EVAL or SBTAircraft system managementBN/ANormal system operation according to defined instructionsThis is not considered as a stand-alone topic. It is linked with the topic ‘compliance’. Where a system is not managed according to normal or defined procedures, this is determined as a non-compliance.See ‘compliance’ topic above. There are no defined scenarios, but the instructor should focus on learning opportunities when system management non-compliances manifest themselves during other scenarios. Underpinning knowledge of systems and their interactions should be developed and challenged, and not merely the application of normal procedures.Intentionally blankX
CRZ APP LDGMinimum fuel, caused by extended delays, weather, etc. where the crew would need to manage a minimum fuel situation.xxxx
Approach, visibility close to minimumBAPPAny situation where visibility becomes a threatRecognise actual conditions. Observe aircraft and/or procedural limitations. Apply the appropriate procedures if applicable. Maintain directional control and safe flight path.Approach in poor visibilityxxxx
APPApproach in poor visibility with deteriorations necessitating a decision to perform a go-aroundxxx
LDGLanding in poor visibilityxxx
LandingBLDGPilots should have opportunities to practise landings in demanding situations at the defined frequency. Data indicates that landing problems have their roots in a variety of factors, including inappropriate decision-making, in addition to manual aircraft control skills if difficult environmental conditions exist. The purpose of this item is to ensure that pilots are exposed to this during the programme.Landing in demanding environmental conditions, with malfunctions as appropriateThis topic should be combined with the adverse-weather topic, aircraft system malfunctions topic or any topic that can provide exposure to a landing in demanding conditions.Intentionally blank
Assessment and training topicFrequencyFlight phase activationDescription (includes type of topic, being threat, error or focus)Desired outcome (includes performance criteria OR training outcome)Guidance material (GM) Example scenario elementsPROCOMFPAFPMLTWPSDSAWWLMKNO
EVAL or SBTSurpriseBALLThe data analysed during the development of the EBT concept indicated substantial difficulties encountered by crews when faced with a threat or error, which was a surprise or an unexpected event. The element of surprise should be distinguished from what is sometimes referred to as the ‘startle factor’ — the latter being a physiological reaction. Wherever possible, consideration should be given towards variations in the types of scenario, times of occurrences and types of occurrence, so that pilots do not become overly familiar with repetitions of the same scenarios. Variations should be the focus of EBT programme design, and not left to the discretion of individual instructors, in order to preserve programme integrity and fairness.Exposure to an unexpected event or sequence of events at the defined frequency in order to build resilience.Rejected take-offXXX
Intentionally blankIntentionally blank
EVAL or SBTWind shear recoveryBTOWith or without warnings including predictive. A wind shear scenario is ideally combined with an adverse-weather scenario containing other elements.Anticipate potential for wind shear. Avoid known wind shear or prepare for suspected wind shear. Recognise wind shear encounter. Take appropriate action. Apply the appropriate procedure correctly. Assure aircraft control. Recognise out of wind shear condition. Maintain or restore a safe flight path. Assess consequential issues and manage outcomes.Predictive wind shear warning during take-offxx
TOWind shear encounter during take-offxxx
TOWind shear encounter after rotationxx
TOPredictive wind shear after rotationxx
APPPredictive wind shear during approachxxx
APPWind shear encounter during go-aroundxxxx
APPWind shear encounter during approachxxx
EVAL or SBTWorkload, distraction, pressure, stressBALLThis is not considered a topic for specific attention on its own, but more as a reminder to programme developers to ensure that pilots are exposed to immersive training scenarios which expose them to manageable high workload and distractions during the course of the EBT programme, at the defined frequency.Manage available resources efficiently to prioritise and perform tasks in a timely manner under all circumstancesIntentionally blankIntentionally blank
Assessment and training topicFrequencyFlight phase activationDescription (includes type of topic, being threat, error or focus)Desired outcome (includes performance criteria OR training outcome)Guidance material (GM) Example scenario elementsPROCOMFPAFPMLTWPSDSAWWLMKNO
Section 7 — UPRT Upset recovery training topic with frequency (C). Manoeuvres training phase or scenario-based training phase (MT or SBT)
MT or SBTUpset recoveryCN/ACompliance with AMC1 or AMC2 to ORO.FC.220&230 Include the recovery exercises in Table 2 of AMC1 ORO.FC.220&230 for the recurrent training programme, such that all the exercises are covered over a period not exceeding 3 years. According to the principles of EBT, covering one component should satisfy the requirement to cover the whole element of recovery from developed upsets. The same principles apply to the exercises of components 2, 3 and 4 where one exercise may satisfy the requirement to cover the whole component. An aeroplane upset is defined as an undesired aeroplane state in flight characterised by unintentional divergences from parameters normally experienced during line operations or training. An aeroplane upset may involve pitch and/or bank angle divergences as well as inappropriate airspeeds for the conditions.Recognise upset condition. Make timely and appropriate intervention. Take appropriate action. Assure timely and appropriate intervention. (AMC1 ORO.FC.220&230 Table 2 component 1) Assure aircraft control. Maintain or restore a safe flight path. Assess consequential issues. Manage outcomes. Consolidate the summary of aeroplane recovery techniques. (AMC1 ORO.FC.220&230 Table 2 component 5) Note: The operator should assess if the exercises should be practised for the either seat qualification.The example scenario elements may be done in ISI, as non-ISI or a combination of both. If done in ISI: The instructor should position the aircraft within but close to the edge of the validated training envelope before handing control to the trainee to demonstrate the restoration of normal flight. Careful consideration should be given to flying within the validated training envelope.Intentionally blank
Table 2 of AMC1 ORO.FC.220&230: Exercises for upset recovery training
A.Recovery from developed upsets
CLB DES2.Recovery from stall events in the following configurations: take-off configuration, clean configuration low altitude, clean configuration near maximum operating altitude, and landing configuration during the approach phase.xxxx
CRZ3.Recovery from nose high at various bank anglesxxxx
CRZ4.Recovery from nose low at various bank anglesxxxx
CRZ
APPDemonstration at a normal cruising altitude. Set conditions and disable aircraft systems as necessary to enable trainee to perform stall recovery according to OEM instructions.xxx
CLB DESDemonstration at an intermediate altitude during early stages of the approach. Set conditions and disable aircraft systems as necessary to enable trainee to perform stall recovery according to OEM instructions.xxx
Recovery from a wake turbulence position with high-bank anglexxxx
Assessment and training topicFrequencyFlight phase activationDescription (includes type of topic, being threat, error or focus)Desired outcome (includes performance criteria OR training outcome)Guidance material (GM) Example scenario elementsPROCOMFPAFPMLTWPSDSAWWLMKNO
Section 8 — Training topics with frequency (C) in alphabetical order. Evaluation phase or scenario-based training phase (EVAL or SBT)
EVAL or SBTATCCALLATC error. Omission, miscommunication, garbled, poor quality transmission. All these act as distractions to be managed by the crew. The scenarios should be combined, where possible, with others of the same or higher weighting, the principal reason being to create distractions.Respond to communications appropriately. Recognise, clarify and resolve any ambiguities. Refuse or question unsafe instructions. Use standard phraseology whenever possible.ATC role-play: the instructor provides scripted instructions, as a distraction to the crewxxx
ALLController error, provided by the instructor according to a defined scripted scenarioxxxx
ALLFrequency congestion, with multiple aircraft using the same frequencyx
APPDestination temporarily closedxxxx
CRZRescue and firefighting services (RFFS) level reduction at destinationxxx
APPRunway change before the interception of the localiser or similar navigation aid in azimuthxxxx
GND/TOStray dogs at the opposite threshold runwayxxx
ALLPoor quality transmissionsx
EVAL or SBTEngine failureCTOAny engine failure or malfunction, which causes loss or degradation of thrust that affects performance. This is distinct from the engine-out manoeuvres described in the MT section above, which are intended only to practise psychomotor skills and reinforce procedures to manage engine failures.Recognise engine failure. Take appropriate action. Apply the appropriate procedure correctly. Maintain aircraft control. Manage consequences.Engine failure or engine malfunction on take-off low speedxxxx
TOEngine failure or engine malfunction on take-off high speed below V1xxxx
TOEngine failure or engine malfunction on take-off above V1xxxx
TOEngine failure or engine malfunction on initial climbxxx
APPEngine malfunctionxxx
CRZEngine failure in cruise (with autopilot)xxx
CRZMultiple engine failure in CRZ (volcanic ash, recoverable). Competency FPM may or may not be included depending on the impact on the automation.xxxx
LDGEngine failure or engine malfunction on landingx
EVAL or SBTFire and smoke managementCGNDThis includes engine, electric, pneumatic, cargo fire, smoke or fumes.Recognise fire, smoke or fumes. Take appropriate action. Apply the appropriate procedure correctly. Maintain aircraft control. Manage consequences.Fire in cargo or cabin/cockpit at gatexxxx
GNDFire during taxixxxxX
GNDFire with no cockpit indicationxxxxX
TOTake-off low speedxxxxX
TOFire or smoke on take-off high speed below V1xxxx
TOFire or smoke on take-off high speed above V1xxx
TOFire or smoke on Initial climbxxx
CRZCargo compartment fire or avionics compartment fire.xxx
APPEngine fire in approach (extinguishable)xx
APPEngine fire in approach (non-extinguishable)xxx
CLB CRZ DESLithium battery fire in the cockpit or cabin compartmentxxxxx
APPFlight deck or cabin firexxxX
GNDAny of the example scenario elements above ending in an evacuationxxxx
EVAL or SBTLoss of communicationsCGNDLost or difficult communications due to either pilot mis-selection or a failure external to the aircraft. This could be for a few seconds or a total loss.Recognise loss of communications. Take appropriate action. Execute the appropriate procedure as applicable. Use alternative ways to communicate. Manage consequences.Loss of communications during ground manoeuvringxx
TOLoss of communications after take-offxxX
APPLoss of communications during approach phase, including go-aroundxxxxX
Assessment and training topicFrequencyFlight phase activationDescription (includes type of topic, being threat, error or focus)Desired outcome (includes performance criteria OR training outcome)Guidance material (GM) Example scenario elementsPROCOMFPAFPMLTWPSDSAWWLMKNO
EVAL or SBTManaging loading, fuel, performance errorsCALLA calculation error by one or more pilots, or someone involved with the process, or the process itself, e.g. incorrect information on the load sheetAnticipate the potential for errors in load/fuel/performance data. Recognise inconsistencies. Manage/avoid distractions. Make changes to paperwork/aircraft system(s) to eliminate error. Identify and manage consequences.This can be a demonstrated error, in that the crew may be instructed to deliberately insert incorrect data — for example, to take off from an intersection with full-length performance information. The crew will be asked to intervene when acceleration is sensed to be lower than normal, and this may be part of the operator procedures, especially when operating mixed fleets with considerable variations in MTOM.xxx
TOWind report with take-off clearance not consistent with prior performance calculation. ATC, cabin crew or other people are pushing crew to take off quickly.xxxx
GNDEnvironmental change during taxi (e.g. heavy rain) not consistent with prior take-off performance calculationxx
GNDFuel ground staff on industrial action. Only limited amount of fuel available, which is below the calculated fuel for the flightxxxx
GNDAdvise crew that there is a change of the load sheet figures during taxi to the runway. The crew may have limited time due to a calculated take-off time (CTOT) — ATC slot.xx
GNDBraking action reported ‘medium’. The information is transmitted just before take-off. The flight is subject to a CTOT — ATC slot.xxx
EVAL or SBTNavigationCGNDExternal NAV failure. Loss of GPS satellite, ANP exceeding RNP, loss of external NAV source(s)Recognise a NAV degradation. Take appropriate action. Execute the appropriate procedure as applicable. Use alternative NAV guidance. Manage consequences.External failure or a combination of external failures degrading aircraft navigation performance on groundxxxx
TO CLB APP LDGExternal failure or a combination of external failures degrading aircraft navigation performance in flightxxxx
GNDStandard initial departure change during taxi. The flight may be subject to a CTOT — ATC slot.xxx
APPLoss of runway lighting below decision heightxxx
CRZNo fly zone: when the crew changes control frequency, the new ATCO informs the crew that they are flying over an unannounced ‘no fly zone’ that is not included in the NOTAMs. (To trigger such an event, the context may be as follows: an unexpected military conflict in the territory the aircraft is flying over or the crew is forced to re-route in flight and the new route flies over a city that has an important event such the Olympic games, a G20/G7 submit, or the route is flying near a space rocket launch close to the time of the launch, like the Guiana Space Centre, Cape Cañaveral, etc.).xxx
Operationsor type-specificCALLIntentionally blankIntentionally blankIntentionally blankIntentionally blank
Operations of special airport approvalCAPP LDGSee equivalency of approaches relevant to operations.The operator should comply with the national qualification requirements published in the AIP.Intentionally blankIntentionally blank
EVAL or SBTPilot incapacitationCTOConsequences for the non-incapacitated pilotRecognise incapacitation. Take appropriate action including correct stop/go decision. Apply the appropriate procedure correctly. Maintain aircraft control. Manage consequences.During take-offxxxxX
APPDuring approachxxxX
Runway or taxiway conditionCGND TO LDGContamination or surface quality of the runway, taxiway, or tarmac including foreign objectsRecognise hazardous runway condition. Observe limitations. Take appropriate action. Apply the appropriate procedures correctly. Assure aircraft control.Planned anticipated hazardous conditions with dispatch information provided to facilitate planning and execution of appropriate proceduresxX
GND TO LDGUnanticipated hazardous conditions, e.g. unexpected heavy rain resulting in flooded runway surfacexxx
TOTake-off on runway with reduced cleared width due to snowxxxx
TOStop/go decision in hazardous conditionsxxx
EVAL or SBTTerrainCALLAlert, warning, or conflictAnticipate terrain threats. Prepare for terrain threats. Recognise unsafe terrain clearance. Take appropriate action. Apply the appropriate procedures correctly. Maintain aircraft control. Restore safe flight path. Manage consequences.ATC clearance giving insufficient terrain clearancexxxX
ALLDemonstration of terrain avoidance warning systems (TAWS) (this scenario element may be done in an ISI.)xxx
TO CLBEngine failure where performance is marginal leading to TAWS warningxxx
DES APPATC provides a wrong QNHxx
DES‘Virtual mountain’ refers to the surprise element of an unexpected warning. Care should be exercised in creating a level of realism, so this can best be achieved by an unusual and unexpected change of route during the descent.xxx
TrafficCCLB CRZ DESTraffic conflict. ACAS RA or TA, or visual observation of conflict, which requires evasive manoeuvringAnticipate potential loss of separation. Recognise loss of separation. Take appropriate action. Apply the appropriate procedure correctly. Maintain aircraft control. Manage consequences.ACAS warning that requires crew interventionxxxx
Dilemma: Visual acquisition of conflicting traffic followed by an ACAS warning (resolution advisory) triggered by the same or other traffic. Even if the traffic is in sight, the pilot should follow the RA.xxx
While in descent, ACAS warning (traffic advisory) of an aircraft below. The crew should not initiate an avoidance manoeuvre based on TA (except decreasing the rate of descent unless otherwise instructed by ATC, etc.). This example scenario can be done during climb with conflicting traffic above.xxx

END GEN3 JET

AMC · AMC3 ORO.FC.232 — Regulation (EU) No 965/2012 · ED Decision 2022/014/R · Air OPS Easy Access Rules · EAR revision 27 Mar 2026

AMCAcceptable means of compliance

AMC4 ORO.FC.232EBT programme assessment and training topics

Show the text

GENERATION 3 (TURBOPROP) — TABLE OF ASSESSMENT AND TRAINING TOPICS

Assessment and training topicFrequencyDescription (includes type of topic, being threat, error or focus)Desired outcome (includes performance criteria OR training outcome)Flight phase activationGuidance material (GM) Example scenario elementsPROCOMFPAFPMLTWPSDSAWWLMKNO
Generation 3 Turboprop — Recurrent assessment and training matrixCompetency map
Section 1 — Skill retention. Manoeuvres training phase (MT)
MTRejected take-offARejected take-off after the application of takeoff thrust and before reaching V1 (may be in LVOs or CAT I or above)Demonstrate manual aircraft control skills with smoothness and accuracy as appropriate to the situation. Detect deviations through instrument scanning. Maintain spare mental capacity during manual aircraft control. Maintain the aircraft within the flight envelope. Apply knowledge of the relationship between aircraft attitude, speed and thrust.TOFrom initiation of take-off to complete stop (or as applicable to the procedure)xx
Failure of the critical engine between V1 and V2AFailure of the critical engine from V1 and before reaching V2 in the lowest CAT I visibility or in LVO meteorological (MET) conditions.TOThe manoeuvre is complete at a point when the aircraft is stabilised at normal engine-out climb speed with the correct pitch and lateral control, in trim condition and, as applicable, autopilot engagement. Only one failure of the critical engine between V1 and V2 a year may be done in LVO conditions.xx
Failure of one engine on take-offBFailure of one engine from V1 and before reaching V2 in the lowest CAT I visibility or in LVO MET conditions.TOThe manoeuvre is complete at a point when the aircraft is stabilised in a clean configuration with engine-out procedures completed. Only one failure of the critical engine between V1 and V2 a year may be done in LVO conditions.xx
Failure of one engine above V2 (any segment of the TO) in the lowest CAT I visibility or in LVO MET conditions.The manoeuvre is complete at a point when the aircraft is stabilised in a clean configuration with engine-out procedures completed.xxx
Emergency descentCInitiation of emergency descent from normal cruise altitudeCRZThe manoeuvre is complete once the aircraft is stabilised in emergency descent configuration (and profile). However, if the EBT programme does not include the example scenario element ‘emergency descent’ in the training topic ‘automation management’, the emergency descent procedures should be completed and should not stop once the aircraft is stabilised in emergency descent configuration.xxx
Engine-out approach & landingAWith the critical engine (if applicable) failed, normal landingLDGInitiation in a stabilised engine-out configuration from not less than 3 NM final approach, until completion of roll-outxx
Engine-out approach & go-aroundAWith the critical engine (if applicable) failed, manually flown normal precision approach to DA, followed by a manual go-around — the whole manoeuvre to be flown without visual referenceAPPThis manoeuvre should be flown from intercept to centreline until acceleration after go-around. The manoeuvre is complete at a point when the aircraft is stabilised at normal engine-out climb speed with the correct pitch and lateral control, in trim condition and, as applicable, autopilot engagement (describe generally the critical part of the manoeuvre).xx
Go-aroundAGo-around, all engines operativeAPPHigh energy, initiation during the approach at 150 to 300 m (500 to 1 000 ft) below the missed approach level-off altitudexxx
Initiation of a go-around from DA followed by visual circuit and landingxxx
During flare/rejected landingxxx
Pilot qualification to operate in either pilot’s seatBAs per ORO.FC.235APPComplete the manoeuvres mandated in ORO.FC.235.Intentionally left in blank.
Section 2 — Equivalency of approaches relevant to operations. Evaluation phase, manoeuvres training phase or scenario-based training phase (EVAL, MT or SBT)
MTApproach type A or BBApproach type A or B flight method 3DSee equivalency of approaches relevant to operations that place an additional demand on a proficient crewAPPSee equivalency of approaches relevant to operationsxxxxx
Approach type ABApproach type A flight method 2DSee equivalency of approaches relevant to operations that place an additional demand on a proficient crewAPPSee equivalency of approaches relevant to operationsxxxxx
EVAL or SBTApproach type ABApproach type A flight method 3D or 2DSee equivalency of approaches relevant to operations that place an additional demand on a proficient crewAPPSee equivalency of approaches relevant to operationsxxxxx
Approach type BBApproach type B flight method 3DSee equivalency of approaches relevant to operations that place an additional demand on a proficient crewAPPSee equivalency of approaches relevant to operationsxxxxx
Section 3 — Equivalency of approaches under specific approvals and Take-off under specific approvals. Evaluation phase, manoeuvres training phase or scenario-based training phase (EVAL, MT or SBT)
MTSPA approach(es)BApproach requiring specific approvalSee equivalency of approaches relevant to operations — specific approvalAPPApproaches flown from FAF to landing or go-aroundxxx
EVAL or SBTSPA approach(es)BApproach requiring specific approvalSee equivalency of approaches relevant to operations — specific approvalAPPApproaches flown from FAF to landing or go-aroundxxx
EVAL, MT or SBTSPA rejected take-off (RTO)BEngine failure after the application of take-off thrust and before reaching V1 (in low-visibility MET conditions, preferably in the lowest approved visibility) Low-visibility RTO is not required under Part SPA but instead in Appendix 9 Section 6. Note: AMC1 SPA.LVO.120 point (f) does not require a low-visibility RTO. RTO is required only in the initial LVO course (point (g)(1)(iii) of AMC1 SPA.LVO.120).Demonstrate manual aircraft control skills with smoothness and accuracy as appropriate to the situation. Detect deviations through instrument scanning. Maintain spare mental capacity during manual aircraft control. Maintain the aircraft within the flight envelope. Apply knowledge of the relationship between aircraft attitude, speed and thrust.TORTO — can be combined with the assessment and training topic ‘surprise’ in EVAL or SBTxx
VAL, MT or SBTLVTOBNotwithstanding AMC1 SPA.LVO120 point (f)(1) AMC1 SPA.LVO.120 requires SPA manoeuvres in the frequency of the OPC, as OPC is substituted in the EBT programme. Thus, the frequency in EBT is determined in every cycle (B). Low-visibility take-off, preferably in the lowest approved visibilityTOThe manoeuvre is complete at a point when the aircraft is stabilised at normal climb speed with the correct pitch and lateral control, in trim condition and, as applicable, autopilot engagement.xx
Assessment and training topicFrequencyFlight phase activationDescription (includes type of topic, being threat, error or focus)Desired outcome (includes performance criteria OR training outcome)Guidance material (GM) Example scenario elementsPROCOMFPAFPMLTWPSDSAWWLMKNO
Generation 3 Turboprop — Recurrent assessment and training matrixCompetency map
Section 4 — Training topics with frequency (A) in alphabetical order. Evaluation phase or scenario-based training phase (EVAL or SBT)
EVAL or SBTAdverse weatherAGNDThunderstorm, heavy rain, turbulence, ice build-up to include de-icing issues, as well as high-temperature conditions. The proper use of anti-ice and de-icing systems should be included generally in appropriate scenarios.Anticipate adverse weather. Prepare for suspected adverse weather. Recognise adverse weather. Take appropriate action. Apply the appropriate procedure correctly. Assure aircraft control.Predictive wind shear warning before take-off, as applicablexxx
ALLAdverse-weather scenario, e.g. thunderstorm activity, precipitation, icingxxxx
TOWind shear encounter during take-off, not predictivexxxx
TOPredictive wind shear warning during take-offxxxx
TOCrosswinds with or without strong gusts on take-offxx
CRZTurbulence that increases to severe turbulencexxxx
CRZWind shear encounter scenario during cruisexxxxx
APPReactive wind shear warning during approach or go-aroundxxxx
APPPredictive wind shear warning during approach or go-aroundxxxx
APPThunderstorm encounter during approach or on missed approachxxx
APPIncreasing tailwind on final approach (not reported)xxxx
APPApproach and landing in demanding weather conditions, e.g. turbulence, up and downdrafts, gusts and crosswinds including shifting wind directionsxxx
APPNon-precision approach in cold-temperature conditions, requiring altitude compensation for temperature, as applicable to the typexxx
APP LDGCrosswinds with or without strong gusts on approach, final approach and landing (within and beyond limits)xxx
APPIn approach, unexpected braking action ‘good to medium’ reported by the preceding aircraftxxxx
APPModerate to severe icing conditions during approach effecting aircraft performancexxxx
APPReduced visibility even after acquiring the necessary visual reference during approach, due to rain or fogxxx
EVAL or SBTAutomation managementACLB CRZ DES APPThe purpose of this topic is to encourage and develop effective flight path management through proficient and appropriate use of the flight management system(s), guidance and automation, including transitions between modes, monitoring, mode awareness, vigilance and flexibility needed to change from one mode to another. The means of mitigating errors are included in this topic. The errors are described as mishandled auto flight systems, inappropriate mode selection, mishandled flight management system(s) and inappropriate autopilot usage.Know how and when to use the flight management system(s), guidance and automation. Demonstrate correct methods for engagement and disengagement of the auto flight system(s). Demonstrate appropriate use of flight guidance, auto thrust and other automation systems. Maintain mode awareness of the auto flight system(s), including engagement and automatic transitions. Revert to different modes when appropriate. Detect deviations from the desired aircraft state (flight path, speed, attitude, thrust, etc.) and take appropriate action. Anticipate mishandled auto flight system. Recognise mishandled auto flight system. Take appropriate action if necessary. Restore correct auto flight state. Identify and manage consequences.ACAS warning (resolution advisory), recovery and subsequent engagement of automationxx
ALLFMS tactical programming issues, e.g. step climb, runway changes, late clearances, destination re-programming, executing diversionxxx
CLB CRZ DES APPRecoveries from TAWS, management of energy state to restore automated flightxxx
CLB CRZ DES APPAmendments to ATC cleared levels during altitude capture modes to force mode awareness and interventionxxx
ACAS warning (resolution advisory to level off) during climb or descent; for example, close to the cleared level when the capture mode has already been activated.xxx
TOLate ATC clearance to an altitude below acceleration altitudexxx
TO APPEngine-out special terrain proceduresxxx
CRZForcing autopilot disconnect followed by re-engagement, recovery from lowor high-speed events in cruisexxxx
CLBEngine failure during or after initial climb using automationxx
CRZEngine failure in cruise to onset of descent using automationxx
CRZEmergency descentxxx
DES APPManaging high-energy descent capturing descent path from above (correlation with unstable approach training)xxxx
APPNo ATC clearance received prior to commencement of approach or final descentxxx
APPReactive wind shear and recovery from the consequent high-energy statexxx
APPAutomation fail to capture the approach altitude in descent (e.g. last altitude before the FAP). Ideally, the failure occurs when the workload is high (e.g. configuration of the aircraft for final approach).xxxx
APPNon-precision or infrequently flown approaches using the maximum available level of automationxxx
APPGear malfunction during an approach planned with autoland (including autobrake). Competency FPA may or may not be included depending on the impact of such malfunction on the automation.xxx
APPATC clearances to waypoints beyond the programmed descent point for a coded final descent point during an approach utilising a final descent that is commanded by the flight management systemxxxx
EVAL or SBTCompetencies — non-technical (CRM)AAPPThis encapsulates the general CRM principles and objectives. It includes communication; leadership and teamwork; problem-solving and decision-making; situation awareness and management of information; and workload management. Emphasis should be placed on the development of leadership, shown by EBT data sources to be a highly effective competency in mitigating risk and improving safety through pilot performance.Exposure to an event or sequence of events to allow the pilot to build awareness of human factors in aviation and the human limitations. This includes the development of the following competencies: Communication: Demonstrate: — effective use of language; — responsiveness to feedback; and — capability to state the plans and resolve ambiguities. Leadership and teamwork: Use appropriate authority to ensure focus on the task. Support others in completing tasks. Problem-solving and decision-making: Detect deviations from the desired state, evaluate problems, identify the risk, consider alternatives and select the best course of action. Continuously review progress and adjust plans. Situation awareness and management of information: Have an awareness of the aircraft state in its environment; project and anticipate changes. Workload management: Prioritise, delegate and receive assistance to maximise focus on the task. Continuously monitor the flight progress.GPS failure prior to commencement of approach associated with position drift and a terrain alertxxxx
DESCabin crew report of water noise below the forward galley indicating a possible toilet pipe leak, with consequent avionics failuresxxx
CRZSmoke removal but combined with a diversion until landing is completed.xxxxxx
GNDApron fuel spillingxxx
CRZImportant water leak in an aircraft galleyxxxx
ALLA relevant number of cabin crew are wounded or incapacitated. Additionally, the cabin crew wounded or incapacitated are the most competent (e.g. senior cabin crew member).xxx
ALLUnruly passenger(s)xx
GNDPassenger oxygen: passenger service unit open and mask falling downxxx
ALLPassenger with medical problems — medical emergencyxx
CRZCredible threat reported to the crew. Stowaway or fugitive on board.xxxx
GNDNo METAR or TAFOR is available for destination due to industrial action at the destination airportxxxx
CRZCredible bomb threat reported to crewxxxx
CLB DESCredible bomb threat or pressurisation problem, but no quick landing possible (due to weather, terrain or other reasons)xxxx
APPDiversion with low remaining fuel or increased fuel flow due to system malfunctionxxxx
EVAL or SBTAPPACAS warning (resolution advisory) immediately following a go-around, with a descent manoeuvre required. (The RA should be a command for descent when the aircraft is above 1 100 ft AGL.)xxxxx
EVAL or SBTComplianceAALLCompliance failure. Consequences of not complying with operating instructions (e.g. SOPs). This is not intended to list example scenario elements, but instructors should ensure that observed non-compliances are taken as learning opportunities throughout the programme. In all modules of the programme, the FSTD should as far as possible be treated like an aircraft, and non-compliances should not be accepted simply for expediency.Recognise that a compliance failure has occurred. Make a verbal announcement. Take appropriate action if necessary. Restore safe flight path if necessary. Manage consequences.The following are examples of potential compliance failures and are not intended to be developed as scenarios as part of an EBT module: 1. Requesting flap beyond limit speed 2. Flaps or slats in the wrong position for phase of flight or approach 3. Omitting an action as part of a procedure 4. Failing to initiate or complete a checklist 5. Using the wrong checklist for the situationIntentionally blank
EVAL or SBTGo-around managementAAPPAny threat or error that can result in circumstances that require a decision to perform a go-around, in addition to the execution of the go-around. Go-around scenarios should be fully developed to encourage effective leadership and teamwork, in addition to problem-solving and decision-making, plus execution using manual aircraft control or the flight management system(s) and automation as applicable. Design should include the element of surprise, and scenario-based go-arounds should not be predictable and anticipated. This topic is completely distinct from the go-around manoeuvre listed in the MT section that is intended only to practise psychomotor skills and a simple application of the procedures.Adverse-weather scenario leading to a reactive wind shear warning during approachxxxx
APPAdverse-weather scenario leading to a predictive wind shear warning during approach or go-aroundxxxx
APPAdverse-weather scenario, e.g. thunderstorm activity, heavy precipitation or icing forcing decision at or close to DA/MDAxxxx
APPDA with visual reference in heavy precipitation with doubt about the runway surface braking capabilityxxxx
APPAdverse-wind scenario resulting in increasing tailwind below DA (not reported)xxx
APPAdverse-wind scenario including strong gusts and/or crosswind out of limits below DA (not reported)xxx
APPAdverse-wind scenario including strong gusts and/or crosswind out of limits below 15 m (50 ft) (not reported)xxx
APPLost or difficult communications resulting in no approach clearance prior to commencement of approach or final descentxxx
APPBirds: large flocks of birds below DA once visual reference has been establishedxxx
APPSystem malfunction, landing gear malfunction during the approach
EVAL or SBTManual aircraft controlACLB CRZ DES APPControls the flight path through manual controlDemonstrate manual aircraft control skills with smoothness and accuracy as appropriate to the situation. Detect deviations through instrument scanning. Maintain spare mental capacity during manual aircraft control. Maintain the aircraft within the normal flight envelope. Apply knowledge of the relationship between aircraft attitude, speed and thrust.Flight with unreliable airspeed, which may or may not be recoverablexxxx
CLB CRZ DES APPAlternate flight control modes according to malfunction characteristicsxxxx
CLB CRZ DES APPACAS warning (resolution advisory) requires the pilot to descend or ATC calls for immediate descent (preferably during climb which requires a significant change in aircraft attitude)xxx
ACAS warning (resolution advisory) requires the pilot to climb or ATC calls for immediate climb (preferably during descent which requires a significant change in aircraft attitude).xxx
DESTAWS warning when deviating from planned descent routing, requiring immediate responsexxx
TOScenario immediately after take-off which requires an immediate and overweight landingxxxx
TOAdverse wind, crosswinds with or without strong gusts on take-offxx
TOAdverse weather, wind shear, wind shear encounter during take-off, with or without reactive warningsxxx
TOEngine failure during initial climb, typically 30-60 m (100-200 ft) (autopilot off)xxxx
CRZWind shear encounter scenario during cruise, significant and rapid change in wind speed or down/updrafts, without wind shear warningxxxxx
APPAdverse weather, wind shear, wind shear encounter with or without warning during approachxxxx
APPAdverse weather, deterioration in visibility or cloud base, or adverse wind, requiring a go-around from visual circling approach, during the visual segmentxxxxxxx
APPInterception of the glide slope from above (correlation with unstable approach training)xxx
APP LDGAdverse wind, crosswinds with or without strong gusts on approach, final approach and landing (within and beyond limits)xxx
APP LDGAdverse weather, adverse wind, approach and landing in demanding weather conditions, e.g. turbulence, up and downdrafts, gusts and crosswinds including shifting wind directionsxxx
APP LDGCircling approach manually flown at night in minimum in-flight visibility to ensure ground reference, minimum environmental lighting and no glide slope guidance lightsxxxx
APP LDGRunway incursion during approach, which can be triggered by ATC at various altitudes or by visual contact during the landing phasexxx
LDGAdverse wind, visibility, type-specific, special consideration for long-bodied aircraft, landing in minimum visibility for visual reference, with crosswindxxxx
LDGSystem malfunction, auto flight failure at DA during a low-visibility approach requiring a go-around flown manuallyxxxx
APP LDGApproach planned with autoland, followed by a failure below 1 000 ft requiring a manual go-around and an immediate landing due to fuel shortagexxxx
TOIn-seat instruction: Insufficient engine failure recovery, forcing the pilot monitoring to take over the flight controlsxxxx
APP LDGIn-seat instruction: Unstable approach on short final or long landing, forcing the pilot monitoring to take over the flight controlsxxxx
EVAL or SBTMonitoring, cross-checking, error management, mismanaged aircraft stateAALLThe scenarios should be realistic and relevant, and should be used for the purpose of demonstration and reinforcement of effective monitoring. Modules in the FSTD should be treated like those in an aircraft so that trainees have the opportunity to develop the competency with the practice of the right techniques and attitudes related to these topics through pilot performance, and that instructors have the opportunity to assess and train these topics in a realistic environment. As shown by the EBT data report, these topics are of key importance to improve safety in operations. In addition, the operator may also use these topics to develop scripted role-playing scenarios in the form of ISI. These scenarios cater for the need to monitor flight path excursions from the instructor pilot (PF), detect errors and make appropriate interventions, either verbally or by taking control as applicable. Demonstration scenarios may also be used. Demonstrated role-play should contain realistic and not gross errors, leading at times to a mismanaged aircraft state, which can also be combined with upset management training.Recognise mismanaged aircraft state. Observe the pilot’s behaviour: how the pilot is mitigating errors, performing cross-checking, monitoring performance and dealing with a mismanaged aircraft state, in order to ensure that observed deviations, errors and mistakes are taken as learning opportunities throughout the programme. Monitor flight path excursions. Detect errors and threats through proper cross-checking performance. Make appropriate interventions either verbally or by taking control if applicable. Take appropriate action if necessary. Restore the desired aircraft state. Identify and manage consequences.Deviations from the flight path, in pitch attitude, speed, altitude, bank anglexx
ALLIn-seat instruction: Simple automation errors (e.g. incorrect mode selection, attempted engagement without the necessary conditions, entering wrong altitude or speed, failure to execute the desired mode) culminating in a need for direct intervention from the pilot monitoring, and where necessary taking control.xx
APPIn-seat instruction: Unstable approach or speed/path/vertical rate not congruent with the required state for the given flight conditionxxxx
LDGIn-seat instruction: Demonstration exercise — recovery from bounced landing, adverse wind, strong gusts during landing phase, resulting in a bounce and necessitating recovery action from the pilot monitoringxxx
Unstable approachADES APPReinforce stabilised approach philosophy and adherence to defined parameters. Encourage go-arounds when crews are outside these parameters. Develop and sustain competencies related to the management of high-energy situations.ATC or terrain-related environment creating a high-energy descent with the need to capture the optimum profile to complete the approach in a stabilised configurationxxx
DES APPATC or terrain-related environment creating a high-energy descent leading to unstable conditions and requiring a go-aroundxxx
APPApproach and landing in demanding weather conditions, e.g. turbulence, up and downdrafts, gusts and crosswinds including shifting wind directionsxxx
APPIncreasing tailwind on final approach (not reported)xxxx
APP LDGCrosswinds with or without strong gusts on approach, final approach and landing (within and beyond limits)xxx
Section 5 — UPRT training topic with frequency (B). Evaluation phase, manoeuvres training phase or scenario-based training phase (EVAL, MT or SBT)
EVAL, MT or SBTUpset prevention trainingBN/ACompliance with AMC1 or AMC2 to ORO.FC.220&230 Include upset prevention elements in Table 1 for the recurrent training programme in at least every cycle, such that all the elements are covered over a period not exceeding 3 years. The elements are numbered with letters from A to I in Table 1 of AMC1 ORO.FC.220&230. Each element is made up of several numbered components. According to the principles of EBT, covering one component should satisfy the requirement to cover the whole element of recognising and preventing the development of upset conditions.Early recognition and prevention of upset conditions. When the differences between LHS and RHS are not significant in the handling of the aircraft, UPRT may be conducted in either seat.See Table 1 of AMC1 ORO.FC.220&230: Elements and respective components of upset prevention training.Intentionally blank
CRZDemonstration of the defined normal flight envelope and any associated changes in flight instruments, flight director systems, and protection systems. This should take the form of an instructor-led exercise to show the crew the points beyond which an upset condition could exist.xxx
TO APPSevere wind shear or wake turbulence during take-off or approachxxxx
CRZAs applicable and relevant to the aircraft type, demonstration at a suitable intermediate level, with turbulence as appropriate; practise steep turns and note the relationship between bank angle, pitch and stalling speedxxx
CRZAt the maximum cruise flight level for the current aircraft weight, turbulence to trigger overspeed conditions (if FSTD capability exists, consider use of the vertical wind component to add realism)xxxx
CRZAt the maximum cruise flight level for the current aircraft weight, turbulence and significant temperature rise to trigger low-speed conditions (if FSTD capability exists, consider use of the vertical wind component to add realism)xxxx
CRZHigh-altitude loss of reliable airspeedxxxxx
CRZHigh-altitude ACAS RA (where the RA is required to be flown in manual flight)xxxx
Section 6 — Training topics with frequency (B) in alphabetical order. Evaluation phase or scenario-based training phase (EVAL or SBT)
EVAL or SBTAircraft system malfunctions, including operations under MELBALLAny internal failure(s) apparent or not apparent to the crew Any item cleared by the MEL but having an impact upon flight operations — for instance, thrust reverser locked. Malfunctions to be considered should have one or more of the following characteristics: Immediacy Complexity Degradation of aircraft control Loss of primary instrumentation Management of consequences The operator should vary malfunctions for each characteristic over the EBT cycle. Unless specified otherwise in the operational suitability data, at least one malfunction with each characteristic should be included in every cycle. Combining characteristics should not reduce the number of malfunctions below seven for each cycle. For each crew member, the characteristics of degraded control and loss of instrumentation should be in the role of pilot flying and the others may be in the role of pilot flying or pilot monitoring. For full details, see the malfunction equivalency methodology.Recognise system malfunction. Take appropriate action including correct stop/go decision. Apply the appropriate procedure correctly. Maintain aircraft control. Manage consequences. Apply crew operating procedures where necessary. Respond appropriately to additional system abnormalities associated with MEL dispatch.(i) System malfunctions that require immediate and urgent crew intervention or decision, e.g. fire, smoke, loss of pressurisation at high altitude, failures during take-off, brake failure during landing. (ii) System malfunctions that require complex procedures, e.g. multiple hydraulic system failures, smoke and fumes procedures, major electrical system failure. (iii) System malfunctions that result in significant degradation of flight controls in combination with abnormal handling characteristics, e.g. jammed flight controls, certain degradation of FBW control, jammed horizontal stabiliser; flaps and/or slats locked; other malfunctions that result in degraded flight controls. (iv) System failures that require monitoring and management of the flight path using degraded or alternative displays, unreliable primary flight path information, unreliable airspeed, e.g. flight with unreliable airspeed (v) System failures that require extensive management of their consequences (independent of operation or environment), e.g. fuel leak.Intentionally blank
TOMEL items with crew operating procedures applicable during take-offxx
TOResponse to an additional factor that is affected by an MEL item (e.g. system failure, runway state)xxxx
GNDMalfunction during preflight preparation and prior to departurexxx
CLBMalfunction after departurexxxx
ALLMalfunctions that require immediate attention (e.g. bleed fault during engine start, hydraulic failure during taxi)xxx
CLB CRZFuel leak (management of consequences)xxxx
TOMalfunction on take-off high speed below V1xxx
TOMalfunction on take-off high speed above V1xx
GNDDuring taxi to the runway, a spurious brake temperature announcement. The crew had the correct brake temperature moments before the failure.xxx
TOTyre failure during take-offxxx
TOMalfunction on initial climbxx
APPMalfunction on approachxxx
APPMalfunction on go-aroundxxx
LDGMalfunction during landingxxxxx
EVAL or SBTAircraft system managementBNormal system operation according to defined instructionsThis is not considered as a stand-alone topic. It is linked with the topic ‘compliance’. Where a system is not managed according to normal or defined procedures, this is determined as a non-compliance.See ‘compliance’ topic above. There are no defined scenarios, but the instructor should focus on learning opportunities when system management non-compliances manifest themselves during other scenarios. Underpinning knowledge of systems and their interactions should be developed and challenged, and not merely the application of normal procedures.Intentionally blankx
CRZ APP LDGMinimum fuel, caused by extended delays, weather, etc. where the crew would need to manage a minimum fuel situationxxxx
Approach, visibility close to minimumBAPPAny situation where visibility becomes a threatRecognise actual conditions. Observe aircraft and/or procedural limitations. Apply the appropriate procedures if applicable. Maintain directional control and safe flight path.Approach in poor visibilityxxxx
APPApproach in poor visibility with deteriorations necessitating a decision to perform a go-aroundxxx
LDGLanding in poor visibilityxxx
LandingBLDGPilots should have opportunities to practise landings in demanding situations at the defined frequency. Data indicates that landing problems have their roots in a variety of factors, including inappropriate decision-making, in addition to manual aircraft control skills if difficult environmental conditions exist. The purpose of this item is to ensure that pilots are exposed to this during the programme.Landing in demanding environmental conditions, with malfunctions as appropriateThis topic should be combined with the adverse-weather topic, aircraft system malfunctions topic or any topic that can provide exposure to a landing in demanding conditions.Intentionally blank
EVAL or SBTSurpriseBALLThe data analysed during the development of the EBT concept indicated substantial difficulties encountered by crews when faced with a threat or error, which was a surprise or an unexpected event. The element of surprise should be distinguished from what is sometimes referred to as the ‘startle factor’ — the latter being a physiological reaction. Wherever possible, consideration should be given towards variations in the types of scenario, times of occurrences and types of occurrence, so that pilots do not become overly familiar with repetitions of the same scenarios. Variations should be the focus of EBT programme design, and not left to the discretion of individual instructors, in order to preserve programme integrity and fairness.Exposure to an unexpected event or sequence of events at the defined frequency in order to build resilience.Rejected take-offxxx
Intentionally blankIntentionally blank
EVAL or SBTTerrainBALLAlert, warning, or conflictAnticipate terrain threats. Prepare for terrain threats. Recognise unsafe terrain clearance. Take appropriate action. Apply the appropriate procedures correctly. Maintain aircraft control. Restore safe flight path. Manage consequences.ATC clearance giving insufficient terrain clearancexxx
ALLDemonstration of terrain avoidance warning systems (TAWS) (this scenario element may be done in an ISI.)xxx
TO CLBEngine failure where performance is marginal leading to TAWS warningxxx
DES APPATC provides a wrong QNHxx
DES‘Virtual mountain’ refers to the surprise element of an unexpected warning. Care should be exercised in creating a level of realism, so this can best be achieved by an unusual and unexpected change of route during the descent.xxx
EVAL or SBTWind shear recoveryBTOWith or without warnings including predictive. A wind shear scenario is ideally combined with an adverse-weather scenario containing other elements.Anticipate potential for wind shear. Avoid known wind shear or prepare for suspected wind shear. Recognise wind shear encounter. Take appropriate action. Apply the appropriate procedure correctly. Assure aircraft control. Recognise out of wind shear condition. Maintain or restore a safe flight path. Assess consequential issues and manage outcomes.Predictive wind shear warning during take-offxx
TOWind shear encounter during take-offxxx
TOWind shear encounter after rotationxx
TOPredictive wind shear after rotationxx
APPPredictive wind shear during approachxxx
APPWind shear encounter during go-aroundxxxx
APPWind shear encounter during approachxxx
Workload, distraction, pressure, stressBALLThis is not considered a topic for specific attention on its own, but more as a reminder to programme developers to ensure that pilots are exposed to immersive training scenarios which expose them to manageable high workload and distractions during the course of the EBT programme, at the defined frequency.Manage available resources efficiently to prioritise and perform tasks in a timely manner under all circumstances.Intentionally blankIntentionally blank
Section 7 — UPRT Upset recovery training topic with frequency (C). Manoeuvres training phase or scenario-based training phase (MT or SBT)
MT or SBTUpset recoveryCN/ACompliance with AMC1 or AMC2 to ORO.FC.220&230 Include the recovery exercises in Table 2 of AMC1 ORO.FC.220&230 for the recurrent training programme, such that all the exercises are covered over a period not exceeding 3 years. According to the principles of EBT, covering one component should satisfy the requirement to cover the whole element of recovery from developed upsets. The same principles apply to the exercises of components 2, 3 and 4 where one exercise may satisfy the requirement to cover the whole component. An aeroplane upset is defined as an undesired aeroplane state in flight characterised by unintentional divergences from parameters normally experienced during line operations or training. An aeroplane upset may involve pitch and/or bank angle divergences as well as inappropriate airspeeds for the conditions.Recognise upset condition. Make timely and appropriate intervention. Take appropriate action. Assure timely and appropriate intervention. (AMC1 ORO.FC.220&230 Table 2 component 1) Assure aircraft control. Maintain or restore a safe flight path. Assess consequential issues. Manage outcomes. Consolidate the summary of aeroplane recovery techniques. (AMC1 ORO.FC.220&230 Table 2 component 5) Note: The operator should assess if the exercises should be practised for the either seat qualification.The example scenario elements may be done in ISI, as non-ISI or a combination of both. If done in ISI: The instructor should position the aircraft within but close to the edge of the validated training envelope before handing control to the trainee to demonstrate the restoration of normal flight. Careful consideration should be given to flying within the validated training envelope.Intentionally blank
Table 2 of AMC1 ORO.FC.220&230: Exercises for upset recovery training
A.Recovery from developed upsets
CLB DES2.Recovery from stall events in the following configurations: take-off configuration, clean configuration low altitude, clean configuration near maximum operating altitude, and landing configuration during the approach phase.xxxx
CRZ3.Recovery from nose high at various bank anglesxxxx
CRZ4.Recovery from nose low at various bank anglesxxxx
CRZ
APPDemonstration at a normal cruising altitude. Set conditions and disable aircraft systems as necessary to enable trainee to perform stall recovery according to OEM instructions.xxx
CLB DESDemonstration at an intermediate altitude during early stages of the approach. Set conditions and disable aircraft systems as necessary to enable trainee to perform stall recovery according to OEM instructions.xxx
Recovery from a wake turbulence position with high-bank anglexxxx
Section 8 — Training topics with frequency (C) in alphabetical order. Evaluation phase or scenario-based training phase (EVAL or SBT)
EVAL or SBTAdverse windCTOAdverse wind/crosswind. This includes tailwind but not ATC mis-reporting of the actual wind.Recognise adverse-wind conditions. Observe limitations. Apply the appropriate procedures. Maintain directional control and safe flight path.Take-off with different crosswind/tailwind/gust conditionsxx
TOTake-off with unreported tailwindxx
TOCrosswinds with or without strong gusts on take-offxx
APPWind exceeding limits on final approach (not reported)xxxx
APPWind exceeding limits on final approach (reported) in manual aircraft controlxxxx
APPIncreasing tailwind on final approach (not reported)xxxx
APPApproach and landing in demanding weather conditions, e.g. turbulence, up and downdrafts, gusts and crosswind including shifting wind directionsxxx
APPAdverse-wind scenario resulting in increasing tailwind below DA (not reported)xxx
APPAdverse-wind scenario including strong gusts and/or crosswind out of limits below DA (not reported)xxx
APPAdverse-wind scenario including strong gusts and/or crosswind out of limits below 15 m (50 ft) (not reported)xxx
APP LDGCrosswind with or without strong gusts on approach, final approach and landing (within and beyond limits)xxx
EVAL or SBTATCCALLATC error. Omission, miscommunication, garbled, poor quality transmission. All these act as distractions to be managed by the crew. The scenarios should be combined, where possible, with others of the same or higher weighting, the principal reason being to create distractions.Respond to communications appropriately. Recognise, clarify and resolve any ambiguities. Refuse or question unsafe instructions. Use standard phraseology whenever possible.ATC role-play: the instructor provides scripted instructions, as a distraction to the crewxxx
ALLController error, provided by the instructor according to a defined scripted scenarioxxxx
ALLFrequency congestion, with multiple aircraft using the same frequencyx
APPDestination temporarily closedxxxx
CRZRescue and firefighting services (RFFS) level reduction at destinationxxx
APPRunway change before the interception of the localiser or similar navigation aid in azimuthxxxx
GND TOStray dogs at the opposite threshold runwayxxx
ALLPoor quality transmissionsx
EVAL or SBTEngine failureCTOAny engine failure or malfunction, which causes loss or degradation of thrust that affects performance. This is distinct from the engine-out manoeuvres described in the MT section above, which are intended only to practise psychomotor skills and reinforce procedures to manage engine failures.Recognise engine failure. Take appropriate action. Apply the appropriate procedure correctly. Maintain aircraft control. Manage consequences.Engine failure or engine malfunction on take-off low speedxxxx
TOEngine failure or engine malfunction on take-off high speed below V1xxxx
TOEngine failure or engine malfunction on take-off above V1xxxx
TOEngine failure or engine malfunction on initial climbxxx
APPEngine malfunctionxxx
CRZEngine failure in cruise (with autopilot)xxx
LDGEngine failure or engine malfunction on landingx
EVAL or SBTFire and smoke managementCGNDThis includes engine, electric, pneumatic, cargo fire, smoke or fumes.Recognise fire, smoke or fumes. Take appropriate action. Apply the appropriate procedure correctly. Maintain aircraft control. Manage consequences.Fire in cargo or cabin/cockpit at gatexxxx
GNDFire during taxixxxxx
GNDFire with no cockpit indicationxxxxx
TOTake-off low speedxxxxx
TOFire or smoke on take-off high speed below V1xxxx
TOFire or smoke on take-off high speed above V1xxx
TOFire or smoke on initial climbxxx
CRZCargo firexxx
APPEngine fire in approach (extinguishable)xx
APPEngine fire in approach (non-extinguishable)xxx
CLB CRZ DESLithium battery fire in the cockpit or cabin compartmentxxxxx
APPFlight deck or cabin firexxxx
GNDAny of the example scenario elements above ending in an evacuationxxxx
EVAL or SBTLoss of communicationsCGNDLost or difficult communications due to either pilot mis-selection or a failure external to the aircraft. This could be for a few seconds or a total loss.Recognise loss of communications. Take appropriate action. Execute the appropriate procedure as applicable. Use alternative ways to communicate. Manage consequences.Loss of communications during ground manoeuvringxx
TOLoss of communications after take-offxxx
APPLoss of communications during approach phase, including go-aroundxxxxx
EVAL or SBTManaging loading, fuel, performance errorsCALLA calculation error by one or more pilots, or someone involved with the process, or the process itself, e.g. incorrect information on the load sheetAnticipate the potential for errors in load/fuel/performance data. Recognise inconsistencies. Manage/avoid distractions. Make changes to paperwork/aircraft system(s) to eliminate error. Identify and manage consequences.This can be a demonstrated error, in that the crew may be instructed to deliberately insert incorrect data — for example, to take off from an intersection with full-length performance information. The crew will be asked to intervene when acceleration is sensed to be lower than normal, and this may be part of the operator procedures, especially when operating mixed fleets with considerable variations in MTOM.xxx
GNDFuel ground staff on industrial action. Only limited amount of fuel available, which is below the calculated fuel for the flight.xxxx
GNDAdvise crew that there is a change of the load sheet figures during taxi to the runway. The crew may have limited time due to a calculated take-off time (CTOT) — ATC slot.xx
GNDBraking action reported ‘medium’. The information is transmitted just before take-off. The flight is subject to a (CTOT) — ATC slot.xxx
EVAL or SBTNavigationCGNDExternal NAV failure. Loss of GPS satellite, ANP exceeding RNP, loss of external NAV source(s)Recognise a NAV degradation. Take appropriate action. Execute the appropriate procedure as applicable. Use alternative NAV guidance. Manage consequences.External failure or a combination of external failures degrading aircraft navigation performance on groundxxxx
TO CLB APP LDGExternal failure or a combination of external failures degrading aircraft navigation performance in flightxxxx
GNDStandard initial departure change during taxi. The flight may be subject to a CTOT — ATC slot.xxx
APPLoss of runway lighting below decision heightxxx
CRZNo fly zone: when the crew changes control frequency, the new ATCO informs the crew that they are flying over an unannounced ‘no fly zone’ that is not included in the NOTAMs. (To trigger such an event, the context may be as follows: an unexpected military conflict in the territory the aircraft is flying over or the crew is forced to re-route in flight and the new route flies over a city that has an important event such the Olympic games, a G20/G7 submit, or the route is flying near a space rocket launch close to the time of the launch, like the Guiana Space Centre, Cape Cañaveral, etc.).xxx
Operationsor type-specificCALLIntentionally blankIntentionally blankIntentionally blankIntentionally blank
Operations of special airport approvalCAPP LDGSee equivalency of approaches relevant to operations.The operator should comply with the national qualification requirements published in the Aeronautical Information Publication.Intentionally blankIntentionally blank
EVAL or SBTPilot incapacitationCTOConsequences for the non-incapacitated pilotRecognise incapacitation. Take appropriate action including correct stop/go decision. Apply the appropriate procedure correctly. Maintain aircraft control. Manage consequences.During take-offxxxxx
APPDuring approachxxxx
Runway or taxiway conditionCGND TO LDGContamination or surface quality of the runway, taxiway, or tarmac including foreign objectsRecognise hazardous runway condition. Observe limitations. Take appropriate action. Apply the appropriate procedures correctly. Assure aircraft control.Planned anticipated hazardous conditions with dispatch information provided to facilitate planning and execution of appropriate proceduresxx
GND TO LDGUnanticipated hazardous conditions, e.g. unexpected heavy rain resulting in flooded runway surfacexxx
TOTake-off on runway with reduced cleared width due to snowxxxx
TOStop/go decision in hazardous conditionsxxx
EVAL or SBTTrafficCCLB CRZ DESTraffic conflict. ACAS RA or TA, or visual observation of conflict, which requires evasive manoeuvringAnticipate potential loss of separation. Recognise loss of separation. Take appropriate action. Apply the appropriate procedure correctly. Maintain aircraft control. Manage consequences.ACAS warning that requires crew interventionxxxx
Dilemma: Visual acquisition of conflicting traffic followed by an ACAS warning (resolution advisory) triggered by the same or other traffic. Even if the traffic is in sight, the pilot should follow the RA.XxX
While in descent, ACAS warning (traffic advisory) of an aircraft below. The crew should not initiate an avoidance manoeuvre based on TA (except decreasing the rate of descent unless otherwise instructed by ATC, etc.). This example scenario can be done during climb with conflicting traffic above.xx

END GEN3 TURBOPROP

AMC · AMC4 ORO.FC.232 — Regulation (EU) No 965/2012 · ED Decision 2022/014/R · Air OPS Easy Access Rules · EAR revision 27 Mar 2026

AMCAcceptable means of compliance

AMC5 ORO.FC.232EBT programme assessment and training topics

Show the text

GENERATION 2 (JET) — EBT PROGRAMME — TABLE OF ASSESSMENT AND TRAINING TOPICS Given the very small number of turbo-jet aeroplanes of the second generation in current use in commercial air transport operations, the operator should apply for an alternative means of compliance to develop a table of assessment and training topics to apply EBT.

AMC · AMC5 ORO.FC.232 — Regulation (EU) No 965/2012 · ED Decision 2021/002/R · Air OPS Easy Access Rules · EAR revision 27 Mar 2026

AMCAcceptable means of compliance

AMC6 ORO.FC.232EBT programme assessment and training topics

Show the text

GENERATION 2 (TURBOPROP) — TABLE OF ASSESSMENT AND TRAINING TOPICS

Assessment and training topicFrequencyDescription (includes type of topic, being threat, error or focus)Desired outcome (includes performance criteria OR training outcome)Flight phase activationGuidance material (GM) Example scenario elementsPROCOMFPAFPMLTWPSDSAWWLMKNO
Generation 2 Turboprop — Recurrent assessment and training matrixCompetency map
Section 1 — Skill retention. Manoeuvres training phase (MT)
MTRejected take-offAEngine failure after the application of take-off thrust and before reaching V1 (may be in LVO or CAT I or above)Demonstrate manual aircraft control skills with smoothness and accuracy as appropriate to the situation. Detect deviations through instrument scanning. Maintain spare mental capacity during manual aircraft control. Maintain the aircraft within the flight envelope. Apply knowledge of the relationship between aircraft attitude, speed and thrust.TOFrom initiation of take-off to complete stop (or as applicable to the procedure)xx
Failure of the critical engine between V1 and V2AFailure of the critical engine from V1 and before reaching V2 in the lowest CAT I visibility or in LVO meteorological (MET) conditions.TOThe manoeuvre is complete at a point when the aircraft is stabilised at normal engine-out climb speed with the correct pitch and lateral control, in trim condition and, as applicable, autopilot engagement. Only one failure of the critical engine between V1 and V2 a year may be done in LVO conditions.xx
Failure of one engine on take-offBFailure of one engine from V1 and before reaching V2 in the lowest CAT I visibility or in LVO MET conditions.TOThe manoeuvre is complete at a point when the aircraft is stabilised in a clean configuration with engine-out procedures completed. Only one failure of the critical engine between V1 and V2 a year may be done in LVO conditions.xx
Failure of one engine above V2 (any segment of the TO) in the lowest CAT I visibility or in LVO MET conditions.The manoeuvre is complete at a point when the aircraft is stabilised in a clean configuration with engine-out procedures completedxxx
Emergency descentCInitiation of emergency descent from normal cruise altitudeCRZThe manoeuvre is complete once the aircraft is stabilised in emergency descent configuration (and profile). However, if the EBT programme does not include the example scenario element ‘emergency descent’ in the training topic ‘automation management’, the emergency descent procedures should be completed and should not stop once the aircraft is stabilised in emergency descent configuration.xxx
Engine-out approach & landingAWith the critical engine (if applicable) failed, normal landingLDGInitiation in a stabilised engine-out configuration from not less than 3 NM final approach, until completion of roll-outxx
Engine-out approach & go-aroundAWith the critical engine (if applicable) failed, manually flown normal precision approach to DA, followed by a manual go-around — the whole manoeuvre to be flown without visual referenceAPPThis manoeuvre should be flown from intercept to centreline until acceleration after go-around. The manoeuvre is complete at a point when the aircraft is stabilised at normal engine-out climb speed with the correct pitch and lateral control, in trim condition and, as applicable, autopilot engagement (describe generally the critical part of the manoeuvre).xx
Go-aroundAGo-around, all engines operativeAPPHigh energy, initiation during the approach at 150 to 300 m (500 to 1 000 ft) below the missed approach level-off altitudexxx
Initiation of a go-around from DA followed by visual circuit and landingxxx
During flare/rejected landingxxx
Pilot qualification to operate in either pilot’s seatBAs per ORO.FC.235APPComplete the manoeuvres mandated in ORO.FC.235.Intentionally left in blank.
Section 2 — Equivalency of approaches relevant to operations. Evaluation phase, manoeuvres training phase or scenario-based training phase (EVAL, MT or SBT)
MTApproach type A or BBApproach type A or B flight method 3DSee equivalency of approaches relevant to operations that place an additional demand on a proficient crewAPPSee equivalency of approaches relevant to operationsxxxxx
Approach type ABApproach type A flight method 2DSee equivalency of approaches relevant to operations that place an additional demand on a proficient crewAPPSee equivalency of approaches relevant to operationsxxxxx
EVAL or SBTApproach type ABApproach type A flight method 3D or 2DSee equivalency of approaches relevant to operations that place an additional demand on a proficient crewAPPSee equivalency of approaches relevant to operationsxxxxx
Approach type BBApproach type B flight method 3DSee equivalency of approaches relevant to operations that place an additional demand on a proficient crewAPPSee equivalency of approaches relevant to operationsxxxxx
Section 3 – Equivalency of approaches under specific approvals and take-off under specific approvals. Evaluation phase, manoeuvres training phase or scenario-based training phase (EVAL, MT or SBT)
MTSPA approach(es)BApproach requiring specific approvalSee equivalency of approaches relevant to operations — specific approvalAPPApproaches flown from FAF to landing or go-aroundxxx
EVAL or SBTSPA approach(es)BApproach requiring specific approvalSee equivalency of approaches relevant to operations — specific approvalAPPApproaches flown from FAF to landing or go-aroundxxx
EVAL, MT or SBTSPA rejected Take-off (RTO)BEngine failure after the application of take-off thrust and before reaching V1 (in low-visibility MET conditions, preferably in the lowest approved visibility) Low-visibility RTO is not required under Part SPA but instead in Appendix 9 Section 6. Note: AMC1 SPA.LVO.120 point (f) does not require a low-visibility RTO. RTO is required only in the initial LVO course (point (g)(1)(iii) of AMC1 SPA.LVO.120).Demonstrate manual aircraft control skills with smoothness and accuracy as appropriate to the situation. Detect deviations through instrument scanning. Maintain spare mental capacity during manual aircraft control. Maintain the aircraft within the flight envelope. Apply knowledge of the relationship between aircraft attitude, speed and thrust.TORTO — can be combined with the assessment and training topic ‘surprise’ in EVAL or SBTxx
VAL, MT or SBTLVTOBNotwithstanding AMC1 SPA.LVO120 point (f)(1) AMC1 SPA.LVO.120 requires SPA manoeuvres in the frequency of the OPC, as OPC is substituted in the EBT programme. Thus, the frequency in EBT is determined in every cycle (B). Low-visibility take-off, preferably in the lowest approved visibilityTOThe manoeuvre may is complete at a point when the aircraft is stabilised at normal climb speed with the correct pitch and lateral control, in trim condition and, as applicable, autopilot engagement.xx
Assessment and training topicFrequencyFlight phase activationDescription (includes type of topic, being threat, error or focus)Desired outcome (includes performance criteria OR training outcome)Guidance material (GM) Example scenario elementsPROCOMFPAFPMLTWPSDSAWWLMKNO
Generation 3 Turboprop — Recurrent assessment and training matrixCompetency map
Section 4 — Training topics with frequency (A) in alphabetical order. Evaluation phase or scenario-based training phase (EVAL or SBT)
EVAL or SBTAdverse weatherAGNDThunderstorm, heavy rain, turbulence, ice build-up to include de-icing issues, as well as high-temperature conditions. The proper use of anti-ice and de-icing systems should be included generally in appropriate scenarios.Anticipate adverse weather. Prepare for suspected adverse weather. Recognise adverse weather. Take appropriate action. Apply the appropriate procedure correctly. Assure aircraft control.Predictive wind shear warning before take-off, as applicablexxx
ALLAdverse-weather scenario, e.g. thunderstorm activity, precipitation, icingxxxx
TOWind shear encounter during take-off, not predictivexxxx
TOPredictive wind shear warning during take-offxxxx
TOCrosswinds with or without strong gusts on take-offxx
CRZTurbulence that increases to severe turbulencexxxx
CRZWind shear encounter scenario during cruisexxxxx
APPReactive wind shear warning during approach or go-aroundxxxx
APPPredictive wind shear warning during approach or go-aroundxxxx
APPThunderstorm encounter during approach or on missed approachxxx
APPIncreasing tailwind on final approach (not reported)xxxx
APPApproach and landing in demanding weather conditions, e.g. turbulence, up and downdrafts, gusts and crosswinds including shifting wind directionsxxx
APPNon-precision approach in cold-temperature conditions, requiring altitude compensation for temperature, as applicable to the typexxx
APP LDGCrosswinds with or without strong gusts on approach, final approach and landing (within and beyond limits)xxx
APPIn approach, unexpected braking action ‘good to medium’ reported by the preceding aircraftxxxx
APPModerate to severe icing conditions during approach effecting aircraft performancexxxx
APPReduced visibility even after acquiring the necessary visual reference during approach, due to rain or fogxxx
EVAL or SBTAircraft system managementAN/ANormal system operation according to defined instructionsThis is not considered as a stand-alone topic. It is linked with the topic ‘compliance’. Where a system is not managed according to normal or defined procedures, this is determined as a non-compliance.See ‘compliance’ topic above. There are no defined scenarios, but the instructor should focus on learning opportunities when system management non-compliances manifest themselves during other scenarios. Underpinning knowledge of systems and their interactions should be developed and challenged, and not merely the application of normal procedures.Intentionally blankx
CRZ APP LDGMinimum fuel, caused by extended delays, weather, etc. where the crew would need to manage a minimum fuel situation.xxxx
EVAL or SBTAutomation managementACLB CRZ DES APPThe purpose of this topic is to encourage and develop effective flight path management through proficient and appropriate use of the flight management system(s), guidance and automation, including transitions between modes, monitoring, mode awareness, vigilance and flexibility needed to change from one mode to another. The means of mitigating errors are included in this topic. The errors are described as mishandled auto flight systems, inappropriate mode selection, mishandled flight management system(s) and inappropriate autopilot usage.Know how and when to use the flight management system(s), guidance and automation. Demonstrate correct methods for engagement and disengagement of the auto flight system(s). Demonstrate appropriate use of flight guidance, auto thrust and other automation systems. Maintain mode awareness of the auto flight system(s), including engagement and automatic transitions. Revert to different modes when appropriate. Detect deviations from the desired aircraft state (flight path, speed, attitude, thrust, etc.) and take appropriate action. Anticipate mishandled auto flight system. Recognise mishandled auto flight system. Take appropriate action if necessary. Restore correct auto flight state. Identify and manage consequences.ACAS warning (resolution advisory), recovery and subsequent engagement of automationxx
ALLFMS tactical programming issues, e.g. step climb, runway changes, late clearances, destination re-programming, executing diversionxxx
CLB CRZ DES APPRecoveries from TAWS, management of energy state to restore automated flightxxx
CLB CRZ DES APPAmendments to ATC cleared levels during altitude capture modes to force mode awareness and interventionxxx
ACAS warning (resolution advisory to level off) during climb or descent; for example, close to the cleared level when the capture mode has already been activated.xxx
TOLate ATC clearance to an altitude below acceleration altitudexxx
TO APPEngine-out special terrain proceduresxxx
CRZForcing autopilot disconnect followed by re-engagement, recovery from lowor high-speed events in cruisexxxx
CLBEngine failure during or after initial climb using automationxx
CRZEngine failure in cruise to onset of descent using automationxx
CRZEmergency descentxxx
DES APPManaging high-energy descent capturing descent path from above (correlation with unstable approach training)xxxx
APPNo ATC clearance received prior to commencement of approach or final descentxxx
APPReactive wind shear and recovery from the consequent high-energy statexxx
APPAutomation fail to capture the approach altitude in descent (e.g. last altitude before the FAP). Ideally, the failure occurs when the workload is high (e.g. configuration of the aircraft for final approach).xxxx
APPNon-precision or infrequently flown approaches using the maximum available level of automationxxx
APPGear malfunction during an approach planned with autoland (including autobrake). Competency FPA may or may not be included depending on the impact of such malfunction on the automation.xxx
APPATC clearances to waypoints beyond the programmed descent point for a coded final descent point during an approach utilising a final descent that is commanded by the flight management systemxxxx
EVAL or SBTCompetencies — non-technical (CRM)AAPPThis encapsulates the general CRM principles and objectives. It includes communication; leadership and teamwork; problem-solving and decision-making; situation awareness and management of information; and workload management. Emphasis should be placed on the development of leadership, shown by EBT data sources to be a highly effective competency in mitigating risk and improving safety through pilot performance.Exposure to an event or sequence of events to allow the pilot to build awareness of human factors in aviation and the human limitations. This includes the development of the following competencies: Communication: Demonstrate: — effective use of language; — responsiveness to feedback; and — capability to state the plans and resolve ambiguities. Leadership and teamwork: Use appropriate authority to ensure focus on the task. Support others in completing tasks. Problem-solving and decision-making: Detect deviations from the desired state, evaluate problems, identify the risk, consider alternatives and select the best course of action. Continuously review progress and adjust plans. Situation awareness and management of information: Have an awareness of the aircraft state in its environment; project and anticipate changes. Workload management: Prioritise, delegate and receive assistance to maximise focus on the task. Continuously monitor the flight progress.GPS failure prior to commencement of approach associated with position drift and a terrain alertxxxx
DESCabin crew report of water noise below the forward galley indicating a possible toilet pipe leak, with consequent avionics failuresxxx
CRZSmoke removal but combined with a diversion until landing is completed.xxxxxx
GNDApron fuel spillingxxx
CRZImportant water leak in an aircraft galleyxxxx
ALLA relevant number of cabin crew are wounded or incapacitated. Additionally, the cabin crew wounded or incapacitated are the most competent (e.g. senior cabin crew member).xxx
ALLUnruly passenger(s)xx
GNDPassenger oxygen: passenger service unit open and mask falling downxxx
ALLPassenger with medical problems — medical emergencyxx
CRZCredible threat reported to the crew. Stowaway or fugitive on board.xxxx
GNDNo METAR or TAFOR is available for destination due to industrial action at the destination airportxxxx
CRZCredible bomb threat reported to crewxxxx
CLB DESCredible bomb threat or pressurisation problem, but no quick landing possible (due to weather, terrain or other reasons)xxxx
APPDiversion with low remaining fuel or increased fuel flow due to system malfunctionxxxx
APPACAS warning (resolution advisory) immediately following a go-around, with a descent manoeuvre required. (The RA should be a command for descent when the aircraft is above 1 100 ft AGL.)xxxxx
EVAL or SBTComplianceAALLCompliance failure. Consequences of not complying with operating instructions (e.g. SOPs). This is not intended to list example scenario elements, but instructors should ensure that observed non-compliances are taken as learning opportunities throughout the programme. In all modules of the programme, the FSTD should as far as possible be treated like an aircraft, and non-compliances should not be accepted simply for expediency.Recognise that a compliance failure has occurred. Make a verbal announcement. Take appropriate action if necessary. Restore safe flight path if necessary. Manage consequences.The following are examples of potential compliance failures and are not intended to be developed as scenarios as part of an EBT module: 1. Requesting flap beyond limit speed 2. Flaps or slats in the wrong position for phase of flight or approach 3. Omitting an action as part of a procedure 4. Failing to initiate or complete a checklist 5. Using the wrong checklist for the situationIntentionally blank
EVAL or SBTGo-around managementAAPPAny threat or error that can result in circumstances that require a decision to perform a go-around, in addition to the execution of the go-around. Go-around scenarios should be fully developed to encourage effective leadership and teamwork, in addition to problem-solving and decision-making, plus execution using manual aircraft control or the flight management system(s) and automation as applicable. Design should include the element of surprise, and scenario-based go-arounds should not be predictable and anticipated. This topic is completely distinct from the go-around manoeuvre listed in the MT section that is intended only to practise psychomotor skills and a simple application of the procedures.Adverse-weather scenario leading to a reactive wind shear warning during approachxxxx
APPAdverse-weather scenario leading to a predictive wind shear warning during approach or go-aroundxxxx
APPAdverse-weather scenario, e.g. thunderstorm activity, heavy precipitation or icing forcing decision at or close to DA/MDAxxxx
APPDA with visual reference in heavy precipitation with doubt about the runway surface braking capabilityxxxx
APPAdverse-wind scenario resulting in increasing tailwind below DA (not reported)xxx
APPAdverse-wind scenario including strong gusts and/or crosswind out of limits below DA (not reported)xxx
APPAdverse-wind scenario including strong gusts and/or crosswind out of limits below 15 m (50 ft) (not reported)xxx
APPLost or difficult communications resulting in no approach clearance prior to commencement of approach or final descentxxx
APPBirds: large flocks of birds below DA once visual reference has been establishedxxx
APPSystem malfunction, landing gear malfunction during the approach
EVAL or SBTManual aircraft controlACLB CRZ DES APPControls the flight path through manual controlDemonstrate manual aircraft control skills with smoothness and accuracy as appropriate to the situation. Detect deviations through instrument scanning. Maintain spare mental capacity during manual aircraft control. Maintain the aircraft within the normal flight envelope. Apply knowledge of the relationship between aircraft attitude, speed and thrust.Flight with unreliable airspeed, which may or may not be recoverablexxxx
CLB CRZ DES APPAlternate flight control modes according to malfunction characteristicsxxxx
CLB CRZ DES APPACAS warning (resolution advisory) requires the pilot to descend or ATC calls for immediate descent (preferably during climb which requires a significant change in aircraft attitude)xxx
ACAS warning (resolution advisory) requires the pilot to climb or ATC calls for immediate climb (preferably during descent which requires a significant change in aircraft attitude).xxx
DESTAWS warning when deviating from planned descent routing, requiring immediate responsexxx
TOScenario immediately after take-off which requires an immediate and overweight landingxxxx
TOAdverse wind, crosswinds with or without strong gusts on take-offxx
TOAdverse weather, wind shear, wind shear encounter during take-off, with or without reactive warningsxxx
TOEngine failure during initial climb, typically 30-60 m (100-200 ft) (autopilot off)xxxx
CRZWind shear encounter scenario during cruise, significant and rapid change in wind speed or down/updrafts, without wind shear warningxxxxx
APPAdverse weather, wind shear, wind shear encounter with or without warning during approachxxxx
APPAdverse weather, deterioration in visibility or cloud base, or adverse wind, requiring a go-around from visual circling approach, during the visual segmentxxxxxxx
APPInterception of the glide slope from above (correlation with unstable approach training)xxx
APP LDGAdverse wind, crosswinds with or without strong gusts on approach, final approach and landing (within and beyond limits)xxx
APP LDGAdverse weather, adverse wind, approach and landing in demanding weather conditions, e.g. turbulence, up and downdrafts, gusts and crosswinds including shifting wind directionsxxx
APP LDGCircling approach manually flown at night in minimum in-flight visibility to ensure ground reference, minimum environmental lighting and no glide slope guidance lightsxxxx
APP LDGRunway incursion during approach, which can be triggered by ATC at various altitudes or by visual contact during the landing phasexxx
LDGAdverse wind, visibility, type-specific, special consideration for long-bodied aircraft, landing in minimum visibility for visual reference, with crosswindxxxx
LDGSystem malfunction, auto flight failure at DA during a low-visibility approach requiring a go-around flown manuallyxxxx
APP LDGApproach planned with autoland, followed by a failure below 1 000 ft requiring a manual go-around and an immediate landing due to fuel shortagexxxx
TOIn-seat instruction: Insufficient engine failure recovery, forcing the pilot monitoring to take over the flight controlsxxxx
APP LDGIn-seat instruction: Unstable approach on short final or long landing, forcing the pilot monitoring to take over the flight controlsxxxx
EVAL or SBTMonitoring, cross-checking, error management, mismanaged aircraft stateAALLThe scenarios should be realistic and relevant, and should be used for the purpose of demonstration and reinforcement of effective monitoring. Modules in the FSTD should be treated like those in an aircraft so that trainees have the opportunity to develop the competency with the practice of the right techniques and attitudes related to these topics through pilot performance, and that instructors have the opportunity to assess and train these topics in a realistic environment. As shown by the EBT data report, these topics are of key importance to improve safety in operations. In addition, the operator may also use these topics to develop scripted role-playing scenarios in the form of ISI. These scenarios cater for the need to monitor flight path excursions from the instructor pilot (PF), detect errors and make appropriate interventions, either verbally or by taking control as applicable. Demonstration scenarios may also be used. Demonstrated role-play should contain realistic and not gross errors, leading at times to a mismanaged aircraft state, which can also be combined with upset management training.Recognise mismanaged aircraft state. Observe the pilot’s behaviour: how the pilot is mitigating errors, performing cross-checking, monitoring performance and dealing with a mismanaged aircraft state, in order to ensure that observed deviations, errors and mistakes are taken as learning opportunities throughout the programme. Monitor flight path excursions. Detect errors and threats through proper cross-checking performance. Make appropriate interventions either verbally or by taking control if applicable. Take appropriate action if necessary. Restore the desired aircraft state. Identify and manage consequences.Deviations from the flight path, in pitch attitude, speed, altitude, bank anglexx
ALLIn-seat instruction: Simple automation errors (e.g. incorrect mode selection, attempted engagement without the necessary conditions, entering wrong altitude or speed, failure to execute the desired mode) culminating in a need for direct intervention from the pilot monitoring, and where necessary taking control.xx
APPIn-seat instruction: Unstable approach or speed/path/vertical rate not congruent with the required state for the given flight conditionxxxx
LDGIn-seat instruction: Demonstration exercise — recovery from bounced landing, adverse wind, strong gusts during landing phase, resulting in a bounce and necessitating recovery action from the pilot monitoringxxx
Unstable approachADES APPReinforce stabilised approach philosophy and adherence to defined parameters. Encourage go-arounds when crews are outside these parameters. Develop and sustain competencies related to the management of high-energy situations.ATC or terrain-related environment creating a high-energy descent with the need to capture the optimum profile to complete the approach in a stabilised configurationxxx
DES APPATC or terrain-related environment creating a high-energy descent leading to unstable conditions and requiring a go-aroundxxx
APPApproach and landing in demanding weather conditions, e.g. turbulence, up and downdrafts, gusts and crosswinds including shifting wind directionsxxx
APPIncreasing tailwind on final approach (not reported)xxxx
APP LDGCrosswinds with or without strong gusts on approach, final approach and landing (within and beyond limits)xxx
Section 5 — UPRT training topic with frequency (B). Evaluation phase, manoeuvres training phase or scenario-based training phase (EVAL, MT or SBT)
EVAL, MT or SBTUpset prevention trainingBN/ACompliance with AMC1 or AMC2 to ORO.FC.220&230 Include upset prevention elements in Table 1 for the recurrent training programme in at least every cycle, such that all the elements are covered over a period not exceeding 3 years. The elements are numbered with letters from A to I in Table 1 of AMC1 ORO.FC.220&230. Each element is made up of several numbered components. According to the principles of EBT, covering one component should satisfy the requirement to cover the whole element of recognising and preventing the development of upset conditions.Early recognition and prevention of upset conditions. When the differences between LHS and RHS are not significant in the handling of the aircraft, UPRT may be conducted in either seat.See Table 1 of AMC1 ORO.FC.220&230: Elements and respective components of upset prevention training.Intentionally blank
CRZDemonstration of the defined normal flight envelope and any associated changes in flight instruments, flight director systems, and protection systems. This should take the form of an instructor-led exercise to show the crew the points beyond which an upset condition could exist.xxx
TO APPSevere wind shear or wake turbulence during take-off or approachxxxx
CRZAs applicable and relevant to the aircraft type, demonstration at a suitable intermediate level, with turbulence as appropriate; practise steep turns and note the relationship between bank angle, pitch and stalling speedxxx
CRZAt the maximum cruise flight level for the current aircraft weight, turbulence to trigger overspeed conditions (if FSTD capability exists, consider use of the vertical wind component to add realism)xxxx
CRZAt the maximum cruise flight level for the current aircraft weight, turbulence and significant temperature rise to trigger low-speed conditions (if FSTD capability exists, consider use of the vertical wind component to add realism)xxxx
CRZHigh-altitude loss of reliable airspeedxxxxx
CRZHigh-altitude ACAS RA (where the RA is required to be flown in manual flight)xxxx
Section 6 — Training topics with frequency (B) in alphabetical order. Evaluation phase or scenario-based training phase (EVAL or SBT)
EVAL, MT or SBTAircraft system malfunctions, including operations under MELBALLFor full details, see the malfunction equivalency methodology. Any internal failure(s) apparent or not apparent to the crew Any item cleared by the MEL but having an impact upon flight operations — for instance, thrust reverser locked. Malfunctions to be considered should have one or more of the following characteristics: Immediacy Complexity Degradation of aircraft control Loss of primary instrumentation Management of consequences The operator should vary malfunctions for each characteristic over the EBT cycle. Unless specified otherwise in the operational suitability data, at least one malfunction with each characteristic should be included in every cycle. Combining characteristics should not reduce the number of malfunctions below seven for each cycle. For each crew member, the characteristics of degraded control and loss of instrumentation should be in the role of pilot flying and the others may be in the role of pilot flying or pilot monitoring. For full details, see the malfunction equivalency methodology.Recognise system malfunction. Take appropriate action including correct stop/go decision. Apply the appropriate procedure correctly. Maintain aircraft control. Manage consequences. Apply crew operating procedures where necessary. Respond appropriately to additional system abnormalities associated with MEL dispatch.(i) System malfunctions that require immediate and urgent crew intervention or decision, e.g. fire, smoke, loss of pressurisation at high altitude, failures during take-off, brake failure during landing. (ii) System malfunctions that require complex procedures, e.g. multiple hydraulic system failures, smoke and fumes procedures, major electrical system failure. (iii) System malfunctions that result in significant degradation of flight controls in combination with abnormal handling characteristics, e.g. jammed flight controls, certain degradation of FBW control, jammed horizontal stabiliser; flaps and/or slats locked; other malfunctions that result in degraded flight controls. (iv) System failures that require monitoring and management of the flight path using degraded or alternative displays, unreliable primary flight path information, unreliable airspeed, e.g. flight with unreliable airspeed (v) System failures that require extensive management of their consequences (independent of operation or environment), e.g. fuel leak.Intentionally blank
TOMEL items with crew operating procedures applicable during take-offxx
TOResponse to an additional factor that is affected by an MEL item (e.g. system failure, runway state)xxxx
GNDMalfunction during preflight preparation and prior to departurexxx
CLBMalfunction after departurexxxx
ALLMalfunctions that require immediate attention (e.g. bleed fault during engine start, hydraulic failure during taxi)xxx
CLB CRZFuel leak (management of consequences)xxxx
TOMalfunction on take-off high speed below V1xxx
TOMalfunction on take-off high speed above V1xx
GNDDuring taxi to the runway, a spurious brake temperature announcement. The crew had the correct brake temperature moments before the failure.xxx
TOTyre failure during take-offxxx
TOMalfunction on initial climbxx
APPMalfunction on approachxxx
APPMalfunction on go-aroundxxx
LDGMalfunction during landingxxxxx
EVAL or SBTEngine failureBTOAny engine failure or malfunction, which causes loss or degradation of thrust that affects performance. This is distinct from the engine-out manoeuvres described in the MT section above, which are intended only to practise psychomotor skills and reinforce procedures to manage engine failures.Recognise engine failure. Take appropriate action. Apply the appropriate procedure correctly. Maintain aircraft control. Manage consequences.Engine failure or engine malfunction on take-off low speedxxxx
TOEngine failure or engine malfunction on take-off high speed below V1xxxx
TOEngine failure or engine malfunction on take-off above V1xxxx
TOEngine failure or engine malfunction on initial climbxxx
APPEngine malfunctionxxx
CRZEngine failure in cruise (with autopilot)xxx
LDGEngine failure or engine malfunction on landingx
LandingBLDGPilots should have opportunities to practise landings in demanding situations at the defined frequency. Data indicates that landing problems have their roots in a variety of factors, including inappropriate decision-making, in addition to manual aircraft control skills if difficult environmental conditions exist. The purpose of this item is to ensure that pilots are exposed to this during the programme.Landing in demanding environmental conditions, with malfunctions as appropriateThis topic should be combined with the adverse-weather topic, aircraft system malfunctions topic or any topic that can provide exposure to a landing in demanding conditions.Intentionally blank
EVAL or SBTSurpriseBALLThe data analysed during the development of the EBT concept indicated substantial difficulties encountered by crews when faced with a threat or error, which was a surprise or an unexpected event. The element of surprise should be distinguished from what is sometimes referred to as the ‘startle factor’ — the latter being a physiological reaction. Wherever possible, consideration should be given towards variations in the types of scenario, times of occurrences and types of occurrence, so that pilots do not become overly familiar with repetitions of the same scenarios. Variations should be the focus of EBT programme design, and not left to the discretion of individual instructors, in order to preserve programme integrity and fairness.Exposure to an unexpected event or sequence of events at the defined frequency in order to build resilience.Rejected take-offxxx
Intentionally blankIntentionally blank
EVAL or SBTTerrainBALLAlert, warning, or conflictAnticipate terrain threats. Prepare for terrain threats. Recognise unsafe terrain clearance. Take appropriate action. Apply the appropriate procedures correctly. Maintain aircraft control. Restore safe flight path. Manage consequences.ATC clearance giving insufficient terrain clearancexxx
ALLDemonstration of terrain avoidance warning systems (TAWS) (this scenario element may be done in an ISI.)xxx
TO CLBEngine failure where performance is marginal leading to TAWS warningxxx
DES APPATC provides a wrong QNHxx
DES‘Virtual mountain’ refers to the surprise element of an unexpected warning. Care should be exercised in creating a level of realism, so this can best be achieved by an unusual and unexpected change of route during the descent.xxx
EVAL or SBTWorkload, distraction, pressure, stressBALLThis is not considered a topic for specific attention on its own, but more as a reminder to programme developers to ensure that pilots are exposed to immersive training scenarios which expose them to manageable high workload and distractions during the course of the EBT programme, at the defined frequency.Manage available resources efficiently to prioritise and perform tasks in a timely manner under all circumstancesIntentionally blankIntentionally blank
Section 7 — UPRT Upset recovery training topic with frequency (C). Evaluation phase, manoeuvres training phase or scenario-based training phase (EVAL, MT or SBT)
MT or SBTUpset recoveryCN/ACompliance with AMC1 or AMC2 to ORO.FC.220&230 Include the recovery exercises in Table 2 of AMC1 ORO.FC.220&230 for the recurrent training programme, such that all the exercises are covered over a period not exceeding 3 years. According to the principles of EBT, covering one component should satisfy the requirement to cover the whole element of recovery from developed upsets. The same principles apply to the exercises of components 2, 3 and 4 where one exercise may satisfy the requirement to cover the whole component. An aeroplane upset is defined as an undesired aeroplane state in flight characterised by unintentional divergences from parameters normally experienced during line operations or training. An aeroplane upset may involve pitch and/or bank angle divergences as well as inappropriate airspeeds for the conditions.Recognise upset condition. Make timely and appropriate intervention. Take appropriate action. Assure timely and appropriate intervention. (AMC1 ORO.FC.220&230 Table 2 component 1) Assure aircraft control. Maintain or restore a safe flight path. Assess consequential issues. Manage outcomes. Consolidate the summary of aeroplane recovery techniques. (AMC1 ORO.FC.220&230 Table 2 component 5) Note: The operator should assess if the exercises should be practised for the either seat qualification.The example scenario elements may be done in ISI, as non-ISI or a combination of both. If done in ISI: The instructor should position the aircraft within but close to the edge of the validated training envelope before handing control to the trainee to demonstrate the restoration of normal flight. Careful consideration should be given to flying within the validated training envelope.Intentionally blank
Table 2 of AMC1 ORO.FC.220&230: Exercises for upset recovery training
A.Recovery from developed upsets
CLB DES2.Recovery from stall events in the following configurations: take-off configuration, clean configuration low altitude, clean configuration near maximum operating altitude, and landing configuration during the approach phase.xxxx
CRZ3.Recovery from nose high at various bank anglesxxxx
CRZ4.Recovery from nose low at various bank anglesxxxx
CRZ
APPDemonstration at a normal cruising altitude. Set conditions and disable aircraft systems as necessary to enable trainee to perform stall recovery according to OEM instructions.xxx
CLB DESDemonstration at an intermediate altitude during early stages of the approach. Set conditions and disable aircraft systems as necessary to enable trainee to perform stall recovery according to OEM instructions.xxx
Recovery from a wake turbulence position with high-bank anglexxxx
Section 8 — Training topics with frequency (C) in alphabetical order. Evaluation phase or scenario-based training phase (EVAL or SBT)
EVAL or SBTAdverse windCTOAdverse wind/crosswind. This includes tailwind but not ATC mis-reporting of the actual wind.Recognise adverse-wind conditions. Observe limitations. Apply the appropriate procedures. Maintain directional control and safe flight path.Take-off with different crosswind/tailwind/gust conditionsxx
TOTake-off with unreported tailwindxx
TOCrosswinds with or without strong gusts on take-offxx
APPWind exceeding limits on final approach (not reported)xxxx
APPWind exceeding limits on final approach (reported) in manual aircraft controlxxxx
APPIncreasing tailwind on final approach (not reported)xxxx
APPApproach and landing in demanding weather conditions, e.g. turbulence, up and downdrafts, gusts and crosswind including shifting wind directionsxxx
APPAdverse-wind scenario resulting in increasing tailwind below DA (not reported)xxx
APPAdverse-wind scenario including strong gusts and/or crosswind out of limits below DA (not reported)xxx
APPAdverse-wind scenario including strong gusts and/or crosswind out of limits below 15 m (50 ft) (not reported)xxx
APP LDGCrosswind with or without strong gusts on approach, final approach and landing (within and beyond limits)xxx
Approach, visibility close to minimumCAPPAny situation where visibility becomes a threatRecognise actual conditions. Observe aircraft and/or procedural limitations. Apply the appropriate procedures if applicable. Maintain directional control and safe flight path.Approach in poor visibilityxxxx
APPApproach in poor visibility with deteriorations necessitating a decision to perform a go-aroundxxx
LDGLanding in poor visibilityxxx
EVAL or SBTATCCALLATC error. Omission, miscommunication, garbled, poor quality transmission. All these act as distractions to be managed by the crew. The scenarios should be combined, where possible, with others of the same or higher weighting, the principal reason being to create distractions.Respond to communications appropriately. Recognise, clarify and resolve any ambiguities. Refuse or question unsafe instructions. Use standard phraseology whenever possible.ATC role-play: the instructor provides scripted instructions, as a distraction to the crewxxx
ALLController error, provided by the instructor according to a defined scripted scenarioxxxx
ALLFrequency congestion, with multiple aircraft using the same frequencyx
APPDestination temporarily closedxxxx
CRZRescue and firefighting services (RFFS) level reduction at destinationxxx
APPRunway change before the interception of the localiser or similar navigation aid in azimuthxxxx
GND/TOStray dogs at the opposite threshold runwayxxx
ALLPoor quality transmissionsx
EVAL or SBTFire and smoke managementCGNDThis includes engine, electric, pneumatic, cargo fire, smoke or fumes.Recognise fire, smoke or fumes Take appropriate action. Apply the appropriate procedure correctly. Maintain aircraft control. Manage consequences.Fire in cargo or cabin/cockpit at gatexxxx
GNDFire during taxixxxxx
GNDFire with no cockpit indicationxxxxx
TOTake-off low speedxxxxx
TOFire or smoke on take-off high speed below V1xxxx
TOFire or smoke on take-off high speed above V1xxx
TOFire or smoke on Initial climbxxx
CRZCargo firexxx
APPEngine fire in approach (extinguishable)xx
APPEngine fire in approach (non-extinguishable)xxx
CLB CRZ DESLithium battery fire in the cockpit or cabin compartmentxxxxx
APPFlight deck or cabin firexxxx
GNDAny of the example scenario elements above ending in an evacuationxxxx
EVAL or SBTLoss of communicationsCGNDLost or difficult communications due to either pilot mis-selection or a failure external to the aircraft. This could be for a few seconds or a total loss.Recognise loss of communications. Take appropriate action. Execute the appropriate procedure as applicable. Use alternative ways to communicate. Manage consequences.Loss of communications during ground manoeuvringxx
TOLoss of communications after take-offxxx
APPLoss of communications during approach phase, including go-aroundxxxxx
EVAL or SBTManaging loading, fuel, performance errorsCALLA calculation error by one or more pilots, or someone involved with the process, or the process itself, e.g. incorrect information on the load sheetAnticipate the potential for errors in load/fuel/performance data. Recognise inconsistencies. Manage/avoid distractions. Make changes to paperwork/aircraft system(s) to eliminate error. Identify and manage consequences.This can be a demonstrated error, in that the crew may be instructed to deliberately insert incorrect data — for example, to take off from an intersection with full-length performance information. The crew will be asked to intervene when acceleration is sensed to be lower than normal, and this may be part of the operator procedures, especially when operating mixed fleets with considerable variations in MTOM.xxx
GNDFuel ground staff on industrial action. Only limited amount of fuel available, which is below the calculated fuel for the flight.xxxx
GNDAdvise crew that there is a change of the load sheet figures during taxi to the runway. The crew may have limited time due to a calculated take-off time (CTOT) — ATC slot.xx
GNDBraking action reported ‘medium’. The information is transmitted just before take-off. The flight is subject to a calculated take-off time (CTOT) — ATC slot.xxx
EVAL or SBTNavigationCGNDExternal NAV failure. Loss of GPS satellite, ANP exceeding RNP, loss of external NAV source(s)Recognise a NAV degradation. Take appropriate action. Execute the appropriate procedure as applicable. Use alternative NAV guidance. Manage consequences.External failure or a combination of external failures degrading aircraft navigation performance on groundxxxx
TO CLB APP LDGExternal failure or a combination of external failures degrading aircraft navigation performance in flightxxxx
GNDStandard initial departure change during taxi. The flight may be subject to a CTOT — ATC slot.xxx
APPLoss of runway lighting below decision heightxxx
CRZNo fly zone: when the crew changes control frequency, the new ATCO informs the crew that they are flying over an unannounced ‘no fly zone’ that is not included in the NOTAMs. (To trigger such an event, the context may be as follows: an unexpected military conflict in the territory the aircraft is flying over or the crew is forced to re-route in flight and the new route flies over a city that has an important event such the Olympic games, a G20/G7 submit, or the route is flying near a space rocket launch close to the time of the launch, like the Guiana Space Centre, Cape Cañaveral, etc.).xxx
Operationsor type-specificCALLIntentionally blankIntentionally blankIntentionally blankIntentionally blank
Operations of special airport approvalCAPP LDGSee equivalency of approaches relevant to operations.The operator should comply with the national qualification requirements published in the aeronautical information publication (AIP).Intentionally blankIntentionally blank
EVAL or SBTPilot incapacitationCTOConsequences for the non-incapacitated pilotRecognise incapacitation. Take appropriate action including correct stop/go decision. Apply the appropriate procedure correctly. Maintain aircraft control. Manage consequences.During take-offxxxxx
APPDuring approachxxxx
EVAL or SBTRunway or taxiway conditionCGND TO LDGContamination or surface quality of the runway, taxiway, or tarmac including foreign objectsRecognise hazardous runway condition. Observe limitations. Take appropriate action. Apply the appropriate procedures correctly. Assure aircraft control.Planned anticipated hazardous conditions with dispatch information provided to facilitate planning and execution of appropriate proceduresxx
GND TO LDGUnanticipated hazardous conditions, e.g. unexpected heavy rain resulting in flooded runway surfacexxx
TOTake-off on runway with reduced cleared width due to snowxxxx
TOStop/go decision in hazardous conditionsxxx
EVAL or SBTTrafficCCLB CRZ DESTraffic conflict. ACAS RA or TA, or visual observation of conflict, which requires evasive manoeuvringAnticipate potential loss of separation. Recognise loss of separation. Take appropriate action. Apply the appropriate procedure correctly. Maintain aircraft control. Manage consequences.ACAS warning that requires crew interventionxxxx
Dilemma: Visual acquisition of conflicting traffic followed by an ACAS warning (resolution advisory) triggered by the same or other traffic. Even if the traffic is in sight, the pilot should follow the RA.xxx
While in descent, ACAS warning (traffic advisory) of an aircraft below. The crew should not initiate an avoidance manoeuvre based on TA (except decreasing the rate of descent unless otherwise instructed by ATC, etc.). This example scenario can be done during climb with conflicting traffic above.xxx
Wind shear recoveryCTOWith or without warnings including predictive. A wind shear scenario is ideally combined with an adverse-weather scenario containing other elements.Anticipate potential for wind shear. Avoid known wind shear or prepare for suspected wind shear. Recognise wind shear encounter. Take appropriate action. Apply the appropriate procedure correctly. Assure aircraft control. Recognise out of wind shear condition. Maintain or restore a safe flight path. Assess consequential issues and manage outcomes.Predictive wind shear warning during take-offxx
TOWind shear encounter during take-offxxx
TOWind shear encounter after rotationxx
TOPredictive wind shear after rotationxx
APPPredictive wind shear during approachxxx
APPWind shear encounter during go-aroundxxxx
APPWind shear encounter during approachxxx

END GEN2 TURBOPROP

AMC · AMC6 ORO.FC.232 — Regulation (EU) No 965/2012 · ED Decision 2022/014/R · Air OPS Easy Access Rules · EAR revision 27 Mar 2026

AMCAcceptable means of compliance

AMC8 ORO.FC.232EBT programme assessment and training topics

Show the text

SCENARIO ELEMENTS AND COMPETENCY MAPPING

(a)The operator may develop scenario elements and a competency map that are more relevant to its operation.

(b)When developing scenario elements, the operator should ensure that there can be no negative training when asking pilots to induce their own errors.

(c)Competencies mapped are those considered critical in managing the scenario. They are determined according to the following principles:

(1)those competencies considered most critical to the successful management of the defined threat or error; or

(2)those competencies most likely to be linked to the root cause of poor performance in the case of unsuccessful management of a defined threat or error.

(d)The competency map may indicate scenarios or combinations of scenarios for development of particular competencies.

(e)The competency map indicates the most critical competencies suggested by design, but the instructor should always assess all observed competencies.

AMC · AMC8 ORO.FC.232 — Regulation (EU) No 965/2012 · ED Decision 2021/002/R · Air OPS Easy Access Rules · EAR revision 27 Mar 2026

GMGuidance material

GM1 ORO.FC.232EBT programme assessment and training topics

Show the text

TABLE OF ASSESSMENT AND TRAINING TOPICS The assessment and training topics usually have several example scenario elements. At least one example scenario element is selected (e.g. Gen 4 topic ‘Go-around’ in MT has three example scenario elements — the operator may choose one at each module (frequency A)). Flight phase for activation:

AbbreviationFlight phaseDescription
GND (1)Flight planning, preflight, engine start & taxi-outGround phases up to when the crew increases thrust for taking-off
Taxi-in, engine shutdown, post-flight & flight closingFrom the speed that permits the aircraft to be manoeuvred by means of taxiing for arriving at a parking area until the crew completes post-flight and flight closing duties.
TO (2)Take-offThis phase begins when the crew increases the thrust for taking-off. It ends after the speed and configuration are established at a defined manoeuvring altitude or to continue the climb for cruise.
CLB (3)ClimbThis phase begins when the crew establishes the aircraft at a defined speed and configuration enabling the aircraft to increase altitude for the purpose of cruise. It ends with the aircraft established at a predetermined constant initial cruise altitude at a defined speed.
CRZ (4)CruiseThe cruise phase begins when the crew establishes the aircraft at a defined speed and predetermined constant initial cruise altitude and proceeds in the direction of a destination. It ends with the beginning of descent for an approach.
DES (5)DescentThis phase begins when the crew departs the cruise altitude for an approach at a particular destination. It ends when the crew initiates changes in aircraft configuration and/or speed to facilitate a landing on a particular runway.
APP (6)ApproachThis phase begins when the crew initiates changes in aircraft configuration and/or speeds enabling the aircraft to manoeuvre for landing on a particular runway. It ends when the aircraft is in the landing configuration and the crew is dedicated to land on a specific runway. It also includes go-around where the crew aborts the descent to the planned landing runway during the approach phase. Go-around ends after speed and configuration are established at a defined manoeuvring altitude or to continue the climb for cruise.
LDG (7)LandingThis phase begins when the aircraft is in the landing configuration and the crew is dedicated to touchdown on a specific runway. It ends when the speed permits the aircraft to be manoeuvred by means of taxiing for arrival at a parking area.
ALL (8)AllAny or all phases of flight

GM · GM1 ORO.FC.232 — Regulation (EU) No 965/2012 · ED Decision 2021/002/R · Air OPS Easy Access Rules · EAR revision 27 Mar 2026

GMGuidance material

GM2 ORO.FC.232EBT programme assessment and training topics

Show the text

COMPETENCY MAP PROCESS Note 1. The competency map process may be done in teams of instructors. Then the results are compared and reconciled by a small group of subject matter experts (SMEs). Note 2. It is always easy to map SAW or KNO as the underlying competency, but there are almost invariably other competencies, especially when there is ineffective management, so the intent should be to balance the mapping of SAW or KNO and map the other predominant competencies within the scenario.

GM · GM2 ORO.FC.232 — Regulation (EU) No 965/2012 · ED Decision 2021/002/R · Air OPS Easy Access Rules · EAR revision 27 Mar 2026

AMCAcceptable means of compliance

AMC1 ORO.FC.232(b)(1)EBT programme assessment and training topics

Show the text

EBT DATA REPORT

(a)The data report is a large-scale comprehensive study of operational data. It identifies the areas of pilot training for improvement, providing the prioritisation of germane and relevant training topics to guide in the construction of suitable EBT programmes. The data report uses other studies, a variety of data sources and/or varied methodology to mitigate the inherent bias associated with individual types of data sources.

(b)The data report should:

(1)be endorsed or developed by the competent authority, EASA or ICAO;

(2)be reviewed by a team of experts in pilot training, representing airline operators, pilot associations, regulators, and original equipment manufacturers (OEM);

(3)use data or information (training data, operational data and safety data) from the following sources:

(i)accident investigation bodies;

(ii)competent authorities;

(iii)OEM — aircraft;

(iv)EASA safety information;

(v)operators; and

(vi)studies or reports (aviation or scientific);

(4)analyse the data with the following objectives:

(i)to substantiate the need for change in the assessment and training programmes for commercial transport pilots;

(ii)to provide evidence from data analyses to support the derivation of training topics, prioritised according to aircraft generation;

(iii)to challenge and/or corroborate the other sources of data (e.g. Training Criticality Survey and Training Guidance) with operational data;

(iv)to provide feedback regarding the effectiveness of changes implemented through the adoption of competency-based training methodologies; and

(v)to validate or ascertain practices, findings or conclusions made previously by the industry;

(5)include the studies and define the use of such studies in the data report following the criteria below:

(i)The study is relevant from a training perspective (e.g. if incorporating a training change mitigates the risk found in the study).

(ii)There is evidence that it will assist with the identification of competencies to be developed in training in order to mitigate risks encountered in the evolving operational environment.

(iii)The findings of the study will be corroborative or challenging across the spectrum of the analysis made in the data report.

(iv)The study allows the analysis and comparison of the data or findings in the data report and it is coming from industry-respected research or studies;

(6)include an evidence table for the purpose of:

(i)integrating the evidence of the analyses in points (4) and (5);

(ii)identifying meaningful patterns;

(iii)enabling the grouping of evidence to support the key findings; and

(iv)facilitating the prioritisation of results; and

(7)include a prioritisation of the training topics for the purpose of translating data into useful events and scenarios to assess and develop pilot performance (assessment and training topics). The prioritisation shall:

(i)systematically rank threats, errors and competencies along with the factors leading to accidents and serious incidents from multiple data sources to formulate a table of assessment and training topics;

(ii)be performed for each of the generations of aircraft. This allows highlighting the differences and commonalities between generations; and

(iii)ensure sufficient flexibility in the process to allow enhancement of the training programmes according to the type of operation, culture and type of aircraft.

AMC · AMC1 ORO.FC.232(b)(1) — Regulation (EU) No 965/2012 · ED Decision 2021/002/R · Air OPS Easy Access Rules · EAR revision 27 Mar 2026

AMCAcceptable means of compliance

AMC1 ORO.FC.232(b)(3)EBT programme assessment and training topics

Show the text

AIRCRAFT TYPES BY GENERATIONS The operator should only develop an EBT programme for aircraft types for which there is a table of assessment and training topics.

Generation 4 — Jet)From 1988. EFIS cockpit — FMS equipped FADEC Fly-by-wire control systems Advanced flight envelope protection Integrated auto flight control system — navigation performance, and terrain avoidance systems Generation fatal accident average rate: 0,1/million flightsA318/A319/A320/A321 (including neo), A330, A340-200/300, A340-500/600, B777, A380, B787, A350, Bombardier C Series (A220), Embraer E170/E175/E190/E195
Generation 3 — JetFrom 1969 EFIS cockpit — FMS equipped FADEC Integrated auto flight control system — navigation performance, and terrain avoidance systems Basic flight envelope protection — stick shaker/pusher Generation fatal accident average rate: 0,2/million flightsA310/A300-600, B737-300/400/500, B737-600/700/800 (NG), B737 MAX, B757, B767, B747-400, B747-8, B717, BAE 146, MD11, MD80, MD90, F70, F100, Bombardier CRJ Series, Embraer ERJ 135/145
Generation 3 — TurbopropFrom 1992 EFIS cockpit — FMS equipped EEC/ECU or higher engine control Integrated auto flight control system — navigation performance and terrain avoidance systems Basic flight envelope protection — stick shaker/pusherATR 42-600, ATR 72-600, Bombardier Dash 8-400, BAE ATP, Saab 2000
Generation 2 — JetFrom 1964. Integrated auto-flight system. EEC/ECU or higher engine control Analogue/CRT instrument display Basic flight envelope protection — stick shaker/pusher Generation fatal accident average rate: 0,7/million flightsA300 (except A300-600), BAC111, B727, B737-100/200, B747-100/200/300, DC9, DC10, F28, L1011
Generation 2 — TurbopropFrom 1964 Analogue/CRT instrument display EEC/ECU Basic flight envelope protection — stick shaker/pusher Integrated auto flight control systemATR 42, ATR 72 (all series except -600), BAE J-41, Fokker F27/50, Bombardier Dash 7 and Dash 8-100/200/300 Series, Convair 580-600 Series, Shorts 330 and 360, Saab 340, Embraer 120
Generation 1 — JetFrom 1952 First commercial jets. Manual engine control Analogue instrument display Not integrated auto flight control system Basic flight envelope protection — stick shaker/pusher, attitude warning Generation fatal accident average rate: 3.0/million flightsDC8, B707

AMC · AMC1 ORO.FC.232(b)(3) — Regulation (EU) No 965/2012 · ED Decision 2021/002/R · Air OPS Easy Access Rules · EAR revision 27 Mar 2026

All rules in SUBPART FC: FLIGHT CREW

Consolidated from the EASA Easy Access Rules (revision 27 Mar 2026, extracted 17 Aug 2026) for convenience. Not the official publication — verify against the Official Journal of the European Union and the EASA publications before operational use.

Ask Metis about ORO.FC.232 →

Metis opens with Avioverse in October 2026 · request early access.