Trevor_Bartlett’s ATC Tracking Tread - (CLOSED) @ KSMF

Hello everyone! Welcome to my ATC training and tracking thread.

I’ll be controlling Ground and Tower at KSMF. I passed my written exam on my second attempt, but unfortunately I did not pass my first practical evaluation. I’m using this thread to document my progress, improve my skills, and track my development as a controller.

Here are the main areas I’m focusing on:

  • Traffic Pattern Entries
  • Runway Change Operations
  • Aircraft Separation Standards

I’m looking forward to improving with every session. Any constructive feedback or advice is always appreciated. Thanks for following along, and I hope you enjoy watching my progress!

(Also a little note - I follow the irl ATIS of airports)

STATUS: CLOSED

AIRPORT: N/A

SERVER: N/A

RUNWAYS: N/A

4 Likes

I will finish my flight and come for a visit in about 30 min if you will still be open.

1 Like

Yes, I’ll still be here.

1 Like

I’ll stop by for a visit

1 Like

Stopping by for a pattern :slight_smile: will be quick though, need to work on va

1 Like

@Trevor_Bartlett Taxing to my gate at DFW then joining I’ll do pattern work

I’m currently closing but I’ll be open tomorrow

2 Likes

@Trevor_Bartlett Swoop 1 Feedback:

  • Give way conflict on the ground was resolved well, and in correct priority. Remember that similar to roads, taxiways have priority as well. It goes from lowest to highest:

  • Gate → Apron → Secondary taxiway (at some airports) → Primary taxiway → Runway exit → Runway.

  • For the departure, make sure that you give me clearance for takeoff before instructing Delta to lineup and wait (LUAW), but the vision is correct!

  • You don’t have to wait for so long when I am in the air to give me a clearance. This can be given as soon as I liftoff from the ground to maximise your efficiency.

  • One of the main issues today was the fact that you did not give any sequences. Sequences are very important as this command informs the pilot who they are following and where is that aircraft. What you should have done is told Delta the following:

    Delta xxx, number 2, traffic to follow is on left crosswind

    This way he knows who to fly behind.

  • After I have requested to change the runway, your pattern entry for me was Straight in. This is incorrect as I was on Left Downwind (LDW). So your commands should have been:

  • Swoop 1, enter left downwind runway 17R.

    wait for readback from me before sending next command

    Swoop 1, number 1, cleared for the option, after the option, make Right traffic.

Each runway has its own pattern. If I change runways - I need to have a Pattern entry, then a clearance for the option with new traffic direction. (For this scenario that I am in pattern work).

Upwind conflict.

  • Correct upwind conflict resolution is when you extend upwind for the aircraft that is further back or the one that requested the runway change. Not the one that is trying to turn away for their normal pattern. So you mixed this up.
  • After you extend upwind of the aircraft that wants to change and aircraft that is in the way turns away, then you need to give a new PE for the changing aircraft (Delta) and the best way to do this is to give them Right Downwind as a PE. This forces them to turn right and follow me instead of having to maintain both Right downwind and Left downwind for the same runway.

One last thing I will say: pattern work is VFR traffic. This means that pilots are responsible for their own separation. Commands such as maintain slowest practical speed (for separation on downwind and/or base) are unnecessary unless you are trying to make a gap between planes for someone else to take off.

Why was this wrong today?

I requested runway change from 17R to 17L. I have now changed the pattern. Delta stayed on 17R. We do not conflict at all. If we wanted to, we can fly as close as 100ft from each other because it is our responsibility to maintain separation for safety. Check runway assigned is a good command to know, but today there was no need to use it as I was simply crossing other runway cone and trying to fly parallel with Delta.

I hope this helped you and I encourage you to look back through your replay and look at those point. I also strongly recommend you to watch this video as it explain each of the things you will need to know for your test and also why we use those commands.

Best regards,

Maxim/Snooot

2 Likes

Feedback from delta 4141 heavy

Takeoff

  • please don’t issue a line up and wait before clearing the aircraft in front

First pattern

  • No sequence. You should always sequence a plane before clearing them

Second pattern

  • The UWC (upwind conflict) was technically correct, but not the correct way. A more preferred way is to instruct the aircraft changing to enter for the pattern direction for the specific runway (sequence them if required)
  • The “extend down wind, I’ll call your base” was not necessary, a sequence can fix this.
  • The “maintain slowest practical speed is not necessary on downwind, but the usage on final was definitely necessary

Overall great job for a beginner. Here’s some advice, I would personally recommend that you read the ATC manual. I would also recommend watching The perfect ATC test it will help you learn how to handle the situations in the practical test.

Great job today.

Happy controlling! I’d personally like to thank snooot aka @Maxim.k42 for helping me out today I couldn’t have done it without him

1 Like

STATUS: Opened at KSMF

@Trevor_Bartlett Joining now

1 Like

@Trevor_Bartlett I am a Boeing 757-200 American.

1 Like

I’m coming back to test your pattern work.

you should probably decend and slow down..

Sadly can’t join, good luck

1 Like

I’m about to close anyways. Maybe next time!

1 Like

Status is OPENED

dropping in 15 min to do pattern work

1 Like