Sunday, June 26, 2022
No Result
View All Result
Asbarez.com
NEWSLETTER
ՀԱՅ
  • Home
  • Top Stories
  • Community
  • Arts & Culture
    • Art
    • Books
    • Music
    • Theatre
    • Critics’ Forum
  • Op-Ed
    • Editorial
    • Opinon
    • Letters
  • Columns
    • By Any Means
    • My Turn
    • Three Apples
    • Community Links
    • Critics’ Forum
    • My Name is Armen
    • Living in Armenia
  • Videos
  • Sports
  • Home
  • Top Stories
  • Community
  • Arts & Culture
    • Art
    • Books
    • Music
    • Theatre
    • Critics’ Forum
  • Op-Ed
    • Editorial
    • Opinon
    • Letters
  • Columns
    • By Any Means
    • My Turn
    • Three Apples
    • Community Links
    • Critics’ Forum
    • My Name is Armen
    • Living in Armenia
  • Videos
  • Sports
No Result
View All Result
Asbarez.com
ՀԱՅ
No Result
View All Result

April 17, 1993: A Fateful Day in the Battle for Shahumian

by Contributor
April 17, 2013
in Armenia, Featured Story, Latest, Top Stories
4
Share on FacebookShare on Twitter
Yeghnik battalion commander Shahen Meghrian died on April 17, 1993 (photo by Hakop Poghosyan)

BY SONA AVAGYAN
From hetq.am

Commander Shahen Meghrian and 7 “Yeghnik” battalion soldiers killed when their helicopter is hit over Gulistan

“As a leader, Janbulad (Muradyan), flew out in front and I would follow. We reached the hydro-electric and passed through into the forest surrounding the Sarsang Reservoir where the guys from a partisan unit were waiting for us. The guys warmly received us and we began unload the arms and ammunition we had brought. Two or three minutes later, we heard a loud explosion and we all ducked for cover. The guys pointed in the direction of the fire, over to our right. They were firing at us from the direction of Talish.”

This is how Rafik Mehrabyan, helicopter captain with the Armaero airlines, remembers the fateful flight of April 17, 1993.

During the Artsakh War, helicopters would always fly in pairs to the partisan units operating in the Shaumian Region. On April 17, 1993, the second chopper that took off with Rafik Mehrabyan was shot down over the village of Gulistan.

Flying in the downed chopper were Shahen Meghrian, commander of the “Yeghnik” (Asbarez: The Yeghnik battalion was formed by the Armenian Revolutionary Federation) partisan unit and seven fighters under his command. The chopper crew of Captain Janbulad Muradyan, Second Pilot Aram Grigorian and Mechanic Iosif Mikayelyan also died.

The helicopter was transporting large amounts of arms and ammunition to the partisan unit. Janbulad’s chopper was the first to land. Rafik’s touched down not far away.

‘We’ve been spotted, take immediate evasive action…’

“By a stroke of luck, we later found out that the enemy was firing ‘Strela’ missiles at us. These are missiles especially used against airplanes and choppers. If we had known this at the time, we could have immediately turned off the engines and taken up positions with the partisans and relocated elsewhere. I was already in contact with Janbulad, telling him that we should go to the other side where it’s safer. Janbulad hovered for a moment and then moved off to the right, behind the hill, where we wouldn’t be visible. I touched down a bit away and we started to unload our cargo. But they still hadn’t told us what missiles were being fired at us. I got back on the horn and told Janbulad to watch his back and that there was incoming fire. Janbulad answered, ‘make it snappy, we’ve been spotted.’ We knew that we had trouble on our hands,” recounts Rafik Mehrabyan.

Rafik says that Shahen Meghrian and his fighters piled into Janbulad’s chopper because it was closer.

The “Yeghnik” unit leader was preparing to return to Yerevan. After unloading, Rafik’s chopper was the first to take off.

“I had just taken off and was descending into the valley and turning right to get away from the fire we were taking. I was getting into the flight path for Martakert. I realized the enemy had fired off a second missile at us that most likely missed hitting us. I realized the second missile had indeed been fired when it slammed into a nearby mountain, scorching the place to cinders. I told Janbulad to watch out, that they had fired a second missile. By that time, Janbulad was also airborne and we spotted one another. I told him, ‘Let’s get the hell out of here.’ I made a wide turn and then saw that Janbulad’s chopper was engulfed in smoke. He had been hit with a third missile. I frantically tried to get him on the radio, but it was too late,” recounts Rafik Mehrabyan.

