standard operating procedures manualvacanada.org/v6/images/docs/sop.pdf · standard operating...

Standard Operating Procedures Manual

April 2018 www.vacanada.org 0

STANDARD OPERATING PROCEDURES MANUAL

www.vacanada.org



1.0 INTRODUCTION

This document has been put together for the purpose of guiding all members of VAC in their flight duties

and respective roles within the virtual airline. All policies and procedures regarding the virtual airline can be

found in this manual. Flight crew (members) are obliged to follow all procedures mentioned in this

document. Policies and procedures included in this document conform to Canadian Air Regulations (CARs)

and regulations of the VATSIM network. These procedures are not to replace any regulation stated by

CARs or VATSIM, but are used to shape the structure of our organization.

This document will be distributed to all flight crew members, staff members as well as any other parties

concerned. It is the duty of all members to note changes published, indicated by a line in the left margin

within the Standard Operating Procedures (SOP). NOTAMs will be issued temporarily until a revised

publication with the changes has been posted and accessible for reference and printing. It is important to

note that from here on, the term operator will be used in reference to VAC.



PAGE INTENTIONALLY LEFT BLANK



2.0 APPROBATION PAGE OF THE STANDARD OPERATING PROCEDURES

Name of the Operator: VAC

Website: www.vacanada.org

Forum: www.vacanada.org/forum

Headquarters: Montreal Trudeau CYUL

Main Operations Hub: Toronto Pearson CYYZ

This documents describes all Standard Operations Procedures (SOPs) that must be followed by the

operator according to Section 705 of CARs and the VATSIM network regulations. The non-compliance of

SOPs may lead to suspension or termination of a member after an incident has been reviewed. All members

must comply with SOPs at all times.

Michael Chan President & Chief Operating Officer

Bruno Flageol Senior Vice President – Operations

Daniel Desjardins Senior Vice President – Operations

William English Vice President – Systems Operations Control

Arslan Nouar Vice President – Dispatch Operations



3.0 Message from the President & Chief Operating Officer

Dear Members,

A special welcome to you who may be flying with us for the first time. We hope you enjoy your career

with the virtual airline that strives for realism and professionalism by flying to top destinations utilizing the

youngest fleet, from beautiful Canada. Whether you are an aspiring pilot, aviation enthusiast, or just

passing by to see what we offer, thank you for having taken the time to visit us and explore the types of

services we offer you, the prospective virtual pilot.

I am proud to announce that we are continuing our award winning services well beyond the 21st century.

We continue to improve on a daily basis to provide you with a better flight simulator experience. Our latest

major developments have been an upgraded website, new fleet, and myVAC - our exceptional flight

operations system tailored to your personal needs.

Further growth is planned to bring more exciting features and services for our members. Our pilot forum

is a great place to post questions, comments and most of all, the place to share your flight experiences

with fellow VAC pilots. VAC members have access to our myVAC Portal, through which pilots can choose

flights, generate detailed briefing packages, access our fleet section, and maintain their account. Should

you decide to join - a process that is very quick and easy, you will start your VAC career and flights with

ease and enjoyment.

Welcome Aboard.

Michael Chan

President & Chief Operating Officer



4.0 Table of Contents

1.0 Introduction 1

2.0 Approbation Page of the Standard Operating Procedures 3

3.0 Message from the President & Chief Operating Officer 5

4.0 Table of Contents 7

5.0 Modification Process and Distribution List 11

5.1 Modification Process

5.2 myVAC Message Centre

5.3 Distribution List

6.0 Modification List 14

7.0 List of Active Pages 16

8.0 Terms and Conditions 18

9.0 General 23

9.1 Certificate of 705 Operations

9.2 Operations Levels

9.3 Administration

9.4 Functions, Qualifications and Responsibilities

9.5 Nominations

9.6 Rank Structure

9.7 Fleet and Flight Numbers

9.8 Equipment Substitutions and System Wide Flight Numbers

9.9 Transfer Hours

9.10 Flight Acceleration




9.11 VAC Forums

9.12 Discord

10.0 Flight Schedule and Bidding Process 41

10.1 Bidding Procedures

11.0 Pre-Flight and Flight Operations 45

11.1 Use of Package

11.2 Simbrief

11.3 Routes

11.4 Fuel Requirements

11.5 Weather

11.6 Minimas

11.7 Online Events

11.8 Special Assignments

12.0 VACARS Operations and Guide 54

12.1 Downloading VACARS

12.2 VACARS Procedures

12.3 Manual PIREPS

13.0 Flight Dispatch Operations 59

13.1 Standard Operating Procedures

13.2 Bulletins and Memos

13.3 Duties and Responsibilities

13.4 Ways of Communication




13.5 Dispatcher Briefing

13.6 Conflicts and Resolution

13.7 Useful Links

13.0 Contact Us 64

13.1 General Inquiry

13.2 Executive Team Directory



5.0 Modification Process and Distribution List

5.1 Modification Process

5.1.1 Modification to this document are made by the Senior Vice President – Flight Operations and Senior

Vice President – Human Resources when deemed necessary. After approval, the document will be

distributed by the holder of the document. Any modified page must hold the modification number and date

of the last modification. They will be indicated by a black line on the left hand margin of the page. Any time

a modification is made, a copy must be sent to members, including the instructions pertinent to the changes.

5.1.2 The instructions for the modification of the document must include a list of pages to be deleted, a list

of pages to be inserted and a modification justification. The modified text will be identified with a black line

on the left hand margin. If a manual or modifications is removed, instructions to destroy the original must

be sent to all holders. Once a modification is issued, the holder must make an entry in the modification table

found in this section.

5.2 myVAC Message Centre

5.2.1 Any modifications to Standard Operating Procedures or operational news/bulletins will be announced

via the myVAC Message Center to comply with the modification process described above.

5.2.2 It is the members’ responsibility to acknowledge and comply with each and every bulletin published

