Document Information
Document Control Details
| Type | Procedure |
| Revision | 01/2025 |
| Effective Date | 04 OCT 2025 |
| Prepared by | Kai Mannion - LEVOPS |
| Approved by | Sebastian Delcroix - ACCLEV3 |
| Next review date | 04 OCT 2026 |
| Cancelled documents |
Record of Revisions
| Revision Number | Notes | Effective Date |
|---|---|---|
| 01/2025 | Initial issue | 04 OCT 2025 |
Purpose & Scope
This Standard Operating Procedure (SOP) outlines the procedures, responsibilities, and coordination requirements for Baghdad (ORBI) aerodrome operations on the VATSIM network. Its primary goal is to ensure safe, efficient, and standardized handling of IFR and VFR traffic flow into and out of the aerodrome.
This document serves as a reference for both newly certified and experienced controllers operating at Baghdad International Airport (ORBI).
While this SOP focuses specifically on aerodrome operations, it complements and should be used in nonjunction with other local SOPs, including Letters of Agreement (LoAs) with adjacent sectors.
Applicability
This SOP is applicable to all VATSIM air traffic controllers operating Baghdad Airport at the aerodrome level, including:
- Baghdad aerodrome controllers.
- Controllers operating in a top-down capacity from a terminal area (APP or DEP) or enroute (CTR) position.
- Visiting controllers approved by the relevant division or vACC.
- Trainees working under supervision within enroute airspace.
All controllers are expected to adhere to the procedures set forth in this document in conjunction with the VATSIM Global Controller Ratings Policy, the VATSIM Code of Conduct, and applicable local policies.
Authority & Oversight
The development, maintenance, and enforcement of this SOP fall under the authority of the ATC Operations Department and the Levant vACC Leadership. Oversight is coordinated in line with regional and divisional policies set by the Middle East & North Africa Division (VATMENA) and the VATSIM Network.
Amendments or updates to this SOP may be issued as needed to reflect procedural changes, software updates, or coordination adjustments with neighboring FIRs. All controllers are responsible for remaining up to date with the latest version of this SOP and any associated supplements or notices.