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