via the myVAC Message Center.



5.3 Distribution List

5.3.1 The Senior Vice President – Flight Operations must hold a list of all holders of the Standard Operations

Manual and is responsible for the distribution of the manual according to the list.

5.3.2 The manual will be available to any third party as deemed appropriate by the President & Chief

Operating Officer and Senior Vice President – Flight Operations.

5.3.3 All copies of the Standard Operations Procedures Manual are property of VAC and must only be

used for operations at VAC. Upon termination, members must immediately return their copy of the manual

to the Senior Vice President – Flight Operations or their immediate supervisor.

5.3.4 The following list include the holders of the manual and are responsible to keep the manual up to date

following modifications:

Chairman & Chief Executive Officer

President & Chief Operating Officer

Executive Vice President & Chief Information Officer

Senior Vice President – Flight Operations

Senior Vice President – Human Resources

Vice President – System Operations Control

Vice President – Dispatch Operations

Vice President – Online Events

Vice President – Systems Development

Director(s) – Fleet Maintenance

Director(s) – YYZ/YUL/YVR/YWG Operations

Flight Dispatchers

Pilots



6.0 Modification List

No. of Modification Date of Modification Date of Inscription Insertion Written

1 15 Jul 2016 - Bruno Flageol

2 07 Feb 2017 - Michael Chan

3 23 Nov 2017 - Michael Chan

4 02 Feb 2018 - William English

5 10 Apr 2018 - Michael Chan

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21



7.0 List of Active Pages

Page Revision Date Page Revision Date

1 Original 01 May 2016 22 Original 01 May 2016



4 Ammendment 1 15 Jul 2016 25 Original 01 May 2016




8 Ammendment 1 15 Jul 2016 29 Original 01 May 2016




12 Original 01 May 2016 33 Ammendment 1 07 Feb 2017



15 Original 01 May 2016 36 Ammendment 1 10 Apr 2018

16 Original 01 May 2016 37

17 Ammendment 1 01 May 2016 38

18 Ammendment 1 01 May 2016 39






8.0 Terms and Conditions

8.1 Terms and Conditions

8.11 As a member of VAC, the member agrees to be bound and abide by the “VAC – Terms & Conditions”.

These “Policies” will be posted on the website. Any subsequent changes to the policies may also be emailed

to all members. Violations of the policies may result in a probationary period, a temporary suspension, or

termination of the members account.

8.12 The VAC username and password provided to you is your exclusive VAC membership identification.

You may not give permission or knowingly allow your username or password to be used by anyone else.

8.13 Members must use their full name when registering. Incomplete, incorrect or misleading information

may result in account termination.

8.14 You may register for and hold only one VAC registration.

8.15 All members must provide a valid email address. If your email address changes, you can use the

online form under the HR tab of myVAC to modify your email address in the VAC database. The form will

ask you to select your name, password and new email address. If your password is correct, the database

will be updated and a confirmation email will be sent to your new email address. You can find this feature

in your logbook. If you require assistance, please contact the Senior Vice President - Human Resources.

Accounts with invalid email addresses will be removed at management's discretion.

8.16 If you have forgotten your password, please fill in the online form under the HR tab of myVAC to

request your password. The form will ask you to provide your Pilot ID, first name, last name and email

address. If the information matches the VAC database, an email will be sent to your email address (one on

file) with your password. If you require assistance, please contact the Senior Vice President - Human

Resources.



8.0 Terms and Conditions (continued)

8.17 If you want to modify your password, an online form under the HR tab of myVAC must be filled out.

The form will ask you to select your name, enter your current password and new password. If the information

provided matches the VAC database, your password will be updated. If you require assistance, please

contact the Senior Vice President - Human Resources

8.18 All pilots must fly at least one flight within the first 14 days of successful completion of registration.

You may request a leave of absence of up to 6 months; however, active pilots must file a flight every 60

days. Active Pilots who do not comply with this rule will be automatically removed from the roster unless

they request a Leave of Absence (LOA). You can use this feature via your logbook. If you require

assistance, please contact the Senior Vice President - Human Resources.

8.19 All flights must represent a valid VAC flight as assigned by the scheduling system on the website.

Flights not in this system will be rejected and removed after filing.

8.20 Flight Reports will be added to the database and be sent to your Base Director for review. Pilots who

submit false flight reports may have their entire log wiped clean, be under suspended status, or terminated.

Any pilots who fly routes that are not authorized will have their flight reports rejected.

8.21 Each pilot is only permitted to submit a flight report for the type of aircraft for which they has been

certified. Any flight reports filed for uncertified aircraft will be rejected, and repeated offences may lead to

the pilot’s logbook wiped clean, be under suspended status or even termination of membership.

8.22 All new members must read and comply with the Standard Operating Procedures (SOPs).

8.23 VAC registration is open for membership to all individuals thirteen (13) years and older. Individuals

younger than 13 must provide written consent from a parent or guardian. Accounts of individuals under 13

years of age without parental consent will be immediately suspended until such consent is provided.




8.24 Membership is open to all individuals regardless of race, color, religion, creed, sex, sexual orientation,

gender identity, national origin, ancestry, veteran status, disability, genetic information, military service, or

other protected status.

8.25 When flying online (ex. VATSIM Network), it is a requirement to use the flight number assigned for the

flight. Ex: ACA868 or JZA8328 and indicate in the Pilot's Remark that you are a member of VAC and website

address: www.vacanada.org.

8.26 VAC is a non-profit organization and does not charge any fees to apply for or to retain membership in

the organization. No member of VAC may request money or charge fees as a prerequisite to offering any

assistance or product. In addition, no member is permitted to resell or make any commercial or non-

commercial use of the VAC website or forums.

8.27 The prohibitions set forth in this paragraph expressly include any and all sales and/or solicitations of

money, goods and services no matter for what purpose, person, group or cause, without limitation.

Members violating these rules qwill be subject to immediate termination from VAC.

