Official US Government Icon

Official websites use .gov
A .gov website belongs to an official government organization in the United States.

Secure Site Icon

Secure .gov websites use HTTPS
A lock ( ) or https:// means you’ve safely connected to the .gov website. Share sensitive information only on official, secure websites.

Testimony

In This Section

The President’s FY 2015 Budget Request for the U.S. Department of Transportation

STATEMENT OF

THE HONORABLE ANTHONY FOXX
SECRETARY OF TRANSPORTATION

BEFORE THE

APPROPRIATIONS SUBCOMMITTEE ON
TRANSPORTATION, HOUSING, AND URBAN DEVELOPMENT AND RELATED AGENCIES
UNITED STATES SENATE

March 13, 2014

 

Introduction

Chairman Murray, Ranking Member Collins, and Members of the Subcommittee thank you for the opportunity to meet with you today to discuss the President’s FY 2015 Budget request for the U.S. Department of Transportation.   I know all of you share President Obama’s and my commitment to ensuring our Nation’s transportation networks continue to provide all American’s with safe and reliable transportation service.

America’s transportation infrastructure is a National asset we all share-- and it needs our attention.  For many years our leaders have invested in providing, maintaining, and improving transportation networks to meet the needs of our citizens and businesses.  It is because of these investments that we have reliable transportation today.  But increasingly, our investments are not keeping pace with the needs.   Today, we have 100,000 bridges in our country that are old enough for Medicare and a Highway Trust Fund that is running dry.  

As we consider the state of transportation today, we have two important responsibilities we must address.  First, we have to look forward to take charge of transportation decisions that impact our country’s future.  As America continues to grow, we need to ensure that transportation choices are poised to meet the new demands that result from expanding Regions and emerging cities.   This is about so much more than just making travelling easier.  It is about providing access to new job and educational opportunities that open new doors and provide a better quality of life for our citizens.  It is about supporting a growing business network that helps keep local economies strong and provides consumers with expanded choices.  It’s about making our cities and communities places where we all want to be – with easy access to the day-to-day services we all need as well as providing for leisure and other enriching experiences that we all value.    

At the same time, we need to acknowledge that in far too many cases, our current transportation systems have not been maintained to optimal standards and as a result, are not operating in a state of good repair.  This neglect is costly and results in inefficiencies and inconvenience to travelers every day.  Based on the Department’s Conditions and Performance Report, for Transit alone the maintenance backlog for transit systems in our country totals $86 billion and that is growing by an additional $2.5 billion each year. It is important to note that these aren’t just Federal dollars, but, nonetheless, our metrics demonstrate a huge gap between needs and current investment levels.

The President’s Surface Transportation Program Reauthorization Proposal

But it doesn’t have to be this way.  The President has laid out his vision for a four- year $302 billion surface transportation reauthorization proposal to modernize the country’s infrastructure, address our infrastructure deficit, and better connect people to their jobs, schools, and communities every day.      

There are several key elements of this proposal that separate it from its predecessors that I would like to highlight today.  First, the President’s proposal recognizes that moving freight efficiently is critical to our economy and our transportation systems.  The budget requests $10 billion over four years in dedicated funding to invest in freight networks that will improve the movement of goods.  These funds will be used to foster economic growth, advance the President’s export initiative, and improve the efficiency and reliability of freight movement nationwide.  We will reach out to our industry partners such as shippers, truck and rail representatives and associated labor organizations, to ensure that they will play a meaningful role in crafting investment decisions in partnership with State and local officials.   

We recognize that improving project delivery and streamlining the Federal infrastructure permitting processes can yield tangible benefits for Americans while protecting communities and the environment.   The President’s surface transportation reauthorization plan will increase transparency and accountability while at the same time improving interagency coordination.  To advance this effort, the proposal includes $8 million to establish a new interagency permitting acceleration team to be administratively housed within the Office of the Secretary.   This team will work towards the President’s goal of reducing the current permitting processes time by half so that the benefits of new projects will bring can be realized more quickly. 

This surface transportation reauthorization plan acknowledges the important role transportation plays in creating ladders of opportunity for our citizens by including $2.2 billion over four years for a new Rapid Growth Area Transit program that will link people to job and educational opportunities in fast growing areas.  In addition, $120 million is requested over four years for a workforce development program that focuses on improving the size, diversity and skill of our Nation’s construction workforce through partnerships with the Department of Labor and the States.

The President’s surface transportation reauthorization plan also includes a new $2 billion competitive grant program that will encourage innovative solutions to meet our most pressing transportation challenges.  State and local partners will be evaluated on their willingness to commit to performance improvements in key areas such as safety and congestion management.

The President’s vision includes a major emphasis on preserving and improving today’s highway and transit systems.  Known in the proposal as “Fix-it First”,  the reauthorization proposal encourages government and other transportation stakeholders to make optimal use of system capacity; to implement sound asset management principles, and to focus on achieving and maintaining a state of good repair for transportation assets. 

Together, these areas of emphasis will provide a strong foundation from which to manage our surface transportation programs over the next four years.  We are hard at work completing the details of this plan, and will soon be proposing formal legislation for your consideration.   

Funding Overview

Moving forward on these objectives will require funding increases in the Department’s current surface transportation programs over the next four years.  To accomplish this, a total of $72 billion – with nearly $18 billion in FY 2015 is requested for transit programs to focus on the transportation needs of growing suburbs and the deferred maintenance of transportation assets in our cities.  The budget request also includes $500 million for a new Rapid Growth Area Transit Program beginning in         FY 2015 to help communities experiencing fast-growing populations meet new transportation demands.

Funding for Highway programs would increase to $199 billion over four years with $49 billion requested for FY 2015.  Included within this total is funding for a new Freight Program and for highway-specific “Fix-it-First” initiatives to focus investments on the critical safety and capital needs of our existing bridges and roadways.  In addition, more than a billion is provided to support construction and repair of significant transportation infrastructure assets on Federal and Tribal lands.   The President’s FY 2015 request continues the progress achieved to date on alternative financing approaches by providing $1 billion to the Transportation Infrastructure Finance and Innovation Act Program.

The President’s proposal includes funding for rail within the surface transportation reauthorization framework and requests $19 billion over four years to fund rail programs.  For FY 2015, $5 billion is requested to establish a National High-Performance Rail System to support current operations and to improve the rail system of the future.   This bulk of this funding would be divided into two programs—one focused on current passenger rail service initiatives and the other specifically focused on service improvements.

The President’s proposal continues the Department’s commitment to safety by requesting nearly $7 billion for highway safety modes over four years.  For FY 2015, $669 million is requested to support Federal Motor Carrier Safety Administration initiatives to ensure the safe operation of trucks and buses.  Another $851 million will support the ongoing efforts of the National Highway Traffic Safety Administration to focus on emerging issues with vehicle safety and to address new challenges posed by new technologies.

Finally, the President’s surface transportation reauthorization proposal includes $5 billion over four years to fund the competitive TIGER grant program.  TIGER grants provide funding for infrastructure projects of national and regional significance and have been an effective infrastructure improvement mechanism for the past five years.   The FY 2015 Budget requests $1.25 billion to continue the TIGER grants program.

Paying for the Proposal

In developing the President’s surface transportation reauthorization proposal, we are mindful of the important funding commitment this will require.  That is why the President has devoted $150 billion from transition revenue generated from pro-growth tax reform to supplement current revenues from the gas tax.  When combined, these resources will help finance long-term, critical investments in our Nation’s infrastructure.  This proposal provides sufficient funds to ensure the solvency of the Trust Fund during the proposed reauthorization period, to prevent the cash shortfall that is projected to occur later this year.  An additional $87 billion will fund new investments in the surface transportation reauthorization.  

Other Departmental Program Highlights

While much of this discussion has focused on surface transportation needs, the President’s FY 2015 budget request also funds important resource needs for our other critical Transportation programs.

The President requests $15.4 billion in FY 2015 to continue the Federal Aviation Administration’s management of the National Airspace System.  This request supports FAA’s current programs in the areas of air traffic controller and safety staffing, research and development and capital investment.   It also advances the modernization of our air traffic system through “NextGen” – the Next Generation Air Transportation System, which encompasses the deployment of new systems, technologies, and procedures that will help reduce delays, expand air traffic system capacity, and mitigate aviation’s impact on the environment, while ensuring the highest levels of safety.  The President’s plan includes nearly $1 billion in NextGen related initiatives.     

The President’s budget request also acknowledges our responsibilities to ensure the safe transportation of energy products as they travel by rail or truck through our communities.  Recognizing that effective solutions to these transportation concerns require a multimodal focus, the budget also requests $40 million to support the establishment of a new Safe Transportation of Oil Fund to support multimodal prevention and response activities associated with the increased safety issues surrounding the transport of crude oil.  This fund would be housed in the Office of the Secretary and would be available to support initiatives in the Pipeline and Hazardous Materials Safety Administration, the Federal Railroad Administration, and the Federal Motor Carrier Safety Administration.     

Thank you again for the opportunity to share the President’s budget plan for transportation with you today.  I look forward to working with all of you.    

 

Ensuring the Safe Transportation of Energy Products Throughout the Nation

STATEMENT OF

THE HONORABLE ANTHONY FOXX
SECRETARY OF TRANSPORTATION

BEFORE THE

APPROPRIATIONS SUBCOMMITTEE ON
TRANSPORTATION, HOUSING, AND URBAN DEVELOPMENT AND RELATED AGENCIES

RAILWAY SAFETY

UNITED STATES SENATE

April 9, 2014

 

Introduction

Chairman Murray, Ranking Member Collins, and Members of the Subcommittee thank you for the opportunity to meet with you today to discuss the Department of Transportation’s work in ensuring the safe transportation of energy products throughout the Nation.  This emerging issue affects multiple aspects of our transportation network and ensuring the safety of that system is my top priority.

Over the past decade, the United States has successfully expanded our domestic energy production.  In particular, the crude oil and natural gas extracted from the region of North Dakota has yielded impressive results and now provides over 900,000 barrels of oil daily.  As a result, North Dakota is now our second largest oil producing State – yielding more than ten percent of all oil produced in the United States.   All of this is good news for our economy and good news for our energy independence. 

However, at the same time, the increased presence of energy products within our borders and the need to transport them to refineries and distribution points nationwide have raised emerging concerns about our ability to move these products safely through our highways, waterways, and rail systems.  Today, I want to share with you the ongoing efforts within the Department of Transportation to address these concerns and to highlight specific initiatives within the FY 2015 President’s Budget that would support both prevention and response efforts in this area.  

The Department of Transportation has been focused on the safe transportation of hazardous materials for many years.   Because hazardous materials are transported by several modes of transportation, the Department’s prevention and response activities are shared by several of our Operating Administrations.  The Pipeline and Hazardous Materials Safety Administration (PHMSA), Federal Railroad Administration (FRA), and Federal Motor Carrier Administration (FMCSA) all play a role in ensuring that hazardous materials are transported safety.

PHMSA provides oversight and guidance to more than 40,000 companies involved in the commercial transportation of petroleum products and hazardous materials.  Each day, about a million different explosive, poisonous, corrosive, flammable, and radioactive hazardous materials are transported through our transportation corridors – representing as much as 6 million tons of hazardous materials.   The majority of the products under PHMSA’s jurisdiction represent oil and natural gas. 

Over the past few years, PHMSA’s efforts have focused on two fronts:  increasing compliance with existing rules and regulations while at the same time increasing both industry and public awareness of the risks associated with the transportation of oil and other energy products by rail.   PHMSA’s enforcement efforts have yielded significant results.   In fiscal year 2013 alone, PHMSA conducted 1,655 high risk hazardous materials inspections.  As a result of these inspections, PHMSA opened 224 enforcement cases and issued more than 460 citations including some with penalties of nearly $1.6 million. 

At the same time, PHMSA also devotes significant attention to educating the industry and the public on hazardous materials safety and partners with the States to increase awareness on safety standards and practices.  To enhance the dialogue between PHMSA and State and industry partners, PHMSA established a Joint Safety Advisory Committee to address rail safety concerns and to illicit feedback on needed safety improvements.   These steps are all part of PHMSA’s aggressive campaign on multiple fronts to mitigate risks and ensure transportation safety.

We recognize -- as is often the case -- that comprehensive solutions to our difficult transportation issues require a multimodal focus.  In the case of crude oil and energy products transportation, much of this material is moved by trucks and rail or a combination of both as the product travels from the oil wells to refineries and distribution points.   At every stage of the process opportunities exist for safety risks that must be mitigated.  This is why PHMSA is joined by FRA and FMCSA in addressing hazardous material transportation safety concerns. 

For example, FRA has long held the authority to issue Emergency Orders as a method for addressing safety concerns on rail.   In August of 2013 FRA worked with PHMSA on an Emergency Order to address the proper attending and securing of trains.   In February 2014, FRA and PHMSA issued another Emergency Order highlighting the importance of proper testing and classification of crude oil prior to shipping, and the importance of using proper packaging for the specific hazardous materials to be transported.   The use of these joint orders has been very helpful in gaining immediate attention on problem areas.

In response to recent train accidents involving tank cars carrying crude oil, in January oil industry representatives and rail industry CEOs met with me and Administrators Quarterman, Szabo, and Ferro in a “Call to Action”.  At this meeting, the Rail CEOs were asked to develop specific plans and recommendations to immediately improve the safety of crude oil shipments.  I sent a letter to the American Association of Railroads (AAR) asking for their help in implementing a series of voluntary actions that would improve the safety of railroads transporting crude oil and the communities they move through.  President and CEO Edward Hamberger signed the agreement the same day and support from individual railroads followed shortly.

            This “Call to Action” resulted in several important changes that will go a long way in improving safety and I am pleased that our industry partners have joined with us in this critical effort.   The AAR agreed to:

  • apply hazardous materials routing analysis to trains with 20 or more tank cars loaded with petroleum crude oil, which will help determine the safest and most secure route for the product to travel;
  • adhere to speed restrictions for Key Crude Oil Trains (20 or more tank cars filled with petroleum crude oil) and additional speed restrictions if these trains are traveling in high urban areas;  
  • use distributive power locomotives and other solutions to prevent train pile-ups;  
  • install wayside defective bearing detectors every 40 miles to prevent equipment-related accidents;  
  • work with the railroads to develop a list of emergency response resources along Key Crude Oil train routes that can be provided to emergency responders upon request; and
  • provide $5 million to develop and provide training on safe hazardous material transportation.  

FRA and PHMSA have also been working jointly to conduct “Operation Safe Delivery”.  This initiative involves joint activities at all transportation phases to investigate how shippers and carriers are classifying crude oil and to understand the characteristics of the material.  Efforts have focused primarily on the Bakken region and include spot inspections, data collections, and sampling that help in verifying compliance with Federal safety regulations.   

The safe transportation of energy products also includes important efforts by FMCSA since trucks play such a pivotal role in the transportation of these materials.   During 2014, FMCSA partnered with the North Dakota Highway Patrol, the Federal Railroad Administration, the Pipeline and Hazardous Materials Safety Administration, and the Montana Department of Transportation to conduct several multi-agency “Strike Force” Operations.  These “Strike Forces” help to ensure materials are properly classified and motor carriers and drivers are operating safely.  A “Strike Force” operation in February 2014 produced nine violations.

Looking Forward

While we are making progress in addressing the new and emerging safety risks associated with the safe transportation of energy products, we recognize that there is more to be done.  This is why the President’s 2015 Budget includes a request for a new $40 million flexible fund to support prevention and response associated with the safe transportation of crude oil.  Building on our successful collaborations among the affected Operating Administrations, this funding would be concentrated in one fund and be available to support enhanced inspection levels, investigative efforts, research and data analysis, and testing in the highest risk areas. 

This fund will be administered by the Department’s Chief Financial Officer and Assistant Secretary for Budget and Programs who will ensure resources are made available to initiatives within the Federal Railroad Administration, Pipelines and Hazardous Materials Safety Administration, and the Federal Motor Carriers Safety Administration.  Drawing on their expertise in specific subject areas, the Administrators for each Operating Administration, together with the Assistant Secretary for Research and designated representatives from the offices of the Assistant Secretary for Policy, General Counsel, and the Chief Financial Officer, would jointly serve as a decision-making Board and would be responsible for the effective administration of the fund.  Eligible projects would be rapidly reviewed and approved by the Board before funds are transferred to an Operating Administration for implementation.    Examples of eligible expenditures of the Safe Transportation of Energy Products Fund would include initiatives such as the following:

  • Data Driven Safety Interventions – Funding will support the collection and analysis of transportation data on incident, injury, and fatality risks for bulk shipment of flammable liquids by road and rail.  This data will be used to define the scope of the problem and to inform efforts/ target funding toward the most effective safety interventions.  Constituent modes would make proposals to the Board to secure funding for activities that enhance safety or to respond to current incidents.  The Board could choose to prioritize multimodal efforts as appropriate.
  • Additional Safety Personnel – At this initial establishment phase, the fund would be used to support additional personnel divided between FRA and PHMSA for safety inspection and enforcement personnel to provide the backbone of the multimodal effort for this first year.  These resources will conduct inspections, investigations and testing for issues such as tank car performance, commodity classification, and root cause analysis of train derailments.
  • Training and OutreachEfforts – to improve oil spill emergency response and community preparedness.
  • Robust Regulatory Development – to focus on the implementation of comprehensive regulatory actions that would provide the industry with a combination of performance metrics and operating standards that will result in enhanced safety practices, more effective rail operations, and improved tank car survivability. 
  • Economic Analysis – to identify and evaluate costs associated with current system-wide risks of bulk shipments by rail as well as analyses of future system needs
  • NTSB Recommendations – Funds would also be used to address outstanding and anticipated NTSB recommendations.

