The geek with a cynical view

Thursday, January 1, 2015

Accidents and incidents involving the Airbus A320 family 2014

Accidents and incidents involving the Airbus A320 family

The Airbus A320 family accidents and incidents are counting 60 aviation occurrences, including 24 hull-loss accidents with a total of 789 fatalities as of April 2012.[1][2][3][4][5] There have been 50 incidents of glass cockpit blackout.[6][7][8]

Contents [hide]
1 Accidents and incidents
1.1 A319
1.2 A320
1.3 A321
2 See also
3 References

Accidents and incidents[edit]
A319[edit]
On 1 July 2002, America West Airlines Flight 556, using an Airbus A319, was ordered back to the terminal at Miami International Airport after the pilots were found to be intoxicated; both were given prison sentences; the passengers continued their flight to Phoenix with other airlines.
On 19 January 2003, Northwest Airlines Airbus A319-114 and registered as N313NB, was damaged by maintenance personnel at LaGuardia Airport being taxied from a maintenance area to the gate, striking the gate and a 757, collapsing the nosegear. The Airbus was damaged beyond repair and written off.[9]
On 12 August 2010, Azerbaijan Airlines Flight 75, using an Airbus A319-111 and registered as 4K-AZ04, suffered a collapse of the undercarriage when the aircraft departed the runway on landing at Atatürk International Airport, Istanbul, Turkey. The aircraft was substantially damaged but all 127 passengers and crew escaped unharmed.[10]
On 24 September 2010, Wind Jet Flight 243, using an Airbus A319-132 and registered as EI-EDM, landed short of the runway and broke an undercarriage when the aircraft attempted landing at Palermo Airport, Italy. Preliminary reports name windshear as one possible cause for the accident. The aircraft was seriously damaged and was written off but stopped in the grass out of the runway. About 20 passengers were injured.[11]
On 24 May 2013, British Airways Flight 762, using an Airbus A319-131 and registered as G-EUOE, returned to London Heathrow Airport after fan cowl doors detached from both engines shortly after take off. During the approach a fire broke out in the right engine and persisted after the engine was shut down. The aircraft landed safely with no injuries to the 80 people on board. A preliminary accident report revealed that the cowlings had been left unlatched following overnight maintenance. The separation of the doors caused airframe damage and the right hand engine fire resulted from a ruptured fuel pipe.[12]
A320[edit]
On 26 June 1988, Air France Flight 296, using a recently introduced and just months-old Airbus A320-111, crashed into the tops of trees beyond the runway on a demonstration flight at Mulhouse-Habsheim Airport, France. Three passengers (of 136 on board) were killed.
On 14 February 1990, Indian Airlines Flight 605, using an Airbus A320-231, carrying 146 people, crashed on its final approach to the HAL Airport, Bangalore. 88 passengers and four crew members were killed.[13]
On 20 January 1992, Air Inter Flight 148, using an Airbus A320-111, crashed into a high ridge near Mount Sainte-Odile in the Vosges mountains while on final approach to Strasbourg at the end of a scheduled flight from Lyon. This accident resulted in the deaths of 87 of the aircraft's occupants (six crew members, 90 passengers).
On 14 September 1993, Lufthansa Flight 2904, using an Airbus A320-211, coming from Frankfurt am Main with 70 people, crashed into an earth wall at the end of the runway at Warsaw. A fire started in the left wing area and penetrated into the passenger cabin. The training captain and a passenger died.
On 22 March 1998, Philippine Airlines Flight 137, using an Airbus A320-214, crashed and overran the runway of Bacolod City Domestic Airport, RPVB, in Bacolod, Philippines, plowing through homes near it. None of the passengers or crew died, but many were injured and three on the ground were killed.
On 23 August 2000, Gulf Air Flight 072, using an Airbus A320-212, crashed into the Persian Gulf on a go-around during a night visual approach to Bahrain Airport. All 143 passengers and crew on board lost their lives.
On 7 February 2001, Iberia Flight 1456, using an Airbus A320-214, carrying 143 people, crashed on landing at Bilbao Airport in heavy low level turbulence and gusts. All occupants survived; aircraft had to be scrapped.[14]
On 21 September 2005, JetBlue Airways Flight 292, using an Airbus A320-232, executed an emergency landing at Los Angeles International Airport (LAX) after the nose wheels jammed in an abnormal position. No one was injured.
On 3 May 2006, Armavia Flight 967, using an Airbus A320-211, crashed into the Black Sea while attempting to conduct a go-around following its first approach to Sochi Airport, Russia. All 113 passengers and crew on board lost their lives. The accident was aPilot error / Controlled flight into terrain accident.[15]
On 17 July 2007, TAM Airlines Flight 3054, using an Airbus A320-233, was not able to stop while landing at Congonhas International Airport in São Paulo, Brazil. One engine thrust reverser had been deactivated. As of 2009, the accident was caused by pilot error(by positioning the left throttle into reverse with the right engine throttle being in the climb power setting) and by bad weather (this was possibly exaggerated by the lack of effective drainage grooving on the runway). All 187 passengers and crew died with 12 fatalities on the ground, the ground fatalities mainly from the TAM headquarters and the petrol station at the end of the runway, totaling 199 people. This crash is the deadliest accident involving the A320.[16]
On 30 May 2008, TACA Flight 390, using an Airbus A320-233, from San Salvador, overran the runway after landing at Toncontín International Airport in Tegucigalpa, Honduras, in bad weather conditions. There were five fatalities plus two on the ground.[17]
On 27 November 2008, XL Airways Germany Flight 888T, a test flight of an A320-232 stalled in a low speed test and control could not be regained, causing the aircraft to crash into the sea off the southern French coast. The aircraft was on lease by XL Airwaysand scheduled to be returned to Air New Zealand. All seven people aboard died.[18][19][20]

