MaxAvSafety: WW Commercial Incident/ Accident Rpt

Real World Aviation
1

MaxSez: Provided for your information as professional knowledge, Please add updates, omitted rpts, photo’s/video’s and relative antidotal data below

Friday Jun 30th 2017
Incident Condor A321 at Bourgas on Jun 30th 2017, bird strike
Incident Jetblue A320 near Atlantic City on Jun 28th 2017, smoke in cockpit
Incident Republic E175 at Toronto on Jun 20th 2017, runway incursion
Incident Blue B734 at Bucharest on Jun 29th 2017, engine shut down in flight
Accident Emirates A388 over Arabian Sea on Jan 7th 2017, wake turbulence sends business jet in uncontrolled descent
Incident Indigo A320 at Patna on Jun 30th 2017, rejected takeoff due to engine stall prompts evacuation
Accident Asiana B772 at San Francisco on Jul 6th 2013, touched down short of the runway, broke up and burst into flames
Thursday Jun 29th 2017
Incident Easyjet A320 at Inverness on Jun 29th 2017, bird strike
Incident Delta B752 near Memphis on Jun 29th 2017, possible issue with an engine
Incident Qantas A388 near Sydney on Jun 29th 2017, engine oil leak
Incident Nouvelair A320 at Monastir on Jun 27th 2017, bird strike
Incident Westjet B737 near Winnipeg on Jun 16th 2017, unusual odour in cabin
Incident Canada E190 near Winnipeg on Jun 19th 2017, frozen automation
Incident THY A321 at Bucharest on Jun 22nd 2017, overran runway on landing
Incident Qantas B744 at San Francisco on Oct 6th 2016, bird strike
Incident Finnair A319 at Helsinki on Oct 28th 2016, crew corrects ATC mistake
Incident Finnair A321 at Helsinki on Oct 28th 2016, ATC operational error corrected by flight crew
Wednesday Jun 28th 2017
Incident KLM B772 and KLM B738 at Amsterdam on Jun 22nd 2017, conflicting takeoff clearances
Incident Azur Air B763 at Moscow on Jun 28th 2017, cabin did not pressurize
Incident Jazz DH8D at Edmonton on Jun 12th 2017, smoke in cockpit
Incident Emirates A388 near Dubai on Nov 9th 2016, hydraulic overheat leads to unsafe main gear on landing
Tuesday Jun 27th 2017
Incident Egypt B738 at Cairo on Jun 26th 2017, blew nose tyre on departure
Incident Corendon Dutch B738 near Amsterdam on Jun 27th 2017, wheel well fire indication
Incident Malindo B738 near Dhaka on Jun 27th 2017, cracked windshield
Incident Jet2.com A332 at Tenerife on Jun 27th 2017, burst two tyres on landing
Incident Canada A319 at Toronto on May 2nd 2017, hydraulic leak
Incident Vietnam A321 near Hanoi on Mar 27th 2017, loud noise
Incident REX SF34 near Sydney on Mar 17th 2017, propeller detached in flight
Incident Thomas Cook Scandinavia A332 near Shannon on Jun 26th 2017, dropped high speed tape in flight, low engine oil pressure
Incident Malindo B739 near Delhi on Jun 25th 2017, engine shut down in flight
Monday Jun 26th 2017
Incident LGW Walter DH8D at Venice on Jun 25th 2017, unsafe gear
Incident Iberia Express A320 at Santa Cruz de la Palma on Jun 25th 2017, flock of birds
Incident Azores A313 at Boston on Jun 25th 2017, struck taxiway light on landing
Incident Germanwings A319 enroute on Mar 19th 2017, aircraft started descent uncommandedly two times
Incident Germanwings A319 enroute on Mar 16th 2017, speed scale removed from PFD 3 times
Incident Eastern Australia DH8C at Adelaide on Jun 23rd 2017, smoke in cockpit
Incident AirAsia X A333 near Learmonth on Jun 25th 2017, engine shut down in flight after severe vibrations
Sunday Jun 25th 2017
Incident American A321 near Minneapolis on Jun 24th 2017, unsafe thrust reverser indication
Incident Ryanair B738 near Milan on Jun 23rd 2017, smoke in cabin
Saturday Jun 24th 2017
Incident KLM Cityhopper E190 at Amsterdam on Jun 24th 2017, engine vibrations
Incident Delta MD88 near Bristol on Jun 23rd 2017, smell of smoke in cockpit
Incident Delta B764 near Boston on Jun 22nd 2017, problem with minimum/maximum speed indications
Friday Jun 23rd 2017
Incident Delta A333 near Amsterdam on Jun 23rd 2017, smell of smoke in cabin, runway surface identified as source
Incident China Eastern A321 at Hong Kong on May 24th 2017, runway excursion on landing
Incident Jetblue E190 near Charleston on Jun 23rd 2017, smoke in cockpit
Incident GoAir A320 at Delhi on Jun 21st 2017, bird strike
Thursday Jun 22nd 2017
Incident United B772 near Baker Lake on Jun 20th 2017, lavatory woes
Incident American A333 at Charlotte on Jun 21st 2017, flaps problems
Incident Delta B772 over Pacific on Jun 22nd 2017, burning odour and smoke in cabin
Incident Europa A332 at Madrid on Oct 17th 2014, takeoff despite vehicle on runway
Incident Transat A313 at Montreal on Jun 16th 2017, hydraulic problem
(AvHerald)

