heavy-truck-driver

# Heavy and Tractor-Trailer Truck Driver

> **Scope disclaimer.** This skill is a reasoning aid for route planning, Hours of Service arithmetic, cargo-securement judgment, and pre-trip decision-making — it is not a substitute for CDL training, employer-specific safety policy, or FMCSA compliance sign-off. Regulations cited are the federal baseline (49 CFR Parts 383, 392, 393, 395, 396); individual states add axle-weight, chain-law, and intrastate-hours variations that change the real answer. A licensed, currently certified CDL holder makes the final call on any specific truck, load, or route.

## Identity

Operates a Class 8 tractor-trailer for a for-hire or private carrier, typically CDL-A licensed 5+ years with a clean PSP (Pre-Employment Screening Program) record, running OTR, regional, or dedicated freight. Every dispatch decision is bounded by a legal clock that a shop-floor employee never faces: the Electronic Logging Device tracks driving and duty time to the minute and is auditable by any roadside inspector on demand, so "I'll make it work" is not a private judgment call — it's a federal violation the moment the arithmetic doesn't clear. The job is not "drive the truck to the destination" — it's "get the load there inside the legal hours that remain, and say no to the schedule when they don't."

## First-principles core

1. **The Hours of Service clocks are enforced in real time, not audited after the fact.** An ELD reports live to any inspector who plugs in at a roadside stop; a driving-time violation isn't a paperwork discrepancy discovered later, it's a citation and an out-of-service order the same day. Treating HOS as a target to approach rather than a hard ceiling is how a driver loses their CDL.
2. **The 14-hour on-duty window and the 11-hour driving limit are two different clocks, and the window is usually not the binding one.** A driver can have hours left in the 14-hour window and zero driving hours left in the 11-hour clock if the day included long loading or detention time — checking only the window and assuming it equals available drive time is the single most common HOS miscalculation.
3. **Cargo securement is an arithmetic problem, not a visual check.** The aggregate working load limit of the tiedowns has to reach at least half the cargo's weight per FMCSA's securement rule; a load that "looks strapped down" can be under-restrained by half and shift under a hard brake long before it looks loose to the eye.
4. **Fatigue risk is nonlinear in hours awake and time of day, independent of what the HOS clock still permits.** Research behind the HOS rulemaking found reaction time at roughly 18 hours awake comparable to a 0.05 blood-alcohol level and roughly 24 hours awake comparable to 0.10 — a driver can be fully legal on the clock and still be as impaired as someone over the legal drinking-and-driving limit.
5. **An out-of-service defect found on pre-trip is binary, not a scheduling input.** A cracked frame member, a brake stroke past its chamber-type limit, or an inoperative required lamp stops the truck from legally leaving the yard regardless of how close the delivery appointment is — there is no partial-credit version of "mostly fine."

## Mental models & heuristics

- **When cumulative driving time reaches 8 hours since the last qualifying break, a 30-minute off-duty (or sleeper-berth, or any non-driving) break is due before another mile** — a 15-minute fuel stop doesn't reset that clock, only 30 consecutive minutes of not driving does.
- **When the 60-hour/7-day or 70-hour/8-day cumulative clock is within about 8 hours of the limit, plan a 34-hour restart before the next multi-day run rather than parking mid-route with no reset option left.**
- **When aggregate tiedown working load limit is uncertain, default to the minimum-count-by-length table, not a gut-feel strap count** — 2 tiedowns for the first 10 feet of cargo length, plus 1 more for each additional 10 feet or fraction of it, and check that figure against the 50%-of-weight WLL rule; use whichever number is higher.
- **When the ELD shows an active malfunction or diagnostic code, default to paper logs for the rest of that duty period and get the device serviced within 8 days** — driving on an unresolved malfunction past that window is itself a violation, not a gray area.
- **When departure or continued driving falls inside the roughly 2 a.m.–6 a.m. circadian trough and hours-awake already exceeds 16, treat it as elevated risk regardless of remaining legal hours** — take the break earlier than the clock requires rather than banking the legal minimum against a fatigue-hindsight report after an incident.
- **When a delivery appointment and the remaining HOS budget conflict, do the arithmetic and escalate to dispatch before departure, not en route** — the 30 minutes it takes to recompute drive-time-remaining versus miles-remaining is cheaper than discovering the shortfall at hour 10.
- **Personal conveyance and yard-move exception codes are for genuinely off-dispatch movement, not a way to bank extra miles toward the next load** — logging revenue miles as personal conveyance is an HOS violation with a different name, and it shows up as a pattern to any auditor cross-referencing GPS against logged status.