US Airways Flight 1549, ditched in the Hudson River in 2009 with all passengers surviving
On 15 January 2009, US Airways Flight 1549, using an Airbus A320-214, en route from New York City LaGuardia Airport to Charlotte, North Carolina, ditched into the Hudson River seven minutes after takeoff. All 150 passengers and five crew survived, with only five serious injuries. The accident was due to a collision with a flock of Canada geese, which disabled both engines.[21] The entire airframe including the wings, has been preserved at the Carolinas Aviation Museum and is now on display. This was also the first ditching of an A320.
On 29 August 2011, Gulf Air Flight 270, using an Airbus A320-214, from Bahrain to Cochin carrying 143 people, skidded off the runway on landing due to pilot error.[22] The weather was poor with heavy rain and strong winds. The aircraft was badly damaged and seven passengers were injured. Some people were reported to have jumped from an emergency exit when the evacuation slide failed to deploy.[23][24]
On 20 September 2012, Syrian Air Flight RB-501, using an Airbus A320-212, collided in mid-air with a military helicopter. The A320 lost half its vertical stabilizer but landed safely; the helicopter crashed, killing three of its occupants.[citation needed]
On 2 June 2013, Cebu Pacific Flight 971, using an Airbus A320-214 and registered as RP-C3266 carrying 165 passengers inbound from Manila, overshot the runway at Francisco Bangoy International Airport in Davao Cityduring a heavy rain. There were no fatalities and injuries, however the plane was heavily damaged.[25]
On 28 December 2014, Indonesia AirAsia Flight 8501 disappeared midway into the flight of more than two hours from the Juanda International Airport with 162 on board.[26]
A321[edit]
On 1 September 2001, an Aero Lloyd Airbus A321, operating a charter flight from Catania-Fontanarossa Airport, Italy to Berlin Tegel Airport, Germany, had an attempted hijacking shortly after take off. The plane was diverted to Naples Airport in Italy where it made an emergency landing and the hijacker was arrested. There is a mix of reports ranging from the man using wax candles as dynamite and that of a panic attack. Nobody was injured in the incident.
On 21 March 2003, TransAsia Airways Flight 543, using an Airbus A321 and registered as B-22603 on a flight from Taipei Songshan Airport, landed at Tainan Airport and collided with a truck on the runway. The truck went on the runway without noticing the incoming plane. The 175 passengers and crew were uninjured but the two people in the truck were injured. The aircraft was severely damaged in the accident and was written off.[27]
On 28 July 2010, Airblue Flight 202, an Airbus A321 flying from Karachi to Islamabad, crashed in Margalla Hills in Islamabad, Pakistan. The weather was poor with low visibility. During a non-standard self-created approach procedure below Minimum Descent Altitude the aircraft collided with terrain after the captain ignored a total of 21 cockpit warnings to pull-up. 146 passengers and six crew were on board the aircraft. There were no survivors.[28] The commander, Pervez Iqbal Chaudry, was one of Airblue's most senior pilots with more than 35 years' experience. The accident was a Pilot error / Controlled flight into terrain accident and the only fatal accident involving the A321.[29]
See also[edit]
Airbus
References[edit]

