ICAO Fluency Practice: Speak in a Clear Sequence

The aircraft is at the stand and I can see a loader near the cargo door. There are a baggage cart and two people near it. Maybe there is a problem with the equipment, but I do not know. I would ask the ground team for information. Then I would tell the crew if we need more time before departure.

The aircraft is parked with a loader at the cargo hold and a baggage cart waiting nearby. The handlers are talking, although the picture does not tell us why. The equipment might need attention, so I would ask the ground team for an update before drawing a conclusion. Once I knew the likely effect on readiness, I would pass that information to the crew and ATC if necessary.

There is a loader alongside the hold, a cart waiting and two handlers discussing something. A loading delay is possible, but a still image cannot tell us whether anything has actually failed. I would check with the ramp team first, then give the crew a concise update: what is known, what remains uncertain and when we expect more information. If departure readiness changes, I would inform ATC rather than speculate about a departure time.

A vehicle is in front of our way on the taxiway. It looks stopped, and our aircraft is behind it. I would tell the controller that we can see the vehicle and that we are holding position. I would wait for the situation to become clear. Before moving again, I would confirm the next instruction with the controller.

There is a service vehicle stopped on the taxiway ahead of the aircraft. I would remain in position, report the obstruction to ground control and give our location. I would also explain whether the vehicle is moving. Once the route is clear, I would confirm the controller's instruction before continuing, so that the crew and controller share the same understanding.

The vehicle appears stationary on the taxiway ahead, so the immediate priority is a clear account of what we can see and where we are. I would tell ground control that we are holding and describe the obstruction without guessing why it stopped. When the situation changes, I would report that as well and confirm the instruction to continue. That closes the loop before the aircraft moves again.

It is raining and the taxiway is wet. The pilots can see the line in front, but the view through the window is not very clear. We can have a delay of time if we need more information. I would check the taxi route with the other pilot. If I was not sure about the instruction, I would ask the controller to repeat it.

Rain is running down the windscreen and the taxiway is wet, although the centreline is visible nearby. The conditions may make it harder to identify visual references further ahead. I would check the assigned route with the other pilot and listen carefully to ground control. If either the route or our position was uncertain, I would say so and request clarification before continuing.

The rain and reflections make the forward view less distinct, though the centreline is still visible close to the aircraft. That does not tell us how clear the rest of the route is. I would cross-check our clearance and position with the other pilot, then tell ground control if we lost a visual reference. A short, specific request for clarification would be more useful than a general statement that the weather is poor.

Two controllers are in the tower. One is looking outside with binoculars and the other controller is in the headset. I think they are watching the airfield and talking to aircraft. They need to share information clearly. If something changes, one controller can tell the other what happened and where it is. The second controller can repeat the important detail to check it.

One controller is observing the airfield through binoculars, while the other is wearing a headset at the console. The photograph does not tell us exactly what either person is handling. A useful handover would identify the aircraft or location, state the current situation and mention any action still required. The receiving controller could repeat any detail that needs confirmation before taking over.

The controller with binoculars is looking out across the airfield, while a colleague at the console has a headset on. We cannot infer the traffic situation from the picture, but we can discuss how they might coordinate. I would make the update specific: identify the traffic or location, describe the current restriction and say what is still outstanding. If the receiving controller was uncertain, I would invite a concise check rather than rely on a nod.

The worker is making a stop with the arms. A tug is near the front of the aircraft, and the aircraft is parked. I cannot see all the people around it. The crew should understand the signal and talk to the ground team. Before any movement, I would check that the team is ready and that the required communication is clear.

A ground worker is giving a stop signal while a tug is positioned near the parked aircraft. The picture shows the signal but does not establish the rest of the movement plan. I would coordinate with the ground team, confirm their readiness and make sure the crew understands the intended movement. If the signal or instruction was unclear, I would ask for clarification before proceeding.

The worker's raised arms indicate a stop, with the tug close to the aircraft's nose. A still picture cannot tell us whether the tug is connected or what movement has been planned. I would acknowledge the signal, establish clear communication with the ground team and confirm the next step with the other pilot. If anything did not match our understanding, we would resolve it before any movement.

