ICD code V33.3XXA – Three-wheeled vehicle collision, unspecified occupant

Key takeaways

V33.3XXA is a billable ICD-10-CM code valid for fiscal year 2026, while parent code V33.3 is non-billable and cannot go on a claim.

The 7th character A designates the initial encounter, so use it only while the patient is still in active treatment.

V33.3XXA, V33.3XXD and V33.3XXS share the same parent, and picking the wrong one is a top denial trigger.

External cause codes are always secondary, so the injury itself carries the primary diagnosis on the claim.

Pabau submits claims through the Claim.MD clearinghouse, runs real-time eligibility checks, and tracks each claim status in one place.

ICD-10 code V33.3XXA: Definition and billable status

ICD-10 code V33.3XXA is the billable ICD-10-CM code for an unspecified occupant of a three-wheeled motor vehicle. It covers a collision with a car, pick-up truck, or van in a nontraffic accident, initial encounter.

The code sits in the V30-V39 block of external cause codes, which covers occupants of three-wheeled motor vehicles injured in transport accidents. The CDC/NCHS ICD-10-CM web tool lists V33.3XXA as an active, billable code for fiscal year 2026, effective October 1, 2025.

The word nontraffic in the descriptor carries weight. ICD-10-CM treats a transport accident as nontraffic when it happens entirely somewhere other than a public highway. A collision in a parking lot, a yard, or on private land qualifies. The same crash on a public road does not.

The unspecified occupant designation applies when the medical record does not identify whether the injured person was the driver, a passenger, or another occupant. If that detail is documented, a more specific sibling code in the V33 family is correct instead.

Code details at a glance

The table below captures the structural attributes coders verify before submitting a claim. Check the fiscal year validity row. CMS updates ICD-10-CM codes every October 1, so a code billable in FY2026 needs re-checking for earlier dates of service.

According to the CMS ICD-10 codes page, external cause codes in Chapter 20 are assigned as secondary codes. They identify the circumstances of an injury, while the primary diagnosis describes the injury itself.

Understanding the 7th character: A, D, and S

The 7th character extension sets the encounter type for V33.3XX codes. Picking the wrong character is one of the most common reasons external cause claims are rejected on audit.

The ICD-10-CM Official Guidelines for Coding and Reporting define each encounter type precisely. Initial encounter does not simply mean the first visit to any provider.

Here is a practical way to tell A from D. If the clinician is still deciding how to manage the injury, character A applies. Once the treatment plan is set and the patient is recovering or rehabilitating, character D is correct.

Sequela (S) applies when a new condition develops as a direct consequence of the collision injury, such as chronic pain documented months later.

Sibling codes and the V33 hierarchy

V33.3 is the non-billable parent code for unspecified occupant collisions in the V33 category. Submitting V33.3 on a claim results in a rejection. Coders select one of its child codes, each carrying the XX placeholder followed by an encounter suffix.

The unspecified occupant code is a last resort rather than a default. When the record contains any indication of the patient’s role, even a phrase like the driver was treated, the specific code is required. The AAPC Codify ICD-10-CM lookup shows the full V33 hierarchy with applicable-to notes.

Two facts decide the code, and the record has to settle both. The chart below runs them in order.

Crosswalking V33.3XXA to ICD-9-CM

Practices processing legacy claims may need to map V33.3XXA back to its approximate ICD-9-CM equivalent. Translations between the two systems are approximate rather than exact, because they carry different levels of clinical specificity. No ICD-9-CM code captures the 7th character encounter detail that V33.3XXA carries.

The E822.9 mapping comes from the final general equivalence mappings published by CMS and CDC. It is approximate. ICD-9-CM had no way to record vehicle type, occupant role, or encounter phase the way ICD-10-CM does. Label every V33.3XXA crosswalk as approximate in your own documentation.

Documentation requirements for V33.3XXA

A clean claim built on V33.3XXA needs the medical record to support each element of the descriptor. Miss one of the anchors below and a payer can deny on specificity grounds.