Jump up^ Airbus A320 occurrences. Aviation Safety, 2 April 2012.
Jump up^ Airbus A320 hull-loss occurrences. Aviation Safety, 2 April 2012.
Jump up^ Airbus A320 statistics. Aviation Safety, 2 April 2012.
Jump up^ "JACDEC's Airliner Safety Statistics: Aircraft". JACDEC. 17 May 2007.
Jump up^ NTSB Accident Database search on A320. NTSB. Retrieved 14 April 2012.
Jump up^ Katz, Peter."Glass-Cockpit Blackout". Plane & Pilot Magazine, 21 October 2008. Retrieved on 14 April 2012.
Jump up^ NTSB Safety Recommendation A-08-53 through −55. NTSB, 22 July 2008. Retrieved on 14 April 2012.
Jump up^ Air Accidents Investigation: 2/2008 G-EUOB. Aaib.gov.uk, 22 October 2005. Retrieved on 12 January 2011.
Jump up^ "ASN Aircraft accident summary".
Jump up^ "4K-AZ04 Accident description". Aviation Safety Network.Archived from the original on 19 August 2010. Retrieved13 August 2010.
Jump up^ "EI-EDM Accident description". Aviation Safety Network.Archived from the original on 2 October 2010. Retrieved25 September 2010.
Jump up^ "AAIB special bulletin S3/2013". Retrieved 3 June 2013.
Jump up^ Smith, Derek J. (2 May 2001). "Transportation Disasters – Aerospace".[dead link]
Jump up^ "Accident description Iberia EC-HKJ". Aviation Safety Network. 13 July 2013. Retrieved 13 July 2013.
Jump up^ "Final Accident Report" (PDF). Russian Interstate Aviation Committee. Archived from the original on 30 August 2007. Retrieved 7 August 2007.
Jump up^ "Accident description PR-MBK". Aviation Safety Network. Retrieved 16 July 2011.
Jump up^ "Four Dead After Airliner Overshoots Honduras runway". CNN. 30 May 2008. Archived from the original on 31 May 2008. Retrieved 30 May 2008.
Jump up^ "Official: Airbus A320 crashes into sea off France". CNN. 27 November 2008. Archived from the original on 5 December 2008. Retrieved 27 November 2008.
Jump up^ Field, Michael (28 November 2008). "Five New Zealanders in Air NZ plane crash". Fairfax New Zealand. Archived from the original on 9 December 2008. Retrieved 27 November 2008.
Jump up^ "Airbus jet crashes in test flight". BBC News. 27 November 2008. Archived from the original on 28 November 2008. Retrieved 27 November 2008.
Jump up^ Augstums, Ieva; Mitch Weiss (15 January 2009). "Charlotte final destination for most on down plane". FoxNews.com. Associated Press.
Jump up^ "Gulf Air skids in Cochin". NDTV, 29 August 2011.
Jump up^ "Gulf Air A320 Skids off Runway in Kochi". Aviation Week. 29 August 2011.
Jump up^ "Gulf Air plane skids off runway in Indi". BBC News. 29 August 2011.
Jump up^ Manlupig, Karlos (2 June 2013). "Cebu Pacific plane overshoots Davao airport runway". Retrieved 3 June 2013.
Jump up^ "AirAsia flight QZ8501 from Indonesia to Singapore missing". BBC News. 28 December 2014. Retrieved 28 December 2014.
Jump up^ "Accident Transasia Airlines Flight 543 A321 B-22603 | Airfleets aviation". Airfleets.net. 22 March 2003. Retrieved 17 May2012.
Jump up^ "Crash: AirBlue A321 near Islamabad on Jul 28th 2010, impacted mountaineous terrain near the airport". Avherald.com. Retrieved 17 May 2012.
Jump up^ "Accident description Airblue AP-BJB". Aviation Safety Network. 13 July 2013. Retrieved 13 July 2013.

Sunday, December 28, 2014

Indonesia AirAsia Flight 8501

Indonesia AirAsia Flight 8501
From Wikipedia, the free encyclopedia

This article documents an ongoing aviation incident. Information may change rapidly as the event progresses, and initial news reports may be unreliable. (December 2014)

Indonesia AirAsia Flight 8501
PK-AXC, the missing aircraft, pictured in 2011
Incident summary
Date 28 December 2014
Summary Missing
Site Last known position over Java Sea

3.2466°S 109.3682°E Coordinates:

3.2466°S 109.3682°E [1]
Passengers 155
Crew 7
Missing 162 (all)
Aircraft type Airbus A320-216
Operator Indonesia AirAsia
Registration PK-AXC
Flight origin Juanda International Airport, Surabaya, Indonesia
Destination Singapore Changi Airport

Indonesia AirAsia Flight 8501 (QZ8501/AWQ8501) is an Indonesia AirAsia Airbus A320-216 flight that went missing en route to Singapore from Surabaya, Indonesia on 28 December 2014[2] with 155 passengers and 7 crew on board.[3]

Indonesia AirAsia is an affiliate of Malaysian low-cost airline AirAsia. The incident is the third in 2014 involving a Malaysian airline or its affiliate(s), after the loss of Malaysia Airlines Flights 370 and 17 earlier in the year.[4]

Contents [hide]
1 Disappearance
1.1 Timeline of disappearance
2 Aircraft
3 Passengers and crew
4 Search and rescue effort
5 Response
6 See also
7 Notes
8 References
9 External links

The flight took off from Juanda International Airport, Surabaya, at 05:35 Western Indonesian Time (WIB, UTC+7) and was scheduled to land at Singapore Changi Airport at 08:30 Singapore Standard Time (SST, UTC+8).[5] The plane had been under Indonesian air traffic control when it requested to deviate from its original flight path due to poor weather conditions.[6] The pilot had requested to climb to 38,000 feet (11,600 m) to avoid thick clouds,[7] although the final altitude indicated by the transponder and collected by Flightradar24 was 32,000 ft (9,750 m).[5] The plane lost contact with air traffic control at 06:17 WIB[a] while travelling over theJava Sea between Kalimantan (Borneo) and Java,[3] still under Indonesian air traffic control, at normal cruising altitude and speed.[10] A meteorological analysis revealed that the aircraft was traversing a storm cluster during the minutes prior to its disappearance.[11]

No distress signal was sent from the missing aircraft, the Indonesian Transport Ministry said.[12][13]

The aircraft was operated by AirAsia Indonesia, and the Air Operator Certificate was issued by the Indonesia Director General of Civil Aviation. According to International Civil Aviation Organization (ICAO) Indonesia is below, or does not meet the ICAO eight critical safety elements established by ICAO.[14] Indonesia is currently listed by the U.S. FAA International Aviation Safety Assessment Program (IASA Program) as Category 2 meaning that Indonesia does not meet International Civil Aviation Organization International (ICAO) Standards for Air Operator oversight. Air Asia Indonesia does not fly into the European Union and therefore not on the EU Blacklist. [15] [16]
Timeline of disappearance[edit]
Elapsed (HH:MM)TimeEvent
UTC WIB
UTC+7SST
UTC+8
00:00 27 December 28 December Take-off from Juanda International Airport [5]
22:35 05:35 06:35
00:42 23:17 06:17 07:17 Lost from Indonesian air traffic control radars[9]
00:49 23:24 06:24 07:24 Lost radio contact with air traffic control[9]
01:55 28 December 07:30 08:30 Missed scheduled arrival at Singapore Changi Airport (WSSS)[5]
00:30

Aircraft[edit]

The aircraft is an Airbus A320-216,[b] with serial number 3648, registered as PK-AXC. It first flew on 25 September 2008, and was newly delivered to AirAsia on 15 October 2008. The aircraft had accumulated approximately 23,000 flight hours in some 13,600 flights. It had undergone its most recent scheduled maintenance on 16 November 2014.[8] The aircraft is powered by two CFM International CFM56-5B6 engines and is configured to carry 180 passengers.[17]
Passengers and crew[edit]

AirAsia released the nationalities of the 162 passengers and crew which include 144 adults, 17 children and 1 infant. The cabin crew consisted of four flight attendants. Additionally, AirAsia had an engineer as part of the aircrew onboard.[18]

The pilots aboard the flight were:[19]
Captain Iriyanto, who had a total of 20,537 flying hours, of which 6,100 were with AirAsia Indonesia on the Airbus A320.
First Officer Rémi Emmanuel Plesel, who had a total of 2,275 flying hours with AirAsia Indonesia[20]
People on board by nationality[21]NationNo.

Indonesia [c] 155

South Korea 3

France [d] 1

Malaysia 1

Singapore 1

United Kingdom 1
Total 162

Search and rescue effort[edit]

