Bex. .I don't think the 'Area bod' did his job properly. Surely passing an estimate, obtaining a squawk/freq constitutes a basis of co-ordination. Why then was the aircraft put on a 7000 squawk and told "suggest you contact...they have your details"? That's pretty wishy washy and patently not what was previously agreed. It's proved to be open to quite a bit of interpretation so far on this forum so it it must have been equally difficult for a foreign aircrew to appreciate the subtlety of what had been arranged.
IMHO, I think this demonstrates a growing lack of awareness amongst some Area controllers of the rest of us providing ATSOCAS out here in 'injun' country. ACC's responsibility doesn't stop at the boundary of CAS. (MATS pt.1 refers!!). I know the primary task is within CAS and I accept that they're outrageously busy but it can also be argued that they're suitably equipped and qualified to provide RIS/RAS/FIS in the vicinity of CAS.. .My unit (APC and primary Radar) is about 20nm from the nearest CAS and it's fairly common for our inbounds to be leaving CAS between 20-50nm out. We have an excellent relationship with our nearest LARS unit(s) and some of our airways traffic is handed over to them. They, in turn, will co-ordinate with us. More often than not, though, ACC will just point leavers in our direction and freecall them. We rarely get estimates,(although I have actually noticed an improvement since NERC) and often the first call from the aircraft is late, high and conflicting with our procedural 'stack'!. .I'll climb down from my soapbox now and wait for the fallout!!