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 TypeScratch
VISUALV
ILSI
LOCL
RNAVR
VORO
LDAD
CONTACTC
GPSG
SDFS
TACANT
NDBN
ILS/DMEJ
LOC/DMEK
VOR/DMEF
LDA/DMEA
NDB/DMEB


Examples
{Approach Type}{Runway}

Approach TypeRunwayScratchpad Code
VisualRWY 01V1
ILSRWY 10i10
ContactRWY 10RC0R
LOCRWY 10CL0C
LDARWY 10LD0L

Variants

Approach Type and variantRunwayScratchpad Code
ILS YRWY 30iY0
ILS YRWY 30RiY0R
RNAV ZRWY 1RZ1
VOR-An/aOA

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”.

For convenience, the following is a quick guide for users.

The following Field F entries are approved for use without verbal coordination:

  • Headings – the letter H followed by a three digit number
  • Present Heading – the letters PH
  • The Forward Slant character serves as a “until joining…” or “when able, cleared direct…” as appropriate.

Examples – H050, PH, H180/JAX, H300/J79, H240/V157, PH/CHA

  • Assigned Speeds – the letter S followed by a three digit number, or M (Mach) followed by the two-digit assigned value. Do not insert a period after the “M”.
  • The symbol (+) (maintain a specified speed or greater), or the symbol (-) (maintain a specified speed or less) may follow the assigned speed or Mach number.

Examples – S250, S210+, S230-, M82, M76+, M80-

  • Weather deviations must use the designated characters
    • D – deviation
    • L – left
    • R – right
    • N – north
    • E – east
    • S – south
    • W – west
    • /(NAVAID or Fix) – direct next NAVAID/Fix
    • D+2 headings – deviate between (D090+120)
    • If weather deviation instructions exceed the nine character limit, verbal coordination is required.

Example – D20L/PROVI is not an appropriate scratchpad. Verbal coordination is required because that command exceeds the character limit.

  • Two digits specify turns in degrees and must include direction characters. Three digits specify headings.
    • DN, D20L, D090/BOS
  • The inclusion of a /NAVAID or /waypoint indicates that the pilot has been authorized to deviate for weather and must rejoin the route at the NAVAID, waypoint, or fix indicated in the fourth line entry.
    • Examples: DL/ATL, D20R/ONL
  • The absence of a NAVAID or waypoint indicates that the pilot has been instructed to deviate for operational needs, but has not been recleared to join the route. The receiving controller must provide a clearance to rejoin the route.
  • Aircraft authorized to conduct celestial navigation
    • Example: CELNAV
  • Request for altitude change – the letters RQ followed by the requested altitude in three-digits.
    • Examples – RQ090, RQ150, RQ350
  • Request for route change – the letters RQ, followed by a slant (/), followed by a specific fix identifier.
    • Examples – RQ/ICT, RQ/TUL, RQ/PONCT
Fourth Line Data Examples
HeadingH104, PH, 20R, 35L
SpeedS300, S230+, S250-, M78, M80+, M82-
Heading and SpeedH240, M75
Weather DeviationsD20L, D080+120, DL/ATL, D20R/ONL, D090/F
Free Form TextH090/FSM, PH/CHA, RQ/WENDY. RQ090, RQ270, CELNAV, NORDO, AWAY, AFK