The need for this initiative is especially important because the U.S. is now the global leader in crude oil production capacity growth, and because we expect this trend to continue for the foreseeable future.

As our domestic energy production efforts continue to expand, the Department of Transportation will draw on its long history of addressing the safe transportation of hazardous materials and use lessons learned to enhance our efforts in this new emerging area.We will also continue to explore new methods and strategies for ensuring these energy products are moved safely through our cities, towns and neighborhoods.We will continue working with our State and industry partners, to develop practical and workable changes that enhance safety and efficiency, ensuring that we maintain an open dialogue with the public to ensure their concerns are promptly addressed.

Thank you again for the opportunity to meet with you today.  I look forward to working with all of you.    

 

The GM Ignition Switch Recall: Why Did It Take So Long

STATEMENT OF

THE HONORABLE DAVID FRIEDMAN
ACTING ADMINISTRATOR,
NATIONAL HIGHWAY
TRAFFIC SAFETY ADMINISTRATION

Before the

COMMITTEE ON ENERGY AND COMMERCE
SUBCOMMITTEE ON OVERSIGHT AND INVESTIGATIONS
U.S. HOUSE OF REPRESENTATIVES

 Hearing on

The GM Ignition Switch Recall: Why Did It Take So Long?

April 1, 2014

Chairman Murphy, Ranking Member DeGette, and members of the Committee:

Thank you for the opportunity to appear before you today to discuss the recall process of the National Highway Traffic Safety Administration (NHTSA) and the General Motors (GM) ignition switch recall.

Let me begin my testimony by saying, on behalf of everyone at NHTSA, that we are deeply saddened by the loss of life in vehicle crashes involving the GM ignition switch defect.  Our deepest sympathies are with the families and friends.

It is this kind of tragedy that our defects investigation team works long hours trying to prevent. Our core mission to save lives and prevent injuries on America’s roadways is something we take very seriously, whether we are trying to curb dangerous driver behavior, improve the safety of vehicles, or find safety defects and ensure that automakers correct them. 

In today’s testimony, I will give you an overview of NHTSA, who we are and what we do.  I will go over the agency’s defects investigation and recalls process that have led to thousands of recalls of millions of vehicles.  Next, I will discuss where we are on each of three key priorities regarding this case.

Our first priority is the recall; we need to ensure that GM gets the vehicles fixed quickly and that it is doing all it can to keep consumers at risk informed and to identify all vehicles that may have a defective ignition switch. Second, we are pursuing an investigation of whether GM met its timeliness responsibilities to report and address this defect under Federal law—an investigation that will end with holding GM accountable if it failed in those responsibilities.  Third, we are examining the new facts and our efforts in this case to understand what took place and to determine how to continue to improve our efforts.

NHTSA has an aggressive and effective defects investigation program with staff who is deeply and personally dedicated to their mission, often working nights and weekends in pursuit of potential defects. That work has resulted in thousands of recalls involving hundreds of millions of vehicles and items of motor vehicle equipment, which have helped to protect millions of consumers from unanticipated safety hazards in their vehicles (Figure 1).

Figure 1. Total Number of Vehicle Recalls, 1993-2013

Based on our review of NHTSA’s actions concerning airbag non-deployment in the recently recalled GM vehicles, we know the agency examined the available information multiple times using consumer complaints, early warning data, special crash investigations, manufacturer information about how air bags function, and other tools, but did not find sufficient evidence of a possible safety defect or defect trend that would warrant opening a formal investigation.  This was a difficult case pursued by experts in the field of screening, investigations and technology involving airbags that are designed to deploy in some cases, but not in cases where they are not needed or would cause greater harm than good.  GM had critical information that would have helped identify this defect. With that and other information in hand, we can look for lessons learned from this experience that may further improve our process.

An Overview of NHTSA and its Mission

NHTSA is not a large agency.  We currently have 591 employees.  The President’s budget for fiscal year 2015 requests $5.2 million for additional staff to help strengthen our ability to address the enormous safety mission that this agency faces.

NHTSA is a data-driven organization that approaches highway safety by considering both the behavioral and the vehicle aspects of crashes.   Human behavior remains the leading cause of highway crashes and deaths, so NHTSA places an emphasis on reducing impaired driving, encouraging seat belt use at all times, and underscoring the dangers of distracted driving.  These programs have shown enormous success over the years in driving down the number of deaths involving alcohol and driving up the percentages of vehicle occupants who wear seat belts.  More work, however, is required, as nearly one-third of fatalities involve alcohol and more than half involve an unbelted occupant.

As those efforts seek to change human behavior, NHTSA’s vehicle safety program focuses on ways to save lives through safety improvements to vehicles, ensuring that vehicles meet all safety standards, and eliminating vehicle defects that pose an unreasonable risk to safety.

Our research and rulemaking priorities concentrate on finding the areas of highest risk where new or amended vehicle standards can make a significant impact on reducing the death toll on our nation’s highways.  In 2012, there were 5.6 million police-reported crashes in America, and tragically, 33,561 Americans died in fatal crashes.  Because we know that most fatal crashes are caused by human behavior, and we know that vehicles are driven and controlled by humans who will make errors, we must continue to find more ways to protect drivers and passengers when crashes happen.  NHTSA’s regulation of occupant crash protection has resulted in significant improvements in the crashworthiness of today’s vehicles.  These standards have saved many thousands of lives and prevented countless injuries.  Highway fatalities over the past five years are at lows not seen since 1950.  NHTSA has also used its vehicle crash ratings to inform consumers and motivate vehicle manufacturers to voluntarily improve the safety of their vehicles above the federal standards.  This New Car Assessment Program (NCAP), known generally as the government’s 5-star safety rating program, has been an overwhelming success in driving improvements in vehicle safety.  NHTSA was the first vehicle safety agency in the world to implement such a program.  Today, these programs have been implemented around the world.

Fatal crashes where a vehicle problem is a cause or contributing factor are relatively rare in comparison to crashes caused by human factors in properly functioning vehicles.  But such cases receive significant scrutiny because NHTSA requires that automakers sell vehicles that meet specific safety standards and that they find and fix defects as soon as they are aware of them.  As a result, we invest significant effort to find those problems through NHTSA’s vehicle safety enforcement program. 

For vehicles and vehicle equipment in the U.S., manufacturers must certify that their products meet applicable Federal Motor Vehicle Safety Standards (FMVSS).  The Office of Vehicle Safety Compliance (OVSC) tests a sample of new vehicles and equipment each year to determine whether they meet those standards.   If the vehicles or equipment do not comply, manufacturers must recall them and provide a remedy to the consumer.

The Office of Defects Investigation (ODI) has a different mission.  ODI searches through consumer complaints, manufacturer data, data from NHTSA’s National Center for Statistics and Analysis (NCSA), special crash investigations, and other sources for information that might indicate the presence of a defect or defect trend.  Where it can find a possible defect or defect trend posing an unreasonable risk to safety, it investigates.  If NHTSA can demonstrate that a defect exists and that it poses an unreasonable safety risk, the agency can order a recall. 

NHTSA’s ability to influence or order recalls is its greatest strength in safeguarding against problems in the vehicles traveling our roads today.  Since 2000, NHTSA has influenced, on average, the recall of nearly 9 million vehicles every year, as well as millions of items of equipment, for safety related defects.

An Overview of the Defects Investigation and Recall Process 

Defects Investigations

Each potential defect investigation is unique and dependent on the data gathered in each case.   NHTSA uses a number of tools and techniques to gather and analyze data and look for trends that warrant a vehicle safety investigation, and possibly a recall.  These tools include customer complaints to NHTSA, early warning data, as well as other sources that might provide related information, such as crash investigations and industry-related websites.  Additionally, the law requires manufacturers to inform NHTSA within five business days of any noncompliance or defects that create an unreasonable risk to safety. They are then required to initiate a recall to remedy the defect and notify affected consumers.

NHTSA’s defects investigation office, ODI, has a staff of 51 people.  Their goal is to find possible defects or defect trends that may indicate significant safety risks in particular makes, models, and model years; determine whether there is an unreasonable safety risk apparently being caused by a defect; and, if so, persuade—or require— the manufacturer to conduct a recall.  The staff also performs other important functions, such as responding to inquiries and tracking the hundreds of recalls that occur each year.  That entails monitoring quarterly reports on completion rates, ensuring the scope of the recalls is correct, and compiling information on recalls for the public.

The defects investigation process begins with the screening of incoming information for evidence of a potential safety defect.   Complaints from consumers are the primary source of information.   NHTSA receives over 45,000 complaints a year through SaferCar.gov and the Vehicle Safety Hotline, and reviews each one promptly.  Human eyes review every single complaint.  Follow-up is sometimes required to get additional information, and in cases of interest, NHTSA staff will contact the complainants directly to obtain clarifying information.  Screeners also look at technical service bulletins issued by manufacturers, reports of foreign recalls, crash investigations done by NHTSA’s Special Crash Investigations office, and supplemental information such as occasional reports from insurance companies and information available on the Internet.  When appropriate, the screeners consult NHTSA’s crash databases, including the Fatality Analysis Reporting System (FARS) and National Automotive Sampling System (NASS).  Also, members of the public may file petitions asking NHTSA to investigate and order a recall on a particular matter.  The agency carefully reviews each petition before making a decision on whether to grant or deny it.  If granted, a formal investigation is opened. Since 2004, the agency has opened 980 investigations.  These safety defect investigations have resulted in 1,299 recalls involving more than 95 million vehicles, equipment, tires, and child restraints, which have helped reduce vehicle fatalities to historic lows.  For example, a NHTSA investigation recently led to the recall of over 4 million child safety seats and is still underway regarding the possible recall of infant seats.

Another important source of information is Early Warning Reporting (EWR) data submitted quarterly by manufacturers of vehicles, tires, and child seats.   For light vehicle manufacturers, the data include counts of property damage claims, warranty reports, consumer complaints, and field reports, which are efforts by the automaker to look into specific incidents.  These aggregate data are broken down by make, model, and model year and by component category (e.g., steering, braking, engine, speed control).   Manufacturers must also submit brief reports on each claim against the company for death or injury allegedly related to a possible vehicle defect.  The volume of the data received is enormous.  NHTSA uses sophisticated data mining techniques to identify trends in the data that may be evidence of a safety defect. When potential trends are found, the EWR division can make a referral to the team involved in the screening process.

Those who screen NHTSA’s various sources of information are in constant communication and support each other in their efforts to identify potential defect issues.  When patterns emerge from any source, the screeners look very carefully at what may be behind the patterns.   Where there is possible evidence of a defect trend, the screening staff recommends that the appropriate investigating division consider opening an investigation.   ODI staff meets regularly to determine which recommendations warrant opening an investigation and which may warrant continued monitoring.   With preliminary evidence and 16 investigators, ODI must analyze all of the fact patterns and discern whether potential defects likely involve more serious risks or are likely to reveal a defect trend.

If it is determined that an investigation is warranted, a preliminary evaluation begins.   This often entails detailed interviews with complainants, requesting relevant information from the manufacturer, and analysis to determine whether there is sufficient evidence either to seek a recall or continue to a more in-depth investigation.  If it is determined that sufficient evidence exists, the next stage is the engineering analysis, which involves gathering additional information from consumers and the manufacturer, perhaps testing of vehicles or equipment by NHTSA’s Ohio based test facility, surveys of peer vehicle experience, and further in-depth analysis of the underlying problem. 

If, at any stage, ODI staff believes there is enough information to determine that a specific defect exists and that it creates an unreasonable risk to safety, they urge the manufacturer to conduct a recall.  Where the manufacturer is not persuaded by NHTSA to undertake a recall, NHTSA’s Associate Administrator for Enforcement may issue an initial decision requiring that the manufacturer conduct the recall.   Following the initial decision, NHTSA convenes a public meeting in which interested parties—including the manufacturer, consumers, suppliers, public interest groups—may provide testimony.   The manufacturer is given another opportunity to submit comments on the testimony heard at the public meeting.  If, after review of all the information generated by the administrative process, the Administrator concludes that a recall should occur, the Administrator issues a recall order.  A recall order is not self-enforcing.  If the manufacturer does not follow the order, NHTSA would seek enforcement.  To prevail in court, NHTSA must be able to prove that a defect exists and that the defect creates an unreasonable safety risk. 

Manufacturers generally adhere to their legal duty to identify non-compliance or safety defects and initiate recalls, but the NHTSA investigation process helps to ensure that these steps are occurring and to recognize when they are not.  Over the last 10 years, manufacturers have recalled more than 83 million vehicles for safety defects where NHTSA has not investigated, and have recalled over 86 million additional vehicles based on NHTSA’s defect investigations.   No other country has a defects investigation program of this scope.

Recalls

When a manufacturer recalls a vehicle at NHTSA’s urging during or after an investigation, we call it an “influenced recall.”  Whether a recall is influenced or not, the recall process is the same.  When a manufacturer recalls a vehicle model or vehicle equipment, the manufacturer files a defect information report with NHTSA under 49 CFR Part 573, known in the industry as a “573 Report.”  Certain information is required in the report under 49 CFR 573.6(c), including, for example, identification of the line of vehicles or vehicle equipment under recall, the number of affected vehicles or pieces of vehicle equipment, a description of the defect, and a description of the remedy.  

The regulations require manufacturers to submit the 573 report within five business days of their determination that a defect is safety related.  For this reason, the 573 report must also include a chronology of events that led to the recall decision.   NHTSA reviews every recall to ensure that the manufacturer has met its obligation to inform the agency of safety-related defects or to make a timely decision that its products contain a safety defect.  If indications show that it has not, NHTSA may open another investigation called a Timeliness Query (TQ) to collect additional relevant information.  This Administration has placed an emphasis on timeliness in order to safeguard the integrity of the process and encourage automakers to aggressively pursue potential safety defects.  Since 2009, automakers have paid record fines totaling more than $85 million for lack of timeliness in reporting vehicle safety defect issues to NHTSA.  Because of this emphasis, we believe that all manufacturers in the automobile industry are now paying much closer attention to their responsibility to protect their customers and the driving public.                                                                                                                                            

Upon receipt of a 573 report, NHTSA enters it to NHTSA’s Artemis database as ODI investigators screen it for completeness, proper scope, timeliness, and effectiveness of the proposed remedy.  NHTSA sends an acknowledgement letter and recall summary to the manufacturer, requesting the manufacturer to supply any missing information.  NHTSA posts each new recall on its website at SaferCar.gov.

Under 49 CFR Part 577, manufacturers are required to notify owners of vehicles and vehicle equipment under recall.  The “577 letter” must state that the manufacturer has determined that there is a safety defect in a vehicle or piece of vehicle equipment that the consumer owns.  It must provide information about where and when a remedy to the defect can be acquired, and it must inform the consumer that the remedy will be provided by the manufacturer free of charge.

The manufacturer must then track how many of the items under recall receive the remedy (“recall completion”) and report the numbers to NHTSA for six quarters.  NHTSA uses these numbers to later calculate a completion rate analysis and work with manufacturers where the completion rate is below average.

We believe our defects investigation program and recalls process has functioned extremely well over the years in identifying defects that create unreasonable risks and ensuring that recalls occur whenever appropriate.  Even so, we continually seek ways to improve.  In 2011, the Department of Transportation’s IG reviewed the ODI investigation process and issued 10 recommendations for improvement. In response to actions taken and/or information provided by the agency, the IG has closed nine of the 10 recommendations and we are in the process of finalizing our report to the IG addressing the remaining recommendation which concerns developing a staffing model.  A list of the recommendations is attached (Attachment 1).

In addition to implementing the IG recommendations, ODI has taken steps to further improve its ability to find defects. One recent improvement is the deployment of a new Business Intelligence and Natural Language Processing suite focused on our consumer complaints, which helps supplement the human review process and has expanded our ability to harvest data and identify defect trends.  Even after implementing this software and all of the IG’s recommendations, we will continue to look for ways to make our processes more effective.

An Overview of NHTSA’s Special Crash Investigation (SCI) program

NHTSA’s Special Crash Investigations (SCI) Program provides in-depth crash data ranging from basic information obtained from routine police and insurance crash reports to comprehensive data from reports by professional crash investigators. Hundreds of data elements relevant to the vehicle, occupants, injury mechanisms, roadway, and safety systems involved are collected for each of more than 130 crashes studied annually.

SCI investigations are quite different from ODI defects investigations.  While defects investigations look for defect trends in a line of vehicles or vehicle equipment, SCI investigations provide data and observations associated with a specific incident that are useful for examining new, emerging, and rapidly changing technology, including the safety performance of alternative fueled vehicles, child safety restraints, adapted vehicles, safety belts, air bags, vehicle-pedestrian interactions, and potential safety defects.  SCI investigators locate and analyze unique real-world crashes to generate data that can be used to improve the performance of automotive safety systems.  This information may be helpful to NHTSA’s research and rulemaking offices in considering possible new or amended standards, to ODI in considering whether to investigate an issue or in support of an ongoing investigation, or to industry and other interested observers.  Cases of interest are selected from a diverse network of sources, including NHTSA's Auto Safety Hotline, the Department of Transportation's National Response Center, NHTSA's regional offices, NASS FIELD Offices, automotive manufacturers, other government agencies, law enforcement agencies, engineers, and medical personnel.

Professional crash investigators obtain data and take photographs of the crash sites. They locate the vehicles involved, photograph them, measure the crash damage, and identify interior locations that were contacted by the occupants, and if equipped, obtain the Event Data Recorder (EDR) data for evaluating safety system performance. The investigators follow up their on-site investigations by interviewing crash victims and other involved parties, and by reviewing medical records to determine the nature and severity of injuries. Each investigation provides extensive information about pertinent pre-crash, crash, and post-crash events involving the occupants, vehicles, rescue, and environmental factors, which may have contributed to the event's occurrence or severity. Included in each report is an analysis and determination of the occupant kinematics and vehicle dynamics as they occurred throughout the crash. The reports provide detailed performance evaluations of the air bag, the use of seat belts, and any other safety features.

