Chapter 1 - Introduction

The Data Tables for the 2001 National Transit Database (NTD) Report Year is one of three publications comprising the National Transit Database Program's Annual Report. It provides detailed summaries of financial and operating data submitted to the Federal Transit Administration (FTA) by the nation's mass transit agencies for the Report Year ending on or between January 1 and December 31, 2001. FTA administers the NTD Program through a professional services support contract under the guidance of FTA's Office of Oversight in the Office of Program Management. This is the 22nd Annual Report published.

Two additional publications complete the Annual Report:

1. The National Transit Summaries and Trends
2. The Transit Profiles presented in two volumes: The Top Thirty Agencies and Transit Profiles

For the 2001 Report Year, 601 transit agencies submitted data. Of that, 68 agencies received waivers from detailed reporting (Nine or Fewer Vehicles Waivers), and 2 were deleted because their report was incomplete. Thus, 534 agencies are included in the database. Agencies granted waivers are listed in Appendix B - Transit Agencies Receiving Nine or Fewer Vehicles Waivers; and deleted agencies are listed in Appendix C - Transit Agencies Deleted from 2001 Annual Publications. Appendix D lists agencies that had a mode/type of service deleted. Appendix E lists agencies by name with Appendix F listing agencies by UZA name.

49 USC 5335 requires the establishment of a uniform system of accounts and records, plus a reporting system for the collection and dissemination of public mass transportation financial and operating data by uniform categories. All applicants and direct beneficiaries of Federal assistance under 49 USC 5307 are subject to the reporting system and the uniform system of accounts and records. The NTD Reporting System assists FTA in meeting the need for information on which to base planning for public transportation services and in making public-sector investment decisions at all levels of government.

Definitions for transit terminology used in the 2001 NTD Annual Report publications may be found in the 2001 NTD Reporting Manual or on the NTD web site at www.NTDProgram.com.

Report Organization

The report consists of two chapters:

Chapter 1 Understanding and Using this Report: Provides general information to assist the reader in using this and earlier reports.

Chapter 2 The Data Tables: Financial and operating data by specific mode for individual transit agencies. Each table is described and general information is provided.

Data Tables Organization

The Data Tables in Chapter 2 are organized into four major groups:

1. Transit revenues
2. Transit expenses
3. Non-financial operating data
4. Performance indicators.

The first three groups of tables (transit revenues, expenses, and non-financial operating data) contain summaries of the data required by NTD. The fourth group displays performance indicators comprised of selected statistics derived from data in the first three groups. Typically, these indicators are computed as ratios, relating measures of input to measures of output (e.g., operating expenses per vehicle revenue hour), or measures of output to measures of service consumption (e.g., unlinked passenger trips per vehicle revenue hour).

Numbering of the tables was consistent from 1992 through 1994. Beginning in 1995, with the expansion of safety and security data, new tables were incorporated (Tables 21 through 26). Then in 1998, with the inclusion of operating expenses paid for by capital funds, Table 2 was added to accommodate Federal government sources for transit operating funds applied data. With the 1999 Report Year, data on maintenance facilities leased by transit agencies were collected and Table 16 was created.

There were no changes in the numbering of the tables in 2001. The following chart details the numbering of the 2001 Annual Report tables:

Special Notes on Reporting and the Data Tables

Several general issues pertaining to the reporting system and this Annual Report are summarized below. These summaries are to aid in interpreting and using the data published in this report.

Number of Agencies Reporting Since 1995

Alphabetical by State

Transit agencies are organized alphabetically by state. This enables easier identification of specific transit agencies for data analysis.

Transit Agency Names

Due to space limitations, transit agency names are abbreviated using 25 characters or less. Also, transit agency acronyms are used if one exists and the agency name is too long to abbreviate.

Identification Number and Organization Type

A four-digit identification number is assigned to each transit agency. The first digit of this number corresponds with the FTA Region in which the transit agency is located (FTA Regions 1 through10). FTA Region 10 is indicated with a zero (0).

Transit Agency Fiscal Year

The NTD Report Year was changed beginning with 1983 to correspond to the fiscal year of the reporting transit agency.

Database Adjustments

Financial and operating data summaries contained in this report are based on transit agency reports submitted for the current Report Year (2001). Audits or other reviews conducted after the publication date may result in minimal changes that more accurately reflect actual statistics. These changes are not available to FTA.

Mode and Vehicle Type Codes

The following mnemonic codes represented by two alphabet letters are used to describe modes and vehicle types in the tables:

Multi-UZA Reports

Some transit agencies, particularly agencies reporting commuter rail mode, provide data for transportation services serving more than one urbanized area (UZA). For NTD reporting purposes, a transit agency serving more than one UZA and filing a single report is assigned to the UZA that receives the majority of transportation service. For 49 USC 5307 apportionment purposes, relevant data are desegregated into the various component UZAs.

Purchased Transportation

Many transit agencies contract for some or all transportation services. Public agencies and/or private carriers may provide these contracted services. Contracted transportation services (called purchased transportation) are split in two categories:

1. Expenses for contract carriers where data are included in the purchasing agency's report (object class 508.01).
2. Expenses for contract carriers that file their own report (object class 508.02). Contract carriers using 100 or more vehicles to provide annual maximum service are required to file a separate report. For the 2001 Report Year, 29 reports were received from private providers operating more than 100 vehicles.

Three tables (Tables 11 through 13) identify purchased and directly operated expenses. Note that contract carriers providing 100 or more revenue vehicles in maximum service must file a separate report and are listed as directly operated services. Transportation brokerage systems under contract to public agencies and managing 100 or more vehicles in maximum service are listed as purchased transportation. This results in operating data being reported twice:

1. As an expense for the transit agency contracting with the provider(s), which is reported under object class 508.02.
2. For the individual contract operator that provides purchased transportation services under the contractual relationship.

For the 2001 Report Year, there were 139 transit agencies that acquired 100 percent of their service from purchased transportation providers, and 35 filed as directly operated reporting more that 100 vehicles. Mode- specific operating data are identified as being part of a purchased service arrangement by the letter "p" added to the mode code. Tables 11 and 27 are the only tables with this designation. Unless specified by this letter or in the table headers, data are for directly operated public transportation providers and contract operations that file a separate report.

Reporting of purchased transportation has undergone several revisions beginning with the 1984 Report Year:

