airport cdm münchen - Airport Collaborative Decision Making

Airport CDM München 

AIRPORT 

COLLABORATIVE 

DECISION 

MAKING 

- AIRPORT CDM 

MÜNCHEN - 

- BRIEF DESCRIPTION - 

Version 4

Version: V4.0 

Author: Airport CDM Team München 

Date: 07.05.2007 

Number of pages: 18 


Airport CDM MUC –Brief Description Page 2

Table of contents 


1. Diagram ..................................................................................................................... 4 

2. Brief description ......................................................................................................... 5 

2.1. General.............................................................................................................. 5 

2.2. Flight plan validation.......................................................................................... 5 

2.2.1. Early DPI — data exchange with the CFMU.............................................. 5 

2.2.2. Target DPI — data exchange with the CFMU ........................................... 5 

2.2.3. Flight Update Message (FUM) — data exchange with the CFMU............. 6 

2.2.4. Automated target off-block time (TOBT).................................................... 6 

2.3. Person responsible for TOBT ............................................................................ 7 

2.4. TOBT reporting routines .................................................................................... 7 

2.5. TOBT correction/deletion................................................................................... 8 

2.5.1. Cancel DPI — data exchange with the CFMU........................................... 9 

2.6. Target start-up approval time – TSAT acknowledgement ................................. 9 

2.7. TOBT and TSAT in extreme situations.............................................................. 9 

2.7.1. HTML masks............................................................................................ 10 

2.7.2. SEPL dialogue......................................................................................... 11 

2.7.3. Internetdialog „WEASEL“......................................................................... 12 

2.7.4. MAS page................................................................................................ 13 

2.8. De-icing ........................................................................................................... 13 

2.9. Changes within the sequence ......................................................................... 13 

2.10. Start-up and push-back ................................................................................... 14 

2.10.1. Datalink Clearance - DCL ........................................................................ 14 

2.10.2. ATC DPI – data exchange with the CFMU .............................................. 14 

2.11. Coordination with the CFMU ........................................................................... 15 

2.12. Remote holding ............................................................................................... 15 

2.13. Contact address and information..................................................................... 15 

2.13.1. Airport CDM information messages......................................................... 16 

3. Aeronautical Information Publication – AIP –........................................................... 18 

3.1. Persons responsible for the process/contact persons..................................... 18 


1. Diagram 

0800 0800 0830 0830 Airport CDM München 

1200 1030 0900 1000 0930 1100 1130 1230 1200 1030 0900 1000 0930 1100 1130 1230 ATC- 

FPL 

(EOBT-3) 

F 

U 

M 

Early-DPI 

(FPL/Schedule-Comparison) 

Estimated Landing time 

(CFMU/DFS) 

Final 

approach 

Take Off 

Outstation Landing 

EOBT-2 

(CTOT) 

TSAT 

Issue 

(TOBT- 

40) 

Target-DPI 

(„Slot Adjustment Window“) 

This diagram depicts the scope of the airport CDM procedure at Munich Airport from the 

time when the ATC flight plan is activated (EOBT -3h) to take-off. The blue arrows show 

the data flow of the CFMU, the orange arrow shows the exchange of information via email 

with the relevant aircraft operator or handling agent, with regard to any adjustments 

which may become necessary. 

TSAT 

Aircraft 

ready 

Ground Start 

handling Up 

ASAT 

„Inblock“ 

Start 

Ground 

handling 

TOBT 

Automatic generated TOBT 

Information Information exchange exchange via via „E-mail „E-mail „ mail“ mail“ “ with with AO/HA 

AO/HA 

