The housing is intact.
The display works.
The phone powers on.
Then the charging cable is connected.
Nothing happens.
PASS?
No.
The device survived the impact visually, but one required function was lost.
That difference matters because drop test pass/fail criteria are not based on appearance alone.
A product may show no visible crack and still have electrical, mechanical, functional, or safety-related damage. On the other hand, a small cosmetic mark does not automatically mean that the product has failed.
The real question is:
Did the specimen still meet the required acceptance criteria after impact?
That question should be answered using evidence—not by looking at the product after the test and deciding whether the damage “seems acceptable.”
This guide explains how to define acceptance criteria before testing, how to inspect a product after impact, and how to turn observations into a defensible PASS / FAIL decision.
If you are still defining the overall test method rather than the post-impact decision, start with our guide to Drop Testing for Electronic Equipment: Methods, Failure Modes & Equipment Selection, which explains the main impact variables, failure paths, and equipment selection logic.
No Crack Is Only an Observation
“No crack” tells you something useful.
It tells you that no visible crack was observed.
It does not tell you that the product passed.
The same applies to statements such as:
- the product still turns on;
- the display still lights up;
- the housing looks normal;
- the button still moves.
These are inspection results.
They become PASS criteria only when they match the actual acceptance requirement.
A practical way to think about it is:
Observation
What changed?
↓
Requirement
What was allowed?
↓
Decision
Does the result still meet that requirement?
Suppose a smartphone has no visible damage after a corner drop, but the charging connector now works only when the cable is held at a particular angle.
The housing may have passed visual inspection.
The device may still power on.
But if normal charging operation is required, the final result is still:
FAIL
That is why visual survival and test acceptance should not be treated as the same thing.
Surviving the impact is not the same as passing the drop test.
Define Failure Before the First Drop
A weak test plan often follows this sequence:
DROP
↓
SEE DAMAGE
↓
DISCUSS WHETHER IT COUNTS
That is where arguments begin.
One engineer sees a small housing gap and calls it minor.
Another calls it enclosure separation.
The supplier says it is acceptable.
The customer rejects it.
At that point, the problem may not be the specimen.
The problem may be the test plan.
The test did not fail here. The acceptance rule was never clearly defined.
A stronger sequence is:
DEFINE TEST OBJECTIVE
↓
DEFINE ACCEPTANCE CRITERIA
↓
RECORD BASELINE
↓
PERFORM THE TEST
↓
COLLECT EVIDENCE
↓
COMPARE WITH REQUIREMENT
↓
PASS / FAIL
The criteria should answer questions such as:
- Is cosmetic damage allowed?
- Are housing cracks acceptable?
- Can a connector become loose?
- Must all functions remain normal?
- Are electrical values allowed to change?
- Is any safety-related damage automatically unacceptable?
The answers will depend on the product, applicable specification, customer requirement, and test purpose.
The important part is that they exist before the test.
Never use the damaged specimen to invent the acceptance criteria.
Five Layers of Post-Impact Evaluation
For electronic products, post-drop inspection can be organized into five layers:
Cosmetic
Structural
Mechanical
Electrical
Functional & Safety
These layers are not equally important for every product.
They are simply a practical way to avoid stopping the inspection too early.
Cosmetic: What Changed on the Surface?
Start with what is visible.
Typical observations include:
- scratches;
- dents;
- coating damage;
- chipped finishes;
- surface marks;
- discoloration.
Cosmetic damage should be recorded.
Whether it causes failure depends on the requirement.
A scratch on an industrial enclosure may be acceptable.
The same scratch on a finished consumer product may violate an appearance specification.
The important distinction is:
Scratch ≠ Crack ≠ Exposed Internal Part
They may all be visible, but they do not carry the same engineering meaning.
Structural: Is the Product Still Physically Intact?
Structural inspection looks beyond surface appearance.
Check for:
- housing cracks;
- enclosure separation;
- broken clips;
- permanent frame deformation;
- fractured glass;
- loose panels;
- displaced assemblies;
- exposed internal parts.
A structural change can affect more than appearance.
It may alter:
- internal support;
- protection against contact;
- environmental sealing;
- connector alignment;
- future durability.
This is why a visible crack should not simply be recorded as “damage.”
Its location, size, and effect on the product should also be understood.
Mechanical: Does It Still Move, Fit and Connect Correctly?
Mechanical failures are easy to miss when the outside still looks normal.
Useful checks may include:
- buttons;
- switches;
- hinges;
- latches;
- connectors;
- covers;
- mounting points;
- moving assemblies.
Consider a USB connector after a drop.
It remains attached.
It still accepts the cable.
But it now moves noticeably inside the housing.
Visually, the product may still look acceptable.
Mechanically, something has changed.
The question becomes:
Is that change within the allowable condition?
Electrical: The Failure May Not Be Visible
This is where electronic product drop testing becomes more interesting.
A product may have:
No crack
No broken display
No loose housing
and still fail electrically.
Post-impact checks may include:
- continuity;
- resistance;
- charging behavior;
- connector contact;
- output stability;
- insulation condition;
- power input or output;
- product-specific electrical measurements.
And electrical failure is not always binary.
There are at least three useful conditions to distinguish.
Hard Failure
The function is gone.
Examples:
No power
No charging
Open circuit
Intermittent Failure
The function works only under certain conditions.
Examples:
Charging only works at one cable angle
Power drops out when the product is moved
Connection appears and disappears
Degradation
The product still functions, but performance has changed.
Examples:
Increased contact resistance
Reduced connector stability
Abnormal output fluctuation
This distinction matters because:
PASS / FAIL is not always the same as works / does not work.
A product can degrade before it completely fails.
That degradation may be exactly what the drop test is supposed to reveal.
Functional & Safety: Can the Product Still Do Its Job Safely?
Function is the final practical test.
For a smartphone, engineers may verify:
- power-on;
- display;
- touch response;
- buttons;
- camera;
- microphone;
- speaker;
- charging;
- communication functions.
For a charger, battery-powered device, or other electronic equipment, the checklist will be different.
Safety also requires separate attention.
Potential concerns may include:
- exposed conductors;
- damaged insulation;
- abnormal heating;
- battery deformation;
- leakage;
- unsafe enclosure opening;
- displaced internal parts.
A product may still operate after the impact and still be unsafe.
That is not a successful result.
Function without safety is not a PASS.
PASS Is Not a Majority Vote
Suppose a smartphone is checked after a drop.
The results are:
| Inspection Item | Result |
|---|---|
| Housing | ✓ |
| Display | ✓ |
| Camera | ✓ |
| Buttons | ✓ |
| Charging | ✕ |
Four checks pass.
One fails.
Does that mean the overall score is 4 out of 5, or 80%?
No.
If normal charging is a required acceptance criterion, the final result is:
FAIL
This is one of the easiest mistakes to make when interpreting a drop test.
Acceptance criteria are not usually a voting system.
Acceptance criteria are gates—not votes.
One failed required function may be enough to determine the final result.
This does not mean every observed change causes failure.
It means the final decision must be tied to the importance of the requirement, not to the number of green checkmarks.
Baseline First. Drop Second.
A post-test inspection is only as useful as the information available before the test.
Imagine finding a small scratch after the drop.
Was it caused by the impact?
Without a pre-test record, maybe.
Maybe not.
Now imagine a charging fault.
Was charging normal before the test?
Again, you need a baseline.
A simple sequence is:
PRE-TEST CHECK
↓
DROP
↓
POST-TEST CHECK
↓
COMPARE
↓
WHAT CHANGED?
The pre-test baseline may include:
- product ID;
- photographs;
- housing condition;
- existing scratches;
- buttons;
- connector condition;
- charging;
- required functions;
- relevant electrical checks.
The goal is not to document every possible characteristic.
The goal is to document the characteristics that matter to the acceptance decision.
Without that baseline, a post-test observation can become an argument.
With it, the change becomes evidence.
A baseline turns damage into evidence.
The Failure You Cannot See
Impact damage does not always appear where the product contacts the surface.
A device lands on its corner.
The corner loads the enclosure.
The enclosure loads the frame.
The frame transfers force into internal components.
The eventual failure may occur at:
- a connector;
- a solder joint;
- the PCB;
- a battery mount;
- an internal bracket;
- a cable termination.
Some of these failures are hidden.
Others are intermittent.
Some may not produce an immediate symptom.
For example, the product may:
- power on normally after the drop;
- charge once;
- fail after repeated connector movement;
- show unstable contact during later use.
This is where the idea of latent damage becomes useful.
Latent damage does not mean every dropped product will fail later.
It means the absence of an immediate visible symptom does not prove that no internal change occurred.
Inspection depth should therefore match the test objective and product risk.
A routine screening test may need only visual and functional checks.
A failure investigation may justify:
- repeated connector operation;
- electrical measurement;
- functional cycling;
- internal inspection;
- follow-up reliability testing.
The point is not to inspect everything.
It is to inspect deeply enough to answer the engineering question.
If you want to understand why an impact at one location can produce a failure somewhere else inside the product, see Drop Testing for Electronic Equipment: Methods, Failure Modes & Equipment Selection for a deeper explanation of impact load paths and common electronic-product failure modes.
Requirement → Evidence → Decision
This is the simplest framework for evaluating drop-test results.
1. Requirement
What must remain acceptable?
Examples:
No housing crack
Charging must remain normal
No exposed conductor
Display must operate
Connector looseness must remain within defined limit
2. Evidence
What actually changed after impact?
Examples:
1 mm housing gap
Charging intermittent
No visible crack
Connector movement increased
Display normal
3. Decision
Does the evidence violate the requirement?
That gives the final:
PASS / FAIL
The process may sound obvious, but it solves a common problem.
Without this structure, teams often jump directly from:
“We found damage.”
to:
“So is it a failure?”
The missing step is the defined criterion.
Damage Is Not Binary
During development, it can be useful to record more than PASS / FAIL.
Consider these examples:
| Observation | Engineering Meaning | Typical Decision Logic |
|---|---|---|
| Small scratch | Cosmetic change | Depends on appearance criteria |
| Housing crack | Structural change | Evaluate against defined limit |
| Loose connector | Mechanical degradation | Check allowable condition |
| Charging intermittent | Electrical / functional degradation | Fail if normal charging is required |
| Exposed conductor | Safety hazard | Normally unacceptable |
| No visible damage | Observation only | Continue functional evaluation |
The purpose of this table is not to create a universal acceptance standard.
It is to show why:
Damage classification and final acceptance are related—but they are not the same thing.
During R&D, recording the failure mode, severity, and location can be more useful than writing only “FAIL.”
Where Should the Acceptance Criteria Come From?
This is another area where confusion is common.
Acceptance criteria may come from several places.
Applicable Standard
A test standard may define the test method, inspection requirement, acceptable condition, or post-test performance.
Customer Specification
A customer may impose requirements that are more specific or stricter than the general test method.
Product Specification
Internal product requirements may define cosmetic, mechanical, electrical, or functional limits.
Safety or Regulatory Requirement
Certain damage conditions may be unacceptable because they create a hazard.
Internal Engineering Requirement
During development, an engineering team may define additional screening criteria to compare prototypes or design revisions.
These sources should not be mixed together casually.
A standard may define how to perform the drop.
A customer document may define how much visible damage is acceptable.
An internal specification may define what electrical performance must remain within limits.
Those can all be part of the same test plan.
The test method and the acceptance criterion are not always the same document.
That distinction makes reporting much clearer.
Inspect Once—or After Every Drop?
Suppose the test sequence is:
Face
↓
Edge
↓
Corner
When should the product be inspected?
After every impact?
Or only after the full sequence?
The answer depends on the test objective.
For formal testing, follow the specified procedure.
For development and failure analysis, intermediate inspection can be useful because it helps identify:
When did the first change begin?
For example:
Drop 1 → normal
Drop 2 → connector looseness appears
Drop 3 → charging becomes intermittent
That sequence provides much more design information than a single final FAIL.
But intermediate handling should not alter a test that is supposed to run as a continuous defined sequence.
So the rule is simple:
Inspection timing should be designed—not improvised.
A Good Drop Test Report Explains the Decision
A weak report says:
Result: FAIL
A useful report explains:
What was tested?
How was it dropped?
What changed?
Why does that change lead to PASS or FAIL?
A practical report may include:
| Item | Record |
|---|---|
| Specimen | Model, configuration, sample ID |
| Pre-test condition | Visual and functional baseline |
| Test requirement | Standard / customer / internal specification |
| Drop height | Defined test height |
| Orientation | Face / edge / corner |
| Impact surface | Defined surface and condition |
| Sequence | Number and order of drops |
| Visual result | Damage observed |
| Structural result | Crack / deformation / separation |
| Mechanical result | Buttons / connectors / moving parts |
| Electrical result | Relevant measurements or checks |
| Functional result | Required functions |
| Safety result | Hazard or abnormal condition |
| Failure mode | Type and location |
| Photographs | Before / after |
| Final decision | PASS / FAIL against defined criteria |
The impact surface should be recorded because it is part of the test condition.
Two specimens dropped from the same height but onto mechanically different surfaces may not experience equivalent impacts.
For a deeper explanation of why steel, wood, concrete, plate thickness, backing, and surface condition can influence the result, see Drop Test Impact Surface: Steel, Wood or Concrete—Does It Change the Result?
Reliable Decisions Need Repeatable Impacts
Pass/fail evaluation assumes that the test condition itself was valid.
Consider two nominally identical corner drops.
In the first test, the specimen hits the intended corner.
In the second, the product rotates during release and lands partly on its face.
If one passes and one fails, the difference may come from the specimen.
Or it may come from the impact condition.
That is why repeatability matters.
Variables such as:
- drop height;
- orientation;
- release;
- impact surface;
- drop sequence;
- specimen condition;
need to be sufficiently controlled.
Good acceptance criteria cannot compensate for an uncontrolled impact.
For applications where face, edge, and corner orientation itself is part of the test requirement, our guide Face, Edge and Corner Drop Testing: What Each Drop Reveals explains why these orientations load the product differently and why impact orientation should be controlled rather than treated as a cosmetic detail.
RS-DP-03A2 for Controlled Electronic Product Drop Testing
For portable electronic products requiring controlled face, edge, and corner impacts, the ITM-LAB RS-DP-03A2 Automatic Drop Test Machine is designed to help reproduce defined drop conditions with controlled positioning and release.
The machine does not determine PASS or FAIL.
Its role is earlier in the process:
DEFINED ORIENTATION
↓
CONTROLLED RELEASE
↓
DEFINED IMPACT
↓
POST-TEST EVIDENCE
↓
COMPARE WITH CRITERIA
↓
PASS / FAIL
That distinction is important.
Reliable evaluation begins with a repeatable test condition.
For machine configuration, test range, application details, and inquiry information, link this section directly to the RS-DP-03A2 Automatic Drop Test Machine product page.
Practical Drop Test Pass/Fail Checklist
Use this as a planning framework rather than a replacement for the applicable specification.
Before the Test
☐ Identify the applicable requirement
☐ Define the test objective
☐ Define acceptance criteria
☐ Record specimen ID and configuration
☐ Photograph the pre-test condition
☐ Verify required functions
☐ Confirm drop height
☐ Confirm orientation
☐ Confirm impact surface
☐ Define inspection timing
During the Test
☐ Confirm the intended orientation
☐ Record each impact
☐ Note abnormal rotation or release
☐ Record intermediate observations when required
☐ Keep the test condition consistent
After the Test
☐ Cosmetic inspection
☐ Structural inspection
☐ Mechanical inspection
☐ Electrical verification where applicable
☐ Functional verification
☐ Safety inspection
☐ Photograph relevant changes
☐ Record failure mode and location
☐ Compare evidence with criteria
☐ Record final PASS / FAIL
The most important checkbox is still near the top:
Define failure before the first drop.
FAQ
What determines whether a product passes a drop test?
A product passes when it still meets the predefined acceptance criteria after the required drop condition or test sequence.
The criteria may come from a standard, customer requirement, product specification, safety requirement, or internal engineering plan.
Is no visible damage enough for a PASS?
Not necessarily.
No visible damage is an inspection result.
Electrical, mechanical, functional, or safety-related failure can exist even when the exterior appears normal.
Does cosmetic damage automatically mean FAIL?
No.
Cosmetic damage becomes a failure only when it exceeds the applicable acceptance requirement.
A scratch may be acceptable in one application and unacceptable in another.
Can a product fail even if it still powers on?
Yes.
Power-on is only one function.
A device may still power on while charging, communication, connectors, buttons, insulation, or another required function has failed.
What is an intermittent drop-test failure?
An intermittent failure is a condition that appears only under certain states or movements.
Examples include charging that works only at a certain cable angle or a connection that drops out when the product is moved.
These conditions should not be ignored simply because the product works during one quick check.
Should functionality be checked after every drop?
Not always.
Formal test procedures should follow the specified inspection timing.
During development or failure analysis, intermediate checks may help identify when degradation begins.
Why is a pre-test baseline important?
Because post-test evaluation depends on knowing what changed.
Without a baseline, engineers may not know whether a scratch, loose connector, or functional issue existed before testing.
Final Takeaway
A drop test does not end when the specimen hits the impact surface.
That is when the evaluation begins.
The outside may look normal.
The display may still work.
The product may still power on.
None of those observations, by themselves, define PASS.
A strong decision follows a clearer logic:
Requirement
↓
Evidence
↓
Comparison
↓
PASS / FAIL
And for electronic products, that evidence may need to include more than appearance:
Cosmetic
Structural
Mechanical
Electrical
Functional & Safety
Three rules are worth carrying into every test plan:
No visible damage is an observation—not a pass criterion.
Define failure before the first drop.
Acceptance criteria are gates—not votes.
When those rules are combined with a controlled impact condition and a documented pre-test baseline, PASS / FAIL becomes much less subjective—and much more useful to engineering, quality, customers, and laboratories.
For portable electronics requiring controlled face, edge, and corner impact conditions, the ITM-LAB RS-DP-03A2 can support repeatable drop execution before the final post-impact evaluation is made.
