If you wish to contribute or participate in the discussions about articles you are invited to join SKYbrary as a registered user

 Actions

Work in progress

Example article

From SKYbrary Wiki

Revision as of 10:50, 10 September 2018 by Editor1 (talk | contribs)
Article Information
Category: Ground Operations Ground Operations
Content source: SKYbrary About SKYbrary
Content control: SKYbrary About SKYbrary

Description

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.

Article Title

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:

Altitude Deviation

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.

Article Structure

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.

  • CRJ1, Lexington KY USA, 2006 (On 27 August 2006, a Bombardier CRJ100 cleared for a night take off from runway 22 instead began take off on unlit runway 26. It was too short and the aircraft ran off the end at speed and was destroyed by the subsequent impact and post-crash fire with the deaths of 49 of the 50 occupants - the First Officer surviving with serious injuries. The Investigation found that the actions of the flight crew had caused the accident but noted that insufficiently robust ATC procedures had been contributory and the effects of an ongoing runway extension project had been relevant.)
  • DHC6, Jomson Nepal, 2013 (On 16 May 2013, a DHC6-300 on a domestic passenger flight made a tailwind touchdown at excessive speed in the opposite direction of the of 740 metre-long runway to the notified direction in use and, after departing the runway to one side during deceleration, re-entered the runway and attempted to take off. This failed and the aircraft breached the perimeter fence and fell into a river. The Investigation identified inappropriate actions of the aircraft commander in respect of both the initial landing and his response to the subsequent runway excursion and also cited the absence of effective CRM.)
  • SW4, New Plymouth New Zealand, 2009 (A visual approach by a Swearingen SA227 at New Plymouth was rushed and unstable with the distraction of a minor propeller speed malfunction and with un-actioned GPWS warnings caused by excessive sink and terrain closure rates. After a hard touchdown close to the beginning of the runway, directional control was lost and the aircraft left the runway to the side before continuing parallel to it for the rest of the landing roll.)

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