Boeing

  • | | |

    False Cargo Fire Alarm in Bogota

    An American Airlines flight AA908, a Boeing 777-200 en route from Buenos Aires to Miami made an emergency landing in Bogota after a warning of a problem in the hold.

    There were 250 passengers aboard and 14 crew. No injuries were reported. The indicator was a false alarm.

    American Airlines sent a replacement flight from the Colombian capital yesterday, at 13.10 local time.

  • | | | | |

    Orient Thai Airlines Flat in Thailand

    On July 31, 2013, an Orient Thai Airlines Boeing 73703T) was en route from Guiyang to Phuket.

    Pilots diverted to Surat THani airport and made an emergency landing around 7pm. While taxiing on the runway, a main gear tire slipped off the pavement had had a flat.

    The plane was towed off the runway. Flights were disrupted till about 9 pm.

    There were 137 Chinese passengers aboard. No injuries were reported.

  • | | | | |

    Southwest NoseGear Collapse July 22 Update


    Investigators are still working to determine the problem why the landing gear of Southwest Airlines Flight 345 collapsed while the plane was landing in New York on Monday.

    Input and coverage continues below:

    See Videos

    • Nose Gear Collapse ‘Humongous Jolt’

    • CBS 2 minutes 9 seconds

    • Details from Los Angeles Times 1 min 13 seconds

    • Raw footage 11 seconds

    SOUTHWEST AIRLINES FLIGHT 345 BOEING 737 AIRCRAFT LANDED AND THE NOSE GEAR COLLAPSED, PASSENGERS EVACUTED VIA CHUTES ONTO THE RUNWAY AND WERE BUSSED TO THE TERMINAL. 8 PERSONS ON BOARD SUSTAINED UNKNOWN INJURIES, LAGUARDIA AIRPORT, NEW YORK, NY

    Date: 22-JUL-13
    Time: 21:45:00Z
    Regis#: N753SW/SWA345
    Aircraft Make: BOEING
    Aircraft Model: 737
    Event Type: Incident
    Highest Injury: Unknown
    Aircraft Missing:
    Damage: Unknown
    LOCATION
    City: NEW YORK
    State: New York

  • | | | | |

    Southwest Airlines Diverts due to Flaps Flops

    On July 23, 2013, a Southwest Airlines Boeing 737-300 en route from Kansas City to Indianapolis developed a problem with the flaps.

    Pilots diverted back to Kansas City and made an emergency landing. (See flight path below)

    None of the 54 aboard suffered injury.

    The flight eventually took off and arrived in Indianapolis at 1 a.m. with no indication if this was the same or a different jet.

    * Flight Path:

  • | | | | |

    Southwest Airlines Boeing Nosegear Collapses in NY


    On July 22, 2013, a Southwest Airlines Boeing 737-700 en route from Nashville,TN to La Guardia was making a landing when the nose gear collapsed.

    Five passengers and 3 crew were injured on the slides and hospitalized.

    There were 144 passengers and 6 crew aboard.

    A passenger described landing as “a bang and a bounce and then just a slam on the brakes and then it was a skidding”

    The airline confirmed a nose gear collapse, 5 passengers and 3 cabin crew reported injuries and were taken care of by local responders.

    Video Below

  • |

    Before Crash, Asiana Airlines Told to Revamp


    Asiana Flight 214 clipped a sea wall with its tail as it came in to land at the US airport and skidded out of control before catching fire at San Francisco’s international airport on July 6, killing three people and injuring dozens. Two months prior to the accident, South Korea’s transport ministry had requested Asiana Airlines Inc. to review safety measures.

    On April 30, the Korean government told Asiana to hire more pilots, engineers and cabin crew, to centralize its safety management system and to set up oversight for aircraft maintenance.

    Had Asiana complied with this directive? Did Asiana have adequate training for new pilots? Was the PIC aware of the situation of the SF airport? – South Korea’s Asiana Airlines will be subject of a three-week government investigation. These are some of the questions that the investigation should be covering.

    Lee Kang-Kuk, a ten year pilot was 40 hours into his B777 flight training.

    The wrecked fuselage of Asiana Airlines flight 214 is sitting in storage at San Francisco International Airport

  • | | | | |

    Japan Airlines Flight Returns to Boston


    A Japan Airlines 787 was en route from Boston to Tokyo when a maintenance indicator flashed early in the flight.

    Pilots returned to Boston where they made a safe landing at 6:15 p.m. The problem is being reported as a maintenance issue.

    Flightradar24 website shows that Japan Airlines flight 7 was over Hudson Bay in Canada when it turned around.

  • | | | | | |

    Utair Boeing Skids off Runway


    On July 15, 2013, a UTair Boeing 737-524 en route from Moscow to Kiev ran off the runway on landing. It was misting at the time, leading to a slippery runway but was described as coming to a quick stop at 30-40 meters on level ground.

    Firefighters took five minutes to arrive and ambulances five minutes after that but there was no fire and no injury reported.

    None of the 77 passengers or crew sustained any injury. Passengers disembarked evacuated from the plane with fixed ladders rather than inflatable emergency ladders on to the soft ground, and were transported to the gate.

    Raw Video

  • | | | | | | | | | | | | | | | | |

    Aviation Events recorded this weekend

    13-JUL-13
    Time: 00:01:00Z
    Regis#: ASA769
    Aircraft Make: BOEING
    Aircraft Model: 737
    Event Type: Incident
    Highest Injury: Unknown
    Damage: None
    LOCATION
    City: CHICAGO
    State: Illinois
    Country:
    DESCRIPTION
    Description: ALASKA AIRLIINES FLIGHT 769 BOEING 738 AIRCRAFT, REGISTRATION UNKNOWN, DIVERTED DUE TO UNKNOWN ODOR IN THE CABIN, 3 FLIGHT ATTENDANTS SUSTAINED UNKNOWN INJURIES, AIRCRAFT LANDED WITHOUT INCIDENT, CHICAGO, IL

    Date: 14-JUL-13
    Time: 22:45:00Z
    Regis#: UAL408
    Aircraft Make: AIRBUS
    Aircraft Model: A320
    Event Type: Incident
    Highest Injury: Unknown
    LOCATION
    City: HOUSTON
    State: Texas
    Country:
    DESCRIPTION
    Description: UNITED AIRLINES FLIGHT 408 AIRBUS A320 AIRCRAFT, REGISTRATION UNKNOWN, ENCOUNTERED SEVERE TURBULENCE AND 1 FLIGHT ATTENDANT SUSTAINED UNKNOWN INJURY, LANDED WITHOUT INCIDENT, HOUSTON, TX

    Date: 13-JUL-13
    Time: 20:28:00Z
    Regis#: N3734H
    Aircraft Make: BOEING
    Aircraft Model: 737
    Event Type: Incident
    LOCATION
    City: JACKSONVILLE
    State: Florida
    Country:
    DESCRIPTION
    Description: N3734H DELTA AIRLINES FLIGHT 8957 BOEING 737 AIRCRAFT ON LANDING, WENT OFF THE END OF THE RUNWAY INTO THE GRASS, NO INJURIES, DAMAGE UNKNOWN, PASSENGERS DEPLANED VIA STAIRS AND BUSSED TO TERMINAL, JACKSONVILLE NAVAL AIR STATION, JACKSONVILLE, FL

    Date: 12-JUL-13
    Time: 11:51:00Z
    Regis#: JIA444
    Aircraft Make: CANADAIR
    Aircraft Model:
    Event Type: Incident
    Damage: Minor
    LOCATION
    City: ROANOKE
    State: Virginia
    Country:
    DESCRIPTION
    Description: US AIRWAYS PSA FLIGHT JIA444, CRJ2 AIRCRAFT, REGISTRATION UNKNOWN, SUSTAINED MINOR DAMAGE TO WINDSHIELD UNDER UNKNOWN CIRCUMSTANCES, DIVERTED AND LANDED WITHOUT INCIDENT AT ROANOKE, VA

    14-JUL-13
    Time: 23:05:00Z
    Regis#: FEDEX399
    Aircraft Make: BOEING
    Aircraft Model: 757
    Event Type: Incident
    Damage: Minor
    LOCATION
    City: MEMPHIS
    State: Tennessee
    Country:
    DESCRIPTION
    Description: FEDEX FLIGHT 399 BOEING 757, REGISTRATION UNKNOWN, AIRCRAFT SUSTAINED MINOR DAMAGE TO LEADING EDGE OF FLAP UNDER UNKNOWN CIRCUMSTANCES, MEMPHIS, TN

    14-JUL-13
    Time: 17:14:00Z
    Regis#: N1016S
    Aircraft Make: MOONEY
    Aircraft Model: M20J
    Event Type: Incident
    Highest Injury: None
    Damage: Minor
    LOCATION
    City: MONTAGUE
    State: California
    Country:
    DESCRIPTION
    Description: AIRCRAFT LANDED GEAR UP, MONTAGUE, CA

    12-JUL-13
    Time: 17:00:00Z
    Regis#: N104DG
    Aircraft Make:
    Aircraft Model: KITFOX
    Event Type: Incident
    Highest Injury: None
    Damage: Unknown
    LOCATION
    City: SMOKETOWN
    State: Pennsylvania
    Country:
    DESCRIPTION
    Description: AIRCRAFT FORCE LANDED IN A CORN FIELD OFF THE END OF THE RUNWAY, NEAR SMOKETOWN, PA

    12-JUL-13
    Time: 23:00:00Z
    Regis#: N32EM
    Aircraft Make: SCHEMPP HIRTH
    Aircraft Model: DISCUS B
    Event Type: Incident
    Highest Injury: None
    Damage: Minor
    LOCATION
    City: MOUNDHOUSE
    State: Nevada
    Country:
    DESCRIPTION
    Description: AIRCRAFT FORCE LANDED IN A FIELD, NEAR MOUNDHOUSE, NV

    13-JUL-13
    Time: 23:15:00Z
    Regis#: N328CM
    Aircraft Make: MOONEY
    Aircraft Model: M20F
    Event Type: Incident
    Highest Injury: None
    Damage: Minor
    LOCATION
    City: APALACHICOLA
    State: Florida
    Country:
    DESCRIPTION
    Description: AIRCRAFT LANDED GEAR UP, APALACHICOLA, FL
    INJURY DATA
    Total Fatal: 0

    12-JUL-13
    Time: 19:30:00Z
    Regis#: N6101H
    Aircraft Make: STEARMAN
    Aircraft Model: C3B
    Event Type: Incident
    Highest Injury: None
    Damage: Minor
    LOCATION
    City: EVERETT
    State: Washington
    Country:
    DESCRIPTION
    Description: AIRCRAFT ON LANDING SUSTAINED MINOR DAMAGE, EVERETT, WA

    13-JUL-13
    Time: 00:38:00Z
    Regis#: N72100
    Aircraft Make: BEECH
    Aircraft Model: 36
    Event Type: Incident
    Highest Injury: None
    Damage: Minor
    LOCATION
    City: CADIZ
    State: Kentucky
    Country:
    DESCRIPTION
    Description: AIRCRAFT ON LANDING STRUCK A DEER, CADIZ, KY

    13-JUL-13
    Time: 21:31:00Z
    Regis#: N93957
    Aircraft Make: CESSNA
    Aircraft Model: 185
    Event Type: Incident
    LOCATION
    City: KENAI
    State: Alaska
    Country:
    DESCRIPTION
    Description: AIRCRAFT ON LANDING FLIPPED OVER, POLLY CREEK AREA ON THE BEACH, NEAR KENAI, ALASKA

    13-JUL-13
    Time: 23:12:00Z
    Regis#: N9608G
    Aircraft Make: CESSNA
    Aircraft Model: 206
    Event Type: Incident
    LOCATION
    City: DILLINGHAM
    State: Alaska
    Country:
    DESCRIPTION
    Description: AIRCRAFT FORCE LANDED ON THE TUNDRA, NEAR DILLINGHAM, ALASKA

    13-JUL-13
    Time: 20:00:00Z
    Regis#: N123HP
    Aircraft Make: BELL
    Aircraft Model: 206
    Event Type: Accident
    Highest Injury: None
    Damage: Substantial
    LOCATION
    City: INYOKERN
    State: California
    Country:
    DESCRIPTION
    Description: N123HP BELL 206 ROTORCRAFT ON LANDING SUSTAINED SUBSTANTIAL DAMAGE, INYOKERN, CA

    13-JUL-13
    Time: 04:30:00Z
    Regis#: N1374H
    Aircraft Make: AERONCA
    Aircraft Model: 15AC
    Event Type: Accident
    Highest Injury: Unknown
    Damage: Substantial
    LOCATION
    City: TALKEETNA
    State: Alaska
    Country:
    DESCRIPTION
    Description: AIRCRAFT STRUCK A TREE UNDER UNKNOWN CIRCUMSTANCES, TALKEETNA, ALASKA

    14-JUL-13
    Time: 23:59:00Z
    Regis#: N1837B
    Aircraft Make: LUSCOMBE
    Aircraft Model: 8
    Event Type: Accident
    Highest Injury: None
    Damage: Substantial
    LOCATION
    City: ROSE HILL
    State: Kansas
    Country:
    DESCRIPTION
    Description: AIRCRAFT ON LANDING WENT OFF THE SIDE OF THE RUNWAY, ROSE HILL, KS

    14-JUL-13
    Time: 15:30:00Z
    Regis#: N5176N
    Aircraft Make: STEARMAN
    Aircraft Model: E75
    Event Type: Accident
    Highest Injury: None
    Damage: Substantial
    LOCATION
    City: BOZEMAN
    State: Montana
    Country:
    DESCRIPTION
    Description: AIRCRAFT FORCE LANDED SHORT OF THE RUNWAY, BOZEMAN, MT

    14-JUL-13
    Time: 01:15:00Z
    Regis#: N544WK
    Aircraft Make:
    Aircraft Model: HAWK
    Event Type: Accident
    Highest Injury: Minor
    Damage: Substantial
    LOCATION
    City: SAN SIMON
    State: Arizona
    Country:
    DESCRIPTION
    Description: AIRCRAFT EXPERIMENTAL DAKOTA HAWK, STRUCK POWERLINES AND CRASHED INTO AN ORCHARD, 5 MILES FROM SAN SIMON, AZ

    15-JUL-13
    Time: 02:10:00Z
    Regis#: N66409
    Aircraft Make: BEECH
    Aircraft Model: 35
    Event Type: Incident
    Highest Injury: None
    Damage: Minor
    LOCATION
    City: MEDFORD
    State: Oregon
    Country:
    DESCRIPTION
    Description: AIRCRAFT ON LANDING, GEAR COLLAPSED, MEDFORD, OR

  • | | | |

    Alaska Airlines Flight Diverted


    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

  • | | | | | |

    Thomson Airways Boeing Diverts to Heathrow

    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.

  • | | | | | |

    Ethiopian Airlines Fire at Heathrow


    photographer Josh May

    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:

    • a gadget such as the coffeemaker
    • a manufacturing or installation defect in his jet;
    • a different systemic defect in the 787 model

    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.

  • | | | | |

    Asiana Interviews

    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.

  • | | |

    Raw video

    When you see this amateur video of the Asiana Airlines crash, you really wonder how there were any survivors at all. Of the 307 people—291 passengers and 16 crew—aboard Asiana Airlines Boeing 777-200ER Flight 214, two passengers were killed and 181 injured.
    Click to open video page

    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.

  • | | | |

    NTSB launching team to investigate Boeing 777 crash in San Francisco

    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.

  • | | | |

    Breaking News: Asiana Airlines Crash in San Francisco


    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:

    • Source says no passengers died in San Francisco crash
    • Source says two passengers died in San Francisco crash
    • Pilots who saw Asiana 777 crash in San Francisco say it landed hard, cartwheeled, erupted in flames.
    • A fire truck sprays Asiana Flight 214 after it crash landed at San Francisco airport.
    • NTSB sending “Go-Team” to San Francisco to investigate crash landing of an Asiana B-777.
    • Asiana 777 fell short of runway, eerily similar to British Airways 777 crash in 2008
    • The FAA has said all SFO flights are canceled.
    • 18 flights to and from Denver affected.


    Raw Video

    News Video


    mashable

    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.

  • | | | | |

    Turkish Airlines Bird Strike

    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.

  • | | | |

    273 Korean Air Passengers Wait in Plane when Diverted to Russia

    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.

    In George’s Point of View

    I’d like to consider two additional points for those passengers stuck on their plane:

    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.

  • |

    Lajes Site of Oil Leak Diversion

    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…)

  • | | | |

    Thomson Airways Boeing Grounded after Bird Strike

    A Thomson Airways Boeing 787-8 sustained a bird strike on a Manchester—Cardiff—Shannon flight on the Cardiff-Shannon leg.

    On taking off from Cardiff, the bird strike occurred. The pilot reported that all systems appeared operational. Pilots continued to Shannon and made a safe landing with emergency services on standby.

    On the ground, the flight did not need to be towed but continued under its own power.

    Maintenance did confirm evidence of damage in the jet’s right side engine. The training flight was cancelled and crews worked on the damaged engine.

    This is listed as a training flight of a recently delivered jet.

  • | | | | | | |

    United Boeing Dreamliner Flies Houston to Houston


    photographer Greg Kieca

    On June 24, 2013, a United Boeing 787 Houston to Denver flight developed an issue with the brakes (or brake indicator) and made an emergency landing. Details about the specific problem were not released.

    The flight left Houston at 9.12am and arrived in in Houston at 11:58 a.m.

    None of the 219 passengers and 13 crew members sustained any injury. Maintenance examined the plane. The plane was returned to service.

    Stranded passengers were provided travel solutions by a Boeing field service representative.

  • | |

    Commercial Plane Comparison

    June 17. 2013
    While the upbeat “video below” compares basic features, the real world of aviation is focusing on a comparison of the problems noted.

    • Airbus (350) had a “blockage in the drilling station and the knock-on effect hampering wing production” and problems with suppliers of A350 structural components. A350 also face the looming challenge of obtaining certification
    • Boeing (787) which already graduated to the market, has demonstrated issues with 787’s lithium-ion batteries which use 10 times more power during initial start-up than other Boeings. In-flight monitoring made a demonstrable difference in reliability. A recent report estimates that 29 flights had been “saved” because of the 787’s extensive monitoring system

  • | | |

    Egyptian overrun

    June 15, 2013
    A six year old Boeing 373-86N # SU-BPZ leased from an Egyptian company was providing flight 921 en route from Novosibirsk Russia to Thessaloniki Greece when it skidded off the runway.

    The plane stopped past the end of pavement. There were 160 aboard, including 5 crew, none of whom were injured.

    The cause of the incident has not been released.