Supporting

European
Aviation

FLIGHT
DISPATCHER
DAYS
17-18 Jan 2024
Donal Lalor – EUROCONTROL NMD/ACD/PCI
 FF-ICE Introduction – What?

FF-ICE
Flight & Flow Information for
ICAO FF-ICE
CONCEPT a Collaborative Environment SERVICES

INCREASED STANDARD REPLACES FPL GUFI

INFORMATION FORMAT 2012
SHARING

Flight Dispatcher Days 2

 FF-ICE Introduction – What?

FPL 2012 FF-ICE Flight Plan (eFPL)

Flight Dispatcher Days 3

 FF-ICE Introduction – Why?

UNDERSTAND COLLABORATION SCALABLE & MACHINE TRAJECTORY

REQUIREMENTS FLEXIBLE READABLE BASED OPS
ENABLER

Flight Dispatcher Days 4

 FF-ICE Introduction – When?

OPTIONAL-ICAO FPL 2012

SUNSET 2034

Flight Dispatcher Days 5

 FF-ICE Introduction – When?

31st December 2025

FF-ICE Mandate
CIR (EU) 2021/116 All IFR GAT Airspace Users
Common Project 1 (CP1) EU, Norway & Switzerland

Flight Dispatcher Days 6

 FF-ICE Introduction – Further Information

NM IFPS USERS MANUAL ffice@eurocontrol.int

Flight Dispatcher Days 7

 eFPL Deployment@Lufthansa
Ops Changes and Challenges

NM Flight Dispatcher Days, 18th Jan 2024

Paul Schiemangk, Lufthansa Group

lufthansagroup.com
How does an FF ICE flight plan (eFPL) look like?

vs.

NM Flight Dispatcher Days

18/01/24
Page 9
Same same, but different - easy

NM Flight Dispatcher Days

18/01/24
Page 10
Same same, but very different

NM Flight Dispatcher Days

18/01/24
Page 11
Live Demo

eFPL productive at Lufthansa for few city pairs since Dec 2022

NM Flight Dispatcher Days

18/01/24
Page 12
We file the full truth about the vertical profile

Are we happy now?

☺ We might get an ACK instead of a REJ

 We might get a REJ instead of an ACK

☺ We might be considered not to intersect with a regulation compared to ICAO2012 FPL

 We might be considered to intersect with a regulation compared to ICAO2012 FPL

NM Flight Dispatcher Days

18/01/24
Page 13
We receive the full truth about the vertical profile calculated by Eurocontrol

How do we use that information? – Status Lido/Lufthansa:

• Update of ATS FPL in crew briefing with translated ICAO2012 FPL
• no recalculation/display/further consideration of “agreed trajectory” so far

NM Flight Dispatcher Days

18/01/24
Page 14
And your daily quick steps during flight planning?

• Change FL in Item 15
• Adapt EOBT
• Check IFPUV with copy/paste in other tools
• Change equipment
• Change alternate
• Edit free text in Item 18
…

NM Flight Dispatcher Days

18/01/24
Page 15
Major systematic challenges

• eFPL exchange with multiple stakeholders (going outside Europe)

• Data consistency (Eurocontrol, ANSPs, flight planning tool…)

And finally: something does not work…

…and you might want to file/change the FPL through other tools…
And now?

NM Flight Dispatcher Days

18/01/24
Page 16
Paul Schiemangk
paul.schiemangk@dlh.de

lufthansagroup.com
 eFPL Future in Lido Flight
NM Flight Dispatcher Days, 18th Jan 2024 Public
Technical aspects

ICAO flight plan FF-ICE flight plan

ICAO FPL: text format eFPL: FIXM XML format

Transmission as telex messages (AFTN or SITA) Exchange via web services (e.g. NM B2B services)

Flight plan messages: FPL, CHG, DLA, CNL Request: FiledFlightPlan, FlightPlanUpdate,
FlightPlanCancellation

Reply messages: ACK, REJ, MAN Reply: FiledFlightPlan, FlightPlanUpdate,

FlightPlanCancellation

eFPL Future in Lido Flight

January 18th, 2024 - Lido Flight Public
Page 19
Display the reply

Request Reply

eFPL Future in Lido Flight

January 18th, 2024 - Lido Flight Public
Page 20
Display the reply

Table view

eFPL Future in Lido Flight

January 18th, 2024 - Lido Flight Public
Page 21
Display the reply

Graphic

eFPL Future in Lido Flight

January 18th, 2024 - Lido Flight Public
Page 22
Display the reply

Graphic

eFPL Future in Lido Flight

January 18th, 2024 - Lido Flight Public
Page 23
Display the reply

Map, Chart

eFPL Future in Lido Flight

January 18th, 2024 - Lido Flight Public
Page 24
Analyze the reply

Can the data in the request and the data in the reply differ?
Yes: NM calculated trajectory considering additional constraints (for instance “profile tuning restrictions” (PTR))

Which data elements can differ?

4D trajectory (request: filed trajectory, reply: agreed trajectory)

Which elements of the trajectory can change?

SID, STAR, cruise levels -> trip distance, trip time

How to identify significant differences between request and reply?

Significant differences might require reaction

eFPL Future in Lido Flight

January 18th, 2024 - Lido Flight Public
Page 25
Analyze the reply

Significant differences?
Request Reply

eFPL Future in Lido Flight

January 18th, 2024 - Lido Flight Public
Page 26
Analyze the reply

Significant differences?
Request Reply

eFPL Future in Lido Flight

January 18th, 2024 - Lido Flight Public
Page 27
Analyze the reply

Additional points – significant difference?

Reply

eFPL Future in Lido Flight

January 18th, 2024 - Lido Flight Public
Page 28
Use the reply

Constraints considered in the NM trajectory

Reply

eFPL Future in Lido Flight

January 18th, 2024 - Lido Flight Public
Page 29
Far in the future: FF-ICE Planning Service

Approach
• First flight calculation starts 36-24 hours before EOBT
• First flight calculation considers as less as possible constraints
• Next flight calculations consider constraints provided in the replies
• Additional flight calculations triggered by flight re-evaluations by NM

Goals
• NM gets early an information about the traffic demand
• Activation of necessary constraints only (-> “Dynamic RAD”)
• Flights can become less restricted
• The filed trajectory can become the agreed trajectory

eFPL Future in Lido Flight

January 18th, 2024 - Lido Flight Public
Page 30
Thomas Eschenhagen

thomas.eschenhagen@lhsystems.com
Backup

NM Flight Dispatcher Days

18/01/24
Page 32
Backup

NM Flight Dispatcher Days

18/01/24
Page 33
Backup

NM Flight Dispatcher Days

18/01/24
Page 34
Backup

NM Flight Dispatcher Days

18/01/24
Page 35