• Vehicle type: The record must confirm the vehicle was a three-wheeled motor vehicle, such as a motorized tricycle or trike. Standard motorcycles and four-wheeled vehicles have separate code categories.
• Nontraffic setting: The record must place the collision somewhere other than a public highway. A crash on a public road falls outside this code.
• Occupant role: The record must state that the patient’s role is unknown, or contain no indication of driver versus passenger status. Any documented role points the coder to V33.0XXA, V33.1XXA, or V33.2XXA instead.
• Collision counterpart: The record must confirm the other vehicle was a car, pick-up truck, or van. Collisions with pedestrians, cyclists, heavy transport, or fixed objects use separate V33 sub-categories.
• Encounter type: The record must support the initial encounter designation. Emergency department notes, admission records, and surgical reports usually satisfy this. Routine follow-up notes do not.
• Additional external cause codes: Per CMS ICD-10 coding guidance, report secondary codes for place of occurrence (Y92), activity (Y93), and external cause status (Y99). Add them whenever the record carries that information.

Practices handling high volumes of motor vehicle claims benefit from intake documentation that captures the anchors above at first presentation. Capturing them once beats reconstructing them from a chart six weeks later. Our guide to clean claim requirements covers the wider checks a payer applies before it pays a line.

Coding guidelines and common mistakes

V33.3XXA coding errors cluster into five patterns. Each one is preventable with a single documentation review before the claim goes out.

• Submitting the non-billable parent V33.3: The parent code has no 7th character and is not reportable. Payers reject it automatically. Select V33.3XXA, V33.3XXD, or V33.3XXS depending on the encounter type.
• Defaulting to unspecified occupant when the role is documented: V33.3XXA is meant for records where the occupant role cannot be determined. Using it as a shortcut when the note names a driver is a specificity error payers flag on audit.
• Applying character A to follow-up visits: Character D covers fracture checks, suture removal, physical therapy, and outpatient rehab. Using A beyond the active treatment phase is a common audit finding. Section I.C.20 of the official guidelines sets out the A, D, and S distinction for external cause codes.
• Missing secondary external cause codes: Payers may expect codes covering the place of occurrence and the activity alongside V33.3XXA. Omitting them when the record carries that detail is a completeness problem. Reviewing denial codes shows which CARC and RARC codes payers use to flag incomplete reporting.
• Sequencing V33.3XXA as a primary code: External cause codes in Chapter 20 are always secondary. The primary diagnosis describes the physical injury, such as a fracture, laceration, or contusion code. Reversing that order is a claim structure error.

A run of denials on external cause codes usually points at the intake note rather than the coder. The rules on this code family are short. Once the record captures the collision properly, the code almost picks itself.

How Pabau supports V33.3XXA documentation and claim submission

Accident detail often lands in a free-text note, then has to be hunted down weeks later when a denial arrives. Vehicle type, occupant role, and the encounter phase are all in the chart somewhere. Finding them again costs more than recording them properly did.

Practice management software like Pabau keeps that detail on the patient record, in structured intake and treatment notes your team completes at the first visit. Coders read the same record the clinician wrote, so occupant role and encounter phase are settled before the claim is built.

Pabau also connects to the Claim.MD clearinghouse. You can submit claims from the same system and run real-time eligibility checks before the appointment. Claim status comes back into Pabau, so nobody logs into a payer portal to chase it. Pabau flags missing details on a claim, such as an absent membership or authorization, before you send it.

Structured records are what make cleaner claims management possible, because the coder never has to guess what the clinician saw. On a code like V33.3XXA, that is the difference between a clean submission and a rework queue.

Submit external cause claims with fewer denials

Pabau connects to the Claim.MD clearinghouse, so you can submit claims, run real-time eligibility checks, and track each claim status in one place. See how it fits your coding workflow in a live demo.

Book a demo

Conclusion

The denials on this code come from three places, and all three are decided before the claim is built. Submitting the parent V33.3, picking the wrong 7th character, and defaulting to unspecified occupant account for most rejections here.

So the work belongs at intake rather than in the appeals queue. Ask for vehicle type, occupant role, and the nontraffic setting while the patient is still in front of you. A coder holding those three facts can select the code in seconds.

Pabau keeps that detail on the patient record and sends the finished claim through Claim.MD. Book a demo to see how your team could cut rework on external cause claims.

Continue your research

Need the foundations behind external cause coding? Medical billing fundamentals covers how primary and secondary diagnosis codes are structured for clean claim submission.

Seeing denials you can’t immediately explain? Denial management in healthcare breaks down how to read CARC and RARC codes and build an appeal workflow.

Working through a remittance file? Electronic remittance advice explains how ERA 835 files report the reason a payer cut or denied a line.

Frequently asked questions