Map the NA and NB family before you plan the car

Generated from content/lms/platform-specific-spec-miata/01-identify-the-car-before-you-plan-it/01-map-the-na-nb-family.md; edit the source file, not this page.

Source path: content/lms/platform-specific-spec-miata/01-identify-the-car-before-you-plan-it/01-map-the-na-nb-family.md

Course: Race a Spec Miata by the rulebook

Module: Identify the car before you plan it

Estimated duration: 50 minutes

Spec Miata planning starts before you price parts, choose a donor, or believe a build sheet. Your first job is to map the car into the correct NA or NB family and then let that family control the rest of the planning conversation. That sounds basic until you are standing over a used race car with pop-up headlights, missing trim, a seller story, a cage, a trunk full of spares, and three different years mentioned in the ad. In Spec Miata, the family is not cosmetic trivia. It drives which body shell you are looking at, which engine generation belongs in the car, where the identifying sensors should live, where the ECU should be, what electronics should exist, which sway bar pattern is expected, whether VVT should be present, and which rule table you have to use before money moves.

The principle is simple: identify the chassis generation first, then identify the sub-family, then make the rule plan fit the car instead of making the car fit the story. The SCCA Spec Miata rule text puts the foundation in plain terms: the firewall VIN controls the model-year classification, and the original OEM VIN stamped there must correspond with the model year automobile classified. The NASA rule packet carries the same core idea: the firewall VIN takes precedence and the VIN plates or stampings remain in place. That is why this lesson is not a shopping checklist about nice Miatas. It is a planning skill for race cars. You are learning to prevent a bad chain of assumptions at the very beginning.

For this lesson, keep the scope tight. You are not yet doing a full compliance audit, not deciding whether the car is a true Spec Miata rather than a look-alike, and not using the complete spec line to spend money. Those are related skills. Here, you are building the family map that those later checks depend on. By the end, you should be able to stand at the front of a candidate NA or NB car, identify whether it is NA1, NA2, NB1, or NB2, say what evidence led you there, and name the follow-up checks that protect you from a swapped or misrepresented car.

The four-family map

For Tracky planning purposes, the NA and NB Spec Miata universe in the bonded material divides into four working families. NA1 is 1990 through 1993 and carries the 1.6 engine. NA2 is 1994 through 1997 and carries the 1.8 engine. NB1 is 1999 through 2000 and carries the 1.8 engine. NB2 is 2001 through 2005 and carries the 1.8 engine with VVT. The training overview lists those families directly and then gives the physical cues you can use before you crawl through the whole rulebook.

Do not collapse the map into only NA versus NB. That is the beginner error. A pop-up-headlight NA shell can be NA1 or NA2, and those are not the same planning object. A fixed-headlamp NB shell can be NB1 or NB2, and the VVT difference on the NB2 matters. If you start with only the broad body generation, you will miss the sub-family evidence that tells you which engine controls, intake pattern, electronics, and rule assumptions should be present.

NA1 covers 1990 to 1993. The training overview identifies NA1 by pop-up style headlights, square door bottoms, chrome door handles, an open air intake, and a cam position sensor at the rear passenger side of the head or valve cover. Its engine family is 1.6. This is the earliest Spec Miata planning branch. When you see a pop-up-headlight car, do not immediately call it a 1.6. The headlights only get you to NA. You still need the intake and cam-position-sensor location to separate NA1 from NA2.

NA2 covers 1994 to 1997. It also has pop-up style headlights and square door bottoms, so the outside shell can trick you if you stop there. The training overview separates it by the closed air intake, the cam position sensor at the rear driver side of the head or valve cover, and the year split inside the family: 1994 and 1995 do not have a crank position sensor and do not have an OBDII port, while 1996 and 1997 do have a crank position sensor and are the first years to have an OBDII port. That detail matters because it gives you a built-in electronics expectation. If someone presents a 1996 or 1997 NA2 story, a dead or absent OBDII check is not just an inconvenience. It is a mismatch you have to resolve before planning.

NB1 covers 1999 to 2000. It moves to the newer headlamp style, rounded doors, recessed door handles, closed air intake, and a cam position electrical sensor at the front passenger side valve cover. That sensor location is useful because it keeps you from treating every non-VVT NB as a generic 1.8 car. The NB1 is a fixed-headlamp car without the NB2 VVT signature.