NHTSA and DOT’s Current Efforts on GM’s Recall

GM’s Recall

GM reported this defect and initiated its recall on February 7, 2014.  As of March 28, 2014, the GM recall currently covers approximately 2.1 million vehicles, including the 2005-2007 Chevrolet Cobalt, 2007 Pontiac G5, 2003-2007 Saturn Ion, 2006-2007 Chevrolet HHR, 2006-2007 Pontiac Solstice and 2007 Saturn Sky vehicles. NHTSA is working to ensure that GM has accounted for the full scope of vehicles that may be covered by the recall, is ensuring that consumers receive the needed remedy as soon as possible, and is providing consumers information and resources essential to keep them safe until the vehicles can be fixed. GM has indicated to dealers that it expects to have parts on or about April 7 and will notify consumers that it can begin scheduling repairs soon after that date.  Given the number of vehicles, the repairs may take several months to be completed.

At this time, NHTSA urges owners and drivers to follow GM’s recommendation to “use only the ignition key with nothing else on the key ring” when operating the vehicle, contact GM about added resources available to keep themselves safe, and seek the permanent repair remedy from GM as soon as replacement parts become available.

NHTSA’s Timeliness Investigation

GM first provided NHTSA a chronology of events on February 24, 2014.  The information in GM’s chronology raises serious questions as to the timeliness of GM’s recall.  As a result, on February 26, NHTSA opened its present investigation, a timeliness query.  On March 4, to obtain more detailed information than GM provided in its recall notification letter, NHTSA issued a special order seeking answers and documents, submitted under oath, to questions relevant to how quickly GM acted on information about the defect.  GM’s response is due to NHTSA on April 3.

NHTSA is a data driven organization and we will take whatever action is appropriate based on our findings, including issuing civil penalties of up to the statutory limit of $35 million.

NHTSA and DOT’s Processes 

NHTSA and DOT’s Office of General Counsel (OGC) are currently engaged in a continuous improvement and due diligence process regarding past efforts on airbag non-deployments in GM vehicles under its ignition switch defect recall.  Secretary Foxx recently requested the Department of Transportation Inspector General to initiate an agency audit in connection with the GM recall.  These efforts will ensure that DOT and NHTSA have a full understanding of the facts regarding the GM recall and can take corrective actions to enhance NHTSA’s safety function to the extent necessary and appropriate. These processes will also benefit from any findings from NHTSA’s timeliness investigation, which may shed light on what additional information NHTSA could have had in evaluating airbag non-deployments in this case.

NHTSA’s Past Efforts on Airbag Non-Deployments in the GM Vehicles

NHTSA’s timeliness investigation and joint due diligence review with OGC are ongoing, and the DOT OIG audit is pending, so any understanding of NHTSA’s past efforts is preliminary at this time. We are not aware of any information to suggest that NHTSA failed to properly carry out its safety mission based on the data available to it and the process it followed. NHTSA examined the available information multiple times using consumer complaints, early warning data, special crash investigations, manufacturer information about how air bags function, and other tools, but did not find sufficient evidence of a possible safety defect trend that would warrant opening a formal investigation.  This was a difficult case pursued by experts in the field of screening, investigations and technology involving airbags that are designed to deploy in some cases but not others. GM had critical information that would have helped identify this defect.

What follows is an outline of our current understanding of NHTSA’s past efforts and related background information.

Background on Advanced Airbags

Airbags are a vitally important, supplemental restraint system used to mitigate injuries and death in the event of a crash.   The term “supplemental” is used with regard to airbags because it enhances the protection of the seat belts, which are the primary occupant restraint system in a vehicle.  NCSA estimates that in 2012, 2,213 lives were saved by frontal air bags, adding to the estimated 12,174 lives saved by seat belts. Between 1986 and 2012, frontal air bags are estimated to have saved almost 37,000 lives.

Advanced airbags are not intended to deploy in all crashes, even frontal crashes.  Advanced airbag systems are designed not to deploy when doing so will cause more harm than good.  Smaller occupants who sit closer to the airbag are at risk as are unrestrained occupants, because those occupants will move closer to the airbags during the course of a crash, putting them at risk of being hit with the force of a rapidly expanding bag.  Airbags also may not deploy during crashes that occur off-road with multiple minor impacts because such minor impacts involve much slower changes in speed than on-road vehicle-to-vehicle crashes. Even on-road, airbags may not deploy if the crash was not severe enough to warrant the supplemental protection.

Advanced airbags began to be introduced in the 2004 model year in response to a May 2000 NHTSA rule intended to reduce injuries and deaths resulting from previous airbag designs.  These prior designs presented risks to smaller occupants and infants in rear-facing car seats placed on the front passenger seat.  Advanced airbags factor in additional data to determine when to deploy, such as the size of the individual, the change in velocity, location of the individual within the vehicle, and whether the occupants are belted.

Special Crash Investigations Regarding Vehicle Subject to the GM Recall

The Model Year (MY) 2005 Chevrolet Cobalt was among the first vehicles equipped with advanced airbag features, although the Cobalt’s advanced airbag system was not certified as such by GM until 2006.  

In 2005, a fatal crash in Maryland came to the attention of our SCI team. SCI investigated the Maryland accident as well as two others involving MY2005 Cobalts, one in Wisconsin in 2006 and one in Pennsylvania in 2009.  All three crashes, tragically, resulted in the deaths of unrestrained occupants.  All three also involved airbags that did not deploy and event data recorder (EDR) information indicating the vehicle power was in an accessory position.  (When a vehicle is an accessory position, certain features, or accessories, such as the radio are powered, but others remain off to prevent the vehicle’s battery from being drained.)  The 2005 and 2006 crashes involved vehicles exiting the roadway and striking trees. The 2009 crash involved being struck by an oncoming vehicle in the wrong lane.

Office of Defects Investigation Activities Regarding the Subject Vehicles

As the SCI team examined these individual crashes, NHTSA reviewed other sources of available data to determine whether a problem existed related to airbag non-deployment in certain GM vehicles.  In particular, NHTSA’s early warning division (EWD) collected and reviewed available data on airbag non-deployment in Cobalts.  After receiving early warning data from GM, and searching through available information sources, EWD identified 43 incidents where airbags may not have deployed in a crash.  As a result, in 2007, EWD referred the case to NHTSA’s data analysis division (DAD) for further screening.

Following this referral, DAD reviewed data on non-deployment of airbags in the Cobalt and Ion.  In connection with this evaluation, DAD considered a variety of sources of data, including complaints concerning alleged non-deployments and available information concerning the relevant special crash investigations described above.  During the course of this evaluation, NHTSA brought the airbag non-deployment issue to the attention of GM on at least one occasion.

A defects assessment panel convened in 2007 to review the available information on non-deployment of airbags in the Cobalt and Ion, considering vehicle owner questionnaire (VOQ) complaints reporting non-deployments, early warning data, SCI investigations, and the circumstances of the crashes.  The data available at the time of this evaluation did not indicate a safety defect or defect trend that would warrant the agency opening a formal investigation.  In particular, the available data did not indicate that the Cobalt or Ion were overrepresented compared to other peer vehicles with respect to injury-crash incident rates (Figure 2).  Moreover, the crash data available to NHTSA included incidents involving unbelted occupants and off-road, long-duration events, where it could not be determined that the air bag should have deployed.    

Figure 2. 2007 NHTSA Chart of Airbag Non-Deployment Injury-Crash Incident Rates

Against this backdrop, NTHSA continued to monitor the performance of the Cobalt in frontal crashes, including EWR information, consumer complaints, and one additional SCI report.  Again in 2010, NHTSA reviewed cumulative data on consumer complaints for data the airbag non-deployment rate of Cobalts (Figure 3).  The data showed that the injury-crash incident rate for Model Year 2005 and 2006 Cobalts had decreased by nearly half since the 2007 review and did not provide a basis for a formal investigation.

At the time of these reviews, NHTSA did not have the information that GM has since provided—for instance, new evidence linking airbag non-deployment to faulty ignition switches—which is why we have launched an aggressive investigation into the timing of their recall. 

Figure 3. 2010 NHTSA Chart of Airbag Non-Deployment Injury-Crash Rates

Critical Issues Regarding ODI Work and the Subject Vehicles

In evaluating the potential for a defect or defect trend, ODI relies on expertise regarding the technology and the dynamics of the incidents involved. In this case, ODI was looking for a defect or defect trend regarding airbag non-deployment in circumstances where it appeared a deployment should have occurred.   At the time, ODI did not have clear evidence of a connection between the ignition switch being in the accessory mode and the airbag non-deployment.

Our understanding at the time was that airbag systems were designed to continue to function in the event of power loss during a crash, which is not uncommon. ODI’s understanding of airbag systems, which was verified by available GM service literature reviewed during our due diligence effort, was that an airbag system would be armed and ready to fire for up to 60 seconds after all power to the system was cut off.   At the time ODI was evaluating whether to open an investigation, the two SCI reports showed indications of power loss and identified the vehicle power mode as accessory. The preliminary SCI report on the 2006 Wisconsin crash did identify the issue of the ignition switch being in the accessory position, raising the possibility of an issue, but concluded that, “At this point, it appears the yielding of the tree may have been the likely cause of the non-deployment.”   The final report produced in 2008 identified both the yielding nature of the impact and power loss due to movement of the ignition switch prior to impact as potential causes of non-deployment, but removed any conclusion as to which was the likely cause.  However, due to the timing of the report and investigation, the final version of the report was not complete prior to the determination of whether or not to open an investigation.

As noted previously, advanced airbags are designed to deploy in some cases, but not in others. The two SCI cases used in making the 2007 determination of whether or not to open an investigation included unrestrained occupants in vehicles that exited the roadway and struck yielding objects before rapidly decelerating and coming to rest. These situations, where unrestrained occupants may be out of position, are instances where airbags are less likely to deploy because doing so may harm the occupants.

When data available to NHTSA reveals a basis to investigate a potential risk to motor vehicle safety, the agency takes decisive action.  Over the last 10 years, NHTSA investigations have influenced 35 recalls related to airbags involving 6.5 million vehicles, including 18 recalls of 3.5 million vehicles specifically involving non-deployment.  In those cases, information available to NHTSA demonstrated the need to investigate.

In February 2014, GM submitted information to NHTSA that, for the first time, acknowledged a link between the ignition switch to the airbag non-deployment, as well as key information regarding parts changes, discussions with suppliers, and other efforts currently under consideration in our Timeliness Query.  Had the information newly provided to NHTSA by GM been available before now, it would have better informed the agency’s prior reviews of airbag non-deployment in GM vehicles and likely would have changed NHTSA’s approach to this issue.  

Conclusion

NHTSA’s dedicated and professional staff works to monitor and secure the safety of the U.S. automotive fleet.  The work that they do saves lives on a daily basis, and the importance of that work cannot be overstated.  NHTSA continually seeks new ways to improve our processes. We are reviewing the events leading up to this recall to see if there areas that can be improved.  We are looking to improve our understanding of the way that various manufacturers design airbags to function when the vehicle loses power, considering whether we need to improve the use of Special Crash Investigation (SCI) in our defects screening process, reviewing ways to better incorporate information about remote defect possibilities into the investigative process, and evaluating our process for engaging manufacturers around issue evaluations.

I greatly appreciate the opportunity to testify before you today. I believe it is important that the Members, and the American public, have a better understanding of the vitally important safety work that we do at NHTSA.  I look forward to your questions.

Attachment #1

Office of Inspector General Audit Report:

PROCESS IMPROVEMENTS ARE NEEDED FOR IDENTIFYING AND ADDRESSING VEHICLE SAFETY DEFECTS

National Highway Traffic Safety Administration

Report Number: MH-2012-001

Date Issued: October 6, 2011

RECOMMENDATIONS

We recommend that the National Highway Traffic Safety Administrator:

1. Revise the pre-investigation processes to ensure that the review of each complaint is recorded and that complaints are tracked to associated investigations in Artemis.

2. Establish pre-investigation processes for retaining and storing pre-investigation records, such as investigation proposals and insurance company data.

3. Require that decisions made and actions taken by ODI Defect Assessment Panels are recorded, including justifications for not proceeding to investigations.

4. Establish systematic processes for determining when a third-party or the Vehicle Research Test Center should be used to verify manufacturer information or assist in identifying a potential defect.

5. Revise the ODI investigation process to require justifications for continuing or closing investigations that exceed timeliness goals for PEs and EAs.

6. Revise the ODI investigation process to establish criteria for documenting evidence, such as associated complaints, meetings with manufacturers and other stakeholders, and third-party analysis or testing conducted.

7. Strengthen ODI’s redaction policy and process to better protect consumers’ personal information from public availability, such as by using automated redaction software.

8. Conduct a workforce assessment to determine the number of staff required to ensure that ODI meets its objectives and determines the most effective mix of staff.

9. Develop a formal training program to assist ODI staff in acquiring the knowledge and staying abreast of ODI processes and current and new automobile technologies.

10. Develop and implement a strategy for increasing coordination with foreign countries to enhance ODI’s ability to identify safety defects and to exchange information on foreign recalls.

Examining the GM Recall and NHTSA’s Defect Investigation Process

STATEMENT OF

THE HONORABLE DAVID FRIEDMAN
ACTING ADMINISTRATOR,
NATIONAL HIGHWAY
TRAFFIC SAFETY ADMINISTRATION

Before the

Senate Committee on Commerce, Science, and Transportation
Subcommittee on Consumer Protection, Product Safety, and Insurance

“Examining the GM Recall and NHTSA’s Defect Investigation Process.”

April 2, 2014

 

Chairman McCaskill, Ranking Member Heller, and Members of the Subcommittee:

Thank you for the opportunity to appear before you today to discuss the recall process of the National Highway Traffic Safety Administration (NHTSA) and the General Motors (GM) ignition switch recall.

Let me begin my testimony by saying, on behalf of everyone at NHTSA, that we are deeply saddened by the loss of life in vehicle crashes involving the GM ignition switch defect.  Our deepest sympathies are with the families and friends.

It is this kind of tragedy that our defects investigation team works long hours trying to prevent. Our core mission to save lives and prevent injuries on America’s roadways is something we take very seriously, whether we are trying to curb dangerous driver behavior, improve the safety of vehicles, or find safety defects and ensure that automakers correct them. 

In today’s testimony, I will give you an overview of NHTSA, who we are and what we do.  I will go over the agency’s defects investigation and recalls process that have led to thousands of recalls of millions of vehicles.  Next, I will discuss where we are on each of three key priorities regarding this case.

Our first priority is the recall; we need to ensure that GM gets the vehicles fixed quickly and that it is doing all it can to keep consumers at risk informed and to identify all vehicles that may have a defective ignition switch. Second, we are pursuing an investigation of whether GM met its timeliness responsibilities to report and address this defect under Federal law—an investigation that will end with holding GM accountable if it failed in those responsibilities.  Third, we are examining the new facts and our efforts in this case to understand what took place and to determine how to continue to improve our efforts.

NHTSA has an aggressive and effective defects investigation program with staff who is deeply and personally dedicated to their mission, often working nights and weekends in pursuit of potential defects.  That work has resulted in thousands of recalls involving hundreds of millions of vehicles and items of motor vehicle equipment, which have helped to protect millions of consumers from unanticipated safety hazards in their vehicles (Figure 1).

Figure 1. Total Number of Vehicle Recalls, 1993-2013

Based on our review of NHTSA’s actions concerning airbag non-deployment in the recently recalled GM vehicles, we know the agency examined the available information multiple times using consumer complaints, early warning data, special crash investigations, manufacturer information about how air bags function, and other tools, but did not find sufficient evidence of a possible safety defect or defect trend that would warrant opening a formal investigation.  This was a difficult case pursued by experts in the field of screening, investigations and technology involving airbags that are designed to deploy in some cases, but not in cases where they are not needed or would cause greater harm than good.  GM had critical information that would have helped identify this defect. With that and other information in hand, we can look for lessons learned from this experience that may further improve our process.

An Overview of NHTSA and its Mission

NHTSA is not a large agency.  We currently have 591 employees.  The President’s budget for fiscal year 2015 requests $5.2 million for additional staff to help strengthen our ability to address the enormous safety mission that this agency faces.

NHTSA is a data-driven organization that approaches highway safety by considering both the behavioral and the vehicle aspects of crashes.   Human behavior remains the leading cause of highway crashes and deaths, so NHTSA places an emphasis on reducing impaired driving, encouraging seat belt use at all times, and underscoring the dangers of distracted driving.  These programs have shown enormous success over the years in driving down the number of deaths involving alcohol and driving up the percentages of vehicle occupants who wear seat belts.  More work, however, is required, as nearly one-third of fatalities involve alcohol and more than half involve an unbelted occupant.

As those efforts seek to change human behavior, NHTSA’s vehicle safety program focuses on ways to save lives through safety improvements to vehicles, ensuring that vehicles meet all safety standards, and eliminating vehicle defects that pose an unreasonable risk to safety.

