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 "Main Page"

From SKYbrary Wiki

Line 56: Line 56:
 
{| style="width:99%; border:0px solid #aaa;" border="0" cellpadding="5" cellspacing="2" align="center"
 
{| style="width:99%; border:0px solid #aaa;" border="0" cellpadding="5" cellspacing="2" align="center"
 
|-
 
|-
| <span style="font-size:medium; font-weight:normal;">[[A320, vicinity Naha Okinawa Japan, 2014|Complete lack of situational awareness and failure of monitoring at a self evidently critical stage of flight]]</span>
+
| <span style="font-size:medium; font-weight:normal;">[[B737, Gran Canaria Spain, 2016|Knowing that a runway is closed, would you not question a clearance to take off from it?]]</span>
<span style="color:#AAAAAA;"><sup>posted 10 April 2017 in [[:Category:Accidents and Incidents]]</sup></span>
+
<span style="color:#AAAAAA;"><sup>posted 17 April 2017 in [[:Category:Accidents and Incidents]]</sup></span>
  
On 28 April 2014, an aircraft making a precision radar approach in IMC began descent from 1,000 feet QNH at 6nm from touchdown with the autopilot engaged and continued it until successive EGPWS 'PULL UP' Warnings occurred. Minimum recorded radio height was 242 feet with neither the sea nor the runway in sight.
+
On 7 January 2016, an aircraft was inadvertently cleared by ATC to take off on a closed runway. The take-off was commenced with a vehicle visible ahead at the runway edge. Investigation attributed the controller error to "lost situational awareness" and noted that the pilots had, on the basis of the take-off clearance, crossed a lit red stop bar to enter the runway without explicit permission.
  
<div style="text-align:right;">[[A320, vicinity Naha Okinawa Japan, 2014|'''''Read more >>''''']]</div>
+
<div style="text-align:right;">[[B737, Gran Canaria Spain, 2016|'''''Read more >>''''']]</div>
 
|}
 
|}
 
|-
 
|-

Revision as of 14:16, 14 April 2017

Operational
Issues
Human
Performance
Enhancing
Safety
Safety
Regulations
Air Ground Communication Airspace Infringement Bird Strike Controlled Flight Into Terrain Fire Smoke and Fumes
Air Ground Communication Airspace Infringement Bird Strike Controlled Flight Into Terrain Fire Smoke & Fumes
Ground Operations Airworthiness Level Bust Loss of Control Loss of Separation
Ground Operations Airworthiness Level Bust Loss of Control Loss of Separation
Runway Excursion Runway Incursion Wake Vortex Turbulence Weather Emergency and Contingency
Runway Excursion Runway Incursion Wake Vortex Turbulence Weather Emergency and Contingency
Highlighted Article
Knowing that a runway is closed, would you not question a clearance to take off from it?

posted 17 April 2017 in Category:Accidents and Incidents

On 7 January 2016, an aircraft was inadvertently cleared by ATC to take off on a closed runway. The take-off was commenced with a vehicle visible ahead at the runway edge. Investigation attributed the controller error to "lost situational awareness" and noted that the pilots had, on the basis of the take-off clearance, crossed a lit red stop bar to enter the runway without explicit permission.

Follow us
Newsletter Facebook LinkedIN Twitter
References
Accidents and Incidents browser
Airport Directory
Aircraft Types
CAST Safety Enhancement Plan
Thematic
Single European Sky
EUROCONTROL Training Zone
General Aviation
Go-Around Safety
Airborne Conflict
Automation and Safety
Safety Nets
Preventing Runway Collisions New
Toolkits
SKYclips New
Systems Thinking for Safety
AllClear?
Airspace Infringement Prevention
Stabilised Approach Awareness Toolkit for ATC
Flight Deck Procedures - A Guide for Controllers
Level Bust Toolkit
TCAS Awareness
Just Culture Toolkit
Contributed by.pngEurocontrol logo white 50.gif.pngIcao logo white 50.pngFSF logo white 50.gif.png60px-Air Pilots logo white 50.pngRMETS logo white 50.pngLogo SMICG.gif.pngCAST logo white 50.gif.png