8.28 VAC management reserves the right to temporarily suspend or terminate an individual's membership

from the organization without notification if certain rules have been violated. The member may appeal the

suspension or termination to the Executive Committee, whose decision shall be final. The member will have

the right to review the written report submitted by the manager, and provide a written response to

management within 30 days.

8.29 The general code of conduct reflects on the way VAC expects members to behave as a member of

the organization. Repeated failure to follow the code of conduct may result in suspension, and eventually

termination of the members account.




8.30 Members who are new to the hobby or are otherwise unfamiliar with virtual airlines should well inform

themselves by downloading the educational material provided on the VAC website, joining the forum, asking

questions of management, or otherwise researching the information on their own. This is mandatory before

representing VAC on any third party website such as VATSIM.

8.31 Members should, at all times, be courteous and respectful to one another. Bashing of other members

is strictly prohibited. Threatening or harassing any member will result in immediate suspension or

termination of the member’s account.

8.32 Members represent the VAC community at all times when visiting other sites on the internet. Members

should not undertake any action to bring harm to the reputation of VAC, including, but not limited to

misrepresenting yourself to another organization, breaking the rules and guidelines of another organization,

or making derogatory statements about VAC. Violators will have their membership immediately revoked.



9.0 General

9.1.0 Certificate of 705 Operations

9.1.1 The certificate of operations, as well as all specifications of operations, delivered to VAC are

reproduced and annexed in this manual. It informs the personnel of the authorized operations, restrictions

and any specification deemed necessary.

9.1.2 To facilitate the modification of this document in the event of a modification or production of a new

certificate of operation, the following process will be applied.

9.1.3 Upon the reception of the certificate of operation, the operator shall inform all holders of this manual

and produce copies to be inserted in the manual to reflect the change of certificate.

9.2.0 Operations Level



9.3.0 Administration

Holder of Certificate: VAC

Chairman & Chief Executive Officer: Harvey Hicks

President & Chief Operating Officer Michael Chan

Executive Vice President & Chief Information Officer: - Leave of Absence -

Senior Vice President – Operations Bruno Flageol

Senior Vice President – Human Resources Daniel Desjardins

Vice President – Systems Operations Control William English

Vice President – Flight Dispatch Operations Arslan Nouar

Vice President – Online Events Jordan Dawe

Vice President – Systems Development Cory Blair

Director – Montreal Operations Lukas Kusiak

Director – Toronto Operations Matthew Fernandes

Director – Vancouver Operations Michel Montreuil

Director – Winnipeg Operations Jean-Francois Mayer

Director – Fleet Maintenance Prepar3D Liam McKeown

Director – Fleet Maintenance XPlane Kevin Xie

Flight Dispatcher Jason Rivard

Flight Dispatcher Peter Maria

Flight Dispatcher Bradley Ogilvie

Flight Dispatcher Grant Sproson

Flight Dispatcher Frans Van Zantbeek

Flight Dispatcher Domonick Sandifer



9.4.0 Functions, Qualifications and Responsibilities

9.4.1 Chairman & Chief Executive Officer

The Chairman & Chief Executive Officer is responsible for the formation of the Executive team, establishing

the organization's policy & strategic direction, and overseeing the Executive team's work. This includes the

development of the organization's vision and mission to develop the leading virtual airline.

9.4.2 President & Chief Operating Officer

Directly reporting to the Chairman and Chief Executive Officer, the President & Chief Operating Officer is

responsible for communicating and implementing the organization's vision, mission and overall direction.

With the assistance of senior staff, the President & Chief Operating Officer formulates and implements

strategic plans that guide the organization. Overseeing and evaluating the success of the organization, the

President is responsible for the forming, staffing, leading and managing of VAC. Central focus is on

maintaining awareness of both external and internal competitive landscape, opportunities for expansion,

customer market, new community developments and standards.

9.4.3 Executive Vice President & Chief Information Officer

Directly reporting to the President & Chief Operating Officer, the Executive Vice President & Chief

Information Officer is the primary programmer of the VAC website, myVAC portal, automation as well as

the PHP (Hypertext Preprocessor) coding runs efficiently and effectively for our members. The Executive

Vice President & Chief Information Officer is responsible for executing the support of daily technical needs

of our members and implementing new technology as a result of organizational demand.



9.4.0 Functions, Qualifications and Responsibilities (continued)

9.4.4 Senior Vice President - Operations

Directly reporting to the President & Chief Operating Officer, the Senior Vice President - Operations directs

and controls the activities of daily operations of VAC. Performance standards against operating plans are

reviewed as well as matters requiring a decision. Recommended objectives in each area of operations are

made by developing short and long-term plans in addition to coordinating with other departments of the

organization by establishing operational programs.

9.4.5 Senior Vice President - Human Resources

Directly reporting to Executive Vice President & Chief Information Officer, the Senior Vice President -

Human Resources creates the organization's recruitment and membership plan and overseas the training

and organizational development plan to meet the needs of our members. Recommendations and review of

the organizational structure and staffing levels are made monthly to ensure they accomplish organization

goals and objectives. The Senior Vice President – Human Resources establishes short and long term

departmental goals in improving membership levels.

9.4.6 Vice President – System Operations Control

Directly reporting to the Senior Vice President – Flight Operations, the Senior Director of System Operations

Control ensures the VAC flight schedules are kept up to date including, but not limited to Scheduled

departures, Charters and Reposition / Ferry Flights. In addition to assisting the Vice President – Online

Events in the assignment of flights prior to any VAC VATSIM related events. The Vice President – System

Operations Control is the primary contact for schedule concerns and flight requests.




9.4.7 Vice President – Flight Dispatch Operations

Directly reporting to the Senior Vice President – Operations, the Vice President – Flight Dispatch Operations

provides day to day administrative, function and technical directions to Flight Dispatch. Responsible for the

development, implementation and enforcement of Flight Dispatch functions and maintain efficient standard

