Contactingthe airfielddirectlySubmitting aversion changeafter themission hasalready startedShaneaskingfor HardySomeone callsasking whytheir missionisn't on theflow tableShaneapologizing(for literallyanything)Contractorcalling withan incorrectcallsignSayedcalling; is itapprovedyetMore than 2versionchanges ofone missionin an hourAnythingthat has togo into theSilkway logA version 3that is thesame asversion 1Mission iscancelledwithin 24 hrsof missionstartAt least 2incorrectinputs inthe MRFGetting aPPRkickbackbecause of aNOTAMNo contactinfo in thePOCboxesOAKN givingSilkway a PPRmore than 48hrs prior tomission startContractorcalls/emailsasking forthe PPR orSquawkSubmittingthe MRF V0to RSFCC24 hrs orless outWaiting for 2or more daysfor a responsefrom acontractorMissionhas 4 ormoreversionsContractordoesn't knowtheir NAA orNat RepMissionwith morethan 4legsContractorincorrectlyinputting data inthe MRF (i.e.data in wrongfields)WrongMRFversionWe give asolution andthe contractordoesn't followitContactingthe airfielddirectlySubmitting aversion changeafter themission hasalready startedShaneaskingfor HardySomeone callsasking whytheir missionisn't on theflow tableShaneapologizing(for literallyanything)Contractorcalling withan incorrectcallsignSayedcalling; is itapprovedyetMore than 2versionchanges ofone missionin an hourAnythingthat has togo into theSilkway logA version 3that is thesame asversion 1Mission iscancelledwithin 24 hrsof missionstartAt least 2incorrectinputs inthe MRFGetting aPPRkickbackbecause of aNOTAMNo contactinfo in thePOCboxesOAKN givingSilkway a PPRmore than 48hrs prior tomission startContractorcalls/emailsasking forthe PPR orSquawkSubmittingthe MRF V0to RSFCC24 hrs orless outWaiting for 2or more daysfor a responsefrom acontractorMissionhas 4 ormoreversionsContractordoesn't knowtheir NAA orNat RepMissionwith morethan 4legsContractorincorrectlyinputting data inthe MRF (i.e.data in wrongfields)WrongMRFversionWe give asolution andthe contractordoesn't followit

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