1. FLIGHT PLAN WORKSHOP
Jakarta, 21 November 2011
by
Peter ATKINS
Novaro MARTODIHARDJO

2. Flight Plan Workshop Agenda
Flight Plan Workshop Agenda
No. Time Subjects
Flight Plan Review
1 09.15 – 10.15 — Submission FPL
— RPL operation
ATS Messages Review
2 10.30 – 11.30 — Current ATS Messages
— Flight data exchages
3 11.30 – 12.30 Break
New ICAO Flight Plan Format
4 12.45 – 13.45 — Flight Plan
— ATS Messages
Implementation readiness
— Related Regulation
5 14.00 – 15.15
— Aeronautical Information promulgation
6 15.15 – End Draft Conclution
2

3. Workshop will cover :
Overview on current daily flight plan (FPL) and RPL
operation within U. Pandang and Jakarta ATSU and on
each aerodrome;
Overview of current status of flight data and associated
messages exchanges between FIRs, espacially between
U.Pandang and Jakarta FIR and their associated ATSU on
their FIRs;
National policy and planning on Amendment 1 of the 15th
Edition of PANS-ATM Doc.4444 and associated ATS
messages implementation within U.Pandang and Jakarta
FIR;
Implementation readiness which will cover the readiness
of any related safey regulation documents and flight
plan data presentation for Controller.
3

4. OBJECTIVES:
To review current status of flightplan
management (including RPL) and
associated ATS messages within
U.Pandang and Jakarta FIR to
anticipate the implementation on
Amendment 1 of 15th Edition of
PANS-ATM Doc.4444 which will be
implemented by 15 November 2012.
4

5. Flight Plan Review
FPL Submission
AC 170 -02 require that flight plan should be submitted
prior departure
In the event of a delay of 30 minutes in excess of the
estimated off-block time for a controlled flight or a delay
of one hour for an uncontrolled flight for which a flight
plan has been submitted, the flight plan should be
amended or a new flight plan submitted and the old flight
plan cancelled, whichever is applicable.
When will be the (proper) latest time a flight plan may
be submitted prior off-block time?
5

6. Repetitive Flight Plan
RPLs shall not be used for flights other than IFR flights
operated regularly on the same day(s) of consecutive
weeks and on at least ten occasions or every day over a
period of at least ten consecutive days. The elements of
each flight plan shall have a high degree of stability.
(AC 170 – 02)
RPLs shall cover the entire flight from the departure
aerodrome to the destination aerodrome. RPL
procedures shall be applied only when all ATS authorities
concerned with the flights have agreed to accept RPLs.
(AC 170 – 02)
Procedures for use of RPLs may be established for
flights operating within a single FIR or a single State, OR
may also be established for flights across international
boundaries subject to the provision that affected States
currently utilize or will concurrently use RPLs.
(AC 170 – 02)
Does agreement available for using of RPL within
FIR/s ?
6

7. ATS Messages Review
There three categories of ATS Messages :
1. Emergency messages, distress (SS), urgen (DD), and
other (FF)
2. Movement and controll messages, filed flight plan
messages and associated update messages (FF),
coordination messages (FF), supplementary
messages (FF), control messages (FF)
3. Flight information messages such as traffic information
(FF), meteorological information (FF or GG), essential
aerodrome information (GG)
Example of message : (DEP-ABC112/4545-WSSS-WADD)
7

8. ATS Messages Review
The message above are authorized for transmission via
the aeronautical fixed service (including the aeronautical
fixed telecommunication network (AFTN), direct-speech
circuits or digital data interchange between air traffic
services units, and direct teletypewriter and computer-
computer circuits), or via the aeronautical mobile service,
as applicable. They are classified in categories relating to
their use by the air traffic services and providing an
approximate indication of their importance.
8

9. Current AFTN Network
WSSS
WAAA
WIII
WADD
YBBB
9

10. Flight plan data exchanges
The method of message exchange shall also be
dependent upon the availability of adequate
communications channels, the function to be performed,
the types of data to be exchanged and the processing
facilities at the centres concerned.
Basic flight plan data necessary for flow control
procedures shall be furnished at least 60 minutes in
advance of the flight. Basic flight plan data shall be
provided by either a filed flight plan or a repetitive flight
plan submitted by mail in the form of a repetitive flight
plan listing form or other media suitable for electronic
data processing systems.
10

