Contractorincorrectlyinputting data inthe MRF (i.e.data in wrongfields)WrongMRFversionWaiting for 2or more daysfor a responsefrom acontractorShaneapologizing(for literallyanything)Submitting aversion changeafter themission hasalready startedWe give asolution andthe contractordoesn't followitContractorcalls/emailsasking forthe PPR orSquawkMission iscancelledwithin 24 hrsof missionstartMissionwith morethan 4legsOAKN givingSilkway a PPRmore than 48hrs prior tomission startContactingthe airfielddirectlyAnythingthat has togo into theSilkway logNo contactinfo in thePOCboxesSayedcalling; is itapprovedyetSubmittingthe MRF V0to RSFCC24 hrs orless outShaneaskingfor HardyContractorcalling withan incorrectcallsignA version 3that is thesame asversion 1Contractordoesn't knowtheir NAA orNat RepSomeone callsasking whytheir missionisn't on theflow tableMissionhas 4 ormoreversionsMore than 2versionchanges ofone missionin an hourAt least 2incorrectinputs inthe MRFGetting aPPRkickbackbecause of aNOTAMContractorincorrectlyinputting data inthe MRF (i.e.data in wrongfields)WrongMRFversionWaiting for 2or more daysfor a responsefrom acontractorShaneapologizing(for literallyanything)Submitting aversion changeafter themission hasalready startedWe give asolution andthe contractordoesn't followitContractorcalls/emailsasking forthe PPR orSquawkMission iscancelledwithin 24 hrsof missionstartMissionwith morethan 4legsOAKN givingSilkway a PPRmore than 48hrs prior tomission startContactingthe airfielddirectlyAnythingthat has togo into theSilkway logNo contactinfo in thePOCboxesSayedcalling; is itapprovedyetSubmittingthe MRF V0to RSFCC24 hrs orless outShaneaskingfor HardyContractorcalling withan incorrectcallsignA version 3that is thesame asversion 1Contractordoesn't knowtheir NAA orNat RepSomeone callsasking whytheir missionisn't on theflow tableMissionhas 4 ormoreversionsMore than 2versionchanges ofone missionin an hourAt least 2incorrectinputs inthe MRFGetting aPPRkickbackbecause of aNOTAM

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