Cold

Best or worst pilot, we will never know 😈

First of all, I woud like to credit TacticalError for his feedback improving this idea/post/draft.

Issue:
Current rules&guidelines aren’t inline with unwritten rules/expected behavior of pilots. Issue also causes wrong instructions to (newer) pilots on whats expected of them on EU1. According to several staff: (transport) pilots shouldn’t be in the pilot spawn waiting to be requested. Instead they explained to me “Pilots should be in (pilot) seat ready to transport at ‘actively used’ ground spawn points or close to ground forces in likely need of transport”.
The earlier mentioned ‘awaiting-request’ behavior is in my opinion more in accordance with current rules&guidelines.

Below the rules that are in my opinion causing the issue to occur.
Marked ambiguous parts in Bold

“4.3.1.The primary role of a pilot is to provide logistical support to the infantry on the ground.  Examples of logistical support are: transporting people, ammo, fuel, vehicles, …”
&
“4.4.1.If you are operating a support asset like a mortar or a CAS plane/helicopter you are not allowed to kill the entire AO.  Support assets are there to support the infantry this means that infantry have to call these support assets in.”

I think ‘provide’ and ‘the need for infantry to request’ are the rootcause.
Provide means (according to google) “make available for use”. and “make adequate preparation for a possible event”. Above mentioned ‘awaiting-request’ and ‘pro-active’ behaviors are both valid ways of “providing logistical support”.
‘Awaiting-request’-behavior is valid because allows for faster custom-tailored logistical support.
Pilot doesn’t have to park and possible travel to appropriate asset. Meaning pilot can provide requested support quicker.
‘Pro-active’-behavior because experience learns that this behavior can handle most requests (often even before request are made) quicker.

Above mentioned guideline/rule 4.4.1 suggests ‘awaiting-request’ is the most desirable of the options.

Additional arguments why ‘awaiting-request’ could be considered more appropriate:
-Flying about ‘when no task at hand’ as pilot is also frowned upon.
-Considering more hardcore MilSim way of waiting for transport request before entering a vehicle is within the rules/guidelines of ‘play your role’. Similar approach is expected of CAS & CAP.
-‘Pro-active’ behavior could also include pilots needing to guesstimate when AO/Objective is about to be completed and fly towards it, so exfil is smooth as possible. This could be considered ‘waste of assets’, because unnecessary risk of said asset is taken.

In summary:
A grey area occurs in rules&guidelines for the pilot role and staff enforces unwritten rules. This grey area causes unwanted behavior to occur according to unwritten rules and in my opinion should be resolved.

Proposed solution:
Add guideline to ‘4.3 or 4.4’ which states accurate expectation of transport pilots.
My suggestions for above mentioned:

Edit:
“4.3.1.The primary role of a pilot is to provide logistical support to the infantry on the ground.  Examples of logistical support are: transporting people, ammo, fuel, vehicles, …”
To (in Bold the edit)
“4.3.1.The primary role of a pilot is to provide logistical support to the infantry on the ground. Expected behavior for every pilot is being in a pilot seat ready to transport at ‘actively used’ ground spawn points or close to ground forces to fulfill their likely needs of logistical support.
Examples of logistical support are: transporting people, ammo, fuel, vehicles, …”

OR

Add guideline(s) to section 4.4:
“If you are in a pilot slot, your highest priority is to ensure swift transport of ground assets. This means being in a pilot seat ready to transport at ‘actively used’ ground spawn points or close to ground forces to fulfill their likely needs of logistical support (when no passengers are on-board). Only deviate from above mentioned behavior when non-support elements or staff call for/request different behavior. “

This is a draft, please add your suggestions for the guideline if you think it adds value and should be communicated better.

Goals of solution:
Giving staff a written rule to enforce pro-active logistical support.
Give inexperienced pilots more guidance to the role and a short “job expectation”. (In my opinion, this isn’t clearly communicated, but is expected)
Give players a written guideline to refer to when they observe unwanted behavior.

All feedback is welcome on this idea, feel free to comment your opinion.
 

Wice Skwuad Numba Won

Thanks for the awesome mission ❤️