vIAF – SOP

Revision records [cite: 84]

Document purpose [cite: 85]

This document is designed to cover all operation procedures for the Virtual Israeli Air Force (vIAF). [cite: 86] This document is updated to remain in compliance with VATSIM following policies: CoC, SOA-POL. [cite: 87]

Related Documents [cite: 88]

• vIAF Training policy [cite: 89]
• VATSIM Coc [cite: 90]
• VATSIM SOA-POL [cite: 91]

General conduct [cite: 92]

All members of vIAF either trainee or mission qualified members are expected to behave in manners that doesn't represent the vIAF, VATSIM or themselves in a negative fashion – this includes but not limited to public forums and on vatsim networks. [cite: 93] Example to types of actions like that are: [cite: 94]

• Ignoring ATC instructions calls or requests [cite: 95]
• Making busy ATC more stressful due to unneeded request [cite: 96]
• Acting as a "better member" for any reason. [cite: 97]
• Flying in aircraft that not familiar with flying. [cite: 98]

Failure to follow these requirements can lead to disciplinary action up to and including revocation of membership to the organization [cite: 99]

Ranks [cite: 100]

The vIAF doesn’t employ a strict hierarchical rank system, it is assigned on the following condition: [cite: 101]

Normal vIAF Operations [cite: 103]

All flights – unless prior approval by vIAF managements (1\2\3\4) – must follow the outline below [cite: 104]

• ACARS/Network: The flight must be flown on smartCARS3 and on the VATSIM network. [cite: 105] Manual PIREP submission is only allowed on wing commander approval. [cite: 106]
• Aircraft Usage: The flight must depart from the “approved” departure airport (relevant HUB) or from the last airport and from “approved” fleet [cite: 107]
• Callsign: When flying the callsign must match the ones below [cite: 108] When not flying in mission the callsign should be “IAFXXX” [cite: 109] When flying in mission and a tactical callsign in required the formation leader/mission control shall choose from the ones below: [cite: 110]

Aircraft ICAO Codes: The ICAO aircraft type code when signing in and when filing a flight plan must match the selected aircraft. [cite: 112]

Flight Plans: For any flight must file a flight plan with the vatsim network at all time (Can be filed here) with the remark (RMK/ section) “visraeliairforce.com”. [cite: 114] This ensure that ATC and SUP understand that the pilot is part of VSOA and can act accordingly to that information’s. [cite: 115] It also supports to understand the amount of flights and flight hours in each quarter. [cite: 116]

• Flight rules: IFR and VFR are both permitted subject to weather. [cite: 117] The only main difference between IFR and VFR prefile are the requirement to file route and cruise altitude for IFR flight. [cite: 118] Each pilot must ensure their callsign is IAFXXX/approved tactical callsign and not any other equivalent. [cite: 119]
• Wake category: Info is included on the dropdown, to make the understanding easier the following are the categories by ICAO code. [cite: 120]
• Equipment suffix: based on the navigation equipment you have on the plane to make the understanding easier the following are the suffix by ICAO code: [cite: 121]

*Pilot shall check the https://en.wikipedia.org/wiki/Equipment_codes for any change in the aircraft before flight on briefing [cite: 123]

• The departure and arrival airport are required and for most of the flight and missions will be the same. [cite: 124]
• VFR/SHAKNAI navigation: Shall be declaration of route type, Might include the waypoints themselves IFR: The pilot shall file the full enroute flight path [cite: 125]
• Altitude: normal VFR altitude may be 1000ft, for ATS it may be changed as dispatched. [cite: 126]
• Any other fields: May be filed at pilots/formation leader discretion. [cite: 127]
• Startup/Shutdown: Every flight must start from ramp/helipad at the selected Aerodrome (unless unable due to scenery bugs then procced with cold and dark startup or slew the aircraft to position before connecting) [cite: 128]
• Communications: The vIAF will follow the same procedures as the standard CVFR pilot in LLLL fir and will communicate with ATC as needed (as they are trained in minimal military control and have experience with special civilian traffic). [cite: 129]

Special Operations [cite: 130]

As a VSO approved organization the vIAF is permitted to follow the following operations with the suggested Flight Plan Remarks [cite: 130]

• Medical Rescue Op, VSO - visraeliairforce.com [cite: 131]
• Search and Rescue Op, VSO - visraeliairforce.com [cite: 132]
• Cargo Op, VSO - visraeliairforce.com [cite: 133]
• Intelligence patrol, VSO - visraeliairforce.com [cite: 134]
• Interception Op, VSO - visraeliairforce.com [cite: 135]
• Training, VSO - visraeliairforce.com [cite: 136]
• Repositioning, VSO - visraeliairforce.com [cite: 137]
• Refueling, VSO - visraeliairforce.com etc… [cite: 138]

As an O – 2 (Lt) You are permitted to undertake vIAF standard operations without a task or being tasked [cite: 139] The full range of SOA activities requires further training before you undertake them. [cite: 140]

Non VSOA Flights [cite: 141]

When flying in an aircraft that isn’t in use at vIAF the pilot shall not file the visraeliairforce.com in its remarks as he is not certified by the vIAF for that aircraft [cite: 142]