Fly.akm’s ATC Tracking Thread - [CLOSED] @ N/A

Just found this whilst studying the manual…

I think I should issue a back-taxi, not a T/O, if so, do I clear it for takeoff after it’s lined up? Or do I send another command asking for a LUAW?

Also this. 👆

Adding on to it, is it possible that I decline their request and give them progressive taxi instructions?

In this instance it is specific to the situation. Like the manual states “Controllers should be proactive.”

If you use back-taxi I would only use it in the case that there would be a exit and hold short space at the end of the runway. As for not giving clearance to begin with would be more stress and tough on the controller especially in a busy environment. Just think you give a Back Taxi & LUAW and the pilot is isnt cleared for take off and is still in the LUAW waiting for clearance with a plane on Short Final and you scrambling to get to the command. Take off makes so much more sense.

Yes just give cross.

Make sense?

1 Like

Yessir, thanks!

1 Like

Currently studying, but I do plan to open sometime tomorrow.

Feel free to vote in the mean time!

What airport should I open at tomorrow?
  • KSAN (San Diego)
  • EGSS (Stansted)
  • KSNA (Santa Ana)
  • EGLC (London City)

0 voters

2 Likes

Nice thread… will probably come along if I am free when you open… so you can add me in your ping list!

1 Like

Added! Hope to see you today when I open! :)

1 Like

add me to that ping list! will hopefully try and make it but i have finals this week so ill do my best :)

1 Like

Update #2


I have successfully finished thoroughly studying the Tower Manual on the guide. I feel quite confident, it’s a lot to pack in, lots of scenarios and circumstances, but I think I’ve got it down.


I’ll be opening at KSAN today at 2021-05-23T08:30:00Z, look out for a status update soon.


Here’s the Study Guide/Notes document I use if you’d like to add any comments or tips & tricks.

Open at KSAN


Airport Frequencies Runway/s in Use Focus Point
KSAN Ground & Tower 27 Inbounds and mastering Ground

Notams:

  • Light aircraft allowed.
  • Pattern work allowed
  • Alts for patterns are exactly 1,000 for TBs and 1,500 for TJ.

Open until 2021-05-23T09:25:00Z


Feedback Format

When giving feedback please I would really appreciate it if you could copy the embedded text below, and give me your ratings & honest feedback!

|**Tower Controlling**|Profeciency Level 1-10|

-----

|Ground/Tower|Topic of Mistake|Feedback|Profiecency Level 1-10|
|---|---|---|---|


Ping List:

@Julien_Narayanasawmy
@Airborne_Canuck
@Steven_Tellmann
@Shane
@Darius_Glover
@Collins4486
@nicopizarro
@JulietTango
@HappyDays
@LordWizrak
@Marquatzi
@MJP_27
@JulianQ
@Kedz
@Gritz

i’ll come in around 15 minutes!

1 Like

I’m coming!

1 Like

Sounds good!

Ok!

1 Like

I’ll be there!

Feedback HB-ANT

Ground

  • No issue

Tower

  • Very long delay to receive a “hold short” instruction. I requested departure in sequence, what means you can give me “number 2 for departure” as N1DL was also waiting for takeoff.

  • Could have told me to LUAW after the aircraft passed the threshold. You can be more efficient with arrival/departure.

  • You should have cancelled my takeoff clearance and told G-KEDZ to Go-Around.

If you have any questions, do not hesitate to PM me 😁

1 Like
Ground/Tower Topic of Mistake Feedback Profiecency Level 1-10
Tower Clearance Should be number 2, not number 3 since Alaska 261 has passed the threshold Profeciency Level 7
1 Like

Feedback-G-KEDZ:


Inbound/transition:

  • Incorrect transition altitude, 2000ft was too low. The pattern altitude at SAN is 1500 using the formula (airport elevation + pattern alt for jet which is 1500 AAL). From this, you need to add 1000ft to the pattern altitude and round it up to the nearest thousand. This would mean transition altitude at SAN is 2500ft AAL.

  • Slow response times in general, be speedier to catch conflicts.

  • I could of fit before Alaska, best thing was to sequence them behind me but sequencing me behind them was also fine. I would of had fit if you had faster response times.

  • Pattern entry and sequence was good.

  • No direction with clearance for the option, tell me what direction to make when it touch and go so i know where to fly the pattern. I made right traffic to not confuse you.

  • No sequencing on second pattern, you needed to sequence me behind Alaska.

  • No clearance for the option, had to announce my position and i still had not recieved any clearance.

  • Got very close to HB-ANT. Despite my speed, you should have canceled their takeoff and sent me around. They had to stop themselves. Additionally, i had to call go around because i had not recieved any landing clearance.


That’s all for me, thanks for having me! I suggest thoroughly going through the ATC manual, good first session.

1 Like

Feedback, N1DL

Ground

  • Only use expect runway XX when you know that you need them to face that direction to avoid any conflicts.

Tower

  • I had no idea why you sent me back to the ground frequency, hence the “request frequency change”

  • Really slow departure rhythm. Me and HB-ANT had multiple gaps for us to depart in. A good rule of thumb is, if the arrival is under 3 nm away it’s a good idea to wait.

  • I didn’t receive any clearance or sequence during my entire pattern as a result I tried to hint it to you that you needed to give me a clearance + sequence with reporting position along the way. A good way to ensure this is to have everyone “green” on your screen before at the latest late downwind. You can already begin to sequence people on their crosswind leg.

  • Saudia001VA should have been sequenced behind G-KEDZ after their transition, followed by a sequence to me to follow Saudia.

  • In general you missed a lot of Go Arounds, remember it is the controller whom should initiate this, and not the pilot.

Other than that great job 👏🏻

2 Likes

Feedback from Alaska 261

  • Ground was good
  • Separation is something you have to be aware of. As @DannyHL said, you missed quite a few go arounds, especially during base and final. In the end I had to announce go around due to lost separation, which the controller is the one to give such an instruction, not the pilot.
  • 09:06:36 There were no other planes on the airport or in the air by then. The maintain slowest practical speed was unnecessary.
  • 09:06:38 Very late clearance. I was less than 1nm to the runway and the clearance should be issued during downwind or base.
  • 09:07:19 Late exit runway command, it was at 50 knots instead of 70.

Overall it was a nice session, there are just things that you have to be aware of!

Oh, and just leave the callsign alone. Nothing special

2 Likes

I agree, I messed up a lot on the arrival/departure separation and clearances.

One of my biggest mistakes, I noticed that.

Yes, also noticed this, my apologies.

Wait what? Why?

Yeah, my separation and sequencing wasn’t the best.

Another big mistake by me, I keep forgetting to clear for the option and give landing clearances for full stops.

Mhm.

Ok, I’ll remember that next time.

Thanks for coming! I’d love to see you come the next time I open! :)

Ok, but I do specify the runway when I give taxi clearance?

That was a complete fail on my part, I messed up bad and for no reason whatsoever switched you back.

I have to agree.

I read this on the ATC manual, it said when an aircraft is at 600 feet, it’s 3nm away, for some reason though, the altitude doesn’t change on my screen when I show aircraft information.

Yep, won’t happen again.

Thanks for coming and the feedback!

Taken note of!

Mhm.

That’s odd, I issued it when you were at 67, maybe I was lagging.

Thank you so much! I’d love to have you come again!

2 Likes