of operation. Ensures Flight Dispatchers are provided with the suitable knowledge, training and all

necessary material required to perform their duties. Liaise with Executives and assist on development and

improvement of Flight Operations Standards as needed. Responsible for maintaining and amending

Dispatch manuals.

9.4.8 Vice President – Online Events

Directly reporting to the Senior Vice President – Flight Operations, the Director of Online Events is

responsible for the creation and promotion of “Flying Night in Canada” and VATSIM events. Primary liaison

with VATSIM and Virtual Airline groups utilizing the VATSIM network. Ensures membership receives the

latest news and event information through the website calendar as well as the forum. Actively assists

members through various means of social media.

9.4.9 Director(s) – YYZ, YUL, YVR, YWG Operations

Directly reporting to the Senior Vice President – Human Resources, Hub Directors are responsible for

leading flight operations at our 4 bases in YYZ, YUL, YVR and YWG. They ensure all aspects of the base

are functioning within VAC regulations and monitor compliance amongst its members. Hub Directors are

also responsible to provide direction and guidance to members, support for other departments, as well as

supervise and maintain the accuracy of the flight report database.




9.4.10 Director(s) – Fleet Maintenance

Directly reporting to the Vice President – Flight Operations, the Director of Fleet Maintenance ensures the

highest quality fleet standards are met based on revisions of new payware aircraft models and livery

repaints for Prepar3D, Microsoft Flight Simulator X and XPlane. The Director of Fleet Maintenance is the

primary contact for aircraft support through various communication channels such as the forum, contact

page or e-mail.

9.4.11 Flight Dispatchers

Directly reporting to the Vice President – Flight Dispatch Operations, Flight dispatchers are to provide the

pilot in command with their pre-flight planning, departure, en-route and arrival as needed with any

information required for flight safety and efficiency. Support on Discord application and member forums.



9.5.0 Nominations

9.5.1 Any members acting for the administration of VAC must be nominated by the President & Chief

Operating Officer and a copy of the nomination must be compiled in the staff's file.

The nomination must describe:

- The identification of the nominee and the recommending member.

- The position the candidate has been nominated for.

- The name of their direct supervisor.

- Any applicable restrictions.

9.5.2 The nominee must acknowledge the present manual and by writing the new responsibilities

associated with their new posting.

9.6.0 Rank Structure

Rank Uniform Minimum Hours Required

Regional First Officer

0 – 10 Hours

Regional Captain

10 – 20 Hours

Narrow-body First Officer

20 – 40 Hours

Narrow-body Captain

40 – 65 Hours

Wide-body Relief Pilot

65 – 120 Hours

Wide-body First Officer

120 – 300 Hours

Wide-body Captain

300 – 800 Hours

Senior Captain

800 + Hours



9.7.0 Fleet

9.7.1 Pilots are only allowed to fly the aircraft category that has been authorized as per the company ranking

scale. No pilot shall complete or file a flight report with an erroneous aircraft type.

9.7.2 The fleet has been devised under three (3) categories which regroups different aircraft types.

Regional

Narrow-body

Wide-body

9.7.3 Only P3D, FSX and XPlane aircraft textures for Payware aircraft models in current fleet selection are offered.

9.7.4 Current aircraft livery and models not listed for download may be obtained from third party websites.

9.7.5 The regional category regroups six (6) different types of aircraft from three (3) different regional

operators under Express.

Regional

Aircraft Type Code Operator

Beechcraft 1900D BEH Express

Bombardier Dash8-100/300 DH1/DH3 Express

Bombardier Dash8-Q400 DH4 Express

Bombardier CRJ100/200ER CRJ Express

Bombardier CRJ900 CR9 Express

Embraer 175 E75 Express

9.7.6 To hold the privilege of the Regional category, the flight crew member must hold the rank of First

Officer - Regional. There are no minimum requirements for this category.



9.7.0 Fleet (continued)

9.7.7 The narrow body category regroups five (5) different aircraft types from three (3) different operators

under Mainline, Leisure and Express.

Narrow-body


Embraer 190 E90 Mainline

Airbus A319 319 Mainline; Leisure

Airbus A320 320 Mainline

Airbus A321 321 Mainline; Leisure

Boeing 737 Max 8 7M8 Mainline

9.7.8 To hold the privilege of the narrow body category, the flight crew member must hold the minimum

rank of First Officer – Narrow-body. A minimum total flight time of 20 hours is required. Flight crew with this

privilege also hold the privilege of the regional category for their bidding.



9.7.0 Fleet (continued)

9.7.9 The wide-body category regroups six (6) different aircraft types, under Mainline and Leisure.

Wide-body


Boeing 767-300ER 763 Mainline; Leisure

Boeing 787-8 788 Mainline

Boeing 787-9 789 Mainline

Airbus A330-300 333 Mainline

Boeing 777-200LR 77L Mainline

Boeing 777-300ER 77W Mainline

9.7.10 To hold the privilege of the wide body category, the flight crew member must hold the minimal rank

of Relief Pilot. A minimum total flight time of 65 hours is required. Flight crew with this privilege also hold

the privilege of the narrow-body and regional category for their bidding.



9.8.0 Equipment Substitution and System-Wide Flight Numbers

9.8.1 In order to simulate real world procedures, equipment changes are permitted on some flights. We

encourage our members to follow real world equipment changes which can be referenced at

www.flightaware.com.

9.8.2 Flight crew are only authorized to change equipment on which they hold the privilege.

9.8.3 Equipment changes can only be authorized within the same air operator. Aircrafts operated by

Mainline cannot be changed with aircrafts operated by Leisure or Express flights.

9.8.4 Equipment changes will only be authorized if done within the specified equipment in the table below.

All crew members must follow these restrictions at all times and cannot make any equipment changes not

within the optional equipment list.

9.8.5 It is important to note that exceptions may be made to the following standards following real world

