Position Management
Positions are the core of Landline's structure. Each position represents a controller seat that can log in, make calls, and receive calls. This guide covers creating positions, configuring VATSIM matching, and setting up consolidation trees.
Creating a Position
- In the FE panel, select Positions
- Click Add Position
- Fill in the position details (see below)
- Click Save
Position Fields
| Field | Description | Example |
|---|---|---|
| Callsign | Unique identifier displayed in the grid | 1A |
| Display Name | Friendly name shown on hover/call panel | PHX Arrival North |
| VATSIM Prefix | Pattern for VATSIM position matching | P50_APP |
| Page | Which page this position appears on | Enroute |
| Grid Order | Position in the grid (left-to-right, top-to-bottom) | 1 |
VATSIM Position Matching
The VATSIM Prefix field determines which VATSIM callsigns can log into this Landline position.
How Matching Works
When a controller connects to VATSIM with a callsign like ABQ_16_CTR, Landline checks:
- Does the callsign start with any configured prefix?
- If multiple matches, the most specific match wins
Matching Examples
| VATSIM Callsign | Position Prefix | Match? |
|---|---|---|
| ABQ_16_CTR | ABQ_16 | Yes |
| ABQ_1_CTR | ABQ_16 | No (ABQ_1 ≠ ABQ_16) |
| ABQ_CTR | ABQ_ | Yes (catch-all) |
| PHX_TWR | PHX | Yes |
Specificity Matters
If you have both
If you have both
ABQ_ and ABQ_16 prefixes, a controller on ABQ_16_CTR will match the ABQ_16 position (more specific).
Consolidation Trees
Consolidation routing automatically forwards calls when a position is not staffed. This mirrors real-world sector consolidation.
Setting Up Consolidation
- Edit a position
- Set the Parent Position field
- Save the position
Example Consolidation Tree
ZAB_CTR (Parent - Combined Position)
├── 1A (PHX Arrival North)
├── 1B (PHX Satellite North)
├── 1K (PHX NW NAA)
└── 1C (PHX Arrival South)
In this example:
- If 1A is offline, calls to 1A ring at ZAB_CTR
- If both 1A and ZAB_CTR are offline, the call cannot be completed
ZAB_CTR
Parent (Online)
1A
Offline
1B
Online
1K
Offline
Calls to 1A and 1K route to ZAB_CTR
Multi-Level Consolidation
Consolidation can be nested up to 3 levels:
ZAB_HIGH (Level 1 - Area)
└── ZAB_EAST (Level 2 - Sub-area)
└── 1A (Level 3 - Sector)
Keep Trees Shallow
Deep consolidation trees (more than 2-3 levels) can be confusing for controllers. Try to mirror your real-world consolidation practices.
Deep consolidation trees (more than 2-3 levels) can be confusing for controllers. Try to mirror your real-world consolidation practices.
Position Types
Optionally categorize positions by type for better organization:
- Center - ARTCC/TRACON radar positions
- Approach - Approach/Departure control
- Tower - Local tower positions
- Ground - Ground control
- TMU - Traffic Management Unit
- Supervisor - CIC/Supervisor positions
Bulk Operations
For facilities with many positions:
Import from CSV
- Prepare a CSV file with columns: Callsign, DisplayName, VATSIMPrefix, Page
- In the FE panel, click Import
- Upload your CSV file
- Review the preview and confirm
Export Configuration
- Click Export in the Positions tab
- Save the JSON file as a backup
- Can be imported later to restore configuration
Best Practices
Naming Conventions
- Use consistent callsign format:
FACILITY_SECTOR - Keep callsigns short (8 characters or less)
- Use descriptive display names
Grid Organization
- Place frequently-used positions at the top-left
- Group related sectors together
- Consider workflow when ordering positions
Next Steps
- Channel Configuration - Set up communication between positions