PPRuNe Forums - View Single Post - Plain English in incident reports, please
Old 15th March 2019 | 12:15
  #1 (permalink)  
Judd
 
Joined: Oct 2007
Posts: 386
Likes: 4
From: Here and there
Plain English in incident reports, please

Officialese is creeping more and more into aviation vocabulary. It is stilted and frequently annoying. Read the waffle below. "Threats Errors and Undesired aircraft states and Outcomes", for example.
TEM is an attempt to develop a mind-set which enhances the identification of threats, minimizes the opportunities for error, and resolves those errors when they do occur. The TEM model has three basic components: Threats Errors, and Undesired aircraft states If threats, errors and undesired aircraft states are not recognised and managed in time, an accident or incident may result. In the TEM model this final event is called an outcome.

Instead of expressing themselves in plain English language, we see pilots aping officialese terminology when writing incident reports. For example on NASA's ASR site there was a report submitted by the captain of a Boeing 737MAX that talked about "an autopilot anomaly in which led to an undesired brief nose down situation."
In a self congratulatory report, the captain wrote: 'Systems and Procedures coupled with CRM trapped and mitigated the issue."
All I can say is WTF?.
Judd is offline  
Reply