Flames were shooting out of the chopper. Rafik says that he had no idea where the missiles were being fired from.

We retrieved all those who died and buried them in Yerablur

Mehrabyan said that he and his co-pilot Mushegh tried to land but that the groundcover was too densely forested. On the way back to Martakert, they got in touch with Yerevan and reported that Janbulad’s chopper had been hit but that they couldn’t say what had happened to those inside.

The rest of Shahen Meghrian’s unit had seen what had happened and made their way down to the chopper and reported back to base. Two days later, two helicopters flew in and removed the remains of those who had died.

Stepan Ohanyan, now Deputy Director of Flight Management at Armaero Airlines, was in the helicopter that day that landed on the hilltop as a decoy while the other went down below to retrieve the bodies.

“We didn’t take off until all the bodies had been removed. The Azeris were waiting for us but they only spotted us and opened fire. But, we had landed in a spot just out of range. We got them all out and laid them to rest in Yerablur. They’re all buried side by side in Yerablur,” said Stepan Ohanyan.

Aram Grigoryan, Second Pilot of the downed chopper and Mechanic Iosif Mikayelyan, were posthumously awarded the NKR Military Cross, 2nd Class. Janbulad Muradyan was awarded with the RA Military Cross, 2nd Class, and the NKR Military Cross, 1st Class.

Helicopters the only way in or out of Artsakh

Mehrabyan points out that helicopters were the only means of contact with Artsakh from the start of the war until the liberation of Shushi and Lachin in 1992. Afterwards, ground vehicles could also ferry in supplies and personnel.

He said that Erebuni Airport had been completely turned over to the war effort and that they also used military choppers to fly sorties and for transport runs.

Stepan Ohanyan says the best time to fly was when there was cloud cover over Karvatchar and Martakert. The most difficult runs were when they had to make flight to reach the partisan units in Shahumyan. They had to make their way through a wide and dangerous military front.

“We would fly in over the clouds in Shahumian and see where we could land. It was a seat-of-the-pants landing. You have to remember there were no landing strips or anything. You had to pick your spots. If the valleys below were covered we had to land on mountain tops and unload the passengers. Back then we didn’t care who belonged to what political party. Those who arrived armed and ready to fight were the first to get seats in the chopper. Of course, doctors were also a priority,” said Stepan Ohanyan.

Sergey Melkonyan, who served as the communications chief for the RA domestic airports, was in touch with the two choppers who flew in to meet up with the Shahumian partisans.

Code 200 crackled over the radio… there were fatalities

“I was in contact with the partisans when they reported what had happened. Contact was sporadic due to the weather. When the airwaves cleared the first voice I heard was that of Commander Sergey Chalyan. He gave the code ‘200’ that there were helicopter fatalities,” said Melkonyan.

Melkonyan had travelled to Shaumian back in 1989, to take communications equipment. He was the one to set up periodic communications between Yerevan, Stepanakert and the partisan units and the overall links needed to monitor flights.

“My office became a veritable transceiver station with people filing in and out. There were times when our dead had been evacuated and the news was received with jubilation because our fallen heroes hadn’t fallen into the hands of the enemy. We couldn’t afford to let the enemy use our heroes, whatever their affiliation, to be used as leverage against us in the war. We had already sacrificed so much. We had no right to make any further concessions. The Armenian struggle in Artsakh was something that hadn’t been witnessed since the days of Tigran the Great. Today, lowland Karabakh is completely in the hands of our malevolent neighbor,” said Melkonyan.

Shahen Meghrian and his “Yeghnik” partisan unit were fighting to liberate lowland Karabakh and Shahumian. Shahen’s brother, Petros Meghrian, who also fought in the war was with Melkonyan on April 17.

Special brigade named in honor of Shahen Meghrian

“The partisan movement basically started out with 25 local guys. Later on, guys from the ‘Arabo,’ ‘Tigran Metz’ and ‘Broshyan’ units joined up with us in addition to guys from Hoktemberyan. By 1993, after Shahen’s death, a special military unit had been established that was named the Shahen Meghrian Special Operation Brigade. If it hadn’t been for the ‘Yeghnik’ unit our border today in the north would have been the Tartar River, much further south. The Turks were holed up in Haterk, north of the Sarsang, and in Mataghis. But, thank God, due to the “Yeghniks” we control all the way up to Talish, even though there are 7-8 villages in Martakert occupied by the enemy,” said Petros Meghryan.

