this document is a controlled document and … dispatch rev. 14.pdfflight dispatch standard...

THIS DOCUMENT IS A CONTROLLED DOCUMENT AND CONTAINS PROPRIETARY AND/OR CONFIDENTIAL INFORMATION. THIS CONTROLLED COPY IS MAINTAINED ELECTRONICALLY ON THE INTRANET.

A COPY/PRINT OF THIS DOCUMENT IS AN UNCONTROLLED DOCUMENT.

STANDARD OPERATIONAL PROCEDURES

FLIGHT DISPATCH

Approval Form

OM PART B

Intentionally Blank




FLIGHT DISPATCH

RECORD OF TEMPORARY REVISIONS

OM PART B

Page 4A

16-03-2017 TR 02


TR Nº ISSUE DATE

EFFECTIVE DATE

DATE FILED

FILED BY LOCATION/REMARKS/

STATUS

01 07/03/2017 07/03/2017 ACTIVE

02 16/03/2017 16/03/2017 ACTIVE



STANDARD OPERATIONAL PROCEDURES FLIGHT DISPATCH


Page 4B OM

PART B

TR 02 16-03-2017

Temporary Revision 02

List of OM Part B – Standard Operational Procedures Flight Dispatch pages changed by this

TR:

Chapter Page Number

0 4A

0 4B

3 15

Highlights

3 Out-Station Dispatch Revised the OM A reference, if no OFPL is received by PIC, for

accuracy.




FLIGHT DISPATCH

INDEX

OM PART B

Page 7

17-06-2016 Rev. 14

INDEX

APPROVAL FORM ....................................................................................................... 1

DISTRIBUTION LIST .................................................................................................... 3

RECORD OF NORMAL REVISIONS ............................................................................ 4

REVISION HIGHLIGHTS: ............................................................................................. 4

LIST OF EFFECTIVE PAGES ...................................................................................... 5

INDEX ........................................................................................................................... 7

1 – FLIGHT DISPATCH ................................................................................................ 9

1.1 – FLIGHT OPERATIONS OFFICERS ........................................................................................ 9 1.2 – FOO’S HEALTH REQUIREMENTS ........................................................................................ 9 1.3 – DUTIES / RESPONSIBILITIES ............................................................................................... 9 1.4 – CONTINUED OPERATIONAL CONTROL .............................................................................. 9 1.5 – QUALIFICATION RECORDS .................................................................................................. 9 1.6 – INITIAL TRAINING ................................................................................................................ 10 1.7 – RECURRENT TRAINING ...................................................................................................... 10 1.8 – COMPETENCY EVALUATION ............................................................................................. 10 1.9 – ANNUAL IN-FLIGHT FAMILIARIZATION PROGRAMME .................................................... 10

2 – FLIGHT DISPATCH PREPARATION AND BRIEFING ........................................ 11

2.1 – FLIGHT NOTIFICATION (ACMI EXITING LIS) ..................................................................... 12 2.2 – FLIGHT DISPATCH FOLDER ............................................................................................... 12 2.3 – OPERATIONAL FLIGHT PLAN ............................................................................................. 12 2.4 – ATS FLIGHT PLAN SUBMISSION ........................................................................................ 12 2.5 – NAVTECH AIRCRAFT LIBRARY .......................................................................................... 12 2.6 – AIRPORT SLOTS .................................................................................................................. 12 2.7 – WEATHER BRIEFING ........................................................................................................... 13 2.8 – BRIEFING .............................................................................................................................. 13 2.9 – TAF UPDATE ........................................................................................................................ 14

3 – OUT-STATION DISPATCH ................................................................................... 15

4 – FLIGHT NOTIFICATION MESSAGE .................................................................... 17

4.1 – LOGISTICS............................................................................................................................ 17

5 – PRE-FLIGHT DISPATCH CHECKLIST / FLIGHT DISPATCH FOLDER ............. 19

6 – OPERATIONAL FLIGHT PLANS ....................................................................... 221

6.1 – STANDARD KEYWORDS ................................................................................................... 221 6.2 – HOLD ITEM LIST (HIL) VERIFICATION ............................................................................... 24 6.3 – EXPECTED PAYLOAD ......................................................................................................... 24 6.4 – OFPL ANALYSIS ................................................................................................................... 25 6.5 – MINIMUM FUEL ON BOARD ................................................................................................ 25 6.6 – ALTERNATE AERODROMES SELECTION ......................................................................... 25 6.7 – ETOPS FLIGHTS .................................................................................................................. 26 6.8 – REDUCED CONTINGENCY FUEL PROCEDURE / DECISION POINT PROCEDURE

(RECLEARANCE) FLIGHTS .................................................................................................. 26 6.9 – GMORA ANALYSIS .............................................................................................................. 26 6.10 – OPERATIONAL FLIGHT PLAN DECODER ........................................................................ 27

7 – FILLING AND MANAGEMENT OF ATC FLIGHT PLANS ................................... 29




INDEX

Page 8 | OM

PART B

Rev. 14 17-06-2016

7.1 – IFPS READDRESSING FUNCTION ..................................................................................... 29 7.2 – ROUTE MODIFICATIONS ................................................................................................. 3030 7.3 – FLIGHT PLAN ROUTE VALIDATION ................................................................................ 3030 7.4 – ROUTE AVAILABILITY DOCUMENT ................................................................................ 3030 7.5 – TYPE OF FLIGHT / EMISSION TRADING SYSTEM ........................................................ 3030

8 – FLIGHT WATCH ................................................................................................... 31

8.1 – AIRNAV FLIGHT TRACKER.................................................................................................. 31 8.2 – JUPITER (ETOPS MONITORING) ........................................................................................ 31 8.3 – AIMS ...................................................................................................................................... 31 8.4 – ARO / AIS............................................................................................................................... 40 8.5 – COMMUNICATION DISPATCH / COCKPIT ......................................................................... 40 8.6 – CFMU SECURE WEBSITE (NOP) ........................................................................................ 40 8.7 – METEOROLOGY ................................................................................................................... 41 8.8 – RUNWAY DEFICIENCIES/DOWNGRADE ........................................................................... 41 8.9 – DIVERTION PROCEDURES ................................................................................................. 41 8.10 – SIGNIFICANT DELAYS ....................................................................................................... 41 8.11 – SACA (SAFETY ASSESSMENT FOR COMMUNITY AIRCRAFT) ..................................... 41 8.12 – PARKING AUTHORIZED .................................................................................................... 42 8.12 – AIRCRAFT UNAVAILABLE FOR COMMERCIAL DEPARTMENT ..................................... 42

9 – EMERGENCY PROCEDURES ............................................................................. 43

9.1 – NOTIFICATION ...................................................................................................................... 43 9.2 – FLIGHT DISPATCH EMERGENCY CONTACTS AND SURVIVAL EQUIPMENT LIST ....... 44 9.3 – FLIGHT DISPATCH EMERGENCY AND SURVIVAL EQUIPMENT CONTACTS ................ 45

10 – ATFM SLOT MANAGEMENT ............................................................................ 47

11 – DAILY TASKS ................................................................................................ 4949

12 – ROSTERS MANAGEMENT ................................................................................ 51

12.1 – EAPIS (ELECTRONIC ADVANCE PASSENGER INFORMATION SYSTEM) ................... 51 12.2 – FLEET MANAGEMENT ....................................................................................................... 56 12.3 – CREW MANAGEMENT – INSERT A CREW ...................................................................... 56

13 – OVERFLIGHT PERMITS ................................................................................ 5959

14 – DOCUMENT STORAGE PROCEDURES .......................................................... 61

15 – ACMI PROCEDURES ......................................................................................... 63

15.1 – CATERING/CARGO EQUIPMENT COMPATIBILITY ......................................................... 65 15.2 – LONG TERM OPERATIONS ............................................................................................... 65

16 – ROUTE STUDIES ............................................................................................... 67

17 – HOSTED GRAFLITE APLICATIONS ................................................................. 75




FLIGHT DISPATCH

FLIGHT DISPATCH

1

OM PART B

Page 9

27-10-2015 Rev. 13

1 – FLIGHT DISPATCH

1.1 – FLIGHT OPERATIONS OFFICERS

The Flight Dispatch department is manned 24 hours a day by Portuguese Civil Aviation Authority certified FOOs, as per OM Part A 5.1.1.2 “Flight Operations Officer Licensing”. They report to the Flight Dispatch Manager, or, in case of absence of duty, to the assigned deputy who accumulates Monitor/Instructor duties, as per OM Part A 1.3.5.1.3. Current facilities are located near Lisbon Airport and are equipped with three workstations for flight planning / flight watch purposes, along with a worldwide coverage Navtech library. Security and limited access is guaranteed by a security code door lock. To every FOO shall be given access to these facilities. Coordination/communication between FOOs and the Flight Dispatch Manager shall be done through daily shift reports. In addition, a monthly meeting is done in order to clarify any abnormal situations that may have occurred. Since FOOs are working on shifts, mandatory attendance is not required, though strongly encouraged. Minutes are kept at Flight Dispatch facilities and are distributed electronically to all FOOs. Flight Dispatch Officers will have access to ATS services and respective information through official channels, such as local ARO, official government AIP websites, EuroControl's database, Navtech’s Emergency chapters, in order to have access to data relevant to the safe conduct of each flight, on a day-to-day basis and/or emergency situation.

1.2 – FOO’S HEALTH REQUIREMENTS

All aspects regarding health requirements for FOOs are stated in OM Part A 5.5.1.2.

1.3 – DUTIES / RESPONSIBILITIES

All duties and responsibilities are stated in OM Part A 1.3.5.1.3.

1.4 – CONTINUED OPERATIONAL CONTROL

The Flight Dispatch Manager, or his deputies, has the authority to alter work schedules, taking into consideration Portuguese Law, in order to ensure that the above responsibilities and operational control are constantly maintained by qualified personnel. The deputies have the same authority, duties and responsibilities as the Flight Dispatch Manager whenever they assume his/her functions. The Flight Dispatch Manager, or his/her deputies (REF. OM PART A 1.3.5.1.3.), is not allocated duties on the FOO Roster but will be used to cover unexpected workload. The Flight Dispatch Manager, or his/her deputies are always reachable through appropriate means of communication, and will reinforce the Roster when needed.

1.5 – QUALIFICATION RECORDS

All records that document the fulfillment of requirements associated with operational control, FOOs’ initial and recurrent qualification, as well as a copy of his/her license, are kept in individual folders, and are verified through JUPITER´s training module, as per NO-GER-003. FOOs will be assigned to refreshment courses as needed in order to comply with OM Part A 5.5.1 and Part D 2.3.1.2. FOOs records maintenance, protection and disposal are described in NO-GER-007



1 STANDARD OPERATIONAL PROCEDURES FLIGHT DISPATCH

FLIGHT DISPATCH

Page 10 OM

PART B

Rev. 11 13-04-2015

1.6 – INITIAL TRAINING

All aspects regarding initial training can be found in OM Part D 2.3.1.2.1.

1.7 – RECURRENT TRAINING

All aspects regarding recurrent training can be found in OM Part D 2.3.1.2.3.

1.8 – COMPETENCY EVALUATION

All aspects regarding competency evaluation can be found in OM Part D 2.3.1.3.

1.9 – ANNUAL IN-FLIGHT FAMILIARIZATION PROGRAMME

All aspects regarding in-flight familiarization program can be found in OM Part D 2.3.1.4.




FLIGHT DISPATCH

FLIGHT DISPATCH PREPARATION AND BRIEFING

2

OM PART B

Page 11

17-06-2016 Rev. 14

2 – FLIGHT DISPATCH PREPARATION AND BRIEFING

