Jump to content

Ryan Geckler

  • Content Count

  • Joined

  • Last visited

Everything posted by Ryan Geckler

  1. Saying you've read the docomeents is not the same thing as proving you've read the docomeents.
  2. So basically status quo. Got it. We aren't asking for a lot here guys - a basic, "did you read the rules of the network" test would suffice. Your initial pilot quality increases as the mistakes like connecting on a runway, improper unicom usage, and others go down. A mandatory P1 rating would be awesome, but it's a step that should be looked at after a smaller step has been taken.
  3. Do you think controllers shouldn't have to go through training then?
  4. Yeah, sorry that people who devote countless hours to learning and studying for tests have some different views on the network's direction. Didn't know that wasn't allowed. Maybe the reason it keeps coming up is that there is an actual issue and management hasn't properly addressed the cause? If it's been coming up since 2001, then there is a problem.
  5. "Never" is too strong a word here ... there are plenty of controllers that would have no problem handling a formation flight during an event. It depends on way too many factors to say it would never be allowed. I'd allow it. But the second you screw it up, it's over
  6. Glad to see this idea become less of a fantasy and more of a possible reality from the user base - it's something that I've wanted for a long, long time, and I think it's very overdue. Bingo - there are some differences though. Remember, we are working entire facilities of airspace at a time primarily... if we are busy, we don't have time to try and handhold someone down to the ground. In the real world, that aircraft will go to a different frequency where he is worked down without any distractions. That is a very, very, very rare case for the network.
  7. We have an LOA with them for them to control that field.
  8. Usually these callsigns are covered under a Letter of Agreement with the primary working facility. I'll see what I can dig up for you.
  9. Yeah, a beacon code will time out if it's not picked up on radar after some short amount of time. A flight plan will time out after 30 minutes.
  10. The real beacon code time out period is much shorter than that. I'll try and get you a firm number.
  11. The runways at FLL changed from 9 to 10 ages ago... why was the data so old to begin with?
  12. I have not tweaked the DPI, and yes, I did a proper troubleshoot
  13. Once I used those settings, the program stopped giving me errors. It was trial and error to get it to that point. I'm not sure how else to describe the problem...
  14. In the control panel, managed 3D settings: http://puu.sh/nnKHt/f2e39cc3a9.png http://puu.sh/nnKJi/525a1f5ae6.png
  15. Try it, but when I tried doing that, it failed to make a difference.
  16. This is the same issue I emailed you about. It took a full on driver reinstall and some tweaks to get it to work; be advised though, if you restart your computer, you have to go through the whole process again.
  17. Judging by the box that says "conflicts", I'm saying yes.
  • Create New...