NB2 covers 2001 to 2005. It has the newer headlamp style, rounded doors, recessed door handles, and the VVT assembly located on the front top valve cover on the passenger side. This is the family where the visible VVT cue becomes the quick separator. If the car is presented as a 2001 to 2005 NB2, you expect that VVT signature. If it is not there, you do not solve that discrepancy by guessing. You record it and keep the planning money in your pocket until the VIN and engine-family evidence agree.

Why this mapping skill matters

Spec Miata rules are built around controlled variation. The class exists to make production-based cars race against each other with limited modifications. The SCCA rule text says the class is intended to provide low-cost, production-based competition with limited modifications, and it also says the rules are more open than Showroom Stock but more restricted than Improved Touring. NASA frames its rules as mandates that keep vehicles inside clearly established limits so the contest becomes a test of driving skill. Those are not philosophical niceties. They explain why your family map matters: the class does not allow you to freely assemble the fastest mixture of NA and NB parts.

The SCCA text states that updating or backdating is not allowed for any car, model, specification, or component unless specifically authorized. It also says all engines and internal components used in rebuilding or refurbishment must have been offered for sale by Mazda in the United States for the correct year and VIN of car, except where the rules otherwise provide. That turns family identification into a cost-control and legality-control skill. You are not merely asking what year the dashboard looks like. You are identifying the legal baseline the car has to match.

The NASA rules carry the same planning pressure from another direction: modifications, addition or removal of parts or material are not allowed unless specified or approved, and additional modifications are not permitted. Replacement parts not specified by the rules must be OEM or exact equivalent. If your family map is wrong, every later decision can become wrong: restrictor choice, electronics expectation, engine-control assumptions, allowed interior work, ballast planning, donor-part plan, and even whether a regional class path applies.

Think of family mapping as the first filter in a three-filter process. First, you map the family: NA1, NA2, NB1, or NB2. Second, you verify the car against the hard identifiers: firewall VIN, OBDII presence where expected, ECU location, sensor locations, and visual cues. Third, you use the current rule table and class line before you spend. This lesson owns the first filter and shows how it feeds the second.

The inspection sequence

Start outside the car with the body-generation cues because they are fast and non-invasive. Pop-up headlights put you in NA territory. Newer fixed headlamps put you in NB territory. Square door bottoms and chrome door handles support NA1 identification in the training overview, while rounded doors and recessed door handles support NB identification. These cues are not enough by themselves, but they get your eyes organized.

Then move to the intake and top-front engine cues. On an NA1, you expect the open air intake and a cam position sensor at the rear passenger side of the head or valve cover. On an NA2, you expect a closed air intake and a cam position sensor at the rear driver side of the head or valve cover. On an NB1, you expect a closed air intake and a cam position electrical sensor at the front passenger side valve cover. On an NB2, you expect VVT at the front top valve cover on the passenger side. This is the practical heart of the lesson: you identify the family from several physical clues that should point in the same direction.

Next, ask the electronics question that fits the family. The training overview says the ECU must be in the stock location: an NA ECU is on the passenger-side floorboard footwell, while an NB ECU is mounted vertically under the dash on the far left side. It also says the OBDII port must be operational on all Miatas from 1996 to present. That gives you a clean split inside NA2 and across the whole NB range. A 1990 to 1995 car does not create the same OBDII expectation. A 1996 or newer car does.

For 1996 and newer cars, do not just point at a connector. Plug in a scanner and verify that the port is live. The training overview treats that as the check. It also gives a quick thermal-reader comparison: take water temperature from the water housing at the sensor on the back of the engine, compare it with the OBDII scanner water-temperature reading, and treat a scanner reading that is 20 degrees or more cooler than the thermal reading as evidence that the wiring harness has been modified to make the computer think the engine is running cooler and leaner than it really is. That is a later compliance-style check, but it belongs in your family-mapping workflow because it protects your electronics assumptions.

Then confirm the firewall VIN before you let any soft evidence settle the matter. The training overview places VIN identification in the middle of the firewall above the valve cover and tells you to count 10 digits from left to right for model-year identification. The SCCA and NASA rule chunks both emphasize the original OEM VIN stamped on the firewall and that the firewall VIN takes precedence. For planning, that means the firewall VIN is the anchor. Body cues and engine cues can start the map, but the firewall VIN is what keeps the map from becoming guesswork.

