Yeah! Ce-am ratat-o pe asta!

Ukraine International Airlines Flight PS752 de la Teheran la Kiev s-a prăbușit la câteva minute de la decolare într-o suburbie a Teheranului.
Ora aproximativă a evenimentului 02.48Z. (04.48 ora României)

Ori la acea oră eram online chiar pe flight radar.
La ora 03.51 chiar luasem o captură de ecran a spațiului aerian al României,amuzat fiind să surprind spațiul aerian al României fără nici o aeronavă.

empty

Data și ora din dreapta jos sunt clare. 08.01.2020 ora 03.51.

Dar ce-i mai interesant că anterior acestei capturi am stat cam vreo oră pe spațiul aerian al Iranului și chiar mai mult, am stat cu zoom mărit EXACT pe aeroportul din Teheran.
(am ajuns acolo din plictiseală, în seara zilei anterioare, monitorizând permanent track-ul unei aeronave a Iran Air de la Londra la Teheran, prezentă între 21.30 - 22.00 EET în spațiul aerian al României și am rămas pe Aeroportul din Teheran, simțind în pishuleț că ceva... trebuie să bubuie pe acolo!).

Pe asta am ratat-o!
Dar las că al'dată tot prind Io* în direct, „in real time”, un crash dintr-ăla... spectaculos, cu mațe atârnate prin copaci și multe, multe mortăciuni carbonizate împrășchiate prin brazda patriei.

Poate o să fie vreun wizzair, n-ai văzut? Că-n ultima vreme wizzair a cam început să producă incidente și evenimente care, dacă acum sunt minore, s-ar putea să se acumuleze în timp și să se agraveze.

link înregistrare video a prăbușirii UIA PS752
https://www.youtube.com/watch?v=xRc31DTStwA&feature=emb_logo

(hmmm! 3 explozii consecutive? una în aer, a doua la mică altitudine înainte de prăbușire și a treia - explozia finală la contactul cu solul?)

Din primele date apărute pe agențiile de presă se pare că transponderul aeronavei a încetat să mai transmită cu vreo 4 minute înainte de prăbușire - 02.44 conform playback-ului - iar crash site-ul se află cam la 10 mile nautice EST de locul ultimei transmisii a transponderului, ceea ce confirmă faptul că aeronava era pe un curs de întoarcere către aeroport.
În mod bizar, piloții aeronavei NU AU TRANSMIS nici un semnal de urgență sau altceva care să semnaleze apariția unor probleme la bord.) 

Crash site

Crash site zoom +

Crash site.  

Sursa imaginii Daily Mail UK

Așadar, înregistrarea martorului ocular reprezintă faza finală a zborului, în care avionul  este pe un curs către sud-est, în tentativa de a reveni la aeroport.

-------------------------------


Update 1:
navigând pe diferite site-uri de specialitate și ale unor posturi de știri credibile, nu poate să nu surprindă multitudinea imaginilor ce prezintă fragmente ale avionului având găuri ATIPICE unei prăbușiri cauzate de defecțiuni tehnice.
Aceste găuri, cu specific de tip șrapnel, nu pot proveni decât de la o singură cauză: sursă externă.
Acuma, care or fi generatorii sursei externe - iranienii, americanii, terroriștii, marțienii - deja nu mai contează.

Nu este nevoie să fii investigator NTSB să afirmi cu certitudine că aceste găuri sunt totalmente atipice unui crash bazat pe defecțiuni tehnice.
Seamănă a năibii cu borțile din fuzelajul Malaysian MH17 doborât deasupra Ucrainei.

zoom+

Cea mai edificatoare probă a penetrării aeronavei cu obiecte externe este dovedită de 2 imagini ale stabilizatorului vertical.

stabilizator vertical - privit din partea dreaptă

stabilizator vertical - privit din partea stângă

stabilizator vertical - privit din partea stângă - zoom +

Se poate constata lesne corespondența dimensională exactă dintre orificiul de intrare din partea dreaptă a tail fin cu amprenta inconfundabilă a orificiului de ieșire din partea stângă a tail fin.

Așadar: explozia unui corp străin, în partea dreaptă a aeronavei (în partea de EST a traiectoriei aeronavei, aflată pe un heading cuprins între 289 și 312 grade).

 

---------------------
Update 2:

Pepita de aur (Golden nugget)

„Iranian social media released footage of suspicious wreckage that was founded nearly of passenger jet crash place. 
Suspicious wreckage found at Ukraine plane crash impact site appears to be the nose cone section and control fins of 9M331 surface-to-air missile. 
It is employed by the Russian-made Tor-M1 mobile air defense system and features a semi-automatic command to line of sight (SACLOS) guidance system. 
This system currently in service of the Iranian military deployed at a military base near the crash site.”

sursa: defence-blog

