Erau accident reports

2 examples of this report are attached.

Read the Zonk Air Accident (DOCX) attached-scenario. You are to develop a 'partial' accident investigation report, (greater than four substantial pages), based upon the accident information provided. Be sure to review the Accident Report Project Guidelines (DOCX)attached for detailed information on project requirements.

This assignment tests your ability to apply the lessons and information learned in this course to develop a “partial” accident investigation report based upon the accident information provided on the ‘Zonk Air Accident’ scenario.

Your instructor reserves the right to determine if the length of a paper correlates to a complete document. Obviously, a brief paper indicates a lack of attention on details and research. You have some writing latitude given the mandates of the assignment but keep it uniform and well organized. In other words, do not write a “story-like narrative” or simply cut and paste from the accident scenario. Put forth some energy, creative skills, accurate writing and deduction and have some fun.

This is a blend of technical but readable report writing all encompassed by proper language, syntax, grammar and avoidance of emotional and subjective writing. The report may follow, to some extent, the manner in which the NTSB writes accident reports.

You should, as much as possible, corroborate data by explaining where the information was gained. This is spelled out in the report instructions below. In other words, there should be no leaps to conclusions without proof or data. A good report should include a probable cause and a list of contributing factors all developed and based from the information in the accident report.

Post any questions in the ‘Investigator’s Workshop’ forum so all can see the responses.

Follow the format, conventions, and examples below: