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