Flight Minima
| Aircraft Category | Solo | Close Formation | ||||
|---|---|---|---|---|---|---|
| Level flight | Aerobatics | Outside zone | Level flight | Aerobatics | Outside zone | |
|
Helicopters
|
100 ft | 100 ft | SERA.5005 | 100 ft | 100 ft | SERA.5005 |
|
Propeller aircraft ≤ 1,000 kg
|
100 ft | 100 ft | SERA.5005 | 100 ft | 100 ft | SERA.5005 |
|
Propeller aircraft 1,000–4,000 kg
|
150 ft | 200 ft | SERA.5005 | 150 ft | 300 ft | SERA.5005 |
|
Jets / turboprops > 4,000 kg
|
200 ft | 300 ft | 1,000 ft | 200 ft | 300 ft | 1,000 ft |
|
Gliders
|
100 ft | 150 ft | SERA.5005 | 100 ft | 150 ft | SERA.5005 |
SERA.5005 — Standard VFR rules (150 m / 300 m AGL depending on area). The FDD may raise any minimum due to obstacles or degraded weather conditions. Absolute minimum outside the display zone: 300 ft AGL for all categories.
Mandatory Briefing
Every pilot or display team participating in a VAF event must have received and acknowledged all of the following information before taking off.
Event Identification
- Event name, date and UTC time
- Display site location (airport / DCS map)
- Total programme duration
- Flying Display Director (FDD) contact details
Flight Programme
- Display order for each team and solo performer
- Allocated slot duration per participant
- Entry and exit procedures for the display zone
- Holding procedures while awaiting slot
Radio Procedures (SRS)
- Primary frequency — FDD to pilots
- Secondary / emergency frequency
- Radio call format (callsign + aircraft type)
- Procedure in case of radio failure
DCS Display Zone
- Display line coordinates and orientation
- Crowd line — absolute limit towards spectators
- Minimum altitudes by aircraft category (see minima section)
- Restricted zones and obstacles to avoid
Technical Requirements
- Required DCS World version (stable / open beta)
- Mandatory modules for the event
- Multiplayer server name and password
- Mission file to load before connecting (see Mods page)
Emergencies & STOP Calls
- TOO LOW / TOO CLOSE calls on FDD frequency
- STOP STOP STOP — immediate and final halt of display
- Behaviour after a STOP call (do not resume without authorisation)
- Out-of-server FDD contact (Discord)
Radio Procedures
These procedures apply on the shared SRS server used during VAF events. Join the briefing channel as soon as you connect to the multiplayer server. The FDD is identifiable by the callsign FDD-[EVENT] on the primary frequency.
Standard Radio Calls
Frequencies & Channels
General Rules
Participation Requirements
- 1 Every team or solo pilot must have an accepted application before the closing date.
- 2 Attendance at the pre-event briefing is mandatory (in-person or written via Discord).
- 3 Any pilot who misses the briefing will not be allowed to fly during the event.
- 4 The allocated display slot is personal and non-transferable without prior FDD approval.
- 5 A substitute pilot must be declared to the FDD at least 48 hours before the event.
Aircraft & Modules
- 1 Only official DCS World modules are permitted — no unannounced mods.
- 2 Custom liveries must be submitted for validation at least 2 weeks before the event.
- 3 The aircraft used must match the one declared in the application.
- 4 Any aircraft change after acceptance requires FDD validation.
- 5 Modules in unstable beta may be refused at the FDD's discretion.
Displays & Performance
- 1 The performance must be rehearsed — no improvisation during the airshow.
- 2 Any pass towards the public with a roll axis > 30° is strictly prohibited.
- 3 No aircraft crossings except along the display axis and at a minimum of 450 m.
- 4 Close-formation passes are limited to teams that declared this in their application.
- 5 Overflight of the crowd line is strictly prohibited under any circumstances.
Conduct & Fair Play
- 1 Respectful behaviour towards all participants, staff and spectators at all times.
- 2 Any deliberate attempt to disrupt another team's performance results in immediate exclusion.
- 3 Disputes are submitted to the FDD first, then to VAF organisers as a formal appeal.
- 4 FDD decisions during the event are final and cannot be challenged in the moment.
- 5 Written feedback on the event (positive or negative) is encouraged via the contact form.
Technical Requirements
- 1 Stable internet connection required — repeated disconnections may result in slot removal.
- 2 SimpleRadio Standalone (SRS) is mandatory and must be tested before the briefing.
- 3 The official mission file must be loaded BEFORE connecting to the event server.
- 4 No client-side scripts or mods not validated by the organisation (mission integrity).
- 5 In case of a DCS crash during your slot, report immediately on the FDD frequency.
Sanctions
- 1 Crowd line breach → immediate STOP call and slot suspension.
- 2 Minimum altitude violation without correction → STOP call and written report.
- 3 No response to a TOO LOW or STOP call → exclusion from the current event.
- 4 Hostile behaviour → exclusion and report to VAF organisers.
- 5 Any excluded pilot retains the right to appeal through official channels.
These rules are inspired by OFAC regulations (Directive CMA FS I 001 F), CAA UK (CAP 403) and RA 2335 UK MOD, adapted to the DCS World simulation environment. By participating in a VAF event, every pilot accepts these conditions in full.
Frequently Asked Questions
Can't find what you're looking for? Contact us using the form below.
Contact Us
Ways to Reach Us
contact@virtualairfestivals.com
Discord
Join our community server for instant support
Response Time
We typically respond within 24-48 hours