I'm an IT engineer and consultant, and I run CarYearly. I built the site because the public data on cars is excellent but hard to reach: fuel economy, owner complaints, recalls and crash ratings sit in separate government databases and files that most car buyers never open.
Why I built CarYearly
Anyone shopping for a used car wants to know the same things about the exact model year in front of them: what mileage it really gets, what owners complain about, which recalls apply and how it did in crash tests. The EPA and NHTSA publish all of that, but finding it means searching several sites and reading raw tables. My day job is building systems that collect, check and present data reliably, so I applied the same approach here: take the official numbers, calculate them carefully, and show them on a page anyone can read in a minute.
What I do on the site
- Data pipeline. I designed the code that downloads the EPA and NHTSA data, recalculates every figure and runs automated checks before anything is published.
- Writing and review. I review the written content, including the VIN guides, and check statements our data cannot verify against official sources.
- Corrections. I read every error report sent to hello@caryearly.com and fix confirmed mistakes.
What I am not
I don't work for a carmaker, a dealer or a vehicle history company, and I'm not a mechanic or a licensed adviser.CarYearly reports what official data says; it does not tell you which car to buy. When a page links to a paid partner, the link is marked.
Get in touch
Questions and corrections: hello@caryearly.com. More about the site on the about page, how every number is calculated in the methodology, and how we handle corrections in the editorial policy.