ICD-10 code V86.54XS: Driver of military vehicle, nontraffic sequela

Key takeaways

ICD-10 code V86.54XS covers the driver of a military vehicle injured in a nontraffic accident, reported at a sequela encounter.

The code is billable and valid for FY2026, and its descriptor has not changed since ICD-10-CM took effect in 2015.

V86.54XS is an external cause code, so the residual condition leads the claim and V86.54XS comes last.

Place, activity and status codes such as Y99.1 belong on the initial encounter only, never on a sequela claim.

The fifth character names the vehicle, so 4 is a military vehicle and 5 is a 3- or 4-wheeled ATV.

ICD-10 code V86.54XS reports the driver of a military vehicle injured in a nontraffic accident, at a sequela encounter. It is billable and specific, so it is valid on HIPAA-covered claims for FY2026.

Four things have to line up before it fits. The patient was driving. The vehicle belonged to the military. The accident happened entirely off the public highway. And this visit treats a late effect rather than the injury itself.

The last one is the hard part. Today’s code rests on a note somebody wrote a year ago. Capture that detail early and the rest is mechanical.

What the FY2026 tabular list says about V86.54XS

The table below pulls V86.54XS straight from the FY2026 ICD-10-CM tabular list published by the Centers for Medicare and Medicaid Services (CMS).

Two rows there do most of the work. Chapter 20 records how an injury happened, not what the injury was, which is why this code can never lead a claim. The 7th character then fixes the encounter type.

The wording has not changed since ICD-10-CM took effect on October 1, 2015. V86.54 has always been the military vehicle driver, so an older reference book still describes it correctly. What turns over each year is the fiscal-year file the code appears in.

How the 7th character S changes the encounter

S means the visit treats a sequela, the condition left behind once the acute phase of the injury has ended. Category V86 offers three 7th character values and no others, so every code in it ends in A, D or S.

D and S are the pair that get confused. Routine care during the healing phase takes D, such as a cast check or a wound review. S applies once healing has finished and something permanent remains, like a joint contracture, chronic pain or nerve damage.

There is also no time limit on a sequela code. A visit 14 months after the crash takes S, and so does a visit 14 years after it.

Keep the two codes in step as well. The 7th character on the external cause code should match the 7th character on the injury code for that encounter. Nothing about that rule is specific to military vehicles, and the rest of the transport chapter behaves the same way, V90.21XS included.

Reading V86.54XS from the chapter down

Each character narrows the code a little further. Reading it from the top down shows what every position carries, and where a near-miss code would take you instead.

V86.5 is a generic parent rather than an ATV code. It covers drivers of ambulances, fire engines, snowmobiles, dune buggies, military vehicles, ATVs and dirt bikes hurt off the public highway. The fifth character names the vehicle, and 4 is the military vehicle.

The X in the sixth position is a placeholder with no clinical meaning. It exists so the 7th character lands in the seventh slot. V86.54S is not a valid code, and a claim carrying it fails at submission.

The index path that quietly hands you a traffic code

The Index to External Causes reaches this code through a main term that defaults to traffic, which is where most wrong picks start. Follow the path in this order.

• Accident (to), transport (involving injury to)
• military vehicle occupant (traffic) → V86.34
• nontraffic → V86.94
• driver → V86.54

Stop one line early and you land on V86.34, the traffic code for an occupant whose role was never documented. Take the nontraffic subterm before the driver subterm. The same branch also holds passenger V86.64, hanger-on V86.74 and boarding or alighting V86.44.

Then confirm the pick in the tabular list before you submit it. The index gets you to V86.54 and stops there. Only the tabular list tells you that a 7th character is required, and that the X placeholder has to sit in front of it.

What ICD-10-CM counts as a military vehicle

ICD-10-CM defines both military vehicle and nontraffic in the notes at the head of the transport accident section. The definitions are stricter than most coders expect, and they settle the argument when a payer queries the code.

• Military vehicle: any motorized vehicle operating on a public roadway owned by the military and being operated by a member of the military
• Driver: an occupant of a transport vehicle who is operating or intending to operate it
• Passenger: any occupant other than the driver, except a person traveling on the outside
• Traffic accident: any vehicle accident occurring on the public highway
• Nontraffic accident: any vehicle accident that occurs entirely in any place other than a public highway
• Transport accident: the vehicle must be moving, running or in use for transport at the time

Two things drive the code. Ownership and operator decide whether the vehicle counts as a military vehicle at all. Location then decides the traffic split. V86.04 covers the public highway, while V86.54 covers a training ground, a closed base road or open terrain.

The definitions also set a default. An accident involving only off-road motor vehicles counts as nontraffic unless the record states otherwise. That default helps when the note is thin, though it is no substitute for a documented location.

A parked vehicle is a different story. Where the injury happened during servicing or maintenance, category V86 excludes it and points to W31.-. That branch names construction vehicles but no military ones, so W31.89, contact with other specified machinery, is usually the closest fit.

When another category outranks V86.54XS

Category V86 carries an Excludes1 note, so those codes never appear alongside it on a claim. A few other categories take priority as well, depending on who was hurt and what caused it.

Y36 and Y37 do not absorb every accident that happens on a base. Each Y37 subcategory names a weapon or combat mechanism, from explosions and aircraft destruction to firearms, nuclear, biological and chemical weapons. A rollover during a routine exercise is still a transport accident, so V86.54 remains the right family.

One more boundary is worth knowing. Y37 excludes a military vehicle that collides with a civilian vehicle, and sends those cases to counterpart codes such as V09.01 and V09.21. So check who else was involved before you settle on a category.

Sibling codes that look almost identical

The codes below share the vehicle, the location or the encounter type with V86.54XS. Occupant role is the axis that trips people up most often, because a single word in the note moves the code.