Our research and rulemaking priorities concentrate on finding the areas of highest risk where new or amended vehicle standards can make a significant impact on reducing the death toll on our nation’s highways.  In 2012, there were 5.6 million police-reported crashes in America, and tragically, 33,561 Americans died in fatal crashes.  Because we know that most fatal crashes are caused by human behavior, and we know that vehicles are driven and controlled by humans who will make errors, we must continue to find more ways to protect drivers and passengers when crashes happen.  NHTSA’s regulation of occupant crash protection has resulted in significant improvements in the crashworthiness of today’s vehicles.  These standards have saved many thousands of lives and prevented countless injuries.  Highway fatalities over the past five years are at lows not seen since 1950.  NHTSA has also used its vehicle crash ratings to inform consumers and motivate vehicle manufacturers to voluntarily improve the safety of their vehicles above the federal standards.  This New Car Assessment Program (NCAP), known generally as the government’s 5-star safety rating program, has been an overwhelming success in driving improvements in vehicle safety.  NHTSA was the first vehicle safety agency in the world to implement such a program.  Today, these programs have been implemented around the world.

Fatal crashes where a vehicle problem is a cause or contributing factor are relatively rare in comparison to crashes caused by human factors in properly functioning vehicles.  But such cases receive significant scrutiny because NHTSA requires that automakers sell vehicles that meet specific safety standards and that they find and fix defects as soon as they are aware of them.  As a result, we invest significant effort to find those problems through NHTSA’s vehicle safety enforcement program. 

For vehicles and vehicle equipment in the U.S., manufacturers must certify that their products meet applicable Federal Motor Vehicle Safety Standards (FMVSS).  The Office of Vehicle Safety Compliance (OVSC) tests a sample of new vehicles and equipment each year to determine whether they meet those standards.   If the vehicles or equipment do not comply, manufacturers must recall them and provide a remedy to the consumer.

The Office of Defects Investigation (ODI) has a different mission.  ODI searches through consumer complaints, manufacturer data, data from NHTSA’s National Center for Statistics and Analysis (NCSA), special crash investigations, and other sources for information that might indicate the presence of a defect or defect trend.  Where it can find a possible defect or defect trend posing an unreasonable risk to safety, it investigates.  If NHTSA can demonstrate that a defect exists and that it poses an unreasonable safety risk, the agency can order a recall. 

NHTSA’s ability to influence or order recalls is its greatest strength in safeguarding against problems in the vehicles traveling our roads today.  Since 2000, NHTSA has influenced, on average, the recall of nearly 9 million vehicles every year, as well as millions of items of equipment, for safety related defects.

An Overview of the Defects Investigation and Recall Process 

Defects Investigations

Each potential defect investigation is unique and dependent on the data gathered in each case.   NHTSA uses a number of tools and techniques to gather and analyze data and look for trends that warrant a vehicle safety investigation, and possibly a recall.  These tools include customer complaints to NHTSA, early warning data, as well as other sources that might provide related information, such as crash investigations and industry-related websites.  Additionally, the law requires manufacturers to inform NHTSA within five business days of any noncompliance or defects that create an unreasonable risk to safety. They are then required to initiate a recall to remedy the defect and notify affected consumers.

NHTSA’s defects investigation office, ODI, has a staff of 51 people.  Their goal is to find possible defects or defect trends that may indicate significant safety risks in particular makes, models, and model years; determine whether there is an unreasonable safety risk apparently being caused by a defect; and, if so, persuade—or require— the manufacturer to conduct a recall.  The staff also performs other important functions, such as responding to inquiries and tracking the hundreds of recalls that occur each year.  That entails monitoring quarterly reports on completion rates, ensuring the scope of the recalls is correct, and compiling information on recalls for the public.

The defects investigation process begins with the screening of incoming information for evidence of a potential safety defect.   Complaints from consumers are the primary source of information.   NHTSA receives over 45,000 complaints a year through SaferCar.gov and the Vehicle Safety Hotline, and reviews each one promptly.  Human eyes review every single complaint.  Follow-up is sometimes required to get additional information, and in cases of interest, NHTSA staff will contact the complainants directly to obtain clarifying information.  Screeners also look at technical service bulletins issued by manufacturers, reports of foreign recalls, crash investigations done by NHTSA’s Special Crash Investigations office, and supplemental information such as occasional reports from insurance companies and information available on the Internet.  When appropriate, the screeners consult NHTSA’s crash databases, including the Fatality Analysis Reporting System (FARS) and National Automotive Sampling System (NASS).  Also, members of the public may file petitions asking NHTSA to investigate and order a recall on a particular matter.  The agency carefully reviews each petition before making a decision on whether to grant or deny it.  If granted, a formal investigation is opened. Since 2004, the agency has opened 980 investigations.  These safety defect investigations have resulted in 1,299 recalls involving more than 95 million vehicles, equipment, tires, and child restraints, which have helped reduce vehicle fatalities to historic lows.  For example, a NHTSA investigation recently led to the recall of over 4 million child safety seats and is still underway regarding the possible recall of infant seats.

Another important source of information is Early Warning Reporting (EWR) data submitted quarterly by manufacturers of vehicles, tires, and child seats.   For light vehicle manufacturers, the data include counts of property damage claims, warranty reports, consumer complaints, and field reports, which are efforts by the automaker to look into specific incidents.  These aggregate data are broken down by make, model, and model year and by component category (e.g., steering, braking, engine, speed control).   Manufacturers must also submit brief reports on each claim against the company for death or injury allegedly related to a possible vehicle defect.  The volume of the data received is enormous.  NHTSA uses sophisticated data mining techniques to identify trends in the data that may be evidence of a safety defect. When potential trends are found, the EWR division can make a referral to the team involved in the screening process.

Those who screen NHTSA’s various sources of information are in constant communication and support each other in their efforts to identify potential defect issues.  When patterns emerge from any source, the screeners look very carefully at what may be behind the patterns.   Where there is possible evidence of a defect trend, the screening staff recommends that the appropriate investigating division consider opening an investigation.   ODI staff meets regularly to determine which recommendations warrant opening an investigation and which may warrant continued monitoring.   With preliminary evidence and 16 investigators, ODI must analyze all of the fact patterns and discern whether potential defects likely involve more serious risks or are likely to reveal a defect trend.

If it is determined that an investigation is warranted, a preliminary evaluation begins.   This often entails detailed interviews with complainants, requesting relevant information from the manufacturer, and analysis to determine whether there is sufficient evidence either to seek a recall or continue to a more in-depth investigation.  If it is determined that sufficient evidence exists, the next stage is the engineering analysis, which involves gathering additional information from consumers and the manufacturer, perhaps testing of vehicles or equipment by NHTSA’s Ohio based test facility, surveys of peer vehicle experience, and further in-depth analysis of the underlying problem. 

If, at any stage, ODI staff believes there is enough information to determine that a specific defect exists and that it creates an unreasonable risk to safety, they urge the manufacturer to conduct a recall.  Where the manufacturer is not persuaded by NHTSA to undertake a recall, NHTSA’s Associate Administrator for Enforcement may issue an initial decision requiring that the manufacturer conduct the recall.   Following the initial decision, NHTSA convenes a public meeting in which interested parties—including the manufacturer, consumers, suppliers, public interest groups—may provide testimony.   The manufacturer is given another opportunity to submit comments on the testimony heard at the public meeting.  If, after review of all the information generated by the administrative process, the Administrator concludes that a recall should occur, the Administrator issues a recall order.  A recall order is not self-enforcing.  If the manufacturer does not follow the order, NHTSA would seek enforcement.  To prevail in court, NHTSA must be able to prove that a defect exists and that the defect creates an unreasonable safety risk. 

Manufacturers generally adhere to their legal duty to identify non-compliance or safety defects and initiate recalls, but the NHTSA investigation process helps to ensure that these steps are occurring and to recognize when they are not.  Over the last 10 years, manufacturers have recalled more than 83 million vehicles for safety defects where NHTSA has not investigated, and have recalled over 86 million additional vehicles based on NHTSA’s defect investigations.   No other country has a defects investigation program of this scope.

Recalls

When a manufacturer recalls a vehicle at NHTSA’s urging during or after an investigation, we call it an “influenced recall.”  Whether a recall is influenced or not, the recall process is the same.  When a manufacturer recalls a vehicle model or vehicle equipment, the manufacturer files a defect information report with NHTSA under 49 CFR Part 573, known in the industry as a “573 Report.”  Certain information is required in the report under 49 CFR 573.6(c), including, for example, identification of the line of vehicles or vehicle equipment under recall, the number of affected vehicles or pieces of vehicle equipment, a description of the defect, and a description of the remedy. 

The regulations require manufacturers to submit the 573 report within five business days of their determination that a defect is safety related.  For this reason, the 573 report must also include a chronology of events that led to the recall decision.   NHTSA reviews every recall to ensure that the manufacturer has met its obligation to inform the agency of safety-related defects or to make a timely decision that its products contain a safety defect.  If indications show that it has not, NHTSA may open another investigation called a Timeliness Query (TQ) to collect additional relevant information.  This Administration has placed an emphasis on timeliness in order to safeguard the integrity of the process and encourage automakers to aggressively pursue potential safety defects.  Since 2009, automakers have paid record fines totaling more than $85 million for lack of timeliness in reporting vehicle safety defect issues to NHTSA.  Because of this emphasis, we believe that all manufacturers in the automobile industry are now paying much closer attention to their responsibility to protect their customers and the driving public.                                                                                                                                            

Upon receipt of a 573 report, NHTSA enters it to NHTSA’s Artemis database as ODI investigators screen it for completeness, proper scope, timeliness, and effectiveness of the proposed remedy.  NHTSA sends an acknowledgement letter and recall summary to the manufacturer, requesting the manufacturer to supply any missing information.  NHTSA posts each new recall on its website at SaferCar.gov.

Under 49 CFR Part 577, manufacturers are required to notify owners of vehicles and vehicle equipment under recall.  The “577 letter” must state that the manufacturer has determined that there is a safety defect in a vehicle or piece of vehicle equipment that the consumer owns.  It must provide information about where and when a remedy to the defect can be acquired, and it must inform the consumer that the remedy will be provided by the manufacturer free of charge.

The manufacturer must then track how many of the items under recall receive the remedy (“recall completion”) and report the numbers to NHTSA for six quarters.  NHTSA uses these numbers to later calculate a completion rate analysis and work with manufacturers where the completion rate is below average.

We believe our defects investigation program and recalls process has functioned extremely well over the years in identifying defects that create unreasonable risks and ensuring that recalls occur whenever appropriate.  Even so, we continually seek ways to improve.  In 2011, the Department of Transportation’s IG reviewed the ODI investigation process and issued 10 recommendations for improvement. In response to actions taken and/or information provided by the agency, the IG has closed nine of the 10 recommendations and we are in the process of finalizing our report to the IG addressing the remaining recommendation which concerns developing a staffing model.  A list of the recommendations is attached (Attachment 1).

In addition to implementing the IG recommendations, ODI has taken steps to further improve its ability to find defects. One recent improvement is the deployment of a new Business Intelligence and Natural Language Processing suite focused on our consumer complaints, which helps supplement the human review process and has expanded our ability to harvest data and identify defect trends.  Even after implementing this software and all of the IG’s recommendations, we will continue to look for ways to make our processes more effective.

An Overview of NHTSA’s Special Crash Investigation (SCI) program

NHTSA’s Special Crash Investigations (SCI) Program provides in-depth crash data ranging from basic information obtained from routine police and insurance crash reports to comprehensive data from reports by professional crash investigators. Hundreds of data elements relevant to the vehicle, occupants, injury mechanisms, roadway, and safety systems involved are collected for each of more than 130 crashes studied annually.

SCI investigations are quite different from ODI defects investigations.  While defects investigations look for defect trends in a line of vehicles or vehicle equipment, SCI investigations provide data and observations associated with a specific incident that are useful for examining new, emerging, and rapidly changing technology, including the safety performance of alternative fueled vehicles, child safety restraints, adapted vehicles, safety belts, air bags, vehicle-pedestrian interactions, and potential safety defects.  SCI investigators locate and analyze unique real-world crashes to generate data that can be used to improve the performance of automotive safety systems.  This information may be helpful to NHTSA’s research and rulemaking offices in considering possible new or amended standards, to ODI in considering whether to investigate an issue or in support of an ongoing investigation, or to industry and other interested observers.  Cases of interest are selected from a diverse network of sources, including NHTSA's Auto Safety Hotline, the Department of Transportation's National Response Center, NHTSA's regional offices, NASS FIELD Offices, automotive manufacturers, other government agencies, law enforcement agencies, engineers, and medical personnel.

Professional crash investigators obtain data and take photographs of the crash sites. They locate the vehicles involved, photograph them, measure the crash damage, and identify interior locations that were contacted by the occupants, and if equipped, obtain the Event Data Recorder (EDR) data for evaluating safety system performance. The investigators follow up their on-site investigations by interviewing crash victims and other involved parties, and by reviewing medical records to determine the nature and severity of injuries. Each investigation provides extensive information about pertinent pre-crash, crash, and post-crash events involving the occupants, vehicles, rescue, and environmental factors, which may have contributed to the event's occurrence or severity. Included in each report is an analysis and determination of the occupant kinematics and vehicle dynamics as they occurred throughout the crash. The reports provide detailed performance evaluations of the air bag, the use of seat belts, and any other safety features.

NHTSA and DOT’s Current Efforts on GM’s Recall

GM’s Recall

GM reported this defect and initiated its recall on February 7, 2014.  As of March 28, 2014, the GM recall currently covers approximately 2.1 million vehicles, including the 2005-2007 Chevrolet Cobalt, 2007 Pontiac G5, 2003-2007 Saturn Ion, 2006-2007 Chevrolet HHR, 2006-2007 Pontiac Solstice and 2007 Saturn Sky vehicles. NHTSA is working to ensure that GM has accounted for the full scope of vehicles that may be covered by the recall, is ensuring that consumers receive the needed remedy as soon as possible, and is providing consumers information and resources essential to keep them safe until the vehicles can be fixed. GM has indicated to dealers that it expects to have parts on or about April 7 and will notify consumers that it can begin scheduling repairs soon after that date.  Given the number of vehicles, the repairs may take several months to be completed.

At this time, NHTSA urges owners and drivers to follow GM’s recommendation to “use only the ignition key with nothing else on the key ring” when operating the vehicle, contact GM about added resources available to keep themselves safe, and seek the permanent repair remedy from GM as soon as replacement parts become available.

NHTSA’s Timeliness Investigation

GM first provided NHTSA a chronology of events on February 24, 2014.  The information in GM’s chronology raises serious questions as to the timeliness of GM’s recall.  As a result, on February 26, NHTSA opened its present investigation, a timeliness query.  On March 4, to obtain more detailed information than GM provided in its recall notification letter, NHTSA issued a special order seeking answers and documents, submitted under oath, to questions relevant to how quickly GM acted on information about the defect.  GM’s response is due to NHTSA on April 3.

NHTSA is a data driven organization and we will take whatever action is appropriate based on our findings, including issuing civil penalties of up to the statutory limit of $35 million.

NHTSA and DOT’s Processes 

NHTSA and DOT’s Office of General Counsel (OGC) are currently engaged in a continuous improvement and due diligence process regarding past efforts on airbag non-deployments in GM vehicles under its ignition switch defect recall.  Secretary Foxx recently requested the Department of Transportation Inspector General to initiate an agency audit in connection with the GM recall.  These efforts will ensure that DOT and NHTSA have a full understanding of the facts regarding the GM recall and can take corrective actions to enhance NHTSA’s safety function to the extent necessary and appropriate. These processes will also benefit from any findings from NHTSA’s timeliness investigation, which may shed light on what additional information NHTSA could have had in evaluating airbag non-deployments in this case.

NHTSA’s Past Efforts on Airbag Non-Deployments in the GM Vehicles

NHTSA’s timeliness investigation and joint due diligence review with OGC are ongoing, and the DOT OIG audit is pending, so any understanding of NHTSA’s past efforts is preliminary at this time. We are not aware of any information to suggest that NHTSA failed to properly carry out its safety mission based on the data available to it and the process it followed. NHTSA examined the available information multiple times using consumer complaints, early warning data, special crash investigations, manufacturer information about how air bags function, and other tools, but did not find sufficient evidence of a possible safety defect trend that would warrant opening a formal investigation.  This was a difficult case pursued by experts in the field of screening, investigations and technology involving airbags that are designed to deploy in some cases but not others. GM had critical information that would have helped identify this defect.

What follows is an outline of our current understanding of NHTSA’s past efforts and related background information.

Background on Advanced Airbags

Airbags are a vitally important, supplemental restraint system used to mitigate injuries and death in the event of a crash.   The term “supplemental” is used with regard to airbags because it enhances the protection of the seat belts, which are the primary occupant restraint system in a vehicle.  NCSA estimates that in 2012, 2,213 lives were saved by frontal air bags, adding to the estimated 12,174 lives saved by seat belts. Between 1986 and 2012, frontal air bags are estimated to have saved almost 37,000 lives.

Advanced airbags are not intended to deploy in all crashes, even frontal crashes.  Advanced airbag systems are designed not to deploy when doing so will cause more harm than good.  Smaller occupants who sit closer to the airbag are at risk as are unrestrained occupants, because those occupants will move closer to the airbags during the course of a crash, putting them at risk of being hit with the force of a rapidly expanding bag.  Airbags also may not deploy during crashes that occur off-road with multiple minor impacts because such minor impacts involve much slower changes in speed than on-road vehicle-to-vehicle crashes. Even on-road, airbags may not deploy if the crash was not severe enough to warrant the supplemental protection.

Advanced airbags began to be introduced in the 2004 model year in response to a May 2000 NHTSA rule intended to reduce injuries and deaths resulting from previous airbag designs.  These prior designs presented risks to smaller occupants and infants in rear-facing car seats placed on the front passenger seat.  Advanced airbags factor in additional data to determine when to deploy, such as the size of the individual, the change in velocity, location of the individual within the vehicle, and whether the occupants are belted.

Special Crash Investigations Regarding Vehicle Subject to the GM Recall

