MaxSez: Provided as Professional Knowledge Gained. Pls add updates, omitted rpts, first person related insight, related photo & videos;
Friday Oct 6th 2017
Incident American B763 near New York on Oct 5th 2017, electrical problems
Incident American B763 near Bogota on Oct 4th 2017, electrical problems
Incident Naft F100 at Aghajari on Oct 6th 2017, main wheel locked up during landing
Incident Jazz DH8D at Vancouver on Sep 28th 2017, loss of cabin pressure due to door handle
Incident France A388 over Greenland on Sep 30th 2017, fan and engine inlet separated
Thursday Oct 5th 2017
Incident PSA CRJ9 at Charlotte on Oct 4th 2017, nose gear steering problem
Incident Westjet B738 at Sint Maarten on Mar 7th 2017, go around on short final
Incident Canada B789 near Hyderabad on Sep 19th 2017, ATC tries to divert aircraft despite several Mayday calls following two diversions
Incident Transat A333 near Montreal on Sep 29th 2017, smell of smoke in cabin
Incident Cargologic B744 near Munich on May 19th 2017, dropped flap track fairing in flight
Report Tunis B736 near Munich on May 14th 2017, loss of cabin pressure
Accident American A321 at Bridgetown on Sep 15th 2017, tail damage on landing
Wednesday Oct 4th 2017
Incident American B772 over Atlantic on Oct 4th 2017, cargo smoke indication
Incident Sunwest DH8C at Conklin on Oct 3rd 2017, a real deer landing
Incident Easyjet A320 near Berlin on Oct 4th 2017, burning odour
Incident Southwest B737 at Sacramento on Oct 3rd 2017, bird strike
Accident Maldivian DHC6 at Male on Oct 4th 2017, hard water landing
Incident Swift AT72 near Alicante on Sep 9th 2017, stall in icing conditions
Incident Delta B752 at Las Vegas on Sep 6th 2017, engine fire
Tuesday Oct 3rd 2017
Incident Mesa CRJ9 near Colorado Springs on Oct 1st 2017, loss of cabin pressure
Incident Virgin Atlantic A333 at Saint Lucia on Oct 2nd 2017, runway excursion on backtrack
Report Sprint SF34 at Kirkwall on Mar 20th 2017, descended below minimum safe altitude on approach
Crash Malaysia B772 over Gulf of Thailand on Mar 8th 2014, aircraft missing, data indicate flight MH-370 ended west of Australia, first MH-370 debris identified, search suspended
Monday Oct 2nd 2017
Incident Delta A320 at Detroit on Oct 2nd 2017, engine problem
Incident Jetstar Pacific A320 near Gaya on Oct 2nd 2017, cargo smoke indication
Incident Jet Airways B738 at Chandigarh on Oct 1st 2017, bird strike
Incident Helvetic E190 near Zurich on Jan 12th 2017, loss of cabin pressure and de-icing
Incident Skywest E175 at Portland on Sep 30th 2017, bird strike
Incident American B738 at Dallas on Sep 29th 2017, tail strike on departure
Incident Swiss A333 at Zurich on May 6th 2017, near collision with a drone
Sunday Oct 1st 2017
Incident United B763 near Port au Prince on Sep 26th 2017, hydraulic failure
Incident THY A321 at Istanbul on Oct 1st 2017, flock of birds
Incident Cobham B712 near Melbourne on Sep 29th 2017, engine trouble
Incident Angara A148 at Talakan on Sep 30th 2017, engine shut down in flight
Saturday Sep 30th 2017
Incident Berlin A320 at Sylt on Sep 30th 2017, overran runway on landing
Friday Sep 29th 2017
Incident Finnair A359 over Russia on Sep 29th 2017, technical problem
Incident Jeju B738 at Jeju on Sep 29th 2017, rejected takeoff on ATC instruction, possible ATC error
Incident JAL B773 near Sapporo on Sep 29th 2017, burning odour in cockpit
Incident Westjet B737 at Edmonton on Sep 19th 2017, pitch control problems
Incident Delta MD88 at Newark on Sep 28th 2017, bird strike
Incident Envoy E145 at Dallas on Sep 27th 2017, bird strike
Incident American A321 enroute on Sep 26th 2017, bird strike
Thursday Sep 28th 2017
Incident ANA B763 near Tokyo on Sep 27th 2017, dropped panel in flight
Accident Westjet Encore DH8D at Calgary on Sep 18th 2017, turbulence injures both flight attendants
Accident Ural A321 at St. Petersburg on Sep 28th 2017, mother and infant fell through stairs
Accident JAL B763 near Kagoshima on Nov 10th 2016, turbulence injures cabin crew
Incident Royal Maroc B738 near Lisbon on Sep 9th 2017, engine shut down in flight
Wednesday Sep 27th 2017
Incident Indigo A320 at Raipur on Sep 27th 2017, bird strike
Incident JAL B738 at Tokyo on Sep 27th 2017, rejected takeoff due to engine problem
Incident Canada B763 near Toronto on Sep 15th 2017, electrical burning odour in cabin
- (Historic Final Rpt) A Westjet Boeing 737-800, registration C-GWSV performing flight WS-2652 from Toronto,ON (Canada) to Sint Maarten (Sint Maarten) with 164 people on board, had acquired visual contact with the runway 10 and was flying visually on very short final to Sint Maarten’s runway 10 at about 15:33L (19:33Z), when the aircraft went around from low height, climbed to 4000 feet and entered a hold. The aircraft landed safely on runway 10 about 40 minutes after the go-around.
A ground observer had taken photos of the aircraft and published a story on Mar 9th 2017 claiming the aircraft nearly crashed into the waters at Sint Maarten but Westjet denying that there had been a close call.
On Mar 14th 2017 the airline released following statement quoted in its main part: “Video and photos of the missed approach spawned articles with unfortunate and frankly, irresponsible headlines such as, “Near Miss” and “WestJet denies close call caught on camera at St. Maarten,” with some even speculating on a potential disaster that was averted. We think it’s important to share with you what a missed approach means and how this “near miss” was anything but. Every day our pilots safely land some 700 flights throughout our network of more than 100 destinations in over 20 different countries, many of which have unique weather and terrain. Occasionally a landing will be aborted and a missed approach initiated if the pilots determine it’s the best option. In this case, our crew experienced rapidly changing weather conditions and as a result descended below the normal glide path on the approach to the landing. The crew recognized the situation, and the regularly trained and desired outcome was obtained – a safe missed approach to a safe landing.”
According to position data and barometric altitude data (always using a standard pressure setting 1013hPa) received from the aircraft’s transponder the aircraft was 0.57nm before the runway threshold at 0 feet when the aircraft initiated a go around, the rate of descent was just reducing but still indicating a descent and turning into a rate of climb. Corrected for the present ambient pressure 1019 hPa at the time of the short final the aircraft thus was between 157 (2.04 degrees glidepath) and 182 feet MSL (2.37 degrees glidepath) the transponder resolves the barometric altitude in 25 feet steps). In order to maintain a 3 degrees glideslope at that point the aircraft should have been at 230 feet MSL.
On Mar 17th 2017 the Canadian TSB reported: “During the approach to Runway 10 at TNCM, the aircraft descended too low on final and the flight crew executed a missed approach. A second approach was conducted and the aircraft landed without further event.” The TSB rated the occurrence a “non-reportable incident” (an incident that is not required to be reported to the TSB) and opened a class 3 investigation (the reason for which could be amongst others: “there is significant public expectation that the TSB should independently make findings as to cause(s) and contributing factors”).
On Oct 5th 2017 the TSB changed the occurrence classification from “non-reportable incident” to “incident reportable”.
Runway 10 at Sint Maarten has 3 degree PAPI’s left and right of the runway as shown by a current LIDO RNAV (GNSS) runway 10 approach plate (however, not on the aerodrome chart). In either case (157 to 182 feet) the flight crew would have seen 4 reds from the PAPIs (4 reds at 2.5 degrees or below). Pilots used to describe the PAPIs as “next to useless”, there was also a discussion whether the PAPIs had been “retired”. END
- (Historic Final Rpt). Incident: Canada B789 near Hyderabad on Sep 19th 2017, ATC tries to divert aircraft despite several Mayday calls following two diversions
By Simon Hradecky, created Thursday, Oct 5th 2017 21:34Z, last updated Thursday, Oct 5th 2017 21:35Z
An Air Canada Boeing 787-900, registration C-FGEI performing flight AC-46 (dep Sep 18th) from Toronto,ON (Canada) to Mumbai (India) with 177 passengers and 14 crew, was on approach to Mumbai being cleared for the approach to Mumbai, when ATC cancelled the approach clearance due to a runway excursion by another aircraft, see Incident: Spicejet B738 at Mumbai on Sep 19th 2017, overran runway on landing. The aircraft initiated a missed approach at 3800 feet MSL and entered a hold at FL070, then FL080 and FL100. After about an hour the crew decided to divert to their planned alternate airport and set course, however, shortly afterwards ATC told the crew that the alternate was unable to accomodate them due to being at maximum capacity. The crew consulted with dispatch and decided to divert to Hyderabad (India). The aircraft climbed to FL250 and was enroute to Hyderabad when ATC told them, that Hyderabad also was unable to accomodate them due to being at maximum capacity. The flight crew declared Mayday due to being low on fuel, however, ATC instructed them to enter a hold and tried to divert them several times before giving them a direct route to Hyderabad following the fourth (!) Mayday declaration. The aircraft landed on Hyderabad’s runway 09L 118 minutes after aborting the approach to Mumbai.
The Canadian TSB reported: “The operator reported that ATC continued trying to divert the flight or attempted to place it in another hold. The flight crew had to declare MAYDAY four times before ATC cleared them for the approach into VOHS. The TSB is in contact with India’s AAIB.” END
- Accident: Maldivian DHC6 at Male on Oct 4th 2017, hard water landing
By Simon Hradecky, created Wednesday, Oct 4th 2017 19:42Z, last updated Wednesday, Oct 4th 2017 19:53Z
A Maldivian de Havilland DHC-6-300 Twin Otter on floats, registration 8Q-ISB performing a flight from Dhaalu Atoll to Male (Maldives) with 15 passengers and 3 crew, was on approach to Male’s Sea Port when the aircraft impacted the waters hard at the Sea Port and flipped over at about 11:18Z. The occupants were able to evacuate the aircraft in time. A crew member sustained minor injuries and was taken to a hospital, the other occupants escaped without injuries. The aircraft received substantial damage and became submerged with just the floats remaining above water.
The airline reported the crew attempted to land at the Sea Port, however, due to unexpected extreme weather the crew lost control resulting in a crash landing.
Maldives’ Civil Aviation Authority reported an accident occurred when an aircraft attempted to land at Male’s Water Aerodrome of Velana International Airport. The DHC-6-300 8Q-ISB sustained substantial damage, the 15 passengers and 3 crew were not injured, a number of occupants were taken to a hospital for checks and have been released in the meantime. The occurrence was rated an accident and is being investigated.END
- Incident: Sunwest DH8C at Conklin on Oct 3rd 2017, a real deer landing
By Simon Hradecky, created Wednesday, Oct 4th 2017 21:26Z, last updated Wednesday, Oct 4th 2017 21:32Z
A Sunwest Aviation de Havilland Dash 8-300, registration C-FNSA performing flight CNK-7123 from Edmonton,AB to Conklin Christina Lake,AB (Canada) with 43 passengers and 4 crew, landed on the MEG Energy Christina Lake Airstrip east of Conklin (there is a second aerodrome to the west of Conklin named Conklin Leismer Aerodrome) when the aircraft collided with two deer. The aircraft came to a stop with minor damage.
The Royal Canadian Mounted Police (RCMP) reported there was a collision at the Christina Lake Airstrip, east of Conklin, involving an aircraft and two deer. The two deer jumped out in front of the aircraft and hit the propeller. The aircraft received damage, the occupants remained uninjured. The RCMP did not report on the fate of the deer. The airstrip needed to be closed for 24 hours, the Canadian TSB has been informed about the occurrence.
According to the flight plan the flight was planned to Conklin Leismer Aerodrome.
Christina Lake Aerodome, located at N55.6283 W110.7503, features a gravel runway 08/26 of 1220 meters/4000 feet length. Leismer Aerodrome features a gravel runway 09/27 of 1600 meters/5250 feet length.END
- Incident: Swift AT72 near Alicante on Sep 9th 2017, stall in icing conditions
By Simon Hradecky, created Thursday, Sep 28th 2017 14:30Z, last updated Wednesday, Oct 4th 2017 17:41Z
A Swift Air Avions de Transport Regional ATR-72-212A on behalf of Air Europa, registration EC-KKQ performing flight UX-4050 from Alicante,SP to Madrid,SP (Spain) with 22 passengers and 4 crew, was cleared to climb to FL170 out of Alicante and was climbing through FL165 in icing conditions when the aircraft stalled. The crew recovered the stall, descended the aircraft to FL130 later climbing to FL150 again and continued to Madrid for a safe landing.
Spain’s CIAIAC reported the aircraft suffered a stall while climbing to FL170 in an icing zone. The crew recovered the stall, declared emergency and continued the flight to Madrid. The occurrence was rated a serious incident and is being investigated by the CIAIAC.
The occurrence aircraft remained on the ground for 42 hours before returning to service.
On Oct 4th 2017 the CIAIAC released more details stating the flight was planned at FL170, up to FL150 moderate icing conditions were expected. While climbing through FL130 the crew activated all three layers of protection against ice. About 7 minutes later, just before the aircraft was about to level off at FL170, the aircraft entered stall, the autopilot disconnected, the aircraft experienced a pronounced loss of altitude and pronounced “warping”. The aircraft was recovered by the crew. The crew declared Mayday and received priority to Madrid. During recovery there was a blockage of the rudder, which was later identified to be related to the rudder travel limiter. There were no injuries to the occupants, one passenger suffered from anxiety during the occurrence.END
6). Historic Report: Sprint SF34 at Kirkwall on Mar 20th 2017, descended below minimum safe altitude on approach
By Simon Hradecky, created Tuesday, Oct 3rd 2017 17:45Z, last updated Tuesday, Oct 3rd 2017 17:45Z
A Sprintair Saab 340A on behalf of Loganair, registration SP-KPV performing mail flight LM-757 from Sumburgh,SC to Kirkwall,SC (UK), was on approach to Kirkwall performing the ARC procedure to join the ILS runway 27 about 11nm out of the aerodrome when the aircraft descended below minimum safe altitude. Following ATC intervention the aircraft returned to safe altitude and continued for a safe landing on Kirkwall’s runway 27.
Poland’s PKWBL reported in their brief bulletin in Polish that the probable cause of the occurrence was the crew’s omission to switch the altimeter to QNH pressure and inaccurate processing of the approach checklist.
The PKWBL reported the crew was on the 11nm arc to join the ILS runway 27, minimum safe altitude 1600 feet MSL, when the aircraft according to flight data recorder descended to 960 feet MSL (aerodrome elevation 58 feet MSL). At the same time the crew confirmed an altitude of 1900 feet MSL.
The PKWBL reported at least one member of the flight crew was familiar with the procedures at Loganair, both pilots had received briefing and information for operation in the UK and had carefully prepared for the airports they were operating into.END
7)ncident: Jeju B738 at Jeju on Sep 29th 2017, rejected takeoff on ATC instruction, possible ATC error
By Simon Hradecky, created Friday, Sep 29th 2017 20:40Z, last updated Friday, Sep 29th 2017 20:44Z
A Jeju Air Boeing 737-800, registration HL7779 performing flight 7C-510 from Jeju to Busan (South Korea) with 150 people on board, was cleared for takeoff and was accelerating for takeoff from Jeju’s runway 07 when tower instructed the aircraft to stop. The crew rejected takeoff at high speed (above 95 knots over ground) and brought the aircraft to a stop about 2500 meters/8200 feet down the runway just short of the intersection with crossing runway 13/31. A number of tyres deflated disabling the aircraft on the runway.
Runway 07/25 needed to be closed for about one hour until the aircraft could be towed off the runway.
The airline reported the crew were instructed to reject takeoff and complied with the instruction. Some aircraft equipment was damaged, the brakes overheated causing a number of tyres to deflate. Apparently tower made a mistake, a Navy aircraft was departing crossing runway 13.
A ground observer reported a Navy aircraft was landing on runway 13 at the time.
A replacement Boeing 737-800 registration HL8261 reached Busan with a delay of 3 hours. END
- (Previously Rptd). Accident: Ural A321 at St. Petersburg on Sep 28th 2017, mother and infant fell through stairs
By Simon Hradecky, created Thursday, Sep 28th 2017 19:37Z, last updated Thursday, Sep 28th 2017 19:37Z
An Ural Airlines Airbus A321-200, registration VQ-BOB performing flight U6-91 from Moscow Domodedovo to St. Petersburg (Russia), completed an uneventful flight with a safe landing in St. Petersburg and taxied to the apron. The passengers disembarked via stairs at the front left main door, 90 passengers disembarked without problem, however, when a mother with her one year old infant stepped onto the stairs the platform collapsed and mother and infant fell down onto the concrete apron. The infant is reported in critical condition with traumatic brain injuries, the mother received serious injuries (fractures of her left leg) END