1. The ability to allocate expenses from an object class, such as purchased transportation expenses, to a functional category. Thus, purchased transportation expenses could be reported by function:
   • Vehicle operations (010)
   • Vehicle maintenance (041)
   • Non-vehicle maintenance (042), and
   • General administration (160).

   Prior to 1984, reporters were required to submit all purchased transportation expenses under general administration. Between 1991 and 1995, expenses allocated to object classes 508.01 and 508.02 for purchased transportation were reported under either vehicle operations (010) or general administration (160).

2. In 1995, FTA required all agencies contracting for transportation services to fully detail their purchased transportation costs by mode, function, and object class. The reporting change also required reporting the full cost of the purchased transportation services, including all costs whose funding sources were not included in the contracts. However, many agencies experienced problems complying with the new requirements, so until 1997 FTA allowed agencies to report purchased transportation expenses under object class 508.01 as in previous years. Table 11 includes purchased transportation expenses detailed by function.
3. The 1997 reporting change provided for the inclusion of safety and security data for purchased transportation. Tables 22 through 27 show data for directly operated and purchased transportation services combined.
4. The 1998 reporting change combined fare revenues retained by the seller and fare revenues returned to the buyer into purchased transportation fare revenues (Table 1).
5. The 1999 reporting change includes the reporting of maintenance facilities leased by transit agencies (Table 16) and employee work hours for part-time employees (Table 21).

Deleted, Questionable, Waived, and Not Reported Data

A data item followed by a "Q" indicated that the data item is deemed questionable. The data affected are those where the transit agency failed to respond satisfactorily to questions raised during the validation process, and/or did not collect the data in accordance with FTA's definitions and requirements. In addition, "W" indicates that the reporting agency was granted a waiver, deleted data is indicated with a "D", and "N" indicates data that was not reported.

Data may be deleted or considered questionable by FTA when one or more of the following circumstances exist:

• A transit agency did not submit the required declarations, CEO Certification, and/or Independent Auditor Statement.
• For Title 49 USC 5307 purposes (formerly Section 9 of the Federal Transit Act, as amended), the Independent Auditor Statement declared that the data were not collected in accordance with FTA's definitions and requirements.
• Issue(s) associated with the reporter's documentation, declaration(s), and/or data were not fully resolved prior to the closure of the database.
• Required data were omitted.
• A transit agency did not provide the complete cost of directly operated service.
• A transit agency reported the identical data for 2000 and 2001.
• The reported data were considered questionable following validation.
• Required documentation for non-rail fixed guideway directional route miles was not provided.
• FTA granted a reporting waiver.

Vehicles Operated in Maximum Service

Data for vehicles operated in maximum service (VOMS) are reported by mode and type of service on the Transit System Service Form (406). VOMS is the revenue vehicle count taken during a transit agency's maximum season of the year, on the day of the week that this maximum occurs. It is not taken on a day when a special event or other extreme set of circumstances would cause the resulting tally to represent a one-time event rather than a recurring maximum service requirement. Because it does not include spare and stored vehicles, this fleet-size measure provides a more meaningful estimation of a transit agency's operating characteristics.

Vehicles for Directly Operated and Purchased Transportation Services for a Specific Mode

For tables covering directly operated service only, the specific vehicle counts provided are only for those directly operated by the transit agency, as reported on the Transit System Service Form (406) for directly operated services. Therefore, a transit agency may be grouped in a larger fleet-size category than the number of vehicles shown in a specific table.

For example, a transit agency that both directly operates 450 non-rail vehicles and purchases services involving 75 non-rail vehicles, for a total of 525 vehicles (as reported on separate Transit System Service Form(s) (406) for directly operated and for purchased transportation services), is grouped in the 500-999 vehicles operated in maximum service category. However, in a directly operated services only table this transit agency would show only 450 vehicles in the vehicles operated in maximum service column, because only 450 vehicles are directly operated. Footnotes have been added to specific tables to indicate when vehicles operated in maximum service data are derived only from directly operated services.

Multi-modal transit agencies are included in categories for the number of vehicles operated in maximum service for the combined fleet size for all modes.

Vehicles Available for Maximum Service

Data are reported on the Transit System Service Form (406). They include:

• Spares
• Out-of-service vehicles, and
• Vehicles in or awaiting maintenance.

They do not include:

• Vehicles held for sale
• Emergency contingency use, etc.

If the total active fleet for a given mode varies during the year, the reported figure represents the same time period as that used to report vehicles operated in maximum service. Thus, the difference between vehicles available for maximum service can be used to compute a transit agency's spare ratio.

Total active fleet data from the Revenue Vehicle Inventory Form (408), Table 29, has been consistent since 1984. Unlike the vehicles available for maximum service data described above, the total active fleet data in Table 29 represent only those vehicles owned by the reporting transit agency at the end of their fiscal year and are reported by vehicle type, not mode.

Completeness and Accuracy of the Data

The data submitted to FTA are subjected to extensive analysis and validation. The process includes:

• A detailed examination of each transit agency's report
• Identification of errors or questionable entries, and
• Resolution of any problems by FTA, transit agency personnel and program staff.

FTA's role is to identify and resolve questions regarding the data's accuracy and determine whether or not the data is included in the National Transit Database and the Annual Report. FTA can reject a transit agency's report if the report is not in full compliance with reporting requirements. FTA may also refuse to enter data whose reliability is questionable. FTA does not change reported data.

The quality of the database improves each year as FTA simplifies and clarifies reporting procedures, enhances the reporting software and designs more sophisticated validation checks. Data validation encompasses primarily a review of reported data for consistency and reasonableness. The limitations of these procedures, as well as the volume of data submitted, may permit some erroneous data to find their way into this report. Errors of significant magnitude have been identified and corrected, but some minor errors remain. Minor errors generally result from difficulties experienced by transit agencies in obtaining information, or from misinterpretation of certain data requirements or definitions.

Caution