Finally, write down conflicts. Do not solve them in your head. A 1994 story with a 1996-style electronics claim, a 2001 story with no VVT signature, a pop-up shell with NB-style ECU placement, or an OBDII-era car with a dead OBDII port is not automatically illegal from this lesson alone, but it is no longer a simple family map. It needs the next lesson: verify the car before you trust the story. The skill here is knowing when the evidence is clean and when it has become a problem list.

Sub-skill 1: body-to-family triage

Your first sub-skill is fast body triage. You are using low-effort, high-visibility cues to decide where to look next. NA1 and NA2 both use pop-up style headlights and square door bottoms in the training overview. NA1 is further associated with chrome door handles. NB1 and NB2 are identified by the newer headlamps, rounded doors, and recessed door handles.

The point of body triage is not to finish the identification. It is to prevent wandering. If the body puts you in NA territory, you go straight to the rear of the valve cover and the intake style. If the body puts you in NB territory, you go to the front passenger side valve cover and look for the NB1 sensor pattern or NB2 VVT pattern. Body triage saves time because it tells your eyes where to work.

A good body triage result sounds like this: the body cues say NA, but I have not separated NA1 from NA2 yet. Or: the body cues say NB, but I have not separated NB1 from NB2 yet. That language matters. It keeps you from treating a half-identification as a complete identification.

Sub-skill 2: engine-bay confirmation

The second sub-skill is engine-bay confirmation. This is where the family map becomes specific. NA1 should show the open air intake and the cam position sensor on the rear passenger side. NA2 should show the closed air intake and the cam position sensor on the rear driver side. NB1 should show the closed air intake and the cam position electrical sensor at the front passenger side valve cover. NB2 should show the VVT unit at the front top valve cover on the passenger side.

This is also where you begin detecting cars that need a deeper look. The rules material does not authorize you to infer legality from one part sitting in one place, but it does give you expected configurations. If an NA shell has the wrong sensor location for the claimed sub-family, your answer is not to become creative. Your answer is to stop calling it identified. The car has a mismatch to resolve.

When you practice this, use a three-column note: claimed year, visible family cues, unresolved conflicts. For a clean car, the third column stays empty. For a messy car, the third column becomes the task list for the next inspection. This is how you avoid buying a story.

Sub-skill 3: electronics expectation

The third sub-skill is matching electronics to year and family. The training overview gives three key rules for this lesson. The NA ECU should be on the passenger-side floorboard footwell. The NB ECU should be mounted vertically under the dash on the far left side. The OBDII port must be operational on all 1996 and later Miatas.

This gives you a useful planning decision. For a 1990 to 1995 car, you do not use OBDII operation as the same family-confirming test. For a 1996 to 2005 car, you do. For a 1996 or 1997 NA2, the overview specifically says those years do have a crank position sensor and are the first years to have an OBDII port. For NB1 and NB2, OBDII should be part of your expectation because they are 1999 to 2005 cars.

The scanner check also teaches discipline. A connector under the dash is not the same as a live port, and a live reading is not automatically clean if the temperature comparison suggests harness manipulation. For family mapping, you are not writing a protest. You are deciding whether the car is straightforward enough to plan. A live, plausible OBDII signal supports the map. A dead port or suspicious temperature split moves the car into verification work.

Sub-skill 4: firewall VIN anchoring

The fourth sub-skill is anchoring the family map to the firewall VIN. The training overview locates the VIN in the middle of the firewall above the valve cover and tells you to count the tenth digit from left to right for the year. The SCCA and NASA chunks both make the firewall VIN the controlling reference by saying it must correspond with the model-year automobile classified and that it takes precedence.

In practice, this means you never let exterior paint, a logbook rumor, a seller's ad title, or a class sticker outrank the firewall VIN. The VIN is not the whole compliance inspection, but it is the first hard reference for model year. If the visible family cues and the VIN do not agree, the car is not ready for planning. It is ready for documentation.

A clean result sounds like this: firewall VIN year aligns with NA2, body cues are NA, engine-bay cues are NA2, and electronics expectations match the year. A dirty result sounds like this: firewall VIN points to NB2, but there is no VVT cue and the seller calls it a 1999. The second car may have an explanation, but you do not spend on assumptions while the explanation is missing.

