REGARDING THE ACCIDENT OF AMERICAN AIRLINES FLIGHT 587
**** Hidden Message ***** i<BR>SUBMISSION OF THE<BR>ALLIED PILOTS ASSOCIATION<BR>TO THE NATIONAL TRANSPORTATION<BR>SAFETY BOARD<BR>REGARDING THE ACCIDENT OF<BR>AMERICAN AIRLINES FLIGHT 587<BR>AT BELLE HARBOR, NEW YORK<BR>NOVEMBER 12, 2001<BR>NTSB DCA02MA001<BR>In accordance with 49 CFR 831.14, the Allied Pilots Association (APA) a designated Party to the National<BR>Transportation Safety Board (NTSB) investigation of the accident, respectfully submits to the Board its<BR>contributing factors, probable cause, findings, and recommendations.<BR>Communication with respect to this Submission may be addressed to:<BR>First Officer John David<BR>Allied Pilots Association<BR>14600 Trinity Boulevard, Suite 500<BR>Fort Worth, TX 76155<BR>Telephone: 817.302.2150<BR>Fax: 817.302.2152<BR>ii<BR>TABLE OF CONTENTS<BR>1. EXECUTIVE SUMMARY ................................................................1<BR>A. PROBABLE CAUSE AND CONTRIBUTING FACTORS................................3<BR>2. INTRODUCTION.............................................................................5<BR>3. FACTS, ANALYSES, AND RECOMMENDATIONS.....................6<BR>A. FLIGHT CONTROL SYSTEM.............................................................................6<BR>Table 3.1 Comparisons of Rudder Flight Control Systems..........................8<BR>Table 3.2 Paradigm Shift of A-300-600R Rudder Flight Control System...8<BR>Safety Recommendation 1 .............................................................................9<BR>Safety Recommendation 2 ...........................................................................10<BR>B. FLIGHT ENVIRONMENT..................................................................................11<BR>Figure 3.1 Depicted Flight Path of AA 587 and JAL 47 ..............................14<BR>Safety Recommendation 3 ...........................................................................14<BR>Safety Recommendation 3 ...........................................................................15<BR>Safety Recommendation 4 ...........................................................................15<BR>C. ADVERSE AIRCRAFT PILOT COUPLING ....................................................16<BR>Safety Recommendation 5 ...........................................................................19<BR>Safety Recommendation 6 ...........................................................................20<BR>Safety Recommendation 7 ...........................................................................20<BR>D. OVERSIGHT .......................................................................................................21<BR>1. Bilateral Agreement .......................................................................................21<BR>2. Intended Rudder Usage ................................................................................23<BR>3. Maneuvering Speed.......................................................................................24<BR>4. Aircraft Separation Standards ......................................................................25<BR>Safety Recommendation 8 ...........................................................................26<BR>Safety Recommendation 9 ...........................................................................27<BR>Safety Recommendation 10 .........................................................................27<BR>Safety Recommendation 11 .........................................................................28<BR>4. SUMMATION................................................................................ 29<BR>WORKS CITED................................................................................... 30<BR>LIST OF SAFETY RECOMMENDATIONS....................................... 31<BR>1<BR>1. EXECUTIVE SUMMARY<BR>American Airlines (AA) Flight 587 departed Runway 31L at John F. Kennedy<BR>International Airport on November 12, 2001. The A300B4-605R departed at<BR>approximately 0916 EDT. Two FAA- licensed airmen with over 3,500 combined flight<BR>hours in the A300B4-605R flew the aircraft observing rules, regulations, and<BR>governances mandated by Federal Aviation Regulation (FAR) Part 121. The pilots also<BR>adhered to rules and procedures stipulated by the Federal Aviation Administration<BR>(FAA), the aircraft manufacturer, Airbus, and the certificated air carrier, American<BR>Airlines. AA Flight 587, Aircraft Registration N14053, followed a heavy Japan Air Lines<BR>(JAL) Boeing 747-400. The departure spacing between the two aircraft complied with the<BR>current aircraft separation requirements established by the FAA. Once airborne, a<BR>sequence of events rapidly occurred. The airplane encountered one or more wake vortices<BR>trailing the B-747-400 aircraft. The Pilot Flying (PF) the airplane reacted judiciously to<BR>stabilize the attitude of the airplane in response to the vortices. Aerodynamic forces<BR>exceeded ultimate load on the tail fin within 6.5 seconds, causing the vertical stabilizer to<BR>separate from the aircraft. Twelve seconds later, the aircraft impacted the ground killing<BR>all onboard. The horrific accident happened in less than 90 seconds on a clear morning<BR>with no significant weather. The aviation community was left to investigate an event that<BR>had never happened to a U.S. transport aircraft: the separation of a major component<BR>from an airplane structure.<BR>To understand the separation of the vertical stabilizer, accident investigators began to<BR>look at a number of variables, chiefly:<BR>¡¤ Aircraft design, certification, and modification, concentrating on the flight<BR>control design and the composite structure<BR>¡¤ Other in-service events of A-300 aircraft<BR>¡¤ Pilot behavior and decision making<BR>¡¤ Pilot interaction with the aircraft, including adverse Aircraft Pilot<BR>Coupling (APC)<BR>¡¤ Aircraft separation spacing<BR>¡¤ Effects of wake vortices on trailing aircraft<BR>The discovery process uncovered ten prior in-service events concerning A-300 aircraft,<BR>beginning with an Interflug Airlines event in 1991. In all ten events, the vertical<BR>stabilizers of each Airbus aircraft were exposed to excessive aerodynamic loads¡ªthree<BR>even exceeding ultimate load (United States 2003 (Public Hearing Exhibit 7Q). When the<BR>manufacturer observed these highly unusual in- flight events, Airbus should have<BR>investigated the flaws in the design as the limit load is the maximum load expected when<BR>the aircraft is in service. Ultimate load is defined as the limit load multiplied by a safety<BR>2<BR>factor of 150%.1 The manufacturer failed to correlate the deficiencies obvious in the inflight<BR>events and placed blame on other parties. It is the manufacturer¡¯s responsibility to<BR>assess whether a deficiency exists and, if so, to determine the commensurate need for a<BR>mitigating strategy to prevent a catastrophe. Furthermore, according to the Bilateral<BR>Aviation Safety Agreement (May 1996), Airbus should have disseminated critical<BR>information as a function of their monitoring of in-service aircraft. Yet, throughout the<BR>ten-year span of in-service events, Airbus inexplicably failed to issue any Airworthiness<BR>Directives (ADs), Immediate Action Bulletins, Technical Bulletins, Flight Crew<BR>Operating Manual (FCOM) revisions, or Flight Manual limitation revisions.<BR>Investigators also learned in the discovery process that, in an in-service event in 1997,<BR>another AA Airbus 300-600 vertic al stabilizer had exceeded ultimate load. They<BR>questioned why multiple overloads of the tail fin¡ªa primary aircraft structure¡ªoccurred<BR>without warning. To investigators, there appeared to be a certification ¡°loophole¡± since<BR>aircraft certificating authorities left these in-service events unaddressed. The inaction on<BR>the part of either the manufacturer or the certificating authority violates U.S. transport<BR>certification criterion as neither party acted to ensure the aircraft design met industry<BR>standards. The breakdown in the integrity of the system that governs transport category<BR>aircraft shocked the aviation industry as the investigation progressed, and the flight<BR>community learned that critical operating limitations of the A300 had not been revealed<BR>for over a decade. Investigators uncovered these startling facts months after the 587<BR>accident while the flight crew had less than 6.5 seconds to analyze and react to the<BR>aircraft as it became unrecoverable.<BR>At the public hearing, the manufacturer testified that, unlike aircraft manufactured in the<BR>United States, the A300-600 aircraft had not undergone formal testing for aircraft<BR>handling characteristics. Aircraft manufactured in the U.S. must undergo testing that<BR>evaluates aircraft handling characteristics in both benign and adverse flight conditions.<BR>U.S. aircraft manufacturers employ a standard methodology such as those defined in<BR>Advisory Circular (AC) 25-7A. Airbus used an internal rating system that they felt met<BR>the requirements of FAR 25 but did not apply their internal rating system to gauge the<BR>handling characteristics of the A300-600 in a wake vortices environment.<BR>Facts uncovered during this investigation also highlighted a flaw which is inherently built<BR>into the A300B4-605R rudder design. Airbus¡¯ predecessor aircraft, the A300B2/B4<BR>variant, is equipped with a rudder in which the pilot would exert control forces similar to<BR>those found in other transport category aircraft. However, the modified A300B4-605R<BR>exhibits an oversensitive rudder; it is 7.32 times more sensitive than the similarly- sized<BR>Boeing 767 rudder control system. The FCOM provided by Airbus fails to notate the<BR>extreme rudder control sensitivity difference, fails to outline restrictions placed upon<BR>rudder usage, and fails to reveal how Airbus intended the pilot to use this system.<BR>1 FAR Part 25.301 states, ¡°(a) Strength requirements are specified in terms of limit loads<BR>(the maximum loads to be expected in service) and ultimate loads (limit load multiplied<BR>by prescribed factors of safety).¡±<BR>3<BR>A corollary effect of the A300B4-605R rudder pedal sensitivity is the propensity for a<BR>pilot to become adversely coupled with the aircraft. This anomaly is known as adverse<BR>Aircraft Pilot Coupling (APC) and is usually the result of a deficient flight control design.<BR>An APC event causes a pilot¡¯s rudder inputs to be out of sync with the motion of the<BR>aircraft. In the case of Flight 587, the Pilot Flying¡ªuninformed and unaware of the<BR>hypersensitive rudder pedals¡ªmade appropriate and controlled rudder inputs in response<BR>to the aircraft¡¯s motion as it encountered wake vortices. An unintentional result was that<BR>excessively high aerodynamic loads were placed on the vertical stabilizer which then<BR>broke off the aircraft only 9 seconds after the first rudder pedal input.<BR>A. PROBABLE CAUSE AND CONTRIBUTING FACTORS<BR>The probable cause of this accident was an Aircraft Pilot Coupling (APC) event. This<BR>APC occurrence was the result of a flawed design modification to the A300.<BR>Additionally, the modification was not tested by an accepted Handling Qualities Rating<BR>Method (HQRM). The APC event led to the development of excessive aerodynamic<BR>loads and consequent structural failure of the vertical stabilizer in only 6.5 seconds.<BR>Airbus was forewarned of this catastrophe by preceding in-service events and failed to<BR>caution operators and regulators of this tendency.<BR>The contributing factors of the accident are outlined below:<BR>a. Airbus failed to identify the dramatic changes in a rudder control design that<BR>radically deviated from other aircraft designs.<BR>b. Airbus failed to use an objective standard for rating the aircraft handling<BR>characteristics of the A300B4-600R flight control design, such as the FAA<BR>Handling Quality Rating Method (HQRM), or the Cooper-Harper Pilot<BR>Rating.<BR>c. Airbus failed to publish limitations on the aircraft¡¯s rudder design.<BR>d. Airbus failed to properly educate operators about rudder system limitations.<BR>e. Airbus failed to design an appropriately redundant flight control sys tem that<BR>provides protection by limiting the rudder¡¯s ability to generate excessive<BR>lateral loads on the aircraft structure.<BR>f. Airbus failed to responsibly investigate and report resolutions to prior inservice<BR>events.<BR>g. Aircraft certification authorities failed to require the quantitative evaluation of<BR>flight characteristics and handling qualities for a derivative aircraft design,<BR>thereby ensuring that the derivative model was not susceptible to the hazards<BR>of APC.<BR>4<BR>h. Aircraft certification authorities failed to require quantitative aircraft flight<BR>characteristic and handling quality testing in the presence of wake vortices as<BR>part of the approval process of new and derivative aircraft designs.<BR>i. Regulatory and certification authorities failed to ensure that airmen had proper<BR>knowledge of structural certification requirements for the rudder and vertical<BR>stabilizer.<BR>j. Regulatory authorities failed to ensure mitigation of the risks presented by the<BR>wake vortices of aircraft now approaching 1 million pounds gross weight and<BR>generating significantly stronger and more violent disturbed air masses than<BR>those originally tested in determining criterion for safe aircraft spacing.<BR>k. Regulatory authorities incorrectly defined maneuvering speed (Va) leading to<BR>an industry-wide misconception of the fundamental principle.<BR>5<BR>2. INTRODUCTION<BR>¡°System safety is a specialty within system engineering that supports program risk<BR>management. It is the application of engineering and management principles, criteria<BR>and techniques to optimize safety. The goal of system safety is to optimize safety by the<BR>identification of safety related risks, eliminating or controlling them by design and/or<BR>procedures, based on acceptable system safety precedence¡± (3. 3-2).<BR>The FAA System Safety Handbook<BR>In order for the reader to best understand the complex factors of the AA 587 accident, the<BR>Facts, Analyses and Recommendations portion of this report is divided into four main<BR>areas:<BR>¡¤ Flight Control System<BR>¡¤ Flight Environment<BR>¡¤ Adverse Aircraft Pilot Coupling<BR>¡¤ Oversight<BR>Each section contains facts and analysis followed by recommendations.<BR>This was a complex accident. The Allied Pilots Association (APA) offers this Submission<BR>to aid the Safety Board in its analysis. Suggestions for specific safety recommendations<BR>that APA believes should be a part of the Final Report are compiled at the end of the<BR>report.<BR>6<BR>3. FACTS, ANALYSES, AND RECOMMENDATIONS<BR>A. FLIGHT CONTROL SYSTEM<BR>¡°Control forces should not be so high that the pilot cannot safely maneuver the airplane.<BR>Also the forces should not be so light that it would take exceptional skill to maneuver the<BR>airplane without overstressing it or losing control. The airplane response to any control<BR>input should be predictable to t he pilot.¡± <BR>FAA Advisory Circular 25-7A<BR>In civil aviation, an airplane is judged airworthy by meeting certification standards<BR>established in commercial aviation by FAR Part 25 or the European equivalent. The basis<BR>of this assurance of airworthiness is an understanding that the manufacturer has proven<BR>the proper functioning of the airplane systems, such as the Flight Control System (FCS).<BR>This proof is obtained through extensive analysis, simulation, and flight testing in all<BR>possible flight conditions. The investigation of AA 587 uncovered a lack of design and<BR>regulatory oversight and questionable engineering practices as the airplane evolved from<BR>its original certification basis, the A300B2-1A. The aircraft was adapted over time with a<BR>significantly modified FCS¡ªwithout updating the original certification basis or<BR>complying with bilateral agreements between the United States and French<BR>manufacturers.<BR>The A300B2-1A airplane2 was the first Airbus design, literally their launch vehicle as an<BR>airplane manufacturer. The FCS was a standard hydro- mechanical, servo-control system,<BR>incorporating an analog computer for flight augmentation functions. This was necessary<BR>to address undesirable handling qualities such as Dutch roll in the lateral axis. By the<BR>1980s, digital technology began to supercede analog technologies, and Airbus moved to<BR>modify the original design with digital autopilot and flight augmentation computers while<BR>maintaining the same basic flight control architecture¡ªexcept in the primary FCS of the<BR>rudder design and the secondary FCS system of the spoilers. In 1982, the A310/A300B4-<BR>600 aircraft used digital computers and limited Fly-by-Wire (FBW) technologies with<BR>spoiler movement for roll control. This system is also capable of inducing adverse yaw,<BR>an undesirable lateral motion counteracted by the rudder or yaw damper or both.<BR>The main differences of the modified FCS of the A310/A300-600 spoiler control are<BR>summarized below. These differences are significant in both their physical and handling<BR>quality changes to the airframe.<BR>¡¤ All mechanical linkage and servomotors previously required on the A300B2/B4<BR>spoiler control system were eliminated and actuators were electrically signaled.<BR>2 1971, U.S. certification 1974<BR>7<BR>¡¤ The command/monitoring computer became the basic architecture building block.<BR>It allowed a command channel failure to be detected and neutralized.<BR>¡¤ Each command or monitoring unit included all the electronic components needed<BR>to perform its function without sharing resources with another component.<BR>¡¤ All functions, including spoiler actuator servo-loops, became software based and<BR>fully under control of digital units.<BR>¡¤ Roll control was optimized according to airspeed and flap position. The spoiler<BR>contribution to roll control was significantly increased in comparison to the<BR>previous A300B2 design. One set of ailerons (outboard) was eliminated on the<BR>A310/A300-600 design.<BR>¡¤ Modified and enhanced Flight Control Laws (FCLs) and flight envelope<BR>protection were added.<BR>¡¤ The rudder control unit was changed from Variable Lever Arm (VLA) to Variable<BR>Stop Actuator (VSA).<BR>¡¤ Side-stick pilot controls were incorporated.3<BR>The A300B2/B4 model used a rudder control system employing a Variable Lever Arm<BR>(VLA) to limit rudder travel. A similar rudder-ratio changer design is also fo und in most<BR>other transport category aircraft. The VLA limited the amount of rudder available to the<BR>pilot as the airplane¡¯s speed increased. The rudder pedals consistently moved the same<BR>physical distance, yielding a proportion of rudder relative to speed. In 1988, Airbus<BR>implemented a completely new rudder design, which significantly modified the function<BR>of the previous model and hence, the handling qualities of the new A300-600 airplane<BR>design. This new system used a Variable Stop Actuator (VSA) which is also found in the<BR>MD-80. The VSA also limited the amount of rudder available to the pilot. The difference<BR>in this system is that the distance which the rudder pedals moved also decreased as the<BR>rudder movement decreased in proportion to speed. A significant flaw in the design failed<BR>to offer the same kind of protection as in the McDonnell design. The MD-80 limits<BR>rudder travel and affords protection in the form of rudder ¡°blow down¡± should an<BR>operator demand more rudder travel (with resultant excessive load) than the structure can<BR>withstand. These kinds of redundant system designs are common in commercial<BR>aviation¡ªa standard that should be addressed during certification. The Airbus Flight<BR>Crew Operations Manual (FCOM) addresses the rudder system much like any other<BR>manufacturer and, in fact, did not change the language of the FCOM even after changing<BR>the A300 design from the VLA to the VSA system.<BR>The significance of this modification is best illustrated by reviewing the input required to<BR>move the rudder. The input is comprised of the pilot¡¯s tactile feel and level of exertion<BR>necessary to incrementally manipulate the flight controls and maneuver the flight path of<BR>the aircraft. Table 3.1 is a comparison of rudder control systems across a variety of<BR>manufacturers.<BR>3 These were not used on American Airlines A300-600s.<BR>8<BR>Table 3.1 Comparisons of Rudder Flight Control Systems<BR>Aircraft<BR>Maximum<BR>Force/Breakout<BR>Force Digital Ratio<BR>Degrees of Rudder Per<BR>Pound of Force Above<BR>Breakout<BR>A-300-600B2 4.68 .090<BR>A-300-600B4 4.68 .090<BR>B-757 5.00 .094<BR>B-737 3.33 .114<BR>B-767 4.71 .127<BR>MD-80 4.00 .178<BR>DC-9 3.75 .182<BR>B-747 4.21 .197<BR>B-727 2.94 .212<BR>B-777 3.33 .214<BR>DC-10 6.50 .255<BR>MD-11 6.50 .273<BR>MD-90 3.25 .288<BR>B-717 3.25 .289<BR>(Official Docket Aircraft Performance Report 12)<BR>Table 3.2 is the same comparison of rudder control systems with the addition of the<BR>A300-600R at the bottom.<BR>Table 3.2 Paradigm Shift of A-300-600R Rudder Flight Control System<BR>Aircraft<BR>Maximum<BR>Force/Breakout<BR>Force Digital Ratio<BR>Degrees of Rudder Per<BR>Pound of Force Above<BR>Breakout<BR>A-300-600B2 4.68 .090<BR>A-300-600B4 4.68 .090<BR>B-757 5.00 .094<BR>B-737 3.33 .114<BR>B-767 4.71 .127<BR>MD-80 4.00 .178<BR>DC-9 3.75 .182<BR>B-747 4.21 .197<BR>B-727 2.94 .212<BR>B-777 3.33 .214<BR>DC-10 6.50 .255<BR>MD-11 6.50 .273<BR>MD-90 3.25 .288<BR>B-717 3.25 .289<BR>A-300-600R 1.45 .93<BR>(Official Docket Aircraft Performance Report 12)<BR>9<BR>The change in maximum force and degrees of rudder per pound between the A300B2/B4<BR>and the A300-600 is highly significant. The A300 family has the distinction of having the<BR>lightest breakout force and the highest number of degrees of rudder travel per pound of<BR>force of any other transport category aircraft. Once a pilot initiates rudder movement, he<BR>or she will be challenged with the most sensitive rudder handling qualities of any<BR>transport category airplane. This sensitivity is a precursor to a characteristic known as<BR>Aircraft Pilot Coupling (APC), a condition typically ¡°¡not feasible for a pilot to realize<BR>and react to in real time,¡± and considered unacceptable in U.S. certified designs<BR>(National Research Council 15). Simply, a very light application of force coupled with a<BR>very small movement of the rudder pedal will yield full deflection of the rudder.<BR>¡°Artificial trim and feel systems which produce controllers with too small a displacement<BR>and light force gradients may also lead to severe overcontrol.¡±<BR>FAA Advisory Circular 25-7A<BR>¡°Good flying qualities are fundamental to the elimination of adverse APC. These are<BR>defined in the form of requirements with relevant metrics to be satisfied (8).¡±<BR>National Research Council<BR>The reason for such a significant design difference between these two variants of the<BR>A300 has not been determined. Airbus has not produced a quantitative methodology,<BR>such as the FAA¡¯s Handling Qualities Rating Method (HQRM) or Cooper-Harper tests,<BR>to demonstrate how they evaluated the handling qualities of the variant airplane. Mr.<BR>Jacob, Airbus test pilot, could only explain their methodology at the NTSB Public<BR>Hearing as, ¡°We qualify it to¡ªwe check it¡ªwe¡ªand that means test pilots from<BR>manufacturers and from the certification authorities¡ªqualify the suitability of the<BR>aircraft¡± (540). That statement bears no similarity to the requirements of 14 CFR Part 25.<BR>Safety Recommendation 1<BR>The NTSB should recommend that the FAA require evaluation of all<BR>aircraft operating under U.S. type certification by FAA Handling<BR>Qualities Rating Method (HQRM) or equivalent.<BR>10<BR>Safety Recommendation 2<BR>The NTSB should recommend that the FAA and French DGAC form<BR>an Engineering Evaluation Team to work with Airbus and the<BR>operators of the A310/A300-600 to determine whether pilot training<BR>alone is an adequate remedy to the undesirable Flight Co ntrol System<BR>(FCS) characteristics of these aircraft, or if an FCS modification is<BR>also required.<BR>11<BR>B. FLIGHT ENVIRONMENT<BR>¡°Wake turbulence accidents and incidents have been, and continue to be, a significant<BR>contribution to the worldwide safety statistics¡± (1-1).<BR>Wake Turbulence Training Aid<BR>The encounter of AA 587 with the wake vortices of the preceding aircraft, a Boeing 747-<BR>400, triggered the events leading to catastrophic structural failure of the accident aircraft.<BR>NASA engineers have analyzed the DFDR data from AA Flight 587 and JAL Flight 47,<BR>attempting to recreate the forces of the wake vortices encountered. DFDR data confirms<BR>that the aircraft flew normally until the encounter. Engineers were hampered in their<BR>attempts to analyze the data by three factors (Aircraft Performance Report, 19-20, 11;<BR>Appendix A, 19):<BR>1) Low sampling rates of both DFDRs<BR>2) Lack of specific data to perform force calculations<BR>3) Ambiguous data on flight control and handling characteristics of the<BR>A300<BR>Additionally, they were handicapped in the DFDR analysis by a filter in the System Data<BR>Analog Converter (SDAC) whose properties Airbus was unable to define.<BR>AA 587¡¯s flight path was disturbed by two potentially destructive wake vortices<BR>generated by the Boeing 747-400 aircraft. The vortices carried the legacy of thousands of<BR>documented and undocumented wake turbulence incidents and accidents. Wake<BR>turbulence issues have been clouded by economic influences, particularly airport<BR>capacity. The most direct fix of this problem is to increase separation. This is also the<BR>most opposed solution due to its economic impact. It is time for safety and science to<BR>override economics.<BR>The existence and destructive potential of wake turbulence is more than adequately<BR>substantiated throughout the history of turbojet transport aircraft operations. The<BR>phenomenon has been the subject of study by U.S. and international regulatory agencies,<BR>accident prevention and investigation authorities, and private aviation safety<BR>organizations. Significantly, the character of turbojet transport aircraft has changed<BR>dramatically in terms of operating weights and wing design. These two principal factors<BR>in wake vortex signature are significant in relevance to the 587 accident. Industrial efforts<BR>to determine the wake signatures of new-generation aircraft, such as the 747-400,<BR>however, are absent. Efforts to assess risk in determining the adequacy of wake<BR>turbulence separation criteria applied by Air Traffic Control (ATC) authorities are also<BR>equally absent.<BR>12<BR>Based on a 10- year period of data collection, the Civil Aviation Authority of Great<BR>Britain (CAA) changed from a three- group airplane weight category to a four-group<BR>weight category. In 1991, the CAA presented a paper to participants of an FAAsponsored<BR>conference on aircraft wake vortices held in Washington, D.C. This paper<BR>stated, ¡°The four-group scheme (weight categories) introduced in 1982 was divided as a<BR>result of incident data gathered in earlier years and was designed to provide extra<BR>protection for some types of aircraft found to suffer particularly severe disturbance<BR>behind heavy group aircraft¡± (Wake Turbulence Training Aid, Appendix 4-A, 12). The<BR>CAA, in analysis of events reported between 1972 and 1990, found that ¡°¡the B-747<BR>and B-757 airplanes appear to produce significantly higher incident rates than the other<BR>airplanes considered, indicating prima facie that they produce stronger and more<BR>persistent vortices than other aircraft in their respective weight categories¡¡± (Wake<BR>Turbulence Training Aid Appendix 4-A 13). The maximum take-off weight for the B-<BR>747 at the time of the study was 317,000 kg. or 818,000 lbs (Wake Turbulence Training<BR>Aid, Appendix A, 14). The take-off weight of JAL Flight 47 was 780,000 lbs. Clearly, the<BR>CAA¡¯s four-group weights classification system is relevant to AA 587¡¯s wake encounter.<BR>The FAA divides groups of aircraft in the following manner:<BR>Small aircraft <41,000 lbs.<BR>Large aircraft are between 41,000 lbs. and 255,000 lbs.<BR>Heavy aircraft > 255,000 lbs.<BR>Aircraft are now approaching maximum take-off weights of 1 million pounds. A different<BR>weight group is required for 214,000 pounds of difference in weight (Small to Heavy) but<BR>not for 615,000 pounds of difference (Heavy minimum weight to 747 maximum take-off<BR>weight). NTSB Safety Recommendation A-94-043 clearly states:<BR>¡°...the Board still believes that the most significant problem related to establishing<BR>adequate separation standards is the great range of aircraft weights involved. Thus the<BR>Board believes it would be prudent to create four weight categories in which the ratios of<BR>the high and low weights within each category are similar.¡±<BR>Accordingly, separation standards should reflect the revised weight categories.<BR>The FAA Wake Turbulence Training Aid states on page 2.3:<BR>¡°The strength of wake turbulence is governed by the weight, speed and wingspan of the<BR>generating aircraft. The greatest strength occurs when the generating aircraft is heavy,<BR>at slow speed with a clean wing configuration.¡±<BR>This is precisely the situation encountered by AA 587.<BR>The FAA has limited knowledge of the strength of wake vortices but has seen multiple<BR>incidents and accidents due to this phenomenon. The wake from one of the heaviest<BR>among heavy aircraft, one that the CAA found to be ¡°stronger and more persistent,¡±<BR>created forces that absolutely demanded a response from the pilot of AA 587 (Wake<BR>13<BR>Turbulence Training Aid Appendix 4-A 13). This response to stabilize the aircraft¡¯s flight<BR>attitude triggered the ensuing APC.<BR>Computational Fluid Dynamics (CFDs) and wind tunnel modeling have been used to<BR>predict aircraft behavior, but they are unsatisfactory in determining characteristics and<BR>handling qualities which can involve the coupling of an aircraft, pilot, and environments<BR>such as the counter-rotating air mass of wake vortices. In December 1999, the Safety<BR>Board stated in Safety Recommendation A-94-043 that it ¡°¡does not believe that<BR>unvalidated theoretical evaluations should be used to justify decreased safety<BR>margins such as exemptions to the weight classification system.¡± Additionally, in the<BR>same recommendation, ¡°The Safety Board has no evidence that the FAA/NASA wake<BR>vortex simulation has sufficient validity to define risk in an actual wake vortex<BR>encounter.¡±<BR>The principal conclusions previously reached by the NTSB, and which are cited in the<BR>Wake Turbulence Training Aid (Appendix 4-A 28) of 1994, remain. Currently, the<BR>conclusions stand as:<BR>1. Current Air Traffic Control (ATC) procedures and pilot reactions can<BR>result in aircraft following too closely behind larger aircraft.<BR>2. Pilots do not have sufficient information to determine relative flight paths<BR>and maintain adequate separation distances relative to wake vortices.<BR>AA 587 took off from Runway 31L with the required two minutes of separation from<BR>JAL 47. Upon departing, the Air Route Traffic Control Center (ARTCC) gave the<BR>accident aircraft a turn to the WAVEY intersection. This vector placed the American<BR>airplane inside the turn of the preceding 747, effectively creating a rendezvous turn. The<BR>flight path of the two airplanes is depicted in Figure 3.1 (Official Docket Aircraft<BR>Performance Report 47). The turn immediately reduced the separation between the two<BR>aircraft, exposing AA 587 to a more powerful wake vortex than the departure separation<BR>should have assured. Additionally, the prevailing winds blew the vortices from the 747<BR>into the flight path of the A300. Both of these hazards occurred without the knowledge of<BR>the 587 flight crew, inadvertently exposing them to dramatically- increased risk.<BR>14<BR>Figure 3.1 Depicted Flight Path of AA 587 and JAL 47<BR>15<BR>Safety Recommendation 3<BR>Safety Recommendation 4<BR>The NTSB should recommend that the FAA reexamine the validity of<BR>current ATC wake turbulence separation standards. Focus of the<BR>review should be on the standards for the wide range of ¡°heavy¡±<BR>airplanes currently in operation, and for larger aircraft, such as the<BR>Airbus A380 coming in the near future. This examination should<BR>include new technology and should study proposals for improving<BR>controller training and understanding of wake vortices, including<BR>variables such as relative wind, atmospheric stability, and ATC<BR>vectoring.<BR>The NTSB should recommend the FAA comply with open Safety<BR>Recommendation A-94-056 which states, ¡°Require manufacturers of<BR>turbojet, transport category airplanes to determine, by flight test or<BR>other suitable means, the characteristics of the airplanes¡¯ wake<BR>vortices during certification environment.¡±<BR>16<BR>C. ADVERSE AIRCRAFT PILOT COUPLING<BR>Aircraft Pilot Coupling (APC) is one of the most challenging flight characteristics known<BR>to aerodynamicists and designers of Flight Control Systems (FCSs). It is an unwanted<BR>design flaw affecting the aircraft attitude and motion(s) once disturbed from stable state<BR>conditions. Beginning with an initiating event, these flight characteristics form a<BR>continuous or ¡°closed-loop¡± interaction between the aircraft and the pilot (National<BR>Research Council 14). The phenomena of APC events have often been associated with<BR>the introduction of new technologies, functionalities, or complexities such as the change<BR>on the A300 rudder control system.<BR>¡°APC events are collaborations between the pilot and the aircraft in that they occur only<BR>when the pilot attempts to control what the aircraft does. For this reason, pilot error is<BR>often listed as the cause of accidents and incidents that include an APC ev ent. However,<BR>the committee believes that the most severe APC events attributed to pilot error<BR>are the result of adverse APC that misleads the pilot into taking actions that contribute to<BR>the severity of the event. In these situations, it is often possible, after the fact, to analyze<BR>the event carefully and identify a sequence of actions the pilot could have taken to<BR>overcome the aircraft design deficiencies and avoid the event. However, it is typically not<BR>feasible for the pilot to identify and execute the required actions in real time¡± (161).<BR>National Research Council<BR>The National Research Council (NRC) describes an APC event as both oscillatory and<BR>non-oscillatory divergences from the desired flight path. The pilot is involved (due to his<BR>or her responsibility to respond to an uncommanded aircraft motion) by manipulation of<BR>the flight controls to modify or negate input in a ¡°closed- loop¡± fashion that determines<BR>the flight path of the airplane. The NRC has previously established that the most severe<BR>oscillatory APC events show flight control rate limiting. Rate limiting of the A300 flight<BR>controls has been confirmed by the ground tests conducted by the NTSB Human<BR>Performance and Systems Groups, and Dr. Hess. FAA AC 25-7A also addresses rate<BR>limiting as a root cause for APC. The irony of an APC event is that releasing the controls,<BR>a procedure taught to test pilots but contrary to line pilot training, is one of the most<BR>effective means to counter this adverse condition. Releasing the flight controls is viewed<BR>as so desperate by U.S. aircraft certification authorities that the need to ¡°open the loop¡± in<BR>this manner to maintain control of an aircraft is considered unsatisfactory. Simply stated,<BR>a design which has demonstrated a propensity for APC and subsequent need for the pilot<BR>to release the controls is a non-airworthy design for transport category aircraft.<BR>The divergent motions of the A300 (with the most sensitive rudder control system of any<BR>transport category aircraft) unexpectedly and unpredictably reacted to the environment<BR>and to the pilot attempts to control it. These subsequent lateral accelerations occurred in<BR>the brief period after the aircraft tangentially traversed the counter-rotating wake field<BR>during the final seconds of the AA 587 flight. The forces imposed on the airplane by the<BR>rudder doublets, commanded in response to the unwanted motion, exceeded the vertical<BR>stabilizer structural limitations. The total system failure began with a faulty flight control<BR>17<BR>design and culminated with a pilot struggling to control an aircraft that only moments<BR>before had been a docile, stabilized platform. The aerodynamic loads built in excess of<BR>ultimate load; separation of the vertical stabilizer occurred only 6.5 seconds after the<BR>aircraft entered the vortices of the 747 (Official Docket Aircraft Performance Report 33).<BR>One of the findings of the NRC study states:<BR>¡°Adverse APC events are rare, unintentioned, and unexpected oscillations or divergences<BR>of the pilot-aircraft system. APC events are fundamentally interactive and occur during<BR>highly demanding tasks when environmental, pilot, or aircraft dynamic changes create or<BR>trigger mismatches between actual and expected aircraft responses¡± (33).<BR>National Research Council<BR>In 1997, at the time the NRC published its report, they had identified ten possible pilotinvolved<BR>oscillatory APC events in Airbus aircraft. The manufacturer acknowledged only<BR>three as genuine¡ªbut even one is an acknowledgment of an unsatisfactory aircraft design<BR>and a flawed certification system.<BR>In addition to the reluctance of the manufacturer to admit or address latent deficiencies in<BR>the A300 control design, analysis is further complicated because APC events have been<BR>difficult for line pilots to detect and report. Test pilots are trained to recognize and<BR>analyze APC anomalies; commercial line pilots are not. Further exacerbating discovery<BR>of this latent hazard is the low fidelity of Digital Flight Data Recorders (DFDRs). The<BR>low sampling rate of current DFDRs does not facilitate post-event analysis of high<BR>frequency oscillatory APC events. The sampling rates of flight control parameters are<BR>typically one to two hertz. These rates are designed to best record human versus<BR>mechanical discrepancies. A much higher rate and unfiltered data is required to<BR>accurately assess flight control motion. At the NTSB Public Hearing for Flight 587,<BR>Investigator-In-Charge (IIC) Robert Benzon stated:<BR>¡°In 1994, the Safety Board recommended to the FAA that such filtering be removed from<BR>information sent to the flight recorders. And yet in 2001, this investigation was hampered<BR>by totally unacceptable filtering of the data. In addition, the sampling rates of such data<BR>are simply not adequate¡± (31).<BR>Airbus clearly subscribes to the use of enhancements offered by the digital age with<BR>modifications to the flight control design of their aircraft, including the A300-600. Flight<BR>augmentation computers, flight envelope protection and even limited Fly-by-Wire (FBW)<BR>technologies were modified into this derivative model in 1986. Verification through flight<BR>testing of these new technologies is appropriate with respect to flight control changes.<BR>Testing should be accomplished through proven evaluation methods, such as the FAA¡¯s<BR>Handling Qualities Rating Method (HQRM).<BR>The Pilot In Command (PIC), assisted by the designated Pilot Flying (PF) were both<BR>type-rated in the A300/310 aircraft. Type-rating training is developed in accordance with<BR>FAR 121.401 using the aircraft information provided by the manufacturer. Pilots must<BR>18<BR>demonstrate competent knowledge of the aircraft as well as complete an extensive<BR>flight/simulator-based training course. Both pilots had completed this process; however,<BR>no line pilot possessed critical knowledge of the limitations in the A300 design. The<BR>critical peculiarities of the flight control design found in this investigation were not<BR>shared with pilots or with American Airlines. Further confounding the understanding of<BR>rudder system limitations was the Flight Manual ¡°L/G Unsafe Indication¡±<BR>procedure which dictated alternating sideslips. The overall sensitivity of the rudder<BR>system was not addressed nor was a prohibition on rudder reversals placed in the FCOM<BR>or flight manual. The manufacturer¡¯s decision to omit information from the FCOM links<BR>a failure to recognize a latent hazard (sensitive rudder) with a supervisory failure to<BR>mitigate future risk. With this higher-risk design, it was only a matter of time before the<BR>necessary preconditions were met for the airplane to experience a non-recoverable<BR>adverse APC event.<BR>A training program could not have been developed because the manufacturer offered no<BR>information about the limitations or peculiarities of the rudder system. Neither pilot was<BR>trained to experience this unexpected and unpredictable flight characteristic nor the<BR>aircraft gyrations experienced in the accident sequence. It was far beyond the pilots¡¯<BR>practical experience, surprising the PF and leaving the PIC unaware of the peril they<BR>faced as the PF struggled to maintain control of the aircraft.<BR>The pilots experienced ¡°Surprise and Startle¡± factor, a known Human Performance<BR>reaction, when the aircraft entered the wake field, and the resultant unanticipated motion<BR>of the airplane began. The airplane reaction to the counter-rotating wake vortices first<BR>tended to overbank AA 587 from a steady-state left turn. The PF attempted to counter the<BR>undesired airplane motions. At this point in the mishap sequence, the reaction of the<BR>airplane departed from the rational expectatio ns or practical experiences of either pilot.<BR>The PF¡¯s inability to precisely make an input to the rudder system to stop the oscillatory<BR>lateral motions of AA 587 forced the aircraft to yaw excessively which created<BR>aerodynamic side loads on the airplane structure. The oversensitive rudder, needing only<BR>22 pounds of force to initiate, with an extremely short stroke of only 1.2 inches of travel<BR>to command full rudder, was a mere flex of the PF¡¯s foot. The tactile feel and travel<BR>distance of the aircraft¡¯s rudder pedal was out of balance with line pilot expectations of<BR>the rudder control system.<BR>¡°Artificial trim and feel systems which produce controllers with too small a displacement<BR>and light force gradients may also lead to severe overcontrol.¡±<BR>FAA Advisory Circular 25-7A<BR>Attempts to counter or dampen this motion, an aerodynamic phenomenon known for<BR>decades and addressed by yaw damper systems, were now being exacerbated again by the<BR>system design. The A300 yaw damper actuator has a maximum deflection authority of ¡À<BR>10¡ã, with a maximum rate of ¡À 39¡ã per second. The rudder actuator has a maximum rate<BR>of 60¡ã per second, ¡À 5¡ã. Because the rudder authority is significantly higher than that of<BR>the yaw damper, it can suppress and/or override the yaw damper which negates one of the<BR>yaw damper¡¯s primary functions.<BR>19<BR>No evidence exists to suggest that the actions by the PF were anything other than a<BR>judicious response to correct an unwanted flight attitude. However, this unexpected<BR>condition degraded as the PF struggled to maintain control of the aircraft. Responding<BR>quickly to the three-dimensional motions caused by the wake of a preceding super-heavy<BR>airplane, the PF used as much authority of the FCS as his years of experience handling<BR>aircraft had taught him to use. He reacted to maintain airplane control, up to and<BR>including, the full command authority of his FCS. Commercial line pilots operate<BR>airplanes in this manner: using performance feedback to control their input rather than<BR>physically looking at a control and cognitively applying a fixed distance stroke. The<BR>pilots were unaware of the latent deficiencies in the modified rudder FCS:<BR>¡¤ The extremely light rudder pedal force<BR>¡¤ Shorter rudder pedal travel as speed increases<BR>¡¤ Excessive degrees of rudder travel per pound of force<BR>¡¤ The absence of limiting or protecting systems<BR>The manufacturer failed to warn pilots of these design characteristics and the need to<BR>avoid cyclical motion of the rudder controls. The PF was functioning within the<BR>guidelines written in various procedures, policies, and practices as he struggled to<BR>maintain airplane control. In doing so, he coupled with a hidden flaw in the rudder design<BR>and exceeded an unstated limitation.<BR>Safety Recommendation 5<BR>The NTSB should recommend installation of unfiltered, high sample<BR>rate DFDRs in all transport category aircraft. Further, the NTSB<BR>should recommend that a detailed analysis of operational data from<BR>those aircraft with reports of unexpected performance variances be<BR>made available as part of Service Difficulty Reports (SDRs) required<BR>of aircraft manufacturers.<BR>20<BR>Safety Recommendation 6<BR>Safety Recommendation 7<BR>The NTSB should recommend that the French DGAC require Airbus<BR>to develop formal training for all operators of the A310 and A300-600<BR>similar to that developed by American for its A300-600 pilots. This<BR>airplane -specific training should go beyond NTSB Safety<BR>Recommendation A-02-01 and focus on: (1) the unusually sensitive<BR>rudder; (2) the yaw damper design; (3) the limited capability of the<BR>RTLU to compensate for acceleration; and (4) the unique APC<BR>susceptibility of the A300-600 and the A310. Training should<BR>recognize that the piloting techniques used when flying other<BR>transport category airplanes may not safely transfer when<BR>transitioning from those airplane s to the A310/A300-600.<BR>The NTSB should recommend that the FAA require manufacturers of<BR>transport category airplanes either manufactured in or imported into<BR>the United States to develop FAA-approved advanced maneuver<BR>training programs, including specific documentation and guidance for<BR>classroom and simulator training specific to each airplane.<BR>21<BR>D. OVERSIGHT<BR>1. Bilateral Agreement<BR>Bilateral Aviation Safety Agreements (BASAs) with Implementation Procedures for<BR>Airworthiness (IPA) provide for airworthiness technical cooperation between the FAA<BR>and partner international civil aviation authorities. France and the United States have<BR>agreed to certification and acceptance of aircraft manufactured in either country under the<BR>terms of BASA. The first such agreement, a Bilateral Aviation Agreement (BAA), was<BR>reached in 1973 and was renewed as a BASA in May 1996. BASAs were initiated in part<BR>to enhance cooperation and increase efficiency in matters relating to civil aviation safety.<BR>One other advantage was to reduce the economic burden imposed on the aviation<BR>industry and operators by redundant technical inspections, evaluations, and testing. These<BR>agreements were not intended to diminish the level of safety for the industry. By<BR>requiring equivalent safety measures, the BASA envisioned that aviation products<BR>manufactured in either country would meet the standards of both countries.<BR>Airplanes certificated by the FAA under BASA are required to meet U.S. airworthiness<BR>standards. For transportation category aircraft, the specific standards are defined in 14<BR>Code of Federal Regulations (CFR) Part 25. The BASA process cites several CFR parts<BR>and ACs which define the equivalent requirements for both France¡¯s Direction G¨¦n¨¦rale<BR>de Aviation Civile (DGAC) and the U.S.¡¯s FAA. These CFRs and ACs are the guidance<BR>that a non-U.S. manufacturer must comply with in order to receive a U.S. Type<BR>Certificate for a specific airplane model. The data required by these CFRs and ACs<BR>should be maintained for examination during the lifecycle of a specific airplane. To date,<BR>following numerous requests, neither Airbus nor the DGAC have provided data relevant<BR>to the type certification required for the major component change from the A300B2 to the<BR>A300B4-605R. Specifically, that major component change was the shift from the VLA to<BR>the VSA in the rudder control system.<BR>FAA-AC 21-23A states:<BR>¡°a. Following the type certification of an aircraft, it frequently becomes necessary to<BR>revise data on the aircraft type design. Major changes to a type design not great enough<BR>to require an application for a new TC, sought by the TC holder, may be issued as<BR>amendments to the type certificate issued under 14 CFR 21.29, or otherwise approved by<BR>the FAA. A certification procedure similar to that described in Chapter 2 is conducted<BR>and adjusted for the magnitude and complexity of the design change. The FAA retains the<BR>right to determine whether the proposed change is substantial enough to require a new<BR>type certificate for the changed design.¡±<BR>It is unknown whether Airbus did not identify the major change in the rudder system or if<BR>the FAA determined that ¡°one rudder control unit is like another.¡±<BR>22<BR>Airbus verbally stated the change from VLA to VSA was for weight, reliability, and<BR>simplicity. This design is on all subsequent Airbus designs with one major difference:<BR>limiting systems as a result of Fly-by-Wire (FBW) technology. Airbus also admitted that<BR>their company does not use industry-recognized flight characteristics and handling<BR>quality tests such as the Cooper-Harper Method or the FAA HQRM used in U.S.<BR>certification. 4 Airbus has not produced any other test program data to justify their<BR>selection of overly-sensitive control forces other than what their test pilots thought<BR>appropriate.<BR>Airplane manufacturers hold the proprietary engineering data that allows them to<BR>determine the aerodynamic loads on aircraft experiences based on DFDR data. American<BR>Airlines does not have access to this proprietary data. As such, Airbus had a moral<BR>responsibility to inform the DGAC and the FAA that one of their aircraft experienced a<BR>limit load excursion.<BR>Public Hearing Exhibit 7Q, pages 5 and 6, revealed a total of 11 ¡°high load¡± events.<BR>These high load events all happened on the A300 or A310. Seven of the events exceeded<BR>load limit and three exceeded ultimate load. Five of the high load events involved rudder<BR>doublets. Yet, Airbus remained silent. This is peculiar since limit load, according to Part<BR>25, is ¡°never to be seen in operational use.¡± Also, Airbus was required to inform the<BR>DGAC of these unsafe conditions in accordance with the BASA.<BR>BASA and FAA AC 21-23A also specify requirements for continued airworthiness. The<BR>FAA AC 21-23A states:<BR>¡°When a safety concern arises, the FAA cooperates with its partner to determine the<BR>appropriate corrective action to be taken by operators or owners of affected U.Sregistered<BR>aircraft. The FAA expects exporting CAA¡¯s to keep it informed of<BR>corrective actions that they believe are required for the safety of U.S.-registered<BR>aircraft.¡±<BR>The IPA, in paragraph 3.3.0.0(a), states that the exporting authority is responsible ¡°¡for<BR>resolving in-service safety issues related to design or production. The exporting authority<BR>shall provide applicable information which it has found to be necessary for mandatory<BR>modifications, required limitations and/or inspections to the importing authority to ensure<BR>continued operational safety of the product, part or appliance.¡±<BR>Paragraph 3.3.0.2 of the IPA, ¡°Unsafe Conditions and Mandatory Continuing<BR>Airworthiness Actions,¡± states in paragraph 3.3.0.1(4):<BR>¡°Notifying the importing authority of the unsafe condition and the necessary corrective<BR>actions by submitting a copy of the mandatory continuing airworthiness action¡.¡±<BR>4 The Cooper-Harper Pilot Rating is a numerical Handling Quality Rating (1-10) scale that assigns an<BR>empirical value, indicating the workload task and the performance that could be obtained of a pilot.<BR>23<BR>For U.S. operators, that airworthiness action would be issued in the form of an<BR>Airworthiness Directive (AD).<BR>By its failure to act, Airbus perpetuated an unsafe condition. The manufacturer is<BR>responsible for resolving these unsafe conditions¡ªnot the airlines or the civil authorities.<BR>In response to the NTSB recommendations, American Airlines developed policy and<BR>procedural guidance to mitigate the hazard that had been identified. This action was too<BR>late for the crew and passengers of AA 587.<BR>2. Intended Rudder Usage<BR>Airbus failed to accurately inform the aviation community about the intended purpose of<BR>the rudder on their aircraft. Their testimony at the AA 587 Public Hearing conflicts with<BR>their published documents and the A300-600 FCOM. Furthermore, the FAA failed to<BR>ensure that accurate information was disseminated to the operators of the A300.<BR>In June of 1998, Airbus published a FAST Special Technical Digest. The article,<BR>¡°Aerodynamic Principles of Large-Airplane Upsets,¡± was authored by several people<BR>including Bill Wainwright, Chief Test Pilot for Airbus and Larry Rockliffe, Chief Pilot<BR>and Flight Training Director for Airbus Service Company Inc. The summary of the article<BR>states:<BR>¡°Each upset event may result from different causes, but the concepts for recovery are<BR>similar.<BR>¡¤ Use whatever authority is required of the flight controls¡± (Dempster 12).<BR>In December of 1998, Airbus published an Airplane Upset Recovery Training Aid and<BR>included a letter that stated the manual was ¡°part of an industry effort to reduce loss of<BR>control accidents and incidents¡± (Airplane Upset letter). The letter encouraged the user to<BR>¡°use this training aid to ensure your pilots participate in an effective airplane upset<BR>recovery training program.¡± In a section 2.6.2.3, titled ¡°Use of Full Control Inputs,¡± the<BR>manual reads:<BR>¡°Flight control forces become less effective when the airplane is at or near its critical<BR>angle of attack or stall. Therefore, pilots must be prepared to use full control authority,<BR>when necessary. The tendency is for pilots not to use full control authority because they<BR>rarely are required to do this. This habit must be overcome when recovering from severe<BR>upsets.¡±<BR>No limitations to rudder use or any prescribed intended rudder use were mentioned in<BR>either publication, nor were any rudder qualifications published in the FCOM.<BR>In Mr. Rockliffe¡¯s testimony at the public hearing, he states a completely different use of<BR>the rudder:<BR>24<BR>¡°I think that we need to be clear and -- well, we need to be clear that aileron and normal<BR>roll control is -- is through ailerons and roll spoilers conducted through the yoke or in<BR>the side stick, depending on the type of airplane. And rudder is not a primary flight<BR>control to induce roll under any circumstance unless normal roll control is not<BR>functional. So the consequence of that is that the ailerons, whether you're in cruise or<BR>whether you're elsewhere in the flight envelope, at a much slower or higher angle of<BR>attack, ailerons and roll spoilers would continue to be your normal, usual roll control.<BR>Rudder, on the other hand, is used to control the yaw. It's -- it's used to zero side slip. Mr.<BR>Chatrenet spoke to it, I think, quite well, that for thrust asymmetry or drag asymmetry,<BR>whatever the cause, if you have a yaw condition or a side slip condition, the rudder is<BR>dimensioned and it is there to zero it out, for the pilot to apply rudder so that you end up<BR>with this zero or reduced loading. And that's throughout the entire envelope¡± (243).<BR>This confusing and obtuse statement from the Airbus Services¡¯ Flight Training Director<BR>is an unmistakable example of the manufacturer¡¯s failure to provide clear guidance on the<BR>use of the rudder in the A300.<BR>Mr. Jacob, an Airbus test pilot, testified more directly at the public hearing. He<BR>definitively states limitations to the rudder that were unknown to the operators:<BR>¡°Yaw mode¡ªI have to go back to what the rudder is designed for on a transport category<BR>airplane. A rudder is there to steer the airplane during takeoff and landing roll, to decrab<BR>in case of a crosswind landing, and to zero out any thrust or yaw asymmetry that<BR>might occur¡± (527).<BR>Both Mr. Rockliffe and Mr. Jacob qualify the use of the rudder dramatically when their<BR>company had previously extolled the full use of all flight controls. Yet, while Mr.<BR>Rockliffe testified about rudder limitations, and Mr. Jacob specifically delineated what a<BR>rudder may be used for, Airbus did not publish these limitations until they issued an<BR>FCOM Bulletin in March 2002. For years operators had apparently been operating the<BR>A300 without proper guidance on flight control usage.<BR>The FAA issued Type Certificates for the A300 family of aircraft stating, ¡°This Data<BR>Sheet which is part of Type Certificate No. A35EU prescribes conditions and limitations<BR>under which the product for which the Type Certificate was issued meets the<BR>airworthiness requirements of the Federal Aviation Regulations.¡± It is unknown whether<BR>Airbus shared their hidden flight control limitations with the FAA when the airplanes<BR>were certified. However, it can be definitively stated that hidden flight control limitations<BR>and intentions do not meet the airworthiness requirements of the Federal Aviation<BR>Regulations (FARs).<BR>3. Maneuvering Speed<BR>For many years, a great disservice has been done to pilots by the definition of<BR>maneuvering speed¡¯ (Va). The FAA is the defining authority for aviation regulation and<BR>training in the United States. Their most basic training aid, FAA AC-61-23C: The-Pilot¡¯s<BR>25<BR>Handbook of Aeronautical Knowledge, defines ¡®maneuvering speed¡¯ erroneously. The<BR>AC states that:<BR>¡°The maximum speed at which an airplane can be safely stalled is the design<BR>maneuvering speed. The design maneuvering speed is a valuable reference point for the<BR>pilot. When operating below this speed, a damaging positive flight load should not be<BR>produced because the airplane should stall before the load becomes excessive. Any<BR>combination of flight control usage, including full deflection of the controls, or gust loads<BR>created by turbulence should not create an excessive air load if the airplane is operated<BR>below maneuvering speed.¡±<BR>Certainly this leads pilots to believe that they cannot damage the aircraft structure when<BR>maneuvering below Va. Unfortunately, we now know that this is not the case as AA 587<BR>was operating well below the published maneuvering speed.<BR>FAR 25.1583, Operating Limitations and Information, further reinforces this mistaken<BR>concept. This regulation requires that the Va limitation be defined in the Flight Manual in<BR>this manner:<BR>¡°The maneuvering speed VA and a statement that full application of rudder and aileron<BR>controls, as well as maneuvers that involve angles of attack near the stall, should be<BR>confined to speeds below this value.¡±<BR>No information contrary to this definition of Va was provided by the manufacturer. There<BR>is, therefore, no way that American Airlines or its pilots could have known that an<BR>unusual limitation existed for maneuvering the rudder of an A300 below Va.<BR>NTSB IIC Robert Benzon acknowledged this deficiency in his public hearing testimony,<BR>stating:<BR>¡°Many pilot training programs do not include the information about the structural limits<BR>for the rudder and vertical stabilizer on the airplanes pilots fly. Significantly full rudder<BR>inputs, even at speeds below maneuvering speed, may result in structural loads that<BR>exceed certification requirements¡± (31).<BR>Unfortunately, it took a tragedy for these shortcomings to come to light. Maneuvering<BR>speed is incorrectly defined by the FAA¡ªleading the aviation community to incorrect<BR>assumptions about the protections it affords.<BR>4. Aircraft Separation Standards<BR>The current three-class separation standards between aircraft are inadequate and present a<BR>hazard to all aircraft operating today. These standards were developed using dated<BR>information about aircraft vortices and have not been updated as aircraft weights<BR>approach 1 million pounds. New testing of the ¡°super-heavy¡± generation of aircraft must<BR>be accomplished to mitigate the risk which grows as aircraft weights grow.<BR>26<BR>Many argue that simulations currently exist to accurately predict the wake vortices of<BR>aircraft as they grow in size and change in their wing design. The Safety Board clearly<BR>states in the response to Safety Recommendation A-94-043 that:<BR>¡°The Safety Board has no evidence that the FAA/NASA wake vortex simulation has<BR>sufficient validity to define risk in an actual wake environment. The Safety Board does<BR>not believe that unvalidated theoretical evaluations should be used to justify<BR>decreased safety margins such as exemptions to the weight classification system.¡±<BR>The Board¡¯s genuine concerns are further delineated in Safety Recommendation A-95-<BR>056. This recommendation would require manufacturers ¡°to determine, by flight test or<BR>other suitable means, the characteristics of the airplane¡¯s wake vortex during<BR>certification.¡± This recommendation¡¯s status is ¡°Open/Unacceptable Response.¡± The<BR>FAA justifies its classification of new aircraft within the existing separation standards by<BR>citing the safety record established by those standards. This weak argument was defeated<BR>when AA 587 encountered a wake of unknown intensity.<BR>The Board concludes the open recommendation with the statement:<BR>¡°By testing all new aircraft, the FAA would know how they compare to existing aircraft<BR>and would be able to scientifically determine what adjustments to separation distances<BR>may be necessary. The Board continues to believe that the FAA needs to determine the<BR>characteristics of all transport-category airplanes¡¯ wake vortices during certification.¡±<BR>The NTSB has shown valid concerns about the wake vortices emanating from new<BR>¡°super-heavy¡± aircraft. It is time for the FAA to acknowledge those concerns and act. AA<BR>587 encountered the wake from a 747-400. The wake vortices from this late model 747<BR>have never been measured and are virtually unknown in strength. New separation<BR>standards must be established to protect all aircraft operating in the National Airspace<BR>System (NAS) from this unknown threat which will continue to propagate as aircraft<BR>continue to grow.<BR>Safety Recommendation 8<BR>The NTSB should recommend that the FAA Office of System Safety<BR>(OSS) review the findings of the AA 587 investigation to determine<BR>why these system safety failure s occurred. This effort should include a<BR>team of qualified individuals from industry and government,<BR>including representatives of the French DGAC and FAA certification<BR>officials. The stated goal of the review should be to identify and<BR>understand the system safety failures so as to prevent, if possible, the<BR>re-occurrence of a tragedy like AA 587.<BR>27<BR>Safety Recommendation 9<BR>Safety Recommendation 10<BR>The NTSB should recommend that the FAA more specifically define<BR>the definition of ¡®maneuvering speed,¡¯ as it pertains to all categories of<BR>aircraft and, in so doing, clearly outline the differences of assumptions<BR>as they apply to the three primary flight control surfaces. All<BR>manufacturers¡¯ flight manuals and other associated documents for<BR>airplanes certified in or imported into the United States accordingly<BR>should also be revised to reflect the proper meaning and use of the<BR>term ¡®maneuvering speed.¡¯<BR>The NTSB should recommend a much more aggressive compliance of<BR>system safety practices as outlined in the FAA System Safety<BR>Handbook. The Assistant Administrator of System Safety (ASY) and<BR>office staff should be empowered to act as an independent technical<BR>authority to ensure system safety practices are used through the life<BR>cycle of the various systems receiving FAA approval or certification.<BR>The NTSB should revise Safety Recommendation A-96-64 to the FAA,<BR>re-emphasizing the pertinence of the recommendation to aviation<BR>safety. This recommendation resulted from the 1994 Roselawn,<BR>Indiana, accident and now directly applies to this accident. The<BR>recommendation states, ¡°Establish policies and procedures to ensure<BR>that all pertinent information is received, including the<BR>manufacturer¡¯s analysis of incidents, accidents or other airworthiness<BR>issues, from the exporting country¡¯s airworthiness authority so that<BR>the FAA can monitor and ensure the continued airworthiness of<BR>airplanes certified under the Bilateral Airworthiness Agreement.¡±<BR>28<BR>Safety Recommendation 11<BR>The NTSB should recommend the various governmental agencies<BR>responsible for the bilateral agreements which allow foreign<BR>manufacturers to qualify for U.S. certification form a team to review<BR>the aircraft certification process. Emphasis should be placed on<BR>ensuring that the standards of 14 CFR Part 25 are met fully prior to<BR>certification consideration.<BR>29<BR>4. SUMMATION<BR>Airbus designed and produced the A300B2-1A in 1971. Eleven years later, Airbus<BR>redesigned the rudder control unit in a new model called the A300B4-600. This unique<BR>design dramatically changed the handling characteristics of the airplane. Airbus did not<BR>rely on a verifiable test process to identify any undesirable flight control characteristics<BR>when modifying the rudder system. After ten years of in-service high- load events, Airbus<BR>had knowledge that there may be a flaw in the A300. They then had a chance to fix the<BR>flaw before it resulted in a catastrophic event.<BR>Contrary to the BASA, Airbus chose not to inform the aviation industry of this flaw. In<BR>fact, Airbus published guidance encouraging use of ¡°whatever authority is required of the<BR>flight controls¡± (Dempster 12). They withheld information from the aviation community<BR>when, after participating in a full NTSB investigatio n, they failed to inform American<BR>Airlines and the NTSB that airplane N90070 had exceeded ultimate load in a 1997 event.<BR>That airplane continued to fly with a damaged tail until it was replaced in late 2002.<BR>Airbus had five years in which to notify the NTSB, FAA, DGAC, or American Airlines<BR>of the flaw but chose not to inform anyone until this accident forced the disclosure.<BR>The pilots operating the accident airplane were highly-skilled, fully-qualified, proficient<BR>aviators who were never informed of the unusual limitations of their airplane. They were<BR>trained in an FAA-approved training program though the FAA misinformed them that<BR>they could use full authority of the flight controls below maneuvering speed (Va). The<BR>pilots took off with the FAA-established minimum wake turbulence separation distances.<BR>Unbeknownst to them, those distances were based upon conjecture and outdated data.<BR>When the pilots encountered a wake vortex of unknown strength, they applied flight<BR>controls which were appropriate for their situation. While they did not exceed any<BR>limitations, violate any procedures, or perform unusually in any manner, their aircraft<BR>suffered catastrophic structural failure.<BR>30<BR>WORKS CITED<BR>Airplane Upset Recovery Training Aid. Monteil, Christian. Letter. France. Airbus<BR>Industrie, 1998.<BR>Dempster, Denis, and Leslie Nichols, eds. Aerodynamic Principles of Large-Airplane<BR>Upsets. Spec. issue of Airbus Technical Digest (June 1998).<BR>National Research Council. Aviation Safety and Pilot Control: Understanding and<BR>Preventing Unfavorable Pilot-Vehicle Interactions. Washington. National<BR>Academy Press, 1997.<BR>United States. National Transportation Safety Board. Official Docket 32764 on American<BR>Airlines Flight 587 Accident NTSB Identification: DCA02MA001. Washington.<BR>GPO, 2002.<BR>---. ---. Public Hearing on American Airlines Flight 587 Accident NTSB Identification:<BR>DCA02MA001.Washington. GPO, 2003.<BR>---. Federal Aviation Administration. System Safety Handbook. Washington. GPO, 2000.<BR>---. National Archives and Records Administration. Code of Federal Regulations.<BR>Washington. GPO, 2004.<BR>Wake Turbulence Training Aid. Washington. GPO, 1995.<BR>31<BR>LIST OF SAFETY RECOMMENDATIONS<BR>1. The NTSB should recommend that the FAA require evaluation of all aircraft<BR>operating under U.S. type certification by FAA Handling Qualities Rating Method<BR>(HQRM) or equivalent.<BR>2. The NTSB should recommend that the FAA and French DGAC form an Engineering<BR>Evaluation Team to work with Airbus and the operators of the A310/A300-600 to<BR>determine whether pilot training alone is an adequate remedy to the undesirable Flight<BR>Control System (FCS) characteristics of these aircraft, or if an FCS modification is<BR>also required.<BR>3. The NTSB should recommend that the FAA reexamine the validity of current ATC<BR>wake turbulence separation standards. Focus of the review should be on the standards<BR>for the wide range of ¡°heavy¡± airplanes currently in operation, and for larger aircraft,<BR>such as the Airbus A380 coming in the near future. This examination should include<BR>new technology and should study proposals for improving controller training and<BR>understanding of wake vortices, including variables such as relative wind,<BR>atmospheric stability, and ATC vectoring.<BR>4. The NTSB should recommend that the FAA comply with open Safety<BR>Recommendation A-94-056 which states, ¡°Require manufacturers of turbojet,<BR>transport category airplanes to determine, by flight test or other suitable means, the<BR>characteristics of the airplanes¡¯ wake vortices during certification environment.¡±<BR>5. The NTSB should recommend installation of unfiltered, high sample rate DFDRs in<BR>all transport category aircraft. Further, the NTSB should recommend that a detailed<BR>analysis of operational data from those aircraft with reports of unexpected<BR>performance variances be made available as part of Service Difficulty Reports<BR>(SDRs) required of aircraft manufacturers.<BR>6. The NTSB should recommend that the French DGAC require Airbus to develop<BR>formal training for all operators of the A310 and A300-600 similar to that developed<BR>by American for its A300-600 pilots. This airplane-specific training should go beyond<BR>NTSB Safety Recommendation A-02-01 and focus on: (1) the unusually sensitive<BR>rudder; (2) the yaw damper design; (3) the limited capability of the RTLU to<BR>compensate for acceleration; and (4) the unique APC susceptibility of the A300-600<BR>and the A310. Training should recognize that the piloting techniques used when<BR>flying other transport category airplanes may not safely transfer when transitioning<BR>from those airplanes to the A310/A300-600.<BR>7. The NTSB should recommend that the FAA require manufacturers of transport<BR>category airplanes either manufactured in or imported into the United States develop<BR>FAA-approved advanced maneuver training programs, including specific<BR>32<BR>documentation and guidance for classroom and simulator training specific to each<BR>airplane.<BR>8. The NTSB should recommend that the FAA Office of System Safety (OSS) review<BR>the findings of the AA 587 investigation to determine why these system safety<BR>failures occurred. This effort should include a team of qualified individuals from<BR>industry and government, including representatives of the French DGAC and FAA<BR>certification officials. The stated goal of the review should be to identify and<BR>understand the system safety failures so as to prevent, if possible, the re-occurrence of<BR>a tragedy like AA 587.<BR>9. The NTSB should recommend that the FAA more specifically define the definition of<BR>¡®maneuvering speed,¡¯ as it pertains to all categories of aircraft and, in so doing,<BR>clearly outline the differences of assumptions as they apply to the three primary flight<BR>control surfaces. All manufacturers¡¯ flight manuals and other associated documents<BR>for airplanes certified in or imported into the United States accordingly should also be<BR>revised to reflect the proper meaning and use of the term ¡®maneuvering speed.¡¯<BR>10. The NTSB should recommend a much more aggressive compliance of system safety<BR>practices as outlined in the FAA System Safety Handbook. The Assistant<BR>Administrator of System Safety (ASY) and office staff should be empowered to act as<BR>an independent technical authority to ensure system safety practices are used through<BR>the life cycle of the various systems receiving FAA approval or certification. The<BR>NTSB should revise Safety Recommendation A-96-64 to the FAA, re-emphasizing<BR>the pertinence of the recommendation to aviation safety. This recommendation<BR>resulted from the 1994 Roselawn, Indiana, accident and now directly applies to this<BR>accident. The recommendation states, ¡°Establish policies and procedures to ensure<BR>that all pertinent information is received, including the manufacturer¡¯s analysis of<BR>incidents, accidents or other airworthiness issues, from the exporting country¡¯s<BR>airworthiness authority so that the FAA can monitor and ensure the continued<BR>airworthiness of airplanes certified under the Bilateral Airworthiness Agreement.¡±<BR>11. The NTSB should recommend the various governmental agencies responsible for the<BR>bilateral agreements which allow foreign manufacturers to qualify for U.S.<BR>certification form a team to review the aircraft certification process. Emphasis should<BR>be placed on ensuring that the standards of 14 CFR Part 25 are met fully prior to<BR>certification consideration.
Ò³:
[1]