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 33: Line 33:
 
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).
 
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.
+
It is often very useful to include a dynamic query that will list all events in the SKYbrary A&I database that are tagged with a relevant tag. e.g. a list of all events that tagged as Overrun on Take Off
  
 
{{#ask: [[RE::Overrun on Take Off]]
 
{{#ask: [[RE::Overrun on Take Off]]
Line 42: Line 42:
 
|limit=3}}
 
|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]]
+
A lists of events that accompany each Category e.g. [[Accident and Serious Incident Reports: AW]] is an easy source of the code needed to set up a query. More sophisticated queries are possible e.g. that show a particular kind of event that occurred in a specific phase of flight.
 +
 
 +
==Images==
 +
 
 +
Images on SKYbrary are presented in the following way:
 +
 
 +
[[File:A139_2010_ditched.jpg|thumb|none|500px|The helicopter floating in Victoria Harbour (Reproduced from the Official Report)]]
 +
 
 +
When uploading images, ensure that the size of the image is below 1mb in size.
 +
 
 +
==Tables==
 +
 
 +
Constructing tables is complex and takes a certain amount of patience. Here is an example of a tables whose code can be used as a template:
 +
 
 +
{|{{Prettytable}}
 +
|'''L/N/P/P*'''
 +
|'''Morse'''
 +
|'''L/N/P/P'''
 +
|'''Morse'''
 +
|'''L/N/P/P'''
 +
|'''Morse'''
 +
|'''L/N/P/P'''
 +
|'''Morse'''
 +
|-
 +
|A (a)
 +
!<font size=5>· − 
 +
|B (b)
 +
!<font size=5>  −· · · 
 +
|C (c)
 +
!<font size=5> −· −· 
 +
|D (d)
 +
!<font size=5>−· ·  
 +
|-
 +
|E (e)
 +
!<font size=5>· 
 +
|F (f)
 +
!<font size=5>  · ·−· 
 +
|G (g)
 +
!<font size=5> − −· 
 +
|H (h)
 +
!<font size=5>· ·· ·  
 +
|-
 +
|I (i)
 +
!<font size=5>· · 
 +
|J (j)
 +
!<font size=5>·  −  −  −
 +
|K (k)
 +
!<font size=5> − · −
 +
|L (l)
 +
!<font size=5>· − · ·  
 +
|-
 +
|M (m)
 +
!<font size=5>−− 
 +
|N (n)
 +
!<font size=5>  −· 
 +
|O (o)
 +
!<font size=5> − −−
 +
|P (p)
 +
!<font size=5>· −−·  
 +
|-
 +
|Q (q)
 +
!<font size=5> −−· − 
 +
|R (r)
 +
!<font size=5> ·   −·   
 +
|S (s)
 +
!<font size=5> ·· · 
 +
|T (t)
 +
!<font size=5>−
 +
|-
 +
|U (u)
 +
!<font size=5>··  −
 +
|V (v)
 +
!<font size=5>· · ·   −
 +
|W (w)
 +
!<font size=5>   · − − 
 +
|X (x)
 +
!<font size=5>− · ·− 
 +
|-
 +
|Y (y)
 +
!<font size=5>−· − −
 +
|Z (z)
 +
!<font size=5>  −−· · 
 +
|
 +
!<font size=5> 
 +
|
 +
!<font size=5>
 +
|-
 +
|1
 +
!<font size=5>· − −−−
 +
|2
 +
!<font size=5>··  −−−
 +
|3
 +
!<font size=5>· ·· −−
 +
|4
 +
!<font size=5>··· · −
 +
|-
 +
|5
 +
!<font size=5>· ·  · · · 
 +
|6
 +
!<font size=5>  −· · · · 
 +
|7
 +
!<font size=5> − −· · · 
 +
|8
 +
!<font size=5> − −−· ·   
 +
|-
 +
|9
 +
!<font size=5> − −−−· 
 +
|0
 +
!<font size=5> − −−−−
 +
|
 +
!<font size=5> 
 +
|
 +
!<font size=5>
 +
|-
 +
|Period ['''.''']
 +
!<font size=5> ·−  ·−  ·− 
 +
|Comma [''',''']
 +
!<font size=5>  − −  ··−  − 
 +
|Question ['''?''']
 +
!<font size=5> ·  · − −· · 
 +
|Exclamation ['''!''']
 +
!<font size=5> ·−  ·−  − −   
 +
|-
 +
|Parenthesis Open ['''(''']
 +
!<font size=5> −  ·−  −  ·
 +
|Parenthesis Close [''')''']
 +
!<font size=5>  −·−  −   ·− 
 +
|Colon [''':''']
 +
!<font size=5> − − −· · · 
 +
|Semi Colon [''';''']
 +
!<font size=5>−  · −  ·−  ·
 +
|-
 +
|Start
 +
!<font size=5>  −·  −·  −
 +
|End of Work
 +
!<font size=5>   · · ·   −·  −
 +
|New Page
 +
!<font size=5>  ·  −·  −·  
 +
|Wait
 +
!<font size=5>·  −· ·   ·  
 +
|-
 +
|Understood
 +
!<font size=5> · · ·   −·
 +
|Error
 +
!<font size=5>· ·  · · · · ·  · 
 +
|
 +
!<font size=5>
 +
|
 +
!<font size=5> 
 +
|-
 +
|}

