|

SAFO: Embraer ERJ-190 Series Thrust Reverser Cowling Safety

Similar Posts

  • |

    Australia: flight safety checks

    Victorian aerodrome flight safety checks

    Special flight safety checks are being carried out at 18 Victorian aerodromes next week.

    There will be a series of low-level flights at each aerodrome to make sure flight paths continue to operate safely.

    A twin-engine Cessna Conquest aircraft will be used to conduct the safety checks within an area up to 35 kilometres from each aerodrome.

    The two pilots flying the aircraft will ensure navigation aids are operational and not suffering interference, as well as looking for any new obstacles that could be a danger to aviation safety.

    The Civil Aviation Safety Authority requires these checks to be carried out every three years to maintain a high level of air safety at aerodromes.

    Low-level flying is an essential part of the safety exercise, with the aircraft down as low as several hundred feet at times.

    Local residents may notice an uncommon flying pattern, but this is to make sure obstacles are accurately marked on charts and no new obstacles exist. Obstacles can be towers, trees, masts or buildings that can be a danger to aircraft.

    The checks are scheduled to be carried out between Saturday 11 December and Sunday 19 December 2010.

    If poor weather or other factors do not allow the safety checks to go ahead on the planned days they will be carried out as soon as possible.

    CASA has contracted the operation of the special check flights out to Radiola Aerospace Pty Ltd – a company with wide international expertise in these specialist operations.

    Naracoorte aerodrome flight safety checks

    Special flight safety checks are being carried out at Naracoorte aerodrome next week.

    There will be a series of low-level flights to make sure flight paths at the aerodrome continue to operate safely.

    A twin-engine Cessna Conquest aircraft will be used to conduct the safety checks within an area up to 35 kilometres from the aerodrome.

    The two pilots flying the aircraft will ensure navigation aids are operational and not suffering interference, as well as looking for any new obstacles that could be a danger to aviation safety.

    The Civil Aviation Safety Authority requires these checks to be carried out every three years to maintain a high level of air safety at Naracoorte aerodrome.

    Low-level flying is an essential part of the safety exercise, with aircraft down as low as several hundred feet at times.

    Local residents may notice an uncommon flying pattern, but this is to make sure obstacles are accurately marked on charts and no new obstacles exist. Obstacles can be towers, trees, masts or buildings that can be a danger to aircraft.

    The checks are scheduled to be carried out in the week starting Sunday 12 December 2010.

    If poor weather or other factors do not allow the safety checks to go ahead on the planned days they will be carried out as soon as possible.

    CASA has contracted the operation of the special check flights out to Radiola Aerospace Pty Ltd – a company with wide international expertise in these specialist operations.

    Mount Gambier aerodrome flight safety checks

    Special flight safety checks are being carried out at Mount Gambier aerodrome next week.

    There will be a series of low-level flights to make sure flight paths at the aerodrome continue to operate safely.

    A twin-engine Cessna Conquest aircraft will be used to conduct the safety checks within an area up to 35 kilometres from the aerodrome.

    The two pilots flying the aircraft will ensure navigation aids are operational and not suffering interference, as well as looking for any new obstacles that could be a danger to aviation safety.

    The Civil Aviation Safety Authority requires these checks to be carried out every three years to maintain a high level of air safety at Mount Gambier aerodrome.

    Low-level flying is an essential part of the safety exercise, with aircraft down as low as several hundred feet at times.

    Local residents may notice an uncommon flying pattern, but this is to make sure obstacles are accurately marked on charts and no new obstacles exist. Obstacles can be towers, trees, masts or buildings that can be a danger to aircraft.

    The checks are scheduled to be carried out in the week starting Sunday 12 December 2010.

    If poor weather or other factors do not allow the safety checks to go ahead on the planned days they will be carried out as soon as possible.

    CASA has contracted the operation of the special check flights out to Radiola Aerospace Pty Ltd – a company with wide international expertise in these specialist operations.

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

    FAA and Port Authority of New York and New Jersey Reach Agreement on Airport Safety Violations

    WASHINGTON – The Federal Aviation Administration (FAA) and the Port Authority of New York and New Jersey (PANYNJ) have reached a settlement agreement about aircraft rescue and firefighting (ARFF) violations from December 2010 to June 2012 at four New York area airports owned and operated by the PANYNJ — John F. Kennedy, Teterboro, LaGuardia, and Newark Liberty International.

    “We expect all airports to comply with our safety regulations and to correct any deficiencies immediately,” said U.S. Transportation Secretary Ray LaHood. “These violations were egregious, and they will not be tolerated.”

    Under the agreement, the PANYNJ agrees to pay a $3.5 million fine within 30 days. If there is a violation of the settlement agreement, the FAA will impose an additional fine of $1.5 million and will assess an additional $27,500 daily for each violation. In addition to the fine, the PANYNJ has agreed to take the following actions, with FAA approval, to address the underlying problems that led to systemic noncompliance with ARFF requirements at the four airports:

    • The Port Authority will create a dedicated ARFF force to carry out airport-related ARFF functions with no collateral police officer duties.
    • The staff will report directly to the Department of Aviation and be operational no later than March 31, 2014.
    • The Port Authority will hire an ARFF fire chief and facility captains as soon as possible, but no later than March 31, 2014.
    • The Port Authority will submit a curriculum for training to the FAA on or before December 31, 2013, which includes at least 75 hours of initial ARFF training and 40 hours of annual recurrent firefighting training in addition to Part 139 training, pertaining to an airport’s operational and safety standards and providing for such things as firefighting and rescue.
    • The ARFF personnel will work a 12-hour shift.
    • The Port Authority will amend the airport certification manuals for the four airports to include: an organizational chart; a process to maintain ARFF training records; and a description of ARFF operations, including shift assignments, personnel training records management, and Department of Aviation oversight.
    • The Port Authority will conduct monthly internal audits of ARFF training and shift assignments and annual external audits to ensure that all ARFF personnel assigned to a shift are trained.

    “We expect the Port Authority to have trained safety personnel to ensure the safety of the travelling public and airport personnel, just like we have at all airports in the United States,” said FAA Administrator Michael P. Huerta.

    The FAA became aware of ARFF violations as a result of an annual airport certification safety inspection of JFK in December 2011. The FAA also discovered similar violations at Teterboro, which prompted a full review of training at LaGuardia, Newark Liberty International, and Stewart International Airports. The review of ARFF training revealed violations at LaGuardia and Newark, with no violations at Stewart.

    The FAA believes the settlement agreement provides the best long-term solution to ensure ARFF compliance, given the systemic nature of the PANYNJ airport problems.

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

    Dassault Reaches Milestone With 100th Falcon 7X Delivery

    LITTLE ROCK, Arkansas, — Dassault yesterday delivered the 100th Falcon 7X during a ceremony at its completion center in Little Rock, Arkansas. The aircraft was delivered to a Brazilian financial services company.

    “We promised to design and build the most technically advanced and best flying aircraft in the industry and we’ve already achieved that 100 times,” said John Rosanvallon, President and CEO of Dassault Falcon. “During that time, feedback from pilots and passengers alike has been very positive. Pilots said they appreciate, in particular, the digital flight control system which makes the Falcon 7X so responsive and easy to maneuver. The superb cabin environment is praised by passengers for its smooth flying comfort and quietness.

    To date, the 5,950 nm Falcon 7X fleet has accumulated more than 57,000 flight hours, operating in over 25 countries with orders coming from more than 40 countries. The fleet leader has logged more than 3,000 flight hours since its delivery mid 2007. “The high usage rate (higher than other Falcons) demonstrates that the Falcon 7X is a very active part of many flight departments,” said Jacques Chauvet, Senior Vice President of Customer Service. “Its versatility helps account for its popularity and having gathered over 200 orders”.

    The Falcon 7X has received type certification from 16 aviation authorities and is the only long range business jet with EASA and FAA approvals to use the challenging London City airport.

    7X Background
    The Falcon 7X has the longest range of any Falcon business jet and is the most fuel efficient jet in its class. Since its entry into service in 2007, the 7X cabin has set a new standard for business jets. The cabin has 28 windows which are 10% bigger than previous Falcons. It also features a low in flight cabin altitude of 6,000 feet, even while cruising at an altitude of 51,000 ft, and an advanced temperature control system that maintains the environment to within one degree throughout the entire cabin. Internal sound level has been reduced to 52 dB which is the result of breakthroughs in design, materials and cushioned engine mounts.

    First announced at the Paris Air Show in 2001, the Falcon 7X is the first business jet with a digital flight control system and was simultaneously certified by both the EASA and the FAA on April 27, 2007. It features the award-winning EASy Flight Deck and is powered by three Pratt & Whitney Canada PW307A engines. Its 5,950 nm range (eight passengers, M.80 with NBAA IFR reserves) can comfortably connect 95% of the commonly used business aviation city pairs.

    About Dassault Falcon
    Dassault Falcon is responsible for selling and supporting Falcon business jets throughout the world. It is part of Dassault Aviation, a leading aerospace company with a presence in over 70 countries across five continents. Dassault Aviation produces the Rafale fighter jet as well as the complete line of Falcon business jets. The company has assembly and production plants in both France and the United States and service facilities on multiple continents. It employs a total workforce of over 12,000. Since the rollout of the first Falcon 20 in 1963, 2,000 Falcon jets have been delivered to 67 countries worldwide. The family of Falcon jets currently in production includes the tri-jets-the Falcon 900DX, 900LX, and the 7X-as well as the twin-engine 2000LX.

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

    Statement of Henry Krakowski, Chief Operating Officer, Air Traffic Organization

    Before the Senate Committee on Commerce, Science, & Transportation, Subcommittee on Aviation Operations, Safety, & Security on Field Hearing on the Integration of Unmanned Aircraft Systems (UASs) Into the National Airspace System (NAS): Fulfilling Imminent Operational and Training Requirements


    Chairman Dorgan, Senator Conrad, Congressman Pomeroy:

    Thank you for inviting the Federal Aviation Administration (FAA) to this hearing. Accompanying me today is John Allen, Director of the Flight Standards Service in the Office of Aviation Safety at the FAA. Together, we have distinct yet related duties in carrying out the FAA’s mission to ensure the safety and efficiency of the National Airspace System (NAS). Mr. Allen’s organization is charged with setting and enforcing the safety standards for aircraft operators and airmen. My role as the head of the Air Traffic Organization is to oversee the nation’s air traffic control system, to move flights safely and efficiently, while also overseeing the capital programs and the modernization of the system.

    As the most complex airspace in the world, the NAS encompasses an average of over 100,000 aviation operations per day, including commercial air traffic, cargo operations, business jets, etc. Additionally, there are over 238,000 general aviation aircraft that represent a wide range of sophistication and capabilities that may enter the system at any time. There are over 500 air traffic control facilities, more than 12,000 air navigation facilities, and over 19,000 airports, not to mention the thousands of other communications, surveillance, weather reporting, and other aviation support facilities. With this volume of traffic and high degree of complexity, the FAA maintains an extremely safe airspace through diligent oversight and the strong commitment to our safety mission.

    With regard to unmanned aircraft systems (UAS), the FAA sets the parameters for where a UAS may be operated and how those operations may be conducted safely in the NAS. Our main focus when evaluating UAS operations in the NAS is to avoid any situations in which a UAS would endanger other users of the NAS or compromise the safety of persons or property on the ground. The FAA acknowledges the great potential of UASs in national defense and homeland security, and as such, we strive to accommodate the needs of the Department of Defense (DoD) and Department of Homeland Security (DHS) for UAS operations, always with safety as our top priority.

    When new aviation technology becomes available, we must determine if the technology itself is safe and that it can be operated safely. Whether the technology is to be used by pilots, operators or air traffic controllers, we determine the risks associated with putting that technology into the NAS. Once the known risks are mitigated, we move forward with integration in stages, assessing safety at each incremental step along the way. Unforeseen developments, changing needs, technological improvements, and human factors all play a role in allowing operations within the civil airspace system.

    The FAA is using this same methodology to manage the integration of the new UAS technology into the NAS. While UASs offer a promising new technology, the limited safety and operational data available to date does not yet support expedited or full integration into the NAS. Because current available data is insufficient to allow unfettered integration of UASs into the NAS—where the public travels every day—the FAA must continue to move forward deliberately and cautiously, in accordance with our safety mandate.

    Because the airspace is a finite resource, and in order for us to carry out our safety mission, the FAA has developed a few avenues through which UAS operators may gain access to the NAS. First, the FAA has a Certificate of Waiver or Authorization (COA) process. This is the avenue by which public users (government agencies, including Federal, state, and local law enforcement, as well as state universities) that wish to fly a UAS can gain access to the NAS, provided that the risks of flying the unmanned aircraft in the civil airspace can be appropriately mitigated. Risk mitigations required to grant a COA frequently include special provisions unique to the requested type of operation. For example, the applicant may be restricted to a defined airspace and/or operating during certain times of the day. The UAS may be required to have a transponder if it is to be flown in a certain type of airspace. A ground observer or accompanying “chase” aircraft may be required to act as the “eyes” of the UAS. Other safety enhancements may be required, depending on the nature of the proposed operation.

    The FAA may also set aside airspace for an operator’s exclusive use to segregate the dangerous activity or protect something on the ground, when needed. Some of these exclusive use areas are known as Restricted, Warning or Prohibited Areas. The DoD conducts most of its training in such airspace. In order to set aside Restricted or Prohibited Area airspace, the FAA would need to undertake rulemaking to define the parameters of that airspace. This is typically a time-consuming process that would also include environmental reviews that could impact the proposed airspace.

    Civil UAS operators must apply for a Special Airworthiness Certificate – Experimental Category to gain access to the NAS. This avenue allows the civil users to operate UAS for research and development, demonstrations, and crew training. The Special Airworthiness Certificate – Experimental Category does not permit carriage of persons or property for compensation or hire. Thus, commercial UAS operations in the U.S. are not permitted at this time.

    We are working with our partners in government and the private sector to advance the development of UAS and the ultimate integration into the NAS. First, in accordance with Section 1036 of the Duncan Hunter National Defense Authorization Act (NDAA) for Fiscal Year 2009, Public Law 110-417, the DoD and FAA have formed an Executive Committee (ExCom) to focus on conflict resolution and identification of the range of policy, technical, and procedural concerns arising from the integration of UASs into the NAS. Other ExCom members include DHS and the National Aeronautics and Space Administration (NASA) to capture more broadly other Federal agency efforts and equities in the ExCom. The mission of this multi-agency UAS ExCom is to increase, and ultimately enable routine, access of Federal public UAS operations in the NAS to support the operational, training, developmental, and research requirements of the member agencies. All of these partner agencies are working to ensure that each department and agency is putting the proper focus and resources to continue to lead the world in the integration of UAS.

    The ExCom’s work has also facilitated the work of the Red River Task Force (RRTF), the interagency working group that was established to work on issues regarding the basing of UAS at Grand Forks Air Force Base (RDR). With the ExCom’s work and the RRTF’s work running in parallel, the FAA is able to support more easily and fully the DoD’s needs at RDR. One of the RRTF’s first tasks was to establish two separate tracks for DoD’s goals at RDR: one would be an aeronautical proposal that would involve establishment of a new restricted area(s), while the other would be a broader menu of operational options that could be used either as a stand-alone solution or as a layered approach for the operation of UASs at RDR. We have done this in numerous places and continue to streamline the approval process.

    Currently, the FAA is working with the DoD to determine and evaluate the scope and details of its operational needs at RDR. In addition, the RRTF has examined 18 option sets that can provide short, mid- and long-term solutions to UAS NAS access at RDR. The FAA continues to be committed to working with the DoD on matters relating to UAS operations at RDR in a manner consistent with our safety mission.

    Unmanned aircraft systems are a promising new technology, but one that was originally and primarily designed for military purposes. Although the technology incorporated into UASs has advanced, their safety record warrants caution. As we attempt to integrate these aircraft into the NAS, we will continue to look at any risks that UASs pose to the traveling public as well as the risk to persons or property on the ground. As the agency charged with overseeing the safety of our skies, the FAA seeks to balance our partner agencies’ security, defense, and other public needs with the safety of the NAS. We look forward to continuing our work with our partners and the Congress to do just that.

    Chairman Dorgan, Senator Conrad, Congressman Pomeroy, this concludes our prepared remarks. We would be pleased to answer any questions you might have.

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

    Air Australia Passengers Stranded

    Brisbane’s budget airline Air Australia just announced that flights are canceled and there will be no more new bookings because it can’t pay its bills. The company is now in Australia’s version of bankruptcy protection (voluntary administration). A portion of 4000 passengers were left stranded in places like Phuket and Honolulu. Jetstar and Qantas are considering selling return seats to passengers. Passengers will likely be able to recoup their Air Australia purchase price through their credit card company. The airline has only been in operation for two months. 300 jobs were just lost if the business is unable to recover.

    In George’s Point of View


    Good for Air Australia. It’s the responsible thing to do.

    Frankly, it is better for the operators who are running short of cash to get out fast. Maybe this bankruptcy will uncover some well-heeled investors. If not, getting out fast is the right thing to do. A shortage of cash can result in scrimping where there is no room for cost-cutting, like maintenance, etc. Cash shortages can cause budget cuts that can too easily result in loss of life.

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

    NTSB Says Aggressive Test Flight Schedule, Overlooked Errors Led to Stall and Crash

    Oct. 10, 2012
    The National Transportation Safety Board determined today that the probable cause of the crash of an experimental Gulfstream G650 on April 2, 2011, in Roswell, N.M., was the result of an aerodynamic stall and uncommanded roll during a planned takeoff test flight conducted with only one of the airplane’s two engines operating.
    The Board found that the crash was the result of Gulfstream’s failure to properly develop and validate takeoff speeds and recognize and correct errors in the takeoff safety speed that manifested during previous G650 flight tests; the flight test team’s persistent and aggressive attempts to achieve a takeoff speed that was erroneously low; and Gulfstream’s inadequate investigation of uncommanded roll events that occurred during previous flight tests, which should have revealed incorrect assumptions about the airplane’s stall angle of attack in ground effect.

    Contributing to the accident, the NTSB found, was Gulfstream’s pursuit of an aggressive flight test schedule without ensuring that the roles and responsibilities of team members were appropriately defined, sufficient technical planning and oversight was performed, and that hazards had been fully identified and addressed with appropriate, effective risk controls.

    “In this investigation we saw an aggressive test flight schedule and pressure to get the aircraft certified,” said NTSB Chairman Deborah A.P. Hersman. “Deadlines are essential motivators, but safety must always trump schedule.”

    At approximately 9:34 a.m. Mountain Time, during takeoff on the accident flight, the G-650 experienced a right wing stall, causing the airplane to roll to the right with the right wingtip contacting the runway. The airplane then departed the runway, impacting a concrete structure and an airport weather station, resulting in extensive structural damage and a post-crash fire. The two pilots and two flight engineers on board were fatally injured and the airplane was substantially damaged.

    The NTSB made recommendations to the Flight Test Safety Committee and the Federal Aviation Administration to improve flight test operating policies and encourage manufacturers to follow best practices and to coordinate high-risk flight tests. And the Board recommended that Gulfstream Aerospace Corporation commission an independent safety audit to review the company’s progress in implementing a flight test safety management system and provide information about the lessons learned from its implementation to interested manufacturers, flight test safety groups and other appropriate parties.

    “In all areas of aircraft manufacturing, and particularly in flight testing, where the risks are greater, leadership must require processes that are complete, clear and include well-defined criteria,” said Chairman Deborah A.P. Hersman. “This crash was as much an absence of leadership as it was of lift.”

    The preliminary synopsis of the report is below:

    NATIONAL TRANSPORTATION SAFETY BOARD
    Public Meeting of October 10, 2012
    (Information subject to editing)
    Aircraft Accident Report:
    Crash During Experimental Test Flight
    Gulfstream Aerospace Corporation GVI (G650), N652GD
    Roswell, New Mexico
    April 2, 2011

    NTSB/AAR-12/02

    This is a synopsis from the National Transportation Safety Board’s report and does not include the NTSB’s rationale for the conclusions, probable cause, and safety recommendations. Safety Board staff is currently making final revisions to the report from which the attached conclusions and safety recommendations have been extracted. The final report and pertinent safety recommendation letters will be distributed to recommendation recipients as soon as possible. The attached information is subject to further review and editing.

    Executive Summary

    On April 2, 2011, about 0934 mountain daylight time, an experimental Gulfstream Aerospace Corporation GVI (G650), N652GD, crashed during takeoff from runway 21 at Roswell International Air Center Airport, Roswell, New Mexico. The two pilots and the two flight test engineers were fatally injured, and the airplane was substantially damaged by impact forces and a postcrash fire. The airplane was registered to and operated by Gulfstream as part of its G650 flight test program. The flight was conducted under the provisions of 14 Code of Federal Regulations Part 91. Visual meteorological conditions prevailed at the time of the accident.

    The accident occurred during a planned one-engine-inoperative (OEI) takeoff when a stall on the right outboard wing produced a rolling moment that the flight crew was not able to control, which led to the right wingtip contacting the runway and the airplane departing the runway from the right side. After departing the runway, the airplane impacted a concrete structure and an airport weather station, resulting in extensive structural damage and a postcrash fire that completely consumed the fuselage and cabin interior.

    The National Transportation Safety Board’s (NTSB) investigation of this accident found that the airplane stalled while lifting off the ground. As a result, the NTSB examined the role of “ground effect” on the airplane’s performance. Ground effect refers to changes in the airflow over the airplane resulting from the proximity of the airplane to the ground. Ground effect results in increased lift and reduced drag at a given angle of attack (AOA) as well as a reduction in the stall AOA. In preparing for the G650 field performance flight tests, Gulfstream considered ground effect when predicting the airplane’s takeoff performance capability but overestimated the in ground effect stall AOA. Consequently, the airplane’s AOA threshold for stick shaker (stall warning) activation and the corresponding pitch limit indicator (on the primary flight display) were set too high, and the flight crew received no tactile or visual warning before the actual stall occurred.

    The accident flight was the third time that a right outboard wing stall occurred during G650 flight testing. Gulfstream did not determine (until after the accident) that the cause of two previous uncommanded roll events was a stall of the right outboard wing at a lower-than-expected AOA. (Similar to the accident circumstances, the two previous events occurred during liftoff; however, the right wingtip did not contact the runway during either of these events.) If Gulfstream had performed an in-depth aerodynamic analysis of these events shortly after they occurred, the company could have recognized before the accident that the actual in-ground-effect stall AOA was lower than predicted.

    During field performance testing before the accident, the G650 consistently exceeded target takeoff safety speeds (V2). V2 is the speed that an airplane attains at or before a height above the ground of 35 feet with one engine inoperative. Gulfstream needed to resolve these V2 exceedances because achieving the planned V2 speeds was necessary to maintain the airplane’s 6,000-foot takeoff performance guarantee (at standard sea level conditions). If the G650 did not meet this takeoff performance guarantee, then the airplane could only operate on longer runways. However, a key assumption that Gulfstream used to develop takeoff speeds was flawed and resulted in V2 speeds that were too low and takeoff distances that were longer than anticipated.

    Rather than determining the root cause for the V2 exceedance problem, Gulfstream attempted to reduce the V2 speeds and the takeoff distances by modifying the piloting technique used to rotate the airplane for takeoff. Further, Gulfstream did not validate the speeds using a simulation or physics-based dynamic analysis before or during field performance testing. If the company had done so, then it could have recognized that the target V2 speeds could not be achieved even with the modified piloting technique. In addition, the difficulties in achieving the target V2 speeds were exacerbated in late March 2011 when the company reduced the target pitch angle for some takeoff tests without an accompanying increase in the takeoff speeds.

    Gulfstream maintained an aggressive schedule for the G650 flight test program so that the company could obtain Federal Aviation Administration (FAA) type certification by the third quarter of 2011. The schedule pressure, combined with inadequately developed organizational processes for technical oversight and safety management, led to a strong focus on keeping the program moving and a reluctance to challenge key assumptions and highlight anomalous airplane behavior during tests that could slow the pace of the program. These factors likely contributed to key errors, including the development of unachievable takeoff speeds, as well as the superficial review of the two previous uncommanded roll events, which allowed the company’s overestimation of the in-ground-effect stall AOA to remain undetected.

    After the accident, Gulfstream suspended field performance testing through December 2011 while the company examined the circumstances of the accident. In March 2012, Gulfstream reported that company field performance testing had been repeated and completed successfully. In June 2012, the company reported that FAA certification field performance testing had been successfully completed. Gulfstream obtained FAA type certification for the G650 on September 7, 2012.

    Conclusions

    1. The test team’s focus on achieving the takeoff safety speeds for the flight tests and the lack of guidance specifying precisely when the pitch angle target and pitch limit applied during the test maneuver contributed to the team’s decision to exceed the initial pitch target and the pitch angle at which a takeoff test was to be discontinued.

    2. A stall on the right outboard wing produced a right rolling moment that the flight crew was not able to control, which led to the right wingtip contacting the runway and the airplane departing the runway from the right side.

    3. Given the airplane’s low altitude, the time-critical nature of the situation, and the ambiguous stall cues presented in the cockpit, the flight crew’s response to the stall event was understandable.

    4. The impact forces from the accident were survivable, but the cabin environment deteriorated quickly and became unsurvivable because of the large amount of fuel, fuel vapor, smoke, and fire entering the cabin through the breaches in the fuselage.

    5. The airplane stalled at an angle of attack (AOA) that was below the in ground effect stall AOA predicted by Gulfstream and the AOA threshold for the activation of the stick shaker stall warning.

    6. If Gulfstream had performed an in-depth aerodynamic analysis of the cause of two previous G650 uncommanded roll events, similar to the analyses performed for roll events during previous company airplane programs, the company could have recognized that the actual in-ground-effect stall angle of attack for the accident flight test was significantly lower than the company predicted.

    7. Gulfstream’s decision to use a takeoff speed development method from a previous airplane program was inappropriate and resulted in target takeoff safety speed values that were too low to be achieved.

    8. By not performing a rigorous analysis of the root cause for the ongoing difficulties in achieving the G650 takeoff safety speeds (V2), Gulfstream missed an opportunity to recognize and correct the low target V2 speeds.

    9. Before the accident flight, Gulfstream had sufficient information from previous flight tests to determine that the target takeoff safety speeds (V2) could not be achieved with a certifiable takeoff rotation technique and that the V2 speeds needed to be increased.

    10. Deficiencies in Gulfstream’s technical planning and oversight contributed to the incorrect speeds used on the day of the accident.

    11. Because Gulfstream did not clearly define the roles and responsibilities for on site test team members, critical safety-related parameters were not being adequately monitored and test results were not being sufficiently examined during flight testing on the day of the accident.

    12. Gulfstream’s focus on meeting the G650’s planned certification date caused schedule related pressure that was not adequately counterbalanced by robust organizational processes to prevent, identify, and correct the company’s key engineering and oversight errors.

    13. Gulfstream’s flight test safety program at the time of the accident was deficient because risk controls were insufficient and safety assurance activities were lacking.

    14. The inherent risks associated with field performance flight testing, and minimum unstick speed testing in particular, could be reduced if airplane manufacturers considered the potential for a lower maximum lift coefficient in ground effect when estimating the stall angle of attack in ground effect.

    15. Effective flight test standard operating policies and procedures that are fully implemented by manufacturers would help reduce the inherent risks associated with flight testing.

    16. Flight test safety management system guidance specifically tailored to the needs of manufacturers would help promote the development of effective flight test safety programs.

    17. External safety audits would help Gulfstream monitor the implementation of safety management principles and practices into its flight test operations and sustain long-term cultural change.

    18. Flight test safety would be enhanced if manufacturers and flight test industry groups had knowledge of the lessons learned from Gulfstream’s implementation of its flight test safety management system.

    19. Advance coordination between flight test operators and airport operations and aircraft rescue and firefighting personnel for high-risk flight tests could reduce the response time to an accident site in the event of an emergency.

    Probable Cause

    The National Transportation Safety Board determines that the cause of this accident was an aerodynamic stall and subsequent uncommanded roll during a one engine-inoperative takeoff flight test, which were the result of (1) Gulfstream’s failure to properly develop and validate takeoff speeds for the flight tests and recognize and correct the takeoff safety speed (V2) error during previous G650 flight tests, (2) the G650 flight test team’s persistent and increasingly aggressive attempts to achieve V2 speeds that were erroneously low, and (3) Gulfstream’s inadequate investigation of previous G650 uncommanded roll events, which indicated that the company’s estimated stall angle of attack while the airplane was in ground effect was too high. Contributing to the accident was Gulfstream’s failure to effectively manage the G650 flight test program by pursuing an aggressive program schedule without ensuring that the roles and responsibilities of team members had been appropriately defined and implemented, engineering processes had received sufficient technical planning and oversight, potential hazards had been fully identified, and appropriate risk controls had been implemented and were functioning as intended.

    Recommendations

    To the Federal Aviation Administration:

    1. Inform domestic and foreign manufacturers of airplanes that are certified under 14 Code of Federal Regulations Parts 23 and 25 about the circumstances of this accident and advise them to consider, when estimating an airplane’s stall angle of attack in ground effect, the possibility that the airplane’s maximum lift coefficient in ground effect could be lower than its maximum lift coefficient in free air.

    2. Work with the Flight Test Safety Committee to develop and issue detailed flight test operating guidance for manufacturers that addresses the deficiencies documented in this report regarding flight test operating policies and procedures and their implementation.

    3. Work with the Flight Test Safety Committee to develop and issue flight test safety program guidelines based on best practices in aviation safety management.

    4. After the Flight Test Safety Committee has issued flight test safety program guidelines, include these guidelines in the next revision of Federal Aviation Administration Order 4040.26, Aircraft Certification Service Flight Test Risk Management Program.

    5. Inform 14 Code of Federal Regulations Part 139 airports that currently have (or may have in the future) flight test activity of the importance of advance coordination of high risk flight tests with flight test operators to ensure adequate aircraft rescue and firefighting resources are available to provide increased readiness during known high risk flight tests.

    To the Flight Test Safety Committee:

    6. In collaboration with the Federal Aviation Administration, develop and issue flight test operating guidance for manufacturers that addresses the deficiencies documented in this report regarding flight test operating policies and procedures and their implementation, and encourage manufacturers to conduct flight test operations in accordance with the guidance.

    7. In collaboration with the Federal Aviation Administration, develop and issue flight test safety program guidelines based on best practices in aviation safety management, and encourage manufacturers to incorporate these guidelines into their flight test safety programs.

    8. Encourage members to provide notice of and coordinate high-risk flight tests with airport operations and aircraft rescue and firefighting personnel.

    To Gulfstream Aerospace Corporation:

    9. Commission an audit by qualified independent safety experts, before the start of the next major certification flight test program, to evaluate the company’s flight test safety management system, with special attention given to the areas of weakness identified in this report, and address all areas of concern identified by the audit.

    10. Provide information about the lessons learned from the implementation of its flight test safety management system to interested manufacturers, flight test industry groups, and other appropriate parties.

    src

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