For flight planning purposes, euroAtlantic has contracted SITA/Graflite, a flight plan provider, which is responsible for providing operational flight plans in accordance with the relevant EASA Air OPS provisions applicable to operations within the scope of commercial air transport and not contravening any conditions contained in the Air Operator's Certificate (AOC), respective NOTAM and weather briefing. In order to better comply with flight planning tasks that must be completed within reasonable time, they provided euroAtlantic with SITA/Graflite’s Keyword Manual and have given access to their HelpDesk department. If any anomaly in the normal process of the aforementioned contracted tasks is detected, such as unexpected delays, loss of server communications, missing or inaccurate data, the FOO on duty will advise SITA Helpdesk through the following contacts for immediate resolution: SITA/Helpdesk : Phone +44 208 756 8333 SITA:QIFFPXS Email: [email protected] This notification will be made available to the Flight Dispatch Manager, who will contact euroAtlantic’s SITA Regional Supervisor, open a case file, where the root cause of such anomaly will be identified and corrective actions will be taken. Depending on how important the anomaly may be, the Flight Dispatch Manager will notify the Compliance Manager, the Flight Operations Manager and the IT Manager of such occurrence. On a more proactive approach, a regular monitoring will be performed to services providers, namely Graflite (Gf), specifically to the CFP produced by their system. This procedure must be complied accordingly with NO-DCM-001 and NO-DCM-007. These checklists will be forwarded to the Compliance Monitoring Department for internal analysis. FLIGHT DISPATCH TASKS All flight dispatch tasks must be initiated with no less than 08 hours before ETD. Final flight plan must be completed no more than 06 hours before ETD. An email with METAR, TAF and SIGMET must be sent to aircraft and crew no more than 01 hour before ETD.



mailto:[email protected]



Page 12 OM

PART B

Rev. 14 17-06-2016

2.1 – FLIGHT NOTIFICATION (ACMI EXITING LIS/OPO/FAO/BYJ)

Estimated execution time: 00h10m Flight notification, among external handling providers, must include:

Aircraft type, registry and configuration;

Time table, in UTC times, including the departure and arrival to base;

Crew composition, if already available from AIMS; Minimum off block fuel, according with OM Part A 8.2.1. and estimated elapsed time;

Any logistic action required, such as GPU, aircraft towing, cleaning services, with previous coordination with SOT.

2.2 – FLIGHT DISPATCH FOLDER

Estimated execution time: 00h10m The Flight Dispatch Folder will be retrieved from JUPITER, according with the number of legs that will be performed per crew. This information is obtained inserted on AIMS by Rosters Department.

2.3 – OPERATIONAL FLIGHT PLAN

Estimated execution time: 01h15m The operational flight plan will be produced through the current flight planning service provider, according with the aircraft and time table displayed on AIMS. Final flight plan must be completed no more than 6 hours before ETD.

2.4 – ATS FLIGHT PLAN SUBMISSION

Estimated execution time: 00h25m ATS route derived from operational flight plan shall be submitted to respective AIS centers. Resulting acknowledges shall be confronted with the operational flight plan. Any change to the initial routing implies the production of a new operational flight plan.

2.5 – NAVTECH AIRCRAFT LIBRARY

Estimated execution time: 00h30m It is the responsibility of the FOO to verify that Navtech aircraft’s library is updated liaising with Flight Support. In addition the FOO shall verify that all the airports included in the flight plan are included in the Navigation Database’s (NavDB) list of airports made available by the operations engineering. In the event that any of the airports included in the flight plan are not in the NavDB, the flight crew shall be made aware. Flight crews shall, in such cases, use the airport charts available on the iPads.

2.6 – AIRPORT SLOTS

Estimated execution time: 00h30m The FOO, using available means, will contact the Portuguese Slot Coordination Centre (218445219 - DCNS Coordenação de Slots <[email protected]>) or Lisbon Airport Supervisor (968030268 - ALSSUP <[email protected]>) or Oporto Airport Supervisor (964250179 – OPOSUP [email protected]) in order to confirm if there is an approved airport slot. If this is not the case, corrective actions must be taken, by contacting the lessee staff or applying for the airport slot directly. After the above tasks are completed, the FOO on duty will have one hour available until briefing time (ETD minus 01h30) in order to comply with any eventual last minute changes.




FLIGHT DISPATCH


2

OM PART B

Page 12

07-03-2017 TR 01

2.1 – FLIGHT NOTIFICATION (ACMI EXITING LIS/OPO/FAO/BYJ)

Estimated execution time: 00h10m

Flight notification, among external handling providers, must include:



Crew composition, if already available from AIMS; Minimum off block fuel, according with OM Part A 8.2.1. and estimated elapsed time;

Any logistic action required, such as GPU, aircraft towing, cleaning services, with previous coordination with SOT.

2.2 – FLIGHT DISPATCH FOLDER


The Flight Dispatch Folder will be retrieved from JUPITER, according with the number of legs that will be performed per crew. This information is obtained inserted on AIMS by Rosters Department.

2.3 – OPERATIONAL FLIGHT PLAN


The operational flight plan will be produced through the current flight planning service provider, according with the aircraft and time table displayed on AIMS. Final flight plan must be completed no more than 6 hours before ETD. Whenever block time is longer than schedule an email shall be sent to rosters and commercial department in order to adjust it.

2.4 – ATS FLIGHT PLAN SUBMISSION


ATS route derived from operational flight plan shall be submitted to respective AIS centers. Resulting acknowledges shall be confronted with the operational flight plan. Any change to the initial routing implies the production of a new operational flight plan.

2.5 – NAVTECH AIRCRAFT LIBRARY


It is the responsibility of the FOO to verify that Navtech aircraft’s library is updated liaising with Flight Support. In addition the FOO shall verify that all the airports included in the flight plan are included in the Navigation Database’s (NavDB) list of airports made available by the operations engineering. In the event that any of the airports included in the flight plan are not in the NavDB, the flight crew shall be made aware. Flight crews shall, in such cases, use the airport charts available on the iPads.

2.6 – AIRPORT SLOTS


The FOO, using available means, will contact the Portuguese Slot Coordination Centre (218445219 - DCNS Coordenação de Slots <[email protected]>) or Lisbon Airport Supervisor (968030268 - ALSSUP <[email protected]>) or Oporto Airport Supervisor (964250179 – OPOSUP [email protected]) in order to confirm if there is an approved airport slot. If this is not the case, corrective actions must be taken, by contacting the lessee staff or applying for the airport slot directly. After the above tasks are completed, the FOO on duty will have one hour available until briefing time (ETD minus 01h30) in order to comply with any eventual last minute changes.





Page 12A OM

PART B

TR 01 07-03-2017

Intentionally Blank




FLIGHT DISPATCH


2

OM PART B

Page 13

17-06-2016 Rev. 14

2.7 – WEATHER BRIEFING

Estimated execution time: 00h20m Shall be requested to IPMA with:

METAR and TAF of: Departure Airport,

all enroute alternates, Destination, takeoff and destination alternates

Corridor with narrow (20NM) Include Cross Section Charts at flight levels FL100, FL300, FL340 and FL390 or all bellow flight Top level, top level

and plus 2000ft (e.g. route FL260 charts FL100, FL260 & FL280; route FL320 charts FL100, FL300, Fl340)

Significant Weather Charts of Route Wind temperature Charts of Route

Volcanic Ash Charts if applicable MetOffice Charts of frontal systems Analysis and Forecast T+24 for flights over north Atlantic

and Europe.

2.8 – BRIEFING

Estimated execution time: 00h30m As part of assisting flight deck crew, the following documents must be prepared by an FOO:

Two copies of the operational flight plan;

One copy of submitted Flight Plan or ack message from Eurocontrol;

One copy of weather briefing including Satellite Image;

One copy of NOTAM briefing;

One Pre-Flight Dispatch checklist, that, after Captain’s approval, shall be copied and attached to the Flight Dispatch Folder;

One plotting chart, if applicable, with chosen en-route ETOPS alternate airports properly identified, as well as EEP, ETP and EXT and NAT Tracks;

One copy of NAT Track message, if applicable;

As many flight envelopes as required for the operation, complete with required forms;

One copy of overflying and landing permits, if applicable;

One copy of Flight Deck Briefing to be delivered to the Captain and one copy of Cabin Crew Briefing to be delivered to the Senior Flight Attendant;

Journey Report (AIMS 11.1.46) that, after filled by Captain, must be kept in a folder on OCC.

Six copies of General Declaration (AIMS 11.1.30)





Page 14 OM

PART B

Rev. 14 17-06-2016

All docs shall be sent by mail to crew and aircraft and paperwork will be handed out to SOT staff for delivery to the crew and all questions will be answered by internal phone.

2.9 – TAF UPDATE

Estimated execution time: 00h05m One hour before ETD FOO shall send an email to crew and aircraft mobile phone with last METAR´s, TAF´s of origin, destination and all alternates (take off, destination, enroute and ETOPS) as well as SIGMET of flown FIR´s. If crew have no net or did not receive the email should contact OCC in order that info is sent to Handling agent to be printed.




FLIGHT DISPATCH


2

OM PART B

Page 14A

16-03-2017 TR 02

Intentionally Blank




OUT-STATION DISPATCH

Page 15 OM

PART B

TR 02 16-03-2017

3 – OUT-STATION DISPATCH

The FOO on duty must comply with the time table specified previously (2), taking into consideration that all operational documents are sent to the out-stations usually 03 hours before and at least 02 hours before ETD, by any available means. It is preferable the usage of email, as all information can be condensed into one single message, sent with a delivery receipt. Email text shall have the following text: Quote: Find attached docs for the mentioned flight. (07 files attached). Please: AA// Provide one copy of all attached docs; BB// Provide relevant updated WX charts and text for the route; CC// Confirm if ATS flight plan is with relevant services or needs to be filled locally; DD// Advise if something is missing or not properly received;

EE// In case a NOTOC is passed to captain it must be sent to [email protected] and

[email protected] prior flight. FF// Please ACK this message; According with EASA965, you are hereby requested to maintain in your records, an approved and signed copy of the operational flight plan, at least for the duration of this/these flight(s). Unquote If no email address is available, all documents must be sent though the current flight plan service provider, and the SITA address LISOWYU must be part of the distribution list. Documents that are unable to be sent by email shall be sent by fax. The Pre-Flight Dispatch Checklist is to be signed by the FOO on duty and sent by email or fax, along with the remaining operational paperwork. It is absolutely mandatory that a copy of all sent documents is kept attached to the Flight Dispatch Folder, as well as respective digital delivery receipts. As an additional procedure, serving only as backup in case of failure of out-station contacts, all information should be sent to the flying crew members corporate email address, along with the aircraft e-mail. If no OFPL is received by PIC, or it is not available for a flight, as stated in OM A Chapter 8, Flight Dispatch will advise the following information to crew: ATC route Planned flight level Planned block fuel, trip fuel and landing fuel Planned fuel at TOC and TOD; Fuel check waypoints (every 30 minutes) Estimated take-off weight. All sent information will be kept as hard-copy for the remainder of the flight (as soon as flight is completed they can be destroyed) and soft-copies will be properly identified and stored in Dispatch’s internal server for backup.






3

OM

PART B Page 15|

17-06-2016 Rev. 14

3 – OUT-STATION DISPATCH

The FOO on duty must comply with the time table specified previously (2), taking into consideration that all operational documents are sent to the out-stations usually 03 hours before and at least 02 hours before ETD, by any available means. It is preferable the usage of email, as all information can be condensed into one single message, sent with a delivery receipt. Email text shall have the following text: Quote: Find attached docs for the mentioned flight. (07 files attached). Please: AA// Provide one copy of all attached docs; BB// Provide relevant updated WX charts and text for the route; CC// Confirm if ATS flight plan is with relevant services or needs to be filled locally; DD// Advise if something is missing or not properly received; EE// In case a NOTOC is passed to captain it must be sent to [email protected] and [email protected] prior flight. FF// Please ACK this message; According with EASA965, you are hereby requested to maintain in your records, an approved and signed copy of the operational flight plan, at least for the duration of this/these flight(s). Unquote If no email address is available, all documents must be sent though the current flight plan service provider, and the SITA address LISOWYU must be part of the distribution list. Documents that are unable to be sent by email shall be sent by fax. The Pre-Flight Dispatch Checklist is to be signed by the FOO on duty and sent by email or fax, along with the remaining operational paperwork. It is absolutely mandatory that a copy of all sent documents is kept attached to the Flight Dispatch Folder, as well as respective digital delivery receipts. As an additional procedure, serving only as backup in case of failure of out-station contacts, all information should be sent to the flying crew members corporate email address, along with the aircraft e-mail. If no OFPL is received by PIC, or it is not available for a flight, as stated in OM 8.1.1.23, Flight Dispatch will advise the following information to crew:

