A missed signal, overspeed event, switching collision or work-zone incursion may raise fatigue questions. Federal Hours of Service law limits duty for defined railroad occupations, but regulatory compliance does not necessarily establish that a person was alert, and an excess-service entry does not by itself prove causation. The useful sequence is classify the employee, calculate every duty segment, verify real rest opportunity and compare the timeline with operational performance. This is general education, not legal advice.
Which Hours of Service rule applies?
49 U.S.C. Chapter 211 defines train, signal and dispatching service employees and sets occupation-specific limits. FRA's 49 CFR Part 228 covers records and related requirements, including separate provisions for train employees of commuter and intercity passenger railroads. Do not apply a freight conductor's formula to a dispatcher or passenger-service employee.
| Employee category | General federal framework | Classification questions |
|---|---|---|
| Train employee | Section 21103 generally includes a 12-consecutive-hour ceiling and 10 consecutive hours off in the prior 24 hours, plus monthly and consecutive-day rules | What counted as covered service, waiting or deadhead time, and was passenger service involved? |
| Signal employee | Section 21104 generally limits covered duty to 12 consecutive hours and requires 10 consecutive hours off, with detailed travel and emergency rules | Was the person installing, repairing or maintaining a signal system, and was a claimed emergency actually within the statute? |
| Dispatching service employee | Section 21105 generally uses a 9-hour limit where two or more shifts are employed and 12 hours where only one shift is employed | What facility and shift arrangement applied, and was the employee performing dispatching service? |
| Passenger train employee | Part 228 includes a passenger-service regime and fatigue-mitigation requirements that can differ from the general train-employee rule | Was the service commuter or intercity passenger, and which schedule and analysis governed? |
These are only starting points. Time spent waiting for or riding deadhead transportation, interim release, commingled service, multiple jobs, emergency extensions and consecutive starts can be treated differently. Use the current statutory text and records for the exact date; a quick “twelve hours on, ten off” calculation may omit the issue that matters.
Records that reveal the full duty cycle
The carrier's Hours of Service entry is essential but should be verified. It may not convey a late crew call, interrupted rest, a long ride to lodging, mandatory training, another service period or an abrupt schedule rotation. A neutral chronology separates legal time-on-duty calculations from the human question of meaningful sleep opportunity.
Useful sources can include:
- electronic Hours of Service entries and any excess-service report;
- crew-call recordings, call windows, tie-up records, payroll and assignment history;
- deadhead orders, van logs, lodging arrival and departure records;
- dispatch audio, radio traffic, event-recorder, inward-facing video and PTC alerts;
- schedule changes, consecutive starts, training and mandatory communications;
- the railroad's fatigue-management plan and relevant local policies.
Personal medical or sleep information should be handled through lawful discovery, not public speculation. Observable operational signs — delayed response, repeated acknowledgement, braking input, throttle changes or PTC warnings — may be compared with the schedule by qualified investigators. The black-box and camera evidence guide explains those digital sources.
From long hours to legal causation
An Hours of Service violation is not synonymous with a fatigue-caused accident. The claimant must connect scheduling or fatigue to the act that caused injury: missing a restriction, failing to stop, releasing authority incorrectly or making an unsafe shove. Conversely, a technically compliant employee may still have had little practical sleep because of irregular calls, circadian disruption or mandatory activity known to the carrier.
The type of claimant changes the case. An injured railroad employee may assert a FELA theory based on unsafe scheduling or coworker negligence. A passenger, motorist or pedestrian generally uses the applicable state claim against the responsible carrier or agency. Government notice rules may apply to public transit. Accurate Hours of Service reporting is itself protected activity under 49 U.S.C. § 20109.
Worked evidence example
Hypothetical: a freight engineer misses a temporary speed restriction and enters a curve too fast. The official record shows a lawful start after ten hours off. Crew-call data, however, shows the employee was called twice during that period for assignments later canceled, and van records show a late arrival at lodging. Inward-facing video shows repeated yawning; event data shows no braking response until a PTC alert.
The evidence does not automatically prove negligence or a statutory violation. It separates nominal off-duty time from possible sleep opportunity and connects the schedule to observable performance. Investigators must still confirm whether the calls came from the carrier, how the law treats them, whether the restriction was properly communicated, what PTC did and whether another cause explains the response.
A fatigue-evidence checklist
- Identify each involved employee's actual function instead of assuming one rule applies to the whole crew.
- Preserve duty, call, deadhead, lodging and assignment records for multiple days before the event.
- Request raw operational data and video with a defined time window before routine overwriting.
- Separate verified facts from impressions about whether someone looked tired.
- Compare clocks across payroll, calls, radio, dispatch, event-recorder and PTC systems.
- Check FELA, state limitation and any public-agency notice deadline independently.
For technology that may record or intervene in overspeed, collision and work-zone events, continue with the Positive Train Control evidence guide. Railroad employees should also review the FRSA reporting-protection guide if accurate hours or a safety report triggers discipline.
Frequently asked questions
Does compliance with Hours of Service rules prove a crew was rested?
No. Legal eligibility for duty and actual alertness are different questions. An investigation may also examine call timing, sleep opportunity, deadhead travel, schedule changes, lodging, workload and signs of fatigue in operational data.
Do all railroad employees have the same duty-time limit?
No. Federal law distinguishes train, signal and dispatching service employees, and separate passenger-service regulations may apply. The employee's function and each segment of service must be classified before calculating time.
Which records are most useful in a railroad fatigue investigation?
Hours-of-service records should be compared with crew calls, payroll, dispatch and radio logs, deadhead transportation, schedule history, event-recorder and PTC data, video and witness accounts. No single source necessarily captures the full duty cycle.