He lost seven close relatives during the Artsakh War. On April 17, 1993, another relative, Hayk Meghrian, was killed in the helicopter.

The other partisans who died that day were Artak Khachatryan, Grigor Grigoryan, Poghos Simonyan, Rafik Badalyan, Armen Bazyan and Aleksandr Mezhunts.

Poghos Meghryan –  Yerevan should recognize Karabakh as part of Armenia

Poghos Meghryan recounts, “While in Shahumyan, I always tried to stay at my brother’s side, that is if he wasn’t ordering me to Yerevan to bring back this or that. Me and Shahen grew up together and we were very close. We were seven brothers and four sisters in the family. I was the tenth child and Shahen, the ninth. He was two years older than me.”

Shahen Meghrian was born in 1952 in the Shahumian village of Gulistan, on the northern bank of the Inja River, the current line of contact in the north. In 1975 he graduated from the Faculty of Economics at Yerevan State University. Returning to his native village, he worked as an economist at the Regional Administration. From 1991-1992, he was President of the Regional Executive Committee. From the start of the Karabakh Movement, he assumed the task of organizing the local defense forces.

After the occupation of Shahumian in 1992, Shahen Meghrian and the partisans under his command waged a nine-month struggle to liberate the region until he and the others died on April 17, 1993.

Just a few days before he was killed, Shahen and his men liberated his home town of Gyulistan. They were only able to hold on to the town for two days.

“It was Shahen’s dream that the lands from the Kur to the Araks rivers be united with Armenia. I too, as an Armenian, would like to see such unification. Today, there is much talk and speculation going on about the recognition of Karabakh and such. In my opinion, and I admit I might be wrong or politically a novice, the time has come for Yerevan to recognize Karabakh as an integral part of Armenia, and not as an independent state. Shahen was a wonderful brother and friend to me. Let those who knew him and fought with him add their own comments. There is no one who is without fault, but Shahen was, in my opinion, one of those men who had very few and who took a wealth of knowledge with him to the other world,” said Petros, his brother.

Shahen’s brother and war buddies are convinced that had Shahen not died on that day in the helicopter, Armenian forces would have liberated the whole of Shahumian in 1993-1994.

Contributor

Contributor

Next Post

ANCA-Glendale to Host Blood Drive in Commemorating Genocide

Comments 4

  1. varouj sarkissian says:
    9 years ago

    ARTSAKH was ,is,and allways will be ARMENIA.

    Reply
  2. hi says:
    9 years ago

    god bless shahen.

    Reply
    • john goncuian says:
      9 years ago

      GOD BLESS SHAHEN,MONTE AND ALL OTHERS WHO MADE THE ULTIMATE SACRIFICE FOR ARMENIA. ARTSAKH ALWAYS BELONGED TO ARMENIA.

      Reply
  3. edward demian says:
    9 years ago

    Artsackh is Armenia, and is already united with it in fact. When Artsackh is recognized by the UN, It will have a vote, and with that of Armenia, it will have more influence.

    Reply

Leave a Reply to hi Cancel reply

Your email address will not be published. Required fields are marked *

Recommended

Homenetmen Returns to LACC with Epic Musical Performances for 45th Navasartian Games

Homenetmen Returns to LACC with Epic Musical Performances for 45th Navasartian Games

1 day ago
8 Artists to be Featured in ‘Dreams in Deixis’ Exhibition at Tufenkian Gallery

8 Artists to be Featured in ‘Dreams in Deixis’ Exhibition at Tufenkian Gallery

2 days ago

Connect with us

  • About
  • Advertising
  • Subscribe
  • Contact

© 2021 Asbarez | All Rights Reserved | Powered By MSDN Solutions Inc.

No Result
View All Result
  • Home
  • Top Stories
  • Community
  • Arts & Culture
    • Art
    • Books
    • Music
    • Theatre
    • Critics’ Forum
  • Op-Ed
    • Editorial
    • Opinon
    • Letters
  • Columns
    • By Any Means
    • My Turn
    • Three Apples
    • Community Links
    • Critics’ Forum
    • My Name is Armen
    • Living in Armenia
  • Videos
  • Sports