With the limitations described above and keeping in mind that weather conditions, topography, contractual work rules, etc., are not reported, users of this report should not draw unwarranted conclusions when examining the data. Although comparative evaluations are appealing, analyses cannot account for apparent differences in performance. Such evaluations should encompass a more detailed examination of underlying factors (unique aspects of the transit agency's operating environment, specific management practices, or unusual events during the period covered).

Further Information on the Reporting System

The following FTA documents are available to assist the reader gain a greater understanding of NTD reporting requirements:

• National Transit Database, Uniform System of Accounts (USOA), January 1995.
• 2001 Reporting Manual
• FTA Circular 2710.1A, Sampling Procedures for Obtaining Fixed Route Bus Operating Data Required Under the Section 15 Reporting System, July 18, 1988, and FTA Circular 2710.2A, Sampling Procedures for Obtaining Demand Responsive Bus Operating Data required Under the Section 15 Reporting System, July 22, 1988. These two circulars suggest optional sampling procedures for collecting unlinked passenger trip and passenger mile data required for reports. Complete instructions and worksheets are provided for transit agencies wishing to use these procedures.
• Data User's Guide to the FTA Section 15 Reporting System, Transportation Systems Center, June 1, 1989. The User's Guide is available through McTrans Center [telephone (904) 392-0378].

These and other documents are available upon request from:

Federal Transit Administration
National Transit Database
P.O. Box 457
Merrifield, VA 22116-0457
(703) 205-2475

Industry - Government Cooperation

The National Transit Database (NTD) Reporting Program evolved from the transit industry-initiated Project FARE (Uniform Financial Accounting and Reporting Elements). Over the years, a cooperative working environment has developed between the transit industry and the Federal government regarding issues relevant to data collection and the reporting system. Private and public sectors have recognized the importance of, and need for, timely and accurate data from which to assess the continued progress of the nation's mass transportation agencies.

A Reporting System Advisory Committee was established in January 1983 to make recommendations on improving the quality and usefulness of data collected under the program. Many of these recommendations were then incorporated in the Annual Report. The Advisory Committee's charter expired on September 30, 1986.

In 2000, FTA initiated a review of the NTD program. As a result of the review and subsequent report to Congress, the National Transit Database program has undergone a substantial revamping. The revised Internet Reporting system will address many of the industry's concerns and suggestions, and is scheduled for release in September of 2002.

In its ongoing efforts to continue this cooperative effort, FTA urges all interested parties, including transit operators; state and local governments; planning organizations; trade unions; research organizations; etc, to review and critique this edition of the Data Tables and all publications comprising the Annual Report. Comments and suggestions should be forwarded to FTA at: www.fta.dot.gov, or: www.NTDProgram.com.

Data Availability

The Data Tables for Report Years 1996 through 2001 can be downloaded from FTA's web site at www.fta.dot.gov and the FTA NTD Project's web site at www.NTDProgram.com. The files are in .pdf and .xls format.

Complete databases (in both .dbf and .xls formats) going back to 1996 are also available for download at www.NTDProgram.com.

The data contained in the Annual Report are also available on disk organized by table and are compatible with PCs using Lotus 1-2-3 software. For further information on availability and associated costs, please contact:

Additionally, complete data (including data not published in this report) and data for prior Report Years, are also available from:

NTD Project
U.S. Department of Transportation
Volpe National Transportation Systems Center
DTS-49, Kendall Square
Cambridge, MA 02142
(617) 494-2259
Fax: (617) 494-3260

Chapter 2

The data in this publication have a broad range of applications. They are, however, subject to the limitations discussed in Chapter 1 relating to the need to perform a more detailed examination of underlying factors and data consistency. The statistics in Chapter 2 allow transit agencies to compare their performance more selectively; e.g., by selecting those agencies defined as being within the same peer group by virtue of climate, topography, demographic characteristics of the population served, or factors other than industry averages.

Caution

Some users of the data may tend to overstate the significance of comparisons that are based strictly on data contained in this report. Performance measures obtained using these data should be viewed strictly as tentative indicators of potential areas of improvement. If a specific indicator appears to imply below-average performance relative to industry peers, more detailed analysis is needed to reveal the factors underlying the below average value.

Chapter 2 presents a detailed performance snapshot during a particular period for 534 transit agencies. Since the majority of agencies have reported in prior Report Years, the data can also be used for time-series analyses. Such analyses can contribute to conclusions on the current and evolving conditions and problems of specific transit agencies, and the transit industry as a whole. Time-series analyses, however, must consider two important factors:

1. Beginning with the 1983 report, annual reports were published based on transit agencies' fiscal years, rather than the Federal Fiscal Year period (at that time, July 1 to June 30). See Special Notes on Reporting and this Annual Report in Chapter 1 for additional details.
2. Beginning with the 1990 Annual Report, individual transit agency statistics are reported.

Special Notes on the Desegregated Data Tables

Users of these tables should refer to Special Notes on Reporting and this Annual Report in Chapter 1 for a better understanding of the data, particularly the discussions of purchased transportation; public and private transit agency identification; vehicles operated in annual maximum service; and questionable data items, to avoid confusion. Especially when performing comparative analyses using previously published reports, users should refer to these sections as well as the discussions of individual tables in this chapter.

Reporting Changes

Through the NTD, FTA has implemented several reporting changes since 1992. The following exhibit summarizes these changes, and should be referred to when undertaking analysis involving two or more Report Years.

Transit Revenues

Tables 1 through 10 contain information on types of operating capital funds applied for individual transit agencies. Operating funds applied are reported by transit agency totals, not by individual modes. Table totals are provided for national totals, fleet size, and size of urbanized area; however, these totals vary depending on the number of transit agencies reported.

Also, for these tables the number of vehicles operated in annual maximum service includes those vehicles used for both directly operated and purchased transportation services included under the same transit agency's identification number, as reported on the Transit System Service Form (406). The only exception is Table 10 (Transit Capital Funds Applied), which details data by type of service (directly operated or purchased transportation).

The NTD uses accrual accounting to record financial data; i.e., revenues reported are those that resulted in liabilities for benefits received during the fiscal year, regardless of whether or not payment of the expenditure was made during the reporting period.

Table Descriptions

Transit revenue applied data are presented in the following tables:

Table 1: Transit Operating Funds Applied

Compiled from the Operating Funding Form (203) and reported system wide. The Operating Funding Form (203) incorporates the revenue data by describing the funding sources for operating expenditures, using revenue object classes 401 through 440 (directly generated funds), and the contribution of Federal, state, and local government funds to the operating subsidy of transit agencies. The funds reported on this form are not necessarily revenue earned during the reporting period; the funds may include revenue earned in prior reporting periods. Only funds expended (applied) are reported.

The object classes for fare revenue retained by seller and fare revenues returned to the buyer were replaced with purchased transportation fare revenues in 1999. This object class includes all fare revenues generated by purchased transportation contracts, regardless of whether they were retained by the seller or returned to the buyer.

As of 1991, object class 402 (special transit fares) was included with object class 401 (passenger fares).

The column labeled Directly Generated Funds, Other Revenues includes various revenue object classes, including:

• 403 (school bus service funds)
• 404 (freight tariffs)
• 405 (charter service funds), and
• 406 (auxiliary transportation funds) and revenues accrued through a purchased transportation agreement.

It also includes contract expenditures incurred net of purchased transportation revenues.

Under Directly Generated Funds, the data in the column Dedicated and Other includes:

• Funds dedicated to transit at their source (income, sales, property, gasoline, and
• Other levied taxes as well as bridge, tunnel, and highway tolls). These are fees the transit agency has the legal authority to impose.

The Other Federal Public Funds column details operating funding from sources including:

• Planning Program, 49 USC 5303
• Research, Development, Demonstration and Training Program, 49 USC 5312, and
• Non-urbanized Area Formula Program, 49 USC 5311.

Other changes instituted, beginning with the 1993 Data Tables, affected the public funds subcategories for state and local funds.

1. For state funds, General Revenue was inserted in place of Grants and Reimbursements. However, object class 411 was used for both.
2. Under State Funds, the Dedicated and Other column was changed from Fare Assistance in 1992. Despite the change, both contain object class 412 (state special fare assistance).
3. Under Local Funds, General Revenue replaced Grants and Reimbursements and continued to report object class 409 (local cash grants and reimbursements).
4. Under Local Funds, the Dedicated and Other column changed from Fare Assistance; it continued to report object class 410 (local special fare assistance).

The aggregation of operating funds applied does not include private providers under contract to public agencies if the funds are reported by both entities. This avoids double counting of operating funds applied.

View Table 1 .html      View Table 1 .pdf

Table 2: Federal Government Sources for Transit Operating Funds Applied

This table provides a breakdown of Federal operating assistance funds by those attributable to urbanized area operating assistance funds and urbanized area capital assistance funds used in operations. Prior to 1999, capitalized operating funds were reported under Capital Funding Applied (Table 6 in 1998).

View Table 2 .html      View Table 2 .pdf

Tables 3 and 4: State Taxes Dedicated at Their Source for Transit Operating Funds Applied Local Taxes Dedicated at Their Source for Transit Operating Funds Applied

Tables 3 and 4 are compiled from the Operating Funding Form (203) and state and local taxes, respectively, applied to transit operations. Operating funding from dedicated taxes are desegregated by type of tax (income, sales, property, gasoline, or other). The Other Taxes column includes any other special state or local taxes dedicated at their source to transit operating funding such as payroll and utility taxes.

View Table 3 .html      View Table 3 .pdf
View Table 4 .html      View Table 4 .pdf

Table 5: Directly Generated Taxes Dedicated at Their Source for Transit Operating Funds Applied

Table 5 is compiled from the Operating Funding Form (203). This table provides a breakdown of directly generated dedicated taxes, by income, sales, property, gasoline, and other, applied to transit operations.

View Table 5 .html      View Table 5 .pdf

Table 6: Transit Capital Funds Applied

Data were compiled from the Capital Funding Form (103). Federal sources of assistance are classified either as funds provided under 49 USC 5309, 49 USC 5307, or from other sources. State and local sources are divided into General Revenue and Dedicated. Dedicated sources restrict funds to transportation-related expenditures, while transit must compete with other public programs for general revenues. Dedicated sources of funds are desegregated into taxes (income, sales, etc.) and other (bridges, tunnels, state and local bonds, investment income, etc.).

A reporting change introduced in 1998 required agencies to report capitalized operating funds on the Operating Funding Form (203) and these data are included in Tables 1 and 2. In 1996 this table was changed to include capital data by type of service (TOS), which can be directly operated (DO) or purchased transportation (PT). See Special Notes in Chapter 1 for more details on purchased transportation and directly operated types of services. In 1991, a column was included for transit agency funds dedicated at their source. Transit agency funds do not include fare revenues. Transit Agency Funds was changed to Directly Generated Funds in 1992.

View Table 6 .html      View Table 6 .pdf

Tables 7 and 8: State Taxes Dedicated at Their Source for Transit Capital Funds Applied Local Taxes Dedicated at Their Source for Transit Capital Funds Applied

Tables 7 and 8 are compiled from the Capital Funding Form (103). Both tables were changed in 1996 to include capital data by type of service. These two tables further desegregate the state and local tax revenue applied for public transit capital that was shown in Table 6.

View Table 7 .html      View Table 7 .pdf
View Table 8 .html      View Table 8 .pdf

Table 9: Directly Generated Taxes Dedicated at Their Source for Transit Capital Funds Applied

Data are compiled from the Capital Funding Form (103). Collection of these data is a new reporting requirement. Table 9 provides a breakdown of directly generated dedicated taxes by income, sales, property, gasoline, and other applied for transit capital. This table has included capital data by type of service since 1996.

View Table 9 .html      View Table 9 .pdf

Table 10: Capital Funds Applied by Type of Expenditure

Data are compiled from the Capital Funding Form (103). Table 10 provides a breakdown of the capital funds applied and how they were used. Mode and type of service for three primary categories provide data: rolling stock, facilities, and other. Aggregate totals for each mode and type of service reported by a transit agency are also provided. This table has included capital data by type of service since 1996.

View Table 10 .html      View Table 10 .pdf

Potential Data Applications

Tables 1 through 10 summarize the magnitude and source of transit funds applied for individual transit agencies. The data in these tables permit analyses of the extent to which specific agencies recover operating expenses from fares, as well as the extent to which they rely on various sources of directly generated, local, state, and/or Federal assistance to apply to their operation.

Transit agencies can use these data to compare the types of funds applied and the percentage distributions of their sources to those of other agencies. In general, the data permit cross-sectional and time-series analyses, but more specifically they allow analysts to examine individual agencies and to custom-define peer groups. For example, peer groups could be formed based on mode, fleet size, annual operating expenses, or other factors not contained in this report, such as climate and collective bargaining agreements. Comparisons can then be made to the individual transit agencies in the group averages.

Operating Expenses are reported using accrual accounting and reported in the year they were incurred. This is the year in which they result in liabilities for benefits received, regardless of whether payment is made during the reporting period.

Tables 11 through 14 contain information on the types and amounts of expenses incurred by individual transit agencies. Transit expenses are reported by function and by object class. The number of vehicles operated in annual maximum service includes those vehicles used for both directly operated (DO) and purchased transportation (PT) services included under the same transit agency's identification number, as reported on the Transit System Service Form (406).

Functional classes divide operating expenses into four major categories or functions:

1. Vehicle operations (VO),
2. Vehicle maintenance (VM),
3. Non-vehicle maintenance (NM), and
4. General administration (GA).

Analysis of expenses by function must be qualified by the degree to which transit agencies uniformly allocate expenses among these categories. This analysis should include careful consideration of reporting limitations as well as detailed accounting practices at the specific transit agencies examined.

Expenses by function are reported for both DO and PT services beginning in 1997.

Object classes divide operating expenses into categories such as labor, fringe benefits, services, and materials and supplies, among others.

While revenue data are summarized for all modes operated by a transit agency, the expense data are desegregated by mode. Multi-modal transit agencies were required to fully allocate expenses to the appropriate modes for each of the various functional categories in 1999.

The operating expenses summarized in these tables exclude reconciling items, e.g.:

• Interest expenses
• Leases and rentals, and
• Depreciation.

Reconciling items are reported only as agency totals and are not desegregated by mode or functional class. Reconciling items are required to provide an overall total that is consistent with the total operating funding applied (Tables 1 through 5) and with published reports. These expenses are reported separately because local accounting practices for handling such items (particularly depreciation and amortization) differ widely. Generally, analysts using these data exclude reconciling items from operating expenses. Although this actually understates true operating costs, it resolves the problems inherent with inconsistent treatment of reconciling items.

Table Descriptions

Transit expense data for individual transit agencies are summarized in the following tables:

Table 11: Transit Operating Expenses by Mode and Function

Compiled from the Operating Expenses Form (301), for each reported mode.

Purchased transportation filing a separate report (object class 508.02) was reported by function in 2001. Purchased transportation expenses include both purchased transportation in report (object class 508.01) and purchased transportation filing a separate report (object class 508.02). Because expenses for object class 508.02 are separated by both the buyer and seller(s), the summary for tables excludes this object class to prevent double counting.

These expenses were collapsed under the column Purchased Transportation In Report prior to 1997.

Object classes 508.01 and 508.02 reflect the full cost of purchased transportation services except in cases where part of the funding for the purchased service is provided by the seller(s). Object classes 508.01 and 508.02 include:

• Contract expenditures by the buyer (net of purchased transportation fare revenues)
• Purchased transportation fare revenues
• Other costs incurred by the buyer such as contract administration, marketing, etc.

In cases of purchased transportation involving 100 or more vehicles operated in annual maximum service, expense data are reported twice:

1. By the contracting agencies (buyer) as a purchased transportation expense (under object class 508.02), and
2. By the contract provider (seller), by function and object class, if the seller is not a brokerage system.

Brokers report separately if the purchased transportation agreements involve more than 100 vehicles operated in maximum service, but their expenses are lumped under object class 508.01 and are detailed by function.

In general, expenses reported under object class 508.02 are greater than expenses reported by the seller(s) due to contract costs incurred by the buyer as well as profit made off the transaction by the seller(s).

The summarization of operating expenses by UZA size, mode, and vehicle group totals is calculated by totaling all columns, except object class 508.02. This is to avoid double counting of data when operating expenses are aggregated.

View Table 11 .html      View Table 11 .pdf

Table 12: Transit Operating Expenses by Mode and Object Class

Compiled from the same forms as Table 11. Object class categories correspond to those reported on the Operating Expenses Form (301).

501.01 Operators' salaries and wages
501.02 Other salaries and wages
502 Fringe benefits
503 Services
504.01 Fuel and lubricants
504.02 Tires and tubes
504.99 Other materials and supplies
505 Utilities
506 Casualty and liability costs
508.01 Purchased transportation (in report)
508.02 Purchased transportation (filing separate report)

In addition, 507 (Taxes) and 509 (Miscellaneous expenses) are included as Other. A separate column showing 510 (Expense transfers) is included in this table. Until 1995 expense transfers were included as other expenses. Double counting of operating expenses exists in this table for a limited number of transit agencies (See discussion about object classes 508.01 and 508.02 above for Table 11). The summarization of operating expenses by UZA size, by mode, and vehicle group totals is calculated by summing all columns except purchased transportation filing a separate report (object class 508.02). This is to avoid double counting of data when operating expenses are aggregated.

View Table 12 .html      View Table 12 .pdf

Table 13: Transit Operating Expenses by Function and Object Class - Bus Only Agencies

For the 2001 Report Year, 84 transit agencies operated only bus service this represents 15.1 percent of all transit agencies reporting to the NTD. Of these, 20 received a reporting waiver. Data are cross-classified by major functional and object classes as per Table 12).

