MaxAvSafety: WW Wkly Commercial Accidant/Incidant Rpt

MaxSez: Provided for Professional Knowledge Gained.

Sunday Jul 16th 2017
Incident Korean B773 near Berlin on Jul 15th 2017, loss of communication
Saturday Jul 15th 2017
Incident Austrian A319 and Austrian DH8D at Vienna on Jun 16th 2017, loss of separation, TCAS resolution advisory
Incident France B772 near Glasgow on Jul 15th 2017, burning odour on board
Incident Vueling A320 at Barcelona on Jul 15th 2017, runway “catches” aircraft
Incident Canada A320 at San Francisco on Jul 7th 2017, lined up with taxiway for landing
Incident Caribbean AT72 at Saint Lucia on Jul 9th 2017, engine fire indication
Friday Jul 14th 2017
Incident British Airways A320 enroute on Jul 7th 2017, fumes in cabin
Incident Endeavor CRJ2 at Evansville on Jul 13th 2017, nose gear problem on departure
Incident Martinair B744 at Amsterdam on Jul 14th 2017, engine shut down in flight
Incident Argentinas B738 near Bahia Blanca on Jul 13th 2017, engine shut down in flight
Incident Hawaiian B712 near Honolulu on Jul 12th 2017, engine shut down in flight
Thursday Jul 13th 2017
Incident Flybe DH8D near Southampton on Jul 13th 2017, possibly cracking windshield
Incident Easyjet A319 at Liverpool on Jul 13th 2017, bird strike
Accident Caribbean B738 at Sint Maarten on Jul 12th 2017, jet blast blows woman over
Incident Condor A321 at Bourgas on Jun 30th 2017, bird strike
Incident PIA A320 at Peshawar on Jul 11th 2017, bird strike
Wednesday Jul 12th 2017
Incident Thomas Cook A332 near Stornoway on Jul 12th 2017, galley oven emits smoke
Incident Skywest CRJ7 near Salt Lake City on Jul 11th 2017, cracked windshield
Accident China Eastern A332 near Tyumen on Jun 18th 2017, severe turbulence causes loss of 4000 feet and injures 26
Incident United B738 at Denver on Jul 11th 2017, bird strike
Accident Lufthansa A333 at Munich on Jun 21st 2017, strong odour causes injuries to cabin crew and affects passengers
Accident Lufthansa A319 at Munich on Mar 6th 2017, fumes during engine start
Accident Eurowings A320 near Cologne on Jul 7th 2017, fumes injure three cabin crew
Tuesday Jul 11th 2017
Incident Germanwings A319 near Barcelona on Jul 8th 2017, fumes on board
Incident KLM Cityhopper F70 at Amsterdam on Jul 10th 2017, cracked windshield
Incident KLM Cityhopper E190 at Amsterdam on Jul 10th 2017, GPU hatch open
Incident Norwegian B738 at Helsinki on Jul 11th 2017, runway excursion on landing
Incident Mistral AT72 at Ancona on Jul 7th 2017, smoke detector indication
Incident Jetblue E190 near New York on Jul 11th 2017, fumes in cockpit
Incident PAL A333 near Yangon on Jul 10th 2017, cracked windshield
Incident Zimbabwe B732 near Bulawayo on Jul 10th 2017, loss of cabin pressure
Incident Delta A320 near Daytona Beach on Jul 10th 2017, hail strike
Incident UTAir B738 near Moscow on Jul 11th 2017, engine shut down in flight
Report Austrian A321 near Cairo on Sep 3rd 2014, brand new iPad overheated
News The painted airport at Mexico City
Monday Jul 10th 2017
Incident THY B738 at Kayseri on Jul 10th 2017, bird strike
Incident Thomas Cook A321 at East Midlands on Jul 9th 2017, unruly computer
Incident Swiss A321 at Zurich on Jul 9th 2017, flaps problem
Incident Vueling A320 at Brussels on Jul 9th 2017, sauna in flight
Incident Expressjet CRJ9 at Newport News on Jul 9th 2017, nose gear steering problem
Incident Avianca A320 at Bogota on Jun 30th 2017, bird strike
Incident Iceland B752 at Toronto on Jun 25th 2017, runway incursion
Sunday Jul 9th 2017
Incident Southwest B737 near Las Vegas on Jul 7th 2017, unreliable airspeed and altitude
Incident Delta MD90 near Las Vegas on Jul 8th 2017, generator problem
Incident Iran A306 at Tehran on Jul 9th 2017, engine fire indication
Saturday Jul 8th 2017
Accident Thomson B752 near London on Jul 8th 2017, smoke injures 3 cabin crew
Friday Jul 7th 2017
Incident Swift Air B733 near Miami on Jul 7th 2017, cargo smoke indication
Incident Spirit A319 at Dallas on Jul 7th 2017, hydraulic problem
Incident Aeromexico B737 at Ciudad Juarez on Jul 5th 2017, hydraulic failure
Incident GoJet CRJ7 at Chicago on Feb 17th 2015, runway incursion, departing aircraft takes evasive action