The Model Year (MY) 2005 Chevrolet Cobalt was among the first vehicles equipped with advanced airbag features, although the Cobalt’s advanced airbag system was not certified as such by GM until 2006.  

In 2005, a fatal crash in Maryland came to the attention of our SCI team. SCI investigated the Maryland accident as well as two others involving MY2005 Cobalts, one in Wisconsin in 2006 and one in Pennsylvania in 2009.  All three crashes, tragically, resulted in the deaths of unrestrained occupants.  All three also involved airbags that did not deploy and event data recorder (EDR) information indicating the vehicle power was in an accessory position.  (When a vehicle is an accessory position, certain features, or accessories, such as the radio are powered, but others remain off to prevent the vehicle’s battery from being drained.)  The 2005 and 2006 crashes involved vehicles exiting the roadway and striking trees. The 2009 crash involved being struck by an oncoming vehicle in the wrong lane.

Office of Defects Investigation Activities Regarding the Subject Vehicles

As the SCI team examined these individual crashes, NHTSA reviewed other sources of available data to determine whether a problem existed related to airbag non-deployment in certain GM vehicles.  In particular, NHTSA’s early warning division (EWD) collected and reviewed available data on airbag non-deployment in Cobalts.  After receiving early warning data from GM, and searching through available information sources, EWD identified 43 incidents where airbags may not have deployed in a crash.  As a result, in 2007, EWD referred the case to NHTSA’s data analysis division (DAD) for further screening.

Following this referral, DAD reviewed data on non-deployment of airbags in the Cobalt and Ion.  In connection with this evaluation, DAD considered a variety of sources of data, including complaints concerning alleged non-deployments and available information concerning the relevant special crash investigations described above.  During the course of this evaluation, NHTSA brought the airbag non-deployment issue to the attention of GM on at least one occasion.

A defects assessment panel convened in 2007 to review the available information on non-deployment of airbags in the Cobalt and Ion, considering vehicle owner questionnaire (VOQ) complaints reporting non-deployments, early warning data, SCI investigations, and the circumstances of the crashes.  The data available at the time of this evaluation did not indicate a safety defect or defect trend that would warrant the agency opening a formal investigation.  In particular, the available data did not indicate that the Cobalt or Ion were overrepresented compared to other peer vehicles with respect to injury-crash incident rates (Figure 2).  Moreover, the crash data available to NHTSA included incidents involving unbelted occupants and off-road, long-duration events, where it could not be determined that the air bag should have deployed.    

Figure 2. 2007 NHTSA Chart of Airbag Non-Deployment Injury-Crash Incident Rates

Against this backdrop, NHTSA continued to monitor the performance of the Cobalt in frontal crashes, including EWR information, consumer complaints, and one additional SCI report.  Again in 2010, NHTSA reviewed cumulative data on consumer complaints for data the airbag non-deployment rate of Cobalts (Figure 3).  The data showed that the injury-crash incident rate for Model Year 2005 and 2006 Cobalts had decreased by nearly half since the 2007 review and did not provide a basis for a formal investigation.

At the time of these reviews, NHTSA did not have the information that GM has since provided—for instance, new evidence linking airbag non-deployment to faulty ignition switches—which is why we have launched an aggressive investigation into the timing of their recall. 

Figure 3. 2010 NHTSA Chart of Airbag Non-Deployment Injury-Crash Rates

Critical Issues Regarding ODI Work and the Subject Vehicles

In evaluating the potential for a defect or defect trend, ODI relies on expertise regarding the technology and the dynamics of the incidents involved. In this case, ODI was looking for a defect or defect trend regarding airbag non-deployment in circumstances where it appeared a deployment should have occurred.   At the time, ODI did not have clear evidence of a connection between the ignition switch being in the accessory mode and the airbag non-deployment.

Our understanding at the time was that airbag systems were designed to continue to function in the event of power loss during a crash, which is not uncommon. ODI’s understanding of airbag systems, which was verified by available GM service literature reviewed during our due diligence effort, was that an airbag system would be armed and ready to fire for up to 60 seconds after all power to the system was cut off.   At the time ODI was evaluating whether to open an investigation, the two SCI reports showed indications of power loss and identified the vehicle power mode as accessory. The preliminary SCI report on the 2006 Wisconsin crash did identify the issue of the ignition switch being in the accessory position, raising the possibility of an issue, but concluded that, “At this point, it appears the yielding of the tree may have been the likely cause of the non-deployment.”   The final report produced in 2008 identified both the yielding nature of the impact and power loss due to movement of the ignition switch prior to impact as potential causes of non-deployment, but removed any conclusion as to which was the likely cause.  However, due to the timing of the report and investigation, the final version of the report was not complete prior to the determination of whether or not to open an investigation.

As noted previously, advanced airbags are designed to deploy in some cases, but not in others. The two SCI cases used in making the 2007 determination of whether or not to open an investigation included unrestrained occupants in vehicles that exited the roadway and struck yielding objects before rapidly decelerating and coming to rest. These situations, where unrestrained occupants may be out of position, are instances where airbags are less likely to deploy because doing so may harm the occupants.

When data available to NHTSA reveals a basis to investigate a potential risk to motor vehicle safety, the agency takes decisive action.  Over the last 10 years, NHTSA investigations have influenced 35 recalls related to airbags involving 6.5 million vehicles, including 18 recalls of 3.5 million vehicles specifically involving non-deployment.  In those cases, information available to NHTSA demonstrated the need to investigate.

In February 2014, GM submitted information to NHTSA that, for the first time, acknowledged a link between the ignition switch to the airbag non-deployment, as well as key information regarding parts changes, discussions with suppliers, and other efforts currently under consideration in our Timeliness Query.  Had the information newly provided to NHTSA by GM been available before now, it would have better informed the agency’s prior reviews of airbag non-deployment in GM vehicles and likely would have changed NHTSA’s approach to this issue.  

Conclusion

NHTSA’s dedicated and professional staff works to monitor and secure the safety of the U.S. automotive fleet.  The work that they do saves lives on a daily basis, and the importance of that work cannot be overstated.  NHTSA continually seeks new ways to improve our processes. We are reviewing the events leading up to this recall to see if there areas that can be improved.  We are looking to improve our understanding of the way that various manufacturers design airbags to function when the vehicle loses power, considering whether we need to improve the use of Special Crash Investigation (SCI) in our defects screening process, reviewing ways to better incorporate information about remote defect possibilities into the investigative process, and evaluating our process for engaging manufacturers around issue evaluations.

I greatly appreciate the opportunity to testify before you today. I believe it is important that the Members, and the American public, have a better understanding of the vitally important safety work that we do at NHTSA.  I look forward to your questions.

 

Attachment #1

Office of Inspector General Audit Report:

PROCESS IMPROVEMENTS ARE NEEDED FOR IDENTIFYING AND ADDRESSING VEHICLE SAFETY DEFECTS

National Highway Traffic Safety Administration

Report Number: MH-2012-001

Date Issued: October 6, 2011

RECOMMENDATIONS

We recommend that the National Highway Traffic Safety Administrator:

1. Revise the pre-investigation processes to ensure that the review of each complaint is recorded and that complaints are tracked to associated investigations in Artemis.

2. Establish pre-investigation processes for retaining and storing pre-investigation records, such as investigation proposals and insurance company data.

3. Require that decisions made and actions taken by ODI Defect Assessment Panels are recorded, including justifications for not proceeding to investigations.

4. Establish systematic processes for determining when a third-party or the Vehicle Research Test Center should be used to verify manufacturer information or assist in identifying a potential defect.

5. Revise the ODI investigation process to require justifications for continuing or closing investigations that exceed timeliness goals for PEs and EAs.

6. Revise the ODI investigation process to establish criteria for documenting evidence, such as associated complaints, meetings with manufacturers and other stakeholders, and third-party analysis or testing conducted.

7. Strengthen ODI’s redaction policy and process to better protect consumers’ personal information from public availability, such as by using automated redaction software.

8. Conduct a workforce assessment to determine the number of staff required to ensure that ODI meets its objectives and determines the most effective mix of staff.

9. Develop a formal training program to assist ODI staff in acquiring the knowledge and staying abreast of ODI processes and current and new automobile technologies.

10. Develop and implement a strategy for increasing coordination with foreign countries to enhance ODI’s ability to identify safety defects and to exchange information on foreign recalls.

 

Automated Speed Enforcement

STATEMENT OF

MICHAEL GERACI
DIRECTOR, OFFICE OF SAFETY PROGRAMS
NATIONAL HIGHWAY TRAFFIC SAFETY ADMINISTRATION

Before the

SUBCOMMITTEE ON HIGHWAYS AND TRANSIT
COMMITTEE ON TRANSPORTATION AND INFRASTRUCTURE
UNITED STATES HOUSE OF REPRESENTATIVES

JUNE 30, 2010

Chairman DeFazio and Members of the Subcommittee, I am pleased to be here today to represent the Department of Transportation on the very important safety issue of automated speed enforcement. 

While the number and rate of traffic deaths have decreased significantly in recent years, motor vehicle crashes remain a serious national health problem and a leading cause of death for young Americans.   The National Highway Traffic Safety Administration (NHTSA) is committed to reducing the motor vehicle crash toll and considers every available evidence-based strategy for reducing roadway risk.  Automated traffic enforcement technology is one such strategy, with evidence of effectiveness in reducing risks from speeding and red light running.  

Speeding is one of the most prevalent factors contributing to traffic crashes.[1]  In 2008, speeding was a contributing factor in 31 percent of all fatal crashes and was associated with more than 11,000 fatalities.  NHTSA estimates that speeding-related crashes cost more than $40 billion each year.

Of all drivers in fatal crashes, young males are most likely to have been speeding.  In 2008, 37 percent of male drivers between 15 and 24 years of age who were involved in a fatal crash were reported to have been speeding at the time of the crash.  The great majority - 88 percent in 2008 - of speeding-related fatal crashes occur on roads other than Interstate highways.

A NHTSA study of fatal intersection crashes indicates that an average of about 38 percent of such events at signal-controlled intersections involved at least one driver who ran a red light.[2]   On average, intersection crashes involving red light running result in about 1,000 deaths per year.  The age distribution of drivers who ran a red light in a fatal crash differs from that of speeding-related crashes, with drivers 65 years of age and higher making up about 11 percent of all drivers in two-vehicle intersection crashes, but accounting for 18 percent of those who ran red lights.

Research indicates that automated enforcement systems can result in measurable safety improvements in high-crash locations.[3]  A NHTSA review of thirteen international evaluations of automated speed camera enforcement systems and seven evaluations of automated red light camera systems indicates generally positive effects from these systems.    

Several studies of fixed-camera speed enforcement systems indicate 20 to 25 percent reductions in injury crashes, while studies of mobile systems indicate reductions of injury crashes from 21 to as high as 51 percent. 

Studies of red light running camera systems indicate reductions in overall crashes, angle crashes and red light running crashes by as much as 30 to 50 percent, but show slight increases in rear end crashes.  

Based on available evidence, NHTSA believes that, when appropriately used as one component of an overall traffic safety and law enforcement system, automated enforcement programs can be an effective countermeasure for reducing crashes at high risk locations..  Automated enforcement systems do not replace the need for traditional enforcement operations, but provide an effective supplement when used as part of a comprehensive strategy for reducing traffic crashes. 

NHTSA and the Federal Highway Administration have developed operational guidelines to assist States and communities in designing and implementing effective automated speeding and red light running systems.[4]  These guidelines are based on program evaluations and documented successful practices in communities across the Nation.  The guidelines stress the importance of integrating automated enforcement in a comprehensive system that includes problem identification, appropriate legal authority, coordination with the courts, public education, communications and community support.  The guidelines also address critical automated enforcement operational elements such as enforcement thresholds, the use of fixed and mobile units, overt and covert deployment strategies, signage, and days and hours of operation.

NHTSA encourages adoption of these automated enforcement guidelines through speed management workshops.  These workshops encourage a comprehensive approach to community speed management, including incorporation of automated enforcement where appropriate.  The workshops involve the active participation of the full range of local partners, including highway engineers, law enforcement officials, prosecutors, judges, and safety advocates.  The agency has conducted nine of these workshops, reaching 46 states.   

Speeding and red light running are serious safety problems and NHTSA is committed to identifying and advancing effective solutions.  We will continue to examine the effectiveness of promising countermeasures, including automated enforcement systems, and work closely with States to encourage the adoption of effective programs to help improve safety for all road users.     

I would be pleased to answer any questions you may have.


[1] NHTSA, Speeding, Traffic Safety Facts, 2008 Data, DOT HS 811 166

[2] NHTSA, Analysis of Fatal Motor Vehicle Traffic Crashes and Fatalities at Intersections, 1997 to 2004, February 2006, DOT HS 810 682

[3] NHTSA, Automated Enforcement: A Compendium of Worldwide Evaluations of Results, September 2007, DOT HS 810 763

[4] US Department of Transportation, Speed Enforcement Camera Systems Operational Guidelines, March 2008, DOT HS 810 916

Pilot Fatigue

STATEMENT OF

MARGARET GILLIGAN,
ASSOCIATE ADMINISTRATOR FOR AVIATION SAFETY,
FEDERAL AVIATION ADMINISTRATION,

BEFORE THE

HOUSE OF REPRESENTATIVES,
COMMITTEE ON TRANSPORTATION AND INFRASTRUCTURE,
SUBCOMMITTEE ON AVIATION,

ON

PILOT FATIGUE,

SEPTEMBER 16, 2010.

Chairman Costello, Congressman Petri, Members of the Subcommittee:

Thank you for inviting me to appear before you this morning to discuss the Federal Aviation Administration’s (FAA) efforts to mitigate the impacts of pilot fatigue to enhance aviation safety.  Updating FAA’s regulatory requirements on pilot fatigue has been a high priority for Secretary LaHood and Administrator Babbitt. As you know, Administrator Babbitt was formerly a commercial pilot, so his interest in and insights about pilot fatigue have been longstanding, and were helpful in making rulemaking on this matter an Administration priority.  Their assistance and guidance on this matter have been invaluable.  I am pleased that their focus has enabled the FAA to publish a Notice of Proposed Rulemaking (NPRM) on September 14, 2010, that proposes changes to the current flight duty and rest regulations.  The NPRM represents a comprehensive proposal that is the result of extensive outreach to the aviation industry, labor and the scientific community.  Unlike the existing requirements, the proposal would establish a single, scientifically-based regulatory approach for all Part 121 operators, including domestic and international passenger and cargo operations, as well as supplemental carriers.

While the publication of this NPRM is a huge step forward, I want to stress that it is the latest step in a long history of FAA efforts to mitigate fatigue.  We held symposia on fatigue and worked with aviation industry and the scientific community to gather data to meet the scheduling demands of the industry (including ultra long-range flights), without compromising safety.  As the science of fatigue matured, we worked to educate the industry to mitigate risks as they were identified.  The new proposal reflects our drive to reach consensus across different facets of the aviation industry.

In the past, I have said something that is worth repeating now: regardless of what regulatory framework is in place, mitigating the effects of fatigue is a shared responsibility.  The FAA has the responsibility to put the framework in place.  The air carrier has the responsibility to schedule its flight crews responsibly and in accordance with that framework.  The pilot has the ultimate responsibility to use the hours set aside for rest to actually rest, to report for duty in a fit condition, and to notify the airline when he or she is too fatigued or otherwise not fit for duty.  Nothing about the latest proposal changes those basic responsibilities.

In the aftermath of the Colgan Air Flight 3407 accident in February 2009, the FAA placed great emphasis on all safety factors that either were, or could have been, a contributing cause to the accident.  Secretary LaHood and Administrator Babbitt issued an Airline Safety Call to Action for the foremost aviation safety experts to discuss the best ways to make an already safe industry even safer.  Fatigue was clearly a factor of some concern, given that one member of the Colgan flight crew commuted from the West Coast prior to reporting for duty and the evidence suggested that she may not have had sufficient rest.

In addition to the Call to Action, Administrator Babbitt convened an Aviation Rulemaking Committee (ARC) comprised of representatives from airline management and pilot labor unions to review fatigue-related issues and to make specific scientifically-based recommendations that could be the basis of rulemaking.  The ARC delivered its report and recommendations in September 2009.  The report and recommendations reflected consensus on many issues, but there were a handful of issues where the ARC did not reach consensus.  In addition, the ARC was not charged with performing any type of economic analysis, which the FAA must provide in any rulemaking initiative. 

The NPRM utilizes accepted assumptions as to what causes fatigue and creates a framework that addresses those risks.  For example, it is generally accepted that higher levels of activity cause more fatigue and that most people need eight hours of sleep in a 24 hour period in order to perform effectively and remain alert.  It is also acknowledged that an average person needs in excess of nine hours of sleep in order to recover from accumulated sleep deprivation and the quality of the sleep an individual gets is usually affected by the time of day in which it occurs, with nighttime sleeping being more restorative.

Using these assumptions as a basis, the NPRM focuses on the nature of the operation.  During a duty period, how many take-offs and landings does the pilot fly?  Do the operations involved cross time zones and, if so, how many?  Are the operations during the day or at night?  The proposal recognizes that basing hourly restrictions solely on the total number of hours of duty time or flight time does not have as much meaning as factoring in what kind of operations were being flown during that period.  Different operations result in different fatigue levels and that reality must be recognized in any new regulatory framework.

The NPRM would impose requirements for rest, flight time, and duty time.  There is a proposed nine hour rest requirement prior to flying related duty.  In addition, flight time restrictions include limits for every 28-day period, as well as annual limits.  The flight time restrictions also reflect all operations flown for the carrier by the pilot, even if some of those flights are ferrying operations or other flights not flown under Part 121.  Finally, both the flight time and duty time restrictions proposed would reflect differences in the types of operations flown as well as when they are flown, and require shorter duty periods for certain times of day and quantities of takeoffs and landings.   