The summarization of operating expenses by UZA size, by mode, and vehicle group totals is calculated by totaling all columns except object class 508.02. This is to avoid double counting of data when operating expenses are aggregated.

The total number of buses operated in annual maximum service includes those buses used for both directly operated services (DO) and for purchased transportation (PT) services. The totals are included under the same transit agency's identification number as reported on the Transit System Service Form (406) by type of service for the bus mode.

View Table 13 .html      View Table 13 .pdf

Table 14: Employer-Paid Fringe Benefits

Data are derived from the Fringe Benefits Form (331). The information presented represents agency totals because categories of fringe benefits payments are not reported by mode. This form is not required for transit agencies with 100 or fewer vehicles operated in annual maximum service.

View Table 14 .html      View Table 14 .pdf

Potential Data Applications

The expense tables summarize the costs of operating individual transit agencies. Data are desegregated into mode, function, and object classes. These data can be used to compare costs among various transit agencies and to determine potential areas for improvement. As discussed in Chapter 1, such analysis should incorporate careful examination of all causal factors underlying these differences. This examination can require information beyond that which is obtainable from this reporting system.

Tables 15 through 29 contain non-financial operating data for individual transit agencies. With the exception of Tables 16 and 22 through 27, all the tables include data for directly operated services only.

Transit Maintenance, Safety, and Security