Deci TOR- M1 short-range surface-to-air missile system este talharul. 
Produs de ruși și importat de iranieni.

Dacă la Malaysian MH-17 a fost BUK-M1, acum văd că e vorba de Tor.

Să mai zică careva că rușii nu fac marafeturi acătării, nu ca știfturile alea ruginite ale americanișilor, care fac pârț și cad în capul oaminilor cinstiți și sărmani.

Auzi, bre, că cea de-a doua generație de SAM Tor-M2 a atins o rată a interceptărilor de ... 100%.
UAU! 

Bun, dar exact ca în cazul MH17, nu cine a produs racheta sol-aer e esențial ci întrebarea întrebătoare de baraj este: CINE A APĂSAT PE LAUNCH BUTTON ?

Iranienii într-o impardonabilă eroare?

Americanișul, într-o standard operațiune „false flag”, soră semantică și metodologică cu „maskirovka” russească?

======================================================================= 


Update 3: după fragmentul video prezentat pe Aviation Herald, a apărut un altul care surprinde momentul lovirii avionului de o rachetă.

 Newsy + Bellingcat: Annotated Video Showing Apparent Shoot-Down Of Flight PS752

sursa video:
https://www.bellingcat.com/news/mena/2020/01/09/video-apparently-showing-flight-ps572-missile-strike-geolocated-to-iranian-suburb/ 

și diagrama locului identificat al martorului precum și zona prezumată a impactului, calculată pe baza diferenței de propagare a imaginii / sunetului

======================================================================= 

Hai să mă bag și Io* în seamă pe Aviation Herald:

Căci, căutând o noapte întreagă care sunt datele exacte transmise de transponderul PS752 până în momentul întreruperii, pentru a stabili cert ultima transmisie a transponderului, după ce am identificat cert locul prăbușirii, după ce am găsit coordonatele geografice ale DVOR-DME Imam Khameini  Airport (IKA), după ce am găsit hărțile standard de apropiere și depărtare, măsurând cu rigla Google Earth rezultă că pilotul PS752 a început manevra de întoarcere la dreapta la ora 02.44.17Z.
Până la acea  oră a avut un head de 289.
Acolo începe headingul 290 și se sfârșește cu ultimul heading de  312 grade.
Măsurând distanța dintre locul începerii manevrei și DVOR-DME IKA rezultă că a început întoarcerea la exact 10,54 mile de DME.

Ori harta standard arată că această acțiune se procedează la 17 mile de DME (17 DME IKA)

În atare condiții se poate enunța o ipoteză veridică:
În nord-vestul aeroportului din Teheran, după cum se poate observa pe Google Earth, este full de unități militare.
În seara zilei precedente - 7 ian. 2019, au fost lansate cele 22 de rachete iraniene împotriva obiectivelor americane din Iraq.
După o noapte întreagă de surescitare, oboseală și stres, așteptându-se probabil să fie atacați drept reacție la cele 22 de rachete lansate, iranienii au intrat exact în acea psihoză paranoidă în care, de exemplu, erau forțele armate române în 22 dec. 1989: acel moment de iraționalitate pură în care nu mai știi cine este amic și cine este inamic, ce este normal și ce este anormal ca activitate observabilă, în care percepția evenimentelor înconjurătoare se efectuează după cu totul alți senzori decât cei „de pe timp de pace”.

În atare condiții psihologice, avionul ucrainean decolează ca de obicei.
Probabil tot ca de obicei, controllerul iranian îi permite heading  to PAROT waypoint, pentru a-l scoate cât mai repede din zona capitalei iraniene.
Însă, pentru mințile întunecate de psihoză și teamă ale militarilor de la sol, un avion care se îndreaptă mult prea devreme spre amplasamentul lor, virând evident către obiectivele lor militare, aflat la o altitudine atât de mică (6000 de picioare = aprox. 2000 de metri), li s-o fi părut a fi inamic.

De aici în continuare nu mai e nimic de interpretat, rațiunea dispărând în totalitate.

Un deget fremătând pe butonul de lansare al unei instalații SAM Tor-1M, de producție rusească dar importată de Iran și aflată în dotarea FAA iraniene.

ATÂT!

(continuare pe The Aviation Herald)

02:44:17Z start turning right
By Edelweiss on Friday, Jan 10th 2020 15:13Z

@pilotnico

quote
„Aren't there airplanes flying on a regular basis?”

I expressed the same concern last night:

”why did PS752 get vector to the right so early, after only 10 miles from DVOR-DME IKA?”

If I read this site it is to search for and receive credible information coming from professionals in the field.
But it seems that this site is full of enthusiastic fans of the exaggerated discussion of theisms irrelevant to the case.

So, I come back:
Why PS752 was vectored so fast from head 289 to head 312?
(10,55 nm from DME IKA).

PS 752 granular CSV file:
2020-01-08 02:44:17Z.796,0x508377,35.46024,51.00204,6025,5510,275,290

