B-Series Street & Strip™
A practical B-series performance manual for enthusiasts who want an old-school Honda build to work as a complete package—whether the direction is naturally aspirated, turbocharged, street-focused, strip-focused, or a balanced combination.
Turn B-series potential into a coherent build plan.
The platform offers many legitimate combinations. The hard part is choosing parts and priorities that belong together. This guide organizes the decisions around use case, power system, driveline, tuning, traction, and durability.
Choose a direction before the parts choose it for you.
Define the engine family, use case, response goals, budget, fuel, driveline, and reliability target so the build develops around a controlled mission.
Match airflow, fuel, calibration, and hardware.
Evaluate naturally aspirated and turbo paths as complete systems rather than isolated component upgrades.
Build for repeatability, not a single number.
Use commissioning, tuning discipline, thermal awareness, driveline checks, and post-run inspection to keep performance tied to reliability.
Old-school Honda performance with modern process control.
B-Series Architecture
Understand the B16/B18/B20 landscape, define the build mission, and control compatibility before committing to a combination.
NA, Turbo, Fuel & Driveline
Connect cylinder-head, bottom-end, induction, fueling, transmission, and supporting-system decisions to the intended use.
Tuning, Traction & Validation
Prepare the package for calibration, controlled shakedown, traction management, heat-cycle review, and repeatable street or track use.
Old-school speed still rewards disciplined systems thinking.
A strong B-series build is the result of compatible choices working together. The manual keeps the engine, airflow, fuel, calibration, transmission, chassis, and reliability plan connected from the first decision to the final shakedown.
Baseline the car, choose the build path, then prove the package.
Use the guide to document the starting condition, select a coherent performance direction, sequence the build, and record validation results. Always confirm model-specific service procedures and exact component requirements against current authoritative documentation.
