Cause

  • | | | |

    Two Delta Boeings with Technical Difficulties


    Contact photographer John Farmington
    What: Delta Airlines Boeing 767-300 en route from New York JFK,NY (USA) to Kiev (Ukraine)
    Where: returned to New York
    When: May 3rd 2009
    Who: 212 on board
    Why: The crew listed “operational reasons” but listed no details. They turned back over Moncton,NB and returned flying at lower altitude.


    Contact photographer Wim Callaert
    What: Delta Airlines Boeing 767-300 En route from New York JFK,NY (USA) to Rome Fiumicino
    Where: Bangor,ME
    When: May 4th 2009
    Why: En route, the plane lost all air data computers and had lost most of the flight instruments, and requested to return to the airport of origin. Instead, they diverted to Bangor Maine. A replacement plane completed the flight. Fortunately, all that was suffered was a delay of nine hours.

    George’s Point of View

    This caught my eye mostly because two Boeings flying out of NY’s JFK were both listed as having “technical difficulties.” I wanted to doublecheck and see if they were the same plane.

    Not the same plane.

    The first incident with the undisclosed technical difficulty involved plane registration registration N182DN.
    The second incident, the one with the data computer problem, involved plane registration N196DN.

    I find myself curious to discover what is coincidence and what is not. It may not be the same plane; but it is the same airline, the same model plane. Is it the same flight crew? Same procedures? What about the equipment? Is there something here to discover?

  • | |

    Maintenance Door Opens in Flight

    What: Northwest Airlines flight 2271 en route from Baton Rouge to Memphis
    Where: Baton Rouge Metro Airport Monday
    When: Monday May 4, 2009
    Who: 49 people on board
    Why: When an access door to avionics maintenance on the bottom of the jet opened, the flight returned to Baton Rouge and circled to use fuel before landing.

    George’s Point of View

    Better safe than sorry.

  • | | |

    Jetways Boeing Diverts to Baku due to Smoke Alarm


    Contact photographer Kevin Gutt
    What: Boeing-777-300 ER passenger jet owned by India’s JetWays en route from Delhi to London
    Where: emergency landing at Heydar Aliyev International Airport in Baku Azerbaijan
    When: May 2nd 2009
    Who: 262 passengers and 15 crew
    Why: A fire alert went off in the hold, indicating smoke some four hours into the flight. The plane diverted to Baku and passengers debarked. Apparently whatever the problem was was solved quickly, (false alarm) because the next day passengers apparently continued on their way on the same plane seven hours later.

  • | | |

    Robinson R22 Blown Down in Hong Kong

    What: Robinson R22
    Where: on the site of Hong Kong’s former Kai Tak international airport
    When: May 3
    Who: 2
    Why: During strong winds, the helicopter crashed into a coach parked about 100m away from the Hong Kong Aviation Club. The pilot and his son who was aboard were injured, as well as the coach driver; and all involved were taken to a local hospital. After the crash, the helicopter was reported as leaking fuel.

  • | | | | |

    Airbus Eats Bird over Glasgow


    Contact photographer Wim Callaert
    What: Thomas Cook Airlines Airbus A330-200, en route from Glasgow,SC (UK) to Dalaman (Turkey)
    Where: Manchester
    When: May 3rd 2009
    Who: 322 passengers and 11 crew
    Why: Over Glasgow, the left hand engine apparently ingested a bird; subsequently, the plane suffered failure of the left hand engine while departing (climbing over) Glasgow, then suffered slat failure. The crew was able to shut down the engine and land in Manchester

  • | |

    Northwest Tailstrike

    What: Northwest Airlines Airbus A320-200 en route from Minneapolis, MN to Denver, CO
    Where: Denver
    When: May 4th 2009
    Why: Resulting in (or from) 3.3G acceleration, the Airbus tail struck the ground. Damage was substantial/

    George’s Point of View

    What?? Was the pilot in training??

  • | |

    Stuck Flap Leads to Emergency Landing in Greenville

    What: Delta flight 5800 was en route from Atlanta’s Hartsfield-Jackson International Airport to Greenville Spartanburg International
    Where: Greenville Spartanburg International airport
    When: May 3, 2009 1:23 Sunday afternoon
    Who: 19 passengers
    Why: Pilot declared an emergency due to a stuck flap on the left wing.

  • |

    Emergency Exit Door Falls Off

    What: Saudi Arabian Airlines McDonnell Douglas MD-90-30 en route from Riyadh to Taif Saudi Arabia
    Where: Taif
    When: Apr 28th 2009
    Why: On landing, an overwing exit door opened and fell into the cabin. Plug-type doors are held taught by differential air pressure; but it has not been determined why the door opened.

    George’s Point of View

    I have shoes I refuse to throw away that are, I’m sure, 30 years old. I don’t even wear them but I figure they deserve to share space in my closet with my newer stuff just for old time sake.

    Maybe the owners of some of these very old planes should do the same. Don’t put them out in the desert to rot away. Send them to a museum. But stop using them to for take offs and landings.

  • | | | |

    Swine Flu Terror In The Skies

    What: United Airlines Boeing 777 en route from Munich to Washington
    Where: Logan International Airport 1:46 p.m.-
    When: 3:45 p.m
    Who: 245 passengers and 14 crew members
    Why: When a woman aboard this flight started to feel the flu, 244 passengers and 14 crew members had to go out of their way (at a cost of how many thousands?) and land en route so she be taken by ambulance to Massachusetts General Hospital.

    George’s Point of View

    The US was founded by stalwart pilgrims. Most of our ancestors came to these shores with pennies to their name. We’re formed of hardy peasant stock born of strong roots with nothing but our bodies and brains to make us what we are. We are the survivors of freezing winters, summers spent barefoot on farms, yellow fever, wars, drought, and more war and more drama. We are the spawn of mixed melting pots, and all the harsh trials that weed out the weak. We are sturdy stock.

    We are the survivors of parents or grandparents who told us stories of trudging to and from school in shoulder-high snow walking uphill both ways.

    (And they didn’t have antibiotics.)

    So what would our stalwart predecessors say about this current terror of the flu?

    I think they’d be a little embarrassed.

    Maybe I’m a little concerned about our oldest, sickest and most vulnerable, but I won’t go into the swine flu brouhaha. I’m not a doctor. I would not wish to be any of those millions of swine flu victims in rural Mexico, with access only to rudimentary medical facilities. Because the oldest, the youngest, the sickest, the weakest are the most vulnerable.

    But.

    Let’s face it. The air in a plane is a closed system. It has always been a closed system. That air recirculates. Maybe planes will install uv light machines in their air systems to sterilize the air. In the meantime, we’re all breathing shared air in planes.

    I’m proud that even in these tough economic times, United Airlines is so solvent that it can afford to spend thousands to divert planes when a solitary patient has the sniffles. But…maybe next time, they could spend the equivalent cost of the next “sneeze-diversion” on a couple warehouses full of surgical masks. So that next time we’re in a United Airlines plane, we can rest assured that-if our neighbor sneezes-next to that airsick bag and airplane weekly magazine, we can find a “swine flu” mask, some kleenex and maybe some anti-bacterial hand cleaner.

    D’ya think?

  • | | | |

    A Lesson about Icing

    What: American Eagle Saab 340
    Where: Santa Maria, CA
    When: Jan 2nd 2006
    Who: 2 flight crew members, 1 flight attendant, and 25 passengers
    Why: aircraft lost 5000 feet during climbout due to icing

    George’s Point of View

    Hopefully this incident is another lesson to icing and taking chances.

    NTAB Report Follows:
    LAX06IA076
    HISTORY OF FLIGHT

    On January 2, 2006, at 1439 Pacific standard time, a Saab-Scania AB SF340B+, N390AE, operated by American Eagle Airlines, Inc., as flight 3008, encountered icing conditions during the en route climb over Santa Maria, California. The airplane was at 11,700 feet mean sea level (msl) when it departed controlled flight, and descended to an altitude of about 6,500 feet msl. The pilots recovered control of the airplane, and continued to their scheduled destination of Los Angeles International Airport (LAX), Los Angeles California, where they landed at 1540 without further incident. The 2 flight crew members, 1 flight attendant, and 25 passengers were uninjured, and the airplane did not sustain substantial damage. Instrument meteorological conditions prevailed for the 14 Code of Federal Regulations (CFR) Part 121 scheduled domestic passenger flight that was operating on an instrument flight rules (IFR) flight plan. The flight originated from San Luis County Regional Airport (SBP), San Luis Obispo, California, at 1414.

    A review of the American Eagle Airlines, Inc., flight log disclosed that the accident flight was scheduled to be the flight crew’s fifth trip of the day, and their second trip in the accident airplane. The 1 hour 26 minute accident flight was scheduled to depart from Santa Barbara at 1408, and terminate in Los Angeles at 1513.

    The flight crew members stated in post incident interviews that before the incident flight, they had encountered light rime icing and moderate turbulence on the inbound leg to San Luis Obispo as they were descending from 9,000 to 5,000 feet. The pilots stated that, while preparing for the return flight to Los Angeles, they reviewed the weather conditions for the intended route of flight. The operator’s dispatch package noted two AIRMET (airmen’s meteorological information) reports for icing in clouds and two PIREPs (pilot weather reports) for turbulence. The pilots discussed the conditions that they had encountered on the way in, as well as the conditions for the intended route of flight outbound. Because of the gusty wind conditions and the short runway at San Luis Obispo, the captain decided to perform the departure. He was going to turn control of the airplane over to the first officer after completing the climb checklist at the acceleration altitude.

    In accordance with American Eagle’s minimum equipment list (MEL), the incident airplane was dispatched with the continuous mode of the boot deice system inoperable for the inbound flight and the return incident flight. The flight crew reported that they performed the manual test of the deicer boots as called for in the MEL, and observed the operation of the inboard and outboard wing boot segments. However, they could not see the stabilizer segments, and did not have qualified ground personnel available to observe the test as required by the MEL. The pilots reported that they did confirm illumination of the green boot inflation lights on the overhead panel when they pressed the manual buttons.

    In accordance with company procedures that require flight crews to activate the deice system at the first sign of ice accretion and operate the deice boots continually, the crew stated that they were prepared to operate the deice boots in manual mode as needed during the flight. They departed in level 2 weather conditions (defined as 10 degree Celsius or colder with visible moisture) and with the engine anti-ice on.

    The pilots stated that the weather radar was on, and they did not observe any activity on it. The captain had the autopilot engaged in the medium (M) climb mode. Shortly after taking the controls about 2,500 feet, the first officer changed the autopilot to vertical speed (VS) mode, which gave pitch attitude commands to maintain the vertical speed existing at the time of mode engagement.

    As the airplane climbed through 11,000 feet, the captain noted light rime ice accumulating on the windshield wiper blades and about a 1/2-inch-wide area of ice on the left wing.

    The captain reported that, as he began to reach up to activate the manual deice boot system, he felt a heavy vibration in the airframe. He said that the windscreen immediately turned white. Immediately thereafter, the airplane’s nose dropped, the left wing dropped, and the autopilot disconnected. He grabbed the yoke to take control of the airplane. He said that the clacker sounded (indicating an imminent stall), the stick shaker activated, and the ground proximity warning system emitted a “bank angle” aural warning.

    The flight crew reported that the airplane vibrated again, but less violently than the first episode. The captain leveled the wings, and began pulling up on the control yoke. At this point, he instructed the first officer to manually operate the deice boots. The captain stated that he pushed the condition levers to the maximum position, and brought the power levers to idle. The airplane stabilized in roll, and he could hear chunks of ice shedding off and hitting the fuselage. He kept the airplane in a nose-down attitude, maintaining a 500 feet per minute rate of descent until the airplane was below the freezing level.

    PERSONNEL INFORMATION

    Captain

    The operator reported that the 34-year-old captain held an airline transport pilot (ATP) certificate with a rating for airplane multi-engine land. He held a commercial pilot certificate with ratings for airplane single-engine land and instrument airplane. He had a type rating in the SF340.

    The captain held a first-class medical certificate issued on September 21, 2005. It had no limitations or waivers.

    The captain had a total flight time of 6,764.08 hours, with 3,981.87 hours accumulated in Saab 340 airplanes, of which 2,519.46 hours was as the pilot-in-command (PIC). He had a total of 970 hours of instrument experience and between 1,700 and 1,900 hours of night flight. During the preceding 90 days, 30 days, and 24 hours, he reported that he had flown in both the capacity of PIC and second-in-command (SIC) approximately 172, 47, and 7 hours, respectively. He added that he had acquired numerous hours of aerobatic flight time in a Cessna 150 Aerobat airplane.

    First Officer (FO)

    The operator reported that the 32-year-old FO held a commercial pilot certificate with airplane instrument and multi-engine land ratings. He additionally held an SF340 Type Rating, with the limitations of SF340 SIC privileges only and circling approaches to be completed only in visual meteorological conditions (VMC). The FO was also a certified flight instructor (CFI) for instrument and multi-engine land airplane.

    The FO’s second-class medical certificate was issued on May 25, 2005, with the limitation that he must wear corrective lenses.

    The FO had a total flight time of 1,367.48 hours, with 132.48 hours accumulated in Saab 340 airplanes. He had a total of 94 hours of instrument experience and 185 hours of night flight. During the preceding 90 days, 30 days, and 24 hours, he reported that he had flown approximately 120, 71, and 5 hours, respectively.

    AIRCRAFT INFORMATION

    The airplane was a Saab SF340B+, serial number 340B-390. The airplane had a total airframe time of 17,291 hours at the examination following the incident.

    Systems

    National Transportation Safety Board investigators reviewed the airplane’s maintenance records and logbooks. The day prior to the incident, a flight crew reported that during an en route deice boot check, the timer light illuminated. The deicer timer failure light was later deferred in accordance with the operator’s MEL. The deferral procedures required a placard to be placed adjacent to the deicer timer switch and the auto cycling switch to remain in the “off” position. Investigators did observe an MEL placard (sticker) next to the deice system controls in the cockpit.

    Initial examinations revealed that the airplane’s deice systems were operational; the deicer timer failure light illuminated.

    Aileron Interconnect

    The airplane was equipped with an Aileron Spring Unit. This would allow the flight crew to initially maintain authority in the roll axis if one aileron seized, until the aileron disconnect handle in the cockpit was pulled by a pilot. In the event an aileron seized, the pilot would have to overpower a preloaded spring unit to manipulate an aileron. When the pilot reduced control input pressure, the unit would close allowing the ailerons to be normally coupled. The FO stated that he believed that he did not have his hands on the controls after the captain assumed authority. The roll disconnect handle was not pulled during this incident.

    WEATHER

    A Safety Board meteorologist prepared a factual report, which is part of the public docket. AIRMET Zulu Update 4 for icing (SFOZ WA 022045) was issued on January 2, 2006, at 1345, and valid until 2000. It noted occasional moderate rime/mixed icing in clouds and in precipitation between the freezing level and FL220. The freezing level in central California was 6,000 to 8,000 feet; the freezing level in southern California was 7,000 to 11,000 feet.

    The specialist reviewed San Joaquin Valley, California (HNX) Level II Doppler weather radar Base Reflectivity Images. At 1437:38 at the location of the icing encounter, the HNX beam center was about 16,500 feet with a beam width of about 8,000 feet. The top of the beam was about 20,500 feet, and the bottom of the beam was about 12,500 feet.

    At 1442:36 at the location of the icing encounter, the HNX beam center was about 7,500 feet with a beam width of about 8,000 feet. The top of the beam was about 11,500 feet, and the bottom of the beam was about 3,500 feet.

    A GOES-10 infrared image at 1441 PST at the location of the icing incident recorded a radiative temperature of 244 degrees K (-29 degrees C). Using NAM12 upper air data, this temperature corresponded to a cloud top of about 21,000 feet.

    The report contained experimental Current Icing Potential (CIP) plots that a scientist at the National Center for Atmospheric Research in Boulder, Colorado, provided. It noted that the CIP product (Supercooled Liquid Droplets (SLD) and Ice) combines sensor and numerical model data to provide a three-dimensional diagnosis of the icing environment. The current CIP output consists of a likelihood field ranging from 0 (no icing) to 100 (certain icing). While this is not yet calibrated as a true probability value, CIP has value in pointing out real differences in the likelihood of encountering icing at a given location.

    The plots were: icing severity category composite, maximum SLD potential in the column, maximum potential in column for experiencing icing field, icing severity at 12,000 feet, potential for SLD ice at 12,000 feet, potential for experiencing ice at 12,000 feet, icing severity at 9,000 feet, potential for experiencing ice at 9,000 feet, potential for SLD ice at 9,000 feet, and current icing potential.

    DIGITAL FLIGHT DATA RECORDER (DFDR)

    A Safety Board specialist examined the DFDR data, and the factual report is part of the public docket.

    About 6 minutes after takeoff, the airplane was passing through 9,200 feet. The airspeed began to decline from 180 knots, and the pitch angle began to increase. Around 2 minutes later, at 1439:36, the pitch of the airplane was 14 degrees up and the roll was neutral. One second later, the altitude reached a maximum recorded value of 11,712 feet, and the airplane was in a 16-degree left roll. During the next second, the autopilot disconnected, and the airspeed registered 118 knots.

    The rate of airspeed decay accelerated in the final 10 seconds before the autopilot disconnected. The airplane departed controlled flight at an airspeed of 130 knots indicated airspeed (KIAS), and before the stall warning activated. The DFDR data also revealed that about 26 seconds before the stall roll departure, while the airplane was at a speed of 144 KIAS, the airplane began to experience a slight rolling anomaly that was counter to the direction of the aileron input. Aileron input from the autopilot arrested this slight rolling motion.

    The airplane rolled to 86 degrees left wing down, and then went through a series of roll and pitch movements. It reached 140 degrees of right roll, and a maximum pitch down angle of 48 degrees. It rolled to 75 degrees left wing down, and a pitch of 31 degrees nose down. It then rolled to 94 degrees right wing down, followed by a pitch angle to 40 degrees nose down. Starting at 1440, the altitude and outside air temperature parameters stopped recording valid data for a period of 15 seconds. At 1440:06, the airplane’s pitch angle began to increase. It passed through 0 degrees about 6 seconds later at an airspeed of 219 knots, and a recorded maximum vertical acceleration of 2.5 g’s. The pitch reached 23 degrees nose up at 1440:24; the minimum recorded airspeed value of 105 knots occurred 11 seconds later while the airplane was at an altitude of 7,840 feet. The parameters began to stabilize after this time.

    The DFDR data disclosed that 14 seconds after the initial stall, both ailerons simultaneously traveled to the full up position for approximately 14 seconds.

    DFDR Study

    The DFDR specialist participated in a ground test to validate the control wheel and aileron position data recorded on the event flight and gather additional data related to a breakout scenario. The test did demonstrate that, under a normal scenario, the control wheel being manipulated would lead the control wheel not being manipulated. Also, it showed that moving the control wheel would drive the ailerons to their maximum range values, but moving the ailerons would not drive the control wheels to full range. Additionally, in manually manipulating the ailerons, the left one did not reach its full upwards range.

    TESTS AND RESEARCH

    Performance Study

    A Safety Board specialist conducted a vehicle performance study, which is a part of the public docket. It showed that the airplane’s aerodynamics degraded with time until the airplane stalled. This stall occurred at a lower angle of attack than would be expected for an uncontaminated airframe. The study concluded that the aerodynamic degradation and early stall was consistent with airframe icing.

    ADDITIONAL INFORMATION

    Training

    American Eagle had a recurrent and requalification simulator training syllabus for captains and first officers. It included approach to stalls in the takeoff, clean, and landing configurations. It also included unusual attitudes recoveries from nose low and nose high positions. One section dealt with normal and abnormal emergency situations operations including anti-icing and deicing systems, stall warning, and stick pusher.

    American Eagle’s advanced aircraft maneuvering program (AAMP) includes a review of phenomena that cause upset events and unusual attitude recovery procedures.

    The Operations Group chairperson interviewed several American Eagle pilots. All the pilots interviewed, including the incident captain and first officer, stated that they never practiced encountering a stall in icing conditions as part of their simulator training. Additionally, the pilots could not recall ever having the opportunity to practice a complete stall in the simulator, as they were always instructed to recover at the first indication of an impending stall.

    Minimum Airspeeds for Flight in Icing Conditions

    American Eagle’s 340B+ Airplane Operating manual (AOM) calls for flight crews to compute a final clean airplane climb speed, or Vcln, and to add 15 knots to that value to determine the minimum speed (Vcln+15) in icing conditions. For the incident flight, Vcln was computed to be 126 knots indicated airspeed (KIAS), and the minimum speed in icing conditions was 141 KIAS.

    Use of Autopilot in Icing Conditions

    The limitations section of the American Eagle 340B+ AOM stipulates that the indicated airspeed (IAS) mode is the only authorized flight director/autopilot mode if an airplane is climbing when ice accretion is occurring, or with residual ice on the airframe. In IAS mode, the flight control computer gives pitch attitude commands to maintain the indicated airspeed existing at the time of mode engagement. In the vertical speed (VS) mode of the incident flight, the autopilot would sacrifice airspeed to maintain climb rate.

    Recommendations

    The Safety Board issued several recommendations as a result of the investigation.

    Urgent recommendation A-06-48 asked the FAA to require all operators of Saab SF340 series airplanes to instruct pilots to maintain a minimum operating airspeed of 1.45xVs during icing encounters and before entering known or forecast icing conditions and to exit icing conditions as soon as performance degradations prevent the airplane from maintaining 1.45xVs.

    Recommendation A-06-49 asked the FAA to require the installation of modified stall protection logic in Saab SF340 series airplanes certified for flight into known icing conditions.

    Recommendation A-06-50 asked the FAA to require the installation of an icing detection system on Saab SF340 series airplanes.

    Recommendation A-06-51 asked the FAA to require all operators of turbo propeller-driven airplanes to instruct pilots, except during intermittent periods of high workload, to disengage the autopilot and fly the airplane manually when operating in icing conditions.

    The Safety Board also reiterated the following recommendations to the FAA.

    Recommendation A-03-53 asked the FAA to convene a panel of airplane design, aviation operations, and aviation human factors specialists, including representatives from the National Aeronautics and Space Administration, to determine whether a requirement for the installation of low-airspeed alert systems in airplanes engaged in commercial operations under 14 Code of Federal Regulations Parts 121 and 135 would be feasible, and submit a report of the panel’s findings.

    Recommendation A-03-54 asked that if the panel requested in Safety Recommendation A-03-53 determines that a requirement for the installation of low-airspeed alert systems in airplanes engaged in commercial operations under 14 Code of Federal Regulations Part 121 and 135 is feasible, establish requirements for low-airspeed alert systems, based on the findings of the panel.

  • | | | | |

    Jetstar Airbus Pilot Catches Hydraulic Leak in Time


    Contact photographer Justin Shan
    What: Jetstar Airbus A320-200 en route from Cairnes to Brisbane Australia
    Where: Cairns Airport
    When: 9.30am.
    Who: 179 people
    Why: When the pilot identified a leak in the hydraulics, he made several loops of Cairns airport before undertaking a “standard air return.” After an interim of 3 and a half hours, the plane resumed the flight.

    George’s Point of View

    Yet another Airbus problem.

  • | | |

    Preliminary Conclusion of Melbourne-March 20 Tail strike

    What: Airbus A340 en route for Dubai
    Where: Melbourne airport
    When: March 20
    Who: 257 passengers and 18 crew
    Why: Incorrect weight data on an in-flight computer caused the tail of an Emirates plane to scrape the runway during take-off. ( The Australia’s air safety regulator concluded that the weight was incorrectly entered on the onboard computer which resulted in thrust setting and take-off reference speeds lower than those required for the aircraft?s actual weight. (The weight entered was 112 tons too light.) The incident caused substantial damage to the plane’s tail. The tail ripped out at least one runway light, and dislodged a flight data recorder at the plane’s rear. Manual correction of thrust caused the rear fuselage to scrape the tarmac. The Emirates investigation is considering a flight computer double-entry system “to protect against single data source entry error.”

  • | | |

    Emergency Landing: Asiana Boeing

    What: Asiana Airlines Boeing 777 en route from Seattle Sea-Tac to Seoul, South Korea
    Where: Seattle-Tacoma International Airport
    When: on Wednesday,
    Who: 179 passengers
    Why: There were reports that flames shot out of one of the jet’s engines and television video of smoke as the plane circled before landing.

  • | | | |

    Cessna Lands in Marsh

    What: twin-engine Cessna 310
    Where: marshy area near Pitt Street bridge Mt. Pleasant
    When: Saturday afternoon April 25, 2009 2:56 pm
    Who: Arthur Parker and (approx) ten year old son
    Why: When something “popped” on the plane and he could not turn and started losing altitude, Arthur Parker did the only thing he could, and landed in the Mount Pleasant marsh. He and his son walked out on the wing and waded through the marsh, then walked to a local house. Police officers met them, but Parker declined police and medical assistance.

    Now his biggest problem is how to retrieve his plane from the marsh…

    George’s Point of View

    Just call Triple A?

  • | | |

    Medevac Disaster

    What: Medical evacuation helicopter en route from Ponte Lettia heliport in Upper Corsica
    Where: on the French Mediterranean island of Corsica in the mountainous area near the city of Bastia. The helicopter “brutally” flew into a mountain in poor weather.
    When: Sun Apr 26, 2009
    Who: Five people: two pilots, a medic and two patients
    Why: In spite of bad weather (fog, wind and rain), there was no distress signal. The medical team hadn’t realized how close to delivery the mother was; the helicopter was en route to the hospital as the Frenchwoman was giving birth. Mother and newborn perished in the crash along with everyone aboard. A rescue team of 150 found the wreckage.

  • | | | |

    Emergency Landing and Changeover in Tallahassee


    Contact photographer Ben Wang
    What: American Airlines McDonnell Douglas MD-82 en route from Tampa to the Dallas-Fort Worth Airport
    Where: emergency landing in Tallahassee Florida
    When: Saturday Apr 25th 2009
    Who: 147 people
    Why: After discovering that the plane was experiencing mechanical problems involving the fuel tanks, it took twenty minutes to land. Passengers boarded a MD-83 and reached Dallas nine and a half hours later. The MD-82 with fuel system issues is under examination.

  • | |

    Air France: Cracked Cockpit Windshield

    What: Air France Airlinair Aerospatiale ATR-42-500 en route from Florence (Italy) to Lyon (France)
    Where: diverted to Genoa (Italy)
    When: Apr 25th 2009
    Who: 32 passengers
    Why: While en route, the crew observed a cracked windshield. The airplane landed safely about 50 minutes after departure from Florence.

  • | | |

    Delta Flight Diverted to Boston

    What: Delta Air Lines en route from John F. Kennedy Airport in New York, was bound for Tel Aviv, Israel.
    Where: Boston’s Logan International Airport
    When: 10 p.m Apr 25, 2009
    Who: 206 passengers and 11 crew members aboard
    Why: After take-off, an unruly passenger attempted to break into the cockpit. The incident was not terrorism related; the passenger reportedly had an anxiety/panic attack. He was subdued by other passengers.

  • | | |

    Turbulence over Hawaii

    What: Air Canada Boeing 777-200 LR en route from Australia to Vancouver
    Where: emergency landing in Honolulu
    When: Friday 7:10 a.m.
    Who: 256 passengers and 17 crew members
    Why: When the flight encountered turbulence SW of Honolulu, twenty-two people suffered minor injuries following severe air turbulence. Two passengers were treated at the hospital and released; two crew members were hospitalized; the rest were treated on site. The flight left later, scheduled to arrive in Vancouver at 2:44 p.m.

    The turbulence was related to a thunderstorm.

    George’s Point of View

    It’s not brain surgery. When the seatbelt sign says “Fasten,” please “Fasten.”

    map image

  • | | | | |

    Three Lightning Strikes A Charm.

    What: Republic Airlines Embraer ERJ-170 on behalf of US Airways en route from Montreal to Philadelphia, PA
    Where: on approach to Philadelphia,
    When: Apr 22nd 2009
    Why: On approach, the airplane was struck by a lightning. The crew did not declare emergency and landed safely with no damage sustained.

    What: US Airways Boeing 757-200 en route from Saint Maarten (Netherlands Antilles) to Philadelphia,PA
    Where: on approach to Philadelphia
    When: Apr 22nd 2009
    Who: 96 passengers and 7 crew
    Why: Although on approach, the plane was struck by lightning at 6000 feet, it landed safely 14 minutes later. Skin damage was reported. This was reportedly lightning strike number two.

    What: AirTran Airways Boeing 717-200 en route from Orlando,FL to Philadelphia,PA
    Where: on approach to Philadelphia
    When: Apr 22nd 2009
    Why: The crew declared emergency an emergency when their nose cone incurred a direct lightning strike. Fortunately the airplane landed safely on runway 27R. ( Runway 27L was still in the process of accommodating the prior lightning strike.) Strike number three.

    George’s Point of View

    This may be hindsight, but it seems to me like three different planes hit with lightning at the same city reportedly within a time span of minutes–maybe air traffic control should have checked weather.com or looked out the window or something…

  • | |

    Venezuela: Aerotuey Crash


    What: LTA (Aerotuey) Cessna 208 Caravan en route to Angel Falls
    Where: Canaima Venezuela
    When: Friday April 16
    Who: ten survivors, one child dead
    Why: The engine failed just after takeoff; the plane hesitated on the runway, took off but after airborne, fell into a stand of trees near the runway. Survivors were airlifted to a hospital in Ciudad Bolivar, the nearest city (400 miles away).

    Six year old Thomas Horne was the only fatality. He died en route to the hospital.

  • | | |

    Turbulence: When the Light is ON, SIT.


    Contact photographer Alex G.-Denicourt
    What: Continental Airlines Boeing 737-700 en route from Houston,TX to McAllen,TX
    Where: McAllen, TX
    When: Apr 18th 2009
    Who: 104 passengers and 5 crew
    Why: First, severe thunderstorms delayed takeoff. Then, en route, fasten seat belt signs were on. The plane experienced turbulence while a woman was in the bathroom; she hit the ceiling and sustained serious back injuries. A flight attendant and another passenger also were injured. On landing, the seriously injured women was ported to the hospital and underwent (2?) neck surgery/ies. It is not known if the severely injured passenger will be permanently paraplegic.

    George’s Point of View

    Do not think the seatbelt sign does not apply to you. You’re not someone exempt from turbulence. The seatbelt sign applies to everyone.

  • | |

    Rudder Failure Fails to Alert Crew

    What: Air Canada Airbus A319-100 en route from Montreal,QC to Toronto,ON
    Where: Montreal
    When: Apr 14th 2009
    Who: 117 on board
    Why: As the plane was about to lift off, the rudder moved and the aircraft pivoted to the left. The crew completed the flight. Afterwards, maintenance in Toronto was informed and they replaced the yaw damper actuator and the #1 flight augmentation computer.

    George’s Point of View

    I question whether the crew should have continued on with this flight on board this plane before the maintenance repairs were completed. It is obvious that everyone survived and that is a good thing. But I wonder if the convenience of not stopping is worth either 1. the actual risk; 2. the perceived risk 3. passenger confidence.

    As far as confidence in an airline goes, as for me, ask me any day and I’ll tell you, I’d prefer to be a little late to being a little dead. I think most passengers would agree.

    If not stopping to perform repairs is Air Canada’s policy, then someone needs to rethink this policy, because the issue is not consumer confidence vs the bottom line. It is safety vs foolhardy cutting of corners.

  • |

    Boing Emergency landing in Florida due to Laser


    Contact photographer Thomas Piskol
    What: American Airlines Boeing 757-200 en route from Orlando,FL to Miami,FL
    Where: ?WEST PALM BEACH
    When: 04/20/2009 0:125
    Why: “ON APPROACH REPORTED A LASER BEAM STRIKE” The plane was landed safely in spite of the pilot sustaining an eye injury from a laser pointed at the cockpit.

    Based on Flightaware information, the Aviation Herald reports the landing did not occur at West Palm Beach.

    Also, the flight number was erroneously listed on the FAA site as the registration #.