|

Series of Operational Errors by Pilot Led to 2009 Airplane Crash in Montana

Similar Posts

  • |

    Fatigue Understanding between NATCA and FAA

    The Federal Aviation Administration (FAA) and the National Air Traffic Controllers Association (NATCA) announced agreement on important fatigue recommendations that were developed by a joint FAA-NATCA working group which was established under the 2009 collective bargaining agreement.

    “The American public must have confidence that our nation’s air traffic controllers are rested and ready to work,” said Transportation Secretary Ray LaHood. “We have the safest air transportation system in the world but we needed to make changes and we are doing that.”

    The agreement reinforces existing FAA policy that prohibits air traffic controllers from sleeping while they are performing assigned duties. The FAA will continue to provide air traffic controllers breaks on the midnight shift based on staffing and workload. While on break, air traffic controllers are expected to conduct themselves professionally and be available for recall at all times.

    The FAA and NATCA also agreed that all air traffic controllers must report for work well-rested and mentally alert. It is the employee’s responsibility to notify their supervisor if they are too fatigued to perform their air traffic control duties. As a result of this agreement, air traffic controllers can now request to take leave if they are too fatigued to work air traffic.

    This agreement marks the completion of the tasks required by this joint FAA-NATCA fatigue working group. The FAA and NATCA will continue to collaborate to reduce the risk of fatigue in the workplace.

    “Air traffic controllers have the responsibility to report rested and ready to work so they can safely perform their operational duties,” said FAA Administrator Randy Babbitt. “But we also need to make sure we have the right policies in place to reduce the possibility of fatigue in the workplace.”

    “We are pleased that the efforts of the joint NATCA-FAA fatigue workgroup that produced these science-based recommendations have resulted in an agreement and their implementation into the schedules and work environments of our nation’s dedicated and highly professional air traffic controller workforce,” said NATCA President Paul Rinaldi.

    “We supported the FAA’s action to enhance aviation safety by eliminating single staffing on the midnight shift and we fully support these recommendations that address fatigue. They are common sense solutions to a safety problem that NATCA and fatigue experts have consistently raised for many years.”
    Air traffic controllers will also now be allowed to listen to the radio and read appropriate printed material while on duty during the hours of 10PM and 6AM as traffic permits.

    The FAA had previously adjusted work schedules to give air traffic controllers a minimum of nine hours off between shifts. The FAA and NATCA will develop new watch schedule principles that incorporate fatigue science for schedules beginning no later than September 1, 2012. The FAA and NATCA are already beginning to work with local facilities on watch schedules that reduce the possibility of fatigue in the transition from the day shift to the midnight shift.

    The FAA has also agreed to develop policies that will encourage air traffic controllers to seek medical help for sleep apnea. Currently, air traffic controllers lose their medical qualification if they are diagnosed with sleep apnea. The FAA will work to develop a process for most air traffic controllers with sleep apnea to regain their medical qualification once they receive proper medical treatment. The FAA’s Office of Aerospace Medicine will also develop educational material to raise awareness of the symptoms and the physical effects of sleep apnea.

    As a result of this agreement, the FAA will develop a Fatigue Risk Management System for air traffic operations by January of next year. This management system will be designed to collect and analyze data associated with work schedules, including work intensity, to ensure that the schedules are not increasing the possibility of fatigue. Systems like these are commonly used in other areas of aviation to evaluate levels of risk. The FAA is also designing a comprehensive fatigue awareness and education training program for employees.

    Read the agreement pdf here.

    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.
  • |

    Continental Announces New Tentative Agreement With Flight Attendants

    CHICAGO, Jan. 4, 2011

    Continental Airlines today announced that it has reached a tentative agreement on a new labor contract with the International Association of Machinists and Aerospace Workers (IAM) representing Continental flight attendants. The IAM is expected to hold a ratification vote in the coming weeks.

    “The negotiation teams were able to reach a fair agreement that is another positive step forward as we work to combine our companies,” said Sam Risoli, vice president of Inflight Service for the combined company.

    The agreement covers approximately 9,300 Continental flight attendants located throughout the United States.

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

    FOR IMMEDIATE RELEASE: March 18, 2010
    SB-10-08

    NTSB SAYS NORTHWEST PILOTS’ DISTRACTION LED TO OVERFLIGHT OF MINNEAPOLIS, NOTES ATC SHORTCOMINGS; ISSUES RECOMMENDATIONS ON ATC PROCEDURES

    Washington, DC – The National Transportation Safety Board has determined that Northwest Airlines flight 188 overflew its destination airport of Minneapolis by more than 100 miles and failed to maintain radio communications because the pilots became distracted by a conversation unrelated to the operation of the aircraft. The NTSB’s accident brief, released today, also note air traffic control shortcomings during the event, and the Board issued two safety recommendations to address those shortcomings.

    On October 21, 2009, Northwest Airlines flight 188, an Airbus A320 (N374NW) operating as a scheduled flight between San Diego and Minneapolis, did not communicate with air traffic control for approximately one hour 17 minutes. While in this NORDO (no radio communications) state, it flew past its intended destination at a cruise altitude of 37,000 feet. The crew subsequently re-established radio communications and landed without further incident. There were no injuries.

    The NTSB said that the pilots continued to fly through several air traffic control sectors without replying to any radio commands. The investigation found that the pilots had become engaged in a conversation dealing with the process by which pilots request flight schedules and during the conversation each was using his personal laptop computer, contrary to company policy. The pilots were not aware of the repeated attempts by air traffic controllers’ and the airline to contact them until a flight attendant used the intercom to inquire about the progress of the flight.

    The NTSB also found that the lack of national requirements for recording ATC instructions when using automated flight tracking systems, such as directing an aircraft to switch frequencies or to indicate that an aircraft has checked in on an assigned frequency, was a factor in the controllers delay in performing necessary actions and notifications required by lost communications procedures. In addition, because NORDO events of a short duration are not uncommon, the Safety Board found that controllers and managers may have become complacent in completing necessary NORDO actions and required notifications in a timely manner.

    As a result of deficiencies in ATC communications procedures revealed in this investigation and an accident involving a Pilatus PC-12/45 that crashed in Butte, Montana on March 22, 2009, the Safety Board is making recommendations to the FAA to address the following issues:

    The lack of standard procedures for identifying flight crew-ATC communications in ATC facilities that use automated flight tracking systems.
    The lack of standard phraseology for identifying the emergency nature of emergency ATC radio transmissions.
    The Safety Board’s probable cause finding, with factual narrative, can be accessed at the following link on the Board’s website: http://www.ntsb.gov/ntsb/brief.asp?ev_id=20091022X00120&key=1

    The Safety Recommendation letter can also be found on the Board’s website at: http://www.ntsb.gov/Recs/letters/2010/A10_42_43.pdf.

    Previously, the Safety Board has addressed the potential hazards created by the use of personal electronic devices by transportation operators. Last month, following the Board’s investigation of the Colgan Air 3407 accident near Buffalo, NY, the Board issued a safety recommendation to the FAA to require all Part 121, 135, and 91K operators to incorporate explicit guidance to pilots, including checklist reminders as appropriate, prohibiting the use of personal portable electronic devices on the flight deck. Details of Safety Recommendation A-10-30 can be accessed at: http://www.ntsb.gov/Recs/letters/2010/A10_10_34.pdf.

    Recent accidents and incidents such as the midair collision over the Hudson River last August, Colgan Air flight 3407, and the Northwest pilot’s overflight of the Minnesota airport have demonstrated the clear hazards to aviation safety when pilots and air traffic controllers depart from standard operating procedures and established best practices.

    The Safety Board will convene a 3-day public forum on professionalism in aviation to address methods for ensuring excellence in pilot and air traffic controller performance. The forum is intended to raise awareness by promoting an open discussion between the Safety Board and invited panelists drawn from industry, labor, academia, and government on the importance of developing and reinforcing professionalism in the aviation industry. The forum is scheduled for May 18-20, 2010. More information regarding the forum will be announced in the coming weeks.

    – 30 –

    To include the featured image in your Twitter Card, please tap or click their icon a second time.
  • Flight 447: Press release N° 3

    Paris, 01 June 2009 – 13:59 local time
    Press release N° 3
    Versão brasileira abaixo

    Air France has sent all the information in its possession on the disappearance of flight AF 447 operating the Rio de Janeiro – Paris-Charles de Gaulle route to the French Accident Investigation Bureau for civil aviation (BEA), the French organization in charge of technical investigations into civil aviation incidents and accidents, and to the aircraft manufacturer Airbus. Air France is in permanent contact with the BEA and Airbus.

    The Airbus A330-200 aircraft, registration F-GZCP, left Rio on 31 May at 7:03pm local time (12:03am in Paris). The aircraft hit a zone of stormy weather with strong turbulence at 2am this morning (universal time), i.e. 4am in Paris. An automatic message was received from the aircraft at 2:14am (4:14am in Paris) indicating a failure in the electric circuit in an area a long way off the coast.

    The aircraft was powered with General Electric CF6-80E engines.

    The aircraft had totalled 18,870 flight hours and went into service on 18 April 2005.
    Its last maintenance check in the hangar took place on 16 April 2009.

    Air France shares the anxiety and distress of the families concerned. The families are being taken care of in a specially reserved area of Paris-Charles de Gaulle Terminal 2.

    A toll-free number has been opened at 0800 800 812 in France,
    at 0800 881 20 20 in Brazil
    and + 33 1 57 02 10 55 for calls from outside France.
    NB: We ask journalists not to call this number, which is reserved for families and close relatives.

    Português

    Air France informou ao Bureau de Investigação e Análises para a Segurança de Aviação civil, organismo responsavél na França pelas investigações técnicas sobre acidentes e incidentes da aviação civil, e para a Airbus, fabricante do avião, as informações que tem em seu poder após o desaparecimento do voo AF 447, fazendo a ligação Rio de Janeiro – Paris-Charles de Gaulle : a companhia está em contato permanente com o Bureau e com a Airbus.

    A aeronave, do tipo Airbus A330-200, matrícula F-GZCP, deixou o Rio dia 31 de maio às 19h03 (hora local).

    A aeronave atravessou uma zona de tempestade com fortes turbulências às 2 horas da manhã (horário TU) – 23 horas horário do Brasil. Uma mensagem automática foi recebida às 2h14 da manhã (horário TU = 23h14 horário do Brasil) indicando uma pane do circuito elétrico numa zona afastada da costa.

    A aeronave é equipada de motores General Electric CF6-80E.

    O avião tem um total de 18 870 horas de voo e começou a operar em 18 de abril de 2005.

    A última visita de manutenção em hangar foi feita em 16 de abril de 2009.

    A Air France divide a emoção e a inquietação das famílias envolvidas. Os familiares serão recebidos num local especialmente reservado no aeroporto de Paris Charles de Gaulle 2 assim como no Salão Nobre do Galeão.

    Um toll free está disponível :
    0800 881 2020 para o Brasil
    0800 800 812 para a França,
    e + 33 1 57 02 10 55 para outros países

    NB : Solicitamos aos jornalistas que NÃO liguem para este número, reservado às famílias.

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

    Press Release – FAA Announces Record Number of Laser Events in 2010

    For Immediate Release
    January 19, 2011

    Pointing Lasers at Aircraft Poses a Serious Safety Issue

    WASHINGTON – The FAA announced today that in 2010, nationwide reports of lasers pointed at aircraft almost doubled from the previous year to more than 2,800. This is the highest number of laser events recorded since the FAA began keeping track in 2005.

    Los Angeles International Airport recorded the highest number of laser events in the country for an individual airport in 2010, with 102 reports, and the greater Los Angeles area tallied nearly twice that number, with 201 reports. Chicago O’Hare International Airport was a close second, with 98 reports, and Phoenix Sky Harbor International Airport and Norman Y. Mineta San Jose International Airport tied for the third highest number of laser events for the year with 80 each.

    “This is a serious safety issue,” said U.S. Transportation Secretary Ray LaHood. “Lasers can distract and harm pilots who are working to get passengers safely to their destinations.”

    Nationwide, laser event reports have steadily increased since the FAA created a formal reporting system in 2005 to collect information from pilots. Reports rose from nearly 300 in 2005 to 1,527 in 2009 and 2,836 in 2010.

    “The FAA is actively warning people not to point high-powered lasers at aircraft because they can damage a pilot’s eyes or cause temporary blindness,” said FAA Administrator Randy Babbitt. “We continue to ask pilots to immediately report laser events to air traffic controllers so we can contact local law enforcement officials.”

    Some cities and states have laws making it illegal to shine lasers at aircraft and, in many cases, people can face federal charges.

    The increase in reports is likely due to a number of factors, including the availability of inexpensive laser devices on the Internet; higher power levels that enable lasers to hit aircraft at higher altitudes; increased pilot reporting of laser strikes; and the introduction of green lasers, which are more easily seen than red lasers.

    Top 20 Laser Event Reports by Airport in 2010
    Airport No. of events
    Los Angeles International Airport (LAX) 102
    Chicago O’Hare International Airport (ORD) 98
    Phoenix/Sky Harbor International Airport (PHX) 80
    San Jose International Airport (SJC) 80
    McCarran International Airport (LAS) 72
    Philadelphia International Airport (PHL) 66
    Oakland International Airport (OAK) 55
    Honolulu International Airport (HNL) 47
    San Francisco International Airport (SFO) 39
    Denver International Airport (DEN) 38
    Newark Liberty International Airport (EWR) 38
    Tucson International Airport (TUS) 37
    Miami International Airport (MIA) 36
    Salt Lake City International Airport (SLC) 36
    Portland International Airport (PDX) 32
    LA/Ontario International Airport (ONT) 32
    Bob Hope Airport (BUR) 31
    Baltimore Washington International Airport (BWI) 31
    John Wayne Airport (SNA) 31
    Seattle-Tacoma International Airport (SEA) 26
    To include the featured image in your Twitter Card, please tap or click their icon a second time.