Revision as of 13:58, 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 tagged with a relevant tag. e.g. a list of all events that tagged as Overrun on Take Off

  • B772, St Kitts West Indies, 2009 (On 26 September 2009, the crew of a British Airways Boeing 777-200 unintentionally began and completed their take off in good daylight visibility from the wrong intermediate runway position with less than the required take off distance available. Due to the abnormally low weight of the aircraft compared to almost all other departures by this fleet, the aircraft nevertheless became airborne just before the end if the runway. The investigation attributed the error to a poorly marked taxiway and the failure of the crew to include the expected taxi routing in their pre flight briefing.)
  • 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.)
  • B732, Pekanbaru Indonesia, 2002 (On 14 January 2002, a Boeing 737-200, operated by Lion Air, attempted to complete a daylight take off from Pekanbaru, Indonesia without flaps set after a failure to complete the before take off checks. The rejected take off was not initiated promptly and the aircraft overran the runway. The take off configuration warning failed to sound because the associated circuit breaker was so worn that it had previously auto-tripped and this had not been noticed.)

A lists of events that accompany each Category e.g. Accident and Serious Incident Reports: AW is an easy source of the code needed to set up a query. More sophisticated queries are possible e.g. that show a particular kind of event that occurred in a specific phase of flight.

Images

Images on SKYbrary are presented in the following way:

The helicopter floating in Victoria Harbour (Reproduced from the Official Report)

When uploading images, ensure that the size of the image is below 1mb in size.

Tables

Constructing tables is complex and takes a certain amount of patience. Here is an example of a tables whose code can be used as a template:

L/N/P/P* Morse L/N/P/P Morse L/N/P/P Morse L/N/P/P Morse
A (a) · −  B (b)   −· · ·  C (c)  −· −·  D (d) −· ·  
E (e) ·  F (f)   · ·−·  G (g)  − −·  H (h) · ·· ·  
I (i) · ·  J (j) ·  −  −  − K (k)  − · − L (l) · − · ·  
M (m) −−  N (n)   −·  O (o)  − −− P (p) · −−·  
Q (q)  −−· −  R (r)  ·   −·    S (s)  ·· ·  T (t)
U (u) ··  − V (v) · · ·   − W (w)    · − −  X (x) − · ·− 
Y (y) −· − − Z (z)   −−· · 
1 · − −−− 2 ··  −−− 3 · ·· −− 4 ··· · −
5 · ·  · · ·  6   −· · · ·  7  − −· · ·  8  − −−· ·   
9  − −−−·  0  − −−−−
Period [.]  ·−  ·−  ·−  Comma [,]   − −  ··−  −  Question [?]  ·  · − −· ·  Exclamation [!]  ·−  ·−  − −   
Parenthesis Open [(]  −  ·−  −  · Parenthesis Close [)]   −·−  −   ·−  Colon [:]  − − −· · ·  Semi Colon [;] −  · −  ·−  ·
Start   −·  −·  − End of Work    · · ·   −·  − New Page   ·  −·  −·   Wait ·  −· ·   ·  
Understood  · · ·   −· Error · ·  · · · · ·  ·