While your lovely ATC Moderators enjoy trying to decipher posts about why you were ghosted, we’d like to request you include certain information that will help us expedite the complaint process.
•Your call sign when you were ghosted. Your call sign last week or earlier that day won’t help us. We need to know what it was at the time you were ghosted.
•Please include which server you think you were ghosted on. If you were “ghosted” on the training server, don’t ask for IFATC assistance resolving this because controllers can’t ghost on the training server. Further more, if there is no active ATC in the region you’re flying in, it was a user ghost. Once again, we won’t help resolve these issues.
•Please provide a name or screen shot of the controller information. This saves time by eliminating the step of us going to figure out who to contact.
•Please provide a screen shot of the communication log between your self and the controller leading up to the ghosting AND provide a replay of the session during which you were ghosted.
•Please provide a screen shot of the map at the time of, or immediately following your ghost. While we strongly encourage all ATC to screen shot ghosts, sometimes it’s not possible. We will watch the replay from BOTH the controller and pilot perspective before determining whether to reverse a report or not.
We do our best to investigate and verify all ghostings. IFATC is held to an extremely high performance standard which includes adhering to our ghosting guidelines. Very few people walk away happy when it’s a he said she said situation where none of the above information is included. We will reverse ghostings when needed. However, we won’t do it just because you disagree with it. After all the evidence is gathered and we (The ATC Mods confer a lot on this) feel the ghost was justified, it will not be removed.
Thanks for your cooperation!