MaxAvSafety: Wkly Commercial RW Incident/Accident Rpt. 11/19/17

MaxSez: FYI, Posted Wkly as Professional Knowledge Gained. Pls add omitions,
first person accounts, related videos/photo’s and personal observations by comment.

Saturday Nov 18th 2017
Incident GoAir A20N at Delhi on Nov 18th 2017, bird strike
Incident Skywest CRJ2 near Grand Canyon on Nov 17th 2017, engine problem
Incident Mahan A306 at Yerevan on May 17th 2015, touched down before active runway threshold
Incident Virgin America A320 and Compass E175 at San Francisco on Feb 15th 2017, operational error leads to runway incursion
Incident MIAT B738 near Toulouse on Jun 8th 2016, loss of cabin pressure
Friday Nov 17th 2017
Incident Westjet B736 near Saskatoon on Oct 21st 2017, lavatory smoke indication
Incident Westjet Encore DH8D near Fort McMurray on Oct 24th 2017, sparks and flames in cockpit, shattered windshield
Report Mahan A306 near Shiraz on Jan 19th 2011, left pitot failure, pilot inputs cause 4.31G pulled in flight
Crash Khabarovsk L410 at Nelkan on Nov 15th 2017, impacted ground short of runway
Thursday Nov 16th 2017
Incident Canada A321 near New York on Oct 29th 2017, odour in cockpit
Incident Algerie B736 near Algiers on Nov 10th 2017, cabin pressure problems
Incident Skywest CRJ2 at Wilkes-Barre on Nov 15th 2017, unsafe gear
Incident Indigo A320 at Chennai on Nov 16th 2017, bird strike
Incident Azul E190 at Porto Seguro on Sep 22nd 2014, blew tyres on landing and overran runway
Incident Southwest B738 at Tampa on Nov 15th 2017, bird strike
Incident Hawaiian A332 at Seattle on Nov 7th 2017, engine fire on roll out
Incident PIA A320 near Multan on Oct 18th 2017, loss of cabin pressure
Incident Jetstar A320 over Tasman Sea on Oct 28th 2017, spitting engine
Incident Portugalia E190 at Nice on Nov 6th 2017, takeoff from taxiway rejected on ATC instruction
Incident MyCargo B744 at Maastricht on Nov 11th 2017, runway excursion on takeoff
Incident Privilege Style B752 at Palma Mallorca and Ibiza on Sep 4th 2015, landed below final fuel reserve
Accident Maldivian DHC6 at Dhoores on Nov 16th 2017, collided with object in water on takeoff
Wednesday Nov 15th 2017
Incident KLM Cityhopper E175 at Amsterdam on Nov 15th 2017, unsafe main gear
Incident UTAir AT72 near Krasnojarsk on Oct 26th 2017, smell of USB
Incident American A319 at Miami on Nov 14th 2017, goose in clinch with aircraft
Incident Algerie A332 at Oran on Oct 26th 2017, landed on closed runway
Incident Azur B752 at Goa on Nov 11th 2017, engine problem, passengers left behind but luggage on aircraft
Tuesday Nov 14th 2017
Accident British Airways B772 near London on Nov 13th 2017, fumes on board
Incident Ryanair B738 at Alghero on Nov 14th 2017, bird strike
Incident Delta B712 at Montreal on Nov 10th 2017, engine problem
Incident Westjet Encore DH8D at Kelowna on Nov 1st 2017, cabin pressure problem
Accident China Southern B738 near Changsa on Nov 13th 2017, cargo smoke indication
Incident Aeroflot A320 near Prague on Nov 11th 2017, first officer incapacitated
News UTAir B735 at Moscow on Nov 11th 2017, social media and a go around
Accident Flybe DH8D at Belfast on Nov 10th 2017, gear problem, landed without nose gear
Crash Iran Air B722 near Uromiyeh on Jan 9th 2011, impacted terrain during go-around
Report Tiger A320 at Sydney and Perth on Mar 3rd 2014, incorrect flight plan and fuel issues
Incident Indigo A320 at Vishakhapatnam on Nov 12th 2017, aircraft “airboarne”
Incident Egypt B738 near Frankfurt on Nov 13th 2017, cracked windshield
Monday Nov 13th 2017
Incident Thomas Cook Scandinavia A333 over Russia on Nov13th 2017, failure of weather radar
Incident GoAir A20N at Delhi on Feb 8th 2017, engine shut down in flight, engine fire confirmed by AIB, denied by DGCA
Incident Indigo A320 enroute on Nov 11th 2017, laptop aims for Guinness book of records
Incident LATAM Brasil A321 at Rio Branco on Nov 11th 2017, bird strike
Incident Argentinas B738 at Buenos Aires on Nov 11th 2017, drone strike
Accident Wings AT72 at Nabire on Nov 13th 2017, structural failure of nose gear
Incident AirAsia India A320 at Ranchi on Nov 11th 2017, cargo smoke indication
Sunday Nov 12th 2017
Incident Aerodynamics E145 near Little Rock on Nov 11th 2017, electrical problems
Accident Xiamen B738 at Zhengzou on Nov 10th 2017, flight attendant fell off aircraft
Incident Swiss RJ1H at London on Feb 9th 2017, engine fire
Saturday Nov 11th 2017
Incident Qatar A321 near Goa on Nov 11th 2017, captain falls ill
Accident Aria Air IL62 at Mashhad on Jul 24th 2009, overran the runway
Accident Amaszonas Uruguay CRJ2 at Montevideo on Nov 9th 2017, tyre explosion on the ground causes amputation of both legs of ground worker
(Source: Av Herald)

