Contractordoesn't knowtheir NAA orNat RepAnythingthat has togo into theSilkway logSubmittingthe MRF V0to RSFCC24 hrs orless outMore than 2versionchanges ofone missionin an hourSomeone callsasking whytheir missionisn't on theflow tableWaiting for 2or more daysfor a responsefrom acontractorWrongMRFversionAt least 2incorrectinputs inthe MRFContactingthe airfielddirectlySubmitting aversion changeafter themission hasalready startedContractorcalls/emailsasking forthe PPR orSquawkMissionhas 4 ormoreversionsOAKN givingSilkway a PPRmore than 48hrs prior tomission startContractorincorrectlyinputting data inthe MRF (i.e.data in wrongfields)Missionwith morethan 4legsShaneapologizing(for literallyanything)Shaneaskingfor HardyContractorcalling withan incorrectcallsignGetting aPPRkickbackbecause of aNOTAMSayedcalling; is itapprovedyetNo contactinfo in thePOCboxesWe give asolution andthe contractordoesn't followitMission iscancelledwithin 24 hrsof missionstartA version 3that is thesame asversion 1Contractordoesn't knowtheir NAA orNat RepAnythingthat has togo into theSilkway logSubmittingthe MRF V0to RSFCC24 hrs orless outMore than 2versionchanges ofone missionin an hourSomeone callsasking whytheir missionisn't on theflow tableWaiting for 2or more daysfor a responsefrom acontractorWrongMRFversionAt least 2incorrectinputs inthe MRFContactingthe airfielddirectlySubmitting aversion changeafter themission hasalready startedContractorcalls/emailsasking forthe PPR orSquawkMissionhas 4 ormoreversionsOAKN givingSilkway a PPRmore than 48hrs prior tomission startContractorincorrectlyinputting data inthe MRF (i.e.data in wrongfields)Missionwith morethan 4legsShaneapologizing(for literallyanything)Shaneaskingfor HardyContractorcalling withan incorrectcallsignGetting aPPRkickbackbecause of aNOTAMSayedcalling; is itapprovedyetNo contactinfo in thePOCboxesWe give asolution andthe contractordoesn't followitMission iscancelledwithin 24 hrsof missionstartA version 3that is thesame asversion 1

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