Prevention FAQ — FMCSR 392.62C2: Bus Exit Obstructions

Fleet safety guidance for preventing exit obstruction citations. Based on 12 all-time citations and 58.3% OOS rate across 13M inspections.

OOS Eligible
Severity Weight
1
OOS Eligible
Yes
BASIC Category
Vehicle Maintenance
Code System
FMCSR
Code:
392.62C2
Code System:
FMCSR
BASIC Category:
Vehicle Maintenance
OOS Eligible:
Yes
Severity Weight:
1
Violation Group:
General Securement

Ranks #2,155 of 3,146 FMCSR codes by citation frequency • OOS rate of 58.3% is above the FMCSR-wide average of 33.3%.

Violation Description

Bus - Exit(s) obstructed by baggage/freight

Prevention FAQ for Fleet Managers

Pre-trip discipline, inspector focus, and root-cause fixes

What specific exit-obstruction scenarios do FMCSR inspectors focus on during roadside checks?

Our inspection records show 12 all-time citations for this code, with Texas accounting for 4 of those in the last 180 days. Inspectors conduct a physical walkthrough of the bus during pre-operation or post-accident inspections, checking that all emergency exits, passenger doors, and evacuation routes are completely clear of baggage, cargo, or freight. They verify that overhead racks, under-seat storage, and aisle pathways do not block or partially impede any marked exit. In Texas, where 75% of cited vehicles were placed out-of-service, enforcement appears particularly strict about verifying exit accessibility before departure. Inspectors will also check that exit signage is visible and that door handles are unobstructed.

What should be on the pre-trip exit-clearance checklist for each bus departure?

Every pre-trip inspection must include a mandatory section confirming all exits are unobstructed. The driver should verify: (1) no baggage or cargo blocking any emergency exits or marked emergency windows; (2) aisle pathways are completely clear from front to rear; (3) passenger doors (side exits) open freely without striking luggage; (4) overhead compartments are secured and not bulging into the aisle; (5) under-seat storage does not extend into walking space; (6) exit signs are illuminated and unobstructed; (7) emergency equipment (extinguisher, first aid) is mounted and not blocking exits. Drivers must initial and date this checklist before each trip. For multi-day or charter routes, this check should repeat before each passenger boarding. Document findings on the vehicle's daily inspection report.

What documentation must drivers and dispatch retain to defend against this citation?

Maintain completed pre-trip inspection forms signed by the driver before departure, with a specific exit-clearance checklist section. Retain dated photographs of the bus interior—showing all aisles, emergency exits, and cargo areas—taken before passenger loading or at shift start. Keep dispatch logs noting route assignments and passenger/cargo manifests so you can demonstrate that baggage and freight were loaded and secured according to protocol. Store vehicle maintenance records showing any recent repairs to doors, hinges, or cargo racks. If cited, photograph the exact condition noted by the inspector and document the corrective action taken. These records are crucial if you file a DataQs challenge, as they prove procedural compliance at the time of alleged violation.

What root-cause patterns emerge from violations that co-occur with 392.62C2?

Across our inspection records, the most frequent co-occurring citation is 392.2RG (operating while ill or fatigued), appearing in 2 of the last 90-day inspections flagged for exit obstruction. This suggests drivers may not be conducting careful pre-trip checks when fatigued, or dispatchers are assigning trips without verifying driver fitness. The second pattern: medical certificate violations (391.41APC) appeared alongside exit obstruction, indicating potential driver-competency issues or oversight in the hiring/verification process. Third, we see power steering and brake defects (393.209E, 393.45B2UV) co-occurring, which may reflect broader vehicle-maintenance shortcuts that also skip exit-clearance verification. Root-cause analysis question for your fleet: Are fatigued drivers performing abbreviated pre-trip checks? Are maintenance teams inspecting exits during routine service?

How should we verify repairs or corrective loading practices before a cited bus returns to service?

After a citation, conduct an immediate full vehicle inspection with a supervisor or safety officer present—not just the driver. Verify that all emergency exits, doors, and evacuation pathways are completely clear and operational. Test door opening and closing under load (simulate full passenger weight if possible). Re-photograph the interior with all exits clearly visible. If cargo-loading procedure was the issue, retraining the loading crew is mandatory; document attendance. Review and revise the cargo manifest system to ensure freight weight is distributed to prevent overhead or under-seat overflow into aisles. Have the driver sign a new pre-trip checklist form confirming exit clearance. Only after supervisor sign-off should the vehicle resume revenue service. Retain the corrective-action report in the vehicle maintenance file for at least three years.

What should the fleet review after receiving a 392.62C2 citation?

