| Monthly Ridership Reporting Introduction What
is the National Transit Database Internet Reporting — Monthly Ridership Reporting Overview NTD Monthly Ridership Reporting Mode
Service Operated form (MR-10) Ridership
Activity form (MR-20) List of Examples Example
1 — Continuing Requirements List of Exhibits Exhibit
1 — FY 2007 Reporting Changes and Highlights | Viewing
the 2007 Monthly Ridership Reporting Manual in PDF Format Downloading
Instructions Printing
Instructions .pdf
2007 Monthly Ridership Reporting Manual Acrobat
Reader is required to view the PDF files. |
This section provides an overview of the National Transit Database (NTD) Monthly Ridership reporting requirements, including the following:
This section provides the legislative basis for the NTD reporting system.
This section summarizes the changes in reporting requirements implemented in FY 2007.
This section provides answers to basic reporting questions.
This section presents key definitions as well as reference resources and publications for further detail on issues related to reporting.
The National Transit Database (NTD) is the Federal Transit Administration's (FTA's) primary national database for statistics on the transit industry. Recipients of FTA’s Urbanized Area Formula Program (Section 5307) and Nonurbanized Area Formula Program (Section 5311) grants are required by statute to submit data to the NTD. Over 650 transit agencies and authorities file annual reports to FTA through the internet-based reporting system. Each year, NTD performance data are used to apportion over $4 billion of FTA funds to transit agencies in urbanized areas (UZAs). Annual NTD reports are submitted to Congress summarizing transit service and safety data.
The NTD is the system through which FTA collects uniform data needed by the Secretary of Transportation to administer department programs. The data consist of selected financial and operating data that describe public transportation characteristics. The legislative requirement for the NTD is found in Title 49 U.S.C. 5335(a):
SECTION 5335. NATIONAL TRANSIT DATABASE.
(a) NATIONAL TRANSIT DATABASE To help meet the needs of individual public transportation systems, the United States Government, State and local governments, and the public for information on which to base public transportation service planning, the Secretary of Transportation shall maintain a reporting system, using uniform categories, to accumulate public transportation financial and operating information and using a uniform system of accounts. The reporting and uniform systems shall contain appropriate information to help any level of government make a public sector investment decision. The Secretary may request and receive appropriate information from any source.
(b) REPORTING AND UNIFORM SYSTEMS The Secretary may award a grant under Section 5307 or 5311 only if the applicant, and any person that will receive benefits directly from the grant, are subject to the reporting and uniform systems.
The NTD reporting system evolved from the transit industry initiated Project FARE (Uniform Financial Accounting and Reporting Elements). Both the private and public sectors have recognized the importance of timely and accurate data in assessing the continued progress of the nation's public transportation systems.
Funding for Agencies Serving Urbanized Areas under 200,000 Population
The NTD data are also used in the formula allocations of Federal transit funds. Prior to the Safe, Accountable, Flexible, and Efficient Transportation Equity Act: A Legacy for Users (SAFETEA-LU), only NTD data for urbanized areas with populations of 200,000 or more were used. With the passage of SAFETEA-LU, NTD data for urbanized areas with fewer than 200,000 population are also used in the allocation of Federal transit funding.
SAFETEA–LU directed that there be a one percent takedown from the funds made available under Section 5307. This takedown amount will be for apportionment under the new Small Transit Intensive Cities (STIC) formula. Under the formula for STIC, funds are apportioned to UZAs with a population less than 200,000 that meet or exceed the average level of service for all UZAs with populations between 200,000 and 1,000,000.
SAFETEA–LU also establishes new Growing States and High Density States formula factors (Section 5340) to distribute funds to the section 5307 and section 5311 programs. One-half of the funds are made available under the Growing States factors and are apportioned by a formula based on State population forecasts for 15 years beyond the most recent Census. Amounts apportioned for each State are then distributed between UZAs and nonurbanzied areas based on the ratio of urbanized / nonurbanzied population within each State. The High Density States factors distribute the other half of the funds to States with population densities in excess of 370 persons per square mile. These funds are apportioned only to UZAs within those States.
For more information on SAFETEA-LU, contact your regional administrator or go to www.fta.dot.gov.
In its ongoing efforts to improve upon the NTD Internet Reporting system and to be responsive to the needs of the transit agencies reporting to NTD and the transit community, FTA continues to refine and clarify reporting requirements and Internet Reporting.
Reporting changes for the 2007 NTD are highlighted below. Specific changes are discussed in detail in the applicable sections of this manual.
The following describes changes by reporting form.
Transit agencies that receive or benefit from Urbanized Area Formula Program (UAF) funds must submit or coordinate the submittal of the Monthly Ridership report. These transit agencies or organizations are generally referred to as recipients or beneficiaries.
Transit agencies that are recipients or beneficiaries of FTA Urbanized Area Formula Program (UAF) funds and that manage transit activities must submit the NTD report, regardless of whether they directly operate (DO) or purchase (PT) their transit services. These recipients or beneficiaries can be public entities directly operating services or contracting for all or part of the total transit service provided. The transit agency must report all of the service they provide or purchase, excluding services provided under demonstration grants or test projects funded through the Congestion Mitigation and Air Quality (CMAQ) program or other funds transferred into the Urbanized Area Formula Program (UAF). The following are typical NTD reporters and requirements for recipients and beneficiaries of Urbanized Area Formula Program (UAF) funds.
Public transit agencies must submit a NTD report through the life of the grant and / or the life of the capital equipment obtained through the grant (continuing requirements). If a transit agency does not spend funds from the grant for either capital expenses or operating assistance for the year, the transit agency must still file a NTD report if the grant is still active or capital equipment still has remaining useful life.
Private carriers operating purchased transportation (PT) services that provide public transportation services under contract to recipients or beneficiaries of Urbanized Area Formula Program (UAF) funds must report data to the public transit agency for inclusion in the public transit agency's NTD Annual report. These private providers must supply the purchased transportation data to the buyer for inclusion in the buyer’s report and will no longer submit a separate NTD Annual report for that data. The data pertain only to the services under contract. This applies to almost all private providers.
Contractual agreements between public NTD reporting agencies for purchased transportation (PT) services can either be reported by the seller or buyer of service as directly operated (DO) service. Therefore, when a public agency is the buyer of service and is reporting purchased transportation (PT) service on behalf of the pubic agency which is selling service, the seller must supply the data to the buyer so that it is reported in the buyer’s report as directly operated (DO) service. Additionally, when the seller is reporting the service in their report, the purchased transportation (PT) services are reported as directly operated (DO) service.
Consolidated NTD reporters are a collection of transit agencies filing one report. One reporter may file a consolidated report on behalf of other reporters if it is easier to collect and control the quality of the data. This often occurs when one transit agency coordinates the development and funding of public transportation services in an area. Transit agencies filing a consolidated report must operate within the same urbanized area (UZA).
Transit agencies that wish to file a consolidated report must submit a request to FTA in writing. Such requests for consolidations are subject to FTA approval and must include the following:
Transit agencies with nine or fewer vehicles in annual maximum service (VOMS) that operate only non-fixed guideway (NFG) systems are not required to file a Monthly Ridership report. See the Waivers discussion below for more information regarding waivers that may impact monthly ridership reporting.
Voluntary NTD reporters are those transit agencies, public or private, which are not recipients or beneficiaries of Urbanized Area Formula Program (UAF) grants.
Public carriers that do not use or do not have continuing requirements of Urbanized Area Formula Program (UAF) or Nonurbanized Area Formula Program funds may voluntarily submit a complete NTD report.
Private carriers that are not under contract to an Urbanized Area Formula Program (UAF) or Nonurbanized Area Formula Program funds recipient or beneficiary may voluntarily submit a complete NTD report.
FTA encourages all voluntary public and private providers of public transportation services to report their services to the NTD program. Through the submission of complete and accurate reports, the NTD will be more reflective of the entire transit industry. Voluntary reporters that chose to report a complete NTD report are required to complete Safety and Security (if applicable) and Monthly Ridership reports.
The Monthly Ridership report consists of a series of forms that collect monthly ridership data providing FTA with monthly trends in ridership throughout the year. It must contain all the public transportation service, including complementary paratransit services required by the Americans with Disabilities Act of 1990 (ADA), which the transit agency provides or purchases.
For purchased transportation (PT) service, the report must contain data only for those services under contract.
FTA will not grant special consideration to agencies or make adjustments to the apportionment formula due to strikes, labor disputes or work stoppages.
All agencies are required to submit Ridership data on a monthly basis. The following exhibit presents a summary of NTD reporting requirements.
Exhibit 2 — Summary of NTD Reporting Requirements |
| NTD Monthly Ridership Report |
| Mode Service Operated form (MR-10) All reporters |
| Ridership Activity form (MR-20) All reporters |
Unlike the
NTD Annual Report, which covers the 12-month fiscal year period, the data in the
NTD Monthly Ridership report covers a 12-month period corresponding to the calendar
year.
This section describes the following:
Each transit agency is assigned a unique FTA NTD identification number (NTD ID) to be used in the NTD report and all correspondence. Each transit agency must have a NTD identification number before filing a report. If you are a new reporter and do not have a NTD identification number, please refer to the New Reporters discussion in the Urbanized Area Reporting Manual.
All required forms are completed using Internet Reporting which are accessible from the NTD website at www.ntdprogram.gov. Completing the Mode Service Operated form (MR-10) automatically generates the required Ridership Activity forms (MR-20) for the transit agency.
This manual contains all information necessary to complete the Monthly Ridership report using Internet Reporting. See the Internet Reporting section of this manual for specifics. FTA provides Internet Reporting user names and passwords to transit agencies.
Transit agencies must submit their reports via the Internet Reporting system. A transit agency must file a complete report by the report due date. See the When to Report section below to determine your due date.
Data reported must adhere to the following rules:
Internet Reporting incorporates these rules, formatting data automatically when you complete a cell entry.
Purchased transportation (PT) service is service provided to a public transit agency or governmental unit from a public or private transportation provider based on a written contract. A contractual relationship exists only if all the following criteria are met:
Granting a transportation provider permission to operate certain services through a franchise or license does not, in itself, constitute purchased transportation (PT). Also, management services contracts, in which all or some personnel or services are provided to manage or operate the transit agency, are not purchased transportation (PT). Generally, the service is part of the public transit agency’s directly operated (DO) service.
Cooperative
agreements between public transit agencies or governmental units should not
be reported as purchased transportation (PT) services.
Exhibit 3 — NTD Monthly Ridership Requirements and Timeline | |||
| Form Name | Form Purpose | Reporting Frequency |
Forms Submitted |
|---|---|---|---|
|
Mode Service Operated form (MR-10) |
Gives NTD the information needed to generate the ridership activity forms the transit agency will need to complete for the reporting year. |
Annually (January) and when mode or type of service is added or deleted | One per transit agency |
|
Ridership Activity form (MR-20) |
Provides NTD with monthly information on service provided by the transit agency. | Monthly | One per mode / type of service (TOS) combination |
|
Monthly Reporting Due Dates | |||
|
Month |
Due Date | ||
|
January |
February 28 | ||
|
February | March 31 | ||
| March | April 30 | ||
| April | May 31 | ||
| May | June 30 | ||
| June | July 31 | ||
| July | August 31 | ||
| August | September 30 | ||
| September | October 31 | ||
| October | November 30 | ||
| November | December 31 | ||
| December | January 31 of the following year | ||
NTD requires transit agencies to submit complete reports according to the due date schedule. Failure to report results from not submitting a report, submitting a late report or submitting an incomplete report. As a result, your transit agency's data may not be included in the NTD. Furthermore, FTA may declare your transit agency ineligible to receive any Urbanized Area Formula Program (UAF) grants during an entire Federal fiscal year. This ineligibility applies to all transit agencies, regardless of the size of the urbanized area (UZA) served.
A report is considered late if it is not submitted by the due date. Refer to Exhibit 3 NTD Monthly Ridership Reporting Requirements and Timelines for due dates.
The system will auto-generate a series of three e-mails sent per reporting due date:
Please do not respond to these e-mails. These notices are auto-generated by the system the morning it is sent out, and should be disregarded if you submitted your report within the last few hours.
Transit agencies are required to respond to validation inquiries. Failure to respond within the prescribed timeframe may result in Failure to Report status, which may affect your Urbanized Area Formula Program (UAF) funding eligibility and the amount of funding the UZA receives. If your transit agency serves a UZA with a population of 200,000 or more, data will not be entered into the formula for selected formula statistics.
Transit agencies submit all NTD reports via Internet Reporting at the project's website, www.ntdprogram.gov.
FTA assigns an NTD analyst to each reporting transit agency to assist reporters throughout the year. Please feel free to contact your NTD analyst if there are any questions, or if FTA can do anything to assist you in reporting.
This section contains two items necessary to understanding NTD reporting:
Reporting data for the NTD requires an understanding of the following transit concepts and terms:
Each of these terms is described in further detail in the sections that follow.
The definition of public transportation is important because the purpose of the NTD is to collect information on public transportation. As defined in the Federal Transit Act, public transportation means transportation by bus (MB) or rail, or other conveyance, either publicly or privately owned, providing to the public general or special service (but not including school buses or charter or sightseeing service) on a regular and continuing basis. Public transportation is also synonymous with the terms mass transportation and transit.
Public availability is a key part of the definition. Services defined as public transportation are available to any person who pays a prescribed fare and meets other availability requirements, such as the Americans with Disabilities Act of 1990 (ADA). Charter and school bus services are not considered public transportation because they serve specific groups of people and cannot be used by people not belonging to these groups. Service must be open to the general public, not only to specific categorical groups, such as school children.
NTD reporting is a requirement for recipients and beneficiaries of Section 5307 Urbanized Area Formula Program (UAF) (see the NTD Urbanized Area Reporting Manual for Section 5307 requirements) and Section 5311 Nonurbanized Area Formula Program of the Federal Transit Act. Under the Urbanized Area Formula Program (UAF), the term public transportation usually applies to area-wide services primarily within an urbanized area (UZA). Since Congress uses NTD performance data in statutory formulae to apportion FTA funding to UZAs, the NTD can only contain public transportation or transit data. Transportation service that is not public transportation service should not be reported to the NTD. Public transportation is predominantly commuter service. For the purposes of the NTD, a commuter is a transit rider that travels back and forth during the same day primarily within a UZA. Intercity bus services are excluded under the Urbanized Area Formula Program (UAF). However, some commuter rail and ferryboat intercity services are permitted, if a person travels and returns on the same day. (Refer to the Basic Information module, Identification form (B-10) for NTD modal definitions and requirements).
For NTD reporting, FTA reserves the right to evaluate transit services as public transportation by requiring a written description of the transit services including availability and public notification of the availability of service, compliance with Americans with Disabilities Act of 1990 (ADA) requirements, service area maps, schedules and public timetables, and other materials as necessary. In the case of new modes or significant expansion of transit services, FTA reserves the right to request passenger surveys.
A variety of transit modes are operated in the United States. The NTD reporting system groups transit modes into two broad categories — rail modes and non-rail modes — as follows:
| Rail Alaska railroad (AR) |
Non-Rail Aerial Tramway (TR) |
Modal definitions are used in the NTD reporting system in different ways. Transit agencies are required to report data according to the detailed modal definitions on most reporting forms (e.g., bus (MB), demand response (DR), vanpool (VP) and light rail (LR)). On selected forms (e.g., Transit Way Mileage form (A-20), Service form (S-10), Energy Consumption form (R-30), Federal Funding Allocation Statistics form (FFA-10)), different data items are required for rail and non-rail modes.
Public transportation can be provided in two ways:
Type of service (TOS) is an important element of NTD reporting. On most reporting forms, transit agencies are required to report data by type of service (TOS).
The maximum service operated during the year is an important determinant of a transit system's size and resulting performance. Transit agencies are required to report data on two measures of maximum service:
Vehicles operated in annual maximum service (VOMS) is a count of the revenue vehicles scheduled for the peak day and operating period of the peak service season or schedule of the year. The revenue count is the typical number of vehicles operated and does not consider the number of vehicles operated on atypical days such as holiday celebrations (e.g., Fourth of July), or one-time special events (e.g., World Series celebrations, political conventions).
Vehicles available in annual maximum service is a count of the revenue vehicles available to meet the maximum service requirement (revenue vehicles necessary to meet peak demand) for the fiscal year. This count of revenue vehicles includes:
The count of vehicles does not include:
Spare vehicles are revenue vehicles used to accommodate routine maintenance and repair operations, and to replace vehicles in scheduled service that breakdown or are involved in accidents.
Emergency contingency vehicles are inactive revenue vehicles that normally would have been disposed of at the end of their useful life. FTA allows transit agencies to retain these vehicles if they are stored and maintained, and part of an approved FTA Emergency Contingency Plan.
The FTA Uniform System of Accounts (USOA) and Uniform System of Accounts and Records and Reporting System; Final Rule (CFR Part 630) is essential to understanding the forms and instructions presented in this manual. You can obtain these documents, as well as the other reference documents listed in the exhibit below, by visiting the NTD Project website at www.ntdprogram.gov or calling the NTD Project Office at (703) 462-5220.
The following exhibit provides a list of other documents necessary for NTD reporting.
Exhibit 5 — Reference Documents |
|
2007 NTD Urbanized Area Reporting Manual FTA National Transit Database Uniform System of Accounts (USOA), January 1995 |
Transit agencies must use the National Transit Database (NTD) Internet Reporting system to provide their data via reports to the Federal Transit Administration (FTA). NTD Internet Reporting is the online means for transit agencies to enter, save, review and revise data, and submit reports. It provides for timely and accurate reporting as all tasks and requirements for the NTD can be fulfilled via this system.
This section provides Internet Reporting information for the NTD Monthly Ridership report. Separate instructions for Annual and Safety and Security Internet Reporting are included in the Urbanized Area Reporting Manual and the Safety and Security Reporting Manual.
A checkmark is now required for each mode/type of service (TOS) operated by the agency. Vehicles operated in maximum service (VOMS) is no longer captured on the MR-10 form.
On the MR-20 form, the number of regular service days (column e) will only accept a value between 0 and 23.
All reporting fields are required and must have a value entered before each month’s data can be date stamped.
Monthly data fields and the Edit Date button are no longer available before the month actually occurs.
Column a is now labeled estimated unlinked passenger trips (EUPT).
Numerous measures have been taken to ensure that all data entered into the Internet Reporting system are safe and available only to those with proper access. The NTD servers and network are secured behind a firewall. The website operates the secured web protocol, https, and the entire site is password protected. Additionally, multiple server and database protection layers protect the database files.
Internet Reporting is accessed from the NTD Homepage.
To access Internet Reporting:
Use your Internet service provider (ISP) to connect to the Internet. Internet Reporting requires a web browser that is at least a 6.x version (Internet Explorer 6.0).
If you don’t have the latest version of the browser, go to Microsoft.com to download the latest version free of charge.
Verify that your browser is set to check for newer versions of stored pages with each visit to the page.
In Internet Explorer, this is done by accessing Tools / Internet Options / General / Temporary Internet Files Settings / Every Visit to Page.

