---

INTRODUCTION

Scratchpad entries for the scenarios listed below are NOT optional and must be complied with, even when working a complete combined position by yourself.

Scratchpad entries between TRACON and ENROUTE facilities will NOT be considered valid coordination without verbal/textual briefing of the data contained in the Scratchpad.
Reason: In the real world, ERAM facilities (CTR) cannot see the scratchpad assigned to an aircraft by a STARS facility (APP/DEP) and vice versa. This limitation is also fairly well simulated between vSTARS and vERAM.

Acceptance of a handoff with scratchpad data in the flight data block from another controller simulating the same type of radar system (STARS vs ERAM) constitutes acceptance and approval of the scratchpad entry.

The vERAM QS command without the Clear Weather Symbol (the ` keyboard button) is a fast way to issue headings and speeds into the Scratchpad, however due to limitations of the VATSIM FSD servers, these entries do not transfer to other controllers on the network. To ensure these entries can be seen by others, the Clear Weather Symbol MUST be used as if you were entering “Free Form Text”.

APPROACH ASSIGNMENT

1. Approach assignment/request scratch will be placed in the scratchpad by the controller that is responsible for assigning approach/runway to pilots.
2. Specifics not in the legend below such as HI-ILS/LOC, SA CAT I/II/III, PRM, Back-course and IAPs alike are not scratched and should be voice/text coordinated. Variants of the approaches are scracted such as A/B/C/D/X/Y/Z, if available.
3. The goal is to keep the scratchpad entry limited to 3 characters. Therefore, abbreviate the runway assignment to the last digit of the runway when an approach variant or runway L/R/C designation is present.
   1. When an approach variant is assigned/requested, along with the runway having a L/R/C designation, then a 4 letter scratchpad entry is allowed. Example: Billings (KBIL) RNAV Z 28R approach would be: RZ8R
4. Format:
   {Approach Type} {Variant} {Runway}

Approach Type Code Legend

Approach Type	Scratch
VISUAL	V
ILS	I
LOC	L
RNAV	R
VOR	O
LDA	D
CONTACT	C
GPS	G
SDF	S
TACAN	T
NDB	N
ILS/DME	J
LOC/DME	K
VOR/DME	F
LDA/DME	A
NDB/DME	B

Examples
{Approach Type}{Runway}

Approach Type	Runway	Scratchpad Code
Visual	RWY 01	V1
ILS	RWY 10	i10
Contact	RWY 10R	C0R
LOC	RWY 10C	L0C
LDA	RWY 10L	D0L

Variants

Approach Type and variant	Runway	Scratchpad Code
ILS Y	RWY 30	iY0
ILS Y	RWY 30R	iY0R
RNAV Z	RWY 1	RZ1
VOR-A	n/a	OA

ENROUTE

Enroute (CTR) positions or those providing services to Enroute aircraft must comply with 7110.65 5-4-10 “EN ROUTE FOURTH LINE DATA BLOCK USAGE”.

vZLC members are allowed to utilize the 4th line data to indicate that the pilot has stepped away from monitoring the radios by utilizing the inputs “AWAY” or “AFK”.

Members may also indicate when the pilot is expected to be back by placing the minuets after a slash. For example, this aircraft has been approved to step away from the radios for 5min. The current time is 12:18z. The 4th line data will display “AWAY/23” or “AFK/23”