Sauna in flight? Can someone explain this for me?

1 Like

@Stmaarten1778. As requested :

Incident: Vueling A320 at Brussels on Jul 9th 2017, sauna in flight
By Simon Hradecky, created Monday, Jul 10th 2017 23:07Z, last updated Monday, Jul 10th 2017 23:07Z
A Vueling Airbus A320-200, registration EC-MBS performing flight VY-2151 from Brussels (Belgium) to Malaga,SP (Spain), was climbing out of Brussels’ runway 07R when the crew stopped the climb at FL110, burned off fuel at FL050 and returned to Brussels for a safe landing on runway 01 about 80 minutes after departure.

The airline reported the aircraft returned to Brussels due to a technical problem.

A passenger reported it became incredibly hot in the cabin after departure, everybody was sweating. The crew announced a technical problem, they needed to burn off fuel and would return to Brussels. (Max/AvF)


Lucky no Aussie incidents in the news this week. Nice post as usual Max!

1 Like

How did this turn out? Did they manage to reestablish communication?

Runways catches Vueling A320? Did runway became alive and caught Vueling A320?


Oh asphalt just got hot enough to melt then A320 had its tires sunk into asphalt.

Incident: Vueling A320 at Barcelona on Jul 15th 2017, runway “catches” aircraft

A Vueling Airbus A320-200, registration EC-LQN performing flight VY-2125 from Barcelona,SP to Malaga,SP (Spain), had lined runway 25L up for departure and was waiting for takeoff clearance. After the flight was cleared for takeoff, the crew attempted takeoff, the aircraft however did not move and was stuck at the runway threshold.

The airport reported runway 25L was closed due to an aircraft blocking the runway. The airport was forced to operate with the shorter crossing runwas as result (07L/25R and 02/20) causing minor delays.

A source told The Aviation Herald the asphalt covering the runway melted under the tyres causing the aircraft to sink into the runway surface.

Controladores Aereos reported the aircraft apparently sunk into the runway asphalt and was disabled. A resurfacing of the runway is necessary.


Oh that would not have been good at all! I can imagine the pilots wondering why on earth the plane isn’t moving on full power.


If it was Boeing 777, pilots would have taken whole runway with them.


@Reedgreat… MaxSez: As Requested;

Incident: Korean B773 near Berlin on Jul 15th 2017, loss of communication
By Simon Hradecky, created Sunday, Jul 16th 2017 09:33Z, last updated Sunday, Jul 16th 2017 09:33Z
A Korean Airlines Boeing 777-300, registration HL8011 performing flight KE-917 from Seoul (South Korea) to Zurich (Switzerland) with 211 passengers, was enroute FL380 almost over Berlin (Germany) when the crew set the transponder code for loss of communication. German Airforce dispatched two supersonic fighter aircraft to intercept the aircraft and accompany the aircraft to Stuttgart (Germany), about 80nm north of Zurich, where the aircraft landed safely on runway 07 about 55 minutes later.

German police reported the aircraft was escorted to Stuttgart due to a problem with the aircraft’s radio equipment. Police received some 250 phone calls due to the sonic boom produced by the fighter aircraft.

The passengers were taken to the terminal in Stuttgart. Due to night curfew, lack of available hotel beds and lack of transportation the passengers spent the night at the terminal on cots and were bussed to Zurich the following morning.

The occurrence aircraft is still on the ground in Stuttgart about 11 hours after landing.