Table 15 summarizes the number of revenue system failures. Analyzing data from this table generally requires additional data, such as vehicle miles. A reporting change was initiated in 2001 with the inclusion of system failures for major and minor mechanical reasons that prevent the revenue vehicles from completing their trips.

Major mechanical failure is defined the same as the previous definition of interruptions for mechanical reasons (1997 and prior years). Such failures require assistance from someone other than the revenue vehicle operator(s) to restore the vehicle to an operating condition, and they prevent the vehicle from continuing in revenue service. Major system failures include malfunctions in:

• Brakes
• Doors
• Engine cooling systems
• Steering and front axle
• Rear axle and suspension
• Torque converters
• Similar major mechanical items.

Minor mechanical failures in general do not usually prevent the vehicle from continuing in revenue service. However, the minor system failures reported to the NTD in 2001 were those that prevented the revenue vehicle(s) from completing their trips, either due to internal policies of agencies or due to minor mechanical mishaps that prevented trip completion. Minor system failures are the same as interruptions due to other reasons (1997 and prior years) and include:

• Fareboxes
• Wheelchair lifts
• Air conditioning systems
• Similar minor mechanical items.

System failure figures should be viewed as gross indicators. Analysis of system failures as measures of maintenance performance should be undertaken with caution, requiring detailed examination of how system failures were defined and the individual agencies' policies for taking vehicles out of service. Application of data over time is also relevant in determining trends and conducting further analysis.

