Failure Case report – Teamwork # 6

MENG2110 -"Failure Case" report – Teamwork # 6 . DUE in 4 weeks 1. Each team must choose (*) an engineering-failure case for study and report. 2. Report (5-6 pages minimum) must include: - Brief background on the reported structure/project/system. - Brief and to-the-point general description of failure, and of loss/casualties. - More detailed report of studies carried out to determine the causes of failure, including FIGURES (may cut and paste) and sketches when needed. - Report of developed solutions (if any) to the causes of failure (in future systems/projects, if any) , including figures (may cut and paste) and sketches when needed. - Complete list of references to the used sources of information (websites, technical reports, etc.) (*) by today : deadline for decision: DURING CLASS (please, email to instructor, one decision per team, and **NOT** multiple choices) (NOT DOING SO WILL RESULT IN MANY OF THE FOLLOWING TOPICS BEING TAKEN BY OTHER TEAMS): May choose one of the following suggested classic engineering cases (NOTE: first come-first served, no two teams with same topic, MUST sent CLEAR email WITH TEAM NAME (no just a student name) to instructor to “call” any topic): **NOTE** topic cannot be changed after this lecture, except in case of (**) below See FILE IN FOLIO FOR TOPICS (TOPICS CANNOT BE SELECTED IN ADVANCE OF CLASS AND MUST BE "CALLED" AT SAME TIME THAN REST OF CLASS....) OR (**) choose another engineering-failure topic of your interest from other source, http://www.journals.elsevier.com/case-studies-in-engineering-failure-analysis/ https://www.journals.elsevier.com/engineering-failure-analysis https://www.springer.com/journal/11668 if so your team must get approval from instructor by today at the latest, by sending ASAP email message to gmolina@georgiasouthern.edu)