Sub-skill 5: rule-bound planning

The fifth sub-skill is knowing what to do with the family map after you have it. The family map is not trivia; it controls the planning boundaries. SCCA says authorized modifications are the only modifications and safety items permitted or required, with updating and backdating prohibited unless specifically authorized. NASA says the rules are not guidelines and must be strictly followed. Both rule sets treat the car's identity as the baseline for what can be on it.

That is why the first planning sentence should not be I need to build a Spec Miata. It should be I have identified this as an NA2, or I have identified this as an NB1, and now I will check the current spec line and class rules for that family. The difference is practical. The first sentence invites generic parts shopping. The second sentence forces you to match the car.

This also keeps regional variants in their place. The regional class rules chunk says Spec Miata must comply with the SCCA GCR and category specifications for SM, and it discusses tire-rule exceptions for SMT and SMSE-T as well as an SMSE path for 1.6 cars in SEDiv. Those rules may matter later depending on where and what you run, but they do not replace the family map. You still start by knowing whether the car is NA1, NA2, NB1, or NB2.

Worked example: a pop-up-headlight donor with a 1996 story

You are looking at a caged pop-up-headlight Miata advertised as a 1996 Spec Miata project. The body gives you only the broad NA answer: pop-up style headlights and square door bottoms fit the NA description. At this point, do not call it an NA2 because the headlights alone do not separate NA1 from NA2.

Open the hood. You look for the intake and cam position sensor location. If the car is truly in the 1996 to 1997 NA2 branch, the training overview says you expect a closed air intake, the cam position sensor at the rear driver side of the head or valve cover, a crank position sensor, and an OBDII port because 1996 and 1997 are the first NA years with OBDII. If instead you see the open intake and rear passenger-side cam-position-sensor arrangement associated with NA1, the car is no longer a clean 1996 map. You have a conflict.

Now move to the electronics expectation. A 1996 car should have an operational OBDII port. Plug in a scanner. If the port is live and the ECU location fits NA placement on the passenger-side floorboard footwell, the electronics support the NA2 story. If the port is dead or absent, you have another conflict. If you have a thermal reader, compare water temperature at the water housing sensor on the back of the engine with the OBDII scanner reading. A scanner reading 20 degrees or more cooler than the thermal reading is treated in the training overview as evidence of a modified harness. That does not belong in the family map as a final legal judgment, but it is a strong reason to stop trusting the build story.

Finish with the firewall VIN. The training overview says the VIN is in the middle of the firewall above the valve cover and tells you to count 10 digits from left to right. The rule chunks make the firewall VIN the controlling model-year reference. If the tenth digit and the physical evidence agree on a 1996 NA2, you have a workable family map and can move to the spec line. If the firewall VIN says a different year family, you have a documentation problem before you have a build plan.

The success criterion in this example is not that you prove the car is legal in every respect. The success criterion is that you refuse to make a plan until the claimed 1996 NA2 identity is supported by body cues, engine-bay cues, electronics expectation, and firewall VIN.

Worked example: a fixed-headlamp car claimed as a 2001 but missing the VVT cue

Now you are looking at a fixed-headlamp Miata with rounded doors and recessed door handles. The body triage says NB. The seller calls it a 2001, which would put it in the NB2 family. According to the training overview, NB2 is 2001 through 2005, is a 1.8 with VVT, and has the VVT located on the front top valve cover on the passenger side.

Open the hood and go straight to the NB separator. For an NB1, the training overview points to the closed air intake and a cam position electrical sensor at the front passenger side valve cover. For an NB2, it points to the VVT location on the front top valve cover on the passenger side. If the claimed 2001 car has the NB body cues but no VVT signature, you do not treat it as a normal NB2. It may be mislabeled, swapped, modified, or misunderstood. The lesson does not require you to diagnose all of that on the spot. It requires you to stop the planning chain.

Check the ECU location and OBDII operation next. Because any NB is 1999 through 2005 in this map, OBDII should be operational. The NB ECU should be mounted vertically under the dash on the far left side. A live OBDII port and correct NB ECU location support that you are in the NB universe, but they do not by themselves turn a non-VVT engine bay into a clean 2001 NB2 map.

