Work in progress
From SKYbrary Wiki
Revision as of 10:50, 10 September 2018 by Editor1
First read the article [[Writing a SKYbrary Article]. This article is intended as a deeper and more pragmatic discussion regarding writing conventions, the structure of articles and some tips and example code that will be useful when writing SKYbrary articles.
If the title of an article is to include a commonly recognised abbreviation, always include the full name and add the abbreviation in brackets afterwards, e.g. Instrument Landing System (ILS).
The title of an article should reflect the terminology in use in Europe. Differences in terms between North America and Europe/Rest of World are addressed by ensuring that the North American terms are referred to in the body of the text - this way they will be picked up by search engines. For example take a look at the article on Level Bust; in this case the North American term is highlighted at the top of the article in a larger font like this:
This isn't absolutely necessary - the important thing is to endsure that alternative recognised terminology is referred to at some ;point in the main body text, usually within the Description.
Articles addressing an operational risk should conform to the same generic layout as shown in the exemplar article on Jet Stream. For other articles however, this may not be appropriate. In such cases, the article should always start with a Definition and/or a Description in which you explain what the article is about and also, where appropriate, what it is not about. The main body should then be structured in a logical way finishing with Related Articles (internal links) and Further Reading (external links and Bookshelf items).
Style and Language
SKYbrary articles are closer to an Encyclopaedia entry than a magazine article. The article must avoid references to future events as this makes the article look dated when viewed after those events have taken place. Article are written in UK English.
Accidents and Incidents
Any use of a previous accident or incident, to illustrate a safety point, must link to an existing event in SKYbrary's A&I event database. If the perfect illustration of a safety issue is an event currently not included in the database then a request should be made to the Content Manager to have the event included in the Database (this could take 3 months).
It is often very useful to include a dynamic query that will list all events in the SKYbrary A&I database that are relevant. e.g.
- GLF4, Bedford MA USA, 2014 (On 31 May 2014, a Gulfstream IV attempted to take off with the flight control gust locks engaged and, when unable to rotate, delayed initiating the inevitable rejected take off to a point where an overrun at high speed was inevitable. The aircraft was destroyed by a combination of impact forces and fire and all seven occupants died. The Investigation attributed the accident to the way the crew were found to have habitually operated but noted that type certification had been granted despite the aircraft not having met requirements which would have generated an earlier gust lock status warning.)
- B737, Southend UK, 2010 (On 21 Nov 2010, a Boeing 737-700 being operated by Arik Air on a non revenue positioning flight from Southend to Lagos with only the two pilots on board carried out a successful take off in daylight and normal ground visibility from runway 06 but became airborne only just before the end of the runway.)
- AT43, Madang Papua New Guinea, 2013 (On 19 October 2013, an ATR42 freighter departing Madang had to reject its takeoff when it was impossible to rotate and it ended up semi-submerged in a shallow creek beyond the airfield perimeter. The Investigation found that loading had been contrary to instructions and the aircraft had a centre of gravity outside the permitted range and was overweight. This was attributed to the aircraft operator’s lack of adequate procedures for acceptance and loading of cargo. A lack of appreciation by all parties of the need to effectively mitigate runway overrun risk in the absence of a RESA was also highlighted.)
For examples of what dynamic lists are available, take a look at the lists of events that accompany each Category e.g. Accident and Serious Incident Reports: AW