Voice and writing
How we sound
- Friendly and welcoming. Most people reading are new to us, and many are
new to flight simulation. Write as if you’re talking to someone on their first flight.
- Accurate about ATC, without walls of jargon. Use the right terms, and
explain the ones a newcomer won’t know the first time they appear.
- Clear that it’s a simulation. Indy Center is a community on the VATSIM
network, not a real air traffic control facility. Don’t write anything
that could be seen as real-world advice or guidance.
Names
- Write Indy Center for the community, every time. See
Name and terms for the names that sound alike.
- Write positions for pilots as they appear on the network: IND_CTR, IND_TWR,
CVG_APP.
- Write positions for controllers as they appear in the SOP: FLM 83, CVG LCW, LEX RE
- Write staff titles exactly as the staff page
shows them.** Titles are the most common mistake, so check before you post.
Times
- On the website and in Discord, times show in each reader’s own time
zone. In Discord, use its timestamp tags (
<t:1769644740:F>) so this
happens for you. Hammertime can generate them for you.
- Anywhere that can’t convert times (images, banners, stream overlays,
documents), write them in Zulu with a “Z”: 2300Z. Add the local time
after it if it helps, as event banners do: “2300–0300Z | 7:00–11:00 PM ET”.
- An event that starts at midnight Zulu may be written as 2359Z the day
before, so the Zulu date matches the date most of our members see that
evening.
The disclaimer
Wherever something could be taken for real-world guidance (material for
pilots to use, or tips on how to control), include this disclaimer:
Indy Center is not affiliated with the Federal Aviation Administration or
any governing aviation body. This material is for use on the VATSIM network
only.