
THE SHORT ANSWER
Enter the full 17-character VIN in the decoder above. A Scion VIN usually starts JTK, JTL or JTN for the Toyota-built cars, JF1 for the FR-S and 3MY for the iA. NHTSA's own decoder names the make Toyota and puts Scion in the model field, so that is normal. A decode covers the build only, so run a history report before you pay.
- Common prefixes
- JTK, JTL, JTN, JF1, 3MY
- Make in NHTSA's decoder
- Toyota, with Scion in the model name
- Model years in recall data
- 2004 to 2016
- Decode shows
- The factory build, not later history
What a Scion decode returns, model by model
Each row below started as a short VIN prefix copied from an NHTSA owner complaint and was run through NHTSA's decoder. Only the first characters went in, so the answers are partial, but they show what the engine and plant fields look like on every Scion body style.
| Scion | Starts | Engine | Plant returned |
|---|---|---|---|
| 2005 tC | JTK | 2.4 L | Toyota City, Japan |
| 2005 xA | JTK | 1.5 L | Toyota City, Japan |
| 2006 xB | JTL | 1.5 L | Sagamihara, Japan |
| 2008 xB | JTL | 2.4 L | Kanegasaki, Japan |
| 2008 xD | JTK | 1.8 L | Toyota City, Japan |
| 2012 iQ | JTN | 1.3 L | Toyota City, Japan |
| 2013 FR-S | JF1 | 2.0 L | Ota, Japan (Subaru) |
| 2016 iM | JTN | 1.8 L | Toyota City, Japan |
| 2016 iA | 3MY | 1.5 L | Salamanca, Mexico (Mazda) |
The big engine jump on the xB between 2006 and 2008 is worth knowing. An advert that pairs a 2006 xB with a 2.4 L engine does not match what the decoder returned for that year.
Why NHTSA's decoder says Toyota, not Scion
Type a Scion VIN into the decoder and the make field reads Toyota. The model field carries the brand, as in Scion tC or Scion xB. NHTSA's list of makes has no entry called Scion at all, and its model lookup for that name comes back empty.
The recall and complaint databases behave the other way and file these cars under SCION. So a search can look empty in one government tool and full in another. A seller who says the VIN does not decode as a Scion is reading only the make field.
A quick sanity test
If the decode returns a Toyota make and a model that starts with Scion, the number is behaving normally. If it returns a plain Camry or Corolla for a car sold as an xB, ask why before going further.
The prefixes and who stood behind them
Most Scions were Toyota products from a Japanese plant, but three of the prefixes point somewhere else, and that is where a decode earns its keep.
- JTK: Toyota Motor North America, passenger car. The tC and xA samples above, plus the xD, carried it.
- JTL: Toyota Motor Corporation, multipurpose vehicle. This is the xB prefix.
- JTN: Toyota Motor Corporation, passenger car. The iQ and the iM used it.
- JF1: Subaru Corporation. The FR-S was assembled by Subaru, and the decode lists Subaru as the manufacturer.
- 3MY: Mazda's Mexican plant. The iA is a Mazda underneath, and the decoder says so.
A sedan that starts 3MY and decodes as an iA is exactly right. A tC that starts 3MY needs a long explanation.

Typing the number so it decodes cleanly
Copy the number from a photo instead of squinting through glass, and hold it up to the registration card. One wrong character changes the whole answer.
- Enter all 17 characters with no spaces or dashes.
- Check that the model year in the result matches the advert and the title.
- Compare the engine and plant fields with the car on the lot.
- If the decoder flags the ninth character, retype the number slowly before blaming the car.
That flag is not a verdict. Every one of the samples above drew it because only a prefix was sent. A full, correct VIN passes the check-digit test, the federal formula that exists to catch typing mistakes.

