Key Lime Metro II involved in mid-air collision with Cirrus SR22 near Denver

Key Lime Metro II involved in mid-air collision with Cirrus SR22 near Denver

————

The content for this post was sourced from www.Aviation-Safety.net

View the Original Article

Biocide fuel contamination cause of A321 emergency at London-Gatwick

Biocide fuel contamination cause of A321 emergency at London-Gatwick

————

The content for this post was sourced from www.Aviation-Safety.net

View the Original Article

Unstable approach led to DHC-8-300 hard landing and tailstrike, Canada

Unstable approach led to DHC-8-300 hard landing and tailstrike, Canada

In its newly released investigation report the Transportation Safety Board of Canada (TSB) found that the January 2020 hard landing and tailstrike of a DHC-8-300 in Schefferville, Canada, was the result of an unstable approach.

On 20 January 2020, a DHC-8-314 operated by Air Inuit was conducting a flight from Québec-Jean Lesage Airport, to Schefferville Airport, with three crew members and 42 passengers on board. During the landing, the rear fuselage struck the runway as the wheels touched down. After landing, the aircraft taxied to the terminal to disembark the passengers. There were no injuries; however, the aircraft sustained substantial damage.

The investigation found that the flight crew forgot to perform the descent checklist and realized this at an inopportune time, while the captain (pilot monitoring) was providing a position report. Given ambiguities and contradictions in the company’s stabilized approach guidelines, the captain interpreted that he was allowed to continue the approach below 500 feet above aerodrome elevation, even though the aircraft had not been fully configured for the landing. When the aircraft passed this altitude, the pilots, who were dealing with a heavy workload, didn’t notice and continued the approach, which was unstable. At the time of the landing, the aircraft no longer had enough energy to arrest the descent rate solely by increasing pitch attitude. The pilot’s instinctive reaction to increase the pitch attitude during the flare, combined with the hard landing, resulted in the rear fuselage striking the runway, causing substantial damage to the aircraft’s structure.

The investigation also made findings as to risk related to Air Inuit’s standard operating procedures (SOPs) and training, and to Transport Canada’s (TC) oversight. Transport Canada assessed Air Inuit’s SOPs, but did not identify any specific issues with the operator’s stabilized approach guidelines. If TC does not assess the quality, consistency, accuracy conciseness, clarity, relevance, and content of SOPs, the procedures may be ineffective, increasing risks to flight operations.

Additionally, the captain had not received many of the required training elements during his recurrent training. If required training elements are not included in recurrent training, and if TC’s surveillance plan does not verify the content of crew training, there may be procedural deficiencies or deviations, increasing risks to flight operations.  

Following the occurrence, Air Inuit took a number of safety actions, including the revision of its SOPs to improve guidelines on several subjects, including stabilized approaches, and the revision of its training program to ensure that all training elements are covered within the two-year recurrent training cycle.

Estimated flight path of AIE820 (altitude above sea level, in feet, and remaining distance of the approach path, in statute miles) (Source: Google Earth, with TSB annotations)

The post Unstable approach led to DHC-8-300 hard landing and tailstrike, Canada appeared first on ASN News.

————

The content for this post was sourced from www.Aviation-Safety.net

View the Original Article

FLIGHT ADVISORY – TFR ALERT – SPACE LAUNCH- BOCA CHICA, TX

FLIGHT ADVISORY – TFR ALERT – SPACE LAUNCH

BOCA CHICA, TX

 

May 03, 2021

 

 

*Sunday, May 03, 2021

1200Z – 0100Z

SFC – UNL

 

There may be multiple NOTAMs

*PENDING LAUNCH AUTHORIZATION.

 

Pilots are advised to check NOTAMs frequently for possible changes prior to operations in the area.

NOTAMs will be published at least 24 hours in advance of movement.