MTCD is a generic term for ATC automatic conflict detection about 10 minutes flying ahead, based on flight data processing and its trajectory prediction.
Operationally used applications:
- at Amsterdam ACC under the name Area COnflict Detection (ACOD), where a predecessor of the current system has been working for decades
- in several Centres in the United States under the name User Request Evaluation Tool (URET). URET is also appreciated as a paperstrip replacement system. First experience in Indianapolis some ten years ago and gradually expanded to more centres.
- at the ACC of Riga in Latvia.
Eurocontrol has produced generic specifications and exercised a number of successfull trials in Malmo Sweden, Roma and Maastricht UAC. They assist European ATC units willing to introduce MTCD.
The major challenge is the ability of the Flight Data Processing System to correctly predict the future trajectory of the aircraft. The best results are achieved when controllers keep the FDP system updated. Of course the FDP must be capable of coping correctly with the controller inputs and have an intuitive presentation not requiring extensive study.
Generally, an MTCD is hardly compatible with a paperstrip system. When the FDP system is not kept updated electronically, the MTCD produces too many erroneous signals, annoying the controller who will give up using it - rubbish in/rubbish out. Controllers have no time to make inputs twice, written on the paperstrip and on the electronics. But when electronic systems have a history of failures controllers will prefer sticking to their paperstrips. A bit of catch22 which explains the hardship to introduce MTCD.
Hope this helps. Any progress in Greece?