Recalls on a used Scion: the ones that matter
Recalls follow the VIN, and the Scion list is not short. These are the campaigns worth checking by number before you buy.
| Campaign | Models | Problem | Fix |
|---|---|---|---|
| 16V340000 | 2008 to 2011 xB | Passenger air bag inflator can rupture; 1754517 vehicles | Free inflator or assembly replacement |
| 17V006000 | 2009 and 2012 xB | Same inflator problem; 577875 vehicles | Free replacement |
| 19V741000 | 2008 to 2012 xB | Inflators already swapped once with the same design can explode; 928220 vehicles | Dealer replaces inflator or assembly |
| 18V776000 | 2004 to 2006 xA | Air bag control module may short, firing or disabling the air bags | Inspect, replace module if needed |
| 18E091000 | xB and tC with TRD brake kit | Brake hoses in the optional kit can fail | Swap to a standard kit |
The inflator campaigns split vehicles by where they were sold or registered, so model and year alone cannot say if one particular car is covered. Only its VIN can.
From an NHTSA owner complaint
An owner of a 2008 xB received the notice for campaign 17V006000 and then learned the repair part was not available. A Colorado Toyota dealer told them no vehicles there were being repaired under the maker's rules. They had not suffered a failure, but they were left driving a car with an open air bag recall.
Ask a seller for proof of completion, or have the VIN looked up the day you view the car.
What the decoder cannot tell you
A decode is a statement about the factory. It cannot say whether the xB was in a collision, whether a title carries a salvage or flood brand, or whether the dash reading is honest.
Federal title data is built around five points: the state and date of the current title, brands such as junk, salvage or flood, odometer readings, total loss history and salvage history. A report that comes back with nothing under those headings is a good result.
Scion buyers tend to be shopping at the cheap end of the market, where cars have changed hands several times. That raises the odds that a brand, a lapse or a mileage gap is hiding in the file, and it is the reason a decode alone should not close the deal.
A buyer who found the problem after paying
From an NHTSA owner complaint
A 2019 complaint describes a buyer who purchased a 2008 xB in January and saw the oil light flash within weeks. The engine had run dry. A Toyota dealer replied that the oil campaign had lapsed in January 2018, so the owner would be billed for the fix on a car still under a loan.
The lesson is practical. Whether a campaign has expired, been completed or never covered the car cannot be read from the VIN characters. It lives in records tied to that VIN, and it is cheaper to see them before money moves than after.
An older Scion is also a car where owner reports and decodes can disagree. One tC complaint list contains a VIN that NHTSA decodes as an xA. Trust the decode for the build and the paperwork for everything else.
After the decode: run the history report
When the build matches the advert, run that VIN through the history report. You get a preview at no charge to see if records turn up, then pay once for the full report if you want it. Nothing recurs, and the pricing page shows the single and pack choices.
- Title brands, which a decode never shows
- Accident and damage entries, with auction photos when a car went through one
- Odometer readings over time, to test the dash
- Open recalls on that exact number
Read the result next to the decode. Plant, engine and year say what the car was; the report covers its life afterward.
Where this information comes from
- NHTSA vPIC: VIN decoder — Shows how the decoder treats partial VINs and where the data originates.
- NHTSA recall 16V340000 — Source for the xB inflator campaign, its zones, remedy and vehicle count.
- NHTSA recall 18V776000 — Source for the xA air bag control module campaign.
- NMVTIS: understanding a vehicle history report — Lists the five title indicators and what a clean federal report means.
- NHTSA owner complaint 11030357 — owner experience, paraphrased
- NHTSA owner complaint 11195300 — owner experience, paraphrased
Sources and photos: Facts checked against the sources above in November 2026. Photos by Nina Mercado, Masjid MABA and Iain on Unsplash; diagrams by VINDecode.
Keep reading
- Toyota VIN Decoder: Check the Build, Then the Car's RecordToyota is the make in NHTSA's decode of a Scion, so its prefix rules apply.
- Subaru VIN Decoder: Engine, Drivetrain, Plant and HistoryThe FR-S was built by Subaru, and this page reads that side of its VIN.
- Mazda VIN Decoder: Prefix, Miata Generation and Rotary CheckThe iA is a Mazda built in Mexico, and the 3MY prefix is explained here.
- VIN Decoder Year Chart: Position 10 Codes for 1980 to 2039Every year character in one table, to confirm the tenth position.
Frequently asked questions
Is a Scion a Toyota?
NHTSA's decoder records it that way. A decode of a Scion VIN returns Toyota as the make and the Scion model name, such as tC or xB, in the model field. Manufacturer names in the data are Toyota entities, apart from the FR-S built by Subaru and the iA built by Mazda.
Which character shows the model year on a Scion?
The tenth, the same place as on any car sold in the United States. Letters and digits repeat on a long cycle, so confirm the era with the decoder rather than guessing. If the year in the result differs from the advert, the advert or the VIN needs explaining.
Where was my Scion built?
The plant field in the decode answers it. Samples returned Toyota City, Sagamihara and Kanegasaki in Japan for the Toyota-built cars, Ota in Japan for the Subaru-built FR-S and Salamanca in Mexico for the iA.
Does the decoder show recalls or accidents?
No. It describes the build. Recalls are tied to the VIN in NHTSA's recall data, and accidents, brands and mileage records sit in history databases. Use a recall search for open campaigns and a history report for the rest.
Why does my decode flag the ninth character?
Position nine is a check digit that tests whether the other characters were copied correctly. A flag on a short or misread VIN is common. Retype all 17 characters from the photo and compare them with the title.
Now check the car itself
The guide explains what to look for. The report shows what this VIN has on record.