Contractorincorrectlyinputting data inthe MRF (i.e.data in wrongfields)Mission iscancelledwithin 24 hrsof missionstartSubmittingthe MRF V0to RSFCC24 hrs orless outShaneapologizing(for literallyanything)No contactinfo in thePOCboxesContractordoesn't knowtheir NAA orNat RepAnythingthat has togo into theSilkway logA version 3that is thesame asversion 1Submitting aversion changeafter themission hasalready startedContractorcalling withan incorrectcallsignMissionwith morethan 4legsSomeone callsasking whytheir missionisn't on theflow tableSayedcalling; is itapprovedyetGetting aPPRkickbackbecause of aNOTAMWrongMRFversionShaneaskingfor HardyWe give asolution andthe contractordoesn't followitOAKN givingSilkway a PPRmore than 48hrs prior tomission startWaiting for 2or more daysfor a responsefrom acontractorMore than 2versionchanges ofone missionin an hourMissionhas 4 ormoreversionsAt least 2incorrectinputs inthe MRFContractorcalls/emailsasking forthe PPR orSquawkContactingthe airfielddirectlyContractorincorrectlyinputting data inthe MRF (i.e.data in wrongfields)Mission iscancelledwithin 24 hrsof missionstartSubmittingthe MRF V0to RSFCC24 hrs orless outShaneapologizing(for literallyanything)No contactinfo in thePOCboxesContractordoesn't knowtheir NAA orNat RepAnythingthat has togo into theSilkway logA version 3that is thesame asversion 1Submitting aversion changeafter themission hasalready startedContractorcalling withan incorrectcallsignMissionwith morethan 4legsSomeone callsasking whytheir missionisn't on theflow tableSayedcalling; is itapprovedyetGetting aPPRkickbackbecause of aNOTAMWrongMRFversionShaneaskingfor HardyWe give asolution andthe contractordoesn't followitOAKN givingSilkway a PPRmore than 48hrs prior tomission startWaiting for 2or more daysfor a responsefrom acontractorMore than 2versionchanges ofone missionin an hourMissionhas 4 ormoreversionsAt least 2incorrectinputs inthe MRFContractorcalls/emailsasking forthe PPR orSquawkContactingthe airfielddirectly

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