1. REQUIREMENT FOR THE SUBMISSION OF A FLIGHT PLAN
1.1 i Operators of all flights within the Muscat FIR are required to submit a flight plan;
2. OPERATION OF REPETITIVE FLIGHT PLAN (RPL)
RPLs are not accepted and all operators are required to file a full flight plan in accordance with ENR 1.10.
3. CHANGES TO THE SUBMITTED FLIGHT PLAN
3.1 All changes to a flight plan submitted for an IFR flight or a controlled VFR flight and significant changes to a flight plan submitted for an uncontrolled VFR flight shall be reported as soon as possible to the appropriate ATS unit. In the event of a delay in departure of 30 minutes or more for a flight for which a flight plan has been submitted, the flight plan shall be amended or a new flight plan shall be submitted after the old plan has been canceled. It is imperative that standard ICAO CHG, DLA, CNL protocols are used.
4. FLIGHT PLAN
4.1 Flight Plan Form
5. RNAV OPERATIONS
For Flight Planning purposes all RNAV 5 operators will also be permitted to file Flight Plans routing via all new RNAV 1 routes within the Muscat FIR.
6. INSTRUCTIONS FOR COMPLETING ICAO FLIGHT PLAN FORM
6.1 Record flight plan data on ICAO Flight Plan Form (see page ENR 1.10-21). Adhere closely to the prescribed formats and manner of specifying data.
A |
GBAS landing system |
B |
LPV (APV with SBAS) |
C |
LORAN C |
D |
DME |
E1 |
FMC WPR ACARS |
E2 |
D-FIS ACARS |
E3 |
PDC ACARS |
F |
ADF |
G |
GNSS (See Note 2) |
H |
HF RTF |
I |
Inertial Navigation |
J1 |
CPDLC ATN VDL Mode 2 (See Note 3) |
J2 |
CPDLC FANS 1/A HFDL |
J3 |
CPDLC FANS 1/A VDL Mode 4 |
J4 |
CPDLC FANS 1/A VDL Mode 2 |
J5 |
CPDLC FANS 1/A SATCOM (INMARSAT) |
J6 |
CPDLC FANS 1/A SATCOM (MTSAT) |
J7 |
CPDLC FANS 1/A SATCOM (Iridium) |
K |
MLS |
L |
ILS |
M1 |
ATC SATVOICE (INMARSAT) |
M2 |
ATC SATVOICE (MTSAT) |
M3 |
ATC SATVOICE (Iridium) |
O |
VOR |
P1 |
CPDLC RCP 400 (See Note 7) |
P2 |
CPDLC RCP 240 (See Note 7) |
P3 |
SATVOICE RCP 400 (See Note 7) |
P4-P9 |
Reserved for RCP |
R |
PBN approved (See Note 4) |
T |
TACAN |
U |
UHF RTF |
V |
VHF RTF |
W |
RVSM approved |
X |
MNPS approved |
Y |
VHF with 8.33 KHz channel spacing capability |
Z |
Other equipment carried or other capabilities (See Note 5) |
ALTRV |
for a flight operated in accordance with an altitude reservation; |
ATFMX |
for a flight approved for exemption from ATFM measures by the appropriate ATS authority; |
FFR |
fire-fighting |
FLTCK |
flight check for calibration of navaids; |
HAZMAT |
for a flight carrying hazardous material; |
HEAD |
a flight with Head of State status; |
HOSP |
for a medical flight declared by medical authorities; |
HUM |
for a flight operating on a humanitarian mission; |
MARSA |
for a flight for which a military entity assumes responsibility for separation of military aircraft; |
MEDEVAC |
for a life critical medical emergency evacuation; |
NONRVSM |
for a non-RVSM capable flight intending to operate in RVSM airspace; |
SAR |
for a flight engaged in a search and rescue mission; and |
STATE |
for a flight engaged in military, customs or police services. |
RNAV SPECIFICATIONS | |
---|---|
A1 |
RNAV 10 (RNP 10) |
B1 |
RNAV 5 all permitted sensors |
B2 |
RNAV 5 GNSS |
B3 |
RNAV 5 DME/DME |
B4 |
RNAV 5 VOR/DME |
B5 |
RNAV 5 INS or IRS |
B6 |
RNAV 5 LORANC |
C1 |
RNAV 2 all permitted sensors |
C2 |
RNAV 2 GNSS |
C3 |
RNAV 2 DME/DME |
C4 |
RNAV 2 DME/DME/IRU |
D1 |
RNAV 1 all permitted sensors |
D2 |
RNAV 1 GNSS |
D3 |
RNAV 1 DME/DME |
D4 |
RNAV 1 DME/DME/IRU |
RNP SPECIFICATIONS | |
---|---|
L1 |
RNP 4 |
O1 |
Basic RNP 1 all permitted sensors |
O2 |
Basic RNP 1 GNSS |
O3 |
Basic RNP 1 DME/DME |
O4 |
Basic RNP 1 DME/DME/IRU |
S1 |
RNP APCH |
S2 |
RNP APCH with BARO-VNAV |
T1 |
RNP AR APCH with RF (special authorization required) |
T2 |
RNP AR APCH with RF (special authorization required) |