vIAF – SOP

Virtual Israeli Air Force

Document Control

Revision Records

Document Purpose

This document is designed to cover all operational procedures for the Virtual Israeli Air Force (vIAF). It is updated to remain in compliance with the following VATSIM policies: Code of Conduct (CoC) and VATSIM-POL-Special Operations v5.0.

Related Documents

• vIAF Training Policy
• VATSIM Code of Conduct (CoC)
• VATSIM-POL-Special Operations v5.0

General Conduct

All members of vIAF — whether trainees or mission-qualified — are expected to conduct themselves in a manner that does not reflect negatively on the vIAF, VATSIM, or themselves. This applies across all public forums, the VATSIM network, and any associated platforms.

Examples of unacceptable conduct include, but are not limited to:

• Ignoring ATC instructions, calls, or requests.
• Unnecessarily burdening ATC with avoidable or excessive requests.
• Acting with an attitude of superiority toward other members or network users for any reason.
• Flying aircraft for which the pilot has not received vIAF certification.

Failure to comply with these standards may result in disciplinary action, up to and including revocation of vIAF membership. Members are also reminded that three or more consecutive disciplinary issues involving vIAF members within a single calendar year may result in loss of VSOA partnership status for a period of one year, per VATSIM-POL-Special Operations v5.0, section 8.5.

Ranks

The vIAF does not employ a strict hierarchical rank system. Ranks are assigned based on the following conditions:

Note: O-2 rank and the associated Military Pilot Rating (M-Rating) are issued upon successful completion of the Checkride and updated in PRAMS by vIAF management in accordance with VATSIM-POL-Special Operations v5.0, section 7.

Normal vIAF Operations

All flights — unless prior approval has been granted by vIAF management (vIAF-1 / vIAF-2) — must comply with the requirements outlined below.

ACARS / Network

All flights must be flown on the VATSIM network and recorded via SmartCARS with active flight following throughout. Manual PIREP submission is only permitted with Wing Commander approval.

Aircraft Usage

Flights must depart from the approved departure aerodrome (the relevant wing hub or the last arrival airport) and must be flown using an aircraft from the approved vIAF fleet. Pilots may only operate aircraft for which they hold vIAF certification.

Callsign

When flying, the callsign must conform to the following rules:

• Non-mission flights: The callsign shall be IAFXXX (e.g. IAF101).
• Mission / tactical flights: The formation leader or mission control shall select a callsign from the approved list below.

USE FOR SIMULATOR ONLY – ANY CONNECTION BETWEEN THIS DOCUMENT AND REAL FLIGHT OPERATIONS IS ACCIDENTAL.

Aircraft ICAO Codes

The ICAO aircraft type code used when connecting to the VATSIM network and when filing a flight plan must match the selected aircraft.

Flight Plans

A flight plan must be filed with the VATSIM network for every flight. The remarks section (RMK/) must include: visraeliairforce.com. This enables ATC and VATSIM supervisors to identify the pilot as a VSOA member and act accordingly. It is also required per VATSIM-POL-Special Operations v5.0, section 8.5.

• Flight rules: Both IFR and VFR are permitted, subject to prevailing weather conditions. IFR flights require a full route and cruise altitude to be filed. VFR/MVFR navigation may declare route type and include waypoints at the pilot's discretion.
• Callsign in flight plan: Must be IAFXXX or an approved tactical callsign. No other equivalent format is permitted. Training flights conducted by the Hofit will use the callsign ZIPOR.
• Altitude: Standard VFR cruise altitude is 1,000 ft AGL unless amended by ATC or dispatch.
• Wake category & equipment suffix: Must be filed as listed in the table below. Pilots should verify any changes via the ICAO equipment codes reference before each flight.
• Departure / arrival: Required for all flights. For most operations, these will match the approved wing hub.
• Startup / shutdown: Every flight must begin from a ramp or helipad at the selected aerodrome with a cold-and-dark startup. If scenery prevents this, the aircraft may be slewed to position before connecting.
• Communications: vIAF pilots follow the same communication procedures as standard CVFR pilots within the LLLL FIR, and communicate with ATC as required.

USE FOR SIMULATOR ONLY – ANY CONNECTION BETWEEN THIS DOCUMENT AND REAL FLIGHT OPERATIONS IS ACCIDENTAL.

* Pilots must verify equipment suffix codes against current ICAO documentation prior to each flight, as these may change.

Special Operations

As a VATSIM-approved VSOA, the vIAF is authorised to conduct the following special operations in accordance with VATSIM-POL-Special Operations v5.0, section 6. All special operations flights must include the applicable operation type in the flight plan remarks alongside the organisation website.

Authorised Operations & Flight Plan Remarks

As an O-2 (Lt) and above, you are permitted to undertake standard vIAF operations without prior tasking. The full range of special operations activities requires M-Rating (O-2) and may require additional coordination or approval from vIAF management.

Non-VSOA Flights

When a vIAF member flies an aircraft that is not part of the approved vIAF fleet, or outside of their vIAF certification, the following rules apply:

• The pilot must not include visraeliairforce.com in the flight plan remarks, as they are not flying under VSOA status for that sortie.
• The pilot must not use an IAF or approved tactical callsign for that flight.
• No restricted VSOA activities may be conducted during non-VSOA flights, regardless of the pilot's M-Rating status.
• If an M-Rated pilot becomes involved in an intercept during a non-VSOA flight, they must either update their flight plan to VSOA status or restrict themselves to non-M-Rated activities only, per VATSIM-POL-Special Operations v5.0, section 9.4.2.

1. It is strictly forbidden to use information/documents/knowledge that is not publicly available on the internet.
2. All materials used in the VSOA must be fictional and based solely on publicly available information.

Anyone who violates these rules will be permanently removed from the group and reported to the authorities.

All information found in the Virtual Air Force is written as fiction, and any resemblance is purely coincidental.

USE FOR SIMULATOR ONLY – ANY CONNECTION BETWEEN THIS DOCUMENT AND REAL FLIGHT OPERATIONS IS ACCIDENTAL.