The proposal would also gives carriers the option of integrating a Fatigue Risk Management System (FRMS) into their scheduling systems.  FRMS is a carrier-specific method of evaluating how best to mitigate fatigue, based on active monitoring and evaluation by the carrier and flightcrew members.  In this case, the carrier would model its schedules to determine where there may be risk from fatigue.  The carrier would develop mitigation strategies to eliminate or mitigate that risk.  The FAA will determine that the FRMS provides an equivalent level of protection as afforded by the rule and approve the carrier’s system.  FRMS were strongly supported by both labor and management in the ARC, because it ensures that each schedule is analyzed and proper mitigation is implemented.

This approach has the potential to provide a cooperative and flexible means of monitoring and mitigating fatigue during operations when the prescriptive approach is not optimal.   We are seeking public comments about how best to realize that potential.  An FRMS requires a carrier to develop numerous processes and structures within an operation.  These measures lead to effective management and mitigation of fatigue on the part of both the carrier and its employees that might affect the operation.

One area that I know is of great interest to this Committee is pilot commuting, which our NPRM discusses in the preamble.  The ARC made no recommendation on commuting.  However, the ARC did point out that pilots are required to report to work fit for duty; and that means rested.  Although our proposal does not include specific restrictions on commuting, it does make some modifications to ensure that all pilots, including those who commute, are meeting the existing requirements to report fit for duty.

As I noted at the beginning of this statement, pilot personal responsibility is critical to whatever fatigue rule is ultimately adopted, whether or not commuting restrictions are imposed.  Pilots must commute responsibly, but this proposal broadens that responsibility to include the air carrier, who must be aware of how pilots are commuting to work and must make a determination that each pilot is fit for duty.  It is unreasonable to assume that a pilot is resting while commuting, either locally or long distance, and our proposal requires air carriers to consider the commuting times pilots needs to reach their home base while still receiving the required opportunity for rest.  It also calls on co-workers – other crew members, dispatchers, etc. – to determine that pilots they’re working with are fit for duty.  We believe mandating this shared responsibility will address the risks posed by a pilot failing to identify that he or she is not sufficiently rested – and therefore not fit for duty.

Finally, one of the most challenging issues we have had to resolve in order to move forward with a new fatigue regulatory proposal is that of the costs associated with a new rule compared with the benefits that are expected to accrue from a new requirement.  All of us in government and industry associated with aviation are dedicated to enhancing aviation safety.  This is what we work for day in and day out.  At the same time, we seek to ensure that rules do not impose excessive, unjustified, or unnecessary costs on airlines, airline employees, and consumers.  We are required to provide the public with information about the projected costs and benefits associated with any regulatory proposal.  Reducing fatigue, through whatever means, may result in the carriers having to add more pilots to comply with new standards, thus adding costs.  We believe, however, that carriers will optimize their crew schedules within any new regulatory requirements to continue to be as efficient as possible. 

While we prefer and seek out regulatory options that result in net benefits, there is no absolute requirement that monetary benefits of regulatory proposals outweigh monetary costs.  But the benefits, both quantifiable and nonquantifiable, must justify the associated costs.   While we have explicitly sought public comments about possible improvements in the proposed rule, we believe it meets that standard.  It is important to understand that increasing airline safety creates a number of important social benefits, some of which are hard to quantify.

Though producing this NPRM did take longer than we expected, we believe we have a solid starting point for a new and better way forward in this area.  While this is not the last step in this process, I am extremely proud of the FAA team for this achievement.  I would like to thank the many, many members of the Administration, the aviation and labor community, and the scientific community for their tireless efforts to assist Secretary LaHood and Administrator Babbitt in moving forward with the proposed fatigue NRPM.  I would also like to acknowledge the support of Congress and the families of victims of the Colgan accident and other family groups in this area.

There is work to be done in order to make the NPRM ultimately into a final rule,  but I am confident that this comprehensive proposal is a step forward and I look forward to receiving public comments and to working with all interested parties, including this Committee, to finalize improved flight duty and rest standards that will enhance safety because that is our shared ultimate goal.

Thank you for this opportunity to appear before you.  I would be happy to answer any questions at this time.

The Future of Unmanned Aviation in the U.S. Economy Safety and Privacy Considerations

STATEMENT OF

MICHAEL P. HUERTA,
ADMINISTRATOR,
FEDERAL AVIATION ADMINISTRATION,

BEFORE THE

SENATE COMMITTEE ON COMMERCE, SCIENCE, AND TRANSPORTATION,

ON

THE FUTURE OF UNMANNED AVIATION IN THE U.S. ECONOMY; SAFETY AND PRIVACY CONSIDERATIONS,

JANUARY 15, 2014.

Chairman Rockefeller, Senator Thune, Members of the Committee:

Thank you for the opportunity to appear before you today to discuss unmanned aircraft systems (UAS).  This emerging technology has been of great interest to state and federal government agencies, the public, and Congress for the past several years.  Many new technologies have abstract benefits that are sometimes hard to succinctly describe or understand.  UAS have applications that are not only readily understandable, but have the potential for broad benefits for virtually all Americans.  From homeland security, emergency management and law enforcement, to food and package delivery, the potential uses for UAS technology are limitless.  Realistically, neither the technical nor operational capabilities necessary exist today to implement the opportunities described by visionaries, but their promises for 21st century conveniences are compelling.

Meeting the challenges for realizing this potential will take a concerted effort and must achieve the requisite balance of maximizing the technological benefits, while maintaining safety and efficiency of the national airspace system (NAS).  I would like to update you on the Federal Aviation Administration’s (FAA) efforts as we work with government and industry to improve the technologies associated with UAS so that their integration into the NAS can be achieved in a safe and acceptable manner.

It is important to put the integration of UAS into the NAS in its proper context.  The FAA has a history of accommodating new technology into the NAS safely and effectively.  UAS is the latest technology to be developed that FAA is working to integrate.  While FAA’s role in this effort is critical, it is limited to NAS safety and operational efficiency.  As with other manned technologies, FAA’s role does not extend to directing or otherwise limiting the underlying purposes for which the aircraft is used.   Consequently, if a particular UAS operation does not impact the safety or efficiency of the NAS, it is beyond FAA’s authority to enforce or otherwise correct that action.  However, because FAA is uniquely positioned to gather information from our regulated entities, we are committed to sharing pertinent information to better enable the resolution of all issues affecting the use of UAS, even when they are not specifically safety-related.

For example, in November 2013, FAA released a privacy policy that will apply by contract to the UAS test sites that were selected on December 30, 2013.  This will enable interested organizations and government partners to evaluate a broad range of information provided by the work done at the test sites and assess the potential impact of UAS operations on privacy concerns. 

I am very interested in the selection of the test sites and the important work they will be doing, but before getting ahead of myself, I would like to set forth a basic framework for how the FAA will integrate unmanned aircraft into the NAS.  In some ways, unmanned aircraft are inherently different from manned aircraft.  They possess a wider operational range than manned aircraft, with a wider number of different physical and operational characteristics.  Some UAS are the size of a fist, and fly at low altitudes and slow speeds.  Others have glider-like bodies with the wing span of a 737 and can fly above 60,000 feet.  Many can fly and hover longer than manned aircraft.  Their common characteristic, distinguishing UAS from manned aircraft, is that their pilot is on the ground and not on board the aircraft.  This is a very new and different common denominator.

For the last two decades, the FAA has authorized the limited use of unmanned aircraft for important missions in the public interest.  These include firefighting, disaster relief, search and rescue, law enforcement, border security, military training, and testing and evaluation.  About 36 law enforcement agencies operate unmanned aircraft now under certificates of authorization.  Universities also use unmanned aircraft for research into weather, agriculture, and industrial uses. 

FAA estimates that we can expect 7,500 small unmanned aircraft in the NAS over the next five years, provided regulations and operational guidelines/policies are in place to handle them.  We recognize that, while the expanded use of UAS presents great opportunities, integrating them also presents significant challenges.  Operational issues, such as pilot training, must be addressed.  Additionally, we need to make sure that unmanned aircraft can detect and avoid other aircraft and that they operate safely, even if they lose the link to the pilot in command.  Likewise, manned aircraft must be able to detect these aircraft as well.

Our airspace system is not static and it is important for industry to understand that unmanned operations will evolve over time, just as they have over the past decade.  Today, unmanned aircraft are used to keep our borders safe.  They help with scientific research and environmental monitoring.  They support law enforcement agencies and help state universities conduct research. 

As we move forward, the use of small unmanned aircraft is likely to grow most quickly in civil commercial operations.  These UAS are extremely versatile and have relatively low initial cost and operating expenses.  The FAA is working on a proposed rule governing the use of a wide range of smaller UAS, which, in accordance with the roadmap, we expect to issue this year.

FAA’s long term goal of UAS integration will rely on the test sites to answer key questions and provide solutions to the issues noted above, as well as how they will interface with the air traffic control system.  This information will help the FAA to develop regulations and operational procedures for future civil commercial use of UAS in the NAS.

Last year, the FAA, often in consultation with other key government partners and industry stakeholders, issued a number of key documents intended to assist in defining parameters to safely integrate these very diverse systems into the world’s most complex airspace.  The Integration of Civil UAS in the NAS Roadmap outlines, within a broad timeline, the tasks and considerations needed to enable UAS integration into the NAS.  The five year Roadmap, updated annually, provides stakeholders with proposed agency actions to assist with their planning and development.  One concrete achievement facilitated by the roadmap took place in September 2013 when the first commercial flight of an unmanned aircraft took place in the skies above the Arctic Circle.  A Scan-Eagle completed a 36 minute flight to view marine mammals and survey ice.  There are hopes that UAS can be used to meet environmental and safety requirements in the Artic.   The flight was coordinated by Insitu (the UAS manufacturer), Conoco Phillips, and other federal and international agencies.  The Arctic region is the only area to date where we have authorized the use of small unmanned aircraft for commercial purposes.

The UAS Comprehensive Plan was drafted by the Joint Planning and Development Office (JPDO) in coordination with JPDO Board participants from the Departments of Defense (DOD), Commerce (DOC), Homeland Security (DHS), the National Aeronautics and Space Administration (NASA) and the FAA.  It is a document that considers UAS issues beyond 2015, including technologies necessary for safe and routine operation of civil UAS and the establishment of a process to inform FAA rulemaking projects related to certification, flight standards and air traffic requirements.  The Comprehensive Plan details work that has been accomplished, along with future efforts needed to achieve safe integration of UAS into the NAS.  It sets overarching, interagency goals, objectives, and approaches to achieving integration.  Each partner agency will work to achieve these national goals and may develop agency-specific plans that are aligned to the national goals and objectives.

The safe integration of UAS in the NAS will be facilitated by new technologies being deployed in the NAS as part of NextGen.  The NAS Voice System will allow unmanned aircraft pilots to communicate directly with the air traffic controllers – a key requirement in integration.  Safe integration will lead us from today’s need for accommodation of UAS through individual approvals to a time when unmanned aircraft can “file and fly” in the NextGen environment.

With respect to another important issue for UAS development, in November 2013, FAA also released a privacy policy that applies to the UAS test sites.  This policy requires operators to comply with all local, state and federal laws concerning privacy and civil liberties.  FAA is requiring the test site operators to create a privacy policy that is available to the public.  The test site operator must require anyone operating unmanned aircraft at the site to have a written plan for how they will use and retain any test data acquired.  On a broader level, agencies across the government are coming together to work on privacy issues that may arise with the increasing use of unmanned aircraft beyond these test sites.  Ensuring that UAS integration does not erode individuals’ privacy is a goal supported by both government and industry.

This brings me to the announcement of the selection of the test sites.  FAA received 25 applications from 24 states, so I was quite pleased with the depth and range of the proposals we reviewed.  In selecting the sites, FAA considered many factors.  We made a concerted effort to pick sites that reflected both geographic and climactic diversity.  We also took into consideration the location of ground infrastructure.  We looked at the type of research that would happen at each site and the aviation experience of the applicants, as well as the type and volume of aircraft that fly near the sites.  Our research goals are focused on (1) gathering system safety data, (2) aircraft certification, (3) command and control link issues, (4) control station layout and certification criteria, (5) ground and airborne detect and avoid capabilities, and (6) impacts on affected populations and the environmental. 

The following test sites were selected by the FAA, after consultation with DOD and NASA:

  • University of Alaska.  The University of Alaska proposal contained a diverse set of test site range locations in seven climatic zones as well as geographic diversity with test site range locations in Hawaii and Oregon. The research plan includes the development of a set of standards for unmanned aircraft categories, state monitoring and navigation.  Alaska also plans to work on safety standards for UAS operations. 
  • State of Nevada. Nevada’s project objectives concentrate on UAS standards and operations as well as operator standards and certification requirements. The test site’s research will also include a concentrated look at how air traffic control procedures will evolve with the introduction of UAS into the civil environment and how these aircraft will be integrated with NextGen.  Nevada’s selection contributes to geographic diversity.
  • New York’s Griffiss International Airport.  Griffiss International plans to work on developing test and evaluation as well as verification and validation processes under FAA safety oversight. The test site also plans to focus its research on sense and avoid capabilities for UAS and its sites will aide in researching the complexities of integrating UAS into the congested, northeast airspace.
  • North Dakota Department of Commerce.  North Dakota plans to develop UAS airworthiness essential data and validate high reliability link technology. This test site will also conduct human factors research. North Dakota’s application was the only one to offer a test range in the Temperate (continental) climate zone and included a variety of different airspace which will benefit multiple users.
  • Texas A&M University – Corpus Christi.  Texas A&M plans to develop system safety requirements for UAS vehicles and operations with a goal of protocols and procedures for airworthiness testing. The selection of Texas A&M contributes to geographic and climatic diversity.
  • Virginia Polytechnic Institute and State University (Virginia Tech).  Virginia Tech plans to conduct UAS failure mode testing and identify and evaluate operational and technical risks areas. This proposal includes test site range locations in both Virginia and New Jersey.

As required by Congress, we expect the first test site to be operational within 180 days of the December 30, 2013, announcement and that the test sites  will continue to operate until at least February 2017.

As I noted at the outset, the FAA has successfully brought new technology into the nation’s aviation system for more than 50 years, and I have no doubt that we will do the same with unmanned aircraft.  The announcements of the UAS Roadmap, the Comprehensive Plan, the test site privacy policy and the test site selections are all concrete steps in support of an emerging technology that has extraordinary potential.  We have the safest aviation system in the world, and our goal is to introduce this new and important technology while still maintaining safety as our highest priority.

We are cognizant of the goals that have been set by Congress for us to integrate UAS into the NAS.  We will meet these goals with the collective technological and creative innovations of our government and industry colleagues.

This concludes my statement.  I will be happy to answer your questions at this time.

The FAA Modernization and Reform Act of 2012: Two Years Later

STATEMENT OF

MICHAEL P. HUERTA,
ADMINISTRATOR,
FEDERAL AVIATION ADMINISTRATION,

BEFORE THE

COMMITTEE ON TRANSPORTATION AND INFRASTRUCTURE,
SUBCOMMITTEE ON AVIATION,

ON

THE FAA MODERNIZATION AND REFORM ACT OF 2012: TWO YEARS LATER,

ON

FEBRUARY 5, 2014.

Chairman LoBiondo, Congressman Larsen, Members of the Subcommittee:

Thank you for the opportunity to appear before you today to review the accomplishments of the Federal Aviation Administration (FAA) during the past two years since Congress passed, and the  President signed into law, the FAA Modernization and Reform Act of 2012 (the Act).  For those of us who were working on developing and passing the Act, and I was only in office for part of it, we remember the long and difficult road we travelled to achieve passage.  In part because the bills were works in progress for so long, when the legislation passed, it was truly comprehensive in nature.  It contained over 200 deliverables, nearly half of which were due within the first year after enactment.  FAA takes the Congressional direction we receive very seriously and our employees work hard to achieve the goals and directives you legislate.  Given the breadth and depth of the Act, it would be difficult to provide a comprehensive review of all FAA responses its provisions.  I will, therefore, focus on three main areas that I know are of concern to this Subcommittee: Next Generation Air Transportation System (NextGen), unmanned aircraft systems (UAS), and the consolidation and realignment of FAA facilities, often referred to as section 804.  I think my time before you would be best spent updating you on these three vital initiatives because they are critical to how the agency, the aviation industry and the safety and efficiency of the national airspace system (NAS) will evolve over the coming years.

Before I begin, I would like to note what a difference a year makes.  Last year, I sat before you days before the funding restrictions of sequestration were imposed.  I know everyone in government was challenged by the effects of those restrictions.  I would like to express my gratitude that Congress worked through the many serious compromises and potentially crippling funding issues and passed the Omnibus Appropriations bill.  This vital legislation provides needed predictability during a very uncertain budget environment.  I appreciate the effort and the achievement.

NextGen

Let me begin with NextGen.  Following the Reauthorization, I named Michael G. Whitaker, who assumed the role of Deputy Administrator on June 3, 2013, Chief NextGen Officer.  This is a role of great importance.  Effectively leading the agency through the next phases of NextGen implementation will require working with many organizational components within the FAA, collaborating with industry and labor, and understanding the complexities of the NextGen program.  Mr. Whitaker is a seasoned aviation executive with extensive business, regulatory, legal, and international experience.  I knew that he was the right choice for this role and I am confident that NextGen will continue to flourish under his leadership.  Mr. Whitaker made it clear that helping to build and deploy NextGen was one of the principle reasons he joined the FAA and he has great commitment to ensuring that we reap the maximum benefits from NextGen enhancements. 

