FTA National Transit Database: What Training Records You Must Report

Transit agencies that receive FTA funding and report to the National Transit Database must be able to demonstrate that the training data they submit is accurate, complete, and reconcilable with their underlying training records. NTD reporting is not just a data entry exercise. It is a compliance obligation under 49 U.S.C. 5335, and the data you submit becomes the baseline FTA uses to evaluate your agency during triennial reviews, safety investigations, and data quality audits. If your training records do not support what your NTD submission claims, you have a problem that goes beyond paperwork.

This guide covers what training-related data flows into the NTD, how the S&S-40 and S&S-50 forms intersect with training documentation, and how to build reporting processes that hold up under scrutiny.

What the NTD Is and Why Training Data Matters

The National Transit Database is the federal repository for financial, operating, and safety data reported by transit agencies nationwide. Established under 49 U.S.C. 5335, NTD reporting is mandatory for agencies receiving FTA Urbanized Area Formula Grants (Section 5307) and other federal transit funding.

FTA uses NTD data for multiple purposes:

• Fund apportionment: NTD data directly influences how federal transit dollars are distributed. Inaccurate reporting can affect your agency’s funding allocation.
• Safety trend analysis: Aggregate NTD data helps FTA identify system-wide safety trends and target oversight resources.
• Triennial review preparation: Auditors review NTD submissions before arriving at your agency. Inconsistencies in your data raise flags before the site visit even begins.
• Benchmarking: FTA and SSO agencies compare your safety and training metrics against peer agencies. Outliers, both high and low, draw attention.

Training data enters the NTD through several pathways, and understanding each one is critical to building a defensible reporting process.

Training-Related NTD Reporting Components

Employee Data (Form S-10)

The S-10 form captures workforce data including total employees, total employee hours, and breakdowns by mode. While it does not explicitly ask for training hours, the workforce metrics establish the denominator against which training activity is measured. If you report 500 full-time equivalent employees, auditors can estimate what a reasonable training hour total should look like for an agency of your size.

Safety Events (Forms S&S-40 and S&S-50)

These are the forms where training intersects most directly with NTD reporting.

S&S-40 (Major Event Report): Required within 30 days of a major safety event. Major events include fatalities, injuries requiring transport to a medical facility, property damage exceeding $25,000, and evacuations. The form requires:

• Event description and narrative
• Contributing factors
• Corrective actions taken or planned

When a safety event investigation identifies a training deficiency as a contributing factor, that finding appears in the S&S-40 narrative. FTA and SSO investigators can then request the relevant training records to verify whether the involved employee had current, completed training on the procedures that were not followed.

S&S-50 (Detail Report): Provides additional detail for qualifying events. The narrative section may reference whether the involved employee had completed required training, whether the training covered the specific scenario encountered, and whether the agency’s training program has been updated in response to the event.

When an S&S-40 report cites a training gap as a contributing factor and the agency cannot produce the employee’s training records within 48 hours, the initial safety event becomes a compliance event. The documentation failure compounds the operational failure.

Annual Safety and Security Module

The annual NTD safety submission captures aggregate training metrics at the system level. Depending on the reporting year and FTA’s evolving requirements, this may include:

• Total safety training hours delivered across the agency
• Training hours by category (initial, refresher, remedial)
• Training completion rates for required topics
• Number of employees who completed required compliance training within the reporting period

These figures must reconcile with your underlying training records. You cannot estimate or approximate. The number you submit must be derivable from individual training completion records in your system.

The Reconciliation Problem

The most common training-related NTD compliance issue is reconciliation failure. This happens when:

1. Aggregate hours don’t match individual records. Your NTD submission says 12,000 training hours. But when you add up all individual completion records in your training system, the total is 9,200. The 2,800-hour gap may represent classroom sessions that were not logged in the system, on-the-job training that was tracked informally, or training delivered by contractors who did not submit records. Regardless of the reason, the discrepancy is a finding.

2. Safety event timelines conflict with training records. An S&S-40 says an operator involved in an event completed required training on March 15. But the training record shows the completion date as March 22, seven days after the event. Either the S&S-40 narrative is wrong, the training record was backdated, or there is a timestamp error. Any of these possibilities creates compliance exposure.

3. Workforce counts don’t align with training coverage. The S-10 reports 350 operators. Your training records show only 310 operators completed annual refresher training. The 40-person gap may represent new hires in the pipeline, operators on leave, or simply a documentation failure. Auditors will want to know.

Building NTD-Ready Training Documentation

Principle 1: Aggregate from Individual Records, Not Estimates

Every NTD training metric should be a rollup of individual employee training records. Start with the granular data and sum up, rather than starting with an estimate and trying to find records to support it.

Your training management system should allow you to:

• Query total training hours by date range, filtered by mode, department, or training category
• Export a report showing every individual completion record that contributes to the aggregate total
• Reconcile the exported total against the NTD submission value

If you cannot produce this export, your NTD number is not defensible. Invest in compliance training software that supports this level of reporting.

Principle 2: Capture All Training in One System

Fragmented training records are the root cause of most NTD reconciliation failures. When classroom training is tracked on paper sign-in sheets, CBT is tracked in the LMS, OJT is tracked in supervisor notebooks, and contractor training is tracked nowhere, producing an accurate NTD aggregate is functionally impossible.

Consolidate all training records into a single system of record. This does not mean all training must be delivered through one platform, but all completion records must flow into one database. Establish data feeds from every training delivery channel:

