CarFactBook Problem Intelligence

Common problems & real-world repair outcomes

This database starts with reviewed owner reports tied to exact chassis/model codes, then turns enough evidence into CarFactBook-owned statistics. We do not label a problem “common” from one anecdote: public intelligence requires at least three approved reports for the same exact vehicle, and repair-cost ranges stay separated by country and currency.

Problem Intelligence is collecting evidence.

No exact vehicle has reached the three-approved-report threshold yet. That is intentional: CarFactBook will show an empty state rather than manufacture reliability statistics from tiny samples.

Publication rules: 3+ approved reports per exact vehicle for overall intelligence; 3+ in the same system for system-level patterns; 3+ repair-cost observations in the same country and currency for cost ranges.
Owner Outcome Intelligence v2

Which reviewed repairs actually had follow-up?

0 qualified patterns

Repair patterns publish only after three approved reports share the same exact chassis, system, reviewer-normalized symptom and reviewer-normalized repair key. “Common-fix” wording remains locked until five comparable reports, and even then it is a sample-size signal rather than a recommendation.

Owner Outcome Intelligence is collecting evidence. No exact chassis + symptom + repair combination has reached the three-reviewed-report publication threshold yet. CarFactBook will not manufacture a “common fix” from one or two anecdotes.
No reviewed owner reports are public yet.

That is intentional: CarFactBook starts this dataset empty rather than manufacturing “common problems.” The first useful asset is the structured evidence owners contribute and we verify.

Owner evidence

Share a real problem or repair outcome

Human review required

Start with the four required items: exact vehicle, vehicle system, a short title and what you actually experienced. Everything else can be added only if you know it. CarFactBook would rather receive a small accurate report than a long guessed one.

Minimum useful reportExact chassisSystemProblem titleYour observed symptom

Exact-vehicle handoff: you came from an exact-vehicle CarFactBook page, so that chassis is preselected. Viewing a fact, service or part page does not mean anything happened to your car; tell us only what you actually experienced.

1 · Required coreEnough to create a pending report for human review.
2 · Add repair, mileage & follow-up evidenceOptional, but useful when you actually know it.
Optional details

Dates, mileage, mechanic findings, the repair performed and whether the symptom returned make reports much more useful. Leave any field blank rather than guessing.

Have a receipt or service document? Keep it private in Vehicle Passport, then link that exact event through Repair Casebook if you want the reviewer to see server-verified provenance.

No account required. Pending reports remain private until reviewed.