The controller says the level is not possible for us now because of traffic. I would tell the controller that I understand. Then I would ask if another level is available and explain why we need it. We would keep the current clearance unless a new one is given. I would listen carefully and read back the new instruction.

The controller cannot approve the requested level because of traffic. I would acknowledge that, explain the reason for our request and ask whether an alternative level is available. Until a new clearance is issued, we would continue under the current one. If another level was offered, I would check that it met our needs and read the clearance back accurately.

If the requested level were unavailable, I would acknowledge the restriction and give the controller the reason for the request, especially if it affected our immediate needs. I could then ask about an alternative or the expected delay. Meanwhile, the crew would remain within the current clearance. Any new instruction would be checked and read back, so an offer or expectation is not mistaken for an actual clearance.

I am not sure what taxiway was said by the controller. I would tell the other pilot and make sure we do not continue on a route we do not understand. I would ask ground control to say the taxiway again. Then I would repeat the complete instruction and check the route with the other pilot before we continue.

If I suspected I had misheard the taxiway identifier, I would tell the other pilot immediately and avoid continuing on an unconfirmed route. I would ask ground control to repeat the relevant part of the instruction, then read it back with the call sign. After confirming our position and the route together, we could continue in accordance with the clearance.

I would make the uncertainty explicit to both the other pilot and ground control, rather than try to reconstruct the instruction from memory. Having stopped safely if needed, I would ask for the taxiway identifier to be repeated, read back the instruction and cross-check it against our position. Only once the crew and controller shared the same understanding would I proceed under the confirmed clearance.

We cannot depart yet because the ground team is still checking some equipment. We need to wait some time more, and I do not know the exact delay. I would tell my colleague what the team has said. I would ask them to update us when the check is complete. Then we can tell the controller when we are ready.

The ground team has asked for more time to check a piece of equipment, so we are not ready to depart yet. The duration is uncertain, and I would avoid giving a precise estimate until they confirm one. I would brief my colleague on the reason and ask the team for a further update. Once our readiness is known, we can inform ground control.

I would tell my colleague that the equipment check is still in progress and that our departure readiness has changed. The important distinction is between a confirmed delay and an estimated duration: we know the first, but we may not know the second. I would agree who will contact the ground team for an update and who will inform ATC. That gives everyone a clear next action without inventing a time.

The cabin crew say the passenger is not feeling good. I would ask if the passenger is conscious and what help is being given. I would also ask the cabin crew to tell me if the condition changes. Then I would inform the controller about the situation. If we need assistance on arrival, I would make a clear request.

After the cabin crew report an unwell passenger, I would ask for the person's current condition and the assistance already being provided. I would ask to be updated if anything changed, then discuss the available options with the other pilot. When contacting ATC, I would state the situation, our intentions and any assistance we need, while avoiding details that are not yet confirmed.

I would first establish what the cabin crew actually know: the passenger's condition, the help available and whether there has been a change. I would ask them to keep us informed while the flight crew considers the options. My update to ATC would distinguish confirmed information from uncertainty and include a specific request if we needed assistance. As the situation developed, I would revise the controller rather than let an earlier description become misleading.

On a flight we planned to use one runway, but the controller gave us another runway because the wind changed. Our first plan was not more possible. We asked for more time to prepare and checked the new information together. Then we told the controller when we were ready. I learned that a short update gives everyone time to understand the new plan.

On a fictional departure, the runway changed while we were preparing to taxi because the wind had shifted. We told the controller we needed time to review the new information, then checked our plan together before reporting ready. The departure continued after that. The lesson was to state the delay clearly and confirm the revised plan, rather than assume everyone had understood the change.

In one imagined departure, a wind shift led to a runway change just as the crew was preparing to taxi. We paused, told ground control we needed time to review the revised plan and divided the checks between us. Once both pilots were satisfied, we reported ready and continued. What stayed with me was how much confusion a brief, timely update can prevent when several people are adapting to the same change.