MaxAvSafety: WW Commercial Accident/Incident Rpt

MaxSez: FYI, Posted every Sunday as Professional Knowledge Gained. Pls add follow ups, related first person accounts, photo/videos, and unreported
like items by comment. Thanks

Saturday Aug 19th 2017
Incident Skywest CRJ2 at Kalamazoo on Aug 18th 2017, unsafe gear
Incident Skywest CRJ2 at Grand Forks on Aug 18th 2017, bird strike
Incident Lufthansa B748 over Atlantic on Aug 19th 2017, engine problem
Incident Europa AT72 at Ibiza on Aug 18th 2017, engine shut down in flight
Incident Cham Wings A320 at Khartoum on Aug 19th 2017, runway excursion on landing
Friday Aug 18th 2017
Incident Eurowings A319 at Stuttgart on Aug 13th 2017, rejected takeoff due to one bird strike damaging both engines
Incident Sky Regional E175 near Indianapolis on Aug 13th 2017, multiple EICAS messages result, maintenance action: reset
Incident Atlasglobal A320 near Istanbul on Jul 27th 2017, hail strike
Accident Cavok AN74 at Sao Tome on Jul 29th 2017, rejected takeoff due to flock of birds results in runway overrun
Incident American B738 at Chicago on Aug 17th 2017, bird strike
Incident United B739 at Chicago on Aug 17th 2017, bird strike
Incident Malaysia B738 at Jakarta on Jun 13th 2017, temporary runway excursion, burst tyre on landing
Accident Pelita AT72 at Jakarta on Mar 19th 2017, burst both nose tyres on landing
Thursday Aug 17th 2017
Incident Tunis A320 near Nice on Aug 17th 2017, loss of cabin pressure
Incident Indigo A20N near Nagpur on Aug 16th 2017, engine shut down in flight
Incident Calm AT72 at Churchill on Aug 13th 2017, dip in runway, nose gear did not retract
Incident Lufthansa A388 near Montreal on Aug 2nd 2017, fire in cabin
Accident American A333 near Long Island on Aug 5th 2017, turbulence injures 19
Incident Avianca A320 near Cali on Jul 3rd 2017, GPWS prevents flight into terrain
Wednesday Aug 16th 2017
Incident Pegasus A320 at Gulyali on Aug 16th 2017, bird strike
Incident Shaheen A319 at Lahore on Aug 16th 2017, cabin did not pressurize
Incident Wasaya DH8A near Thunder Bay on Aug 9th 2017, whistling cockpit, leaking hydraulics
Incident France B772 near Halifax on Aug 10th 2017, severe turbulence believed to be wake from a B744
Incident CAA F50 at Beni on Aug 1st 2016, brakes problem
Crash Safari Express F27 at Serengeti on Aug 31st 2014, lost height while enroute at FL170
Accident Aero-Pioneer F27 at Garbaharey on Jun 3rd 2017, right main gear struck top of wall prior to touch down
Incident Jet Airways B773 at Amsterdam on Apr 21st 2017, tailstrike on departure
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
Tuesday Aug 15th 2017
Incident Avianca A319 at Montevideo on Aug 13th 2017, flock of birds
Incident Flybe DH8D at Birmingham on Aug 14th 2017, gear problem after departure
Incident Jetblue A320 near Bermuda on Aug 14th 2017, electrical odour in cockpit
Incident Porter DH8D at Newark on Jul 18th 2017, smell of smoke in cockpit and cabin
Incident China Airlines B738 near Fukuoka on Aug 15th 2017, engine generator problems
Incident Lufthansa A343 near Cologne on Aug 13th 2017, engine shut down in flight
Incident Republic E175 at Toronto on Aug 14th 2017, runway incursion
Monday Aug 14th 2017
Incident British Airways A321 near Paris on Aug 7th 2017, engine shut down in flight
Incident Transavia B738 at Amsterdam on Aug 14th 2017, cabin did not pressurize
Incident Delta B763 near London on Aug 13th 2017, loss of cabin pressure
Incident Canada A320 at Toronto on Aug 6th 2017, could not retract flaps
Incident Envoy E175 at Toronto on Aug 8th 2017, runway incursion
Accident Silver SF34 at Orlando on Aug 12th 2017, turbulence injures 5
Incident Jetblue A320 at New York on Aug 13th 2017, bird strike
Sunday Aug 13th 2017
Incident KLM Cityhopper E190 near Genoa on Aug 13th 2017, loss of cabin pressure
Incident Skywest CRJ2 near Buffalo on Aug 12th 2017, smoke in cockpit
Incident ANA B772 near Tokyo on Aug 12th 2017, cabin did not pressurize
Saturday Aug 12th 2017
Incident Gol B738 near Curitiba on Aug 10th 2017, smoke indication
Incident Lufthansa A343 at Cape Town on Aug 10th 2017, could not fully retract landing gear
Incident Baltic DH8D near Riga on Aug 12th 2017, oil pressure indication problem
Incident Hawaiian B763 over Pacific on Aug 11th 2017, smoke in cockpit
Friday Aug 11th 2017
Incident PSA CRJ2 near Raleigh Durham on Aug 11th 2017, engine problem
Incident Canada A320 enroute on Aug 1st 2017, hydraulic failure
(AvHerald)