Reader Comments: (the comments posted below do not reflect the view of The Aviation Herald but represent the view of the various posters)
7600 approach
By HH-52 on Monday, Jul 17th 2017 09:25Z

How would the procedure be to assign a runway (or even communicate which runways are active) to a plane under 7600 regimen? Is it ascertained at the ground/ATC that the crew can receive inflight METAR etc. so they can make up their mind in which direction to land?

I am just an armchair pilot so I know exactly nothing about the procedures, but to me it seems sensible to assume that the aircraft can’t hear anything and have an interceptor vector the plane in (notwhithstanding that in this particular case the crew apparently happily communicated on 121.5).

By Alex on Monday, Jul 17th 2017 06:31Z

@Marc: there is no need to “guide” them to ZRH as the route is already filed and special lost com procedures known to crew are already published for ZRH.
Except for the radio reception the aircraft was fully functional.
The EU/ICAO lost commprocedure was adopted to let the aircraft fly to original destination according to predetermined route. Upon selection of sw 7600 air traffic control should “clear the way” to destination.

By Naschus on Sunday, Jul 16th 2017 23:08Z

We were flying trough Swiss airspace at time of the interception. Listening on 121.5 all the time. The Koreans were clearly to be heard, you could tell by the accent (and of course by the use of their callsign). Who else should transmit “WE are following the German fighter.”?
They seemed to be transmitting blind as they never answered to anybody.
Don’t know where the contrary information comes from.

2020 one day missing
By Hans Glück on Sunday, Jul 16th 2017 23:04Z

@Peter Müller: what will they do on Feb 29th 2020 then? :)

Direct ZRH
By Marc on Sunday, Jul 16th 2017 22:58Z

Why should they take the risk to guide a plane without radio capabilities to an airport in between mountains, which as well is much busier than Stuttgart and has other stuff to do than clear the airspace for a mute 773 to come in?
Also, tax payed jetfuel is not meant to be spent in order to get Korean Air passengers to their destination more quickly.

Swiss Air Police Operating Hours
By Peter Müller on Sunday, Jul 16th 2017 20:56Z

This is how swiss air police is organnized: (Text in German from Airforce Web)
2016: 50 weeks MO to FR 8am to 6pm
2017: 365 days 8am 6pm
2019: 365 days 6am 22pm
2020: 365 days/24 hours
all QRE 15
Das Projekt Luftpolizeidienst 24 (LP24) geht auf eine Motion von Alt-Ständerat Hans Hess (FDP/OW) aus dem Jahr 2009 zurück. Darin forderte er eine erhöhte Bereitschaft im Luftpolizeidienst auch ausserhalb der normalen Arbeitszeiten. Mit LP24 wird nun in vier Schritten eine permanente Einsatzbereitschaft von zwei bewaffneten Kampfjets innert höchstens 15 Minuten erreicht. Der erste Schritt wurde im Jahr 2016 gemacht: Während 50 Wochen stehen die Flugzeuge an Wochentagen von 8 bis 18 Uhr bereit. 2017 wird diese Präsenz dann auf 365 Tage ausgebaut. Ab 2019 werden die Jets von 6 bis 22 Uhr bereit stehen und Ende 2020 erfolgt dann der Ausbau auf 24 Stunden während 365 Tagen.

By Seb on Sunday, Jul 16th 2017 20:55Z

@Hans58 Not sure about that, some media named it calls, and some named it emergency calls. I don’t think someone would google for the local police station number in a situation like that. 250 calls in half an our is quite a lot I think, even if they were divided on several emergency lines/police stations.
(250 emergency calls would also fit perfectly to a current tendency here in germany about people who call the emergency line for negligible reasons…)

By Beobachter on Sunday, Jul 16th 2017 20:46Z

@Jasper: Well, someone has to do the job, right? And fighter jets are pretty fast, if you have to catch up with a 777.

In 2005 they tried to make a law that allows the Luftwaffe to shoot down airliners if kidnapped by terrorists (9/11 scenario), but the constitutional court (Bundesverfassungsgericht)judged it as a violation of article 1 of our constitution, because you would weigh up the lifes of the innocent people onboard the plane and the innocent people on the ground.
Because every human life is equal, you are not allowed to take the life of hundreds of innocents to safe other innocents (even if the people on the ground are thousands).