In September 2013, Air Force Major General Edward L. Bolton Jr. became the new Assistant Administrator for NextGen.  Mr. Bolton’s accomplished military career involved many leadership positions.  Most recently, he served as Assistant Secretary for Budget in the Office of the Assistant Secretary for Financial Management and Comptroller, where he led a team of financial managers responsible for the Air Force's $110 billion annual budget.  His leadership and commitment to public service is apparent.  I am confident that he is well-suited to lead the talented workforce responsible for transforming the NAS under NextGen.  NextGen is already delivering concrete benefits to users of the national airspace.  Because of NextGen improvements, we are able to guide and track aircraft more precisely on more direct routes.  This allows us to cut flight miles and reduce fuel burn, making air travel more convenient, predictable, and environmentally friendly. NextGen procedures have resulted in reductions in fuel consumption, carbon dioxide emissions, and noise, as envisioned at the time of the Reauthorization.  We are projecting that NextGen will reduce overall delays by 41 percent by 2020, compared with what would happen if we did not implement any additional NextGen improvements.[1]  These delay reductions will provide an estimated $38 billion in cumulative benefits through 2020. We estimate 16 million metric tons in cumulative reductions of carbon dioxide emissions through 2020, and 1.6 billion gallons in cumulative reductions of fuel use.

The agency has made consistent progress in delivering NextGen in several key areas since the Reauthorization.  One such area is Automatic Dependent Surveillance–Broadcast (ADS-B).  This system transitions the nation's air traffic control system from one that relies on radar technology to one that uses global satellites, which can provide more precise location data.  To date, the FAA has installed more than 596 ADS-B ground stations, 566 of which are operational.  ADS-B ground stations provide traffic and weather information to more than 1,700 properly equipped aircraft and supporting air traffic control separation services at eight En Route and 38 Terminal facilities.  Users with ADS-B capabilities are already achieving increases in efficiency and fuel burn.  They can also increase flight hours by virtue of being able to operate in periods of low visibility, which is particularly important in areas like Alaska and over the Gulf of Mexico.

Over the last two years, System Wide Information Management (SWIM) infrastructure investments have enabled significant advancement in the access and distribution of airport surface movement information.  The surface movement data from 27 major airports is now available through a single portal to a broad range of external consumers.  Today there are 19 external consumers, including many cargo and passenger airlines, vendors, and aviation research institutions, receiving surface movement data through this single portal.  This allows operators to make better-informed decisions that improve their efficiency.

We are in the final stages of the En Route Automation Modernization (ERAM) program, which will provide benefits for users and the flying public by increasing capacity and efficiency, as well as allowing us to add new capabilities into the airspace system.

One of the most exciting new capabilities we have underway is Data Communications (Data Comm).  Data Comm allows us to communicate through written instructions to pilots, which reduces the possibility of  error with radio communications.  More importantly, Data Comm allows us to communicate highly complex clearances that are not practical to convey over the radio – instructions that can be automatically loaded into the aircraft’s flight management system.  This will ultimately save operators and passengers time and money, and will vastly improve the flexibility and efficiency of our operations. The FAA has awarded the Data Communications (Data Comm) Integrated Services contract, which will provide for data communications between airport towers and appropriately equipped aircraft in 2016. Operational Data Comm trials are underway in Memphis and Newark.

NextGen’s Performance Based Navigation (PBN) facilitates more efficient design of airspace and procedures which collectively result in improved access, capacity, predictability, operational efficiency, and environmental benefits.  PBN’s Area Navigation and Required Navigation Performance (RNAV and RNP) procedures are providing greater operational flexibility and  capabilities. Optimized Profile Descents allow aircraft to reduce engine power and virtually glide down to the runway.  This leads to reduced fuel burn, which reduces the carbon footprint of large air carriers, as well as reduced noise.  New departure procedures, made capable by NextGen at major airports across the country, are reducing delays and increasing capacity.  The optimization of airspace and procedures in the Metroplex program has seven active teams in various phases of development.

We have expanded our public reporting of NextGen performance through success stories and performance snapshots on our website.  The FAA publishes NextGen-specific metrics at the local level in order to isolate and identify NextGen improvements at site-specific locations.  Core airports, key city pairs, distance/time/fuel reduction, runway safety, the implementation and use of NextGen technology and procedures will continue to be important to understanding the value and benefits of modernization.  Taken together, these metrics reveal the nationwide impact of NextGen development, which has already been shown to provide tremendous benefits to efficiency and the environment.

In this month’s release, we have added three new key performance indicators:

  1. Effective gate-to-gate time at Core 30 airports. An efficiency indicator, it measures the duration of travel from scheduled gate-out time to the actual gate-in time.  As outlined in Sec. 214 of the FAA Reform Act, gate-to-gate is an important metric of NextGen success.
  2. Effective gate-to-gate predictability for city pairs. This too is an efficiency indicator, and we have chosen city pairs as recommended by the NextGen Advisory Committee, our industry-government partnership that advises the FAA on key NextGen initiatives.  Based on the Bureau of Transportation Statistics, the metric measures whether flight duration is consistent over time between NAC-recommended city pairs
  3. Average Daily Capacity for Core 30 airports.

The NextGen Performance Snapshots reports the average daily capacity at Core 30 airports during reportable hours.  For instance, at MEM, reportable hours cover all hours of a day, while at JFK, they include the 6:00 to 23:59 time period.  Another reauthorization metric, the user reference provides the data sources and definitions as well as the methodology to compute the metrics.

In the latest release, we added a metroplex section highlighting the FAA’s initiatives to improve air traffic flows in busy metropolitan areas.  The metroplex concept revolves around traffic flow de-confliction in a complex airspace where airports are in close proximity. There are 21 metroplexes and each metroplex is linked to an individual page that provides:

  • the list of airports included in the metroplex,
  • a description of operations by user class (commercial air carriers, GA, military),
  • passenger volume as well as
  • the expected benefits expected to accrue upon completion of the NextGen near-term procedural improvements implemented by the Optimization of Airspace and Procedures in the Metroplex (OAPM) program

Additionally, we updated our efficiency, access, city pair and environmental metrics with the latest available data.  We also introduced four more success stories that highlight some of the more significant results we are seeing from NextGen implementations. 

  1. Localizer Performance with Vertical Guidance at a GA airport in California - NextGen procedure enables pilots of equipped aircraft to land even when the approach to the runway is covered in fog.   LPV provides a great backup (to the ILS) and it is another means for pilots to get their passengers into airports they otherwise could not.
  2. The use of Performance-Based Navigation at Jackson Hole - A satellite-based precision procedure that makes the landing path to Jackson Hole both safer and shorter for equipped aircraft.  The new procedure, which keeps aircraft on a tightly-defined track along a smooth, curved path, provides a safety cushion between the approach path and the higher terrain to the west.
  3. Area Navigation off-the-ground at DFW - The FAA has put in place a NextGen procedure that triples the number of departures the airport can accommodate, a significant increase in the airport's throughput up to 20% on an average day.  The NextGen procedure makes it possible for flights to take off with less distance between each aircraft — 1 nautical mile compared to the standard 3 nautical miles.  This enables an increase of 15-20 percent of departures per hour when the airport is congested compared to conventional methodology
  4. Airborne Collision Avoidance System X - As NextGen technology enables aircraft to safely fly closer, the FAA is developing a new collision avoidance system.  Terrain Collision Avoidance System was introduced in 1989; however, the system needs an upgrade to accommodate new capabilities that are being introduced in the National Airspace System.  With satellite-based NextGen technologies, aircraft are tracked with a higher precision than with radar and safe separation distances may be reduced.  This means that ATC can get aircraft through busy airspace more efficiently.

As we continue to move forward with NextGen development and deployment, I am confident that we will continue to see benefits to the operation of the national airspace. 

UAS

Many new technologies have abstract benefits that are sometimes hard to succinctly describe or understand.  UAS have applications that are not only readily understandable, but have the potential for broad benefits for virtually all Americans.  From homeland security, emergency management and law enforcement, to food and package delivery, the potential uses for UAS technology are limitless.  Realistically, neither the technical nor operational capabilities necessary exist today to implement the opportunities described by visionaries, but their promises for 21st century conveniences are compelling.

Meeting the challenges for realizing this potential will take a concerted effort and must achieve the requisite balance of maximizing the technological benefits, while maintaining safety and efficiency of the NAS.  The FAA has a history of accommodating new technology into the NAS safely and effectively.  UAS is the latest technology to be developed that FAA is working to integrate.  While FAA’s role in this effort is critical, it is limited to NAS safety and operational efficiency.  As with other manned technologies, FAA’s role does not extend to directing or otherwise limiting the underlying purposes for which the aircraft is used.  That is left to government agencies with the appropriate jurisdiction and Congressional mandates.

I would like to set forth a basic framework for how the FAA will integrate unmanned aircraft into the NAS.  In some ways, unmanned aircraft are inherently different from manned aircraft.  They possess a wider operational range than manned aircraft, with a wider number of different physical and operational characteristics.  Some UAS are the size of a fist, and fly at low altitudes and slow speeds.  Others have glider-like bodies with the wing span of a 737 and can fly above 60,000 feet.  Many can fly longer than manned aircraft.  Their common characteristic, distinguishing UAS from manned aircraft, is that their pilot is on the ground and not on board the aircraft.  This is a very new and different common denominator.

FAA estimates that we can expect 7,500 small unmanned aircraft in the NAS over the next five years, provided regulations and operational guidelines/policies are in place to handle them.  We recognize that, while the expanded use of UAS presents great opportunities, integrating them also presents significant challenges.  Operational issues, such as pilot training, must be addressed.  Additionally, we need to make sure that unmanned aircraft can detect and avoid other aircraft and that they operate safely, even if they lose the link to the pilot in command.  Likewise, manned aircraft must be able to detect these aircraft as well.

Our airspace system is not static and it is important for industry to understand that unmanned operations will evolve over time, just as they have over the past decade.  Today, unmanned aircraft are used to keep our borders safe.  They help with scientific research and environmental monitoring.  They support law enforcement agencies and help state universities conduct research. 

As we move forward, the use of small unmanned aircraft is likely to grow most quickly in civil commercial operations.  These UAS are extremely versatile and have relatively low initial cost and operating expenses.  The FAA, in accordance with the Act, is working on a proposed rule governing the use of a wide range of smaller UAS, which, in accordance with the roadmap, we expect to issue for comment this year.

FAA’s long term goal of UAS integration will rely on the test sites to answer key questions and provide solutions to the issues noted above, as well as how they will interface with the air traffic control system.  This information will help the FAA to develop regulations and operational procedures for future civil commercial use of UAS in the NAS.

Last year, the FAA, often in consultation with other key government partners and industry stakeholders and in accordance with provisions of the Act, issued a number of key documents intended to assist in defining parameters to safely integrate these very diverse systems into the world’s most complex airspace.  The Integration of Civil UAS in the NAS Roadmap outlines, within a broad timeline, the tasks and considerations needed to enable UAS integration into the NAS.  The five year Roadmap, updated annually, provides stakeholders with proposed agency actions to assist with their planning and development.  One concrete achievement facilitated by the roadmap took place in September 2013 when the first commercial flight of an unmanned aircraft took place in the skies above the Arctic Circle.  A Scan-Eagle completed a 36 minute flight to view marine mammals and survey ice.  There are hopes that UAS can be used to meet environmental and safety requirements in the Artic.   The flight was coordinated by Insitu (the UAS manufacturer), Conoco Phillips, and other federal and international agencies.  The Arctic region is the only area to date where we have authorized the use of small unmanned aircraft for commercial purposes.  This flight was organized to demonstrate the feasibility of implementing the Artic provisions in the Act.

The UAS Comprehensive Plan was drafted by the Joint Planning and Development Office (JPDO) in coordination with JPDO Board participants from the Departments of Defense (DOD), Commerce (DOC), Homeland Security (DHS), the National Aeronautics and Space Administration (NASA) and the FAA.  It is a document that considers UAS issues beyond 2015, including technologies necessary for safe and routine operation of civil UAS and the establishment of a process to inform FAA rulemaking projects related to certification, flight standards and air traffic requirements.  The Comprehensive Plan details work that has been accomplished, along with future efforts needed to achieve safe integration of UAS into the NAS in the NextGen timeframe.  It sets overarching, interagency goals, objectives, and approaches to achieving integration.  Each partner agency will work to achieve these national goals and may develop agency-specific plans that are aligned to the national goals and objectives.

With respect to another important issue for UAS development, in November 2013, FAA also released a privacy policy that applies to the UAS test sites.  This policy requires operators to comply with all local, state and federal laws concerning privacy and civil liberties.  FAA is requiring the test site operators to create a privacy policy that is available to the public.  The test site operator must require anyone operating unmanned aircraft at the site to have a written plan for how they will use and retain any test data acquired.  On a broader level, agencies across the government are coming together to work on privacy issues that may arise with the increasing use of unmanned aircraft beyond these test sites.  Ensuring that UAS integration does not erode individuals’ privacy is a goal supported by both government and industry.

This brings me to the announcement of the selection of the test sites, the creation of which were mandated in the Act.  FAA received 25 applications from 24 states, so I was quite pleased with the depth and range of the proposals we reviewed.  In selecting the sites, FAA considered many factors.  We made a concerted effort to pick sites that reflected both geographic and climactic diversity.  We also took into consideration the location of ground infrastructure.  We looked at the type of research that would happen at each site and the aviation experience of the applicants, as well as the type and volume of aircraft that fly near the sites.  Our research goals are focused on (1) gathering system safety data, (2) aircraft certification, (3) command and control link issues, (4) control station layout and certification criteria, (5) ground and airborne detect and avoid capabilities, and (6) impacts on affected populations and the environment. 

The following test sites were selected by the FAA, after consultation with DOD and NASA: University of Alaska; the State of Nevada; New York’s Griffiss International Airport; North Dakota Department of Commerce; Texas A&M University – Corpus Christi; and Virginia Polytechnic Institute and State University (Virginia Tech). 

As required by Congress, we expect the first test site to be operational within 180 days of the December 30, 2013, announcement and that the test sites will continue to operate until at least February 2017.

FAA Facility Consolidation and Realignment – Section 804

When I testified before you last year, I noted that not all Congressional deliverables were created equal.  One of the sections of the Act that holds great potential for the FAA is section 804, a provision which is intended to assist with the consolidation and realignment of FAA facilities.  In order for FAA to be well positioned to meet future demands, we must have strategically placed, state of the art air traffic control facilities.  

While FAA appreciates the importance of this provision, executing the intent of the provision has proven to be challenging.  As originally envisioned, the Act contemplated a single plan being presented to Congress with a comprehensive recommendation encompassing all FAA facilities.  After working extensively with our labor unions, we now believe the most effective workable approach to consolidation and realignment is a segmented one utilizing a repeatable process and incremental steps toward thoughtful and agreed upon recommendations.  Subsequent to providing the details of this process to this Committee’s leadership late last year, we kicked off the first step of this important initiative on January 22, 2014, along with our union colleagues.  We will begin this effort focusing on our terminal facilities with a goal of making an initial recommendation to Congress early next year. 

We expect to evaluate approximately 25 facilities this fiscal year.  The evaluation will include a review of the infrastructure of the facility, the technology the facility can support, including its readiness for NextGen, and how people working at the facility will be impacted by any decision made.  Step two begins the development of business case plans that document the benefits and risks associated with different scenarios.  This includes evaluating each proposed pairing of receiver and transfer candidates.  It also includes an initial outreach to industry stakeholders who might be impacted by the recommendation.  Step three is a more detailed quantification of the costs, benefits and risks of the potential recommendations.  Step four is a ranking the recommendations of the fully developed scenarios and clearing the recommendations throughout the FAA and the Department.  Agreed upon recommendations will then be presented to Congress for your consideration.  After submission to Congress, FAA will publish a notice in the Federal Register to solicit public comment.  We will also be using existing communication opportunities to speak to airlines and system users regarding the status of the process and recommendations.

Throughout this process, five prioritization criteria will be consistently applied and given equal weight.  Factors, such as whether the facility’s airspace borders the airspace of another terminal facility, whether it  provides approach control for core airports, whether it operates full or part time, what its facility condition index is, and whether it is an FAA investment priority will be considered.  Life cycle costs and benefits have also been identified and agreed upon.

There is always great sensitivity surrounding decisions affecting where people will work.  This process took a long time to develop, but I think it was time well spent.  We have worked out all of the details so that employees and management alike can understand why the recommendations that are made got made.  In turn, we can justify the recommendations to Congress at the appropriate time. 

We recognize that facility consolidation and realignment are fundamental to FAA moving forward and meeting its challenges and responsibilities.  With this new process in place, it will support a segmented and repeatable format for identifying and quantifying the difficult decisions that must be made in this area.  I certainly believe that by this time next year, we will have made good use of the authority provided in section 804 and I look forward to being able to report on that.

Conclusion

These are only three of the important areas FAA is working on to meet the future needs of government and the aviation industry without compromising the safety or efficiency of the NAS.  We have an enviable safety record, which means we must constantly look at ways to raise the bar on safety and be smarter about the use of data to keep ahead of emerging safety concerns.  We must learn how to recruit and train our workforce to better adapt to innovation so that we more efficiently and effectively approach our critical mandates.  These are broad priorities.  As we work through completing the directives of the last reauthorization and think about what goals should be included in the next one, we must keep these priorities in mind because there are a lot of details we must work through collectively, government and industry, to support them. 

FAA, government generally, is being asked to do more with less.  Given the fiscal challenges we have seen in the past year and the continued difficult financial environment, we are going to have to have thoughtful conversations about how FAA should prioritize its role – what it makes sense for FAA to continue doing, and how we should do certain things differently.  We need to be strategic in how we prioritize our resources. 

We in this room, the people who are watching this hearing, care about aviation.  We must continue to lead take on the challenges before us.  I very much look forward to working with you as we do.