The NTD Homepage offers the following information and data for reporters and others interested in the NTD:
Clicking the Internet Reporting Login link will open the Internet Reporting Login page. Enter your user name and password to gain access to Monthly Ridership Reporting.
Internet Reporting provides four levels of access to the NTD Report:
The system access level is determined by the user name. The first three characters of the user name define the access level and the last four digits represent the transit agency’s NTD ID. There are four types of user names corresponding to the four access levels available within the NTD Report:
Each transit agency is e-mailed this set of user names with a password for each. Transit agencies determine access within their organizations and distribute user names and passwords accordingly.
A user can change his / her password at any time. Refer to Sys Admin: Changing Your Password for additional information on this topic. Users should be aware that passwords expire every ninety days.
The CEO
and Contact Person (if the NTD Contact Person is the same individual that is responsible
for the Safety and Security report), if they wish, may use the same password for
both the Urbanized Area Report and the Safety and Security Report.

Monthly Ridership Reporting includes the following tabs:

After completing the logon process you will be taken to the Monthly Ridership Report Homepage. Click the Home tab near the top of any screen to return to the Home tab from another area.

Click on the Monthly Ridership tab to open the Monthly Ridership screen. This screen provides links to the Monthly Ridership forms that your agency is required to complete.
Initially, the Monthly Ridership screen only provides access to one form:
Review, complete and save the Mode Service Operated form (MR-10) to automatically generate the Ridership Activity form(s) (MR-20) for each mode / type of service operated by the agency.

