Turkish Airlines cargo 747 crashes in Kyrgyzstan

[runway30]

Turkish Airlines cargo jet crash kills 16

[tech log]

Dreadful news.

[TBSC]

B-747-400F(SCD), reg. TC-MCL, operating flight Turkish TK6491 HKG-FRU.


METARs (the crash happened at 0119-0120 UTC):

UCFM 160100Z VRB01MPS 0050 R26/300N FZFG VV001 M09/M10 Q1023 R26/19//60 NOSIG
UCFM 160130Z VRB01MPS 0150 R26/550 FZFG VV001 M09/M10 Q1024 R26/19//60 NOSIG

[PositiveClimbGearUp]

Death toll now reported as 30. Crew of 4 on board.

http://sptnkne.ws/dqr7

[Kulverstukas]

[psychomantic]

It's not Turkish Airlines cargo plane, but was a wet lease from ACT Airlines, aka My Cargo Airlines.

[Airbubba]

First glance at the FR24 data indicates a possible overrun after touching down on the runway. Looks like they were lined up on runway 26:

https://www.flightradar24.com/data/f...k6491/#c2d9d64

[jmjdriver1995]

Reuters article on the crash. Turkish cargo jet crash kills at least 30 in Kyrgyzstan

[atakacs]

Originally Posted by Airbubba

First glance at the FR24 data indicates a possible overrun after touching down on the runway. Looks like they were lined up on runway 26:

https://www.flightradar24.com/data/f...k6491/#c2d9d64

Well from the pictures it would have a been a hell of an overrun... But at this stage I guess anything is possible.

[Ganzic]

Crash

Looks like the rescue operation is pretty much still ongoing. It looks like they crashed past the rwy on the north side, https://www.google.co.uk/maps/place/...1!4d74.4364417


SA 16/01/2017 06:30->
METAR COR UCFM 160630Z VRB01MPS 0500 R26/0550N FZFG VV002
M08/M09 Q1022 R26/19//60 NOSIG=
SA 16/01/2017 06:00->
METAR UCFM 160600Z VRB01MPS 0350 R26/0400N FZFG VV001 M08/M10
Q1023 R26/19//60 NOSIG=
SA 16/01/2017 05:30->
METAR UCFM 160530Z 00000MPS 0250 R26/0300N FZFG VV001 M08/M09
Q1023 R26/19//60 NOSIG=
SA 16/01/2017 05:00->
METAR UCFM 160500Z 00000MPS 0200 R26/0250N FZFG VV001 M08/M09
Q1023 R26/19//60 NOSIG=
SA 16/01/2017 04:30->
METAR UCFM 160430Z 00000MPS 0150 R26/0200N FZFG VV001 M09/M10
Q1023 R26/19//60 NOSIG=
SA 16/01/2017 04:00->
METAR UCFM 160400Z VRB01MPS 0150 R26/0175N FZFG VV001 M09/M10
Q1024 R26/19//60 NOSIG=
SA 16/01/2017 03:30->
METAR UCFM 160330Z VRB01MPS 0100 R26/0150N FZFG VV001 M09/M10
Q1024 R26/19//60 NOSIG=
SA 16/01/2017 03:00->
METAR UCFM 160300Z VRB01MPS 0100 R26/0150N FZFG VV001 M09/M10
Q1024 R26/19//60 NOSIG=
SA 16/01/2017 02:30->
METAR UCFM 160230Z VRB01MPS 0100 R26/0250N FZFG VV001 M09/M10
Q1024 R26/19//60 NOSIG=
SA 16/01/2017 02:00->
METAR UCFM 160200Z VRB01MPS 0150 R26/0375N FZFG VV001 M09/M11
Q1024 R26/19//60 TEMPO 0100 FZFG=

Wx in that region in winter has taken many lives in the past. Although it looks right on the numbers for CAT2 ILS RW26.

[Airbubba]

Originally Posted by atakacs

Well from the pictures it would have a been a hell of an overrun... But at this stage I guess anything is possible.

The data on FR24 looks pretty solid to me. I don't think those houses were on the runway and the village they hit is indeed west of the airport.

A decelerating descent on the glide is depicted but the groundspeed seems high with the last data point at 162 knots at 0116Z. This seems to correlate with the last point on the FlightAware plot giving 165 knots a few seconds earlier:

Flight Track Log THY6491 16-Jan-2017 HKG / VHHH - FRU / UCFM FlightAware

[DaveReidUK]

Originally Posted by Airbubba

The data on FR24 looks pretty solid to me. I don't think those houses were on the runway and the village they hit is indeed west of the airport.

A decelerating descent on the glide is depicted but the groundspeed seems high with the last data point at 162 knots at 0116Z. This seems to correlate with the last point on the FlightAware plot giving 165 knots a few seconds earlier:

Though at the 162 kt point they still had about half of Bishkek's 14,000 ft/4,200 m runway ahead of them, and were around 3,000 m from the nearest habitation.

Clearly there's more to the story than is apparent from the FR24/FlightAware data.

[Capt Groper]

Cold WX may be a casual factor

Flight tracking data, if correct, indicates A/C platformed at 3100', Jep chart states 3400'.
M09 ~ 10% diff ~= 300'
Just an observation of the published data.

[exynos]

Originally Posted by Capt Groper

M09 ~ 10% diff ~= 300'

Could you please explain this?
Regards.

[Kulverstukas]

Local authorities said that it overfly RWY, then hit the fence and crashed at the houses. Also was said that pilot managed to get out but died on the way to hospital. Death toll now is about 31 and nine body parts found...

[Akrep]

Originally Posted by exynos

Could you please explain this?
Regards.

Cold weather correction for altitude

Rule of thumb -10c add 10% altitude to your altimeter for your real altitude.
In short in cold weather your indicated altitude is always higher then you really are.

[golfyankeesierra]

In short in cold weather your indicated altitude is always lower then you really are

You mean the other way around!!

Your true altitude (height) is lower then the indicated.
Remember: cold=dangerous

[DaveReidUK]

[bekolblockage]

Flight tracking data, if correct, indicates A/C platformed at 3100', Jep chart states 3400'.

FR24 will be showing uncorrected Mode C data. (encoded alt based on 1013)

QNH was 1023/1024 according to the METARs.
30 ft/HPa
So 300 ft sounds about right.

[Capt Groper]

Cold WX corr

Originally Posted by exynos

Could you please explain this?
Regards.

http://http://code7700.com/altimeter_temperature_correction.html

Review first image for picturial explanation.

However this platform ALT diff has now been explained by the previous post by bekolblockage. FlightAware altitude data is based on 1013mb.