First, a slight rant.
I was approaching Kai Tak airport from the south in a Cathay Pacific A330. I followed all Approach ATC instructions and eventually I was about number 3 in line to land. The approach controller notified us that he would be closing in 2 minutes. Finally, approach closed, but I still followed the vectors I was given beforehand. Suddenly, to my right, a giant 777 comes barreling at me- getting so close, it’s icon turned red. A new ATC comes online and tells me to expect vectors to Kai Tak. However, instead of clearing me for approach, the 777 is cleared, and I am instructed to climb once again and take another 30 minute circle of Hong Kong. I ended up quitting because I didn’t have time to make another full approach.
Now obviously it wasn’t the controller’s fault- he/she must’ve thought that it was my fault for being so close to the other aircraft. However, there may be a solution to this problem and other similar ones.
My idea: there should be sharing of logs between IFATC controllers. Basically, if ATC is going through a controller switch and the new controller comes on within 30 minutes, all of the logs are transferred to the new controller. This would allow the new controller to see exactly what had happened before they joined, which would help avoid confusion during controller changes, as well as make them more efficient.
Anyway, that’s my idea.