Complaint against a member

[michael chute 905072]

Hi:

 

Normally I don't complain about others but another member just about caused me to crash last night. I was flying KCVG to KCHO in a CRJ200 for DVA under the call sign DAL3551. The other chap was flying from the East to KCHO in a Cessna 172. I did notice him on the display and used private chat to announce myself and try to get an idea of the ETA's for both of us. He was using the call sign D9296.

 

He arrived first and had ample time to land on R3. I was 100nm west and preparing an ILS approach to R3. As I arrived and began my turn to final. I find him circling the outer maker on the ILS approach at 3000'. I could not fly over/under and as I approach I realized I would hit him and I had to go around.

 

In fairness, I not sure of his motive here---perhaps he just wanted to land with me. Our chat to this point had been friendly and professional but I wish he could be made aware of fying error.

 

Thanks for listening

 

Mike Chute

[Javier Larroulet]

Michael,

it's generally not a good idea to make the callsign public, even though you did it in a very polite way. The other user may have been a newbie who wasn't aware of the proper holding places and/or altitudes or may have not realized he was going to interfere with your landing. Whatever the reason, instead of making a public complaint, it's best to try to dialogue with the other user via private chat or, if unable bacause you're handflying for example, summon a Supervisor who can talk to the pilot and let him/her know that such actions may be disruptive to other people's enjoyment of the network. Chances are the other pilot didn't actually mean to interrupt your approach phase.

 

Cheers!

[Travis Faudree 821145]

Sure it wasn't 3300? Thats the published altitude for the holding pattern over the AZS NDB on the ILS 3 approach at Charlottesville. Being a ZDC controller, we encourage GA aircraft to shoot all sorts of practice instrument approaches in order to better their understanding of the finer points of IFR flying. Its unfortunate that you two reached the same point in space at the same time, but you cannot put any more fault on him than yourself. He was following proper procedure for a holding pattern over the NDB on the approach. Did either one of you announce on UNICOM? Also, please keep in mind that SB3 users have the option of turning off private chat windows, and therefore he may have never received your private chat message attempt to coordinate with him. Had you used the UNICOM frequency, you would then have a valid complaint.

[michael chute 905072]

Thank you both for your advice. We did use both private chat AND unicom.----and he was circling at 3300 not 3000. I am the new one if anybody is and I apologize if I have overstepped proticol. I am not sure (still) of the process to seek out advice of a supervisor. In so far as his call sign being public, I thought all our call signs and names are in the public domain

 

Thanks again for the advice

 

Mike Chute

[Carlos Perea 934840]

At the very least, you've learned that it's best to fly on VATSIM with crashes turned off.

 

I remember my second or third flight, where I connected to the network at a gate with crashes turned on. I connected on top of another aircraft, and was thrust into a never-ending series of crashes since Flight Simulator kept putting me back on top of the other aircraft. There was another time when I was flying with multiplayer aircraft turned off to save frame rates, and I inadvertently taxyed through another aircraft, and he lost his FSP[Mod - Happy Thoughts]engers flight (and began to send me a series of rude private messages).

[Jim Johnson 814050]

Use the command ".wallop " to contact a Supervisor. Example:

 

.wallop Need help at KCVG please.