...BATC directs you to descend to X, let's say 9K feet, and will be vectoring for a visual approach, and yet we're way too high considering how close we are to the airport. This happens to me too often and I'm assuming it's because I'm not following something hidden (to me!) in what ATC directs. The net result is that as it's vectoring me I will be essentially on a downwind leg but need to drop 7K feel to land, and yet it's telling me to turn 90 degrees to intercept an approach vector and we're only 10 nm from the runway. If you can speak to this issue, what I should be listening for to avoid this issue. It's the 'descend and maintain' that leaves me expecting further descent instructions and when I don't hear anything further leaves me puzzled.

Thanks in advance

that's just an issue with BATC's imperfect vectoring,

I just ignore all altitude descent instructions from BATC. I figure my TOD and do the descent anyway. When I get close enough to pick up the ILS I self-vector and fly the approach. I can’t believe after all these years they still get something as simple as descents and vectors ironed out.

Edited 2 hours ago2 hr by haskell