No contactinfo in thePOCboxesAnythingthat has togo into theSilkway logContactingthe airfielddirectlyShaneapologizing(for literallyanything)Missionhas 4 ormoreversionsMore than 2versionchanges ofone missionin an hourWaiting for 2or more daysfor a responsefrom acontractorShaneaskingfor HardyWrongMRFversionMissionwith morethan 4legsA version 3that is thesame asversion 1OAKN givingSilkway a PPRmore than 48hrs prior tomission startContractordoesn't knowtheir NAA orNat RepWe give asolution andthe contractordoesn't followitAt least 2incorrectinputs inthe MRFSubmitting aversion changeafter themission hasalready startedGetting aPPRkickbackbecause of aNOTAMSubmittingthe MRF V0to RSFCC24 hrs orless outSayedcalling; is itapprovedyetContractorincorrectlyinputting data inthe MRF (i.e.data in wrongfields)Someone callsasking whytheir missionisn't on theflow tableContractorcalls/emailsasking forthe PPR orSquawkContractorcalling withan incorrectcallsignMission iscancelledwithin 24 hrsof missionstartNo contactinfo in thePOCboxesAnythingthat has togo into theSilkway logContactingthe airfielddirectlyShaneapologizing(for literallyanything)Missionhas 4 ormoreversionsMore than 2versionchanges ofone missionin an hourWaiting for 2or more daysfor a responsefrom acontractorShaneaskingfor HardyWrongMRFversionMissionwith morethan 4legsA version 3that is thesame asversion 1OAKN givingSilkway a PPRmore than 48hrs prior tomission startContractordoesn't knowtheir NAA orNat RepWe give asolution andthe contractordoesn't followitAt least 2incorrectinputs inthe MRFSubmitting aversion changeafter themission hasalready startedGetting aPPRkickbackbecause of aNOTAMSubmittingthe MRF V0to RSFCC24 hrs orless outSayedcalling; is itapprovedyetContractorincorrectlyinputting data inthe MRF (i.e.data in wrongfields)Someone callsasking whytheir missionisn't on theflow tableContractorcalls/emailsasking forthe PPR orSquawkContractorcalling withan incorrectcallsignMission iscancelledwithin 24 hrsof missionstart

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