У нас вы можете посмотреть бесплатно (Real ATC) A Cathay Dragon Airbus A320 returned back to Tokyo shortly after departure или скачать в максимальном доступном качестве, видео которое было загружено на ютуб. Для загрузки выберите вариант из формы ниже:
Если кнопки скачивания не
загрузились
НАЖМИТЕ ЗДЕСЬ или обновите страницу
Если возникают проблемы со скачиванием видео, пожалуйста напишите в поддержку по адресу внизу
страницы.
Спасибо за использование сервиса ClipSaver.ru
THIS VIDEO IS A RECONSTRUCTION OF THE FOLLOWING SITUATION IN FLIGHT: 01.11.2019. A Cathay Dragon Airbus A320, performing flight HDA-931 from Tokyo (Haneda airport) to Hong Kong with 106 persons on board, was in initial climb out of Tokyo when the crew requested to stop the climb and decided to return back to Tokyo. They reported that there was a technical problem. Soon the aircraft landed safely at the airport of departure. PART OF TEXT VERSION OF COMMUNICATIONS THAT I'M ABLE TO INCLUDE HERE. Do you want more? Write in comments and I'll give you remaining part of text communications (Read if subtitles in video were fast): COMMENTS: Maybe after departure, HDA391 due to some problems made blind transmission and contacted Tower. HDA391: Dragon 391, transmitting blind [SID designator], climbing FL180. TWR: Dragon 391, go ahead. HDA391: Dragon 391, we have technical problem, we now fly [SID designator] departure, climbing FL180. DEPARTURE: Dragon 391, Tower, contact departure 126.0. HDA391: 126.0 Dragon 391. COMMENTS: HDA391 contact departure. HDA391: Departure, Dragon 391, we are on [SID designator] departure, climbing FL180. DEPARTURE: Dragon 391, Tokyo Departure, now radar contact [not clear]. HDA391: Dragon 391 request stop climb at flight level 11000 due to technical problem and stand by for further information. DEPARTURE: Dragon 391, say again. HDA391: Request stop climb FL110 and we have technical problem, so request FL110. DEPARTURE: Dragon 391, maintain 11000. HDA391: Request 11000, Dragon 391. DEPARTURE: Dragon 391, request [not clear] and your intentions. HDA391: Stand by. HDA391: Dragon 391, we’ve got a navigation problem, with a common navigation problem and smell and some other problems on the aircraft, declaring now the PAN and stand by for the intentions, PAN PAN, Dragon 391. DEPARTURE: Dragon 391, confirm… DEPARTURE: Dragon 391, would you return to Haneda? HDA391: Stand by. HDA391: PAN PAN PAN, Dragon 391, request return back to Tokyo Narita Airport. DEPARTURE: Dragon 391, confirm, return to Narita. HDA391: Affirm, to Narita, Dragon 391. DEPARTURE: Dragon 391 [not clear] left to fly heading 180, vectors to Narita airport, runway… HDA391: Left, heading 180, radar vectors in Narita, Dragon 391. DEPARTURE: Dragon 391, descend to Narita airport via radar vectors, now vector 090, vectors to final approach, maintain 11000. HDA391: Heading 090, maintain 11000, Dragon 391. DEPARTURE: Dragon 391, request runway in use in Narita. HDA391: Stand by, 391. DEPARTURE: Dragon 391. HDA391: Dragon 391, go. DEPARTURE: Expect ILS Y Runway 16R approach in Narita. HDA391: Expecting ILS Y 16R for Narita, Dragon 391. DEPARTURE: Dragon 391, also Narita weather conditions, IMC and visibility 900m and celling broken 100f. Also runway 16R RVR: touchdown 300m, midpoint 400m, stop end 600m and [not clear] HDA391: Due to weather we request diversion to Tokyo Haneda airport. DEPARTURE: Ok, [not clear] back to Haneda? Confirm. HDA391: Back to Haneda, affirm, Dragon 391. DEPARTURE: Dragon 391, just confirm, now request Haneda? ------ This is maximum I can write here. Do you want more? Write in comments and I'll give you remaining part of text communications ------- THE VALUE OF THIS VIDEO: THE MAIN VALUE IS EDUCATION. This reconstruction will be useful for actual or future air traffic controllers and pilots, people who plan to connect life with aviation, who like aviation. With help of this video reconstruction you’ll learn how to use radiotelephony rules, Aviation English language and general English language (for people whose native language is not English) in situation in flight, which was shown. THE MAIN REASON I DO THIS IS TO HELP PEOPLE TO UNDERSTAND EVERY EMERGENCY SITUATION, EVERY WORD AND EVERY MOVE OF AIRCRAFT. SOURCES OF MATERIAL, LICENSES AND PERMISSIONS: Source of communications – https://www.liveatc.net/ (I have a permission (Letter) for commercial use of radio communications from LiveATC.net). Map, aerial pictures (License (ODbL) ©OpenStreetMap -https://www.openstreetmap.org/copyrig...) Permission for commercial use, royalty-free use. Radar screen (In new versions of videos) – Made by author. Text version of communication – Made by Author. Video editing - Made by author. HOW I DO VIDEOS: 1) I monitor media, airspace, looking for any non-standard, emergency and interesting situation. 2) I find communications of ATC unit for the period of time I need. 3) I take only phrases between air traffic controller and selected flight. 4) I find a flight path of selected aircraft. 5) I make an animation (early couple of videos don’t have animation) of flight path and aircraft, where the aircraft goes on his route. 6) When I edit video I put phrases of communications to specific points in video (in tandem with animation). 7) Together with my comments (voice and text) I edit and make a reconstruction of emergency, non-standard and interesting situation in flight.