Click on the Notes tab to open the Notes Summary screen. Internet Reporting allows the transit agency to create a form note to explain unusual circumstances or data discrepancies that impact the data being submitted to the NTD.
To create a form note click on the Add Form Note link at the top right of the form you are editing or viewing. Internet Reporting will take you to the Form Notes screen for the specific form. Internet Reporting will pre-fill the mode and type of service (if applicable) for which the note is created. The transit agency completes the note comment.
To save a form note, click on the Save button at the bottom of the screen. To return to the form being edited without saving the note, click on the Cancel button.
Click on the Notes tab to view the Notes Summary screen. You can review the form notes associated with a specific form or all form notes for the report. While working in a form click on the Notes tab to display the Form Notes screen for the form. The form name and mode / type of service will be displayed just beneath the tabs.
While you are entering and saving monthly ridership data for any given month, you can edit a note for that month after it has been created. Click on the Edit Note link in the far right column on the Notes screen. Once the monthly ridership data for any given month is date stamped, the notes are frozen and cannot be edited. However, if needed, additional form notes can be added.
Notes are
frozen each time the Edit Date button is clicked. If the report is edited
and redated, the previously submitted notes will not be affected.
All form notes can be printed from the Reports tab by clicking the All Form Notes link.

The Communications tab gives transit agencies a centralized area in which to view past correspondence with the Federal Transit Administration’s (FTA) National Transit Database (NTD) program. In addition, the correspondence view can be filtered to show only certain processes or communication types.

