1
Events / Re: ZFW Presents: The Nolan Danziger Memorial SNO
« on: September 17, 2022, 12:13:11 PM »
No banner?
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Are we talking about the bug with AFV or actual volume levels?
There is an AFV bug where the volume will unexpectedly go to astronomical levels and blow your ears out, and the next transmission by the same person will be normal. There was an entire channel dedicated to troubleshooting it in the AFV discord, not sure if it is still there or if that discord is active. It still happens all the time so I guess they never did figure it out.
As far as general volume levels I rarely have any issues. 1 in 10 pilots will say my mic is low, but I've done everything possible to mitigate that and its few and far between so I think pilots need to understand they can and should adjust aircraft volume in their settings/ plane settings and adjust the AFV volume in their pilot client.
Can we please get our microphone volumes under control? Ever since audio for vatsim came out, we've had this epidemic of people who are way too loud, and people who are way too quiet. I'll be flying along and all of a sudden: "CENTER THIS IS AMERICAN ONE WITH YOU!!!!" and if it doesn't blow out my speakers, it certainly makes my ears ring.
It's not only pilots. I find controllers with the same problem. My recommendation for everyone is at the beginning of your next flying or controlling session, go into your client settings and make sure your mic is in the green band.
Side note, does anyone have any hacks to make my pc mitigate suddenly loud volumes? If I could limit the maximum db level or something that would be awesome.
disclaimer: AAL1 callsign is a placeholder and not intended to single anyone out.
I am honestly a little confused with this one as the SID has published crossing restrictions from the CGO VORTAC as posted in this picture.
https://prnt.sc/1x6uqos
My best guess is to why they assign the "Climb Via Sid" instruction is to provide vertical separation for arrivals and departures. Since it is a radar-nav sid, I am assuming basically the TRACON will vector the aircraft to the applicable DTA to get aircraft on it's assigned route of flight. I also want to assume the TRACON may have aircraft fly over other aircraft that are arriving.
https://prnt.sc/1x6v8s9
In this second picture, at DRSCL the aircraft should meet DRSCL at 2200 feet and will be 6.7 DME from the runway. In the first picture, aircraft are required to be at or above 3000 feet 5.5 DME from the CGO VORTAC. I hope this helps in a way, but this is why I think that aircraft that fly the ORD6 are assigned climb via sid so they do not conflict with arrivals.
You're on the right track... It's for keep-them-in-the-Bravo reasons. Departures will never be in a position to conflict with the arrivals that are over the Marker. We have procedures that inherently separate departures from that portion of arrival airspace that we call "the dump". At the tower, we vector aircraft on initial headings so that they remain clear of the dump. The west flow dump is a 040 heading to a 140, east flow is 220-320.
The climb restrictions keep the ORD departures inside the Bravo, or even 1000 feet above the floor in come instances. This provides separation from not only MDW, but also PWK, and other satellite airports and satellite airspace.
Sometimes heavies on long flights (and BRICKYARDs ONLY FOR SOME REASON RYAN ) will notify us that they are unable to make climb restrictions, and we just have to coordinate with the TRACON so they can stop MDW departures and protect a little more airspace than normal.
I am honestly a little confused with this one as the SID has published crossing restrictions from the CGO VORTAC as posted in this picture.
https://prnt.sc/1x6uqos
My best guess is to why they assign the "Climb Via Sid" instruction is to provide vertical separation for arrivals and departures. Since it is a radar-nav sid, I am assuming basically the TRACON will vector the aircraft to the applicable DTA to get aircraft on it's assigned route of flight. I also want to assume the TRACON may have aircraft fly over other aircraft that are arriving.
https://prnt.sc/1x6v8s9
In this second picture, at DRSCL the aircraft should meet DRSCL at 2200 feet and will be 6.7 DME from the runway. In the first picture, aircraft are required to be at or above 3000 feet 5.5 DME from the CGO VORTAC. I hope this helps in a way, but this is why I think that aircraft that fly the ORD6 are assigned climb via sid so they do not conflict with arrivals.
I am also curious what drama could have possibly come up with this. Because in my experience, albeit limited, I haven't even heard rumors of any crews having problems with the climbing via the ORD6 in real life, let alone seen anything. Its pretty self explanatory. Hit the altitudes, follow the speed, that's it.
Not to sound frank, but I do honestly think that there are several other rules of the book that our energy should be focused on for the purposes of vatsim. But that's just me.
When i heard that JFK was having an FNO i new that it was gonna be one of the biggest FNO's Vatsim has seen in a while.. what i didnt expect was that i was held on Chicago Ground for 3+ hours for absolutley no reason, I departed chicago finally at 0150 Zulu, now noticing that i can no longer participate in the FNO im making the decisions if i should continue the flight or just close out of my sim. Why fly an FNO when you cant even Participate. Very Disappointed with this FNO
Regardless of what was agreed, the event is clearly a tongue-in-cheek nose-thumbing to the new FNO guidelines, which were instituted to *prevent* all FNO traffic from being focused onto a single airfield.
Yes, let's funnel an unrealistic amount of traffic into one of the 3 NY Metro airports during convective weather season and just hope for the best.
I'd better make sure someone's on ZMP so we can start creating 50 MIT for JFK over Iowa...
We know you’re sick and tired of flying into boring FNOs where all the traffic is nicely distributed!
Imagine using dodgy advertising to create ground stops and try to work around rules implemented and agreed upon by every ARTCC.
Nobody likes groundstops
I definitely think POSCON is on to something when they (a) are building an infrastructure which allows pilots to receive positive or negative feedback just like controllers do, and (b) empower controllers to take immediate action when pilots are disrupting the frequency and/or the flow.
Making those actions subject to review, and to discipline controllers who abuse them -- and making the note that the pilot receives when it happens constructive, encouraging them to fix the issue and try again next time -- those are the challenges. And they're big ones, which is probably why VATSIM leadership has balked at moving in that kind of direction.
Perhaps VATUSA or VATSIM HQ can build something similar to the real-world NASA Aviation Safety Reporting System, in which:As a long-term goal, statistics of the most common deviations at each facility can also be published, and facilities can address these specific issues.
- Any participating member (pilot, controller, observer) can submit a report.
- Incident reports are made public but personal identifying information (PII) is redacted.
- Constructive feedback is provided to the offending pilot so they can become aware of their mistakes, when often times there is not enough time for the controller to explain everything in the moment online.
- Self-reporting grants the offending pilot immunity (at least for the first violation) from certain CoC/CoR enforcement actions.
Fair, it is cool to see who's at the top and who isn't. But what exactly is the point of ranking 'best to worst' in a volunteer organization?
I'd suspect that facilities under, probably 10th are getting messages or emails from their RMs with something along the lines of "You should do better in your facility" (in fact, I know some are). So let me dive into why this, in my opinion, shouldn't be done:
1) Each facility has a different membership base with different circumstances. Some have a lot of new-ish members that are just here to have a good time, some take it more seriously, etc etc. Yeah, they all have a VATSIM CID. Let's use, ZMP as an example (ranked last). (Using HOME controllers only) ZMP has 78 controllers on there home roster. Now lets take out the OBSs that can't do anything (29). Now we have 49. Now, lets take into consideration how many controllers actually have a cert for any level (GND, TWR, APP, CTR): 40. Now, lets look at ZMPs uptime on any level of controlling, YTD (1/1 thru 6/30): ~756 (+/- a few, math done by hand, and there's probably positions I missed). Lets take that 756 and divide that by how many controllers were active with certs (40). That's an average of 18.9 hours per active, certified controller. Take into account ZMPs activity requirement (3 hours per calendar quarter) and they're doing just fine per their required hours (6 hours required for the two quarters, Jan thru June...literally averaging triple their requirement). Point here is, you can't just rate this all by up-time. It should be done using the logic above, to actually see how their doing.
2) What is the UNDERLYING cause of controllers not wanting to control? P I L O T S. I'll be damned if I'm going to staff more than I'm required, when us controllers are held to a crazy high standard, yet the 13 year old that gets MFSF2020 can connect without actually being checked for competency to comply with basic ATC instructions. Obviously this issue goes higher than VATUSA, but VATUSA isn't doing anyone any favors by telling facilities towards the bottom of the list "You should be online more." What VATUSA COULD be doing to help improve and motivate controllers to do more than what it required, is to be up at the front door of the BOG, knocking until they actually start taking pilot competency seriously. IT IS NOT FUN when we get online, and have to hand hold 50% of the pilots on our frequency. That alone is a big reason why most facilities don't have an higher uptime. Then you need to account for environmental factors like, I don't know, actually having a life outside the hobby, LOAs, etc. Controllers are BURNTOUT from dealing with the pilots that do not know what they're doing. We can preach to them that they should read the Pilot Learning documents, but currently that is merely a recommendation.
3) Last year (IIRC), VATUSA was more worried about having exit interviews with S1s (who cares?) when we should have been focusing on our C1+'s that got fully certified, worked some hours, and went away. Who cares why the S1 who did minimal training to work a DEL/GND position left? You'd have much more meaningful feedback if we focused on the fully certified C1+s that left after certification. If we did that, I'm willing to bet that you'd be hearing the same thing about pilots over, and over, and over again...if you had that feedback last year, maybe we could have made meaningful impact network wide regarding pilot competency, and eliminating that as a factor for Burnout.
4) You don't motivate leaders/members of a volunteer organization by comparing them to the guy next door. You're treating this as a company-type measurable metric, as if the pilots are our customers. No. Don't. PLEASE DON'T. By reaching out to some ARTCC leaders and telling them "We think your facility should be on more" again, is ignoring the underlying issues at hand. We need to first address the WHY, fix those issues, THEN we can begin to make headway in uptime.
Disclaimer - I wouldn't have made this post, if some ARTCCs weren't being told to "Do Better" when there are things that need to be addressed first, before we start asking more of VOLUNTEERS. This isn't meant to be an attack [insert legal jargon here] but is just honest feedback from a concerned VATUSA member .
Ross, while I would agree as far as intra-facility communications go it is (or would be) still useful for inter-facility comms. Something for thought.
The correct answer is Canes for chicken tenders, Chick-Fil-A for sandwiches.