ATC route

Planned flight level

Planned block fuel, trip fuel and landing fuel

Planned fuel at TOC and TOD;

Fuel check waypoints (every 30 minutes)

Estimated take-off weight. All sent information will be kept as hard-copy for the remainder of the flight (as soon as flight is completed they can be destroyed) and soft-copies will be properly identified and stored in Dispatch’s internal server for backup.






Page 16 OM

PART B

Rev. 14 17-06-2016

Intentionally Blank




FLIGHT NOTIFICATIONS MESSAGE

4

OM

PART B Page 17

17-06-2016 Rev. 14

4 – FLIGHT NOTIFICATION MESSAGE

Flight Notification messages are issued by Flight Dispatch for all flights outbound or inbound LIS with 06 hours in advance as a minimum towards ETD/ETA. Receiving addresses shall include the contracted handling agent, all departments flight preparation related, fuel and catering suppliers, cleaning and airport authorities. The message must include:



Crew composition, if already available from AIMS; Crew composition, should it be available, must be included in the message so that the handling agent can produce a General Declaration to be used in those flights out of Schengen area and/or or military bases.

Minimum off block fuel, according with OM Part A 8.1.8.2 and estimated elapsed time; Fuel to supply must be the Minimum required as per the operational flight plan rounded up to the nearest hundred or thousand kilos; Estimated Elapsed Time (EET) is also extracted from the operational flight plan.

Any logistic action required, such as GPU, aircraft towing, cleaning services, with previous coordination with SOT. If the aircraft is parked in a remote position, the FOO on duty must contact the Airport Operational Control in order to coordinate a parking position suitable for fueling and crew /passengers boarding.

4.1 – LOGISTICS

Cargo containers, pallets, catering equipment, dressing and in-flight material are to be advised by SOT staff.




FLIGHT NOTIFICATIONS MESSAGE

Page 18 OM

PART B

Rev. 14 17-06-2016

Intentionally Blank




PRE-FLIGHT DISPATCH CHECKLIST /

FLIGHT DISPATCH FOLDER

5

OM PART B

Page 19 |

17-06-2016 Rev. 14

5 – PRE-FLIGHT DISPATCH CHECKLIST / FLIGHT DISPATCH FOLDER

A Pre-Flight Dispatch Checklist will be completed before each flight to ensure a flight will not be commenced unless it has been ascertained, to the extent possible, that conditions and ground facilities required for the flight are adequate for the type of operation. The Pre-Flight Dispatch Checklist / Flight Dispatch Folder will be retrieved from JUPITER, according with the number of legs that will be performed per crew. If not available, form must be filled with flight data and technical crew based on AIMS. This information may be obtained directly from the Rosters Department. All items are to be checked according with instructions on the Pre-Flight Dispatch Checklist. Procedures for proper analysis are defined in chapter 6 Operational Flight Plans. Attached to the Pre-Flight Dispatch Checklist / Flight Dispatch Folder, there will be a copy of all operational flight documents needed (and General Declaration) a so that the cockpit crew and the FOO utilize a common set of flight documents for each planned flight. Any relevant data, such as over-flight and landing permits, shall be also attached to this folder. Exchanged ATC messages, such as ACK, DLA, CNL and SAM messages shall also be kept, as well as airport slots confirmations. After flight is completed, the Pre-Flight Dispatch Checklist / Flight Dispatch Folder is to be scanned and backed up daily.



5 STANDARD OPERATIONAL PROCEDURES

FLIGHT DISPATCH

PRE-FLIGHT DISPATCH CHECKLIST / FLIGHT DISPATCH FOLDER

Page 20 OM

PART B

Rev. 14 17-06-2016




FLIGHT DISPATCH

OPERATIONAL FLIGHT PLANS

6

OM PART B

Page 21 |

17-06-2016 Rev. 14

6 – OPERATIONAL FLIGHT PLANS

Operational flight plans will be generated in accordance with the aircraft and schedule issued by Commercial Department as displayed on AIMS. Euroatlantic Airways uses SITA GRAFLITE in order to produce Operational Flight Plan, Flight Dispatch Manager is responsible to pass basic aircraft data to the provider whenever there are changes on the fleet or any info is received from Ops Engineering or DME (NF 06-14). If the flight departs from LIS, the operational flight plan must be signed by both FOO and PIC. If departing from out-station, the identification of flight deck crew and FOO’s name and license number must be written down on the operational flight plan.

6.1 – STANDARD KEYWORDS

Below are the standard keywords utilized in order to produce the operational flight plans:

M-CALLSIGN (M) As per ICAO Doc. 8585; M-CPT / FO (M) As per AIMS, if available; M-FD/ (M) Flight Dispatcher ID and License Nr; ATC-IS/1 (C) Default value ATC-IN/1. I: specifying flight rules I/V; S: type of flight as parag

7.5 DRM- (C) Description of MEL/CDL ITEM open with impact on Dispatch DTE- (C) Date of flight. Mandatory for route studies, usually YEAR if no season is

requested. Or to specify previous, present or next day. SWT-6000 (M) For B777 and B767 flight plan summary based on a gap of 6000Kg above

and below estimated ZFW, for B737 flight plan summary based on a gap of 4000Kg ;

SMB-20 (M) Elapsed time and fuel consumption 2000´ below planned flight level; WXS-3 (M) Weather report every three compulsive reporting points, 2000’ above and

below planned flight level;

NTM-Q (M) Company filtered NOTAMS automatically for destination and alternate ETOPS airports and Reclearance alternates. ENR- Keyword will force other airports as departure and no-ETOPS alternate Airports;

ENR- (M) Departure airport and all non ETOPS Enroute alternates; SWX-FT/ (M) Long TAF automatically for destination and alternate ETOPS airports and

Reclearance alternates. ENR- Keyword will force other airports as departure and no-ETOPS alternate Airports.

ARM-RMK/ (M) Free text to be used filing ATC FPLS (Item 18) namely callsign; ARM-PBN/ (C) can be used to override the PBN values;





Page 22 OM

PART B

Rev. 14 17-06-2016

MOD- (C) Minimum fuel on arrival as prescribed for each aircraft type – only to be used

if fuel on arrival is below figures stated in 6.5; AFU- (C) Extra fuel as per MEL or as prescribed for each aircraft type or by

appointment of the Fleet Chief, Chief Pilot of Flight Operations Director; RTW- (C) Restricted Takeoff Weight must be filled whenever different of MTOW; RLW- (C) Restricted Landing Weight must be filled whenever tankering is planned as

stated on parag 6.5; ; RVF- (O) Changes the amount of contingency fuel reserves. This amount may be

reduced to 3% (RVF-030) should it be needed to optimize payload for long-haul flights, according with EASA Air OPS regulations;

CAL- (M) Capping cruise flight level (B777: CAL-410; B767, B737 CAL-400), for flights

bellow one hour CAL-FL=flight time in minutes/2; FXH- (O) force altitude during flights in accordance with FL odd/even rules; PRF- (O) force altitude during flights override FL odd/even rules. USE MUST BE

DONE WITH CAUTION;

EEP- (C) Defines ETOPS area and initiates calculation of ETOPS entry and exit points. Airports must be defined with ICAO code (four letters);

ETX- (C) Defines the equi-time points for the ETOPS alternates. If fuel on board, while

overlying an ETP is not enough to reach the ETOPS enroute alternate, the flight plan will automatically be re-calculated to take into account this extra value ; Option “/I “ will increase this value to take into consideration ice accretion, option “/T120” is required when aircraft is ETOPS120. Airports must be defined with ICAO code (four letters) ;

VID- (C) default MMZ. Changes ICAO designator on the operational flight plan RTE- (M) Must be always filled; If no route to alternate is automatically available after

destination must continue as: …<destination>/ALT <route to alternate>. DMT-03 (C) 03 minutes of fuel consumption whenever a SID is not defined on RTE. EQP- (C) can be used to override item 10a/b with new values. Must be used if a MEL

affects any of equipments TAX- (O) default B777 - 800kg, B767 – 500kg and B737 – 200kg. Provision of taxi fuel

(overrides normal taxi fuel) max 5 digits; CPA- (O) Cap the altitude/flight level between destination and first alternate . For time

of flights to alternate bellow one hour CPA-FL=flight time in minutes/2 CP2- (O) Cap the altitude/flight level between destination and second alternate (if

required). For time of flights to alternate bellow one hour CP2-FL=flight time in minutes/2.

OFC-F (C) Must be used on route studies to calculate navigation taxes; (M) mandatory, (C) Conditional, must be used on certain conditions, (O) Optional




FLIGHT DISPATCH


6

OM PART B

Page 23

17-06-2016 Rev. 14

For additional queries regarding flight planning, in order to comply with the conditions and limitations specified in the AOC, the FOO on duty will refer to SITA/Graflite’s Flight Planning Reference Manual, or contact SITA/Graflite’s HelpDesk at +44 (0) 0208 756 8333, [email protected] or QIFFPXS. Also, loaded SID and STAR can be verified by sending SITATEX messages as below: STARs

NDP ADP MMZ/(airport ICAO code)/A

SIDs

NDP ADP MMZ/(airport ICAO code)/D

Or via AVIVA see chapter 17. If, for any reason, Graflite software becomes unavailable, flight plans can be requested through SITATEX messages as follows, sent to QIFPMXS:

CFP MMZ/9999/TIP/BEY/TLZ ETD-1330 ETA-1630 FLT-156,GRF- ALT-LCA/S PLD-41000 M-CPT/xxxxxxx M-FD/xxxxxx SWT-4000,SMB-20 SWX-FT/TIP/BEY/LCA/CAI/ATH,WXS-3 ATC-IN/1,VID-TMA,CPA-240 RTE-TIP/GARU1C GARUS/V400 WHALE/M1 RASNO/UM1 ARLOS/UB1 RTE-PLH/UM978 LCA/UR19 KUKLA/KUKL2F BEY MOD-4500 NTM-Q/TIP/BEY/LCA/CAI/ATH

MMZ/9999/(origin) / (dest) / (acft tail number) ETD ETA FLT-(flight number),GRF- ALT-(alternate)/S PLD-(payload) Remaining keywords as mentioned above

Or via FBOL, see chapter 17.






Page 24 OM

PART B

Rev. 14 17-06-2016

6.2 – HOLD ITEM LIST (HIL) VERIFICATION

Prior to the beginning of dispatch, the FOO on duty shall take into consideration any HIL items and respective MEL items that may affect normal flight dispatch procedures. This information is available from Jupiter and can be accessed as follows:

Jupiter Go To Operações Gráfico

Click on the aircraft’s registration

Based on the information displayed, maintained and updated by DME/MOP/TS as per MCC’s NF-04, the FOO on duty will analyze respective MEL in order to dispatch an aircraft with limitations.

6.3 – EXPECTED PAYLOAD

Expected payload, if available from AIMS or reliable sources (e.g. handling agents), will be used for the production of the operational flight plan. If no payload is available, the following weights shall be used:

B777-200 (CS-TFM) 30.000 Kgs

B767-300 (CS-TFT/ CSTKT/CS-TRN) 30.000 Kgs

B767-300 (CS-TLO/CSTKR) 25.000 Kgs

B767-300 (CS-TKS) 26.000 Kgs

B767-375ER (CS-TLZ) 40.000 Kgs

B737-800 (CS-TQU) 14.000 Kgs

Position flights 1.500 Kgs (for CS-TLZ consider 3000Kgs)

All queries referring to Dangerous Goods transportations must be forwarded to SOT staff




FLIGHT DISPATCH


6

OM PART B

Page 25

Rev. 14 17-06-2016

6.4 – OFPL ANALYSIS

Upon completion of operational flight plan, the optimized route shall be verified regarding the following items:

