Reported risk evidence comparison

Electrical appliances and equipment: operating/charging heat, labels/instructions, plug interfaces — reported risk evidence

The acquired cohort contains 4 official alert references published from 2007-10-12 to 2007-10-19. This page compares 3 selected, distinct product descriptions, including ac battery charger - radio-controlled toy car with remote control and ac battery charger, radio-controlled toy car with remote control.. The other 1 records still contribute to the cohort counts but are not displayed: descriptions may repeat, lack the display inputs, or fall outside the eight-description display limit. 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.

AC battery charger - Radio-controlled toy car with remote control and AC battery charger · 1067/07

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

Reported product description
The package of the product contains a toy car (scale: 1:10, number plate: MH-787-039 or MH-787-038) operated by batteries with a frequency of 27 MHz, a battery charger FENGHUI ELECTRONIC (Model No FH-2210572U AC 220V 50 Hz; DC 9,6V; 250 mA Class II), a remote control "RADIO CONTROL SUPER POWERED 27 MHz", 1 battery-AA 700mAh 9,6V Ni-Cd, and a dry battery of 9V 6LR61. L: 45 cm X W:20 cm X H:12 cm. Indication on the packaging: “PACEMAKER”. [1]
Reported risk explanation
The product poses a risk of electric shock because:- the plug of the battery charger is non-standardized, therefore the live pins are accessible when connecting to the power supply, - the age symbol (8 years), certain safety instructions of the battery charger and warnings are missing; and a risk of burns because the cover of the battery charger significantly overheats during abnormal use.The product does not comply with the Low Voltage Directive and the relevant European standards. [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 authorities Date of entry into force: Unknown [1]

Read the official alert ↗

Radio-controlled toy car with remote control. · 1012/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 of 1:18) with a control frequency of 40 MHz (number plate: “SPEEDY RACER NO:8233”) operated by batteries, a battery charger "Gers Electronics charger. CO., LTD" (model No. GS-104823E AC 230V 50 Hz; DC 4,8V; 230 m Class II), a remote control ("TOP RACER SUPERIOR POWERED SPEED"), 4 batteries-AA 700mAh 1,2V Ni-Cd, and a dry battery of 9V 6F22. L: 27 cm X W:12 cm X H:7,5 cm. [2]
Reported risk explanation
The product poses a risk of :(i) electric shock because:- the plug of the battery charger is non-standardized, therefore the live pins are accessible when connecting to the power supply. - the age symbol (8 years), certain safety instructions of the battery charger and warnings are missing. (ii) burns and fire since the batteries can be charged in the toy car, they are removable without using a tool and interchangeable with the dry battery. The contacts of the battery holder of the car can be short-circuited and then they significantly overheat, the cover of the battery charger significantly overheats during abnormal use, the cover of the battery holder of the remote control can be removed without using a tool and the contacts can be short-circuited. 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 ↗

Radio-controlled toy car with remote control. · 1013/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 of 1:12, number plate on the car: NO:8579) with a control frequency of 27 or 40 MHz, operated by batteries, a battery charger YIXIN ELECTRONIC (model No. YX-3515A8 AC 220V 50/60 Hz; 7,2V; 250 mA Class II), a remote control ("EXALTED SPORTS CAR CONTROL SUPER POWER'S NEW PROJECT RADIO CONTROL SYSTEM."), 6 batteries-AA 700mAh 1,2V Ni-Cd, and a dry battery of 9V 6LR61. L: 37 cm X W:17 cm X H:10,5 cm. [3]
Reported risk explanation
The product poses a risk of :(i) electric shock because:- the plug of the battery charger is non-standardized, therefore the live pins are accessible when connecting to the power supply. - the age symbol (8 years), certain safety instructions of the battery charger and warnings are missing. (ii) burns and fire since the batteries can be charged in the toy car, they are removable without using a tool and interchangeable with the dry battery. The contacts of the battery holder of the remote control can be short-circuited, the cover of the battery charger significantly overheats during abnormal use.The product does not comply with the Low Voltage Directive and relevant European standards EN-60335 and EN-50088. [3]
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 [3]

Read the official alert ↗

What this acquired cohort contains

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

Report yearRecorded alerts
20074

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.

3 distinct descriptions displayed; 1 cohort records not displayed. Missing fields: {'description': 1}.

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], [3]

  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]

  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], [3]

  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

  • [2] /Safety-Gate/notifications[37] (caseNumber=1012/07; parser=safety-gate-weekly-xml-2) · record 9b904f1a8085680f8a3c2c35a6de41a35bd14f70aaddcb68b86e44afa1d67aa7
  • [3] /Safety-Gate/notifications[36] (caseNumber=1013/07; parser=safety-gate-weekly-xml-2) · record 255c281b150bf78cf72eff4cee125f7036d52b53a6248242593b0b3e9ab026ee
  • [4] /Safety-Gate/notifications[32] (caseNumber=1017/07; parser=safety-gate-weekly-xml-2) · record d2a69238690e5b11e1d2c24f29179e21ca7e1f242798b3d4ba22007874179892

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