FMCSR 392.62C2: Bus Exit Obstructed — Driver Q&A

Yes, there is a significant risk. Across our inspection records, 58.3% of 392.62C2 citations result in an out-of-service order. That is much higher than the national average of 31.4% across all FMCSR codes. Of the 12 all-time citations in our database for this violation, 7 were placed out of service on the spot. If an inspector finds your exits blocked by baggage or freight, you should expect a strong possibility of being unable to operate until the obstruction is cleared.

First priority: clear all baggage and freight from exit paths immediately. Inspect every emergency exit and door to confirm nothing blocks passenger egress. Second: review your pre-trip and load-planning procedures to prevent this in the future. The data shows co-occurring violations often involve fatigue (392.2RG and 392.2W appear in 3 shared inspections) and medical certificate issues (391.41APC in 1 shared inspection), so examine whether time management or driver health played a role. Document the correction in writing and take photos showing clear exits before resuming operations.

This is a serious but relatively uncommon violation. It ranks 2132nd out of 3,036 FMCSR codes by citation volume, meaning most drivers never encounter it. However, its out-of-service rate of 58.3% puts it well above the all-FMCSR average of 31.4%. The peer codes in the unsafe-driving category—like 392.2 (operating while ill/fatigued)—have OOS rates ranging from 0.0% to 2.4%. At 58.3%, this obstruction violation carries one of the highest enforcement consequences in its class.

Texas accounts for the majority of recent enforcement. In the last 180 days, Texas had 4 citations for 392.62C2, with 3 resulting in out-of-service orders (75.0% OOS rate). Over a 12-month period, our records show 9 total citations nationwide, and only 3 in the last 90 days, indicating the violation is not increasing in frequency. If you operate in Texas, stay especially vigilant about exit clearance during pre-trip inspections and load verification.

In the last 90 days, our data shows 392.62C2 frequently co-occurs with driver fatigue violations (392.2RG in 2 shared inspections and 392.2W in 1 shared inspection). This pattern suggests rushed loading or inadequate pre-trip procedures tied to tired operation. One citation also paired with a missing medical certificate (391.41APC). Another common co-occurrence is equipment defects like brake tubing issues (393.45B2UV) and fifth-wheel problems (393.71H). This suggests inspectors finding exit obstructions often flag other safety gaps on the same vehicle.

Over all time in our database, three carriers have been cited twice for this violation: MEXABUS LLC (USDOT 4092902), USA MEX INC (USDOT 2574554), and DURHAM SCHOOL SERVICES LP (USDOT 350651). Several other carriers—including FLO CHARTER LLC, KAUFMAN TOURS LLC, and SCION TOURS LLC—each have one citation. The most frequently cited vehicle makes are MCIN (4 citations), THOM (3 citations), and VOLV (2 citations). These numbers reflect a small but consistent pool of enforcement events across the carrier base.

Enforcement is volatile but generally low. In the last 12 months, citation volume ranged from 0 (multiple months) to 3 in February 2026. The 90-day count stands at 3 citations, suggesting no clear upward trend. However, the out-of-service rate in recent months remains high: 5 of 7 recent citations (71.4%) resulted in roadside removal. This means when inspectors cite this violation, they are likely to put the bus out of service, so prevention is more important than waiting for enforcement rates to change.

Yes, you can submit a DataQs (FMCSA Safety Management System challenge) within 90 days of the citation. A 392.62C2 violation is based on a physical, observable condition—obstructed exits—making it a good candidate for challenge if: the obstruction was not actually blocking egress, the baggage/freight was secured legally, or the inspector's measurement or documentation was inaccurate. Gather photos from your pre-trip, load photos, and weight distribution records. DataQs success depends on evidence, not argument, so document everything you can before the window closes.