Hello…
A recent topic conforts me in the idea for a violation issuing ratio.
What about an ATC specific statistic in the user profile showing a vio/ops ratio like a pilot can see its vio/landing ratio?
Could help adjust our issuing tolerance level ![]()
Hello…
A recent topic conforts me in the idea for a violation issuing ratio.
What about an ATC specific statistic in the user profile showing a vio/ops ratio like a pilot can see its vio/landing ratio?
Could help adjust our issuing tolerance level ![]()
What I’m going to say could be irrelevant to your request, but there’s already the violation to landing ratio.
What @J-F_V is asking for is one for ATC, similar to the landings/violations stat for pilots.
Think it’s a good idea and should be something that is easily implemented
Correct, I just thought the concept was too similar to the currently existing violation/landing ratio as it also shows ATC given violations as well as automated level 1 violations which also shows a pilot’s capability of keeping the correct speed and not flying unprofessionally near airports (stunts violations)
I’m sorry, but this “feature” makes no sense. Violations handed out from ATC doesn’t mean anything about the ATC. They cannot control the skill of the pilots nor the rate at which their operations and violations handed out grow. What if someone only controls at smaller airports, but still gets traffic from friends. It’s likely he has very few violations but still many operations. But that doesn’t mean anything about his ATC skills. Then you have someone who’s incredibly good, but always staffs LAX, JFK, LHR, and SYD. Now he’s gonna have a ton of operations too, but very likely a lot of violations handed out as well. Once again, it says nothing about his skill level.
I agree to a very large extend to Petre’s reasoning.
This violation-ratio idea may not say much about the IFATC’s skills, but it could say something about his/her attitude. We have IFATC’s with a huge variety of age and general experience, and I still see IFATCs out there who ‘like to play the boss’ rather than ‘serve the pilots’. And I don’t know if there’s a mechanism in IF that asks questions to IFATCs who have an unusual number of Reports. So maybe a ratio could help there.
To this respect, it isn’t the number of violations given that is seriously tracked, but the number of appealed violations per user. This is tracked internally by IFATC mods.
Also, I think I may have had a slight misunderstanding of the original feature request. I was thinking that @J-F_V wanted this ratio to be displayed for everyone to see. I realize now that he wants it to be for private use. I still don’t get how it’s a helpful stat, but I don’t have an issue with it being added. To me it just seems like there are other things related to ATC that would be more useful to track. But that’s just me.
A controller with 10,000 ops and 100 vios issued is not expected to be any more tolerant than a controller with 10,000 ops and 200 vios issued.
A controller won’t issue fewer vios because they feel like they’ve issued a lot recently. Commit a violation, receive a violation.
If you really want to avoid a violation, comply with all ATC commands and don’t do anything without approval from the controller.
I agree with this @NoirIncognito ; also different frequencies produce different violation to ops ratios
Approach tends to give out a lot more violations just because there is a lot more to manage when tuned into approach as opposed to tower/ground.
I believe Petre brings up several wonderful points; especially some airports being notorious for
pilots.
There are two potential scenarios I can think of if this is implemented.
A user looks up the ATC profile and sees the corresponding ratio.
If it’s high, the user might be more inclined to focus to try to prevent a mistake.
If it’s low, the user might be more relaxed and comfortable. I don’t think it will encourage trolling though.
I see more benefit than harm tbh. One thing to consider though…IRL pilots don’t see how many phone numbers an ATC has given out. But I doubt they see how many hours and landings other pilots have done too ![]()
Hello…
Yeah I was talking about a personal private statistic with total issued, total appealed, and how much reversed or maintained so a controler could « feel » its own behavior.
Let’s say I’m a new controller. Having a statistic saying
total ops 54, vio issued 6, appealed 3, maintained 3
Vs
total ops 54, vio issued 32, appealed 28, maintained 2
could help me early understand better my behavior.
The point is as a controller, I don’t (very rarely) have follow up on my vios issued. Knowing how much got appealed / maintained in a simple private and anonymized stat field could be great.
Like some of you said it wouldn’t be a perfect thing…like G score some landings can be worst than other and sessions / stations have different challenges and work load.
As I said in another msg, I see this as a personal performance stat like landing G’s score for a pilot more than a strict quality check system for IFATCs.
But yes it could also be used to introduce ratio levels like green all good, yellow - high level of reversed by appeals detected (optional measure to take), and red - you very above the average etc…
But this colored levels part I agree wouldn’t be very useful or effective. And there is already something to address this appeal team says above.
To make it short, as a controler I would like to see the statistic privately on my profile, but wouldn’t want it to be a disciplinary or quality check tool
Then you’re changing your feature request… because your feature request is currently a violation/operation ratio, which I think has been shown to be unhelpful and perhaps even could be detrimental.
Also, violations to appeals and successful vs unsuccessful appeals are already tracking internally by IFATC. I’m not sure if this would work, but I think DM’ing a moderator asking for the counts would get you that number. However I could see the appeal to be able to view your own stats at will. That might be a conversation that has to happen between IFATC admins and IF staff ![]()
If you issue a vio and it’s successfully appealed due to misuse, you’d be notified.
If you issue a vio and it’s appealed but you’re not wrong in issuing it, you might not be contacted.
If you issue a vio you won’t ever be updated on the status of the appeal, but you will be notified if you issue a vio incorrectly or they request additional info in the investigation.
If you want to know how many vios you’ve issued improperly, count the amount of times a supervisor or appeals team has corrected you.
@NoirIncognito was definitely right, and I think that this is actually more appropriate to be introduced than the one in the feature.
Everyone may meet a misbehaving pilot. In this case, issuing violation correctly is just a matter of probability and not much referable. It is the misuse that makes the difference.
Misuse/total instead of total/operations. Also this should be private for self-improvement only.