The Sys Admin screen provides the ability to change your NTD password.
All passwords expire every ninety days. You can change your password at anytime on the Sys Admin screen by specifying your current and new password. To be valid, a password must be at least eight characters long and contain at least one letter and one number. It cannot contain spaces. Passwords are case-sensitive. If you do not update your password within the ninety-day term, you will be forced to update your password when you first access the system once the ninety-day period has expired. The screen is similar to the one available on the Sys Admin screen and the same password rules apply.

Click on the Help tab to display the Help screen. The Help screen provides access to the 2007 NTD Reporting Manual for additional help in completing the NTD report forms. The Help screen displays the table of contents for the Monthly Ridership Reporting Manual with links to each section of the manual.
Do not use the browser Back and Forward buttons to navigate between screens. Instead, use the Internet Reporting system buttons, tabs and links.
A Save button is provided at the bottom of each Internet Reporting form. When entering information into a form it is strongly recommended that you save the form frequently. This will prevent the loss of data if your Internet connection is unexpectedly lost. Also, Internet Reporting has an automatic time-out feature which will log you off of the system after a period of inactivity. It is strongly recommended that you save your work every 15 minutes. Otherwise, there is a risk that the next action you take on the system will result in the closure of the screen displayed in your browser and the loss of any data that you had not saved.
Click on the Print
button supplied at the bottom of the form screen to display the report in the
Adobe Acrobat Viewer. Click the Print button
in the upper left corner of
the viewer. Then click the Okay button on the resulting Print window.
Note: Only forms for 2006 or later will print using the Adobe Acrobat Viewer. Previous years’ forms will print using the Crystal Reports Viewer and function the same as forms printed from the Reports tab.
Forms can be printed using the Crystal Reports Viewer. For troubleshooting information refer to the Announcement section of the Monthly Ridership Report Homepage.
In order to facilitate printing of forms Internet Reporting utilizes the Crystal Reports downloadable viewer and writer. You will be prompted to download the Crystal Smart Viewer for Active X free of charge the first time the print functionality is accessed, (a report link is clicked on the Reports tab or the Print button is clicked on a form page). This download occurs only once and is absolutely necessary to view or print a report.
This module contains two forms:
Transit agencies with a Nine or Fewer Vehicles Waiver are not required to complete a Monthly Ridership report.
The Mode Service Operated form (MR-10) is completed once at the beginning of the calendar year and revised only if there is a new mode and type of service (TOS) added or discontinued during the reporting period. This form is used to identify the modes and types of service (TOS) operated by the transit agency. Internet Reporting uses this information to generate the appropriate ridership activity forms for the transit agency.
This form is required for all transit agencies, except those agencies with a Nine or Fewer Vehicles Waiver.
The Ridership Activity form (MR-20) collects monthly information regarding transit service provided by the agency. These data provide FTA with monthly trends in passenger usage and service levels.
This form is required for all transit agencies, except those agencies with a Nine or Fewer Vehicles Waiver.