V86.94XS deserves a warning of its own. Reaching for the unspecified occupant code when the chart says the patient was driving lowers specificity for nothing. It also invites a documentation query that costs more time than reading the note would have.

How to sequence a sequela claim

The residual condition leads. The injury that caused it follows, carrying the 7th character S. V86.54XS is reported last, as the external cause. Sequela coding takes at least two codes, and for an injury it usually takes three.

Worked example. A soldier rolled a military truck on a training ground 14 months ago and fractured the first lumbar vertebra. The fracture has healed, and he now attends for chronic pain arising from it.

• G89.21 Chronic pain due to trauma, sequenced first as the residual condition
• S32.010S Wedge compression fracture of first lumbar vertebra, sequela
• V86.54XS Driver of military vehicle injured in nontraffic accident, sequela

Change the residual and the first slot changes with it. Where a lumbar sprain is what remains, S33.8XXS takes the lead instead, and the rest of the claim keeps the same shape.

What stays off the claim matters just as much. Place of occurrence (Y92), activity (Y93) and external cause status (Y99) codes are assigned only at the initial encounter. The guidelines state plainly that activity and status codes do not apply to late effects.

So Y92.84 for a military training ground and Y99.1 for military activity belong on the first claim only. Both look like a natural fit for a military case, which is exactly why they end up on sequela claims that should not carry them.

What the record has to show

Every element of the code has to be visible in the record, and most of them are captured long before the sequela visit. Practices that collect accident detail on digital intake forms rarely have to reconstruct it a year later.

• Occupant role: the note names the patient as the driver, not a passenger or a person riding on the outside
• Vehicle and operator: the record shows a vehicle owned by the military and operated by a member of the military
• Accident location: the note places the event entirely off the public highway, such as a training ground or open terrain
• Link to the original injury: the current condition is documented as a direct result of that accident, with a date or a prior encounter referenced
• Healing status: the note confirms the acute injury has resolved and describes the residual condition being treated
• Payer rules: external cause reporting is not mandated nationally, so check state requirements and payer policy first

That last point surprises coders who treat external cause codes as compulsory. No national rule requires them. Many states and payers do require them, and the data feeds injury research, so most practices report them by default.

How the claim moves, and where it stalls

A sequela claim passes through three sets of hands. The clinician documents the residual condition and ties it back to the accident.

The coder then picks the residual first, adds the injury code with S, and finishes with V86.54XS. Billing sends it, and the payer checks it against its own external cause policy.

Almost every stall happens in the middle step. Role or location is missing from the note, or the two 7th characters do not match. Y92 and Y99 codes also get carried over from the first visit.

Late effects also travel. A crash treated in an emergency room often reaches physical therapy practices or sports medicine practices months later. None of the original chart travels with the patient.

So run four checks before you submit.

• Is the residual condition first on the claim, and V86.54XS last?
• Does the injury code carry the same 7th character as the external cause code?
• Does the note place the accident entirely off the public highway?
• Have the Y92, Y93 and Y99 codes from the first visit been removed?

Six mistakes that get V86.54XS denied

Most denials on this code trace back to one of six habits. Each one is easy to catch before the claim leaves the practice.

• Coding an ATV as a military vehicle. V86.55XS is the ATV driver and V86.65XS the ATV passenger. The fifth character 4 is what makes a code military
• Stopping at the index main term. That lands on V86.34, a traffic code for an occupant whose role is unknown
• Using S while the injury is still healing. Routine care during recovery takes D, not S
• Dropping the X placeholder. V86.54S is invalid and fails at submission
• Listing V86.54XS first. An external cause code can never be the first-listed or principal diagnosis
• Adding Y92, Y93 or Y99 codes. Those belong on the initial encounter, not on a sequela claim

How Pabau keeps accident detail attached to the claim

External cause coding fails on memory, not on knowledge. The details that justify V86.54XS are gathered at the first visit, and the claim that needs them goes out months or years later. When they live in a scanned note or a colleague’s recollection, the sequela claim is built on guesswork.

Practice management software like Pabau keeps that trail in one place. Accident mechanism, occupant role and location are captured on intake forms and stay attached to the patient record.

Coders then search and attach diagnosis codes inside that same record, so nobody switches tabs to look a code up and retype it elsewhere.

From there, claims management carries the coded encounter through to submission. Fewer claims get rebuilt from scratch, and the documentation trail is ready the day an auditor asks for it.

Keep injury detail attached to every future claim

Pabau links intake forms, clinical notes and diagnosis coding to one patient record. The accident detail behind a sequela claim is still there a year later. See how coding and claims work together in a live demo.

Book a demo

Conclusion

V86.54XS is narrow by design, and that is what makes it easy to get wrong. Four answers pick the code on their own. Who was driving, who owned the vehicle, where the accident happened, and whether the injury has finished healing.

The trade-off worth remembering is timing. None of that can be reconstructed at the sequela visit, so the work belongs at the first encounter. Practices that capture the accident properly on day one code the late effect in minutes.

That makes this a records problem before it is a coding problem. Book a demo to see how Pabau keeps injury documentation and diagnosis coding in one workflow. External cause claims then hold up years after the accident.

Continue your research

Need the same sequela rules on another transport code? ICD-10 code V79.49XS applies the identical 7th character framework to a bus driver injured in a collision.

Coding a follow-up visit rather than a late effect? ICD-10 code W25.XXXD shows how the D character works on an external cause code.

Looking for the residual condition that leads the claim? ICD-10 code S62.032S is a sequela injury code sequenced ahead of the external cause.

Still coding the accident itself? ICD-10 code S32.416A covers the initial encounter, where place and activity codes still belong.

Want the accident detail captured before it is needed? Medical forms at your healthcare practice shows how to structure intake so nothing is missing later.

Frequently asked questions