1. Structural/Operational Limitations Weight, through FlygPrestanda website.

2. NOTAMs, through SITA/Graflite software or reliable sources, such as EAD; This NOTAMs briefing will be verified thoroughly with special incidence in origin, destination, alternates, ETOPS alternates and enroute alternates. Also, since NOTAMs are received in 'parts', the FOO will make sure that the briefing is complete and that all pages are accounted for. If runway deficiencies and/or obstacles are encountered, the FOO on duty will notify FlygPrestanda as stated in FlyGp Instructions.

3. Meteorological conditions, through SITA/Graflite software or reliable sources, such as Instituto Português do Mar e da Atmosfera:

o Origin, destination and en-route airports, as determined in OM Part A 8.1.2 “Criteria for Determination the Usability of Aerodromes”;

o Significant weather charts, through local Meteorology Office; o ETOPS en-route alternates, if applicable, as determined in OM Part A 8.1.2 “Criteria for

Determination the Usability of Aerodromes”;

4. Current NAT Track message, if applicable, through SITA/Graflite’s staff;

5. Wind shear

6.5 – MINIMUM FUEL ON BOARD

Unless otherwise stated, as per Fleet Chief’s request, a minimum required fuel policy is to be carried out and must take into account what is stated in OM Part A 8.1.7.1 Fuel Planning Procedures To increase final reserve fuel awarness the value for every operational flight plan must have as minimum fuel on board upon arrival as follows:

B777-200 7.000 Kgs

B767-300 5.000 Kgs

B737-800 3.500 Kgs If tankering fuel is required, in order to avoid over-weighted landings, Maximum Landing Weight shall be limited as follows below, using RLW- keyword:

B777-200 4.000 Kgs

B767-300 3.000 Kgs

B737-800 2.000 Kgs

6.6 – ALTERNATE AERODROMES SELECTION

For dispatching the aircraft it shall be assumed that: (1) aircraft will land on the most favorable runway, in still air; and (2) aircraft will land on the runway most likely to be assigned, considering the probable wind speed and direction, the ground handling characteristics of the aircraft and other conditions such as landing aids and terrain.

However, if unable to comply with (1) for a destination aerodrome having a single runway where a landing depends upon a specified wind component, the aircraft may be dispatched if two alternate aerodromes are designated. In turn, if unable to comply with (2) for the destination aerodrome, the aircraft shall be only dispatched if an alternate aerodrome is designated.





Page 26 OM

PART B

Rev. 14 17-06-2016

All destination alternate aerodromes shall be chosen as per what is stated in OM Part A 8.1.2 “Criteria for Determination the Usability of Aerodromes”. Take-off alternate selection must be in accordance with OM Part A 8.1.2.4.2 “Takeoff Alternate Aerodrome” and must be recorded in both in the OFPL an in the Pre-Flight Dispatch Checklist. Whenever available, ATS routes for alternate aerodromes shall be provided when preparing the operational flight plan, by adding “/S” to the aerodrome code. If no ATS route is available, it shall be add on RTE keyword or a request shall be made to SITA Graflite’s Helpdesk and Navdata department.

6.7 – ETOPS FLIGHTS

ETOPS flights are to be dispatched taking into account OM Part A 8.5.8 “Flight Dispatch”, and OM C Chapter 3 - ETOPS Enroute Airports tables ATS flight plans must reflect chosen ETOPS alternates at field 18.

6.8 – REDUCED CONTINGENCY FUEL PROCEDURE / DECISION POINT PROCEDURE (RECLEARANCE) FLIGHTS

Reduced Contingency Fuel Procedure / Decision point procedure operational flight plans are described in OM Part A 8.1.8.3. All aerodromes must be considered Adequate as a minimum (OM A 8.1.2.2.1) and weather conditions must be in accordance with Planning Minima for Destination Aerodrome (OM A 8.1.2.3.2) and Planning Minima for En-Route Alternate Required at the Planning Stage, Destination Alternate Aerodromes, Isolated Destination Aerodrome and 3% ERA aerodrome (OM A 8.1.2.3.3). In order to produce such a flight plan, the following keywords shall be used:

RCR-VIE/BTS/ALB RTE-CCU/DCT TEPAL/R460 GGC/R460 BBN/R460 LLK/R594 RTE-DPN/G333 TIGER/G452 ZDN/UL125 RADAL/T210 RUS/R661 RTE-ZAJ/UL124 BONAM/UG81 VAN/UL852 CRM/UT33 SIN/UT33 RTE-KUGOS/UL851 SUBES/UL610 BATTY/DCT LOGAN/LAM3A RTE-LHR/RCR ALB/Y102 MIQ/UL605 GAMLI/GAML4W VIE

Reclearance format – INITIAL DESTINATION / INITIAL ALTERNATE/ DECISION POINT Route description– ORIGIN to FINAL DESTINATION, followed by “keyword” “/RCR”, from which the next route description will be from DECISION

POINT to INITIAL DESTINATION.

6.9 – GMORA ANALYSIS

As defined in OM Part A 8.1.1.1 “Flight planning requirements”, the operational flight plan automatically calculates eventual GMORA conflicts. GMORA warnings result when, in case of engine failure, aircraft’s level off altitude is below published GMORA. However, as published GMORAs usually reflect a considerable large area, in case of such warnings, the FOO will request a detailed analysis from Operations Engineering. Based on such analysis, the FOO will:

Maintain ATC routing, after receiving confirmation from Operations Engineering, or;




FLIGHT DISPATCH


6

OM PART B

Page 27

Rev. 14 17-06-2016

Maintain the planned ATC route, after receiving confirmation from Operations Engineering, if an escape route or a similar possibility is available to allow an emergency descent, or,

Modify the planned ATC route to avoid the fore mentioned conflict. Operations Engineering analysis take into consideration oxygen requirements as follows:

Oxygen Supply (IAW CMM 35-21-

50)

A/C

22 MIN CS-TFM

12 MIN CS-TFT

22 MIN CS-TKR

22 MIN CS-TKS

22 MIN CS-TKT

12 MIN CS-TLO

12 MIN CS-TRN

(*) CS-TLZ

12 MIN CS-TQU

(*) IAW minimum dispatch pressure for installed oxygen cylinders “MEL ATA 35-11-2-OXYGEN”

6.10 – OPERATIONAL FLIGHT PLAN DECODER

Current operational flight plan format and respective decoder can be found at OM Part A 8.1.8.2 “Operational Flight Plan”.





Page 28 OM

PART B

Rev. 14 17-06-2016

Intentionally Blank




FLIGHT DISPATCH

FILLING AND MANAGEMENT OF ATC FLIGHT PLANS

7

OM PART B

Page 29

Rev. 14 17-06-2016

7 – FILLING AND MANAGEMENT OF ATC FLIGHT PLANS

ATC flight plans will be filed through SITATEX as follows:

To both IFPS centres when the route lies within the IFPZ boundaries. It is recommended that “RMK / IFPSRA” to be added upon submission.

FP1 - Brussels (Haren) FP2 – Paris (Brétigny)

AFTN EUCHZMFP LFPYZMFP

SITA BRUEP7X PAREP7X

Ops Telephone + 32 (0)2 745 1950 + 33 (0)1 6988 1750/62/66

Ops Fax + 32 (0)2 729 9041 + 33 (0)1 6988 3822

Since it is IFPS responsibility to verify and acknowledge submitted ATC routes, the FOO on duty, in case of doubts regarding eventual route changes, will contact the appropriate IFPS centre according with the below table:

IFPS unit responsible for processing

Flights departing all aerodromes within (ICAO country codes)

FP1

E..., (except EKVG), LK.., LO.., LS.., LZ.., PC.., PG.., PH.., PJ.., PK.., PM.., PW.., PT.., K..., M..., T..., S..., all ZZZZ departures, all flight plans with source AFIL

FP2

LA.., LB.., LC.., LD.., LE.., LF.., LG.., LH.., LI.., LJ.., LL.., LM.., LN.., LP.., LQ.., LR.., LT.., LU.., LV.., LW.., LX.., LY.., EKVG, PA.., PF.., PL.., PO.., PP.., A..., B..., C..., D..., F..., G..., H..., N..., O..., R..., U..., V..., W..., Y..., Z...

To concerned FIRs, TWRs, AIS room, ARTCCs and AROs of both origin and destination aerodromes, when the route lies outside the IFPZ boundaries, through AFTN message (FF designator)

To IFPS centers and through AFTN message (AD designator – see paragraph 7.1) to concerned FIRs, TWRs and AROs of both origin and destination aerodromes, when the routes leaves or enters IFPZ boundaries..

SITA messages can be accessed through Internet browser as below: URL: https://internetmail.mconnect.aero: Username: [email protected] Password: __________

7.1 – IFPS READDRESSING FUNCTION

The FOO on duty can use IFPS readdressing function, when the routes leaves or enters IFPZ boundaries, by submitting the ATC flight plan to both IFPS centers and adding the concerned AFTN addresses through the AD designator.





FILING AND MANAGEMENT OF ATC FLIGHT PLANS

Page 30 OM

PART B

Rev. 14 17-06-2016

7.2 – ROUTE MODIFICATIONS

All Operational flight plans will be in accordance with the ATS route approved by ATS centers. ATS routes, and/or any last minute route changes imposed by IFPS or any other ATS center, will be previously coordinated with such centers, and will be reflected in a new operational flight plan that must be delivered / transmitted by any feasible means to the PIC before departure.

7.3 – FLIGHT PLAN ROUTE VALIDATION