Significant:

  1. Incident: Virgin America A320 and Compass E175 at San Francisco on Feb 15th 2017, operational error leads to runway incursion
    By Simon Hradecky, created Saturday, Nov 18th 2017 18:53Z, last updated Saturday, Nov 18th 2017 18:53Z
    A Virgin America Airbus A320-200, registration N627VA performing flight VX-920 from San Francisco,CA to Las Vegas,NV (USA), was cleared to line up and wait runway 28L and was taxiing into position.

A Compass Airlines Embraer ERJ-175 on behalf of American Airlines, registration N214NN performing flight CP-6081/AA-6081 from Los Angeles,CA to San Francisco,CA (USA), was on final approach to San Francisco’s runway 28L at about 20:00L (04:00Z Feb 16th) when tower received an ASDE-X alert and instructed the Embraer to go around. The crew complied and went around from about 450 feet MSL. The aircraft positioned for another approach and landed safely on runway 28L about 12 minutes later.

On Nov 18th 2017 the NTSB reported night visual meteorological conditions prevailed. The occurrence was rated an incident and is being investigated. END

  1. Incident: Westjet Encore DH8D near Fort McMurray on Oct 24th 2017, sparks and flames in cockpit, shattered windshield
    By Simon Hradecky, created Friday, Nov 17th 2017 20:53Z, last updated Friday, Nov 17th 2017 20:53Z
    A Westjet Encore de Havilland Dash 8-400, registration C-FQWE performing flight WS-3177 from Calgary,AB to Yellowknife,NT (Canada) with 52 passengers and 4 crew, was enroute at FL250 about 90nm northwest of Fort McMurray,AB (Canada) when the crew heard a loud pop and observed sparks and flames from the right hand windshield. The crew declared emergency reported a cracked windshield and diverted the aircraft to Fort McMurray for a safe landing about 30 minutes later.

The Canadian TSB reported the crew heard a loud pop, saw sparks and flames from the right hand windshield and observed the windshield had shattered. The crew declared emergency and initiated a controlled descent to FL100, worked the related checklists and diverted to Fort McMurray for a safe landing. END

  1. Incident: Westjet Encore DH8D near Fort McMurray on Oct 24th 2017, sparks and flames in cockpit, shattered windshield
    By Simon Hradecky, created Friday, Nov 17th 2017 20:53Z, last updated Friday, Nov 17th 2017 20:53Z
    A Westjet Encore de Havilland Dash 8-400, registration C-FQWE performing flight WS-3177 from Calgary,AB to Yellowknife,NT (Canada) with 52 passengers and 4 crew, was enroute at FL250 about 90nm northwest of Fort McMurray,AB (Canada) when the crew heard a loud pop and observed sparks and flames from the right hand windshield. The crew declared emergency reported a cracked windshield and diverted the aircraft to Fort McMurray for a safe landing about 30 minutes later.

The Canadian TSB reported the crew heard a loud pop, saw sparks and flames from the right hand windshield and observed the windshield had shattered. The crew declared emergency and initiated a controlled descent to FL100, worked the related checklists and diverted to Fort McMurray for a safe landing. END

  1. Report: Mahan A306 near Shiraz on Jan 19th 2011, left pitot failure, pilot inputs cause 4.31G pulled in flight
    By Simon Hradecky, created Friday, Nov 17th 2017 17:14Z, last updated Friday, Nov 17th 2017 19:39Z
    A Mahan Air Airbus A300-600, registration EP-MNH performing flight W5-88 from Shiraz to Tehran Mehrabad (Iran) with 163 passengers and 12 crew, was climbing through FL120 when the captain (54, ATPL, 18,362 hours total, 8,123 hours on type), pilot monitoring, spotted light clouds ahead and activated engine anti-ice. The first officer (25, CPL, 3,411 hours total, 1,950 hours on type), pilot flying, had engaged autopilot 2. While the aircraft levelled off at FL160 the captain noticed a red flag on his primary flight display, the first officer provided control inputs to lower the nose, the autopilot disconnected, an overspeed warning activated for about 30 seconds, an EGPWS warning activated for about 6 seconds, the crew provided nose up inputs causing high G-loads up to +4.31G on the airframe and managed to stabilize the aircraft again. The crew continued the flight to Tehran, where the aircraft landed without further incident. There were no injuries, the aircraft sustained no damage although the trimmable horizontal stabilizer was replaced.

