Abstract

What constitutes a cause is a particularly important question for those who teach or study technical writing. This article describes a case that helps students look beyond the technical "causes" of a commuter airplane crash in order to address the complex web of policies, practices, actions and events that contributed to the crash. Using an approach grounded in stakeholder theory and ethical theory, students use real documents ranging from news accounts to FAA policies to NTSB hearing exhibits to identify systemic problems that contributed to the disaster. Working from particular stakeholder perspectives, they work collaboratively to develop and argue for policy changes that will prevent future tragedies. The abundance of real documents that drive this case make it an especially useful tool for engaging students in difficult-to-teach subject matter including the role of writing in the failure of technical systems, deliberative and judicial rhetoric, stakeholder theory, visual rhetoric, and ethics.

Journal
IEEE Transactions on Professional Communication
Published
2004-12-01
DOI
10.1109/tpc.2004.837969
CompPile
Open Access
Closed
Topics
Export

Citation Context

Cited by in this index (8)

  1. IEEE Transactions on Professional Communication
  2. Journal of Technical Writing and Communication
  3. Journal of Technical Writing and Communication
  4. Journal of Technical Writing and Communication
  5. Journal of Technical Writing and Communication
Show all 8 →
  1. IEEE Transactions on Professional Communication
  2. Journal of Technical Writing and Communication
  3. IEEE Transactions on Professional Communication

References (33) · 1 in this index

  1. 10.4324/9781410606815
  2. 10.2307/358988
  3. Technical Communication Quarterly
  4. Political–ethical implications of defining technical communication as a practice
    J. Adv. Compos.
  5. Classical Rhetoric for the Modern Student
Show all 33 →
  1. Classical Rhetoric for the Modern Student
  2. Flight 5481 Declared Emergency Before Crash Cable News Network
  3. NTSB Releases New Details on Crash of Flight 5481
  4. NTSB Focuses Investigation on Mechnics, Weight of Aircraft
  5. Third-party maintenance issues grab spotlight
    Overhaul Mainten.
  6. Aircraft maintenance firm, airline sever ties after Charlotte, N.C., crash
    Charlotte Observer
  7. Associated Press
  8. NTSB cites maintenance worker fatigue in Air Midwest crash
  9. Associated Press
  10. Assoc. Press
  11. NTSB explores second fatal crash of Beechcraft 1900D this yea
  12. Technicians cite confusing instructions in Raytheon manual
    Aviation Daily
  13. Two Grad Students Die in Charlotte Plane Crash
  14. Federal Aviation Administration
  15. NTSB: Tail Equipment Moved Erratically
  16. Associated Press
  17. Crash Raises Concern About Weight, Stability in Commuter Flights
  18. Associated Press
  19. Report: Airplane Maintenance Companies Made Mistakes
  20. “Flight Path Animation” in NTSB Board Meeting Presentations: Air Midwest Flight 5481. Available
  21. Federal Aviation Administration
  22. Federal Aviation Administration
  23. “Appendix C: Air Midwest’s elevator control system rigging procedure at the time of the a…
  24. Operations 2 Attachment 5: Beechcraft 1900D load manifest and load report/worksheet. Nati…
  25. Federal Aviation Administration
  26. Aircraft Systems Engineering
  27. Airplane Performance
  28. Human Performance