Since IFPS will correct or reject any route that does not comply with ATS regulations, routes within, entering or leaving IFPZ boundaries shall be validated using CFMU’s Free Text Editor. (Additional queries will be addressed to Flight Plan Filling Department at +32 (0) 2 745.19.50/62/66.

7.4 – ROUTE AVAILABILITY DOCUMENT

Route planning can also be verified through the usage of the RAD (Route Availability Document – via NOP website) and all region-specific route restrictions can be obtained from Navtech ECHARTS OFFICE software or navcharts.

7.5 – TYPE OF FLIGHT / EMISSION TRADING SYSTEM

Although EuroAtlantic’s operation is considered to be non-regular, the FOO on duty will take particular notice to the flight’s characteristics and submit ATS flight plans accordingly by indicating the correct letter on field 8 (Type of Flight). Special attention must be taken to flights that begin and end in the same airport without additional landings or flights exclusively for the purpose of obtaining flight licenses (base-flights). These flights must be submitted with X (other than defined categories) at field 8 and must have a remark written down at field 18, eg, “RMK/TRAINING FLIGHT - REQUEST TOUCH-AND-GO AT LPPT”, hence becoming exempted from Carbon Dioxide Emission Trading System regulated by EU Directives. For reference, below is an excerpt of Doc. 4444: “TYPE OF FLIGHT: Denotes the type of flight as follows: “S” for Scheduled Air Service, “N” for Non-scheduled Air Transport Operation, “G” for General Aviation, “M” for Military, and “X” for everything else.” For “X” flights add RMK STS/HEAD for presidential flight, STS/HUM for humanitarian flight STS/STATE for state flight.




FLIGHT DISPATCH

FLIGHT WATCH

8

OM PART B

Page 31

17-06-2016 Rev. 14

8 – FLIGHT WATCH

The following tasks are to be completed in order to assist the PIC.

8.1 – AIRNAV FLIGHT TRACKER

AirNav Flight Tracker is intended for flight watch purposes. Updated regularly with 28-day AIRAC cycle, it will graphically represent EuroAtlantic’s aircrafts when in flight. Jupiter has been programmed to liaise directly with AirNav, hence updating it automatically with flight plan. FOO must send AD and ED MVT from AIMS to [email protected] If any anomaly in the normal process of the aforementioned contracted tasks is detected, such as unexpected delays, loss of server communications, missing or inaccurate data, the FOO on duty will advise AirNav Systems Customer Support through the following contacts for immediate resolution:

AirNav Systems Phone: 1-619-330-2482 / +351 918 767 767

Toll-free 1-800-401-2474

Fax: 1-619-923-3393

Email: [email protected] [email protected]

Address: AirNav Systems LLC, 4660 La Jolla Village Dr. Suite 500, San Diego, CA 92122 - USA

This notification will be made available to the Flight Dispatch Manager, who will contact AirNav Systems Supervisor, open a case file, where the root cause of such anomaly will be identified and corrective actions will be taken. Depending on how important the anomaly may be, the Flight Dispatch Manager will notify the Quality Manager and the Flight Operations Manager of such occurrence. Thus, by constantly monitoring these external services in day-by-day basis, the FOO on duty complies with outsourced service providers monitoring.

8.2 – JUPITER (ETOPS MONITORING)

The JUPITER software is a valuable software tool for flight watch as soon as CFP was updated and T/O time filled ETOPS significant times are calculated and an on time alert is pop up on FOO screen to check ETOPS alternates conditions, namely METEO and NOTAMs. FOO shall archive relevant info on respective folder.

8.3 – AIMS

The AIMS software must be correct and permanently updated by the FOO on duty for flight watch; Below are several examples how AIMS should be updated. 8.3.1 SCHEDULE or RE-SCHEDULE (on behalf of Comm Dpt) Flight are schedule or re-schedule by Commercial Department during office hours, otherwise OCC have to do it on their behalf. No historic log is required. If it is a Re schedule OOV shall change flight on “Flight Schedule Changes”, status shall be changed to RS. Delay will be considered from new schedule. Noted on JUPITER






FLIGHT WATCH

Page 32 OM

PART B

Rev. 14 17-06-2016

8.3.1.1 Insert New Carrier Code.

If carrier code does not exist an error message will be displayed

Go to AIMS 7.4.5. System Configuration/Crew Management System Related Codes/Crew Transport –Carrier Codes and fill “IATA code” and “ICAO code”




FLIGHT DISPATCH

FLIGHT WATCH

8

OM PART B

Page 33

17-06-2016 Rev. 14

8.3.2 RE-SCHEDULE (OCC) A flight is re-schedule due client request or Rosters requirement with Commercial Department approval. FOO shall fill ETD on “Actual flight info” and mark “Re-schedule (change STD/STA) as well”. Then change flight on “Flight Schedule Changes”, status to RS. Graphically noted change, delay will be considered from initial schedule and crew have to be informed by Rosters about new reporting time. Schedule flights MUST NOT change STD/STA unless decided by Customer, if needed a new report time must be defined and pass to crew. A new JLOG must be sent to crew. Noted on JUPITER

8.3.3 DELAY CREW REPORT TIME A flight is delayed due duty time requirement (must be considered when at least one crew member reports). FOO shall fill ETD on “Actual flight info” and mark “Delay the crew report time” flag. Then change flight on “Flight Schedule Changes”, status to RS. Graphically noted change, delay will be considered from initial schedule and crew must be informed by rosters about new reporting time. A new JLOG must be sent to crew. Not noted on JUPITER.




FLIGHT WATCH

Page 34 OM

PART B

Rev. 14 17-06-2016

8.3.4 DELAY (AND ATC FLIGHT PLAN SUBMITED) A new ETD is required by client or due operational reasons, ATC Flight Plan or a Delay was submitted. FOO shall fill ETD on “Actual flight info” send a MVT message to AIRNAV ([email protected] ) with ED and if necessary to the client. Graphically noted change (red), delay will be considered from initial schedule. Not noted on JUPITER.

8.3.5 DIVERT & FORCE TO RETURN DIV/FR/RR If a flight is diverting (DIV) returning ramp (RR) returning ramp on departing airport (FR). FOO shall press DIV fill “Divert flight“ with all data, than select “Generate a corresponding message” if necessary to inform airports involved and generate a report with all flights that will be affected. 8.3.5.1 RETURNING RAMP (RR) After insert data send a new JLOG to captain. If necessary send new CFP, NOTAM and weather briefing.





FLIGHT DISPATCH

FLIGHT WATCH

8

OM PART B

Page 35

17-06-2016 Rev. 14

8.3.5.2 FLYING TO RAMP (FR) After insert data on AIMS send a new JLOG to captain. After be informed about new ETD send new CFP, NOTAM and weather briefing.

8.3.5.3 DIVERT (DIV) Get intentions from captain, inform client and get their intention. Inform key persons on company and fill AIMS.




FLIGHT WATCH

Page 36 OM

PART B

Rev. 14 17-06-2016

8.3.6 CHANGE DATE OF FLIGHT (RE-SCHEDULE OR DELAY) If re-schedule or delaying a flight changes the date of flight it is necessary to correct Estimated dep day. A pop up window will advise in order to check. Inform rosters because crew must be add again.

8.3.6 CHANGE OF REGISTRY (AIRCRAFT TYPE) Select route or flight concerned and drag for correct aircraft. A pop-up menu will ask to confirm if you want to move registry and aircraft type. A pop-up window with “not qualified crew” shows up and FOO shall de-assign one by one defining a modification reason.




FLIGHT DISPATCH

FLIGHT WATCH

8

OM PART B

Page 37

17-06-2016 Rev. 14




FLIGHT WATCH

Page 38 OM

PART B

Rev. 14 17-06-2016

Movement signals received will have to be filled on AIMS the following priority/reliability order must be considered:

Flight deck crew phone call or SMS;

CFMU secure website;

Handling agent movement messages

Chokes are to be rounded up in multiples of 5 and take-off and landing movements will be updated to the exact minute. On depart fill ATD, TOFF, ETA and FPBurn (based on CFP), V2, Total pax, departure delays if applicable. 8.3.7 FILL JOURNEY LOG

Upon reception of the Journey Log, the FOO on duty must update AIMS,(menu 4.2. Voyage Reports) scan the report, sent it to predetermined mailing list and archive. A special attention must be given to flight time and block times, pax, as well as fuel

Do not send JLOG if any value is incorrect




FLIGHT DISPATCH

FLIGHT WATCH

8

OM PART B

Page 39

17-06-2016 Rev. 14




FLIGHT WATCH

Page 40 OM

PART B

Rev. 14 17-06-2016

8.4 – ARO / AIS

If necessary, due to computer breakdown or other reasons that may prevent an automatic flight monitoring, the FOO on duty will contact Lisbon AIS in order to, through the appropriate ATS services, maintain flight monitoring.

8.5 – COMMUNICATION DISPATCH / COCKPIT

On ground, through the use of the aircraft’s mobile phone, the FOO on duty will maintain a permanent watch upon the turnaround, being alert for the need of any specific request from cockpit. The FOO on duty will act as liaison with GCM, if such need occurs. At departure crew must send MVT, V2, number of pax, delay codes and times as well as info if there is a NOTOC for FOO fill AIMS System as describe in SOPS 737/767/777. When airborne, if the need to contact an aircraft occurs, or in case of an emergency first known to the operator, the FOO on duty will contact Stockholm Radio services who will redirect the call or send an AFTN message to ATC with following text: “Please pass to “callsign” – “contact your operations center via stocholm radio. Thanks for cooperation, Best regards”. In the event of an emergency, the FOO or other delegated person initiates procedures as outlined in the ERPM, while avoiding taking any action that would conflict with ATC procedures; Verbal communications held with any aircraft, such as movement messages, delay requests, or any abnormal situation shall be recorded on AIMS Actual flight info. VHF or HF comms (even attempts on Stockholm Radio) must be written by clicking the memo icon and select “14.Comms OCC/Flt crew” .

At arrival crew must send final MVT as stated in SOPS 737/767/777 for FOO fill AIMS System

8.6 – CFMU SECURE WEBSITE (NOP)

In order to maintain a more thorough flight monitoring, CFMU website will be checked at least every hour for updates regarding the ATD and ATA of aircraft. If CFMU website is out of service, the FOO on duty will contact local ARO requesting above information.




FLIGHT DISPATCH

FLIGHT WATCH

8

OM PART B

Page 41

17-06-2016 Rev. 14

8.7 – METEOROLOGY

All meteorological improvements/degradations must be analyzed, specifically those mentioned in FD SOPS 6.3. Significant degradations that may jeopardize flight safety are to be communicated to flight deck crew as per 8.5.

8.8 – RUNWAY DEFICIENCIES/DOWNGRADE

While performing flight watch, in the event of a runway intended to operate that became downgraded or inadequate for the safe conduct of a flight, the FOO on duty will immediately advise the flight deck as per 8.5, Fleet chief, Commercial Department and GCM.

8.9 – DIVERTION PROCEDURES

In the event of a diversion, the FOO on duty will advise the Fleet chief, Commercial Department and GCM. If required, the FOO will co-ordinate with client to apply for handling services. Written communications shall be sent to “euroAtlantic atrasos e diversões” mailing list. AIMS procedures as par 8.3

8.10 – SIGNIFICANT DELAYS

Any situation that can result in a significant delay shall be communicated through “euroAtlantic atrasos e diversões” mailing list. In this circumstance, ED messages must be sent to all stations, client included. AIMS procedures as par 8.2.

8.11 – SACA (SAFETY ASSESSMENT FOR COMMUNITY AIRCRAFT)

Whenever reported by PNT or other reliable sources that a SACA/SANA is being held at one of euroAtlantic’s aircrafts, all available information shall be communicated through “euroAtlantic SAFA report” mailing list.




FLIGHT WATCH

Page 42 OM

PART B

Rev. 14 17-06-2016

8.12 – PARKING AUTHORIZED

Whenever received LIS, OPO or FAO parking authorization, or aircraft is in other airport parked or it is at “TAP Hangar” shall be reflected at AIMS 4.1 Aircraft Movement Control with a Yellow box stating “Airport, Stand 999” or “TAP Hangar”.

8.13 – AIRCRAFT UNAVAILABLE FOR COMMERCIAL DEPARTMENT

Any department that identify a major reason to keep aircraft unavailable for Commercial Department shall be reflected at AIMS 4.1 Aircraft Movement Control with a Black box stating reason and department in charge, e.g. “SOT / Blocked for security” or “SOT / Blocked for cleaning”.




FLIGHT DISPATCH

EMERGENCY PROCEDURES

9

OM PART B

Page 43

17-06-2016 Rev. 14

9 – EMERGENCY PROCEDURES

In case of missing contact/information at aircraft’s scheduled ETA, the FOO on duty will attempt to obtain this data through Stockholm Radio, aircraft’s mobile phone, ATS services and/or local handling agent. If no information is obtained, notification procedures described in 9.1 will occur. In the event of an emergency situation that endangers the safety of an aircraft or persons, first known to the FOO, the FOO will retrieve all operational data available (Callsign; aircraft position; time of report; aircraft’s altitude; PIC’s intentions). If required, the FOO will also request for assistance to the appropriate Rescue & Coordination Center.

9.1 – NOTIFICATION

1st Step - in case of an incident or accident (ERPM color code RED) with a EuroAtlantic aircraft on

ground or during flight, the first contact from the ATC is made directly to the Flight Operations Officer on duty. 2nd Step - Regardless of the seriousness or category of the situation, the Flight Operations Officer on Duty, must immediately call the ECC Manager, Eduardo Nascimento - mobile +351 912573200, and make a clear statement of the occurrence according to the information received and confirm this information by mail to:

[email protected]

with copy to:

[email protected];

[email protected]

[email protected];

[email protected];

[email protected] ;

[email protected];

[email protected];

rufino.oliveira@ euroatlantic.pt;

joao.semedo@ euroatlantic.pt ;

[email protected];

This message works as the first alert and for the records, must be written on simple and clear language and contain the same information transmitted to the ECC Manager during the first phone call, including the time of contact. Kenyon International Emergency Services will be informed as well, through H24

contact phone +44 (0) 1344 316 650, as soon as the ALERPHA or DISTRESS PHASE is declared by

the ECC Evaluation Risk Committee. 3

rd Step - The Flight Operations officer on duty, after acting according points above, must also alert the

Flight Dispatch Manager, if he is not present, in order for him to come immediately to its Job Site and take control of the situation acting in accordance with the checklist and obligations of this department. 4

th Step - The ECC Manager, after receiving the information above, must immediately call and request

the presence at the Emergency Command Center of the following members also called as the Evaluation Threat Committee as described below:





Page 44 OM

PART B

Rev. 14 17-06-2016

A

Flight Dispatch

B

ER Manager

C

Kenyon

C

Accountable Manager

D

Flight Ops Manager

E

Safety Manager

F

Chief Pilot

11 Go-Team 12 DQU 13 DME7 DOT 14 DAF 12 DCO9 Cabin Crew

Manager

10 Ops Eng.

Manager

8 Fleet Chief

Pilots

1 PCA

Evaluation Risk Committee

6 Rosters

Manager

5 Training

Manager

Emergency Management Center

4 Comm.

Manager

2 Legal

3 Marketing

G

IT

Supply the responsible Rescue & Coordination Center and overflown FIR/UIR through AFTN messages, stating the nature of the emergency and all the information retrieved previously and emergency survival equipment on board, using the “Flight Dispatch Emergency Contacts and Survival Equipment” list

xxxx ZOZX (FIR/UIR Oceanic); xxxx ZQZX (FIR/UIR); xxxx ZRZX (FIR/UIR Radar Control) ; xxxx YCYX (RCC);

Notify the Safety Manager, or, if unable to establish positive contact, notify Maintenance Control Centre (GCM) in order to preserve all records regarding the emergency, as per OM A 11.2.3;

Maintain Euroatlantic’s Emergency Committee updated with any developments that might occur.

9.2 – FLIGHT DISPATCH EMERGENCY CONTACTS AND SURVIVAL EQUIPMENT LIST

This list is updated by the Flight Dispatch Manager, or his/her deputy when absent from duty, and is solely based on data contained in the Cabin Manual or retrieved through DME Engineering and Logistic’s department. DME Engineering and Logistic’s department will inform any changes directly to the Flight Dispatch Manager.. This list must visible and accessible to FOOs at all time, preferably in a hard copy format near their working station.




FLIGHT DISPATCH


9

OM PART B

Page 45

17-06-2016 Rev. 14

9.3 – FLIGHT DISPATCH EMERGENCY AND SURVIVAL EQUIPMENT CONTACTS

LISBON ACC TEL: +351 21 855 33 17 LISBON MIL TEL: +351 21 855 34 62/59 LISBON RCC TEL:+351 21 771 60 00 / +351 21 770 82 07 (Fax: +351 21 770 81 34) AFTN LPAMYCYX OCEANIC RCC TEL:+351 295 54 05 15 (Fax: +351 295 54 07 92) AFTN LPLAYCYX FOR OTHER FIR/UIR RCC USE AFTN ADDRESSES AS FOLLOWS: XXXX YCYX (RCC) XXXX ZQZX (ACC) XXXX ZOZX (ACC OCEANIC) XXXX ZRZX (ACC RADAR COVER)

EMERGENCY SURVIVAL EQUIPMENT AS PER CM, AMM and EEL

Yellow Rafts

Normal /overload capacity

Survival kits

Flares Water Supplies

First-Aid Kits

Medical Kit

ELTs Type / Frequencies

CSTFM 06x Life Raft 51 / 59 02x Life Raft 54 / 62

08 16 326 gallons. 04 01

02x Rescue Kannad 406AS 01 fixed ELT 121.5VHF / 243MHz / 406MHz (sat)

CSTFT 06x Slide Raft 58 / 78 02x Slide Raft 46 / 57

08 12 298 gallons 04 01 02x Rescue Kannad 406AS 121.5VHF / 243MHz / 406MHz (sat)

CSTKS 04x Slide Raft 46 / 57 02x Slide Raft 24 / 32 02x Slide Raft 58 / 78

08 16 298 gallons 04 01


CSTKT 04x Slide Raft 46 / 57 02x Slide Raft 24 / 32 02x Slide Raft 58 / 78

08 16 298 gallons 04 01


CSTKR 04x Slide Raft 46 / 57 02x Slide Raft 24 / 32 02x Slide Raft 58 / 78

08 16 298 gallons 04 01


CSTLO 01x Life Raft 46 / 69 04x Slide Raft 58 / 78

05 10 298 gallons 04 01 02x PLB 500-12Y 121.5VHF / 243MHz / 406MHz (sat)

CSTLZ 02x Life Raft 06 / 09 02 04 4 gallons (lavatory)

01 n/a 01x Rescue 406S 121.5VHF / 243MHz / 406MHz (sat)

CSTQU 04x Life Rafts 46 / 69 (may be without life rafts)

04 08 60 gallons 03 01

02x Rescue 406S 01 fixed ELT 121.5VHF / 243MHz / 406MHz (sat)

CSTRN 06x Slide Raft 58 / 78 02x Slide Raft 46 / 57 08 16 298 gallons 04 01

02x Rescue 406S 121.5VHF / 243MHz / 406MHz (sat)





Page 46| OM

PART B

Rev. 14 17-06-2016

FIRST AID KIT MEDICAL KIT

Bandages (unspecified)

Burns dressings (unspecified)

Wound dressings, large and small

Adhesive tape, safety pins and scissors

Small adhesive dressings

Antiseptic wound cleaner

Adhesive wound closures

Adhesive tape

Disposable resuscitation

Simple analgesic

Antiemetic

Nasal decongestant

Splints, suitable for upper and lower limbs

Gastrointestinal antacid

Anti-diarrhea medication

Ground/Air visual signal code for survivors

Disposable gloves

Sphygmomanometer – non mercury

Stethoscope

Syringes and needles

Oral pharyngeal airways

Tourniquet

Coronary vasodilator

Anti-spasmodic

Epinephrine 1:1000

Aden cortical steroid

Major analgesic

Diuretic

Antihistamine

Sedative / anticonvulsant

Medication for hypoglycaemia

Antiemetic

Atropine

Digoxin

Uterine contracting

Disposable gloves

Bronchial dilator – including an inject able form

Needle disposal box

Anti-spasmodic drugs

Catheter




FLIGHT DISPATCH

ATFM SLOT MANAGEMENT

10

OM PART B

Page 47

17-06-2016 Rev. 14

10 – ATFM SLOT MANAGEMENT

ATS flight plans, after being submitted to IFPS, are analyzed by CFMU (Central Flow Management Unit), regarding route, weather conditions in concerned airports, ATC acceptance rate, among other factors. Should the need to delay the ETD of a particular flight occur, CFMU will report it to the concern AIS centres and to Dispatch through SAM messages, addressed to LISOWYU. The FOO on duty shall maintain a constant watch of the flight’s status and let the flight deck crew know of new assigned CTOT; :

Let the flight deck crew know of new assigned CTOT;

If the delay is inferior to one hour, coordinate with the Captain so that he will issue a Ready Message directly to the TWR;

If no success is obtained through this action, the FOO on duty will contact CFMU directly by phone requesting an improvement which, if obtained, shall be immediately reported to the Captain.





Page 48| OM

PART B

Rev. 14 17-06-2016

Intentionally Blank




FLIGHT DISPATCH

DAILY TASKS

11

OM PART B

Page 49

17-06-2016 Rev. 14

11 – DAILY TASKS

The FOO on duty on night shift, usually comprised between 24.00h and 08.00 from Monday till Friday will have apply SIR format messages for Portuguese main stations to cross-check for unused runways slots and proceed to change/revise or deletion of mentioned slots.: On the morning shift, at 13:00 FOO on duty will apply for airport parking authorizations for all aircrafts parked at LIS or OPO and coordinate runways slots accordingly. If, by any chance, a parking authorization is not allowed or, by Airport Supervisor requirements, an aircraft is to depart from base airport, in addition to notifying Commercial, Rosters and Maintenance Department, the Finance Department and the Administration are to be alerted for this situation and specifically be informed that the positioning flight is due to parking limitations this must be done using “euroAtlantic parqueamento não autorizado” mailing list. FOO must coordinate with GCM and Commercial department which aircraft has to be positioning and in which airport. After decision coordinate with rosters and inform airport supervisor.

The FOO on duty on afternoon shift will check next 24 hours flights and, through Graflite, cross-check all available aerodrome NOTAMs for destinations and landing alternate to be operated; The FOO on afternoon shift duty on Monday Wednesday and Friday at 1730LT will initiate a conference call with Comercial Department, Finnance Department, Roster, maintenance and Ground ops in order to get an overview of expected activity till the next briefing. To coordinate this conference call use “euroatlantic conference call” mail list. The FOO on afternoon shift duty on Sunday must prepare Operations Weekly Briefing and, when ready send it through “Euroatlantic Weekly Report” mail list. Flight Dispatch Manager or it´s deputy is responsible to prepare the monthly briefing before first Monday of next month and send it through “Euroatlantic Weekly Report” mail list.




DAILY TASKS

Page 50 OM

PART B

Rev. 14 17-06-2016

Intentionally Blank




FLIGHT DISPATCH

ROSTERS MANAGEMENT

12

OM PART B

Page 51

17-06-2016 Rev. 14

12 – ROSTERS MANAGEMENT

12.1 – EAPIS (ELECTRONIC ADVANCE PASSENGER INFORMATION SYSTEM)

The following procedures apply when there is a need to send out of office hours.

a) Access https://eapis.cbp.dhs.gov e fill in “Sender ID” APIS*J9K (capital case)

b) Insert password ???????????? (small case) - -cross-check with Rosters Department

c) Terms and Conditions: I agree




ROSTERS MANAGEMENT

Page 52 OM

PART B

Rev. 14 17-06-2016

d) Inbound Flight/Outbound Flight

e) Carrier Code: MM; Flight Number: as per Jupiter; Suffix Code (for CSTLZ, the suffix code

is Z); Tail Registration: as per Jupiter, without the prefix for the country of registration;

f) Flight Itinerary – Fill in IATA code, local time;

g) Traveler Counts: Number of crew members, passengers and transit passengers

according with duty roster.




FLIGHT DISPATCH

ROSTERS MANAGEMENT

12

OM PART B

Page 53

17-06-2016 Rev. 14

h) Crew Information: Select crew members Show details Save to manifest;




ROSTERS MANAGEMENT

Page 54 OM

PART B

Rev. 14 17-06-2016

i) Review Manifest Done Next;




FLIGHT DISPATCH

ROSTERS MANAGEMENT

12

OM PART B

Page 55

17-06-2016 Rev. 14

j) Submit Print (as .pdf) and send to necessary departments;




ROSTERS MANAGEMENT

Page 56 OM

PART B

Rev. 14 17-06-2016

12.2 – FLEET MANAGEMENT

The following procedures apply when there is a need to update AIMS out of office hours. On “Aircraft Movement Control” 4.1, press Alt U