operations. For flight requests, feel free to email the appropriate Hub Operations Director, Vice President

- System Operations Control, or Vice President – Flight Dispatch Operations.



9.8.0 Equipment Substitution and System-Wide Flight Numbers (continued)

EXPRESS

Scheduled Equipment Equipment Substitution

BEH (Express – EVS) No Equipment Substitution

DH1 (Express – JZA) DH3, DH4

DH3 (Express – JZA) DH1, DH4

DH4 (Express – JZA) CRJ, CR9

CRJ (Express – JZA) DH4, CR9

CR9 (Express – JZA) CRJ, DH4

BEH (Express – GGN) CRJ (select pre-approved YYZ routes only)

CRJ (Express – GGN) No Equipment Substitution

E75 (Express – SKV) No Equipment Substitution

LEISURE


319 321

321 319

763 No Equipment Substitution




MAINLINE


E90 319, 320, 321, 7M8 (All Routes)

333, 763, 788, 789 (Pre-Approved Domestic Only)

319 E90 (Non-ETOPS / Non Caribbean routes only)

320, 321, 7M8 (All Routes) 333, 763, 788, 789 (Pre-Approved Domestic Only)





763 333, 788, 789, 77L, 77W

333 763, 788, 789, 77L, 77W

788 333, 763, 789, 77L, 77W

789 333, 763, 788, 77L, 77W

77L 77W

77W 77L

9.8.6 It is important for members to recognize which flight numbers and callsigns should be used when

flying online at VATSIM.

9.8.7 When flying online using your carrier-specific ICAO callsign and flight number, please remember to

indicate in the remarks section of your flight plan you are representing VAC.




9.8.1 Many members have questions about real world procedures when operating Express - Jazz 8XXX

flight numbers. Although the flight number may be 8863, however when you log into VATSIM, you drop the

first zero. Therefore your ATC callsign will be JZA863. Same goes for all JZA8XXX flight numbers, real-

world procedure is to drop the first 8. However, if flying YUL-YTZ operations using JZA7951, you log in

using the full callsign and your ATC callsign will also be JZA7951

Flight Number Carrier & ICAO Callsign

0001 – 1599 Mainline – ACA / AC

1600 – 1999 Leisure – ROU / RV

2000 – 2199 Mainline / Leisure – Extra Sections (Callsigns Above)

7000 – 7199 Mainline / Leisure / Express – Positioning / Ferry

Charter Flights

7200 – 7450 Express – GGN / ZX

7500 – 7749 Express – SKV / RS

7750 – 7809 Express – EVS / 8K

7950 – 7980 Express – JZA / QK YUL-YT-YUL

8001 – 8999 (001-999 while online as per above)

Express – JZA / QK



9.90 Transfer Hours

9.9.1 A maximum of 50 flight hours may be transferred from another virtual airline or VATSIM hours with

proof of flight hours.

9.9.2 Member must provide a visible website link (not password protected) or screenshot from a third party

profile indicating flight hours during the registration process or through e-mail to the Hub Director.

9.9.3 If the member has hours incurred from a previously registered VAC account, please indicate this

during registration or by e-mail to the Hub Director. A member of the Executive Team will review and credit

full hours if applicable.

9.10.0 Flight Acceleration

9.10.1 Flight acceleration is strictly prohibited. Members found using flight acceleration will be

automatically placed under suspension by an Executive Team member. Repeated offences will result in

termination of member account.



9.11.0 VAC Forums

9.11.1 The VAC Forums is pilot central where our members can ask questions, post screenshots, view

online events and most importantly share their flight simulation/aviation experiences.

9.11.2 When you register an account with an active VAC ID, you are automatically given access to our pilot

forums. A separate login with the same VAC credentials will be required to gain access to the forums.



9.12.0 Discord

9.12.1 Discord is a multi-platform communication application and is completely free. It can be used on your

computer running on PC, Mac, Linux or mobile devices running Android and iOS. For members using

Discord on your mobile devices, please ensure you are on a WIFI network when using Voice Channels to

prevent data overage charges from your service provider.

Discord Download Information:

Computer: https://discordapp.com/download

Mobile Devices: Android (Google Play), Apple (App Store)

Channel: https://discord.gg/bPCjrjq

9.12.2 Once you have registered, as per Standard Operating Procedures - your nickname must coincide

with your VAC ID. For example: "VAC005 - Daniel Desjardins" This must be changed within 24 hours of

registration and is enforced.

9.12.3 Member forums at www.vacanada.org/forum continue to be your primary source for updates and

trip report screenshots at VAC.

https://discordapp.com/download



10.0 Flight Schedule and Bidding System

10.1.0 Bidding Procedure

10.1.1 Before each flight, crew members must bid their flight schedule in order to have access to their flight

in the VACARS system. To access the bidding system, you must login through the myVAC portal using

your VAC ID and password.

10.1.2 Under the flight bid section, you will have access to the update flight schedule. Search tools will

assist you to find flights by departure airport, arrival airport, specific route, aircraft type, or specific operators.



10.1.0 Bidding Procedure (Continued)

10.1.3 Once the flight crew has selected a flight, a confirmation page will appear to verify the selected flight,

aircraft type and passenger load. When confirmed, the flight will automatically be added to the crew's

schedule under the Flight Ops section.

10.1.4 Flight crews are allowed to substitute equipment within the procedures indicated in Section 9.8.0 of

the SOP manual.

10.1.5 As specified in Section 9.8.2 of the SOP Manual, flight crew are only authorized to bid flights within

their privileged aircraft category. Any flight conducted under an unauthorized category will result in punitive

measures by the Operations department.

10.1.6 Schedules may also be awarded through the Pairing Request feature. This unique option allows

pilots to bid for a particular pairing of choice.



10.1.0 Bidding Procedure (Continued)

10.1.7 Based on the parameters provided, myVAC automatically generates a flight schedule.

10.1.8 Should you wish to process the flight assignment, click “Add flights to schedule” and “Accept” to

