01 Document control and scope
| Document | VHUF-OM-001, Operations Manual |
| Version | 1.0, 20 November 2026 |
| Owner | VHUF Commander |
| Approved | Hegyi Marcell, VHUF Commander, CID 1689603, 20 November 2026 |
| Review | Every 12 months, after each VSOD audit, and after any change to VATSIM-POL-Special Operations |
| Related | VHUF-SOP-001; Ops Paperwork System; Forms FR and FA; EFT syllabus; VATSIM-POL-Special Operations v5.0 |
The manual applies to every VHUF member. Members read it, and the SOP, before their first VHUF flight and confirm in the Read File. Any member may propose a change in the ops channel; the Commander decides and issues a new version.
Order of precedence: VATSIM Code of Conduct and policies, then ATC instructions, then this manual, then the SOP and course syllabi.
02 Organisation and chain of command
One person may hold several posts while VHUF is small, with one exception: nobody gives a check ride to a student they instructed on that course. The current holder of each post (name or callsign, and CID) is listed on vhuf.hu.
| Post | Reports to | Responsibilities |
|---|---|---|
| Commander | VATSIM VSOD | Final authority; approves documents, mission types and qualifications; VHUF representative on the VSOA Discord; primary VATSIM contact email |
| Deputy Commander | Commander | Acts for the Commander; runs audits and VSOD correspondence |
| Operations Officer | Commander | Schedule, TRA bookings, Flight Authorizations, ATC co-ordination, event orders, activity check |
| Chief Flight Instructor (CFI) | Commander | Courses and syllabi; appoints and checks IPs; training records; PRAMS updates |
| Stan/Eval | Commander | Check rides and exams through Flight Examiners; keeps the Letter of Xs |
| Squadron leaders | Operations Officer | Run Puma, Dongó, Camel and SAC squadrons and the Flight Training Flight; review applications |
| Instructor Pilots (IP) | CFI | Teach and grade training sorties |
| Flight Examiners (FE) | Stan/Eval | Fly stage and end-of-course checks |
| Web and Admin | Deputy Commander | vhuf.hu, public roster, privacy policy, Discord |
03 Membership
3.1 Joining
- Apply. Through "Join us" on vhuf.hu with name, VATSIM CID, simulator and experience.
- Requirements. Active VATSIM account in good standing, pilot rating P0 or higher, working voice, readable English (ATC and documents are in English).
- Assignment. A squadron leader reviews the application and assigns the member to Course 1 or, with prior learning, to a later course.
- Read File. The member reads this manual and the SOP and confirms before the first VHUF flight.
3.2 Staying active
- Active pilot. At least one VHUF flight on VATSIM every 90 days.
- VHUF minimums. At least 8 active members, and at least 10 flights under VHUF callsigns in any 60 days. The Operations Officer checks both monthly from the Flight Log.
- Inactive. A member past 90 days goes to "On hold" and off the public roster until they fly again with an IP.
3.3 Public roster
vhuf.hu shows active pilots only, each with at least the VATSIM CID and the short name VHUF. A real name may replace the CID only with the member's agreement. See the active pilot roster.
3.4 Leaving
A member may leave at any time by telling their squadron leader. They come off the roster and PRAMS within 7 days; training records are kept as in section 9.
04 Network conduct
- Follow the VATSIM Code of Conduct and VATSIM-POL-Special Operations on every flight. A VHUF callsign exempts no one from either.
- ATC instructions come first. If a mission cannot be flown as briefed under ATC's instructions, change the mission, not the instruction.
- Without ATC, use UNICOM 122.800; restricted activities only as SOP section 5 allows for uncontrolled airspace.
- No arguments on frequency or in text; take issues to the squadron leader after the flight.
- Keep Discord and vhuf.hu respectful; moderators remove abusive content.
- Use only licensed or freely distributable aircraft, scenery and documents.
05 Callsigns and flight plans
5.1 Callsigns
Each unit flies under its own callsign, as the real units do. The Operations Officer assigns the number for each flight; a formation shares the callsign word with consecutive numbers (PUMA11, PUMA12). Every VHUF callsign is listed here and on vhuf.hu, and every flight plan carries VHUF.HU in the remarks (5.2), so VSOD can count all of them toward the VSOA activity minimum.
| Unit | Aircraft | Callsign | Example (voice) |
|---|---|---|---|
| 101st Puma Squadron | JAS 39 Gripen C/D | PUMA + number | PUMA11 ("Puma one-one") |
| Dongó Squadron | L-39NG | DONGO or WASP + number | DONGO21 ("Dongo two-one") |
| Camel Squadron | Falcon 7X | FALCON + number | FALCON01 ("Falcon zero-one") |
| Camel Squadron | A319 | CAMEL + number | CAMEL01 ("Camel zero-one") |
| Camel Squadron | KC-390 | ORCA + number | ORCA01 ("Orca zero-one") |
| SAC Heavy Airlift Wing | C-17 | BRK + number | BRK01 |
| Flight Training Flight | Zlin Z-242L / Z-143LSi | Aircraft side number only | 36 ("three-six") |
| Staff and events | Any | VHUF + number | VHUF01 |
| International operations | Any unit | HUF + number | HUF123 |
International operations: every unit uses HUF + number on flights that leave Hungarian airspace; the unit callsign is used for domestic flights.
Check before first use that VATSIM accepts the chosen callsign; if a number-only Zlin callsign is refused, ops assigns an alternative and records it here.
5.2 Flight plan remarks
Every VHUF flight plan carries: RMK/VHUF.HU VSOA <mission code> <FA number>
Example: RMK/VHUF.HU VSOA TRG FA-26-021 (mission codes: SOP 4.1)
While VSOD reviews the VHUF application, add UNDER VSOD REVIEW and fly no restricted activity. Pilots flying under an exemption add the exemption text VSOD gives, with the VHUF URL.
06 Flight operations
6.1 Request and authorization
| Step | Document | Who | When |
|---|---|---|---|
| Request | Form FR, Flight Request (FR-YY-###) | Pilot | At least 48 h before |
| Schedule | Ops Log, Schedule tab | Operations Officer | On receipt |
| Authorization | Form FA, Flight Authorization (FA-YY-###) | Ops supervisor | Before the brief |
| Record | Ops Log, Flight Log tab; gradesheet | IP or flight lead | Same day |
No FA number, no flight. Requests under 48 hours need the Operations Officer's approval on the FA.
6.2 Qualification and currency
- Qualification. A pilot flies only mission types they are qualified for (SOP 4.1), as shown in the Letter of Xs.
- Currency (VHUF rule). A landing in the last 30 days, and an instrument approach in the last 60 days once the pilot has flown one. Not current means a dual sortie with an IP before any solo, check or event sortie. The Ops Log Currency tab shows status automatically.
6.3 Weather (VHUF values)
| Sortie | Minimum (simulator weather) |
|---|---|
| Student solo, visual | Ceiling 2,000 ft, visibility 8 km, crosswind within the type limit |
| Dual visual training | Ceiling 1,500 ft, visibility 5 km |
| Instrument training | Published approach minima at destination, and an alternate available |
| Formation | Students: ceiling 3,000 ft, visibility 8 km. Qualified pilots: published minima |
Pilots use live VATSIM weather unless the brief says otherwise.
6.4 Risk assessment
The FA scores five factors 1-3 each. Total 5-8 Low: ops supervisor approves. 9-11 Medium: squadron leader or CFI. 12-15 High: Commander only, or cancel.
6.5 Airspace and ATC
- TRAs and other special use airspace are booked in the Schedule and used only when released by the controlling ATC unit, under any agreement VHUF holds with VATSIM Hungary. With no ATC online they may be used as SOP section 5 allows; if ATC comes online, leave the area until released.
- The Operations Officer tells VATSIM Hungary in advance of each event and TRA booking.
- Any special use airspace agreement is reported to the VATSIM VP Virtual Airlines and Special Operations (policy 9.5).
6.6 Formation
- Maximum 4 aircraft. The flight lead holds formation lead qualification; students fly only as wingman with an IP in the formation.
- Each pilot files a flight plan; the lead does the radio work; remarks name the formation, e.g.
FORM 2 ACFT LEAD PUMA11. - Join-up and break-up are briefed and flown clear of other traffic.
6.7 Intercepts
Only under SOP section 5: pre-briefed VSOA participants, or the ATC-initiated three-party process where ATC, interceptor and interceptee all agree before any manoeuvre. Never against an uninvolved user.
6.8 Emergencies and incidents
- Simulated emergencies only with ATC's agreement or with no ATC online, and never on a busy frequency.
- A real problem (simulator crash, lost connection) is reported to ATC by text if possible, and to the flight lead afterwards.
- Any incident involving another network user is reported to the Operations Officer the same day.
6.9 Cancelling
The ops supervisor, IP, flight lead or pilot may cancel at any time for weather, risk, ATC workload or doubt. A cancellation is never held against the pilot; set the Schedule status to Cancelled or Weather.
07 Events
- Annual event. At least one public flight event every calendar year (policy 8.3), promoted on my.vatsim.net events, the VATSIM forums and social media. Co-sponsored with VATSIM Hungary where possible.
- Event order. For every event: date and times (UTC), participants with CIDs and callsigns, aircraft, route and airspace, ATC co-ordination, frequencies, brief time, mission codes, and the person in charge. Issued by the Operations Officer at least 7 days before.
- Joint events with other VSOAs. Event order agreed and signed by both organisations.
- Post Event Report. Filed within 14 days (VHUF value): participants and CIDs, flights flown, ATC involved, what went well, problems and lessons, screenshots. Sent to VSOD and kept for audit.
08 Training and ratings
8.1 Courses
Course 1 (EFT, Zlin) is approved. Courses 2F, 3F, 2A and 3A are built and approved one at a time (SOP 4.2). Every course the CFI approves meets policy 8.6:
- Hours. At least 10 hours of instruction: approved materials, knowledge tests, instructor-student time, flight time and check rides.
- Syllabus. Lists every activity and its time.
- Media. Never purely verbal: briefing decks, PDFs, charts.
- Lessons. Each has an objective, content and evaluation criteria tied to this manual and the SOP.
- Records. Kept and shown to VSOD on request (section 9).
8.2 Instructors and examiners
- IP. Holds the qualification they teach, recommended by a squadron leader, completes an IP upgrade check with the CFI, appointed in the Letter of Xs.
- FE. An experienced IP appointed by Stan/Eval; never examines their own student on the same course.
8.3 M-ratings and PRAMS
The CFI updates PRAMS when a pilot completes mission-ready training as defined in the VSOD M-Rating Policy Manual, and when a pilot leaves VHUF. Pilots in several VSOAs track their own M-ratings and tell each VSOA.
8.4 Prior learning
Pilots certified in another approved VSOA may be fast-tracked. Recognition of prior learning is decided by the CFI case by case, normally an evaluation sortie with an FE. Military pilot ratings transfer between VSOAs.
09 Records, audits and data protection
| Record | Where | Kept |
|---|---|---|
| Roster, Schedule, Flight Log, Logbook, Currency | VHUF Ops Log | Permanently while VHUF exists |
| Forms FR and FA | Ops channel or shared drive, named FR-26-014_PUMA11.pdf | 2 years |
| Gradesheets, check results, Form 8, exams | Training records, per pilot | Membership plus 2 years |
| Letter of Xs, Read File confirmations | Ops Log | Current plus previous version |
| Event orders, Post Event Reports | Ops channel or shared drive | 3 years |
Retention periods are VHUF values.
Audits
VSOD audits VHUF at least once a year and may audit at any time. The Deputy Commander provides requested information within 10 days and corrects any finding within 7 days of feedback.
Data protection (GDPR)
VHUF stores only: name, VATSIM CID, Discord name, email, simulator, and flight and training records. The privacy policy says what is stored, why, for how long and how to ask for deletion. A member may ask to have their data deleted at any time; records VSOD needs for an audit are anonymised instead of deleted.
10 Discipline
Partnership is a privilege. Under VATSIM policy, three or more consecutive disciplinary issues involving VHUF members in one calendar year cost VHUF its partnership for one year. VHUF therefore acts early:
- Verbal warning. By the squadron leader, recorded.
- Written warning. By the Commander; restricted activities suspended for 30 days.
- Suspension. From VHUF flying for up to 90 days.
- Removal. From VHUF, roster and PRAMS.
Any VATSIM supervisor action against a member during a VHUF flight is reported to the Commander at once. Serious cases may go straight to suspension or removal.