The Mode Service Operated form (MR-10) is used to identify the modes and types of service (TOS) operated by the transit agency. Internet Reporting uses this information to generate the appropriate ridership activity forms for the transit agency. This form is completed once at the beginning of the calendar year and revised only if there is a mode added or discontinued during the reporting period.
All agencies must complete the Mode Service Operated form (MR-10) annually. The exception is transit agencies with a Nine or Fewer Vehicles Waiver, who need not complete this form. Data for the 2007 reporting year must be submitted by February 28, 2008.
A checkmark is now required for each mode/type of service (TOS) operated by the agency. Vehicles operated in maximum service (VOMS) is no longer captured on the MR-10 form.
The Mode Service Operated form (MR-10) is used to identify the modes and types of service (TOS) operated by the transit agency. The data reported on this form is used by Internet Reporting to generate the appropriate Ridership Activity forms (MR-20) for the transit agency for the calendar year.
Internet Reporting prepares one set of monthly forms for each mode / type of service (TOS) operated by the transit agency.
When the Mode Service Operated form (MR-10) is accessed, use the check-boxes to indicate which modes/types of service (TOS) are operated by your agency. Once the form has been saved and submitted, the check boxes are no longer active.
If you need to add or delete a mode or type of service (TOS) during the report year, use the Add / Delete Mode / Type of Service button at the bottom of the screen. Common reasons for a mode / type of service being added or deleted:
Transit agencies operate one or more modes of transit service. A mode is a system for carrying transit passengers described by specific right-of-way (ROW), technology and operational features.
The
NTD recognizes the following modes of public transit service:
| Aerial Tramway (TR) Non-Rail – Fixed Guideway
A system of aerial cables with suspended vehicles. |
Automated Guideway (AG) Rail – Fixed Guideway
An electric railway of guided vehicles that is operated with a computer and without vehicle operators. The transit systems in Detroit, Jacksonville, and Miami operate this mode. | Bus (MB) Non-Rail – Fixed Guideway or Non-Fixed Guideway
The most prevalent mode in the country, and is powered by a motor and fuel contained within the vehicle. |
|
Cable Car (CC) Rail – Fixed Guideway
A railway propelled by moving cables located beneath the street. While popular at the turn of the last century, the only surviving system is operated in San Francisco. |
Commuter Rail (CR) Rail – Fixed Guideway
Typically operated over old freight railroad lines and is diesel or electric propelled. Usually, the service operates between a central city and adjacent suburbs. |
Demand Response (DR) Non-Rail – Non-Fixed Guideway
Scheduled in response to calls from passengers. Passengers with similar origins and destinations are often scheduled to ride the same vehicle. Many transit systems operate demand response (DR) service to meet the Federal ADA requirements, and expenses and passenger trips are reportable for DR. |
|
Ferryboat (FB) Non-Rail – Fixed Guideway
A mode that carries passengers over a body of water using diesel or steam powered vessels. | Heavy Rail (HR) Rail – Fixed Guideway
An electric railway with exclusive or separate right-of-way (ROW) from other vehicles or foot traffic. It has high passenger carrying capacity and high platform loading. Most of the nation’s subway services are classified as heavy rail. |
Inclined Plane (IP) Rail – Fixed Guideway
A railway operating on steep slopes and grades with vehicles powered by moving cables. The transit systems in Chattanooga, Cambria County, and Pittsburgh operate this mode. |
| Jitney (JT) Non-Rail – Non-Fixed Guideway
Operated on fixed routes using passenger cars or vans as demand warrants without fixed schedules or fixed stops. The Laguna Beach transit system operates this mode. |
Light Rail (LR) Rail – Fixed Guideway
An electric railway that operates in mixed traffic with automobiles or has grade crossings with automobiles. Typically, light rail (LR) trains are short and consist of one to two cars. | Monorail (MO) Rail – Fixed Guideway
An electric railway that is suspended from or straddles a guideway formed by single beam, rail or tube. The service in Seattle is the only public transportation monorail (MO) reported in the NTD. |
|
Publico (PB) Non-Rail – Non-Fixed Guideway
Operated over fixed routes, but not on fixed schedules. The service is privately owned and operated, but is regulated by local or state governments. The service in San Juan, Puerto Rico is the only publico service reported in the NTD. |
Trolleybus (TB) Non-Rail – Fixed Guideway
A bus service operated using an electric bus that is powered by a motor drawing current from overhead wires using trolley poles. Trolleybus (TB) service is operated by the transit systems in Boston, Dayton (OH), Philadelphia, San Francisco, and Seattle. | Vanpool (VP) Non-Rail – Non-Fixed Guideway
A commuting service operating under pre-arranged schedules for previously formed groups of riders in vans. |
|
Alaska Railroad (AR) Rail – Fixed Guideway
A special railroad that Congress recognized for certain FTA funding that operates in Alaska. |
Other If none of the choices fits your agency, select the category: Other. Internet Reporting will display a box for you to describe the other mode. |
If a vehicle is used for more than one mode, report it under each mode for which it is used and describe the use of the vehicle using the Add Form Notes link.
For example, the transit agency may use five of its vehicles in bus (MB) mode during peak hours and, during non-peak hours, may use the five vehicles in demand response (DR) service. The vehicle would be reported as bus (MB) and demand response (DR) on the Mode Service Operated form (MR-10) and supports another mode should be indicated on the NTD Annual report, Revenue Vehicle Inventory form (A-30).
When all data have been entered into the form and verified for accuracy, click on the Submit Report button to generate the required forms.

