Submittingthe MRF V0to RSFCC24 hrs orless outSayedcalling; is itapprovedyetA version 3that is thesame asversion 1Contractorcalling withan incorrectcallsignAt least 2incorrectinputs inthe MRFShaneaskingfor HardyOAKN givingSilkway a PPRmore than 48hrs prior tomission startContractorincorrectlyinputting data inthe MRF (i.e.data in wrongfields)Waiting for 2or more daysfor a responsefrom acontractorMissionwith morethan 4legsShaneapologizing(for literallyanything)Getting aPPRkickbackbecause of aNOTAMContractordoesn't knowtheir NAA orNat RepAnythingthat has togo into theSilkway logContactingthe airfielddirectlyContractorcalls/emailsasking forthe PPR orSquawkSomeone callsasking whytheir missionisn't on theflow tableMore than 2versionchanges ofone missionin an hourWe give asolution andthe contractordoesn't followitNo contactinfo in thePOCboxesMissionhas 4 ormoreversionsWrongMRFversionSubmitting aversion changeafter themission hasalready startedMission iscancelledwithin 24 hrsof missionstartSubmittingthe MRF V0to RSFCC24 hrs orless outSayedcalling; is itapprovedyetA version 3that is thesame asversion 1Contractorcalling withan incorrectcallsignAt least 2incorrectinputs inthe MRFShaneaskingfor HardyOAKN givingSilkway a PPRmore than 48hrs prior tomission startContractorincorrectlyinputting data inthe MRF (i.e.data in wrongfields)Waiting for 2or more daysfor a responsefrom acontractorMissionwith morethan 4legsShaneapologizing(for literallyanything)Getting aPPRkickbackbecause of aNOTAMContractordoesn't knowtheir NAA orNat RepAnythingthat has togo into theSilkway logContactingthe airfielddirectlyContractorcalls/emailsasking forthe PPR orSquawkSomeone callsasking whytheir missionisn't on theflow tableMore than 2versionchanges ofone missionin an hourWe give asolution andthe contractordoesn't followitNo contactinfo in thePOCboxesMissionhas 4 ormoreversionsWrongMRFversionSubmitting aversion changeafter themission hasalready startedMission 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. Submitting the MRF V0 to RSFCC 24 hrs or less out
  2. Sayed calling; is it approved yet
  3. A version 3 that is the same as version 1
  4. Contractor calling with an incorrect callsign
  5. At least 2 incorrect inputs in the MRF
  6. Shane asking for Hardy
  7. OAKN giving Silkway a PPR more than 48 hrs prior to mission start
  8. Contractor incorrectly inputting data in the MRF (i.e. data in wrong fields)
  9. Waiting for 2 or more days for a response from a contractor
  10. Mission with more than 4 legs
  11. Shane apologizing (for literally anything)
  12. Getting a PPR kickback because of a NOTAM
  13. Contractor doesn't know their NAA or Nat Rep
  14. Anything that has to go into the Silkway log
  15. Contacting the airfield directly
  16. Contractor calls/emails asking for the PPR or Squawk
  17. Someone calls asking why their mission isn't on the flow table
  18. More than 2 version changes of one mission in an hour
  19. We give a solution and the contractor doesn't follow it
  20. No contact info in the POC boxes
  21. Mission has 4 or more versions
  22. Wrong MRF version
  23. Submitting a version change after the mission has already started
  24. Mission is cancelled within 24 hrs of mission start