Contractorincorrectlyinputting data inthe MRF (i.e.data in wrongfields)Mission iscancelledwithin 24 hrsof missionstartContractorcalls/emailsasking forthe PPR orSquawkSayedcalling; is itapprovedyetSubmitting aversion changeafter themission hasalready startedWaiting for 2or more daysfor a responsefrom acontractorShaneaskingfor HardyShaneapologizing(for literallyanything)Anythingthat has togo into theSilkway logMissionhas 4 ormoreversionsContractorcalling withan incorrectcallsignMore than 2versionchanges ofone missionin an hourGetting aPPRkickbackbecause of aNOTAMAt least 2incorrectinputs inthe MRFA version 3that is thesame asversion 1Submittingthe MRF V0to RSFCC24 hrs orless outMissionwith morethan 4legsNo contactinfo in thePOCboxesContractordoesn't knowtheir NAA orNat RepOAKN givingSilkway a PPRmore than 48hrs prior tomission startWrongMRFversionWe give asolution andthe contractordoesn't followitContactingthe airfielddirectlySomeone callsasking whytheir missionisn't on theflow tableContractorincorrectlyinputting data inthe MRF (i.e.data in wrongfields)Mission iscancelledwithin 24 hrsof missionstartContractorcalls/emailsasking forthe PPR orSquawkSayedcalling; is itapprovedyetSubmitting aversion changeafter themission hasalready startedWaiting for 2or more daysfor a responsefrom acontractorShaneaskingfor HardyShaneapologizing(for literallyanything)Anythingthat has togo into theSilkway logMissionhas 4 ormoreversionsContractorcalling withan incorrectcallsignMore than 2versionchanges ofone missionin an hourGetting aPPRkickbackbecause of aNOTAMAt least 2incorrectinputs inthe MRFA version 3that is thesame asversion 1Submittingthe MRF V0to RSFCC24 hrs orless outMissionwith morethan 4legsNo contactinfo in thePOCboxesContractordoesn't knowtheir NAA orNat RepOAKN givingSilkway a PPRmore than 48hrs prior tomission startWrongMRFversionWe give asolution andthe contractordoesn't followitContactingthe airfielddirectlySomeone callsasking whytheir missionisn't on theflow table

Operator Bingo - Call List

(Print) Use this randomly generated list as your call list when playing the game. There is no need to say the BINGO column name. Place some kind of mark (like an X, a checkmark, a dot, tally mark, etc) on each cell as you announce it, to keep track. You can also cut out each item, place them in a bag and pull words from the bag.


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
  1. Contractor incorrectly inputting data in the MRF (i.e. data in wrong fields)
  2. Mission is cancelled within 24 hrs of mission start
  3. Contractor calls/emails asking for the PPR or Squawk
  4. Sayed calling; is it approved yet
  5. Submitting a version change after the mission has already started
  6. Waiting for 2 or more days for a response from a contractor
  7. Shane asking for Hardy
  8. Shane apologizing (for literally anything)
  9. Anything that has to go into the Silkway log
  10. Mission has 4 or more versions
  11. Contractor calling with an incorrect callsign
  12. More than 2 version changes of one mission in an hour
  13. Getting a PPR kickback because of a NOTAM
  14. At least 2 incorrect inputs in the MRF
  15. A version 3 that is the same as version 1
  16. Submitting the MRF V0 to RSFCC 24 hrs or less out
  17. Mission with more than 4 legs
  18. No contact info in the POC boxes
  19. Contractor doesn't know their NAA or Nat Rep
  20. OAKN giving Silkway a PPR more than 48 hrs prior to mission start
  21. Wrong MRF version
  22. We give a solution and the contractor doesn't follow it
  23. Contacting the airfield directly
  24. Someone calls asking why their mission isn't on the flow table