ECAM COMPLETION IS THE BEGINNING OF THE NEXT ASSESSMENT
The immediate objective after a failure is to preserve a safe flight path while identifying the applicable problem and procedure. The FCTM assigns flying, navigation and communication to the flying role, with failure management performed on command by the monitoring role. That division remains useful in a single-user simulator: establish the flight path first and deliberately allocate attention to the procedure, using pause for study when needed. The warning title, system indication and aircraft response should form a coherent diagnosis before a consequential control is moved. [21, PDF pp. 65–69]
Use system identification, selector identification and the intended action as a linked crosscheck. For guarded or potentially irreversible controls, apply the procedure's confirmation discipline. Observe feedback on the receiving system display after the selection, recognising that not every action has identical automatic feedback. A disappearing line or silenced aural is not a general declaration that the aircraft has returned to its original capability. Retain the distinction between acknowledging information, carrying out an action and evaluating the resulting aircraft state. [21, PDF pp. 66–70]
Review STATUS and the applicable QRH summary to plan the rest of the flight. Identify handling, navigation, communication, approach, landing and go-around consequences, including any new performance assessment. LAND ASAP requires a suitable landing opportunity, not simply the geometrically nearest database airport. The source notes that a closest-airports list is sorted by location without establishing suitability. Weather, runway, available approach, aircraft capability and the remaining urgency still need judgement. Use the relevant summary and procedure rather than constructing a private replacement checklist from individual system facts. [21, PDF pp. 70–73]
Airbus's reset guidance requires an authorised procedure or the applicable reset-table conditions, read and performed with the necessary crosscheck. It distinguishes a procedure-requested reset, a table-authorised option after ECAM, and limited A320 ground electrical-transient cases. The ground exception is not permission to reset any malfunction of a listed system: the specified conditions still govern. Record attempts and results for maintenance. Resetting from memory or from a forum's generic off/on suggestion can remove evidence, trigger tests or alter flight-control capability without establishing that the underlying condition is repaired. [134]
Separate aircraft recovery from simulator recovery. Removing an injected failure, requesting simulated maintenance, loading a panel state and restarting the application are different operations with different purposes. A software reload may make an exercise usable again while destroying the evidence needed to assess the original aircraft response. Preserve the state and notes before that intervention when practical, and label the subsequent reset as an exercise or software action. Use the Fenix support route for a repeatable program problem; do not describe an application restart as an Airbus airborne procedure. [127, Failure removal and ground maintenance] [61, Panel-state activation and loading transition] [135, Official support reporting route]