{"messages":[{"role":"system","content":"прочитай текст всех разделов, создай json файл с переработанным содержанием с установленной в файле структурой, по возможности сократи текст таким образом, чтобы не потерялся смысл, а так же исключи информацию не относящуюся к работе пилота.\n\nИзвлеки части текста и представь ответ как JSON следующего формата:"},{"role":"user","content":"# GMMN CASABLANCA MOHAMMED V International, MOROCCO\r\n\r\n## ADDITIONAL INFORMATION\r\n\r\n**1-** The messages of MVT, LDM and SLS for all commercial flights From\/ To CASABLANCA\/Mohammed V (GMMN) will be sent to the SITA addresses CMNOSXH & CMNOPXH.\r\n\r\n**2- BIRD HAZARDS:** Presence of birds around the runway and at maneuvering areas.\r\n\r\n#### <u>3- SPECIFIC INFORMATION FOR THE OPERATION OF THE A380:<\/u>\r\n\r\nThe operation of the Airbus A380 is subject to a specific route and under specific conditions, after approval of the technical operating file by the competent authority, namely:\r\n\r\n\\- Restriction on the Weight of the aircraft on landing;\r\n\r\n\\- Restriction on the Weight of the aircraft for movement on the maneuvering area;\r\n\r\n\\- Restriction on the use of external engines during the movement phase on the maneuvering area (IDLE position);\r\n\r\n\\- Restriction on the power of external engines during takeoff;\r\n\r\n\\- Use of on-board cameras during the entire period of movement on the movement area.\r\n\r\n\\- The parking stand reserved for the A380 aircraft is J1 (stand reserved for code F ACFT).\r\n\r\n\\- If the J1 stand is not available, E1 or J15 will be used.\r\n\r\n\\- RWY inspecting is required after A380 takeoff or landing\r\n\r\n**3.1  Ground movement:**\r\n\r\n**<u>Taxi into stand J1 via TWY M:<\/u>**\r\n\r\n\\- Use only TWY M ;\r\n\r\n\\- Stands C1 and C2 should be free of all ACFT;.\r\n\r\n\\- Stand E1 should be free of the following type of ACFT: B777, B747, A340, A350, A330 and the DREAMLINER B787;\r\n\r\n\\- Adjacent vehicle service road N° 1 should be closed during parking maneuver.\r\n\r\n**<u>Taxi from stand J1 for departure via TWY M:<\/u>**\r\n\r\n\\- The start-up with minimum power will be carried out after the push and pull operations towards the predefined positions;\r\n\r\n\\- Stand E1 should be free of the following type of aircraft: B777, B747, A340, A350, A330 and the DREAMLINER B787\r\n\r\n\\- Adjacent vehicle service road N°1 should be closed during parking maneuvere E1;\r\n\r\n\\- Use only TWY M;\r\n\r\n\\- Minimum power when taxiing.\r\n\r\n**<u>Taxi into stand E1 Via TWY M:<\/u>**\r\n\r\n\\- Use only TWY M;\r\n\r\n\\- Use center line until abeam the stand E3 then the ACFT will be pushed back to stand E1;\r\n\r\n\\- Stand E2 should be free;\r\n\r\n\\- Adjacent taxilane should be limited for code C ACFT\r\n\r\n**<u>Taxi from stand E1 for departure via TWY M:<\/u>**\r\n\r\n\\- Use only TWY M;\r\n\r\n\\- Minimum power when taxiing.\r\n\r\n\\- Adjacent vehicle service road N°1 should be closed during parking maneuver.\r\n\r\n**<u>Taxi into the parking stand J15 via TWY P:<\/u>**\r\n\r\n\\- Adjacent vehicle service road north of TWY P (lane 3) should be restricted;\r\n\r\n\\- Stands B11 to B14 should be limited for code C ACFT or less;\r\n\r\n\\- Stands E12, J13 and J14 should be free of all ACFT.\r\n\r\n**<u>Taxi into parking stand J15 via TWY Q:<\/u>**\r\n\r\n\\- Stands J13 and J14 should be free of all ACFT.\r\n\r\n**<u>Taxi from stand J15 for departure via TWY P:<\/u>**\r\n\r\n\\- Adjacent vehicle service road north of TWY P (lane 3) should be restricted.\r\n\r\n\\- Stands B12 to B14 should be limited for code C ACFT or less. \r\n\r\n\\- Stands B11 and J14 should be free of all ACFT.\r\n\r\n\\- Start engines at taxilane abeam stand B12 after push and pull operations.\r\n\r\n**<u>Taxi from stand J15 for departure via TWY Q:<\/u>**\r\n\r\n\\- Adjacent vehicle service road (lane 4 ) should be restricted;\r\n\r\n\\- Stands D2 to D4, J13 and J14 should be closed.\r\n\r\n\\- Start engines at taxilane abeam stand B12 after push back operation.\r\n\r\n**<u>3.2 shoulders<\/u>**\r\n\r\n\\- The shoulders of the straight taxiways are paved;\r\n\r\n\\- The shoulders of the turning taxiways are paved;\r\n\r\n\\- To avoid jet blast risks on parking stands, crews are asked to taxi on taxiways with restriction on thrust;\r\n\r\n\\- Crews should use on-board cameras during the entire taxiing phase.\r\n\r\n**<u>3.3 Obstacles free strip<\/u>**\r\n\r\nObstacles free strips on A380 paths meet the following conditions: \r\n\r\nNo obstacle, at a distance of less than 45 m from the center line of the taxiway.\r\n\r\n**<u>4- Rescue and fire fighting category :<\/u>**\r\n\r\nLevel **9** provided on the runway operated by A380 \r\n\r\n5- Strength of RESA and strip:\r\n\r\n5.1 California Bearing Ratio(CBR) of RESA:\r\n\r\n|   RWY   | California Bearing Ratio |\r\n| :-----: | :----------------------: |\r\n| 35R\/17L |         8 à 9 %          |\r\n| 35L\/17R |         8 à 9 %          |\r\n\r\n5.2 California Bearing Ratio (CBR) of strip:\r\n\r\n|                  Strip                  | California Bearing Ratio |\r\n| :-------------------------------------: | :----------------------: |\r\n|        Side stripes RWY 35L\/17R         |           9 %            |\r\n| Side stripes RWY 35R\/17L (35L\/17R side) |           9 %            |\r\n|  Side stripes RWY 35R\/17L(aprons side)  |           8 %            |\r\n\r\n"},{"role":"assistant","content":"{\"GENERAL\":{\"Airport regulations\":[\"Messages for all commercial flights to\\\/from GMMN sent to SITA addresses CMNOSXH & CMNOPXH.\"],\"Schedule coordination\":[],\"Ground Movement\":{\"Apron Procedures\":[],\"Towing of ACFT\":[],\"Taxiing\":[\"Use only TWY M for A380 operations.\",\"Minimum power during taxiing.\",\"Adjacent vehicle service roads should be restricted during parking maneuvers.\"],\"Removal of disabled aircraft\":\"\"},\"Use of APU\":[],\"Use of Runways\":[],\"Low visibility procedures\":[],\"Procedures for IFR flights\":[],\"ATS surveillance procedures\":[],\"Noise Abatement Procedures\":[],\"Regional regulations\":[],\"ATIS\":[],\"VFR Procedures\":[]},\"DEPARTURE\":{\"A-CDM\":[],\"Start-up Procedures\":[],\"Push-back procedures\":[],\"De\\\/anti-icing\":[],\"Low visibility procedures\":[],\"Taxiing\":[\"Taxi into stand J1 via TWY M requires adjacent stands to be free of specific aircraft types.\",\"Taxi from stand J1 for departure via TWY M requires adjacent stands to be free of specific aircraft types.\"],\"Runway Occupancy Time\":[],\"Simultaneous Line-Up\":[],\"Take-Off\":[],\"Continued Take-Off\":[],\"Departure Procedures\":[],\"Communication Failure\":[],\"Noise Abatement Procedures\":[],\"Regional regulations\":[],\"VFR Procedures\":[]},\"ARRIVAL\":{\"Arrival Routes\":[],\"Aerodrome Minima\":[],\"Holding Procedures\":[],\"Approach\":[],\"Runway Occupancy Time\":[],\"Taxiing\":[\"Taxi into stand E1 via TWY M requires adjacent stands to be free.\",\"Taxi from stand E1 for departure via TWY M requires adjacent stands to be free.\"],\"Emergency Landing Procedure\":[],\"Noise Abatement Procedures\":[],\"Low visibility procedures\":[],\"Communication Failure\":[],\"Regional regulations\":[],\"VFR Procedures\":[]},\"MISCELLANIUOS\":{\"Helicopter Operations\":[],\"Bird migration\":[\"Presence of birds around the runway and at maneuvering areas.\"],\"Engine Test Runs\":[],\"Visual Docking Guidance Systems\":[],\"Specific Traffic Regulations\":[],\"Schedule maintenance on the runway\":[],\"Positions not visible from control tower\":[],\"Fuel Dumping\":[],\"Warnings\":[]}}"}]}
{"messages":[{"role":"system","content":"прочитай текст всех разделов, создай json файл с переработанным содержанием с установленной в файле структурой, по возможности сократи текст таким образом, чтобы не потерялся смысл, а так же исключи информацию не относящуюся к работе пилота.\n\nИзвлеки части текста и представь ответ как JSON следующего формата:"},{"role":"user","content":"# GMMN CASABLANCA MOHAMMED V International, MOROCCO\r\n\r\n## FLIGHT PROCEDURES\r\n\r\n#### <u>VISUAL APPROACH:<\/u>\r\n\r\nThe flight crew members are required to use all guidance instruments to ensure they are established on final of the RWY on which they were cleared to land.\r\n\r\n**<u>Caution:<\/u> during visual approach there is a risk of confusion between:**\r\n\r\n\\- parallel TWY T and RWY 35R\/17L; \r\n\r\n\\- RWY 35L and RWY 35R;\r\n\r\n\\- RWY 17L and RWY 17R.\r\n\r\n#### <u>START-UP, PUSH-BACK PROCEDURES:<\/u>\r\n\r\nDeparting ACFT shall contact Mohammed V Tower or Ground 10 min before EOBT, by transmitting the following data :\r\n\r\n• Call sign;\r\n\r\n• Parking stand;\r\n\r\n• D-ATIS acknowledgement; \r\n\r\n• Destination.\r\n\r\n1.The start-up shall be requested according to CFMU regulatory measures and when the ACFT is ready.\r\n\r\n2.Pushback and taxi must be performed immediately after receiving authorization from the Tower taking into account the traffic information (Ground) and restrictions contained in the authorization.\r\n\r\nThe Tower must be informed in case of delay of start up or taxi.\r\n\r\n3.The use of reverse thrust is strictly prohibited on the apron and parking stands.\r\n\r\n4.In nose-in stands, engines start- up is performed during pushback.\r\n\r\nHowever, if the APU fails, the tower may allow engine start-up in nose-in stands before taxi.\r\n\r\nThe anti-collision lights must be turned on during engine start-up and pushback.\r\n\r\n#### <u>LOW VISIBILITY PROCEDURES (LVP):<\/u>\r\n\r\n##### 1. Communications\r\n\r\nWhen LVP are in force the information is announced at the first radio contact with the aircraft and on D-ATIS frequency **126.300 MHz**\r\n\r\nThe DATIS message contains the phrase “Low visibility procedures in force runway…” and also provides details of any unavailability of equipment relevant to LVP.\r\n\r\nController will communicate available RVRs to the pilot at first radio contact, and upon any change.\r\n\r\nPilots are required to check their operational minima.\r\n\r\nPilots will be informed by ATC when LVP are cancelled.\r\n\r\n##### 2. Criteria of implementation and end of LVP:\r\n\r\nLVP includes preparation, activation and cancellation phases.\r\n\r\nThe preparation phase begins when visibility is less than or equal to 1500 meters and\/or the ceiling is less than or equal to 300 feet, and a deterioration in weather conditions is expected.\r\n\r\nThe activation phase is triggered when the RVR is less than or equal to 800 meters and\/or the ceiling is less than or equal to 200 feet.\r\n\r\nThe LVP will end when the RVR is greater than 1500 meters and the ceiling is greater than 300 feet, and a continued improvement in weather conditions is observed.\r\n\r\n##### 3. Other information\r\n\r\n• Aircraft movement on the ground:\r\n\r\nIn order to safely manage and maintain a geographic separation between aircraft on the ground, taxiing to the aprons or to the runway will be as follows:\r\n\r\nZone 1: Stands from E1 to E12, C1 to C8, B1 to B10, and J1 to J9.\r\n\r\nAccess to this area will be via taxiway M and exit via taxiway P.\r\n\r\nZone 2: Stands from D1 to D3, J11 to J15, C23 to C26 and B11 to B14.\r\n\r\nAccess to this area will be via taxiway P and exit via taxiway Q.\r\n\r\nZone 3: Stands from D4 to D15, F1 to F9, and G1 to G6. \r\n\r\nAccess to this area will be via taxiway Q or R and exit via taxiway R.\r\n\r\n• Restrictions:\r\n\r\nDuring LVP, the air traffic controller limits the traffic to a maximum of three (03) manoeuvring aircraft.\r\n\r\n• Responsibilities of the pilot in command:\r\n\r\nThe decision to undertake or continue operating manoeuvrers corresponding to an approach procedure remains with the captain.\r\n\r\n• Aircraft guidance by the Follow-me:\r\n\r\nOn request, aircraft will continue to be guided to their parking stands by the FOLLOW-ME car.\r\n\r\n• Separations on Approach:\r\n\r\nTo allow the execution of approaches when LVP are in force, the horizontal separation minimums on approach will be 15 NM.\r\n\r\n• Exiting runway:\r\n\r\nDuring LVP, runway should be vacated via taxiway:\r\n\r\nU1, M1 or N1 if RWY 35R in use. \r\n\r\nW1, M2 or N2 if RWY 35L in use. \r\n\r\nPilots must report position when reaching the stand.\r\n\r\n\r\n\r\n• Aircraft departures\r\n\r\nThe controller will limit the movement of aircraft on the ground as follows:\r\n\r\nIn case of successive requests of departures, taxi instructions to the second aircraft could be issued as follows:\r\n\r\n\\- No departing aircraft (from zone 1) will be authorized to taxi or leave the apron towards the runway 35R\/L until N°1 reports that it is on TWY T3.\r\n\r\n\\- No departing aircraft (from zone 2) will be authorized to taxi or leave the apron towards the runway 35R\/L until N°1 reports that it is on TWY T2.\r\n\r\n\\- No departing aircraft (from zone 3) will be authorized to taxi or leave the apron towards the runway 35R\/L until N°1 reports that it is aligned and ready for take-off.\r\n\r\n\\- After take-off, pilots should report «Airborn»."},{"role":"assistant","content":"{\"GENERAL\":{\"Airport regulations\":[],\"Schedule coordination\":[],\"Ground Movement\":{\"Apron Procedures\":[\"Use of reverse thrust is prohibited on the apron and parking stands.\",\"Engines start-up in nose-in stands is performed during pushback.\"],\"Towing of ACFT\":[],\"Taxiing\":[\"• Aircraft movement on the ground: \\n In order to safely manage and maintain a geographic separation between aircraft on the ground, taxiing to the aprons or to the runway will be as follows: \\n Zone 1: Stands from E1 to E12, C1 to C8, B1 to B10, and J1 to J9. \\n Access to this area will be via taxiway M and exit via taxiway P. \\n Zone 2: Stands from D1 to D3, J11 to J15, C23 to C26 and B11 to B14. \\n Access to this area will be via taxiway P and exit via taxiway Q. \\n Zone 3: Stands from D4 to D15, F1 to F9, and G1 to G6. \\n Access to this area will be via taxiway Q or R and exit via taxiway R. \\n • Restrictions: \\n During LVP, the air traffic controller limits the traffic to a maximum of three (03) manoeuvring aircraft. \\n • Responsibilities of the pilot in command: \\nThe decision to undertake or continue operating manoeuvrers corresponding to an approach procedure remains with the captain. \\n • Aircraft guidance by the Follow-me: \\n On request, aircraft will continue to be guided to their parking stands by the FOLLOW-ME car. \\n• Separations on Approach: \\n To allow the execution of approaches when LVP are in force, the horizontal separation minimums on approach will be 15 NM. \\n • Exiting runway: \\n During LVP, runway should be vacated via taxiway: \\nU1, M1 or N1 if RWY 35R in use. \\n W1, M2 or N2 if RWY 35L in use. \\n Pilots must report position when reaching the stand.\"],\"Removal of disabled aircraft\":\"\"},\"Use of APU\":[],\"Use of Runways\":[],\"Low visibility procedures\":[\"LVP announced at first radio contact and on D-ATIS frequency.\",\"Visibility less than or equal to 1500 meters triggers preparation phase.\",\"RVR less than or equal to 800 meters triggers activation phase.\",\"LVP ends when RVR is greater than 1500 meters.\"],\"Procedures for IFR flights\":[],\"ATS surveillance procedures\":[],\"Noise Abatement Procedures\":[],\"Regional regulations\":[],\"ATIS\":[],\"VFR Procedures\":[]},\"DEPARTURE\":{\"A-CDM\":[],\"Start-up Procedures\":[\"Contact Tower or Ground 10 min before EOBT with call sign, parking stand, D-ATIS acknowledgement, and destination.\",\"Start-up requested when ACFT is ready.\"],\"Push-back procedures\":[\"Pushback and taxi performed immediately after receiving authorization from Tower taking into account the traffic information (Ground) and restrictions contained in the authorization. \\n The Tower must be informed in case of delay of start up or taxi. \\n In nose-in stands, engines start- up is performed during pushback. \\n However, if the APU fails, the tower may allow engine start-up in nose-in stands before taxi. \\n The anti-collision lights must be turned on during engine start-up and pushback.\"],\"De\\\/anti-icing\":[],\"Low visibility procedures\":[\"1. Communications \\n When LVP are in force the information is announced at the first radio contact with the aircraft and on D-ATIS frequency **126.300 MHz**  \\n The DATIS message contains the phrase “Low visibility procedures in force runway…” and also provides details of any unavailability of equipment relevant to LVP. \\n Controller will communicate available RVRs to the pilot at first radio contact, and upon any change.\\n Pilots are required to check their operational minima. \\n Pilots will be informed by ATC when LVP are cancelled. \\n 2. Criteria of implementation and end of LVP: \\nLVP includes preparation, activation and cancellation phases.\\n The preparation phase begins when visibility is less than or equal to 1500 meters and\\\/or the ceiling is less than or equal to 300 feet, and a deterioration in weather conditions is expected. \\n The activation phase is triggered when the RVR is less than or equal to 800 meters and\\\/or the ceiling is less than or equal to 200 feet. \\n The LVP will end when the RVR is greater than 1500 meters and the ceiling is greater than 300 feet, and a continued improvement in weather conditions is observed.\"],\"Taxiing\":[\"Taxi instructions limited during LVP based on aircraft position. The use of reverse thrust is strictly prohibited on the apron and parking stands.\"],\"Runway Occupancy Time\":[],\"Simultaneous Line-Up\":[],\"Take-Off\":[],\"Continued Take-Off\":[],\"Departure Procedures\":[\"The controller will limit the movement of aircraft on the ground as follows: In case of successive requests of departures, taxi instructions to the second aircraft could be issued as follows: \\n - No departing aircraft (from zone 1) will be authorized to taxi or leave the apron towards the runway 35R\\\/L until N°1 reports that it is on TWY T3. \\n - No departing aircraft (from zone 2) will be authorized to taxi or leave the apron towards the runway 35R\\\/L until N°1 reports that it is on TWY T2. \\n - No departing aircraft (from zone 3) will be authorized to taxi or leavne the apron towards the runway 35R\\\/L until N°1 reports that it is aligned and ready for take-off. \\n - After take-off, pilots should report «Airborn».\"],\"Communication Failure\":[],\"Noise Abatement Procedures\":[],\"Regional regulations\":[],\"VFR Procedures\":[]},\"ARRIVAL\":{\"Arrival Routes\":[],\"Aerodrome Minima\":[],\"Holding Procedures\":[],\"Approach\":[],\"Runway Occupancy Time\":[],\"Taxiing\":[],\"Emergency Landing Procedure\":[],\"Noise Abatement Procedures\":[],\"Low visibility procedures\":[],\"Communication Failure\":[],\"Regional regulations\":[],\"VFR Procedures\":[\"The flight crew members are required to use all guidance instruments to ensure they are established on final of the RWY on which they were cleared to land.**<u>Caution:<\\\/u> during visual approach there is a risk of confusion between: \\n - parallel TWY T and RWY 35R\\\/17L; \\n - RWY 35L and RWY 35R;\\n - RWY 17L and RWY 17R.\"]},\"MISCELLANIUOS\":{\"Helicopter Operations\":[],\"Bird migration\":[],\"Engine Test Runs\":[],\"Visual Docking Guidance Systems\":[],\"Specific Traffic Regulations\":[],\"Schedule maintenance on the runway\":[],\"Positions not visible from control tower\":[],\"Fuel Dumping\":[],\"Warnings\":[]}}"}]}
{"messages":[{"role":"system","content":"прочитай текст всех разделов, создай json файл с переработанным содержанием с установленной в файле структурой, по возможности сократи текст таким образом, чтобы не потерялся смысл, а так же исключи информацию не относящуюся к работе пилота.\n\nИзвлеки части текста и представь ответ как JSON следующего формата:"},{"role":"user","content":"# GMMN CASABLANCA MOHAMMED V International, MOROCCO\r\n\r\n## NOISE ABATEMENT PROCEDURES\r\n\r\n#### 1. Aircraft use restrictions\r\n\r\nTurbojet aeroplanes are to comply with the climb procedures hereunder:\r\n\r\n\\- Maintain the speed V2 +10 (or that which allows aircraft attitude, depending on the type of aircraft) up to 3000 FT with flaps set in the take-off configuration.\r\n\r\n\\- Maintain the take-off power until 1500 FT, then reduce climbing power until 3000 FT.\r\n\r\n#### 2. Aerodrome use restrictions \r\n\r\n**a) Use restrictions by night :**\r\n\r\nFor take-off from 2300-0600 UTC and with a tailwind component less than or equal to 7 KT, the RWY 17L or 17R is to be used.\r\n\r\nIf for operational reasons RWY 17L or 17R cannot be used, upon pilot request, at engine start up, another QFU may be attributed with additional delays.\r\n\r\n**b) Engine test:**\r\n\r\nEngine test shall not be done except in areas assigned by the Control Tower and after authorization of this one.\r\n\r\n**c) Conditions of RWY use:** \r\n\r\n**• Take-off**\r\n\r\nFrom 0600-2300 and with a tailwind component less than or equal to 7 KT, RWY 35R must be used.\r\n\r\nIf for operational limitation reasons RWY 35R or 35L cannot be used, upon pilot request, at engine start up, another QFU may be attributed with additional delays.\r\n\r\n**• Landing**\r\n\r\na. RWY 35 R or 35L must be used until a tailwind component less than or equal to 7 KTs.\r\n\r\nb. When the landing is only possible on RWY 17R or 17L, 2 cases shall be considered :\r\n\r\n<u>**1st case:**<\/u> ceiling more or equal than 1500 FT\/ground and the visibility more than or equal to 5000 m.\r\n\r\nInstrument procedure of RWY 35R or 35L is used followed by a right down-wind for RWY 17L or 17R.\r\n\r\n<u>**2nd case:**<\/u> ceiling less than 1500 FT\/ground.\r\n\r\nThe instrument procedure of RWY 17L or 17R is used."},{"role":"assistant","content":"{\"GENERAL\":{\"Noise Abatement Procedures\":[\"Turbojet aeroplanes must maintain speed V2 +10 up to 3000 FT with flaps in take-off configuration.\",\"Maintain take-off power until 1500 FT, then reduce to climbing power until 3000 FT.\"]},\"DEPARTURE\":{\"Noise Abatement Procedures\":[\"For take-off from 2300-0600 UTC with a tailwind ≤ 7 KT, use RWY 17L or 17R.\",\"If RWY 17L or 17R cannot be used, pilots may request another QFU at engine start with potential delays.\",\"From 0600-2300 with a tailwind ≤ 7 KT, use RWY 35R for take-off.\",\"If RWY 35R or 35L cannot be used, pilots may request another QFU at engine start with potential delays.\"],\"Take-Off\":[\"From 0600-2300 and with a tailwind component less than or equal to 7 KT, RWY 35R must be used. \\n If for operational limitation reasons RWY 35R or 35L cannot be used, upon pilot request, at engine start up, another QFU may be attributed with additional delays.\"]},\"ARRIVAL\":{\"Noise Abatement Procedures\":[\"For landing, use RWY 35R or 35L until a tailwind ≤ 7 KT.\",\"If landing on RWY 17R or 17L is necessary, consider the following cases:\",\"1st case: Ceiling ≥ 1500 FT and visibility ≥ 5000 m - use instrument procedure for RWY 35R or 35L followed by right down-wind for RWY 17L or 17R.\",\"2nd case: Ceiling < 1500 FT - use instrument procedure for RWY 17L or 17R.\"],\"Approach\":[\"a. RWY 35 R or 35L must be used until a tailwind component less than or equal to 7 KTs. \\n b. When the landing is only possible on RWY 17R or 17L, 2 cases shall be considered : \\n <u>**1st case:**<\\\/u> ceiling more or equal than 1500 FT\\\/ground and the visibility more than or equal to 5000 m. \\n Instrument procedure of RWY 35R or 35L is used followed by a right down-wind for RWY 17L or 17R. \\n <u>**2nd case:**<\\\/u> ceiling less than 1500 FT\\\/ground. \\n The instrument procedure of RWY 17L or 17R is used.\"]},\"MISCELLANIUOS\":{\"Helicopter Operations\":[],\"Bird migration\":[],\"Engine Test Runs\":[\"Engine test shall not be done except in areas assigned by the Control Tower and after authorization of this one\"],\"Visual Docking Guidance Systems\":[],\"Specific Traffic Regulations\":[],\"Schedule maintenance on the runway\":[],\"Positions not visible from control tower\":[],\"Fuel Dumping\":[],\"Warnings\":[]}}"}]}
{"messages":[{"role":"system","content":"прочитай текст всех разделов, создай json файл с переработанным содержанием с установленной в файле структурой, по возможности сократи текст таким образом, чтобы не потерялся смысл, а так же исключи информацию не относящуюся к работе пилота.\n\nИзвлеки части текста и представь ответ как JSON следующего формата:"},{"role":"user","content":"# GMMN CASABLANCA MOHAMMED V International, MOROCCO\r\n\r\n## LOCAL TRAFFIC REGULATIONS\r\n\r\n1- Airport is prohibited:\r\n\r\n\\- for non equipped radio communication aircraft\r\n\r\n\\- for Gliders\r\n\r\n2- Except ATC authorization, aircraft landing at\r\n\r\n- RWY 17R have not to vacate via TWYs W1 and P2 \r\n\r\n- RWY 17L have not to vacate via TWY U1\r\n\r\n- RWY 35L have not to vacate via TWY W2\r\n\r\nto vacate via TWY P.\r\n\r\n3- Except ATC authorization:\r\n\r\n\\- Intersection take offs are not permitted;\r\n\r\n\\- After full vacating of the runway 35L\/17R, aircraft have to hold short at the holding point before runway 35R\/17L;\r\n\r\n\\- After full vacating of the runway 35R\/17L, aircraft have to hold short before the parallel Taxiway."},{"role":"assistant","content":"{\"GENERAL\":{\"Airport regulations\":[\"Non-equipped radio communication aircraft are prohibited.\",\"Gliders are prohibited.\",\"ATC authorization is required for specific runway vacating procedures.\"],\"Use of Runways\":[\"Aircraft landing on RWY 17R must not vacate via TWYs W1 and P2 without ATC authorization., \\n Aircraft landing on RWY 17L must not vacate via TWY U1 without ATC authorization., \\n Aircraft landing on RWY 35L must not vacate via TWY W2 without ATC authorization. \\n Except ATC authorization: \\n - Intersection take offs are not permitted; \\n - After full vacating of the runway 35L\\\/17R, aircraft have to hold short at the holding point before runway 35R\\\/17L; \\n- After full vacating of the runway 35R\\\/17L, aircraft have to hold short before the parallel Taxiway.\"]}}"}]}
{"messages":[{"role":"system","content":"прочитай текст всех разделов, создай json файл с переработанным содержанием с установленной в файле структурой, по возможности сократи текст таким образом, чтобы не потерялся смысл, а так же исключи информацию не относящуюся к работе пилота.\n\nИзвлеки части текста и представь ответ как JSON следующего формата:"},{"role":"user","content":"# URSS SOCHI, RUSSIAN FEDERATION\r\n\r\n## LOCAL AERODROME REGULATIONS\r\n\r\n#### 1. Airport regulations \r\n\r\nOpposite-direction take-off and landing operations are authorized at Sochi AD. \r\n\r\nMovement of ACFT on the aerodrome shall be carried out under own engines power, by towing using special vehicles; skid equipped helicopters shall taxi by air – all operations are subject to clearance of TWR controller (call sign “Sochi-Ground”, FREQ 119.000 MHz) and strict observance of taxi guide line marking. \r\n\r\nACFT engines start-up and run-up are permitted: \r\n\r\n\\- at idle power - on stands 1-22 under the supervision of ground handling specialists; \r\n\r\n\\- in other operating modes - on TWY M and on taxi route N1 (see appropriate chart). \r\n\r\n**Hot spots on RWY and TWY** \r\n\r\nIntersection of RWY 06\/24 and RWY 02\/20. \r\n\r\n\\- when operating flights using two runways simultaneously or taxiing along the runway, flight crews shall maintain visual look-out and radio listening watch, strictly follow ATS unit instructions. \r\n\r\nIntersection of TWYs L, M, R: \r\n\r\n\\- flight crews shall taxi with increased look-out in accordance with the marking and ATS unit instructions. \r\n\r\n#### 2. Taxiing to and from stands \r\n\r\nTaxi and tow operations are PROHIBITED without clearance of “Sochi-Ground” controller. \r\n\r\nTowing and taxiing of ACFT shall be carried out via taxiways and the apron by clearance of “Sochi-Ground” controller with the following peculiarities: \r\n\r\n\\- taxiing (towing) of ACFT into (out of) stands shall be carried out under the supervision of ground handling specialists; \r\n\r\n\\- ACFT shall taxi strictly along the marking except the cases when it is necessary to avoid obstacles, to follow ATC controller’s instructions, to follow “Follow-me” vehicle. \r\n\r\nFlight crew shall advise ATS unit if additional time of more than 1 minute is required for start of pushback\/ towing after obtaining ATS unit clearance. If more than 1 minute has passed after issuing clearance for pushback\/towing and the flight crew has not commenced the procedure, then the flight crew must request another clearance for pushback\/towing. \r\n\r\nACFT parked on stands 1-22 shall start engines on TWY M, it is permitted to start engines on the mentioned stands except stands 14-15 for turboprop and turbojet ACFT parked facing RWY 06\/24. \r\n\r\nTWY A, B, M (segment from TWY A to TWY B) are AVBL for Il-96-300PU, Il-76 (index 6 ACFT) and index 1-5 ACFT, authorized to operate at the aerodrome. \r\n\r\nTWY M (segment from TWY C to stand 22) is AVBL for A-220-100\/300, A-319 and its modifications, A-320 and its modifications, A-320neo, A-321 and its modifications, B737-700\/800\/900\/MAX 8, Bombardier CS 300, Tu-134, Yak-42, Be-200 (index 4 ACFT with wingspan of 36 m or less and main wheel track of 7.5 m or less), and index 1-3 ACFT, authorized to operate at the aerodrome. \r\n\r\nTWY C, M (segment from TWY B to TWY C) are AVBL for An-24, An-26, An-30, An-32, Il-114, B737-200\/300\/400\/500, RRJ-95B, Bombardier Dash 8 Q400 and its modifications, Fokker 50\/50F\/60, Fokker F27 Friendship, BAe Avro RJ-70\/85\/100, BAe-146-200 (index 3 ACFT)  and index 1 and 2 ACFT, authorized to operate at the aerodrome. \r\n\r\nTWY E, F, G, M (segment from stand 23 to TWY H) are AVBL for B707-320C, B747 and its modifications, B767-200\/300 and their modifications, B777 and its modifications, A-310, A-330 and its modifications, A-350-900 (index 6 ACFT) and index 1-5 ACFT, authorized to operate at the aerodrome. \r\n\r\nTaxiing via TWY M shall be executed at reduced speed strictly along the taxi guide lines for the following ACFT types: \r\n\r\n\\- from TWY A to TWY B, E, F, G - Il-96-300PU, Il-86, Il-76, Il-62, B707-320C, B747-100\/200\/300\/400\/400ER\/SP, B767-200\/200ER\/300\/300ER\/300F\/400\/400ER, B777-200\/200ER\/200LR\/300\/300ER, A-310-200, A-330-200\/300, A-350-900 (index 6 ACFT); \r\n\r\n\\- from stand 23 to TWY H – A-319, A-320, A-320neo, A-321, B757-200, Il-18, Tu-134, Tu-204, Tu-204-100, Tu-214 (index 4 ACFT with outer main gear wheel track above 7.5 m), Tu-154 (index 5 ACFT), Il-96-300PU, Il-86, Il-76, Il-62, B707-320C, B747-100\/200\/300\/400\/400ER\/SP, B767-200\/200ER\/300\/300ER\/300F\/400\/400ER, B777-200\/200ER\/200LR\/300\/300ER, A-310-200, A-330-200\/300, A-350-900 (index 6 ACFT). \r\n\r\nTWY H, L, M (segment from TWY H to TWY N), N (segment from TWY M to RWY 02\/20), P, Q, T, U, V, W are AVBL for An-124-100 (index 7 ACFT) and index 1-6 ACFT, authorized to operate at the aerodrome. \r\n\r\nTWY K, N (segment from apron to TWY M), R, Z, Z1, Z2, Z3 are AVBL for Il-96-300PU, Il-76, B707-320C, B747 and its modifications, B767-200\/300 and their modifications, B777 and its modifications, A-310, A-330 and its modifications, A-350-900 (index 6 ACFT), and index 1-5 ACFT, authorized to operate at the aerodrome. \r\n\r\nTWY Y is AVBL for Tu-154 (index 5 ACFT), An-12, Il-18, Tu-134, Tu-204, Tu-204-100, Tu-214, Yak-42, Be-200, B737-700\/800\/900, B737 MAX 8, B757-200, A-220-100\/300, A-319 and its modifications, A-320 and its modifications, A-320neo, A-321 and its modifications, Bombardier CS 300 (index 4 ACFT) and index 1-3 ACFT, authorized to operate at the aerodrome. \r\n\r\nTaxi route N1 is established on Apron 1 (along stands 23-38 on the south side) for taxiing of index 1-6 ACFT. \r\n\r\nThe following taxi routes are established on Apron 2: \r\n\r\n\\- T1 (along stands 57-60 on the north side) – for taxiing of index 1-7 ACFT; \r\n\r\n\\- T2 (along stand 60 on the west side) – for taxiing of index 1-6 ACFT; \r\n\r\n\\- T3 (along stands 57-60 on the south side) – for taxiing of index 1-6 ACFT; \r\n\r\n\\- Y1 (along stands 39 (A-D) – 56 on the north side) – for taxiing of index 1-5 ACFT; \r\n\r\n\\- Y2 (between stands 39D, 39E and stand 40) – for taxiing of index 1 ACFT; \r\n\r\n\\- Y3 (between stands 39A, 39B, 39C, 39D and stands 39E, 39F, 39G, 39H) – for taxiing of index 1 ACFT; \r\n\r\n\\- Y4 (along stands 39E, 39F, 39G, 39H on the south side) – for taxiing of index 1 ACFT. \r\n\r\nTaxiing via TWY M from stand 1 to stand 4 is permitted only when stands 1-4 are vacant. \r\n\r\nTaxiing of index 1-6 ACFT via TWY M to\/from TWY A is permitted only when stands 1-4 are vacant.  \r\n\r\n***Note:*** \r\n\r\nACFT taxi routes are indicated on appropriate charts. \r\n\r\nACFT shall taxi into\/out of stand 32 only when stand 33 is vacant. \r\n\r\nACFT shall taxi into stand 36С only when stands 34, 35 are vacant. \r\n\r\nACFT shall taxi out of stand 36C only when stands 37, 38 are vacant. \r\n\r\nACFT shall taxi into stand 60 only when stand 59 is vacant. \r\n\r\nACFT shall execute a turn at RWY 02 extremity at safe speed along the minimum radius of turn according to the Aeroplane Flight Manual with flight crew’s increased caution. \r\n\r\nACFT taxiing into\/out of stands under own engines power as well as ACFT towing shall be carried out under control of specialists of ground maintenance service. \r\n\r\n#### 3. Arrival \r\n\r\nStandard arrival route is assigned to flight crews by the ATS unit. \r\n\r\nFlight crew shall plan vacation of the RWY along the nearest TWY or along the TWY recommended by the ATS unit considering landing distance available (for RWY 02 – 2400 m, for RWY 06 – 2745 m). \r\n\r\n#### 4. Departure \r\n\r\n**4.1 ACFT departure** \r\n\r\nATC clearance shall be requested from “Sochi-Ground” controller H24. \r\n\r\nDeparture Service (call sign “Sochi-Delivery”) may operate in the Russian and English languages by decision of the Flight Control Officer, notification provided via ATIS.  \r\n\r\nATC clearance shall be requested 5-20 minutes before the estimated time of departure, when ACFT is completely ready for departure. The request must include: ACFT call sign, stand number, destination aerodrome, ATIS code letter, information concerning necessity of de-icing\/anti-icing treatment.  \r\n\r\nStart-up of one engine in the process of towing is permitted by arrangement with driver of tow truck. In this case specialist in charge of ACFT departure is responsible for compliance with safety measures.  \r\n\r\nIn order to expedite traffic, the flight crew may be cleared for immediate take-off. After obtaining such clearance the flight crew shall taxi onto the runway and execute take-off without interrupting movement. \r\n\r\nACFT shall take off without stop at the line-up position within 30 seconds after obtaining ATC clearance at the runway-holding position. \r\n\r\nIn case the full length of RWY 24 shall be used, flight crew shall inform ATS unit controller after obtaining departure clearance at the runway-holding position. \r\n\r\nDeparture from RWY 20 shall be executed from RWY beginning (TWY Q) only. \r\n\r\nTake-off from both runways shall be executed taking into account: \r\n\r\n\\- wind restrictions, established in the Aeroplane Flight Manual for the specified ACFT type and\/or Operations Manual of the airline; \r\n\r\n\\- compliance of other ACFT restrictions with present weather, RWY condition and required minimum for take-off. \r\n\r\n**Procedure of ACFT take-off from RWY 24** \r\n\r\nBefore start of taxiing, the flight crew shall advise line-up position to ATS unit controller taking into account the published information on TORA, TODA and ASDA. ATS unit controller assigns exit from the terminal area via the designated SID routes or via the assigned tracks (vectoring). \r\n\r\nTake-off of ACFT by a pilot-in-command’s decision shall be carried out from the position on the runway, where the declared distances of the runway from the start of take-off run conform to the required ones for actual take-off mass of ACFT and take-off instructions. \r\n\r\nEight line-up positions are AVBL on RWY 24 with the following declared distances: \r\n\r\n\\- from the RWY beginning: TORA 2895 m, TODA 3045 m, ASDA 2895 m; \r\n\r\n\\- from TWY L: TORA 2690 m, TODA 2840 m, ASDA 2690 m; \r\n\r\n\\- from TWY K: TORA 2525 m, TODA 2675 m, ASDA 2525 m; \r\n\r\n\\- from TWY H: TORA 2377 m, TODA 2527 m, ASDA 2377 m; \r\n\r\n\\- from TWY G: TORA 2204 m, TODA 2354 m, ASDA 2204 m; \r\n\r\n\\- from TWY F: TORA 2004 m, TODA 2154 m, ASDA 2004 m; \r\n\r\n\\- from TWY E: TORA 1505 m, TODA 1655 m, ASDA 1505 m; \r\n\r\n\\- from TWY V: TORA 1492 m, TODA 1642 m, ASDA 1492 m. \r\n\r\nDuring take-off from TWY H, G, F, E, V pilot-in-command is provided with information about TORA. \r\n\r\n**Procedure of ACFT take-off from RWY 20** \r\n\r\nOne line-up position is AVBL on RWY 20 with the following declared distances from the RWY beginning (TWY Q): \r\n\r\n\\- TORA 2500 m, TODA 2650 m, ASDA 2500 m. \r\n\r\nBefore start of taxiing, the flight crew shall report when ready for take-off to ATS unit controller. \r\n\r\nATS unit controller assigns exit from the terminal area via the designated SID routes or via the assigned tracks (vectoring). \r\n\r\n***Note:*** \r\n\r\nIn the event of an aborted take-off from RWY 20 ACFT shall turn at RWY 02 THR at reduced speed, with flight crew exercising extreme caution. Width of RWY 02\/20 turn pad at THR 02 is 60 m. \r\n\r\n#### 5. Parking area for small aircraft (General aviation) \r\n\r\nGeneral aviation aircraft shall be escorted by «Follow-me” vehicle to the designated stands. \r\n\r\n#### 6. Parking area for helicopters \r\n\r\nStands 1-22, 33-38, 39A-39H, 40-53, 54A-54F, 55-64 are AVBL for parking of helicopters. Specific stand for parking is indicated by the ATS unit. \r\n\r\n#### 7. Apron \r\n\r\n**7.1 Apron 1** \r\n\r\n**Stands 1-4** \r\n\r\nParking on stands designated for ACFT carrying Heads of State, official delegations shall be executed by instruction of the aerodrome administration as directed by head of shift of the airport. \r\n\r\nParking of ACFT on stands 1-4 not in alignment with the marking is permitted as outlined below: \r\n\r\n1)for Il-96 type ACFT – abeam TWY A; \r\n\r\n2)for Tu-204 type ACFT – on stand 4 or TWY B; \r\n\r\n3)for Mi-8 type HEL – on segment between TWY A and TWY B; \r\n\r\n4)for up to 3 (three) Il-76 type ACFT in the following order: \r\n\r\n\\- one ACFT - abeam TWY B (ILS critical area limit must not be crossed); \r\n\r\n\\- one ACFT – on stands 1-3 in the direction of TWY M (from where ACFT shall taxi onto TWY B); \r\n\r\n\\- one ACFT – abeam TWY A (from where ACFT shall taxi onto TWY M, TWY B). \r\n\r\n**Stands 5-8** \r\n\r\nStands are AVBL for parking of Falcon, Fokker, Global, Gulfstream and other ACFT of the same class. \r\n\r\nStands 5-7 are AVBL for parking of ACFT with wingspan 28 m or less, length 26 m or less.  \r\n\r\nTo park onto the stands ACFT shall execute a turn through an adjacent vacant stand after the “Follow-me” vehicle in the direction of RWY 06\/24, heading towards the ground handling specialist providing marshalling services to arriving ACFT. \r\n\r\nStand 8 is AVBL for parking of ACFT with wingspan 24 m or less. To park onto the stand ACFT shall execute a turn through stand 9 after the “Follow-me” vehicle in the direction of RWY 06\/24, heading towards the ground handling specialist providing marshalling services to arriving ACFT. \r\n\r\nParking of Mi-8 and class below HEL on stands 5-8 shall be carried out in accordance with appropriate chart, HEL turn is permitted within boundaries of one stand. \r\n\r\nStands 5-8 are AVBL for parking of skid equipped HEL, air taxiing to the stands shall be carried out at minimum height along taxi guide line marking. \r\n\r\nACFT parked on stands 5-8 facing RWY 06\/24 shall taxi out of the stands onto TWY M at idle power. \r\n\r\n**Stands 9-17** \r\n\r\nThe stands are AVBL for parking of index 1-5 ACFT. ACFT shall taxi out of the stands for engines start-up using tow tractor. Engines shall be started during ACFT towing. \r\n\r\nStands are AVBL for parking of ATR-72, Falcon, Fokker, Global, Gulfstream and other ACFT of the same class. \r\n\r\nStands 9-11 are AVBL for parking of ACFT with wingspan 24 m or less. To park onto the stands ACFT shall execute a turn through stands 10-12 respectively after the “Follow-me” vehicle in the direction of RWY 06\/24, heading towards the ground handling specialist providing marshalling services to arriving ACFT. \r\n\r\nStands 12-17 are AVBL for parking of ACFT with wingspan 28 m or less, length 29.5 m or less. To park onto the stands ACFT shall execute a turn through stands 13-18 respectively after the “Follow-me” vehicle in the direction of RWY 06\/24, heading towards the ground handling specialist providing marshalling services to arriving ACFT. \r\n\r\nMi-8 and class below HEL shall be parked on stands 9-17 in accordance with appropriate chart. \r\n\r\nStands 9-17 are AVBL for parking of skid equipped HEL, air taxiing to the stands shall be carried out at minimum height along taxi guide line marking. \r\n\r\nACFT parked on stands 9-17 shall taxi out of stands onto TWY M at idle power. \r\n\r\nIt is PROHIBITED for turboprop and turbojet ACFT to taxi out of stands 13, 14. \r\n\r\n**Stands 18-22** \r\n\r\nThe stands are AVBL for parking of index 1-5 ACFT. ACFT shall taxi out of the stands for engines start-up using tow tractor. Engines shall be started during ACFT towing. \r\n\r\nStands are AVBL for parking of ATR-72, Falcon, Fokker, Global, Gulfstream and other ACFT of the same class. \r\n\r\nStands 18, 19 are AVBL for parking of ACFT with wingspan 28 m or less, length 29.5 m or less. To park onto the stands ACFT shall execute a turn through stands 19, 20 respectively after the “Follow-me” vehicle in the direction of RWY 06\/24, heading towards the ground handling specialist providing marshalling services to arriving ACFT. \r\n\r\nStand 20 is AVBL for parking of ACFT with wingspan 28 m or less, length 29.5 m or less. To park onto the stand ACFT shall execute a turn between stands 20 and 21 after the “Follow-me” vehicle in the direction of RWY 06\/24, heading towards the ground handling specialist providing marshalling services to arriving ACFT. \r\n\r\nStand 20 is AVBL for parking of ACFT with a wingspan of 48 m when stands 19, 21 are vacant. \r\n\r\nStands 21, 22 are AVBL for parking of ACFT with wingspan 24 m or less. \r\n\r\n1)To park onto stand 21 ACFT shall execute a turn through stand 22 after the “Follow-me” vehicle in the direction of RWY 06\/24, heading towards the ground handling specialist providing marshalling services to arriving ACFT. \r\n\r\n2)To park onto stand 22 ACFT taxiing via taxi route N1 shall execute a turn in the direction of RWY 06\/24, heading towards the ground handling specialist providing marshalling services to arriving ACFT, and ACFT taxiing via TWY M shall taxi along taxi guide line on stand 23 after the “Follow-me” vehicle. \r\n\r\nMi-8 and class below HEL shall be parked on stands 18-22 in accordance with ACFT parking chart. \r\n\r\nStands 18-22 are AVBL for parking of skid equipped HEL, air taxiing to stands shall be carried out at minimum height along taxi guide line marking. \r\n\r\nACFT parked on stands 18-22 shall taxi out of stands at idle power. \r\n\r\n***Attention!** Stands 23-32 are equipped with aerobridges and docking guidance SAFEDOCK system for ACFT parking on stands.* \r\n\r\n**Stand 23** \r\n\r\nThe stand is AVBL for parking of index 6-7 ACFT (B747-400, B777-200, A-330 and its modifications, A-350-900 ACFT) and below. \r\n\r\nIndex 6-7 ACFT (B747-400, B777-200, A-330 and its modifications, A-350-900 ACFT) shall taxi into stand 23 via TWY M. \r\n\r\nIndex 6-7 ACFT (B747-400, B777-200, A-330 and its modifications, A-350-900 ACFT) shall taxi out of the stand onto TWY M for engines start-up using tow tractor. \r\n\r\nEngines shall be started during ACFT towing. \r\n\r\nTowing of ACFT with a wingspan of above 45 m out of stand 23 onto TWY M, when stand 22 is occupied, is PROHIBITED. \r\n\r\n**Stands 24-29** \r\n\r\nThe stands are AVBL for parking of ACFT with a wingspan of not above 48 m (B767-300 ACFT and less). \r\n\r\nACFT shall taxi out of the stands for engines start-up using tow tractor. Engines shall be started during ACFT towing. \r\n\r\nStand 25 is AVBL for parking of ACFT with a wingspan of not above 60.3 m (A-330-200\/300 ACFT and less). \r\n\r\n**Stand 30** \r\n\r\nThe stand is AVBL for parking of ACFT with a wingspan of not above 39 m (B757-200 ACFT and less). \r\n\r\nACFT shall taxi out of the stand for engines start-up using tow tractor. Engines shall be started during ACFT towing. \r\n\r\n**Stand 31** \r\n\r\nThe stand is AVBL for parking of ACFT with a wingspan of not above 36 m (B737-900ER ACFT and less). \r\n\r\nACFT shall taxi out of the stand for engines start-up using tow tractor. Engines shall be started during ACFT towing. \r\n\r\n**Stand 32** \r\n\r\nThe stand is AVBL for parking of index 6-7 ACFT (B747-400, B777 and its modifications, A-330 and its modifications, A-350-900 ACFT) and below. \r\n\r\nIndex 6-7 ACFT (B747-400, B777 and its modifications, A-330 and its modifications, A-350-900 ACFT) shall taxi into stand 32 via TWY M. \r\n\r\nIndex 6-7 ACFT (B747-400, B777 and its modifications, A-330 and its modifications, A-350-900 ACFT) shall taxi out of the stand onto TWY M for engines start-up using tow tractor. \r\n\r\nEngines shall be started during ACFT towing. \r\n\r\nWhen index 1-7 ACFT taxi into stand 32, stand 33 must be vacant. \r\n\r\nStand 33 is AVBL for temporary parking of index 1-5 ACFT for loading (unloading) of baggage and embarkation (disembarkation) of passengers during ACFT servicing on stand 32. \r\n\r\nPushback of ACFT from stand 32 to TWY M shall be executed strictly to abeam stand 31.  \r\n\r\n**Stands 33-35** \r\n\r\nThe stands are AVBL for index 5 ACFT (A-319, B737-500, Be-200 ACFT) and below. \r\n\r\nStand 33 is used as a temporary parking position for disembarking (embarking) passengers, when stand 32 is vacant or used for ACFT maintenance.   \r\n\r\nStands 34, 35 are AVBL for parking of ACFT in accordance with ACFT parking chart. ACFT with wingspan 24 m or less shall be parked onto stands 34, 35 by executing a turn through an adjacent vacant stand in the direction of RWY 06\/24, heading towards the ground handling specialist providing marshalling services to arriving ACFT. ACFT can taxi into stand 34 under assistance of the “Follow-me” vehicle through stand 33. \r\n\r\nACFT parked facing RWY 06\/24 shall taxi out of the stands at idle power. \r\n\r\nProcedure of HEL parking onto stands 33-35: \r\n\r\n\\- Mi-8 and class below HEL - in accordance with the established parking procedure; \r\n\r\n\\- skid equipped helicopters - at minimum height along taxi guide line marking. \r\n\r\n***Attention!** Stands 36-38 are used for ACFT de-icing\/anti-icing treatment.*  \r\n\r\n**Stand 36** \r\n\r\nThe stand is AVBL for parking of index 6 ACFT (A-310-200, B767-200\/300, Il-62, Il-76) and index below ACFT. \r\n\r\nACFT shall taxi out of the stand for engines start-up using tow tractor. Engines shall be started during ACFT towing. \r\n\r\n**Stand 36A** \r\n\r\nThe stand is AVBL for ACFT with wingspan 48 m or less.  \r\n\r\nACFT shall taxi out of the stand for engines start-up using tow tractor. Engines shall be started during ACFT towing. \r\n\r\n**Stand 36B** \r\n\r\nThe stand is AVBL for parking of index 6, 7 ACFT (A-330 and its modifications, A-350-900, B747-400, B777 and its modifications, An-124), by taxiing via TWY M under assistance of the “Follow-me” vehicle. \r\n\r\nACFT shall be towed from the stand onto TWY M, engines shall be started, when ACFT is under tow. \r\n\r\nTaxiing into\/out of the stand shall be executed when stands 36, 36A, 36C are vacant. \r\n\r\n**Stand 36C** \r\n\r\nACFT shall taxi into the stand along the marking after the “Follow-me” vehicle when stands 34, 35, 36, 36A, 36B are vacant. \r\n\r\nACFT shall taxi out of stand 36C when stands 37, 38 are vacant. \r\n\r\nDe-icing\/anti-icing treatment on the stand is permitted for ACFT with running engines. \r\n\r\n**Stands 37, 38** \r\n\r\nThe stands are AVBL for parking of index 5 ACFT (A-320, B737-700 ACFT) and below. \r\n\r\nACFT shall taxi out of the stands for engines start-up using tow tractor. \r\n\r\nIndex 6-7 ACFT (B747-400, B777 and its modifications, A-330 and its modifications, A-350-900 ACFT) shall taxi into stand 32 via TWY M. \r\n\r\n\r\nIndex 6-7 ACFT (B747-400, B777 and its modifications, A-330 and its modifications, A-350-900 ACFT) shall taxi into stand 32 via TWY M. \r\n\r\nIndex 6-7 ACFT (B747-400, B777 and its modifications, A-330 and its modifications, A-350-900 ACFT) shall taxi out of the stand onto TWY M for engines start-up using tow tractor. \r\n\r\nEngines shall be started during ACFT towing. \r\n\r\nWhen index 1-7 ACFT taxi into stand 32, stand 33 must be vacant. \r\n\r\nEngines shall be started during ACFT towing. \r\n\r\n**Stand 37** is AVBL for outside washing of ACFT. \r\n\r\n***Note:** ACFT may be parked not in alignment with the marking by instruction of the AD operator, as directed by head of shift of the airport (or designated persons) for efficient use of the parking space.* \r\n\r\n**7.2 Apron 2**\r\n\r\n**Stands 39 (А, В, С, D, E, F, G, H)**\r\n\r\nStands are AVBL for parking of Falcon 2000 type ACFT, Mi-8, Ka-32 type HEL, taxiing into stands - under own engines power facing SE and NW. \r\n\r\nSkid equipped HEL shall be parked onto the indicated stands as outlined below: \r\n\r\n\\- by air taxiing along taxi guide line marking at minimum height; \r\n\r\n\\- by towing the HEL into the stand using ground handling wheels after landing abeam stand 39. \r\n\r\nFalcon 2000 type ACFT shall taxi out of the stand under own engines power. \r\n\r\n**Stands 40-47** \r\n\r\nThe stands are AVBL for index 6 ACFT (B757-200, Tu-214, A-310-200 ACFT) and below. \r\n\r\nACFT shall be parked facing south-east. \r\n\r\nACFT may taxi into the stands for parking facing north-west through any adjacent vacant stand after the “Follow-me” vehicle. \r\n\r\nACFT may taxi out of the stands facing south-east under own engines power after the “Follow-me” vehicle. ACFT shall taxi out of the stands facing north-west under own engines power. \r\n\r\nTaxiing of ACFT onto taxi route Y1 shall be executed by towing. \r\n\r\nEngines start-up shall be executed on taxi route Y1.  \r\n\r\nTaxi-in procedures: \r\n\r\n\\- Tu-214, A-310-200 and class below, B757-200 ACFT: under own engines power - facing SE; after the “Follow-me” vehicle - facing NW, through any adjacent vacant stand; \r\n\r\n\\- A-319, A-320, B737-100, B737-500 and class below ACFT shall be parked onto the stands by executing a turn through an adjacent vacant stand after the “Follow-me” vehicle, heading towards the ground handling specialist providing marshalling services to arriving ACFT; \r\n\r\n\\- Falcon, Fokker, Global, Gulfstream, other ACFT of the same class with wingspan 32 m or less shall be parked onto the stands by executing a turn through an adjacent vacant stand in the direction of RWY 06\/24, heading towards the ground handling specialist providing marshalling services to arriving ACFT; \r\n\r\n\\- Mi-8 and class below HEL shall be parked onto the stands in accordance with ACFT parking chart; \r\n\r\n\\- Mi-26 HEL shall taxi into the stand and execute a turn within the boundaries of the stand; taxiing into stands 41-47 can be carried out through any adjacent vacant stand. When stand 39 is occupied, HEL shall be parked onto stand 40 by towing; \r\n\r\n\\- skid equipped HEL shall air taxi into stands along taxi guide line marking at minimum height. \r\n\r\nTaxi-out procedures: \r\n\r\n\\- facing NW - under own engines power; \r\n\r\n\\- facing SE - under own engines power after the “Follow-me” vehicle; \r\n\r\n\\- ACFT parked facing RWY 06\/24 shall taxi onto TWY M at idle power; \r\n\r\n\\- onto TWY Y - by towing, engines shall be started after towing is completed; \r\n\r\n\\- Mi-26 type HEL parked on stand 40 shall leave the stand under tow, when stand 39 is occupied. \r\n\r\n**Stands 48-52** \r\n\r\nThe stands are AVBL for index 6 ACFT (Il-76, B767-200\/300 ACFT) and below. \r\n\r\nACFT shall be parked facing south-east. ACFT may taxi into the stands for parking facing north-west through adjacent vacant stand after the “Follow-me” vehicle. The mentioned ACFT types shall taxi into the stands under own engines power. \r\n\r\nTaxiing of ACFT onto taxi route Y1 shall be executed by towing. \r\n\r\nEngines start-up shall be executed on taxi route Y1. \r\n\r\n**Stand 53** \r\n\r\nThe stand is AVBL for index 5 ACFT (A-319, B737-500, Be-200 ACFT) and below. \r\n\r\nThe mentioned ACFT types may taxi into stand 53 under own engines power by executing a turn through stand 52 after the “Follow-me” vehicle. \r\n\r\nACFT may taxi out of the stand facing south-east under own engines power after the “Follow-me” vehicle. ACFT shall taxi out of the stand facing north-west under own engines power. \r\n\r\n**Stands 54 (A, B, C, D, E, F)** \r\n\r\nStands are AVBL for parking of Mi-8 and class below HEL, taxiing into the stand - under own engines power facing NE or SW. \r\n\r\nHEL shall be towed from stand 54, when stands 53, 55 are occupied, or in case HEL is unable to execute a turn on the stand. In other cases HEL shall leave the stands under own engines power. \r\n\r\n**Stands 55, 56** \r\n\r\nTaxi-in procedures: \r\n\r\n\\- Il-62, Tu-204, A-321-200 type ACFT - facing SE, after the “Follow-me” vehicle; \r\n\r\n\\- Falcon, Fokker, Global, Gulfstream, other ACFT of the same class with wingspan 32 m or less - by executing a turn through an adjacent vacant stand in the direction of RWY 06\/24, heading towards the ground handling specialist providing marshalling services to arriving ACFT; \r\n\r\n\\- Mi-8 and class below HEL - in accordance with appropriate chart; \r\n\r\n\\- Mi-26 type HEL shall taxi into the stands and execute a turn, or shall taxi into the stands through an adjacent vacant stand; \r\n\r\n\\- skid equipped HEL shall air taxi into the stands at minimum height along taxi guide line marking; \r\n\r\n\\- in exceptional cases, stands are AVBL for parking of B767-300 type ACFT. \r\n\r\nTaxi-out procedures: \r\n\r\n\\- Il-62, Tu-204, A-321-200 type ACFT - by towing only; \r\n\r\n\\- ACFT with wingspan 32 m or less parked on stands facing RWY 06\/24 shall taxi out of the stands onto TWY M at idle power. "},{"role":"assistant","content":"{\"GENERAL\":{\"Airport regulations\":[\"Opposite-direction take-off and landing operations are authorized.\",\"Movement of ACFT on the aerodrome shall be under own engine power or towing with clearance.\",\"ACFT engines start-up is permitted at idle power on designated stands under supervision.\"],\"Schedule coordination\":[],\"Ground Movement\":{\"Apron Procedures\":[\"Taxiing and towing operations require clearance from 'Sochi-Ground'.\",\"Flight crew must advise ATS if additional time is needed for pushback. \\n **Hot spots on RWY and TWY** Intersection of RWY 06\\\/24 and RWY 02\\\/20. \\n - when operating flights using two runways simultaneously or taxiing along the runway, flight crews shall maintain visual look-out and radio listening watch, strictly follow ATS unit instructions. \\n Intersection of TWYs L, M, R: \\n - flight crews shall taxi with increased look-out in accordance with the marking and ATS unit instructions.\"],\"Towing of ACFT\":[\"Towing must be supervised by ground handling specialists.\"],\"Taxiing\":[\"Taxiing must follow taxi guide lines and ATS instructions.\",\"Taxiing via TWY M is permitted at reduced speed for specific ACFT types.\"],\"Removal of disabled aircraft\":\"\"},\"Use of APU\":[],\"Use of Runways\":[\"Flight crews must maintain visual lookout and follow ATS instructions at runway intersections.\"],\"Low visibility procedures\":[],\"Procedures for IFR flights\":[],\"ATS surveillance procedures\":[],\"Noise Abatement Procedures\":[],\"Regional regulations\":[],\"ATIS\":[],\"VFR Procedures\":[]},\"DEPARTURE\":{\"A-CDM\":[\"ATC clearance must be requested 5-20 minutes before departure.\",\"Start-up of one engine during towing is permitted with arrangements.\"],\"Start-up Procedures\":[\"Engines must be started during towing. ACFT engines start-up and run-up are permitted: \\n - at idle power - on stands 1-22 under the supervision of ground handling specialists; \\n - in other operating modes - on TWY M and on taxi route N1 (see appropriate chart).\"],\"Push-back procedures\":[\"Pushback must be executed under supervision and with clearance.\"],\"De\\\/anti-icing\":[],\"Low visibility procedures\":[],\"Taxiing\":[\"Taxi-out procedures: \\n - Il-62, Tu-204, A-321-200 type ACFT - by towing only; \\n - ACFT with wingspan 32 m or less parked on stands facing RWY 06\\\/24 shall taxi out of the stands onto TWY M at idle power. \\n Taxiing onto the runway must be completed within 30 seconds after clearance. \"],\"Runway Occupancy Time\":[],\"Simultaneous Line-Up\":[],\"Take-Off\":[\"Take-off must consider wind restrictions and compliance with weather conditions.\"],\"Continued Take-Off\":[],\"Departure Procedures\":[\"ATC clearance shall be requested from 'Sochi-Ground' controller H24. \\n Departure Service (call sign 'Sochi-Delivery') may operate in the Russian and English languages by decision of the Flight Control Officer, notification provided via ATIS. \\n ATC clearance shall be requested 5-20 minutes before the estimated time of departure, when ACFT is completely ready for departure. The request must include: ACFT call sign, stand number, destination aerodrome, ATIS code letter, information concerning necessity of de-icing\\\/anti-icing treatment. \\n Start-up of one engine in the process of towing is permitted by arrangement with driver of tow truck. In this case specialist in charge of ACFT departure is responsible for compliance with safety measures. \\n In order to expedite traffic, the flight crew may be cleared for immediate take-off. After obtaining such clearance the flight crew shall taxi onto the runway and execute take-off without interrupting movement. \\n ACFT shall take off without stop at the line-up position within 30 seconds after obtaining ATC clearance at the runway-holding position. \\n In case the full length of RWY 24 shall be used, flight crew shall inform ATS unit controller after obtaining departure clearance at the runway-holding position. \\n Departure from RWY 20 shall be executed from RWY beginning (TWY Q) only. \\n Take-off from both runways shall be executed taking into account: \\n - wind restrictions, established in the Aeroplane Flight Manual for the specified ACFT type and\\\/or Operations Manual of the airline; \\n - compliance of other ACFT restrictions with present weather, RWY condition and required minimum for take-off. \\n **Procedure of ACFT take-off from RWY 24** \\n Before start of taxiing, the flight crew shall advise line-up position to ATS unit controller taking into account the published information on TORA, TODA and ASDA. ATS unit controller assigns exit from the terminal area via the designated SID routes or via the assigned tracks (vectoring). \\n Take-off of ACFT by a pilot-in-command’s decision shall be carried out from the position on the runway, where the declared distances of the runway from the start of take-off run conform to the required ones for actual take-off mass of ACFT and take-off instructions. \\n Eight line-up positions are AVBL on RWY 24 with the following declared distances: \\n - from the RWY beginning: TORA 2895 m, TODA 3045 m, ASDA 2895 m; \\n - from TWY L: TORA 2690 m, TODA 2840 m, ASDA 2690 m; \\n - from TWY K: TORA 2525 m, TODA 2675 m, ASDA 2525 m; \\n - from TWY H: TORA 2377 m, TODA 2527 m, ASDA 2377 m; \\n - from TWY G: TORA 2204 m, TODA 2354 m, ASDA 2204 m; - from TWY F: TORA 2004 m, TODA 2154 m, ASDA 2004 m; \\n - from TWY E: TORA 1505 m, TODA 1655 m, ASDA 1505 m; \\n - from TWY V: TORA 1492 m, TODA 1642 m, ASDA 1492 m. \\n During take-off from TWY H, G, F, E, V pilot-in-command is provided with information about TORA. \\n **Procedure of ACFT take-off from RWY 20** \\n One line-up position is AVBL on RWY 20 with the following declared distances from the RWY beginning (TWY Q): \\n - TORA 2500 m, TODA 2650 m, ASDA 2500 m. \\n Before start of taxiing, the flight crew shall report when ready for take-off to ATS unit controller. \\n ATS unit controller assigns exit from the terminal area via the designated SID routes or via the assigned tracks (vectoring). \\n ***Note:*** \\n In the event of an aborted take-off from RWY 20 ACFT shall turn at RWY 02 THR at reduced speed, with flight crew exercising extreme caution. Width of RWY 02\\\/20 turn pad at THR 02 is 60 m.\"],\"Communication Failure\":[],\"Noise Abatement Procedures\":[],\"Regional regulations\":[],\"VFR Procedures\":[]},\"ARRIVAL\":{\"Arrival Routes\":[\"Standard arrival routes are assigned by ATS.\"],\"Aerodrome Minima\":[],\"Holding Procedures\":[],\"Approach\":[\"Flight crew must plan runway vacation along the nearest TWY.\"],\"Runway Occupancy Time\":[\"Flight crew shall plan vacation of the RWY along the nearest TWY or along the TWY recommended by the ATS unit considering landing distance available (for RWY 02 – 2400 m, for RWY 06 – 2745 m)\"],\"Taxiing\":[\"Taxiing after landing must follow ATS instructions. Taxi-in procedures: \\n - Il-62, Tu-204, A-321-200 type ACFT - facing SE, after the “Follow-me” vehicle; \\n - Falcon, Fokker, Global, Gulfstream, other ACFT of the same class with wingspan 32 m or less - by executing a turn through an adjacent vacant stand in the direction of RWY 06\\\/24, heading towards the ground handling specialist providing marshalling services to arriving ACFT; \\n- Mi-8 and class below HEL - in accordance with appropriate chart; \\n- Mi-26 type HEL shall taxi into the stands and execute a turn, or shall taxi into the stands through an adjacent vacant stand; \\n- skid equipped HEL shall air taxi into the stands at minimum height along taxi guide line marking; \\n - in exceptional case, stands are AVBL for parking of B767-300 type ACFT. \"],\"Emergency Landing Procedure\":[],\"Noise Abatement Procedures\":[],\"Low visibility procedures\":[],\"Communication Failure\":[],\"Regional regulations\":[],\"VFR Procedures\":[]},\"MISCELLANIUOS\":{\"Helicopter Operations\":[\"Helicopters must be escorted by a 'Follow-me' vehicle.\"],\"Bird migration\":[],\"Engine Test Runs\":[],\"Visual Docking Guidance Systems\":[],\"Specific Traffic Regulations\":[],\"Schedule maintenance on the runway\":[],\"Positions not visible from control tower\":[],\"Fuel Dumping\":[],\"Warnings\":[]}}"}]}
{"messages":[{"role":"system","content":"прочитай текст всех разделов, создай json файл с переработанным содержанием с установленной в файле структурой, по возможности сократи текст таким образом, чтобы не потерялся смысл, а так же исключи информацию не относящуюся к работе пилота.\n\nИзвлеки части текста и представь ответ как JSON следующего формата:"},{"role":"user","content":"# URSS SOCHI, RUSSIAN FEDERATION\r\n\r\n## LOCAL AERODROME REGULATIONS\r\n\r\n**Stands 57-60** \r\n\r\nStands are AVBL for parking of An-124, Il-96, A-330, A-350, B747 and class below ACFT, parking onto the stands facing SE - after the “Follow-me” vehicle.  \r\n\r\nACFT shall taxi into\/out of the stands under own engines power. \r\n\r\nACFT may taxi into stands 57-59 under own engines power by executing a turn towards RWY 06\/24 through an adjacent vacant stand.  \r\n\r\nAn-124 ACFT may taxi into the stands by executing a turn through adjacent vacant stand. \r\n\r\nACFT shall taxi into stand 60 only when stand 59 is vacant. \r\n\r\n**Stands 61-63** \r\n\r\nStands are designated for parking of HEL, taxiing into\/out of stands - under own engines power. \r\n\r\n**Stand 64**\r\n\r\nStand is AVBL: \r\n\r\n1)for de-icing\/anti-icing treatment of ACFT; \r\n\r\n2)as a quarantine stand; \r\n\r\n3)for ACFT subject to unlawful interference. \r\n\r\nThe stand is AVBL for index 7 ACFT (An-124, Il-96, B747 and its modifications, B777 and its modifications, A-330 and its modifications, A-350-900 ACFT) and below. \r\n\r\nACFT shall taxi into\/out of the stand under own engines power facing north-east and south-west. \r\n\r\nStand 64 is AVBL for ACFT subject to unlawful interference as follows: \r\n\r\n\\- ACFT shall be parked on heading 058° MAG (facing the mountains) when a person, creating a threat of unlawful interference, is present in the cockpit; \r\n\r\n\\- ACFT shall be parked on heading 238° MAG (facing the sea) when a person, creating a threat of unlawful interference, is present in the passenger cabin. \r\n\r\n***Note:** ACFT may be parked not in alignment with the marking by instruction of the AD operator, as directed by head of shift of the airport (or designated persons) for efficient use of the parking space.* \r\n\r\n#### 8. Taxiing – limitations \r\n\r\nDuring movement of ACFT on the aerodrome, for the purpose of safety provision, the responsibility is allocated as outlined below: \r\n\r\n1)“Sochi-Ground” controllers are responsible for accuracy of information about taxi conditions and limitations at the AD, issuing clearance for movement of ACFT along the established route, advising flight crews about ACFT relative positioning, including ACFT proceeding along the same route, when taxiing in low visibility conditions (below 400 m); \r\n\r\n2)pilot-in-command is responsible for observing taxi rules and maintaining a listening watch; \r\n\r\n3)duty specialist of the Follow-me service - for safety during taxiing of ACFT via TWY and along the apron after the “Follow-me” vehicle; \r\n\r\n4)ground handling specialist (providing marshalling services to arriving or departing ACFT) - for safety during parking of ACFT onto the stand, towing of ACFT from the stand to the engines start-up position, taxiing of ACFT out of the stand and from the start-up position. \r\n\r\nAssistance of the “Follow-me” vehicle is provided upon request of the flight crew. \r\n\r\n**Taxi-in procedure for ACFT not equipped with a tow bar** \r\n\r\n Stands 36-38 are AVBL for parking of: \r\n\r\n\\- index 1 ACFT (with wingspan 24 m or less) on heading 148° MAG - under own engines power, at idle power under the supervision of the ground handling specialist providing marshalling services to arriving ACFT, by executing a right or a left turn within dimensions of one stand, or after the “Follow-me” vehicle; \r\n\r\n\\- index 2 ACFT (with wingspan 32 m or less) on heading 148° MAG - under own engines power, at idle power under the supervision of the ground handling specialist providing marshalling services to arriving ACFT, by executing a right or a left turn through an adjacent vacant stand, or after the “Follow-me” vehicle. \r\n\r\n***Note:*** \r\n\r\n1.Stands 10, 11 are AVBL for parking of all modifications of Tu-154 ACFT and class below ACFT in order to provide operation of VIP flights. \r\n\r\n2.Taxiing of ACFT via TWY C shall be executed at reduced speed strictly along taxiway centre line at idle power. \r\n\r\n3.Il-96, Il-86, Il-76, Tu-204, B737, B757, B767 type ACFT shall taxi via TWY A after landing and into stand 1 under own engines power. After parking on the stand and unloading passengers, turn onto heading 148° MAG shall be executed by tow truck.  \r\n\r\n4.Taxiing of ACFT with a wingspan of 35 m and more from stand 1 via TWY M to TWY C shall be cleared when stands 5, 6, 7, 8, 9 are vacant. \r\n\r\n5.Turn at RWY 20 THR shall be carried out at reduced speed, with flight crew exercising extreme caution. \r\n\r\n6.Engines start-up and taxiing to runway-holding position from stands 1-22, 33-38 are permitted for index 1 ACFT (with wingspan of 24 m or less, mass of 20 tons or less) and HEL. \r\n\r\n7.Taxiing for take-off and RWY vacation after landing shall be executed with increased caution of the flight crew at reduced speed at idle power of engines. \r\n\r\n8.Taxiing speed shall be chosen by the pilot-in-command. \r\n\r\n**WARNINGS:** \r\n\r\nWithin an area from the limit of graded portion of a runway strip to runway strip boundary (150 m from runway centre line) of RWY 06\/24, there are objects (lighting poles), located at a distance from 72 m to 150 m south of runway centre line and at a distance from 90 m to 150 m north of runway centre line. \r\n\r\nWithin an area from the limit of graded portion of a runway strip to runway strip boundary (150 m from runway centre line) of RWY 02\/20, there are objects (lighting poles, building), located at a distance from 93 m to 150 m south of runway centre line and at a distance from 82 m to 150 m north of runway centre line.  \r\n\r\n\r\n\r\n**The following is PROHIBITED:** \r\n\r\n\\- taxiing of ACFT with a wingspan of above 36 m via TWY M (from TWY C to stand 20); \r\n\r\n\\- taxiing of ACFT with a wingspan of above 45 m by towing to TWY M from stand 23 when stand 22 is occupied; \r\n\r\n\\- taxiing of ACFT with a wingspan of above 57 m via TWY Y along stand 64 when stand 64 is occupied; \r\n\r\n\\- simultaneous taxiing of ACFT via TWY M (from stand 23 to stand 38) and via taxi route N1 on Apron 1 for ACFT with a wingspan of above 42 m; \r\n\r\n\\- simultaneous taxiing of ACFT via TWY M (from TWY H to TWY L) and via TWY N for ACFT with a wingspan of above 56 m; \r\n\r\n\\- taxiing of ACFT with a wingspan of above 55 m via taxi route Y1 along stand 39, when stand 39 is occupied; \r\n\r\n\\- taxiing of ACFT with a wingspan of above 57 m via taxi route Y1 along stands 40-53, when stands 40-53 are occupied; \r\n\r\n\\- taxiing of ACFT with a wingspan of above 43 m via taxi route Y1 along stands 54-56, when stands 54-56 are occupied; \r\n\r\n\\- taxiing of ACFT with a wingspan of above 61 m via taxi route T3 along stands 57-60, when stands 57-60 are occupied; \r\n\r\n\\- taxiing of ACFT with a wingspan of above 61 m via taxi route T2, when stand 60 is occupied; \r\n\r\n\\- presence and movement of special vehicles and mechanical means via the road for special vehicles (on the south side of stands 5-22, on the north side of stands 39-56, on the south side of stands 57-60) towards taxiing ACFT during taxiing via TWY M along stands 5-22 and Apron 2 via taxi routes Y1 and T3; \r\n\r\n\\- taxiing of index 6 ACFT (wingspan of 42-60 m) via TWY M when stand 20 is occupied by Il-86, Il-76 ACFT; \r\n\r\n\\- taxiing of index 6 ACFT (wingspan of 42-60 m) from stand 1 via TWY M when stands 5-22 are occupied by Tu-154, Tu-134, Yak-42 ACFT; \r\n\r\n\\- presence of ACFT with a wingspan of above 56 m at runway-holding positions near RWY 02\/20 on TWY P, Q during execution of take-off\/landing operations on RWY 02\/20. \r\n\r\n#### 9. Removal of disabled aircraft \r\n\r\nSee appropriate chart. \r\n\r\n#### 10. Training and practice flights, technical test flights \r\n\r\nTraining and practice flights, technical test flights are conducted in accordance with rules and procedures established in the regulatory documents. \r\n\r\n#### 11. Use of the runway \r\n\r\n**Two RWY system operation** \r\n\r\nThe following options are established to provide two RWY system operations: \r\n\r\n1)basic: RWY 02 is used for arrival, RWY 24 is used for departure; \r\n\r\n2)option NR 1: RWY 06 is used for arrival, RWY 20 is used for departure; \r\n\r\n3)option NR 2: RWY 06 is used for arrival, RWY 24 is used for departure; \r\n\r\n4)option NR 3: RWY 02 is used for arrival, RWY 20 is used for departure; \r\n\r\n5)option NR 4: RWY 02 and RWY 06 are used for arrival; \r\n\r\n6)option NR 5: RWY 20 and RWY 24 are used for departure. \r\n\r\nWhen take-off is executed from RWY 24 from TWYs K, H, G, F, RWY 02 can be used for landing. \r\n\r\n**Departure procedures when using one active RWY** \r\n\r\nIn case when only RWY 06\/24 is active and ACFT is arriving on the opposite course, only LAMET 1D, LA 1S, ADNET 1S, IRGID 1S SIDs shall be used to join ATS routes as instructed by controller during clearance issuance. \r\n\r\nTo pass TABAN, climb straight ahead to 600 ft\/(180) m or above after take-off, at a distance not closer than D5.6 ADL turn LEFT and proceed directly to TABAN as instructed by controller during clearance issuance. \r\n\r\nIn case when only RWY 02\/20 is active and ACFT is arriving on the opposite course, only LAMET 1X, LA 1X, ADNET 1X, IRGID 1X, TABAN 1C SIDs shall be used to join ATS routes as instructed by controller during clearance issuance. \r\n\r\nTo pass TABAN climb straight ahead to 600 ft\/(180) M or above after take-off, at a distance not closer than D5.6 ADL turn LEFT and proceed directly to TABAN as instructed by controller during clearance issuance. \r\n\r\n#### 12. Helicopter traffic – limitation \r\n\r\nHelicopters shall join routes KЛ 622, KЛ 693, KR 846 via established VFR departure routes under control of appropriate ATS units. \r\n\r\nWidth of the above mentioned routes in the service area of Sochi LCU is 1-2 km (0.5-1.1 NM). \r\n\r\nArrival to the AD shall be executed in accordance with the established VFR arrival routes. \r\n\r\n**WARNINGS**\r\n\r\nIf RWY is occupied (or other ACFT execute approach), ACFT shall proceed to the holding area. \r\n\r\nFlight via routes KЛ 622, KЛ 693 through the restricted area URR501 are subject to clearance of the administration of the Caucasus State Nature Biosphere Reserve, except for ACFT, executing Head of State and official delegation flights. \r\n\r\nEntry into URR501 area shall be carried out via routes assigned in accordance with requests for flight operations. Flight operations in URR501 area below altitude (height) 6600'\/2000 m AGL without clearance of the administration of the Caucasus State Nature Biosphere Re-serve are PROHIBITED.  \r\n\r\nBy-passing of prohibited areas URP105, URP106 shall be carried out via route KR 846. Head of State flights (official delegation flights) in areas URP105, URP106 are permitted.  \r\n\r\n#### 13. Flight operations at helipad “Helicopter complex NR 1” \r\n\r\nVFR flights of HEL to\/from Helicopter complex NR 1 helipad are carried out H24. \r\n\r\nDepartures (arrivals) of HEL are executed in accordance with the established VFR departure (arrival) routes. \r\n\r\n\r\n\r\n\r\n\r\n**Arrival** \r\n\r\nWhen approaching the AD and establishing visual contact with the helipad, flight crew shall: \r\n\r\n\\- request ATS clearance for execution of approach and landing on helipad at own discretion (as on landing site, selected during the flight); \r\n\r\n\\- after obtaining controller’s clearance, flight crew shall execute approach to helipad (depending on direction of approach and actual wind) and vertical landing out of ground effect. \r\n\r\nPilot-in-command is responsible for the safety of landing from the moment the decision to execute approach is taken until landing.   \r\n\r\n**Taxiing to and from stands. Taxiing – limitations** \r\n\r\nAfter landing (for take-off) HEL shall taxi into\/out of stands under tow. If required, taxiing of helicopter under own engines power is permitted under control of ground personnel strictly along the taxi route, maintaining obstacle clearance of not less than half of main rotor diameter (but not less than 10 m).  \r\n\r\n**Removal of disabled aircraft** \r\n\r\nDisabled aircraft are removed by towing. Hydraulic jack can be used, if required.  \r\n\r\n**Parking area for helicopters** \r\n\r\n7 (seven) stands for HEL with dimensions up to 26 m are AVBL on apron of helipad “Helicopter complex NR 1”. Stands are numbered from 1 to 7 and provided with stands and taxi routes marking.   \r\n\r\n**Apron of helipad “Helicopter complex NR 1”** \r\n\r\nApron of helipad “Helicopter complex NR 1” is connected to apron 2 of Sochi AD by exit taxiway (CLSD, temporarily not used). Apron dimensions: 226 x 70 m, PCN 23\/R\/A\/W\/T.  \r\n\r\nStart-up and run-up of HEL engines are permitted on the apron, if adjacent stands are vacant and safe distance to obstacles is provided. \r\n\r\n**Training flights, technical test flights, use of the helipad “Helicopter complex NR 1”** \r\n\r\nTraining and practice flights, technical test flights are executed by arrangement with ATS unit in accordance with the submitted request and obtained clearance for the use of airspace. \r\n\r\n**Helicopter traffic – limitation on helipad “Helicopter complex NR 1”** \r\n\r\nDuring take-off (landing) of HEL it is PROHIBITED: \r\n\r\n\\- to overfly the adjoining occupied TLOF; \r\n\r\n\\- to overfly the state aviation apron. \r\n\r\nTake-off from helipad “Helicopter complex NR 1” is executed after obtaining clearance of Sochi AD ATS unit.  \r\n\r\n***Notes:*** \r\n\r\n*If unable to execute landing on helipad “Helicopter complex NR 1”, flight crew shall land at Sochi AD or proceed to an alternate aerodrome. If unable to proceed to an alternate AD, HEL shall land on the landing site, selected during the flight.*  "},{"role":"assistant","content":"{\"GENERAL\":{\"Airport regulations\":[\"Stands 57-60 available for parking of specific aircraft types, taxiing under own power.\",\"Stands 61-63 designated for helicopter parking, taxiing under own power.\",\"Stand 64 available for de-icing, quarantine, and unlawful interference procedures.\"],\"Schedule coordination\":[],\"Ground Movement\":{\"Apron Procedures\":[\"**Stands 57-60** \\n Stands are AVBL for parking of An-124, Il-96, A-330, A-350, B747 and class below ACFT, parking onto the stands facing SE - after the “Follow-me” vehicle.  \\n ACFT shall taxi into\\\/out of the stands under own engines power. \\n ACFT may taxi into stands 57-59 under own engines power by executing a turn towards RWY 06\\\/24 through an adjacent vacant stand.  \\n An-124 ACFT may taxi into the stands by executing a turn through adjacent vacant stand. \\n ACFT shall taxi into stand 60 only when stand 59 is vacant. \\n **Stands 61-63** \\n Stands are designated for parking of HEL, taxiing into\\\/out of stands - under own engines power. \\n **Stand 64** \\n Stand is AVBL: \\n 1)for de-icing\\\/anti-icing treatment of ACFT; \\n 2)as a quarantine stand; \\n 3)for ACFT subject to unlawful interference. \\n The stand is AVBL for index 7 ACFT (An-124, Il-96, B747 and its modifications, B777 and its modifications, A-330 and its modifications, A-350-900 ACFT) and below. \\n ACFT shall taxi into\\\/out of the stand under own engines power facing north-east and south-west. \\n Stand 64 is AVBL for ACFT subject to unlawful interference as follows: \\n - ACFT shall be parked on heading 058° MAG (facing the mountains) when a person, creating a threat of unlawful interference, is present in the cockpit; \\n- ACFT shall be parked on heading 238° MAG (facing the sea) when a person, creating a threat of unlawful interference, is present in the passenger cabin. \\n ***Note:** ACFT may be parked not in alignment with the marking by instruction of the AD operator, as directed by head of shift of the airport (or designated persons) for efficient use of the parking space.* \"],\"Towing of ACFT\":[],\"Taxiing\":[\"Taxiing – limitations \\n During movement of ACFT on the aerodrome, for the purpose of safety provision, the responsibility is allocated as outlined below: \\n 1)“Sochi-Ground” controllers are responsible for accuracy of information about taxi conditions and limitations at the AD, issuing clearance for movement of ACFT along the established route, advising flight crews about ACFT relative positioning, including ACFT proceeding along the same route, when taxiing in low visibility conditions (below 400 m); \\n 2)pilot-in-command is responsible for observing taxi rules and maintaining a listening watch; \\n 3)duty specialist of the Follow-me service - for safety during taxiing of ACFT via TWY and along the apron after the “Follow-me” vehicle; \\n 4)ground handling specialist (providing marshalling services to arriving or departing ACFT) - for safety during parking of ACFT onto the stand, towing of ACFT from the stand to the engines start-up position, taxiing of ACFT out of the stand and from the start-up position. \\n Assistance of the “Follow-me” vehicle is provided upon request of the flight crew. \\n **Taxi-in procedure for ACFT not equipped with a tow bar** \\n Stands 36-38 are AVBL for parking of: \\n- index 1 ACFT (with wingspan 24 m or less) on heading 148° MAG - under own engines power, at idle power under the supervision of the ground handling specialist providing marshalling services to arriving ACFT, by executing a right or a left turn within dimensions of one stand, or after the “Follow-me” vehicle; \\n- index 2 ACFT (with wingspan 32 m or less) on heading 148° MAG - under own engines power, at idle power under the supervision of the ground handling specialist providing marshalling services to arriving ACFT, by executing a right or a left turn through an adjacent vacant stand, or after the “Follow-me” vehicle. \\n***Note:*** \\n 1.Stands 10, 11 are AVBL for parking of all modifications of Tu-154 ACFT and class below ACFT in order to provide operation of VIP flights. \\n 2.Taxiing of ACFT via TWY C shall be executed at reduced speed strictly along taxiway centre line at idle power. \\n 3.Il-96, Il-86, Il-76, Tu-204, B737, B757, B767 type ACFT shall taxi via TWY A after landing and into stand 1 under own engines power. After parking on the stand and unloading passengers, turn onto heading 148° MAG shall be executed by tow truck.  \\n 4.Taxiing of ACFT with a wingspan of 35 m and more from stand 1 via TWY M to TWY C shall be cleared when stands 5, 6, 7, 8, 9 are vacant. \\n 5.Turn at RWY 20 THR shall be carried out at reduced speed, with flight crew exercising extreme caution. \\n 6.Engines start-up and taxiing to runway-holding position from stands 1-22, 33-38 are permitted for index 1 ACFT (with wingspan of 24 m or less, mass of 20 tons or less) and HEL. \\n 7.Taxiing for take-off and RWY vacation after landing shall be executed with increased caution of the flight crew at reduced speed at idle power of engines. \\n 8.Taxiing speed shall be chosen by the pilot-in-command. \\n **WARNINGS:** \\n Within an area from the limit of graded portion of a runway strip to runway strip boundary (150 m from runway centre line) of RWY 06\\\/24, there are objects (lighting poles), located at a distance from 72 m to 150 m south of runway centre line and at a distance from 90 m to 150 m north of runway centre line. \\n Within an area from the limit of graded portion of a runway strip to runway strip boundary (150 m from runway centre line) of RWY 02\\\/20, there are objects (lighting poles, building), located at a distance from 93 m to 150 m south of runway centre line and at a distance from 82 m to 150 m north of runway centre line. \\n **The following is PROHIBITED:** \\n- taxiing of ACFT with a wingspan of above 36 m via TWY M (from TWY C to stand 20); \\n- taxiing of ACFT with a wingspan of above 45 m by towing to TWY M from stand 23 when stand 22 is occupied; \\n- taxiing of ACFT with a wingspan of above 57 m via TWY Y along stand 64 when stand 64 is occupied; \\n- simultaneous taxiing of ACFT via TWY M (from stand 23 to stand 38) and via taxi route N1 on Apron 1 for ACFT with a wingspan of above 42 m; \\n- simultaneous taxiing of ACFT via TWY M (from TWY H to TWY L) and via TWY N for ACFT with a wingspan of above 56 m; \\n- taxiing of ACFT with a wingspan of above 55 m via taxi route Y1 along stand 39, when stand 39 is occupied; \\n- taxiing of ACFT with a wingspan of above 57 m via taxi route Y1 along stands 40-53, when stands 40-53 are occupied; \\n- taxiing of ACFT with a wingspan of above 43 m via taxi route Y1 along stands 54-56, when stands 54-56 are occupied; \\n - taxiing of ACFT with a wingspan of above 61 m via taxi route T3 along stands 57-60, when stands 57-60 are occupied; \\n - taxiing of ACFT with a wingspan of above 61 m via taxi route T2, when stand 60 is occupied; \\n- presence and movement of special vehicles and mechanical means via the road for special vehicles (on the south side of stands 5-22, on the north side of stands 39-56, on the south side of stands 57-60) towards taxiing ACFT during taxiing via TWY M along stands 5-22 and Apron 2 via taxi routes Y1 and T3; \\n - taxiing of index 6 ACFT (wingspan of 42-60 m) via TWY M when stand 20 is occupied by Il-86, Il-76 ACFT; \\n - taxiing of index 6 ACFT (wingspan of 42-60 m) from stand 1 via TWY M when stands 5-22 are occupied by Tu-154, Tu-134, Yak-42 ACFT; \\n - presence of ACFT with a wingspan of above 56 m at runway-holding positions near RWY 02\\\/20 on TWY P, Q during execution of take-off\\\/landing operations on RWY 02\\\/20.  \"],\"Removal of disabled aircraft\":\"Disabled aircraft are removed by towing. See appropriate chart. \"},\"Use of APU\":[],\"Use of Runways\":[\"**Two RWY system operation** \\n The following options are established to provide two RWY system operations: \\n 1)basic: RWY 02 is used for arrival, RWY 24 is used for departure; \\n 2)option NR 1: RWY 06 is used for arrival, RWY 20 is used for departure; \\n 3)option NR 2: RWY 06 is used for arrival, RWY 24 is used for departure; \\n 4)option NR 3: RWY 02 is used for arrival, RWY 20 is used for departure; \\n 5)option NR 4: RWY 02 and RWY 06 are used for arrival; \\n 6)option NR 5: RWY 20 and RWY 24 are used for departure. \\n When take-off is executed from RWY 24 from TWYs K, H, G, F, RWY 02 can be used for landing. \\n **Departure procedures when using one active RWY** \\n In case when only RWY 06\\\/24 is active and ACFT is arriving on the opposite course, only LAMET 1D, LA 1S, ADNET 1S, IRGID 1S SIDs shall be used to join ATS routes as instructed by controller during clearance issuance. \\n To pass TABAN, climb straight ahead to 600 ft\\\/(180) m or above after take-off, at a distance not closer than D5.6 ADL turn LEFT and proceed directly to TABAN as instructed by controller during clearance issuance. \\n In case when only RWY 02\\\/20 is active and ACFT is arriving on the opposite course, only LAMET 1X, LA 1X, ADNET 1X, IRGID 1X, TABAN 1C SIDs shall be used to join ATS routes as instructed by controller during clearance issuance. \\n To pass TABAN climb straight ahead to 600 ft\\\/(180) M or above after take-off, at a distance not closer than D5.6 ADL turn LEFT and proceed directly to TABAN as instructed by controller during clearance issuance. \"],\"Low visibility procedures\":[\"Controllers responsible for taxi conditions in low visibility.\",\"Pilots must maintain a listening watch.\"],\"Procedures for IFR flights\":[],\"ATS surveillance procedures\":[],\"Noise Abatement Procedures\":[],\"Regional regulations\":[],\"ATIS\":[],\"VFR Procedures\":[]},\"DEPARTURE\":{\"A-CDM\":[],\"Start-up Procedures\":[],\"Push-back procedures\":[],\"De\\\/anti-icing\":[\"De-icing procedures available at Stand 64.\"],\"Low visibility procedures\":[],\"Taxiing\":[\"Taxiing procedures for various aircraft types outlined.\"],\"Runway Occupancy Time\":[],\"Simultaneous Line-Up\":[],\"Take-Off\":[\"Take-off procedures vary based on active runway.\"],\"Continued Take-Off\":[],\"Departure Procedures\":[],\"Communication Failure\":[],\"Noise Abatement Procedures\":[],\"Regional regulations\":[],\"VFR Procedures\":[]},\"ARRIVAL\":{\"Arrival Routes\":[],\"Aerodrome Minima\":[],\"Holding Procedures\":[],\"Approach\":[\"Approach procedures include radar and non-radar control.\"],\"Runway Occupancy Time\":[],\"Taxiing\":[\"Taxiing procedures for arriving aircraft outlined.\"],\"Emergency Landing Procedure\":[],\"Noise Abatement Procedures\":[],\"Low visibility procedures\":[],\"Communication Failure\":[],\"Regional regulations\":[],\"VFR Procedures\":[]},\"MISCELLANIUOS\":{\"Helicopter Operations\":[\"Helicopters shall join routes KЛ 622, KЛ 693, KR 846 via established VFR departure routes under control of appropriate ATS units. \\n Width of the above mentioned routes in the service area of Sochi LCU is 1-2 km (0.5-1.1 NM). Arrival to the AD shall be executed in accordance with the established VFR arrival routes.\\n Flight operations at helipad “Helicopter complex NR 1” \\n VFR flights of HEL to\\\/from Helicopter complex NR 1 helipad are carried out H24. \\n Departures (arrivals) of HEL are executed in accordance with the established VFR departure (arrival) routes. \\n **Arrival** \\n When approaching the AD and establishing visual contact with the helipad, flight crew shall: \\n- request ATS clearance for execution of approach and landing on helipad at own discretion (as on landing site, selected during the flight); \\n- after obtaining controller’s clearance, flight crew shall execute approach to helipad (depending on direction of approach and actual wind) and vertical landing out of ground effect. \\n Pilot-in-command is responsible for the safety of landing from the moment the decision to execute approach is taken until landing. \\n **Taxiing to and from stands. Taxiing – limitations** \\n After landing (for take-off) HEL shall taxi into\\\/out of stands under tow. If required, taxiing of helicopter under own engines power is permitted under control of ground personnel strictly along the taxi route, maintaining obstacle clearance of not less than half of main rotor diameter (but not less than 10 m). \\n**Removal of disabled aircraft** \\n Disabled aircraft are removed by towing. Hydraulic jack can be used, if required.  \\n **Parking area for helicopters** \\n 7 (seven) stands for HEL with dimensions up to 26 m are AVBL on apron of helipad “Helicopter complex NR 1”. Stands are numbered from 1 to 7 and provided with stands and taxi routes marking. \\n **Apron of helipad “Helicopter complex NR 1”** \\n Apron of helipad “Helicopter complex NR 1” is connected to apron 2 of Sochi AD by exit taxiway (CLSD, temporarily not used). Apron dimensions: 226 x 70 m, PCN 23\\\/R\\\/A\\\/W\\\/T. \\n Start-up and run-up of HEL engines are permitted on the apron, if adjacent stands are vacant and safe distance to obstacles is provided. \\n **Training flights, technical test flights, use of the helipad “Helicopter complex NR 1”** \\n Training and practice flights, technical test flights are executed by arrangement with ATS unit in accordance with the submitted request and obtained clearance for the use of airspace. \\n **Helicopter traffic – limitation on helipad “Helicopter complex NR 1”** \\n During take-off (landing) of HEL it is PROHIBITED: \\n- to overfly the adjoining occupied TLOF; \\n- to overfly the state aviation apron. \\n Take-off from helipad “Helicopter complex NR 1” is executed after obtaining clearance of Sochi AD ATS unit.\\n ***Notes:*** \\n *If unable to execute landing on helipad “Helicopter complex NR 1”, flight crew shall land at Sochi AD or proceed to an alternate aerodrome. If unable to proceed to an alternate AD, HEL shall land on the landing site, selected during the flight.*  \"],\"Bird migration\":[],\"Engine Test Runs\":[],\"Visual Docking Guidance Systems\":[],\"Specific Traffic Regulations\":[\"Training and practice flights, technical test flights Training and practice flights, technical test flights are conducted in accordance with rules and procedures established in the regulatory documents. \"],\"Schedule maintenance on the runway\":[],\"Positions not visible from control tower\":[],\"Fuel Dumping\":[],\"Warnings\":[\"If RWY is occupied (or other ACFT execute approach), ACFT shall proceed to the holding area. \\n Flight via routes KЛ 622, KЛ 693 through the restricted area URR501 are subject to clearance of the administration of the Caucasus State Nature Biosphere Reserve, except for ACFT, executing Head of State and official delegation flights. \\n Entry into URR501 area shall be carried out via routes assigned in accordance with requests for flight operations. Flight operations in URR501 area below altitude (height) 6600'\\\/2000 m AGL without clearance of the administration of the Caucasus State Nature Biosphere Re-serve are PROHIBITED.  \\n By-passing of prohibited areas URP105, URP106 shall be carried out via route KR 846. Head of State flights (official delegation flights) in areas URP105, URP106 are permitted.\"]}}"}]}
{"messages":[{"role":"system","content":"прочитай текст всех разделов, создай json файл с переработанным содержанием с установленной в файле структурой, по возможности сократи текст таким образом, чтобы не потерялся смысл, а так же исключи информацию не относящуюся к работе пилота.\n\nИзвлеки части текста и представь ответ как JSON следующего формата:"},{"role":"user","content":"# URSS SOCHI, RUSSIAN FEDERATION\r\n\r\n## FLIGHT PROCEDURES\r\n\r\n#### General provisions\r\n\r\nDuring flights within Sochi AD CTR and CTA flight crew must: \r\n\r\n\\- have ATS unit clearance, obtained before entry to relevant area of responsibility; \r\n\r\n\\- report position by ATS unit request; \r\n\r\n\\- follow instructions of the relevant ATS units; \r\n\r\n\\- have and constantly maintain two-way radio communication on VHF range; \r\n\r\n\\- have HF range and ADF medium frequency range radio equipment, allowing to monitor ATS unit instructions to provide back-up in case of VHF equipment failure; \r\n\r\n\\- have and constantly keep running ACFT transponder. \r\n\r\nArriving ACFT, which are on the final approach segment, have priority over departing ACFT. \r\n\r\nApproach and landing shall be executed only on RWY 06 and RWY 02, excluding helicopters executing VFR flights. \r\n\r\nTake-off shall be executed only from RWY 24 and RWY 20, excluding helicopters executing VFR flights. \r\n\r\n**Flight crew shall request clearance for pushback\/towing when ground personnel and towing tractor are ready to commence the procedure. After obtaining clearance for pushback\/towing from stand, the flight crew shall commence the procedure immediately.** \r\n\r\nIn case of necessity of extra time for pushback\/ towing commencement after obtaining clearance from ATS unit (more than 1 minute), flight crew shall inform ATS unit about it. If more than 1 minute passed after issuance of pushback\/towing clearance and flight crew has not commenced the procedure, flight crew must request a new clearance for pushback\/towing. \r\n\r\nСlearance to taxi to the runway-holding position shall be requested by the flight crew reporting TWY number, in case the flight crew is ready to take off not from the RWY beginning. \r\n\r\nIn case of necessity of long RWY occupation (more than 1 minute), before occupation flight crew shall inform ATS unit of time, required for take-off preparation. If more than 1 minute passed after issuance of take-off clearance, flight crew must request a new clearance for take-off. \r\n\r\n#### Basic operating mode of AD \r\n\r\nDeparture from RWY 24 and Arrival on RWY 02 is preferential mode which, if possible, is used to the maximum. \r\n\r\nRNAV SID and RNAV STAR are basic procedures at the aerodrome: \r\n\r\n\\- RWY 24 SID – with “Delta” designator; \r\n\r\n\\- RWY 02 STAR – with “Kilo” designator; \r\n\r\n\\- RWY 20 SID – with “Charlie” designator; \r\n\r\n\\- RWY 06 STAR – with “Lima” designator. \r\n\r\nWhen departing to GUBOR, SID via IRGID is recommended for use due to opposite traffic via BINOL. \r\n\r\nWhen departing via LAMET, use airways and requirements for minimum crossing altitude for the following points: \r\n\r\n\\- A 277 – LAMET\/FL060; \r\n\r\n\\- G 352 – LAMET\/FL060; \r\n\r\n\\- G 487 – LAMET\/FL220; \r\n\r\n\\- R 230 – LAMET\/FL280. \r\n\r\n\r\nWhen departing via TABAN, use airways and requirements for minimum crossing height for the following points: N 166 – TABAN\/FL060, B 147 – TABAN\/FL210. \r\n\r\nWithin “Sochi-Radar” responsibility area (aerodrome control service), 5 km (2.7 NM) minimum interval of horizontal separation is established, 10 km (5.4 NM) minimum interval of horizontal separation is established as follows: \r\n\r\n\\- ACFT proceeds after ACFT, which mass is 136000 KG and more; \r\n\r\n\\- ACFT passes the wake of ACFT, which mass is 136000 KG and more; \r\n\r\n\\- ACFT, succeeding ACFT, which mass is 136000 KG and more, uses the same RWY. \r\n\r\nWhen ACFT is completely ready for departure, flight crew shall request clearance for engine start-up and taxiing (towing) from “Sochi-Ground”, reporting stand number, code letter of ATIS information, SIGMET information, when ready to take off not from the RWY beginning – runway-holding position (TWY), and turn ACFT transponder on. \r\n\r\nFlight crew may start engines during ACFT towing, if this procedure is indicated by the Aeroplane Flight Manual and approved by the technical personnel of the tow team. \r\n\r\n***Note:*** \r\n\r\nAircraft completely ready for departure means, that all pre-flight procedures are completed (including border and customs control when executing international flight), all passengers are on board, entrance and cargo doors are closed, stairs removed (aerobridge is disconnected and is in a retracted position), tow bar is connected (when towing is required), ground personnel is ready for towing (taxiing) and has established radio communication with flight crew. \r\n\r\n“Sochi-Ground” controller issues clearance for ACFT to start movement towards runway-holding position, assigning taxi route and taxi instructions. \r\n\r\nEngine warm-up is cleared to execute on TWY M or RWY by clearance of “Sochi-Ground” controller or “Sochi-Start” controller respectively. \r\n\r\n#### Flight operations using QNH pressure \r\n\r\nATS unit assigns and flight crew shall maintain altitudes below the transition level in feet based upon QNH pressure. If necessary, any altitude, not below safe altitude, divisible by 100 feet may be assigned. \r\n\r\nThe value of aerodrome QNH pressure in hPa is transmitted in ATIS broadcast. Flight crew of ACFT, not equipped for maintaining altitude in feet based upon QNH pressure, must have information, contained in conversion tables, to execute flights at altitudes below transition level. QFE pressure is issued by the ATS unit upon request of flight crew only. \r\n\r\nWhen executing VFR flights below the lower safe flight level, ACFT shall execute flights at altitudes based upon QNH pressure, divisible by 1000 feet. If necessary, any altitude, not below safe altitude, divisible by 100 feet may be assigned. \r\n\r\nWhen executing flights below the lower safe flight level, pressure scale of barometric altimeter shall be changed from area QNH to aerodrome QNH during entry to CTR (radius of 20 km (10.8 NM) from ARP), pressure scale of barometric altimeter shall be changed from aerodrome QNH to area QNH during exit from CTR. \r\n\r\n#### Low visibility procedures \r\n\r\nLow visibility procedures (LVP) are applied when RVR is less than 550 m to prevent collision of ACFT and are implemented by the Flight Control Officer, informing aerodrome operator (authorized representative of operator) and flight crews. \r\n\r\nSochi AD is not approved for category II, III precision approach operations. \r\n\r\nSochi AD is approved for take-off from RWY 24 and RWY 20, when visibility is 300 m in the day-time and 400 m at night. \r\n\r\nWhen LVP are in force, control over ACFT movement on the manoeuvring area shall be executed as follows: \r\n\r\n\\- using A-SMGCS (Advanced Surface Movement Guidance and Control System) “Vega“; \r\n\r\n\\- via instructions issued by controller; \r\n\r\n\\- via reports of the flight crew; \r\n\r\n\\- via reports of the duty specialist of the «Follow-me» service. \r\n\r\nWhen LVP are in force, presence of more than one ACFT on the RWY used for take-off is PROHIBITED. \r\n\r\nLVP are cancelled by the Flight Control Officer when RVR is 550 m or above. \r\n\r\n#### Procedures for low visibility operations \r\n\r\nLVP are applied: \r\n\r\n\\- to prevent ACFT collision in conditions of low visibility; \r\n\r\n\\- to protect critical areas of ILS localizer and ILS glide path localizer. \r\n\r\nATS unit, directing ACFT movement at the aerodrome, informs flight crews on position of ACFT, relative to each other, including those which move along the same route. \r\n\r\nTaxiing at night and in the day-time when visibility is less than 2000 m shall be executed with navigation lights and taxi lamps switched on. \r\n\r\nACFT taxiing shall be executed under the direction of “Sochi-Ground” controller only after “Follow-me“ vehicle, equipped with “ground-to-air“ and “ground-to-ground“ two-way radio communication, flashing lights and “Follow me“ display, strictly along the centre line regardless of ACFT parking area to the marking line of runway-holding position, when TWY and RWY lighting equipment is turned on. \r\n\r\nFlight crew shall report presence of the “Follow-me” vehicle in front of the ACFT to “Sochi-Ground” controller. \r\n\r\nIf obstacles are detected on taxi-route, flight crew must take measures to avoid collision and report it to ATS unit.  \r\n\r\nTaxiing speed shall be chosen by the flight crew depending on condition of apron and TWY surface, visibility conditions and presence of obstacles. \r\n\r\nResponsibility for assignment of taxi routes on the manoeuvring area is placed on “Sochi-Ground” and “Sochi-Start” controllers within the areas of their responsibilities. \r\n\r\n**Departure** \r\n\r\nFlight crews shall request start-up clearance when ready for start-up, reporting ACFT stand number. After obtaining tow or taxi clearance from “Sochi-Ground” controller, ACFT must vacate the stand immediately. \r\n\r\nWhen taxiing along the apron and manoeuvring area flight crew must constantly check ACFT position, especially at TWY intersections, to make sure that taxiing is executed in conditions of complete safety. In case of safety related difficulties or doubts, it is required to stop taxiing and report to “Sochi-Ground” controller. \r\n\r\nTransfer of control from “Sochi-Ground” controller to “Sochi-Start” controller shall be carried out at the runway-holding position (ILS critical area) marking. \r\n\r\n When LVP are in force, the following is PROHIBITED: \r\n\r\n\\- to cross the runway-holding position limit (ILS critical area) displayed by the established day marking without clearance of “Sochi-Start” controller; \r\n\r\n\\- to take off not from the RWY beginning; \r\n\r\n\\- to take off without stop at the line-up position. \r\n\r\nFlight crew should read back all instructions of “Sochi-Ground” and “Sochi-Start” controllers, when holding at the RWY. \r\n\r\nAfter obtaining line-up clearance, flight crew shall start taxiing. \r\n\r\n**Arrival** \r\n\r\nWhen LVP are in force – landing is PROHIBITED. **RWY and appropriate equipment approved to support low visibility procedures** \r\n\r\nATS unit ensures that information on LVP validity is included in\/excluded from ATIS broadcast. LVP are implemented using the phrase: *“Low visibility procedures in progress, check your minimum”*. LVP are implemented by the Flight Control Officer reporting it to AD operator (operator’s representative) and flight crews. \r\n\r\n**Weather conditions for LVP application** \r\n\r\nLVP are implemented when RVR is below 550 m at least at one of six observation points on both RWY. \r\n\r\nLVP are cancelled when RVR is 550 m or above at all observation points on both RWY. \r\n\r\n**Description of ground marking signs\/lighting for use in accordance with LVP** \r\n\r\nILS critical area marking and runway-holding position marking are displayed on TWY А, B, C, D, E, F, G, H, K, L, N, P, Q. Runway-holding position marking on TWY A, B, C, D, E, F, G, H, K, L, N, P, Q coincides with ILS critical area marking. RWY 06\/24 is equipped with RWY guard lights (yellow clearance bars). \r\n\r\n#### Procedures for IFR flights \r\n\r\nFlight operations in the terminal area of the AD are conditioned by close location of prohibited areas URP105, URP106, close proximity of the state border and mountainous area with elevation above 3000 m AMSL. \r\n\r\nAll SID, STAR and approach procedures of Sochi AD are based on RNAV 1 specification using GNSS. \r\n\r\nACFT operating flights in Sochi CTA shall proceed along area navigation routes, established flight routes, SID and STAR applying “Direct to” procedure and via tracks assigned by ATS unit by vectoring. \r\n\r\nBefore requesting engines start-up, tow clearance, flight crew must report stand number, latest ATIS broadcast code letter and obtain departure instructions, SSR transponder code. \r\n\r\n**Departure** \r\n\r\nACFT flight shall be operated in accordance with the flight plan, submitted by the user of the airspace or its representative to the appropriate ATS unit within the established time limits and to the addresses of FPL submission (see Flight planning). \r\n\r\nClearance for towing, engines start-up and taxiing is issued to the flight crew based on permission to use the airspace and upon request of the pilot-in-command. \r\n\r\nOperation of Departure Service, call sign “Sochi-Delivery”, communication in English and Russian, may be organized by the decision of the Flight Control Officer, notification provided via ATIS. \r\n\r\nWhen there is no information about “Sochi-Delivery” operation in ATIS messages, clearance shall be requested from “Sochi-Ground” controller. \r\n\r\nFlight crews of departing ACFT must establish contact with “Sochi-Delivery” (“Sochi-Ground”) controller 10 minutes before estimated engines start-up time, when ACFT is completely ready for departure, but not earlier than 30 minutes before the planned departure time. \r\n\r\nThe request must include ACFT call sign, stand number, destination aerodrome, ATIS information, confirmation of readiness for engines start-up, information concerning necessity of de-icing treatment. \r\n\r\n**Departure clearance includes:** \r\n\r\n\\- ATC clearance; \r\n\r\n\\- runway for take-off (when ATIS is not AVBL); \r\n\r\n\\- SID designator and initial climb altitude; \r\n\r\n\\- ATS unit frequency (to establish radio contact after take-off); \r\n\r\n\\- SSR code (SQUAWK); \r\n\r\n\\- in case of change of the route indicated in the flight plan - a new transit route or waypoints till joining the airway. \r\n\r\nDeparture clearance is valid within 30 minutes after EOBT. \r\n\r\nIf a departure delay for more than 30 minutes from the departure time indicated in the FPL is expected due to ATS reasons,  ATS unit controller shall advise the estimated time of departure to the pilot-in-command (in this case, pilot shall coordinate engines start-up time with the controller).  \r\n\r\nWhen ACFT is completely ready for take-off, flight crew shall change over to frequency of “Sochi-Ground” controller, by the instruction of “Sochi-Delivery” controller, to obtain clearance for engines start-up and taxiing (towing), reporting stand number and ATIS information code letter. \r\n\r\nClearance for towing and engines start-up shall be requested by the flight crew on “Sochi-Ground” operating frequency, indicating ACFT call sign and position.  \r\n\r\nATS unit controller issues clearance for taxiing to the runway-holding position and taxi instructions upon request of the flight crew. \r\n\r\n**Take-off** \r\n\r\nTake-off not from the RWY beginning shall be carried out upon request of the flight crew or at the initiative of the appropriate ATS unit. Pilot-in-command is responsible for making the decision to perform such take-off. \r\n\r\nTake-off and initial climb shall be executed: \r\n\r\n\\- via RNAV SID applying “Direct to” procedure; \r\n\r\n\\- via tracks assigned by ATS unit using radar vectoring when continuous radar control is AVBL. \r\n\r\nUnless otherwise instructed by ATS unit, ACFT shall climb in compliance with the assigned SID and after take-off establish radio contact with TWR controller (call sign “Sochi-Radar”). Having established radio contact after take-off, flight crew must report take-off execution, assigned SID and FL (altitude) to be reached. \r\n\r\nHaving established radio contact with APP controller in climb, the flight crew must report present FL and FL (altitude) to be reached. \r\n\r\nRNAV SID is available for ACFT with certified equipment operated by flight crews having appropriate approval. If flight crew has no information on RNAV SID parameters or if unable to maintain the assigned RNAV SID, flight crew must report it to ATS unit and request instructions to join ATS route or vectoring. \r\n\r\n**Arrival** \r\n\r\nDescent and arrival shall be executed: \r\n\r\n\\- via RNAV STAR and approach procedures, applying “Direct to” procedure; \r\n\r\n\\- via tracks assigned by ATS unit using radar vectoring when continuous radar control is AVBL. \r\n\r\n\\- RNAV STAR is available for ACFT with certified equipment operated by flight crews having appropriate approval. \r\n\r\nIf flight crew has no information on RNAV STAR and\/or approach procedure parameters or if unable to maintain the assigned RNAV STAR and\/or approach procedure, flight crew must report it to ATS unit and request vectoring for arrival and\/or approach. \r\n\r\nIn order to expedite and manage traffic flow, provide the established separation intervals between ACFT and provide navigation assistance to flight crews, ATS unit can apply vectoring and assign forward and vertical speeds within the limits defined for the specified ACFT type. \r\n\r\nHaving established radio contact with ATS unit, the flight crew must report ACFT position, flight level, ATIS information code letter and obtain RNAV STAR designator (instructions for arrival to the AD). \r\n\r\nWhen proceeding along STAR, flight crew must maintain the track, vertical profile and speed restrictions published on STAR chart. \r\n\r\n***Note:*** \r\n\r\nAltitude and speed restrictions can be cancelled. Direct routing on STAR track shall be carried out only after obtaining the instruction from ATS unit to proceed directly to the assigned point. \r\n\r\n#### IFR approach \r\n\r\nThe basic type of instrument approach is ILS approach. Flight crew shall obtain information on ILS approach availability via ATIS. If intended to execute an approach other than ILS approach, flight crew must report it to APP controller. \r\n\r\nFlight crew must be ready to proceed directly to the assigned waypoint by the instruction of the ATS unit at any moment of time. \r\n\r\nIf ACFT uses own navigation, approach clearance is issued when ACFT is on the initial approach segment (approaching IF). After obtaining approach clearance, flight crew shall descend maintaining the profile of the published approach procedure. \r\n\r\nDuring vectoring, approach clearance is issued together with the last assigned track, in this case the flight crew shall maintain altitude cleared by ATS unit until intercepting the glide path. \r\n\r\nOn the final approach segment, flight crew shall maintain IAS not less than 300 km\/h (160 knots) up to a distance of 8 km (4.3 NM) from landing RWY THR. \r\n\r\n**Emergency landing procedure** \r\n\r\nIn case of emergency situation on board, requiring immediate landing, the flight crew shall report it to ATS unit and follow its instructions. \r\n\r\n#### **Visual approach** \r\n\r\nRWY 06 and RWY 02 are AVBL for visual approach operations. \r\n\r\nVisual approach shall be executed: \r\n\r\n\\- upon request of the pilot-in-command; \r\n\r\n\\- at the initiative of ATS unit (when it is not possible to execute\/continue instrument approach due to technical reasons). \r\n\r\nATS unit issues clearance to execute visual approach to the flight crew of ACFT, operating IFR flight, under the following conditions: \r\n\r\n\\- flight crew is able to maintain visual contact with RWY or its references; \r\n\r\n\\- reported ceiling conforms to or exceeds the altitude at which the initial approach segment begins for the ACFT, that obtained such a clearance, or \r\n\r\n\\- flight crew reports that meteorological conditions allow to execute visual approach and landing. \r\n\r\nATS unit can commence vectoring of ACFT for execution of visual approach, provided that the reported ceiling is above the established minimum vectoring altitude and meteorological conditions allow to suppose that visual approach and landing can be executed. Clearance to execute visual approach is issued only after the flight crew reports establishing visual contact with RWY and\/or its references, after that vectoring is terminated. \r\n\r\nSeparation shall be provided between ACFT that obtained clearance to execute visual approach and other arriving and departing ACFT. \r\n\r\nFor successive visual approaches, separation between ACFT shall be maintained by the controller until the pilot of a succeeding ACFT reports having the preceding ACFT in sight. The pilot shall then be instructed to continue approach and maintain own separation between the preceding ACFT. \r\n\r\nWhen both ACFT are of a heavy wake turbulence category, or the preceding ACFT is of a heavier wake turbulence category than the succeeding ACFT, the controller shall issue a caution of possible wake turbulence. \r\n\r\nThe pilot-in-command of the ACFT concerned shall be responsible for ensuring that the separation interval between a preceding ACFT of a heavier wake turbulence category is acceptable. If deemed necessary to increase separation interval, the flight crew shall inform the ATS unit accordingly, stating their requirements. \r\n\r\nWhen executing visual approach, flight crew must maintain continuous visual contact with the runway and (or) its references. In case visual contact with RWY and (or) its references is lost, flight crew shall carry out missed approach under IFR and immediately inform ATS unit about it. \r\n\r\nWhen executing visual approach, flight crew bears full responsibility for maintaining safe flight altitudes and safe overflying of obstacles. \r\n\r\n#### GNSS approach procedure \r\n\r\nWhen executing GLS, RNP approach, flight crew must report alternative approach procedure to “Sochi-Start” controller. When ACFT execute approach procedures, ATS unit controls GNSS performance using GBAS equipment. If unable to provide approach procedure, ATS unit informs flight crew and advises to use the alternative approach procedure. \r\n\r\n#### **Missed approach under IFR** \r\n\r\nRadar vectoring may be applied to provide execution of missed approach. \r\n\r\nIn case of a missed approach over the course of a visual approach (before establishing on final) ACFT shall turn onto the heading of the RWY of landing and proceed in accordance with the published missed approach procedure. \r\n\r\n***Note:*** \r\n\r\nIn case of approach to RWY 06, missed approach procedure up to MAPt shall be executed by clearance of “Sochi-Start” controller only, in order to provide safe separation intervals between the departing ACFT. \r\n\r\nIn case missed approach is executed by decision of pilot-in-command, the flight crew must immediately report it to “Sochi-Start” controller. Flight crew shall change over to radio communication with “Sochi-Radar” controller by the instruction of “Sochi-Start” controller. \r\n\r\n#### Priority approach procedure \r\n\r\nPriority approach shall be carried out in accordance with the established approach procedure or along tracks assigned by ATS unit by vectoring. \r\n\r\n#### Minimum Runway Occupancy Time for arriving ACFT \r\n\r\nThe flight crew shall: \r\n\r\n\\- when preparing for landing, determine exit TWY for RWY vacation that will enable to minimize time of ACFT presence on the RWY considering actual landing conditions; \r\n\r\n\\- plan RWY vacation via TWY assigned by the ATS unit (if appropriate instruction was obtained); \r\n\r\n\\- vacate the RWY as quickly as possible, observing operational standards and safety measures; \r\n\r\n\\- after landing, having realized that it is not possible to vacate the RWY via the assigned TWY, flight crew shall proceed to the next TWY at the maximum taxi speed established for RWY specified in the Aeroplane Flight Manual. \r\n\r\n#### Procedures related to application of the reduced runway separation minima \r\n\r\nNot applicable. \r\n\r\n#### ATS surveillance procedures \r\n\r\nATS surveillance systems, such as primary surveillance radar (PSR), secondary surveillance radar (SSR) are applied either alone or in combination for air traffic services, including the provision of separation between ACFT. \r\n\r\nBefore providing an ATS surveillance service to an ACFT, identification shall be established and the flight crew informed by ATS unit. Thereafter, identification shall be maintained until termination of the ATS surveillance service. \r\n\r\nIf identification is subsequently lost, the flight crew shall be informed by ATS unit. \r\n\r\n**Radar control and ATS using primary surveillance radar** \r\n\r\nWhere PSR is used for identification, ACFT may be identified by one of the following procedures: \r\n\r\n\\- by correlating a particular radar position indication with an ACFT reporting its position over, or as bearing and distance from, a point shown on the situation display, and by ascertaining that the track of the particular radar position is consistent with the ACFT path or reported heading; \r\n\r\n\\- by correlating an observed radar position indication with an ACFT which is known to have just departed, provided that the identification is established within 2 km (1.1 NM) from the end of the runway used. Particular care should be taken to avoid confusion with ACFT holding over or overflying the aerodrome, or with ACFT departing from or making a missed approach over adjacent runways; \r\n\r\n\\- by transfer of identification; \r\n\r\n\\- by ascertaining the ACFT heading, if circumstances require, and following a period of track observation; \r\n\r\n\\- by instructing the flight crew to execute one or more changes of heading of 30 degrees or more and correlating the movements of one particular radar position indication with the ACFT acknowledged execution of the instructions given or correlating the movements of a particular radar position indication with manoeuvres currently executed by an ACFT having so reported. \r\n\r\nWhen using these methods, the ATS unit shall verify that the movements of not more than one radar position indication correspond with those of the ACFT. \r\n\r\n**Radar control and ATS using secondary surveillance radar** \r\n\r\nWhere SSR is used for identification, ACFT may be identified by one of the following procedures: \r\n\r\n\\- by identification of the ACFT call sign or SSR discrete code of a Mode S-equipped ACFT; \r\n\r\n\\- by transfer of ACFT identification; \r\n\r\n\\- by monitoring of compliance with an instruction to set a specific SSR code; \r\n\r\n\\- by monitoring of compliance with an instruction to squawk IDENT. \r\n\r\nATS unit shall make check at the earliest opportunity to ensure that the code set by the flight crew is identical to that assigned to the ACFT. Only after this check has been made shall the discrete code be used as a basis for identification. \r\n\r\n**ATS surveillance procedures within Sochi CTA** \r\n\r\nEntry of ACFT not equipped with transponders into CTA may be restricted. \r\n\r\nEntry of state aviation ACFT not equipped with transponders into CTA may be permitted after coordination with “Sochi-Approach” or “Sochi-Radar” controller. In this case, time of entry into CTA, route and flight altitude for state aviation ACFT not equipped with transponders are assigned by “Sochi-Approach” or “Sochi-Radar” controller depending on air situation in CTA. \r\n\r\nRadar vectoring is applied to provide the established separation intervals between ACFT, expedite air traffic flow, provide approach sequence and minimize ACFT flight time in CTA. \r\n\r\nVectoring in CTA is permitted at altitudes not below the minimum safe flight altitudes in accordance with ATC Surveillance Minimum Altitude Chart (Surveillance Minimum Altitude Area). \r\n\r\nTo coordinate intervals between ACFT, ATS unit controller can assign forward and vertical speeds within the limits indicated in the Aeroplane Flight Manual for the specified ACFT type \r\n\r\nACFT transit flights within ATS airspace shall be carried out along airways (ATS routes) and along the tracks assigned by ATS unit by radar vectoring. \r\n\r\n**Surveillance and ATS using ADS-B** \r\n\r\nNot applicable. "},{"role":"assistant","content":"{\"GENERAL\":{\"Airport regulations\":[\"Flight crew must have ATS unit clearance before entering the area.\",\"Report position upon ATS unit request.\",\"Follow ATS unit instructions.\",\"Maintain two-way radio communication on VHF.\",\"Have HF and ADF equipment for backup.\",\"Keep ACFT transponder running.\",\"Arriving ACFT, which are on the final approach segment, have priority over departing ACFT.\"],\"Schedule coordination\":[],\"Ground Movement\":{\"Apron Procedures\":[\"Request clearance for pushback\\\/towing when ready.\",\"Inform ATS if more than 1 minute is needed after clearance.\"],\"Towing of ACFT\":[],\"Taxiing\":[\"Request taxi clearance by reporting TWY number.\",\"Inform ATS if long RWY occupation is needed.\"],\"Removal of disabled aircraft\":\"\"},\"Use of APU\":[],\"Use of Runways\":[\"Approach and landing on RWY 06 and RWY 02.\",\"Take-off from RWY 24 and RWY 20.\"],\"Low visibility procedures\":[\"LVP applied when RVR < 550 m.\",\"No more than one ACFT on RWY during LVP.\"],\"Procedures for IFR flights\":[\"Maintain altitudes below transition level based on QNH pressure.\",\"Change altimeter settings when entering\\\/exiting CTR.\"],\"ATS surveillance procedures\":[\"Maintain identification until ATS service termination.\",\"Inform flight crew if identification is lost.\"],\"Noise Abatement Procedures\":[],\"Regional regulations\":[],\"ATIS\":[],\"VFR Procedures\":[]},\"DEPARTURE\":{\"A-CDM\":[\"Request start-up clearance when ready.\",\"Contact 'Sochi-Delivery' 10 minutes before estimated start-up.\"],\"Start-up Procedures\":[\"Request clearance for engine start-up and taxiing.\"],\"Push-back procedures\":[\"Commence pushback immediately after clearance.\",\"**Flight crew shall request clearance for pushback\\\/towing when ground personnel and towing tractor are ready to commence the procedure. After obtaining clearance for pushback\\\/towing from stand, the flight crew shall commence the procedure immediately.**\",\"In case of necessity of extra time for pushback\\\/ towing commencement after obtaining clearance from ATS unit (more than 1 minute), flight crew shall inform ATS unit about it. If more than 1 minute passed after issuance of pushback\\\/towing clearance and flight crew has not commenced the procedure, flight crew must request a new clearance for pushback\\\/towing.\"],\"De\\\/anti-icing\":[],\"Low visibility procedures\":[\"LVP prohibits crossing RWY-holding position without clearance.\"],\"Taxiing\":[\"Check ACFT position constantly during taxi.\",\"Сlearance to taxi to the runway-holding position shall be requested by the flight crew reporting TWY number, in case the flight crew is ready to take off not from the RWY beginning.\"],\"Runway Occupancy Time\":[\"Inform ATS of time needed for take-off preparation.\",\"In case of necessity of long RWY occupation (more than 1 minute), before occupation flight crew shall inform ATS unit of time, required for take-off preparation. If more than 1 minute passed after issuance of take-off clearance, flight crew must request a new clearance for take-off.\"],\"Simultaneous Line-Up\":[],\"Take-Off\":[\"Take-off not from RWY beginning requires request.\"],\"Continued Take-Off\":[],\"Departure Procedures\":[\"Departure clearance includes ATC clearance, runway, SID designator, and SSR code.\"],\"Communication Failure\":[],\"Noise Abatement Procedures\":[],\"Regional regulations\":[],\"VFR Procedures\":[]},\"ARRIVAL\":{\"Arrival Routes\":[],\"Aerodrome Minima\":[],\"Holding Procedures\":[],\"Approach\":[\"Execute RNAV STAR and approach procedures.\",\"Report position and obtain RNAV STAR designator.\",\"Approach and landing shall be executed only on RWY 06 and RWY 02, excluding helicopters executing VFR flights.\"],\"Runway Occupancy Time\":[\"Minimize time on RWY after landing.\"],\"Taxiing\":[],\"Emergency Landing Procedure\":[\"Report emergency to ATS and follow instructions.\"],\"Noise Abatement Procedures\":[],\"Low visibility procedures\":[\"Landing prohibited during LVP.\"],\"Communication Failure\":[],\"Regional regulations\":[],\"VFR Procedures\":[]},\"MISCELLANIUOS\":{\"Helicopter Operations\":[],\"Bird migration\":[],\"Engine Test Runs\":[],\"Visual Docking Guidance Systems\":[],\"Specific Traffic Regulations\":[],\"Schedule maintenance on the runway\":[],\"Positions not visible from control tower\":[],\"Fuel Dumping\":[],\"Warnings\":[]}}"}]}
{"messages":[{"role":"system","content":"прочитай текст всех разделов, создай json файл с переработанным содержанием с установленной в файле структурой, по возможности сократи текст таким образом, чтобы не потерялся смысл, а так же исключи информацию не относящуюся к работе пилота.\n\nИзвлеки части текста и представь ответ как JSON следующего формата:"},{"role":"user","content":"# URSS SOCHI, RUSSIAN FEDERATION\r\n\r\n## FLIGHT PROCEDURES\r\n\r\n#### Communication failure \r\n\r\nIn the event of radio communication failure flight crew must: \r\n\r\n\\- switch on distress signal (“MAYDAY”) and set SSR transponder to code 7600; \r\n\r\n\\- take measures to re-establish radio communication using emergency FREQ 121.500 MHz, reserve FREQ 129.000 MHz, HF-channel 5592 kHz, radio communication with other ACFT and ATS units; \r\n\r\n\\- maintain a listening watch on NDB AD frequency (365 kHz) for information and ATS unit instructions; \r\n\r\n\\- use mobile communication, if required (Flight Control Officer of Aerodrome Control Centre: \r\n\r\n+7 (918) 605-16-11,  +7 (862) 241-98-20; \r\n\r\n\\- execute approach as prescribed by the established radio communication failure procedures; \r\n\r\n\\- proceed to an alternate aerodrome in case of adverse weather conditions at Sochi AD. \r\n\r\n**Radio communication failure after take-off and\/or during climb to FL (ALT)** \r\n\r\nIn the event of radio communication failure after take-off (if communication with “Sochi-Radar” (“Sochi-Approach”) was not established), flight crew must: \r\n\r\n1)If a decision was taken to land at Sochi AD: \r\n\r\na) when proceeding to NDB LA: \r\n\r\n\\- climb in accordance with RNAV SID maintaining ALT 10000 ft; \r\n\r\n\\- after passing NDB LA turn LEFT to KOGUL at ALT 10000 ft; \r\n\r\n\\- after passing KOGUL start descending from ALT 10000 ft and execute approach procedure (KOGUL – GOKIN – IF) depending on the active RWY specified in ATIS broadcast. Hold in the holding area over GOKIN at ALT 6000 ft, if required; \r\n\r\nb) when proceeding to ADNET: \r\n\r\n\\- climb in accordance with RNAV SID maintaining FL150; \r\n\r\n\\- after passing ABUNI turn RIGHT to BINOL at FL150 and join RNAV STAR BINOL 1K or BINOL 1L (depending on the active RWY of landing specified in ATIS broadcast); \r\n\r\n\\- after passing PITOP start descending from FL150 to ALT 6000 ft in the holding area over PITOP (hold in the holding area over PITOP at ALT 6000 ft, if required); \r\n\r\n\\- having reached ALT 6000 ft, proceed directly to IF and execute approach procedure; \r\n\r\nc) when proceeding to IRGID: \r\n\r\n\\- climb in accordance with RNAV SID maintaining FL150; \r\n\r\n\\- after passing IRGID turn RIGHT to BINOL at FL150 and join RNAV STAR BINOL 1K or BINOL 1L (depending on the active RWY of landing specified in ATIS broadcast); \r\n\r\n\\- after passing PITOP start descending from FL150 to ALT 6000 ft in the holding area over PITOP (hold in the holding area over PITOP at ALT 6000 ft, if required); \r\n\r\n\\- having reached ALT 6000 ft, proceed directly to IF and execute approach procedure; \r\n\r\nd) when proceeding to BINOL: \r\n\r\n\\- climb in accordance with RNAV SID maintaining FL150; \r\n\r\n\\- after passing BINOL turn LEFT to BINOL at FL150 and join RNAV STAR BINOL 1K or BINOL 1L (depending on the active RWY of landing specified in ATIS broadcast); \r\n\r\n\\- after passing PITOP start descending from FL150 to ALT 6000 ft in the holding area over PITOP (hold in the holding area over PITOP at ALT 6000 ft, if required); \r\n\r\n\\- having reached ALT 6000 ft, proceed directly to IF and execute approach procedure. \r\n\r\ne) when proceeding to TABAN: \r\n\r\n\\- climb in accordance with RNAV SID maintaining ALT 10000 ft and maximum vertical speed; \r\n\r\n\\- after passing TABAN at ALT 10000 ft turn RIGHT descending to GOKIN to ALT 6000 ft; \r\n\r\n\\- after passing GOKIN proceed directly to IF (depending on the active RWY of landing specified in ATIS broadcast) and execute approach procedure (hold in the holding area over GOKIN at ALT 6000 ft, if required); \r\n\r\nf) when proceeding to LAMET: \r\n\r\n\\- climb in accordance with RNAV SID maintaining ALT 10000 ft and maximum vertical speed; \r\n\r\n\\- after passing LAMET at ALT 10000 ft turn LEFT descending to GOKIN to ALT 6000 ft; \r\n\r\n\\- after passing GOKIN proceed directly to IF (depending on the active RWY of landing specified in ATIS broadcast) and execute approach procedure (hold in the holding area over GOKIN at ALT 6000 ft, if required). \r\n\r\n2)If a decision was taken to proceed to the destination aerodrome, flight crew shall continue to climb to FL200 in accordance with the assigned RNAV SID, then follow the flight route indicated in the flight plan maintaining FL200 for 5 minutes, after that, climb to the cruising level in accordance with the flight plan. \r\n\r\nIf deviation from the specified procedure is required, flight crew must set transponder to code 7700. \r\n\r\n**Communication failure during arrival** \r\n\r\nIf STAR was assigned by the ATS unit and acknowledged by the flight crew, ACFT shall fly the assigned STAR and execute approach procedure. \r\n\r\nIf STAR was not assigned and ACFT that is being vectored experiences radio communication failure, flight crew must: \r\n\r\n\\- join STAR in accordance with the flight plan at ALT last assigned by the ATS unit and acknowledged by the flight crew; \r\n\r\n\\- fly RNAV STAR “Kilo“ or “Lima“ and execute approach procedure (depending on the active RWY of landing specified in ATIS broadcast); \r\n\r\n\\- in the event of a missed approach, continue the flight maintaining flight route and profile of the missed approach procedure to the maximum extent in accordance with item “Communication failure during missed approach”. \r\n\r\nIf deviation from the specified procedure is required, flight crew must set transponder to code 7700. \r\n\r\n**Communication failure during missed approach** \r\n\r\nIn the event of radio communication failure during missed approach procedure, flight crew must: \r\n\r\n\\- set SSR transponder to code 7600; \r\n\r\n\\- continue the established missed approach procedure climbing to 6000 ft; \r\n\r\n\\- hold over PITOP for 5 minutes; \r\n\r\n\\- in case a decision to execute landing was taken – set SSR transponder to code 2000 (burn out fuel, if required) and execute approach in accordance with the established procedure depending on the active RWY of landing, specified in ATIS broadcast;  \r\n\r\n\\- in case a decision to proceed to the alternate aerodrome was taken – set SSR transponder to code 7700, then climb to the flight level prescribed by the established communication failure procedures (after passing FL200 set SSR transponder to code 7600). \r\n\r\n**Radio communication failure after ACFT enters Sochi CTA** \r\n\r\nFlight crew shall continue the flight in accordance with the flight plan. \r\n\r\nIf unable to land at Sochi AD (due to meteorological conditions or for other reasons), flight crew can proceed to an alternate aerodrome in accordance with the flight plan. \r\n\r\n**Radio communication failure during VFR flights** \r\n\r\nACFT proceeding below the lower (safe) flight level shall continue the flight in accordance with the flight plan to the aerodrome of first landing at the altitude assigned earlier by the ATS unit. \r\n\r\nIf radio communication failure occurs, when ACFT leaves or enters Sochi CTR flight crew must: \r\n\r\n\\- switch on distress signal (“MAYDAY”) and set SSR transponder to code 7600; \r\n\r\n\\- take measures to re-establish radio communication using emergency FREQ 121.500 MHz, reserve FREQ 129.000 MHz, HF-channel 5592 kHz, radio communication with other ACFT and ATS units; \r\n\r\n\\- maintain a listening watch on NDB AD frequency (365 kHz) for information and controller’s instructions; \r\n\r\n\\- use mobile communication, if required (Flight Control Officer of the Aerodrome Control Centre): \r\n\r\n+7 (918) 605-16-11,  \r\n\r\n+7 (862) 241-98-20; \r\n\r\n\\- depending on the direction of arrival to the AD, hold for 5 minutes, after that execute approach under VFR.  \r\n\r\nVFR arrival to RWY 06: \r\n\r\n\\- join holding area ABMIN at 1000 ft, then proceed along ABMIN 2L;  \r\n\r\n\\- join holding area DUKEZ at 1000 ft, then proceed along DUKEZ 2L; \r\n\r\n\\- join holding area RINUN at 4000 ft, then proceed along RINUN 2L. \r\n\r\nVFR arrival to RWY 24: \r\n\r\n\\- join holding area ABMIN at 1000 ft, then proceed along ABMIN 2N; \r\n\r\n\\- join holding area DUKEZ at 1000 ft, then proceed along LATRA 2N; \r\n\r\n\\- join holding area RINUN at 4000 ft, then proceed along RINUN 2N. \r\n\r\n***Note:*** \r\n\r\nACFT not equipped with SSR transponders experiencing radio communication failure are PROHIBITED to enter Sochi CTR.\r\n\r\n#### Actions in case of detection of unauthorized flight operations of Unmanned Aircraft in Sochi CTA \r\n\r\nIn case of obtaining information about presence of an Unmanned Aircraft (hereinafter referred to as: UA) within the area of responsibility of ATS unit, the ATS unit shall make warning alert in accordance with the coordinated rules, including notification of the competent air defence authorities.  \r\n\r\nIn case of obtaining information about unauthorized flight of an UA within the area of responsibility of ATS unit (or in case of UA detection by surveillance systems), and obtaining confirmation of UA flight from the air defence authority, the ATS unit shall inform flight crew(s) about it.  \r\n\r\nAfter obtaining such information, flight crew shall increase caution, stop descent, inform ATS unit about amount of fuel remaining and readiness to proceed to the alternate aerodrome and follow ATS unit instructions. \r\n\r\nFlight crews of CAT A ACFT and HEL, operating VFR flights shall climb to the lowest safe flight level and inform ATS unit about amount of fuel remaining and readiness to proceed to the alternate aerodrome, and follow ATS unit instructions. \r\n\r\nIn case ACFT is on final, flight crew shall execute missed approach procedure and follow ATS unit instructions. \r\n\r\nTWR controller should increase caution and continuously monitor the take-off and landing area.  \r\n\r\n#### Procedures for VFR flights \r\n\r\nRequirements for flight operations under VFR: \r\n\r\n\\- to maintain two-way radio communication; \r\n\r\n\\- to obtain clearance of the relevant ATS unit; \r\n\r\n\\- to report ACFT position, when required; \r\n\r\n\\- to follow instructions of the ATS unit controllers. \r\n\r\nClearance for VFR flights is issued by the ATS unit under the following conditions, provided flight situation allows: \r\n\r\n\\- a flight plan shall be submitted; \r\n\r\n\\- ATS unit clearance must be obtained immediately before ACFT enters Sochi CTA; \r\n\r\n\\- position report shall be submitted in accordance with para 3.6.3 of ICAO Annex 2; \r\n\r\n\\- deviations from flight routes are permitted only, provided prior clearance for these deviations was obtained; \r\n\r\n\\- flight shall be carried out with visual reference to the ground, otherwise the flight shall be carried out in accordance with instrument flight rules; \r\n\r\n\\- two-way communication shall be maintained on the prescribed frequency. \r\n\r\n***Note:*** \r\n\r\nATS unit clearance is intended only to provide separation between IFR and VFR flights. \r\n\r\nIn VMC less than the minimums prescribed for VFR flight, pilot-in-command shall request clearance to climb to safe flight ALT from the ATS unit. \r\n\r\nHolding areas for ACFT, operating VFR flights, are indicated on appropriate charts.  \r\n\r\n#### Helicopter flight operations \r\n\r\nHEL shall taxi or air taxi to the RWY, Helipad from stands, or from the RWY, Helipad to stands along the taxi routes established for ACFT at ALT up to 30 ft. \r\n\r\nTake-off\/landing flight paths must not require overflying the airport terminal and fuelling facilities, stands. \r\n\r\nHEL shall take-off from\/land on RWY 02\/20 and RWY 06\/24, Helipads and from\/on any point on the manoeuvring area observing the requirements of the aviation legislation of the Russian Federation. Take-off and landing of helicopters from\/on the RWY can be carried out as running and no-run. \r\n\r\nVFR holding areas for helicopters are established to regulate approach sequence (see VFR ARRIVAL CHARTS): ABMIN, DUKEZ, OREL IZUMRUD, RINUN. \r\n\r\nWhen HEL execute ILS approach, landing shall be carried out on the runway. \r\n\r\nSimultaneous approaches to helipad and RWY are permitted, provided: \r\n\r\n\\- meteorological visibility is 5 km or above and ceiling is 300 m or above; \r\n\r\n\\- information about ACFT relative position is provided to flight crews; \r\n\r\n\\- flight crews report establishing visual contact with other ACFT; \r\n\r\n\\- ACFT approach paths do not intersect; \r\n\r\n\\- safe intervals between ACFT are maintained over the course of VFR flights. \r\n\r\nSimultaneous use of several Helipads is permitted, provided:  \r\n\r\n\\- meteorological visibility is 5 km or above and ceiling is 300 m or above; \r\n\r\n\\- information about ACFT relative position is provided to flight crews; \r\n\r\n\\- flight crews report establishing visual contact with other ACFT; \r\n\r\n\\- ACFT approach paths do not intersect; \r\n\r\n\\- safe intervals between ACFT are maintained over the course of VFR flights.  \r\n\r\n**Missed approach during VFR flight** \r\n\r\nIn the event of a missed approach over the course of approach to RWY 06 or RWY 02, ACFT shall proceed to the holding areas OREL IZUMRUD or RINUN, unless otherwise instructed by the ATS unit. \r\n\r\n***Note:*** \r\n\r\n**1.Procedure for landing in emergency situations** \r\n\r\nIf flight crew identifies failure of ACFT landing gear (or has doubts about its operating condition) over the course of ACFT arrival to the AD, landing shall be carried out on RWY 06. If failure of ACFT landing gear occurs, ACFT shall make a low pass over RWY 06 at 700 ft\/(200) m to allow Control Tower officials to assess landing gear condition\/damage. \r\n\r\nThe decision on whether the ACFT shall land on RWY 06 or proceed to an alternate aerodrome shall be taken after consulting the technical and engineering service specialist and ATS unit. \r\n\r\n\r\n\r\n**2.Criteria for indication of changes of RVR and height of cloud base (vertical visibility)** \r\n\r\nATS unit timely informs the flight crew, whenever changes occur in accordance with the following criteria: \r\n\r\na) visibility (the lowest visibility value among the three observed) improves and reaches or exceeds, or deteriorates and drops below one or several of the following values: \r\n\r\n\\- 5000 m - in cases where significant numbers of flights are operated in accordance with the visual flight rules; \r\n\r\n\\- 5000 m, 3000 m and below - when only NDB is operating; \r\n\r\n\\- 3000 m, 2500 m, 2000 m, 1500 m, 1000 m, 800 m, 600 m. \r\n\r\nb) RVR values improve and reach or exceed, or deteriorate and drop below the following values: \r\n\r\n\\- 2000 m, 1500 m, 1000 m, 800 m, 600 m, 350 m, 150 m. \r\n\r\nc) height of the lower cloud base, when the amount of a layer or mass of cloud is FEW or increasing (or vertical visibility) reaches or exceeds, or drops below one of the following values: \r\n\r\n\\- 450 m - when providing VFR flights; \r\n\r\n\\- 300 m, 210 m, 180 m, 150 m, 120 m, 90 m, 60 m, 30 m. \r\n\r\n**3.Provision of ATS to state aviation ACFT** \r\n\r\nATS of state aviation ACFT unable to establish radio communication with ATS units on the prescribed VHF FREQ over the course of flight operations in Sochi CTR and CTA shall be provided on FREQ 124.000 MHz, after relevant ATS units are notified in advance. \r\n\r\nState aviation ACFT that engage afterburner over the course of flight operations relate to category “Heavy” considering wake turbulence. \r\n\r\n**4.Flight Information Service** \r\n\r\nATS unit is responsible for timely notifying flight crews about meteorological conditions at Sochi aerodrome and, if required, at destination, alternate, and en-route aerodromes, changes in availability\/status of navigation aids, changes in condition of the aerodrome, presence of unmanned balloons, wake or jet turbulence hazard, adverse weather conditions in CTA and any other information that might affect safety of flight operations, if AVBL. \r\n\r\nInformation about meteorological conditions at the aerodrome is included in ATIS broadcast. \r\n\r\nWhen RWY is dry or friction coefficient is 0.6 or above over the entire length of the RWY, calculated friction is not transmitted. \r\n\r\n**5.Use of the airspace** \r\n\r\nACFT flight shall be operated in accordance with the flight plan submitted by the airspace user or its representative to the appropriate ATS unit within the established time frame, to relevant addresses in accordance with ACFT Movement Messaging Manual of the Russian Federation. Flight plan shall be submitted by the airspace user to obtain clearance to operate in Class A and C airspace, and to notify ATS (Flight Control) units, if intended to use Сlass G airspace. FPL shall be filed not earlier than 5 days and not later than 1 hour before time of departure. \r\n\r\nClearance for tow, start-up and taxi operations is issued to the flight crew based on clearance to operate in the airspace (PLN), upon request of the pilot-in-command. \r\n\r\nIn Item 13 of the FPL (Departure Aerodrome and Time) the four-letter location indicator of the departure AD (according to FPL) is inserted, after that, without a space, the estimated time of departure (estimated off-block time (EOBT) in four figures (hours and minutes) is inserted. In the event of ACFT departure from a civil aviation aerodrome, it is required to indicate the intended time of departure from the apron (stand) as the estimated time of departure. \r\n\r\nA DLA message shall be submitted, if ACFT departure is delayed for more than 30 minutes from the estimated off-block time indicated in the initial flight plan, but not later than 2359 (UTC) of the intended date of departure. When the flight is delayed past midnight, a message highlighting changes to the original flight plan (CHG) that includes the amended date of departure in Item 22 of the FPL shall be submitted by the airspace user or its representative. After submitting DLA and CHG messages, airspace user must obtain clearance to operate in the airspace (PLN) from the ATS units.  \r\n\r\nIf the airspace user requests ATS unit to change time of departure to an earlier time, he must submit a CNL relating to the original FPL to the ATS unit, then submit a new FPL, containing indication of earlier time in accordance with the ACFT Movement Messaging Manual of the Russian Federation. After that, the airspace user must obtain a new PLN and follow the instructions of the ATS unit. "},{"role":"assistant","content":"{\"GENERAL\":{\"Airport regulations\":[\"#### Communication failure \\n In the event of radio communication failure flight crew must: \\n - switch on distress signal (“MAYDAY”) and set SSR transponder to code 7600; \\n  - take measures to re-establish radio communication using emergency FREQ 121.500 MHz, reserve FREQ 129.000 MHz, HF-channel 5592 kHz, radio communication with other ACFT and ATS units; \\n - maintain a listening watch on NDB AD frequency (365 kHz) for information and ATS unit instructions; \\n - use mobile communication, if required (Flight Control Officer of Aerodrome Control Centre: \\n +7 (918) 605-16-11,  +7 (862) 241-98-20; \\n - execute approach as prescribed by the established radio communication failure procedures; \\n - proceed to an alternate aerodrome in case of adverse weather conditions at Sochi AD.\",\"\\n #### Actions in case of detection of unauthorized flight operations of Unmanned Aircraft in Sochi CTA \\n In case of obtaining information about presence of an Unmanned Aircraft (hereinafter referred to as: UA) within the area of responsibility of ATS unit, the ATS unit shall make warning alert in accordance with the coordinated rules, including notification of the competent air defence authorities.  \\n In case of obtaining information about unauthorized flight of an UA within the area of responsibility of ATS unit (or in case of UA detection by surveillance systems), and obtaining confirmation of UA flight from the air defence authority, the ATS unit shall inform flight crew(s) about it.  \\n After obtaining such information, flight crew shall increase caution, stop descent, inform ATS unit about amount of fuel remaining and readiness to proceed to the alternate aerodrome and follow ATS unit instructions. \\n Flight crews of CAT A ACFT and HEL, operating VFR flights shall climb to the lowest safe flight level and inform ATS unit about amount of fuel remaining and readiness to proceed to the alternate aerodrome, and follow ATS unit instructions. \\n In case ACFT is on final, flight crew shall execute missed approach procedure and follow ATS unit instructions. \\n TWR controller should increase caution and continuously monitor the take-off and landing area.\"],\"Schedule coordination\":[\"ACFT flight shall be operated in accordance with the flight plan submitted by the airspace user or its representative to the appropriate ATS unit within the established time frame, to relevant addresses in accordance with ACFT Movement Messaging Manual of the Russian Federation. Flight plan shall be submitted by the airspace user to obtain clearance to operate in Class A and C airspace, and to notify ATS (Flight Control) units, if intended to use Сlass G airspace. FPL shall be filed not earlier than 5 days and not later than 1 hour before time of departure. \\n Clearance for tow, start-up and taxi operations is issued to the flight crew based on clearance to operate in the airspace (PLN), upon request of the pilot-in-command. \\n In Item 13 of the FPL (Departure Aerodrome and Time) the four-letter location indicator of the departure AD (according to FPL) is inserted, after that, without a space, the estimated time of departure (estimated off-block time (EOBT) in four figures (hours and minutes) is inserted. In the event of ACFT departure from a civil aviation aerodrome, it is required to indicate the intended time of departure from the apron (stand) as the estimated time of departure. \\n A DLA message shall be submitted, if ACFT departure is delayed for more than 30 minutes from the estimated off-block time indicated in the initial flight plan, but not later than 2359 (UTC) of the intended date of departure. When the flight is delayed past midnight, a message highlighting changes to the original flight plan (CHG) that includes the amended date of departure in Item 22 of the FPL shall be submitted by the airspace user or its representative. After submitting DLA and CHG messages, airspace user must obtain clearance to operate in the airspace (PLN) from the ATS units.  \\n If the airspace user requests ATS unit to change time of departure to an earlier time, he must submit a CNL relating to the original FPL to the ATS unit, then submit a new FPL, containing indication of earlier time in accordance with the ACFT Movement Messaging Manual of the Russian Federation. After that, the airspace user must obtain a new PLN and follow the instructions of the ATS unit. \"],\"Ground Movement\":{\"Apron Procedures\":[],\"Towing of ACFT\":[],\"Taxiing\":[],\"Removal of disabled aircraft\":\"\"},\"Use of APU\":[],\"Use of Runways\":[],\"Low visibility procedures\":[],\"Procedures for IFR flights\":[],\"ATS surveillance procedures\":[\"**Provision of ATS to state aviation ACFT** \\n ATS of state aviation ACFT unable to establish radio communication with ATS units on the prescribed VHF FREQ over the course of flight operations in Sochi CTR and CTA shall be provided on FREQ 124.000 MHz, after relevant ATS units are notified in advance. \\n State aviation ACFT that engage afterburner over the course of flight operations relate to category “Heavy” considering wake turbulence. \",\"\\n **Flight Information Service** \\n ATS unit is responsible for timely notifying flight crews about meteorological conditions at Sochi aerodrome and, if required, at destination, alternate, and en-route aerodromes, changes in availability\\\/status of navigation aids, changes in condition of the aerodrome, presence of unmanned balloons, wake or jet turbulence hazard, adverse weather conditions in CTA and any other information that might affect safety of flight operations, if AVBL. \\n Information about meteorological conditions at the aerodrome is included in ATIS broadcast. \\n When RWY is dry or friction coefficient is 0.6 or above over the entire length of the RWY, calculated friction is not transmitted.\"],\"Noise Abatement Procedures\":[],\"Regional regulations\":[],\"ATIS\":[\"**Criteria for indication of changes of RVR and height of cloud base (vertical visibility)** \\n ATS unit timely informs the flight crew, whenever changes occur in accordance with the following criteria: \\n a) visibility (the lowest visibility value among the three observed) improves and reaches or exceeds, or deteriorates and drops below one or several of the following values: \\n - 5000 m - in cases where significant numbers of flights are operated in accordance with the visual flight rules; \\n - 5000 m, 3000 m and below - when only NDB is operating; \\n - 3000 m, 2500 m, 2000 m, 1500 m, 1000 m, 800 m, 600 m. \\n b) RVR values improve and reach or exceed, or deteriorate and drop below the following values: \\n - 2000 m, 1500 m, 1000 m, 800 m, 600 m, 350 m, 150 m. \\n c) height of the lower cloud base, when the amount of a layer or mass of cloud is FEW or increasing (or vertical visibility) reaches or exceeds, or drops below one of the following values: \\n - 450 m - when providing VFR flights; \\n - 300 m, 210 m, 180 m, 150 m, 120 m, 90 m, 60 m, 30 m. \"],\"VFR Procedures\":[\"Requirements for flight operations under VFR: \\n - to maintain two-way radio communication; \\n - to obtain clearance of the relevant ATS unit; \\n - to report ACFT position, when required; \\n - to follow instructions of the ATS unit controllers. \\n Clearance for VFR flights is issued by the ATS unit under the following conditions, provided flight situation allows: \\n - a flight plan shall be submitted; \\n - ATS unit clearance must be obtained immediately before ACFT enters Sochi CTA; \\n - position report shall be submitted in accordance with para 3.6.3 of ICAO Annex 2; \\n - deviations from flight routes are permitted only, provided prior clearance for these deviations was obtained; \\n - flight shall be carried out with visual reference to the ground, otherwise the flight shall be carried out in accordance with instrument flight rules; \\n - two-way communication shall be maintained on the prescribed frequency. \\n ***Note:*** \\n ATS unit clearance is intended only to provide separation between IFR and VFR flights. \\n In VMC less than the minimums prescribed for VFR flight, pilot-in-command shall request clearance to climb to safe flight ALT from the ATS unit. \\n Holding areas for ACFT, operating VFR flights, are indicated on appropriate charts.\",\"\\n **Radio communication failure during VFR flights** \\n ACFT proceeding below the lower (safe) flight level shall continue the flight in accordance with the flight plan to the aerodrome of first landing at the altitude assigned earlier by the ATS unit. \\n If radio communication failure occurs, when ACFT leaves or enters Sochi CTR flight crew must: \\n - switch on distress signal (“MAYDAY”) and set SSR transponder to code 7600; \\n - take measures to re-establish radio communication using emergency FREQ 121.500 MHz, reserve FREQ 129.000 MHz, HF-channel 5592 kHz, radio communication with other ACFT and ATS units; \\n - maintain a listening watch on NDB AD frequency (365 kHz) for information and controller’s instructions; \\n - use mobile communication, if required (Flight Control Officer of the Aerodrome Control Centre): \\n +7 (918) 605-16-11,  \\n +7 (862) 241-98-20; \\n - depending on the direction of arrival to the AD, hold for 5 minutes, after that execute approach under VFR.  \\n VFR arrival to RWY 06: \\n - join holding area ABMIN at 1000 ft, then proceed along ABMIN 2L;  \\n - join holding area DUKEZ at 1000 ft, then proceed along DUKEZ 2L; \\n - join holding area RINUN at 4000 ft, then proceed along RINUN 2L. \\n VFR arrival to RWY 24: \\n - join holding area ABMIN at 1000 ft, then proceed along ABMIN 2N; \\n - join holding area DUKEZ at 1000 ft, then proceed along LATRA 2N; \\n - join holding area RINUN at 4000 ft, then proceed along RINUN 2N. \\n ***Note:*** \\n ACFT not equipped with SSR transponders experiencing radio communication failure are PROHIBITED to enter Sochi CTR.\",\"**Missed approach during VFR flight** \\n In the event of a missed approach over the course of approach to RWY 06 or RWY 02, ACFT shall proceed to the holding areas OREL IZUMRUD or RINUN, unless otherwise instructed by the ATS unit. \"]},\"DEPARTURE\":{\"A-CDM\":[],\"Start-up Procedures\":[],\"Push-back procedures\":[],\"De\\\/anti-icing\":[],\"Low visibility procedures\":[],\"Taxiing\":[],\"Runway Occupancy Time\":[],\"Simultaneous Line-Up\":[],\"Take-Off\":[],\"Continued Take-Off\":[],\"Departure Procedures\":[],\"Communication Failure\":[\"**Radio communication failure after take-off and\\\/or during climb to FL (ALT)** \\n In the event of radio communication failure after take-off (if communication with “Sochi-Radar” (“Sochi-Approach”) was not established), flight crew must: \\n 1)If a decision was taken to land at Sochi AD: \\n a) when proceeding to NDB LA: \\n - climb in accordance with RNAV SID maintaining ALT 10000 ft; \\n - after passing NDB LA turn LEFT to KOGUL at ALT 10000 ft; \\n - after passing KOGUL start descending from ALT 10000 ft and execute approach procedure (KOGUL – GOKIN – IF) depending on the active RWY specified in ATIS broadcast. Hold in the holding area over GOKIN at ALT 6000 ft, if required; \\n b) when proceeding to ADNET: \\n - climb in accordance with RNAV SID maintaining FL150; \\n - after passing ABUNI turn RIGHT to BINOL at FL150 and join RNAV STAR BINOL 1K or BINOL 1L (depending on the active RWY of landing specified in ATIS broadcast); \\n - after passing PITOP start descending from FL150 to ALT 6000 ft in the holding area over PITOP (hold in the holding area over PITOP at ALT 6000 ft, if required); \\n - having reached ALT 6000 ft, proceed directly to IF and execute approach procedure; \\n c) when proceeding to IRGID: \\n - climb in accordance with RNAV SID maintaining FL150; \\n - after passing IRGID turn RIGHT to BINOL at FL150 and join RNAV STAR BINOL 1K or BINOL 1L (depending on the active RWY of landing specified in ATIS broadcast); \\n - after passing PITOP start descending from FL150 to ALT 6000 ft in the holding area over PITOP (hold in the holding area over PITOP at ALT 6000 ft, if required); \\n - having reached ALT 6000 ft, proceed directly to IF and execute approach procedure; \\n d) when proceeding to BINOL: \\n - climb in accordance with RNAV SID maintaining FL150; \\n - after passing BINOL turn LEFT to BINOL at FL150 and join RNAV STAR BINOL 1K or BINOL 1L (depending on the active RWY of landing specified in ATIS broadcast); \\n - after passing PITOP start descending from FL150 to ALT 6000 ft in the holding area over PITOP (hold in the holding area over PITOP at ALT 6000 ft, if required); \\n - having reached ALT 6000 ft, proceed directly to IF and execute approach procedure. \\n e) when proceeding to TABAN: \\n - climb in accordance with RNAV SID maintaining ALT 10000 ft and maximum vertical speed; \\n - after passing TABAN at ALT 10000 ft turn RIGHT descending to GOKIN to ALT 6000 ft; \\n - after passing GOKIN proceed directly to IF (depending on the active RWY of landing specified in ATIS broadcast) and execute approach procedure (hold in the holding area over GOKIN at ALT 6000 ft, if required); \\n f) when proceeding to LAMET: \\n - climb in accordance with RNAV SID maintaining ALT 10000 ft and maximum vertical speed; \\n - after passing LAMET at ALT 10000 ft turn LEFT descending to GOKIN to ALT 6000 ft; \\n - after passing GOKIN proceed directly to IF (depending on the active RWY of landing specified in ATIS broadcast) and execute approach procedure (hold in the holding area over GOKIN at ALT 6000 ft, if required). \\n 2)If a decision was taken to proceed to the destination aerodrome, flight crew shall continue to climb to FL200 in accordance with the assigned RNAV SID, then follow the flight route indicated in the flight plan maintaining FL200 for 5 minutes, after that, climb to the cruising level in accordance with the flight plan. \\n If deviation from the specified procedure is required, flight crew must set transponder to code 7700. \\n **Radio communication failure after ACFT enters Sochi CTA** \\n Flight crew shall continue the flight in accordance with the flight plan. \\n If unable to land at Sochi AD (due to meteorological conditions or for other reasons), flight crew can proceed to an alternate aerodrome in accordance with the flight plan. \"],\"Noise Abatement Procedures\":[],\"Regional regulations\":[],\"VFR Procedures\":[]},\"ARRIVAL\":{\"Arrival Routes\":[],\"Aerodrome Minima\":[],\"Holding Procedures\":[],\"Approach\":[],\"Runway Occupancy Time\":[],\"Taxiing\":[],\"Emergency Landing Procedure\":[\"**Procedure for landing in emergency situations** \\n If flight crew identifies failure of ACFT landing gear (or has doubts about its operating condition) over the course of ACFT arrival to the AD, landing shall be carried out on RWY 06. If failure of ACFT landing gear occurs, ACFT shall make a low pass over RWY 06 at 700 ft\\\/(200) m to allow Control Tower officials to assess landing gear condition\\\/damage. \\n The decision on whether the ACFT shall land on RWY 06 or proceed to an alternate aerodrome shall be taken after consulting the technical and engineering service specialist and ATS unit. \"],\"Noise Abatement Procedures\":[],\"Low visibility procedures\":[],\"Communication Failure\":[\"**Communication failure during arrival** \\n If STAR was assigned by the ATS unit and acknowledged by the flight crew, ACFT shall fly the assigned STAR and execute approach procedure. \\n If STAR was not assigned and ACFT that is being vectored experiences radio communication failure, flight crew must: \\n - join STAR in accordance with the flight plan at ALT last assigned by the ATS unit and acknowledged by the flight crew; \\n - fly RNAV STAR “Kilo“ or “Lima“ and execute approach procedure (depending on the active RWY of landing specified in ATIS broadcast); \\n - in the event of a missed approach, continue the flight maintaining flight route and profile of the missed approach procedure to the maximum extent in accordance with item “Communication failure during missed approach”. \\n If deviation from the specified procedure is required, flight crew must set transponder to code 7700. \\n **Communication failure during missed approach** \\n In the event of radio communication failure during missed approach procedure, flight crew must: \\n - set SSR transponder to code 7600; \\n - continue the established missed approach procedure climbing to 6000 ft; \\n - hold over PITOP for 5 minutes; \\n - in case a decision to execute landing was taken – set SSR transponder to code 2000 (burn out fuel, if required) and execute approach in accordance with the established procedure depending on the active RWY of landing, specified in ATIS broadcast;  \\n - in case a decision to proceed to the alternate aerodrome was taken – set SSR transponder to code 7700, then climb to the flight level prescribed by the established communication failure procedures (after passing FL200 set SSR transponder to code 7600). \\n **Radio communication failure after ACFT enters Sochi CTA** \\n Flight crew shall continue the flight in accordance with the flight plan. \\n If unable to land at Sochi AD (due to meteorological conditions or for other reasons), flight crew can proceed to an alternate aerodrome in accordance with the flight plan. \"],\"Regional regulations\":[],\"VFR Procedures\":[]},\"MISCELLANIUOS\":{\"Helicopter Operations\":[\"HEL shall taxi or air taxi to the RWY, Helipad from stands, or from the RWY, Helipad to stands along the taxi routes established for ACFT at ALT up to 30 ft. \\n Take-off\\\/landing flight paths must not require overflying the airport terminal and fuelling facilities, stands. \\n HEL shall take-off from\\\/land on RWY 02\\\/20 and RWY 06\\\/24, Helipads and from\\\/on any point on the manoeuvring area observing the requirements of the aviation legislation of the Russian Federation. Take-off and landing of helicopters from\\\/on the RWY can be carried out as running and no-run. \\n VFR holding areas for helicopters are established to regulate approach sequence (see VFR ARRIVAL CHARTS): ABMIN, DUKEZ, OREL IZUMRUD, RINUN. \\n When HEL execute ILS approach, landing shall be carried out on the runway. \\n Simultaneous approaches to helipad and RWY are permitted, provided: \\n - meteorological visibility is 5 km or above and ceiling is 300 m or above; \\n - information about ACFT relative position is provided to flight crews; \\n - flight crews report establishing visual contact with other ACFT; \\n - ACFT approach paths do not intersect; \\n - safe intervals between ACFT are maintained over the course of VFR flights. \\n Simultaneous use of several Helipads is permitted, provided:  \\n - meteorological visibility is 5 km or above and ceiling is 300 m or above; \\n - information about ACFT relative position is provided to flight crews; \\n - flight crews report establishing visual contact with other ACFT; \\n - ACFT approach paths do not intersect; \\n - safe intervals between ACFT are maintained over the course of VFR flights.  \"],\"Bird migration\":[],\"Engine Test Runs\":[],\"Visual Docking Guidance Systems\":[],\"Specific Traffic Regulations\":[],\"Schedule maintenance on the runway\":[],\"Positions not visible from control tower\":[],\"Fuel Dumping\":[],\"Warnings\":[]}}"}]}
{"messages":[{"role":"system","content":"прочитай текст всех разделов, создай json файл с переработанным содержанием с установленной в файле структурой, по возможности сократи текст таким образом, чтобы не потерялся смысл, а так же исключи информацию не относящуюся к работе пилота.\n\nИзвлеки части текста и представь ответ как JSON следующего формата:"},{"role":"user","content":"# URSS SOCHI, RUSSIAN FEDERATION\r\n\r\n## ADDITIONAL INFORMATION\r\n\r\n#### 1.Bird concentrations in the vicinity of the airport \r\n\r\nThe ornithological situation in the vicinity of the aerodrome is conditioned by seasonal and daily bird migration. Seasonal bird migrations occur in March – May and in September – November, and can shift due to change of climate and weather conditions. \r\n\r\nCertain bird species migrate at night. Hovering birds overfly the territory of the aerodrome and aerodrome environs in the second half of the day. Flocks of sparrows can be observed over the course of the day, peaks of activity occur in morning hours (0600-1100) and after midday. \r\n\r\nTWR controller conducts visual observation of bird migration in daylight hours in take-off and approach sectors, on the RWY strip and taxi routes. \r\n\r\nIn case of hazardous ornithological situation the Flight Control Officer (controller): \r\n\r\n\\- informs flight crews about presence of birds in take-off and approach sectors; \r\n\r\n\\- instructs flight crews to join holding area. \r\n\r\nAfter obtaining information about hazardous ornithological situation, flight crews should increase caution, if necessary, avoid dangerous area of bird concentration and switch on landing lights, enhance monitoring of engines (engine) performance, execute missed approach, if required. \r\n\r\nRadar control of bird migration is not provided. \r\n\r\nInformation on the ornithological situation is broadcasted to flight crews via ATIS. \r\n\r\n#### 2.Change of ACFT departure sequence depending on situation on the ground and in the air, weather conditions \r\n\r\n**Slot coordination** \r\n\r\nSochi airport is a Level 3 fully-coordinated airport according to IATA classification. \r\n\r\nA request, a cancellation and a change of the parameter of any flight operation must be submitted to the Schedule coordination service in the form of a formalized message SCR (Slot clearance request\/reply) in accordance with IATA standards (SSIM Ch. 6, Standard Schedules Information Manual) within the following time frames: \r\n\r\n\\- not later than one day before the planned date of a scheduled (passenger\/cargo) flight: daily 0500-1600 UTC. \r\n\r\nCommunication via: \r\n\r\ne-mail: SLOT_manager@aer.aero - international\/domestic flights; \r\n\r\nAFTN: URSSAPCS; \r\n\r\ntel.: +7 (862) 249-72-38. \r\n\r\nH24, for all types of flight operations, in the tactical AFTM phase, communication via: \r\n\r\ne-mail: planning_disp@aer.aero - international\/domestic flights; \r\n\r\nAFTN: URSSAPBF; \r\n\r\ntel.: +7 (862) 249-72-29. \r\n\r\nDaily, for all types of flight operations: \r\n\r\nMON-THU: 1400-0500 UTC; \r\n\r\nFRI: after 1100 UTC; \r\n\r\nSAT, SUN and HOL: H24. \r\n\r\nCommunication via: \r\n\r\ne-mail: planning_disp@aer.aero - international\/domestic flights; \r\n\r\nAFTN: URSSAPBF; \r\n\r\ntel.: +7 (862) 249-72-29. \r\n\r\nRequests filed with violation of IATA standards (SSIM Ch. 6, Standard Schedules Information Manual) are not accepted for consideration. \r\n\r\nFlights without or not adhering to the approved slot time are PROHIBITED. \r\n\r\nTo ensure use of the available runway system capacity at Sochi AD, airspace users (airlines) should plan and provide flight operations in accordance with the allocated slots. \r\n\r\n1.Deviation of ETA from the approved slot is permitted within the following limits: \r\n\r\n\\- +20\/-20 minutes for flights under 4 hours; \r\n\r\n\\- +30\/-30 minutes for flights over 4 hours. \r\n\r\n2.If revision of arrival and\/or departure time is expected, and when there is a change in ACFT type, representative of the airspace user (airline) must approve the new arrival\/departure slot with the Schedule coordination service before submitting FPL and ensure timely submission of FPL and all related standard messages to the addresses indicated in Addressing of flight plan messages. \r\n\r\n3.When submitting a FPL for non-scheduled flights, approved arrival slot at Sochi airport should be indicated. "},{"role":"assistant","content":"{\"GENERAL\":{\"Airport regulations\":[\"Sochi airport is a Level 3 fully-coordinated airport.\",\"Requests for flight operations must be submitted to the Schedule coordination service.\",\"Flights without approved slot time are PROHIBITED.\"],\"Schedule coordination\":[\"Sochi airport is a Level 3 fully-coordinated airport according to IATA classification. \\n A request, a cancellation and a change of the parameter of any flight operation must be submitted to the Schedule coordination service in the form of a formalized message SCR (Slot clearance request\\\/reply) in accordance with IATA standards (SSIM Ch. 6, Standard Schedules Information Manual) within the following time frames: \\n - not later than one day before the planned date of a scheduled (passenger\\\/cargo) flight: daily 0500-1600 UTC. \\n Communication via: \\n e-mail: SLOT_manager@aer.aero - international\\\/domestic flights; \\n AFTN: URSSAPCS; \\n tel.: +7 (862) 249-72-38. \\n H24, for all types of flight operations, in the tactical AFTM phase, communication via: \\n e-mail: planning_disp@aer.aero - international\\\/domestic flights; \\n AFTN: URSSAPBF; \\n tel.: +7 (862) 249-72-29. \\n Daily, for all types of flight operations: \\n MON-THU: 1400-0500 UTC; \\n FRI: after 1100 UTC; \\n SAT, SUN and HOL: H24. \\n Communication via: \\ne-mail: planning_disp@aer.aero - international\\\/domestic flights; \\n AFTN: URSSAPBF; \\n tel.: +7 (862) 249-72-29. \\n Requests filed with violation of IATA standards (SSIM Ch. 6, Standard Schedules Information Manual) are not accepted for consideration. \\n Flights without or not adhering to the approved slot time are PROHIBITED. \\n To ensure use of the available runway system capacity at Sochi AD, airspace users (airlines) should plan and provide flight operations in accordance with the allocated slots. \\n 1.Deviation of ETA from the approved slot is permitted within the following limits: \\n - +20\\\/-20 minutes for flights under 4 hours;\\n - +30\\\/-30 minutes for flights over 4 hours. \\n 2.If revision of arrival and\\\/or departure time is expected, and when there is a change in ACFT type, representative of the airspace user (airline) must approve the new arrival\\\/departure slot with the Schedule coordination service before submitting FPL and ensure timely submission of FPL and all related standard messages to the addresses indicated in Addressing of flight plan messages. \\n 3.When submitting a FPL for non-scheduled flights, approved arrival slot at Sochi airport should be indicated. \"],\"Ground Movement\":{\"Apron Procedures\":[],\"Towing of ACFT\":[],\"Taxiing\":[],\"Removal of disabled aircraft\":\"\"},\"Use of APU\":[],\"Use of Runways\":[],\"Low visibility procedures\":[],\"Procedures for IFR flights\":[],\"ATS surveillance procedures\":[],\"Noise Abatement Procedures\":[],\"Regional regulations\":[],\"ATIS\":[\"Information on the ornithological situation is broadcasted to flight crews via ATIS.\"],\"VFR Procedures\":[]},\"DEPARTURE\":{\"A-CDM\":[],\"Start-up Procedures\":[],\"Push-back procedures\":[],\"De\\\/anti-icing\":[],\"Low visibility procedures\":[],\"Taxiing\":[],\"Runway Occupancy Time\":[],\"Simultaneous Line-Up\":[],\"Take-Off\":[],\"Continued Take-Off\":[],\"Departure Procedures\":[\"Flight crews must approve new arrival\\\/departure slots with the Schedule coordination service.\"],\"Communication Failure\":[],\"Noise Abatement Procedures\":[],\"Regional regulations\":[],\"VFR Procedures\":[]},\"ARRIVAL\":{\"Arrival Routes\":[],\"Aerodrome Minima\":[],\"Holding Procedures\":[],\"Approach\":[],\"Runway Occupancy Time\":[],\"Taxiing\":[],\"Emergency Landing Procedure\":[],\"Noise Abatement Procedures\":[],\"Low visibility procedures\":[],\"Communication Failure\":[],\"Regional regulations\":[],\"VFR Procedures\":[]},\"MISCELLANIUOS\":{\"Helicopter Operations\":[],\"Bird migration\":[\"The ornithological situation in the vicinity of the aerodrome is conditioned by seasonal and daily bird migration. Seasonal bird migrations occur in March – May and in September – November, and can shift due to change of climate and weather conditions. \\n Certain bird species migrate at night. Hovering birds overfly the territory of the aerodrome and aerodrome environs in the second half of the day. Flocks of sparrows can be observed over the course of the day, peaks of activity occur in morning hours (0600-1100) and after midday. \\n TWR controller conducts visual observation of bird migration in daylight hours in take-off and approach sectors, on the RWY strip and taxi routes. \\n In case of hazardous ornithological situation the Flight Control Officer (controller): \\n- informs flight crews about presence of birds in take-off and approach sectors; \\n - instructs flight crews to join holding area. \\n After obtaining information about hazardous ornithological situation, flight crews should increase caution, if necessary, avoid dangerous area of bird concentration and switch on landing lights, enhance monitoring of engines (engine) performance, execute missed approach, if required. \\n Radar control of bird migration is not provided. \\n Information on the ornithological situation is broadcasted to flight crews via ATIS. \"],\"Engine Test Runs\":[],\"Visual Docking Guidance Systems\":[],\"Specific Traffic Regulations\":[],\"Schedule maintenance on the runway\":[],\"Positions not visible from control tower\":[],\"Fuel Dumping\":[],\"Warnings\":[]}}"}]}
{"messages":[{"role":"system","content":"прочитай текст всех разделов, создай json файл с переработанным содержанием с установленной в файле структурой, по возможности сократи текст таким образом, чтобы не потерялся смысл, а так же исключи информацию не относящуюся к работе пилота.\n\nИзвлеки части текста и представь ответ как JSON следующего формата:"},{"role":"user","content":"# URSS SOCHI, RUSSIAN FEDERATION\r\n\r\n## NOISE ABATEMENT PROCEDURES\r\n\r\n#### 1.General provisions \r\n\r\nNoise abatement procedures at Sochi aerodrome shall be applied only during take-off and climb and shall be executed by the flight crews of all ACFT. \r\n\r\nNoise abatement procedures shall not be executed at the expense of flight safety reduction. \r\n\r\nNoise abatement procedures shall not be executed in case of one of the aircraft engines failure during take-off. \r\n\r\n#### 2.Use of the runway system during the day period \r\n\r\nRWY 02\/20, RWY 06\/24 are used for landing\/take-off of ACFT depending on air, meteorological and ground situation.   \r\n\r\n#### 3.Use of the runway system during the night period \r\n\r\nRWY 02\/20, RWY 06\/24 are used for landing\/take-off of ACFT depending on air, meteorological and ground situation. \r\n\r\n#### 4.Take-off restrictions \r\n\r\nTake-off with a tailwind component is permitted in accordance with the Aeroplane Flight Manual for the specified aircraft type. \r\n\r\nAfter take-off from RWY 20 and climbing to 750 ft\/(205) m or above with the maximum possible climb gradient aircraft shall proceed to D5.6 ADL, turn LEFT to intercept R187° ADL, then proceed on track 187° MAG, contact “Sochi-Radar” (on frequency 119.700 MHz) and execute RIGHT climbing turn in accordance with assigned SID or by ATS unit instruction. \r\n\r\nAfter take-off from RWY 24 and climbing to 600 ft\/(180) m or above with the maximum possible climb gradient aircraft shall proceed to D5.6 ADL, turn RIGHT to intercept R249° ADL, then proceed on track 249° MAG, contact “Sochi-Radar” (on frequency 119.700 MHz) and execute RIGHT climbing turn in accordance with SID or by ATS unit instruction.  \r\n\r\nChange of flight direction after take-off is permitted after ATS unit clearance is obtained, not earlier than ACFT reaches D5.6 ADL and altitude (height): \r\n\r\n\\- during take-off from RWY 20 – 750 ft\/(205) m or above;  \r\n\r\n\\- during take-off from RWY 24 – 600 ft\/(180) m or above. \r\n\r\nThe minimum indicated air speed of steady climb shall not be less than (V₂+20) km\/h, or less than that prescribed in the Aeroplane Flight Manual, if it has greater value. \r\n\r\nMaintaining the minimum indicated air speed during climb is not required, if it leads to exceeding the maximum permissible angle of attack. \r\n\r\nEngines power shall not be reduced until: \r\n\r\n\\- aircraft reaches 1100 ft AMSL; \r\n\r\n\\- the selected standard power mode enables ACFT with maximum certificated take-off mass to maintain the established climb gradient of not less than 4% at speed (V₂+20) km\/h or that prescribed in the Aeroplane Flight Manual, if it has greater value and angle of attack does not exceed the maximum permissible; \r\n\r\n\\- take-off flight path provides overflying of all obstacles located below the flight path with sufficient clearance, when all ACFT engines are operating, and taking into consideration possible engine failure and time required for remaining operating engines to develop full power. \r\n\r\n#### 5.Landing restrictions \r\n\r\nNot applied. \r\n\r\n***Note*** \r\n\r\nSpecial take-off procedures are not applied at Sochi aerodrome. \r\n\r\n"},{"role":"assistant","content":"{\"GENERAL\":{\"Noise Abatement Procedures\":[\"1.General provisions \\n Noise abatement procedures at Sochi aerodrome shall be applied only during take-off and climb and shall be executed by the flight crews of all ACFT. \\n Noise abatement procedures shall not be executed at the expense of flight safety reduction. \\n Noise abatement procedures shall not be executed in case of one of the aircraft engines failure during take-off. \\n #### 2.Use of the runway system during the day period \\n RWY 02\\\/20, RWY 06\\\/24 are used for landing\\\/take-off of ACFT depending on air, meteorological and ground situation.\\n #### 3.Use of the runway system during the night period \\n RWY 02\\\/20, RWY 06\\\/24 are used for landing\\\/take-off of ACFT depending on air, meteorological and ground situation. \\n #### 4.Take-off restrictions \\n Take-off with a tailwind component is permitted in accordance with the Aeroplane Flight Manual for the specified aircraft type. \\n After take-off from RWY 20 and climbing to 750 ft\\\/(205) m or above with the maximum possible climb gradient aircraft shall proceed to D5.6 ADL, turn LEFT to intercept R187° ADL, then proceed on track 187° MAG, contact “Sochi-Radar” (on frequency 119.700 MHz) and execute RIGHT climbing turn in accordance with assigned SID or by ATS unit instruction. \\n After take-off from RWY 24 and climbing to 600 ft\\\/(180) m or above with the maximum possible climb gradient aircraft shall proceed to D5.6 ADL, turn RIGHT to intercept R249° ADL,  then proceed on track 249° MAG, contact “Sochi-Radar” (on frequency 119.700 MHz) and execute RIGHT climbing turn in accordance with SID or by ATS unit instruction. \\n Change of flight direction after take-off is permitted after ATS unit clearance is obtained, not earlier than ACFT reaches D5.6 ADL and altitude (height): \\n - during take-off from RWY 20 – 750 ft\\\/(205) m or above;  \\n - during take-off from RWY 24 – 600 ft\\\/(180) m or above. \\n The minimum indicated air speed of steady climb shall not be less than (V₂+20) km\\\/h, or less than that prescribed in the Aeroplane Flight Manual, if it has greater value. \\n Maintaining the minimum indicated air speed during climb is not required, if it leads to exceeding the maximum permissible angle of attack. \\n Engines power shall not be reduced until: \\n - aircraft reaches 1100 ft AMSL; \\n - the selected standard power mode enables ACFT with maximum certificated take-off mass to maintain the established climb gradient of not less than 4% at speed (V₂+20) km\\\/h or that prescribed in the Aeroplane Flight Manual, if it has greater value and angle of attack does not exceed the maximum permissible; \\n - take-off flight path provides overflying of all obstacles located below the flight path with sufficient clearance, when all ACFT engines are operating, and taking into consideration possible engine failure and time required for remaining operating engines to develop full power. \\n #### 5.Landing restrictions \\n Not applied. \\n ***Note***\\n Special take-off procedures are not applied at Sochi aerodrome. \"],\"Use of Runways\":[]},\"DEPARTURE\":{\"Take-Off Restrictions\":[]},\"ARRIVAL\":{\"Landing Restrictions\":[]}}"}]}