A Form Note can be attached to any form to explain unusual circumstances or data discrepancies thatimpact the data being submitted to NTD. Use the Add Form Note link for relevant information to a form. Click on the Add Form Note link at the top of the screen and enter your note on the Notes screen. You can review and / or edit a Form Note from the Notes tab.

If the agency adds or discontinues a new mode / type of service (TOS) (directly operated (DO) or purchased transportation (PT)), click on the Add / Delete Mode / Type of Service button at the bottom of the form. A new screen will appear. Click on either the Add or Delete Mode / Type of Service button depending on whether a mode / type of service (TOS) is being added or discontinued. Select the mode and type of service from the Drop-Down boxes for the correct line and enter either the new service start date or the out of service date. Save the form and click on the Submit Report button.
Completing the Mode Service Operated form (MR-10)
From the Monthly Ridership tab, click on the Mode Service Operated form (MR-10) link.
Form Level Help: Click on the Help tab at the top of the screen for form level help. A form note can be attached to any form. Use the Add Form Note link for relevant information to a specific field, to the entire form or to multiple forms. Click on the Add Form Note link at the top of the screen and enter your note on the Notes screen. You can review and / or edit a form note from the Notes tab. Form notes can be edited or revised until the form is Saved after which new form notes can be added.
Saving or Closing the Form: Click on the Submit button to save and submit the form. Click on the Close button to close the form without saving.
Completing
the Form
Adding a Mode / Type of Service
Deleting a Mode / Type of Service


