A post-event crane inspection is the step the schedule pressures you to skip. The morning after a storm, the pressure is to get back to work. The crane looks the same as it did on Friday, nothing is obviously bent, and the schedule already lost two days to weather. That combination is how damaged equipment returns to service — not through negligence, but because the damage that matters is rarely the damage you can see from the ground.
Event-driven inspections are the layer most often missing from a written program, because they cannot be put on a calendar. They are triggered by things happening, and things happen at inconvenient times.
What the regulation requires
29 CFR 1926.1412 sets out inspections triggered by conditions rather than by schedule. Equipment that has had a modification or addition affecting safe operation requires inspection by a qualified person under 1412(a). Repaired or adjusted equipment requires inspection under 1412(b). Equipment used in severe service or subject to conditions that could adversely affect safe operation requires appropriate inspection under 1412(h).
That last provision is the one covering weather and impact events, and its breadth is deliberate. The standard does not enumerate every event because it cannot — it places the obligation on the employer to recognize that something happened and to respond proportionately.
ASME B30.5 is more explicit for mobile cranes, and manufacturer manuals frequently specify inspection requirements after defined wind speeds, lightning strikes, and shock loading events. Those manufacturer criteria are the practical benchmark, and they are usually stricter than anything in the CFR.
The events that should trigger a post-event crane inspection
- Wind exceeding the in-service or out-of-service limit for that machine, whether or not the crane was operating.
- Lightning strike to the crane or to nearby structure.
- Collision — the crane struck something, or something struck the crane, including a load swinging into structure.
- Shock or dynamic loading — a load picked up suddenly, dropped and caught, or dragged.
- Two-blocking, even where nothing visibly parted.
- Overload, including any recorded on the LMI’s log whether or not anyone reported it.
- Outrigger settlement or a near-tip, however brief.
- Flood or immersion of any component.
- Seismic activity above a nominal threshold, particularly for fixed and tower equipment.
- Transport damage — a machine that shifted on a trailer or struck an overhead on the road.
Wind: the limits and what they mean
Three wind numbers matter and manufacturers publish all three: the in-service limit above which lifting stops, the out-of-service limit the machine can survive when properly secured, and the securing procedure that has to be complete before that second number arrives.
The inspection question after a wind event is whether the machine experienced forces beyond what it was configured to take. A mobile crane left with the boom up in a gust exceeding the stowed limit has been loaded in a direction and magnitude the structure does not see in normal work. A gantry that moved on its rails during a storm has experienced impact loading at whatever stopped it.
Look at the boom and its connections, the boom hoist system and pendants, the turntable bearing and its bolting, outrigger and stabilizer condition, and any securing hardware — rail clamps, storm pins, tie-downs — that may have been loaded or may have failed silently. On tower cranes, weathervaning behavior, slew brake condition, and tie connections all belong in the scope.
Lightning is the event with the least visible evidence
A lightning strike can leave almost no external mark and cause substantial damage. Current passing through the machine finds ground through bearings, wire rope, and structural connections, and it produces localized heating and arcing at every interface it crosses.
The specific concerns are pitting and arc damage in the turntable bearing races, damage to wire rope where current jumped between rope and sheave, degraded electrical and electronic systems including the load moment indicator and anti-two-block circuits, and arc strikes on structural members that create hard, brittle spots and crack initiation sites.
Manufacturer guidance after a strike is frequently prescriptive and frequently expensive — some require bearing inspection or replacement. It is also the guidance most likely to be ignored, because the machine starts and runs normally afterward. Electronic damage in particular can present as intermittent faults weeks later, which is why documenting the strike matters even when the immediate inspection finds nothing.
Impact and shock loading
Collisions and shock loads put forces into the structure through load paths that normal operation does not use. A boom struck laterally has been loaded in a direction it has minimal capacity to resist. A load dropped and caught applies a dynamic multiple of its static weight.
The inspection concentrates at connections and stress concentrations: boom section joints and pins, lattice chord and lacing members, the turntable bearing and its bolts, outrigger boxes and their welds, and the hook block and rope. Coating cracks along weld toes are the leading indicator, and anything suspect goes to non-destructive testing rather than to a judgment call.
After a two-blocking event, the wire rope is replaced rather than assessed, and the hook block, sheaves, and boom tip are examined for damage. That is not a conservative interpretation — it is the standard response, because rope that has been crushed against a stop has damage that inspection cannot reliably bound.
The event nobody reported
A major fraction of the events that should trigger inspection are never reported. Nothing broke, the crew was embarrassed, the schedule was tight, and by the end of the shift it had not happened.
Two things catch these. The first is the equipment’s own logs — modern LMI systems record overload events, peak loads, and override use, and reading that log during a routine inspection surfaces events nobody mentioned. The second is the physical record: bent floats, bowed mats, fresh coating cracks, and scuffs on structure are all evidence of forces the machine was not supposed to see.
Finding that pattern changes the conversation from an equipment finding to a reporting one. A crew that does not report near-misses is a program problem, and it is worth addressing separately from whatever the inspection found.
Who performs it and what scope
Event-driven inspections generally require a qualified person, because the judgments involved are structural and the outcome is a return-to-service determination. The scope is set by the event: a minor impact to a non-load-bearing area may warrant a focused examination, while a lightning strike or a suspected overload warrants something close to a full full inspection.
What is not acceptable is a competent-person walkaround substituting for the determination. The question after an event is not whether the machine looks serviceable — it is whether the structure retains its capacity, and that is a qualified person’s call.
Documentation, and why this record matters more than most
Post-event inspection records are read closely, because their existence sets up that the organization recognized the event and responded. The record should state what happened, when, and in what conditions. What was inspected and to what criteria. The findings. The disposition and who authorized return to service. And any restrictions imposed.
Recording the event itself is as important as recording the inspection. A file that jumps from a routine monthly to a repair order with nothing explaining the gap invites the worst interpretation. This is the same principle that governs the monthly record — a documented finding with a documented closure is worth more than an unbroken run of clean forms.
Building the trigger list before you need it
The practical failure here is that nobody decides in advance what counts. At 6 a.m. after a storm, with the crew waiting, is a poor moment to determine whether last night’s gusts exceeded the stowed limit.
Write the triggers into the program: the specific wind speeds for each machine from the manufacturer’s manual, the response to a lightning strike within a stated distance, the requirement to report any contact or shock loading, and who has authority to call for the inspection. Add a weather data source so the wind speed is a fact rather than an argument.
Seasonal preparation belongs alongside it — hurricane season planning for coastal operations and cold-weather procedures where relevant. Both are considerably cheaper to arrange in advance than to improvise.
Overhead and fixed equipment has its own event list
Events for overhead cranes look different from mobile equipment because the machine cannot leave. Collisions between cranes on a shared runway, a load striking building steel, a derailment, a hoist run into the upper limit, and building settlement or seismic movement all belong on the trigger list.
The runway is the element most likely to absorb the damage and least likely to be inspected afterward. A crane that derailed or was stopped hard by an end stop has loaded the rail, the clips, and the supporting structure in ways normal travel does not, and the evidence sits sixty feet up. Reading the runway and rail condition after such an event is the part that gets deferred until a shutdown, which is usually months later.
Fire and heat exposure deserve a specific mention. A crane above a fire, even a small one, may have experienced temperatures that affect structural steel properties and certainly affects wiring, and the damage is not proportional to the visible soot.
Returning to service after an event
The determination that ends a post-event inspection is a return-to-service decision, and it should be explicit rather than implied by the absence of findings. A qualified person states that the equipment is fit to return, under what conditions, and with what restrictions if any.
Partial returns are legitimate and underused. A machine cleared for reduced capacity, or cleared for use pending a component replacement scheduled within a stated period, is a normal outcome — and writing that restriction down is what makes it real. Verbal restrictions do not survive a shift change.
Where repair is required, the sequence is engineering, repair, inspection, and where the repair was structural, potentially a load test as part of the verification. Repairs to load-bearing structure need an approved procedure from the manufacturer or an engineer before work starts, not after — and the same qualified person requirements apply to the post-repair inspection under 1926.1412(b).
Common questions
Is a post-event inspection required by OSHA?
1926.1412(h) requires inspection appropriate to conditions that could adversely affect safe operation, which covers weather and impact events. Manufacturer criteria and ASME B30.5 are more specific, and manufacturer guidance is the practical benchmark.
What wind speed triggers an inspection?
The manufacturer’s stated limit for that machine and configuration — there is no universal figure. Both the in-service and out-of-service limits matter, and exceeding either is a trigger.
Does a crane need inspection after a lightning strike?
Yes, and follow the manufacturer’s post-strike procedure, which frequently includes turntable bearing examination and electrical system verification. The absence of visible damage is not evidence that none occurred.
Can we keep working while waiting for the inspection?
No. Where an event may have affected safe operation, the equipment stays out of service until a qualified person completes the inspection and authorizes return.
What if the crane was not operating during the event?
It can still have been damaged. A parked machine in high wind, or one struck while idle, has experienced loading regardless of whether anyone was in the seat.
Does a load test have to follow?
Not automatically. The qualified person determines the scope, and where structural repair was required, load testing may form part of the return-to-service determination.
What happens if the inspection finds damage?
The equipment stays down pending repair under an approved procedure and re-inspection — the path described in what happens when a crane fails inspection.
Decide the triggers while the weather is good
Nearly every argument about whether a post-event inspection is necessary happens under schedule pressure, with the crane needed and the event already several hours in the past. Deciding the triggers in advance removes the argument entirely.
If you need a qualified person for a post-event assessment — or want the trigger list built into your program before the season that will test it — get in touch. Same-week scheduling is what this work usually requires, and it is how we scope it.
← All Posts