Table 6: Functions which were required to be performed after the flight 965 received the proposal of runway change.
1. Communication with ATC | 2. Input and execute the route to FMC | ||
Input | N/A (Not applicable) | Input | N/A |
Output | Communication is established correctly | Output | Aircraft starts to fly correct course |
Precondition | Frequency is set correctly | Precondition | Correct course is identified |
Resource | Information exchanged among crews and ATC | Resource | Information from chart, Instrument and ATC |
Control | Crews, ATC, Radio equipment, Radar | Control | Crews, FMC, ND: Navigation Display |
Time | Several tens of seconds | Time | Several tens of seconds |
3. Identifying approach course | 4. Descending for new approach course | ||
Input | N/A | Input | N/A |
Output | Approach course is identified | Output | Flight continues correctly |
Precondition | Crew recognize the current flight status | Precondition | New flight plan is validated |
Resource | Information from chart, Instrument and ATC | Resource | Altitude, Distance (Available time) |
Control | Crews, ATC | Control | Pilot Flying (PF) |
Time | Several tens of second | Time | Few minutes |
5. Review of flight plan for RWY change | |||
Input | Accepting runway change | ||
Output | Flight plan is validated | ||
Precondition | Crew recognize current flight status | ||
Resource | Altitude, Distance (Available time) | ||
Control | Crews, ATC | ||
Time | Several tens of seconds or few minutes |