This is the Boeing 737-500 involved in the flight 363 crash. Image: Osudu / Flickr

This is the Boeing 737-500 (VQ-BBN) involved in the flight 363 crash. Image: Osdu / Flickr

Earlier today, a Tatarstan Airlines’ Boeing 737-500 (reg VQ-BBN) crashed in the city of Kazan, killing all on-board. Flight 363, which took off from Moscow’s Domodedovo International Airport (DME) and was heading to Kazan International Airport (KZN), had 44 passengers and six flight crew.

A Russia’s Investigative Committee said in a release that the plane, “hit the runway and burst into flames.” The aircraft aborted one landing attempt and then crashed during the second. At this time, it is unknown what caused the crash and why the first landing attempt was aborted.

Screen shot of a video taken at the crash scene. Click to via video on Telegraph.co.uk

Screen shot of a video taken at the crash scene. Click to via video on Telegraph.co.uk

The weather at the time of the crash had light rain and winds.

One of the passengers on-board the aircraft appears to be the son of the Governor of the Republic of Tatarstan.

Boeing has released the following statement: “Boeing extends its deepest condolences to the families of those who perished in the Aircompany Tatarstan Flight U9-363/2B-363 accident on landing in Kazan, Russia, in route from Moscow. A Boeing technical team will launch to provide technical assistance to the investigation at the request and under the direction of Russia’s investigating authority, the Interstate Aviation Committee. In accordance with the international protocol governing aviation accident investigations, all inquiries about the investigation must be directed to the NTSB.”

MORE TATARSTAN FLIGHT 363 INFORMATION

This story was written by one or more of our AirlineReporter staff members. Email us: [email protected]

http://www.airlinereporter.com
Photo Tour of the Boeing 737 Renton Factory
1 Comment

Last time I checked, which was yesterday when I flew a 737… it didn’t have a prop on it.

Leave a Reply

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