Pilot Training Realism

Pilot Handbook
_________________________________________________________

PTR
PILOT HANDBOOK
PTR Pilot Handbook 2

[Page intentionally left blank]

Created by the PTR Staff Team

PTR Pilot Handbook 3

Chapter 1:
General Introduction to PTR
SECTION 1: WELCOME TO PTR

1-1-1. Introduction
Welcome to the Pilot Training Realism server, also known as: PTR.

1-1-2. About PTR

What is PTR?: PTR is a server that aims to provide a 24/7 type realism server on
the Pilot Training Flight Simulator game, similar to VATSIM. We are a group that
is based and uses time from the United States of America. We are different from
other servers such as V1 and ATC-24, because we not only have a 24/7 server
running, but we also host events in the middle of that server going on. We also
offer 24/7 service to ALL air traffic control positions, such as Center, Approach
and Departure, Tower, Ground, and Delivery, though these positions may not be
online 24/7.

1-1-3. Purpose of PTR

The entire purpose for PTR, is to be different from other servers that provide a
realistic experience in PTFS. We aim to be open 24/7, while hosting events that
pilots can fly in every week at different locations.

Created by the PTR Staff Team

PTR Pilot Handbook 4

Chapter 2
Flying on the PTR Network
SECTION 1: INTRODUCTION

2-1-1. Flying
When flying on the PTR Network, pilots are expected to know how to navigate the
map using the charts provided by PTR. Pilots are also expected to follow all of the
rules when on the PTR Network.

2-1-2. Communication
Pilots on the PTR Network are to maintain United States Phraseology with Air
Traffic Controllers, and vice versa. Pilots are also required to contact the correct
controller based on where they are flying (Ex. If a pilot is flying enroute from
YPPH > ISAU, and they are above the Chicago Airspace [RFD], then they must be
in the ZAU enroute frequency [ZAU_CTR]). There is more information on this on
the pilot guide

SECTION 2: AS A PILOT…

2-2-1. Aircraft
Pilots are expected to know how to fly the aircraft that they are equipped with. If
you are used to flying smaller jets, and decide to fly the A380, we suggest the pilot
becomes familiar with the aircraft before they fly it on the network.

2–2-2. Flight Plans

When flying IFR (Instrument Flight Rules), pilots MUST file a flight plan using
the google form linked in the flight plans channel.
When flying VFR (Visual Flight Rules), unless going by “Flight Following”, pilots
are NOT required to file a flight plan using the google form.

Created by the PTR Staff Team

PTR Pilot Handbook 5

When filing any type of flight plan, pilots are required to use the correct
information that the form field says (Ex. ICAO for Departure Airport). Many
mistakes come from both the altitude, and equipment suffix. If you need help with
any of these, please read the pilot guide linked here.
Pilots are also required to file a valid route. (Ex. KRFD/18R EASTN1 INDEX
HONDA RJTT/31)

2-2-3. Reading ATIS

Before requesting VFR or IFR clearance, it is requested that pilots read the D-ATIS
of the correct airport(s) they are flying at thoroughly to fully understand the
operations, weather, and remarks before flying to avoid confusion.

2-2-4. Getting Instructions from ATC

As a pilot, you are required to follow all instructions given by the controller you
are currently with.

2-2-5. Reading Back Instructions from ATC

As a pilot, you are required to fully readback instructions given by ATC, not matter
what it may be. You may ask the controller if you can alternate, and do something
else that does not follow the instruction, but if the controller denies that request,
you must do what you are told by the controller.

Created by the PTR Staff Team

PTR Pilot Handbook 6

Chapter 3
Pilot Rules
SECTION 1: GENERAL RULES

3-1-1: Leaving the Network

Leaving the network is okay at any time. When you leave on the ground and
haven’t talked to a controller, there is no reason to say anything, you can reset, log
off, and do whatever. HOWEVER:
- When on the GROUND and have talked to a controller, not only do you
have to tell the controller you are logging off, but you must coordinate where
to put your aircraft (in the ocean, grass, etc.)
- When in the AIR and have talked to a controller, you have to warn the
controller that you are going to leave, and when safe, jump out of the plane
so that it will fall out of the sky and everyone dies :)

3-1-2: Aircraft Restrictions

For airliners and cargo (Boeing 737, Airbus A340, etc.):
- 1. You cannot file under VFR (Visual Flight Rules)
- 2. You may not file a custom callsign with any airliner. The only exceptions
are for freighters, and for the “SkyWest” callsign for regional jets.
- 3. You must maintain a speed at or below 250 knots when departing out of
any airport
- 4. In the departure airspace, aircraft must maintain speed restrictions given
by ATC. When entering an airspace, they must be at or below 210 knots, no
exceptions unless given by ATC.
- 5. You must follow all speed, altitude, and heading changes given by ATC
For VFR/General Aviation Aircraft:
- 1. When filing under a custom callsign, you MUST stick to the N_____
format. (Ex. N6542D, N6206D, NU537C, N123AB)

Created by the PTR Staff Team

PTR Pilot Handbook 7

- 2. When flying in General Aviation aircraft, you have the option to choose
either IFR or VFR
- 3. When flying in certain general aviation aircraft, you must be careful of the
equipment suffix, and whether or not the aircraft is RNAV, VOR, or DME
capable.

SECTION 2: PILOT AND ATC COMMUNICATION

3-2-1. Voice Chat Limitations

Both controllers and pilots cannot do the following in ANY voice chat:
- Interrupt over other controllers and pilots talking in the frequencies (also
known as “keying”, in real aviation)
- Scream in frequencies
- Yell at other pilots
- Start arguments
- Having conversations in active frequencies
- Use any derogatory language in frequencies (strong curse words, slurs, etc.)
- Name-call
A frequencies purpose is restricted to the following:
- For talking to pilots and controllers

3-2-2. In-Game Text Chat

Text chat in game is NOT used for ATC and Pilot communication. It can be used
for controller coordination, and asking a controller a question when a frequency is
open. Controllers and pilots MUST have access to a microphone in order to fly on
the PTR Network.

3-2-3. ATC Instructions

Pilots must follow all instructions given by controllers. If necessary, the pilot can
request something different, though if denied by the controller, the pilot must do as
they were told.

3-2-4. Phraseology
Pilots and controllers must use United States Phraseology when flying and
controlling on the PTR Network.

Created by the PTR Staff Team

PTR Pilot Handbook 8

SECTION 3: FLYING

3-3-1. Charts
Pilots must follow the charts that are used at all times when flying on the PTR
Network.

3-3-2. Staff interactions

If a staff member sees you breaking one of either the server rules, or any of the
rules listed above, they reserve the right to ban, kick, or mute you if deemed
necessary. They also reserve the right to drag you into a private room to discuss
something you may have done. If you leave during that, you may be punished with
a strike for evading a moderator, plus whatever the offense was.

SECTION 4: APPLICATION

3-4-1. Applying
Pilots are allowed to apply as many times as they need in order to be accepted.
Pilots must answer at least 8 of the application's questions correctly in order to be
accepted.

3-4-2. Googling/Searching Answers

Pilots are NOT allowed to be searching up/googling answers in their application.
Currently, the application does not have a way for us to determine whether or not
you googled the answer. However, a good way for staff members and other pilots
to know that you cheated is if your knowledge in-game does not match up to your
application. If caught searching up/googling answers, a pilot’s role will be revoked,
and if necessary, they can receive a modlog.

Created by the PTR Staff Team

PTR Pilot Handbook 9

END OF PTR
PILOT HANDBOOK

Created by the PTR Staff Team