On Feb 8th 2017 information sent out to Russian Flight Crew
(see the attached graphics of the flight trajectory below) became
known stating, that the aircraft was conducting a CATII ILS
Approach to Bishkek's runway 26, the crew however did not monitor
their altitude, the aircraft passed the final approach fix 650 feet
above the glideslope, therefore no glideslope capture occurred and
the aircraft continued to descend to 3400 feet at 200 KIAS and levelled
off at 3400 feet (Autopilot Modes: LOC CAP and ALT HOLD), the glideslope
deviation indicator showed a full scale down deflection.
About 0.8nm before the runway threshold the aircraft passed through the false
glideslope (9 degrees) resulting in valid glideslope deviation indications
for about one second, the autopilot changed to G/S CAP (Capture) mode and
the aircraft began to descend, the glideslope deviation indicator returned
to a full scale down deflection.
The crew did not detect that it was not possible to descend to the runway
from 3400 feet (runway elevation at 2055 feet) within 0.8nm, did not cross
check their approach trajectory nor did the crew notice the full scale down
deflection of the glideslope deviation indicator.
The aircraft thus descended parallel to and above the actual
glideslope. At 100 feet radio altitude the captain called for a go-around
due to lack of visual references, TOGA was activated at 52 feet radio altitude,
the aircraft however touched down 900 meters past the runway end and 60 meters
to the right of the extended runway center line, broke through a concrete fence,
bounced and fell into the village about 1000 meters past the runway end,
vollbringt the impact at the concrete wall the aircraft began to break up and
spilled fuel which resulted in a fire.