Iran’s CAO released their final report concluding the probable causes of the serious incident were:

The cause of Mahan Air A300-600, EP-MNH incident is an uncontrolled action by the pilot on controls, responding to an unreliable airspeed fault on ADC1.The crew did not follow up the unreliable airspeed procedure according to the operations manual.

contributive causes:

  • Weak cockpit resource management.

  • Technical defects on #1 Pitot heating system.END

  1. Incident: Privilege Style B752 at Palma Mallorca and Ibiza on Sep 4th 2015, landed below final fuel reserve
    By Simon Hradecky, created Wednesday, Oct 7th 2015 18:09Z, last updated Thursday, Nov 16th 2017 15:41Z
    A Privilege Style Boeing 757-200 on behalf of jet2.com, registration EC-ISY performing flight LS-58 from Manchester,EN (UK) to Palma Mallorca,SP (Spain) with 208 passengers and 8 crew, was descending towards Palma Mallorca when the crew needed to take a number of deviations around cloud while positioning for an ILS approach to runway 06L. On short final, descending through 500 feet AGL at 08:36Z and in visual contact with the runway, the aircraft encountered windshear, approximately 40 knots gain of airspeed, prompting the crew to go around. The aircraft climbed back to 6000 feet and positioned for a second approach to runway 06L. While on downwind and descending through 5200 feet the crew aborted the second approach about 10 minutes after aborting the first approach, climbed to FL100 and diverted to Menorca,SP (Spain). Enroute to Menorca while deviating around weather the crew was informed that there were go arounds in Menorca, too, the crew thus decided to turn around and divert to Ibiza,SP (Spain), declared Mayday due to low fuel and was cleared direct to the approach fix at Ibiza for an ILS approach to runway 24, was cleared for the approach about 29 minutes after the go around and landed without further incident on runway 24 touching down 37 minutes after the go-around with less than the final fuel reserve remaining.

On Oct 7th 2015 Spain’s CIAIAC reported they opened an investigation into the occurrence stating that storms with the occurrence of hail were battering the Balearic Islands that morning causing numerous go-arounds at Palma Mallorca, Menorca and Ibiza, 10 aircraft to Palma Mallorca diverted to other airports that morning. The CIAIAC reported there were four frustrated approaches to Palma Mallorca (editorial note: not supported by radar data and time line).

On Nov 16th 2017 the CIAIAC released their final report in Spanish concluding the probable causes of the incident were:

The incident occurred by landing the aircraft with an amount of fuel on board lower than the final reserve set out in the operational flight plan. As a result of the deterioration of the meteorological conditions the flight was significantly longer than scheduled and the diversions were not carried out in conditions as forecast.

The CIAIAC reported that the operational flight plan (OFP) had listed Menorca as well as Ibiza as alternate aerodromes. Given the weather forecasts the crew decided to uplift 1500 kg more fuel than computed on the OFP. The CIAIAC analysed that the OFP anticipated complex meteorologic conditions, the severity of which however could not be anticipated from the information available prior to departure nor enroute when updates were provided to the crew via ACARS.

At the time of arrival at Palma Mallorca the complex weather situation had already caused a number of go arounds. Menorca however was experiencing the same weather conditions and it was therefore not adviseable to divert to Menorca with the most active cells moving there.

The CIAIAC commended ATC for providing the recommendation to the crew: “Menorca is wrong, the storms are moving there too, storms are moving east hence Ibiza appear most feasable” which prompted the crew to change plans and divert to Ibiza. However, at this time the aircraft had already flown considerable distance towards Menorca and cut into the fuel reserve planned for a diversion from Palma Mallorca to Ibiza (directly). As result the aircraft landed with less than the final fuel reserve remaining. The OFP had estimated a flying time of 2:36 hours including the diversion to Ibiza, the aircraft however landed in Ibiza 3:03 hours after departure with 1093kg of fuel remaining, while the required final fuel reserve was 1,697kg.

No safety recommendations were issued as result of the investigation.END

  1. Accident: Maldivian DHC6 at Dhoores on Nov 16th 2017, collided with object in water on takeoff
    By Simon Hradecky, created Thursday, Nov 16th 2017 15:02Z, last updated Thursday, Nov 16th 2017 15:06Z
    A Maldivian de Havilland DHC-6-200 Twin Otter on floats, registration 8Q-IAG performing a flight from Dhoores Retreat Resort to Male (Maldives) with 12 passengers and 3 crew, was accelerating for takeoff when the right hand float collided with an object in the water and bent causing the aircraft to nearly keel over coming to a stop partially submerged with the cockpit under the water level. There were no injuries, the aircraft sustained substantial damage.