Flight Assignments section of myVAC.

10.1.9 Selected pairing will automatically be added to the Flight Assignment section of myVAC.



11.0 Pre-Flight and Flight Operations

11.1.0 Use of Briefing Package

11.1.1 Briefing packages are available and should be used for flight planning. It is important to remember

that these packages are for simulation only and should never be used for real world operations.

Packages can be found under assigned flights in your myVAC portal. You must have a SimBrief Account

(separate account) to generate the flight plan package.



11.2.0 SimBrief

11.2.1 SimBrief requires an independent username and password from the myVAC portal. For your first

visit, you will need to create a new account in order to access your flight briefing. Visit www.simbrief.com

and follow onscreen instructions before generating your flight plan package through myVAC.

11.3.0 Routes

11.3.1 When you are ready to consult your briefing package, you will be asked for your flight route if no

route has been previously entered in the system. To find the actual route for your flight, you may use

www.flightaware.com. You may enter your new route if it has changed from our database.

11.3.2 Pilots who fly online are encouraged to use the actual routes to respect ATC procedures on the

VATSIM network.

11.3.3 Direct GPS routes will not be accepted. If no FMC is on board for RNAV routes, load the route in

the Flight Simulator GPS via our downloadable routes or by manual entry.

11.3.4 Traditional navigation using airways, VOR to VOR for example, are accepted.

11.3.5 It is not a requirement that you acquire the most recent AIRAC for your FMC/FMS systems, but we

do strongly suggest the latest AIRAC for flight operations.



11.4.0 Fuel Requirements

11.4.1 An aircraft operated in IFR flight shall carry an amount of fuel that is sufficient to allow the aircraft:

(i) where an alternate aerodrome is specified in the flight plan or flight itinerary, to fly to and execute an approach and a missed approach at the destination aerodrome, to fly to and land at the alternate aerodrome and then to fly for a period of 30 minutes or

(ii) where an alternate aerodrome is not specified in the flight plan or flight itinerary, to fly to and execute an approach and a missed approach at the destination aerodrome and then to fly for a period of 30 minutes.

11.4.2 Every aircraft shall carry an amount of fuel that is sufficient to provide for:

(a) taxiing and foreseeable delays prior to take-off;

(b) meteorological conditions;

(c) foreseeable air traffic routings and traffic delays;

(d) landing at a suitable aerodrome in the event of loss of cabin pressurization or, in the case of a multi-engine aircraft, failure of any engine, at the most critical point during the flight; and

(e) any other foreseeable conditions that could delay the landing of the aircraft.

11.4.3 Even though the briefing packages include the amount of fuel required for the flight, it is the flight

crew's responsibility to ensure that sufficient fuel has been boarded.

11.5.0 Weather

11.5.1 Your generated briefing package will include the current weather (METARs) as well as all the valid

TAFs for your departure airport, arrival airport and alternate airport(s).



11.5.0 Weather (continued)

11.5.2 It is the Pilot-in-Command’s (PIC) responsibility to ensure that all weather information are accurate

and valid. The PIC must be aware of all the active SIGMETs and AIRMETs affecting the flight

11.5.3 Pilots are encouraged to publish any PIREPs on the Fin to Fin messaging system within VACARS.

PIREP should be in standard format, but we do accept plain language to help our unfamiliar users. PIREPs

will be useful for everyone.

11.5.4 More current weather information can be found at www.navcanada.com

11.6.0 Minimas

11.6.1 Unless otherwise authorized by the appropriate ATC unit, the Pilot-In-Command (PIC) of an IFR

aircraft shall, when conducting an approach to an aerodrome or a runway, ensure that the approach is

made in accordance with the instrument approach procedure.

11.6.2 No PIC of an IFR aircraft shall commence an instrument approach procedure unless the aircraft

altimeter is set to an altimeter setting that is usable at the aerodrome where the approach is to be

conducted.

11.6.3 No PIC of an IFR aircraft shall conduct an instrument approach procedure except in accordance with

the minima specified in the Canada Air Pilot or the route and approach inventory.



11.6.0 Minimas (Continued)

11.6.4 No Pilot-In-Command (PIC) of an IFR aircraft shall, unless the required visual reference necessary

to continue the approach to land has been established:

i) In the case of a CAT I or CAT II precision approach, continue to the final approach descent below

the decision height.

ii) In the case of a non-precision approach, descend below the minimum descent altitude.

11.6.5 Where the PIC of an IFR aircraft conduction an instrument approach does not establish the required

visual reference referred to in subsection 10.6.4 the PIC shall initiate a missed approach procedure:

i) In the case of a CAT I or CAT II precision approach, at decision height; and

ii) In the case of a non-precision approach, at the missed approach point.



11.7.0 Online Events

11.7.1 Flight Crew bidding for events will follow the same procedure as describe in section 10.1.0 of the

SOP manual. Events will be announced periodically throughout the year with specific information regarding

the departure airport(s), arrival airport(s) and/or specific routings.

11.7.2 All flight crew members bidding and acting as Pilot-In-Command (PIC) or Second in Command (SIC)

for a flight on the VATSIM network are obliged to follow all specified regulations and instructions under the

authority of VAC, the VATSIM network and any third party present.

11.7.3 As part of our agreement conditions with VATSIM while using their network, it is mandatory that all

flights begin with a real world callsign (ex. ACAxxxx, JZAxxxx, etc). The pilot must also state in the

Remarks section of the flight plan: “Operated by VAC | www.vacanada.org” in the textbox field when filing

a flight plan. Failure to comply will result in a reminder from the Executive Team.



11.7.0 Online Events (continued)

11.7.4 Pilots participating in online events do not have aircraft type rating restrictions when flying

on the VATSIM Network. However the aircraft type must be within current VAC fleet.

11.7.5 We do require each member participating to include the following in the Remarks section of your

Flight Plan when connected to VATSIM

