Working Thames Radar - hints and tips?

JSJ

Hi all,
I'm now starting to get into the approach sectors, having got my head around Birmingham and Southampton, I thought I'd give Thames a try.

I like the new point merge implementation, seems easy to use with directs at the relevant point to ensure separation.

However, a couple of pointers would be appreciated:

When would be the right point to descend City inbounds for runway 27? I've started to descend them after leaving RAVSA and that gets them to A40 around NEPNA which may be a bit too early. I keep them at 220 knots until around IPKUS.
City outbounds towards Clacton I assume are to be kept at A30 to avoid the Heathrow inbounds on westerlies being descended on top, until the line through IPKUS?
For Biggin inbounds, I vector them towards the extended centreline for runway 21, but Biggin doesn't like that and takes them around for another go at the same altitude (A30), causing a potential conflict.

Any other hints appreciated.

Cheers.

CloggyUk

JSJ Hi.

I have never controlled Thames, but all deps of 27 need to stay at 3000 until clear of the LL-westerlies RMA.

Regarding descending traffic, early enough, but not too early in order to stay in your bit of airspace. You’d have to check the available maps to see what floor and ceiling are for each segment.

Do you establish the traffic on final for KB? It is potentially similar as with the issues reported in the LL thread and programmed routes. If possible, route it direct to the final approach fix if RNAV traffic, then switch to vectors to move it around the sky and establish it on final. If you could add some screenshots or a description how you route the traffic it can help working out why it happens. If I have time at some point I’ll see if I can have a go a Thames to see what’s what.

Cheers, C