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

Difference between revisions of "Example article"

From SKYbrary Wiki

Line 23: Line 23:
 
==Article Structure==
 
==Article Structure==
  
Articles should conform to the same generic layout as shown in the exemplar article on [[Jet Stream]]
+
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.
 +
 
 +
{{#ask: [[RE::Overrun on Take Off]]
 +
|?Synopsis=
 +
|format=ul
 +
|order=random
 +
|searchlabel=
 +
|limit=3}}
 +
 
 +
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]]

Revision as of 10:50, 10 September 2018

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.

  • B763, Manchester UK, 2008 (On 13 December 2008, a Thomsonfly Boeing 767-300 departing from Manchester for Montego Bay Jamaica was considered to be accelerating at an abnormally slow rate during the take off roll on Runway 23L. The aircraft commander, who was the pilot not flying, consequently delayed the V1 call by about 10 - 15 because he thought the aircraft might be heavier than had been calculated. During the rotation the TAILSKID message illuminated momentarily, indicating that the aircraft had suffered a tail strike during the takeoff. The commander applied full power and shortly afterwards the stick shaker activated briefly. The aircraft continued to climb away and accelerate before the flaps were retracted and the after-takeoff check list completed. The appropriate drills in the Quick Reference Handbook (QRH) were subsequently actioned, fuel was dumped and the aircraft returned to Manchester for an overweight landing without further incident.)
  • FA20, Durham Tees Valley UK, 2012 (On 9 August 2012, a serviceable Cobham Leasing Fan Jet Falcon overran the 2291 metre long runway at Durham Tees Valley after beginning rejecting take off from above V1 because of a suspected bird strike. The crew believed there was a possibility of airframe damage from a single medium sized bird sighted ahead which might have been hit by the main landing gear. It was found that the overrun distance had been increased by low friction on the stopway and noted that the regulatory exemption issued for operation without FDR and CVR was no longer appropriate.)
  • CL60, Teterboro USA, 2005 (On 2 February 2005, a Challenger, belonging to Platinum Jet Management, crashed after taking off from Teterboro, New Jersey, USA. The aircraft's center of gravity was well forward of the forward takeoff limit.)

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