U.S. Department of Transportation
Federal Transit Administration
11th Annual State Safety
Oversight Program Meeting
September 17 to 20, 2007
The Federal Transit Administration (FTA) held its 11th Annual State Safety Oversight Program Meeting in Minneapolis, Minnesota - September 17 to 20, 2007. This meeting was co-hosted by the Minnesota Department of Public Safety and Metro Transit.
There were a total of 95 attendees at this year's meeting, including:
Appendix A of this Meeting Summary contains the Participant List. The Annual Meeting was facilitated by Mr. Levern McElveen, Safety Team Leader, FTA's Office of Safety and Security. During the three-and-a-half days, presentations were given by:
Sessions were also conducted by Mr. Michael Taborn, Director of FTA's Office of Safety and Security, Mr. Richard Wong, with FTA's Office of Chief Counsel, and Mr. Richard Gerhart, Security Team Leader with FTA's Office of Safety and Security, to address:
Presentations were also made by Ms. Annabelle Boyd, Mr. Jim Caton, and Mr. Andy Lofton, contractors for FTA's SSO Program, and by several UTC representatives, including:
This year's annual meeting also included a break-out session focused on identifying and managing hazardous conditions. Separate training sessions were also provided for SSO personnel and rail transit agency representatives to address specific issues and initiatives relevant to their respective implementation of 49 CFR Part 659 requirements.
On Wednesday afternoon, September 19, 2007, Metro Transit provided a tour of its alignment, Operations Control Center, Vehicle Maintenance Facility, Traction Power Sub-Station, and gave a special presentation on its Track Worker Protection Program.
Appendix B provides a listing of the contents of the CD-ROM included with this Meeting Summary. This CD-ROM includes electronic copies of all viewgraph presentations, handouts, and other materials distributed during the 11th Annual SSO Program Meeting.
Appendix C provides the results of the evaluations received from the participants of the 11th Annual SSO Program Meeting, including recommendations for topics and issues to be addressed at future meetings.
The Meeting Summary presents the topics covered at the meeting and highlights discussion points and identified action items. It is organized into the following sections:
Mr. Levern McElveen, Safety Team Leader for FTA's Office of Safety and Security, kicked the meeting off by welcoming participants to Minneapolis. Mr. McElveen explained that the agenda for the meeting had been developed through a working group comprised of SSO and rail transit agency representatives to include topics of interest to the SSO community. Mr. McElveen reviewed the agenda with the attendees, highlighting break-out sessions, the tour at Metro Transit, and the welcome reception on Monday night. Mr. McElveen then introduced Mr. Michael Taborn, Director, FTA's Office of Safety and Security.
Michael Taborn, Director, FTA's Office of Safety and Security
Mr. Taborn welcomed everyone to the annual meeting and stated that attendance was at an all alltimehigh. He commended the participants for their commitment to the SSO Program and extended a special thanks to the meeting's hosts, Deputy Commissioner Tim Leslie and Lt. Tim Rogotzke of the Minnesota Department of Public Safety and Metro Transit's General Manager, Brian Lamb, along with Mike Conlon and John MacQueen from Metro Transit's Safety Department.
Mr. Taborn went on to state that FTA conducts an ambitious program of oversight and technical assistance activities designed to prevent public transportation fatalities, injuries, property damage and system interruption, and to ensure the capability to respond effectively to those accidents, security incidents, and emergencies that do occur. Mr. Taborn noted that FY 2007 saw FTA's greatest investment yet in supporting the safety, security and emergency preparedness of the public transportation industry, and its strongest delivery of programs, products, training, and services.
Specifically for the SSO Program, in FY 2007, FTA:
Mr. Taborn next discussed the National Transportation Safety Board (NTSB) hearing, which was held Tuesday, September 11, 2007, to adopt findings and recommendations from the NTSB's investigation of the July 11, 2006 derailment at the Chicago Transit Authority (CTA). Mr. Taborn noted that, during this hearing, the Board declared, very publicly, its belief that the SSO program is not sufficiently overseeing rail transit safety. Mr. Taborn stated that the NTSB believes FTA should be requiring more and doing more to ensure rail transit safety on a day-today basis.
Mr. Taborn noted that FTA is committed to working with the NTSB, the nation's rail transit agencies, and the State safety oversight agencies to address the NTSB's recommendations and to determine ways in which the SSO program can be improved. Mr. Taborn also clarified that FTA is concerned that in the investigative process used to assign responsibility for this derailment, the NTSB did not appropriately identify the roles, responsibilities, and authorities of the involved parties as specified in 49 CFR Part 659. The SSO rule has been developed to bridge local, State, and Federal authorities and responsibilities for safety oversight of rail transit agencies, and there are inherent challenges that must be addressed every day in using this framework to identify and resolve safety issues.
Mr. Taborn explained that it is understandable, in light of the facts of the derailment at CTA, that the NTSB believes "someone" should have stepped in to do "something" to prevent the systemic degradation of CTA's track. However, it is important to recognize that corrective actions cannot be required, and rail transit agencies cannot be forced to address them, without appropriate delegations of authority.
In the coming months, Mr. Taborn explained that FTA will be working at all levels to review its enabling legislation to determine if there are ways that FTA can provide rail transit safety managers, SSO agencies, and FTA's own management of the SSO Program with additional authorities to require and enforce that actions be taken to identify and address safety deficiencies.
Mr. Taborn urged the attendees to take similar actions within their own agencies to identify opportunities for improvement in the management of their safety programs and the enforcement of safety authorities.
In addition, Mr. Taborn noted that FTA has established a new Fire Safety and Analysis Program in partnership with the National Association of State Fire Marshals to analyze industry data regarding public transportation fires and to develop recommendations for preventing and fighting fires in the public transportation environment. It is FTA's hope that the findings from this program will help to address NTSB recommendations regarding needed improvements in the management of "smoke in tunnel conditions" at rail transit agencies.
Mr. Taborn also stated that in FY 2008, FTA will be kicking off new initiatives to address track worker protection and maintenance oversight issues in the rail transit industry. Mr. Taborn noted that the safety, security, and emergency preparedness problems faced by the public transportation industry are far more complex than those of 30 years ago, and implementing solutions is therefore more challenging. Aging infrastructure and increasing demands for rail transit service have raised risks for track workers and passengers, and highlighted the need for additional safety oversight of critical maintenance functions. Emerging technologies offer new opportunities for protecting public transportation passengers and employees, but also pose new risks and challenges.
Recent national and international events, such as the devastation left by hurricane Katrina, the advance of avian flu, new threats to homeland security, and the dramatic increase in local support for new investments in public transportation are altering the institutional and policy framework for transit safety and security in unprecedented ways.
FTA is continually looking for ways that it can support the efforts of the rail transit industry to improve rail transit safety and security, from the preliminary engineering phase through to operations and the decommissioning of vehicles and equipment. Mr. Taborn emphasized that meetings, such as the 11th Annual SSO Program Meeting, provide a forum for SSO agencies, rail transit agencies, and other industry stakeholders to communicate their thoughts and ideas to FTA and the rest of the SSO Community. Mr. Taborn urged the attendees to participate in each session.
Mr. Taborn reiterated that FTA is committed to the future of rail safety and security through all means available: regulation, policy, training, partnership, and technical assistance. He concluded his welcoming remarks by thanking everyone for their continued support in working with FTA to make the SSO program strong and effective. Mr. Taborn then introduced Mr. Mokhtee Ahmad, Regional Administrator for FTA's Region 7.
Mokhtee Ahmad, FTA Regional Administrator, Region 7
Mr. Ahmad welcomed everyone to Minneapolis on behalf of FTA's Administrator, Mr. Jim Simpson, FTA's Deputy Administrator, Ms. Sherry Little, and FTA's Associate Administrator for Program Management, Ms. Susan Schruth. Mr. Ahmad also explained that he was here on behalf of Ms. Marisol Simon, FTA's Regional Administrator for Region 5, which includes Minnesota. Because of previous obligations, Ms. Simon was unable to attend the 11th Annual SSO Program Meeting in person.
Mr. Ahmad stated that he joined FTA in 1998, as the Regional Administrator for Region VII, which includes Missouri, Iowa, Nebraska, and Kansas. FTA's Region VII Office is based in Kansas City, Missouri. Mr. Ahmad noted that over the last decade, he has watched the SSO program grow from its infancy to its current size, where 26 SSO agencies have been designated for 43 rail transit agencies, and several more States and rail transit agencies will join the program by 2010.
As a Regional Administrator, Mr. Ahmad noted that he provides leadership to the Regional Office in the administration of FTA's programs and the management of Federal financial assistance within the terms of the FTA Act, other Federal statutes, and regional plans. Mr. Ahmad also supports headquarters initiatives to meet goals established for FTA by the U.S. Department of Transportation and the FTA Administrator.
Mr. Ahmad noted that over the last few years, he has worked closely with Ms. Schruth, Mr. Taborn, and Mr. McElveen to identify, oversee, and achieve safety, security and emergency preparedness goals for the transit industry. Mr. Ahmad noted that he has a special interest in safety issues from his early career at the Kansas Department of Transportation, where he initiated and collaborated on the department's annual publications of selected statistics, including Age and Alcohol Traffic Accidents and Accident Statistics.
Mr. Ahmad explained that FTA manages an Annual Performance Plan, which specifies a number of different goals for the agency which must be met in each Fiscal Year (FY). In FY 2007, two goals were established related to safety, security and emergency preparedness. In FY 2008, these two goals have been combined into one over-arching goal.
Mr. Ahmad explained that it has been his pleasure to work with Ms. Schruth, Mr. Taborn, and Mr. McElveen on these goals and their supporting programs. So far, Mr. Ahmad reported that FTA has completed all required activities to meet its FY 2007 safety, security, and emergency preparedness goals, and is well underway to establish its work program for meeting the FY 2008 goal.
Mr. Ahmad urged the participants at the 11th Annual SSO Program Meeting to continue their candid dialogue with FTA regarding ways in which in the SSO program can be strengthened. Mr. Ahmad noted that with the reauthorization of SAFETEA-LU being less than two years away, it is an ideal opportunity to raise issues that should be addressed in the next transportation authorization bill. Mr. Ahmad concluded his welcoming remarks by wishing the participants a great meeting.
Brian Lamb, Metro Transit General Manager
Mr. McElveen then introduced Metro Transit General Manager Brian J. Lamb. Mr. Lamb stated that Metro Transit was very pleased to be co-hosting the 11th Annual SSO Program Meeting, and to have an opportunity to showcase both the Twin Cities and the Hiawatha Light Rail line.
Mr. Lamb began his comments by explaining that he was a little nervous to be speaking in front of the nation's rail transit safety directors and SSO program managers this Monday morning, because on Sunday afternoon at about 4:00pm, an elderly driver of a van took a U-turn in front of a Hiawatha Light Rail train, causing a collision. While the elderly driver was not seriously injured and no one on the train was hurt, the accident did shut down light rail service for about an hour on a part of the system. Mr. Lamb joked that when he was informed of the accident, the first thing he thought of was that attendees of the 11th Annual SSO Program Meeting may have been on the train, and would have a stack of detailed reports waiting for him regarding how Metro Transit managed the accident.
Mr. Lamb then asked the participants, in a show of hands, to indicate who had been to Minneapolis-St. Paul before. Most of the group had never been to the Twin Cities.
Mr. Lamb provided an overview of a few places of interest, including the shops and restaurants along the Nicollet Mall, the Minneapolis Institute of Arts, the Hubert H. Humphrey Metrodome and the Vikings Stadium. Mr. Lamb also pointed out that the Minnesota Wild, an expansion hockey team, play at the Xcel Energy Center. Mr. Lamb noted that the Republican National Convention will take place at the Xcel Energy Center in early September of next year.
Mr. Lamb cited the importance of gatherings such as the 11th Annual SSO Program Meeting to foster relationships between local, State, and Federal levels of government to promote safety, security, and emergency preparedness. Mr. Lamb explained that he has a close working relationship with his SSO agency, the Minnesota Department of Public Safety (DPS). He thanked Kent O'Grady and DPS for everything that they accomplished in working with Metro Transit to ensure a compliant safety program for the Hiawatha Light Rail line when the system opened in 2004.
Mr. Lamb explained that when emergencies happen, such as the recent collapse of the I-35W bridge over the Mississippi, these relationships and shared commitments can make all of the difference. Mr. Lamb noted that, in close coordination with FTA and U.S. DOT , within days after the bridge collapse, Metro Transit was able to obtain a $5 million grant to support the provision of additional transit service to reduce congestion. Mr. Lamb went on to report that since the collapse, Metro Transit has posted the highest ridership in its history.
Mr. Lamb also identified the ways in which the region's interoperable radio system helped to support effective response. Since Metro Transit was in constant communication with local law enforcement, Minnesota DPS, and other responders, Metro Transit was able to dispatch buses within 15 minutes to transport emergency responders from designated staging areas to specified deployment locations near the river. Metro Transit also was able to re-route its service, and within just a few hours, provide alternate routes to passengers.
Mr. Lamb observed that most Americans take safety for granted. They expect their bridges and roadways, their transit systems, their food, and their toys to be well-designed and free from any threats to their well-being. Americans do not always appreciate what is required to ensure their safety, and they quickly become outraged when their safety is jeopardized. In our society, it is incumbent upon all of us to ensure that we meet all safety standards, and that we maintain constant vigilance in our efforts to provide services and products to the public.
Mr. Lamb then provided a brief overview of Metro Transit's operations. Metro Transit has a fleet of over 820 buses, providing approximately 120 bus routes throughout Minneapolis and St. Paul. Metro Transit is making great gains in reducing fuel emissions by using hybrid buses, next-generation fuels like biodiesel and ultra-low sulfur diesel, and clean diesel technologies. Metro Transit provides approximately 220,000 daily trips on its bus system.
Since 2004, Metro Transit has also operated the Hiawatha Light Rail Line, which links downtown Minneapolis with Minneapolis/St. Paul International Airport and the Mall of America. It spans 12 miles and serves 17 stations. Ridership on the line has greatly exceeded exceptions, and has already surpassed the pre-construction estimate for the year 2020. Each day, approximately 30,000 people use the Hiawatha Light Rail system to reach their destinations.
Mr. Lamb noted that Metro Transit is now building its first commuter rail system, the Northstar line. This system will run from the Big Lake area to downtown Minneapolis along Highway 10, and will provide more than 5,000 daily trips. Metro Transit is also investigating expansion options to connect downtown Minneapolis and downtown St. Paul using light rail and bus rapid transit.
Metro Transit, like all transit agencies, is committed to safe and secure operations. Mr. Lamb pointed out that a General Manager's job is challenging, and many different options must be weighed in making decisions. Mr. Lamb stated that while he cannot always give the Metro Transit Safety Department everything it asks for, the on-going dialogue with his Safety Department and the Minnesota DPS is a critical part of his job. Whenever possible, he works with the Metro Transit Safety Department and Minnesota DPS to address issues proactively and effectively. Mr. Lamb concluded his welcoming remarks by wishing everyone a successful meeting.
Assistant Commissioner Tim Leslie, Minnesota Department of Public Safety
Mr. McElveen next introduced Lt. Tim Rogotzke, the SSO Program Manager for Minnesota DPS. Lt. Rogotzke then introduced Assistant Commissioner Tim Leslie from Minnesota DPS. Assistant Commissioner Leslie welcomed the participants at the 11th Annual SSO Program Meeting to Minneapolis. He thanked Lt. Rogotzke for introducing him, and for his hard work in taking over from Kent O'Grady in managing the SSO program for the State of Minnesota.
Assistant Commissioner Leslie also noted that since the State Police fall within Minnesota DPS, the agency has a tremendous amount of experience with traffic safety and accident investigation, and a vested interest in mitigating those situations which lead to unsafe behavior on the State's roadways and transit systems.
Assistant Commissioner Leslie clarified that though the Twin Cities may appear as one city to the rest of the nation, here is Minnesota, the river dividing the two cities is very important. Assistant Commissioner Leslie explained how he grew up in Minneapolis and then spent the first part of his career working in law enforcement in St. Paul. He noted that there are significant differences between the two cities and their residents, and that these differences are the source of wide-spread humor in the region.
Assistant Commissioner Leslie observed that though there are challenges in uniting a varied region and getting people to work together, overall the region shares a strong commitment to safety and emergency preparedness. Assistant Commissioner Leslie commended the FTA, the SSO agencies, and the rail transit agencies for making a point of getting together and knowing each other well in advance of an actual accident or emergency. Assistant Commissioner Leslie pointed out that an emergency is not the time to be exchanging business cards.
Assistant Commissioner Leslie clarified that Minnesota DPS and Metro Transit are united in their mission to respond well and effectively when things go wrong. Assistant Commissioner Leslie noted that no one wants to be criticized for a delay in providing needed resources to support victims and their families. While it sometimes is a thankless job, there are rewards in knowing that you and your agency have done the best you can to help people during the most difficult of situations.
Assistant Commissioner Leslie then described the response to the I-35W bridge collapse on August 1, 2007. The bridge over the Mississippi collapsed during rush hour, plunging dozens of cars and their occupants into the river. The calamity disrupted transportation, aimed a spotlight on public infrastructure, and evoked an outpouring of public response.
In addition to the heroic stories of the victims on the bridge working to help each other, Assistant Commissioner Leslie pointed out that the public service agencies, including Metro Transit, responded incredibly well and cooperatively. Because the region has an excellent interoperable communications system, all of the involved responders could talk to each other and respond quickly to changing needs and conditions. Also, as a result of extensive regional emergency planning and frequent drills and exercises, the responders knew each other and the respective capabilities of each other's agencies. Activities that may take many hours in some places were accomplished in minutes during the bridge response.
Assistant Commissioner Leslie also described how Minnesota DPS and Metro Transit are working together to plan for the 2008 Republican National Convention. The Twin Cities are proud to have been selected to host such an important event.
However, even one year out, there is a tremendous amount of work required to ensure a successful event. Assistant Commissioner Leslie noted that, once again, Minnesota DPS, other public safety agencies, and Metro Transit are in the difficult position of working to ensure that nothing goes wrong. Assistant Commissioner Leslie explained that though their activities may be taken for granted during the actual Convention, it is critical to go through the planning phase to ensure the safety and security of all attendees and the eventual Republican Presidential nominee.
In conclusion, Assistant Commissioner Leslie commended the assembled group for their commitment to transportation safety and security. He noted that through the SSO program, State agencies could work cooperatively and effectively with their rail transit agencies to prevent accidents, to investigate accidents and do occur, to develop corrective actions to prevent recurrence, and to ensure the protection of rail transit passengers and employees.
Following the welcoming remarks, Mr. Jim Caton and Mr. Andy Lofton, FTA SSO program contractors, delivered the meeting's first presentation. Their presentation, entitled "SSO Audit Program 2007," provided an update on FTA's SSO audit program and a summary of key findings identified through the program during 2007. They began by describing the audit process, walking the participants through a typical audit timeline as shown in Figure 1 below.
Figure 1. Audit Timeline
Mr. Caton and Mr. Lofton reviewed the materials that must be submitted electronically by each SSO agency 4 weeks prior to the audit. These materials include copies of the SSO agency's Program Standard and supporting procedures, and copies of critical materials for each rail transit agency in the SSO agency's jurisdiction, including the following:
Mr. Caton and Mr. Lofton explained that these materials are used by the audit team to familiarize themselves with how the SSO agency and rail transit agency are implementing 49 CFR Part 659 requirements. The audit team also uses these materials to populate audit checklists, maximizing verification efforts prior to the onsite records review, and facilitating finalization of audit schedules by prioritizing SSO program areas. Finally, these materials are used to develop and document pre-audit concerns and to refine questions and establish verification points for the onsite reviews and interviews.
Each audit takes approximately 3 to 4 days to complete on-site and is performed by a 3 to 4 person audit team. Audit attendees usually include the SSO agency Program Manager, the SSO agency contractor (if applicable), and safety and security department representatives from the rail transit agency.
Unlike in the past, where the SSO audits took place at the SSO agency headquarters, in 2007, most of the SSO audits have been conducted at a rail transit agency in the SSO agency's jurisdiction. This change provides FTA's SSO audit team with the chance to review records at the rail transit agency and, if appropriate, to observe specific functions, activities, or concerns that are being managed through the SSO program.
Each audit begins with an entrance briefing that is used to set the agenda for the audit and to explain the activities that will be performed. Interviews are conducted onsite using an audit checklist. Oversight processes and implementation issues are discussed, and feedback is solicited from audit participants.
The audit team also performs records reviews to verify program implementation, and SSO agency and rail transit agency documentation. As appropriate, an on-site tour or examination may be included as part of the SSO audit. Once the audit is complete, the audit team holds an exit briefing with the SSO and rail transit agency representatives to present preliminary findings and recommendations.
In making findings, Mr. Caton and Mr. Lofton explained that FTA has developed criteria to identify those instances where an element of a State's safety oversight program is determined to be either in "Non-Compliance" or in "Compliance with Recommendation."
Mr. Caton and Mr. Lofton explained how FTA's audit team makes these findings. As specified in the revised 49 CFR Part 659, there is a listing of approximately 250 distinct activities that the SSO program administered by the State must perform. If the SSO program is not performing one of these activities, a finding of "non-compliance" is made. If a State is performing the activity, but the audit team has identified opportunities for improvement based on outstanding recommendations to FTA from NTSB or the GAO related to this activity, then a "compliance with recommendation" finding is made. All other activities found to be in compliance are classified as "compliant" and no findings are made.
FTA also uses the audit process as an opportunity to identify effective practices. These practices are referenced by the SSO audit team during the exit briefing. Finally, if additional technical assistance is provided during the audit, this assistance is also noted during the exit briefing.
Once the audit has been completed, a Final Audit Report is developed to present audit activities and findings. The final report is typically delivered within 2 weeks of the audit. FTA requires that the SSO agency address all findings of "non-compliance" within 60 days. FTA includes, as part of its Final Audit Report, an Audit Findings Tracking Matrix, which contains all of the findings and provides columns for the SSO agency to describe its proposed corrective actions. FTA uses this matrix to work with the SSO agency to track all findings to closure.
When completing its responses to the audit report, the SSO agency is required to address all findings of "non-compliance." FTA also encourages each SSO agency to address each finding of "compliance with recommendation." However, in the event the SSO agency determines not to address these findings, then FTA does require that the agency provides its rationale for not addressing the "compliance with recommendation" finding.
FTA then tracks all audit findings and resolution efforts, sending out monthly reminders if findings are not closed within the 60 day period. In certain instances, depending on the nature of the finding, the SSO agency may require several months to complete the corrective action. In these cases, FTA may require bi-monthly or even quarterly updates rather than monthly updates.
Mr. Caton and Mr. Lofton then explained that all data gathered through the audit is logged into FTA's SSO Audit Program Database to support program assessment and tracking of findings across the industry. FTA also uses this information to support its management of the SSO program and to update the Rail Transit Safety Action Plan.
Mr. Caton and Mr. Lofton next summarized the audit program findings identified during the current audit cycle, which included audits performed on the SSO Programs of the Tennessee DOT , Missouri DOT , St. Clair County, California PUC , Florida DOT , Arkansas HTD , Michigan DOT , Louisiana DOTD , and Texas DOT . Figure 2 summarizes the number of non-compliance and compliance with recommendation findings generated during the current audit cycle.
Mr. Caton and Mr. Lofton further clarified the findings of non-compliance identified through the 2007 SSO Program Audit cycle. The most common findings involved situations where:
SSO agencies had approved SSPPs that did not address specific provisions contained within the SSO agency's Program Standard or specific provisions within 49 CFR Part 659;
Mr. Caton and Mr. Lofton next reviewed the finding classifications used by FTA to track and close-out findings. These classifications are defined as follows:
Mr. Caton and Mr. Lofton stated that, to date, only one (1) SSO agency has closed all of its audit findings. Sixty-eight (68) percent of all audit findings identified through the 2007 SSO Program Audit cycle have not been closed. Forty (40) percent of the agencies audited in 2007 have failed to meet submission deadlines. In addition, 30% of these agencies have failed to submit the Audit Findings Tracking Matrix on a consistent basis.
Mr. Caton and Mr. Lofton also provided examples of acceptable and unacceptable reasons for the SSO agency to delay resolution of audit findings. Acceptable reasons for delay included revisions to codes or standards that could not be expedited because they required approvals of State legislative bodies or extensive legal reviews, or the SSO agency's inability of verify implementation of corrective action until a specific event occurred, such as an accident, submittal of an annual report, or an annual certification. Unacceptable reasons for delay include non-responsiveness, and delays in revisions without clearly identifying action plans and milestone dates.
Mr. Caton and Mr. Lofton then explained how FTA tracks and manages those situations where SSO agencies fail to close out findings. FTA first sends routine emails requesting updates on the status of required materials. In the event of non-responsiveness, Mr. Caton and Mr. Lofton explained that FTA will first issue a letter to the SSO Program Manager's direct supervisor(s) asking for additional support in getting the findings closed. FTA may also coordinate with its Regional Offices and review capital project funding to get a letter issued directly to the rail transit agency.
Mr. Caton and Mr. Lofton concluded their presentation by emphasizing the need for continued compliance with FTA's SSO Audit Program and FTA's desire to continue its partnership with the SSO community. Through this program, FTA hopes to increase the quality of safety and security program implementation, to collect effective practices that can be shared with industry, and to provide technical assistance when possible.
Comments and Discussion
Following this presentation, representatives from several of the audited SSO agencies and their rail transit agencies were asked to discuss their audit experiences. The following issues were raised:
Ms. Annabelle Boyd, FTA SSO program contractor, gave a presentation on the September 6, 2007 clarification letter issued by FTA on the hazard management program requirements specified in 49 CFR Part 659. Ms. Boyd explained that participants at the 11th Annual SSO Program Meeting should have received FTA's September 6, 2007 clarification letter via email and that it was in hard copy as part of their hand-outs for this meeting.
Ms. Boyd noted that FTA prepared this letter in response to questions received from SSO agencies and rail transit agencies regarding how the hazard management program, specified in the revised 49 CFR Part 659, should be developed, documented, administered, and monitored. Ms. Boyd explained that this letter provides background regarding why FTA developed these new requirements in the revised Part 659; a detailed explanation of these requirements, including direct references to the applicable 49 CFR Part 659 provisions; and examples of effective practices used by SSO agencies and rail transit agencies to implement these provisions in their respective programs.
Ms. Boyd reminded participants that Section 659.39 of FTA's original rule required SSO agencies to get involved in the rail transit agency's hazard management program primarily during the identification, investigation and resolution of accidents and "unacceptable hazardous conditions." During public notice and comment undertaken for the Part 659 rule revision, both SSO agencies and rail transit agencies expressed their frustration with this approach. Both complained about the subjectivity inherent in defining an "unacceptable hazardous condition." SSO agencies also noted that, because of this subjectivity, occasionally, these investigations became unnecessarily adversarial. SSO agencies also complained that they had no authority to require on-going reporting regarding the rail transit agency's hazard management program.
As FTA explained in the preamble to the revised rule, FTA changed the hazard management program requirements to resolve these issues. Through these new requirements, FTA intended for the SSO agencies to actively monitor the rail transit agency's performance of the hazard management program in an ongoing manner. SSO agencies would no longer become involved in this program only after an accident or an "unacceptable hazardous condition" had been identified. Further, by removing the vast majority of minor accidents and single-person injuries from SSO accident reporting thresholds, FTA responded to recommendations from rail transit agencies that these minor occurrences would be more effectively addressed through the hazard management program.
FTA intended for this new approach to be a "win-win" for all involved parties. Rail transit agencies could document and manage minor incidents, such as slips, trips, and falls and other single-person injuries, through the hazard management program with less administrative burden. SSO agencies would receive on-going updates regarding the status of rail transit agency activities to address these minor incidents and other concerns through the hazard management program. Should a rail transit agency identify an "unacceptable hazardous condition," then the SSO agency would be much better prepared to support an investigation.
Ms. Boyd next reviewed each of the sections of Part 659 that establish the hazard management program requirements. Ms. Boyd began with the revised section 659.15 (b)(8), which requires the SSO agencies, in their Program Standards, to identify their requirements for "ongoing communication and coordination relating to the identification, categorization, resolution, and reporting of hazards to the oversight agency."
Ms. Boyd explained that this provision gives each SSO agency the authority to require ongoing reporting from each rail transit agency in its jurisdiction regarding the performance of its hazard management program. This section also provides SSO agencies with the authority to require notification and investigation reports or other information regarding the identification of specific types or categories of hazards at the rail transit agency.
Ms. Boyd then addressed Part 659.19 (f), which defines minimum requirements for what must be contained in the rail transit agency's hazard management program. In § 659.19 (f), FTA authorizes each SSO agency to require each rail transit agency to include in its System Safety Program Plan (SSPP) "a description of the rail transit agency's process used to implement its hazard management program, including activities for:
Section 659.19 (f) requires that each SSPP contain a section that addresses each of the five items specified in § 659.19 (f). Ms. Boyd explained, that in meeting the fifth item specified in § 659.19 (f), FTA expects that each rail transit agency will include a description of how it will provide ongoing reporting to the SSO agency regarding the activities performed in the hazard management program and the status of findings and hazard mitigation activities. Ms. Boyd also noted that this description should conform to any requirements specified by the SSO agency in its Program Standard to address 49 CFR 659.15 (b)(8).
Ms. Boyd then explained that Section 659.31 provides additional clarification regarding the authority conferred to each SSO agency to require each rail transit agency in its jurisdiction to develop, implement, and document, in its SSPP , a program to identify and resolve hazards. Ms. Boyd pointed out that Section 659.31 (a) states that this program must include "any hazards resulting from subsequent system extensions or modifications, operational changes, or other changes within the rail transit environment."
Ms. Boyd also noted that Section 659.31 (b) requires that the hazard management program implemented by the rail transit agency "must, at a minimum:
Ms. Boyd further explained that Section 659.31 provides each SSO agency with the authority to require each rail transit agency to document, in its SSPP or supporting procedures, the following:
Ms. Boyd then addressed Sections 659.17 and 659.25 of the revised rule, which confer the authority to each SSO agency, through the annual SSPP update, review, and approval process, to ensure that 49 CFR Part 659 hazard management program requirements are adequately addressed in the rail transit agency's SSPP . If the rail transit agency's SSPP does not comply with § 659.19 (f) and § 659.31 (a) and (b) requirements, or with the ongoing reporting provisions specified in the SSO agency's Program Standard to address section 659.15 (b)(8), then the SSO agency may reject the SSPP . This rejection would occur through the same review and approval process the SSO agency uses to ensure SSPP conformance to other § 659.19 requirements and its Program Standard.
Ms. Boyd then provided some examples of ways in which SSO agencies and rail transit agencies have complied with these provisions. For example, Ms. Boyd noted that, in Program Standards or procedures, SSO agencies ensure "ongoing communication and coordination" regarding the rail transit agency's implementation of the hazard management program by requesting the following:
Based on Initial Submissions made to FTA by May 1, 2006, and the results of SSO Audits conducted over the last 15 months, Ms. Boyd explained that the most common methods used to address these requirements include:
Ms. Boyd noted that a sample hazard tracking matrix is located on Page 58 in Chapter 9 of FTA's Implementation Guidelines for 49 CFR Part 659. Detailed recommendations for requiring a hazard management program that complies with 49 CFR Part 659 provisions are included in Section 6 - Hazard Management Process of Appendix E: Program Requirements for Development of a Rail Transit Agency SSPP , located in FTA's Resource Toolkit for State Oversight Agencies Implementing 49 CFR Part 659.
Mr. Al Fazio, General Manager, New Jersey Transit, River LINE, and Vice President, Bombardier Mass Transit Corporation, facilitated this session, which included four presenters from the rail transit industry, who described their approaches to identifying, resolving, and tracking hazards.
During his introductory comments, Mr. Fazio explained that as a General Manager, he considers an active focus on hazard management to be the best form of "enlightened self interest." Though he acknowledges that other General Managers may not be deeply invested in their agency's system safety programs, Mr. Fazio stated that, for him, in this day and age of 24-hour media and complex relationships with oversight agencies, he could not imagine a situation where he could run his agency and not be actively involved in the implementation of the hazard management program.
Mr. Fazio also explained that, while he is the General Manager of New Jersey Transit River LINE, he is not an employee of New Jersey Transit. Mr. Fazio noted that the operation and maintenance of the River LINE system is managed entirely by Bombardier, under contract to New Jersey Transit. As more and more rail transit service is being provided by contractors, Mr. Fazio explained that there is a movement within the American Public Transportation Association (APTA) to refer to rail transit agencies as "rail transit systems."
Mr. Fazio explained that while this change in terminology may seem insignificant, it is actually quite important because it recognizes that contractors, too, have accountability for critical functions, such as safety, during rail transit operations and maintenance. Therefore, in the APTA Rail Transit Standards Program and other APTA materials, "rail transit system" will be used increasingly more often as a term of the trade.
Mr. Fazio noted that one of the most challenging parts of his job is distinguishing real risk from imaginary risk. For example, he explained that most of River LINE's track runs through suburban areas where there are no threats from overhead construction, and in many cases, no buildings located adjacent to the tracks. River LINE operates Diesel Multiple Units (DMUs) so there are no overhead catenary wires. Therefore, he was actively involved in a hazard assessment which determined that River LINE's track workers did not need to wear hardhats. These workers instead now wear ball caps, which are more comfortable in the field and provide less distraction for workers who must bend over and turn their heads as part of their jobs. By assessing real risk, instead of imagined risks, River LINE was able to ensure safety and to avoid wasting its limited resources enforcing requirements for unnecessary personal protective equipment.
Mr. Fazio also noted that this focus on managing real risks has proved invaluable in working with State and Federal oversight agencies and Conrail to ensure River LINE's access to track on the general railroad system. Mr. Fazio pointed out that River LINE's DMU operate on 34 miles of single track with passing sidings from Camden to Trenton, and a 1.5 mile street-running section of embedded track in Camden. Approximately 24 miles of this alignment is on the general railroad system.
River LINE provides service on this track under the terms of a temporal separation waiver with the Federal Railroad Administration (FRA). To make this work, River LINE uses a combination of advanced rail traffic control, automatic train stop signaling, and temporal separation that yields maximum safety and track availability for passengers and freight. River LINE's operations control center also dispatches ConRail freight traffic at night, Sunday through Friday.
Because of FRA oversight, Mr. Fazio explained that River LINE's operating rules are a Northeast Operating Rules Advisory Committee (NORAC) derivative with additional rules in place for light rail transit operations. However, since River LINE has been waived from some FRA requirements, River LINE also falls under 49 CFR Part 659, and participates in the SSO program managed by New Jersey Department of Transportation (NJDOT).
As a result, River LINE has to work with FRA , FTA and NJDOT to continually demonstrate that running trains at 60 mph over single track with tightly timed meets at sidings, under conditions of temporal separation with freight traffic, is safe. Largely through River LINE's commitment to its program for assessing and controlling hazards, Mr. Fazio noted that River LINE has been able to work with FRA , NJDOT , and Conrail to extend River LINE's service hours and to ensure track access for special events.
Mr. Fazio concluded his comments by stating that it is a very exciting time to be providing light rail passenger service on the general railroad system. Hazard management and appropriate risk identification and mitigation are critical to the success of this service, and to continued dialogue with FRA regarding the possibility, one day, of truly intermingled freight and light rail service on the general railroad system. Mr. Fazio urged anyone who was interested in these topics to consider attending the 14th Railway Age Passenger Trains on Freight Railroads Conference, October 22-23, 2007, in Washington D.C.
Mr. Fazio then introduced the first speaker in the session, Mr. Henry Hartberg, Senior Manager of Operations Safety, Dallas Area Rapid Transit (DART).
Mr. Hartberg provided a description of DART's automated approach to identifying, assessing, managing, and tracking hazards. Mr. Hartberg noted that DART uses a proprietary, automated Workflow system to manage administrative tasks and that hazard identification and reporting have been incorporated into this system.
Mr. Hartberg pointed out that DART's Workflow system started in the late 1990s as a way to assign, track, and monitor accounts payable items as they moved through the procurement process. However, it quickly became apparent that this system, which enables users throughout the agency to handle and follow-up on workflow actions easily, and which allows supervisors and managers to monitor activities in real-time and to use graphical reports, had wide-spread applicability for a range of DART functions.
Mr. Hartberg explained that, in the beginning, the developers of this system were widely soliciting additional functions and features. Mr. Hartberg met with them and proposed that a hazard identification reporting function be included in the system.
For this function, Mr. Hartberg identified some of the challenges he faced in managing hazards that he believed could be addressed through an automated system:
Further, Mr. Hartberg wanted to make sure that the person filing the hazard report, his or her supervisor, and the DART Safety Department would receive automated emails notifying them of any new activity performed to address the hazard.
Mr. Hartberg also wanted the system to ensure that the hazard identification report was a simple form that the person reporting the hazard could quickly and easily file. Once the hazard identification report was filed, Mr. Hartberg noted that the DART Safety Department would need to use the system to:
Finally, Mr. Hartberg wanted the system to provide the ability, at any time, to check the status of actions performed to address the reported hazard and to provide reports, through scorecards or other features, tracking the time required to close the hazard, the number and types of reported hazards, and the individuals involved.
Mr. Hartberg noted that he was lucky to work with the system developers at the beginning of the process, when DART had not yet fully committed to the Workflow system. The hazard reporting function was only the third or fourth workflow developed, and received a lot of attention and care from the developers.
Now, DART's in-house, web-based, automated task distribution program is greatly in demand, and the developers are back-logged with dozens of requests for new workflows. However, through the strong relationship Mr. Hartberg was able to build with the developers, he was also able to get workflows for DART's random drug testing program and periodic employee physical program. To date, over 60 other workflows are used by DART.
Mr. Hartberg then reviewed screenshots from the hazard reporting Workflow, walking the participants of the 11th Annual SSO Program Meeting through the steps involved. Mr. Hartberg noted the following:
Mr. Hartberg pointed out that, using the system, supervisors and employees can choose different actions from drop down menus, such as "Move to Safety Action Required," which sends the form back to the Safety Department, "Close," "Reject," "Reassign," or "Provide Comments." The "Close" option is only a suggestion to close and requires the Safety Department to review the form and hazard log history before sending it through the Workflow process, which moves the item directly to the DSC for review. Once reviewed by the Committee, the Safety Department can choose "Permanently Close This Item" from the drop down menu, which provides final hazard closure. Any action or reporting tied to the hazard log item is tracked and linked to the item through the "Event History." This creates a complete file for the hazard report.
Mr. Hartberg also informed the participants at the 11th Annual SSO Program Meeting that the DART system is password protected and that only Mr. Hartberg or his designated proxy has the ability to close an item in the system. Mr. Hartberg also has the ability to reassign responsibility resolution activities and provide comments to an item. Mr. Hartberg or his proxy can also initiate emails to the supervisor of the individual responsible for implementing corrective actions instances of inaction.
Mr. Hartberg concluded his presentation by identifying several off-the-shelf software packages that may also be used for hazard management purposes. These included: Intuit Quickbase, Goal Enforcer (Visual), 2020 Software (Internet Based), and Webex.
Mr. Craig Macdonald, Director of Risk Management, Claims, and Safety for St. Louis Metro, presented his organization's method for identifying and managing hazards through the internal safety audit process. His presentation addressed Chapters 5, Hazard Management, Chapter 11, Internal Safety Audit Process, Chapter 13, Equipment and Facility Inspections, and Chapter 14 Maintenance Audits of St. Louis Metro's SSPP .
Mr. Macdonald began by providing a brief description of the St. Louis Metro system, which consists of 45 miles of double track, 1 junction and 3 terminal stations; 37 passenger stations; highway-to-rail grade crossings; and 87 Siemens light rail vehicles (LRVs). The system provides 3.5 million miles of service to approximately 24.7 million passengers annually. Mr. Macdonald noted that St. Louis Metro's Risk Management, Claims, and Safety Department is staffed by 21 personnel.
Mr. Macdonald explained that the SSO program for St. Louis Metro actually consists of two SSO agencies - the Missouri Department of Transportation (DOT) and the Illinois St. Clair County Transit District. These agencies have a formal memorandum of understanding and collaborative agreement between them that provides for a single SSO agency program standard. St. Louis Metro coordinates and communicates with both agencies through quarterly meetings and the Executive Safety and Security Committee.
Mr. Macdonald next began a discussion of how his agency identifies, analyzes, and eliminates hazards, pointing out that hazard identification in rail transit systems can be difficult for anyone unfamiliar with these systems. Mr. Macdonald noted that hazards can be identified through the analysis of mishaps or near misses that may occur within the system, reports made by employees or customers, or through the internal safety and security audit review process.
Mr. Macdonald noted that he would be describing how St. Louis Metro identifies hazards through its internal safety audit process. Mr. Macdonald explained that the 21 SSPP and 5 System Security Plan elements, identified in Part 659, are audited over a 3-year period. To assist auditors in completing the audits, St. Louis Metro has developed a 3-year audit schedule, which is included as part of the SSPP . This schedule, provided as Figure 3 below, includes the specific Part 659 reference for each SSPP and System Security Plan area to be audited.
Mr. Macdonald noted that, prior to performing any of its internal audits, St. Louis Metro meets with both officials from both its joint SSO agencies at least 30 days in advance of conducting an audit. Once approved by the SSO agencies, Metro formally schedules the audit.
Topics addressed during the internal safety and security audits include Facility and Equipment Inspections and the Maintenance Audit Process. For Facility and Equipment Inspections, St. Louis Metro audits the LRV inspection program, station inspections, signal houses and traction power sub-stations (TPSSs), and yards and shops. These audits are thorough and includeevaluation of facility components including fire suppression and detection equipment operation, machinery such as cranes, lifts, tools, and personal protective equipment (PPE), material safety data sheets (MSDSs), etc. LRV inspections include doors, track brakes, radius rods, ventilation systems, undercarriage, lights, and emergency systems.
The audits are performed using various standards including the SSPP , NFPA, APTA, SSO Standards, Maintenance Procedures, and Manufacturer Specifications. All findings are documented and verified using written checklists. Mr. Macdonald provided an example of the things that would be reviewed during a facility maintenance audit. These included facility maintenance SOP , housekeeping, emergency evacuation procedures, security and access controls, indoor air quality, and environmental compliance.
During an LRV audit, St. Louis Metro would review maintenance SOP , safety SOP , DOT vehicle inspection criteria, Siemens maintenance specifications, identified safety critical items, best practices, and LRV maintenance records. Mr. Macdonald noted that at St. Louis Metro, LRV inspections are modeled after the DOT and North American Out-of-Service Criteria and all vehicles with Category I defects, as defined below are removed from service.
Audit findings are then prepared by each auditor assigned to perform the audit and are reviewed by the safety manager and affected department. Typical issues identified during these audits include: deficiencies in implementation of the SSPP provisions, standard operating procedures, rulebooks or manufacturer recommendations, improper procedures used in the field (tools, training, schedules), unsafe conditions or procedures in the field (PPE, energized systems), and maintenance deficiencies.
Figure 3: St. Louis Metro Internal Safety and Security Sample Audit Table
|Audit Topic 1||Chapter in SSPP 2||FTA Ref. 659||Departments 3||2006||2007||2008|
|Safety/Security Policy, Goals, Objectives, Mgmt||1,2,4; SSP||659.19(a), (b), &(c); 659.23(a)||SAF; SEC; EXEC. MGMT; ALL||XX|
|SSPP & SSP Implementation, Review & Approval||3, 20; SSP||659.19(d) & (e); 659.23(e); 659.25||SAF; SEC; EXEC MGMT||XX|
|Hazard Management||5||659.19(f); 659.31||SAF; OPS; LRVM; MOW; ENGR||XX|
|System modification & Configuration Mgmt||7||659.19(g) & (p)||SAF; ENG; MOW; OPS||XX|
|Safety & Security Certification||6; SSP||659.19(h); 659.23(b)||SAF; ENG; RS; SEC; OPS||XX|
|Safety & security data Acquisition||8; SSP||659.19(i)||SAF; OPS; FROWM; MOW||XX|
|Accident & Incident Investigation (includes security incidents)||9; SSP||659.19(j); 659.33||SEC; SAF; ALL||XX|
|Emergency response program||10||659.19(k)||SEC; SAF; OPS; MOW; EXEC. MGMT||XX|
|Internal Safety & Security Audits||11||659.19(l); 659.23(d); 659.27||SAF; SEC||XX||XX||XX|
|Rules and procedures compliance||12||659.19(m)||OPS; MOW||XX|
|Facility & Equip inspections||13||659.19(n)||SAF; MOW; LRVM||XX|
|Maintenance audits and inspections||14||659.19(o)||LRVM; MOW||XX|
|Training & Certification & Contractor Safety||15||659.19(p)||OPS; MOW SEC; SAF; CON||XX|
|Employee Safety & Security||15; SSP||659.19(r); 659.23(c)||SAF; SEC||XX|
|HazMat/Environmental /MSDS program||17||659.19(s)||SAF; ENG; MOW; PROC||XX|
|Drug and alcohol testing||20||659.19(t)||HR; MOW; OPS; LRVM; CON||XX|
|Procurement||19||659.19(u)||PROC; ENG; MOW||XX|
|Security Threat & Vulnerability||SSP||659.23(b)||SEC||XX|
|Security Protective Measures||SSP||659.23(c)||SEC||XX|
As specified in 49 CFR Part 659, corrective action plans, to be reviewed and approved by the SSO agency, are not required for findings or recommendations developed during the internal safety audit process. However, Mr. Macdonald noted that if the internal safety audit uncovers an "unacceptable hazard" then MDOTand St. Clair County do require a corrective action plan. These hazards are reported to the SSO agency verbally within 24 hours and are followed by an initial written report within 7 days. Additional reports are provided to the SSO agency as needed.
The corrective action plan is reviewed and approved by the SSO agency when it is first submitted by Metro, and, again, once it is implemented. The Executive Safety Committee is also notified. This process is described in the SSO agency Program Standard and in Metro's SSPP .
An Internal Safety Audit Process Annual report is developed each year to summarize what audits have been completed and to provide a status of audit item closures for the past two years. The report also describes the audit processes and highlights key findings. Corrective action plans and proposed resolutions are developed or each unacceptable hazard and included in the report. The CEO of St. Louis Metro certifies the report through his signature.
In order to track corrective actions, St. Louis Metro uses a simple database that can export to a summarized format in Excel. The format matches the FTA format used on the 2006 Annual Reporting Template. The CAP Tracker uses electronic and paper distribution systems to provide applicable parties with necessary corrective action plan data such as responsibilities for closure and status. Corrective action plans are reviewed at quarterly meetings and at Executive Safety and Security Committee meetings.
Ms. Theresa Impastato, Safety Manager, New Jersey Transit (NJT), South New Jersey Light Rail, River LINE, presented NJT 's methods for identifying and managing hazards duringoperations. She began her presentation with a brief description of the River LINE, building on the overview provided by Mr. Fazio. River LINE uses Diesel Multiple Units (DMUs) to operate on 34 miles of track from Camden to Trenton, including a 1.5 mile street running section ofembedded track in Camden, NJ. River LINE operates on the general railroad system under atemporal separation waiver from FRA . ConRail freight traffic is dispatched by the River LINE control center staff at night, Sunday through Friday. Ms. Impastato explained, as noted by Mr. Fazio, River LINE is under the duel regulation of FRA and FTA, with State Safety Oversight provided by New Jersey Department of Transportation (NJDOT).
Ms. Impastato next began her discussion of NJT 's hazard identification and resolution process during operations and maintenance, stating that this process is essential to the continued safety of the system. The methods for identifying hazards within NJT 's operations and maintenance include clear communications (with control center, through communication links, work orders, and committee meetings); inspections of vehicles, facilities, and the alignment; audits of safety critical systems; review of maintenance records; and through acceptance testing. The hazard classification and management system used by the River LINE conforms to MIL-STD-882 requirements for severity and probability.
In compliance with Federal requirements and in addition to State standards, the River LINE reports hazardous conditions to the appropriate regulatory agencies including the FRA and NJDOT and, under certain conditions, will meet with NJDOT to devise a mitigation strategy and execution plan. In order to ensure the continued monitoring of the resolution of hazardous conditions, a monthly update on the River LINE's actions is sent to the SSO agency.
Quarterly hazard management meetings are also held by NJDOT , in which each railroad under their oversight presents an update on the progress of their hazard resolution actions. These meetings enable all operating entities under State Safety Oversight to share information, evaluate best practices and engage in discussion and review of current events. Quarterly updates are also sent to FRA on the progress associated with reportable conditions.
Internally, hazardous conditions are tracked via an Access database with monthly reports being made available to the SSO agency. During the monthly System Safety Committee meetings, open items are tracked in the meeting minutes and reviewed for action. Daily management meetings are held in the mornings, which also track the progress being made on open action items. Monthly management meetings are also held, during which time, more in depth tracking of actions takes place. Hazardous conditions are analyzed and evaluated to determine root and contributory causal factors. Based on the root cause findings, mitigation will include a combination of procedural, operational, and mechanical changes in practice.
Ms. Impastato explained that the River LINE has sought to actively identify, mitigate, and document hazardous conditions during operations. She then provided two examples, involving (1) human factors and (2) system integration deficiencies. The first example involved stop signal violations, which are typically caused by an operating rule violation in which the LRV operator fails to properly acknowledge a restrictive or approach signal indication and proceeds past the upcoming stop signal. The second example involved loss of shunt (LOS) incidents, which are caused by the failure of the light rail vehicle (LRV) to properly occupy a track circuit resulting in the potential for the signaling system to display a "false" proceed indication.
To address the first example, Ms. Impastato provided greater detail regarding the River LINE's signaling systems. The River LINE is a single track railroad with passing sidings that employ a Northeast Operating Rules Advisory Committee (NORAC) compliant wayside signal system designed for a freight braking profile. The use of a fixed light rail transit (LRT) approach sign indicates to an LRV operator the braking distance to the signal. The signal system includes automatic train protection (ATP) in the form of trip stop inductors used to arrest the motion of a vehicle passing a stop signal through a penalty application of the emergency braking system.
Ms. Impastato noted that River LINE experienced a series of stop signal violations which exceeded the industry average occurring over a three year period. As a result, NJT performed an analysis of the signal violation conditions to determine root causes and to verify any suspected statistical relationships. Initially, a number of factors were thought to be causing the signal violations. These included the location of the violation, direction of travel, length of time in service, time of day, weather conditions and visibility, and fatigue. While certainly contributing to the probability stop signal violations, none of these causal factors showed a statistically significant relation to the probability of a signal violation occurring.
NJT next interviewed operators to determine if there was a common thread between the signal violation incidents. The vast majority of the LRV operators who had violated a stop signal stated that they had observed the approach signal indicating that they were to approach the next signal prepared to stop and upon seeing an opposing movement clear their consist, presumed that the signal was permissive for their movement. Ms. Impastato pointed out that this turned out to be one of the most significant findings in addressing the signal violations as distraction and complacency require different methods of mitigation than presumption.
To mitigate the hazardous condition, a white paper was first written on the River LINE's stop signal violation reduction program, focusing on the reduction of violations through operational and procedural means. This was done because the violations were related to human factors.
Additionally, when a stop signal is passed the trip stop inductor activates the LRV emergency braking system stopping the LRV prior to the fouling point of any switch. The opposing interlocking signals are immediately set to stop with active trip stop inductors to stop any train from entering the fouled interlocking. The central control system receives a "passed stop signal" alarm indicating to the dispatchers that all permissive signals have dropped and all train traffic in the area has stopped
Also, the disciplinary policy was reviewed and minor revisions were made creating a progressive policy to address repeat offenses. Investigation procedures were also reviewed with emphasis on improved root cause determination of signal violations; and post-incident review requirements were established for operator retraining.
NJT also implemented a number of operational mitigations. Operators were instructed to announce any restricting or approach signal indications received over the radio. This was required to enhance the operator's situational awareness via a verbal reminder of upcoming conditions. The Rules and Procedures Efficiency Checks program was reviewed. Increased check rides and banner obstruction tests were performed along with reverse routing practices employed at random to alter the signal indications received in the field. Random LRV downloads are taken daily and reviewed by the Safety Department and Trainmasters to evaluate operator compliance with rules and restrictions. When a pattern of non-compliance is observed, the operator is subject to re-training and increased frequency of ride checks in order to establish proper habits in the operator.
Systemic changes include a bi-weekly signal preview ride in which the Signal Maintenance Supervisor is required to make a round trip check ride to ensure that all signals have acceptance previews. Also, LRT approach signs were enlarged.
Potential long-term mitigations include the installation of a cab-signaling system for the River LINE, in which operating speeds are enforced via an indication in the operators cab and penalty braking applications. While a cab-signaling system will not eliminate the potential for a signal violation, it will reduce the severity of a violation markedly via the enforcement of operating speed.
After the implementation of these mitigation actions, the River LINE has observed a 78% reduction in signal violations.
Ms. Impastato next gave further details regarding the loss of shunt incidents the River LINE began experiencing in the fall of 2005. The cause of these incidents was believed to be excessive leaf build-up on the rail and subsequently on the LRV wheels. In response to this condition, the River LINE implemented several operational mitigations. First, the Central Control System alarms alert controllers via a "Loss of Indication" alarm when an interruption in the track circuit occurs. Upon receiving the alarm, the control center applies blocking devices to the interlocking signals and switches and instructs all trains to report clear of the CP in question, further increasing the margin of safety incurred via the "clear block" operating practice.
Maintenance mitigations included dispatching signal maintainers to the field to verify the alarm concurrently with the operational mitigations taking place. Field conditions are documented. Vehicle maintenance crews also inspected the LRVs that lost indication and noted any abnormal wheel conditions.
In order to effectively mitigate the hazardous condition created by a Loss of Shunt or LOS Incident, River LINE first needed to determine the causal factors contributing to the occurrence of these incidents. This began with an extensive statistical analysis of the incidents. Twentyeight LOS incidents occurred on the River LINE alignment during the period from November 1, 2005 through November 14, 2005. Variables analyzed to determine if there was a significant statistical relationship between their values and the probability of a LOS incident occurring included direction of travel, length of time elapsed since last LRV wheel truing, location, scrubbing activity by location, ConRail movement by location, weather conditions, length of track circuit, time of day, LRV consists, and interlocking and ABS territory.
Due to the short time frame of data available, all common causes of variation may not have been introduced into the sample in proportion to their relative size in the population. The small sample size may have introduced a minor bias into the data.
Four variables including weather, time of day, location, and length of track circuit exhibited a statistically significant relationship to the probability of experiencing a LOS incident. These four variables were further analyzed using multiple regression analysis to determine their interactions and to examine any spurious correlations which may have existed. Through this analysis, it was determined that time of day and weather appeared to be strongly correlated, but are not statistically independent.
After confirming the causal factors statistically, the next step was to look at reducing the probability of a LOS incident occurring by focusing efforts on the reduction of the effects of each variable. Since controlling the weather or leaf drop was not feasible, the River LINE sought to control the influence of these factors. A three pronged approach was taken to address the condition focusing on integration of the track conditions, the signal system, and the vehicle system.
In order to control, to the fullest extent possible, the environmental conditions which contribute to the probability of experiencing a LOS incident, the River LINE has undertaken an extensive vegetation control program. This program includes brush cutting and pre- and post-emergent weed spraying concentrating on the areas where a loss of shunt incident occurred.
Signal system mitigations included increasing LOS timing in other areas. A modification to the LOS timing in CP 242 and CP 269, both problem areas, was completed in 2006. Increasing the LOS timing in these areas has proven to be effective at reducing the number of shunting incidents experienced in 2006. Comparison between sample populations of LOS incidents experienced in 2005 and 2006 showed a 40% reduction in the test areas with increased LOS timing. Based on the success obtained in reduction of LOS incidents within the pilot area versus the remainder of the alignment, an increase to 15 seconds of LOS timing was implemented system-wide in January 2007. NJT also split long (over 5000 ft) track circuits into multiple circuits. This work is expected to be completed during the fall of 2007, and should also mitigate LOS issues experienced during rainfall.
Track condition mitigations included an "Aqua Train" and profile grinding of the rail. The Aqua Train is a high powered water jet system used by NJT to clean contamination from the rails. The train is currently being evaluated for use on the River LINE. Research has been conducted on similar consists across the US, and a tank car and a flat car have been procured for use as an aqua train on the River LINE.
Profile grinding of the rail to modify the wheel/rail contact patch in order to improve shunting capabilities is being evaluated for a system-wide application excluding the street running sections of track. Two wayside shunt enhancers were also procured for installation in problem track circuit areas in 2006. Installation on track circuit 2541 was completed feeding both directions. Monitoring of the enhancer's performance has taken place with two private crossings which pose no hazard to vehicular traffic if the crossing system malfunctions. Initial results appear to improve shunting capabilities and additional units have been installed in identified problem areas. Further evaluation of the effectiveness of these mitigations will occur during the fall of 2007.
Cast iron wheel shoes were designed to eliminate the contaminant build-up on the LRV wheel sets. Stainless steel and composite material shoes were also evaluated. Cast iron was considered to be the preferred material due both to its longer wearing qualities and its ability to "rough" up the wheels allowing the wheel to bite through the leaf matter on contaminated rails. Tests of the wheel shoe effectiveness were conducted with significant improvements to shunt capabilities in adverse conditions noted. Third generation wheel shoes will be evaluated during the fall 2007.
A peer review consisting of representatives from railroads who have experience in shunting and adhesion problems will also take place in October of 2007, and continued information sharing is taking place between the River LINE and other systems world-wide with regard to leaf contamination.
Ms. Impastato explained that since the River LINE does not experience LOS Incidents outside of the fall season, each change made during the preceding year is carefully tracked and evaluated for its impact on the shunting capabilities of the system.
Mr. Nagal Shashidhara, Director of System Safety and Quality Assurance Program for Light Rail Operations, New Jersey Transit gave a presentation outlining challenges experienced by rail transit agencies who use Military Standard 882 D (or earlier versions) in guiding their hazard assessment activities. Mr. Shashidhara noted that he is frequently frustrated when applying MIL-STD 882 in the rail transit environment, because the standard was designed to support space travel and advanced weapons systems.
Mr. Shashidhara explained that in MIL-STD 882, a single fatality is a catastrophic event. Mr. Shashidhara noted, much to the collective amusement of participants at the 11th Annual SSO Program Meeting, that there are no grade crossings in space. Also, there are no trespassers or suicides or automobile drivers making illegal left turns in space.
Yet in transportation, there are approximately 45,000 annual fatalities on our roadways, and the rail transit industry experiences 60 to 80 fatalities each year. Managing risk, even from fatalities, is a critical part of what rail transit agencies do. However, since MIL-STD 882 is based on an extremely high standard, more suitable to the National Aeronautics and Space Administration (NASA), application of this matrix in the rail transit environment tends to encourage overly restrictive requirements that do not contribute to overall safety and, that sometimes, lead to impractical conclusions.
In assessing and resolving risk, Mr. Shashidhara noted that the three light rail transit agencies in New Jersey have a variety of processes they use to identify, evaluate, and control hazardous conditions. Acceptable risks are determined through engineering means, combined with education, training, enforcement and disciplinary actions.
Mr. Shashidhara expressed his opinion that much of risk management in the rail transit industry ultimately centers on creating conditions that lead the public, customers, and transit operating staff to appropriate behavior. Mr. Shashidhara emphasized that experience in transit system safety, local environmental settings, and actual data should play a key role in assessing hazards. He further explained that in the operation of a transit system, there are many situations that may result in an unwanted event and that transit systems should implement programs to avoid such events, even though doing so may require the system to take a chance at achieving an operational gain versus some future, low probability, potential loss.
Mr. Shashidhara next reviewed the consequences of ignoring risks, by first defining risk as the potential for the realization of unwanted, negative consequences of an event. He explained that risk reduction involves avoidance of losses and the unwanted consequences as well as the probability and potential for such losses. These losses can take financial, human, legal, and other forms such as diminished public confidence in the system or environmental impacts.
While there may be some general agreement in the rail transit industry on the importance of resolving "unacceptable" hazards, many rail transit agencies spend most of their time focusing on "undesirable" hazards. For these hazards, the risk can be tolerated if it can be demonstrated to be as low as reasonably practicable, following senior management review. Therefore, while potentially serious, these events do not necessarily justify the expenditure of resources for their remediation. Examples of undesirable hazards or risks provided by Mr. Shashidhara included:
Also, Mr. Shashidhara pointed out that rail transit agencies must assess the impacts of other undesirable events on risk, such as the following:
In applying the MIL-STD-882 matrix to these events, rail transit agencies receive little more than confirmation that the risks, are in fact, "undesirable." However, the MIL-STD 882 matrix does not provide sufficient detail regarding what a rail transit agency should do - if anything - to prioritize or mitigate these risks. It does not help safety managers indicate where additional resources should be applied.
Mr. Shashidhara then reviewed other models in use in this country and abroad that expand the basic MIL-STD-882 precepts to include other elements, such as "hazard detectability" and "operational impacts." Hazard detectability is a measure of the ability to adequately detect, notice, and communicate an unsafe condition or action. Operational impact addresses potential interruption of service as a result of the event. By adding these two features to the basic MIL-STD 882 matrix, the resulting Risk Criticality Number (RCN) provides a relative scale of priority. Mr. Shashidhara noted that by using this approach, hazard severity can measured according to the following scale:
|IM||Multiple Fatalities - 10 or more. Extensive damage, and/or loss of a major station for an extended period (most severe).|
|I||Fatalities - 9 or less. Major system damage, but less than total loss of a major station facility. Loss of a tunnel; loss of multiple tracks; extensive loss of rolling stock.|
|II||Severe injury, severe occupational illness. Severe system damage, loss of track, loss of rolling stock.|
|III||Minor injury, minor occupational illness, or minor system damage.|
|IV||Less than minor injury, occupational illness, or system damage (least severe).|
Hazard probability can be measured as follows:
|DESCRIPTION||LEVEL||FREQUENCY FOR SPECIFIC ITEM(S)(Events/Hour)||SELECTED FREQUENCY FOR FLEET OR INVENTORY (Multiple of single items)|
|FREQUENT||A (most frequent)||Likely to occur frequently Greater than 10-3||Continuously experienced|
|PROBABLE||B||Will occur several times in the life of the item 10-6 to 10-5||Will occur frequently 10-3|
|OCCASIONAL||C||Likely to occur sometimes in the life of the item 10-6 to 10-5||Will occur several times 10-4|
|REMOTE||D||Unlikely to occur but possible in the life of the item 10-7 to 10-6||Unlikely but can reasonably be expected to occur 10-6|
|IMPROBABLE||E (least frequent)||So unlikely it can be assumed it may not be experienced, lessz than 10-7||Unlikely to occur but possible 10-7|
Hazard detectability can be measured as follows:
|DESCRIPTION||Level of Detection|
|Da=1.0||No detection prior to event (not detectable)|
|Db=0.75||Less than adequate detection, notice, communication|
|Dc=0.55||Partial detection, notice, communication|
|Dd=0.15||Adequate detection, notice, communication (easily detectable)|
Operational impact can be measured as follows
|DESCRIPTION||Level of Operational Impact|
|Ola||Mass evacuation of station or 100% service shutdown greater than 1 day (most|
|Olb||Less than mass evacuation of station or service shutdown of 100%, 60% capacity loss for a single day|
|Olc||Evacuation from tunnel, 10% capacity loss for 1 day|
|Old||Loss of service less than 10% for 1 day (least severe)|
Using these measures, Mr. Shashidhara noted that the worst possible combination would consist of a Severity of IM (most severe), a Frequency of A (most frequent), a Detectability of Da (not detectable), and an Operational Impact of Ola (most severe).
Another model, used in India, expands this approach even further. Following this model, hazard frequency classifications are determined using the following:
|F1||Frequent||Greater than 10 incidents per year|
|F2||Common||1 to 10 incidents per year|
|F3||Likely||1 incident to 1 every 10 years|
|F4||Rare||1 every 10 years to 1 every 100 years|
|F5||Unlikely||One every 100 years to one every 1,000 years|
|F6||Improbable||1 every 1,000 years to 1 every 10,000 years|
|F7||Incredible||Less than 1 every 10,000 years|
Safety Severity categories include:
|SR||Safety Related||No significant effect on safety, but with other faults could result in hazard to passengers, public, or staff|
|S1||Service||Delay of train service causing station overcrowding|
|S2||Minor||First aid treatment, station closure|
|S3||Serious||Injury requiring doctor attention, evacuation of one or more trains|
|S4||Major||One or more severe injuries|
|S5||Critical||1 or more fatalities or numerous injuries|
|S6||Catastrophe||More than 10 fatalities|
|S7||Disaster||More than 50 fatalities|
Reliability measures include:
|RR||Safety Related||No significant effect on service, but with other faults could result in service disruption|
|R1||Service||DDelay of train service causing queuing and overcrowding, or trains from entering service|
|R2||Minor||Great delay of service, or temporary station closure, train(s) taken out of service|
|R3||Serious||Delay of service (20 min), closure of station for two or more hours|
|R4||Major||Severe service disruption, trains strained, closure of station for more than 1 day|
|R5||Critical||Disruption of train service throughout system, closure of any part of system for 1 or more days|
|R6||Catastrophe||Closure of 1 to 4 weeks|
|R7||Disaster||Closure of 4 or more weeks|
Frequency, safety severity, and reliability are then combined to generate the following Risk Criticality Matrix:
|Severity Frequency||Service S1/R1||Minor S2/R2||Serious S3/R3||Major S4/R4||Critical S5/R5||Catastrophe S6/R6||Disaster S7/R7|
|Likely 10-1 -1/yr||C||C||C||A||A||A||A|
|Rare 10-2-10-1 /yr||D||D||D||B||A||A||A|
|Unlikely 10-3 -10-3 /yr||D||D||D||D||B||A||A|
|Incredible Less than 10-4/yr||D||D||D||D||C||C||B|
Each risk classification is defined as follows:
|A||Risk should be considered broadly unacceptable for those groups for whom the agency has a prime duty of care, including passengers, staff, and ordinary members of the public.|
|B||Level of risk is undesirable. The risk can only be tolerated if it can be demonstrated to be as low as reasonably practicable, and following senior management review.|
|C||Level of risk is broadly tolerable, provided that it can be shown that risks are being managed as low as reasonably practicable. Technical review is required to confirm whether further risk reduction measures are justified.|
|D||Level of risk is broadly acceptable, and further risk reduction measures should be implemented only if they can be shown to be justified on a cost - benefit basis. Technical review is required to confirm that the risk assessment is reasonable.|
Mr. Shashidhara noted that both of these approaches offer clear advantages for the rail transit industry over the MIL-STD-882 matrix. Mr. Shashidhara recommended that FTA work with the SSO agencies, the rail transit industry, and APTA to review the current MIL-STD 882 matrix to determine if a new, more applicable model should be included in 49 CFR Part 659.
Mr. Shashidhara recommended the formation of a Task Force to review these issues in greater detail. Mr. Shashidhara noted that judicious application of the risk analysis process for rail transit operations must consider all of the above mentioned factors. Using these factors, a revised matrix may be developed to allow for greater flexibility in transit operations.
During the Monday afternoon session of the 11th Annual SSO Meeting, the attendees broke up into two groups. Each group was given three hazard scenarios to evaluate and discuss. The scenarios included:
For each scenario, each group was asked to consider several questions:
After each group evaluated their respective scenarios, the attendees reconvened to report back their findings and conclusions. In general, each group determined that the scenarios were not "unacceptable hazardous conditions" and, as such, did not have to be reported to the SSO agencies. However, each scenario required actions to be taken, and if left unaddressed, could potentially result in an accident.
Meeting participants voiced their appreciation for the hazard management exercises, stating that the exercises helped States and transit agency representatives to address confusion surrounding the hazard management process and observe and discuss the varied approaches implemented throughout the industry. FTA appreciates the feedback from participants and will develop similar group exercises for future meetings and workshops.
On Tuesday, September 11, 2007, NTSB conducted a public hearing regarding its 14-month investigation into the July 11, 2006 derailment on the Chicago Transit Authority (CTA) Dearborn Blue Line subway. As a result of its investigation, NTSB determined that a deficient safety culture existed at CTA that allowed the track infrastructure to deteriorate to an unsafe condition.
NTSB also determined that CTA's State oversight agency, the Illinois Regional Transportation Authority (RTA) and FTA, through its oversight of Illinois RTA, failed to require CTA to develop corrective actions to address identified safety deficiencies. Specifically for the CTA derailment, NTSB identified concerns with:
NTSB adopted recommendations for CTA, Illinois RTA and FTA. During the hearing, NTSB stated its opinion that implementation of these recommendations would strengthen the SSO program and its implementation at CTA and all other rail transit agencies affected by 49 CFR Part 659.
Ms. Annabelle Boyd, FTA SSO program contractor, provided an in-depth presentation regarding NTSB's findings and recommendations. Ms. Boyd began with a description of the CTA derailment.
On Tuesday, July 11, 2006 at a little after 5:00 p.m. the operator of CTA train number 220, an 8-car train traveling northbound in the CTA Blue Line subway, received a "blue light alarm" on his control panel, indicating a problem with one of the cars. The train had operated normally through Clark/Lake Station and was proceeding toward Grand/Milwaukee station. The "blue light" operated in conjunction with an exterior indicator that illuminated both sides of the problem car.
The operator stopped the train, and looked back through his window to determine which car was having problems. He was unable to see the external indicator light due to track curvature and limited visibility. The operator decided to address the problem at the next station, and proceeded forward. As the train began to move, its emergency-braking mode automatically activated and brought the train to a stop.
The last car of train number 220 had derailed in a slight curve to the left approximately 53 feet past Clark/Lake Station. The point of derailment, later identified by NTSB, was the approximate location where the train was when the "blue light" warning activated.
At the point of derailment, an electric arc caused material under the train to catch fire. Thick smoke began to fill the tunnel. The front of the train was now located approximately 350 feet from the emergency exit grate at Clinton and Fulton.
The train operator immediately contacted CTA's Control Center and requested that power be removed. The train operator then exited the train and walked along the catwalk to investigate. Many passengers had self-evacuated from the rear of the train and were walking toward him, reporting smoke and fire. The train operator used his voice and hand signals to direct more than 1,000 passengers away from the smoke to the emergency exit grate at Clinton and Fulton. The train operator also checked each car to make sure that the passengers were evacuating.
Ms. Boyd noted that the evacuation took a little less than an hour. The Chicago Fire Department, which assisted in the evacuation, reported that 152 persons were treated for injuries, mostly related to smoke inhalation. There were no fatalities. Total damage to the derailed CTA vehicle and track exceeded $1 million.
Ms. Boyd then described the NTSB response to the derailment. After being notified, NTSB immediately dispatched a 12-member investigation team to CTA. During the course of its on-site investigation, NTSB:
NTSB also conducted a three-hour interview with FTA on November 28, 2006 to discuss the SSO program and FTA's oversight of the Illinois RTA. NTSB was represented by Mr. James Southworth, Director, NTSB Railroad Division; Mr. James Henderson, Investigator-in-Charge of the CTA derailment; and Mr. Robert Campbell, Railroad Investigator on the CTA derailment.
FTA was represented by Mr. Scott Biehl and Mr. Richard Wong from FTA's Office of Chief Counsel (TCC); Mr. Ronald Hynes from FTA's Office of Research, Demonstration and Innovation (TRI), and Mr. Michael Taborn from FTA's Office of Safety and Security (TPM-30). FTA Administrator James Simpson and Mr. Richard Steinmann, Senior Advisor to the Administrator, were also in attendance.
During the meeting, FTA reviewed its enabling legislation and the approach FTA used in developing 49 CFR Part 659. FTA also answered a number of questions from the NTSB investigators regarding:
Ms. Boyd then turned to the September 11, 2007 NTSB hearing. Ms. Boyd noted that NTSB determined that the probable cause of the derailment was:
"The Chicago Transit Authority's ineffective management and oversight of its track inspection and maintenance program and its system safety program resulted in unsafe track conditions."
In making this finding, for the first time, NTSB cited the system safety program managed by a rail transit agency part of the probable cause of an accident it investigated.
NTSB also determined that contributing the derailment were:
"The Illinois Regional Transportation Authority's failure to require that action be taken by the Chicago Transit Authority to correct unsafe track conditions, and the Federal Transit Administration's ineffective oversight of the Regional Transportation Authority."
With this determination, for the first time since 49 CFR Part 659 went into effect in 1997, the NTSB cited the inaction of an SSO agency as a contributing factor for a rail transit agency accident. Further, this is the first time ever that NTSB has cited FTA's oversight of an SSO agency as a contributing factor to an accident it investigated.
Ms. Boyd then reviewed NTSB's rationale in making these findings of probable cause and contributing factors. Ms. Boyd noted that NTSB determined that this derailment was an "organizational accident," resulting from systemic failures at every level within CTA, Illinois RTA, and FTA.
NTSB determined that CTA had adopted a flawed track inspection process, where track inspection and maintenance were performed by the same individuals. Track inspectors worked Monday to Friday, 7:00am to 3:00pm. They inspected track on Mondays and Thursdays. On Tuesdays and Fridays, they made minor repairs to the defects they had identified during inspections. On Wednesdays, they worked as part of maintenance crews to address larger defective track conditions.
During the hearing, NTSB investigators questioned why CTA would structure this organization so that inspectors would be responsible for identifying repairs that they would then have to make. NTSB believed that this organization was poorly designed, and limited the integrity of the track inspection process.
NTSB also expressed concerns about the track inspection process itself. When walking track, inspectors had to confirm that the optimal gage of 56 and ½ inches was in place to sustain train speeds of 25 mph. The allowable speed for track gage equal to 58 inches was 6 mph. If inspectors identified track gage beyond 58 inches, the track should be removed from service.
In managing these inspections, track inspectors were equipped with a flashlight, a tapeline ruler or a carpenter's fold-out ruler, chalk, a pen, and a note pad. NTSB also noted that no gage templates or automated inspection devices were used, and that lighting in the subway tunnels was poor. Locations of needed repairs were marked in tunnel walls and rail with chalk and written on note cards, for later transcription to the inspection reports. However, track inspectors left the tracks at 2:45pm, each day, leaving little time for documentation on the day in which the inspection was conducted.
NTSB noted that there were missing inspection records. In fact, more than 80 percent of inspection records were missing for the Blue Line territory where the derailment occurred between May 1 and July 11, 2006. A 12-month expanded review of all track inspection records showed:
NTSB also found that there was insufficient inspection time provided. NTSB observed a "typical day" of track inspection in the Blue Line territory where the derailment occurred. In this case, the inspection territory was 6.22 miles long - 3.11 miles in each direction. Inspectors entered the track at 9:00am when train headways were reduced to 7 minutes, and left by 2:45pm. There was no weekend, nighttime, or overtime track inspection scheduled. Inspectors walked track, but faced constant distractions from oncoming trains and the need to clear. Perhaps 4 of every 7 minutes could be spent on track inspection. During the "typical inspection" observed by NTSB, the inspector was unable to complete the assigned inspection. He was about 1.5 miles short. However, the inspection report was completed for entire territory.
NTSB also concluded that CTA failed to provide an adequate number of personnel to perform inspections. CTA only had 2 inspectors per territory. There were no back-ups or "floating" personnel. In the event of the absence of one of the inspectors, due to illness, vacation, holidays, or other reasons, inspections could not take place. NTSB also determined that maintenance took priority over inspection, and that inspections would be halted and inspection personnel would be utilized to make priority repairs on Mondays and Thursdays. Finally, NTSB observed that, while CTA management expected inspections to get done, they provided no additional time for track inspectors to walk track and made no allowances for over-time.
NTSB also observed the limited training and qualifications for CTA track inspectors. NTSB noted that these inspectors were required to have one year of construction experience and one day of classroom training on CTA's Track Maintenance Standards Manual. While this training did cover the 16 possible indications of a gage problem, including dark streaks on the inside rail of a curve, lateral movement of a tie plate on the tie or rail on the tie plate, missing spikes, and poor tie conditions, the training did not cover special issues associated with conducting inspections in tunnels or on elevated structures, or problems associated with electrolysis and corrosion. NTSB noted that inspectors they interviewed stated that this training covered too much material in one day, and was difficult to implement in the field.
After completing the one-day training course, CTA inspectors then went through one year of on-the-job training, where they worked with a more senior inspector. There were no qualification exams, refresher training, or formal performance evaluations provided by senior management. NTSB found that even these minimal requirements has not been met, and there was wide-spread evidence of inexpert and inappropriate repairs on the track.
Finally, NTSB found that CTA, which relied solely on the visual inspection of its track, failed to use technology advancements, such as track geometry vehicles and rail defect detector vehicles, to ensure track integrity. NTSB also expressed its opinion that CTA's track standards were incomplete because they did require rail flaw detection or track geometry inspection, and did not include rail fastener requirements and corroded rail requirements.
NTSB determined that:
"The dark area on the inner rail of the curve, the abrasion on the tie plates and ties, the broken lag screws, and the tie plates' elongated fastener holes in the area of the derailment were all readily observable and should have been documented during walking inspections."
NTSB found that because CTA "failed to establish an effective track inspection and maintenance program, unsafe track conditions and deficiencies were not corrected."
Missed Opportunities in Safety Oversight
Based on its investigation, NTSB also determined that there were a series of failures in the safety oversight process that should have identified the deficient track conditions and required corrective action, but did not. NTSB referred to these failures as "missed opportunities."
Ms. Boyd then briefly reviewed each of these "missed opportunities" identified by NTSB.
Missed Opportunity #1: 2004 APTA Safety Review
An APTA Rail Safety Review was conducted at CTA in 2004. This review made two findings on track inspection:
While the APTA Review was voluntary, corrective actions were not developed, followed up, and resolved by CTA.
Missed Opportunity #2: 2005 CTA Internal Safety Audit Process (ISAP)
During its 2005 ISAP of track inspection and maintenance, CTA's system safety officers and engineers:
During its 2005 ISAP, CTA's system safety officers reviewed implementation of CTA's SSPP requirements with senior management in the maintenance function, and received assurances and reports showing that the specified inspection activities and corresponding oversight were being performed as documented in the SSPP .
In its 2005 ISAP, CTA's system safety officers made no findings regarding the performance of track inspection and maintenance. NTSB found this approach to be highly inadequate, and determined that CTA's safety function needed additional authority to oversee implementation of the SSPP provisions related to track inspection.
Missed Opportunity #3: 2004 Illinois RTA Three-Year Safety Review
As part of its 2004 Three-Year Safety Review, Illinois RTA conducted a "field observation" of the CTA track and stations. Illinois RTA observed the following conditions:
It should be noted that none of these conditions were observed in the area where the derailment occurred, and that this "field observation" was conducted from CTA station platforms.
Illinois RTA also noted that there were fewer track inspection personnel at CTA when compared to other similar transit systems, and less formal training of track inspection personnel at CTA than is typically provided in the industry.
Based on these observations, Illinois RTA reviewed CTA's annual Capital Improvement Plan, and noted that approximately 4,000 tie replacements were scheduled for both the Blue and Red Lines, and that grouting initiatives were underway in the Blue Line and the Red Line tunnels to stem water seepage. Further, Illinois RTA determined that, in 2004, CTA was implementing its scheduled maintenance program. Also, Illinois RTA determined that:
As specified in FTA's Part 659, Illinois RTA issued findings requiring corrective action only on whether CTA was implementing the track maintenance section of its SSPP and whether this section needed to be updated. Since CTA had adopted the voluntary APTA Standard for Rail Transit Track Inspection and Maintenance as part of the facilities maintenance program referenced in the SSPP , Illinois RTA made a finding that:
Based on the training elements identified for track inspectors in the SSPP , Illinois RTA also issued a finding that:
However, Illinois RTA did not demand immediate correction of the deficient track conditions noted in its "field observation" because the agency believed this was beyond the scope of its authority. Illinois RTA, based on its review of CTA's Capital Improvement Program and scheduled maintenance program, believed these deficiencies were scheduled to be repaired.
Illinois RTA used a corrective action plan tracking matrix to document its follow-up with CTA:
Illinois RTA accepted these responses. NTSB found this approach inadequate. NTSB concluded: "Because the Regional Transportation Authority failed to follow up with the Chicago Transit Authority and prompt action to correct safety deficiencies identified in the triennial report, unsafe track conditions continued to exist that should have been corrected."
Missed Opportunity #4: FTA SSO Program Monitoring
NTSB also cited FTA for failing to make Illinois RTA require corrective actions from CTA to address the observations in its 2004 Three-Year Safety Review. NTSB notes that for a variety of reasons relating to the events of September 11, 2001 and the dramatic increase in the size of the SSO program between 2002 and 2005, FTA failed to stick to its three-year audit cycle for Illinois RTA.
NTSB also pointed out that FTA failed to require and review Illinois RTA's 2004 Three-year Safety Review Final Report, thereby missing an opportunity to require Illinois RTA to demand that CTA develop corrective action plans to address the track deficiencies. NTSB noted that FTA only received the authority to require these reports in its revision to 49 CFR Part 659 published in the Federal Register on April 29, 2005, which went into effect on May 1, 2006. However, NTSB still believed that FTA should have reviewed this report and required Illinois RTA to demand corrective action for the deficient track conditions.
Finally, NTSB cited FTA's failure to ensure that Illinois RTA's SSO program devoted sufficient personnel and technical resources to the oversight of CTA. NTSB determined that these failings were evidence of FTA's inadequate support for the SSO program.
NTSB found that: "The Federal Transit Administration's oversight of the Regional Transportation Authority's Rail Safety Oversight Program was inadequate and failed to prompt actions needed to correct track safety deficiencies on the Chicago Transit Authority's rail transit system."
After laying out the NTSB rationale for its findings, Ms. Boyd then raised some concerns that FTA, Illinois RTA, and CTA have regarding this investigation and its determinations of probable cause and contributing factors. Ms. Boyd noted that the CTA derailment, and the systematic degradation in track conditions that caused it, is a serious accident with important implications for the entire rail transit industry.
However, in its presentation of FTA's 49 CFR Part 659 requirements, Ms. Boyd pointed out that NTSB did not appropriately identify the roles, responsibilities, and authorities of CTA's system safety department, Illinois RTA, the FTA, and the local and State agencies that fund CTA. NTSB implied that the CTA system safety department, Illinois RTA, and FTA had authorities and responsibilities to provide independent quality assurance/quality control (QA/QC) over the performance of track inspection and maintenance activities that are not conferred in 49 CFR Part 659.
Shared Responsibility for Safety Oversight
Based on a limited delegation of Congressional authority, FTA designed the SSO program as one in which FTA, States, and rail transit agencies collaborate to ensure safety and security. Ms. Boyd noted that this program was not created to provide the type of oversight to the rail transit industry that FRA provides to freight railroads and commuter railroads. Instead, this program was designed to reinforce local accountability for the safety and security of rail transit service. In the majority of cases, State oversight agencies and even rail transit safety departments do not enforce compliance with track standards. This activity is traditionally performed by senior management in the maintenance department or by a dedicated QA/QC function.
The 43 heavy and light rail agencies in the SSO program are entities of local government, not for-profit carriers. As such, Congress has determined that they cannot be regulated by Federal interstate commerce provisions. Also, since these agencies do not operate on the general railroad system, except in specific instances where shared use waivers are in effect, they are not subject to FRA jurisdiction, like commuter rail agencies.
Through their legal designations and enabling legislation, Congress has determined that these local agencies remain ultimately accountable for the safety of the service they provide. These agencies are held responsible by their executives, their Boards of Directors, their internal and external auditing functions, their funding partners, the voters in their communities, the statutory requirements specified by States and municipalities in the creation of these public agencies, and tort claims liability provisions.
In the case presented at the hearing, NTSB made assumptions about what could have been done to prevent the derailment based on its familiarity with regulatory programs managed by FRA , particularly 49 CFR Part 213, Track Safety Standards. NTSB also compared the CTA track inspection and system safety programs with "industry standards," developed by the American Public Transportation Association (APTA) in partnership with FTA, and "effective practices" used at Bay Area Rapid Transit (BART), New York City Transit (NYCT), and three commuter railroads overseen by FRA .
NTSB implied that Illinois RTA and FTA should have required implementation of these standards and practices through the SSO program. However, NTSB did not acknowledge that, at the current time, 49 CFR Part 659 does not provide Illinois RTA or FTA with the authority to require implementation of 49 CFR Part 213, APTA Rail Transit Standards, or "effective practices" used at BART or NYCT, or procedures in place at commuter railroads, unless these standards and practices are specifically adopted by the rail transit agency in its SSPP .
Further, NTSB did not clarify that Congress, in the enabling legislation for 49 CFR Part 659, confers no specific enforcement authorities to FTA or the States, such as the authority to issue civil penalties or to suspend revenue service. The SSO program was not established by Congress to ensure correction of all identified defects or deficiencies observed at a rail transit agency, from a missing or burned-out light bulb, to expired fire extinguishers, to specific track defects in specific locations, to requiring the use of specific technology and track testing programs. Rather, the program was designed to provide broad oversight to ensure that the rail transit agency has programs and procedures in place for accomplishing these activities.
"The Power of the Purse"
During the hearing, at several points, NTSB stated that FTA has the "power of the purse" in requiring the implementation of corrective actions and in conferring this authority to State agencies. Yet, FTA is expressly prohibited by Congress from regulating the operations, routes, schedules, and fares of rail transit agencies (49 U.S.C. 5334 (b) (1)). While NTSB's Legal Counsel read this provision during the hearing, he failed to note that this provision is attached to every grant program that FTA manages, including the Section 5307 program, which provides the basis of FTA's authority for the SSO rule.
To date, Congress has limited the authority of SSO agencies to review rail transit agency safety programs and require corrective actions. These limitations stem from the history of "self-regulation" in the rail transit industry and the way in which Congress has structured the SSO program to bridge local, State, and Federal authorities and responsibilities for safety oversight of rail transit agencies. These limitations are based on the reality that the majority of rail transit funding in the United States comes from local and State sources and fare revenues.
FTA is a funding partner, but not the main contributor in keeping the nation's rail transit agencies in service. Congress has made it clear that local and State governments, along with FTA, share responsibility for ensuring the safety of the rail transit systems they fund.
NTSB investigators, upon questioning from the Board, were unable to provide information on CTA's annual operating and capital budgets or the amount of money FTA contributes to these budgets, or the amount of money CTA budgeted for maintenance and actually received between 2004 and 2006. During the lunch break, NTSB investigators obtained this information, but did not present it clearly when the hearing resumed.
CTA's annual operating budget for FY 2008 is projected to be $1.2 billion. As specified by Congress, FTA provides no funds to support this budget. However, local and State agencies are expected to subsidize the elements of this operating budget not covered by fare revenues and other revenues generated by CTA, such as advertising and real estate management. At CTA, fare and other revenues only cover approximately $560 million of the $1.2 billion budget.
For FY 2008, CTA's annual maintenance budget is projected to be approximately $490 million, of which FTA will provide approximately $133 million in Section 5307 funds. FTA also will provide approximately $93 million in Section 5309 Fixed Guideway Remodernization funds and $96 million in Section 5309 New Start funds.
The penalty assigned by Congress for the failure of a State to make "adequate effort" to comply with 49 CFR Part 659 is the withholding of five (5) percent of the Section 5307 funds provided to the urbanized area or State. Therefore, even if FTA had determined that Illinois RTA was not fulfilling its obligations under 49 CFR Part 659 (which it did not), FTA could have withheld $6.5 million from CTA. While this is a sizeable amount of money, it is less than .04 percent of CTA's combined annual operating and capital budgets. FTA's "power of the purse" is limited by Congress, and NTSB should have identified and described this situation accurately.
By failing to correctly depict FTA's authority in the SSO program, NTSB did not recognize that Congress has intentionally limited the authority conferred to FTA in administering the SSO program. Congress views the funding and safety oversight of public transportation as a partnership at the local, State, and Federal levels, not as an exclusive Federal responsibility. Congress expects that State and local funding agencies, working with the rail transit agencies, will do their part to support safety oversight, in partnership with FTA's SSO program.
Resources Devoted to the SSO Program
During the hearing, NTSB determined that the resources Illinois RTA devoted to its SSO program were highly inadequate. Illinois RTA provides .5 full-time equivalents per year plus contractor support.
FTA's Office of Chief Counsel has determined that FTA does not have the authority from Congress to require States to devote specific levels of personnel resources to the SSO program. Nor can FTA require specific qualifications from personnel assigned by the State to manage the SSO program.
Congress also has prohibited FTA from funding the States to cover the costs of addressing 49 CFR Part 659 requirements, with the exception of 5309 funds for States establishing new oversight agencies for New Starts systems. Congress also prohibits the use of Section 5307 funds from covering the costs of salaries for rail transit agency safety personnel. At the current time, as specified by Congress, FTA provides virtually no funding to support the SSO program or the rail transit agency safety departments. Congress structured this arrangement to ensure that State and local partners meet their obligations for overseeing the safety of the rail transit service they fund.
CTA's Budget Crisis and Impacts on Maintenance
NTSB did not cite the extreme under-capitalization of CTA as a probable cause or contributing factor for this accident. FTA is very concerned that NTSB did not use its authority to highlight this issue.
Since the Illinois State legislature failed to reauthorize its State transportation funding bill, Illinois FIRST, in 2004, CTA has been on the verge of bankruptcy. The State of Illinois has provided no funds to support CTA's operating and capital maintenance budgets. As a result, since 2004, CTA's capital maintenance program has declined by almost $400 million and it has received $300 million less than anticipated for operating support. Due to lack of State funding, CTA faced a $110 million deficit in FY 2007 and is projecting an almost $200 million deficit for FY 2008.
For the last four years, CTA has transferred money from its capital budget to sustain operations and cover these deficits. CTA has also cut tens of millions of dollars from its budget. In many ways, the facts of this derailment are actually an itemized listing of the impacts of this protracted budget crisis on CTA's ability to perform adequate maintenance. NTSB noted an insufficient number of maintenance personnel, insufficient time allotted to perform maintenance (no overtime, nighttime, or weekend work), insufficient investment in the training and oversight of maintenance personnel, insufficient scheduling and performance of maintenance activities, and insufficient quality assurance/quality control over critical maintenance functions, such as track inspection. NTSB also identified a "lack of safety culture" and low expectations among employees that critical maintenance activities would actually be performed. Most of these findings are directly attributable to the structural budget deficits forced by the failure of the State of Illinois to meet its funding obligations. This failing has decimated CTA's capital maintenance program.
By not even mentioning this situation, NTSB failed to use its unique position to single out a critical contributing factor to the deteriorated track conditions. Further, the Board failed to make a public statement regarding the obligations of State government to adequately fund the maintenance of aging infrastructure.
SSO Program Verification Requirements
FTA, through its SSO program, provides technical assistance and makes recommendations to rail transit agencies regarding what safety responsibilities should be assumed by their safety functions, their operating and maintenance functions, their QA/QC functions, and their executive leadership. However, ultimately, it is up to each rail transit agency to determine how specific activities, such as track inspection, will be performed, documented in the SSPP , and overseen and reported through the rail transit agency's internal safety audit process. Further, it is left up to each SSO agency to determine how it will assess the rail transit agency's implementation of its SSPP and issue findings requiring corrective action.
For the internal safety audit process, at many rail transit agencies around the nation, executive leadership in the maintenance department performs the field verification and conveys the results to the system safety function. In some cases, joint review committees are established with the system safety function, in other cases, consultants are used to support this activity. The approaches vary considerably in industry, and no two agencies use exactly the same procedures.
CTA's system safety department was not unique in that, prior to the derailment, its system safety officers and engineers were not trained to conduct track inspection, and did not have the authority in the SSPP to review track inspection records or to observe the performance of track inspection. Due to express congressional prohibitions on FTA's authority to regulate the operations of rail transit agencies, FTA's Chief Counsel has determined that FTA does not have the authority to specify how the internal safety audit process is performed, and to require that specific activities to be performed by specific rail transit functions. While FTA recommends that the system safety function assumes a larger verification role in the internal safety audit process, 49 CFR Part 659 does not currently require it.
These limitations also extend to the authority FTA provides in 49 CFR Part 659 to SSO agencies in conducting their Three-Year Safety Reviews. FTA requires the SSO agency, once every three years, to conduct an on-site review at the rail transit agency to determine whether the rail transit agency's SSPP is being implemented and whether it should be updated. SSO agencies issue findings requiring corrective actions when they determine that the SSPP provisions are not being implemented or that the SSPP needs to be updated.
However, while FTA requires an "on-site review" at the rail transit agency, FTA does not specify that the SSO agency must conduct an independent inspection of track, equipment, facilities, or infrastructure as part of its Three-Year Safety Review. Nor does FTA require the SSO agency to demand corrective action plans to correct specific defects or deficiencies identified during onsite inspections.
Ensuring the Integrity of Aging Infrastructure
Finally, FTA is concerned that NTSB did not appear to consider, at any length, whether it was appropriate to have rail transit safety officers responsible for directly overseeing the performance of track inspection and maintenance. FTA believes that how the nation's rail transit agencies ensure the integrity of their track is a critical issue, particularly for rail transit agencies with aging infrastructure.
There are important questions to be addressed in determining how this process should be overseen and who is best equipped to manage it. Rail transit safety officers are not FRA inspectors. They are not trained to perform track inspection; they are not vested parties in labor contracts authorized to evaluate the performance of track workers; and, in most cases, the nation's rail transit safety departments do not have the experience or resources to assume this function. FTA is concerned that by applying the FRA model to the rail transit industry, NTSB overlooked critical distinctions between traditional maintenance QA/QC functions and traditional safety functions.
Ms. Boyd concluded her presentation by reviewing the recommendations NTSB made as a results of its investigation.
To the Federal Transit Administration:
1. Modify your program to ensure that State safety oversight agencies take action to prompt rail transit agencies to correct all safety deficiencies that are identified as a result of oversight inspections and safety reviews, regardless of whether those deficiencies are labeled as "findings," "observations," or some other term.
2. Develop and implement an action plan, including provisions for technical and financial resources as necessary, to enhance the effectiveness of State safety oversight programs to identify safety deficiencies and to ensure that those deficiencies are corrected.
3. Schedule the Chicago Transit Authority as a priority for receiving the maintenance oversight workshop and the training course to be developed for track inspectors and supervisors that will address the unique demands of track inspection in the rail transit environment.
4. Inform all rail transit agencies about the circumstances of the July 11, 2006, Chicago Transit Authority subway accident and urge them to examine and improve, as necessary, their ability to communicate with passengers and perform emergency evacuations from their tunnel systems, including the ability to (1) identify the exact location of a train, (2) locate a specific call box, and (3) remove smoke from their tunnel systems.
To the State of Illinois:
5. Evaluate the Regional Transportation Authority's effectiveness, procedures, and authority, and take action to ensure that all safety deficiencies identified during rail transit safety inspections and reviews of the Chicago Transit Authority are corrected, regardless of whether those deficiencies are labeled as "findings," "observations," or some other term.
To the Regional Transportation Authority:
6. Determine if track safety deficiencies on the Chicago Transit Authority's Dearborn Subway in the area of the derailment have been adequately repaired.
7. Strengthen your follow-up action on Chicago Transit Authority system safety reviews to ensure that the Chicago Transit Authority corrects all identified safety deficiencies, regardless of whether those deficiencies are labeled as "findings," "observations," or some other term.
To the Chicago Transit Board:
8. Direct the Chicago Transit Authority to correct all safety deficiencies identified by the Regional Transportation Authority in its most recent and future safety inspections and reviews, regardless of whether those deficiencies are labeled as "findings," "observations," or some other term.
To the Chicago Transit Authority:
9. Correct all safety deficiencies identified by the Regional Transportation Authority in its most recent and future safety inspections and reviews, regardless of whether those deficiencies are labeled as "findings," "observations," or some other term.
10. Examine all of the elements in the American Public Transportation Association's "Standard for Rail Transit Track Inspection and Maintenance" and incorporate all appropriate elements of this standard in your system safety program. Specifically, include the regular use of track geometry vehicle inspections and the inspection of rail for internal defects in your system safety program.
11. Evaluate all territories to determine the number of inspectors and the amount of time needed to ensure that adequate track inspections are conducted, and implement appropriate changes.
12. Schedule as a priority the maintenance oversight workshop and the training course that the Federal Transit Administration plans to develop for track inspectors and supervisors that will address the unique demands of track inspection in the rail transit environment.
13. Perform a comprehensive computational study of the existing ventilation system using various fire and smoke scenarios to identify potential deficiencies, and make improvements to the ventilation system and smoke removal procedures based on the findings of the study. These actions should address reinstalling fan 108 and replacing unidirectional fans (including fan 133) with dual direction fans as needed.
14. Examine and improve as necessary your ability to communicate with passengers and perform emergency evacuations. Ms. Boyd noted that NTSB would formally transmit these recommendations to FTA and the other agencies in the next few weeks. NTSB will also publish the final accident investigation report, which was approved at the September 11, 2007 Board hearing. In the recommendation letter and final report, NTSB may provide additional clarification regarding what it means by correcting "all safety deficiencies that are identified as a result of oversight inspections and safety reviews, regardless of whether those deficiencies are labeled as "findings," "observations," or some other term."
Ms. Boyd then introduced Ms. Violet Gunka from Illinois RTA, who provided both RTA's response to the NTSB investigation and gave an update regarding the activities performed at CTA and by Illinois RTA since the derailment to prevent recurrence.
Ms. Gunka explained that representatives from CTA's system safety department and Illinois RTA watched the NTSB hearing together via webcast at RTA's headquarters on September 11, 2007. Ms. Gunka voiced her agreement with many of the points raised by Ms. Boyd regarding concerns with the NTSB investigation and its depiction of Illinois RTA's authority and FTA's SSO program.
Ms. Gunka also explained that Illinois RTA was not satisfied with the way in which NTSB presented Illinois RTA's 2004 Three-year Safety Review. Though Illinois RTA provided extensive comments on NTSB's Draft Statement of Fact regarding the accident, Illinois RTA does not believe that NTSB adequately addressed their comments. Ms. Gunka also pointed out that, in several interviews with Illinois RTA personnel, it did not seem that NTSB investigators understood FTA's SSO program and how it was different from FRA 's safety program.
Ms. Gunka then reviewed the two NTSB recommendations made to Illinois RTA, and described the activities already underway to address CTA's deteriorating track conditions. NTSB recommended that Illinois RTA:
Ms. Gunka began her discussion of the activities taken by CTA over the last 14 months to address this derailment by identifying activities performed to locate trains in tunnels and to support emergency evacuations in tunnels under smoke conditions:
For the area of tunnel ventilation, Ms. Gunka noted that CTA has proposed that the following system improvements should be made; however, because of the budget crisis, funding is currently not available for all these proposed improvements:
Ms. Gunka then described the activities taken by CTA to address improvements in its track inspection and maintenance program:
Also, in August, CTA re-organized its track engineering department to separate track inspectors from track maintainers. Also, the department was increased in size by 42 positions and two additional supervisors were also added. Now CTA has:
CTA is also working to replace all wooden ties in the subway system, and will continue to use tamping equipment for ballasted portions of track. Tamping helps realign track and stabilizes the ballast supporting the track. A signal system upgrade is also underway. By the end of 2007, CTA will have replaced 4,000 additional rail ties in the Blue Line subway and 4,000 ties in the Red Line subway.
Ms. Gunka noted that Illinois RTA has not yet approved CTA's accident investigation report for July 11, 2006 derailment. In addition to the NTSB findings focusing on track, Illinois RTA has requested that CTA address the following items as part of the investigation report:
Ms. Gunka concluded her presentation of Illinois RTA and CTA post-accident activities by reiterating Illinois RTA's concerns regarding the NTSB findings. Ms. Gunka stated that NTSB misrepresented Illinois RTA and the SSO Program. NTSB gave an impression that there was no follow-up on the corrective actions but did not clarify or recognize the fact that neither FTA nor Illinois RTA has the authority to require corrective actions for observed track deficiencies, especially when these observations are made as part of a general review, not the result of an indepth inspection. Further, Ms. Gunka reiterated that none of the observed track conditions identified in the 2004 Three-Year Safety Review were in the area where the derailment occurred.
Ms. Gunka then provided an overview of Illinois RTA's Three-Year Safety Review process. This process begins with an entrance briefing with CTA Executive Staff present, where the SSO program and Illinois RTA's role are discussed, along with the review process and activities. The review itself is a two week process at the end of which an exit briefing is held, which includes the CTA Executive Staff. At the exit briefing, a summary of findings is provided.
Ms. Gunka noted that, as specified in 49 CFR Part 659, the Three-Year Review process carried out by Illinois RTA is a broad review of the implementation of CTA's SSPP and not a QA/QC for track inspection. Ms. Gunka explained that requiring corrective actions for track deficiencies has never been a part of the Illinois RTA SSO program or FTA's 49 CFR Part 659 requirements.
She further noted that Illinois RTA does not have the equipment or the expertise to perform QA/AC for track inspections, nor has there ever been the expectation that Illinois RTA would assume this role. Due to diligence, in its 2004 Three-Year Safety Review, Illinois RTA made observations in the area of track maintenance; however, they were not considered findings. These observations were brought to the attention of CTA Executive Staff and were also included in the Review Report as "observations".
Illinois RTA has a solid relationship with the CTA and other partner agencies. Quarterly meetings are held with participation by CTA, FTA, IDOT and TSA . These meetings facilitate interagency coordination, reporting and information exchange to determine and implement appropriate corrective actions.
Illinois RTA also has a corrective action tracking tool, which includes all corrective actions from Three-year Safety Reviews, Annual Internal Reviews and Accident Investigations. Updates in this tracking matrix are made whenever verification from CTA is received that the corrective action has been completed. Outstanding corrective actions are also discussed during the quarterly meeting.
Ms. Gunka concluded her presentation by stating that Illinois RTA just completed its 2007 Three-year Safety Review of CTA. During this review, Illinois RTA adopted several "lessons learned" from the way in which the NTSB presented its 2004 Three-year Safety Review report. Ms. Gunka noted that Illinois RTA has made changes in the formatting of its report, and in the classification of its findings. Illinois RTA also decided not to include any observations, recommendations, or other information that was not germane to a specific finding.
Mr. Taborn thanked Ms. Gunka for her presentation, and then offered his perspective on the NTSB investigation, as the Director of FTA's Office of Safety and Security.
Mr. Taborn noted that the CTA accident and the gradually deteriorating track conditions that caused it raise many important issues. One of them is the appropriate level of Federal regulation in the public transportation industry. Another is how municipalities and States, facing budget deficits, can provide sufficient resources to support the maintenance of aging infrastructure. Finally, Mr. Taborn observed, that when confronted with the facts of this accident, we must be concerned that perhaps such an event could happen again at another public transportation agency.
Mr. Taborn noted that, as both Ms. Boyd and Ms. Gunka observed, FTA does have concerns with the NTSB investigation and the investigative process used to assign responsibility for this derailment. Mr. Taborn explained that FTA does not believe that NTSB appropriately identified the roles, responsibilities, and authorities of the involved parties as specified in 49 CFR Part 659. Mr. Taborn explained that FTA is still assessing NTSB's determinations regarding the appropriate role of the rail transit safety function, the SSO agency, and FTA in overseeing the performance of track inspection and maintenance.
Mr. Taborn further noted that FTA can argue with NTSB about these roles and responsibilities, and about who is accountable for performing which functions. FTA can also dispute NTSB claims that Part 659 provides adequate delegations of authority to SSO agencies to require corrective action plans for every identified safety deficiency, from a missing or burned-out light bulb to specific track conditions in specific locations, to requirements in training and qualification programs, to the use of specific technology and testing programs.
However, Mr. Taborn pointed out that FTA cannot deny that a hazard continued to exist at CTA that was neither reported to nor managed through the SSO program at any level. Mr. Taborn explained that, since the derailment, FTA has worked closely with CTA and Illinois RTA to support the turn-around in CTA's track inspection and maintenance program. FTA has also taken a hard look at its administration of the SSO program. Mr. Taborn then noted that, that while it was not a focus of the NTSB investigation, FTA's biggest concern with the derailment is that at all levels of our SSO program, we did not intervene effectively through the hazard management program to identify and manage an ongoing hazardous condition.
Mr. Taborn explained that on September 6, 2007, FTA released a letter clarifying 49 CFR Part 659 hazard management program requirements and urging improvements in their implementation. Mr. Taborn noted that this letter was discussed extensively yesterday, and that he hoped the participants had a better understanding of these requirements. Mr. Taborn explained that while it will take many months, perhaps years, to address the NTSB recommendations from the CTA derailment fully in the SSO program, he did want to take a moment to discuss new initiatives that FTA has in place to support immediate improvements. At roundtables, workshops, and meetings like this one, FTA has given presentations with representatives from both Illinois RTA and CTA on this accident and the actions now being taken by CTA to improve its maintenance program. FTA has tried to explain how this situation occurred, and to highlight indicators and precursors that agencies at all levels can use to catch and manage these conditions before an accident occurs.
In the SSO audit program, FTA has placed special emphasis on the requirements of the hazard management program, ensuring that both rail transit safety functions and the SSO agency are made aware of potential maintenance concerns. FTA has also developed a new Track Worker Protection and Maintenance Oversight Initiative, which was introduced in Administrator Simpson's Dear Colleague Letter of May 8, 2007.
Beginning in FY 2008, FTA plans to conduct two-day workshops at four heavy rail transit agencies. These workshops will include maintenance, operations and safety personnel, executive leadership, and State safety oversight personnel, and will explore maintenance safety oversight challenges and attempt to identify possible options for improvement. FTA plans to use these workshops to galvanize the attention of industry on maintenance and safety issues. These workshops will also support the development of guidelines on improved maintenance practices in the rail transit environment.
FTA also plans to develop a track inspector refresher training course, which will be piloted at four other heavy rail agencies in FY 2008, then offered to the entire industry in FY 2009. FTA will also develop a training video/DVD specifically on track worker protection. FTA will also prepare pocket guides on track inspection and track worker protection for use in the field.
FTA is working to update its highly successful Transit Watch program to include safety issues for employees and passengers. Through this new initiative, transit agencies will have templates, brochures, posters and other materials available to support adherence to safety rules and to prevent at-risk behavior.
FTA also will be conducting outreach directly with rail transit agency chief executive officers (CEOs) regarding track worker protection and maintenance oversight issues.
In the last year, FTA has developed a training curriculum for State oversight personnel, and is providing financial support to enhance their professional development and certification through the World Safety Organization (WSO).
FTA will continue to support research regarding track inspection and track worker protection, and will continue to coordinate with APTA regarding the development of consensus-based, voluntary standards through the APTA Rail Transit Standards Program. Finally, FTA will also continue to sponsor research through the Transportation Research Board (TRB), Transit Cooperative Research Program (TCRP), and the University Transportation Centers (UTCs).
Mr. Taborn then called Mr. Mike Flanigon to the podium to provide a few words about the CTA derailment and the NTSB findings and recommendations. Before joining FTA as the Director of FTA's Office of Technology, Mr. Flanigon was a rail transit investigator for NTSB, and in the first few months after the CTA derailment, served as the NTSB Investigator-in-Charge.
Mr. Flanigon pointed out that there are really two parts to the NTSB's investigation and findings. The first part is the way in which NTSB interpreted FTA's legal authorities and the role of the SSO agencies and rail transit agency system safety departments as specified in 49 CFR Part 659. Mr. Flanigon explained that, often, when NTSB wants to see a change in policy, they will make a recommendation to the appropriate Federal agency, rather than directly to Congress. He pointed out that this may have been the case with the CTA investigation findings and recommendations.
Mr. Flanigon noted that while members of the SSO community could ask whether it was appropriate for NTSB to make the findings it did, the SSO community needs to appreciate the extreme deterioration of CTA's track. This was not a case of an isolated segment of track in poor condition. The entire track in the Blue Line subway was in very bad condition. Mr. Flanigon noted than in his office at FTA he has a portion of the fixation system from CTA's track that came loose after he pressed on the rail with his hand.
Mr. Flanigon stated that based on his experience, his biggest concern was that CTA had track standards in place, which required that speed restrictions be imposed on wide gage track or, depending on the extent of the gage problem, that the track be removed from service. For whatever reasons, these track standards were not enforced by CTA inspectors, roadmasters, foremen, and senior management. No one at any level intervened effectively to address these conditions or to impose speed restrictions. Therefore, wide gage track was allowed to remain in service, and trains were allowed to operate over this track at inappropriate speeds. As a result, a derailment occurred that should never have happened.
Mr. Flanigon noted that CTA has fired the individuals involved for negligence, the General Manager has stepped down, and CTA has since re-vamped both its track inspection and maintenance program. However, Mr. Flanigon observed that none of this post-accident activity can erase what was a truly deficient condition regarding the enforcement of CTA's track standards. This is a wake-up call to the rest of the industry, particularly for those agencies that, like CTA, have aging infrastructure.
Mr. Flanigon pointed out that it is incumbent on each rail transit agency, its safety function, and its oversight bodies to ensure the integrity of the internal processes put in place to safeguard the integrity of critical systems, such as track. Mr. Flanigon also agreed with Mr. Taborn that there are complex issues involved in determining how oversight functions can effectively identify and address these types of issues through the hazard management program, the conduct of on-site reviews and inspections, and other means.
Questions and Answers
Based on the presentations, there were a number of questions from participants at the 11th Annual SSO Program Meeting:
Mr. McElveen thanked everyone for the great discussion regarding the challenges we are currently facing in conducting audits and reviews. After a short break, Mr. McElveen then introduced Mr. Michael Flanigon, Director, FTA Office of Technology, and Ms. Lisa Colbert, Transportation Program Manager, FTA Office of Research, Demonstration, and Innovation. Mr. McElveen explained that over the past year, he has been working closely with Mr. Flanigon and Ms. Colbert to identify additional opportunities for incorporating safety issues into FTA's research programs.
Mr. Flanigon kicked off the session by summarizing the activities and responsibilities of FTA's Office of Technology. Mr. Flanigon noted that his office works with University Transportation Centers (UTCs) and other organizations and agencies to evaluate rail technologies and programs that can be used by the rail industry to improve system safety and security.
Mr. Flanigon next stated that the FTA appropriated $80.5 million during FY 2007 to various research programs and organizations including the National Research Program, the Transit Cooperative Research Program, the National Transit Institute, UTCs, Capital Investment Grants, and Non-FTA funded programs involving intelligent transportation systems (ITS) and Maglev technologies. In addition to these existing programs, Mr. Flanigon stated that FTA has recently awarded and started programs for Preventing Rail System Suicides and Machine Vision Intrusion Detection. FTA is currently evaluating programs for Train Operator Post-Traumatic Stress Syndrome Studies and Third Rail Insulator Cleaning Technology Demonstrations.
Mr. Flanigon also explained that FTA is involved with a Shared Track Research program that will look at specific separated shared use operations and identify specific technologies that could work on these systems. This program builds on the joint efforts of the FRA Office of Research and Development, and the FTA Office of Research, Demonstration, and Innovation. The goal of this program is to explore the feasibility of shared use operations of passenger and freight trains using ITS to ensure system safety is maintained or improved through the use of these technologies. FTA also supports the current Crash Energy Management Program, which focuses on improving railcar designs to better withstand the impacts of collisions.
Additionally, FTA is developing a Safety Auditor Training Program that will help address NTSB recommendations stemming from the CTA derailment and other previous accidents where rail transit agency internal oversight could have been improved. The objective of this program is to develop lesson plans, graphics, workbooks and other materials to help safety auditors be the best they can be, providing them with a greater level of qualification and education to identify $100,000 in FTA funding in FY 2007.
FTA is also excited to be expanding its research into different crash energy management technologies including the use of end of track devices, car interior features, testing and simulators, and diesel multiple unit (DMU) fuel tank crash resistance. FTA is also exploring different security related technologies for use in the rail transit environment including web based station simulators, train operator emergency training simulators, harnessing machine vision technology, and WiFi operations control center subway train communication links to passengers. Mr. Flanigon concluded his presentation be soliciting feedback from the audience and asking that they please provide any ideas they may have for additional research topics to his office.
Ms. Colbert next discussed FTA's relationship with the UTCs, explaining how FTA works in partnership with the UTCs to develop better transit education, research and technology resources for the industry. Through FTA's Office of Research, Demonstration, and Innovation, Ms. Colbert is responsible for managing the UTC program for FTA by increasing FTA's involvement with the UTCs, and fostering collaboration between transit agencies, private organizations, and the UTCs.
Ms. Colbert provided a brief history of the UTC program, stating that in 1987, the Surface Transportation and Uniform Relocation Assistance Act established the program and created a UTC in each of the ten Federal regions. In 1991, the Intermodal Surface Transportation Efficiency Act (ISTEA) reauthorized the UTC Program and increased the total number of UTCs from 10 to 20. In 1997, the Transportation Equity Act for the 21st Century increased the UTC program to 33 Centers nationwide, and finally, enacted in 2005, the Safe, Accountable, Flexible, Efficient Transportation Equity Act: A Legacy for Users (SAFETEA-LU) created 60 UTCs.
Ms. Colbert explained that while the UTCs are funded by the FTA and FHWA, they are administrated by the Research and Innovative Technology Administration (RITA), and that legislation has been used to categorize the UTCs into five groups based on funding amounts. There are currently ten national UTCs with funding of $3.5 million per year, 10 regional UTCs with $2 million in funding per year, 10 Tier I UTCs that receive $1 million in funding per year, 22 Tier 2 UTCs that receive $500,000 in funding per year, and eight Tier 3 UTCs that receive between $400,000 and $2 million in funding each year.
In 2006, the UTCs listed as Regional and Tier I were subjected to a competition. As a result, six new candidates entered the program in 2007. All of the DOT modal administrations participated in the evaluation process.
The UTCs have requirements they must abide by. These include:
In addition, each UTC must develop a Theme that encompasses more than one mode of surface transportation and clearly links to the national strategy for surface transportation research. Each UTC is expected to devise and implement a process for selecting research projects that includes peers and other experts in the field, including at least one individual from the U.S. DOT . Additionally, each UTC is required by law to be supportive of the National Strategy for Surface Transportation Research as defined by (1) the report of the National Highway Research and Technology Partnership entitled Highway Research and Technology: The Need for Greater Investments dated April 2002, and (2) the programs of the National Research and Technology Program of the FTA. Each UTC is also strongly encouraged to support the national research, development, and technology high-priorities of DOT and its Operating Administrations, as identified by the DOT Strategic Plan, the U.S. DOT Research, Development, and Technology Plan, and other items that RITA may post on the UTC program's web site. There are two DOT -wide activities: (1) Advanced Research and (2) Congestion Chokepoints.
The mission of the UTC is to advance U.S. technology and expertise in the many disciplines comprising transportation through education, research, and technology transfer at universitybased centers. Through partnerships with state and local transportation agencies, governments and the private sector, the universities serve as important sources in developing transportation leaders and innovations to meet the nation's need for safe, efficient, and environmentally sound movement of people and goods.
Each UTC publishes a semi-annual Informational Center Newsletter, and an annual report that details that Center's research, education, and technology transfer results, and publishes research reports. These results are available on the UTC's website. In addition, published reports are cataloged in the Transportation Research Information Service (TRIS) database and the National Transportation Library. When UTCs first select research projects to be conducted, each UTC submits to the Transportation Research Board's Research in Progress (RiP) database a project description of each project. The UTCs also contribute in unique ways to these objectives (research, education, & technology transfer).
Ms. Colbert further explained that various UTCs conduct basic and applied transportation research in numerous, multimodal fields; aid workforce development by creating programs for the professionals and providing undergraduate and graduate students an education program that includes multidisciplinary course work and participation in research; and make these research and education results available through an ongoing program of technology transfer that can be implemented, utilized, or applied. She then provided a listing of each of the UTCs grouped by as follows:
Hazard probability can be measured as follows:
|National||Regional||Tier I||Tier II|
|Marshall University||Region 1: Massachusetts Institute of Technology||Georgia Institute of Technology||California State University-San Bernardino|
|Montana State University||Region 2: City College of City University of New York||Iowa State University||Cleveland State University|
|Northwestern University||Region 3: Pennsylvania State University||Rutgers University||George Mason University|
|Oklahoma State University||Region 4: University of Tennessee||San Jose State University||Hampton University|
|Portland State University||Region 5: Purdue University||University of Florida||Kansas State University<|
|University of Alaska||Region 6: Texas A&M University||University of Idaho||Louisiana State University|
|University of Minnesota||Region 7: University of Nebraska||University of Maryland College Park||Michigan Technological University|
|University of Missouri-Rolla||Region 8: North Dakota State University||University of Michigan||North Carolina State University|
|University of Vermont||Region 9: University of California, Berkeley||University of South Florida||Northwestern University|
|University of Wisconsin||Region 10: University of Washington||University of Southern California||University of Akron|
|University of Arkansas|
|University of California-Davis|
|University of Connecticut|
|University of Delaware-Newark|
|University of Detroit Mercy|
|University of Massachusetts-Amherst|
|University of Memphis|
|University of Nevada-Las Vegas|
|University of Rhoda Island|
|University of Toledo|
|Utah State University|
|Youngstown State University|
FTA currently provides $7 million in annual funding to support 8 of the UTCs. These include:
Ms. Colbert next provided several examples of UTC research projects. These included San Jose State University's "Increasing Transit Ridership: Lessons Learned from the Most Successful Transit Systems in the 1990's," which looked at external and internal factors that impact ridership and what measures transit agencies can implement to increase ridership. The report became the basis of a ridership course at the National Transit Institute.
The second exampled was a collaborative effort between North Dakota State University,Colorado State University, the University of Utah, and the University of Wyoming. This study was conducted to identify ITS technologies that transit systems are using, and particularly to aid in the progress of the Welfare to Work Initiative.
Ms. Cobert's final example was a study conducted by Texas Southern University to measure the potential impacts of transportation facilities on land values. The findings indicated that transit bus facilities are not overriding variables causing changes in land values. Other UTC research projects include the 1999 Transit Customer Satisfaction Index, which was conducted by the University of South Florida to provide a systematic evaluation of participating transit authority's customer satisfaction, insight into the factors that drive customer satisfaction, and recommendations for how to increase customer satisfaction. Also mentioned was another study conducted by the University of South Florida pertaining to land developer participation in providing for bus facilities and operations.
In 2006, FTA conducted 3 dialogue sessions with UTCs and the transit industry:
(1) APTA Bus and Paratransit Conference (CA)
(2) Community Transportation Association of America (FL)
(3) APTA Rail Conference (NY)
The purpose of these sessions was to introduce FTA and to establish a relationship with the UTCs; to provide a private sector network group for the UTCs; to inform UTCs about the FTA Strategic Research Plan and goals; to obtain an understanding of how the UTC program operates; and to identify what the UTCs expectations were of FTA.
In 2007, FTA continued to formulate a relationship and conduct outreach activities with the UTC community, and now participates on 10 UTC Advisory Boards and has visited at least 4 separate UTC facilities. To date FTA has conducted three roundtable meetings and two workshops at UTCs. The purpose of the meetings was to discuss real transit problems that were suggested by the transit industry; to share and exchange ideas about the topics; to determine how important the topic were on a national or regional level; and to prioritize the topics.
Ms. Colbert concluded her presentation by briefly introducing each of the UTC representatives in attendance at the 11th Annual SSO Meeting. Representatives from the UTCs that delivered presentations included Dr. Reinhardt Brown, Interim Executive Director, South Carolina State University; James E. Clyburn University Transportation Center, Center of Excellence in Transportation; Dr. Jill Hough, Director, North Dakota University, Small Urban & Rural Transit Center; Dr. Mahmud Farooque, Ph.D., Center/Managing Director, NEXTRANS, Purdue, Regional University Transportation Center; and Dr. Max Donath, Director, University of Minnesota, Intelligent Transportation Systems Institute.
The representatives from the UTCs delivered various presentations pertaining to their programs during the remainder of the UTC Research Programs Session. At the conclusion of this session, Mr. McElveen opened the floor to questions and asked that the audience think about and provide the UTCs with potential research topics. Mr. McElveen also noted that the rail transit industry is currently seeing a significant trend in losing experienced personnel and managers due to retirements. He then suggested that UTCs consider conducting a research project in how the rail transit industry might better identify and hire qualified rail transit safety professionals.
Some participants suggested potential areas of research for the UTCs. Suggested topics included:
Ms. Isabel Kaldenbach, National Director, Light Rail Safety Education, Operation Lifesaver, Inc. began her presentation with an overview of Operation Lifesaver. The organization was founded in 1972 when the annual average of collisions at highway-rail grade crossings exceeded 12,000. At that time, a six-week public awareness campaign called "Operations Lifesaver" was sponsored by the office of Governor Andrus, Idaho Peace Officers, and the Union Pacific railroad. The campaign grew, and during its first year, Idaho's crossing-related fatalities dropped by 43 percent.
From its origins in Idaho, Operation Lifesaver has grown exponentially and is now a National organization with six international partners, and over 3,000 trained presenters. The continuing goal of the organization is to educate drivers and pedestrians with regards to the hazards of rail grade crossings and trespassing on railroad property. Through education, Operation Lifesaver has worked to eliminate death and injuries at rail grade crossings and on rail rights-of-way. Since 1981, the number of annual fatalities related to rail grade crossings has dropped by almost 50 percent (from 728 to 362) and the total number of collisions at crossings has dropped by over 65 percent, from 9,295 to 2,897.
Ms. Kaldenbach next explained how Operation Lifesaver developed its safety campaign for light rail transit. This program, which meets a need identified by many light rail agencies, as well as federal policymakers, was developed jointly by the Federal Transit Administration and Operation Lifesaver, with significant assistance by the American Public Transportation Association (APTA). Ms. Kaldenbach noted that the complete program is available on Operation Lifesaver's website at: http://www.oli-lightrail.org
Ms. Kaldenbach explained that developing this program for the light rail environment was challenging. While light rail is one of the fastest growing modes of transit in the country, it is not widely understood by the public. Unlike traditional rail (Amtrak, commuter lines, freight railroads) or buses, light rail programs vary enormously from city to city, in operation and infrastructure. Some have dedicated lanes, while others share street corridors; some equipment looks like traditional train equipment, some like early-20th century streetcars. Light rail systems run at different speeds, and face different operating hazards.
Ms. Kaldenbach also noted that some light rail systems have vehicles that resemble buses on steel wheels; some light rail trains operate in the center median, some at curbside, and others are completely off-street. Because light rail cars are quieter, bi-directional, more frequent, and often operate right on city streets, long-established safety programs for traditional rail were not applicable to light rail. Finally, since light rail agencies are heavily funded by local agencies, messages developed for the program would have to cater to a very local clientele.
Ms. Kaldenbach explained that it took a great deal of research and discussion to create a safety education program whose characters, situations, and messages were widely applicable to this mode of transit. The messages had to resonate across widely divergent light rail systems, and the character had to be sensitive to the traveling public in various cities and its endless variety of ethnicities, ages, income levels, disabilities, and of course, both genders.
To develop its messages and character, in January of 2003, Operation Lifesaver compiled a list of agencies that either considered themselves light rail, were widely (if erroneously) viewed as light rail by the general public, or were not light rail at all but had extensive rail safety education experience (for example, Long Island Railroad). Also, Operation Lifesaver compiled a list of areas that did not have light rail yet, but had planning and development well underway -- since educating people who have never seen light rail in their neighborhood is a particular challenge.
Early in 2003, Operation Lifesaver invited 44 transit agencies across the country to participate in developing this program, and made presentations at several public transit conferences throughout the year to introduce as many agencies as possible to the developing effort. Ultimately, 23 agencies and a half dozen experts with previous experience in the transit world came together to help design the program, agree on a character, and most importantly identify core messages that could help educate customers, future customers, motorists, pedestrians and neighbors about light rail safety.
Through regular conference calls, a listserve, and email contact, seven messages were identified (with three to four sub-messages for each) and a character and story line were developed. After rejecting some proposals, the group unanimously agreed on Earl P. Nutt, a squirrel who travels the country, seeing the sites. Various story lines were developed that could place Earl in amusing but educational situations as he travels light rail lines across the country. Ms. Kaldenbach noted that the Earl cartoon is "cute" enough to appeal to younger audiences, but his character is edgy and savvy enough to appeal to older children more drawn to Bugs Bunny, SpongeBob, and the Simpsons.
Once the group agreed on Earl and his messages, Operation Lifesaver and the educational and graphic design firm Flying Rhino developed collateral materials, including:
In the fall of 2003, the first packages of materials were distributed to agencies to be tested in their operations. The agencies were:
Since 2003, the campaign has expanded beyond school children. Materials have now been developed for teenagers and adults. Ms. Kaldenbach noted that that these materials are very different from what Operation Lifesaver had done in the past. However, through a comprehensive pilot program, the organization actively sought feedback from the children and others who participated in the initial training programs. Through this feedback, Operation Lifesaver learned important lessons regarding what worked and what did not work in the rail transit environment. Operation Lifesaver made adjustments to the organization's programs based on these comments.
Today, Operation Lifesaver offers and produces a wide variety of education manuals, fact sheets, posters, brochures, and checklists for presenters. Many are based on the character of Earl P. Nutt that can be customized to fit the transit agency needs including using the transit agency's own logo in the brochures. Many of the materials are also bilingual. The material -- distributed free of charge to any transit agency that requests it -- is designed to be used as individual transit agencies like, to meet their needs. Agencies can pick and choose among the offerings, drop their logos into the artwork, and/or adapt the artwork and messages for use in their efforts. All materials are being made available in a variety of formats, which should make it easy for an in-house agency or contracted graphic designers to adapt them.
If agencies decide they would like to develop their own cadre of local presenters, Operation Lifesaver also will train its local speakers to be presenters using these materials. At the conclusion of her presentation, Ms. Kaldenbach took questions. Ms. Kaldenbach was asked if Operation Lifesaver has any training programs that might be useful specifically for the SSO community. She responded that SSO representatives can attend training, or if interested, can become certified Operation Lifesaver trainers, but no program has been developed specifically for SSO Program Managers.
An audience member asked if the Operation Lifesaver program addresses Americans with Disabilities Act (ADA) issues. Ms. Kaldenbach stated that these issues are not yet extensively addressed by the program; however, it is an area of interest that the program may pursue in the future.
In a related question, Ms. Kaldenbach was asked how senior citizens were included in the program. She stated that they receive information through community outreach programs similar to the standard programs issued by Operation Lifesaver. Next, Ms. Kaldenbach was asked if the program includes examples of accidents or near misses.
She replied that this is done primarily through the state coordinators, who should be contacted if the participants were interested in getting more information about the programs in their respective states.
Finally, one participant asked if the program could be extended to include Security. Ms. Kaldenbach stated that this was a possibility, but that no action is currently being taken to incorporate security issues.
Mr. Rick Gerhart, Security Team Leader for FTA's Office of Safety and Security, facilitated the panel on partnering for Rail Transit Security Oversight. Mr. Gerhart began his session by relating a humorous story on the importance of teamwork from the days when Casey Stengel managed the "lovable loser" New York Mets.
Mr. Gerhart then turned to a more serious matter. He explained that FTA's Office of Safety and Security is in the process of developing a Five-Year Strategic Plan ( FY 2008 through FY 2012). In Fiscal Year 2007, Mr. Gerhart stated that FTA's Office of Safety and Security initiated this planning process by collecting data through interviews with FTA staff (inside and outside the Office of Safety and Security), Federal partners (e.g., staff from the Federal Railroad Administration, Federal Motor Carrier Administration, Office of the Secretary, Department of Homeland Security, including the Transportation Security Administration [TSA]), and transit industry stakeholders (e.g., the American Public Transportation Association and Community Transportation Association of America). The Office also reviewed FTA guidance documents and other materials as part of data collection.
Based on analysis performed from this information collection, FTA's Office of Safety and Security then mapped out an approach for the next five years to assure that its safety, security, and emergency management programs are balanced based on industry needs, driven by clear goals, and assessed for utility and effectiveness on a regular basis.
Mr. Gerhart noted that the purposes of the Five-Year Strategic Plan are to:
Mr. Gerhart explained that, through this strategic planning process, FTA is developing a longterm work program to help FTA meet three goals:
1. Expand Office of Safety and Security outreach and customer service with FTA Regional Offices, public transportation agencies, other Federal partners, and State oversight agencies.
2. Integrate and improve safety, security, and emergency management programs, building on the benefits of an all-hazard approach for training, technical assistance, and partnerships with industry.
3. Enhance training management program to build core competencies in safety, security, and emergency preparedness, emphasizing, wherever possible, all-hazard approaches.
Mr. Gerhart concluded his discussion of the Five-Year Strategic Plan by telling the participants that a brochure explaining this process is available on FTA's safety and security website, and that the final Five-Year Strategic Plan will also be posted there when it is completed later this year.
Mr. Gerhart then introduced Mr. Peter Roe, Branch Chief, TSA Surface Transportation Security Inspection Program (STSIP). Mr. Roe also began his presentation by recounting another New York Mets story from the 1960s.
Then, Mr. Roe provided an update regarding TSA 's findings from its Baseline Assessment for Security Enhancement (BASE) program. Mr. Roe noted that TSA 's Fiscal Year 2007 goal for the transit industry included completing BASE reviews of the 50 largest transit agencies based on ridership. To date 44 of these reviews have been completed and five others are currently in progress. TSA 's Fiscal Year 2008 goal includes completing BASE reviews on transit agencies ranked 51 through 100, again based on ridership.
Mr. Roe provided an overview of the process used to conduct the BASE reviews. Mr. Roe noted that BASE is a tool to provide uniform guidance to Transportation Security Surface Inspectors and security auditors for review of transit agency security programs. TSA 's Mass Transit Division and STSIP developed the tool in support of the program goals to:
The BASE program assesses security posture at each reviewed agency, gathering baseline security program data, and facilitating security enhancement in mass transit systems nationally.
Mr. Roe noted that the reviews conducted in the BASE program are guided by a detailed checklist built on TSA and FTA Security and Emergency Management Action Items (including 17 core areas that are considered the foundation of an effective security program), TSA 's Transit Security Fundamentals, the security requirements of 49 CFR Part 659, and TSA 's Security Directives for rail-based passengers systems. This checklist is used to evaluate program components using standard audit practices through document reviews, interviews with personnel, and system observations. The 17 areas assessed in the BASE review include:
1. Establish written Security Programs and Emergency Management Plans.
2. Define roles and responsibilities for security and emergency management.
3. Ensure operations and maintenance supervisors and managers are held accountable for security issues under their control.
4. Coordinate Security and Emergency Management plans with local and regional agencies.
5. Establish and maintain a Security and Emergency Training program.
6. Establish plans and protocols to responds to the DHS Homeland Security Advisory System (HSAS) threat levels.
7. Implement and reinforce a Public Security and Emergency Awareness Program.
8. Conduct tabletop and functional drills.
9. Establish and use a risk management process to assess and manage threats, vulnerabilities and consequences.
10. Establish and use an information sharing process for threat and intelligence information.
11. Establish and use a reporting process for suspicious activity (internal and external).
12. Control access to security critical facilities with ID badges for all visitors, employees, and contractors.
13. Conduct physical security inspections.
14. Conduct background investigations of employees and contractors.
15. Control access to documents and security-critical systems and facilities.
16. Ensure existence of a process for handling and access to Sensitive Security Information (SSI).
17. Conduct Security Program audits.
Mr. Roe noted that, in general, the public transportation industry is making great strides in enhancing its security posture. The BASE reviews show that rail transit agencies covered by 49 CFR Part 659 are generally meeting the rule's basic requirements. In addition, transit agencies are coordinating security and emergency preparedness activities locally and regionally. Mr. Roe noted that the high level of participation of the Top 50 transit agencies in their local and regional emergency planning processes has been one of the most impressive overall findings of the BASE reviews. Mr. Roe also stated that results from the BASE reviews indicate that the transit industry is identifying critical assets and that risk and vulnerability assessments are being completed.
Mr. Roe then provided an aggregate analysis of the results from the 44 BASE reviews conducted to date. This presentation showed the average scores of the transit industry for each of the 17 recommended measures assessed through the BASE checklist. Mr. Roe explained, that based on these reviews, TSA has learned that the transit industry is struggling most in addressing the following issues:
After this discussion of the weaknesses identified by the BASE reviews at the Top 50 transit agencies, Mr. Roe then identified some of the best practices observed by TSA during these reviews. Mr. Roe noted that over 50 such practices have been observed by TSA, including the following:
Mr. Roe concluded his presentation by reiterating that the BASE program serves as a valuable tool in supporting and strengthening transit security through identification of security program gaps or weaknesses; the collection of security program data to establish national baselines; the provision of data to support security program refinement; the provision of current security specific data to support Federal grant and program development decisions; and the reduction of occurrence of duplicative audits focused on individual programs.
SSO and Rail Transit Agency Response
During the question-and-answer period after his presentation, Mr. Roe was asked if the BASE review could be used during the New Starts process to improve security. Mr. Roe responded by recommending that the BASE review process be used at project onset and encouraged project personnel to contact their local TSA regional offices to request that a BASE review be performed during this project phase. Mr. Roe noted that, because of the New Start process, the BASE review checklist would need to be modified to be more applicable to a New Starts project in the preliminary stages of design versus its existing format, which is directed towards existing systems in operation.
Mr. Roe was next asked where he thought the responsibility for system security should reside in an organization's structure. He responded that placement may not be as important as the authority given to the security function. While some agencies establish a direct reporting relationship between top management and the security functions, others do not. Both have their benefits; however, what is most important is if the security function has the appropriate level of authority and responsibility to fulfill its functions. Mr. McElveen interjected that the FTA is seeing that the transit industry is beginning to create executive management level positions for both safety and security.
Mr. Roe also responded to a question pertaining to the security directives that have been established by TSA , stating that TSA is moving away from these directives and that Tom Farmer, in his presentation, would provide additional detail on the future role of TSA regulation in the rail transit industry. However, if participants wanted copies of these directives, Mr. Roe urged them to contact their TSA regional offices.
New TSA Legislative Authorities
Mr. Gerhart then introduced Mr. Thomas Farmer, Deputy General Manager, Mass Transit, TSA . Mr. Farmer also used a New York Mets baseball story to kick-off his session. Mr. Farmer then presented an overview of the new legislation that has been enacted to implement the recommendations of the 9/11 Commission Act of 2007, Public Law 110-53.
Mr. Farmer began by stating that the President Bush signed this act on August 3, 2007 and that it was a culmination of concerted efforts initiated from the outset of the 110th Congress. Two former House bills - HR 1, Implementing the 9/11 Commission Recommendations Act, and HR 1401, Rail and Public Transportation Security Act; and a former Senate bill - S4, Improving America's Security Act - were the forerunners to the Act.
A joint conference committee was created and used to resolve differences and to produce the legislation as enacted during July 2007. The comprehensive homeland security legislation provisions encompass a broad spectrum of subjects including intelligence, education and training, information sharing, transportation security, and the spread of democratic freedoms. Mr. Farmer pointed out that sections of most interest to public transportation are Titles XII through XV, including:
Mr. Farmer went on to state that the focus of TSA is currently in three areas: security grant authorizations, security support programs, and regulatory and security program mandates. Through the security grant authorization program, the Federal government has authorized $650 million in FY 2008 for public transportation. This authorization will increase to $1.1 billion by FY 2012.
For railroad transportation including passenger and freight operations, security grants have been authorized for $448 million in FY 2008. This authorization will increase to $508 million by FY 2012.
In addition, Amtrak has received grants to make security improvements to tunnels located in the Northeast Corridor. The focus of these improvements will be on tunnels used for passenger rail service in the Washington DC, Baltimore, and New York/New Jersey areas. Grants have also been authorized to improve Amtrak fire and life safety.
Mr. Farmer also stated that specific programs or protections have been authorized to support security enhancement activities through various means. These include:
Next, Mr. Farmer briefly discussed the various program and regulatory mandates established by the legislation. These include:
Program Mandates: In the next year, TSA will be responsible for developing legislation to implement the following program mandates:
Regulatory Mandates: In the next year, TSA will be responsible for developing regulations to implement the following requirements:
Mr. Farmer concluded his presentation by taking questions from the audience.
SSO and Rail Transit Agency Response
Mr. Farmer was asked if funding would be made available to SSO agencies through TSA to meet the TSA security requirements. Mr. Farmer responded that funding through the TSA for this purpose would be unlikely.
Mr. Farmer was also asked for practical methods that could be used to verify System Security Plan (SSP) implementation. He responded that the SSO agencies should:
Mr. Farmer stated that the BASE assessments are being used to develop the key areas of legislation and further explained the mandates that have been made, which TSA must now implement and follow. Among these, TSA has been directed to perform name-based checks of front-line transit employees against terrorism watch lists. Discussion of the potential legal constraints that may be experienced with implementing such a program then ensued, and Mr. Farmer was asked if the TSA had identified a case that would be going through the legal system to assure there will be no law suits if rail transit agencies follow this program. Mr. Farmer responded that no such case has been identified at this time.
Following this question, Mr. Farmer was asked why the Commercial Drivers License (CDL) certification process could not be used to perform the same type of name-based checks since it addresses much of the same information and is more specific to individuals using social security numbers than simply using names. Mr. Farmer responded that he agreed with this approach and stated that TSA will likely follow the CDL example however a final decision has not yet been made.
Mr. Farmer was next asked what he felt was the best security strategy for rail transit systems. He responded that TSA recommends that each rail system assume that it is being monitored and watched at all times and that they use active deterrents to prevent terrorist activity.
Finally, Mr. Farmer was asked to provide clarification regarding what TSA grant money could be used for. He stated that it could not be used for training of non-rail transit agency personnel and that paratransit systems have not been considered to date. He also clarified that the costs incurred by a rail transit agency to back-fill an employee's position while he/she is attending training is an eligible expense that can be recouped through the grant program.
The Wednesday morning session of the 11th Annual SSO Meeting began with a brief introduction by Mr. McElveen, who reviewed the day's agenda. Following this introduction, the attendees broke into two groups. Rail transit agency representatives participated in a session led by Dr. Beverly Sauer, Professor of the Practice-Managerial Communication, McDonough School of Business, Georgetown University. SSO agency representatives attended a separate session to review the SSO Program Managers Training Curriculum, and to discuss other issues in the SSO Program.
a. Rail Transit Agencies
Dr. Sauer's presentation "Risk Communication: Making the Case for Safety in Presentations, Reports, and Meetings" discussed the importance of communicating clearly with top management to effectively implement safety recommendations. Dr. Sauer stated that the goal of her training session was to provide the rail transit agency participants with the knowledge and skill needed to improve the communication aspects of hazard assessment, risk management, accident investigation and safety; to enhance rail transit agency responsiveness to the implementation of Part 659; and to help the rail transit agencies improve local day-to-day documentation and system safety communication in their organizations.
Dr. Sauer stated that rail transit agencies must work cooperatively with SSO Program Managers and others to implement Part 659 and, in some cases, must partner with more powerful departments to resolve safety and security issues. Rail transit agencies also need specific instruction to help them develop the SSPP and status reports on accident investigations and corrective action plans. Dr. Sauer highlighted that this must be accomplished with limited staff resources and other day-to-day demands.
Dr. Sauer explained that strong legal authority does not automatically confer respect, appreciation, or a willingness to partner. Technical experts must therefore design and deliver information to audiences who do not always share the same knowledge, education, experience, or authority. This requires the technical experts to shift their stance from "technical observers" to "active persuaders."
Dr. Sauer pointed out that many safety directors report to different levels within their organizations and are sometimes three to five management levels removed from the General Manager. As a result of these organizational challenges, other departments may not implement required safety actions, or they may take actions of their own without informing the safety directors. Other technical issues are also faced by the rail transit agencies, along with interorganizational challenges. For example, SSO enforcement efforts may initially be directed at the wrong level, the safety director may not have the authority or resources to address needed actions, SSO Program Managers may not have the authority or support to engage rail transit agency executive leadership, and resistance to change may prevent effective implementation of corrective actions at the agency.
Dr. Sauer pointed out that each of these challenges actually indicates a larger problem for the agency, which is a failure to effectively communicate. In many instances, agencies allow technical details to obscure the seriousness of problems and too often there is no clear metric for evaluating the significance of observations, inspection reports, and analyses. Scientific observations, findings, and analyses fail to convey the imminence of a situation and do not persuade management.
There is also often a lack of transparency and accountability in the communications of a rail transit agency. Data reports and field visits may provide conflicting data; agencies may be concerned with legal issues and potential liabilities; multiple priorities must be managed causing safety to become lost; and different levels of personnel may have different perceptions of safety and their responsibilities for providing safety.
Dr. Sauer reasoned that the rail transit industry faces these challenges and problems because most engineers and safety managers are meticulous and detail oriented, and have been trained to communicate in a very technical manner that is not clear or effective for communicating with management.
Building on these premises, Dr. Sauer used the Columbia space shuttle accident as an example of how poor communication had a direct impact in causing the accident. Speculation and informal communication in NASA emails showed that during the Columbia crisis, disaster response was slowed. As a result NASA began training individuals to distinguish patterns of discourse appropriate to collaboration, information, face-to-face inspections, research and development, and crisis risk decision-making as an ongoing process of research and development work.
Dr. Sauer next presented the Sago Mining disaster as an example of how automated systems of authority impacted the disaster response. Dr. Sauer posed the questions "if we give workers the decision making power as authorized persons, what are their liabilities when the systems fail?" She explained that in the Sago Mining disaster, these automated systems exposed tensions between old and new narrative identities, which required new training and communication practices that was never provided. To manage the risks presented by automated systems of communication, the organization must account for embodied experience, and consider the relationships between "clock time" and "relative time," as well as the human dimensions of automated control.
Dr. Sauer recommended that individuals and managers be trained to contextualize and assess detail for specific audiences. She also recommended that documentation tracking systems be used to insure follow through in communication. She cautioned that specifications of language obscure the distinction between future plans and real time implementation and that Passive sentence structures obscure individual accountability. To combat these problems, individuals should be trained to recognize operational descriptive and functional discourses, and to use active sentence structure to put accountability back into safety communications.
Dr. Sauer next discussed how to persuade audiences through effective communications, noting that stakeholders should be defined and communications should build on what these stakeholders know and understand. Dr. Sauer concluded her presentation by presenting a few techniques for communicating more effectively, including:
Ms. Boyd presented FTA's SSO Program Managers Training Program Curriculum, by first providing the SSO representatives with a brief background of the curriculum and how it was developed. In July, 2006, the Government Accountability Office (GAO) recommended that the FTA Administrator assess whether oversight agency personnel were receiving adequate amounts of training to perform their activities effectively. The GAO recommended that FTA develop an official training curriculum and provide guidance for State oversight agencies, and the provision of FTA resources, if feasible, to support SSO Program Managers in completing the training curriculum.
Ms. Boyd noted that FTA responded to this recommendation by developing a draft training curriculum, which was discussed at the 2nd Annual SSO Program Managers Meeting held in Tampa, FL May 7 - 10, 2007, and in August 2007, began developing Individualized Training Plans (ITPs) for SSO Program Managers. FTA also began allocating resources to fund the SSO Program Manager's training through the Transit Safety Institute (TSI).
Ms. Boyd explained that following the presentation of the SSO Program Managers Training Curriculum in Tampa, FL, FTA distributed the 2007 SSO Program Managers Training Survey. SSO Program Managers were asked to complete the survey, providing FTA with a snapshot of SSO Program Manager training received to date as well as input regarding the usefulness of a wide range of training courses and topics. FTA used the data gathered from the SSO Program Managers Training Survey to further tailor the curriculum to fit SSO Program Managers' needs.
Of the types of training methods available (i.e., workshops, lectures, panel sessions, facilitated structured discussions, facilitated free discussions, case studies, self study, and computer based training), respondents felt that workshops, lectures and case studies were the most helpful. SSO Program Managers were also asked to assess the extent to which they felt they had received a satisfactory amount and quality of training in several key areas. The responses received are provided below.
|Training Area||Training Needs Met||More Training Needed||Unsure|
|Rail Transit Operations and Maintenance||4||25||2|
|Hazard Management Process||1||26||3|
|Reviewing SSPPs and System Security Plans||11||20||0|
|Conducting Audits and Reviews||8||22||1|
|Working with RTA Personnel||16||12||3|
To gather data on the amount of budgetary allocations available for training, SSO Program Managers were asked to provide information pertaining to the training budgets of their respective agencies. The training budgets of each SSO agency varied greatly and in several cases were unknown. Of the 26 responses received, nearly half stated that they received $2,500 or less annually to attend training.
When asked how many times per year they would be able to participate in workshops and training sessions lasting between three and five days, 5 of the 31 SSO Program Managers responded that they would be able to attend once per year, 13 responded that they would be able to attend twice per year, 9 responded that they would be able to attend three times per year, and 4 responded that they would be able to attend training of this length, four or more times per year.
Attendees were finally asked to indicate the level of training they would like to receive (i.e., introductory, advanced, update/refresher, or none) pertaining to FTA's SSO Program and the degree of importance for which they felt the training was necessary. Responses indicate that of the training topics provided, an introductory level of training is desired most strongly for establishing program performance measures for SSO Programs, implementing the hazard management process, and three-year safety and security review conduct. An advanced level of training is most strongly desired for SSPP review and corrective action plan management; and a refresher level of training is most strongly desired for SSO administrative procedures.
Training topics considered to be most important included review of the internal safety/security audit process, Three-Year Safety/Security Review conduct, Program Standard development, Security Plan review, SSPP review, and investigation report review.
After reviewing the survey results, Ms. Boyd explained that the survey results helped to clarify the needs of the SSO community and to develop the ITPs for each SSO Program Manager. The ITPs are being built around the following three training tiers:
Ms. Boyd further explained that FTA is committed to partnering with State agencies to ensure that sufficient resources are available to support SSO Program Manager training. Each ITP will cover the period FY 2008 through FY 2010, and will be developed in consultation with each SSO Program Manager to address Tier 1 and Tier 2 training needs. FTA began contacting SSO Program Managers in August, and so far almost all SSO Program Managers have been scheduled for training through their ITPs.
In each ITP, FTA will identify training costs to be covered by FTA and propose training costs to be covered by the SSO Program Manager's organization. FTA will also track the progress of each SSO Program Manager in receiving this training over the three-year period, and will continue to follow up with his or her supervisor regarding the status of the training plan in semiannual correspondence.
Completed ITPs will be transmitted to each SSO Program Manager's immediate supervisor, soliciting support in the provision of resources to ensure that the SSO Program Manager receives the identified training during the specified three-year period. FTA's Administrator will also send a "Dear Colleague" letter to enhance awareness and request support in implementing the SSO Program Managers Training Curriculum.
Ms. Boyd went on to state that over the three-year period between October 1, 2007 to September 30, 2010, FTA anticipates being able to cover training costs for no less than three core courses. During Fiscal Year 2008 (October 1, 2007 to September 30, 2008), FTA will provide each SSO Program Manager with funds - to be administered by TSI - to attend two of the following core courses: Transit Rail System Safety (FT00543), Transit System Security (FT00432), Transit Industrial Safety Management (FT00457), and Effectively Managing Transit Emergencies (FT00456).
By September 30, 2010, FTA is committed to ensuring that each SSO Program Manager has applied for two (2) certificates - TSI Rail Transit Safety and Security Certificate, and WSO Rail Transportation Safety Certification. TSI awards its Rail Transit Safety and Security Certificate to individuals who have successfully completed four of the five core courses in a consecutive three-year period. Additional information on the TSI Rail Transit Safety and Security Certificate is available at: http://www.tsi.dot.gov/divisions/Transit/TSSP.aspx or by calling TSI at (405) 954- 3682. As part of each SSO Program Manager's ITP, representatives from FTA's Office of Safety and Security will identify key application deadlines and requirements.
In partnership with TSI , the WSO has established two certification categories for the rail transportation industry - Certified Safety Specialist and Certified Safety and Security Director. To be designated as a Certified Safety Specialist, an individual must have successfully completed the five core courses (or have received equivalencies from TSI ) and have a minimum of five (5) years of directly related safety experience in the rail transportation industry. To receive the Certified Safety and Security Director (CSSD) designation, an individual must have successfully completed the five core courses (or have received equivalencies from TSI ) and have a minimum of ten (10) years of directly related safety experience in the rail transportation industry. Additional information on this certificate program can be obtained from WSO World Management Center, 106 W. Younger Ave, Suite G, P.O. Box 518, Warrensburg, MO 64093, Telephone: (660)747-3132, URL: http://www.worldsafety.org/, E-mail: firstname.lastname@example.org.
Ms. Boyd then introduced Ms. Radonna Snider, Program Analyst with TSI , who walked the SSO Program Managers through the travel process to be used in filing their travel forms. Ms. Snider also distributed TSI 's Travel Brochure, which was developed to explain this process to the SSO Program Managers.
Key steps in this process include the following:
Ms. Snider noted that she was available to support any SSO Program Manager with questions regarding this process. Her contact information is:
Mr. Richard Wong, FTA Legal Counsel, then spoke in general terms about the NTSB recommendations and the reauthorization of SAFETA-LU. Mr. Wong explained FTA's current legal position, and noted that additional enforcement authorities for SSO agencies, or direct FTA funding to the States, would require additional delegations of authority from Congress to FTA. Mr. Wong also urged SSO Program Managers to work with their State agencies and lobbying entities and with the American Association of State Highway and Transportation Officials (AASHTO) to place their needs before members of the House Transportation and Infrastructure Committee and its Chairman, James Oberstar.
Following Mr. Wong's remarks, Mr. Taborn led a group discussion pertaining to the NTSB's findings and recommendations from the CTA derailment investigation and the new authorities provided to TSA in H.R. 1 and their potential impacts on the SSO program. The following issues were discussed:
After breaking for lunch, the group reconvened in the hotel lobby and boarded two Metro Transit articulated buses, which transported the meeting attendees to Metro Transit's Light Rail System Maintenance Facility and Control Center. The tour of this facility was organized and coordinated by Mr. Mike Conlon and Mr. John MacQueen of Metro Transit's Safety Department.
In route to the facility, Mr. Conlon and Mr. MacQueen arranged for the group to drive by the site of the Minneapolis bridge collapse, which occurred August 1, 2007. The accident site served as a poignant reminder of the current state of the nation's roadway infrastructure system and how catastrophic accidents can happen so quickly and without warning. Once at the maintenance facility, the participants broke into several groups, which were each led on tours of the facility including the maintenance shops, control center, and power substation. A brief presentation was also delivered by Mr. MacQueen, pertaining to the agency's track worker protection and inspection training programs.
Mr. MacQueen noted that the types of work performed on the Metro Transit ROW include:
Mr. MacQueen stated that regardless of the type of work being performed, training is required. All employees and contractors that will be working within 12 feet of track center must take a 1-hour On-Track Safety training class. All Metro Transit rail employees working in operations or maintenance must be "rules qualified" and must be recertified on those rules annually.
Mr. MacQueen explained that the methods of track protection used at Metro Transit depend on the type of work being performed. Before work begins, a determination must be made as to whether or not the work is routine inspection, if it involves maintenance, if tools will be used, how it will impact train service, and if the track needs to be taken out of service. Depending on the answers to these questions, employees can use five different methods for protecting the track. These include:
Self protection is allowed if the work does not require the use of tools. It is generally for minor inspection or observation of the track. Use of a designated lookout is preferred to individual protection. To use a designated lookout, the work being performed must be of a nature that it can be immediately interrupted so that the crew can clear the track and a passing train can operate through the work area without risk. One person remains focused on train movements at all times and alerts the crew of approaching movements.
Mr. MacQueen next explained the "Line 5" rule and stated that it is used to temporarily restrict a work zone. It requires the use of Track Warrant and can be used at the discretion of the RCC Supervisor as a form of protection for workers in lieu of a work zone. Such usage is limited to locations where trains have clear visibility of the restricted area, and the work performed does not hinder the ability to hear an approaching train, and the work group is able to clear prior to arrival of the train. It may also be used specifically to protect activity along the ROW that may unexpectedly encroach on the ROW , or for switch inspection or other stationary inspections. Mr. MacQueen stressed that it cannot be used to protect transit workers in or near tunnels, or on or near flyovers, with the exception of Lake Street Station within ten feet outside of the railroad signals.
When Line 5 is used, a temporary sign is set to designate a temporary speed restriction. When issued, trains or other track equipment must pass through the stated limits at restricted speed until the rear of the consist is past the restricted zone (rear end restriction) and must look out for persons or equipment in the ROW . The Train Operator is ultimately responsible for the safety of workers when Line 5 is used.
Mr. MacQueen next explained that a movement coordinator is in charge of a work zone. The work zones allow movement of trains through the area only with permission of the movement coordinator. The movement coordinator performs no other work than controlling train movements and ensuring that workers are clear of the track when necessary. This person may or may not be a foreman, but regardless of who holds this role, he/she cannot perform any other work until the job is complete.
The final type of track protection discussed by Mr. MacQueen was "Employee in Charge" protection. This type of protection can be used only when the track is out of service. Therefore there are no train movements in the area. The Employee in Charge is responsible for obtaining permission to occupy the track and is responsible for ensuring all workers and equipment are clear before putting the track back in service. Because there are no train movements in the area, the Employee in Charge is able to perform other tasks while holding this role.
Mr. MacQueen stated that Metro Transit does operate through a tunnel, and that work can only be performed in these locations if the track is taken out of service, or if a work zone has been established. When in the tunnel, track workers must call the RCC to state if they are in the clear. This can only be done if they are inside a cross passage and is not allowed if they are on the walkway.
Mr. MacQueen stressed that communication is the key to a successful track worker protection program. Prior to performing any task requiring the coordination of two or more employees, the employees involved in the job must hold a "job briefing" to insure all have a clear understanding of the task to be performed and their individual responsibilities. The job briefing discusses:
If necessary, an additional briefing is held as the work progresses or the situation changes.
Mr. MacQueen stated that to get the most out of their track worker protection program, they investigate all close calls and try to improve rules and procedures to prevent recurrences. They also retrain employees as necessary. They also try to learn from other agencies.
When WMATA began having track worker safety problems, Metro Transit took its existing protocols and added an additional requirement that track inspectors make a radio statement to the RCC of walking track inspections. Inspectors state the stations they are in between and in what direction they are moving. Walking track inspectors are also required to report to RCC via radio when they pass fixed locations such as stations. The RCC updates train operators of the locations passed by walking track inspectors. The train operators are then required to pass walking track inspectors at restricted speed.
Mr. MacQueen concluded his presentation by reiterating that "safety is everyone's" responsibility. Following Mr. MacQueen's presentation and the tour of Metro Transit's facilities, the group boarded a light rail train which transported the group to the Mall of America for dinner. This trip enabled participants to become better acquainted with Metro Transit's Light Rail System, vehicles, and stations.
The final day of the 11th Annual SSO Program Meeting began with two presentations regarding certifications available to rail transit safety and SSO personnel. Mr. Ronald Keele, Executive Director, Office of Safety and Risk Management, Maryland Transit Administration, explained the process for becoming a Certified Safety Professional (CSP). Ms. Elayne Berry, Executive Director of Safety and Quality Assurance, Metropolitan Atlanta Rapid Transit Authority (MARTA) discussed the benefits of becoming a Six Sigma Black Belt.
Certified Safety Professional
Mr. Keele began his presentation by explaining that there are several different certifications available to rail transit safety and SSO professionals. Perhaps the most common in the industry is the Professional Engineer (PE) designation. Other certifications include:
Mr. Keele explained that Certified Safety Professional (CSP) is the registered certification mark of the Board of Certified Safety Professionals (BCSP), established in 1969 and headquartered in Savoy, Illinois. BCSP also issues an ASP-Associate Safety Professional--certificate as a preliminary step to CSP status.
To qualify for the CSP , one must:
Mr. Keele explained that candidates who have successfully passed other exams through other acceptable certification and licensing programs, and who currently hold such certifications or licenses, may be granted a waiver from the Safety Fundamentals exam. Acceptable certifications and licenses include the Certified Industrial Hygienist (CIH), Certified Health Physicist, and Professional Engineer (PE) designations.
Mr. Keele then presented the following sample question to provide the audience with an example of the type of questions that will be faced on the Comprehensive Practice Exam.
Mr. Keele revealed that the answer to this question is 24,833,382 gallons of water, and emphasized the difficulty of the exam.
Mr. Keele noted that to retain the Certified Safety Professional designation, a person who has met the requirements to achieve the CSP must:
Mr. Keele observed that making the decision to pursue additional certifications is an individual choice. With a CSP , Mr. Keele pointed out that you can achieve a great deal of personal satisfaction by:
Mr. Keele also noted that the CSP credential is a recognized and highly credible designation for safety professionals. There are only 11,000 safety professionals with CSP s in the United States. Receiving such a designation allows you to elevate your status within the transit or oversight agency and increases your recognition among your peers as a competent safety professional. Receiving increased responsibility and increased pay within the organization is also a possibility. Mr. Keele also pointed out that becoming a CSP also improves the agency's image and instills a public confidence and level of assurance in the agency's performance.
Mr. Keele explained that he obtained his CSP when he worked for NASA. He joined NASA shortly after the Challenger accident, and, at the time, NASA encouraged all of its safety professionals to obtain CSP s, in part to restore public confidence in the agency.
For more information concerning the CSP certification, questions can be directed to the BCSP at: 208 Burwash Avenue, Savoy, IL 61874, Website: http://www.bcsp.org/, Telephone number: 217-359-9263.
Six Sigma Black Belt
Ms. Elayne Berry next discussed the benefits of becoming a Six Sigma Black Belt in the rail transit environment. Ms. Berry explained that Six Sigma is a disciplined, data-driven approach and methodology for eliminating defects (driving towards six standard deviations between the mean and the nearest specification limit) in any process -- from manufacturing to transactional and from product to service.
The statistical representation of Six Sigma describes quantitatively how a process is performing. To achieve Six Sigma, a process must not produce more than 3.4 defects per million opportunities. A Six Sigma defect is defined as anything outside of customer specifications. A Six Sigma opportunity is then the total quantity of chances for a defect. Process sigma can easily be calculated using a Six Sigma calculator.
The fundamental objective of the Six Sigma methodology is the implementation of a measurement-based strategy that focuses on process improvement and variation reduction through the application of Six Sigma improvement projects. This is accomplished through the use of two Six Sigma sub-methodologies: DMAIC and DMADV.
Both Six Sigma processes are executed by Six Sigma Green Belts and Six Sigma Black Belts, and are overseen by Six Sigma Master Black Belts. According to the Six Sigma Academy, Black Belts save companies approximately $230,000 per project and can complete four to 6 projects per year. General Electric, one of the most successful companies implementing Six Sigma, has estimated benefits on the order of $10 billion during the first five years of implementation. GE first began Six Sigma in 1995 after Motorola and Allied Signal blazed the Six Sigma trail.
Ms. Berry noted that at MARTA, the Six Sigma approach is used to focus on key performance indicators as they relate to hazard management, accidents and incidents, and investigations. She further explained how MARTA has incorporated the Six Sigma belt designations into its professional development initiatives for staff. She stressed however, that before pursuing this designation, you should first indentify potential projects that can be used to gain the designation and evaluate the return on investment.
Ms. Berry next described the project she pursued to become a Six Sigma Black Belt. This project involved a bus fuel efficiency study that was performed to improve fleet miles per gallon in the operating environment, and to increase the ratio of fuel consumed for revenue service versus overhead. To complete the project, Ms. Berry used various analysis techniques including DMAIC, Cause and Effect Analysis of fuel consumption, SIPOC Diagramming, Process Ranking, Process Capability, and Feasibility Analysis. As a result of this project, MARTA was able to reduce the sources of variations in the fuel and fluid systems for revenue vehicles. It was also able to increase the correlation between actual miles driven and calculated miles per gallon (MPG); model fuel usage before and after the service change occurred to determine the impact and sources of variation on calculated MPG by fuel type to allow for increased efficiency; and reduce operating margins of fuel usage for the revenue fleet.
Ms. Berry explained that to obtain the Six Sigma Green Belt designation requires approximately three to six months. To become a Green Belt, Ms. Berry performed a study to improve reliability and reduce service interruptions by evaluating pre-in-service rail car inspections effectiveness in identifying defects prior to entering service. Other proposed Green Belt projects include:
Ms. Berry concluded her presentation by noting that Six Sigma provides a unique approach to resolving real-word problems by combining proven elements of total quality management with systems analysis. This program also promotes professional development of quality and safety staff, and generates cost savings that are readily apparent to executive leadership.
The final session of the 11th Annual SSO Program Meeting was devoted to accident investigation. This session included three presentations on accident investigation practices, followed by a question-and-answer period.
Accident Investigation as a Collaborative Effort
Mr. Jerry Shook, State Safety Oversight Program Manager, New York Public Transportation Safety Board, delivered the first presentation of the day pertaining to effective practices in accident investigation. He began his presentation by providing a brief overview of his agency.
The Public Transportation Safety Board (PTSB) was created by the State of New York in 1984, in response to recommendations from the National Transportation Safety Board (NTSB). PTSB was one of the first dedicated safety oversight agencies in the country, and, along with the California Public Utilities Commission, the Massachusetts Department of Public Utilities, and the Pennsylvania Department of Transportation, was one of the models cited by NTSB in its recommendations to FTA to create the SSO program.
When FTA's SSO rule was originally published, Mr. Shook noted that the PTSB was the obvious choice to implement Part 659 provisions for the two rail transit systems in the State of New York: New York City Transit (NYCT) and the Niagara Frontier Transportation Authority (NFTA), a light rail system in Buffalo.
In 1997, PTSB had 12 years of experience, an existing Safety Program Standard, an accident investigation process, a process for managing corrective action plans, and a positive working relationship with the rail transit agencies. Additionally, PTSB had already required each rail transit agency in its jurisdiction to create and implement a System Safety Program Plan.
Mr. Shook noted that PTSB is responsible for investigating or causing to be investigated, all rail transit accidents meeting the reporting thresholds established by Part 659. The investigation process is focused on determining how the accident took place and what caused it. The effectiveness of the investigation process is maximized through a strong working relationship and cooperation with the rail transit agencies, their Safety Offices, and through shared resources.
Mr. Shook explained that resources are an issue for all SSO agencies and for the transit agencies as well. By combining efforts during accident investigation, through participation in rail transit agency accident investigation teams, committees, boards, and task forces, both the SSO agency and the rail transit agency can benefit.
Mr. Shook noted that PTSB has a formal and public process in place for adopting accident investigation reports. Mr. Shook explained that, for each accident investigation, based on the evidence collected and, often in partnership with the rail transit agency, PTSB drafts a report meeting its internal guidelines and format. This report is shared with the rail transit agency.
Meetings are then held to address any concerns that either agency may have. Once these concerns are addressed, the report is sent to the PTSB Board for review and approval. Once approved, it is returned to the rail transit agency for corrective action plan development. Corrective action plans are reviewed and approved by the Board and tracked through fruition, pending any further developments that may arise.
Mr. Shook concluded his presentation by noting that, while specific authorities to request or subpoena records and to formally and publicly approve accident investigation reports can be useful to SSO agencies in conducting accident investigations, it is far more important to establish a positive working relationship with the rail transit agencies. Partnering on critical safety issues, such as accident investigation, enhances the programs and capabilities of both agencies.
Multi-Modal Accident Investigation
Following Mr. Shook's presentation, Mr. Ron Keele presented the Maryland Transit Administration's (MTA) processes for multi-modal accident investigation. Mr. Keele gave this presentation on behalf of Ms. Bernadette Bridges, Deputy Executive Director, Office of Safety and Risk Management, MTA, who had to leave the meeting unexpectedly.
Mr. Keele explained that MTA operates light rail, heavy rail, commuter rail, bus, and contracted commuter bus and paratransit service. Mr. Keele noted that it is the policy of the MTA to ensure that all accidents/incidents, regardless of origin, the operator(s) involved, or of the responsible party, be subject to a formal and objective investigation. Therefore, internal accident notification and reporting requirements are very important.
Mr. Keele noted that all accidents involving MTA vehicles, stations, right-of-way, or other MTA properties under the direction of the MTA Operations Control Center (OCC) are reported to the Office of Safety and Risk Management. Notification is made through MTA's Emergency Notification System (ENS), which alerts all essential MTA personnel, including the Rail Safety Oversight Agency (RSOA), of the accident.
The notifications are received via cell phone, are voice recorded, and automatically assigned a unique identification number that is provided at the end of the notification message. The call is electronically recorded and logged for a period of two weeks.
Once notified that an accident/incident has occurred, it is the responsibility of the Executive Director, Office of Safety and Risk Management, or a designated representative, to provide continuing updates to the app opriate MTA Deputy Administrator(s), regulatory agencies, and other personnel. If necessary, the Director, Office Safety and Risk Management, or a designated representative immediately notifies the National Response Center/NTSB of the accident/incident.
Mr. Keele explained that each MTA mode has been assigned a safety officer who is responsible for responding to the accident. For MARC Commuter Rail, the safety officer is also responsible for coordinating with the FRA . Upon notification and based on the severity of the accident (all fatalities, occupational injuries, high-visibility events, and near misses) modal safety officers respond to the accident scene to perform the accident investigation, according to MTA's accident investigation procedures. The MTA Transit Police also play a critical role in accident investigation. Mr. Keele noted that his RSOA , represented by Mr. Matt Bassett, also frequently responds to rail accidents.
All vehicle operators and MTA personnel are required to follow the appropriate standard and emergency operating procedures (SOPs/EOPs) while at the scene of an accident/incident. The role of on-scene coordinator will often change during the course of the accident/incident. As the first MTA representative at the scene, the vehicle operator serves as the acting on-scene coordinator until emergency responders arrive or until otherwise instructed by the OCC . The primary responsibility of the operator is the safety of his/her passengers and any injured parties. At no time shall the operator volunteer any information regarding the accident/incident to anyone except MTA personnel or the police. It is the responsibility of the operator to assist emergency response personnel as they arrive at the scene and to maintain contact with the appropriate OCC .
As emergency responders and MTA personnel arrive, various mechanisms may be used to control the scene and to begin the accident/incident investigation process. Depending on the severity and location of the accident/incident, access to the scene may be restricted, photographs and measurements may be taken, and witness statements may be gathered. It is the responsibility of all MTS personnel at the accident/incident scene to support all investigation efforts as deemed necessary by the on-scene coordinator. This may include submitting to drug and alcohol screening.
After completing the preliminary investigation, a fact report is generated and provided, within 24 hours, to MTA executive management staff and the RSOA . The Report provides a description of the accident and photographs depicting the physical evidence of the accident scene.
Each report is assigned a unique document control number such as LR.A.09172007-1. This number provides the following information:
For contracted operations, such as contracted commuter bus and paratransit operations, the contractors' dispatcher is notified of the accident/incident and is then responsible for coordinating and monitoring emergency response efforts. Contractors maintain accurate accident/incident and injury data, and shall cooperate with all accident/incident investigations. This includes submitting comprehensive accident/incident reports to the MTA as well as any other information the MTA deems necessary to conduct an accident/incident investigation and to ensure similar events do not occur.
For MARC operations, all accidents/incidents are reported to the dispatcher for the territory in which the train is operating. The train dispatcher then notifies emergency personnel and coordinates and monitors all corrective and emergency response action required at the site. The Amtrak/CSX Safety Department conducts a formal investigation into the accident/incident and prepares a report or submission to the appropriate authorities. Notification of an accident/incident can be made by telephone, two-way radio, fax or personal pager. The MTA MARC Control Center is also informed of the event and notifies the Office of Safety and Risk Management. By agreement, Amtrak/CSX is responsible for preparing all accident/incident reports for MARC service. The MTA is the reporting railroad however and must authorize all MARC reports prepared by Amtrak/CSX. The MTA is also notified of all accidents/incidents involving CSXT freight operations that may affect MTA operations or services.
For more serious accidents, under authority conferred to the MTA Executive Standing Safety and Security Committee (ESSSC), an Accident/Investigation Board may be established. The Executive Director, Office of Safety and Risk Management is responsible for notifying the AIB members of their participation in the investigation. The safety representative, or ranking safety office staff member, if more than one safety representative is present, serves as the Accident Investigation Board Leader unless the Executive Director, Office of Safety and Risk Management appoints a different leader at the discretion of the ESSSC .
The AIB is authorized to conduct the investigation of the accident/incident in the most expedient manner as determined by the Leader in conjunction with the ESSSC and the Executive Director, Office of Safety and Risk Management. The AIB is also authorized to impound, receive, and examine any evidence related to the accident/incident. The AIB is responsible for maintaining the integrity of the evidence and the chains of custody. In fulfilling this responsibility, secure facilities and assistance from the MTA Police may be utilized. At no time shall the investigation interfere with rescue operations.
In all cases, the MTA strives to identify the causes and contributing factors to the accident/incident and to take immediate corrective actions to ensure that the same or similar type of accident/incident does not occur. Accordingly, it is critical that the accident/incident investigation process maintains a strong link to the hazard and risk identification and resolution process.
Depending on the complexity of the accident, a comprehensive report is required to complete the investigation. This report must be completed and submitted within 30 days to MTA executive management and the RSOA agency, the Maryland Department of Transportation (MDOT). This report may include descriptions of the following:
The MTA works and meets with its RSOA at quarterly review meetings in which accident/incident reports are reviewed for completeness; the status of outstanding findings and corrective actions are reviewed; and report discrepancies and any other additional recommendations by the RSOA are discussed.
Additionally, the MTA ESSSC meets to ensure that all major accident recommendations are implemented as defined by the System Safety Program Plan. The ESSSC also assure that findings and recommendations which cannot be resolved at staff level are presented for executive committee resolution and implementation.
Accident Investigation for Streetcar Systems
The final presentation of the 11th Annual SSO Meeting was provided by Mr. Joe Diaz, System Safety and Security Officer, Hillsborough Area Regional Transit Authority (HART). Mr. Diaz began by describing the TECO Line Streetcar System, operated by HART and located in Tampa, Florida. Phase I of this system opened in 2002, and provides 2.3 miles of service connecting downtown Tampa, Channelside and Ybor City. Phase II, currently in the planning stages, will extend service an additional 1/3 mile into the downtown central business district. It will connect the more than 35,000 people who work in the downtown area to almost every major downtown parking structure.
Mr. Diaz noted that, while small, the TECO streetcar carries passengers to and from numerous businesses, major hotels and entertainment venues throughout the Ybor and Channelside districts. The line also provides service to the Tampa Convention Center, Tampa Aquarium, Port of Tampa Cruise Ships, and the St. Pete Times Forum - home of the Tampa Bay Lightning.
Mr. Diaz noted that average annual ridership for the streetcar is 419,878, with an average monthly ridership of approximately 34,989. Over sixty percent of TECO streetcar service is provided to tourists and over 60 percent of TECO's ridership occurs on the weekends. Mr. Diaz also noted that current ridership statistics show an increase of approximately 40,000 riders for Fiscal Year 07. Several key special events have generated this increased ridership. TECO streetcars can also be chartered for special occasions such as conventions, weddings, parties.
TECO operates a conventional electric rail (600V DC) overhead catenary system (OCS). It is a single-track, bi-directional system with six sidings (passing tracks) to permit the passing of streetcars traveling in opposite directions. Streetcars operate by line of sight with one direction having right over the other. Streetcars traveling in the opposite direction must enter designated sidings and await the arrival of the streetcar traveling in the opposite direction.
Mr. Diaz explained that HART owns ten historic replica streetcars: nine Birney cars and one breezer-style car all purchased from the Gomaco Trolley Company in Ida Grove, Iowa. In addition to the ten Gomaco cars, a restored standard single truck Birney Safety Car owned by the Tampa and Ybor City Street Railway Society is also housed at the Ybor Station facility.
A key feature of the system is an at-grade crossing (Ybor Interlocking) of the CSX Railroad's Tampa Terminal Subdivision located near the old alignment of 13th Street between 4th and 5th Avenues in Ybor City. CSX personnel conduct training on interlocking to student motormen.
Mr. Diaz noted that the streetcar tracks do not share vehicle travel lanes, and are separated from street traffic by low barriers and landscaping. At signalized intersections, a separate signal (Opticom) is linked to the traffic control system. Mr. Diaz pointed out that one would think that the possibility of accidents would be limited to driveways and intersections.
However, this is not the case. Mr. Diaz then proceeded to show a number of photographs depicting automobiles (including a police car) that had crossed the barriers and landscaping into the streetcar tracks and struck a TECO streetcar. He noted that since 2003, the TECO system has experienced 69 total incidents to date and that 43 of these incidents involved automobile turns/pulls in front of streetcar. Mr. Diaz observed that, statistically speaking, an automobile turning/pulling in front of the streetcar is the biggest threat to system safety.
Mr. Diaz joked that HART has had so much experience investigating streetcar accidents, that the agency has been forced to revise its accident investigation procedure a number of times. The most current version is called "Investigation of Incidents and Hazardous Conditions Procedure, No. 2, Version 8, January 2007."
Mr. Diaz then reviewed the procedure and showed the forms used to document the investigation. Mr. Diaz noted that the procedure explains how investigations will be conducted by the HART Office of Safety and Security for Streetcar Operations. The procedure also applies to any identified hazardous condition. A second purpose of the procedure is to provide a uniform policy for the establishment and assembly of a HART Incident Investigation Team.
Mr. Diaz noted that "major incidents," including a fatality or multiple injuries, a collision, derailment or fire that causes property damage in excess of $25,000, or a hazardous condition, are investigated by the HART Incident Investigation Team, as directed by the HART Office of Safety and Security. "Minor incidents," which includes everything else, are investigated by frontline supervisory personnel, as directed by the Office of Safety and Security.
When investigating a "major accident," the HART System Safety and Security Officer is the Team Leader. Permanent members of the HART Incident Investigation Team are designated by the Office of Safety and Security and include the following: System Safety and Security Officer, Manager of Streetcar Services, Risk Management, and a Transit Supervisor. A minimum of three (3) team members are used for investigation when activated.
During investigations, the HART Incident Investigation Team is responsible for performing the following activities:
The Initial Incident Reports include:
Mr. Diaz noted that HART spent a lot of time working on its accident investigation form, including the creation of diagrams with images of the streetcar, to ensure that both HART personnel and Tampa police could accurately document the accident.
Mr. Diaz also explained that, for minor incidents, all Motorman Accident Reports are submitted to Dispatch for time and date stamp on the same day of event. All Transit Supervisor Accident Investigation Report/Materials are placed in a manila envelope with checklist label to identify all items contained in envelope:
Mr. Diaz explained that HART 's Risk Department personnel pick up all reports twice daily Monday through Friday. The Risk Department provides Safety Department with copies of all reports daily, and the Safety Department reviews all reports and records them categorically in a Monthly Occurrence Incident Summary Log.
Mr. Diaz also explained how HART reviews the accident reports with employees. First, accidents/incidents involving any HART vehicle are reviewed by the Safety Officer to determine preventability. Prior to the rating, the Safety Officer meets with the employee to discuss the accident/incident. At the meeting, the employee is informed of the rating. The employee receives written notification of rating and if preventable, penalty. The employee is entitled to appeal the preventable rating to the Tampa Area Safety Council.
Mr. Diaz then explained the discipline for involvement in a preventable accident within a 12-month period:
Mr. Diaz also explained that individual accidents drop from an employee's record after 12 months from date of accident. Mr. Diaz noted that as a result of this policy, a number of streetcar motormen were forced to resign.
Mr. Diaz ended his presentation by reviewing several hazardous conditions that the system has experienced since it began operation and how they have been resolved. On the street running sections of the alignment, trolley operators found it difficult to judge the distance to intersections and motorists sometimes found it difficult to judge the distance between their vehicles and the trolley/right-of-way. As a result, side impact collisions did occur. To resolve this hazard, Mr. Diaz and his staff worked with the city of Hillsborough to paint lines on roadway pavement to clearly delineate the operating envelop of the trolley.
Mr. Diaz also described that, in response to a series of yard derailments, a program was developed for re-training motormen and providing written safety warnings. Right yellow clearance Lines were also painted in the Barn and Yard.
Mr. Diaz explained that, as a result of one collision in 2004, an automobile hit and damaged a switch box. HART repaired the switch, put in a speed restriction, and acquired an outside contractor to inspect switch and provide written documentation of switch condition.
Mr. Diaz provided another example in which the HART determined that it was unprepared to remove trolleys from service and to store them in a safe location during an extreme weather event such as a hurricane. In response, the organization entered into an agreement with a local towing contractor and executed a mock exercise to determine how long it would take to remove a trolley from service and place it into storage. HART personnel determined that approximately three hours are required to remove one trolley from service, transport it to the contractor's storage site, and return to get the next trolley. The agency has since developed a plan for emergencies such as these.
Mr. Diaz noted that he has established a strong relationship with his SSO agency, the Florida Department of Transportation (FDOT). He pointed out that FDOT and the SSO Program Manager, Mr. Mike Johnson, support his activities, provide a thorough review of his accident investigation reports, and actively track the status of his corrective actions. Mr. Diaz noted that FDOT oversight has been particularly helpful to use a leverage point in working with the city of Hillsborough on getting corrective actions implemented, such as the painting of lines on roadways.
Mr. Diaz concluded his presentation by observing that even though the job of keeping a rail transit system safe may sometimes feel like a gigantic, overwhelming task, it is critical, in the words of Winston Churchill, to "never, never, never give up."
Questions and Answers
After the presentations, participants asked Mr. Shook, Mr. Keele, and Mr. Diaz questions about the types of accidents they investigate, the biggest challenges they face in addressing Part 659 accident investigation requirements, and how they communicate with transit supervisors and police during accident investigations. Mr. Diaz also received several technical questions regarding the operation of the TECO streetcar.
The 11th Annual SSO Program Meeting concluded with an open forum for discussion. Participants identified what they liked about the meeting and areas for improvement. See Appendix C of this report for greater detail.
Several locations were suggested for the 12th Annual SSO Program Meeting, including San Juan, Puerto Rico and Charlotte, North Carolina. FTA will coordinate with SSO and rail transit agency officials prior to making a final determination on the site of the next workshop.
Mr. Taborn officially adjourned the 11th Annual SSO Meeting, and thanked all participants for their hard work, contributions, and commitment to safety and security.
State Safety Oversight
Special Training Sessions
11th ANNUAL SSO PROGRAM MEETING EVALUATION SUMMARY
The 11th Annual Meeting State Safety Oversight (SSO) Program Meeting focused on a range of issues of interest in the rail transit safety, security and oversight community. The Annual Meeting included 18 sessions over four days:
Monday, September 17, 2007
Tuesday, September 18, 2007
Wednesday, September 19, 2007
Thursday, September 20, 2007
At the conclusion of the meeting, participants were asked to complete an Evaluation Form rating the hotel setting and each session held with areas provided to include personal comments. Of the approximately 75 attendees from rail transit agencies, SSO agencies and FTA Regional Offices, 46 participants submitted their completed evaluation forms. The results of the submitted evaluation forms are presented below. (Note: The approximately 20 other attendees from Federal agencies, universities, and industry associations did not complete evaluations, since either they only attended part of the meeting to give a presentation or they sponsored the meeting.)
In their overall evaluations of the Program Meeting, on average ninety six (96) percent of Program Meeting respondents either strongly agreed or agreed with the following statements:
As part of the Evaluation Form, participants were asked four questions:
The Feedback and Comments section of the summary documents the actual comments made by participants for each of these questions. Below is a summary of Key Points that participants made in these comment sections:
Participants were asked to rank, on a four-point scale, the quality of the Millennium Hotel as a meeting venue and the guest room accommodations for the 11th Annual SSO Program Meeting. Overall, participants were pleased with the Millennium as a venue however they felt that the guest room accommodations were not quite up to the standards set at the Spring Meeting and the last DOT / DHS Safety & Security meeting. Actual comments made by the participants appear in their entirety in Appendix A: Feedback and Comments.
The following depicts the four-point rank scale used:
|Hotel Room Accommodations||2||10||20||11||2.93|
|Meeting Room Accommodations||0||3||17||26||3.50|
|Program Meeting/Networking Reception||0||1||10||29||3.70|
|Breakfast, Lunch and Snacks||0||0||15||31||3.67|
2. Quality & Usefulness of Sessions
Participants were asked to rank the quality of each session conducted during 11th Annual Meeting SSO Program Meeting and its usefulness to their work using the following four-point scale:
|McElveen, Caton, Lofton||Status of SSO Audit Program Findings||3.49||3.63|
|Taborn, Wong & Boyd||Hazard Management Process Clarification||3.40||3.51|
|Hartberg||Internet Based Hazard Tracking Systems||3.37||3.28|
|Macdonald||Identifying and Managing Hazards from the Internal Safety Audit Process||3.33||3.26|
|Shashidhara||Identifying and Managing Hazards during Operations||3.16||3.16|
|Impastato||Identifying and Managing Hazards during Operations||3.40||3.27|
|GROUP EXERCISE||Hazard Management Program Break-Out Sessions
(Team Building Exercises)
|Boyd, Gunka, Taborn, Wong & Flanigon||NTSB Findings and Recommendations||3.61||3.60|
|Flanigon, Colbert & UTC Representatives||University Transportation Center Research Programs||2.73||2.40|
|Gerhart, Roe & Farmer||Partnering for Rail Transit Security Oversight||3.32||3.21|
|Sauer||Rail Transit Agencies: Risk Communication: Making the Case for Safety in Presentations*||2.83||2.92|
|Boyd, Snider, Caton, Wong & Taborn||State Safety Oversight Agencies: FTA's SSO Program Managers Training Program Curriculum*||3.46||3.46|
|Conlon, MacQueen||Tour of Metro Transit Light Rail System||3.73||3.63|
|Keele & Berry||Safety Credentials: Becoming a CSP and SIGMA SIX||3.34||3.03|
|Shook||Effective Practices in Accident Investigation - Lessons Learned||3.39||3.12|
|Keele||Multi-Modal Accident Investigation||3.49||3.37|
|Diaz||Effective Practices in Accident Investigation - Streetcar Systems||3.59||3.47|
|McElveen, Taborn, and Wong||Accident Investigation Questions and Answers||3.38||3.39|
The "Quality and Usefulness of Session" section included an area where participants were provided space to answer the follow question:
"Any comments on the sessions or suggestions for improvement?"
The following is a brief summary of some of the comments. The actual comments are presented in Feedback and Comments.
Each area of the 11th Annual SSO Program Meeting Evaluation form contained a section where respondents could enter personal comments. Below are the questions and actual comments made by respondents for each section as applicable.
Any comments on the accommodations or suggestions for improvement?
1) The hotel rooms were so-so, not what I was used to after Salt Lake, Tampa, etc.
2) Hotel - no room heat. PowerPoint handouts at time for presentation would be helpful.
3) Thank you for arranging/coordinating the accommodations. IT has been an absolutely enjoyable week. Having coordinated smaller scale events similar to this, I understand the amount of resources this must have cost. Thank you once again for all of your efforts.
4) Printed copies of presentations would be helpful. More time allotted to Q & A. Less TSA - they tend to be repetitive in their presentations.
5) Multiple projector screens or displays should be used in a large room. Use microphones in fixed locations so that audience contributors have a better chance of participation, i.e. those wishing to speak would queue up at the microphones and await their turn to speak.
6) Did not like having to pay $9.95 each day requiring a new subscription daily for internet access. Many hotels off free internet.
7) Vinyl seats leave a guy sweaty and hot. Please require cloth seats in the future.
8) Hotel wasn't as nice as the others. The HVAC didn't work well, plumbing backed up repeatedly, the ice machine produced foreign matter in the ice, etc. Otherwise the meeting accommodations were excellent.
9) The hotel rooms were small and drafty. My room fluctuated in temperature often and the bed was lumpy. The bathroom was extremely small and the exhaust fan did not work.
10) I am a newcomer in a start-up so do not have comparative experience for this forum. However, I did try to complete survey and I intend to attend future meetings.
11) One of the best decors in Minneapolis. Breaks well spaced. Cokes should have been left on the table instead of taken away after snack. Great variety of snacks. Bigger font size for names on nametags.
12) Small rooms. Have to pay for water.
13) Room - no heat.
14) Two years in a row I have stayed at the overflow hotel. On both occasions it appears that the accommodations at the overflow hotel have been better. Last year we received free cooked to order breakfast and free internet and printing. This year we had free cooked to order breakfast and much larger rooms. More homework should be done to provide the best accommodations possible. At this rate I prefer to stay at the overflow hotel. The only issue I have it that we were told that the 2nd hotel was 4 blocks away. However, it was more like 10 to 12 blocks away. This years meeting room was not as nice as the one in Utah.
15) Larger projection screen (which would require larger room).
16) I stayed at Embassy Suites; excellent facilities and comfort. At Millennium - lunch delicious and very nice conference room. Meeting recommendations at Puerto Rico - First weeks of November are perfect because hurricane season ended and is low season tourism. Flight and hotels cheaper than in summer.
17) Because I called after the cut off date, I was lodged at the Embassy Suites. Very good facilities.
18) Audio at times was too loud.
19) Good meeting.
2. Quality and Usefulness of Sessions
Any comments on the accommodations or suggestions for improvement?
1) Time management needs to improve. For example, the UTC's talked for two hours in a supposed "dialogue" and the SSO/RTA groups had about ten minutes. It was also very concerning when time was spent on word games and hearing from Dr. Sauer, but the attendees (who were paying to attend) were told there was no time and we "had to move on." I should point out that Dr. Sauer had a day and a half to present in Tampa for the SSO's and three hours with the RTAs here. I felt (and many of my colleagues agreed) that she had more than enough time, her material was tangentially relevant at best, and her presence for all four days was not necessary.
2) Joe Diaz talked much too fast - difficult to follow and absorb all the valuable information he had to share!
3) Time not productive for Sauer and UTC sessions. This time needed for more group discussions on key SSO issues.
4) Reduce the number of "second tier topics" and allow more time for the "very useful" topics. This way there will be more time available fro discussion. 49 CFR Part 659 requirements - refresher of what the rule requires would be useful. Case studies of best practices of Hazard Management program implementation by RTAs. Panel member's content materials should be vetted to ensure valuable subject matter is presented that is relevant to the SSOs and RTAs. Review the steps involved in New Starts being compliant with 49 CFR Part 659 would be valuable.
5) Poor coordination in the field trip facility.
6) Had to leave prior to last presentation on Thursday.
7) Additional question time.
8) This has been a week of learning for me. I have enjoyed many of the presentations observed this week. However, it will be equally more engaging if more time was allowed for open forum/discussion. It is helpful to hear from agencies across the country and all sides.
9) SOA community must have support of FTA. Administrator must have that support illustrated to RTAs and other State and Federal partners. RTA must be a role model on Safety of organization being a direct report and statewide within the organization. Most FTA resources and legislation influence revolves around funding, not safety. It is frustrating to hear issues raised and not clear answers given. Safety and Security is first - not second behind funding, but funding is more glamorous.
10) Provide more opportunities for individual discussion outside of the group discussion sessions and facilitate the group discussions in a more controlled manner. There are obviously many individual agenda that detract from group discussions.
11) Perhaps some presentations by SSO/ SOA on how they plan, prepare and implement the safety and security Triennial Review.
12) Stay more focused on the topics and not allow discussions to get out of hand. We would have got a lot more done if certain agencies would not have tried to use up everyone's' time.
13) I would recommend a 10 minute break every 50 minutes.
14) More time for questions and answers should be programmed into the conference. Workshops on Hazard management & Identification should begin now.
15) Dr. Sauer spent too much time on anecdotes and self promoting which detracted from her presentation. I would very much enjoy a featured course on report and project presentations, statistical analysis which would include Microsoft Project, Excel Graphics and so on. A more technical session at the intermediate to advanced level. I found the SIGMA 6 program very intriguing. I would like some contact information for the program.
16) Bev Sauer needs a PowerPoint editor - her slides were too cluttered and confusing. Break-out session for separate SOAs and RTAs was extremely beneficial. Attendance list/attendee face book would be very helpful for new, first-time attendees. Even a list of addresses (email and postal) and phone numbers.
17) Sometimes I wonder how much RTA's and SOA 's play a role in developing the agenda. Some of the sessions are really great and others are dry. Are we doing a good job at capturing what people want to hear about when they attend these meetings? I think we've had enough of Dr. Sauer. We deferred to her too much during Q & A as opposed to letting RTA's and SOA 's get their questions in.
18) Sessions about investigations are very important and would be better presented during Tuesday or Wednesday because Thursday a lot of people went back home and missed the session.
19) I would have given Thursday's training earlier and would have given the Risk Communication last. Because of flight arrangements to Puerto Rico, I think I missed one of the most important and useful training that was given on Thursday.
20) More focus on the practical aspects of the SSPP and SPP planed development and implementation would have offered more of an opportunity to learn of best practices and lesson learned from the experiences of other agencies. A majority of the topics were more " FYI " information rather than core knowledge. From talking to participants it seems that the core knowledge such as requirements of plans and implementation of safety elements, obligations under 49 CFR Part 659 may not be fully understood by RTA and SSO reps with more experience than me.
21) After 3 hours of one subject my eyes were glazed over. Please limit any subject to no more than 1 1/2 hours.
22) Flip charts should be set up for "parking lot" issues that people want to bring up that really don't fit into the question portion. A one-hour session at the end of the day should be used to cover parking lot issues and those interested could stay and participate. Participants should be encouraged to ask related questions and keep non-related comments on "parking lot" list.
What did you find the most beneficial from the 11th Annual Meeting SSO Program Meeting?
1) Networking. Open forums. Presentations.
2) Group discussions.
3) Discussion of NTSB , CTA Report.
4) Hazard management, accident investigation, ISAP, group discussions.
5) The information applied directly to my work.
6) The discussions about TSA's potential role in security. The hazard management process and the tour of the Metro Transit facility were the most useful and interesting components. Also the Thursday morning.
7) Dr. Sauer's presentation
8) Thursday, Jerry (Shook) from New York and Tampa (Joe Diaz), Systems and practices in reference to accidents and reporting.
9) Discussion on the implications of the latest NTSB hearing on the CTA derailment. Discussion on the Hazard management program clarification - however there should be more time allocated to this topic at the spring meeting.
10) Clarification of hazard management.
11) Update on UHC information and learning about funding for TSI training.
12) The review of the CTA /NTSB Investigation
13) The networking opportunities.
14) Accident investigation Thursday morning session.
15) Updates on development of Federal view of what the SSO program is and is not intended to be.
16) Many of the presentations were helpful and motivating. But the most beneficial of this week was the exchanges made between agencies.
17) Networking, learning from both peers and transit agencies.
18) I was glad to have the opportunity to meet my peers from around the country.
19) UTC activities.
20) Discussion on topics with other agencies.
21) Opportunity to make contacts of other peers and learn what others do.
22) Meeting of peers across the country.
23) Meeting peers. Discussions of relevant topics. Information on FTA.
24) Clarification on hazard management implementation, future trends in security oversight and networking.
25) The individual discussion with colleagues across the country.
26) Lessons learned from CTA /NTSB . Tour of OFM. Presentations that included working tools.
27) Finding available hotel rooms at the government rate. Selecting a city that has non-stop flights to most major cities. Noontime adjournment on the last day.
28) Interaction between my peers.
29) Accident Investigation session, RTA tour, TSI training and Chicago/NTSB report.
30) The open candid discussions amongst those present. Appreciated the opportunity to be able to personal meet, interact and exchange ideas with other transit agency professionals. Networking not only important but very beneficial.
31) The interaction with other system operators and SSO.
32) Visit to Metro Transit!
33) Hazardous tracking.
34) Very good representation of speakers from different agencies. Presentation on Audit process was very helpful, as well as Accident Investigations and Hazard management topics.
35) I heard that other transit companies were so confounded by the FTA directions on the subject of SSPP and SSP .
36) Break out groups let every individual voice their opinions or facts about situations from their experiences.
37) Opportunity to learn from Transit professionals from many different cities, different communities, with varied job experience.
38) Hearing thoughts and questions from other RTA/SSOs. How the other SSO did with FTA audit. Hazard management approaches from RTA/SSO. NTSB CTA investigation.
Was there anything you felt should have been covered that was not?
1) More security issues/discussion.
2) I suggest that for the next meeting, FTA consider an "Ask FTA" 2-hour block where we can bring prepared questions to present to an FTA panel and hear back from the group. This would focus more discussion on the concerns of the SSO's and RTA's and if the questions are prepared, the discussion might be more focused.
3) Corrective action plans. Security plans.
4) Rule requirements and New Starts. More information about audit process - FTA Audit of SSO. More clarification of Rule requirements of the triennial review by SSO of RTA. More clarification of Rule requirements of RTA internal safety audit.
5) Audit standards.
6) Detailed New Starts process!
7) The program was filled with useful information. I would like to observe more discussion of capital projects. In particular, the working relationship/improvement of the working relationship between FTA, PMOC s and the SSOA personnel.
8) Hazard management. While on the agenda, there is still a lack of understanding and widely varied opinions. Result is frustrating. Can this truly be regulated or should it be? HM is common sense - doing the right thing. Is it necessary to report HM's or should concentrations be on fixing? The audit process and oversight will shed light on HM if correctly carried out. Therefore, should we waste time on additional reports and matrices?
9) I would have liked to hear the CTA derailment recommendations from an NTSB at the conference.
18) More information on security.
19) What gets marked SSI and what doesn't? The first day I thought someone said that would be covered later in the week.
20) Most things were covered. Maybe more detail on some items could have been provided.
21) Analysis of monumental amounts of emails received. -How to determine what is important to you. Filters available, labeling priorities? Other suggestions. Presentation overview by Tony Tisdale to explain what he normally receives and criteria for distribution.
22) No. Only that Thursday's training should have been given earlier.
23) No, but TSA left me with unanswered questions and doubt.
24) I felt that the worker protection issue should be brought forward and placed ahead of many of the presentation this week. Losing one life is far more devastating than one derailment.
25) Information form the conference outline was successfully administered.
26) Terrorism. We don't need another awareness level presentation, but an exchange of true "best practices" discussion would be a great benefit. With November 2008 being a presidential election, terror threat level will certainly be highlighted.
27) TSA thoughts on security other than terrorism.
Do you have any suggestions for topics you would like to see covered in future SSO Program Meeting?
1) More case studies; group discussions.
2) Specific security related topics other than terrorism/TSA related. Triennial audits technologies/best practices.
3) More automated tracking and documenting of program requirements.
4) General Managers' need to be involved with this group, even if it's only for one day.
5) Corrective Action plans - requirements of the Rule and how to ensure smooth implementation of CAPS. Exercises in effective communications with rail transit agency staff.
6) Auditing methods and standards.
7) Hazard Analysis. Operational case studies. Configuration management and document control.
8) How about conducting training sessions that would count for certification.
9) Please see the response to the previous question. (The program was filled with useful information. I would like to observe more discussion of capital projects. In particular, the working relationship/improvement of the working relationship between FTA, PMOC s and the SSOA personnel.)
10) Accident investigation forms a regulatory perspective. Workshop to approach PRNM - involvement in legislative process and proceedings. Safety and security - the connection.
11) I would like to have the opportunity to present accident investigation and hazards condition findings from our property and solicit feedback and discussion from the SSO/RTA community.
12) Reducing the stress of auditing.
13) Compare how RR & transit stack up in light of NTSB safety criticisms of Chicago.
14) Hours of Service.
15) Some focus on getting the RTA's classes on doing what is required in 659.
16) Possible and upcoming changes to rules affecting the SSO Program.
17) SSMP responsibilities.
18) Please see page 3 (Quality & Usefulness of Sessions) in regards to a short technical session. Asset management (not more than 60 minutes). Newly promulgated regulations overview and how they integrate with other agencies i.e. OSHA, TSA, FTA and of course, the SSO's. Preventability analysis.
19) NTSB - how they handle recommendations to close out, the availability/disclosure of their accident investigation data, who are the NTSB members.
20) Models to improve hazard management issues.
21) Where problems have occurred in reporting incidents.
22) More on security if TSA doesn't take it over.
23) Should offer TSI training during one or two days to make it more worth our time.
24) Forum for security/police representatives to discuss program issues - separate training session to focus on changing security regulations (essentially a break-out session after a group review is conducted by FTA & TSA.). Developing liaison between Police (either local or transit) with Safety Department (developing good working relationships). System Security and Emergency Preparedness Plan development, combining System Security Program Plan with System Security and Emergency Preparedness Plan.
25) Include Q&A as part of safety department, and how we can improve both areas.
26) Yes - SSPP Best Known Methods (BKM)s . We should compare and adopt these BKM's.
27) Long breakout sessions for New Starts.
28) Railway Worker Protection. Rail - wheel interface.
29) More on Accident Investigation as it fits within 49 CFR presently. Every transit system does the same thing but each agency differs.
30) Safety and Security Management in New Starts program.
31) Yes, terrorism (see previous comment.) More best practices and exchange of ideas.
32) Schedule 15-30 minutes for questions and answers after major topics (Hazard Management, NTSB report, etc.)
Any other comments?
1) Separate Joe Diaz entertainment hour! (joking aside, Joe did an exceptional job and has excellent presentation skills). Mike Flanigon's presentation was also exceptional and very informative.
2) Very well done. Thought more time needed for question and answers. It would be helpful to have provided materials for the purpose of review, notes and information.
3) More open forum discussion time!! Otherwise, Excellent conference!
4) No additional sessions needed on Risk Communication Training or unrelated UTC products. Find ways to get message out to DOT Heads and agency managers. Great meeting. Provides excellent opportunity to share and network with peers. Hope these are continued to keep everyone updated and aware of program activities. Continue to allow SSOA input and be receptive to ideas.
5) I find these meetings extremely valuable for me. I always learn new and better ways to do things and take away lots of ideas for program involvement! (Now I just have to implement them!)
6) Just to re-emphasize my time-management comments. The RTA's and SSO's pay to be here and it sends the wrong message when there is a lot of off-topic discussion and then no time to hear from us. That said the re-scheduled Wednesday feedback session was the right choice and very helpful.
7) I'd like more breaks and more discussion time for topics.
8) Thank you one last time for all of your work/efforts in the arranging/coordinating this event.
9) I suggest a breakout session that would allow SSO's to have open dialogue with FTA on problems or difficulties at all levels of implementation of program aspects. Possibly more one-on-one time would be helpful. I directly asked for one-on-one meeting and it never happened. Not complaining, I am just enforcing/emphasizing the point. These sessions are too long. Many of us work other responsibilities while at SSO. I suggest starting at 8:30am and go to 3:00pm. At 3pm, hold one-on-one sessions between the FTA and SSO's. It will allow Q/A inherent to the SSO and give the others an opportunity to field calls during the day. Maybe shorten to 2 1/2 days. Many people do not like discussing their issues or concerns in the open forum, but one-on-one or in small group settings may result in a more productive dialogue and feedback for FTA and the SSO. Specific comments on GSA, security and Rail Oversight. FTA should not fight to keep security. Let it go to TSA. It should fight for TSA to include "General" security oversight measures that are not terrorist related. FTA should explore an Interagency Agreement between FTA and FRA to conduct track inspections and oversight on behalf of FTA. (Resources could be provided for it. This is a side issue, but must also be addressed). The CTA was a wakeup call - now is not the time to be territorial.
10) As always, I appreciate the opportunity to participate and further enhance our partnerships. Consider fewer items on agenda and shorter hours - possible 9am - 3pm with working lunch. Most of us have on-going issues from our regular lives. The opportunity to visit other properties is invaluable.
11) I would like to see the meal breaks organized somehow to encourage more interaction. The food and service were adequate but I believe with a few changes these breaks could be a better opportunity for networking and discussion.
12) I would like to thank everyone for their hospitality, being a new member of this group, I appreciate being welcomed into the community.
13) I enjoyed this meeting and feel that I learned a lot. I look forward to attending future meetings.
14) Great conference!
15) This was my first time at this event. I found it to be very helpful in a variety of arenas; networking and rule promulgation being foremost.
16) CD/Zip drive containing presenter's visual presentations - will they be sent out afterwards?
17) Organizer should always get a room in the hotel that is large enough to have a large group meet after hours.
18) I would suggest that the FTA review all presentations for review. Limit all slides to no more than 6 lines per slide. This is a basic presentation rule.
19) The hotel and facilities were fantastic! As long as a CD is available with all the presentations on it, then no handouts was a good move. Providing lunch for everyone was great! It kept the groups together, ideas continued to flow even over lunch which took away the pressure of finding a restaurant and being back in one hour. Good job everyone. Thank you.
20) Good idea with allowing more discussion time. Many of Dr. Sauer's comments were lengthy, took up valuable time. Military Standards 882, Hazard management presentation seemed too complicated to use. Good lunch!
21) I would have liked the evaluations on the first day so we could fill out as we go.
22) Good opportunity.
23) As always - informative and thought provoking.