Someone who gives order to shoot down a airliner or someone who does it anyway would be accused of murder (§ 211 StGB).

In case that the 9/11 scenario becomes true, well yeah, the authorities would have to watch.
But maybe the fighter pilot would take the risk of getting jailed and shoot it down anyway. It’s a question of morality…

@ Herb & Beobachter
By Jak on Sunday, Jul 16th 2017 20:25Z

So if Monaco decides to invade Switzerland during the night they may have some more holes in the Swiss cheese cause people were worried about the sonic booms :)) Thank You !

By Hans58 on Sunday, Jul 16th 2017 20:15Z

Are you sure those 250 people did call the emergency number (110)?
One can call the local police office by normal landline. And if the really did call 110 along the line of the supersonic sound it’s not an issue. 110 has more than one line.

By Juergen on Sunday, Jul 16th 2017 19:39Z

Do not understand the reason for the interception. There is a radio failure procedure to follow the flight plan route, enter the holding at dest and start approach at the est ldg time within 30 min.Thats it !

@ Jak re: op hours
By Herb on Sunday, Jul 16th 2017 19:20Z

There are plans to have 24 hrs / 7 days a week for a couple F/A 18 to be ready for immediate take-off (withing 10-15 minutes) from the main Swiss Airforce base Payerne.

Not long ago they had such a air police flight, towards the north , around ALthenrhein and people were worried about the sonic booms.

I wish I heard them…

These loss comms occur more frequently it seems, especially with far east airlines.

"why use armed aircraft for these type of escorts"
By Dubai_Phil on Sunday, Jul 16th 2017 18:41Z

Because fighter aircrafts are used for air policing. What aircraft you propose to use?
And a) you just do not know what will happen and b) you do not have the time to take ammunition out.

By (anonymous) on Sunday, Jul 16th 2017 18:30Z

Sorry “who dials 7600”

By (anonymous) on Sunday, Jul 16th 2017 18:28Z

Who dials 7500 while hi-jacking an AC? It’s like shouting “FIRE” during a bank robbery.

By Jasper on Sunday, Jul 16th 2017 17:53Z

If shooting the airliner down would never happen, then why use armed aircraft for these type of escorts?

What do you think would happen if the airliner had ignored the instructions and turned towards a population centre? You can be sure the authorities have a plan for this eventuality, and I doubt it involves just watching.

German fighters in Switzerland
By KKN on Sunday, Jul 16th 2017 16:56Z

German fighters have been in Switzerland before without large public outcry. One unfortunately never returned.

Admittedly training; but concerning serious missions, there have at least been German police forces in Switzerland, requested of course. One wouldn’t believe but nations and authorities can be pretty pragmatic.

Concerning shooting -god forbid- being non-constitutional, noble. But relies on somebody down the chain willing to break law/constitution. What’s the point showing/deploying a weapon (system) if not ready to use it in extremis. Just don’t.

Sorry for OT.

If keeping them in DE, why wait til STR. Maybe not borders - STR close & less busy than ZRH for R/T?

@ anonymous on Sunday, Jul 16th 2017 16:36Z
By 727driver on Sunday, Jul 16th 2017 16:43Z

After 9/11 things have obviously changed.
Do you mind to consider “someon else” dialed in 7600?

By (anonymous) on Sunday, Jul 16th 2017 16:36Z

Why should they shoot them? They squaked 7600 not 7500. Escort yes, they needed some help obviously. No need to shoot.

@Harald: German Air Force is not allowed to shoot down a passenger aircraft in any case. It would be against the constitution. So this would not be a problem here.

1 Like

Out of interest, what is this post referring to? What’s the source? I think I got tagged falsely.

It was from a website that apperantly had a member that had the username of jasper


@Jasper… MaxSez: “Jasper” is a respondent to an excerpt narrative/conversation included in an incident report as initially posted as the Topic in the wkly Harold Incident/Accident reports. It’s posted in response to a members request. In future in order to bring context to this wkly feature, read the entries in order, all will become clear. Bottom Line, it’s not you Jasper it’s someone, somewhere grousing. If your still a bit confused PM me.

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