MaxAvSafety: Wkly RW Commercial Incident/Accident Report 11/23/17

MaxSez: Provided Wkly as Professional Knowledge Gained. Pls add related comments, inside and related photo’s/video’s.

Thursday Nov 23rd 2017
Crash Khabarovsk L410 at Nelkan on Nov 15th 2017, impacted ground short of runway, right propeller went into reverse in flight
Incident Argentinas A343 enroute on Nov 14th 2017, engine trouble
Incident Vueling A320 near Marseille on Nov 17th 2017, both flight crew seriously "inconvenienced"
Incident Fedex A306 at Denver on Nov 21st 2017, engine failure
Incident Eurowings A319 near Cologne on Nov 20th 2017, air conditioning problem prompts cabin crew to don smoke hood
Incident Meridiana B762 near Mauritius on Nov 13th 2017, engine shut down in flight
Incident Jet Airways B738 near Ahmedabad on Nov 21st 2017, cargo smoke indication
Wednesday Nov 22nd 2017
Incident Ata MD83 at Tehran on May 8th 2017, runway incursion forces departing F100 to climb over the MD83
Accident Virgin Australia AT72 at Canberra on Nov 19th 2017, hard landing and tail strike
Incident Indonesia AirAsia A320 near Perth on Oct 15th 2017, loss of cabin pressure
Tuesday Nov 21st 2017
Incident British Airways B789 near Copenhagen on Nov 21st 2017, fire in cabin
Incident Lufthansa A346 near Chicago on Nov 20th 2017, cabin temperature problems
Incident Delta B764 over Atlantic on Nov 13th 2017, smoke and fumes in cockpit
Incident Transavia B737 near Amsterdam on Nov 21st 2017, cabin pressure problems
Incident Nepal A320 at Kathmandu on Nov 18th 2017, the eagle has blended
Incident Budapest E120 at Savonlinna on Nov 21st 2017, could not retract landing gear
Incident Easyjet A319 near Brest on Nov 20th 2017, loss of cabin pressure, smell of smoke in cabin
Incident Atrak A320 at Tehran on Aug 13th 2016, rejected takeoff due to runway excursion
Monday Nov 20th 2017
Incident KLM B773 near Nice on Nov 20th 2017, cargo smoke indication
Incident Europa E195 at Madrid on Nov 19th 2017, rejected takeoff due to uncommanded yaw
Incident JAL B788 near San Francisco on Nov 19th 2017, electrical problems
Incident Avior B732 near Manta on Nov 19th 2017, engine shut down in flight, loss of cabin pressure
Incident American B789 near Quebec City on Nov 8th 2017, cracked windshield
Incident American A321 at Philadelphia on Nov 17th 2017, bird strike
Incident Skywest CRJ2 near Grand Canyon on Nov 17th 2017, engine problem
Accident Horizon DH8D at Sacramento on Nov 19th 2017, bird strike
Report Indigo A320 at Kolkata on Jul 14th 2015, hard landing at +3.1G
Incident Singapore A333 at Yangon on May 21st 2014, temporary runway excursion on landing
Sunday Nov 19th 2017
Incident KLM B744 near Los Angeles on Nov 18th 2017, engine vibrations
Incident Mango B738 at Johannesburg on Nov 19th 2017, bird strike
Report Click IL76 near Zahedan on Jul 2nd 2008, uncontained engine failure causes adjacent engine fire
Saturday Nov 18th 2017
Incident GoAir A20N at Delhi on Nov 18th 2017, bird strike
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
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 gears.

(Source: AvHerald)

17 Likes

Ouch, that must’ve have been a pretty uncomfortable ride for all of those passangers to go through.

2 Likes

Fedex A306 at Denver on Nov 21st 2017, engine failure

Hmm wonder what happened here.🤔

@Blizzard. MaxSez: This was a Final Incidant Report. Interesting conclusion.
Pilot Error a contributing factor.

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.

The CAO reported that following the flight the aircraft was grounded due to the high G-Loads of up to 4.31G experienced in flight. A subsequent inspection of the airframe did not reveal any damage or anomaly, however, Airbus advised Mahan Air to replace the trimmable horizontal stabilizer, which the airline complied with.

