Skip to main content

Flightstrips Common Features

Group 664.png

1.1 Scopes

All configurations of Flightstrips includes various Scopes. Each position may have different versions of a scope, depending on whether the position is strictly controlling its own AOR, or also other areas as part of “top-down controlling”.

Each scope consist of four columns of similar size.

At the bottom of the each scope is the “task bar” for common features between the scopes.

e.g. EKCH_A_GND, will have the scope of AA+AD when sitting as the only apron, but will have the scope of APN ARR when sitting with a A/B_GND split.

Rectangle 324.png

1.2 Bays

Each of the four columns are several “bays” stacked on top of each other, all labelled with a header detailing the phase of movement where each particular bay should be used.

Strips are located within the bay generally sorted from bottom and up.

Critical bays such as bays reserved for runway occupancy have highlighted black backgrounds

A bay may, or may not also have buttons for various tactical tools applicable to that phase of movement.

Rectangle 324.png

1.3 Flight Strips

Flight Strips comes in two colors. A Blue strip for outbound flights, and a Yellow Strip for inbounds.

 

While the many different looks of strips may seem confusing at first, they are all based on the same fundamentals.

  1. SI Field
    • Description: The transfer/assume mechanism, indicating the owner of the strip.
      • Operation: Click to Transfer/Assume
  2. Callsign Field
    • Description:The field of clicking to drag the strip around
      • Operation: Click and hold to select the strip, and drag it to another bay, or
              • Click to highlight to strip and click on a bay to move
  3. Action Fields
    • Description: Various fields of action items and information items,
      • Operation: Varies from scope to scope, from bay to bay adjusting to the important

1. The SI Field

SI field has different colors depending on the state of ownership of the strip.

  • Purple: when it is concerned, meaning you will receive ownership of this at some point, but not yet.
  • Purple/White: In transfer towards YOU from previous controller
  • White: Assumed and controlled by YOU
  • White/Orange: In transfer towards next controller from YOU
  • Orange: Transferred and accepted by next controller

The logic is identical to transfer/assume in COOPANS, only difference is Concerned in COOPANS is green instead of purple.

2. Callsign Field

The callsign field is one which you can click on. Clicking the callsign does two different things depending on whether or not you have assumed the strip (white color SI field).

NOT ASSUMED
Not assumed

Clicking on callsign field will open the “Callsign Menu” where you can select various submenus

- FORCE ASSUME: Takes the strip and assumed it, regardless of who is the owner.

- VIEW FPL: Opens the flightplan of the strip

ASSUMED
Assumed

Clicking on the callsign field, will select the strip, made apparent by the purple fill color of the field.

Holding the click down will allow you to drag the strip around.

Clicking on an empty space in another bay will move the strip around.

It is common procedure to click and drag the strip to establish the correct sequence within the bay

3. Action Fields

Various click spots, some to open menus, some are not clickable. It varies between the bays, and is explained in the position specific chapters.

Rectangle 324.png

1.4 Task Bar

Common to all scopes are the Task bar, which enables various features. It contains from left to right:

SCOPE VIEW

Preferred scope is opened by default, but can be changed if needed. Click to manually select a different scope.

WEATHER INFORMAITON ICONS

Displays the weather and runway in use information from the ATIS and Euroscope setup. Runway selection can be manually selected if needed. ATIS can be clicked to view full ATIS. Will display in RED if no ATIS is connected.

RWY STATUS ICONS

Three icons displaying each of the three runway pairs. They are black by default.

Can be selected as LOW-VIS (Orange displayed)

Can be selected as CLOSED (Red displayed)

STRIP ACTION ICONS

To the right of the runway status icons is the 4 strip action icon.

  • TRF: After selecting a strip (click on callsign), clicking on TRF will open a menu to manually select any online controller to transfer a strip to.
  • MRK: After selecting a strip (click on callsign), clicking on MRK will mark the strip by a purple outline for tactical purposes
  • REQ: After clicking on REQ, click on any strip on your scope to request a transfer to you, to receive the strip.
  • X: After selecting a strip (click on callsign), clicking on X will delete the strip.
Group 435.png



Group 664 (1).png

FlightStrips contains several types of strips, which are tactical and not associated with a flight. They are identified by being distinctively different colors from the strips.

Rectangle 324.png

2.1 MESSAGES

All scopes contain a bay for internal messages, to communicate and coordinate with other flight strips users.

To use press one of the buttons in the Messages header. Write your own, or select the most commonly used standard messages.

Select the specific position you want to write your message to, or select BROADCAST to send the message to everybody using FlightStrips. Once a message is sent, it can be individually deleted by each controller by clicking on the “X”.

All messages are subject to VATSIM-Scandinavia rules and VATSIM Code of Conduct limitations.

 Rectangle 324.png

2.2 MEMORY AIDs

Memory aids are types of strips a controller can activate to put a condition or reminder to an aircraft.

Clicking the MEMAID button in the appropriate headers, opens the MEMAID window which is similarly structured to MESSAGES.

To make a flight specific memory aid, select the flight before clicking memory aid, and you will see the airplane in parenthsis in the MEM AID strip.

 Rectangle 324.png

2.3 CROSSING

CROSSING strip takes a bright yellow color and is a tactical reminder when an aircraft in one bay, as to cross the path of an aircraft in another bay.

To create a crossing strip, click on the “X” in the yellow box above a qualifying bay. The strip is produced instantly.

Once produced, you can move it around, to the correct position to reflect where traffic will cross.

Any controller can force ownership of the “CROSSING” strip by clicking on the strip and selecting “FORCE ASSUME”. A “CROSSING” strip should be deleted once the condition is no longer present.

Examples of use are:

GW_TWR needs to cross 22L on the way to Apron East. Crossing strip activated by A_TWR to signify gap where GW can cross

A_TWR needs to taxi via C and RWY30 to K3. Crossing strip activated by D_TWR to signify gap between departures A_TWR can cross.

 Rectangle 324.png

2.4 LAND/START

LAND and START strips takes bright orange colors. This strip is to mark an aircraft landing or taking off on a runway, where the strip may not actually be present.

Uniquely to LAND/START strips an hourglass is present, which can be clicked to start a time. This can be useful for Wake Turbulence separation.

 

Examples of use are:

A_TWR needs a landing on 22R. Strip can be activated to signify landing on 22R.

A_TWR needs a low pass on RWY30. Strip can be activated on TWY DEP to ensure no flights are crossing 12/30 while aircraft performs low pass.

Back to top