Contractorcalling withan incorrectcallsignOAKN givingSilkway a PPRmore than 48hrs prior tomission startAt least 2incorrectinputs inthe MRFContactingthe airfielddirectlyWe give asolution andthe contractordoesn't followitMission iscancelledwithin 24 hrsof missionstartA version 3that is thesame asversion 1Getting aPPRkickbackbecause of aNOTAMContractordoesn't knowtheir NAA orNat RepSomeone callsasking whytheir missionisn't on theflow tableSubmitting aversion changeafter themission hasalready startedShaneapologizing(for literallyanything)Missionhas 4 ormoreversionsContractorcalls/emailsasking forthe PPR orSquawkContractorincorrectlyinputting data inthe MRF (i.e.data in wrongfields)Shaneaskingfor HardyMore than 2versionchanges ofone missionin an hourAnythingthat has togo into theSilkway logSubmittingthe MRF V0to RSFCC24 hrs orless outNo contactinfo in thePOCboxesWaiting for 2or more daysfor a responsefrom acontractorWrongMRFversionSayedcalling; is itapprovedyetMissionwith morethan 4legsContractorcalling withan incorrectcallsignOAKN givingSilkway a PPRmore than 48hrs prior tomission startAt least 2incorrectinputs inthe MRFContactingthe airfielddirectlyWe give asolution andthe contractordoesn't followitMission iscancelledwithin 24 hrsof missionstartA version 3that is thesame asversion 1Getting aPPRkickbackbecause of aNOTAMContractordoesn't knowtheir NAA orNat RepSomeone callsasking whytheir missionisn't on theflow tableSubmitting aversion changeafter themission hasalready startedShaneapologizing(for literallyanything)Missionhas 4 ormoreversionsContractorcalls/emailsasking forthe PPR orSquawkContractorincorrectlyinputting data inthe MRF (i.e.data in wrongfields)Shaneaskingfor HardyMore than 2versionchanges ofone missionin an hourAnythingthat has togo into theSilkway logSubmittingthe MRF V0to RSFCC24 hrs orless outNo contactinfo in thePOCboxesWaiting for 2or more daysfor a responsefrom acontractorWrongMRFversionSayedcalling; is itapprovedyetMissionwith morethan 4legs

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