When VH-CWR requested change to 17R on upwind, that was known as a UWC. What you should do is the following:
VH-CWR enter right downwind 17R
VH-CWR extend upwind
Await for conflicting traffic (A6-HRF) to turn crosswind.
If conflicting traffic does not turn in a timely manner, you can send the conflicting traffic a “turn crosswind/base”.
VH-CWR, number 2, traffic to follow is on right crosswind
VH-CWR turn downwind
The pushback to the wrong direction was fine, although next time you can check first since the airport wasn’t really busy
On my first pattern I had to request for touch and goes, when you could’ve just cleared me for landing since I was remaining in the pattern
The “Unable” when I requested change to 17R was completely unnecessary, you could’ve told me to extend upwind, or made me make left traffic for 17R instead. If the separation wasn’t enough on downwind you can just tell me to extend dw
Other than that, you’re all good! Good luck on your IFATC journey @B38M !!
I thought it was to be given after the aircraft has slowed down (below 40 kts), but @Cwaker has corrected me on that, I’ll keep that in mind. Thank you for your feedback!
Airport : FSIA Server : Training Duration : 2025-04-16T09:00:00Z→2025-04-16T10:00:00Z Remarks : RWY 13 in use, pattern work and departures are allowed.
Ping list : @Cwaker@Waxyscorpion308@Lagggpixel
FSIA is now closed. Thank you to everyone that came by!