Selects national OAT reporting and remark conventions for France (DGAC/DIRCAM), Germany (BMVg/Luftwaffe), or United Kingdom (RAF/MilAIP).
?
Switch between building route strings, constructing custom Item 18 remarks, or compiling the full standalone vPILOT flight plan string.
?
Flight departure date formatted in standard 6-digit YYMMDD format. Double-click to open calendar.
?
I (IFR), V (VFR), T (OAT Tactical), Y (IFR then VFR), Z (VFR then IFR).
?
Indicates the general category of operations. M = Military, S = Scheduled, N = Non-scheduled, G = General Aviation, X = Special.
?
Cruising speed unit and numerical speed value.
?
Cruising altitude unit and value.
?
Defines standard OAT routing templates, air-refueling orbits, or mixed GAT/OAT profile types.
?
Fix and conditional format where flight transitions from General Air Traffic to Operational Air Traffic.
?
Fix where flight transitions back from OAT to GAT reporting standards.
?
Target waypoint, flight rules, and speed/altitude parameters.
?
Target waypoint, flight rules, and speed/altitude parameters.
?
Chronological waypoints, radar corridors, and direct routing segments separated by single spaces.
?
Target waypoint to inject the STAY block, followed by segment and delay duration (HHMM).
?
Optional working area or delay segment 2.
?
Optional working area or delay segment 3.
?
Denotes aircraft wake turbulence classification. J = Super, H = Heavy (136t+), M = Medium, L = Light.
?
Field 10a radio communication, navigation, and approach aid equipment codes.
?
Field 10b surveillance equipment and transponder capability codes.
?
Select multiple Performance Based Navigation codes indicating approved RNAV/RNP navigation specifications. Concatenated without spaces.
?
Additional navigation equipment identifiers or equipment augmentation.
?
Special handling indicators required by air traffic control, such as STATE, NONRVSM, MARSA, or SAR.
?
SELCAL code for selective calling radio systems (e.g., SEL/ABDE).
?
Surveillance equipment capabilities and data link identifiers (e.g., SUR/260B).
?
Select aircraft approach speed category for PER/ remark.
?
Originator address or dispatch identifier for the filed flight plan.
?
Communication capabilities, voice frequencies, or data link apps (e.g., COM/UHF VDL2).
?
Aircraft registration or military tail number identifier (e.g., FA1801).
?
Operator designator or military unit identifier (e.g., FAF, GAF, 29 SQN ROYAL AIR FORCE).
?
Total fuel endurance expressed in hours and minutes (e.g., 0200 for 2 hours).
?
Estimated elapsed time to FIR boundaries or destination waypoints (e.g., ENSAC0030).
?
Detailed description of military exercise or low-flying activity within STAY 1 area.
?
Operational Air Traffic status tag. For France, OAT appears at the beginning of remarks to indicate active OAT phases.
?
Virtual organization identifier tag (e.g., VIRTUALNATO.ORG).
?
I (IFR), V (VFR), Y (IFR then VFR), Z (VFR then IFR). T is available as a vNATO input convenience but the generator maps T to I for the VATSIM ICAO import string; keep OAT status in the route/RMK.
?
M = Military, S = Scheduled, N = Non-scheduled, G = General Aviation, X = Special.
?
Cruising speed unit and numerical value format.
?
Altitude unit and numerical value format.
?
Aircraft radiotelephony callsign (e.g., NATO01).
?
Standard 2 to 4-character ICAO aircraft designator (e.g., FA18, C17).
?
Departure aerodrome ICAO code and Estimated Off-Block Time in UTC.
?
Destination aerodrome ICAO code and Total Estimated Elapsed Time.
?
Alternate destination aerodrome ICAO code if required.
?
Defines standard OAT routing templates, air-refueling orbits, or mixed GAT/OAT profile types.
?
Fix and conditional format where flight transitions from General Air Traffic to Operational Air Traffic.
?
Fix where flight transitions back from OAT to GAT reporting standards.
?
Target waypoint, flight rules, and speed/altitude parameters.
?
Target waypoint, flight rules, and speed/altitude parameters.
?
Chronological waypoints, radar corridors, and direct routing segments separated by single spaces.
?
Working area target waypoint, segment, and delay duration in HHMM.
?
Optional working area or delay segment 2.
?
Optional working area or delay segment 3.
?
Denotes aircraft wake turbulence classification. J = Super, H = Heavy (136t+), M = Medium, L = Light.
?
Enter the exact ICAO Item 10a equipment string when the dropdown does not represent the aircraft. This overrides the dropdown. Example: SDE3R. Capability codes are never added automatically.
?
Select multiple Performance Based Navigation codes indicating approved RNAV/RNP navigation specifications. Concatenated without spaces.
?
Additional navigation equipment identifiers or equipment augmentation.
?
Special handling indicators required by air traffic control, such as STATE, NONRVSM, MARSA, or SAR.
?
SELCAL code for selective calling radio systems (e.g., SEL/ABDE).
?
Surveillance equipment capabilities and data link identifiers (e.g., SUR/260B).
?
Select approach speed category for PER/ remark.
?
Originator address or dispatch identifier for the filed flight plan.
?
Communication capabilities, voice frequencies, or data link apps (e.g., COM/UHF VDL2).
?
Aircraft registration or military tail number identifier (e.g., FA1801).
?
Operator designator or military unit identifier (e.g., FAF).
?
Total fuel endurance expressed in hours and minutes (e.g., 0200).
?
Detailed working area description for military exercises.
?
Regulatory remarks and organization tags.
VATSIM import preflight is ready. Generate the FPL to run structural validation.
Automatically captures exports with timestamp and Date of Flight (DOF) when clicking 'Copy' above.
Enter ICAO code(s) above and click 'Fetch Weather'...
Terminal Aerodrome Forecast (TAF)
Enter ICAO code(s) above and click 'Fetch Weather'...
Decoded Weather Parameters
Click 'Fetch Weather' to generate plain language breakdown...
🌐 Oceanic Report — Version 1.1
V1.1 adds automatic named-fix resolution. Coordinate fixes are decoded directly; named fixes are resolved from a locally imported X-Plane-style waypoint/navaid dataset or from your vNATO custom-fix library. Navigation data stays in your browser and is not included with this suite.
NAVIGATION DATANO DATA
Source—
AIRAC / Version—
Waypoints0
Navaids0
Import a ZIP or Waypoints.txt + Navaids.txt.
Use only navigation data you are licensed or otherwise authorised to process. The vNATO suite does not redistribute third-party navdata.
OFFLINE
LIVE AIRCRAFT
Position—
Altitude—
Groundspeed—
Heading—
Last VATSIM update—
ROUTE / REPORTING POINTSNo route loaded
Load a flight plan to build the Oceanic Report route.
POSITION REPORT
V1.1 notes / limitations
Coordinate fixes such as 454901N0013507E are decoded without navdata.
Named fixes are resolved locally from imported X-Plane-style Waypoints.txt and Navaids.txt data. ZIP import is supported in modern Chromium browsers.
If an identifier has several candidates, the resolver prefers waypoint records and uses surrounding resolved route geometry/current aircraft position to choose the most plausible candidate.
Unknown military/OAT points can be saved as vNATO custom fixes with the Set Fix action; they are retained in this browser.
Live position comes from the public VATSIM Data API and is polled about every 15 seconds. Crossing time is interpolated between consecutive network positions.
Descent Profile Parameters
Calculated Descent Metrics
Altitude to Lose:0 ft
Pure Descent Distance:0.0 NM
Start Descent (Total NM from Fix):0.0 NM
Required Vertical Speed (FPM):0 FPM
Time to Target Alt:0.0 min
Runway & Wind Parameters
Crosswind & Headwind Breakdown
Headwind Component:0 kts
Crosswind Component:0 kts
Wind Angle Offset:0° off runway
Leg Distance & Burn Parameters
Estimated Time Enroute & Fuel Required
Estimated Time Enroute (ETE):00:00 (HH:MM)
Leg Fuel Required:0 lbs
Total with 30m Reserve:0 lbs
Aerodrome Environment Parameters
Calculated Performance Index
Pressure Altitude:0 ft
Density Altitude (DA):0 ft
Estimated Takeoff Roll Increase:+0.0%
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.
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.
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).
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.
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).
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.
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.
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.
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.
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).
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.
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.