Search and rescue operations have been ongoing under the guidance of the Civil Aviation Authority of Indonesia.[8][22] The search was suspended at 7.45 pm local time on 28 December due to darkness and bad weather, to be resumed in daylight.[23] An operations center to coordinate search efforts is being set up in Pangkal Pinang.[24]

Shortly after being confirmed missing, Indonesia's National Search and Rescue Agency deployed seven ships and two helicopters to search the shores of Belitung and Kalimantan.[25] The Indonesian Navy and the provincial Indonesian National Police Air and Water Unit each sent out search and rescue teams.[26] In addition, an Indonesian Air Force Boeing 737 reconnaissance aircraft was dispatched to the last known location of the airliner.[27]

The Indonesian Navy confirmed that it had dispatched four ships by the end of the first search day, joining the initial search efforts. Further aircraft, amongst them a CASA/IPTN CN-235, have also joined from the Indonesian Air Force.[28] The Indonesian Army deployed ground troops to search the shores and mountains of adjacent islands.[29]

Singapore's Rescue Coordination Centre (RCC), managed by the Civil Aviation Authority of Singapore (CAAS) and supported by various agencies, including the Republic of Singapore Air Force (RSAF), has also initially deployed a C-130 Hercules aircraft to aid in the search and rescue operation.[30] An officer from Singapore will be deployed to Jakarta to coordinate with the Indonesian authorities on the search operations, and two more C-130 Hercules aircraft will be deployed for the second day of the search and rescue operation.[31]

Malaysia's government has also set up a rescue coordination center at Subang and has deployed three military vessels and three aircraft, including a C-130 Hercules, to assist in search and rescue operation.[32][33][34]
Response[edit]

Secondary radar image that has been leaked (released without permission) and shows Flight 8501 (circled in yellow) at an altitude of 36,300 ft (11,100 m) and climbing, while only travelling at 353 kn (654 km/h; 406 mph) ground speed.

Indonesia AirAsia, following the disappearance, changed its website and social media branding to greyscale images, in mourning for the presumed deaths of the passengers.[35][36] An emergency call center has also been established by the airline, for family or friends of those who may have been on board the aircraft.[8]

An emergency information center was set up at Juanda International Airport, providing hourly updates and lodging for relatives.[37] Smaller posts were also opened at Soekarno–Hatta International Airport [38] and Sultan Hasanuddin International Airport.[39]

Immediately following the incident, unconfirmed and speculative early reports suggested that the flight had crashed off the island of Belitung in Indonesia.[40][41][42]

Prime Minister of Singapore Lee Hsien Loong expressed his condolences over the missing AirAsia flight via Twitter: "Saddened to hear of missing flight #QZ8501. My thoughts are with the passengers and their families. - LHL."[43] Prime Minister Lee also called President Joko Widodo and offered help in the search as stated in another tweet.

Prime Minister of Malaysia Najib Razak also issued an announcement via Twitter: "Very sad to hear that AirAsia Indonesia QZ8501 is missing. My thoughts are with the families. Malaysia stands ready to help."[44]

Prime Minister of Australia Tony Abbott contacted Indonesian President Widodo offering assistance in the search for the aircraft. A statement provided by his office stated that "Australia would do whatever we humanly could to assist" and that they had a P-3 Orion aircraft on standby to help assist in the search.[45]

India has put on standby three ships and a maritime surveillance aircraft for assistance in the search operation. Indian Navy sources said one ship in Bay of Bengal and another two in Andaman Sea have been put on standby. Along with these, a Boeing P-8I aircraft has also been put on standby.[46]
See also[edit]

Saturday, December 20, 2014

Misfortune Cookie Flaw Puts 12 Million Routers at Risk

http://recode.net/2014/12/18/misfortune-cookie-flaw-puts-12-million-routers-at-risk/

Misfortune Cookie Flaw Puts 12 Million Routers at Risk

Researchers at the security software company Check Point say they’ve discovered a serious vulnerability lurking inside the routers and modems used to deliver Internet connectivity to 12 million homes and small businesses around the world, and it’s going to be a complicated matter to fix it.

Dubbed the Misfortune Cookie, the weakness is present in cable and DSL modems from well-known manufacturers like D-Link, Huawei and ZTE, and could allow a malicious hacker to hijack them and attack connected computers, phones and tablets. An attacker exploiting Misfortune Cookie could also monitor a vulnerable Internet connection, stealing passwords, business data or other information. Check Point didn’t disclose how an attack might be carried out. Spokespeople for D-Link, Huawei and ZTE had no immediate comment on the vulnerability.

