Waiting for 2or more daysfor a responsefrom acontractorShaneaskingfor HardyContractorcalling withan incorrectcallsignShaneapologizing(for literallyanything)OAKN givingSilkway a PPRmore than 48hrs prior tomission startContactingthe airfielddirectlyAt least 2incorrectinputs inthe MRFSayedcalling; is itapprovedyetWrongMRFversionSomeone callsasking whytheir missionisn't on theflow tableNo contactinfo in thePOCboxesGetting aPPRkickbackbecause of aNOTAMA version 3that is thesame asversion 1Mission iscancelledwithin 24 hrsof missionstartContractorcalls/emailsasking forthe PPR orSquawkSubmittingthe MRF V0to RSFCC24 hrs orless outSubmitting aversion changeafter themission hasalready startedAnythingthat has togo into theSilkway logContractordoesn't knowtheir NAA orNat RepContractorincorrectlyinputting data inthe MRF (i.e.data in wrongfields)Missionwith morethan 4legsMissionhas 4 ormoreversionsWe give asolution andthe contractordoesn't followitMore than 2versionchanges ofone missionin an hourWaiting for 2or more daysfor a responsefrom acontractorShaneaskingfor HardyContractorcalling withan incorrectcallsignShaneapologizing(for literallyanything)OAKN givingSilkway a PPRmore than 48hrs prior tomission startContactingthe airfielddirectlyAt least 2incorrectinputs inthe MRFSayedcalling; is itapprovedyetWrongMRFversionSomeone callsasking whytheir missionisn't on theflow tableNo contactinfo in thePOCboxesGetting aPPRkickbackbecause of aNOTAMA version 3that is thesame asversion 1Mission iscancelledwithin 24 hrsof missionstartContractorcalls/emailsasking forthe PPR orSquawkSubmittingthe MRF V0to RSFCC24 hrs orless outSubmitting aversion changeafter themission hasalready startedAnythingthat has togo into theSilkway logContractordoesn't knowtheir NAA orNat RepContractorincorrectlyinputting data inthe MRF (i.e.data in wrongfields)Missionwith morethan 4legsMissionhas 4 ormoreversionsWe give asolution andthe contractordoesn't followitMore 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. Waiting for 2 or more days for a response from a contractor
  2. Shane asking for Hardy
  3. Contractor calling with an incorrect callsign
  4. Shane apologizing (for literally anything)
  5. OAKN giving Silkway a PPR more than 48 hrs prior to mission start
  6. Contacting the airfield directly
  7. At least 2 incorrect inputs in the MRF
  8. Sayed calling; is it approved yet
  9. Wrong MRF version
  10. Someone calls asking why their mission isn't on the flow table
  11. No contact info in the POC boxes
  12. Getting a PPR kickback because of a NOTAM
  13. A version 3 that is the same as version 1
  14. Mission is cancelled within 24 hrs of mission start
  15. Contractor calls/emails asking for the PPR or Squawk
  16. Submitting the MRF V0 to RSFCC 24 hrs or less out
  17. Submitting a version change after the mission has already started
  18. Anything that has to go into the Silkway log
  19. Contractor doesn't know their NAA or Nat Rep
  20. Contractor incorrectly inputting data in the MRF (i.e. data in wrong fields)
  21. Mission with more than 4 legs
  22. Mission has 4 or more versions
  23. We give a solution and the contractor doesn't follow it
  24. More than 2 version changes of one mission in an hour