Table 16 summarizes transit facilities based on the number of vehicles assigned to the facility. In addition, two classifications of facilities are defined for general-purpose use and heavy maintenance work.

• A general-purpose facility is the most commonly reported facility, because it provides running repairs, servicing, and vehicle storage as well as component repair and overhaul.
• A heavy maintenance facility is one wholly dedicated to component repair and overhaul, and usually only the larger transit agencies have such a facility.

The number of vehicles assigned to a facility will vary depending on its size (capacity) and the number of modes operated by the agency. Also, unique geographical features and/or constraints that may make it more economical to operate more than one facility to support a small fleet of vehicles may result in a greater number of facilities being reported for the transit fleet than would normally be required. Many transit agencies are operating multi-modal service (e.g., bus and demand response systems), and in such cases the facility is required to be allocated among the modes using the facility.

For example, if a transit agency reports 100 total vehicles, of which 70 are buses and 30 were demand response, it would allocate the facility as .7 for bus and .3 for demand response. When relatively small transit agencies report multiple facilities, one needs to consider some of the factors mentioned above and whether or not a proper allocation was performed.

Transit safety and security data are compiled from the Transit Safety and Security Form (405). Reporting requirements for safety data were expanded in 1995 with the addition of fatalities and injuries for patrons, employees, and others for each safety item, such as collisions and non-collisions (derailments, personal casualties and fires). Additionally, new items for personal casualties were added.

Reporting requirements were expanded in 1997 with the inclusion of safety and security data for purchased transportation. Reporting of security data commenced with the 1995 Report Year, with only agencies serving urbanized areas (UZAs) with greater-than 200,000 populations required to report. Data are reported by mode and summarized using the FBI Uniform Crime Reporting (UCR) Program criteria. The definitions used in Form 405 are from the FBI Uniform Crime Reporting Handbook, 1984.

Transit Way Mileage

Directional route miles are reported on the Transit Way Mileage Form (403) and presented in Tables 18 through 20. The term directional route miles is defined as:

• The mileage in each direction over routes that public transportation vehicles travel while in revenue service.

Directional route miles are a measure of the facility or roadway, not the amount or frequency of service carried on the facility; i.e., number of routes or vehicle revenue miles. They are determined by direction of service, but not by the number of traffic lanes or rail tracks existing in a given right-of-way.

If vehicles travel in only one direction within a right-of-way, each mile is counted once. If vehicles travel in both directions, each mile is counted twice. A mile of single track over which commuter rail service operates in both directions represents two directional route miles.

The number of routes along the measured distance does not influence directional mileage; e.g., a mile of exclusive busway on which a transit agency operates six different routes in only a single direction represents one directional mile.

Tables 18 through 20 contain data for directly operated service only, as their titles indicate. Other annual publications (Transit Profiles, National Transit Summaries and Trends) report directional route miles for both directly operated and purchased transportation modes.

Service Supplied and Service Consumed Data

Service supplied data include vehicle miles, vehicle revenue miles, vehicle hours, and vehicle revenue hours. Transit agencies were asked to report both their scheduled and actual vehicle revenue miles of service in 1984. The purpose of adding scheduled vehicle revenue miles of service is to allow a transit agency to indicate whether it may have more or less service than was originally scheduled or planned. The difference between vehicle miles and vehicle revenue miles represents deadheading. Definitions of the above data terms can be found in the Reporting Manual Glossary.

Service consumed data refer to ridership information (measures of use of the service supplied) and include unlinked passenger trips and passenger miles.

Passenger mile data are normally collected through sampling because it is usually not part of a transit agency's routine operations and is among the most difficult to collect. While FTA has developed several such techniques, transit agencies were allowed to use self-certifying sampling techniques beginning with the 1990 Report Year. Regardless of the sampling technique used, it must satisfy precision and confidence level requirements of 10 percent and 95 percent, respectively.

Service supplied and service consumed data are reported on the Transit System Service Form (406); data are reported in terms of average weekday, average Saturday, and average Sunday.

Table Descriptions

Non-financial operating data are provided in the following tables. For multi-modal agencies, data are desegregated by individual modes.

Table 15: Revenue Vehicle Maintenance Performance

Data are compiled from the Revenue Vehicle Maintenance Performance and Energy Consumption Form (402). The number of vehicles operated in annual maximum service are those vehicles used for directly operated services only, as reported on the Transit System Service Form (406).

View Table 15 .html      View Table 15 .pdf

Table 16: Maintenance Facilities

Data are compiled from the Revenue Vehicle Maintenance Performance and Energy Consumption Form (402). The number of vehicles operated in annual maximum service represents those vehicles used for directly operated and purchased transportation services.

This table includes data for maintenance facilities owned and leased by transit agencies. Prior to 1999, only maintenance facilities owned by transit agencies were reported.

View Table 16 .html      View Table 16 .pdf