Monthly ridership activity information is collected by mode and type of service (TOS). These data provide FTA with monthly trends in passenger usage and service levels.
Reporters must enter their data by the end of the month following the month for which data is being reported, i.e., January data is submitted by the last day of February.
The number of regular service days (column e) will only accept a value between 0 and 23.
All reporting fields are required and must have a value entered before each month’s data can be date stamped.
Monthly data fields and the Edit Date button are no longer available before the month actually occurs.
Column a is now labeled estimated unlinked passenger trips (EUPT).
There are two Ridership Activity forms (MR-20) tailored for:
The Ridership Activity form (MR-20) is used to report monthly data by mode and type of service (TOS) for the revenue vehicles used to provide transit service. The data include:
The data items in this form are similar to the annual data reported on the Service form (S-10). The data reported on the Ridership Activity form (MR-20) must be consistent with the annual data reported in the Service form (S-10).
Data fields for future months will not appear until the 1st of the following month (i.e., February data fields will not be available until March 1).
As the form is being completed, changes should be saved by clicking the Save button frequently.
When all data have been entered for a particular month and the data have been verified for accuracy, the month’s data should be date stamped by clicking the Edit Date button at the end of the row. The date under the Submit Date column should reflect the current date. Next click on the Save button at the bottom of the form to save the data. If you do not click on the Save button at the bottom of the form, the data will not be saved.
To close the form, click on the Close button to return to the Monthly Ridership tab. The submit date is the date that the user last updated and saved data for a particular month. Ridership data can be updated, date stamped and saved until the end of February of each year, after this time revisions must be done through your ridership analyst.
To revise data for prior months, enter the data in the appropriate cell for the month being revised. Click on the Edit Date button at the end of the row. The date under the Submit Date column should reflect the current date. Next, click on the Save button at the bottom of the form. To close the form, click on the Close button to return to the Monthly Ridership tab.
Estimated unlinked passenger trips (EUPT) are the number of passengers who board public transportation vehicles. Passengers are counted each time they board vehicles no matter how many vehicles they use to travel from their origin to their destination.
Since it can be very difficult and costly to count each passenger (100 percent count), many transit agencies estimate annual unlinked passenger trips (EUPT) based on a sampling procedure. The Federal Transit Administration (FTA) requirements are:
Transit agencies are not required to use a sampling procedure to estimate and report annual unlinked passenger trips (EUPT). Actual counts (100 percent sample) are acceptable and meet FTA requirements. More detailed information about FTA’s sampling requirements is presented in the Service Module section of the reporting manual.
Actual counts (100 percent sample) involve counting passengers each time they board a vehicle. This method is generally applicable to smaller systems, but its use is not precluded by a system’s size. If 100 percent counts are available, they are preferable to sampling and should be reported on the Ridership Activity form (MR-20).
If the transit agency uses a sampling method, the total estimated unlinked passenger trips (EUPT) for a specific month should be estimated using the sample data collected during the month and the same procedure that the transit agency uses to estimate annual unlinked passenger trips (EUPT). This approach may not meet FTA’s confidence and precision levels for annual data, but does meet FTA’s requirements for a good faith effort for reporting monthly data on the Ridership Activity form (MR-20).
If the transit agency changes its sampling procedure, it should revise its reported estimated unlinked passenger trips (EUPT) for the current year and the prior year using the new methodology. The transit agency should contact their validation analyst for assistance in reporting the revised estimates for the prior year.
Example 2 — Transit Agency Makes 100 Percent Count for Bus (MB) to Calculate the Total Unlinked Passenger Trips for the Month | ||
|
Day |
Number of Days in Month |
Total Estimated Unlinked Passenger Trips |
|---|---|---|
| Weekday |
21 | 46,956 |
| Saturday |
5 | 5,987 |
| Sunday |
5 | 3,125 |
| Solution: The total unlinked passenger trips for weekday, Saturday, and Sunday are summed to arrive at the total unlinked passenger trips for the month. | ||
|
Total | 31 |
56,068 |
The transit agency reports 56,068 for total estimated unlinked passenger trips (EUPT) for the month.
Example 3 — Transit Agency Uses Sampling Procedure for Bus (MB) to Estimate the Total Unlinked Passenger Trips for the Month: FTA C 2710.1A for Bus (MB) | |||||||||
| Weekday | |||||||||
|
AM Peak |
Midday |
PM Peak |
Other |
Total |
Saturday |
Sunday |
Total | ||
|---|---|---|---|---|---|---|---|---|---|
| Sample | |||||||||
|
1. Unlinked Passengers |
321 |
249 |
301 |
52 |
131 |
165 | |||
| Bus Trips | |||||||||
| 2. Sampled | 10 |
11 |
9 |
3 |
6 |
9 | |||
| 3. Total | 4,844 |
4,289 |
4,579 |
1,512 |
1,768 |
802 | |||
| Solution: Dividing the total sampled estimated unlinked passenger trips (EUPT) by the number of sampled trips results in the sample average. The sample averages for weekday, Saturday, and Sunday are multiplied by the respective total number of bus trips to calculate the monthly-estimated unlinked passenger trips for weekday, Saturday, and Sunday. The total estimated unlinked passenger trips (EUPT) for weekday, Saturday, and Sunday are summed to arrive at the estimated total monthly-estimated unlinked passenger trips. | |||||||||
|
AM Peak |
Midday |
PM Peak |
Other |
Total |
Saturday |
Sunday |
Total | ||
| Sample Average | |||||||||
|
4. Passengers/Trips |
32.10 |
22.64 |
33.44 |
17.33 | 21.83 |
18.33 | |||
| Monthly Total | |||||||||
| 5. Unlinked Passengers | 155,492 |
97,103 |
153,122 |
26,203 |
431,920 |
38,595 |
14,701 |
485,216 | |
Actual vehicle revenue hours (VRH) and miles (VRM) are incurred when non-rail service is available to the general public. These are the miles and hours traveled by vehicles in carrying passengers, plus layover/recovery time. It does not include the miles and hours for items such as deadhead, charter services, school bus service, operator training or maintenance testing. For rail service, the data are reported in terms of passenger car revenue hours and miles.
More detailed information about the collection of revenue hours (VRH) and miles (VRM) is presented in the Service Module section of this manual.
This is the number of revenue vehicles / passenger cars operated to meet the maximum service requirement during the month. In most instances, this is the number of scheduled vehicles/passenger cars since most transit agencies have sufficient vehicles/passenger cars to operate the scheduled service. Vehicles operated in maximum service (VOMS) / passenger cars in operation exclude atypical days or one-time special events.
This data item is different than the vehicles operated in annual maximum service (VOMS) that is reported on the Service form (S-10). The difference between the forms is the time period used in the definition— a month in the Ridership Activity form (MR-20) and a fiscal year in the Service form (S-10).
Enter the number of days during the month that the agency operates normal weekday service. Saturday, Sunday (holiday), reduced or special event service should not be included. This column will only accept a value between 0 and 23.