35.46024 N = 35°27'36.86"N
51.00204 E = 51° 0'7.34"E

This shortcut procedure, combined with the state of arousal, fatigue and stress accumulated in the evening of January 7 and the night between January 7 and 8, can create the factual and psychological context that led to this catastrophe?

@Edelweiss
By reader on Friday, Jan 10th 2020 15:53Z

I think, you are incorrect in saying that the plane was vectored "early" to the right. You are right, that PS-752 the day before continued straight longer, however PS-752 on January 4th was also cleared for a right turn at pretty much the same location and followed the same trajectory as on the accident flight.

The only difference in the two trajectories is that the accident flight was delayed for departure by half an hour but that is all I see from the data.

@reader
By Edelweiss on Friday, Jan 10th 2020 17:24Z

I propose to study the reference points of flight PS752 from January 6, 2020. You will have a very big surprise, a surprise that is in full agreement with the Standard departure chart.

Departure at heading 289,
(35°31'0.74"N 50°46'52.39"E) 1st turning point to right to heading 306 at 23.59 nm DME IKA,
(35°32'25.90"N 50°44'14.77"E) 2nd turning point to head 316 at 26,45 nm DME IKA and
(approximately 36°13'45.86"N 49°55'25.15"E) 3rd turning point to left after PAROT way point.

So unfortunate error of (probably) tower controller to admit the turn to the right too early it may be a secondary but essential circumstance of this aviation tragedy.

Look over what area the aircraft was redirected too fast?
Over that area full of military units and military objectives.
Military objectives whose personnel were already after a night of stress, fatigue and anguish of an imminent attack.

diferențele dintre zborurile dintre 6 ianuarie și 8 ianuarie

@Edelweiss
By 727driver on Friday, Jan 10th 2020 17:34Z

Thx, indeed a very interesting observation.

@727driver
By Edelweiss on Friday, Jan 10th 2020 18:09Z

With pleasure.
At this point I remember the words of NTSB investigator Greg Feith: never an aircrash is caused by a single cause. There is always a combination of circumstances that trigger the tragedy.
The cause of the PS752 crash is already evident:
(politically correct) deflagration of a body device outside the aircraft, deflagration produced on the right side of the flight path, most likely at the moment when the transponder transmissions has stopped to work.

I brought to your attention an essential detail, which can justify that subjective component of the catastrophe.

The departure mode of the PS752 is a bizarre mix between the standard departure chart AD 2 OIIE SID 1-5:

PAROT 3G DEP: DEP RWY 29L/R – After Take off turn left climb on RDL 285 up to 17 DME (RDL316 FM RUS VOR) then turn right to intercept RDL 311 FM RUS VOR to PAROT and climb to cleared level.

PAROT 2H DEP: DEP RWY 29L/R – After take off turn right to intercept RDL 305 to PAROT and climb to cleared level.

By Edelweiss on Friday, Jan 10th 2020 18:18Z

Instead of "body" will be read ”device”

”Interesting” sites on the Google Earth
By Edelweiss on Friday, Jan 10th 2020 23:28Z

2 ”interesting” sites at 3.6 - 5.4 miles northwest of the presumed position of the hitted airplane in video no. 2

Google Earth:

35°33'43.96"N 50°53'55.54"E

35°35'21.24"N 50°53'33.82"E

The second landmark is more than interesting with the access gate, the guardrails along the fences, the fighting technique visible in different points but especially in the back, where there are those excavated sites and those underground access gates.
Military objectives within the range of SAM Tor-M1 - 7.5 nm = 12 km.
Towards ... the northwest of ”estimated area of impact”

interesting sites

 site 1

site 2

site 2 zoom +

By Mark on Friday, Jan 10th 2020 23:49Z

@Edelweiss The point at which the aircraft turns North looks to vary quite a bit looking at the ADS-B from the 4th, 6th and 8th. It's the same plane with all three flights.

not 3, only 2 departure methods
By Edelweiss on Saturday, Jan 11th 2020 00:56Z

@ Mark
January 8 is exactly the same departure trajectory as January 4.
The position of the last transmission of the transponder is exactly on the route at heading 312 (311) to PAROT.

But I think this is a shortcut departure from the IKA.
In the PS752 cockpit there were 3 pilots: captain, FO and another captain instructor.

The only one responsible for this vectorization can only be the tower / approach controller.

This trajectory-shortcut fly over those bizarre objectives, the coordinates of which I have posted previously.

My unprofessionally verdict: a double error:

an careless controller
&
a finger trembling on the launch button, panicked by the approach of an aircraft at low altitude and on the direct route.

CVR & FDR
By Tom on Friday, Jan 10th 2020 23:55Z

Question for anyone that knows: Can the data on the recorders be altered in any way other than complete erasure?
 

ACI enthusiast viewer
By Edelweiss on Saturday, Jan 11th 2020 01:38Z

@Tom
Yes!

Ask captain Michel Asseline - Air France 296 Flight - how CVR and FDR data can be manipulated. :)

„The TV documentary series Mayday also reports claims in Season 9 Episode 3 that the flight recorder might have been tampered with and indicated that four seconds had been cut from the tape; this was shown by playing back a control tower tape and comparing it to the remaining tape. The pilot argues that he attempted to apply thrust earlier than indicated in the flight recorder data.”

&

„It was also claimed by the Institute of Police Forensic Evidence and Criminology, based in Lausanne, Switzerland, that the flight data recorders may have been switched and were not the original ones in the aeroplane.”
 

===============================

premature vectorization
By baned Edelweiss on Saturday, Jan 11th 2020 13:02Z

- a STANDARD DEPARTURE based on the chart - PAROT 3G DEP: DEP RWY 29L/R – After Take off turn left climb on RDL 285 up to 17 DME (RDL316 FM RUS VOR) then turn right to intercept RDL 311 FM RUS VOR to PAROT and climb to cleared level.

RADAR DEPARTURE: on RWY heading climb to maintain 7000 ’ , EXPECT RADAR vectors.
(or departure end of runway climb on runway heading maintain 7.000 feet, contact Mehrabad radar 119.7 when airborne expect radar vectors).

It is not a valid argument that other aircraft followed the same departure procedure. Analyze the departure of the PS752 from January 6 and you will have a big surprise.

Anyway, my opinion is that the Teheran tower controller or Mehrabad ATC prematurely vectored the aircraft to head 312: only 5900 ft and only 10.55 nm DME IKA.

This detail is essential to understanding the confusion of AA forces.

remembrance
By Edelweiss on Saturday, Jan 11th 2020 15:16Z

Without contesting the doubtful evidences of this case (the rocket guiding cone or the inlet / outlet holes in the vertical stabilizer), yesterday I tried to discuss other objective / subjective elements that can complement the cumulative circumstances that led to this tragedy.

”This shortcut procedure, combined with the state of arousal, fatigue and stress accumulated in the evening of January 7 and the night between January 7 and 8, can create the factual and psychological context that led to this catastrophe?”

„So unfortunate error of (probably) tower controller to admit the turn to the right too early it may be a secondary but essential circumstance of this aviation tragedy.

Look over what area the aircraft was redirected too fast?
Over that area full of military units and military objectives.
Military objectives whose personnel were already after a night of stress, fatigue and anguish of an imminent attack.”

„I remember the words of NTSB investigator Greg Feith: never an aircrash is caused by a single cause. There is always a combination of circumstances that trigger the tragedy.”

The Statement of IAF confirmed the factual and psychological ensemble that led to this tragedy.

@Edelweiss
By 727driver on Saturday, Jan 11th 2020 15:25Z

Yeah, looks like another example of swiss cheese model.

- off track
- shift change of militaries at 06:00 LT
- not monitoring TWR FREQU ?
 

exactly that fateful accumulation of circumstances
By Edelweiss on Saturday, Jan 11th 2020 15:35Z

@727driver
Exactly!
Also add vectorization under standard altitude (7000).
Today we examined some Tehran radar departures and when they were vectored:

Jan 11 20
Radar departures and vector turning right at…
Mahan Air IRM112: 7200 ft
Turkish THY8WC: 7200 ft
Iran Air IRA733: 7525 ft
Iran Air IR751: 7425 ft
Qeshm Airlines QSM2273: 7.850 ft (initial vectored a little bit to the left)

PS752 was vectored to teh right at 5.900 ft.

So, it is more than justified the phrases: „TAKING THE SHAPE AND ALTITUDE OF A HOSTILE TARGET” and „such SENSITIVE AND CRITICAL CIRCUMSTANCES”.

So many circumstantial elements were gathered as if we were reviewing the Tenerife crash - The Crash of Century

Edelweiss - accurately and open source
By 727driver on Saturday, Jan 11th 2020 22:17Z

Very well observed.

Nowadays the world is a global village....;)
 

  

Edelweiss - accurately and open source
By Edelweiss on Saturday, Jan 11th 2020 22:53Z

727 driver believe me I haven't read Christo at all.

I didn't even have time.
We wasted 2 whole nights haunting Google earth on a circle sector from north to west, with a radius equal to the TOR-M1 official range: 7.5 miles = 12 km.

I have seen homes, mining, refineries, to reach me for the next 30 years.

The only interesting landmarks were those communicated yesterday evening, after it was evident that there is a certain military objective for sure: quard towers visible after the shadow,military technique, solid fences, access routes, gates to underground shelters and especially those unmistakable sites for military technique dug into the ground.

My posting was yesterday evening at 23.28 UTC.

Today I see that Christo appears around noon and specifies that the presumed place of launch is not where he calculated he is 3 km further northwest.
Exactly the second landmark indicated by me.

Nice work, bro Christo!
 

Question
By (anonymous) on Sunday, Jan 12th 2020 07:33Z

Is the turning instruction from ATC partly responsible for this tragedy?

@Question
By Edelweiss on Sunday, Jan 12th 2020 13:29Z

YES!
I think so.
An essential factor in this tragedy is the neglected vectorization performed by ATC.
This is the hypothesis that I have tried to promote on attention, with objectivity and decency.
Keep track of my posts from the past days in the AHerald archive.

The data are unquestionable: a departure from the Tehran airport seems to be a typical Radar departure.

Although the instructions require 7000 feet (FL070) as the cleared level, at which the plane can be vectorized to PARROT waypoint, PS752 was vectored to the PAROT at only 5900 feet.
PREMATURELY.

Otherwise the entire climb up path of the PS752 suggests a slow climbing.
Compared to other aircraft taking off on the same routes, differences of 1500 feet less in the turning point to the right and 2000 feet less at the point of the last transponder transmission.

Maybe this premature vectorization, along with the altitude below radar departure instructions, justifies that expression in the IAF staff statement
”TAKING THE SHAPE AND ALTITUDE OF A HOSTILE TARGET”

We can somehow know which is the automatic target selection algorithm implemented in the Tor-M1 system?

If there is somewhere there is a "line" of software that is cynically indifferent:
”Each radar spot at an altitude of less than 7,000 feet can be a presumptive enemy”
„Each target below 7000 feet, located on a course directly to the site of the Air Defence facility, is highly likely to trigger an attack on the base.”

We can't know how "thinks" that little tin-mind in Tor-M1? Not!

But we know for sure that the radar clearance instructions provide for a mandatory (mandatory) level: 7.000 ft.

And we also know that someone - IKA Tower Controller or Mehrabad ATController - vectorized the aircraft in violation of the mandatory requirements of the departure instructions.

PS752 was TOO LOW.

@seven-two-sewen-delta-romeo-india-victor-echo- romeo
By Edelweiss on Sunday, Jan 12th 2020 14:04Z

Based on the good understanding we have created with each other, I propose a credible point of view:
No, the military isn’t unprofessional, but they are as unbelieving as Thomas (incredulous, distrustful, suspicious, mistrustful).

For them a callsign is nothing more than a presentation that can be a mask, which can be misleading.
There are countless examples of military operations in which jetfighters or aircrafts carrying troops were hidden under callsigns of civilian planes or were in the radar shadow of some civilian aircraft.

 e.g.

- israeli forces intervened at the airport in Entebbe - Uganda in 1976
- american surveillance aircraft under the radar shadow of KAL007
- ukrainian Sukhoi who maneuvered in the immediate vicinity (shadow) of MH17

And so on.

So for a military man from an anti-aircraft military objective the data received from the sources mentioned by you may be unbelievable data.
His experience and military training requires him to be circumspect and to rely only on his own devices and technique.

For the military man with his finger on the release button, a callsign has the same theoretical value as John Doe or Jane Doe.

Interesting point of reference, isn't?

De aici în continuare, cele mai prețioase comentarii au fost cenzurate de un bou austriac. Plus cenzurate gârlă dintre comentariile zilei de 11, în dialog cu 727driver, Werner Huss sau Ziberov.

Despre cel mai prețios comentariu cenzurat, vezi postarea The success of halberd and robbery journalism

==========================================================================

Măsurători pe hartă:

8 ian. 2020 - punctul de start a întoarcerii spre dreapta se află la doar 10,55 mile de DME IKA

6 ian: primul punct de începere a headingului  306 se află la 23,59 mile de DME

cel del-al doilea punct de ăntoarcere pe vectorul 316 este la 26,45 mile de DME.

Altitudinea PS752 la vectorizarea spre head 312: doar 5.900 de picioare.

Spre comparație, altitudinea altor aeronave, vectorizate în ziua de 11 ian. 2020:

Jan 11 20
Radar departures and vector turning right at…

Mahan Air IRM112: 7200 ft
Turkish THY8WC: 7200 ft
Iran Air IRA733: 7525 ft
Iran Air IR751: 7425 ft
Qeshm Airlines QSM2273: 7.850 ft (initial vectored a little bit to the left)

==========================================================================

Epilog 11 ian 2020: 

Iranul a recunoscut doborârea din greșeală a avionului ucrainean.

End of story!

(fragmentele evidențiate cu majuscule confirmă circumstanțele obiective și subiective enunțate în comentariile din zilele de 9 și 10 ian. 2020)

 ”1- Following the threats made by the president and military commanders of the criminal United States to target many positions inside the territory of the Islamic Republic of Iran in case of a reciprocal operation [by Iran], and considering the unprecedented increase in aerial moves in the region, the Armed Forces of the Islamic Republic of Iran WERE AT THE HIGHEST LEVEL OF STANDBY IN ORDER TO [BE ABLE TO] RESPOND TO POSSIBLE THREATS. 

2- In early hours after the missile attack [on US’ Ain al-Assad base in Iraq], the military flights of the US’ terrorist forces had increased around the country. The Iranian defence units received news of witnessing flying targets moving towards Iran’s strategic centres, and then several targets were observed in some [Iranian] radars, which INCITED FURTHER SENSITIVITY AT THE AIR DEFENCE UNITS.

3- Under such SENSITIVE AND CRITICAL CIRCUMSTANCES, the Ukrainian airline’s Flight PS752 took off from Imam Khomeini Airport, and when turning around, it approached a sensitive military site of the IRGC, TAKING THE SHAPE AND ALTITUDE OF A HOSTILE TARGET. In such conditions, due to human error and in an unintentional move, the airplane was hit [by the Air Defence], which caused the martyrdom of a number of our compatriots and the deaths of several foreign nationals.”

 The Statement of General Staff of the Iranian Armed Forces----------

=======================================================================

arhivă
PS752-Granular-Data

time, hex, latitude, longitude, altitude, squawk, speed, track

2020-01-08 02:41:36Z.074,0x508377,35.41348,51.16485,0,5510,17,289

2020-01-08 02:41:37Z.884,0x508377,35.41356,51.16456,0,5510,20,289

2020-01-08 02:41:40Z.912,0x508377,35.41363,51.16432,0,5510,22,289

2020-01-08 02:41:44Z.164,0x508377,35.41383,51.16358,0,5510,36,286

2020-01-08 02:41:47Z.194,0x508377,35.41405,51.16279,0,5510,49,289

2020-01-08 02:41:49Z.662,0x508377,35.41427,51.16199,0,5510,62,289

2020-01-08 02:41:53Z.838,0x508377,35.41462,51.16076,0,5510,74,286

2020-01-08 02:41:56Z.694,0x508377,35.41512,51.15899,0,5510,90,289

2020-01-08 02:41:57Z.602,0x508377,35.41525,51.15852,0,5510,94,289

2020-01-08 02:42:08Z.316,0x508377,35.41708,51.15187,3050,5510,129,288

2020-01-08 02:42:11Z.804,0x508377,35.41772,51.14965,3075,5510,139,288

2020-01-08 02:42:14Z.824,0x508377,35.4185,51.14685,3075,5510,151,288

2020-01-08 02:42:17Z.342,0x508377,35.4191,51.14473,3075,5510,157,288

2020-01-08 02:42:20Z.382,0x508377,35.41983,51.142,3075,5510,165,288

2020-01-08 02:42:24Z.010,0x508377,35.42081,51.13867,3075,5510,175,288

2020-01-08 02:42:27Z.628,0x508377,35.42166,51.13564,3150,5510,180,289

2020-01-08 02:42:30Z.178,0x508377,35.42248,51.13265,3250,5510,179,288

2020-01-08 02:42:33Z.932,0x508377,35.42336,51.12957,3425,5510,177,289

2020-01-08 02:42:34Z.004,0x508377,35.42336,51.12957,3425,5510,177,289

2020-01-08 02:42:36Z.032,0x508377,35.4239,51.12757,3500,5510,178,288

2020-01-08 02:42:38Z.752,0x508377,35.42481,51.12447,3575,5510,183,289

2020-01-08 02:42:39Z.202,0x508377,35.42481,51.12447,3575,5510,183,289

2020-01-08 02:42:43Z.744,0x508377,35.42596,51.12047,3675,5510,187,289

2020-01-08 02:42:44Z.364,0x508377,35.42625,51.11938,3700,5510,188,289

2020-01-08 02:42:46Z.252,0x508377,35.42683,51.11738,3750,5510,190,289

2020-01-08 02:42:48Z.198,0x508377,35.42756,51.11483,3825,5510,193,289

2020-01-08 02:42:48Z.708,0x508377,35.4277,51.11435,3825,5510,193,289

2020-01-08 02:42:52Z.456,0x508377,35.42853,51.11143,3925,5510,196,289

2020-01-08 02:42:54Z.444,0x508377,35.42928,51.10887,4025,5510,197,289

2020-01-08 02:42:54Z.984,0x508377,35.42947,51.10822,4050,5510,197,289

2020-01-08 02:42:57Z.546,0x508377,35.4304,51.10495,4175,5510,197,289

2020-01-08 02:42:58Z.524,0x508377,35.43068,51.10402,4200,5510,196,288

2020-01-08 02:42:58Z.542,0x508377,35.43068,51.10402,4200,5510,196,288

2020-01-08 02:43:00Z.984,0x508377,35.43142,51.10133,4300,5510,197,288

2020-01-08 02:43:03Z.772,0x508377,35.43226,51.09835,4375,5510,199,288

2020-01-08 02:43:03Z.800,0x508377,35.43226,51.09835,4375,5510,199,288

2020-01-08 02:43:03Z.854,0x508377,35.43226,51.09835,4375,5510,199,288

2020-01-08 02:43:07Z.042,0x508377,35.43324,51.09484,4450,5510,203,289

2020-01-08 02:43:08Z.576,0x508377,35.4337,51.09318,4475,5510,205,289

2020-01-08 02:43:09Z.608,0x508377,35.4337,51.09318,4475,5510,205,289

2020-01-08 02:43:10Z.480,0x508377,35.43435,51.09098,4500,5510,207,289

2020-01-08 02:43:14Z.400,0x508377,35.43528,51.08771,4525,5510,211,289

2020-01-08 02:43:14Z.432,0x508377,35.43544,51.08723,4550,5510,211,289

2020-01-08 02:43:14Z.888,0x508377,35.43544,51.08723,4550,5510,211,289

2020-01-08 02:43:16Z.400,0x508377,35.43626,51.08426,4575,5510,216,289

2020-01-08 02:43:17Z.460,0x508377,35.43663,51.08305,4575,5510,218,289

2020-01-08 02:43:19Z.540,0x508377,35.43715,51.08117,4600,5510,220,289

2020-01-08 02:43:20Z.070,0x508377,35.43732,51.08053,4600,5510,220,289

2020-01-08 02:43:23Z.548,0x508377,35.43837,51.07693,4675,5510,223,289

2020-01-08 02:43:24Z.640,0x508377,35.43874,51.07561,4700,5510,224,289

2020-01-08 02:43:25Z.178,0x508377,35.43892,51.07509,4700,5510,225,289

2020-01-08 02:43:25Z.524,0x508377,35.43942,51.07332,4725,5510,226,289

2020-01-08 02:43:28Z.704,0x508377,35.44052,51.06937,4775,5510,232,289

2020-01-08 02:43:28Z.752,0x508377,35.44052,51.06937,4775,5510,229,289

2020-01-08 02:43:28Z.774,0x508377,35.44052,51.06937,4775,5510,232,289

2020-01-08 02:43:32Z.646,0x508377,35.44157,51.06571,4825,5510,234,289

2020-01-08 02:43:34Z.594,0x508377,35.44244,51.06268,4875,5510,237,289

2020-01-08 02:43:35Z.022,0x508377,35.44244,51.06268,4875,5510,237,289

2020-01-08 02:43:35Z.900,0x508377,35.44276,51.06153,4875,5510,238,289

2020-01-08 02:43:37Z.552,0x508377,35.44377,51.05816,4900,5510,241,289

2020-01-08 02:43:38Z.950,0x508377,35.44432,51.05627,4925,5510,244,289

2020-01-08 02:43:39Z.034,0x508377,35.44432,51.05627,4925,5510,244,289

2020-01-08 02:43:40Z.640,0x508377,35.44492,51.0541,4975,5510,246,289

2020-01-08 02:43:43Z.632,0x508377,35.44611,51.05015,5025,5510,248,289

2020-01-08 02:43:44Z.680,0x508377,35.44611,51.05015,5025,5510,248,289

2020-01-08 02:43:44Z.740,0x508377,35.44611,51.05015,5025,5510,248,289

2020-01-08 02:43:47Z.346,0x508377,35.44734,51.04586,5125,5510,251,289

2020-01-08 02:43:49Z.088,0x508377,35.44823,51.04283,5200,5510,252,289

2020-01-08 02:43:49Z.142,0x508377,35.44823,51.04283,5200,5510,252,289

2020-01-08 02:43:50Z.556,0x508377,35.44864,51.04149,5250,5510,253,289

2020-01-08 02:43:53Z.774,0x508377,35.44991,51.03722,5350,5510,254,289

2020-01-08 02:43:54Z.206,0x508377,35.44991,51.03722,5350,5510,254,289

2020-01-08 02:43:54Z.860,0x508377,35.45032,51.03576,5375,5510,255,289

2020-01-08 02:43:55Z.884,0x508377,35.45097,51.03354,5425,5510,257,289

2020-01-08 02:43:58Z.890,0x508377,35.45215,51.02943,5500,5510,261,289

2020-01-08 02:43:59Z.300,0x508377,35.45232,51.02887,5500,5510,261,289

2020-01-08 02:43:59Z.362,0x508377,35.45215,51.02943,5500,5510,261,289

2020-01-08 02:44:03Z.304,0x508377,35.45358,51.0246,5550,5510,264,289

2020-01-08 02:44:05Z.150,0x508377,35.45435,51.02194,5575,5510,267,289

2020-01-08 02:44:05Z.186,0x508377,35.45435,51.02194,5575,5510,267,289

2020-01-08 02:44:05Z.714,0x508377,35.45479,51.02045,5600,5510,268,289

2020-01-08 02:44:08Z.198,0x508377,35.45605,51.01612,5675,5510,271,289

2020-01-08 02:44:09Z.170,0x508377,35.45645,51.01473,5700,5510,272,289

2020-01-08 02:44:10Z.190,0x508377,35.45645,51.01473,5700,5510,272,289

2020-01-08 02:44:12Z.704,0x508377,35.45755,51.01089,5800,5510,273,289

2020-01-08 02:44:14Z.276,0x508377,35.45865,51.00718,5900,5510,274,289

2020-01-08 02:44:15Z.288,0x508377,35.45865,51.00718,5900,5510,274,289

2020-01-08 02:44:15Z.344,0x508377,35.45865,51.00718,5900,5510,274,289

2020-01-08 02:44:17Z.796,0x508377,35.46024,51.00204,6025,5510,275,290

2020-01-08 02:44:19Z.152,0x508377,35.46085,51.00014,6100,5510,275,291

2020-01-08 02:44:19Z.160,0x508377,35.46085,51.00014,6100,5510,275,291

2020-01-08 02:44:20Z.674,0x508377,35.46168,50.99789,6175,5510,275,292

2020-01-08 02:44:23Z.698,0x508377,35.46341,50.99361,6325,5510,274,297

2020-01-08 02:44:24Z.242,0x508377,35.46368,50.99293,6350,5510,274,297

2020-01-08 02:44:24Z.256,0x508377,35.46368,50.99293,6350,5510,274,297

2020-01-08 02:44:25Z.754,0x508377,35.46428,50.99155,6400,5510,274,297

2020-01-08 02:44:25Z.772,0x508377,35.46428,50.99155,6400,5510,274,297

2020-01-08 02:44:25Z.772,0x508377,35.46428,50.99155,6400,5510,274,297

2020-01-08 02:44:32Z.914,0x508377,35.46964,50.9816,6800,5510,274,305

2020-01-08 02:44:34Z.072,0x508377,35.47048,50.98019,6850,5510,274,306

2020-01-08 02:44:34Z.564,0x508377,35.4709,50.97954,6875,5510,275,306

2020-01-08 02:44:35Z.952,0x508377,35.47202,50.97776,6925,5510,275,307

2020-01-08 02:44:39Z.606,0x508377,35.47453,50.97404,7075,5510,275,309

2020-01-08 02:44:40Z.124,0x508377,35.47453,50.97404,7075,5510,275,309

2020-01-08 02:44:40Z.684,0x508377,35.47504,50.97341,7100,5510,275,309

2020-01-08 02:44:42Z.364,0x508377,35.47737,50.97021,7225,5510,276,311

2020-01-08 02:44:44Z.406,0x508377,35.47911,50.96792,7325,5510,276,312

2020-01-08 02:44:45Z.476,0x508377,35.48007,50.96666,7350,5510,276,313

2020-01-08 02:44:45Z.498,0x508377,35.4796,50.96727,7325,5510,276,313

2020-01-08 02:44:48Z.612,0x508377,35.48286,50.96306,7500,5510,276,313

2020-01-08 02:44:49Z.592,0x508377,35.48365,50.96201,7550,5510,276,313

2020-01-08 02:44:50Z.076,0x508377,35.48365,50.96201,7550,5510,276,313

2020-01-08 02:44:51Z.570,0x508377,35.48543,50.95968,7650,5510,276,313

2020-01-08 02:44:54Z.692,0x508377,35.48813,50.95608,7800,5510,276,312

2020-01-08 02:44:54Z.694,0x508377,35.48813,50.95608,7800,5510,276,312

2020-01-08 02:44:55Z.146,0x508377,35.48845,50.95562,7825,5510,276,312

2020-01-08 02:44:57Z.384,0x508377,35.49046,50.95299,7925,5510,275,312

2020-01-08 02:44:57Z.914,0x508377,35.49046,50.95299,7925,5510,275,312

2020-01-08 02:44:57Z.962,0x508377,35.49046,50.95299,7925,5510,275,312

Evoluția constantă a principalilor parametri - altitudine și viteză - poate conduce la ideea că locul ultimei transmisii a transponderului este chiar LOCUL LOVIRII AERONAVEI DE ACEL CORP STRĂIN (ca să grăiesc political correct).
Acuma, luând în considerare caracteristica de short range a Tor-M1 - poate lovi ținte de la 12 km (7,5 mile), aflate la altitudini de 6.000 de metri (20.000 de picioare), se poate trage un cerc cu raza de hai să zicem 15 km în jurul locului ultimei transmisii a transponderului și se poate căuta... talharul.