Someone callsasking whytheir missionisn't on theflow tableWe give asolution andthe contractordoesn't followitSubmittingthe MRF V0to RSFCC24 hrs orless outContractorincorrectlyinputting data inthe MRF (i.e.data in wrongfields)OAKN givingSilkway a PPRmore than 48hrs prior tomission startMission iscancelledwithin 24 hrsof missionstartMissionwith morethan 4legsContractorcalls/emailsasking forthe PPR orSquawkAnythingthat has togo into theSilkway logNo contactinfo in thePOCboxesMore than 2versionchanges ofone missionin an hourShaneaskingfor HardyContactingthe airfielddirectlySubmitting aversion changeafter themission hasalready startedMissionhas 4 ormoreversionsContractordoesn't knowtheir NAA orNat RepSayedcalling; is itapprovedyetGetting aPPRkickbackbecause of aNOTAMWaiting for 2or more daysfor a responsefrom acontractorWrongMRFversionShaneapologizing(for literallyanything)A version 3that is thesame asversion 1Contractorcalling withan incorrectcallsignAt least 2incorrectinputs inthe MRFSomeone callsasking whytheir missionisn't on theflow tableWe give asolution andthe contractordoesn't followitSubmittingthe MRF V0to RSFCC24 hrs orless outContractorincorrectlyinputting data inthe MRF (i.e.data in wrongfields)OAKN givingSilkway a PPRmore than 48hrs prior tomission startMission iscancelledwithin 24 hrsof missionstartMissionwith morethan 4legsContractorcalls/emailsasking forthe PPR orSquawkAnythingthat has togo into theSilkway logNo contactinfo in thePOCboxesMore than 2versionchanges ofone missionin an hourShaneaskingfor HardyContactingthe airfielddirectlySubmitting aversion changeafter themission hasalready startedMissionhas 4 ormoreversionsContractordoesn't knowtheir NAA orNat RepSayedcalling; is itapprovedyetGetting aPPRkickbackbecause of aNOTAMWaiting for 2or more daysfor a responsefrom acontractorWrongMRFversionShaneapologizing(for literallyanything)A version 3that is thesame asversion 1Contractorcalling withan incorrectcallsignAt least 2incorrectinputs inthe MRF

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