Full no-fly! Russian Emergency Investigation Map-22M3 Bomber Crash Cause

 Full no-fly! Russian Emergency Investigation Map-22M3 Bomber Crash Cause

Reference News Network reported Jan. 24 that Russia Today television website published on Jan. 22 Georgi Mosalovs report entitled Falling in Sudden Snow: Tu-22M3 crash in Mormansk resulted in three deaths.

Reported that on January 22, a Tu-22M3 strategic bomber of the Russian Aerospace Force crashed in the Russian state of Molmansk. Russias Ministry of Defense issued a news that the bomber crashed in a sudden snowfall during flight training. Two crew members died on the spot, while the other died in hospital. A wounded man is in critical condition. Tupolev, the bombers R&D unit, explained that the Tupolev-22M3 that crashed was overhauled in 2012 and that company experts would be involved in the investigation of the cause of the accident.

Mormansk Disaster Medical Center released a message that the Russian Tu-22M3 supersonic long-range bomber accident killed three crew members: two died at the time of the accident, the other died in hospital. Russian news agency quoted the news as saying: Three people died and one was injured - in intensive care.

According to the Information and Mass Media Department of the Russian Ministry of Defense, the Tu-22M3 bomber had an accident during flight training: it had suffered a short violent snowstorm. Sources from the Russian Ministry of Defense said: On January 22, 2019, a Tu-22M3 crashed into snow and made a forced landing after completing planned flight training in Mormansk. As a result, the bomber crashed because of the failure of the forced landing.

DATA PICTURE: The moment of takeoff of Russian Tu-22M3 strategic bomber. (Pictures come from the Internet)

DATA PICTURE: Russian Tu-22M3 counter fire bombs air strikes IS targets in Syria. (Pictures come from the Internet)

Russias Ministry of Defense stressed that the timing of the accident was not loaded. There was a fire at the accident site, but it was put out quickly. According to preliminary information, the fire at the site of the accident has been extinguished, said the Mormansk State Government Press Bureau.

For safety reasons, emergency department staff carried the bomber wreckage away from the accident site. Bomber wreckage is being evacuated and transported to a safe location, emergency sources told Tass.

The Russian Defense Ministry Committee arrived at the Mormansk Airport to find out all the circumstances of Tu-22M3s failure to make a forced landing. All possibilities of accidents, including military aircraft technical failures, are currently being studied.

Powerful Department sources told Tass News Agency that the cause of the accident may also be crew errors. He explained: The weather is getting worse and the bombers have a sudden snowfall. In this case, driving errors are likely to occur, which leads to forced landing failure. As a result, the bombers structure was damaged and it caught fire.

DATA PICTURE: Training data map of Russian Tu-22M3 bomber troops. (Pictures come from the Internet)

Reported that Tupolevs News Office told Tass that Tupolevs experts will participate in the investigation of the cause of the bomber crash. Experts from R&D companies and manufacturers will be involved in the work of the accident investigation committee, Tass quoted a representative of Tupolevs Information Service as saying.

Tupolev said the Tu-22M3 bomber that crashed was manufactured in 1986 and overhauled in 2012. In 1983, Tu-22M3 was loaded into the Soviet Army. The last of the bombers was manufactured in 1993. A total of 268 Tu-22M3 were manufactured.

According to public statistics of the Russian Army, Tu-22M3 had only one accident before, when it landed at Novgorod Airport in July 2004. Four crew members died at that time. The cause of the accident was a technical failure of the bomber.

Powerful Department sources told Tass that all Tu-22M3 will be banned until the cause of the accident is ascertained.

Source: Responsible Editor of Reference Message Network: Yao Wenguang_NN1682