11 Likes

Could of been a disaster. Also, this is one of the reasons why I don’t want to be on a A380.

2 Likes

@NismoKits. MaxSez: FYI and interests.

Incident: Lufthansa A388 near Montreal on Aug 2nd 2017, fire in cabin
last updated Thursday, Aug 17th 2017 20:36Z
A Lufthansa Airbus A380-800, registration D-AIMI performing flight LH-440 from Frankfurt/Main (Germany) to Houston Intercontinental,TX (USA) with 486 passengers and 24 crew, was enroute at FL380 near Montreal,QC (Canada) when a battery fire broke out in the cabin of the aircraft, which was extinguished by cabin crew. The aircraft continued to Houston for a safe landing about 4 hours later.

The FAA confirmed on Monday Aug 7th 2017, that there had been an in-cabin battery incident. On Friday Aug 4th the FAA had advised that they were not (yet) aware of such an occurrence. The FAA added on Monday that they are working with Lufthansa to find out more details about the occurrence.

A passenger in the aft cabin reported the aircraft was enroute near Montreal when a fire alarm triggered and smell of smoke developed in the cabin. The captain announced a short circuit had triggered a fire in the cabin, later reported that a silicon battery had been wedged into a seat of the business class causing a short circuit and a fire of the battery. The passenger reported everything except the exit signs went dark, only sirenes could be heard. Obviously vents were opened, an air rush exiting the cabin could be felt. Flight attendants battled the fire with fire extinguishers. After the fire was out the captain announced, that there had been no damage to the aircraft, hence they were able to continue to Houston.

On Aug 8th 2017 the airline confirmed the occurrence reporting an external power bank used to charge smartphones, tablets etc. caught fire after it got trapped in a business class seat. The airline routine warns passengers to avoid getting their personal devices and batteries be trapped in seats.

On Aug 17th 2017 the Canadian TSB reported the aircraft was enroute about 260nm northeast of Montreal when the flight crew was informed about heavy electrical smoke/fire underneath passenger seat 10C. The source of the smoke and fire was identified as a passenger power bank stuck in the seat mechanism. Cabin crew extinguished the fire using three fire extinguishers. Once the fire was extinguished the smell dissipated after completion of the smoke removal procedure. No emergency was declared and the aircraft continued to destination. Maintenance repaired the seat and returned the aircraft to service. (AvHerald)

5 Likes

Wait what? I don’t understand why this is here lol.

2 Likes
1 Like

Because of this maybe ^^^

1 Like

How in the world? Max please provide info

not max but info from avherald
n Air France Boeing 777-200, registration F-GSPK performing flight AF-333 from Boston,MA (USA) to Paris Charles de Gaulle (France), was enroute at FL350 about 50nm southwest of Halifax,NS (Canada), the flight crew requested a climb to FL360.

A KLM Boeing 747-400, registration PH-BFC performing flight KL-24 from Houston Intercontinental,TX (USA) to Amsterdam (Netherlands), was enroute at FL370 on the same airway about 10nm ahead of the Air France Boeing 777.

The Boeing 777-200 was cleared to climb to FL360, however reported severe turbulence after reaching FL360.

The Canadian TSB reported at that point the Boeing 777-200 was 12nm behind the KLM 747. The severe turbulence is believed to have been wake turbulence from the 747.

The B772 climbed further to FL370. Both aircraft continued to their destinations without further incidents.

1 Like

Oh ok that makes a lot more sense now. Thanks for the info.

Because AvHerald updates the incident reports when there’s a new development/progress from some certain past incidents. So don’t be surprised if you find an incident report from 2009 but listed on Max’ Incident report 😉

2 Likes

@Qantas737guy… MaxSez: Appreciate responding to a request for my input in my Topic. Not very civil or courteous on your part. Care to discuss it meet me via PM. Gooday.

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