Mr. Chairman, this concludes my statement.  I will be happy to answer your questions at this time.

 

[1] In order to assess the full cost of delay, the Department of Transportation (DOT) considers the value of air travelers’ time. From 2003 to 2011, this was estimated by DOT at $28.60 per hour. In the Revised Departmental Guidance on Valuation of Travel Time in Economic Analysis, DOT increased that value for 2012 to $43.50 per hour.

The Impact of Wind Farms on Military Readiness

STATEMENT OF

NANCY KALINOWSKI,
VICE PRESIDENT,
SYSTEM OPERATIONS SERVICES,
AIR TRAFFIC ORGANIZATION,
FEDERAL AVIATION ADMINISTRATION

BEFORE THE

HOUSE ARMED SERVICES COMMITTEE,
SUBCOMMITTEE ON READINESS

ON

THE IMPACT OF WIND FARMS ON MILITARY READINESS,

JUNE 29, 2010.

Chairman Ortiz, Congressman Forbes, Members of the Subcommittee:

Thank you for the opportunity to appear before you today.  My name is Nancy Kalinowski and I am the Vice President of System Operations Services for the Federal Aviation Administration (FAA).  In that capacity, I am charged with overseeing the process by which we evaluate the impact of proposed construction on the navigable airspace.  Any proposed structure that could potentially interfere with navigable airspace must be evaluated by my office.  The evaluation results in an agency finding of whether the proposed structure is a hazard for air navigation.  During the evaluation, our Obstruction Evaluation Services office works with the individual or entity that submits the proposal, as well as other interested FAA offices and government agencies, as required.  In recent years, as the need for alternative energy has become a major focus of government and industry, the volume of proposed wind turbines submitted to the FAA for review has increased dramatically.  As such, it is certainly fitting to discuss how we review these proposals to understand the process and evaluate potential improvements.

The FAA is vested with broad authority to manage the navigable airspace and develop plans and policies for its use.  Whether by regulation or agency order, the FAA ensures the safety of aircraft and efficient use of the airspace.  Navigable airspace is a limited national resource and the FAA’s primary mission in this context is to preserve that resource for aviation; however, we are also called upon to negotiate equitable solutions to conflicts over the use of the airspace for non-aviation purposes.  There is a statutory requirement that a person or entity (a “proponent”) give adequate public notice of the construction, alteration, establishment or extension of any structure when such notice would ensure the safety of air commerce as well as the efficient use and preservation of navigable airspace and/or airport capacity.  Generally, public notice is required if the structure is more than 200 feet in height above ground level, near or on an airport (military or public use) or heliport, or if such a notice is specifically requested by the FAA.  The notice provides the FAA with the opportunity to identify the potential aeronautical hazards to minimize any adverse affects to aviation.  It is the proponent’s responsibility to propose mitigation in response to identified hazards.  If the FAA can take action to address the hazard, that action can be part of the mitigation plan, but the cost of mitigation, including upgrading navigational aids, if required, is borne by the proponent.  Mitigating actions could also include revising published data or issuing a Notice to Airmen (NOTAM) to alert pilots to airspace or procedural changes made because of a structure.  In addition, mitigation could include recommending appropriate markings and lighting to make the structure visible to pilots or depicting structures on aeronautical charts to inform pilots and improve safety.

Structures that require notice may include buildings to antenna towers – essentially anything that meets the criteria noted above.  This would include wind turbines and the new generation of wind turbine generators, which can be more than 400 feet in height and have blades that spin up to 200 miles per hour.  Each wind turbine is evaluated separately, but the cumulative effect of the wind turbines on navigable airspace will obviously be more significant based on the total number of turbines grouped together.  The number of wind turbine cases handled by the FAA has increased from 3,030 in 2004 to 25,618 last year.  To date in 2010, we have 18,685 wind turbine cases.  One concern that the wind turbines raise is that the blade tips rotate above the radar, thus affecting the capability of the target to be received on the radar equipment.  Additionally, they reflect radio waves, and exceed the line of sight protection criteria.  To give you an idea of the impact of wind turbines on long range radar, there is a radar cross section spectrum that identifies how clearly a range of objects are picked up on the radar.  Insects and birds are at the low end.  Conventional cruise missiles are in the mid range.  Most aircraft are a little higher in the spectrum, with large aircraft (e.g., a Boeing 747) and the space shuttle at the highest end of the spectrum.  Wind turbine blades spinning, in some instances, at more than 200 miles per hour are picked up by radars with a signal strength greater than a Boeing 747.  Because the radar repeatedly sees this large return, the radar will not pick up actual aircraft in the same area.

The clutter that is created by wind turbines can result in a complete loss of primary radar detection above a wind farm.  When that clutter occurs, it appears at all altitudes, so simply directing the aircraft to a different altitude does not solve the problem.  Similarly, on the Next Generation Weather Radar (NEXRAD), wind farm activity looks remarkably like storm activity, thus complicating the communication of precise weather information by controllers to pilots.  (Wind turbine impacts on NEXRAD, which are owned and operated by the National Oceanic and Atomospheric Administration, are not currently considered in FAA’s evaluation process.)  Existing FAA radars have limited capability to filter out clutter.  The radar can be modified by increasing the sensitivity to reduce clutter from the wind turbines, but in doing so, what the radar can see is also reduced, to the point where actual aircraft targets can drop off.  Consequently, there are real and significant issues that must be evaluated by the government prior to the approval of wind turbines. 

Although not an issue of consideration in the evaluation process, another issue of some concern is that there is competition for the land which both the radars and the wind turbines need to occupy.  Lease holders who currently have primary radars are now being offered substantial financial incentives not to renew their leases with the FAA and instead, lease to companies that want to install wind turbines.  This puts the FAA in the undesirable position of having to condemn property at fair market value to avoid losing the use of the navigational aid.  The call for the FAA to simply move its radars to accommodate requests to install wind turbines fails to take into account that this is not a realistic option for a number of reasons.  The FAA cannot take down a radar without an unacceptable loss of coverage.  Even assuming an acceptable, alternate site could be identified, the radar could not simply be moved.  Rather, a new radar would have to be installed at the new location.  The reality is that the FAA does not have extra radars available for replacement and there are no spare long range radars.  Even if a new radar were available, moving the radar site would require changes to the national airspace system.  Airways, reporting points, and airspace fixes are parts of the airspace system that could be impacted.  Depending on the situation, such changes could require regulatory action.  The bottom line is that moving radars around the country is a costly, disruptive, unacceptable, and unworkable proposition.  It may sound simple, but in fact, it is not something the FAA can accommodate or the taxpayers can afford.

So having set forth the complexity and concerns of locating wind turbines near primary radars, let me now turn to how we attempt to strike the balance between the need for an uninterrupted radar signal and the clean energy that wind turbines supply.  The current regulatory requirement is that the proponents must file notice with the FAA as early in the planning process as possible, but no later than 30 days prior to the date the proposed construction is expected to begin.  The 30 day timeframe has been in place for 45 years and was appropriate for single, stationary structures that the FAA largely dealt with at that time.  Wind turbines have a cumulative effect, so the evaluation of their impact is significantly more complicated than single, stationary structures. 

Ninety-seven percent of the notices the FAA receives are sent electronically, where the proponents simply fill out a form online.  The FAA acknowledges receipt of the notice and, after an initial study, issues a determination of whether or not a hazard exits.  The initial study normally takes 30 days, but as noted, a wind turbine’s cumulative implications can require more extensive evaluation within the FAA, the Department of Defense (DoD), and the Department of Homeland Security (DHS).  Each time the status of the applicant’s proposal is changed, the applicant will be notified by FAA of the change.  The initial evaluation includes review by FAA’s Offices of Airports, Flight Standards, Frequency Management, and appropriate military organizations.  The offices typically respond online with whether they have an objection and what the objection is.  It is then incumbent on the proponent to propose mitigation. 

The FAA’s authority to issue hazard determinations is limited to the scope of Part 77 of Title14, Code of Federal Regulations.  The FAA lacks the authority to evaluate impacts to airspace not within our jurisdiction.  For example, if wind turbines are located more than 12 miles offshore and, therefore, are not in U.S. territorial waters, the FAA lacks the authority to declare them a hazard, even if the military has concerns with the placement or cumulative impact of those wind turbines. 

Our role in making hazard determinations can require the FAA to facilitate the exchange of information between the proponent and the objecting governmental entity.  This process can take a considerable period of time depending upon how well negotiations proceed between the parties.

In conclusion, the FAA has an efficient means of processing wind turbines proposals, which includes evaluating all valid aeronautical comments, reviewing all pertinent analytical reports, and issuing determinations that take into account all comments and findings.  Although we believe the process works well, we are always considering potential improvements and modifications, including whether the 30 day review is realistic when considering the latest highly complex structures, a grouping of which can have an unwanted cumulative effect.  We are open to discussion of how to improve the process. 

Thank you for the opportunity to describe FAA’s role in this very important process.  This concludes my statement.  I will be happy to answer your questions at this time.

The Role of Unmanned Aerial Systems on Border Security

JOINT STATEMENT OF

NANCY KALINOWSKI,
VICE PRESIDENT, SYSTEM OPERATIONS SERVICES,
AIR TRAFFIC ORGANIZATION,
AND
JOHN ALLEN,
DIRECTOR, FLIGHT STANDARDS SERVICE,
AVIATION SAFETY,
FEDERAL AVIATION ADMINISTRATION,

BEFORE THE

HOUSE OF REPRESENTATIVES,
COMMITTEE ON HOMELAND SECURITY,
SUBCOMMITTEE ON BORDER, MARITIME, AND GLOBAL COUNTERTERRORISM,

ON

THE ROLE OF UNMANNED AERIAL SYSTEMS ON BORDER SECURITY,

JULY 15, 2010.

 

Chairman Cuellar, Congresswoman Miller, Members of the Subcommittee:

Thank you for inviting the Federal Aviation Administration (FAA) to this hearing.  We are Nancy Kalinowski, Vice President of System Operations Services in the Air Traffic Organization (ATO), and 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 air operators and airmen.  Ms. Kalinowski’s role is to provide overall guidance for air traffic procedures and airspace issues and her office is the focal point for daily ATO interface with the Department of Defense (DoD) and the Department of Homeland Security (DHS) regarding air transportation security issues. 

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, through diligent oversight, the FAA maintains an extremely safe airspace.   

With regard to unmanned aircraft systems (UAS), we – the FAA  – set 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 recognizes the great potential of UASs in national defense and homeland security, and as such, we strive to accommodate the DoD and DHS’ needs for UAS operations, but we must do so without jeopardizing safety.  Because airspace is a finite resource, to help mitigate risk, FAA sets aside airspace for an operator’s exclusive use when needed.  These exclusive use areas are known as Restricted or Prohibited Areas.  The DoD conducts most of its training in such airspace.  Along the southern border of the country, the DoD has elected to share that restricted airspace with Customs and Border Protection (CBP).  However, the CBP also operates UASs in civil airspace, as discussed below.

When new aviation technology becomes available, we must first determine whether the technology itself is safe and whether it can be operated safely.  Whether the technology is to be used by pilots or air traffic controllers, we determine the risks associated with putting that technology into the NAS.  Once we address and mitigate those risks, 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 whether the new technology is safe enough to be permitted into the system.

The FAA is using this same methodology to manage the integration of the new UAS technology into the NAS.  While many view UASs as a promising new technology, the limited safety and operational data available does not support expedited or full integration into the NAS.  For example, some of the data that we do have comes from the CBP, and while we have reason to believe that the safety data that we do have may not be a representative sampling of UAS operations, it is all we have.   To the extent that this limited data from CBP are representative, they suggest that accident rates for UASs are higher than in general aviation and may be more than an order of magnitude higher than in commercial aviation. 

For example, from Fiscal Year 2006 to Fiscal Year-to-Date 2010 (July 13, 2010), CBP reports a total of 5,688 flight hours.  The CBP accident rate is 52.7 accidents per 100,000 flight hours (the standard safety data normalization factor/the standard on which safety data is reported).  This accident rate is more than seven times the general aviation accident rate (7.11 accidents/100,000 flight hours) and 353 times the commercial aviation accident rate (0.149 accidents/100,000 flight hours).

While the CBP accident rate appears to be higher than general or commercial aviation, we note that CBP’s total reported flight hours of 5,688 are very small in comparison to the 100,000 hour standard typically used to reflect aviation safety data and accident rates.  CBP has had seven deviations (where the aircraft has done something unplanned or unexpected and violates an airspace regulation) so far this fiscal year in over 1,300 hours of flight time, as compared to the five deviations in 1,127 hours of flight time in Fiscal Year 2009.   Continuing review of UAS operations will enhance FAA’s ability to assess the safety to improve ongoing use of this technology.  

This is the crux of the FAA’s responsibility.  More data is needed before an informed decision to fully integrate UASs into the NAS can be made.  Because of this, the FAA must make conservative decisions with respect to UAS NAS integration.  Until such time as the data can support an informed decision to integrate UASs in the NAS – where the public travels every day – in accordance with our safety mandate, the FAA must continue to move forward deliberately and cautiously. 

For UASs to gain access to the civil airspace, 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.  Civil UAS operators must apply for a Special Airworthiness Certificate – Experimental Category to gain access to the NAS.  This avenue allows the civil user to operate the UAS for research and development, demonstrations, and crew training.  The Special Airworthiness Certificate does not permit carrying persons or property for compensation or hire.  Commercial UAS operations in the U.S. are not permitted at this time. 

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.

To apply for a COA, public entities may submit an application online with the FAA.  The FAA then evaluates the request.  Internally, ATO first examines the application for feasibility – airspace experts review and ensure the operation will not severely impact the efficiency of the NAS.  The application is then sent to Flight Standards to evaluate the operational concept, the airworthiness release of the aircraft, the pilot/crew qualifications, and the policies and procedures used by the operator.  From that in-depth evaluation, special provisions are written.  These internal FAA offices then confer together to address any remaining concerns and harmonize the provisions needed to ensure the safe operation of the UAS.  Once these steps have taken place, the COA is signed and given to the applicant.

We have recognized the need to streamline our process for evaluating COA applications.  To address the timeliness concerns of applicants, the FAA is working to simplify the COA process and has also increased staffing levels by more than a dozen people.  The FAA is working to better standardize the review process and increase communication and transparency between the agency and the applicants.  We take this process seriously and while we are taking specific steps to improve the COA application process, we will always take the time needed to ensure these operations can be conducted safely.  

These efforts are already showing improvements.  In 2009, we issued 146 COAs.  So far this year, we have issued 122 COAs, and we are on track to issue over 200 this year.  At the current time, we have 268 active COAs on 133 different aircraft types, issued to 151 proponents.  CBP currently has 11 COAs issued to them. 

Normally, COAs are worked on a first-come, first-served basis.  However, given that there are emergency and disaster situations where the use of UASs has saved lives and otherwise mitigated emergency situations, the FAA has issued three special disaster COAs, one to CBP and two to the DoD.  Both agencies have requested COAs using the special process, and most disaster COAs have been issued before either agency had the aircraft and personnel in place to fly the mission.  In addition, there is a second type of special “emergency” COA.  Emergency COAs have been used to help with California wildfires, the Deepwater oil spill, and special law enforcement missions. These have been issued in minutes or hours, not days and weeks.  The FAA has issued three disaster COAs and 16 emergency COAs to CBP for its use.

These are only a few of the many improvements that the FAA is implementing to address the concerns with the COA application process.  In the meantime, 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 enable increased, and ultimately routine, access of Federal public UAS operations into the NAS to support the operational, training, developmental, and research requirements of the FAA, DoD, DHS, and NASA.  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.  We thank the Congress for enabling the formation of the ExCom to advance the work of UAS integration into the NAS and streamline the COA process.

The FAA expects small UASs to experience the greatest near-term growth in civil and commercial operations because of their versatility and relatively low initial cost and operating expenses. The agency has received extensive public comment on small UASs, both from proponents who feel their size dictates minimal regulation and from groups concerned about the hazards that UAS pose to piloted aircraft as well as persons and property on the ground.

In April 2008, the FAA chartered an Aviation Rulemaking Committee (ARC) to examine these operational and safety issues and make recommendations on how to proceed with regulating small UASs. The agency has received the ARC’s recommendations, and is drafting a proposed rule.  Ensuring the safety of all airspace users while not putting undue burdens on small UAS operators is a challenging task; the FAA hopes to publish the proposed rule by mid-2011.

Additionally, the FAA has asked RTCA – an internationally recognized standards organization that frequently advises the agency on technical issues – to work with the FAA and industry and develop UAS standards.  RTCA will answer two key questions: 

  1. How will UASs handle the challenges of communication, command, and control? and
  2. How will UASs “sense and avoid” other aircraft?

These activities are targeted for completion before 2015.

As the FAA moves forward with improving the processes for integrating UAS into the NAS, we want to acknowledge and thank our partner agencies from DHS in helping to keep our skies safe.  CBP, in cooperation with the FAA, conducted a comprehensive training session for all of their UAS pilots and sensor operators just last month.  The 16-hour CBP training safety meeting was conducted June 14th and15th with classroom training, as well as guided discussion periods involving pilots and sensor operators from CBP.  This approach to safety provided the two agencies with an environment to share knowledge and experience and forged a partnership that takes into account both the security of the homeland as well as the safety of our airspace.  We look forward to continuing that partnership with the CBP, as well as the other Federal agencies, as UAS technology matures.

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 careful review.  Now, as we attempt to integrate these aircraft into the NAS, we need to take a hard look at the risk 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 Cuellar, Congresswoman Miller, Members of the Subcommittee, this concludes our prepared remarks.  We would be pleased to answer any questions you might have.