Reported risk evidence comparison

Toys: operating/charging heat, labels/instructions, plug interfaces — reported risk evidence

This comparison covers 2 official alert references, including radio-controlled toy car with remote control and battery charger., radio-controlled toy car with remote control., published from 2007-10-12 to 2007-10-12. The recorded risks raise separate evidence questions about operating/charging heat, labels/instructions, plug interfaces. Compare the product features and dated findings below before scoping an investigation. These historical observations do not determine your product’s compliance or a market failure rate.

Evidence retrieved 2026-10-07. Source versions and topic-specific limits are listed below.

Dated official observations

Compare the product features and reported failure mechanism

The source wording below describes the reported case at that time. Read each complete report before using it in an investigation.

Radio-controlled toy car with remote control and battery charger. · 1029/07

Report published 2007-10-12 · notifying country Hungary · reported origin People's Republic of China

Reported product description
The package of the product contains a plastic toy car with a control frequency of 27 MHz or 49 MHz, (number plate on the product: WOLFHOUND), operated by batteries, a battery charger (XIONG FENG ELECTRONIC model No.: XF-3053A AC 220-240V;50/60 Hz;/DC 9,6V 200mA Class II ; for the connection of the battery charger an transformer adaptor is also provided), a remote control (“R/C FREE CONTROL TOP POWERFUL TOP SUPERIOR SPEEDY CE MHz 006P 6LR61 9V”), battery ( “Ni-Cd AA700mAh 9,6V”), and a dry battery of 9V 6LR61. Size: L: 38 cm x W:18 cm x H:15 cm. Inscription on the packaging: Power Cross-Country 4WD. [1]
Reported risk explanation
The product poses a risk of :(i) electric shock because:- the plug of the battery charger is non-standardized, the attached transformer adaptor does not comply with the Hungarian plug/socket system. - the age symbol (8 years) and certain technical parameters (voltage) are missing, there are no instructions in Hungarian for the safe use. (ii) burns since the battery charger can be short-circuited and thus the cover overheats.The product does not comply with the Low Voltage Directive and relevant European standards EN-60335 and EN-50088. [1]
Reported measures, verbatim
Type of economic operator to whom the measure(s) were ordered: OtherCategory of measure(s): Withdrawal from the market and recall from consumers ordered by the authority. Date of entry into force: Unknown [1]

Read the official alert ↗

Radio-controlled toy car with remote control. · 1033/07

Report published 2007-10-12 · notifying country Hungary · reported origin People's Republic of China

Reported product description
The package of the product contains a plastic toy car (scale 1:16)with a control frequency of 27 MHz, (number plate on the product: QX-3021), operated by batteries, a battery charger (QUN XING 220V;50/60 Hz; output: DC 6V 700mA Class II), a remote control (“QUNXING SUPER POWER RADIO CONTROL MADE IN CHINA R/C 27 MHz 9V”), battery ( “Ni-Cd AA1000mAh 4,8V”), and a dry battery of 9V 6LR61. Size: L: 26 cm x W:11,5 cm x H:7 cm. [2]
Reported risk explanation
The product poses a risk of :(i) electric shock because:- the plug of the battery charger is non-standardized and the attached adaptor-transformer does not comply with the national plug/socket system,- the cover of the battery charger can be removed without using a tool,- the age symbol (8 years), certain safety instructions of the battery charger and warnings are missing.(ii) burns and fire because when the battery charger is short-circuited the cover overheats. The product does not comply with the Low Voltage Directive and relevant European standards EN-60335 and EN-50088. [2]
Reported measures, verbatim
Type of economic operator to whom the measure(s) were ordered: OtherCategory of measure(s): Withdrawal from the market and recall from consumers ordered by the authority. Date of entry into force: Unknown [2]

Read the official alert ↗

What this acquired cohort contains

2 distinct official alert references, published between 2007-10-12 and 2007-10-12. Counts describe the acquired reports, with no market denominator.

Report yearRecorded alerts
20072

Recorded risk labels within this evidence task

Label combinations are source facts within one comparison; they do not create separate guides with identical preparation tasks.

Source selection, exclusions and calculation method

