Missionwith morethan 4legsSomeone callsasking whytheir missionisn't on theflow tableShaneapologizing(for literallyanything)Contractorcalling withan incorrectcallsignContactingthe airfielddirectlyMission iscancelledwithin 24 hrsof missionstartWaiting for 2or more daysfor a responsefrom acontractorSubmittingthe MRF V0to RSFCC24 hrs orless outAt least 2incorrectinputs inthe MRFWe give asolution andthe contractordoesn't followitAnythingthat has togo into theSilkway logWrongMRFversionMissionhas 4 ormoreversionsNo contactinfo in thePOCboxesGetting aPPRkickbackbecause of aNOTAMContractorcalls/emailsasking forthe PPR orSquawkOAKN givingSilkway a PPRmore than 48hrs prior tomission startSayedcalling; is itapprovedyetContractorincorrectlyinputting data inthe MRF (i.e.data in wrongfields)A version 3that is thesame asversion 1Submitting aversion changeafter themission hasalready startedShaneaskingfor HardyContractordoesn't knowtheir NAA orNat RepMore than 2versionchanges ofone missionin an hourMissionwith morethan 4legsSomeone callsasking whytheir missionisn't on theflow tableShaneapologizing(for literallyanything)Contractorcalling withan incorrectcallsignContactingthe airfielddirectlyMission iscancelledwithin 24 hrsof missionstartWaiting for 2or more daysfor a responsefrom acontractorSubmittingthe MRF V0to RSFCC24 hrs orless outAt least 2incorrectinputs inthe MRFWe give asolution andthe contractordoesn't followitAnythingthat has togo into theSilkway logWrongMRFversionMissionhas 4 ormoreversionsNo contactinfo in thePOCboxesGetting aPPRkickbackbecause of aNOTAMContractorcalls/emailsasking forthe PPR orSquawkOAKN givingSilkway a PPRmore than 48hrs prior tomission startSayedcalling; is itapprovedyetContractorincorrectlyinputting data inthe MRF (i.e.data in wrongfields)A version 3that is thesame asversion 1Submitting aversion changeafter themission hasalready startedShaneaskingfor HardyContractordoesn't knowtheir NAA orNat RepMore than 2versionchanges ofone missionin an hour

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