AIRCRAFT Route – flight number of first leg (must be unique for that date Aircraft – choose from pop up menu on same day as stated on Period (5.Fri in this case) Flight – flight number of leg with IATA code if not YU Of – off set day (with cursor verify date) Tp – choose from pop up menu Cr – Charterer if not airway code will be numeric and filled by Comm dept

12.3 – CREW MANAGEMENT – INSERT A CREW

The following procedures apply when there is a need to update AIMS out of office hours. On “Aircraft Movement Control” 4.1, press Alt U “CREW route”




FLIGHT DISPATCH

ROSTERS MANAGEMENT

12

OM PART B

Page 57

17-06-2016 Rev. 14

CREW Route – flight number of first leg with a letter (must be unique for that date Flight – select only legs to be flight Fill crew complement




ROSTERS MANAGEMENT

Page 58 OM

PART B

Rev. 14 17-06-2016

+ on Flight Schedule Changes MIS 17. Scroll stand-by list for flight till find crew with “No violation found”

Insert crew route number

Update Proceed Define a modification reason and confirm operation




FLIGHT DISPATCH

OVERFLIGHT PERMITS

13

OM

PART B Page 59

17-06-2016 Rev. 14

13 – OVERFLIGHT PERMITS

Usually, countries that have not adhered to the Schengen Agreement have specific entry and overflight requirements. To this end, the FOO on duty will check particular ATS routes and retrieve all over flown FIRs. By cross-checking this data with a plotting chart and with Navtech Airport Directory information, the FOO will contact the required CAAs in order to obtain overflight permits.

(FPL-MMZ1111-IS

-B763/H-SHIRWXYZ/S

-LPPT0640

-N0458F350 DCT OSLAD UR724 IBALU UN857 AMETA DCT ESS UR724

ADM/N0465F340 UR977 BULIS/N0461F370 UR981 GAO DCT UNOTA UR981

LAG UR603 INOSA DCT

-FPST0540 FOOL

-EET/GMMM0027 GOOO0135 DRRR0236 DGAC0403 DNKK0418

DGAC0456

FCCC0536

REG/CSTFK SEL/JMEK

RMK/CALLSIGN

OPR/MMZ

RMK/NAV/RNV10)

Whenever an urgent situation arise or Overflight permit is related to designated countries that euroatlantic have special agreements FOO must request a proforma with cc to Flight Dispatch manager in order to get permition from administration.




DOCUMENT STORAGE PROCEDURES

Page 60 OM

PART B

Rev. 14 17-06-2016

Intentionally Blank




FLIGHT DISPATCH


14

OM PART B

Page 61

17-06-2016 Rev. 14

14 – DOCUMENT STORAGE PROCEDURES

In order to comply with OM Part A 2.1.3 “Control Analysis and Storage of Records”, upon reception of a flight envelope, the FOO on duty must distribute documents as follows:

Journey Log – AIMS must be updated with data retrieved from the Journey Log. The Journey Log will then be scanned and sent to “euroAtlantic Relatórios de Voo” mailing list. It is kept separately at Flight Dispatch offices –

Fuel and oil records are to be separated and sent to Finance Department (airport mailbox);

Catering and aircraft cleaning services records are to be separated and delivered to SOT;

Cabin Crew reports are to be separated and sent to Cabin Crew Manager (white page) (Beloura Mailbox). They are to be scanned and sent to “euroAtlantic Cabin Crew Reports” mailing list;

Event record readout forms are to be scanned and sent to “euroAtlantic Event Record Readout” mailing list (Maintenance Mailbox);

Confidential Flight Reports are to be sent to Flight Operations Director (Beloura Mailbox);

Aircraft Accident / Incident Report GPIAA / Portuguese Civil Aviation Authority forms / Air Safety Reports are to be sent to Safety Department (Beloura Mailbox);

All Weather Operations I Automatic Approach Report forms are to be scanned and sent to “euroAtlantic Automatic Approach” mailing list (Beloura Mailbox);

Line Training Record forms are to be sent to Training Department (Beloura Mailbox);

Passenger Quality Questionnaires are to be sent to Marketing (Beloura Mailbox);

Airport Security Visit are to be sent to Security Department (Beloura Mailbox).

Fatigue Servey (Beloura Mailbox)

Upon completion of the above, the flight envelope must only contain the following:

Signed Pre-Flight Dispatch Checklist

Signed operational flight plans;

ATS flight plans;

Plotting charts

NAT Track message;

Take-off/Landing Cards;

Aircraft Security Check;

Load sheets;

Cargo Manifests;

NOTOCs, if applicable;

Weather briefings;

NOTAMs; These documents will be scanned and then stored for a period of 3 months. The scanned documents are backed-up daily.





Page 62 OM

PART B

Rev. 14 17-06-2016

Intentionally Blank




FLIGHT DISPATCH

ACMI PROCEDURES

15

OM PART B

Page 63 |

17-06-2016 Rev. 14

15 – ACMI PROCEDURES

ACMI requests must be always forwarded to the Commercial Department. After standard work schedule, national holidays, or weekends, if such a request occurs, the FOO on duty will:

Using AIMS, verify if there is any aircraft available to comply with ACMI request;

Confirm with GCM, through H24 mobile phone, in order to verify if there are any last minute MEL limitations that may decrease aircraft performance;

Use instructions received from Commercial Department, related with ACMI rate and aircraft preferences, providing them with client’s identification and possible schedule;

Answer to client with following message type:

EUROATLANTIC AIRWAYS IS PLEASED TO OFFER AS FOLLOWS: B767-300ER CS-T__ (__C____Y) FROM LIS ALL DAY

DEPARTURE 3HRS UPON FINAL CONFIRMATION FROM LIS ACMI RATE ______€ + __€ PERDIAMS PPP + HOTAC + TRANSFERS B777-200ER CS-TFM (30C293Y) FROM OPO ALL DAY DEPARTURE 6HRS UPON FINAL CONFIRMATION FROM OPO ACMI RATE ______€ + __€ PERDIAMS PPP + HOTAC + TRANSFERS OPERATIONS SUBJECT TO A/C AVAILABILITY AND PRIOR SALES, CREW CONTINUOUS AVAILABILITY, SLOTS, AUTH GOV, LANDING PERMITS, OVER FLIGHTS, CONTRACT SIGNED BY BOTH PARTIES AND FUNDS ON EUROATLANTIC BANK ACCOUNT COMMERCIAL DEPARTMENT PH:+351 21 9247315/16/17/18/19/20/24 FX:+351 21 924 7391 H24:+351 91 724 9671 EMAIL: [email protected] OCC PH:+351 21 844 4731 H24:+351 91 866 0983 SITA: LISOWYU EMAIL: [email protected]

If client request more info, the FOO on duty will:

Create a schedule, including departure and arrival flights from base, establishing 1 hour turnarounds for position flights and 1h30m (1h00M for B737) turnarounds for live flights.

Check all Airports in accordance with following AIRPORT RISK ANALYSIS table (to be used for

ROUTE STUDIES also). o In accordance with the bellow table check the total score of the airport. If the score is 5 or less FOO

may approve the use of airport. If the score is 5 or more, or even if one of the parameters has no score, an approval must be obtained from Fleet Chief, Chief Pilot or Flight Operations Director:






ACMI PROCEDURES

Page 64 OM

PART B

Rev. 14 17-06-2016

o Airfield Category (OM-part C) 0 – Cat A; 1 – Cat B; 4 – Cat C.

o Length 0 - Longer than 7000’ (6500’ for B737); 2 – Between 6000’ and 7000’ (6000´and 6500’ for B737); 5 – Shorter than 6000’.

o Width 0 – wider or equal of 45m; 5 – less than 45m.

o CFR of departure or destination 0 – B777 – 9, B767 – 8, B737 – 7; 5 – B777 – 8, B767 – 7, B737 – 6; 6 – B777 – 7, B767 – 6, B737 – 5 request approval from airport authorities.

o Radio Aids 0 – Precision approach; 1 – Non Precision approach; 5 – Without radio aids.

o Control 0 – Controlled airfield; 5 – Uncontrolled airfield.

If airport have limitations on PCN a previous permition from airport authorities must be received.

Confirm with Rosters Department, through H24 mobile phone, for crew availability to operate possible schedule. If HOTACS are needed, Rosters department will advise the FOO on duty to request it to the client.

Based on the information received by the above departments, the FOO on duty will inform client with cc for Rosters, GCM, Ground Ops and Commercial Department as follows: EUROATLANTIC AIRWAYS CAN OPERATE YOUR REQUEST AS FOLLOWS: ACFT: xxxxx-xxx VER. xxx/xxx PROPOSED SCHEDULE (UTC TIMES): xxx(date) LIS0600 – xxx0900 – POS xxx(date) xxx0800 – yyy1200 – LIVE xxx(date) yyy1330 – xxx1730 - LIVE xxx(date) xxx1830 – LIS2130 – POS ACMI RATE: xxx EUROS PER BLOCK HOUR + HOTACS + __ EUROS PER DIEMS IN CASE OF CONFIRMATION, YOUR CLIENT MUST: AA// PROVIDE OPERATIONAL CONTACTS FOR ALL STATIONS (TEL, FAX, SITA, E-MAIL, VHF); BB// ADVISE CATERING EQUIP NEEDS. ACFT IS xxx (KSSU/ATLAS) COMPATIBLE; CC// ADVISE BAGGAGE CONTAINER NEEDS. ACFT IS xxx (AKE/DPE/P6P...) COMPATIBLE; DD// ADVISE FLIGHT NUMBERS FOR ABOVE SCHEDULE, ICAO CODE AND RADIO CALLSIGN; EE// ADVISE PREFERABLE ROUTING BETWEEN LIVE SECTORS; FF// ADVISE OVERFLYING PERMITS (IF APPLICABLE); GG// ADVISE HANDLING AGENTS IN CASE A NOTOC IS PASSED TO CAPTAIN MUST BE SENT TO [email protected] and [email protected] prior flight. HH// PROVIDE HOTAC AND TRANFERS FOR xxx CREW MEMBERS AT xxx (IF APPLICABLE);

II// APPLY FOR DEPARTURE AND ARRIVAL AIRPORT SLOTS AT LIS AT EMAIL ADDRESSES [email protected] / [email protected] WITH COPY TO [email protected] / [email protected] DEPARTURE WILL OCCUR ___ HOURS AFTER FINAL CONFIRMATION.








FLIGHT DISPATCH

ACMI PROCEDURES

15

OM PART B

Page 65 |

17-06-2016 Rev. 14

ANY OFFER MADE BY EUROATLANTIC IS ALWAYS SUBJECT TO CONTINUOUS AIRCRAFT AVAILABILITY, CREW AND AUTH GOVS UNTIL CONTRACT SIGNED FROM BOTH PARTIES.

Any request that involve bars, duty-free or catering for passengers to be boarded at base, must be coordinated with SOT.

All communication between euroAtlantic/client must be done in writing, with copy to the Commercial Department.

After final confirmation, the following actions must be taken:

ACMI must be confirmed to Roster, GCM and SOT departments. As soon as crew is assembled, Rosters department will advise crew identification;

Client’s designated handling agent must be informed through standard Flight Notification Message. If no handling agent is indicated, flights shall be attended by euroAtlantic’s handling agent and costs will be recharged to the client. The same applies to airport taxes, fuel and catering.

MTOW charts must be checked for all destination aerodromes;

Flights are to be dispatched according with 2.6) and 2.7). No flight is authorized to depart without confirmation of airport runway slot is approved.

Confirm if iPads are updated and charged as well as mobile phone. After flight departure AIMS and AirNav software must be updated with the ACMI schedule.

15.1 – CATERING/CARGO EQUIPMENT COMPATIBILITY

As per information available from SOT, below is Euroatlantic’s fleet compatibility scheme:

Full/Half trolley

Containers Oven Inserts ULDs Palletes

B772 ACE KSSU Atlas/32 LD2,LD3,LD6

B763 Atlas Atlas Atlas LD2,LD3,LD6, LD7,LD9,LD10, LD11

PMC,PAG,P6P

B763 CSTLO

Atlas KSSU Atlas LD2,LD3,LD6, LD7,LD9,LD10, LD11

PMC,PAG,P6P

B76F N/A Atlas Atlas LD2,LD3,LD6, LD7,LD9,LD10, LD11

PMC,PAG,P6P

B73H Atlas Atlas KSSU sp N/A N/A

15.2 – LONG TERM OPERATIONS

Given the proper planning time, Flight Dispatch will contact the client regarding operational issues such as overflying and landing permits, slots, preferential routing, and alternate selection. Flight Dispatch will send to all concerned stations the “Briefing Instructions for Out-stations Operations” in order to smooth communication between both parties and alert to euroAtlantic operational requirements.




ACMI PROCEDURES

Page 66 OM

PART B

Rev. 14 17-06-2016

Intentionally Blank




FLIGHT DISPATCH

ROUTE STUDIES

16

OM PART B

Page 67

17-06-2016 Rev. 14

16 – ROUTE STUDIES

Route studies and payload analysis are requested by the Commercial through Cost Analysis Department and are to be conducted before scheduling a series of flights. They are prioritized as UUU (within two hours) UU (eight hours) U (seventy two hours). Cost Analysis Department will numerate every individual study - four digits numeric order/year, which is part of file name and inserted on CFP as flight number. The study will always be made in order to obtain the maximum payload available or as requested, based on yearly weather average, If study requires an assessment of operational risk involved and security classification DSP add a prefix “P” to the file name and send it to Ops Engineering with cc for safety, security, fleet chief, pilot chief, flight operations director. Ops Engineering will became in charge to coordinate that study became complete and send it back to DSP Upon completion, such studies shall be sent electronically to the respective mailing list. The study is based on an evaluation of relevant operational factors such as:

Altitude ensuring the safety minimums for all phases of flight - Minimum takeoff and landing altitudes are guaranteed through the procedures for calculations of performance described in "Aeroplane performance and operating limitations” manual and the respective aircraft’s AFM. MTOW tables are used to obtain the maximum take-off weights and landing as described in fields 19 and 23. Enroute minimum altitude is guaranteed after checking fields 36 and 37. If required an escape route is requested to Ops Engineering.

Length, width, and strength of the runway pavement. - Guaranteed by checking fields 20 and 24 If an alert appears PCN must be checked on PCN CALCULATION and if necessary a request to airport/national authorities must be done. Conclusions must be written on field 26.

Radio aids to navigation and lighting – In this item all airport risk analysis is evaluated with same rules describe on 15. Fields 21 and 25 of the cover sheet must be filled with format M9L9W9F9R9C9,

Weather Considerations - Guaranteed by completing fields 8, 15, 16 and 17.

Calculations of fuel consumption - Obtained through the operational flight plan.

Emergency services - Guaranteed by checking origin and destination rows as well enroute alternates table and reflected on fields 21 and 25

Considerations to freeze fuel in long-haul operations, where applicable - Guaranteed by filling in the fields 41 and 42.

ETOPS requirements, if applicable - Guaranteed by preparing the flight plan in accordance with ETOPS rules, when necessary. Check fields 37 and 39 after analyzing the operational flight plan.

Air Traffic Services - Guaranteed by filling fields 39 and 40.

Operations with engine failure - Guaranteed by preparing the flight plan in accordance with ETOPS rules, when necessary. Check fields 36 and 37 after analyzing the operational flight plan.

Depressurization on inhospitable areas - For the purposes of fuel consumption, the operational flight plan contemplates the depressurization on inhospitable areas. Obstacle clearance is guaranteed by checking field 7.




ROUTE STUDIES

Page 68 OM

PART B

Rev. 14 17-06-2016

Classification of special airports - Guaranteed by filling in fields 41 and 42. If airport have, on DSP matrix, a score above 5 a formal approval have to be obtain from Fleet Chief, Chief Pilot or Operations Director by phone and mail. Ops Engineering must record those approvals and send them to OCC.




FLIGHT DISPATCH

ROUTE STUDIES

16

OM PART B

Page 69

17-06-2016 Rev. 14

01

08 10 11

02

04

06

35

38

41

43

45 47

05

07

03

25

26

34 36 37

39

42

24

40

44

46

23

15

31 32 33

09

17

22

27

28

29 30

13 14 12

16

21 20 19 18




ROUTE STUDIES

Page 70 OM

PART B

Rev. 14 17-06-2016

Responsibilities

Responsible Department Fields

Flight Dispatch (DSP) 1 to 33 and 45

Ops Engineering 34 to 38 and 45

Respective Fleet Chief 39 to 40 and 45 *

Chief-Pilot 41 to 42 and 45 *

Safety Manager 43 to 44 *

Flight Operations Director 47 *

* Fleet Chief, Chief Pilot, Safety Manger, Security, Flight Operations Director instead of signed document may send an email referring route study number with comments/decision which Ops Engineering must assure that is attached to route study and sent to OCC before study be sent to Commercial Department or Costs Analysis Department.

Field filling details 01 Date

02 Aircraft’s ICAO code

03 Registration

04 Departure IATA code

05 Departure ICAO code

06 Arrival IATA code

07 Arrival ICAO code

08 Temperature in two-digit format Celsius. Negative temperatures will be preceded by M. Average temperatures for the period of validity of the study can be obtained using the website www.worldclimate.com.

09 Center of Gravity percentage. B767 and B737 with no CG in MTOWs for routes studies

purposes only, for B777 MTOW with CG FWD 25%.

10 Anti-ice OFF configuration is to be selected in MTOWs for routes studies purposes only

11 Optimum Flaps configuration is to be selected in MTOWs for routes studies purposes

only

12 Improved climb configuration is to be selected in MTOWs for routes studies purposes only.

13 Packs OFF configuration is to be selected in MTOWs for routes studies purposes only

14 NIL or ATA number specifying inoperative item, if any.

15 Average winds enroute.

16 Monthly/annual period.

17 Special Weather Considerations - TAF code for weather phenomena, if any.

18 Takeoff runway used for flight plan preparation, indicated by . Runway is to be chosen according with aerodrome’s indication and/or wind predominance. If not using a pair of runways an alert must be included on field 26

19 MTOW limited by structural or maximum performance of the aircraft concerned. The weight is calculated according to the analysis of runway obtained through the website www.flygp.se. For more details about getting the values through the analysis of runway see "Aeroplane Performance and Operating Limitations." CG25% MTOWs are to be used for B777-200 fleet.



http://www.worldclimate.com/

http://www.flygp.se/


FLIGHT DISPATCH

ROUTE STUDIES

16

OM PART B

Page 71

17-06-2016 Rev. 14

20 Maximum taxi weight limited by apron for the type of airplane concerned. Any limitation should be clarified with airport authorities and present to Fleet Chief or Chief Pilot that will formally decide if mentioned limitation is to be considered.

21 Radio-aids and runway lighting includes DSP risk analysis score as stated above.

22 Landing runway used for flight plan preparation, indicated by . Runway is to be chosen according with aerodrome’s indication and/or wind predominance.

23 Maximum landing weight limited by structural or Maximum Performance for the aircraft concerned.

24 Maximum taxi weight limited by apron for the type of airplane concerned. Any limitation should be disregarded for routes studies purposes only. If such is the case, this limitation will be indicated and the Chief Pilot that will formally decide if mentioned limitation is to be considered

25 Radio-aids and runway lighting includes DSP risk analysis score as stated above.

26 Runway relevant operational information.

27 Compliance with Fleet limitations (top right corner).

28 Any observations regarding Fleet limitations (refer to OM A 8.1.2.2.1 e B-DOV-007).

29 Maximum estimated takeoff, taking into consideration any structural/runway limitations.

30 Maximum available payload.

31 Fuel requirements for departure

32 Expected remaining fuel after flight completion

33 Expected flight time

NOTE: COMMERCIAL ROUTE STUDIES ARE CONSIDERED COMPLETE AFTER THIS. THEY MUST INCLUDE A COPY OF THE OPERATIONAL FLIGHT PLAN USED, PREPARED WITH OVERFLYING TAXES ATTACHED. IT MUST BE SENT TO BOTH COMMERCIAL AND COSTS DEPARTMENT. STUDIES WITH ANY TYPE OF LIMITATION WAITING FOR FLEET CHIEF, CHIEF-PILOT, SAFETY MANAGER AND FLIGHT OPERATIONS DIRECTOR DECISION SHALL NOT BE SENT WITHOUT PREVIOUS AUTHORIZATION. NUMBERING OF ROUTE SUDIES MUST KEEP A PREFIX “P” IF THEY NEED FLIGHT OPERATIONS DECISION. OPS ENGINEERING MUST OBTAIN FINAL APROVAL. 34 Checking for the requirements related to one engine failure. At the end of the flight plan

there will be a summary indicating, for each nav point, respective flight level, available flight level after engine failure and GMORA. If GMORA conflicts with expected flight level after an engine failure at a specific point, as indicated in the flight plan, this may indicate that a profile analysis of descent after an engine failure is required. Hence, this particular route study and respective plotting chart should be sent to Ops Engineering for analysis, which will proceed as described in NP-DOV-006. Ops Engineering will inform via email if it is feasible to build an escape route for the route in question. If not, a rerouting will take place and the process will be repeated.




ROUTE STUDIES

Page 72 OM

PART B

Rev. 14 17-06-2016

35 For GMORA above 8000 feet, the route study and respective plotting chart will be sent to Ops Engineering. Ops Engineering will inform via email if it is feasible to build an escape route for the route in question. If not, a rerouting will take place and the process will be repeated.




FLIGHT DISPATCH

ROUTE STUDIES

16

OM PART B

Page 73

17-06-2016 Rev. 14

36+37 For GMORA above 10,000 feet, the oxygen requirements according to EASA Air OPS Part CAT.IDE.A.230, CAT.IDE.A.235 and CAT.IDE.A.240 must be met. The entire fleet is equipped in order to do so. Each plane’s MEL defines the required minimum number of oxygen cylinders and chemical oxygen generators. The required pressure of oxygen cylinders used for PNT is described in OM A 8.8.2.

In the event of depressurization, chemical oxygen generators will determine for how long

certain flight levels can be maintained. Complying with field 34 will guarantee any

remaining oxygen requirements

38 Observations for field (32), (33), (34) and (35)

39 ATS relevant observations.

40 Availability of Radar Approach Control, Radar Control Route Service, standard ATS services and minimum number of radio aids to landing and takeoff. The minimum number of navigational aids is described in OM A 8.1.3 and 8.1.4.

41 Indication that field (42) must be filled if "Aerodrome Categorization for Flight Crew Competence Qualification" is required.




ROUTE STUDIES

Page 74 OM

PART B

Rev. 14 17-06-2016

42 Special Classification of origin and destination airport in accordance with "Aerodrome Categorization for Flight Crew Competence Qualification" of the OM C. Enroute ATS sectors and additional emergency equipment, if such is required by over flown State, is also analyzed.

Note: If EuroAtlantic Airways conducts passenger flights across land areas that have been designated by the state(s) concerned as areas in which search and rescue would be especially difficult, EuroAtlantic shall ensure all passenger aircraft in its fleet utilized for such flights are equipped with signaling devices and life-saving equipment (including, means of sustaining life) in accordance with requirements of the applicable state(s).

43 Risk factor. Should be filled with the value taken from the table contained in chapter 7.6

of "Safety Management Manual", according with its instructions and after consideration of all data collected.

44 Observations for field (43) requesting a detailed Safety or Security Risk Assessment; 45 Flight Dispatcher’s name. 46 Chief-Pilot’s signature. 47 Flight Operations Director signature / approval




FLIGHT DISPATCH

HOSTED GRAFLITE APLICATIONS

17

OM PART B

Page 75

17-06-2016 Rev. 14

17 – HOSTED GRAFLITE APLICATIONS

17.1 – FBOL – FLIGHT BRIEFING SERVICES

All SITA/GRAFLITE manuals and backup to SITA/GRAFLITE are available at:

https://www.flightops.sita.aero

Password: __________

Documentation:

Flight Planning:



https://www.flightops.sita.aero/



Page 76 OM

PART B

Rev. 14 17-06-2016

17.2 – AVIVA – FLIGHT BRIEFING SERVICES

17.2.1 – AVIVA – GENERIC

Configuration parameters are available on AVIVA (MMZ flight planning 3.a3d):

userID: MMLIS01

PASSWORD : _______

Keywords:

Enter: right “Ctrl”

Esc: F3

Go: F1

Select ACTIVE application (e.g. “1” right “Ctrl”




FLIGHT DISPATCH


17

OM PART B

Page 77

17-06-2016 Rev. 14

Password: _______ right “Ctrl”

17.2.2 – AVIVA – NAVDATA

NAVDATA MENU F4

Password: __________





Page 78 OM

PART B

Rev. 14 17-06-2016

Select with “X” right “Ctrl”

F3 – Go back

17.2.3 – AVIVA – BASIC PARAMETERS FOR AIRCRAFT

AIRCRAFT DETAILS F5

F1




FLIGHT DISPATCH


17

OM PART B

Page 79

17-06-2016 Rev. 14

right “Ctrl”

Select with “x” right “Ctrl”





Page 80 OM

PART B

Rev. 14 17-06-2016

Green data are editable. Whenever necessary may be changed:

OWE = MIN ZFWT

ITEM19 = Pay attention with CS-TQU changes with dinghies

CLIMB DEG, CRUISE DEG, DESC DEG and HOLD DEG

FREE FORMAT = change item 18

ITEM 10