Table 17: Energy Consumption

Data for this table are compiled from the Revenue Vehicle Maintenance Performance and Energy Consumption Form (402). The number of vehicles operated in annual maximum service is those vehicles used for directly operated services only, as reported on the Transit System Service Form (406).

The table was expanded in 1995 with the inclusion of kerosene and grain additive fuel. However, only 3 agencies reported these fuel types in 2001; therefore, they were collapsed under Other Fuel. Fuel types reported are for revenue vehicles only.

View Table 17 .html      View Table 17 .pdf

Table 18: Transit Way Mileage: Details by Transit Agency Directly Operated Service for Non-Rail Modes,
Table 19: Transit Way Mileage: Details by Transit Agency Directly Operated Service for Ferryboat Modes, and
Table 20: Transit Way Mileage: Details by Transit Agency Directly Operated Service for Rail Modes,

Data are compiled from the Transit Way Mileage Form (403), directly operated service only. For an explanation of directional route miles, see the above section on transit way mileage.

Tables 18 through 20 display transit way mileage in three separate groups:

1. Non-rail
2. Ferryboats, and
3. Rail.

This separation provides for easier comparison of like modes and reduces the number of unnecessary blank entries. By law, all directional route mileage for ferryboat and trolleybus modes is classified as exclusive for reporting purposes.

View Table 18 .html      View Table 18 .pdf
View Table 19 .html      View Table 19 .pdf
View Table 20 .html      View Table 20 .pdf

Table 21: Transit Agency Employee Work Hours and Person Count

Employee work hours were broken down into full-time and part-time employee categories in 1999. Prior to that time only total work hours were reported. A mode followed a lower-case "f" indicates full-time employees, while a lower-case "p" indicates part-time employees.

Data are compiled from the Transit System Employee Form (404) and are collected for both employee work hours and an actual person count at fiscal-year end. Fractional entries for actual person counts result when employees work for more than one function, mode, or type of service. In those instances the actual person count is prorated among labor classifications and modes by type of service. When working on capital projects, an employee's labor is considered a capital expense; otherwise, it is an operating expense.

Some care is required for analyses of the data presented in this table. Work hours cover the entire Report Year, whereas person counts are based on those employed on the last day of the Report Year. This may distort the annual average number of hours per employee.

While many transit modes are labor intensive, others are not. Due to the unique characteristics of their operations, some modes such as vanpool do not always provide complete employee-related data. Another reporting anomaly sometimes occurs when transit agencies providing directly operated service use contracted services for a portion of the service provision. In these situations, labor is either not reported for an activity (e.g., vehicle maintenance) or only reported for the labor that is engaged in activities associated with the contract services. As a result, labor is understated and, when reported within a directly operated report, can create misleading information. Examples of how this occurs include:

• Transit agencies acquiring operating labor through a purchased transportation arrangement.
• Maintenance services performed by another municipal entity like a public works department.
• Specific management services performed by a management services company.

When zero and/or low values are reported within a directly operated report, caution should be exercised in the use of employee-related data.

Transit Safety

Data are compiled from the Transit Safety and Security Form (405). Reporting requirements for safety data were expanded in 1995 with the addition of fatalities and injuries to patrons, employees, and others for each safety item, such as collisions and non-collisions (derailments, personal casualties and fires). New items were also added for personal casualties.

Reporting safety and security data for purchased transportation became mandatory in 1997.

New data requirements frequently result in some data anomalies due to reporting misunderstandings and incorrect applications by transit agencies. The data can also be impacted by agencies requesting data waivers.

Safety data are presented in Tables 22 through 24. In each table, the number of vehicles operated in annual maximum service represents those vehicles used for both directly operated (DO) and purchased transportation (PT) services, as reported on the Transit Agency Service Form (406).

View Table 21 .html      View Table 21 .pdf

Table 22: Transit Safety: Number of Incidents - Collisions, Non-Collisions, and Total Property Damage

This table includes data related to incidents and total transit property damage. An incident is defined as an unforeseen occurrence that results in collision, derailment, personal casualty, non-arson fire, or property damage exceeding $1,000 associated with transit agency revenue vehicles, maintenance areas, and rights-of-way. Incidents are divided into two main categories:

1. Collisions, the total number of incidents involving collisions with other vehicles, objects, and people is presented in addition to the total number of collisions at grade crossings, as well as attempted/successful suicides.
2. Non-Collisions, the incidents related to derailments, personal casualties, and non-arson fires.

   View Table 22 .html      View Table 22 .pdf

Table 23: Transit Safety: Number of Fatalities - Collisions and Non-Collisions

This table presents fatalities related to collisions and non-collisions. A fatality is defined as:

• A death confirmed within 30 days after an incident that occurs.

Reported under Collision, Derailment, Personal Casualty, or Non-Arson Fires.

In this table, for each category of collisions and non-collisions, the number of fatalities involving patrons and non-patrons (employees and others) is presented.

View Table 23 .html      View Table 23 .pdf

Table 24: Transit Safety: Number of Injuries - Collisions and Non-Collisions

This table presents injuries related to collisions and non-collisions as in the previous table. Injury is defined as:

• Any physical damage or harm to a person requiring medical treatment, or any physical damage or harm to a person reported at the time and place of occurrence.

For each category of Collisions and Non-Collisions, the number of injuries involving patrons and non-patrons (employees and others) is presented.

View Table 24 .html      View Table 24 .pdf

Transit Security

Data are compiled from the Transit Safety and Security Form (405). Only agencies serving urbanized areas (UZAs) in excess of 200,000 population must report on transit security data. The reporting of security data commenced in the 1995 Report Year.

Data are reported by mode and type of service and summarized according to the FBI Uniform Crime Reporting (UCR) Program criteria. The definitions below are taken from the FBI Uniform Crime Reporting Handbook, 1984. Data for transit security are divided into two categories:

1. Part I - Offenses (Reports). This category includes serious crimes against persons, such as homicide, forcible rape, robbery, and aggravated assault. These offenses are reported based on records of calls for assistance, complaints, and/or investigations. Part I also includes crimes against property, such as larceny/theft, motor vehicle theft, burglary, and arson.
2. Part II - Offenses (Arrests). This category involves less serious crimes, and offenses are reported based on arrests made. For each crime, data are presented by mode and type of service.