Then anchor the firewall VIN. If the firewall VIN points to 2001 and the VVT cue is missing, the conflict becomes more serious because the controlling year says NB2 while the engine-bay evidence does not show the NB2 marker. If the firewall VIN points to 1999 or 2000, the seller's 2001 claim is the problem and the car may instead be mapping as NB1. Either way, the family map has done its job: it has prevented you from planning restrictor, electronics, and build spending around a casual year claim.

Worked example: an NA1 candidate for regional 1.6 planning

The regional rules chunk mentions an SMSE class purpose of giving owners of the 1.6 Mazda Miata a low-cost class in which to compete in SEDiv series such as SARRC, ECR, and Time Trials. That regional path is not the whole national Spec Miata plan, and the rule text says SMSE must comply with the current SCCA GCR and category specification for all 1.6 cars listed for SM. Still, it shows why an NA1 map can matter in a real planning conversation.

Suppose the car has pop-up headlights, square door bottoms, chrome door handles, an open air intake, and the cam position sensor on the rear passenger side of the head or valve cover. Those training-overview cues map it as NA1, 1990 through 1993, 1.6. Now the planning conversation is specific. You are not deciding whether any cheap Miata can become the right regional car. You are deciding whether this 1.6 NA1 identity is supported well enough to continue.

Because NA1 is 1990 through 1993, the OBDII expectation is different from a 1996 and newer car. You still anchor the firewall VIN, and you still use current rules before you spend, but you do not fail the car simply because it lacks the OBDII pattern that belongs to later cars. This is the value of family mapping: it keeps a correct old-car feature from looking like a defect, and it keeps a wrong later-car feature from being waved away.

Calibration cues: how you know you are doing it well

The first calibration cue is speed with restraint. A good intermediate driver or builder can make the first body triage in under a minute, but still refuses to call the job finished. You should hear yourself say NA body, need NA1 versus NA2, or NB body, need NB1 versus NB2. If your notes jump straight from headlights to final year family, you are skipping the skill.

The second cue is evidence clustering. A clean family map has multiple cues pointing the same way: body style, intake style, sensor location, electronics expectation, ECU location, and firewall VIN. You should be able to explain the identification without relying on one cue. If one cue is missing because a race car has been stripped or modified, the remaining cues and the firewall VIN become more important.

The third cue is conflict discipline. You are improving when you stop smoothing over mismatches. A car advertised as a 1996 but showing NA1 engine-bay cues is not close enough. A 2001 claim without the NB2 VVT cue is not close enough. An OBDII-era car with a dead OBDII port is not close enough. Your output should be a clean map or a clear list of unresolved conflicts.

The fourth cue is planning language. Good identification changes the way you talk. You stop saying this is an NA Miata and start saying this appears to be an NA2, pending firewall VIN confirmation and OBDII operation. You stop saying this is an NB and start saying this maps as NB1 because it has the NB body cues and the front passenger-side cam-position-sensor pattern, with no NB2 VVT cue. That precision keeps you honest.

The fifth cue is knowing when to hand off to the next lesson. Once the family is mapped, you do not need to prove every Spec Miata legality item in this lesson. Restrictor color and logo, shock identification, sway bar configuration, hardtop security, tire rule, battery location, mirrors, wipers, body damage, and axle inspection all matter, but they belong to later compliance and spec-line work. Your job here is to make those later checks point at the correct car.

Common mistakes

The first common mistake is the headline-only identification. You see pop-up headlights and say 1.6 NA1. That is wrong because the training overview puts both NA1 and NA2 under pop-up style headlights. Good looks like using the pop-up headlights only as NA triage, then separating NA1 from NA2 with intake style, cam-position-sensor location, year, VIN, and electronics expectation.

The second mistake is treating every NB as the same 1.8 plan. The training overview separates NB1 from NB2 by the VVT cue. Good looks like checking the front passenger side of the valve cover area and asking whether you are seeing the NB1 cam-position electrical sensor pattern or the NB2 VVT pattern. If the claimed 2001 to 2005 car does not show the VVT marker, good work means you write down the mismatch instead of planning around the claim.

The third mistake is believing the seller's year before the firewall VIN. The SCCA and NASA chunks both emphasize the firewall VIN and its precedence. Good looks like using the seller's year as a hypothesis, not as the answer. You check the firewall VIN and count the tenth digit for the year reference described in the training overview.

