Contractorcalls/emailsasking forthe PPR orSquawkMissionwith morethan 4legsAt least 2incorrectinputs inthe MRFSubmitting aversion changeafter themission hasalready startedMission iscancelledwithin 24 hrsof missionstartOAKN givingSilkway a PPRmore than 48hrs prior tomission startSubmittingthe MRF V0to RSFCC24 hrs orless outGetting aPPRkickbackbecause of aNOTAMContractorincorrectlyinputting data inthe MRF (i.e.data in wrongfields)WrongMRFversionShaneapologizing(for literallyanything)More than 2versionchanges ofone missionin an hourWaiting for 2or more daysfor a responsefrom acontractorSomeone callsasking whytheir missionisn't on theflow tableContractordoesn't knowtheir NAA orNat RepShaneaskingfor HardyWe give asolution andthe contractordoesn't followitNo contactinfo in thePOCboxesMissionhas 4 ormoreversionsAnythingthat has togo into theSilkway logSayedcalling; is itapprovedyetContactingthe airfielddirectlyA version 3that is thesame asversion 1Contractorcalling withan incorrectcallsignContractorcalls/emailsasking forthe PPR orSquawkMissionwith morethan 4legsAt least 2incorrectinputs inthe MRFSubmitting aversion changeafter themission hasalready startedMission iscancelledwithin 24 hrsof missionstartOAKN givingSilkway a PPRmore than 48hrs prior tomission startSubmittingthe MRF V0to RSFCC24 hrs orless outGetting aPPRkickbackbecause of aNOTAMContractorincorrectlyinputting data inthe MRF (i.e.data in wrongfields)WrongMRFversionShaneapologizing(for literallyanything)More than 2versionchanges ofone missionin an hourWaiting for 2or more daysfor a responsefrom acontractorSomeone callsasking whytheir missionisn't on theflow tableContractordoesn't knowtheir NAA orNat RepShaneaskingfor HardyWe give asolution andthe contractordoesn't followitNo contactinfo in thePOCboxesMissionhas 4 ormoreversionsAnythingthat has togo into theSilkway logSayedcalling; is itapprovedyetContactingthe airfielddirectlyA version 3that is thesame asversion 1Contractorcalling withan incorrectcallsign

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