En-route Airspace & Airways
FIRs, sectors and the airway network, and reading flight plans as an area controller.
Area control – "Centre" or "Control" on the radio – looks after aircraft between the terminal areas: climbing out of one TMA, cruising along the airways and descending into the next. Your airspace is large, your traffic is fast, and your decisions are made minutes ahead. This lesson covers the structure you work in.
1. FIRs, UIRs and sectors
- An FIR (Flight Information Region) is the area one state provides air traffic services in. The Levant region: Amman FIR (OJAC), Damascus FIR (OSTT), Beirut FIR (OLBB) and Baghdad FIR (ORBB), with Jeddah (OEJD), Cairo (HECC), Ankara (LTAA) and Tehran (OIIX) around them.
- Some states split the upper part into a UIR; in practice the same centre controls both.
- Each FIR is divided into sectors, vertically (lower and upper) and laterally. On IVAO a single controller often covers the whole FIR, top-down to the ground where no lower position is open.
2. The airway network
Airways are corridors of controlled airspace between navigation points, typically 10 NM wide, named with a letter and number:
- Conventional airways between VORs and NDBs – e.g. UL, UM, UR routes in the upper airspace.
- RNAV routes between waypoints defined by coordinates, flown with GPS/FMS.
- Free route airspace in some FIRs: aircraft fly direct between entry and exit points.
Each airway segment has a minimum en-route altitude and, often, a direction or level restriction. Your sector file shows them; the en-route charts explain them.
3. Reading a flight plan as a centre controller
From the ICAO flight plan you need:
- Aircraft type and wake category (field 9): performance and speed.
- Equipment (field 10):
W= RVSM approved,R= PBN, transponder capabilities. - Cruising speed and level (field 15), and the route: SID, airways, waypoints, STAR.
- Remarks (field 18): e.g.
RMK/IVAOVA/LVTfor Levant flights, PBN codes, registration.
Check the route is valid and the requested level is right for the direction. A mistake caught on the ground saves a reroute in the air.
4. The flight strip and your plan
For each aircraft entering your sector you should know: where it enters, at what level, where it leaves, and what level it must be at when it leaves. Write it down (strip or label) – your whole job is to get every aircraft from its entry condition to its exit condition, safely separated from all the others.
5. Climbs and descents in your airspace
- Departures come from Approach climbing to an agreed level; you climb them to their cruising level as traffic allows.
- Arrivals leave your airspace descending to the agreed level for the next approach – plan their top of descent early (roughly 3 NM per 1,000 ft for a jet: from FL370 to FL120 needs about 75 NM).
- Overflights simply cross at cruise – your main task is crossing conflicts.
6. Direct routings
The most appreciated words in the sky: "Levant two one eight, proceed direct DAKAP." A direct saves time and fuel, but check it doesn't take the aircraft out of controlled airspace, through a restricted area or into a conflict.
Controlling it at Levant
Levant flights often cross several FIRs in one trip – Amman, Damascus, Beirut, Baghdad, then on to Europe or the Gulf. As an Amman or Baghdad centre controller you will see long-haul Levant traffic at cruise; a smooth climb, an early direct and a well-planned descent make their flight.
Check yourself
- Give the ICAO codes of the Amman, Damascus, Beirut and Baghdad FIRs. OJAC, OSTT, OLBB, ORBB.
- Which flight plan letter shows an aircraft is RVSM approved? "W" in field 10.
- About how far before the boundary must a jet at FL370 start down to cross it at FL120? About 75 NM (25 × 3).
- What two things do you know for every aircraft in your sector? Its entry and exit conditions (point and level).
Simulation training material. Airway names, waypoints and agreed levels are examples: use the current IVAO division sector files and letters of agreement.