The fourth mistake is confusing a present OBDII connector with a verified electronics system. The training overview says the OBDII port must be operational on 1996 and later Miatas and says to plug in a scanner to verify the port is live. Good looks like actually connecting the scanner. Better still, when you have a thermal reader, you compare the water temperature reading at the engine sensor area with the OBDII scanner reading and treat a 20-degree-or-more cooler scanner reading as a harness-modification warning.

The fifth mistake is starting parts planning before identity planning. The rules material is clear that authorized modifications and correct-year components matter. Good looks like pausing the shopping list until you know the family and have the current GCR or applicable NASA rule line in front of you. In Spec Miata, a bargain part that belongs to the wrong family can create more cost than it saves.

The sixth mistake is letting regional class language replace the core map. The regional chunk discusses SMT, SMSE-T, Toyo tire exceptions, and the SMSE path for 1.6 cars, but it also points back to the SCCA GCR and Spec Miata category specifications. Good looks like using regional rules after you know the car, not using a regional label to avoid identifying the car.

Drill: the four-family walkaround

At your next event, do this drill on three cars with permission from the owners or crew. You are not inspecting legality, touching parts, or making accusations. You are practicing family mapping. Pick one obvious NA, one obvious NB, and one car where you do not already know the year.

For each car, give yourself five minutes. Minute one is body triage: write NA or NB, then list the visible cues such as pop-up headlights, new headlamps, square door bottoms, rounded doors, chrome handles, or recessed handles. Minute two is engine-bay family confirmation: for an NA, look for open versus closed intake and rear passenger-side versus rear driver-side cam-position-sensor placement; for an NB, look for the front passenger-side sensor pattern or the NB2 VVT marker. Minute three is electronics expectation: decide whether OBDII should be present and operational based on the mapped year range, and identify where the ECU should be for NA or NB. Minute four is VIN anchoring: locate the firewall VIN area and, if appropriate and permitted, identify the tenth digit as the year reference. Minute five is conflict logging: write clean map or write the unresolved conflicts.

Do the drill on three cars in one day. Your success criterion is not speed by itself. Your success criterion is that your final note for each car uses one of these forms: clean NA1 map, clean NA2 map, clean NB1 map, clean NB2 map, or unresolved because evidence conflicts. If you write just NA Miata or NB Miata, repeat the drill because you stopped too early.

A stronger version of the drill is to add one OBDII-era check when an owner permits it. On a 1996 or later car, plug in a scanner and verify the port is live. If you also have a thermal reader and the owner agrees, compare the scanner water-temperature reading with a thermal reading at the water housing sensor area described in the training overview. Record whether the two readings are reasonably aligned or whether the scanner is 20 degrees or more cooler. This turns the drill from visual identification into evidence-based planning.

When this principle breaks down

The family map is powerful, but it is not a full legality verdict. Race cars get rebuilt. Interiors get stripped within allowed boundaries. Safety equipment gets installed. Doors can be gutted where the rules allow it with NASCAR-style side protection. Pedals may be modified for driver comfort and accessibility. Ballast can be added under strict mounting rules. Air bag systems are disarmed and may be removed. Spare tires, tools, carpets, mats, and some interior materials may be removed. If you expect a showroom car, you will misread a legal race car.

That is why this lesson separates family mapping from compliance inspection. Some missing comfort parts are normal under the rules. Some removed interior materials are allowed. Some driver-fit modifications are allowed. But none of that erases the family identity problem. The rules allow certain modifications for safety, fit, and racing preparation; they do not make the car a free mixture of model years.

The practical boundary is this: family mapping asks what car is this, while compliance inspection asks whether this car has been prepared legally. Do not confuse those questions. If a door panel has been altered, that may belong to the safety and cage-rule discussion. If the firewall VIN, sensor location, VVT marker, ECU location, and OBDII expectation do not align with the claimed family, that belongs to identity verification before planning.

Cross-references

After this lesson, the natural next skill is verifying the car before you trust the story. That lesson should take over when the family map has conflicts: mismatched VIN story, dead OBDII on a 1996 or newer car, questionable ECU location, missing VVT cue on an NB2 claim, or temperature data that suggests harness modification.

