OAKN givingSilkway a PPRmore than 48hrs prior tomission startSubmittingthe MRF V0to RSFCC24 hrs orless outWaiting for 2or more daysfor a responsefrom acontractorSayedcalling; is itapprovedyetAnythingthat has togo into theSilkway logWrongMRFversionShaneaskingfor HardyShaneapologizing(for literallyanything)Mission iscancelledwithin 24 hrsof missionstartContractorincorrectlyinputting data inthe MRF (i.e.data in wrongfields)No contactinfo in thePOCboxesContactingthe airfielddirectlyGetting aPPRkickbackbecause of aNOTAMContractordoesn't knowtheir NAA orNat RepMissionhas 4 ormoreversionsSubmitting aversion changeafter themission hasalready startedSomeone callsasking whytheir missionisn't on theflow tableA version 3that is thesame asversion 1Contractorcalls/emailsasking forthe PPR orSquawkWe give asolution andthe contractordoesn't followitAt least 2incorrectinputs inthe MRFMore than 2versionchanges ofone missionin an hourMissionwith morethan 4legsContractorcalling withan incorrectcallsignOAKN givingSilkway a PPRmore than 48hrs prior tomission startSubmittingthe MRF V0to RSFCC24 hrs orless outWaiting for 2or more daysfor a responsefrom acontractorSayedcalling; is itapprovedyetAnythingthat has togo into theSilkway logWrongMRFversionShaneaskingfor HardyShaneapologizing(for literallyanything)Mission iscancelledwithin 24 hrsof missionstartContractorincorrectlyinputting data inthe MRF (i.e.data in wrongfields)No contactinfo in thePOCboxesContactingthe airfielddirectlyGetting aPPRkickbackbecause of aNOTAMContractordoesn't knowtheir NAA orNat RepMissionhas 4 ormoreversionsSubmitting aversion changeafter themission hasalready startedSomeone callsasking whytheir missionisn't on theflow tableA version 3that is thesame asversion 1Contractorcalls/emailsasking forthe PPR orSquawkWe give asolution andthe contractordoesn't followitAt least 2incorrectinputs inthe MRFMore than 2versionchanges ofone missionin an hourMissionwith morethan 4legsContractorcalling withan incorrectcallsign

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