On July 12, 2013, an Alaska Airlines BOEING 738 on flight 769 developed an odor in the cabin.
Pilots diverted to Chicago where they made a safe landing.
Three flight attendants were affected.
The flight made a safe landing with no additional injuries. The incident is under investigation.
* http://flightaware.com/live/flight/ASA769/history/20130712/2255Z/KBOS/KSAN
A Thomson Airways Boeing 787-800 en route from Manchester to Orlando on July 12 was enroute when technical problems–an electronic issue– developed.
Pilots diverted back to Manchester, circling Wales where they dumped fuel prior to securing a safe landing with emergency services on standby. Passengers were provided an alternative flight. A dedicated team of engineers inspected # G-TUIC.
The problem was reported to be a flushing issue.
A United Airlines/SkyWest Flight 5229 Canadair Regional Jet CRJ-200 ( Brownsville-Houston flight diverted to McAllen on July 12, 2013 when the pilots discovered pressurization problems.
Pilots received a cabin door indicator light in the flight deck.
Passengers disembarked without any problems.
None of the 43 aboard suffered injury.
An Ethiopian Airlines’ Queen of Sheba, a Boeing 787 #ET-AOP which had been sitting empty for eight hours caught fire and shut down Heathrow Airport for an hour Friday. The fire seems to have started in the upper fuselage, far from the 787’s lithium-ion batteries. A battery fire would have been “contained by the new casing and…smoke would have been vented outside of the airplane.” Nearly a dozen fire trucks responded to the scene. The plane was parked on the apron taxiway E at Stand 592 next to a fire station.
#ET-AOP had arrived from Addis Ababa as flight ET700 at 06:30a.m. Departure was scheduled as ET701 to Addis Ababa at 21:10.
In photos, damage appears on the outside top of the upper fuselage near the vertical stabilizer, on the left side of the top of the airplane just in front of the tail. The fire was not caused by lithium-ion batteries, which are in in the cargo-bay.
Potential causes of the fire:
NTSB Sends Investigator to Participate in Investigation of London Boeing 787 Dreamliner Fire
The National Transportation Safety Board has sent an investigator to assist in the investigation of a fire that occurred yesterday aboard a parked Boeing 787 Dreamliner at Heathrow Airport, London, England.
NTSB Senior Air Safety Investigator Lorenda Ward has been appointed as the traveling U.S. accredited representative. Ms. Ward will be accompanied by NTSB airplane systems investigators and representatives from the Federal Aviation Administration and Boeing.
The investigation is being conducted by the Air Accidents Investigation Branch (AAIB) of the United Kingdom, which will release all information.
NTSB STATEMENT ON ERRONEOUS CONFIRMATION OF CREW NAMES
July 12, 2013
WASHINGTON – The National Transportation Safety Board apologizes for inaccurate and offensive names that were mistakenly confirmed as those of the pilots of Asiana flight 214, which crashed at San Francisco International Airport on July 6.
Earlier today, in response to an inquiry from a media outlet, a summer intern acted outside the scope of his authority when he erroneously confirmed the names of the flight crew on the aircraft.
The NTSB does not release or confirm the names of crewmembers or people involved in transportation accidents to the media. We work hard to ensure that only appropriate factual information regarding an investigation is released and deeply regret today’s incident.
On July 10, 2013 at about 4:45 a.m., a Beech A36 Bonanza with four aboard took off from Fallon Municipal airport en route to Dixie Valley.
Pilot Dan Urquhart force-landed in the desert a couple hundred yards from Fallon Municipal Airport near the intersection of Indian Lakes Road and Enterprise Way.
Two injured parties were flown by Care Flight medical helicopter in stable condition, and one injured party driven to to Banner Churchill Community Hospital and one other hospital.
Damage to the plane has not yet been assessed.
A Peruvian National Police Bell UH-1H with three aboard was en route from Tangier Island airport 8:05 p.m. when it crashed over an area of coca cultivation during night training.
The wreckage was located near Tingo Maria Peru on La Moyuna Mountain.
Base control indicated that before communication broke off at 8:00 pm, the helicopter was in distress.
The helicopter worked the area of ??Leoncio Prado and Alto Huallaga (Tingo María) under drug control in cooperation with the United States.
The three crew, two officers and a sergeant of the Peruvian police members were retrieved and taken to the air base in Tingo Maria. Search teams located the helicopter five minutes from a local police base.
On July 9, 2013 at 9 a.m., a Southwest Airlines flight en route from Baltimore’s BWI Marshall Airport to Las Vegas with 174 passengers, and 6 crew aboard developed engine trouble. The right engine developed a leak.
Pilots diverted to Kansas City International Airport where they made a safe landing.
Good job pilots. Safe landing. No injuries.
I’ve said it before and likely will say it again. Maintenance, Maintenance, Maintenance.
Commercial planes are up and down all day long. It’s constant.
Problems with these planes are just a matter of time. There must be absolute iron-clad maintenance and inspection that is equally as aggressive as the operator that wants their entire fleet in the air all the time.
You know the old adage:
For want of a nail the shoe was lost.
For want of a shoe the horse was lost.
For want of a horse the rider was lost.
For want of a rider the message was lost.
For want of a message the battle was lost.
For want of a battle the kingdom was lost.
And all for the want of a horseshoe nail.
Think of how easily this applies to a plane.
For want of a maintenance check a washer was lost
For want of a washer the oil was lost.
For want of the oil, an engine was lost.
For want of an engine, the pilot was lost.
For want of the pilot, the plane was lost.
For want of the plane, the passengers were lost.
And all for want of a maintenance check.
So…I wasn’t really expecting to say it again so soon:
Maintenance, Maintenance, Maintenance.
Some stories of the Asiana Crash in San Francisco
Currently there are 51 hospitalized, 8 in critical condition, one child. Five fire attendants are being treated for burns.
Federal investigators talked to the pilots why they shut down the autopilot 82 seconds before landing. This was the first time the pilot had landed a 777 at this airport. When the fire started in the middle of the plane, there were passengers still in the back that had to walk through the smoke to exit, passing people trapped in their seats. Flight attendants heroically got passengers out of the plane, and tried to put out the fire.
One passenger Eugene Ra describes the instants before the crash, looking out the window knowing they were too low. THe plane’s impact was powerful enough that it snapped the plane, and the spines of at least two of the passengers. The cabin filled with smoke and fear. After the plane stopped, there was silence.
The plane flew in too low and too slow, initiating a stick shaker (stall) warning, and struck the sea wall, severing art of the tail.
Plane Crash San Francisco Asiana Airlines Crash Survivor Interview
* A cautionary note: The official investigation of the cause of the crash will take a year or more. No matter what news releases or speculations come about before the official investigation is just speculation. We do not know, for example, if some part or software in the plane malfunctioned, leading the pilots to respond as they did.
Photographer Frederico Cavalcante
A Lufthansa Airbus A321-131 #D-AIRE en route from Barcelona to Frankfurt Airport had taken off when the left engine developed problems.
The flight returned make a safe landing in Barcelona.
The problem may have been a bird strike.
Emergency services were on standby as the plane landed. An alternative flight was arranged. None of the 200 aboard were injured.
Asiana Press Releases for Incident Involving Asiana Flight
OZ 214 – July 7, 2013 06:30 (Kor. Time) 2013-07-07 10:02
The following information has been confirmed.
Asiana Airlines flight OZ214 (Aircraft Registration HL7742) departed Incheon International Airport on July 6, 2013 at 16:35 (Korea time) bound for San Francisco. Only July 7, 2013 at 11:28 (Local time) an accident occurred as OZ214 was making a landing on San Francisco International Airport’s runway 28.
There were a total of 291 passengers (19 business class, 272 travel class) and 16 cabin crew aboard. The majority of the passengers were comprised of 77 Korean citizens, 141 Chinese citizens, 61 US citizens, 1 Japanese citizen, etc. for a total of 291 people.
Asiana Airlines is currently investigating the specific cause of the incident as well as any injuries that may have been sustained to passengers as a result. Asiana Airlines will continue to cooperate fully with the investigation of all associated government agencies and to facilitate this cooperation has established an emergency response center at its headquarters.
At this point no additional information has been confirmed. New developments will be announced as more information becomes available.
#2
Official Asiana Statement from OZ214 Incident Press Conference 2013-07-07 16:31
We at Asiana Airlines would like express our utmost sympathy and regret for the distress experienced by the passengers of OZ flight 214 and their families as a result of this accident. We apologize most deeply.
Asiana Airlines flight OZ214 departed Incheon International Airport on July 6, 2013 at 16:35 (Korea time) bound for San Francisco. On July 6, 2013 at 11:27 (Local time) an accident occurred as OZ214 landed on San Francisco International Airport’s runway 28.
A total of 291 passengers were aboard the aircraft. (77 Koreans, 141 Chinese, 64 Americans, 3 Indians, 3 Canadians, 1 French, 1 Japanese and 1 Vietnamese)
Asiana Airlines has established emergency response centers to ascertain the cause of this crash and to look after injured passengers and contact their families. Asiana continues to actively cooperate with all Korean and US governmental institutions in the ongoing investigation.
# 3
Statement from July 8th Press Conference on OZ214 Incident 2013-07-08 15:42
Asiana would like to provide a brief update regarding the status of OZ214.
The special charter flight dispatched by Asiana Airlines yesterday at 13:33 (Korea Time) carrying twelve support staff, eight government inspectors and members of the Korean media has arrived on location in San Francisco. Its passengers have begun supporting the victims and their familes and assisting in the investigation.
Asiana Airlines is providing airfare and lodging for families of the passengers. In the event that the number of family members seeking support increases, Asiana is also preparing to operate additional charter flights.
Two Korean family members departed for the United States yesterday. Another four are expected to depart today followed by an additional four on Wednesday. Asiana Airlines is also supporting twelve Chinese family members and six Chinese government officials, who will depart from Shanghai for the United States (via Incheon) today.
48 injured persons are being treated at local hospitals in the San Francisco area. Each hospital is staffed with dedicated personnel and transportation to provide the utmost support for the victims and their families.
Asiana Airlines deeply regrets this accident and is dedicating great efforts to support and ensure a swift and thorough investigation.
* A cautionary note: The official investigation of the cause of the crash will take a year or more. No matter what news releases or speculations come about before the official investigation is just speculation. We do not know, for example, if some part or software in the plane malfunctioned, leading the pilots to respond as they did.
update:
On July 07, 2013, a Rediske Air Inc deHavilland DHC-3 Otter with 10 aboard was taking off from Soldotna Airport Alaska. THe crash was reported at 11:23 a.m.
Nikiski pilot Willy Rediske and nine passengers died on impact. The crash occurred at Funny River Road. By the time Soldotna police, fire and medic personnel with Central Emergency Services and Alaska State Troopers responded, the plane was on fire.
First responders are notifying family members and retrieving remains.
Investigator Brice Banning who had been targeting the Asiana Airlines crash will instead be launching the Soldotna crash investigation.
Aircraft Details:
The National Transportation Safety Board launched a full go-team to San Francisco, Calif., to investigate the July 6, 2013 crash involving Asiana Airlines Flight 214, a Boeing 777. The crash occurred while the aircraft was landing at San Francisco International Airport.
NTSB Senior Aviation Accident Investigator Bill English will serve as investigator-in-charge. NTSB Chairman Deborah A.P. Hersman is accompanying the team and will serve as the principal spokesman.
Public Affairs Specialists Kelly Nantel and Keith Holloway will also be on-scene in San Francisco to coordinate media related activities. They can be reached by mobile phone at 202-557-1350.[portfolio_slideshow loop=true]
* A cautionary note: The official investigation of the cause of the crash will take a year or more. No matter what news releases or speculations come about before the official investigation is just speculation. We do not know, for example, if some part or software in the plane malfunctioned, leading the pilots to respond as they did.
On July 4, a North-Way Chrysler Motors Ltd. Cessna 182 Skylane with three aboard was near Griffith Island in Georgian bay and flipped as the pilot was trying to land at an island airstrip but came to rest 220 meters short of the runway. All three aboard succumbed to fatal injuries.
The float plane crash occurred off the south end of the Griffith Island. The fatalities were family members 45, 52 and 72.
A Joint Rescue Co-ordination Centre out of Trenton, On circled the downed plane. Three ambulances were on standby at Big Bay dock.
When assistance arrived, the plane was upside down and partially submerged. The Grey County OPP, Bruce Peninsula OPP and Cape Croker police marine units attended, along with Grey and Bruce County paramedics, Inter Township firefighters, Owen Sound firefighters and the Ministry of Natural Resources were dispatched to the scene. The Transportation Safety Board of Canada’s air division arrived Friday.
On July 6 2013, an Asiana Airlines Boeing 777 Flight 214 en route from Taipei made a hard landing on runway 28 at San Francisco international airport.
Rescue services—firefighters and ambulances—responded to the scene.
Passengers exited via air slides. On the video below, it appears the tail is missing. Other video shows the top of the aircraft is charred.
The Asiana Airlines #HL7742 landed hard, slid and/or cartwheeled, and came to rest with landing gear not visible. Debris–apparently the landing gear–is scattered down the runway. Smoke appeared to be coming from the side of the plane opposite from where passengers were exiting via slides. After the plane was on the ground, witnesses saw parts break off and a ball of fire. The attitude of the plane seemed normal but an apparent tailstrike may have damaged systems and limited flight control.
Air traffic to San Francisco international airport has been suspended.
Weather at the time of the accident (11:28 LT / 18:28 Z) was repored as:
KSFO 061756Z 21006KT 10SM FEW016 18/10 A2982 RMK AO2 SLP097 T01780100 10183 20128 51005
KSFO 061856Z 21007KT 170V240 10SM FEW016 18/10 A2982 RMK AO2 SLP098 T01830100
The plane’s first flight was 2005-02-25, 8 years 4 months ago and flew with 2 Pratt & Whitney PW4090.
Heard on Twitter:
NTSB Press MEETING
NTSB Go-Team Pre-Departure Press Avail on Asiana B-777 Crash
WHAT: Press Availability with Chairman Deborah A.P. Hersman as the NTSB go-team departs to San Francisco to investigate the crash landing of an Asiana Boeing 777.
TIME: 5:30 p.m. EDT
LOCATION: Hanger 6 at Reagan National Airport
* A cautionary note: The official investigation of the cause of the crash will take a year or more. No matter what news releases or speculations come about before the official investigation is just speculation. We do not know, for example, if some part or software in the plane malfunctioned, leading the pilots to respond as they did.
A Turkish Airlines Istanbul-Athens Boeing 737-800 made an emergency landing on July 5 after a bid strike.
After takeoff from Ataturk International Airport at 7:40, the plane hit a flock of birds.
The pilot returned to the airport and made a safe landing with damaged engine baffles.
Passengers disembarked and were provided an alternative flight.
On July 1, 2013, a TAM Linhas Aereas Airbus A320 en route from Sao Paulo to Rio de Janeiro with 153 aboard made a landing at Rio.
While navigating the runway, the plane ran off the runway and became mired.
The Airbus A320-200 landed on Rio de Janeiro Galeao Airport’s runway 28 and veered off the runway.
An investigation is underway. No injuries were reported.
July 2, 2013, a Korean Air Boeing 777 with 273 passengers aboard was en route from Chicago to Seoul when it had a drop in pressure as jet fuel was being pumped into the engine. The left engine broke down. After the malfunction, the pilots dumped fuel and diverted to Anadyr airport in Russia, where they made an emergency landing.
Passengers had to wait inside the plane until the replacement jet arrived, so that with ten hours on the ground made a 13 hour flight almost 24 hours long for passengers.
The malfunctioning jet was grounded in Russia pending inspection.
As Anadyr airport is not one we have visited, we wonder if there is no Customs facility at Anadyr airport for individuals without visas to get some relief from the plane, which had to be exceedingly uncomfortable. Certainly there must be some humane way to abide by international law.
This excessive time stretches some IATA standards of passenger accommodation from both airline and airport. The question isn’t whether passengers are entitled to some kind of compensation for their time and trouble, but rather how the airline and airport are going to recompense the passengers.
The disruptive passenger of Monday ( US Airways flight from Vegas to Charlotte) repeats “disruptive and unruly” behavior Tuesday on Albuquerque to Chicago.
The Chicago flight had to divert to Kansas City to unload Mr. “disruptive and unruly” after he tried to exit the plane when it was still flying.
Around 11:30, Kansas City airport police escorted the passenger from the flight after he had been aggressive, shouting, and refusing to stay seated.
The American Eagle Flight 3172 continued to land safely at O’Hare.
Currently, there are five reported survivors: the flight crew of three, and a woman with a child.
The flight manifest lists 28 aboard, including 9 children plus 2 infants.
A dense fog and heavy rains hampered search crews that included Mi-8 helicopters, an AN-26 plane and an An-74.
Deputy of parliament of Yakutia Alexander Morozkin and the head of Republican investment company Victor Yefimov may be aboard. The pilot’s name is Mikhail Nikolaevich. The extent of his injuries have not been released.
We remember on June 2009 when 152 people died aboard a Yemenia Airlines Airbus A310-300.
Yemenia Flight 626.
We remember.
The years pass and the headlines fade, but the families will never forget the loss of their loved ones, and neither should we.
The pilot was about to land on an airstrip in the Comores Islands when ATC lost contact.
The plane and all its passengers crashed into the ocean.
12-year old Bahia Bakari survived the crash, rescued after thirteen hours in the ocean, clinging to debris. She was and is a miracle.
The final report on Flight 626 concluded the crash was due to the crew’s inappropriate flight control inputs that led to an aerodynamic stall.
Crews inappropriate flight control inputs means pilot error. In this case, the pilot error was exacerbated by a nineteen year old plane in dubious condition, bad weather conditions (winds gusting to 64 km/h 40 mph; 35 kn) and a primitive airport.
Crashes like Yemenia should function like red lights. The only way they make sense is if when they happen, we stop and consider those who were lost, and investigate what went wrong. On behalf of safety, the aviation industry should mandate to use every atom of what is discovered to prevent future accidents. The industry in general, and the airlines in specific should make changes that will help prevent future accidents.
Pilot error means airlines like Yemenia are still having problems training pilots. Still problems in the cockpit. Sadly, conditions still exist for more accidents like this in Yemenia’s future.
I was on a pilot talk forum and saw that a US Airways Flight 799, a B757 200 from AMS to PHL (that’s Amsterdam to Philadelphia) sprung a leak and diverted to Lajes on the 26th or 27th.
Lajes in the Azores. Tourists there. Also an airbase.
OF all the places in the world to get stranded, imagine getting stranded in Lajes.
Apparently after the passengers were picked up the next day, their replacement flight was diverted too.
I wonder how much the passengers will want the compensation package that will be offered to them (probably free tickets for more US Airways flights…)
I glance at a lot of news sites, mostly skimming just to make sure the facts are the same across the board, and I don’t usually stop and make comments about one particular site, or other. I’m usually focused on the message, not the messenger.
But once in a while, I come across erroneous content.
What should I do when I come across a site that posts an article that says up till the crash in the Comoros, Yemenia Airlines had an unblemished record?
What world is that staff reporter living in? Who gave them that information? Because it’s wrong.
Today’s Yemenia was formerly Yemen Airlines and Yemen Arab Airlines and Yemen Airways. (There may be more DBA names I’m leaving out.)
This airline, rebranded over and over, has had at least 11 crashes and a couple of hijackings thrown in (1973 and 1975.) Just take a look at the actual record.
And there were EU Safety sanctions in JUL 2008: EU safety action (Safety deficiencies noted by ramp inspections in several countries; Yemenia took corrective actions.); on JUL 2009: EU safety action (The European Aviation Safety Agency (EASA) suspended the maintenance organisation approval EASA.145.0177 issued to Yemenia Yemen Airways, due to unresolved safety deficiencies.) On JUL 2009: EU safety action (The authorities of France suspended the certificates of airworthiness of the aircraft of type Airbus A310 registered in France (F-OHPR and F-OHPS) and operated by the carrier.) On NOV 2009: EU safety action (Member States will verify systematically the effective compliance of Yemenia with the relevant safety standards through the prioritisation of ramp inspections to be carried out on aircraft of this carrier.)
The EU is right to be so demanding. Yemenia Airlines has a dangerous record, no matter what the airline is called. Lack of safety is the reason the airline has been on the EU blacklist. Don’t the people of Yemen deserve a safe carrier?
(See below)
Hijacks first:
A privately owned Cirrus SR22 en route from from Moorabbin Airport was on landing approach when it struck trees and crashed in Boxwood. The plane crashed north of Benalla a city in northeastern Victoria, Australia.
The plane impacted trees near the private airstrip.
The 51 year old pilot died at the scene.
The Australian Transport Safety Bureau and CASA are investigating.
At 5:10 pm Tuesday, Gerard Dale Pearson, 71, was piloting a float plane that crashed on Shoal Lake, in Michigan.
Emergency services, including Itasca County Search and Rescue, Cohasset Fire and Minnesota DNR and Itasca County Sheriff Department retrieved the pilot from the submerged plane.
Pearson was airlifted to Grand Itasca Hospital, then Miller Dwan in Duluth Michigan.
The cause of the crash is under investigation.