Security data are presented in Tables 25 through 27. In each table, the number of vehicles operated in annual maximum service represents those vehicles used for both directly operated (DO) and purchased transportation (PT) services, as reported on the Transit Agency Service Form (406).

Table 25: Transit Security: Part I - Offenses (Reports) Violent Crime

Table 25 presents data for violent crime (crimes against persons). For each reported crime, the total (in vehicle plus in station plus other transit property) for patrons, employees, and others is included. The data are presented by mode and type of service for transit agencies serving UZAs in excess of 200,000 population.

View Table 25 .html      View Table 25 .pdf

Table 26: Transit Security: Part I - Offenses (Reports) Property Crime

Table 26 presents data for property crime. As in Table 24, for each reported crime the total number of reports for patrons, employees, and others is included. The data are presented by mode and type of service for transit agencies serving UZAs in excess of 200,000 population.

View Table 26 .html      View Table 26 .pdf

Table 27: Transit Security: Part II - Offenses (Arrests) and Transit Property Damage

Table 27 presents data for less serious crimes and are reported based on arrests made. Data are presented by mode and type of service. Additionally, the total transit property damage is included.

View Table 27 .html      View Table 27 .pdf

Transit Service

Table 28: Transit Operating Statistics: Service Supplied and Service Consumed

This table summarizes transit agency service supplied and service consumed data. Data are compiled from the Transit System Service Form (406) for directly operated (DO) and purchased transportation (PT) service.

Vehicles available for maximum service represent the total annual active service fleet and include:

• Spares
• Out of service vehicles, and
• Vehicles in or awaiting maintenance.

They do not include vehicles being held for sale, emergency contingency use, etc.

If the total active fleet for a given mode varies during the year, the reported figure represents the same time period as that used to report vehicles operated in maximum service. Thus, the difference between vehicles available for annual maximum service and vehicles operated in annual maximum service can be used to compute a transit agency's spare ratio. See Chapter 1 for further details on vehicle data.

With regards to demand response (DR), jitney (JT), publico (PB), and vanpool (VP) modes, data for the column Annual Scheduled Vehicle Revenue Miles have been zeroed. By definition, these modes do not have scheduled service.

View Table 28 .html      View Table 28 .pdf

Vehicle Inventory

Table 29: Age Distribution of Active Revenue Vehicle Inventory

Data are compiled from the Revenue Vehicle Inventory Form (408) for directly operated services only. Vehicle Type and Active Vehicles by Age Grouping show data in the total active fleets. Vehicle type codes are listed in Chapter 1. The age of a vehicle is considered to be the number of years since its date of manufacture.

The National Transit Database reporting system is based on a transit agency's fiscal year. Over 60 percent of all transit agencies reporting complete their respective fiscal year before the end of a calendar year. As a result, a revenue vehicle manufactured, delivered, tested, and accepted by a transit agency after the fiscal-year end but within the calendar or manufacturer year will not be reported until the next Report Year.

View Table 29 .html      View Table 29 .pdf

Potential Data Applications

The data presented in Tables 15 through 29 can be used to help answer questions regarding service provided by individual transit agencies relative to the investment required. For example, how many employees, how much fuel, and how many vehicles were required to provide that service; how safe was that service; and how much use was made of the service by transit patrons.

Data are derived using the Operating Expenses Form (301), the Revenue Vehicle Maintenance and Energy Form (402), the Transit Way Mileage Form (403), the Transit System Employee Form (404), the Transit Safety Form (405), and the Transit System Service Form (406).

Tables 30 through 33 are comprised of data for directly operated service (DO) only and from selected performance indicators for individual transit agencies. These indicators are not reported directly, but are computed from other reported data. Usually, these relate measures of service outputs to measures of resource inputs such as vehicle revenue miles per operating expense, and service outputs to service consumption such as vehicle revenue miles per unlinked passenger trip. Performance measures are computed separately for each mode, and therefore should utilize only data items reported on a modal basis (revenues and reconciling expenses are excluded).

Many performance indicators can be computed from these data and other sources. Users should note the limitations relating to analyzing any performance indicators, and carefully examine underlying or causal factors in greater detail. Added to these limitations are data waivers granted to reporters due to reporting burden, initial report submission, unique circumstances, and other factors. The combinations of these limiting factors may compound interpretation and use of individual performance indicators for a particular mode and type of service.

Potential for distortion exists if only one or two performance indicators are viewed in isolation. For example, the single measure operating expense per unlinked passenger trip might be misleading for a transit agency with a disproportionately high number of transfers (caused, for example, by geographical or routing constraints).

In addition, users of these performance indicator data are advised that similar performance indicators derived from other 2001 publications may contain different values when comparisons between reports are made. This is applicable in cases where a ratio is computed using purchased transportation data, while the performance indicators presented in the publication are for directly operated service only.

Table Descriptions

Table 30: Details by Transit Agency Directly Operated Service - Service Supplied Ratios

Table 30 includes ratios that relate variables of service supplied such as vehicle revenue miles and hours. It also presents data on peak-to-base ratio, with the inclusion of peak- and base-period vehicles.

View Table 30 .html      View Table 30 .pdf

Table 31: Details by Transit Agency Directly Operated Service - Cost Efficiency and Cost Effectiveness

Table 31 includes ratios related to cost efficiency (the link between service inputs and service outputs), such as operation expense per revenue hour and operating expense per vehicles operated in maximum service. It also includes ratios related to cost effectiveness (the link between service inputs to service consumption), such as operating expense per unlinked passenger trip and operating expense per passenger mile.

View Table 31 .html      View Table 31 .pdf

Table 32: Details by Transit Agency Directly Operated Service - Service Consumption per Service Output Ratios and Miles per Vehicle Maintenance Expense

Table 32 measures service effectiveness (the link between service outputs and service consumption). It presents ratios such as unlinked passenger trips per vehicle revenue mile and passenger miles per vehicle revenue hour.

View Table 32 .html      View Table 32 .pdf

Table 33: Details by Transit Agency Directly Operated Service - Employee Work Hour per Vehicles Operated in Maximum Service

Table 33 presents ratios of employee work hours by function per vehicles operated in maximum service. The table serves as a measure of service efficiency.

View Table 33 .html      View Table 33 .pdf

All documents are provided in PDF, PPT and MS Excel format need to download Readers or Viewers to view.