Russian term (edited): �������� �� ��������� ������� ������ �� ������

Change of taxi time report

Russian term (edited): �������� �� ��������� ������� ������ �� ������

This answer has been made invisible to others.


Comment for Kurt

I think these are important hairs :). Yes, there is this RPRT abbreviation for "report", also used in aviation e.g. for weather reports. BUT there is a very specific thing, called MVT, — "movement telex message", or sometimes simply "movement telex", and _not_ a "report". Taking the risk of being too insistent, I would dare ask you to look at the docs and specifications issued by IATA, Eurocontrol, etc.

I am not here for KudoZ points etc but to help colleagues, and I always stand for the translator to know her/his subject before trying to translate. This KudoZ system is of great help for many people by and large. I dare say however that in some cases it pushes people to suggest terms beyond their level of reasonable awareness and knowledge. I am afraid we have this sort of situation here.

I think what we need first of all is to understand which "время прибытия" and "руление" is meant here. There are several possible options, some of them listed here starting with the most probable one (this is not and exhaustive list):
1) "Время прибытия" to the gate, which can change because of longer taxiing after landing. Then, the parameters used include EONB (estimated on-block time) and AIBT (actual in-block time), and they will both change. There may be an MVT from the arrival airport, notifying of that change e.g. the next airport if this is a transit.
2) Both "время прибытия" to the gate and the landing time can change due to the fact that there was longer taxiing before take-off. In theory, there may be an MVT called "Сообщение об изменении времени прибытия по рулению" sent by the _departure airport_ to the arrival airport. However, there is I think an MVT sent anyway notifying of the actiual take-off time, so I don't think there is an extra MVT in this case.

I am not sure of either option however. Therefore, I have
(1) asked the asker too look at the meaning of the source text, to (maybe) understand from there which "время прибытия" and which "руление" are meant here, and
(2) tried to find the guy I know (close friend of my relatives), who is a top-level manager within the Ukrainian ATC system and knows for sure all those MVT formats. (No reply from him as yet.)

With regard to your example about two pilots relaying their taxi report through another pilot, this is not a valid example here, since their reports sent (probably by voice?) to the ATC tower, other pilots, etc, are not movement telex messages, or MVTs, which are clearly mentioned in Alexander's question.

Please stay assured that I don't mean any offence, but simply ask you to be careful about some important details of what we're talking about.

--------------------------------------------------
Note added at 19 hrs 31 mins (2004-07-24 16:16:21 GMT)
--------------------------------------------------

Just one more thing to add. Here we are not talking \"об изменении времени руления\", but \"об изменении времени прибытия по рулению\", so, irrespective of our discussion on \"message\" vs. \"report\" etc, it shouldn\'t be \"regarding change in taxi time\", but some change in arrival/in-bloick|whatever time, that change being either related somehow to taxiing, or simply _after_ taxiing. Remember that in Russian \"по\" has both meanings of \"вследствие\" (like in \"по причине\") and \"после\" (like in \"по окончании\").

--------------------------------------------------
Note added at 3 days 5 hrs 26 mins (2004-07-27 02:10:51 GMT)
--------------------------------------------------

Well, I\'ve got it!

At http://www1.iata.org/WHIP/_Files/WgId_0041/MTGCALL.doc , there is an IATA memorandum once sent to the members of the Aircraft Movement Control Messages Working Group. I saw it already several times within the last two days, but did not grasp the most important part, as far as this question goes.

Talking about the new time code, RTNS (Return to Normal Schedule), it says:
\"2. The previous Aircraft Control and Movement Messages Working Group proposal said FLD would be included in all relevant messages, however, the REVISED ETA (PART 3G), and the ARRIVAL TAXI TIME VARIANCE (PART 3H) do not have the FLD included as an optional element. FLD to be valid with these two messages.

6. ...Alternatively users can just use their same MVT masks and put RTNS in place of the time leading to more compliance with this method. It would be used in all existing times type message:
DEP (EX., ADRTNS/RTNS, ADRTNS, AD06RTNS/06RTNS, EARTNS, EBRTNS)
ARR (EX., AARTNS AARTNS/RTNS, AA/RTNS, AA07RTNS/07RTNS)
DELAY (EX., ED05RTNS, NI05RTNS)
RETURNS (EX., RRRTNS, EBRTNS, FRRTNS/RTNS, FRRTNS, FR/RTNS, EARTNS, EBRTNS)
REVISED ETA (EX., EARTNS, EBRTNS)
ARR TAXI VARIANCE (EX., AARTNS, EBRTNS).\"

So this one is Arrival Taxi Variance message, and the right answer to Alexander\'s previous question is \"Revised Estimated Time of Arrival message\".

I think what contributed to my confusion (and probably not just mine :) ) here was mixing of two things. I kept thinking in terms of \"certain type of MVT message <=> certain type of time code used\". But types of MVT messages themselves, and types of timings used in them, are different things. So, for example, EB code for Estimated On-Block Time can be used in a Departure-type MVT, or Revised ETA-type MVT, or Arrival Taxi Time Variance MVT.

We did it! Kurt, thank you for your input: I am always interested in getting things sorted out, but you made me interested even deeper in this ATC staff :).

So, I hope you guys will all agree by now: the final answer is

Arrival Taxi Time Variance message

Huh :)

--------------------------------------------------
Note added at 3 days 14 hrs 43 mins (2004-07-27 11:27:54 GMT) Post-grading
--------------------------------------------------

I\'ve just noticed that after I deleted this answer accidentally, I\'ve managed to restore it by copying from my screen in such a complete form that even \"This answer has been made invisible to others.\" is here :).