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

 Actions

Difference between revisions of "Accident and Serious Incident Reports: UAS"

From SKYbrary Wiki

(Created page with "{{Infobox Fire |source = SKYbrary |source_image = SKYbrary |source_caption = About SKYbrary |control = SKYbrary |control_image = SKYbrary |con...")
 
 
(2 intermediate revisions by one other user not shown)
Line 1: Line 1:
{{Infobox Fire
+
{{Infobox Unmanned Aerial Systems
 
|source            = SKYbrary
 
|source            = SKYbrary
 
|source_image      = SKYbrary
 
|source_image      = SKYbrary
Line 10: Line 10:
 
Accident and Incident Reports relating to accidents which involved [[Unmanned Aerial Systems]]
 
Accident and Incident Reports relating to accidents which involved [[Unmanned Aerial Systems]]
  
==Non-Fire Fumes==
+
==List of events on SKYbrary==
{{#ask: [[General::Unmanned Aircraft Involved]]
+
{{#ask: [[GeneralSub::Unmanned Aircraft Involved]]
 
|?Synopsis=
 
|?Synopsis=
 
|format=ul
 
|format=ul

Latest revision as of 05:28, 29 April 2020

Article Information
Category: Unmanned Aerial Systems Unmanned Aerial Systems
Content source: SKYbrary About SKYbrary
SKYbrary SKYbrary About SKYbrary

Definition

Accident and Incident Reports relating to accidents which involved Unmanned Aircraft Systems

List of events on SKYbrary

  • Predator B, vicinity Nogales USA, 2006 (On April 25, 2006 a Predator B an unmanned aerial vehicle (UAV), collided with the terrain following a loss of engine power approximately 10 nautical miles northwest of the Nogales International Airport, Nogales, Arizona.)
  • UAV, manoeuvring, north of Reims France, 2006 (On 29 February 2016, control of a 50 kg, 3.8 metre wingspan UAV was lost during a flight test being conducted in a Temporary Segregated Area in northern Belgium. The UAV then climbed to 4,000 feet and took up a south south-westerly track across Belgium and into northern France where it crash-landed after the engine stopped. The Investigation found that control communications had been interrupted because of an incorrectly manufactured co-axial cable assembly and a separate autopilot software design flaw not previously identified. This then prevented the default recovery process from working. A loss of prescribed traffic separation was recorded.)