An FMCSA investigator asks for the maintenance file on bus 27 and starts flipping: identity, schedule, repair history. Get your bus maintenance records right and it's a five-minute non-event; get them wrong and one missing line becomes a violation, even if the bus is flawless. Here is exactly what 49 CFR 396.3 requires in every per-bus file. Book a demo to see an audit-ready file build itself per bus.
The Compliant Maintenance File Every Bus Needs
Under 49 CFR 396.3, every bus you control for 30+ days needs its own maintenance file — and an auditor knows in seconds whether it's complete. Here are the three records the file must contain, the bus-only test record most fleets miss, and how long to keep it all.
- 1What is this bus?
- 2What's due, and when?
- 3What's been done to it?
The Rule Behind Every Bus Maintenance Record
Section 396.3 is the foundation of vehicle maintenance compliance. It says every motor carrier must systematically inspect, repair, and maintain the buses under its control — and keep a per-vehicle file that proves it. Saying you maintain your fleet isn't enough in an audit; the records have to demonstrate it.
The trigger is control, not ownership. You must keep a maintenance file for any bus you control for 30 consecutive days or more — owned units and leased buses on terms longer than 30 days alike. If it's yours to run for a month, it is yours to document.
And the standard is systematic. A file that shows scattered, react-to-failure repairs tells an auditor you don't have a program. A file showing scheduled intervals and a clean history tells them you do. That difference is the whole point of the record.
The Three Records Every Bus Maintenance File Must Contain
Under 396.3(b), a compliant file has three parts. Each answers a question an auditor will ask of any bus, and a file missing any one of them is incomplete. Here's what belongs in each — and why it matters.
Vehicle Identification
"What is this bus?"
Company/unit number (if marked), make, serial number (VIN), year, and tire size. If the bus isn't owned by you, the file must name who furnished it. It sounds trivial, but it ties every schedule entry and repair unambiguously to one specific bus — and a missing data point as small as tire size routinely draws a violation.
The Maintenance Schedule
"What's due, and when?"
A means to indicate the nature and due date of the inspection and maintenance operations to be performed. This is your PM program on paper: which services this bus needs and when each comes due, whether triggered by mileage or calendar. It's the record that proves the work is planned, not improvised.
Inspection & Repair History
"What's been done?"
A dated record of all inspections, repairs, and maintenance indicating their date and nature. This is the running history — every PM performed, every defect fixed, when and what. It closes the loop: the schedule says what should happen, this proves it did.
Those three map to three auditor questions: what is this bus, what does its program call for, and what has actually been done. Answer all three per bus and the file is complete. Miss one across several buses and it reads as a systemic recordkeeping failure, not an isolated slip. Sign up free and build all three records for every bus in one place.
The Record That Applies to Buses and Nothing Else
Here's the one trucking-focused fleets overlook: 396.3 has a fourth required record that exists only for buses. It's small, it's specific, and an auditor who works passenger carriers will look for it.
Pushout windows, emergency doors & marking lights
Under 396.3(b)(4), your file must include a record of the tests conducted on pushout windows, emergency doors, and emergency door marking lights. Section 396.3(a)(2) requires these bus-specific safety features to be inspected at least every 90 days — and the test results have to live in the maintenance record.
This is exactly the kind of item that gets lost in a paper file — a 90-day interval that no one's tracking until an auditor asks for the log. Because it's unique to buses and passenger safety, it carries real weight in a passenger-carrier review. Book a demo to see 90-day emergency-exit tests tracked and logged automatically.
The Retention Rule for Your Bus Maintenance Records
Having the right records isn't enough if you purge them too early. Section 396.3 sets a specific retention window, and buses carry a few adjacent record types with their own clocks. Keep this straight or an otherwise-clean file becomes a gap.
The 396.3 file itself follows the "1 and 6" rule: one year in service plus six months after the bus leaves your control. That trailing six months trips people up — you sell or retire a bus and the obligation to hold its records doesn't end with it. Records must also be kept where the bus is housed or maintained and produced on demand.
The Common Mistakes That Turn a File Into a Violation
Most 396.3 findings aren't about buses in bad shape — they're about paperwork gaps in files for buses that are perfectly fine. Walk your own files against this list before an auditor does.
- ✗
A missing identity field
No tire size, no VIN, no unit number. A single absent data point in the identification record is enough to be cited.
- ✗
No documented schedule
Repairs are logged but nothing shows what's due and when. Without the schedule, there's no proof the program is systematic.
- ✗
History with gaps
A defect noted on a DVIR with no repair record closing it. The chain from problem to fix has to be visible and dated.
- ✗
No 90-day emergency-exit log
The bus-only pushout-window and emergency-door test record simply isn't there — a gap unique to passenger fleets.
- ✗
Records purged too early
Files for a sold bus shredded the day it left, ignoring the trailing six-month retention obligation.
- ✗
Scattered across systems
Identity in one binder, schedule in a spreadsheet, history in a drawer. If you can't produce it fast, it reads as no program at all.
Every one of these is a documentation problem, not a mechanical one — and every one disappears when each bus's identity, schedule, history, and tests live in a single file that can't lose a field. Book a demo to see a file that flags its own gaps before an auditor finds them.
Why a Bus CMMS Builds the File 396.3 Wants
The three-record file is simple in theory and brutal to keep by hand across a real fleet. The difference between a file that passes and one that doesn't usually isn't effort — it's whether the system won't let a record go missing.
- Identity fields entered once and never checked for gaps
- PM schedule in one tool, repair history in another
- 90-day emergency-exit tests tracked by memory, if at all
- Retention clocks watched manually, records purged too soon
- An audit request means assembling a file bus by bus, by hand
- Complete identity profile per bus — VIN, year, tire size, all of it
- PM schedule and dated repair history in one linked record
- 90-day emergency-exit tests scheduled, logged, and retained
- Retention handled automatically — nothing expires unnoticed
- Any bus's full 396.3 file exported for an investigator in one click
This is the Compliance & Safety core of BusCMMS: it doesn't just store records, it assembles the exact file 396.3 describes — identity, schedule, history, and bus-specific tests — so completeness is the default, not a monthly scramble.
A Safety Coordinator Who Stopped Dreading the File Request
"Our files weren't bad — they were scattered. Identity info on the equipment cards, PM schedules in a spreadsheet, repairs in the work-order binders. When an investigator asked for the file on a specific bus, it took me half a day to assemble it, and I always held my breath over the 90-day emergency-exit tests because nobody owned that log. Once every bus had one digital file, that request became a one-click export. Same records we always had — they just finally live in one place that won't drop a field."
That's the shift: the requirement never changes, but where the records live decides whether an audit is a non-event or a bad afternoon. Sign up free and give every bus one file that's always complete.
Bus Maintenance Records: The Bottom Line
Compliant bus maintenance records come down to one file per bus answering three questions: what is it, what's due, and what's been done — plus the bus-only 90-day emergency-exit test log and a retention window of one year in service plus six months after.
The requirement is simple; keeping it complete across a real fleet, by hand, is not. Put each bus's identity, schedule, history, and tests in one system that won't lose a field and holds the retention clock for you, and 396.3 stops being audit anxiety and becomes a one-click export.
Frequently Asked Questions
What must a bus maintenance file contain under 49 CFR 396.3?
A compliant file needs three records: vehicle identification (company or unit number if marked, make, serial number/VIN, year, and tire size — plus who furnished the bus if you don't own it); a maintenance schedule indicating the nature and due date of the inspection and maintenance operations to be performed; and a dated record of all inspections, repairs, and maintenance showing their date and nature. For buses there is also a fourth record under 396.3(b)(4): the results of tests on pushout windows, emergency doors, and emergency door marking lights, which must be inspected at least every 90 days.
Which buses need a 396.3 maintenance file?
The requirement is based on control, not ownership. You must keep a maintenance file for every bus you control for 30 consecutive days or more — that covers owned buses and leased or rented buses on terms longer than 30 days. Private motor carriers of passengers on a non-business basis are excepted, but for a school district, transit agency, or charter operator, essentially every bus in regular service needs its own file.
How long do I have to keep bus maintenance records?
The 396.3 maintenance file must be retained for one year while the bus is under your control, plus six months after the bus leaves your control — the "1 and 6" rule. Records must be kept where the vehicle is housed or maintained and produced on demand. Related records follow separate clocks: annual periodic inspection reports under 396.17 are kept 14 months, and daily DVIRs under 396.11 are kept three months. Selling or retiring a bus does not end the obligation to hold its records for that trailing six months.
What is the emergency-exit test record for buses?
Section 396.3(a)(2) requires pushout windows, emergency doors, and emergency door marking lights on buses to be inspected at least every 90 days, and 396.3(b)(4) requires the results of those tests to be kept in the maintenance record. It is a bus-specific requirement that fleets coming from a trucking background often overlook, and because it directly concerns passenger egress in an emergency, auditors reviewing passenger carriers look for it. Tracking the 90-day interval and logging each test is the practical challenge on paper.
How does a bus CMMS help with 396.3 recordkeeping?
A purpose-built bus CMMS like BusCMMS assembles the exact file 396.3 describes for each bus: a complete identity profile, a PM schedule showing what's due and when, a dated inspection and repair history built from work orders and DVIRs, and a log of 90-day emergency-exit tests. Because the records are structured and linked, a missing identity field or an unclosed defect is visible immediately rather than at audit time, retention is tracked automatically so nothing expires unnoticed, and any bus's full file exports in one click when an investigator asks — turning recordkeeping from a manual scramble into an audit-ready default.
