Here is a good example relating to my previous post:

1

While on the approach to LAX just now, I was in contact with captain524 (SoCal Approach). Right from the start of the approach, I received instructions that zigzagged me toward the runway. Unfortunately—and please forgive me for saying this—it was handled so poorly that I ended up having to execute a missed approach, even though I had followed every instruction immediately.

The second attempt was no better and wouldn’t have allowed for a landing either; I was far too high—at 3,000 feet—right on the approach path. Then, immediately after the final instruction, I was admonished to consult the user guides. I aborted the flight. Receiving instructions that lead nowhere, followed by a reprimand to check the user guides, really isn’t fun.

r.

1 Like
2

I was United 2507 Heavy

3

I wouldn’t do that publicly. It’s always better to dm a controller and ask him, why this happened.
And if that doesn’t lead to a satisfactory solution, you still can contact some ATC supervisor or similar to sort that out.
I only had two cases, where I dm’ed an ATC and it was always a nice conversation, which explained everything.

4

well were you on ILS approach?
and maybe you didnt catch the localizer?
this is quite random i dont believe an approach controller doing such things as you call ‘‘zigzags’’ towards the runway

5

Hi,

I apologise that you’re unsatisfied with my service. It’s not appropriate to discuss the issue publicly and so I’ll be sending you a dm shortly.

3 Likes