Conduct a post-event review meeting involving the cited driver, the dispatcher, and the maintenance supervisor. Review the exact condition documented by the inspector and cross-reference your pre-trip checklist from that day—was it completed? If not, determine why. Analyze loading patterns: does baggage exceed the designed compartment capacity? Are passengers or cargo handlers placing items in emergency aisles? Check whether the driver had prior fatigued-driving citations (392.2RG appeared in 2 of our recent co-occurring inspections), which could explain rushed or incomplete pre-trip checks. Assess whether your pre-trip form was being followed at all. Update your checklist if it was vague or incomplete. Document the corrective actions taken and retrain affected personnel within 10 days. Flag the driver for additional pre-trip observation over the next 30 days.

How does this citation affect the carrier's CSA Vehicle Maintenance BASIC score?

A 392.62C2 citation is a non-OOS violation (not placed out-of-service), but our data shows it carries a 58.3% OOS rate when cited—well above the all-FMCSR average of 31.4%—indicating FMCSR considers it a serious safety issue. When a citation does result in OOS placement, it contributes directly to your Vehicle Maintenance BASIC score. Even non-OOS citations accumulate severity points. Ranked #2132 of 3,036 FMCSR codes by citation volume, this is a lower-frequency violation, but the disproportionate OOS rate means inspectors view exit obstruction as a critical safety defect. Repeated citations will erode your Safety Management Fundamentals BASIC and can trigger a compliance review. A single citation may not crash your score, but clustered violations across your fleet indicate systemic loading or pre-trip-inspection failures that FMCSA will scrutinize.

What driver training topics should the fleet prioritize to prevent this violation?

Implement mandatory annual training covering: (1) emergency evacuation procedures—drivers must be able to explain every exit to passengers; (2) pre-trip inspection protocols with emphasis on exit verification as the first and non-negotiable step; (3) coordination with dispatch and cargo handlers to ensure baggage is loaded only in designated compartments, never in aisles or emergency areas; (4) recognition of fatigue and procedures for requesting route delays if fatigued (since 392.2RG co-occurs in our data); (5) documentation completion—drivers sign pre-trip forms, not routine paperwork. Conduct ride-alongs quarterly where a supervisor observes the driver's pre-trip routine and provides real-time feedback. Use photo-based scenario training showing obstruction examples and correct loading. For new drivers, require a supervised trip before solo operation. Document all training attendance in driver qualification files.

When should we consider filing a DataQs challenge if we believe the citation was incorrect?

File a DataQs challenge only if: (1) your photographic and inspection documentation clearly shows all exits were unobstructed before the inspection (photograph date/timestamp must align with citation date); (2) the inspector's documentation contradicts standard inspection procedures (e.g., cited exit obstruction that doesn't appear in any photo or maintenance record); (3) the vehicle was not in revenue service on the citation date, or the cargo/baggage manifest proves the cited load condition was impossible. Do not challenge simply because you disagree with the severity. Include your pre-trip checklist, dated photographs of the interior, dispatch logs, and signed statements from the driver and any witnesses. Submit within 90 days of the citation date. Without photo or logistical evidence of non-compliance, a challenge will likely fail and delay closure.

How often should the fleet conduct self-audits for exit-obstruction risk across the bus fleet?

Our data shows 3 citations in the last 90 days and 9 in the last 12 months, indicating a steady but low-volume issue. However, the 58.3% OOS rate suggests severity is high when detected. Conduct a full fleet self-audit (all buses) quarterly—photograph all exits, test door operation, and verify cargo-area capacity limits. Between quarterly audits, inspect a rotating sample of 20% of the fleet monthly during routine maintenance. After any citation, increase audit frequency for that vehicle and similar models (our top cited makes are MCIN with 4 citations, THOM with 3, and VOLV with 2—prioritize these during inspections). Train dispatch and maintenance staff to conduct informal visual checks during each fuel stop on long routes. If your fleet experiences a second citation within 12 months, escalate to weekly supervised pre-trip checks for all buses until compliance is verified over two consecutive weeks.

Last updated: 2026-04-20T16:45:34.533Z Guidance derived from TruckCodex inspection data Read the full article → Quick Q&A →

Top Enforcing States

Where 392.62C2 is most commonly cited (last 180 days)

1. Texas
3
OOS 66.7%

Data sources & freshness

TruckCodex aggregates official public-sector datasets. See the Source registry for dataset-level coverage and the Freshness log for last-import timestamps.

Census, SAFER, SMS, Licensing & Insurance (L&I), roadside inspections, crashes, and authority history.

Refreshed daily.

Vehicle recall campaigns, defect investigations, and consumer safety complaints (SCRS).

Refreshed daily.
EIA

Retail diesel and gasoline price history and state fuel-tax tables.

Refreshed weekly.

Cross-border carrier registry and Canadian recall campaigns where applicable.

Refreshed weekly.

TruckCodex is an independent aggregator; it is not affiliated with FMCSA, NHTSA, EIA, or Transport Canada. Always verify compliance-critical information directly with the originating agency.