7 Likes
2

Interesting, did they switch to the backup computer or was it all 3?

p.s thanks for the reports!

3

@Insertusernamehere… MaxSez: As requested, Old (final/investigation complete) but interesting.

Incident: Germanwings A319 enroute on Mar 19th 2017, aircraft started descent uncommandedly two times

A Germanwings Airbus A319-100, registration D-AGWG performing flight 4U-493 from Sarajevo (Bosnia and Herzegovina) to Cologne/Bonn (Germany), was enroute when the flight mode changed from NAV to HDG several times, both with autopilot 1 or autopilot 2 in use. The aircraft subsequently twice unexpectedly, without pilot command or intention, entered a descent of about 700fpm causing altitude deviations of about 150 feet while enroute at FL340 and was stopped and returned to assigned altitude by pilot intervention. About two minutes after the last altitude deviation the crew decided to descend the aircraft to FL240 near Stuttgart (Germany) and continued for a safe landing in Cologne.

Germany’s BFU reported on Jun 26th 2017 that the occurrence had not been reported to them.

The aircraft remained on the ground for 3 days for the subsequently engineering investigation including involvement by Airbus before returning to service. The history of the occurrence 3 days earlier, see Incident: Germanwings A319 enroute on Mar 16th 2017, speed scale removed from PFD 3 times, was included in the investigation and considerations. As result of the engineering investigation, that examined both flight management and guidance systems (FMGS) both testing okay, the FMGS #1 as well as another Air Data Module were replaced on recommendation by Airbus.

1 Like
4

Interesting, thanks - wasn’t a major issue so they didn’t switch to direct law, but unusual nonetheless. Dangers of computers here…

1 Like
5

I was expecting a more intriguing ending to the report. It would have been better if it read:

Upon inspection, an adult Burmese python was found asleep in the avionics bay. Extraction proved tricky for the brave engineers. Recommended snake proof wiring loom was fitted, and aircraft was returned to service.

2 Likes
6

That was a while ago (I know you didn’t write this tho)

Haven’t heard about this one^^^ how bad damge

“Incident REX SF34 near Sydney on Mar 17th 2017, propeller detached in flight”

While ago aswell 😉

7

Yep, that’s right. Is this Qantas’ fault?

8

Yeah I didn’t hear about that 747 bird strike.

1 Like
9

As requested Wombat, MaxSends