//Operated by VAC | www.vacanada.org //

11.7.6 Special Online Events not on the VAC schedule may be granted provided the following information

is sent to your Hub Director for approval. The e-mail must also indicate which event you will be

participating.

Event Name:

Pilot Name:

Employee Number:

Base:

Flight Number: ACA/JAZ/SKY/ROU/GGN + last 4 digits of your employee number

Date:

From (IATA):

To (IATA):

Departure Time (local):

Arrival Time (local):

Equipment Type:



11.7.0 Online Events (continued)

11.7.7 Pilots are required to comply with the following conditions when flying on the VATSIM network.

More information on the VATSIM Network can be found at www.vatsim.net

All online flights are recorded with VACARS after online event assignment has been approved.

All group flight events are flown on the VATSIM network.

Ensure you have all charts available for your flight.

Members must comply with all applicable VATSIM policies and procedures. This includes a

professional conduct with VATSIM air traffic controllers and supervisors.

Pushback from gate is at own discretion unless otherwise advised by online ATC.

Takeoff between aircraft when no ATC is available: 2 minutes for narrow-body and 3 minutes for

wide-body for aircraft separation.

11.8.0 Special Assignment

11.8.1 Special Assignments may be authorized through e-mail by the Hub Director or the Administration

under special circumstances such as real world special event or fly-ins organized by VAC. These

assignments will appear directly in the crew's schedule once assigned by the supervising authority.

11.8.2 Pilots participating in online events not have aircraft type rating restrictions when flying on the

VATSIM Network. However the aircraft type must be within current VAC fleet.

11.8.3 We require each member participating to include the following in the Remarks section of your

Flight Plan when connected to VATSIM:

//Operated by VAC | www.vacanada.org //



12.0 VACARS Operations and Guide

12.1.0 Downloading VACARS

12.1.1 In order to have access to the VACARS system, you must first log on the myVAC portal using your

employee ID and password.

12.1.2 Once you have logged on, you will be able to find the VACARS application under the ‘Files’ tab.

VACARS2 runs on P3D, XPlane and FSX platforms. Download the applicable UIPC for your system.



12.1.0 Downloading VACARS (continued)

12.1.3 To install, you must carefully read the onscreen instructions and make sure the system is installed

in your flight simulator main folder.

12.1.4 For any questions concerning the installation, please refer to the crew forum at

www.vacanada.org/forum for further assistance.

12.2.0 VACARS Procedures

12.2.1 The Pilot-In-Command must launch VACARS at the departure gate prior to pushback. The

flight must also end with the aircraft parked at the arrival gate. Failure to comply will result in temporary

suspension and may lead to termination.

12.2.2 The VACARS system works in conjunction with the myVAC system. To initialize a flight in the

preflight page, you must already bid a flight using the myVAC system. The system status is displayed in

the lower right hand corner of the VACARS system. Only when the status is showing "SYSTEM RUNNING"

are your departure/arrival times being tracked and transmitted to your logbook.

12.2.3 Pilots shall load Flight Simulator and double click on the VACARS shortcut on the desktop to launch

the system (the order they are loaded in should not matter). At this point, the VACARS status should indicate

"FS LINK FAILED" if you are still on the FS create a flight screen.

12.2.4 Once you actually start a flight by clicking the "Fly Now!" button, the "FS LINK FAILED" should

change to read "NOT INITIALIZED" as the VACARS system connects to your simulator.

12.2.5 If the status does not change within 30 seconds and still shows "FS LINK FAILED" you have likely

not registered VACARS with the aircraft you have loaded and should re-run the CONFIGURE VACARS

tool (can be run via the Start Menu/VACARS folder)



12.2.0 VACARS Procedures (Continued)

12.2.6 The system status updates once every 30 seconds, so it might not update immediately after you

click "Fly Now!" Give it 30 seconds and check it again to make sure it successfully connects to FS.

12.2.7 Select the PREFLIGHT page and enter all the data matching the flight bid.

EX: VAC8 HKG-YVR 77L, PILOT ID, Password.

12.2.8 If the initialization is successful, the system will show "VAC8 INITIALIZED." The system status

should also update to show "SYSTEM RUNNING" within 30 seconds.

12.2.9 The pilot can now fly the flight normally. There is no requirement to run FS in windowed mode unless

you want to bring up the VACARS system during the flight to make weather requests or use the message

system.



12.2.0 VACARS Procedures (Continued)

12.2.10 The VACARS system MUST remain open (it can be minimized but NOT closed) for your

departure / arrival times to be transmitted. If you close it by mistake, simply restart the VACARS program

and it should remember your flight data (the SYSTEM RUNNING status should remain).

12.2.11 When the pilot arrives at the gate and wishes to end the flight, signal this to the VACARS system

by setting the parking brakes and opening the main exit (Shift + E by default). Once this is done, within 30

seconds the VACARS system should file the PIREP and display “Report Filed”.

12.2.12 Never close VACARS or your flight simulator until the system displayed “Report Filed”, otherwise

your report might be lose and a manual PIREP will be necessary.

12.3.0 Manual Pireps

12.3.1 You may file your flight after completion using myVAC portal in case there is an issue with the

VACARS system. In order to do so, you must log on to your portal using your employee ID and password.

Under “Flight Ops”, you can chose to file your flight by clicking on the “File” button with the corresponding

flight.

12.3.2 Manual filing is accepted, but limited to two (2) flights per month.

i) Manual filing is considered a backup system only.

ii) Manual reports are approved by the Director – Hub Operations

12.3.3 In order to minimize false reports, all manual flight reports will be reviewed by the operations

department.



13.0 Flight Dispatch Operations

13.1 Standard Operating Procedures

13.1.1 Flight Dispatch department have been implemented as a new service to help the Pilot In

Command (PIC) in performing his flight more efficiently and a big step towards real life Flight Operations.

