Drop testing electronics before you commit to tooling
Drop testing electronics on your own bench: how to set a realistic spec, build a cheap rig, spot latent damage and fix the design before tooling.

Anything a person carries will be dropped, usually onto a hard floor and rarely at a convenient angle. Drop testing electronics is how you find out, on your own bench, what a fall onto a kitchen floor or a car park does to your enclosure, your board and your battery, before a customer finds out for you.
This post is for founders and engineers with a handheld or portable device heading towards tooling. It covers how we set a sensible drop spec, how we run the test cheaply, what actually breaks, and which fixes are worth making early.
Why drops break products in unexpected places
People expect a drop to crack the housing. In practice, the housing is often the part that survives. The damage happens inside, where heavy parts keep moving after the enclosure has stopped.
A fall onto a hard floor produces a very short, very sharp deceleration. Peak values in the hundreds to low thousands of g are common, with pulse widths around a millisecond or less. The exact figure depends on the drop height, the floor, the device’s mass and how much the housing flexes on impact. A soft overmould or a compliant corner can cut the peak dramatically; a rigid polycarbonate shell on concrete does the opposite.
The failures we see most often are:
- Battery movement. A pouch cell held only by foam tape shifts, pulls on its tabs or leads, or presses into a component on the board.
- Connectors unseating. FPC and ZIF connectors, board-to-board headers and loose JST plugs can partially disconnect, giving intermittent faults that are hard to reproduce.
- Cracked ceramic capacitors. Larger MLCCs placed near board edges, screw bosses or mounting points crack when the board flexes. They may pass a functional test and fail weeks later as a short.
- Solder joint damage. Large BGAs, QFNs and heavy through-hole parts such as inductors or buzzers can crack joints at the corners.
- Snap-fits and bosses. Clips release, screw bosses split at their base, or the housing halves open just enough to eject a button.
- Displays and windows. Glass and thin acrylic crack at the corners, especially when the bezel transfers load straight into them.
Setting a drop testing spec that matches real use
There is no single correct drop height. The useful starting point is how the device is actually carried and used, then a margin on top.
| Use case | Typical fall | Where it lands |
|---|---|---|
| Desk or bedside device | Around 0.7–0.8 m | Wood, tile, carpet |
| Handheld, used standing | Around 1.0–1.5 m | Tile, concrete, asphalt |
| Wearable or clip-on | Around 1.0–1.5 m, often onto an edge | Pavement, gym floors |
| Industrial handheld | 1.5 m or more, repeated | Concrete, steel |
Published standards give you a recognisable framework. IEC 60068-2-31 covers free-fall and rough handling tests, and MIL-STD-810 Method 516 includes a transit drop procedure that many rugged products reference. Both are useful templates for orientations, counts and surfaces. Neither replaces thinking about your own product: a bedside sensor does not need a rugged-tablet spec.
The surface matters as much as the height. Steel plate or bare concrete is far harsher than plywood over concrete, and both are harsher than vinyl flooring. Write the surface into the spec explicitly, or two labs will give you two different answers.
A typical spec we would write for a consumer handheld reads something like: 1.2 m onto concrete, all six faces, twelve edges and eight corners (26 drops), on at least three units, with a full functional check after every drop and no safety-relevant damage permitted.
A drop rig that costs very little
You do not need a commercial drop tester for development work. What you need is repeatability, so a design change is judged against the last result rather than luck.
- A fixed height reference. A marked post or a ruler fixed to the wall, measured from the lowest point of the device to the floor.
- A consistent release. A simple clamp, a vacuum cup or a pin release beats dropping by hand, which adds spin and changes the impact orientation.
- A defined surface. A concrete paving slab or steel plate laid on a solid floor, not a suspended timber floor that absorbs energy.
- A camera. Slow-motion video from a phone at 240 fps is enough to see which corner hits first, whether the device bounces onto a second face and whether parts flex visibly.
- Optional instrumentation. A high-g accelerometer inside a test unit, or logging the device’s own IMU at its highest rate, gives a rough peak figure. Treat consumer IMU readings as indicative only: most saturate well below real impact levels.
Hitting an exact corner by free fall is hard. For development work we accept some variation and record the actual impact orientation from the video.
What to check after every drop
A device that still powers on has not necessarily passed. Many drop failures are latent: a cracked capacitor or a half-seated connector can survive a quick check and fail later.
- Run a short functional test after each drop: power, radio connection, sensors, buttons, display and charging.
- Measure sleep current. A jump of a few tens of microamps is a common sign of a cracked MLCC or a damaged part leaking current.
- Inspect the housing for gaps, whitening at bosses and clips, and moved buttons.
- At the end of the sequence, open the unit. Check battery position, connector seating, screw torque and any marks where internal parts struck each other.
- For units that pass, run them through a temperature cycle or a few days of normal use. Latent damage often shows up then.
Log every drop with height, orientation, surface, unit number and result. A test you cannot repeat or compare is only an anecdote.
Design fixes worth making early
Most drop problems are cheaper to prevent in CAD and layout than to fix after tooling. The fixes we reach for first are:
- Retain the battery mechanically. Ribs or a pocket that locate the cell on all sides, with foam for compliance rather than as the only restraint.
- Keep sensitive parts away from flex points. Move larger MLCCs away from board edges, screw holes and connectors, and orient them so board bending does not load them along their length.
- Secure cables and connectors. Use latching connectors, add a rib that holds an FPC down, or a dab of adhesive on plugs that would otherwise work loose.
- Support heavy parts. Add staking or underfill for large components, and avoid hanging heavy parts off a thin board without support.
- Give bosses room to survive. Gussets, sensible wall-to-boss ratios and generous radii at the base. The same principles apply to clips; our post on snap-fit design for small enclosures goes into detail.
- Add compliance at the corners. Rounded corners, TPE bumpers or overmoulding reduce peak load far more than thicker walls do.
Where drop testing electronics fits in the build schedule
Test early, but read early results carefully. 3D-printed housings do not behave like moulded PC or PC/ABS: SLA parts tend to be more brittle, and printed nylon may be tougher or weaker depending on wall thickness and print orientation. A cracked SLA housing tells you little about the moulded part.
What prints are good for is finding internal problems: a battery that moves, a connector that pops out, a board that flexes into a component. Those failures do not depend much on the housing material, so it pays to find them during the first engineering builds. The formal run with moulded parts belongs later, once the design is close to final. We describe where each build sits in EVT, DVT and PVT for small hardware teams.
A checklist before you commit to tooling
- Write a drop spec with height, surface, orientations, count and number of units, based on real use.
- Build a simple, repeatable rig and film every drop.
- Measure sleep current and run a full functional test after each drop, not just at the end.
- Fix battery retention, connector security and MLCC placement before tooling, then repeat the full sequence on moulded parts.
A few days of careful drop testing is cheap compared with a mould change or a returns batch. The aim is not to pass a number on paper, but to know exactly how your product fails and to have decided that it is acceptable.