|

What NOT to Bring On Board

Similar Posts

  • | | | | |

    Southwest #762 Diverts to Boise

    While en route from Seattle to Phoenix, a Southwest Airlines Boeing 737-700 flight 762 suffered a cracked windshield. Pilots made an emergency landing in Boise at Gowen Field. The plane went to maintenance, and the 143 passengers had to wait for another flight to get to Phoenix.

    The cabin never lost air pressure but had to dump fuel to make a safe landing.

    FOX 10 News | myfoxphoenix.com

    To include the featured image in your Twitter Card, please tap or click their icon a second time.
  • Return of the Volcano

    Saturday Iceland’s Grimsvotn volcano spewed a 7-miles plume of gas and ash. Initial warnings shut down airports in Iceland- (ISAVIA established a 120 mile no-fly zone around the volcano, closed Keflavik airport, and canceled all domestic flights.)

    Tuesday airports in Ireland will be shut down. Forecasts are tentative because there is uncertainty how the plume will interact with the weather, but it is not expected to be as overwhelming as last year’s eruption of Eyjafjallajokull.


    London volcanic ash advisory centre’s ash map
    “some ash cloud may reach parts of northern Europe in the next 48 hours.”

    To include the featured image in your Twitter Card, please tap or click their icon a second time.
  • | |

    NTSB: No Rush to Judge

    George’s Point of View

    As urgent as the idea of an NTSB recommendation sounds, there is apparently no rush. The latest NTSB safety recommendation to EASA is rooted in a 2001 crash: American Airlines Airbus Flight 587. (see narrative below)

    Probable cause of this accident was the in-flight separation of the vertical stabilizer as a result of the loads beyond ultimate design that were created by the first officer’s unnecessary and excessive rudder pedal inputs. (i.e. The pilot used the rudder and it fell off.)

    (To put this into simplistic car terms, your car just skidded on some ice. You did some fancy and extreme steering which may or may not have been necessary. And the steering wheel just came off in your hands. Pretty much all you can do now is spectate and die.)

    The pilot’s unnecessary and excessive rudder pedal input was based on a violent wake turbulence encounter. The pilot’s “unnecessary and excessive” rudder pedal input broke the rudder.

    Isn’t this a dubious conclusion? Isn’t this like blaming a car crash on a driver hitting brakes too hard? The airbus had just taken off and encountered turbulence. Since when do flight controls not handle “aggressive input”?

    Initial suggestions included pilot retraining. (I.E. don’t fix the problem, train the pilots to work around it.) This month, the NTSB encouraged modification of European certification standards. In other words, the NTSB wants to physically limit the rudder movement to what the design can safely manage. Maybe that makes more sense than expecting a pilot engaged in a desperate struggle to save a failing plane to have to make accommodations for flighty flight controls.

    Some take the angle that the problem lies in the rudder design and/or composition. In 2001, the FAA was one of those so inclined.

    On November 16, 2001, the FAA issued emergency AD 2001-23-51 warning of failure of the vertical stabilizer-to-fuselage attachment fittings, transverse (side) load fittings, or rudder-to-vertical stabilizer attachment fittings, if not corrected, could result in loss of the vertical stabilizer and/or rudder and consequent loss of control of the airplane. The FAA considers that, before structural failure, it may be possible to detect indications of possible failure modes that could result in separation of the vertical stabilizer from the airplane. These indications include edge delaminations, cracked paint, surface distortions, other surface damage, and failure of the transverse (side) load fittings. Similarly, indications of failure of the rudder assembly, which could lead to failure of the vertical stabilizer, may also be detectable with such an inspection.

    This failure has happened more than once.

    In the Air Transat flight 961 incident (also a 300 series Airbus) out of Varadero, Cuba, the rudder disintegrated. The pilot in that flight questions the integrity of the rudder design and composition.

    Here another point that has been commonly made. Aircraft have had rudders made of aluminum for 70 years without them disintegrating. With high tech composites, planes are falling out of the sky.

    In March 2006, US safety investigators recommended rudder inspections on Airbus A300-600 jets because a FedEx A300-600 rudder damaged during maintenance.

    Tested on the ground by Fed Ex engineers, in the Fed-Ex A300 cargo plane, the hydraulic system which actuates the rudder tore a hole around the hinges exactly where the rudders of both flight 961 and flight 587 did. Coincidence? I think not.

    Does the certification process need an overhaul? I think so.

    Have a couple of dead pilots again become convenient scapegoats for/by using the very computer controlled flight control system that they believed protected them? I bet I know what the pilots think.

    Flight 587, Official NTSB narrative of the crash
    On November 12, 2001, about 0916:15 eastern standard time, American Airlines flight 587, an Airbus Industrie A300-605R, N14053, crashed into a residential area of Belle Harbor, New York, shortly after takeoff from John F. Kennedy International Airport (JFK), Jamaica, New York. Flight 587 was a regularly scheduled passenger flight to Las Americas International Airport, Santo Domingo, Dominican Republic, with 2 flight crewmembers, 7 flight attendants, and 251 passengers aboard the airplane. The airplane’s vertical stabilizer and rudder separated in flight and were found in Jamaica Bay, about 1 mile north of the main wreckage site. The airplane’s engines subsequently separated in flight and were found several blocks north and east of the main wreckage site. All 260 people aboard the airplane and 5 people on the ground were killed, and the airplane was destroyed by impact forces and a postcrash fire. Flight 587 was operating under the provisions of 14 Code of Federal Regulations (CFR) Part 121 on an instrument flight rules flight plan. Visual meteorological conditions prevailed at the time of the accident.

    The accident airplane arrived at JFK about 2231 on the night before the accident. The airplane had been flown from San Jose, Costa Rica, to JFK with an intermediate stop in Miami International Airport, Miami, Florida. During postaccident interviews, the pilots of the flight leg from MIA to JFK indicated that the flight was smooth and uneventful.

    Flight 587 was the first leg of a 1-day roundtrip sequence for the flight crew. American Airlines records indicated that the captain checked in for the flight about 0614 and that the first officer checked in about 0630. The gate agent working the flight arrived at the departure gate about 0645. She stated that the flight attendants were already aboard the airplane at that time and that the captain and the first officer arrived at the gate about 0700.

    About 0710, the airplane fueling process began. The airplane fueler indicated that, during the fueling process, he saw one of the pilots perform an exterior inspection of the airplane. He finished the fueling process about 0745 and stated that he saw nothing unusual regarding the airplane.

    Statements provided to the Port Authority of New York and New Jersey Police Department by American Airlines maintenance and avionics personnel indicated that, sometime between 0730 and 0800, the captain reported that the number 2 pitch trim and yaw damper system would not engage. Two avionics technicians were sent to the airplane to investigate the problem. They performed an auto flight system (AFS) check, which indicated a fault with the number 2 flight augmentation computer. The circuit breaker was then reset, another AFS check was performed, and no fault was detected. In addition, an autoland system check was performed, and that test also did not detect a fault. The avionics technicians estimated that they were in the cockpit for 5 to 7 minutes.

    The cockpit voice recorder (CVR) recording began about 0845:35. The CVR indicated that, about 0859:58, the airplane was cleared to push back from the gate. About 0901:33, the ground controller provided the flight crew with taxi instructions to runway 31L, and the first officer acknowledged these instructions. About 0902:05, the captain told the first officer, “your leg, you check the rudders.” (The first officer was the flying pilot, and the captain was the nonflying pilot.) Data from the flight data recorder (FDR) showed that, about 0902:07, the rudder pedal check began. The FDR data also showed that a maximum right rudder pedal deflection of about 3.7 inches was recorded about 0902:11 and that a maximum left rudder pedal deflection of 3.6 inches was recorded about 0902:19. About 0902:23, the first officer responded, “rudders check.” The FDR data showed that the rudder pedals returned to their neutral position about 0902:25.

    About 0906:53, the ground controller provided the pilots of Japan Air Lines flight 47, a Boeing 747-400, with taxi instructions to runway 31L. About 0908:01, the ground controller instructed the Japan Air Lines pilots to contact the local (tower) controller. About 0908:58, the ground controller instructed the flight 587 pilots to follow the Japan Air Lines airplane and to contact the local controller. The first officer acknowledged this instruction.

    About 0911:08, the local controller cleared the Japan Air Lines airplane for takeoff. About 0911:36, the local controller cautioned the flight 587 pilots about wake turbulence and instructed the pilots to taxi into position and hold for runway 31L. The first officer acknowledged the instruction. About 0913:05, the local controller instructed the Japan Air Lines pilots to fly the bridge climb and to contact the departure controller at the New York Terminal Radar Approach Control (TRACON). About 0913:21, the flight 587 captain said to the first officer, “you have the airplane.”

    About 0913:28, the local controller cleared flight 587 for takeoff, and the captain acknowledged the clearance. About 0913:35, the first officer asked the captain, “you happy with that [separation] distance?” About 3 seconds later, the captain replied, “we’ll be all right once we get rollin’. He’s supposed to be five miles by the time we’re airborne, that’s the idea.” About 0913:46, the first officer said, “so you’re happy.”

    The National Transportation Safety Board’s airplane performance study for this accident0 determined that flight 587 started its takeoff roll about 0913:51 and lifted off about 0914:29, which was about 1 minute 40 seconds after the Japan Air Lines airplane. About 0914:43, the local controller instructed the flight 587 pilots to turn left, fly the bridge climb, and contact the New York TRACON departure controller. About 5 seconds later, the captain acknowledged this instruction. Radar data indicated that the airplane climbed to 500 feet above mean sea level (msl) and then entered a climbing left turn to a heading of 220º. About 0915:00, the captain made initial contact with the departure controller, informing him that the airplane was at 1,300 feet msl and climbing to 5,000 feet msl. About 0915:05, the departure controller instructed flight 587 to climb to and maintain 13,000 feet msl, and the captain acknowledged this instruction about 5 seconds later. About 0915:29, the CVR recorded the captain’s statement “clean machine,” indicating that the gear, flaps, and slats had all been retracted.

    About 0915:35, flight 587 was climbing through 1,700 feet msl with its wings approximately level. About 1 second later, the departure controller instructed flight 587 to turn left and proceed direct to the WAVEY navigation intersection (located about 30 miles southeast of JFK). About 0915:41, the captain acknowledged the instruction. The controller did not receive any further transmissions from flight 587.

    FDR data indicated that, about 0915:36, the airplane experienced a 0.04 G drop in longitudinal load factor, a 0.07 G shift to the left in lateral load factor, and about a 0.3 G drop in normal (vertical) load factor. The airplane performance study found that these excursions were consistent with a wake turbulence encounter. Between 0915:36 and 0915:41, the FDR recorded movement of the control column, control wheel, and rudder pedals. Specifically, the control column moved from approximately 0º (neutral) to 2º nose up, 2º nose down, and back to 0º; the control wheel moved a total of seven times, with peaks at 18º right, 30º left, 37º right, 34º left, 5º left, 21º left, and 23º right, before moving to between 5º and 6º left; and the rudder pedals moved from about 0.1 inch left (the starting point for the pedals) to about 0.1 inch right and 0.2 inch left before moving to 0.1 inch left. The airplane performance study indicated that, during this time, the rudder moved from 0º (neutral) to about 2º left, about 0.6º right, and back to 0º.

    During the wake turbulence encounter, the airplane’s pitch angle increased from 9º to 11.5º, decreased to about 10º, and increased again to 11º. The airplane’s bank angle moved from 0º (wings level) to 17º left wing down, which was consistent with the turn to
    the WAVEY navigation intersection.

    At 0915:44.7, the captain stated, “little wake turbulence, huh?” to which the first officer replied, at 0915:45.6, “yeah.” At 0915:48.2, the first officer indicated that he wanted the airspeed set to 250 knots, which was the maximum speed for flight below 10,000 feet msl. At that point, the airplane was at an altitude of about 2,300 feet msl.

    FDR data indicated that, about 0915:51, the load factors began excursions that were similar to those that occurred about 0915:36: the longitudinal load factor dropped from 0.20 to 0.14 G, the lateral load factor shifted 0.05 G to the left, and the normal load factor dropped from 1.0 to 0.6 G. The airplane performance study found that these excursions were also consistent with a wake turbulence encounter. According to the FDR, the airplane’s bank angle moved from 23º to 25º left wing down at 0915:51.5, the control wheel moved to 64º right at 0915:51.5, and the rudder pedals moved to 1.7 inches right at 0915:51.9.

    At 0915:51.8, 0915:52.3, and 0915:52.9, the CVR recorded the sound of a thump, a click, and two thumps, respectively. At 0915:54.2, the first officer stated, in a strained voice, “max power.” At that point, the airplane was traveling at 240 knots. About 0915:55, the captain asked, “you all right?” to which the first officer replied, “yeah, I’m fine.” One second later, the captain stated, “hang onto it. Hang onto it.” The CVR recorded the sound of a snap at 0915:56.6, the first officer’s statement “let’s go for power please” at 0915:57.5, and the sound of a loud thump at 0915:57.7. According to the airplane performance study, the vertical stabilizer’s right rear main attachment fitting fractured at 0915:58.4, and the vertical stabilizer separated from the airplane immediately afterward. At 0915:58.5, the CVR recorded the sound of a loud bang. At that time, the airplane was traveling at an airspeed of about 251 knots.

    According to the FDR, the rudder pedals moved from 1.7 inches right to 1.7 inches left, 1.7 inches right, 2.0 inches right, 2.4 inches left, and 1.3 inches right between 0915:52 and 0915:58.5. Also, the FDR showed that the control wheel moved 64º to the right at 0915:51.5, 78º (full) to the left at 0915:53.5, 64º to the right at 0915:55.5, and 78º to the left at 0915:56.5.

    The airplane performance study estimated that, at 0915:53.2, the rudder was deflected 11º to the left, and the sideslip angle at the airplane’s center of gravity (cg) was about 4º to the left (after peaking temporarily at 5º to the left).21 At 0915:56.8, the rudder was deflected 10.2º to the left, and the sideslip angle was about 7º to the left. At 0915:58.4 (the time that the right rear main attachment fitting fractured), the rudder was deflected between 10º and 11º to the right, the sideslip angle was between 11º and 12º to the right, and the airplane experienced a 0.2 G shift to the right in lateral load factor.

    The CVR recorded, at 0916:00.0, a sound similar to a grunt and, 1 second later, the first officer’s statement, “holy [expletive].” At 0916:04.4, the CVR recorded a sound similar to a stall warning repetitive chime, which lasted for 1.9 seconds. At 0916:07.5, the first officer stated, “what the hell are we into…we’re stuck in it.” At 0916:12.8, the captain stated, “get out of it, get out of it.” The CVR recording ended 2 seconds later. The airplane was located at 40º 34′ 37.59″ north latitude and 73º 51′ 01.31″ west longitude. The accident occurred during the hours of daylight.

    To include the featured image in your Twitter Card, please tap or click their icon a second time.
  • | | | |

    Angel Flight Emergency Landing


    What: Houston to Decatur
    Where: Decatur Municipal Airport
    When: Sept 6 2012, 10:30 a.m.
    Who: 4 aboard
    Why: No one was injured when Pilot Mark Moran made a hard landing in Decatur when returning a passenger from cancer treatment and surgery. Moran is an Angel Flight program pilot, providing free flights to sick people who cannot afford their treatments. Moran came in too fast and would have performed a go round but he didn’t feel he had enough lift to make it over powerlines at the end of the runway. He veered left off the end of the runway through a barbed wire fence. Fire crews sprayed down the leaked fuel.

    (unconfirmed)

    To include the featured image in your Twitter Card, please tap or click their icon a second time.
  • | | |

    Testimony: Icing

    Statement of John Hickey, Deputy Associate Administrator for Aviation Safety

    Before the House of Representatives, Committee on Transportation and Infrastructure, Subcommittee on Aviation on Aircraft Icing

    Chairman Costello, Ranking Member Petri, Members of the Subcommittee: Thank you for inviting me here today to discuss the challenges icing conditions pose to flight operations and the Federal Aviation Administration’s (FAA) efforts to mitigate the safety risks posed by icing. For more than a decade, the FAA has been working to better understand the hazards posed by icing conditions and to improve regulations, policies and procedures to ensure safe airplane operation. Still, research into the complicated phenomenon of icing continues to yield new insights and mitigation measures.

    Today, I want to highlight some of the known icing threats and mitigation measures as well as our icing program approach and a number of our recent efforts that have been crucial to further decreasing the risk associated with aircraft icing. First, however, it is important to understand the framework within which we work to address icing risks.

    As the agency charged with setting the standards for safe aircraft operations, we establish the standards for operations during all types of meteorological conditions, including those that might result in icing on the ground or in flight. Aircraft manufacturers and operators meet these standards through a variety of means depending on where the icing risk occurs (on the ground or in flight), and the aircraft’s system capabilities and intended usage. Our standards for operations in icing conditions encompass both operational and aircraft certification requirements. Operational requirements include standards and aircraft specific operating procedures for icing encounters and pilot and dispatcher training. All pilots engaged in commercial operations must receive training on identification of, safe operation in, and how to avoid and exit icing conditions. They must also be trained on deicing system operation and capabilities of the particular aircraft they operate.

    An aircraft design approval — what we call a “type certificate” — provides the design specifications that an aircraft must be built to, in order to meet the FAA’s standards for safe design. Aircraft must also comply with operation requirements, as set forth by the rules under which the airplane is being operated. Design and operation requirements must both be met in order to satisfy the FAA’s standards for safe operation. In order for an aircraft to be certificated for operations in icing conditions, the aircraft’s manufacturer must be able to demonstrate that the aircraft can safely operate within the icing conditions specified by FAA regulations. We know today that these specified conditions represent 99% of all known atmospheric conditions that result in icing. For the remaining 1%, we are conducting research and are working to translate our findings into certification standards. I want to emphasize that airplanes are prohibited from operations in known icing conditions unless they meet the certification standards for operations in those conditions and at no time may any aircraft continue to operate in severe icing conditions.

    Aircraft Icing

    Unmitigated icing presents risks to aircraft. The accumulation of ice on an aircraft’s wing changes the shape of the wing, and hence the aerodynamic capabilities of the wing to generate lift. For this reason, ice accumulation on an aircraft on the ground may impact the aircraft’s ability to takeoff, while ice accumulation in flight has the potential to raise the minimum speed at which the wing is capable of creating sufficient lift, and potentially causing the aircraft to stall.

    Ground icing: Ground icing is, as the name implies, the accumulation of ice, snow or frost on the aircraft while it is on the ground. This form of icing is both common and meteorologically predictable. During the winter months, the conditions in which ice accumulation on an aircraft is possible become more prevalent and vigilant action becomes necessary to ensure planes are properly deiced and cleared of snow and ice prior to takeoff. Winter precipitation poses a threat to aviation operations because airplane performance is predicated upon the wings being free of contamination. The accumulation of ice, snow, or frost has an adverse effect on the wing’s ability to produce lift, potentially limiting an airplane’s ability to takeoff and climb.

    Currently, the FAA prohibits takeoff unless the airplane’s critical surfaces are completely clear of wintry precipitation. As many of you have likely seen, this is typically achieved by applying deicing or anti-icing fluids to the critical surfaces of the airplane. To provide for a safe takeoff, it is important that a deiced airplane not remain on the ground for an extensive period after deicing during precipitation. At the start of this winter season, as in years past, the FAA issued its annual winter “hold over times” and list of approved anti ice and deicing fluids. “Hold over times” govern the amount of time that may elapse between deicing and takeoff. In the event that the aircraft exceeds the amount of wait time permitted between deicing and takeoff, FAA regulations require the aircraft to be reinspected for adhering contamination or exit the takeoff queue and be deiced again prior to departure. These holdover time tables are revised annually. Some of the reasons for the annual update include improvements in the effectiveness of deicing and anti-icing fluids, reduction of environmental impacts and new information learned through FAA fluid research.

    In-flight icing: Unlike ground icing, in-flight icing knows no season and can be difficult to predict. In-flight icing results from atmospheric conditions that can occur at anytime of the year, regardless of the weather conditions on the ground. According to FAA regulations, any pilot who finds himself or herself in icing conditions while operating an aircraft that is not approved for operations in icing must immediately exit the icing conditions. This means redirecting the aircraft to a different altitude or route, or landing.

    There are multiple atmospheric conditions that can result in the build-up of ice on an aircraft during flight. To mitigate the risk of ice build-up during flight, aircraft that are certificated to operate in icing conditions are equipped with devices that shed ice from the aircraft, such as expandable pneumatic boots, or prevent the formation of ice through the use of heat. A pilot’s ability to recognize icing conditions and activate deicing and anti icing systems in a timely manner is critical to those systems’ effectiveness. Because of the pilot’s critical role in managing flight in icing conditions, we have used both our rulemaking and advisory authorities, to provide pilots with the latest information on how to identify icing, to require early and systematic use of deicing systems and to require exit from icing conditions under certain circumstances.

    Some aircraft are also equipped with ice detection systems. Ice detection systems assist the flightcrew with ice detection and timely activation of the ice protection system. These systems automatically detect ice accretion and annunciate the presence of ice accretion to the flightcrew. Some ice detection systems are designed to automatically initiate the operation of the aircraft deicing systems while others are what we call “advisory” and require the flightcrew to ensure ice protection systems are activated at the first sign of ice accretion on the airplane.

    Although our current regulations address the vast majority of all known icing conditions, we have steadily worked to address two types of in-flight icing phenomena outside of the existing icing certification envelope: supercooled large droplets (SLD) and ice crystals. SLD icing can occur in freezing rain and freezing drizzle conditions — turning water to ice upon contact with the airframe, which can lead to larger accumulations or build up on areas of the wing and tail aft of the protected area. We expect to issue a Notice of Proposed Rulemaking (NPRM) to address this small area of vulnerability, by incorporating atmospheric conditions that are associated with SLD icing into our certification criteria. In the interim, we have taken immediate steps through our airworthiness directive authority to ensure that pilots can identify severe icing which may be produced by SLD conditions and execute exit procedures.

    Ice crystals are also a newly identified threat. We now believe that flight into certain types of storm clouds can cause ice to build up deep inside the core of jet engines and cause temporary shutdowns. Understanding this threat has been particularly challenging because, typically, by the time an aircraft lands, the affected engine has restarted and there is no evidence for us to evaluate. We are currently working with industry and other governmental research partners on developing ways to recreate the atmospheric conditions in which ice crystals form and learn all that we can about how to mitigate the threat of this phenomenon. Although there is research that still needs to be done in this area, we are closely monitoring the condition and its possible causes. To mitigate the risk, the FAA issued Airworthiness Directives (ADs) requiring operational changes when in or near convective weather and engine design changes to make jet engines more tolerant of ice crystal conditions.

    Icing Safety Actions

    Safety concerns about the adequacy of the icing certification standards were brought to the forefront of public and governmental attention by a 1994 accident in Roselawn, Indiana, involving an Avions de Transport Regional ATR 72 series airplane. The NTSB attributed this accident to what we now call SLD–an icing phenomenon that, at the time, was not fully understood. Shortly after this accident, the FAA initiated a review of aircraft safety in icing conditions to determine what could be done to increase safety. This review resulted in our current icing program.

    As meteorologists will attest, simply understanding some of these icing phenomena are difficult and complex. Determining how to address these complex phenomena to support safe aircraft operations takes additional time and extensive research. That is why we tackle the dangers of icing with a multi-prong approach. To address those threats that are clearly understood or for which immediate mitigation is available, we take immediate safety action. In the meantime, concurrent research and development and rulemaking efforts are underway. To date, our icing program includes seven rulemaking initiatives–three have been adopted as final rules, while others are in various stages of development. Additionally, we have issued over 200 ADs on 50 different aircraft models, and have undertaken other operational training and mitigation initiatives.

    Immediate Actions: The FAA’s icing program addresses the immediate icing safety concerns for the current fleet of aircraft through the use of ADs. The FAA has the authority to issue an AD if we determine that some aspect of flying in icing conditions on a particular airplane model creates an unsafe condition that puts the flying public in immediate danger. ADs carry the same force as a regulation and are targeted to specific aircraft makes and models. ADs must be complied with in order to continue operating a covered airplane. As described above, the FAA has been aggressive in issuing ADs when we determine they are needed. These ADs cover safety issues ranging from crew operating procedures and training, to design changes that have significantly reduced the icing risk to the overall fleet.

    For example, with our AD authority, we require that pilots of airplanes equipped with deicing boots activate those boots at the first sign of icing conditions. We have also issued numerous ADs that direct the crews of certain airplane designs on how to monitor and detect early signs of the onset of severe icing and to exit the area immediately. Other ADs require stall warning systems of certain airplanes to be modified to provide an earlier warning of a potential stall in icing conditions and mandate changes to address any susceptibility to stalling of the horizontal tail in icing conditions. These ADs serve as effective safety measures for the current fleet.

    Longer Term Actions: The FAA’s icing program also includes a number of longer term actions to further improve the safety of flying in icing conditions both for the current fleet and for future airplane designs. These actions include rulemaking, issuing safety bulletins, developing improved training material, drafting new or updating existing Advisory Circular guidance material, and further research. We recognize that fast action is an important goal for implementing any safety improvement. We also acknowledge that some actions, such as rulemaking, take longer than others. Rulemaking is a deliberative process that must involve the input of those stakeholders who are affected by the rules.

    Also, in some cases, developing and implementing rules depends on extensive research to understand the particular phenomena and its effect on safety, and to develop appropriate risk mitigations.

    For example, in order to understand SLD icing sufficiently to identify an appropriate set of requirements that airplane manufacturers could comply with, a significant amount of research had to be done. We needed to learn how to characterize SLD, then reproduce it, and finally, understand its effect on airplane operations and designs. For these reasons, at the same time that we tasked the Aviation Rulemaking Advisory Committee (ARAC) to develop certification criteria for the safe operation of airplanes in SLD icing conditions, we also began supporting research efforts by NASA and Environment Canada to gather additional SLD data. Using existing and new SLD data and analysis, the ARAC completed the majority of the work defining the SLD icing envelope. But even after the SLD icing envelope was defined, we continued to learn more about the complexities of SLD, which led us to focus analysis of the impact of SLD on aircraft engines and determine that new standards for smaller aircraft should be considered in a separate rulemaking. The process took time, more time than we anticipated and more time than we wanted, but once we had a sufficient understanding of the science and the technical solutions, we moved forward with the SLD rulemaking. I am pleased to report that the SLD NPRM is now in executive coordination within the Department.

    In the meantime, we formed and tasked an Aviation Rulemaking Committee (ARC) to review the proposed regulations applicable to transport category aircraft for SLD, mixed phase, and ice crystals and recommend how they should be modified for smaller aircraft. The SLD research we conducted for the transport category SLD rulemaking provides the basis for our scientific understanding of SLD, upon which we can develop additional technological solutions for smaller aircraft.

    In addition to the intensive efforts to understand and revise our regulations to address SLD and ice crystals, since 2007, FAA has completed three icing rules and just this week closed the comment period on an additional NPRM. The completed icing rules include:

    • Performance and Handling Qualities in Icing Conditions for Transport Category Airplanes, adding new airworthiness requirements that require designers to demonstrate specific airplane performance and handling qualities for flight in icing conditions.
    • Activation of Airframe Ice Protection System for Transport Category Airplanes, requiring either the automatic activation of ice protection systems or a method to alert pilots when they should be activated. Further, after the initial activation, the ice protection system must operate continuously, automatically turn on and off, or alert the pilots when the system should be cycled.
    • Removal of Airplane Operating Regulations Allowing Polishing of Frost on Wings of Airplanes, effectively prohibiting all aircraft from taking off with polished frost on the wings.

    The NPRM, for which the comment period just closed, would require certain scheduled airlines either to retrofit their existing fleet with ice-detection equipment or make sure the ice protection system activates at the proper time. For those aircraft with an ice-detection system, the FAA proposes that the system alert the crew each time they should activate the ice protection system. The ice protection system would either turn on automatically or pilots would manually activate it. For aircraft without ice-detection equipment, the crew would activate the protection system based on cues listed in their airplane’s flight manual during climb and descent, and at the first sign of icing during cruise.

    We are also evaluating the comments received in response to an additional NPRM that included proposed changes to training and checking requirements for pilots operating flights under part 121. In addition to many other revisions, this NPRM proposed changes that would further specify training requirements for icing operations.

    I want to acknowledge that throughout our ongoing and comprehensive effort to mitigate the risks presented by airplane icing, the National Transportation Safety Board icing recommendations have been instructive. Although we are not always able to take the exact action the Board recommends, we value and fully analyze their recommendations and benefit from their investigations of icing-related accidents. We firmly believe that our actions meet the intent of the vast majority of the Board’s icing recommendations.

    Although we have made significant advancements in our understanding of icing since the tragic 1994 Roselawn accident, icing related threats continue to be a focus of the FAA’s safety experts. The total number of accidents related to environmental icing of airplanes has been decreasing steadily, year after year, for the last 13 years. This safety achievement is the direct result of our intensive focus on improving our understanding of complex icing phenomenon and the best methods for avoiding and mitigating icing conditions. The FAA is proud of this growing safety record and is committed to expanding it.

    Mr. Chairman, Congressman Petri, Members of the Subcommittee, this concludes my prepared remarks. I would be happy to answer any questions that you might have.

    To include the featured image in your Twitter Card, please tap or click their icon a second time.
  • | | | | | |

    Helios Flight 522 Crash Killed 121, Greek Court Acquits Officials


    Click to view full size photo at Airliners.net
    Contact photographer Karl Nixon

    What: Helios Airways Boeing 737-300 en route from Cyprus to Athens to Prague, Czech Republic
    Where: Athens
    When: Aug. 14, 2005
    Who: 121 passengers
    Why: Before losing radio contract, pilots reported trouble with the air conditioning system. In the flight, cabin pressure failure knocked out the pilots. They made it to Athens, but the plane ran out of fuel and crashed. Crash video shows fire fighting planes controlling fires, bodies, baggage, airplane spread over a large debris field, the tail and engines relatively intact. At the time of the crash, except for one pilot (who was observed trying to land the plane), everyone aboard was comatose due to lack of oxygen.

    In the case, prosecution failed to prove that German pilot Hans-Juergen Merten and his Cypriot co-pilot Charalambos Charalambous didn’t meet the minimum standards

    A Cyprus court has acquitted four former airline officials of manslaughter charges.

    In George’s Point of View


    This court case is just another example of how long aviation cases, including the criminal cases of potentially/allegedly responsible parties, can drag on in court.

    See 5 part video study of Flight 522




    To include the featured image in your Twitter Card, please tap or click their icon a second time.