The CAO reported significant weather was forecast near Shiraz with thunderstorms up to FL180 and icing conditions between FL110 and FL180.

The cockpit voice recorder was overwritten until the time of landing. The flight data recorder was downloaded and revealed, that the unreliable airspeed event began when the aircraft climbed through 15,840 feet with the IAS reducing from 271 KIAS to 191 KIAS, while the speed over ground remained at 345 knots. Autothrust accelerated the engines from 96 to 106% N1. At 16,372 feet MSL a large nose down input was recorded, autopilot 2 disconnected, the pitch changed from 7 degrees nose up to 2 degrees nose down, autothrust was disconnected, the IAS further decreased to 33 KIAS with the speed over ground still being at 345 knots, the speed over ground began to increase and reached 414 knots, the engines reduced from about 105% to 93% N1, the stab trim changed from +2.6 degrees to +0.4 degrees, the pitch reached 18 degrees nose down, ground speed 411 knots, the pitch decreased further to 27 degrees nose down, the EGPWS issued a warning. A large nose up input was recorded, the engines accelerated to 106/110% N1, at 12,130 feet MSL, 415 knots over ground, the aircraft encountered +4.31G and began to climb again. 18 seconds later the aircraft levelled off at FL150 at 338 KIAS and continued the flight to Tehran within normal operating limits.

A post flight examination of the left pitot tube showed, that the insulation between heater resistance and pitot case was breached causing an intermittent continuity between heater resistance and pitot case. Both Air Data Computers were examined as well with no findings.

The CAO analysed that the overspeed warning was legitimate and obviously originated from ADC#2 (right hand pitot system) while the ADC#1 showed 33 knots IAS. The overspeed warning would be triggered if either of the ADCs exceeds 339 KIAS. It thus also followed that ADC#2 data including IAS and TAS remained valid throughout the event, and the IAS recorded on the flight data recorder came from ADC#1.

The CAO analysed that the autopilot 2 dropped offline as result of a large nose down input.

The CAO analysed that the autothrust disconnects if the IAS exceeds 511 knots or becomes invalid. Autothrust receives its input from ADC#1 even if autopilot 2 is engaged. Autothrust therefore disengaged due to invalid airspeed (from ADC#1).

The CAO further analysed the pitch trim was caused by manual crew input.

Due to the pitch trim and the elevator inputs the trimmable horizontal stabilizer produced a torque moment that reached 173% of its design limit. The fuselage loads as well as the engine loads remained near their design limits, the engine pylon loads remained below their design limits.

3 Likes

Can you provide more info about this incident?
Thanks.

2 Likes

@AllegiantAir. MaxSez: RTB, Good Call by the crew.

Incident: Fedex A306 at Denver on Nov 21st 2017, engine failure
By Simon Hradecky, created Thursday, Nov 23rd 2017 01:50Z, last updated Thursday, Nov 23rd 2017 01:50Z
A Fedex Federal Express Airbus A300-600, registration N653FE performing freight flight FX-1352 from Denver,CO to Memphis,TN (USA) with 2 crew, was climbing out of Denver’s runway 17R when the crew stopped the climb at 10,000 feet MSL reporting an engine (CF6) failure, the engine recovered and appeared to be operating normally again but they wouldn’t take a risk. The crew declared emergency and returned to Denver for a safe landing on runway 17R about 15 minutes after departure. The aircraft taxied to the apron.

The aircraft remained on the ground for about two hours, then departed again but flew to Los Angeles,CA (USA) still as flight FX-1352.

1 Like

@Kiz. MaxSez: Probabble Lithium Batt incidant, Source News

Incident: British Airways B789 near Copenhagen on Nov 21st 2017, fire in cabin
By Simon Hradecky, created Tuesday, Nov 21st 2017 23:04Z, last updated Tuesday, Nov 21st 2017 23:04Z
A British Airways Boeing 787-900, registration G-ZBKN performing flight BA-39 from London Heathrow,EN (UK) to Beijing (China), was enroute at FL370 about 35nm south of Copenhagen (Denmark) when the crew decided to turn around and return to London reporting there had been some electrical fire in the cabin, which had been extinguished. The aircraft returned to Heathrow for a safe landing on runway 27R about 100 minutes later.