13.1.2 Flight Dispatch SOP has been produced as a new guidance material to guide Flight Dispatchers

on how to perform their duty and understanding their duties and responsibilities.

13.2 Bulletins and Memos

13.2.1 At anytime there is an immediate need to amend the manual a bulletin will be issued under the

authority of the Senior Vice President Flight Operations or the Vice President Dispatch Operations, until

the updated manual will be released.

13.3 Duties and Responsibilities

13.3.1 Vice President – Dispatch Operations Functions

Provide day to day administrative, functional and technical directions to Flight Dispatch

organization.

Responsible for the development and implementation and enforcement of Flight Dispatch

functions, to maintain efficient standard of operation.

Ensure that the Flight Dispatchers are provided with the suitable knowledge, training and all

necessary material required to perform their duty.

Liaise with the Executives and assist on development and improvement of the Flight Operations

Standards as needed.

Responsible of maintaining and amending Dispatch manuals.



13.3 Duties and Responsibilities (continued)

13.3.2 Dispatcher Requirements

Comfortably reading text / graph weather as well as NOTAMs

Training may be provided for the Flight Dispatchers as required.

Flight Operations knowledge is an asset.

13.3.3 Dispatcher Duty

The dispatcher is to provide the Pilot-In-Command (PIC) in their pre-planning, departure, en-route and

arrival as needed with any information that helps to operate the flight safely and efficiently.

13.3.4 Basic information to be provided by the dispatcher consists of:

Latest weather for origin and destination.

Active runway.

Departure / Arrival gate as needed.

13.3.5 Extra information or services that might be provided to the PIC at the dispatcher’s discretion and if

requested by the PIC, it consists of but not limited to:

Formulate a flight plan or provide a routing as needed.

Provide Takeoff or landing runway performance if able (MOTW / MLW, takeoff and landing data).

Runway conditions (Dry, Wet or Contaminated).

13.3.6 Responsibilities of Dispatcher:

The Dispatcher is only available to provide the PIC with information they need to perform their

flight more efficiently.

The Dispatcher is not to be held responsible of any incident that might affect the flight.

It is the PIC sole responsibility to decide the safest course of action to be taken, and the final call

to perform their flight safely.



13.4 Ways of Communication

13.4.1 Communications Method

Text (Discord: AIRLINE OPERATIONS DISPATCH #Text_Dispatch)

Voice (Discord: AIRLINE OPERATIONS DISPATCH Channel #Dispatch 129.87)

The dispatcher will choose to go for Desk A or B based on availability.

13.5 Dispatcher Briefing

13.5.1 The briefings are an additional task to add more realism and might include but not limited to:

Pre-planning, departure, enroute, and arrival.

Where the dispatcher might provide the gate number, significant weather changes or runway

closures etc.

Briefing the pilot about the active runway as well as the expected runway based on the direction

of the flight at some airports.

13.6 Conflicts and Resolutions

13.6.1 Any conflict between the Dispatcher and the Pilot-In-Command should have the matter raised with

the Vice President – Flight Dispatch Operations.

Appropriate actions will be taken for any inappropriate behavior based on the Standard Operating

Procedures (Point 8.31).



13.7 Useful Links

NAV Canada OIS (Active Runways):

https://extranetapps.navcanada.ca/ois/ois.aspx

NAV Canada Aviation Weather (Canadian Weather/NOTAMs):

https://flightplanning.navcanada.ca

NOAA (Worldwide Weather/NOTAMs):

https://aviationweather.gov/metar

Jeppesen Weather (En-route Weather):

http://ww1.jeppesen.com/aviation/personal/ain-weather.jsp#

Skyvector:

https://skyvector.com/

Flight status (Dep/Arr Gates):

https://www.aircanada.com/ca/en/aco/home/fly/flight-information/flight-status-results.html#/home:

Flight status and actual Routings:

https://flightaware.com

Toronto Terminal 1/3 Gates (To be cross checked with YYZ Gates Chart Below):

T1

https://www.torontopearson.com/uploadedImages/Pearson/Content/To_and_From/Maps/Terminal1-

AfterSecurity_May2017.png

T3

https://www.torontopearson.com/uploadedImages/Pearson/Content/To_and_From/Maps/Terminal3-

AfterSecurity_May2017.png

https://extranetapps.navcanada.ca/ois/ois.aspx

https://flightplanning.navcanada.ca/

https://aviationweather.gov/metar

http://ww1.jeppesen.com/aviation/personal/ain-weather.jsp

https://skyvector.com/

https://www.aircanada.com/ca/en/aco/home/fly/flight-information/flight-status-results.html#/home

https://flightaware.com/

https://www.torontopearson.com/uploadedImages/Pearson/Content/To_and_From/Maps/Terminal1-AfterSecurity_May2017.png






14.0 Contact Us

14.1.0 General Inquiry

14.1.1 We invite you to contact your general e-mail at [email protected]

14.1.2 Executive Team Directory

Chairman & CEO Harvey Hicks - -

President & COO Michael Chan [email protected]

Executive Vice President & CIO -Leave Of Absence- - -

Senior Vice President – Operations Bruno Flageol [email protected]

Senior Vice President – Human Resources Daniel Desjardins [email protected]

Vice President – Systems Operations Control William English [email protected]

Vice President – Flight Dispatch Operations Arslan Nouar [email protected]

Vice President – Online Events Jordan Dawe [email protected]

Vice President – Systems Development Cory Blair [email protected]

Director – Montreal Operations Lukas Kusiak [email protected]

Director – Toronto Operations Matthew Fernandes [email protected]

Director – Vancouver Operations Michel Montreuil [email protected]

Director – Winnipeg Operations Jean-Francois Mayer [email protected]

Director – Fleet Maintenance XPlane Kevin Xie [email protected]

Director – Fleet Maintenance P3D Liam McKeown [email protected]

standard operating procedures manualvacanada.org/v6/images/docs/sop.pdf · standard operating...

Documents