Maldives Civil Aviation Authority dispatched investigators on site and opened an investigation.

8Q-IAG being secured (Photo: Maldives Aviation Daily):
C013D7A7-3B70-4040-857C-FCB190A0CB22

  1. Report: Tiger A320 at Sydney and Perth on Mar 3rd 2014, incorrect flight plan and fuel issues
    By Simon Hradecky, created Tuesday, Nov 14th 2017 15:14Z, last updated Tuesday, Nov 14th 2017 15:14Z
    A Tiger Airways Australia Airbus A320-200, registration VH-VNJ performing flight TT-937 from Sydney,NS to Perth,WA (Australia) with 177 passengers, was preparing for departure from Sydney estimated to arrive in Perth shortly before night curfew. The operational flight plan was delivered to the flight crew with delay, the flight crew recognized that the flight plan had been in error being based only on the dry operating weight without including any payload and passengers. With the night curfew looming, the difficulties and additional delay needed to fetch a new flight plan at the terminal (which would have added a further delay of 20 minutes), the difficulties to raise the chief pilot (who did not respond to the phone calls), the captain decided first officer and he himself would recompute the fuel figures needed, they had correct data of the mass and balance data, and assessed, that instead of 9,261 kg of fuel as on the operational flight plan they’d need 13,500 kg of fuel. In addition the crew decided to apply increased monitoring of the fuel consumption during the flight, compute early their point at where they would be committed to land at the destination and ensure that weather conditions were favourable at that point too. Following the uplift of fuel topping up to 13,520 kg of fuel in the tanks the aircraft departed, the flight crew monitored the fuel consumption and was satisfied they could reach Perth with sufficient fuel to meet the (legal) requirements of final fuel reserve. The aircraft landed safely with 1,914 kg of fuel remaining in the tanks (minimum fuel remaining was required at 1,139 kg).

Australia’s TSB released their final report reporting the correct fuel amount should have been at least 15,343kg and concluding the most probable causes of the incident were:

Contributing factors

  • On identifying that the operational flight plan for the Sydney to Perth sector had been based on an incorrect aircraft weights, resulting in the fuel calculation and subsequent fuel plan being significantly in error, the aircraft captain chose to re-calculate the required fuel load using resources available on the flight deck. The required fuel load calculated and uplifted did not include the operator’s requirement to carry a ‘60 minute top-up’ additional fuel, resulting in the aircraft departing with a fuel load that was below that required under the company’s operations manual. END
  1. Incident: Indigo A320 at Vishakhapatnam on Nov 12th 2017, aircraft “airboarne”
    By Simon Hradecky, created Tuesday, Nov 14th 2017 14:38Z, last updated Tuesday, Nov 14th 2017 14:38Z
    An Indigo Airbus A320-200, registration VT-IDN performing flight 6E-742 from Vishakhapatnam to Hyderabad (India) with 159 people on board, was accelerating for takeoff from Vishakhapatnam’s runway 10 when during the final stages of the takeoff run the crew observed a wild boar on the runway. Being unable to deviate around the boar the crew decided to rotate the aircraft early, the crew decided to return to the airport to have the aircraft checked for any possible damage. The aircraft levelled off at 8000 feet, burned off fuel and landed safely back on Vishakhapatnam’s runway 10 about one hour after departure.

An examination revealed no damage, the aircraft was refueled and departed again as flight 6E-742D about 2 hours after landing and reached Hyderabad with a delay of 3 hours.

The airline reported the crew could not have rejected takeoff in time nor steered the aircraft to avoid the wild boar, hence rotated early being forced to take the aircraft airborne. The crew decided to return to have the aircraft assessed for any damage, the aircraft departed again following that check.END

5 Likes

Nice report again Max!

But why are some of these from 2011 and others from years ago. Also where is the one about the Air-Crash in England that happened?

1 Like

Because on AvHerald (where he gets them), they are in order of when they updated the article, so if they updated an old article today, it would be at the top.

2 Likes

Okay then. I understand.

1 Like

@Liam_Kirk… MaxSez: FYI, Dated data is normally the results of formal investigation board results. Thus published upon public disclosure.
On the “ crash” unfortunately with out detail I’m unable to respond, my crystal ball is in maintenance. Google is your friend.

WARNING: The information transmitted herewith is personal & sensitive information intended only for use to the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any negitive review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this communication is strictly prohibited. If you are not the addressee and read this communication in error, please apologize to the sender forthwith by the most expeditious means available. (LOL)

2 Likes

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.