Missionwith morethan 4legsMission iscancelledwithin 24 hrsof missionstartShaneapologizing(for literallyanything)Contractorincorrectlyinputting data inthe MRF (i.e.data in wrongfields)Submitting aversion changeafter themission hasalready startedAt least 2incorrectinputs inthe MRFOAKN givingSilkway a PPRmore than 48hrs prior tomission startMissionhas 4 ormoreversionsContractorcalling withan incorrectcallsignSomeone callsasking whytheir missionisn't on theflow tableSayedcalling; is itapprovedyetNo contactinfo in thePOCboxesContractorcalls/emailsasking forthe PPR orSquawkWaiting for 2or more daysfor a responsefrom acontractorA version 3that is thesame asversion 1Contractordoesn't knowtheir NAA orNat RepWrongMRFversionAnythingthat has togo into theSilkway logMore than 2versionchanges ofone missionin an hourContactingthe airfielddirectlyShaneaskingfor HardyWe give asolution andthe contractordoesn't followitSubmittingthe MRF V0to RSFCC24 hrs orless outGetting aPPRkickbackbecause of aNOTAMMissionwith morethan 4legsMission iscancelledwithin 24 hrsof missionstartShaneapologizing(for literallyanything)Contractorincorrectlyinputting data inthe MRF (i.e.data in wrongfields)Submitting aversion changeafter themission hasalready startedAt least 2incorrectinputs inthe MRFOAKN givingSilkway a PPRmore than 48hrs prior tomission startMissionhas 4 ormoreversionsContractorcalling withan incorrectcallsignSomeone callsasking whytheir missionisn't on theflow tableSayedcalling; is itapprovedyetNo contactinfo in thePOCboxesContractorcalls/emailsasking forthe PPR orSquawkWaiting for 2or more daysfor a responsefrom acontractorA version 3that is thesame asversion 1Contractordoesn't knowtheir NAA orNat RepWrongMRFversionAnythingthat has togo into theSilkway logMore than 2versionchanges ofone missionin an hourContactingthe airfielddirectlyShaneaskingfor HardyWe give asolution andthe contractordoesn't followitSubmittingthe MRF V0to RSFCC24 hrs orless outGetting aPPRkickbackbecause of aNOTAM

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