|
[ Career Points Scoring January 2006- ] |
| |
|
Individual Scoring |
Mission
Result (1) |
Score |
Pilot
Status (2) |
Score |
Kills/Other |
Score |
Success |
20 |
For Returning To Base (RTB)
with your own aircraft |
5 |
Friendly
Fire (3) see below |
see below |
Partial
Success |
10 |
Ejected, KIA or AWOL |
0 |
Technical failure (TECH) (6) see below |
15 |
| Failed |
0 |
LOA submitted 24hrs prior to Flight Night |
10 |
Each A-G Kill (7)
see Below |
1 |
| |
LOA submitted less than 24hrs prior to Flight
Night |
5 |
Each A-A Kill
(7) see Below |
2 |
| Flight Leader Bonus (for each individual flight
in the package) |
+30% |
Attending the Official Mission |
20 |
| |
| Human AWACS controller (if
applicable) |
will receive average
score of all the human pilots who flew the mission + 5points . For
Mission reporting, Flights Leaders should record Role as AWACS, leaving the Pilot Status and Mission Outcome fields
empty. |
|
Flight Scoring |
| Flight Score |
= |
Sum of all the individual Scores of the
pilots who flew the mission |
+ |
RTB Bonus (4)
see below |
| |
+ |
FWA (5) see
below |
|
+ |
Human AWACS controller score (if
applicable) |
| (1) |
Criteria for Mission Success
and Mission Partial Success
will be clearly stated in the briefing that all pilots
will receive before flying the mission. Any other result
is of course a Mission Failed.
Pay close attention to what is said in the debrief. Since
we no longer only depend on the Falcon 4 debrief you may
be required to support your result by either a screenshot
of the debrief, listing that you indeed have destroyed
the briefed target or provide an ACMI of the actual strike
itself. Note: It is always a good idea that someone
in the flight ACMI's most of the mission, but for the
sake of the mission result an ACMI only covering the strike
itself should be provided to your flights command. It
may be a good idea to decide who will make this ACMI in
the pre-flight briefing. The Writer of an Official
TE should not take a Flight Lead position when flying any
official mission that they have created and should not be
involved in any strategic decisions taken by the flight in
respect of the mission planning in the interests of
impartiality.
|
|
(2) |
RTB = Returned To Base, i.e. you managed to land on the airbase from which
you took off. However, in case of emergency this also
includes landing on any friendly controlled airbase,
but you should always try to get back to the airbase
you started from unless the briefing specifically states
otherwise.
Ejected = Ejected from aircraft. This means that you for some reason had to eject from
your F-16 or other aircraft. We have no way of actually
monitoring if you survived your ejection, other than
reviewing ACMI's from all flights which just is not
practical, so we leave it up to your common sense, i.e.
if for example you punch out while at 100 feet with
your Viper inverted, you should of course report that
you were killed.
KIA = Killed In Action,
speaks for itself.
LOA =
Leave of absence:
Email sent to your flight lead/2ic at least (wherever
possible) 24hrs in advance of Flight Night advising them
that you will not be able to attend. Out of
courtesy to your colleagues, please submit an LOA even
if the notice given is less than 24 hrs to avoid members
waiting around unnecessarily for absent pilots.
AWOL =
Absent Without Leave :
Failure to send in an LOA (see above). The
requirement for continued membership of the 185th is a
minimum of 50% attendance on Official Flight
Nights. Failure to meet this standard
without reasonable explanation or extenuating
circumstances will result in your removal from the Roster.
|
| (3) |
All
Friendly Fire incidents, against Human pilots, are subject
to an automatic Penalty:
All friendly fire incidents
against Human pilots will automatically result in
the offender receiving a fixed score of 20 points
for the mission, regardless of their status or
mission outcome. Offenders may appeal to Command,
through their Flight Leader, within 7 days of the
incident if they feel the sanction is unjust,
but no appeals will be heard without supporting
evidence of the event, such as pilot testimony, ACMI
and screenshots. Command will review all evidence on
the matter and submit a verdict within 7 days of
receiving an appeal. If Command finds that the
friendly fire occurred due to technical problems in
the game, they have the power to clear the accused
of all charges and restore their full flight score.
Command's decision will be final and there is no
further right of appeal.
Friendly Fire score:
- Offender: Fixed tariff of 20 points applied
regardless of contribution to the mission and
mission outcome.
A2A and
A2G kills should be recorded as normal as these will
still count toward the Ace of the Base and Master
Mudpounder awards. Note that the friendly fire
kill MUST NOT be included in the AA kills reported
in the CPL Mission Report.
- Victim: The victim receives normal credit for the
mission including any kills recorded up until the
incident. Their status should be recorded as EJT or
KIA.
|
| (4) |
RTB
Bonus= Supplement to the Team score to reward
Flights who bring as many planes home as possible
:
Applied to the Package as a whole (ie
all human controlled aircraft who took off) as follows:-
100% Human Controlled Aircraft
RTB = +20 to the Flight Score
51-99% Human Controlled Aircraft
RTB = +10 to the Flight Score
Less than 50% Human Controlled
Aircraft RTB = +5 to the Flight
Score
0% Human Controlled Aircraft RTB
= No adjustment to the Flight Score |
| (5) |
FWA =
Flight Weighting Adjustment :
Adjustment to the team score to take account of number
of human pilots that actually flew the mission.
Less pilots means harder level of difficulty.
Official Missions MUST never be attempted with
less than 3. If you have less than 3 then you MUST merge with one of the other teams
or request that Command provides additional pilots for
the night.
Adjustment formula is (average score
of all the human pilots that took part excluding TECHS
and LOAs) multiplied by the number of AI
pilots + 1 if flight flies WITHOUT human AWACS support.
If Flight flies WITH human AWACS
support, the adjustment formula is (average score
of all the human pilots that took part excluding TECHS
and LOAs) multiplied by the number of AI
pilots. The human who takes the AWACS seat will
receive the average score of all the human pilots and
should be recorded in this role on the Mission Results
input screen for the CPL.
If 2 flights combine due to lack of
numbers, then each flight will receive the same FWA
based upon the total number of human pilots present.
If the TE is flown with the full
6 pilots + human AWACS the FWA will be 0. |
| (6) |
TECH= Technical Failure:
Pilots are entitled to claim a TECH only
if they are unable to complete the mission due to a
crash to desktop, hardware failure or loss of internet
connectivity whist flying or a technical failure that
prevents them from connecting to the Host. However
they MUST have been present on the squadron Teamspeak
server and made an active attempt to join the flight in
order to claim a TECH. Long term
technical problems such as router issues and computer
stability problems that prevent pilots from
participating from one week to the next should be
handled via the LOA procedure . Pilots should keep
their flight leaders informed as to what they are doing to
resolve the issue in order that someone in the squadron
may be able to help them. If such an absence lasts
longer than 4 weeks, pilots may be moved to the Reserves
at their Flight Leaders discretion until they are able to
fly again.
|
| (7) |
Any Air-to-Air and
Air-to-Grounds kills on Friendly units (Human or AI) are
NOT to be included in the total kills recorded in the
CPL mission results Any Air-to-Ground
kills against civilian targets not authorised by the mission
briefing MUST NOT be counted for the purposes of CPL scoring. |
|
Awards Criteria |
|
Individual Awards |
Qualification |
Elegibility |
| Flight Lead of the
Month/Quarter/Year (TOTAL POINTS) |
Highest number of CPL points scored
in the period |
Open to all pilots |
| Flight Lead of the
Month/Quarter/Year (AVE POINTS) |
Highest Average CPL score in the
period |
Open to all pilots with at least 50% attendance over the period |
| Pilot of the Month/Quarter/Year
(TOTAL POINTS) |
Highest number of CPL points scored
in the period |
Open to all pilots, subject to having flown no more than 25% of
missions as Flight Lead |
| Pilot of the Month/Quarter/Year
(AVE POINTS) |
Highest Average CPL score in the
period |
Open to all pilots with at least 50% attendance over the period
, subject to having flown no more than 25% of missions as Flight
Lead |
| Survivor of the Month/Quarter/Year |
Highest Mission Survival Percentage
in the period |
Open to all pilots with at least 50% attendance over the period |
| Ace of the Base Month/Quarter/Year |
Highest number of Air to Air Kills
in the period |
Open to all pilots |
| Master Mudpounder Month/Quarter/Year |
Highest number of Air to Ground
Kills in the period |
Open to all pilots |
|
Flight
Awards |
| Flight of the Month/Quarter/Year |
Awarded to the Flight with the
highest cumulative CPL team score in the period |
Open to all 4 flights of the 185th VFS |
| |
