ORBcaused byFC doinga CC task“BadTechnicalInput”Someonepronouncesa CC’sname wrongSean callspeople whoare glutenfree “special”ORBcaused byOASIS-PSblack magicSomeonecomplainsabout nothavingenough coffeeSomeonebrings upstudentprankingA CCITasks for asignatureSomeonefallsasleep3 or morespellingmistakes inone slideAn ORBgoes fortwice as longas scheduledA CC makesa suggestthat getscompletelyshut downSomeonetalks about“the thoughtprocess”Someonesends anout of officeemailPat starts talkingabout BDM and noone understandswhat he’s sayingexcept for Gina andRobby and nowRoss and Reidar3 or moretotallyundefinedacronyms usedon a singleslideAn ORBcaused bybad versioncontrolSean suggeststakingsomethingoffline that weall know won’tbeAn ORBcaused by asimplesyntax errorORB causedbycompletelydisregardingprocedure“PersonnelError”Sean asks aquestion with anobvious answerthat leaves theroom speechlessAn ORBcaused byusing thewrong fileImpossibleaction itemsuggestedMAVENishappyFunnyringtonegoes offSomeoneassigns anaction itemto a studentSomeonegetspagedORB caused bymiscommunicationAn FDblames an“FC” insteadofthemselvesAn ORB withno actualeffect on thespacecraftORB causedby ignoringcheckproductsoutputSomeonementions a bestpracticesdocument thatno one knowsexistsORB causedby blindlyexecuting amanprocORB caused byonly one personknowing how toperform a taskSean saysORBs increaseat thebeginning ofthe semesterThere’s aTDRS with one‘S’ and onewith two ‘S’s inthe same ORBAn FDbrutallycriticizessomeoneORBcaused byFC doinga CC task“BadTechnicalInput”Someonepronouncesa CC’sname wrongSean callspeople whoare glutenfree “special”ORBcaused byOASIS-PSblack magicSomeonecomplainsabout nothavingenough coffeeSomeonebrings upstudentprankingA CCITasks for asignatureSomeonefallsasleep3 or morespellingmistakes inone slideAn ORBgoes fortwice as longas scheduledA CC makesa suggestthat getscompletelyshut downSomeonetalks about“the thoughtprocess”Someonesends anout of officeemailPat starts talkingabout BDM and noone understandswhat he’s sayingexcept for Gina andRobby and nowRoss and Reidar3 or moretotallyundefinedacronyms usedon a singleslideAn ORBcaused bybad versioncontrolSean suggeststakingsomethingoffline that weall know won’tbeAn ORBcaused by asimplesyntax errorORB causedbycompletelydisregardingprocedure“PersonnelError”Sean asks aquestion with anobvious answerthat leaves theroom speechlessAn ORBcaused byusing thewrong fileImpossibleaction itemsuggestedMAVENishappyFunnyringtonegoes offSomeoneassigns anaction itemto a studentSomeonegetspagedORB caused bymiscommunicationAn FDblames an“FC” insteadofthemselvesAn ORB withno actualeffect on thespacecraftORB causedby ignoringcheckproductsoutputSomeonementions a bestpracticesdocument thatno one knowsexistsORB causedby blindlyexecuting amanprocORB caused byonly one personknowing how toperform a taskSean saysORBs increaseat thebeginning ofthe semesterThere’s aTDRS with one‘S’ and onewith two ‘S’s inthe same ORBAn FDbrutallycriticizessomeone

ORB DAY BINGO 2018 - 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
25
26
27
28
29
30
31
32
33
34
35
36
37
38
  1. ORB caused by FC doing a CC task
  2. “Bad Technical Input”
  3. Someone pronounces a CC’s name wrong
  4. Sean calls people who are gluten free “special”
  5. ORB caused by OASIS-PS black magic
  6. Someone complains about not having enough coffee
  7. Someone brings up student pranking
  8. A CCIT asks for a signature
  9. Someone falls asleep
  10. 3 or more spelling mistakes in one slide
  11. An ORB goes for twice as long as scheduled
  12. A CC makes a suggest that gets completely shut down
  13. Someone talks about “the thought process”
  14. Someone sends an out of office email
  15. Pat starts talking about BDM and no one understands what he’s saying except for Gina and Robby and now Ross and Reidar
  16. 3 or more totally undefined acronyms used on a single slide
  17. An ORB caused by bad version control
  18. Sean suggests taking something offline that we all know won’t be
  19. An ORB caused by a simple syntax error
  20. ORB caused by completely disregarding procedure
  21. “Personnel Error”
  22. Sean asks a question with an obvious answer that leaves the room speechless
  23. An ORB caused by using the wrong file
  24. Impossible action item suggested
  25. MAVEN is happy
  26. Funny ringtone goes off
  27. Someone assigns an action item to a student
  28. Someone gets paged
  29. ORB caused by miscommunication
  30. An FD blames an “FC” instead of themselves
  31. An ORB with no actual effect on the spacecraft
  32. ORB caused by ignoring check products output
  33. Someone mentions a best practices document that no one knows exists
  34. ORB caused by blindly executing a manproc
  35. ORB caused by only one person knowing how to perform a task
  36. Sean says ORBs increase at the beginning of the semester
  37. There’s a TDRS with one ‘S’ and one with two ‘S’s in the same ORB
  38. An FD brutally criticizes someone