Virtual NATO Flight Planning Suite

Operational Air Traffic (OAT) & Tactical Dispatch System

Operational Disclaimer: This software and manual are proprietary assets of Virtual NATO (re-established in 2017) and are designed exclusively for simulated virtual aviation environments (such as VATSIM). Distribution outside Virtual NATO or without express authorization from vCMC & vDCMC is strictly prohibited. This tool must never be used for real-world flight planning, navigation, or operational dispatch.

Quick System Overview

Welcome to the vNATO Flight Planning Suite. This system integrates automated route generation, country-specific OAT reporting conventions (France, Germany, United Kingdom), Item 18 remark formatting, and live METAR/TAF weather decoding (powered by https://www.checkwxapi.com) into a single unified dispatch console.

Quick Navigation

OAT Guide & Rules

Review national air traffic regulations and routing protocols.

Parameter Glossary

Comprehensive reference of all flight plan variables and inputs.

Equip & PBN Guide

Avionics codes, transponder modes, and PBN qualifications.

Export Log Guide

Manage and download your automated flight export logs.

Virtual NATO Command • Re-established 2017 • vCMC & vDCMC Operational Infrastructure

V5.4 OPERATIONAL GUIDE

ICAO Flight Planning

Build the plan in layers: input, internal state, route compilation, ICAO serialization, preflight validation, then VATSIM import.

FPL

Simulator use only. This suite is designed for Virtual NATO operations in simulated aviation environments. It must not be used for real-world flight planning or dispatch.

Layer Verification Before Generation

INPUT→STATE→ROUTE COMPILER→ICAO FPL→PREFLIGHT→VATSIM

A fault should be corrected at the layer where it originates. A valid ICAO value is not silently changed merely because an external importer presents it differently.

Items 7–10

Callsign, flight rules/type, aircraft type, wake category, communications/navigation equipment and surveillance capability.

Item 13 / 16

Departure, EOBT, destination, estimated elapsed time and alternate aerodrome.

Item 15

Cruise speed/level plus the compiled route, including operational speed/level changes, STAY and transfer points.

Item 18

PBN, NAV, STS, DOF, REG, SEL, PER, OPR, ORGN, COM, STAYINFO and RMK data.

Item 19

Fuel endurance is kept separate from Item 18 and serialized as the final endurance element where supported by the generator mode.

Preflight

Use the VATSIM Import Preflight panel before copying the plan. Resolve errors first; review warnings against the intended mission.

Speed & Level Formats

Field	Format	Example	Meaning
Speed	N	`N0450`	Knots TAS
Speed	K	`K0830`	Kilometres per hour
Speed	M	`M080`	Mach 0.80
Level	F	`F300`	Flight Level 300
Level	A	`A080`	Altitude in hundreds of feet

Recommended Workflow

Select jurisdiction and generator mode. Confirm the country convention before mission-specific data is entered.
Enter aircraft and dispatch data. Callsign, type, departure, EOBT, arrival, EET and alternate.
Configure route semantics. Route, transfer points, STAY blocks and speed/level changes must be associated with the intended waypoint.
Complete equipment and Item 18. Do not advertise capability the simulated aircraft does not have.
Generate and run preflight. Correct structural errors before importing.
Verify the VATSIM form. Compare the imported form with the generated FPL; importer limitations are covered in VATSIM Compat.

WEATHER DESK

Weather Guide

One entry point for METAR, TAF and the live Weather Briefing tool.

WX

METAR

Observed wind, visibility, weather, cloud, temperature/dew point and pressure at the reporting station.

TAF

Forecast conditions and change groups including FM, BECMG, TEMPO and probability groups.

WX Brief Tool

Fetch current METAR/TAF data and view the decoded parameters inside the operational panel.

Fast Reading Order

WIND→VIS→WX→CLOUD→TEMP/DP→QNH→TREND

Operational habit: use the weather products as part of the simulated briefing, then cross-check mission constraints and aerodrome suitability. The helper explains codes; it does not replace pilot judgement in the simulated environment.

OCEANIC REPORT V1.1

Oceanic Operations Guide

Resolve the route, connect the VATSIM aircraft, track sequential fixes and generate a position report from actual/estimated progress.

🌐

Important: Oceanic Report assists simulated operations only. It does not automatically transmit a clearance request or position report to ATC.

Quick Start

1Complete / load FPLUse the route intended for the sortie.

2Open Oceanic ReportUse the OCEANIC REPORT tool button.

3Check navdataImport compatible X-Plane navdata if named fixes need resolution.

4Build / resolve routeConfirm every operational fix that must be tracked.

5Resolve custom fixesAdd coordinates for vNATO/OAT points absent from AIRAC.

6Connect VATSIMEnter the exact pilot callsign and establish live tracking.

7Verify live aircraftPosition, altitude, groundspeed and heading should update.

8Monitor sequential fixesPassed → active/next → future; unresolved fixes protect against skipping.

9Generate reportUse actual crossing time for passed fix and ETA for the next fix.

How Fixes Are Resolved

Coordinate Fix

454901N0013507E

Decoded directly by the suite. No navdata lookup is required.

AIRAC / Named Fix

MALOT

Resolved from the locally imported waypoint/navaid dataset.

Custom vNATO Fix

MGO01

Mission/OAT points not found in AIRAC can be assigned and retained in the local custom-fix library.

Navdata

The suite can process a compatible X-Plane-style ZIP, or waypoint/navaid text files. Navigation data is stored locally in the browser and is not bundled with the vNATO distribution. Re-import a newer package when the user's AIRAC cycle changes.

Duplicate identifiers: where more than one candidate exists, the resolver uses route geometry/current aircraft context and prefers suitable waypoint candidates. Always verify the resolved point before live tracking.

Live Tracking State

RESOLVED / PASSEDCURRENT / NEXTATTENTION / UNRESOLVEDERROR / DISCONNECTEDFUTURE

VATSIM● CONNECTED

NAVDATAAIRAC 2609 ✓

LASTMALOT 1243Z

NEXTSUNOT 1307Z

FOLLOWING52N040W

Position Report Logic

ACTUAL crossing

When live tracking detects the aircraft crossing the active fix, the suite records an interpolated UTC crossing time from successive VATSIM position samples.

ESTIMATED next fix

The next-fix ETA is calculated from current progress. It remains an estimate and can change as groundspeed/track evolves.

CALLSIGN / LAST POSITION / ACTUAL UTC / FL / NEXT POSITION / ETA / FOLLOWING POSITION

Why Hasn't My Fix Advanced?

Unresolved fix: sequential protection can intentionally prevent the tracker from skipping an unresolved operational point.
Callsign mismatch: the VATSIM callsign must match the connected pilot exactly.
Not connected / stale feed: verify the live status and aircraft data fields.
Route geometry: confirm the fix resolved to the intended coordinate, especially with duplicate identifiers.
Off-route flight: the aircraft may not pass sufficiently close to the active fix for a crossing to be confirmed.

REFERENCE LIBRARY

Operational Reference

Fast access to parameter definitions, equipment/PBN capability and common ICAO formats.

REF

Parameter Glossary

Definitions for the main form variables and operational fields used throughout the suite.

Equipment & PBN

Communications/navigation/surveillance equipment, transponder modes and PBN qualification references.

Common ICAO Tokens

Token	Purpose in this suite
`PBN/`	Performance Based Navigation capabilities.
`NAV/`	Additional navigation capability or mission-specific navigation information.
`STS/`	Special handling status; V5.2+ may also mirror it into RMK for VATSIM compatibility.
`DOF/`	Date of flight, YYMMDD.
`REG/`	Aircraft registration.
`SEL/`	SELCAL code when applicable.
`PER/`	Aircraft performance category.
`OPR/`	Operator.
`STAYINFO/`	Information associated with an operational STAY block.
`RMK/`	Free-text remarks and vNATO operational signature/compatibility notes.

Capability discipline: equipment/PBN values should describe the simulated aircraft and mission configuration, not simply everything available in the selector.

INTEROPERABILITY

VATSIM Compatibility

Separate valid ICAO output from importer-form behaviour and network representation.

VATSIM

vNATO INPUT→ICAO GENERATOR→VALIDATION→myVATSIM IMPORT→NETWORK

Core rule: a blank or differently represented field in the VATSIM form does not automatically prove the generated ICAO FPL is wrong. Verify the layer first.

Area	Suite behaviour	Tester action
Mach / Airspeed	Preserves valid Item 15 Mach notation. V5.2+ provides a VATSIM-oriented TAS estimate rather than silently rewriting the FPL.	Check the generated Item 15 and the separate myVATSIM Airspeed field.
Altitude / FL	Preserves the selected ICAO level notation and derives the corresponding feet value for import verification.	If the form is blank, compare it with the generated FPL before reporting a generator defect.
STS	Keeps structured `STS/...` and mirrors it in RMK for compatibility where required by the current suite design.	Verify both Item 18 and the resulting VATSIM remarks.
Y / Z / Tactical	The suite can model operational rule changes, while external network/client representation may be more limited.	Report the generated string and what the VATSIM UI/network actually displayed.
STAY / STAYINFO	STAY is compiled at the selected waypoint; STAYINFO remains structured Item 18 data.	Check route position first, then whether the external importer retained the Item 18 information.
RMK ordering	Structured Item 18 values are serialized before final RMK so remarks do not swallow later indicators.	Include the complete generated FPL in any defect report.

Best Tester Report

BUILD: V5.4
GENERATED ICAO FPL: [paste exact output]
EXPECTED: [what should happen]
ACTUAL: [what happened]
VATSIM MESSAGE: [exact parser/import text if present]
SCREENSHOT: [attach the resulting form]

Operational Disclaimer: This software and manual are proprietary assets of Virtual NATO (re-established in 2017) and are designed exclusively for simulated virtual aviation environments (such as VATSIM). Distribution outside Virtual NATO or without express authorization from vCMC & vDCMC is strictly prohibited. This tool must never be used for real-world flight planning, navigation, or operational dispatch.

1. Introduction & Regulatory Context

Operational Air Traffic (OAT) flight planning governs military and state-configured aircraft operations, requiring strict adherence to national Aeronautical Information Publication (AIP) standards and virtual network (such as VATSIM) filing rules. Because live pre-file systems automatically reject tactical flight rules (T), flights must utilize a safe fallback framework (I for IFR or Z for hybrid rules) while preserving OAT routing rules inside the main route string and Item 18 remarks.

2. Country-Specific Routing & Remark Standards

France (DGAC / DIRCAM): The route string must never start with the term "OAT". However, active OAT phases must be declared by placing RMK/OAT at the beginning of the Item 18 remarks field.

Germany (BMVg / Luftwaffe): The route string must start with "OAT" followed by a space. Remarks do not require the OAT prefix (using standard tags like RMK/VIRTUALNATO.ORG), and airspace blocks follow structured formats (e.g., EDR208 308 1600 1700 FL100 FL350 FOR TRAINING) alongside standard fuel endurance parameters (FUEL0200).

United Kingdom (RAF / MilAIP): The route string must start with "OAT" followed by a space. Operations incorporate specialized national infrastructure including Radar Corridors (e.g., LICHFIELD RC, DAVENTRY RC), Low-Flying Areas (e.g., LFA7), and specific STAYINFO tags.

3. Route Construction & Formatting Rules

No Airfield ICAOs in Route: Never insert departure or destination airfield ICAO codes inside the middle of a route string.
Space-Separated Syntax: Chronological waypoints, radar corridors, and transition descriptors must be separated by single spaces.
STAY Segment Sequence: Low-Flying Areas, Air Refueling tracks (AAR), or working blocks require a STAYX/HHMM entry attached to their waypoint in the route, paired with matching STAYINFOx/ remarks.

4. Tactical Flight Scenarios & Examples

OAT IFR — Ferry / Liaison Flight & Radar Corridors

Route Example: CGY LICHFIELD RC LFA7 STAY1/0015 DCT CGY

OAT VFR — Low-Level Navigation & Low-Flying Areas (LFA)

Route Example: CGY/MID07S LICHFIELD RC LFA7 STAY1/0020 DCT LCH RC DCT CGY

Remarks Example: STAYINFO1/LFA7 LOWAT DELAY 0020

Air Refueling (AAR) & Danger Areas

Route Example: BZN DCT DAVENTRY RC DCT AARA8 STAY1/0030 DCT DAVENTRY RC DCT BZN

Remarks Example: STAYINFO1/AARAS AAR MARSA/NATO11/ DELAY 0030 1200 TO 1230

Comprehensive Parameter Glossary & Operational Index

An exhaustive technical reference detailing every configuration parameter, input field, and flight plan variable supported across the Virtual NATO Flight Planning Suite.

1. General & Flight Identification

Jurisdiction / Country Standard (`countrySelect`)

Descriptor: National regulatory authority & OAT convention selector.
Description: Automatically configures prefix rules, airway routing logic, and remark structures for France (DGAC/DIRCAM), Germany (BMVg/Luftwaffe), or United Kingdom (RAF/MilAIP).

Generator Mode (`fpl-mode-select`)

Descriptor: Operational output profile switcher.
Description: Switches between building individual SWIFT route strings, standalone Item 18 remark blocks, or the complete standalone vxPILOT ICAO flight plan string.

Date of Flight (`dof`)

Descriptor: Flight departure date stamp.
Description: Formatted in standard 6-digit YYMMDD configuration (e.g., 260826) for network coordination.

Callsign (`fplCallsign`)

Descriptor: Radiotelephony tactical callsign.
Description: Official unit callsign assigned for the sortie (e.g., NATO01, BAROK31) mapped directly into the FPL header.

Aircraft ICAO Type (`fplAcftType`)

Descriptor: Standard 2 to 4-character aircraft designator.
Description: Identifies the airframe type for performance and wake tracking (e.g., C17, FA18, A400).

2. Flight Rules, Speeds & Aerodromes

Flight Rules (`rules / icaoRules`)

Descriptor: Air traffic service rules framework.
Description: I (IFR), V (VFR), T (OAT Tactical), Y (IFR then VFR), Z (VFR then IFR). Note: Automatically maps tactical 'T' rules to safe 'I' fallbacks for VATSIM pre-file compatibility.

Type of Flight (`type`)

Descriptor: General operations category indicator.
Description: M (Military), S (Scheduled), N (Non-scheduled), G (General Aviation), X (Special operations).

Speed & Altitude Units (`spdUnit / altUnit`)

Descriptor: Cruising performance metrics.
Description: Speed identifiers (N Knots, M Mach, K Km/h) paired with numerical values, and level type indicators (F Flight Level, A Altitude in hundreds of feet, S Metric tens of meters).

Departure, Arrival & Alternate Aerodromes (`fplDep / fplArr / fplAlt`)

Descriptor: 4-letter ICAO aerodrome designators.
Description: Specifies departure point alongside Estimated Off-Block Time (EOBT), destination with Estimated Elapsed Time (EET), and optional alternate airfields.

3. Routing & OAT Transfer Architecture

Transfer Points & Route Types (`gatToOat / oatToGat / vfrTrans / ifrTrans`)

Descriptor: Airspace boundary transition fixes.
Description: Transition fixes where flights switch between GAT and OAT rules. Automatically strips trailing slashes to enforce clean space-separated formats (e.g., LMG OAT V N0240A010).

STAY Working Segments & Target WPTs (`staySeg / stayDur / stayWpt`)

Descriptor: Tactical orbit and delay block injection.
Description: Target waypoints paired with working blocks (STAY1, STAY2, STAY3) and delay durations in HHMM format. Dynamically hunts for the target waypoint in the route string and injects the delay block directly beside it.

Route Details / Fixes (`route / icaoRoute`)

Descriptor: Chronological waypoint string.
Description: Sequence of direct routing nodes, radar corridors, and navigation fixes separated by single spaces.

4. Item 18 & Remarks Parameters

Wake Turbulence Category (`wake / icaoWake`)

Descriptor: Maximum certificated takeoff mass classification.
Description: J (Super), H (Heavy, 136t+), M (Medium), L (Light). Automatically populates Item 9 formatting.

Equipment & Transponder IFF (`equip / trans`)

Descriptor: Field 10a avionics and Field 10b surveillance suite.
Description: Radio/navigation configuration codes (e.g., SDE3G, SDT) and military transponder modes (C, S, H, E, L, B1, B2) cleanly separated into Item 9/10 without remark syntax corruption.

PBN Performance-Based Navigation (`pbnValue`)

Descriptor: RNAV/RNP approval qualifiers.
Description: Multi-selected navigation specifications concatenated automatically without spaces (e.g., PBN/B2S1).

NAV & STS Special Handling (`nav / sts`)

Descriptor: Navigation augmentation and ATC priority indicators.
Description: Secondary navigation specs (e.g., TACAN, INS) and mandatory priority tags such as STATE, MARSA, or SAR.

Supplementary Item 18 Fields (`sel / sur / per / orgn / com / reg / opr`)

Descriptor: Tactical dispatch and avionics telemetry codes.
Description: Includes selective calling (SEL/), surveillance datalinks (SUR/), aircraft performance data (PER/), originator dispatch addresses (ORGN/), communications suites (COM/), military tail numbers (REG/), and squadron/unit operators (OPR/).

Fuel Endurance & EET (`fuelEnd / eet`)

Descriptor: Total fuel capacity and FIR boundary estimates.
Description: Total fuel endurance in HHMM format appended cleanly as -E/HHMM, alongside FIR estimated elapsed times.

STAYINFO, RMK & Organization Tags (`stayinfo / rmkOat / vso`)

Descriptor: Exercise descriptions and organizational metadata.
Description: Working area notes mapped to STAYINFO1/, regulatory operational air traffic tags (RMK/OAT), organization signatures (VIRTUALNATO.ORG), and optional student pilot designators (VSO TRAINEE).

Operational Disclaimer: This software and manual are proprietary assets of Virtual NATO (re-established in 2017) and are designed exclusively for simulated virtual aviation environments (such as VATSIM). Distribution outside Virtual NATO or without express authorization from vCMC & vDCMC is strictly prohibited. This tool must never be used for real-world flight planning, navigation, or operational dispatch.

Equipment, Transponder & PBN Reference Guide

Detailed breakdown of ICAO Field 10 communication/navigation equipment, surveillance transponder codes, and Performance-Based Navigation (PBN) specifications utilized in military flight planning.

1. Field 10a: Radio Communication, Navigation & Approach Aid Equipment

Code	Configuration / Suite Description
S	Standard equipment (VHF RTF, VOR, and ILS capability).
SD	Standard + DME (Distance Measuring Equipment).
SDT	Standard + DME + TACAN (Tactical Air Navigation system equipped). Essential for military tactical flights.
SDE3	Standard + DME + RNAV (Area Navigation via approved sensors).
SDE3G	Standard + DME + RNAV + GNSS (Global Navigation Satellite System / GPS integration).
SDE3GI	Standard + DME + RNAV + GPS + INS (Inertial Navigation System augmentation).
SDE3GHI	Advanced Military Suite incorporating full GPS, INS, and high-integrity tactical navigation data links.

2. Field 10b: Surveillance Equipment & Transponder Codes

Code	Surveillance & Transponder Capabilities
N	No transponder equipment installed or operational.
A	Mode A only (4-digit identity code, no pressure-altitude reporting).
C	Mode A and Mode C (Identity code plus pressure-altitude reporting).
E	Mode S including aircraft identification, pressure-altitude, and extended squitter (ADS-B) capability.
S	Mode S including both pressure-altitude and aircraft identification capability.
L	Full Mode S suite: aircraft ID, pressure-altitude, ADS-B extended squitter, and enhanced surveillance capability.

3. Performance-Based Navigation (PBN) Specifications

PBN qualifiers define authorized RNAV and RNP navigation standards. Multiple selected capabilities are concatenated directly into Item 18 without spaces (e.g., PBN/B2S1).

RNAV Specifications (Enroute & Terminal):
- A1: RNAV 10 (RNP 10) oceanic/remote operations.
- B1 - B5: RNAV 5 operations utilizing all sensors, GNSS, DME/DME, VOR/DME, or INS/IRS.
- C1 - C4: RNAV 2 precision operations.
- D1 - D4: RNAV 1 high-density terminal operations.
RNP Specifications (Advanced Performance):
- L1: RNP 4 oceanic/remote monitoring.
- O1 - O4: RNP 1 Basic area navigation and radius-to-fix capability.
- S1: RNP APCH (Standard approach capability).
- S2: RNP APCH with BARO-NAV vertical guidance.
- T1 / T2: RNP Authorization Required (AR) APCH with or without RF turns.

METAR Decoding & Reading Guide

Meteorological Aerodrome Reports (METAR) follow a strict sequential format governed by international WMO/ICAO standards. Use this operational reference guide and descriptor tables to decode weather observations rapidly during flight planning.

Anatomy of a Standard METAR String

LFBO 141730Z 24015G25KT 9999 -RA FEW025 SCT042CB 18/12 Q1013 NOSIG

Station Identifier: 4-letter ICAO code indicating the reporting aerodrome (e.g., LFBO).
Date & Time Stamp: Day of the month and Zulu time in hours/minutes followed by 'Z' (e.g., 141730Z).
Wind Vector: True wind direction in degrees and speed in knots, including gust peaks if applicable (e.g., 24015G25KT). Variable ranges indicated with 'V' (e.g., 210V270).
Visibility: Prevailing horizontal visibility in meters (e.g., 9999 for 10km or more). Statute miles or fractions may appear in North American reports (e.g., 1 1/2SM).
Runway Visual Range (RVR): Touchdown zone visibility along active runways (e.g., R27L/1400FT).
Weather Phenomena: Combinations of intensity, descriptors, and phenomena types (e.g., -RA light rain, TSRA thunderstorm with rain).
Sky Condition / Cloud Cover: Cloud coverage layer and base height in hundreds of feet AGL (e.g., FEW025 few at 2,500ft, SCT042CB scattered cumulonimbus at 4,200ft).
Temperature / Dew Point: Ambient air temperature and dew point in degrees Celsius separated by a slash (e.g., 18/12). Negative values prefixed with M.
Altimeter Setting: Atmospheric pressure report. QNH millibars prefixed with Q in Europe (e.g., Q1013) or inches of mercury with A in North America (e.g., A2992).
Recent Weather & Trends: Optional supplemental remarks or landing forecasts (e.g., NOSIG - no significant change expected).

Weather Descriptors & Phenomena Matrix

Code	Category	Meaning / Description
- / +	Intensity	Light (-) or Heavy (+) intensity modifier (moderate has no sign).
VC	Proximity	In the Vicinity (observed between 5 and 10 statute miles of the aerodrome).
MI / PR / BC	Descriptor	Shallow (MI), Partial (PR), or Patches (BC) of fog or mist.
BL / DR / SH	Descriptor	Blowing (BL), Low Drifting (DR), or Showers (SH).
TS / FZ	Descriptor	Thunderstorm (TS) or Freezing (FZ) conditions.
RA / SN / DZ	Precipitation	Rain (RA), Snow (SN), or Drizzle (DZ).
SG / IC / PL	Precipitation	Snow Grains (SG), Ice Crystals (IC), or Ice Pellets (PL).
GR / GS / UP	Precipitation	Hail (GR), Small Hail/Snow Pellets (GS), or Unknown Precipitation (UP).
BR / FG / FU	Obscuration	Mist (BR), Fog (FG), or Smoke (FU).
VA / DU / SA / HZ	Obscuration	Volcanic Ash (VA), Widespread Dust (DU), Sand (SA), or Haze (HZ).
SQ / PO / FC	Other	Squalls (SQ), Dust/Sand whirls (PO), or Funnel Cloud / Tornado / Waterspout (FC).

Sky Coverage & Vertical Limits

SKC / CLR: Sky Clear (0 oktas)

FEW: Few clouds (1 to 2 oktas)

SCT: Scattered (3 to 4 oktas)

BKN: Broken (5 to 7 oktas)

OVC: Overcast (8 oktas)

VV: Indefinite Ceiling / Vertical Visibility

Operational Disclaimer: This software and manual are proprietary assets of Virtual NATO (re-established in 2017) and are designed exclusively for simulated virtual aviation environments (such as VATSIM). Distribution outside Virtual NATO or without express authorization from vCMC & vDCMC is strictly prohibited. This tool must never be used for real-world flight planning, navigation, or operational dispatch.

Terminal Aerodrome Forecast (TAF) Decoding Guide

Terminal Aerodrome Forecasts (TAF) provide expected meteorological conditions at an aerodrome over a specific 24- or 30-hour validity period.

Anatomy of a Standard TAF String

TAF LFBO 141700Z 1418/1518 24015G25KT 9999 -RA FEW025 SCT042CB BECMG 1502/1504 20010KT

Report Type: TAF (routine forecast) or TAF AMD (amended forecast).
Station Identifier: 4-letter ICAO aerodrome designator (e.g., LFBO).
Issuance Time Stamp: Day of the month and Zulu time when the forecast was generated (e.g., 141700Z).
Validity Period: Start day and hours through end day and hours in UTC (e.g., 1418/1518 means valid from the 18th hour of the 14th to the 18th hour of the 15th).
Forecast Wind: Mean predicted wind direction in degrees true and speed in knots, including gusts (e.g., 24015G25KT).
Forecast Visibility: Prevailing horizontal visibility in meters (e.g., 9999 for 10km or greater).
Weather Phenomena: Expected precipitation or obscurations (e.g., -RA light rain).
Cloud Layers: Forecast cloud coverage and base heights (e.g., FEW025 SCT042CB).
Change Groups: Subsequent expected weather transitions indicated by timing and trend codes (e.g., BECMG, TEMPO, FM).

TAF Change & Trend Indicators

Code	Indicator Type	Operational Meaning
FM	From	Rapid and permanent change occurring at a specific exact hour/minute (e.g., `FM142030`). Erases all previous conditions.
BECMG	Becoming	Gradual transition of conditions taking place evenly over a specified time window (e.g., `BECMG 1502/1504`).
TEMPO	Temporary	Temporary fluctuations expected to last for less than an hour at a time and covering less than half the period.
PROB30 / PROB40	Probability	30% or 40% probability of occurrence for specific thunderstorm or weather phenomena.

Operational Disclaimer: This software and manual are proprietary assets of Virtual NATO (re-established in 2017) and are designed exclusively for simulated virtual aviation environments (such as VATSIM). Distribution outside Virtual NATO or without express authorization from vCMC & vDCMC is strictly prohibited. This tool must never be used for real-world flight planning, navigation, or operational dispatch.

Automatic Flight Export Log Guide

The Automatic Flight Export Log is an integrated tracking feature designed to capture, archive, and export generated ICAO flight plans directly within your browser workspace.

1. Operational Workflow

Whenever you generate an ICAO flight plan string under the VATSIM - IMPORT ICAO FPL tab and click the Copy button, the suite automatically captures and records a structured log entry into the export archive box without requiring extra steps.

2. Log Entry Formatting & Metadata

Each logged entry includes:

Export Timestamp: Precise UTC date and time when the copy action occurred.
Date of Flight (DOF): The departure date stamp specified in the flight plan form (formatted in YYMMDD).
Flight Plan String: The exact generated ICAO string copied to your clipboard.

3. Log Management Actions

You can manage your flight records directly from the log panel controls:

Download Log File: Exports your entire session log archive as a text file named vnato_flight_export_log.txt for record-keeping or operational debriefs.
Clear Log: Wipes the active browser text buffer after confirmation to start a fresh sequence.

Virtual NATO Flight Planning Suite

METAR Reports

Terminal Aerodrome Forecast (TAF)

Decoded Weather Parameters

🌐 Oceanic Report — Version 1.1

Descent Profile Parameters

Calculated Descent Metrics

Runway & Wind Parameters

Crosswind & Headwind Breakdown

Leg Distance & Burn Parameters

Estimated Time Enroute & Fuel Required

Aerodrome Environment Parameters

Calculated Performance Index

Virtual NATO Flight Planning Suite

Quick System Overview

Quick Navigation

ICAO Flight Planning

Layer Verification Before Generation

Items 7–10

Item 13 / 16

Item 15

Item 18

Item 19

Preflight

Speed & Level Formats

Recommended Workflow

Weather Guide

METAR

TAF

WX Brief Tool

Fast Reading Order

Oceanic Operations Guide

Quick Start

How Fixes Are Resolved

Coordinate Fix

AIRAC / Named Fix

Custom vNATO Fix

Navdata

Live Tracking State

Position Report Logic

ACTUAL crossing

ESTIMATED next fix

Why Hasn't My Fix Advanced?

Operational Reference

Parameter Glossary

Equipment & PBN

Common ICAO Tokens

VATSIM Compatibility

Best Tester Report

1. Introduction & Regulatory Context

2. Country-Specific Routing & Remark Standards

3. Route Construction & Formatting Rules

4. Tactical Flight Scenarios & Examples

OAT IFR — Ferry / Liaison Flight & Radar Corridors

OAT VFR — Low-Level Navigation & Low-Flying Areas (LFA)

Air Refueling (AAR) & Danger Areas

Comprehensive Parameter Glossary & Operational Index

1. General & Flight Identification

Jurisdiction / Country Standard (countrySelect)

Generator Mode (fpl-mode-select)

Date of Flight (dof)

Callsign (fplCallsign)

Aircraft ICAO Type (fplAcftType)

2. Flight Rules, Speeds & Aerodromes

Flight Rules (rules / icaoRules)

Type of Flight (type)

Speed & Altitude Units (spdUnit / altUnit)

Departure, Arrival & Alternate Aerodromes (fplDep / fplArr / fplAlt)

3. Routing & OAT Transfer Architecture

Transfer Points & Route Types (gatToOat / oatToGat / vfrTrans / ifrTrans)

STAY Working Segments & Target WPTs (staySeg / stayDur / stayWpt)

Route Details / Fixes (route / icaoRoute)

4. Item 18 & Remarks Parameters

Wake Turbulence Category (wake / icaoWake)

Equipment & Transponder IFF (equip / trans)

PBN Performance-Based Navigation (pbnValue)

NAV & STS Special Handling (nav / sts)

Supplementary Item 18 Fields (sel / sur / per / orgn / com / reg / opr)

Fuel Endurance & EET (fuelEnd / eet)

STAYINFO, RMK & Organization Tags (stayinfo / rmkOat / vso)

Jurisdiction / Country Standard (`countrySelect`)

Generator Mode (`fpl-mode-select`)

Date of Flight (`dof`)

Callsign (`fplCallsign`)

Aircraft ICAO Type (`fplAcftType`)

Flight Rules (`rules / icaoRules`)

Type of Flight (`type`)

Speed & Altitude Units (`spdUnit / altUnit`)

Departure, Arrival & Alternate Aerodromes (`fplDep / fplArr / fplAlt`)

Transfer Points & Route Types (`gatToOat / oatToGat / vfrTrans / ifrTrans`)

STAY Working Segments & Target WPTs (`staySeg / stayDur / stayWpt`)

Route Details / Fixes (`route / icaoRoute`)

Wake Turbulence Category (`wake / icaoWake`)

Equipment & Transponder IFF (`equip / trans`)

PBN Performance-Based Navigation (`pbnValue`)

NAV & STS Special Handling (`nav / sts`)

Supplementary Item 18 Fields (`sel / sur / per / orgn / com / reg / opr`)

Fuel Endurance & EET (`fuelEnd / eet`)

STAYINFO, RMK & Organization Tags (`stayinfo / rmkOat / vso`)