Notes
Notes - notes.io |
[01:07:03] NC_SUP: Hello , My name is Nicholas Cavacini, I am one of the VATSIM supervisors. The time is 01:07 UTC, please reply.
[01:07:06] NC_SUP: To contact me simply type (without the quotes) ".msg NC_SUP hello" and then press enter.
[01:07:51] FRDY13: hello
[01:08:53] NC_SUP: Sir, you departed with ATC and now claim that you are unable to contact APP. In addition, you either hit or came very close to hitting another aircraft
[01:10:38] FRDY13: Unable contact it true. this aircraft cannot tune to that frequency. I maintained visual separation from that airctaft, at least 1K vertical and 1NM ahead/behind
[01:11:26] NC_SUP: Why can you not tune the frequency?
[01:12:21] FRDY13: i can tune to 125.14 and 125.16. I suspect that the F22 does not have the international "in-between" frequencies available to most commerical aircraft.
[01:13:07] NC_SUP: You can use the vPilot dot command of (dot)com1 125.150
[01:14:42] FRDY13: thank you for that information
[01:15:50] NC_SUP: You should be with Boston Center 134.7
[01:15:59] NC_SUP: and please fix your squawk code
[01:21:07] NC_SUP: In this case you were in violation of VATSIM Code of Conduct sections A1 and B3. A1 for disturbing the traffic in the airspace and B3 for failing to contact CYUL_APP
[01:23:38] FRDY13: I believe I had good intention via "see and avoid" concerning A1. I maintained adequate separation as the overtaking aircraft.
[01:24:07] NC_SUP: The controller was receiving a conflict alert regarding the seperation
[01:24:53] FRDY13: What does a contact alert entail? Because I know that VFR aircraft are not subject to such alerts.
[01:25:26] NC_SUP: a conflict alert means that the required seperation between aircraft has been compromised
[01:26:48] NC_SUP: The controller had no idea of your intentions and when I arrived it appeared that you could very well have collided with the other aircraft
[01:27:00] FRDY13: I am a VFR aircraft opperating via see and avoid. I should not be held liable for a conflict alert that does not have to do with VFR rules and regulations.
[01:28:41] NC_SUP: A controller is responsible for seperation between aircraft, even VFR. Since you did not have positive communication with ATC they had no idea to your intentions or if you had a visual. It appeared that you could have been either intercepting the aircraft or colliding with it
[01:31:49] FRDY13: The Pilot should be responsible for separation of aircraft, espically VFR. Is that not what See and Avoid principles are based on? The pilot has final responsibility, not the controller.
[01:32:35] NC_SUP: Yes. however, by not contacting the controller as required you caused a disturbance in the airspace
[01:34:31] FRDY13: 1) I am not required to contact the controller as a VFR aircraft who is not flight following 2) Using the full extent of my aviation knowledge, i sqked the appropiate code without delay.
[01:34:56] NC_SUP: You were in the class charlie airspace so you were required to be with ATC
[01:35:29] NC_SUP: plus, when you were given a handoff instruction to contact another controller, you are required to follow that per CoC B10. The other controller is expecting you
[01:35:43] FRDY13: Point 2) is still valid.
[01:37:30] NC_SUP: true, however squawking 7600 on VATSIM does not relieve you of the duty to contact a controller
[01:37:59] NC_SUP: if the controller insists. even during n emergency, that you terminate, you are required to
[01:39:51] FRDY13: Over time time frame of aprox 2 minutes i was contacted by Jerome Nourault (the controller) via text aprox 22 times while I was sqk 7600. not once did he allow me to trouble shoot, not did he offer assistance.
[01:40:27] NC_SUP: Do you have a log of that?
[01:40:32] FRDY13: yes
[01:40:42] NC_SUP: Can you take a screenshot of it?
[01:41:42] FRDY13: Yes, I have done so.
[01:42:03] NC_SUP: Can you either email it to me or upload it?
[01:42:33] FRDY13: stand by please.
[01:43:59] FRDY13: here is the upload link http://imgur.com/3eXEEmh
[01:45:42] NC_SUP: Ok, I do see that. It could have helped to include why you were unable but sending a rapid fire series of contact requests is not appropriate
[01:49:49] FRDY13: OK. So what will come of this situation?
[01:53:05] NC_SUP: So neither party was in the right. The 23 contact requests was very excessive but you should have contacted ATC. I can't really fault ATC for anything besides that because by what you replied with, it appeared that you were unwilling to contact ATC
[01:54:34] NC_SUP: That being said, i do understand where you are coming from so I won't count it as an A1
[01:56:07] FRDY13: Thank you for being able to see where I am coming from.
[01:57:04] NC_SUP: No problem. Don't worry, you won't be suspended or anything from this
|
Notes.io is a web-based application for taking notes. You can take your notes and share with others people. If you like taking long notes, notes.io is designed for you. To date, over 8,000,000,000 notes created and continuing...
With notes.io;
- * You can take a note from anywhere and any device with internet connection.
- * You can share the notes in social platforms (YouTube, Facebook, Twitter, instagram etc.).
- * You can quickly share your contents without website, blog and e-mail.
- * You don't need to create any Account to share a note. As you wish you can use quick, easy and best shortened notes with sms, websites, e-mail, or messaging services (WhatsApp, iMessage, Telegram, Signal).
- * Notes.io has fabulous infrastructure design for a short link and allows you to share the note as an easy and understandable link.
Fast: Notes.io is built for speed and performance. You can take a notes quickly and browse your archive.
Easy: Notes.io doesn’t require installation. Just write and share note!
Short: Notes.io’s url just 8 character. You’ll get shorten link of your note when you want to share. (Ex: notes.io/q )
Free: Notes.io works for 12 years and has been free since the day it was started.
You immediately create your first note and start sharing with the ones you wish. If you want to contact us, you can use the following communication channels;
Email: [email protected]
Twitter: http://twitter.com/notesio
Instagram: http://instagram.com/notes.io
Facebook: http://facebook.com/notesio
Regards;
Notes.io Team