Another related skill is separating a true Spec Miata from a look-alike. The bonded chunks include many compliance cues that are outside this lesson's main scope: restrictor location between throttle body and air intake, required gaskets on both sides, SCCA stamped or Mazda etched restrictor logo, restrictor color by NB year, Penske shock identifiers, sway bar configurations, hardtop security, tire sizes, mirrors, windshield wipers, battery location, required decals, body damage, and axle concerns. Those are real checks, but they are downstream of the family map.

A third related skill is using the spec line before you spend. The training overview says to reference the current GCR for accuracy, and the SCCA rules require a Mazda factory shop manual for the specific make, model, and year. That means your map should lead you to the correct current documents, not to memory or forum advice. Once you know the car is NA1, NA2, NB1, or NB2, you can read the current spec line with the right baseline in mind.

Final operating rule

At intermediate level, your goal is not to become a scrutineer in one lesson. Your goal is to stop being casual about identity. Spec Miata planning is strict because the class is built around controlled, production-based cars with limited modifications. The family map protects your budget, your legality, and your future troubleshooting. Start with the body, confirm in the engine bay, match the electronics, anchor the firewall VIN, and only then plan the car.

Worked example: a pop-up-headlight donor with a 1996 story

A 1996 claim should map as NA2, not merely NA. The body cues get you to NA, but the closed intake, rear driver-side cam-position-sensor location, crank-position-sensor expectation, OBDII port, and firewall VIN are what make the map credible. If the car shows NA1 engine-bay cues or a dead OBDII port, the correct result is unresolved identity, not a shopping list.

Worked example: a fixed-headlamp car claimed as a 2001 but missing the VVT cue

A 2001 claim should map as NB2. The fixed headlamps, rounded doors, and recessed handles identify the NB body family, but the NB2 separator is the VVT cue on the front top valve cover on the passenger side. If that cue is missing, the family map has a conflict that must be resolved with the firewall VIN and further verification before planning.

Worked example: an NA1 candidate for regional 1.6 planning

An NA1 candidate should show the 1990 to 1993 1.6 pattern: pop-up headlights, square door bottoms, chrome door handles, open intake, and rear passenger-side cam-position-sensor location. Regional 1.6 opportunities may matter later, but the family map still comes first and must be anchored to the firewall VIN and current rules.

Common mistakes

The main errors are stopping at headlight style, treating every NB as the same 1.8 plan, believing the seller before the firewall VIN, confusing an OBDII connector with a verified live port, buying parts before identity is stable, and using regional class labels as a substitute for identifying the car. Good work replaces each shortcut with a specific evidence chain.

Drill: the four-family walkaround

At the next event, map three cars in five minutes each with owner permission. Spend one minute on body triage, one on engine-bay family confirmation, one on electronics expectation, one on firewall VIN anchoring, and one on conflict logging. Success means each final note says clean NA1, clean NA2, clean NB1, clean NB2, or unresolved because evidence conflicts.

When this principle breaks down

The family map is not a complete legality inspection. Race cars may legally have removed interior materials, driver-fit pedal changes, safety equipment, ballast, disarmed airbags, and other rule-authorized changes. Those changes can make a legal race car look unlike a street car. They do not remove the need for correct family identification.

Author Review

No quiz questions are attached to this lesson.

Sources

#	Document	Chunk	Pages	Score	Collection
1	Miata Training Overview	a2e9f3ed2527a57ee63f88269754dd3b	1	1	uio_books_raw_v1
2	GCR_SM	8aaac52cf61cfb33dae2abb73f7a7a52	1	1	uio_books_raw_v1
3	2024_Spec_Miata_Rules	f486666f0d1f6f61102ddf03fac74a87	1	1	uio_books_raw_v1
4	2024 NASA Spec Miata Rules	66ac45c14be617ab2977cb35ac9db5f4	1	1	uio_books_raw_v1
5	Miata Training Overview	ff341ef5fb3ac52ff9270426cca8eb42	9	1	uio_books_raw_v1
6	2023 Regional Class Rules	63384ad5199ffa8ecc8abca763c50e09	4	1	uio_books_raw_v1
7	2024 NASA Spec Miata Rules	e164a32416f99ff0fbd3ae603ec22e15	23	1	uio_books_raw_v1
8	GCR_SM	a2f7aa9cd510712c80997e684860bcc3	12	1	uio_books_raw_v1