11. Flight plan data exchanges
FIR
FPL
FPL
FPL
ORIGIN ATC Unit ATC Unit DEST
RPL
RPL
RPL
AFTN
Mail / Fax
Voice if needed
11

12. Flight plan data exchanges
In areas where automated systems are utilized for the
exchange of flight plan data and where these systems
provide data for several ACCs, approach control units
and/or aerodrome control towers, the appropriate
messages shall not be addressed to each individual
ATS unit, but only to these automated systems.
(AC 170-02)
12

13. Flight plan data exchanges
FIR
CFL / EST CFL
FPL
ATC Unit ATC Unit DEST
ORIGIN
RPL
FPL
AFTN
RPL Bulk load
Voice if needed
13

14. New ICAO Flight Plan Format
ICAO State Letter AN 13/2.1-08/50 Dated 25 June 2008
Subject: Approval of Amendment 1 to the PANS-ATM
Action required: a) Implementation of the amendment on
15 November 2012; b) Publication of any differences as of
15 November 2012
Air Navigation Commission, acting under delegated
authority, at the first and second meetings of its 177th
Session, on 22 and 24 January 2008, approved
Amendment 1 to the Procedures for Air Navigation
Services — Air Traffic Management, Fifteenth Edition
(PANS-ATM, Doc 4444) for applicability on 15 November
2012. The amendment was approved on 27 May 2008 by
the President of the Council on behalf of the Council
14

15. New ICAO Flight Plan Format
Amendment 1 stems from the work of the Flight Plan
Study Group (FPLSG). The nature and scope of the
amendment is to update the ICAO model flight plan form in
order to meet the needs of aircraft with advanced
capabilities and the evolving requirements of automated
air traffic management (ATM) systems, while taking into
account compatibility with existing systems, human
factors, training, cost and transition aspects.
Transition
The ICAO Asia Pacific Region has adopted a declared
transition period and a phased implementation from
1 January 2012 until 15 November 2012.
15

16. New ICAO Flight Plan Format (cont)
The phased implementation comprises of :
Phase 1 :1 January to 31 March 2012 ANSPs software
delivery and internal testing
Phase 2: 1 April to 30 June 2012, and ANSPs external
testing and implementation
Phase 3 : 1 July to 15 November 2012 Airspace users
testing and implementation
Are you ready ?
16

17. KEPUTUSAN DIREKTUR JENDERAL
PERHUBUNGAN UDARA
NOMOR: SKEP/279/V /2011
TENTANG
PEMBENTUKAN KELOMPOK KERJA
TIM IMPLEMENTASI
FLIGHT PLAN FORMAT BARU INDONESIA
To establish Indonesia working group team on flight plan
implementation compose of Steering Committee,
Executive and Secretariate which consist of Members as
mentioned on Attachment.
17

18. Task List
1. to coordinate among the team to correspondance
with ICAO State Letters;
2. to review the capacity and limitation toward flight plan
processing which are exists in Indonesia;
3. to surey toward flight plan submision on every unit
which send flight plan;
4. to review toward the use of Repetitive Flight Plan and
its optimalisation for operational purpose in
developing flight safety;
5. to prepare New ICAO Flight Plan Format
implementation;
6. to conduct safety assesment and its associated effect
to the operation of AIDC, ADS-C/CPDLC;
7. to publish aeronautical information publication such
as NOTAM, AIC and AIP as necessary;
18

19. Sharing ideas
What will be the national policy on the adoption of
Amendment 1 to the Procedures for Air Navigation
Services — Air Traffic Management, Fifteenth Edition
(PANS-ATM, Doc 4444)
How are U.Pandang and Jakarta FIR have anticipated
on the implementation of Amendment 1 to the
Procedures for Air Navigation Services — Air Traffic
Management, Fifteenth Edition (PANS-ATM, Doc 4444)
When and how the related safety documents (if any)
be modified / updated.
When and how the related aeronautical information be
managed.
19

20. Conclutions:
20