In an interview with Re/code, Shahar Tal, a researcher at Israel-based Check Point, said the company traced the vulnerability to a programming error made in 2002. That error originated with Allegro Software, the Massachusetts-based developer of RomPager, which unwittingly introduced it into the widely used embedded Web server.

“It was a very simple error that seemed benign at first,” Tal said. “When we took it back to the company, they seemed surprised. The severity was not something they expected.”

The list of devices affected by Misfortune Cookie includes some 200 products from more than 20 companies. All told there are more than 12 million devices with the vulnerability in use today, including some that were manufactured as recently as this year. And yet to date, no real-world attacks using Misfortune Cookie have been detected.

Reached for comment, Allegro Software downplayed the severity of the vulnerability and its responsibility for it. “It’s a 12-year-old bug that was fixed nine years ago,” said CEO Bob Van Andel. He conceded, however, that many of Allegro’s customers haven’t bothered to install the code that protects RomPager against Misfortune Cookie — nor can the company force them to do so.

“There is no contractual obligation on the part of our customers to use the latest code,” Van Andel said. “We have more than 300 customers. Some of them keep up on the maintenance of the code we sell them, but the vast majority do not. They run their own insurance risk when they make that decision.”

So what’s to be done if you suspect your router or modem is among those affected by Misfortune Cookie? Tal suggests calling the manufacturer or the company that provided the equipment and requesting an upgrade.

Sunday, December 14, 2014

A Message From Universal Pictures About Angelina Jolie

Sunday, December 7, 2014

The TPP is the dirtiest deal you've never heard of.

Tuesday, December 2, 2014

Food Recall Warning - Your Fresh Market brand ground beef products recalled due to E. coli O157

Food Recall Warning - Your Fresh Market brand ground beef products recalled due to E. coli O157

Recall date:

December 1, 2014
Reason for recall:

Microbiological - E. coli O157
Hazard classification:

Class 1
Company / Firm:

Cargill Meat Solutions (Est. 700)
Distribution:

Alberta, British Columbia, Manitoba, Saskatchewan
Extent of the distribution:

Consumer
Reference number:

9497

Recall details

Ottawa, December 1, 2014 - Cargill Meat Solutions (Est. 700) is recalling Your Fresh Market brand ground beef products from the marketplace due to possible E. coli O157 contamination. Consumers should not consume the recalled products described below.

The following products have been sold at Walmart stores in Alberta, British Columbia, Manitoba and Saskatchewan.

Recalled products

Brand Name

Common Name

Size

Code(s) on Product

UPC

Your Fresh Market

Extra Lean Ground Beef Sirloin

475 g

Best Before 2014.NO.28

6 05388 18363 7

Your Fresh Market

Extra Lean Ground Beef

475 g

Best Before 2014.NO.28

6 05388 18369 9

Your Fresh Market

Medium Ground Beef

475 g

Best Before 2014.NO.28

6 05388 18365 1

Your Fresh Market

Lean Ground Beef

475 g

Best Before 2014.NO.28 and 2014.NO.29

6 05388 18376 7

Your Fresh Market

Extra Lean Ground Beef

900 g

Best Before 2014.NO.28

6 05388 18372 9

Your Fresh Market

Lean Ground Beef

900 g

Best Before 2014.NO.28

6 05388 18378 1

Your Fresh Market

Lean Ground Beef

1.6 kg

Best Before 2014.NO.28 and 2014.NO.29

6 05388 18379 8

What you should do

Check to see if you have recalled products in your home. Recalled products should be thrown out or returned to the store where they were purchased.

Food contaminated with E. coli O157 may not look or smell spoiled but can still make you sick. Symptoms can include nausea, vomiting, mild to severe abdominal cramps and watery to bloody diarrhea. In severe cases of illness, some people may have seizures or strokes, need blood transfusions and kidney dialysis or live with permanent kidney damage. In severe cases of illness, people may die.
Learn more about the health risks
Sign up for recall notifications by email or follow us on Twitter
View our detailed explanation of the food safety investigation and recall process

Background

This recall was triggered by test results. The Canadian Food Inspection Agency (CFIA) is conducting a food safety investigation, which may lead to the recall of other products. If other high-risk products are recalled, the CFIA will notify the public through updated Food Recall Warnings.

The CFIA is verifying that industry is removing recalled product from the marketplace.

Illnesses

There have been no reported illnesses associated with the consumption of these products.

Printer ready version of photos