2 Likes

Are you able to elaborate on this one @Maxmustang?

I often feel inconvenienced by having to work for a living. Whatever it was I’m sure it was worth it. Especially if it got them a few hours in Marseille…:)
Cheers for the report.

1 Like

What happened here? bird strike?

@Al1983. Max Sez: As Requested, Bottom Line per local press., Possible food associated, they both got the trots.

Incident: Vueling A320 near Marseille on Nov 17th 2017, both flight crew seriously "inconvenienced"
By Simon Hradecky, created Thursday, Nov 23rd 2017 14:57Z, last updated Thursday, Nov 23rd 2017 14:57Z
A Vueling Airbus A320-200, registration EC-HQJ performing flight VY-6204 from Geneva (Switzerland) to Barcelona,SP (Spain), was enroute at FL290 about 60nm north of Marseille (France) when the crew declared emergency and diverted to Marseille for a safe landing about 22 minutes later.

The French BEA reported the occurrence was rated a serious incident and is being investigated. The crew felt strongly “inconvenienced” after climbing through FL100 out of Geneva, donned their oxygen masks, subsequently declared emergency and diverted to Marseille. Passengers and cabin crew were not inconvenienced.

2 Likes

@Owen_Anderson MaxSez: As Requested: Stuff Happens, A lucky Strike!

Incident: Nepal A320 at Kathmandu on Nov 18th 2017, the eagle has blended
By Simon Hradecky, created Tuesday, Nov 21st 2017 21:40Z, last updated Tuesday, Nov 21st 2017 21:40Z
A Nepal Airlines Airbus A320-200, registration 9N-AKX performing flight RA-206 from Delhi (India) to Kathmandu (Nepal) with 135 people on board, was on approach to Kathmandu’s runway 02 instructed to maintain minimum approach speed when an eagle impacted the nose of the aircraft, momentarily blended with the nose section causing a large dent and dropped off. The aircraft continued for a safe landing on runway 02 a few minutes later.

The aircraft remained on the ground in Kathmandu for about 83 hours before returning to service.

9N-AKX seen on the ground in Kathmandu (Photo: Susheel Bhattarai):

2 Likes

Oh man, the eagle made a big dent!, Thanks for giving more info!

1 Like

More information please.

@Josh_Tomaz. MaxSez:: As Requested:

Incident: Mango B738 at Johannesburg on Nov 19th 2017, bird strike
By Simon Hradecky, created Sunday, Nov 19th 2017 18:12Z, last updated Sunday, Nov 19th 2017 18:13Z
A Mango Boeing 737-800, registration ZS-SJH performing flight JE-147 from Johannesburg to Cape Town (South Africa) with 179 people on board, was climbing out of Johannesburg’s runway 03L when a bird impacted the left hand engine inlet (CFM56) causing a dent at the engine inlet. The crew stopped the climb at about FL200 and decided to return to Johannesburg for a safe landing on runway 03L about 25 minutes after departure.

Passenger Sergio Davids reported a bird impacted the left hand engine, then he could smell smoke in the cabin.

The left hand engine in flight (Photo: Sergio Davids):

Ok, that’s just…i don’t even know what to say…:/

Edit: read some more info about this incident, apparently this taxiway was a former runway, and still shows signs of it being a runway before (maybe markings aren’t fully gone or something) and it was nighttime…but still, lighting is different on runways, and they rejected takeoff on the taxiway at nearly 100knts…

2 Likes

@AnikaitD. MaxSez: I’ll say it for you. TS-1 Operation or Pilot Error and lookin for a new job! Regards

2 Likes

Actually, TS1 is worse than departing a taxiway…they just drop there flaps at the gate and takeoff at 110% N1 XD

1 Like

It was when I read “oxygen masks” that the childish giggling started.
That’s a bad day at the office.
Thanks for the elaboration!

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