Incident: REX SF34 near Sydney on Mar 17th 2017, propeller detached in flight
By Simon Hradecky, created Friday, Mar 17th 2017 12:38Z, last updated Tuesday, Jun 27th 2017 14:53Z
A REX Regional Express Saab 340B, registration VH-NRX performing flight ZL-768 from Albury,NS to Sydney,NS (Australia) with 16 passengers and 3 crew, was descending through about FL120 towards Sydney cleared to descend to 8000 feet when the crew declared PAN reported they just had had uncommanded engine (CT7) operations, the right hand propeller had sheared off, they still were able to fly with normal handling of the aircraft. Air Traffic Control stopped departures and sent arriving traffic into holds advising a runway inspection was needed, only one runway would remain available and they couldn’t estimate when the second runway would become available again due to the landing with one propeller sheared off. A second PAN aircraft (medical emergency), that had earlier been assigned to runway 16R, too, was reassigned runway 16L. The Saab continued for a safe landing on Sydney’s runway 16R about 25 minutes later.

Australia’s TSB reported the occurrence was rated a serious incident. Three investigators with expertise in materials failure engineering have been dispatched on site. The ATSB urged: “The ATSB urges anyone who finds a piece of suspected aircraft debris NOT to handle it. Please call the local police or the ATSB on 1800 020 616.”

Sweden’s Statens Haverikommission (SHK) assigned an accredited representative to assist the investigation by the ATSB.

On Mar 21st 2017 the ATSB reported the separated propeller assembly weighing about 100kg/220lbs was found by a police helicopter at the Georges River National Park about 8nm west of Sydney Airport.

The airline grounded 5 more Saab 340s in order to secure propeller gear boxes and shafts of the same production series for detailed examination.

On Apr 13th 2017 the ATSB reported that the recovered propeller was still securely fastened with the bolts and dowel pins to the forward facing flange of the propeller shaft. Initial inspection showed cracks that appeared to run between the propeller shaft and the flange. Further examination revealed the crack was a fatigue crack that started within the propeller mounting flange and then propagated into the shaft section. The crack initiated at a bore of a dowel pin near the forward face of the flange. The dowel pin bore was corroded in parts and corrosion pitting was found near the fracture. The ATSB stated that this was the first critical failure of this type originating within the propeller flange. REX have quarantained all propeller gear boxes with the same flange as VH-NRX. Further examinations are under way at the engine manufacturer.

On Jun 27th 2017 the ATSB provided an update stating:

The engine manufacturer’s preliminary metallurgical analysis of the fractured shaft has identified that fatigue cracking in the propeller main shaft originated within a dowel pin bore that was located on the forward face of the propeller flange from the propeller reduction gearbox (PGB). Their analysis indicates that the initiation of fatigue cracking within the hub flange may be associated with a combination of factors that include:

  • the accumulation of significant operational hours for each propeller reduction gearbox
  • the development of pitting corrosion damage within the dowel pin bore and at the front face of the propeller flange
  • progressive wear and subsequent surface damage of the hub flange at stress-critical regions surrounding the dowel pin.

GE Aviation have released two service bulletins (SBs) to help understand the potential fleet risk for fatigue cracking in other CT7 PGB main propeller shafts.

The ATSB continued the first of the two service bulletins, SB 72-0530 released on May 16th 2017, which intended to conduct detail inspections of the PGB shaft for detection of cracking, corrosion, wear damage and other anomalies. The second service bulletin, SB 72-0531 released on Jun 22nd 2017 and applicable to all PGBs with more than 30,000 hours in service if the main propeller shaft had not been replaced within the last 10,000 hours in service, requires inspections of the hub flange region for cracking, corrosion and wear damage employing visual non-destructive methods.

A Saab 340A, registration N146CA, had lost the right hand propeller on Nov 21st 1991 following engine (CT7) vibrations. The NTSB concluded in their final report then: “A FATIGUE FRACTURE ON THE PROPELLER SHAFT, THAT ORIGINATED AT A SUBSURFACE SLAG INCLUSION, WHICH REMAINED IN THE MATERIAL USED TO MANUFACTURE THE SHAFT.”

3 Likes
10

Thanks for showing this info Max but we’ve heard all about it in the media

2 Likes
11

Well, that can never be good…

1 Like
12

I would like to hear more details about these Finnair incidents.

About that unusual odor on westjet 737, I bet someone farted.

13

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