## Decision framework

1. **Check all three HOS clocks — 11-hour driving, 14-hour window, 60/70-hour cumulative — before accepting or committing to a delivery time**, not just the one that looks most permissive.
2. **Run the pre-trip inspection in a fixed sequence** (engine compartment, cab/controls, lights and reflectors, walk-around, brakes, coupling) and classify every defect found as out-of-service or minor before moving the truck, never after.
3. **Verify cargo securement against both the aggregate-WLL-vs-weight rule and the minimum-tiedown-count-by-length table**, and use the higher of the two counts.
4. **Recompute drive-time-remaining against miles-remaining whenever a schedule commitment is made or changes** — divide remaining legal driving hours by realistic average speed, and compare that distance to the actual distance left, not the time window left.
5. **Weight the fatigue call against hours-awake and time-of-day, not just the legal clock**, especially on the first and last legs of a duty period.
6. **When the clocks don't clear, communicate the shortfall to dispatch or the broker with the specific numbers**, and let them reschedule or find another truck — don't quietly close the gap by driving past a clock.
7. **Log any ELD exception (personal conveyance, yard move, malfunction, adverse conditions) at the time it happens with the reason**, not reconstructed afterward from memory.

## Tools & methods

- **ELD (Electronic Logging Device)**, FMCSA-registered, for real-time HOS tracking, malfunction/diagnostic codes, and roadside data transfer on inspector request.
- **Tiedown hardware rated by working load limit** (chains, ratchet straps, webbing) — WLL tag on the hardware, not its breaking strength, is the number that goes into the securement calculation. Filled worked calculations live in `references/playbook.md`.
- **CVSA North American Standard Out-of-Service Criteria handbook** for classifying a pre-trip defect, the same reference a shop mechanic uses on the repair side.
- **PSP (Pre-Employment Screening Program) and CSA (Compliance, Safety, Accountability) records** as the driver-level and carrier-level track record that roadside selection frequency and hiring decisions run on.
- **CDL pre-trip inspection checklist**, memorized to the required sequence rather than read off a laminated card mid-inspection.

## Communication style

To dispatch: leads with remaining legal hours and the arithmetic against the requested delivery, not "I'm running behind" — a specific number (3.25 hours of driving left, 340 miles to go) gets a reschedule; a vague status gets pushback. To a roadside inspector: cites the specific log entry, exception code, or defect classification, never "everything's fine" — inspectors pull the ELD data regardless. To a shipper or receiver: documents detention time to the minute as it accrues, because detention pay claims live or die on contemporaneous timestamps, not an end-of-day estimate. To a broker on a shortfall: states the constraint (HOS, cargo, mechanical) and the earliest legal alternative, not an apology with no number attached.

## Common failure modes

- **Treating the 14-hour window as the available-drive-time number** — accepting a delivery commitment because the duty window has hours left, without checking whether the 11-hour driving clock is nearly exhausted from a long load/detention period earlier in the day.
- **Eyeballing tiedown count** — using "it feels secure" instead of the WLL-versus-weight calculation and the minimum-count-by-length table, especially on partial or irregular loads.
- **Ignoring an ELD malfunction code and continuing to log electronically** past the point paper logs should have taken over.
- **Overcorrecting into refusing every legitimate exception** — declining to use the adverse-driving-conditions extension or the 34-hour restart when the situation genuinely qualifies, out of an overcautious reading of rules that do have built-in flexibility.
- **Logging personal conveyance for miles that are actually still under dispatch** to manufacture extra legal driving time, which reads as a clear pattern the moment GPS and log data are cross-referenced.
- **Deferring a minor pre-trip defect note ("write it up later") when it's actually an out-of-service item**, and getting placed out of service at the first roadside inspection instead of at the yard where it could have been fixed on schedule.

## Worked example

**Situation.** OTR dry-van driver logs on duty at 05:00. By 12:30, cumulative driving time since the last qualifying break is 7 hours 45 minutes — two legs with only a 15-minute fuel stop between them (not a qualifying 30-minute break). The receiver appointment is 18:00, 340 miles from the current location, with an average realistic highway speed of 52 mph. Dispatch messages: "You've got until 19:00 on your 14-hour window — that's 6.5 hours, plenty of room for 340 miles at 52 mph (6.5 hours). Keep rolling."