• LMS completions via direct database
• Classroom attendance via digital sign-in linked to the central system
• OJT completions via supervisor entry into the system within 24 hours
• Contractor training via documented verification entered by the contracting officer

Principle 3: Timestamp Everything Automatically

Manual date entry is the most common source of timestamp errors, and timestamp errors are the most common source of S&S-40/training record conflicts.

When a worker completes a digital training module, the system generates the timestamp. When an instructor closes out a classroom session, the system logs the end time. When a supervisor signs off on OJT, the mobile entry captures the date and time from the device.

Eliminate every opportunity for a human to type a date into a field after the fact. Backdated entries, whether intentional or accidental, create audit exposure that is difficult to explain. See our guide to building audit-ready training records for specific implementation guidance.

Principle 4: Link Safety Events to Training Records Immediately

When a major safety event occurs, pull the involved employee’s training records within hours, not after the S&S-40 is drafted. This serves two purposes:

1. Accurate S&S-40 narrative: You can state definitively whether the employee had current training on the relevant procedures, rather than making assumptions that you later cannot support.
2. Early gap identification: If the training record is missing or incomplete, you discover the problem when you can still address it proactively, before an investigator discovers it.

Build a standard operating procedure: within four hours of a major safety event, the safety department pulls complete training records for all involved employees and verifies currency. This practice prevents the scenario where an S&S-40 claims “employee had completed all required training” but the records tell a different story.

Agencies that pull training records within the first four hours of a safety event are better positioned to write accurate S&S-40 narratives. Those that wait until the reporting deadline often discover documentation gaps under time pressure, leading to either inaccurate filings or incomplete records.

Principle 5: Run Quarterly NTD Dry Runs

Do not wait until the annual NTD submission deadline to compile your training data. Run a dry compilation quarterly:

1. Export aggregate training hours for the quarter
2. Compare against individual completion records
3. Check for missing records, unlogged sessions, and contractor gaps
4. Reconcile any discrepancies while the data is still fresh

Quarterly dry runs reduce your year-end compilation effort from weeks to days and catch data quality issues when they are still correctable.

NTD Data Quality Reviews

FTA periodically conducts data quality reviews of NTD submissions. These reviews verify that reported data is accurate, complete, and consistent. When training data is flagged:

• FTA may request supporting documentation for reported training hours
• Auditors may sample individual training records to verify the aggregate
• Discrepancies may trigger a corrective action plan with reporting deadlines

The best defense against data quality findings is the ability to produce an auditable trail from the NTD submission value all the way down to individual employee training records. If you can show that 12,000 reported hours equals Employee A (40 hours) + Employee B (35 hours) + … for every employee, the data quality review becomes a formality.

Connecting NTD Reporting to Your PTASP

Your PTASP training program and your NTD reporting should draw from the same data source. Under 49 CFR Part 673, your PTASP documents the training program design. The NTD captures the training program’s outputs as reported metrics.

Alignment points to verify:

• Training topics in the PTASP crosswalk should map to categories in the NTD submission. If your PTASP requires training on 12 safety topics, your NTD training hours should be traceable to those 12 topics.
• Employee counts in the S-10 should match the training coverage counts. If you report 400 operators on the S-10, your training records should show that all 400 completed the required training within the reporting period.
• Safety event corrective actions in S&S-40 should appear in training records. If an S&S-40 says corrective training was delivered to all operators in response to an event, your training records should document that delivery.

Record Retention for NTD Compliance

49 CFR Part 630 governs NTD reporting requirements and references record retention obligations. Agencies should retain training records that support NTD submissions for at least three years beyond the reporting year, consistent with FTA’s general record retention requirements for grant-related documentation.

However, other overlapping regulations may impose longer retention periods. Drug and alcohol testing records under 49 CFR Part 655, for example, have their own retention schedules. PTASP training records should be retained for the duration of the employee’s tenure plus additional years per your SSO’s guidance.

The safest approach is to retain all training records for at least five years beyond the employee’s separation date. Digital storage makes this practical and cost-effective. See our guide on training record retention requirements for a comprehensive breakdown.

Technology Requirements for NTD-Ready Training

Your training system needs specific capabilities to support NTD compliance:

• Aggregate reporting: Ability to produce system-level training hour totals by mode, category, and date range
• Drill-down capability: Ability to trace any aggregate number to its constituent individual records
• Audit export: One-click export of all records supporting an NTD submission value
• Automated timestamps: System-generated timestamps for all training events, eliminating manual date entry
• Certification tracking: Tracking of expiration dates and renewal status for all required certifications
• Compliance gap analysis: Dashboard showing which employees are current and which have gaps

Use our Compliance Gap Calculator to identify where your current reporting infrastructure falls short.

The Bottom Line

NTD reporting is the public face of your agency’s training program. The numbers you submit are permanently on record and subject to verification at any time. Agencies that build training documentation processes with NTD reporting in mind, rather than treating NTD as an afterthought, spend less time on annual submissions, survive data quality reviews without corrective action plans, and maintain consistency between their PTASP documentation and their NTD data. The investment in a centralized, timestamp-driven training records system pays for itself the first time an auditor requests supporting documentation and you can produce it in minutes. For a deeper look at how training documentation supports audit readiness, see our guide to FTA compliance audits and our Audit Readiness Score tool. For the full regulatory framework on Safety Management Systems training, see our FTA Safety Management Systems training compliance guide.