A Form Note can be attached to any form to explain unusual circumstances or data discrepancies that impact the data being submitted to the NTD. Use the Add Form Note link for relevant information to a form. Click on the Add Form Note link at the top of the screen and enter your note on the Notes screen. You can review and / or edit a Form Note from the Notes tab.
Completing the Ridership Activity form (MR-20)
From
the Monthly Ridership screen, click on the Ridership Activity form (MR-20)
link for the applicable mode / type of service (TOS).
Complete the Ridership Activity form (MR-20) following the instructions in this section. Data fields for future months will not appear until the 1st of the following month (i.e., February will not be available until March 1).
Form Level Help: Click on the Help tab at the top of the screen for form level help. A form note can be attached to any form. Use the Add Form Note link for relevant information to a specific field, to the entire form or to multiple forms. Click on the Add Form Note link at the top of the screen and enter your note on the Notes screen. You can review and / or edit a form note from the Notes tab. Form notes can be edited or revised until the form is Date Stamped and saved after which new form notes can be added.
Saving and Closing the Form To save your data, click the Save button at the bottom of the form. If you do not click the Save button prior to closing the Ridership Activity form MR-20, your data will be lost. You will not be able to save data for any month if there are empty data fields for that line. This procedure is followed each month, or each time you return to a prior month to revise data.
Rail Modes
Non-Rail Modes