rEPORTING FOR FLIGHT DUTY

Staff must report for duty no later than 50 minutes before departure, uless if a
staff member has a pre-booked flight absence or is on leave. Exact reporting
locations vary between bases, and this will be shown to you during the practical
session after day 3. Typically, stafff wil meet in the briefing room or onboard an
aircraft.

Each department will operate a crew briefing, designed to create and maintain a
professional and open working enviroment. You must arrive promptly at the
desginated at the designated flight report time and then use the computers in the
flight crew room to log in.

During briefing, you and your respective department will brief at the reporting
point to:

Confirm each staff member's role at each flight stage.

Review any safety memos.
Make all staff members aware of the flights to be operated and the expected
passenger load.
Review service requirements.
Provide any additional information regarding the weather, passenger load risk
factors, ETC.

In order to ensure staff meet the weekly quota, we have an attendance tracking
system which is used to record presence of staff at flight.

1. to login, walk up to the computer and hold F.

2. Once the GUI is open, you will be greeted with 4 options. Select a option and
wait for the sustem to confirm it has logged your attendance.

When logging out early, ensure that a reason is provided, Staff must message the
Flight Dispatcher via PMs or DMs to ask if they can leave early, if not followed,
attendance will be marked as unauthorized.

Should a staff member be unable to fullfil their rostered duty, a reserve STBY will
be called in to take oevr this role. Replacement staff must establish
communications with their crew, obtain necessary details and reaffirm any operating
instructions.

To leave an absence, you must post a message with a reason no later than 30 minutes
before the flight report time, unless if it is a valid emergency, in the #flight-
absences channel. An emergency wcould be anything that may be time sensitive to do
with friends, family, healths, ETC.

It is up to the discretion of the base supervisor to approve/decline absences. Your

attendance, including absence, are tracked vigorously on a weekly basis, unless if
you have applied for an online carreer (incl. Sales & marketing executives,
customer care escalation agents and commerical planning analysts) where you will
instead be given other weekly requirements.

Safety on the ramp

It is important that all staff are fully aware of ramp safety while airisde at an
airport. The following points must always be adhered to:

- All thatt must always wear a Hi-Viz jacket at all times while airside.
- Airside acces is only permitted for staff whose duty requires them to do so.
Security must remeain inoors unless permitted by a supervisor to enter airside.
Observers, misconnected passangers and all other ground-bound personnel must remain
indoors at all time unless given special exemption by senior management. Where
security and/or observers are permitted to enter airside, a Hi-Viz jacket must be
worn.
- All staff must be in possession of a valid Ryanair identification card and
accompanying lanyard.
- When entering or leaving an airport terminal building (airside) staff shall
ensure that all security doors are closed after use.
- All staff must be alert to different types of ramp vehicles.
- When walking on the ramp, staff must use the marked walkway signs on the ground.
- The rotating beacon on top and below an aircraft fuselage indicates it is about
or has its engines running. Never eter the blast radius of an aircraft's engine.
- Never walk on taxiways

Use of administrative powers

Staff must exercise discretion, maturity and common sense. It is a priority for
staff to ensure that any administration command will not result in a glitch or
infringe safety, privacy or security.

As a staff member at Ryanair, staff are given basic moderator administrative

permissions to assist them in performing duties at flights. Due to this,
restrictions have been put into place which makes some commands inaccesible to
lower staff. This includes:

:view - This command can only be performed on passengers and general staff/low
ranks. Staff must seek permission to view anyone who isn't passenger or low rank.
:teleport/:tp/:to -This command can only be performed on passengers and general
staff/low ranks. Staff must seek permission to teleport to anyone who isn't
passenger or low rank. Additionally, staff must always view the user they wish to
teleport to before doing so. If they are in a vehicle, bus or aircraft, or an area
out of your acces levels, staff must NOT teleport to them.

:logs/:chatogs - this command can only be performed when staff needs to check
something essential, such as replaying a message which they were slightly AFK from,
or finding out who violated one of the Administrative Guidelines so that they may
report them and provide evidence.