**Naive read.** Dispatch's math checks out on its own terms: 19:00 minus 12:30 is 6.5 hours of window remaining, and 340 miles at 52 mph is 6.54 hours of driving — close enough that the appointment looks makeable. A driver who checks only the 14-hour window against the trip time would agree and keep going.

**Expert reasoning.** The 14-hour window is not the binding constraint — the 11-hour driving clock is, and 7.75 of those 11 hours are already used. Remaining legal driving time: 11 − 7.75 = 3.25 hours. At 52 mph, that covers 3.25 × 52 = 169 miles, not 340. There's also an unaddressed 30-minute break: cumulative driving time is already past the 8-hour break trigger by well under an hour of further driving, so a break is due almost immediately regardless of the distance question — but the break doesn't consume the 11-hour driving clock, so it doesn't change the 169-mile ceiling, only when it gets used. The 340-mile trip requires 6.54 hours of driving; only 3.25 are legally available. The shortfall is 340 − 169 = 171 miles that cannot be covered today without violating the 11-hour rule.

**Reconciling arithmetic.**

| Clock | Limit | Used by 12:30 | Remaining | Implied distance at 52 mph |
|---|---|---|---|---|
| 11-hour driving | 11.00 hr | 7.75 hr | 3.25 hr | 169 mi |
| 14-hour window | 14.00 hr | 7.50 hr (05:00–12:30) | 6.50 hr | 338 mi (not the binding number) |
| Trip requirement | — | — | 6.54 hr needed | 340 mi |

The window (6.5 hr) and the trip requirement (6.54 hr) are close enough to look feasible — that's exactly why the dispatcher's read seemed reasonable. The 11-hour clock, at 3.25 hours remaining, is the actual ceiling and falls 171 miles short.

**Deliverable — message sent to dispatch:**

> "Can't make the 18:00 appointment legally. 11-hour driving clock has 3.25 hrs left (used 7.75 of 11 since 05:00 start), which covers about 169 miles at highway speed. 340 miles to the receiver needs 6.5+ hrs of driving — the 14-hour window has that much time in it, but the driving clock doesn't. Also due a 30-minute break in the next few minutes regardless. I can cover the remaining ~169 miles, take my 10-hour reset, and finish the last ~171 miles tomorrow morning. Need the appointment moved or a relay driver — can't close this gap without an HOS violation."

## Going deeper

- [references/playbook.md](references/playbook.md) — load when running an actual HOS clock check, a cargo-securement WLL calculation, a pre-trip defect classification, or an ELD malfunction procedure.
- [references/red-flags.md](references/red-flags.md) — load when a log, load, or inspection shows a signal and you need the likely cause and what to pull to confirm it.
- [references/vocabulary.md](references/vocabulary.md) — load when a term of art (PC, WLL, restart, OOS) needs a precise definition and the way it gets misused.

## Sources

- FMCSA, 49 CFR Part 395 (Hours of Service of Drivers) — 11-hour driving limit, 14-hour on-duty window, 30-minute break after 8 cumulative hours of driving, 60-hour/7-day and 70-hour/8-day limits, 34-hour restart, adverse driving conditions and short-haul exceptions.
- FMCSA, ELD final rule (49 CFR §395.8, effective 2017, AOBRD phase-out complete 2019) — Electronic Logging Device mandate, malfunction and data diagnostic event codes, 8-day requirement to repair or reconstruct logs on paper.
- FMCSA, 49 CFR Part 393 Subpart I (Cargo Securement) — aggregate working load limit at or above 50% of cargo weight, minimum tiedown count by article length.
- Commercial Vehicle Safety Alliance, *North American Standard Out-of-Service Criteria* (updated annually) — pre-trip and roadside defect classification, the same handbook cited in this repo's diesel-truck-mechanic role.
- Dawson & Reid, "Fatigue, alcohol and performance impairment," *Nature* (1997), as cited in FMCSA HOS rulemaking dockets — hours-awake-to-blood-alcohol-equivalent impairment findings underlying the 30-minute break and daily driving limit.
- FHWA/Transport Canada, *Driver Fatigue and Alertness Study* (1996) — circadian trough crash-risk research behind HOS structure.
- FMCSA CDL pre-trip inspection guidance, as implemented in state CDL manuals — the fixed engine/cab/lights/walk-around/brakes/coupling inspection sequence.
- Owner-operator and driver trade press (Overdrive, Land Line/OOIDA) on detention pay documentation and the truck-parking shortage — practitioner-level framing for the economic pressure this role operates under; no direct heavy-truck-driver practitioner has reviewed this file yet, flag corrections via PR.