ByGMaxSez: Provided Wkly as Professional Knowledge Gained. Pls expand details, add first person accounts, photo/video’s ect below;
Friday Jan 5th 2018
Incident Transavia B738 at Amsterdam on Jan 5th 2018, burning odour after lightning strike
Incident Lufthansa A319 at Nice on Jan 5th 2018, engine shut down in flight
Incident American B738 at New York on Jan 5th 2018, engine fire
Incident Atlasjet A321 over Bulgaria on Sep 8th 2016, climb instead of descent results in near collision
Accident West Wind AT42 at Fond-du-Lac on Dec 13th 2017, descended into terrain shortly after takeoff
Incident Saudia A333 at Cairo on Jan 5th 2018, did not capture localizer
Incident THY A321 and Egypt B738 at Cairo on Jan 4th 2018, loss of separation on simultaneous go around and takeoff
Thursday Jan 4th 2018
Incident Aeroflot A320 at Barnaul on Jan 3rd 2018, cargo door indication
Incident Malta A319 near Dusseldorf on Jan 3rd 2018, fan of a galley oven
Incident Aeromar AT72 at Mexico City on Dec 22nd 2017, engine shut down in flight
Incident Aeromar AT72 at Mexico City on Dec 22nd 2017, rejected takeoff due to loss of super boost
Incident VivaAerobus A320 at Torreon on Dec 3rd 2017, flock of birds
Incident Hong Kong A333 at Hong Kong on Dec 23rd 2017, rejected takeoff due to other aircraft on runway
Accident Saudia A333 at Lucknow on Dec 27th 2017, nose wheel divorced
Incident Lingus A332 at Dublin on Dec 28th 2017, engine shut down in flight
Wednesday Jan 3rd 2018
Incident British Airways A320 at Geneva on Jan 2nd 2018, smoke in cabin
Incident Iceland B752 near Edmonton on Dec 26th 2017, generator and APU failure
Incident Iran Aseman B734 at Tehran on Jan 2nd 2018, gear problem on departure
Incident Delta B763 near Goose Bay on Jan 2nd 2018, generator failure
Incident Delta B764 at Atlanta on Jan 3rd 2018, sound like engine compressor stall
Incident Delta B764 near Atlanta on Jan 2nd 2018, engine compressor stall
Tuesday Jan 2nd 2018
Incident Easyjet Europe A320 at Tenerife on Jan 1st 2018, door open indication
Incident Southwest B738 at Seattle on Jan 1st 2018, gear indication on departure
Incident Inuit B732 at La Grande Riviere Dec 23rd 2017, smoke from main deck cargo, heat in cabin
Incident Swiss A343 near Johannesburg on Jan 1st 2018, weather radar trouble
Accident Batik B738 enroute on Oct 24th 2017, clear air turbulence injures three
Accident Batik B739 near Surabaya on Jan 2nd 2018, turbulence injures 4
Incident Qantas B744 near Honolulu on Dec 31st 2017, failure of weather radar
Accident American A319 at Boston on Jan 1st 2018, odour on board
Monday Jan 1st 2018
Incident Delta B739 at Atlanta on Dec 30th 2017, vibrations on airframe
Incident United B738 at Saint Lucia on Dec 30th 2017, gear problem on departure
Incident American B738 at New York on Dec 31st 2017, slat problem
Sunday Dec 31st 2017
Incident Indigo A20N at Goa on Dec 31st 2017, engine problem
Incident Skywest CRJ9 at Pasco on Dec 29th 2017, nose gear issue on departure
Incident British Airways A319 at Hamburg on Dec 31st 2017, bird strike on landing
Incident Delta B712 at Detroit on Dec 30th 2017, birdie at the controls
Saturday Dec 30th 2017
Incident Cayman B738 at Grand Cayman on Dec 27th 2017, unidentified odour on board
Incident Rossiya A320 at Chelyabinsk on Dec 30th 2017, door open indication
Friday Dec 29th 2017
Incident Canada A319 at Vancouver on Dec 10th 2017, burning vacuum
Incident Jazz CRJ9 at Regina on Dec 19th 2017, a really cool brake
Incident ABX B762 near Providence on Dec 28th 2017, engine shut down in flight
Accident Skywest CRJ2 near Milwaukee on Dec 28th 2017, loss of cabin pressure
Incident Kuwait A320 near Kuwait on Dec 28th 2017, cargo smoke indication
Accident Norwegian B738 near Alicante on Oct 18th 2017, ATC turns aircraft, TCAS RA and turbulence injures two flight attendants
Accident Etihad A332 near Jakarta on May 4th 2016, turbulence injures 33
Crash Trigana AT42 enroute on Aug 16th 2015, aircraft collided with terrain
Thursday Dec 28th 2017
Incident Orange2Fly A320 at Pristina on Dec 2nd 2017, hard landing
Incident Qantas B744 over Pacific on Dec 27th 2017, failure of weather radar
Incident France A388 near Los Angeles on Dec 27th 2017, engine shut down in flight
Accident Stobart AT72 at Cork on May 26th 2017, passenger fell off aircraft stairs
Incident Sudan A306 at Jeddah on Nov 29th 2017, engine failure on touch down.
1). Incident: Atlasjet A321 over Bulgaria on Sep 8th 2016, climb instead of descent results in near collision
By Simon Hradecky, created Thursday, Oct 6th 2016 16:58Z, last updated Friday, Jan 5th 2018 20:22Z
An Atlasjet Airbus A321-200, registration TC-ATF performing flight KK-6112 from Zurich (Switzerland) to Istanbul (Turkey), was enroute at FL350 about 140nm southeast of Sofia (Bulgaria) and about 130nm northwest of Istanbul when Sofia Center cleared the flight to descend to FL310. The aircraft however initiated a climb instead of the descent.
A THY Turkish Airlines Boeing 737-800, registration TC-JVS performing flight TK-1966 from London Gatwick,EN (UK) to Istanbul (Turkey), was enroute at FL370 about 140nm southeast of Sofia and about 130nm northwest of Istanbul at the same time, when Sofia Center cleared the flight to descend to FL330.
Bulgaria’s AAIU reported that as result the separation between the aircraft eroded to 0 feet vertical and 1.2nm horizontal at FL363, Sofia Center issued vectors to both aircraft turning the A321 left and the B738 right thus establishing diverging flight trajectories and resolving the conflict. The A321 subsequently descended to the cleared FL310, the B738 to the cleared FL330, both aircraft continued to Istanbul for safe landings. The occurrence was rated a serious incident and is being investigated by the Bulgaria’s AAIU.
On Jan 5th 2018 the AAIU released their final report concluding the probable causes of the serious incidents were:
Violation of the autopilot vertical speed selection process technology of A321-211 aircraft resulted in climbing of the aircraft instead of executing the clearance issued to KKK8JY for descent.
A state of Expectation Bias of EXE ATCO that led to issuing of clearance to THY4AV for descent during the time when the KKK8JY started to climb in contrary to the previously issued and confirmed by the crew clearance for descent and the presence of Mode S indication displayed on the ATCAS screen for selected FL 310 by the crew of KKK8JY.
The AAIU reported that following the instruction to descend to FL310 the crew of the Atlasjet A321 correctly read back the clearance, selected FL310 as new altitude target into the flight control unit (FCU), which the controller could also see on his radar screen via the Mode-S data downlink. The controller therefore developed an expectation bias and cleared the THY B738 to descend. However, the crew of the Atlasjet selected the FCU’s vertical speed to +1500 fpm and the aircraft began to climb instead of descend.
The AAIU analysed:
In view of the above, it is concluded that the serious incident under investigation is most probably a result of the following dominant factors related to the third and fourth hypotheses:
A. Violation of the autopilot vertical speed selection process technology of A321-211 aircraft resulted in climbing of the aircraft instead of executing the clearance issued to KKK8JY for descent.
B. A state of Expectation Bias of EXE ATCO that led to issuing of clearance to THY4AV for descent during the time when the KKK8JY started to climb in contrary to the previously issued and confirmed by the crew clearance for descent and the presence of Mode S indication displayed on the ATCAS screen for selected FL 310 by the crew of KKK8JY. END
- Incident: Delta B712 at Detroit on Dec 30th 2017, birdie at the controls
By Simon Hradecky, created Sunday, Dec 31st 2017 16:28Z, last updated Sunday, Dec 31st 2017 16:34Z
A Delta Airlines Boeing 717-200, registration N957AT performing flight DL-1943 from Detroit,MI to Atlanta,GA (USA), was in the initial climb out of Detroit’s runway 21L when the crew reported a maintenance issue and requested to return to the field, no assistance was needed. The aircraft levelled off at 6000 feet and returned to Detroit for a safe landing on runway 21L about 20 minutes after departure.
The airline reported the flight crew noticed a small bird on the flight deck, which had obviously entered the aircraft during boarding. The captain decided to return to Detroit to avoid a possible distraction. The bird was complimented off the aircraft and set free.
The aircraft departed again after about 80 minutes on the ground and reached Atlanta with a delay of 3 hours.
At the time of the boarding ambient temperatures were reported at -9 degrees C and winds at 18 knots gusting 23 knots. END
- Incident: Hong Kong A333 at Hong Kong on Dec 23rd 2017, rejected takeoff due to other aircraft on runway
By Simon Hradecky, created Sunday, Dec 24th 2017 15:35Z, last updated Thursday, Jan 4th 2018 16:15Z
A Hong Kong Airlines Airbus A330-300, registration B-LNU performing flight HX-709 from Hong Kong (China) to Denpasar (Indonesia), was cleared for takeoff from Hong Kong’s runway 07R when the crew of a Cathay Pacific Boeing 747-800, registration B-LJK performing flight CX-71 (dep Dec 22nd) from Anchorage,AK (USA) to Hong Kong (China), advised they were not yet clear of the runway still crossing the runway at taxiway J11 near the end of the runway. Tower in response immediately instructed HX-709 to stop. The crew rejected takeoff at low speed and radioed they were stopping, but were past taxiway J2 about 150 meters down the runway, would like to vacate via J3 and return to the holding point J1. Following taxi the aircraft departed about 8 minutes after the rejected takeoff.
Tower had cleared CX-71 to cross runway 07R at J11 about 35 seconds prior to the takeoff clearance for HX-709.
Hong Kong’s CAD opened an investigation into the occurrence.
On Jan 4th 2018 the CAD reported the occurrence was rated a serious incident. The CAD summarized the occurrence briefly: "Shortly after Aircraft 1 was given take-off clearance by Air Traffic Control (ATC), the pilot of Aircraft 2 informed ATC that it was crossing the same runway and had not yet completely vacated the runway. Upon receiving information from Aircraft 2, ATC immediately instructed Aircraft 1 to stop and Aircraft 1 aborted the take-off. Aircraft 2 then continued to cross the runway while Aircraft 1 followed ATC instructions to vacate and line up the runway again for another take-off. " END
Incident: American B738 at New York on Dec 31st 2017, slat problem
By Simon Hradecky, created Monday, Jan 1st 2018 17:30Z, last updated Monday, Jan 1st 2018 17:30Z
An American Airlines Boeing 737-800, registration N972AN performing flight AA-1609 from Bermuda (Bermuda) to New York JFK,NY (USA) with 144 people on board, was on approach to New York when the crew stopped the descent at 3000 feet reporting they had a flight control issue and might be declaring emergency. About 5 minutes later the crew explained the leading edge devices were stuck in the one o’clock position, declared emergency, requested emergency services to attend the aircraft and advised they were going to stop on the runway 31L for a brief inspection of brakes and checks for leaks. The aircraft landed safely on runway 31L at a higher than normal speed about 30 minutes after stopping the descent. The aircraft stopped on the runway, emergency services reported the brakes appeared hot but there were no leaks, emergency services followed the aircraft to the apron. END
Accident: Norwegian B738 near Alicante on Oct 18th 2017, ATC turns aircraft, TCAS RA and turbulence injures two flight attendants
By Simon Hradecky, created Friday, Dec 29th 2017 19:21Z, last updated Friday, Dec 29th 2017 19:21Z
A Norwegian Air International Boeing 737-800, registration EI-FJJ performing flight D8-5321 from Oslo (Norway) to Alicante,SP (Spain) with 178 passengers, was descending towards Alicante while being surrounded by cumulonimbus cloud. The aircraft had been cleared to descend to FL190 and was already level at FL190, when the crew received instruction by ATC to turn left 90 degrees shortly followed by a TCAS resolution advisory to descend below the cleared FL190. While descending between FL190 and FL180 on TCAS instruction the aircraft encountered turbulence causing injuries to two flight attendants. The aircraft continued to Alicante for a landing without further incident.
Spain’s CIAIAC reported one flight attendants received a serious leg injury, the other a minor back injury when the aircraft turned left 90 degrees following an ATC instruction and descended from the assigned FL190 to FL180 due to a TCAS RA and thus passed through a zone of turbulence. After being clear of conflict the flight crew was informed about the injuries of the flight attendants and continued the flight for a landing at destination without further incident. The CIAIAC opened an investigation into the occurrence. END