Announcement

Collapse
No announcement yet.

Malaysian B777 MH17 crash - poss shot down

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #31
    I suspect the FR24 do receive transponder data from the military flights even though they don't share it, and could release it to the proper authorities if requested.

    Comment


    • #32
      Originally posted by Birdie View Post
      Singapore Airlines got caught with their pants down - for lying that Singapore Airlines do not use Ukraine airspace.
      Really they said that? Within less then an hour 3 more Singapore airliners will pass within 50Km of the strike zone, some as close as 20Km. All 3 Singapore airliners were A380's. It took about 2 hours before word got out there and aircraft started to re-route away from the strike zone.

      MAS17 is shot down at 13:21 z

      At 13:41 just 20 minutes later, Singapore Airlines SQ333, an A380 from Paris will pass just 50Km south of the strike zone.
      sia333.jpg

      At 14:00 Singapore Airlines SQ25, an A380 from Frankfurt will pass just 20Km south of the strike zone.
      sia25.jpg

      At 14:16 Singapore Airlines SQ317, an A380 from London will pass just 50Km south of the strike zone.
      sia317.jpg
      www.ADS-B.ca

      Comment


      • #33
        Originally posted by peterhr View Post
        I suspect the FR24 do receive transponder data from the military flights even though they don't share it, and could release it to the proper authorities if requested.
        Depending on their mission, Military aircraft will use various other modes that are none civilian including mode Five a cryptographically secured version of Mode S.
        www.ADS-B.ca

        Comment


        • #34
          In light of the recent incident, Malaysia Airlines’ Amsterdam (AMS) – Kuala Lumpur (KUL) service,
          MH17 flight number will be retired out of respect for our crew and passengers of the mentioned flight code. This will take into effect on 25 July 2014.

          There are no changes to the frequency of our services and we will continue to operate daily services between Amsterdam and Kuala Lumpur.

          The new flight number replacing MH17 will be:

          MH19 - AMS/KUL

          Our thoughts and prayers remains with the families of our colleagues and passengers of MH 17.

          -end-

          Source: http://www.malaysiaairlines.com/my/en/site/mh17.html
          Brian

          www.RadarSpotters.eu
          [ Feeder Station List ][ Map ][ Latest Feeders Rank Stats ][ ImRadarFeeder.com Radar Feeders WorldWide Map ][ VRS Feeder List ] (NEW)

          Comment


          • #35
            I have a question about the last position. 13:21:28 490 kts 33000 ft 48.0403 38.7728 taken from https://twitter.com/flightradar24/st...348864/photo/1
            This position would be some 15km southeast of the crash location. Is this data interpolated? If I understand correctly the last positions are reported from F-UKHH1 a receiver in Kharkiv, which is quite far away. Does the distance to a receiving station affect the "quality" of the data? Or is it pure digital with error control, all or nothing. Thanks in advance.

            2014-07-21 07_54_01-MH17-greenshot.jpg

            Comment


            • #36
              Originally posted by agrona72 View Post
              I have a question about the last position. 13:21:28 490 kts 33000 ft 48.0403 38.7728 taken from https://twitter.com/flightradar24/st...348864/photo/1
              This position would be some 15km southeast of the crash location. Is this data interpolated? If I understand correctly the last positions are reported from F-UKHH1 a receiver in Kharkiv, which is quite far away. Does the distance to a receiving station affect the "quality" of the data? Or is it pure digital with error control, all or nothing. Thanks in advance.

              [ATTACH=CONFIG]4421[/ATTACH]
              F-UKHH1 simply indicates Kharkiv is the closest AIRPORT to the receiver location. Generally the airspace it is likely to cover. It doesn't mean thats where it is, it could be 100nm away, but cover with 300nm radius.

              No, it does not effect the quality. The GPS co-ordinates come from the aicraft itself. Sent to the transponder, and broadcast to be received by the hardware on the ground.
              Posts not to be taken as official support representation - Just a helpful uploader who tinkers

              Comment


              • #37
                48.0403 38.7728 looks about right... The last radar was T-UKHH1 receiving the ADS-B ... once signal was lost you'll see the FR24 system flip over to T-EST1 which I believe was MLAT trying to re-acquire the transponders signal. Once that failed it gave up.

                shot-down-here.jpg
                www.ADS-B.ca

                Comment


                • #38
                  RC

                  I am not a professional or "even" an amateur but I stumbled accross one strange thing concerning this tragic flight.

                  Here is the link: https://www.facebook.com/photo.php?f...type=3&theater
                  This is Kor Pan's photo on his FB page before the flight with comment:
                  10409688_465419050262262_114194042050554154_n.jpg
                  Mocht hij verdwijnen , zo ziet hij d'r uit .
                  (That's how our plane looks like in case we get lost). Alluding to the 777 vanished in march.

                  Note 1: I don't see the date and time when this photo was uploaded (and EXIF of the downloaded image is blank) and I don't know how to get this information but the time and date of the first comment is 17 July 2:12 (I guess PM Amsterdam time). The following comments tell that Cor Pan was on MH-17 on July 17, 2014.

                  Note 2: My eyes tell that almost certainly there are letters "RC" on the front gear leg "hatch". This is, as far as I understand, the last letters of the plane registration code. Malasian Airlines has only one plane ending with RC - 9M-MRC. But the problem is that the shutdown plane is 9M-MRD. And the second problem is that that day 9M-MRC was nowhere near Europe
                  (http://www.flightradar24.com/data/airplanes/9m-mrc)

                  Note 3: Kor Pan, as far as I understand, really was a passenger of MH-17. I briefly looked the passenger manifest but didn't find him there. Perhaps its his nickname.

                  In the following article: http://www.thestar.com.my/News/World...alks-to-Putin/
                  one can see that the photo is almost the same as in FB page. It was shot from the same place, and compared to it FB-photo looks like cropped. And there are no 2 thick yellow hoses attached to the belly of the plane + in the pilot's window there is some white thing that changes place. So these are two different photos and the article says that it belongs to REUTERS/Yaron Mofaz.
                  The caption says:
                  Malaysia Airlines Flight MH-17 is seen at the G3 gate of Schiphol Airport in Amsterdam, before it took off, heading to Kuala Lumpur, July 17, 2014. REUTERS/Yaron Mofaz
                  While writing this post I've found one more informative article about this story: http://www.examiner.com/article/cor-...-crash-to-come

                  Update: one more "RC"-article: http://chemtrailsplanet.net/2014/07/...d-crash-scene/
                  Last edited by Sergej Kuznetsov; 2014-07-21, 11:37. Reason: update 1

                  Comment


                  • #39
                    Can you comment this plan?

                    4.jpg

                    Comment


                    • #40
                      Log change

                      Can anyone explain why previous MH17 flight routes taken from 14 to 16 July were changed post factum?
                      Was: on 2014-07-17 21:51:00 (http://signor-antonio.livejournal.com/378722.html)
                      Now: 14 July: http://www.flightradar24.com/data/flights/mh17/#3cfb05b
                      15 July: http://www.flightradar24.com/data/flights/mh17/#3d1c512
                      16 July: http://www.flightradar24.com/data/flights/mh17/#3d3d13f

                      Same thing on flightaware.

                      On 17 July evening (as you see on the screenshots on signor-antonio.livejournal.com) these routes 14-16 July were much more southward. Over Sea of Azov. Now they are exactly over the place of the crash.


                      Originally posted by tester View Post
                      Can you comment this plan?
                      Who is asked?
                      Attached Files
                      Last edited by Sergej Kuznetsov; 2014-07-21, 16:34. Reason: update

                      Comment


                      • #41
                        I think it was due to bad weather in that area on July 17. Maybe one of the reasons it went more 'north' on the 17th.
                        The other days before the 17th, the flights were more south in that area.
                        Maybe someone can find weather reports from those days you talked about.
                        Last edited by SoCalBrian; 2014-07-21, 16:41.
                        Brian

                        www.RadarSpotters.eu
                        [ Feeder Station List ][ Map ][ Latest Feeders Rank Stats ][ ImRadarFeeder.com Radar Feeders WorldWide Map ][ VRS Feeder List ] (NEW)

                        Comment


                        • #42
                          Originally posted by SoCalBrian View Post
                          I think it was due to bad weather in that area on July 17. Maybe one of the reasons it went more 'north' on the 17th.
                          The other days before the 17th, the flights were more south in that area.
                          Maybe someone can find weather reports from those days you talked about.
                          Perhaps I didn't phrase it quite clearly.
                          In my previous post I noted that screenshots of MH-17 flights for the dates 14-16 July taken on 17 July evening differ from that same MH-17 flights for the dates 14-16 July which are available now.
                          It looks like they were "corrected". Moved to North. Over the crash place.
                          What are the reasons of such a phenomenon?

                          Comment


                          • #43
                            That would be best for someone from FR24 to answer.
                            Since they are the only one that can edit that tracking information after the flights are done flying.
                            They would be able to show what was deleted/changed.
                            Last edited by SoCalBrian; 2014-07-21, 17:08.
                            Brian

                            www.RadarSpotters.eu
                            [ Feeder Station List ][ Map ][ Latest Feeders Rank Stats ][ ImRadarFeeder.com Radar Feeders WorldWide Map ][ VRS Feeder List ] (NEW)

                            Comment


                            • #44
                              Originally posted by SoCalBrian View Post
                              That would be best for someone from FR24 to answer.
                              Since they are the only one that can edit that tracking information after the flights are done flying.
                              They would be able to show what was deleted/changed.
                              I see.
                              But the thing is that it also occurred with flightaware dot com.
                              I have prooflinks only concerning flightaware. As for FR24, I remember that I visited it, looked for MH-17 flights and I don't remember that there were differences with screenshots from here http://signor-antonio.livejournal.co...22.html?page=4. Alas, I don't copy each screen I look through (that is an idea - computer black box).

                              Comment


                              • #45
                                One more prooflink of precrash routes:
                                http://scallywagandvagabond.com/2014...ace-put-peril/
                                l4.jpg

                                Comment

                                Working...
                                X