Filter the acquired, completely parsed English weekly XML releases. Deduplicate official alert references. Group by product category and the complete set of conditional evidence-question topics supported by actual risk text. Risk-label combinations remain recorded cohort facets and do not create buyer intents. Brand, product name, model, origin, notifying country, measurement-only changes and different wording of the same questions do not create intents. Unrecognized mechanisms stay internal for enrichment. Count report years and notifying countries deterministically. Display at most eight newest descriptions with at least 40 characters after whitespace normalization, nonempty reported measures and distinct casefolded descriptions; break date ties by official identifier. All cohort records count even if their description is shorter or not displayed. This is not a representative sample. Counts concern this acquired corpus only.

One acquired version per official public alert reference. Display at most eight newest distinct product descriptions whose normalized whitespace-collapsed text contains at least 40 characters and has nonempty reported measures; ties sort by official identifier. The complete cohort includes shorter descriptions. This is an explicit display selection, not a representative sample.

2 distinct descriptions displayed; 0 cohort records not displayed. Missing fields: {}.

These are selected, dated enforcement observations in the acquired weekly reports, not a random market sample, market-wide failure rate, proof of current product status, or a determination about your product. Notification country is not a complete sales-market or jurisdiction-coverage field. A quoted legal/standard reference is the report’s statement, not independently verified current law or a mandatory test panel.

Calculation safety-gate-evidence-comparison-10; units recorded alerts; no incidence denominator.

Turn the reported failure mechanism into a scoped investigation

Use this checklist to gather your business or product details before speaking with a specialist. The items below explain what to record and suggest useful supporting documents. You can add your own answers in the editable project brief.

  1. Plug, socket and connector interfaces — what evidence do we have?

    Identify the exact plug/socket or connector configuration, intended country interface and any adapter supplied. Document the interface dimensions, accessible parts and assembly controls for specialist review against current applicable requirements. Do not assume a reported interface failure applies to every configuration.

    Useful evidence: Interface drawings/specifications, destination configurations, adapter BOM and relevant measurements/results.

    Reported context: [1], [2]

  2. Operating heat and battery/charging configuration — what evidence do we have?

    If the product includes the reported battery configuration, compare the actual operating or charging heat mechanism with cell/charger specifications, protection circuitry and foreseeable use. Keep heat or electrochemical injury following mouthing or swallowing separate; it does not establish a charging fault.

    Useful evidence: Cell/charger specifications, protection design, operating limits, assembly/revision history and existing thermal/electrical evidence.

    Reported context: [1], [2]

  3. Labels, instructions and actual use — what evidence do we have?

    Capture the exact label/instruction revision and destination/use context. Compare the information gap described in the report with your own product and current sector requirements, keeping a reported defect separate from a universal wording obligation.

    Useful evidence: Current labels/instructions, revision and market/translation records, use/risk information and reviewed applicable requirements.

    Reported context: [1], [2]

  4. Can we trace the affected component, formula or design revision across our supplied products?

    Compare the reported descriptions with your own identifiers and change records. Treat missing or “Unknown” source fields as unresolved; they do not establish that no action was needed.

    Useful evidence: Product identifiers, revision history, supplier/batch traceability and market/operator records.

  5. Who would own an evidence review and any resulting corrective-action decision?

    Read the reported measures as historical observations. Establish your own operator roles, sector-specific rules, decision owner and communication responsibilities before adopting another case’s response.

    Useful evidence: Supply-chain responsibility map, applicable-law review, investigation scope and documented decision/communication workflow.

Work packages and dependencies

Questions for providers

Sources and data dates

Read the official document in context. The audit details identify the precise locators and preserved versions used for this page.

European Commission — published reference ↗

Report-2007-40 / 2007-10-12 · retrieved 2026-10-07

Audit details: precise locators and snapshot identifiers

Source key D18 · snapshot 8dc3511dd67ac614e53a8f4dc578cc41754e52a4ffb58609a321503a8642ff0f

  • [1] /Safety-Gate/notifications[22] (caseNumber=1029/07; parser=safety-gate-weekly-xml-2) · record 7a749c4cadbe0d9b8010eba3f887474d4be32798c429bf0864afe8b5dc7910bc
  • [2] /Safety-Gate/notifications[18] (caseNumber=1033/07; parser=safety-gate-weekly-xml-2) · record c69c3c02c33946da89ab8fc06036b15063000f5abb2ac6dd85f0f2dddcb92b62

Prepare an editable project brief

Confirm the facts, scope and contact preference before sharing your project. Preparing this page sends no provider outreach.

Choose work packages to discuss

Compare Find GPSR Responsible Person (EU/NI) | Compare & Get Quotes