© 2021 Asbarez | All Rights Reserved | Powered By MSDN Solutions Inc.

Accessibility

Accessibility modes

Epilepsy Safe Mode
Dampens color and removes blinks
This mode enables people with epilepsy to use the website safely by eliminating the risk of seizures that result from flashing or blinking animations and risky color combinations.
Visually Impaired Mode
Improves website's visuals
This mode adjusts the website for the convenience of users with visual impairments such as Degrading Eyesight, Tunnel Vision, Cataract, Glaucoma, and others.
Cognitive Disability Mode
Helps to focus on specific content
This mode provides different assistive options to help users with cognitive impairments such as Dyslexia, Autism, CVA, and others, to focus on the essential elements of the website more easily.
ADHD Friendly Mode
Reduces distractions and improve focus
This mode helps users with ADHD and Neurodevelopmental disorders to read, browse, and focus on the main website elements more easily while significantly reducing distractions.
Blindness Mode
Allows using the site with your screen-reader
This mode configures the website to be compatible with screen-readers such as JAWS, NVDA, VoiceOver, and TalkBack. A screen-reader is software for blind users that is installed on a computer and smartphone, and websites must be compatible with it.

Online Dictionary

    Readable Experience

    Content Scaling
    Default
    Text Magnifier
    Readable Font
    Dyslexia Friendly
    Highlight Titles
    Highlight Links
    Font Sizing
    Default
    Line Height
    Default
    Letter Spacing
    Default
    Left Aligned
    Center Aligned
    Right Aligned

    Visually Pleasing Experience

    Dark Contrast
    Light Contrast
    Monochrome
    High Contrast
    High Saturation
    Low Saturation
    Adjust Text Colors
    Adjust Title Colors
    Adjust Background Colors

    Easy Orientation

    Mute Sounds
    Hide Images
    Virtual Keyboard
    Reading Guide
    Stop Animations
    Reading Mask
    Highlight Hover
    Highlight Focus
    Big Dark Cursor
    Big Light Cursor
    Navigation Keys

    Asbarez.com Accessibility Statement

    Accessibility Statement

    • asbarez.com
    • June 26, 2022

    Compliance status

    We firmly believe that the internet should be available and accessible to anyone, and are committed to providing a website that is accessible to the widest possible audience, regardless of circumstance and ability.

    To fulfill this, we aim to adhere as strictly as possible to the World Wide Web Consortium’s (W3C) Web Content Accessibility Guidelines 2.1 (WCAG 2.1) at the AA level. These guidelines explain how to make web content accessible to people with a wide array of disabilities. Complying with those guidelines helps us ensure that the website is accessible to all people: blind people, people with motor impairments, visual impairment, cognitive disabilities, and more.

    This website utilizes various technologies that are meant to make it as accessible as possible at all times. We utilize an accessibility interface that allows persons with specific disabilities to adjust the website’s UI (user interface) and design it to their personal needs.

    Additionally, the website utilizes an AI-based application that runs in the background and optimizes its accessibility level constantly. This application remediates the website’s HTML, adapts Its functionality and behavior for screen-readers used by the blind users, and for keyboard functions used by individuals with motor impairments.

    If you’ve found a malfunction or have ideas for improvement, we’ll be happy to hear from you. You can reach out to the website’s operators by using the following email

    Screen-reader and keyboard navigation

    Our website implements the ARIA attributes (Accessible Rich Internet Applications) technique, alongside various different behavioral changes, to ensure blind users visiting with screen-readers are able to read, comprehend, and enjoy the website’s functions. As soon as a user with a screen-reader enters your site, they immediately receive a prompt to enter the Screen-Reader Profile so they can browse and operate your site effectively. Here’s how our website covers some of the most important screen-reader requirements, alongside console screenshots of code examples:

    1. Screen-reader optimization: we run a background process that learns the website’s components from top to bottom, to ensure ongoing compliance even when updating the website. In this process, we provide screen-readers with meaningful data using the ARIA set of attributes. For example, we provide accurate form labels; descriptions for actionable icons (social media icons, search icons, cart icons, etc.); validation guidance for form inputs; element roles such as buttons, menus, modal dialogues (popups), and others. Additionally, the background process scans all of the website’s images and provides an accurate and meaningful image-object-recognition-based description as an ALT (alternate text) tag for images that are not described. It will also extract texts that are embedded within the image, using an OCR (optical character recognition) technology. To turn on screen-reader adjustments at any time, users need only to press the Alt+1 keyboard combination. Screen-reader users also get automatic announcements to turn the Screen-reader mode on as soon as they enter the website.

      These adjustments are compatible with all popular screen readers, including JAWS and NVDA.

    2. Keyboard navigation optimization: The background process also adjusts the website’s HTML, and adds various behaviors using JavaScript code to make the website operable by the keyboard. This includes the ability to navigate the website using the Tab and Shift+Tab keys, operate dropdowns with the arrow keys, close them with Esc, trigger buttons and links using the Enter key, navigate between radio and checkbox elements using the arrow keys, and fill them in with the Spacebar or Enter key.Additionally, keyboard users will find quick-navigation and content-skip menus, available at any time by clicking Alt+1, or as the first elements of the site while navigating with the keyboard. The background process also handles triggered popups by moving the keyboard focus towards them as soon as they appear, and not allow the focus drift outside of it.

      Users can also use shortcuts such as “M” (menus), “H” (headings), “F” (forms), “B” (buttons), and “G” (graphics) to jump to specific elements.

    Disability profiles supported in our website

    • Epilepsy Safe Mode: this profile enables people with epilepsy to use the website safely by eliminating the risk of seizures that result from flashing or blinking animations and risky color combinations.
    • Visually Impaired Mode: this mode adjusts the website for the convenience of users with visual impairments such as Degrading Eyesight, Tunnel Vision, Cataract, Glaucoma, and others.
    • Cognitive Disability Mode: this mode provides different assistive options to help users with cognitive impairments such as Dyslexia, Autism, CVA, and others, to focus on the essential elements of the website more easily.
    • ADHD Friendly Mode: this mode helps users with ADHD and Neurodevelopmental disorders to read, browse, and focus on the main website elements more easily while significantly reducing distractions.
    • Blindness Mode: this mode configures the website to be compatible with screen-readers such as JAWS, NVDA, VoiceOver, and TalkBack. A screen-reader is software for blind users that is installed on a computer and smartphone, and websites must be compatible with it.
    • Keyboard Navigation Profile (Motor-Impaired): this profile enables motor-impaired persons to operate the website using the keyboard Tab, Shift+Tab, and the Enter keys. Users can also use shortcuts such as “M” (menus), “H” (headings), “F” (forms), “B” (buttons), and “G” (graphics) to jump to specific elements.

    Additional UI, design, and readability adjustments

    1. Font adjustments – users, can increase and decrease its size, change its family (type), adjust the spacing, alignment, line height, and more.
    2. Color adjustments – users can select various color contrast profiles such as light, dark, inverted, and monochrome. Additionally, users can swap color schemes of titles, texts, and backgrounds, with over 7 different coloring options.
    3. Animations – epileptic users can stop all running animations with the click of a button. Animations controlled by the interface include videos, GIFs, and CSS flashing transitions.
    4. Content highlighting – users can choose to emphasize important elements such as links and titles. They can also choose to highlight focused or hovered elements only.
    5. Audio muting – users with hearing devices may experience headaches or other issues due to automatic audio playing. This option lets users mute the entire website instantly.
    6. Cognitive disorders – we utilize a search engine that is linked to Wikipedia and Wiktionary, allowing people with cognitive disorders to decipher meanings of phrases, initials, slang, and others.
    7. Additional functions – we provide users the option to change cursor color and size, use a printing mode, enable a virtual keyboard, and many other functions.

    Browser and assistive technology compatibility

    We aim to support the widest array of browsers and assistive technologies as possible, so our users can choose the best fitting tools for them, with as few limitations as possible. Therefore, we have worked very hard to be able to support all major systems that comprise over 95% of the user market share including Google Chrome, Mozilla Firefox, Apple Safari, Opera and Microsoft Edge, JAWS and NVDA (screen readers), both for Windows and for MAC users.

    Notes, comments, and feedback

    Despite our very best efforts to allow anybody to adjust the website to their needs, there may still be pages or sections that are not fully accessible, are in the process of becoming accessible, or are lacking an adequate technological solution to make them accessible. Still, we are continually improving our accessibility, adding, updating and improving its options and features, and developing and adopting new technologies. All this is meant to reach the optimal level of accessibility, following technological advancements. For any assistance, please reach out to