Air Traffic Control

[Ronni_Fuentes]

1. Me: Sitting at 6,600 and climbing.
2. ATC: Climb and maintain 6,000.
3. Getting close to 8,000.
4. Please follow instructions or you will be reported.
5. Breaks >250 knots trying to descend back to 6,000 at at least a -5,000 fpm vertical speed.

[BennyBoy_Alpha]

Hey there!

It’s probably best to reach out to the controller privately and explain the situation from your end. We are human and sometimes make mistakes.

See the second part of the topic below for more info re. controller feedback:

Procedures for Appealing Violations and Providing ATC Feedback

[IMG_4201] Introduction With the recent UI changes, I thought it would be a good idea to update my previous tutorial on handling appeals and feedback. For this tutorial, I have created a scenario in which a pilot needs to reach out to an IFATC controller. The aim of this tutorial is to provide a step-by-step guide on how to message a controller and handle appeals, including visual examples. For more guidance on in-app information, please check out the User Guide. Common Reasons to …

[Ronni_Fuentes]

Thanks, @BennyBoy_Alpha ! I wasn’t reported or anything I’m just trying to find out just in a general sense if I’m missing something.

[BennyBoy_Alpha]

Which is why I suggested reaching out to the controller to get their perspective - part of that article is about ATC feedback.

[Ronni_Fuentes]

Yep and I said, ‘Thank you!’ because I read, understood what you said, and appreciated and appreciate your time and help. I wasn’t intending to leave feedback nor was I requesting a repeal of a violation.

[aatogamer]

Why’d you make the topic then?

@Ronni_Fuentes

I’m just trying to find out just in a general sense if I’m missing something.

If the above is what you’re trying to achieve, you should do just what Ben told you: send a PM to the controller.

[Ronni_Fuentes]

??

1. Was I on a Live Server on Infinite Flight?
2. Did I describe a situation and subsequently ask a question?
3. Is it fair to say that the creation of this topic created a discussion?

[aatogamer]

@Trey

If you do not agree with an aspect of your service, please feel free to reach out to the controller via private messages. Public topics will be closed. Similarly, as mentioned in the “Violation Resolution” section, all communication must be respectful and in a calm state.

The topic you’ve been directed to multiple times states that these inquiries should be solved via PM.

In my opinion, you saying you were treated in a certain way doesn’t create any kind of useful discussion that should be open to the public and therefore should be solved privately.

[Riley_Dupont]

just send a PM to the controller.

[Ronni_Fuentes]

… 4. If I was given a violation, believe me I would ask for clarification first and more than likely an appeal.

5. I don’t need to tag any controller in this situation, but just a ‘Hey!’ to any controller …

a. [Callsign], please follow instructions. (i.e. Warning #1.)
i. I immediately tap twice on the communications tab and seeing the last message from the controller that maybe I misunderstood.
ii. I am correcting expeditiously in a way that I do not interfere with an aircraft in my vicinity.

The previous point is EXACTLY what I did.

b. [Callsign], please follow instructions or you will be reported. (i.e. Warning #2.)

6. Why is there such a difference between warnings and controllers?

a. Again, a situation on Expert Server, with the callsign ‘Air Force 2’ is given not one but two ‘Please follow instructions’ messages, and then the report warning.

If I do something wrong, ATC, please send the “Please, follow instructions.” If I don’t listen again, send the ‘…you will be reported…,’ message. If I don’t listen, again, please report me.

I am more inclined to do so now, because I will say it is quite simple:

1. ‘Hey! Let me tap this aircraft on my frequency again.’
2. What is the last very last message I transmitted?
3. Tap ‘Show Information.’
   a. Verify the altitude I assigned.
   b. Verify the current altitude of the aircraft in question which is shown on the third line from the top of the information box.

c. Situation 1: They are not within let’s say +/- 500ft of the assigned altitude.
i. Warning #1
ii. If they don’t correct, send Warning #2.
iii. If not correcting within reason (a few seconds at most)…: Issue Report/Violation.

d. Situation 2:
i. I verify the altitude I assigned as a controller.
ii. I send “Warning #1.”
iii. I verify the altitude shown under user information and accidentally missed that they were ascending.
iv. “[Callsign], I’m sorry.”
v.“[Callsign], climb and maintain (8,000, for example) [or insert any altitude greater than the accidentally transmitted altitude or altitude at which the aircraft is currently ascending through.”

[aatogamer]

@Ronni_Fuentes

I don’t need to tag any controller in this situation, but just a ‘Hey!’ to any controller …

Why’d you then describe what happened to you today with ATC and then ask clarification for it? That’s indicating you want to know what happened, and that you will have to ask from the controller themselves. They don’t bite.

Making a public topic (and putting a wall of text there) is not the way to go. Your best bet to get clarification is - once again - sending a private message to the controller.

Procedures for Appealing Violations and Providing ATC Feedback

[IMG_4201] Introduction With the recent UI changes, I thought it would be a good idea to update my previous tutorial on handling appeals and feedback. For this tutorial, I have created a scenario in which a pilot needs to reach out to an IFATC controller. The aim of this tutorial is to provide a step-by-step guide on how to message a controller and handle appeals, including visual examples. For more guidance on in-app information, please check out the User Guide. Common Reasons to …

[Petre2026]

@Ronni_Fuentes I understand where you are coming from, from your explanation, you weren’t trying to poke at the ATC officer or something like that. But, the reason why you got the feedback you did from this topic is that there is no question in your original post and it is worded against the controller, such that it could almost be taken as a dig against whoever was controlling at the time. Besides, the answer to your question would probably best come from the IFATC officer with whom you interacted, because it may differ from what the community thinks. However, your later post here:

@Ronni_Fuentes

c. Situation 1: They are not within let’s say +/- 500ft of the assigned altitude.
i. Warning #1
ii. If they don’t correct, send Warning #2.
iii. If not correcting within reason (a few seconds at most)…: Issue Report/Violation.

d. Situation 2:
i. I verify the altitude I assigned as a controller.
ii. I send “Warning #1.”
iii. I verify the altitude shown under user information and accidentally missed that they were ascending.
iv. “[Callsign], I’m sorry.”
v.“[Callsign], climb and maintain (8,000, for example) [or insert any altitude greater than the accidentally transmitted altitude or altitude at which the aircraft is currently ascending through.”

this could be a better topic for discussion as the the different ways to handle more universal scenarios.

@aatogamer I don’t think it’s necessary to keep pushing the topic. The directive to continue in PMs has been delivered, and there’s no need to press any other points or remarks.

[aatogamer]

@Ronni_Fuentes

a. [Callsign], please follow instructions. (i.e. Warning #1.)

@Ronni_Fuentes I’m not getting what you’re referring to from here onwards? I just see a big wall of text and no explanation as to what it is regarding? I’d be happy to answer but it’d be great to know your main point first.

@Petre2026

@aatogamer I don’t think it’s necessary to keep pushing the topic. The directive to continue in PMs has been delivered, and there’s no need to press any other points or remarks.

Yeah. I’ve made my point and learnt my lesson now. Thanks and apologies.

[adit]

Hi, this is the original info you provided:

The above is case specific: you claim you were instructed to climb to an altitude you claim you already climbed above.

There is no “how does ATC work” type of issue here that enhances general educational about ATC.

It is a claim of disagreement of the condition leading to the warning you claim you received.

You need to work out the facts with the controller, as already pointed out.

@Ronni_Fuentes

I’m just trying to find out just in a general sense if I’m missing something.

Contact the controller to assist you with clarifying the cause of the discrepancy in your claim.