:bring - This command restricted to most staff due to its danger. This command can
sometimes be used if a passenger falls out of the A/C on cruise, for instance.
However, staff must seek permission from Senior Management first.

:btools - This command is restricted to most staff due to its power and danger.
This tool is only accesible to those who have gone through the required training
course.

All "party" commands are forbidden due to their unprofessionalism. This

includes: :music, :play, :pitch, ETC.

Administrator commands must be used appropriately and sparingly. The administrative

guidelines stated below must be followed at any given time across all Ryanair Group
games:

Staff should never go over the speed of 20 when inside the terminal building, and
mustn't go over the speed of 25 outside. Ground handling agents may speed up to 45
should they need to respond to an emergency, e.g. recovering a stolen vehicle.
Permission from the flight dispatcher or higher is required if passengers are in
game.
Staff must not fly in front of passengers as this is unrealistic. permission must
be given from a Base Supervisor or higher in order to fly with passengers in-game.
Ground handling agents and flight crew may fly without permission to spawn their
respective vehicles/aircraft, ensuring that they do this with extra caution and in
an appropriate location.

Staff must receive permission to view or tp to someone who isn't passenger or low
rank.

For any person whom staff teleport to, staff must view them beforehand to check
that they are in a vehicle or an area which restricts that staff member from
enetring.

Staff may only give tools to players when it is under procedure. This may include
giving a Plus ticket to the family member or a Family Plus ticket. Giving
passengers any tool other than food, drinks, amentities or boarding passes is
prohibited, unless given permission from SM.

Staff must take extra care and attention when performing commands. For instance,
you should never execute the :give command without also specifying a tool name
after the username. If a tool name is not specified then it gives the user every
tool, including security weapons.

Short usernames must be entered in full to prevent username mix ups. Short
usernames are classed as ones that are six characters or less. Usernames longer
than this must have at least 80% of them typed out.

Passengers must never be refreshed once they have passed the security checkpoint,
as their outfit would need to get re-checked at scanners. Instead, if someone
wishes to be refreshed, they must agree to be respawned and go through security
again, Never teleport a passenger past security.

Misuse of the administrative guidelines will result in an automatic disciplary.

This is permanent and wil remain on your record throughout your career.

All commands must be hidden from the view of passengers. This means that they
should be executed i the command bar, or by sending messages by the /c system.

To acces the command bar, press on @ / 'on your keyboard. In the command bar, by
the prefix ',' is not required. You can simply write out the desired command as
shown.

To execute commands using /c system, simply:

Type /c system into the chat

Then enter the command with the prefix :

Disruptive passengers:

Passengers are classified as disruptive when they are breaking any of the rules
outlined on the website, or on the game terms and conditions panel. They may also
be disruptive if they are behaving inappropriately, refuse to cooperate or
challenge staff in any way.

Security staff observe for breaches of rules and conduct routinely patrols around
the termina perimeter will be able to locate DPAX. Some examples of rule breaching
which warrant a DPAX include:

Passengers who repeatedly push into queues.

Passengers who annoy or disturb other passengers or staff, such as by shouting at
them, following them or by sending inappropriate messages.
Passengers who enter off-limit areas such as staff rooms by use of glitching.
Passengers who climb objects in the airport such as fences or shops or who climb
airport infrastructure such as pilars or windows.
Passeners who are rude (racist, sexist, hompohobic, ETC) to other passengers or
staff.
Passengers who shout or attempt to incite a riot or disturbance where such
campaigning is not permitted by the local airport's legislation.
Passengers who lie or give false, misleading, untrue or inaccurate information when
questioned by staff or security puposes.
Passengers who refuse to follow the instructions of staff members.
Passengers who purposely and continuously crowd or attempt to form a queue where
crowding or queueing is not permitted.

While the disruption is minor, staff can attempt to warn and resolve DPAX on their
own. Minor infringements may include passengers who are climbing