Skip to main content

General

ValidityCHAPTER 1 Operating Procedures

1.1 Initial Clearance

1.1.1 Departure Clerances 
All traffic from within the LLLL FIR will depart with a standard departure either IFR, CVFR, or Military ATS, as detailed within the SOP.
Elsewhere, clearances shall be coordinated with the relevant Radar position whose departure is within their area of Proceduresresponsibility

1.1.2 Arrival Clerances

1.1.2.1 Confirmation of STAR by Flight Crew

CHAPTER 2 Provision of Air Traffic Service

CHAPTER 3 Local Separation Standards

CHAPTER 4 ALTIMETER SETTING PROCEDURES AND METEOROLOGY

CHAPTER 5 GENERAL COORDINATION REGULATION

CHAPTER 6 TOP-DOWN COVERAGE

CHAPTER 7 UK INTENTION CODES

CHAPTER 8 CIVIL/MILITARY PROCEDURES 

ControllersProcedures mustrelevant ensureto theymultiple sectors are usingcontained thein mostthis recent version of documentation when controlling and mentoring.Chapter.

8.1 Apolo military control

VariationsTo give a response to the proceduresfollowing andincrease informationin publishedmil TFC in the wikiLLLL FIR, and Agreedto Levelssupport Diagramsthe vIAF VSOA VATIL started applying LLMA c/s "APPOLO" and their splits "LIBA" for the north control and "SHANON" for the south control, as shown in the picture

Apolo control - Bandboxing/Splitting Procedures

LLMA_CTR

"Apolo"

122.900 Mhz

LLMA_N_CTR

"Liba"

132.850 Mhz

Bandbox

LLMA_S_CTR

"Shanon"

122.900 Mhz

8.2 Military Route Corridors

8.2.1 General Procedures
Military corridors are handledestablished to enable the transit of the ATS route structure by Military traffic

8.2.1.1 Apolo control online
When Apolo control is online, they will coordinate with the relevant ACC controller to update on transit in the corridor or closure of civil airspace (as explained in each ACC).

It is both Apolo control and the relevant ACC requirement to maintain separation from the corridor or the T\A; the priority is for military or "National Mission."

8.2.1.2 Apolo control offline
When Apolo control is offline, aircraft/formations wishing to transit a corridor will call the local ACC (Pluto\South\Tel-Aviv) at least 5 minutes prior to transit, while setting the V-LARA application as describedrequired. below.

Traffic

Permanentshould be identified, and TemporaryMode changes

C

Inverified, and may be offered a service outside of the changes of a any procedurescorridor or requirementTraining inArea, LLLLdepending firon aworkload reador andknowledge.

sign

Clerance willshould be published in the following linkformat:
 after                                                   reading"C/S Follow the controllerCorridor at an altitude of XXXft report entering the area."

8.2.2 Sea corridor "Derech Ha-YAM" (讚专讱 讛讬诐)
highlighted in red
Apolo control Sector: Liba
Civil Sector: Pluto\Tel-Aviv\BGN TMA\South

Transit Altitude: 12000ft - FL500 (With exception to BGN TMA, which is requiredsplit toas reportper the following photo), for transit in thelower publishedaltitude, formApolo thatwill herequest indeeddeligation readfrom andTel-Aviv understoodACC

image.png

AIP

8.2.3 Netofa corridor "Derech Netofa" (讚专讱 谞讟讜驻讛)
highlighted in blue
Apolo control Sector: Liba
Civil Sector: Pluto

Transit Altitude: 12000ft - Published Data

30000ft

Some8.2.4 informationGalil includedcorridor
highlighted in thepurple
Apolo wikicontrol documentationSector: isLiba
Civil aeronauticalSector: dataPluto

Transit publishedAltitude: 12000ft - FL500

8.2.5 Bikaa corridor "Derech Bikaa" (讚专讱 讛讘拽注讛)
highlighted in thesteel blue
Apolo control Sector: Liba
Civil Sector: Pluto

Transit Altitude: 12000ft - FL500


LLLLimage.pngimage.png

AIP

image.png

e.g.,

8.2.6 theHahhar inboundcorridor course/axis"Derech forHahhar" holds.(讚专讱 Where there are differences, the information published讛讛专)
highlighted in thebrown
Apolo AIPcontrol shallSector: takeLiba\Shanon
Civil precedence.Sector: Pluto\South\Tel-Aviv

Transit Altitude: 12000ft - FL500 (south of BGN-TMA), 18000ft - 26000ft (Above BGN-TMA)

Letters8.2.7 ofHahhar agreementHanistar corridor "Derech Hahhar Hanistar" (讚专讱 讛讛专 讛谞住转专)
highlighted in yellow
Apolo control Sector: Shanon
Civil Sector: South

Transit Altitude: 8000ft - 11000ft

LoA8.2.8 betweenPlugot VATILcorridor and"Derech anyPlugot" adjacent(讚专讱 FIR驻诇讜讙讜转)
highlighted arein publisheddesert onyellow
Apolo thiscontrol site.Sector: AndShanon
Civil anySector: changesSouth

Transit toAltitude: them12000ft will- beFL500

explained

8.2.9 andHanegev Readcorridor and"Derech signHanegev" notice(讚专讱 讛谞讙讘)
highlighted in pink
Apolo control Sector: Shanon
Civil Sector: South

Transit Altitude: 12000ft - FL500

8.2.10 Hanegev Hamurhevet corridor "Derech Hanegev Hamurhevet" (讚专讱 讛谞讙讘 讛诪讜专讞讘转)
highlighted in Olive
Apolo control Sector: Shanon
Civil Sector: South

Transit Altitude: 12000ft - FL500