(i.e (i.e i.e. i.e. . EOBT/SOBT-Mismatch 

EOBT/SOBT-Mismatch 

EOBT/SOBT Mismatch; Mismatch; ; Acft-Type Acft-Type Acft Type; Type; ; Acft-Registration 

Acft-Registration 

Acft Registration) 

AOBT 

Airport CDM MUC –Brief Description Page 4 

ATC 

DPI 

(CTOT 

Freeze) 

„Take 

Off“ 

ATOT

2. Brief description 


2.1. General 

The turnround process at Munich Airport has been reorganised on the basis of the 

existing confirmed off-block (COB) procedure in Munich and the activities concerning the 

Airport Collaborative Decision Making (CDM). 

The improved quality of the inbound and outbound information is used to optimise the 

chain process from arrival to departure. This optimisation led to the so-called "target 

start-up approval time (TSAT)", i.e. the time at which a Pilot in command / Flight Crew 

can expect the start-up approval at the latest. This TSAT is an essential factor for the 

preparation of a "pre-departure sequence" which takes the requirements of all involved 

parties into account. 

A permanent and fully automated data exchange with the Central Flow Management Unit 

(CFMU) will be implemented to connect the local airport CDM procedure with the 

European air traffic flow and capacity management (ATFCM) in the best possible 

manner. Due to this process, reliable estimated landing and in-block times can be given 

at an earlier time and the calculated take-off time (CTOT) will be more reliable. 

2.2. Flight plan validation 

ATC flight plans for departures are validated with regard to their airport slot, i.e. the 

scheduled off-block time (SOBT). Every flight is requiered to have an airport slot. 

If there is no airport slot available or if the SOBT deviates from the estimated off-block 

time (EOBT) of the ATC flight plan, the contact address of the airline will be informed 

together with the request to coordinate and adjust the time accordingly. 

If there is no Airport Slot available at the beginning of expected flight operations, no 

further sequencing and operational handling will take place for that specific flight. 

2.2.1. Early DPI — data exchange with the CFMU 

An early departure planning information message (E-DPI) is transmitted to the CFMU for 

validated flight plans. The CFMU system indicates flights for which there is an E-DPI as 

flights from a CDM airport. These are then considered accordingly in the further 

processing (e.g. optimized CTOT allocation according to local target times). 

2.2.2. Target DPI — data exchange with the CFMU 

As a rule, for all flights a T-DPI is generated 2 hours before EOBT for which an E-DPI 

was generated. The T-DPI is transmitted to the CFMU in the same way as the E-DPI. 

The T-DPI is used to transmit a local target take-off time (TTOT) to the CFMU. The T- 

DPI opens a so-called "slot adjustment window" within which the CTOT is to be adjusted 

to the local TTOT in the best possible way. 

If the TTOT is changed by five minutes or more (e.g. new TOBT), a new T-DPI is 

generated and transmitted to the CFMU. 



2.2.3. Flight Update Message (FUM) — data exchange with the CFMU 

The CFMU generates and sends flight update messages (FUM) for inbound flights to 

Munich Airport. The following operational events trigger the transmission of an FUM: 

• Estimated landing time (ELDT) minus 3 hours 

• Modification of the ELDT by 5 minutes or more (parameter 5-15 minutes) 

• Change to the ETFMS status, e.g. suspension of a flight 

The FUM provides an ELDT at an early stage. This allows the system to compare the 

inbound with the outbound flight plan, i.e. the EIBT 1 with the EOBT. A comparison is 

made between the receipt of the ATC flight plan and the generation of the TOBT (TMO). 

In the case of inconsistencies, the contact address of the airline will be informed 

accordingly. The airline is expected to react immediately by adjusting either the relevant 

times (DLA message) or the outbound flight plan (CNL message or aircraft type change). 

2.2.4. Automated target off-block time (TOBT) 

At final approach (12 minutes out), the system automatically generates a TOBT. The 

earliest possible time for automatic TOBT generation is 75 minutes before TOBT 

(provision). 

TOBT: Automatically generated point of time, whose supervision and updates are 

in the responsibility of the Airline/Handling Agent. TOBT is the time when 

all ground handling processes will be finished, the aircraft doors closed 

and the boarding bridge removed. At this time the start-up approval could 

be received and the push-back/taxi clearance can be given. TOBT is a 

reference time used for all ground handling processes except for aircraft 

push-back and de-icing. This time is used for coordination purposes, since 

it is the best available time. 

If the time period between in-block and EOBT is less than the Minimum Ground Time 

(MGT), a TOBT with the time value in-block plus MGT is generated. The MGT depends 

on the airline, the aircraft type and the destination. Another condition for the primary 

automated calculation of a correct TOBT is that the TOBT plus the remaining time (RMT) 

are either earlier or the same as the CTOT, otherwise, the TOBT is not generated. 

Graphic: 

„Twelve „Twelve Twelve 

Minutes 

Minutes 

Out“ 

Out“ 

TMO 

TMO 

Arrival 

Arrival 

InBlock 

InBlock 

Ground Ground handling 

handling 

TOBT-calculation 

TOBT-calculation 

TOBT calculation and and adjustment 

adjustment 

1 EIBT is ITA (or ELDT) + 5 minutes 

TSAT TSAT issue issue at 

at 

TOBT-40 TOBT-40 TOBT 40 

End End ground 

ground 

handling 

handling 

= = TOBT 

TOBT 

Pilot Pilot waites waites for 

for 

„Start „Start Up Up Given“ Given 

De De Ice Ice at at apron 

apron 

Latest Latest time time for 

for 

Startup Startup Given Given = 

= 

TSAT 

TSAT 

OffBlock 

OffBlock 

Remote 

Remote 

De De Icing 

Icing 

Take Take off 

off 

CTOT 

CTOT 

EOBT-3h EOBT-3h EOBT 3h Data Data exchange exchange with with CFMU 

CFMU 

Take Take Off 

Off 



Important dependencies for the primary TOBT generation: 

• Automated TOBT = EOBT if: EIBT + MGT ≤ EOBT 

• Automated TOBT = EIBT + MGT if: EIBT + MGT > EOBT 

• Automated TOBT for flights with CTOT only if: TOBT + RMT ≤ CTOT 

If the TOBT is not automatically generated for a flight, it must be entered by the TOBT 

responsible person (2.3) as described in 2.4. 

For aircraft which are not part of a direct turnaround and which do not park on their 

outgoing position, the TOBT is generated at "off-block from the direct preceding 

position". 

2.3. Person responsible for TOBT 

Once the TOBT has been generated automatically, the handling agent, the airline (for 

flights without handling agents) or the pilot-in-command / Flight crew (for general aviation 

flights without handling agent) is responsible for the correctness of and adherence to the 

TOBT. 

If it becomes obvious that the TOBT cannot be respected or shall be brought forward, it 

must be corrected or re-entered by the person responsible for the TOBT. 

It is still mandatory to send a delay message (DLA) to the CFMU if the EOBT deviates by 

15 minutes or more. 

2.4. TOBT reporting routines 

TOBT are reported in one of the following ways: 

• SEPL dialogue 

• Internal system of the airline / handling agent (via system interface) 

• HTML interfaces at all gates 

• FMG traffic operations centre via telephone (+49 (0)89 975-21135) 

• Internet dialog “WEASEL” 

Airline Airline Operator Operator / / Handling Handling Agent Agent / / TWR TWR 

FMG 

FMG 

SEPL-Dialog 

SEPL-Dialog 

SEPL Dialog 

AO AO / / HA 

HA 

Interface 

Interface 

Systems Systems for for Counter 

Counter 

Management 

Management 

Internet Internet Dialog 

Dialog 

WEASEL 

WEASEL 

By By telephone 

telephone 

www 

a 

b 

c 

d 

e 

Basis System Verkehr 

System 

System 

SEPL 

SEPL 

Traffic Traffic operation 

operation 

center 

center 


f


For general aviation flights the pilot in command report appropriate changes: 

• At the counter of the general aviation terminal [+49 (0)89 975-21498; opening 

hours Monday-Sunday from 0440 to 2120 (0340 to 2020)], either in person or by 

telephone. 

• Outside the opening hours of the counter by telephone to the FMG traffic 

operations centre (+49 (0)89 975-21135). 

Luftfahrzeugführer / 

Handling Agent 

Counter 

Telefonisch 

Telefonisch 

a 

a 

General Aviation 

Traffic operation 

center 

FMG 

Basis System Verkehr 

System 

SEPL 

2.5. TOBT correction/deletion 

If the TOBT is not generated automatically or cannot be adhered to, it must be corrected 

or re-entered by the person responsible for the TOBT. 

The TOBT can be updated as often as necessary until the TSAT has been issued. Once 

the TSAT has been issued, the TOBT can only be updated three times. A fourth 

correction is not possible; instead the TOBT must be deleted and entered again. The 

new TOBT must be at least 5 minutes later than the current point in time. 

As the TOBT is triggering additional processes at the airport, TOBT adaptations (also if 

shifting to earlier TOBT of more than 5 minutes) have to be made by the person 

responsible for the TOBT using one of the published TOBT reporting routines. 

If the TOBT is changed to an earlier time after the TSAT has been issued, the new TOBT 

must be at least 5 minutes later than the current point in time. 

If a flight is to be excluded from the TOBT or TSAT calculations, the TOBT is to be 

deleted by way of the aforementioned reporting routines. 

The airline operator may have to initiate a delay message (DLA) in order to undo such a 

process interruption. The TOBT must be adjusted by the person responsible for the 

TOBT. If the aircraft is changed, a change message (CHG type/registration) has to be 

filed. TOBT will remain unchanged and will be assigned to the new aircraft. 


a 

b b


2.5.1. Cancel DPI — data exchange with the CFMU 

When the TOBT for a flight is deleted, a C-DPI message is transmitted to the CFMU. The 

flight is excluded from the special handling process (for flights from CDM airports). The 

CTOT is then issued on the basis of the normal flight plan data until a new DPI is 

available for the flight. 

2.6. Target start-up approval time – TSAT acknowledgement 

The TSAT is calculated 40 minutes before the reported TOBT. The TSAT is the time at 

which the start-up approval and the en-route clearance can be expected at the latest. 

Once the TSAT has been calculated or acknowledged, the TOBT can be corrected a 

maximum of three times. 

The TSAT acknowledgement is made using: 

• SEPL dialog 

• Internal system of the airline operator/handling agent 

• Information systems of FMG (MAS / FIS) 

• FMG traffic operations centre 

• HTML interfaces at all gates 

• Internet dialog “WEASEL” 

For general aviation flights the pilot in command report appropriate changes: 

• At the counter of the general aviation terminal [+49 (0)89 975-21498; opening 

hours Monday-Sunday from 0430 to 2120 (0330 to 2020)], either in person or by 

telephone. 

• Outside the opening hours of the counter by telephone to the FMG traffic 

operations centre (+49 (0)89 975-21135). 

2.7. TOBT and TSAT in extreme situations 

If TOBT and TSAT differ by more than 90 minutes, the handling process has to be 

completed at TOBT, except the passenger boarding. The passenger boarding must be 

completed at TSAT-60. 



2.7.1. HTML masks 

The following working positions are equipped with HTML masks: 

• traffic operations centre (FMG) 

• General Aviation (FMG) 

• airline/handling agent 

The following mask is made available on a SITA PC free of charge to any airline and 

handling agent upon request to FMG. The introduction is conducted by FMG. 

Example: 

Scheduled 

off-block time 

Target 

Target 


Remaining Remaining 

time 

Runway 

delay 

Input fields 

TOBT 

TOBT 

Estimated 


Flight number / call sign 

registration 

Delete TOBT 

Calculated 

take-off time 

Target start-up 

approval time 

Reporting time TOBT 

Taxi time 

De-icing time 

Request for 

remote holding 



2.7.2. SEPL dialogue 

The following positions use the SEPL dialogue: 

• Supervisor TWR (DFS) 

• Clearance delivery (DFS) 

• Traffic operations centre (FMG) 

• Airline/handling agent 

A dialogue with limited functionalities can be requested from FMG by any handling agent 

and airline operator. It is made available on a user terminal rented from FMG. The 

training and introduction is conducted by FMG. 

Runway Runway N/S 

N/S 

Order Order number 

number 

aircraft-status 

aircraft-status 

aircraft status 

Callsign 

Callsign 

Deicing Deicing Marker 

Marker 

Target Target Startup 

Startup 

Approval Approval Time 

Time 

Detail Detail info info for 

for 

selected selected flight 

flight 

Estimate 

Estimate 

OffBock OffBock Time 

Time 

Minimum Minimum Departure 

Departure 

Intervall 

Intervall 

Parkingposition 

Parkingposition 

Calculated 

Calculated 

TakeOff TakeOff Time 

Time 

Target Target OffBlock OffBlock Time 

Time 

( ( * * = = autom. autom. autom . generiert) 

generiert) 



2.7.3. Internetdialog „WEASEL“ 

Depending on access authorization the Web-application for Sequence-Planning 

(Weasel) displays detailed flight and sequence information and allows different inputs, 

e.g. TOBT Update or request remote holding. 

Access to the “WEASEL” dialog can be requested via FMG (airport-cdm@munichairport.de. 



2.7.4. MAS page 

The MAS page (page 167) shows the latest information about the Airport CDM 

procedure to all persons involved. Important information (e.g. runway closures) is 

displayed in the bottom line. 

Flight number / 

call sign 

Scheduled 


Target start-up 

approval time 

Position 

De-icing remark 

Runway 

Date, time Page number 

Sequence (all times UTC) Tue 05.02.05 08:34 S167 

08L/26R 08R/26L 

Flight SOBT TSAT POS ICE Flight SOBT TSAT POS ICE 

* LH 5204 0800 0802 188E - DI 4610 0740 0740 192E 

* OK 557 0750 0808 170E - YP 2284 0745 0745 151 

o KL 3980 0725 0813 904N * LH 5734 0750 0750 191E 

BMW61 0730 0827 H10 o LG 9722 0755 0 755 183 

* LH 851 0800 0838 144 * YP 2236 0755 0755 152 

* LH 959 0800 0845 206E * FU 542 0800 0800 903N 

DIBER 0800 0851 H11 + DE 2246 0800 0800 112 

CSDNR 0800 0857 R10 o LH 5312 0800 0801 173E 

DIRMA 0800 0904 H11 o LH 5840 0805 0805 186E 

+ LH 1047 0805 0908 104 - OS 112 0735 0806 103B 

+ DE 2188 0750 0914 113B + LH 5726 0800 194E 

+ LH 833 0805 0926 102 + LH 5742 0805 174E 

o LH 897 0805 0932 162 LH 5466 0820 187E 

* LH 1510 0805 0939 205E 

o LH 2121 0805 0945 204E 

LH 5950 0805 0950 175E 

+ EAE 402 0815 182E 

+ SN 2642 0830 904S 

The screen is divided into North (08L/26R) and South (08R/26L) runway. For flights with 

remote holding, the TSAT field is displayed in reverse mode. 

2.8. De-icing 

The de-icing times are not taken into consideration when the TOBT is defined. They are, 

however, considered in the TSAT calculation based on the request for de-icing. 

Therefore, the request for de-icing should be made as early as possible. 

In the case of an apron de-icing, the aircraft must have been de-iced before the TSAT. 

2.9. Changes within the sequence 

It is possible to swap flights within the area of responsibility of an airline / handling agent 

after the TSAT has been calculated. If flights have a CTOT, it must be adhered to despite 

the changes within the sequence. 



2.10. Start-up and push-back 

The "pre-departure sequence" is determined on the basis of the TSAT and not of the 

start-up request (SUR). 

At TOBT, the aircraft must be ready for start-up or for apron de-icing. 

If there are any significant changes to the TSAT, the pilot will be informed accordingly by 

the airline / handling agent. In the case of general aviation flights, this task will be 

performed by clearance delivery (TWR). 

If the handling process is completed 5 minutes or less before the TOBT, the Start Up 

approval and En Route Clearance may be requested. Depending on the TSAT as well as 

on the actual operational traffic situation, Clearance Delivery will grant Start Up- and En 

Route clearance. 

As the Pre Departure Sequence and the TOBT are triggering additional processes 

at the airport, TOBT adaptations (also if shifting to earlier TOBT of more than 5 

minutes) have to be performed by the person responsible for the TOBT using the 

published TOBT reporting routines. 

The approval for push-back/taxi has to be requested not later than five minutes after the 

start-up approval has been issued. Otherwise, clearance delivery shall be informed about 

the delay. The TOBT will be deleted and has to be entered again. 

2.10.1. Datalink Clearance - DCL 

For datalink departure clearance (DCL), the published procedures and the time 

parameters published in AIP AD 2 EDDM 1-20 continue to apply. The TSAT is 

transmitted („Start Up approved TSAT “) using CLD (departure clearance 

uplink message – issuance of start-up approval and en-route clearance by clearance 

delivery). The push-back/taxi request shall be made at TSAT +/-5 minutes. 

Example: 

DCL with Start up approval and En Route 

clearance 

QU QXSXMXS 

.MUCDFYA 110454 

CLD 

AN D-AHFX/MA 767A 

- /MUCDFYA.DC1/CLD 0454 070311 EDDM PDC 

001 

HLF111 CLRD TO LPFR OFF 26L VIA AMPEG1S 

SQUAWK 3553 ADT MDI NEXT FREQ 121.775 AT 

IS D 

STARTUP APPROVED TSAT 05:00 

DCL only with En Route Clearance 

QU QXSXMXS 

.MUCDFYA 110818 

CLD 

AN D-ACPQ/MA 891A 

- /MUCDFYA.DC1/CLD 0818 070311 EDDM PDC 

001 

DLH06M CLRD TO LFBO OFF 08R VIA AMPEG1E 

SQUAWK 3545 ADT MDI NEXT FREQ 121.725 AT 

IS J 

STANDBY ON 121.725 FOR STARTUP TSAT 08:30 

2.10.2. ATC DPI – data exchange with the CFMU 

An A-DPI is transmitted to the CFMU actual off-block. The slot adjustment window is 

closed and the CFMU can no longer automatically change the CTOT. For regulated 

flights which haven’t reached CTOT-10 at AOBT, the A-DPI will be sent at CTOT-10 

minutes. 



2.11. Coordination with the CFMU 

Based on a fully automated data exchange with the CFMU, accurate early predictions of 

landing and departure times are established. Furthermore this data exchange will allow 

for more accurate and efficient allocation of CTOT, due to local target take of times. 

The following messages are used: 

• Flight Update Message - FUM 

• Early Departure Planning Information Message - E-DPI 

• Target Departure Planning Information Message - T-DPI 

• ATC Departure Planning Information Message - A-DPI 

The general CFMU procedures remain the same. Additionally, all target take-off times 

(TTOT) are automatically transmitted to the CFMU during the turnround process. In the 

case of longer delays which are caused by the airline operators, the familiar CTOT 

allocation mechanisms apply. They are confirmed or fine-tuned with DPI messages. As a 

rule, the CFMU takes the TTOT into account when it calculates the CTOT and tries to 

adjust them accordingly. 

If an adjustment/extension is not sufficient, DFS (clearance delivery) offers to coordinate 

a new CTOT in consultation with the pilot. 

2.12. Remote holding 

Remote holding can be requested with the SEPL dialog if the TOBT is at least 30 

minutes before the CTOT. 

2.13. Contact address and information 

It is necessary that all airlines/handling agents provide a current contact address (e-mail) 

for messages from the airport CDM procedure to FMG: 

- muc.schedule@munich-airport.de 

- telephone: +49 (0)89 972-21181 

This does not apply to general aviation flights without handling agents, because their 

messages from the airport CDM procedure are transmitted directly to the counter of the 

general aviation terminal (GAT). 

Customers will be informed by e-mail about the following events: 

• No Airport Slot available 

• EOBT (ATC flight plan) and the airport flight plan (SOBT) do not match 

• TOBT cannot be generated automatically, because TOBT + RMT > CTOT 

• EOBT and TOBT differ more than 15 minutes 

• Deletion of the TOBT 

• No ATC flight plan available 

• EIBT is later than EOBT (ATC flight plan) (before final approach) 

• Cancellation of the flight plan in the airport system 

• Aircraft type in the ATC flight plan and the airport system does not match 

• Aircraft registrations in the ATC flight plan and the airport system does not match 



2.13.1. Airport CDM information messages 

• No Airport Slot available (SOBT) 

Example: 

No coordinated Airport Slot for your ATC flightplan, 

aircraft identification ……., available. Please clarify through usual channels. 

NOTE: The Airport CDM process will be suspended until reception of your 

rectification. 

FPL aircraft identification ……. EOBT …. 

• EOBT (ATC flight plan) and the airport flight plan (SOBT) do not match 

Example: 

Your ATC flightplan, aircraft identification ……. / flight number ……. doesn't 

match the coordinated airport slot. Please clarify (modify, cancel, etc.) 

through usual channels. 

Scheduled flight number ……. SOBT …. DATE …….. 


• TOBT cannot be generated automatically, because TOBT + RMT > CTOT 

Example: 

The TOBT for your outbound flight, aircraft identification ……. / flight 

number ……. couldn´t be automatically generated, because it doesn´t match 

with the associated CTOT. Please clarify (modify, cancel, etc.) through 

usual channels and initiate a TOBT. 




FPL Aircraft identification ……. EOBT …. CTOT …. 

• EOBT and TOBT differ more than 15 minutes 

Example: 


number ……. deviates from the EOBT of the ATC flightplan at least 15min. 

You are requested to update your ATC flightplan (DLA, CNL, REG-change, 

etc.) through usual channels. 


FPL aircraft identification ….. EOBT ….. 

• Deletion of the TOBT 

Example: 


number ……. has been deleted. You are requested to set a new TOBT or 

send a cancellation message for your flightplan (CNL) through usual 

channels. 







• No ATC flight plan available 

Example: 

Your ATC flightplan for your outbound flight, flight number ……. is not 

available. Please clarify through usual channels (IFPS) and file a new ATC 

flightplan. 





• EIBT is later than EOBT (ATC flight plan) (before final approach) 

Example: 

Your inbound flight, aircraft identification ……. / flight number …...., doesn't 

match the associated outbound flight. You are requested to update your 

outbound ATC flightplan (DLA, CNL, REG-change, etc.) through usual 

channels. 




FPL aircraft identification (Inbound) …… EIBT …. 


FPL aircraft identification (Outbound) …… EOBT …. 

• Cancellation of the flight plan in the airport system 

Example: 

The dataset for your outbound flight, aircraft identification ……. / flight 

number …… has been deleted within the airport system. 



Scheduled flight number ……. SOBT ….DATE ……. 


• Aircraft type in the ATC flight plan and the airport system does not match 

Example: 

A data discrepancy has been detected for your outbound flight, aircraft 

identification ……. / flight number ……. with respect to the following: FPL- 

Aircraft Type and Aircraft type information within the Airport System differ. 

You are requested to update your flightplan information through usual 

channels. 

Scheduled flight number ……. SOBT …. DATE ……. 

FPL aircraft identification ……. EOBT ….. 



• Aircraft registrations in the ATC flight plan and the airport system does not match 

Example: 

A data discrepancy has been detected for your outbound flight, aircraft 

identification ……. / flight number ……. with respect to the following: FPL- 

Aircraft registration and Aircraft registration information within the Airport 

System differ. You are requested to update your flightplan information 

through usual channels. 

Scheduled flight number …… SOBT ….. DATE ……. 


3. Aeronautical Information Publication – AIP – 

The Airport CDM procedure at Munich Airport is published in AIP Germany, Volume II, 

AD2-EDDM, section AD 2.20 “Local Traffic Regulations”, page 1-14 and following. 

3.1. Persons responsible for the process/contact persons 

For questions concerning the procedure: 

Flughafen München GmbH 

Peter Kanzler 

Tel. +49 (0)89 975-21160 

airport-cdm@munich-airport.de 

For IT questions: 

Flughafen München GmbH 

Achim Tuffentsammer 

Tel. +49 (0)89 975-32410 

achim.tuffentsammer@munich-airport.de

airport cdm münchen - Airport Collaborative Decision Making

Create successful ePaper yourself

Delete template?

Save as template?