ICD-10 Code V05.92XS: skateboard rail collision sequela

Key takeaways

ICD-10 Code V05.92XS covers a pedestrian on a skateboard hit by a railway train or vehicle. The record does not document traffic or nontraffic status, and the visit treats a late effect.

V05.92XS is a valid, billable ICD-10-CM code for FY2026 claims, confirmed against the NCHS tabular list.

The XS ending marks a sequela encounter. Use it only for a late effect, never during initial or subsequent acute care.

A documented public road puts the case on V05.12XS instead, and private property or a rail yard puts it on V05.02XS.

Practice management software like Pabau validates administrative claim fields, including member ID and authorization codes, before a claim is submitted.

ICD-10 Code V05.92XS is a billable external cause code. It covers a pedestrian on a skateboard injured in a collision with a railway train or railway vehicle. It applies when the record does not document whether the accident was a traffic or nontraffic event. The XS ending narrows it to a sequela encounter, so the visit treats a late effect of that injury.

Three details decide whether V05.92XS is the right code. Those are the conveyance, the traffic status, and the encounter type. Change any one of them and the code changes with it.

External cause codes from Chapter 20 never stand alone. The sequela condition is reported first, and V05.92XS follows it as a supplementary code.

ICD-10 Code V05.92XS: quick reference

The table below is the at-a-glance check before a claim goes out. Every field reflects the FY2026 ICD-10-CM tabular list in the CDC ICD-10-CM web tool. For practices handling injury claims, claims management software validates administrative fields such as member ID and authorization codes before submission.

Full code description and component breakdown

The long description of V05.92XS encodes four separate facts. Each one drives code selection, so changing any of them moves the coder to a different V05 code.

What the XS 7th character means

V05.92XS carries the 7th character S, which designates sequela, also called a late effect. It is one of three encounter-type endings in the V05.92 subcategory, and picking the wrong one triggers claim edits. The same logic governs other sequela codes such as S56.125S.

The three 7th character options for V05.92 are:

• A (initial encounter): The patient is under active treatment for the injury. Use V05.92XA for the visits where that treatment happens.
• D (subsequent encounter): The patient is healing. Routine follow-ups, cast changes, and therapy during recovery all take the D ending.
• S (sequela): The injury has left a lasting condition. V05.92XS applies once the current visit is specifically for that late effect.

One sequela rule outranks the rest. Report the specific late-effect condition as the principal or first-listed diagnosis, then V05.92XS after it. The ICD-10-CM Official Guidelines put the external cause code second, never first.

Where V05.92XS sits in the ICD-10-CM hierarchy

ICD-10-CM is maintained by the National Center for Health Statistics, part of the CDC. Knowing where V05.92XS sits helps a coder move to a parent or sibling code when the clinical picture changes.

• Chapter: External causes of morbidity, V00-Y99
• Block: V00-V09, pedestrian injured in transport accident
• Category: V05, pedestrian injured in collision with railway train or railway vehicle
• Subcategory: V05.9, the same collision with traffic status unspecified. It covers every pedestrian conveyance, not only skateboards.
• Five-character code: V05.92, pedestrian on skateboard
• Full code: V05.92XS, sequela encounter

The X in the 6th position is a placeholder. ICD-10-CM uses it to hold position when a code needs a 7th character but has only five of its own. That is standard across the V00-V09 codes, and the X carries no clinical meaning.

Related codes in the V05 family

V05.9 holds one code per pedestrian conveyance, all sharing the unspecified traffic status. Coders working railway cases should read the whole set, since the 5th character is what separates them. The same 7th character logic applies to injury codes elsewhere, such as S22.049K.

Only V05.90XS describes a pedestrian on foot. V05.91XS describes a pedestrian on roller-skates, and V05.92XS describes a pedestrian on a skateboard. The 5th character carries the conveyance, so short code descriptions are an easy place to slip.

The micro-mobility codes break the pattern. V05.931 and V05.938 already carry six characters, so they take no X placeholder before the 7th.

Includes and excludes notes for V05

V05 carries no Includes or Excludes notes of its own. The notes that reach it sit at the V00-V09 block level. They matter when a case looks like a pedestrian collision but is not one.

Accurate medical documentation forms at intake capture the vehicle type and location these notes turn on.

• Block Includes: a person changing a tire on a transport vehicle. It also covers a person examining the engine of a vehicle broken down beside the road.
• Block Excludes1: a fall from a non-transport collision with another person, coded to W03. Also excluded are slipping on ice or snow (W00.-) and being struck by another person (W51).
• Use additional code: report place of occurrence (Y92), activity (Y93), and external cause status (Y99) at the initial encounter.
• Conveyance scope: V05.92XS applies only when the pedestrian was on a skateboard at the time of the original collision.

Traffic, nontraffic, or unspecified: choosing the code

ICD-10-CM defines traffic and nontraffic precisely. The word unspecified in V05.92XS is not a default setting. Reaching for it when the record supports something narrower is a documentation accuracy error.

How ICD-10-CM draws the line:

• Traffic accident: the accident happened on a public highway, meaning a road, street, or way open to public motor vehicle use. A rail crossing on a public road counts. A skateboard sequela here is V05.12XS, and an on-foot sequela is V05.10XS.
• Nontraffic accident: the accident happened anywhere else, such as private property, a rail yard, an industrial site, or private track. A skateboard sequela here is V05.02XS, and an on-foot sequela is V05.00XS.
• Unspecified: the record does not document the location type and it cannot reasonably be inferred. Only then does V05.92XS apply.

Use the framework below once you know both the conveyance and the location.

Good SOAP note documentation at the first visit captures the location detail. That saves a coder from defaulting to unspecified months later at a sequela encounter.

Coding guidelines and documentation tips

External cause codes are not mandatory nationally. The ICD-10-CM Official Guidelines require reporting only where a state mandate or a specific payer asks for it. Check local rules before assuming a claim needs one.

Sequela visits cluster in rehabilitation and follow-up settings. That is where physical therapy practices see the most coding errors, and where clinical documentation software keeps injury details attached to the record.

Key sequela coding rules for V05.92XS:

• Report the sequela condition first, for example post-traumatic pain, scarring, or a neurological deficit. V05.92XS follows it as a supplementary external cause code.
• Do not use V05.92XS at an encounter where the original injury is still being actively treated. That encounter takes V05.92XA.
• Do not use the code unless the condition being treated traces directly to the original railway collision.
• Query the provider when the record hints at a traffic or nontraffic location that earlier coding missed.
• Place of occurrence (Y92) and activity (Y93) codes belong to the initial encounter only. They are not repeated at a sequela visit.

Documentation that forces a coder onto V05.92XS usually looks the same. Emergency notes record the mechanism but not the location, police reports never reach the chart, and transfer records drop the accident circumstances.

Practices using clinical record management tools that carry injury details forward from the first visit avoid most of that. Strong HIPAA compliance habits also help when an audit targets external cause specificity.

The traffic and nontraffic question recurs across the V00-V99 transport range. It shows up in adjacent injury codes too, such as S53.116D.

Code history and FY2026 validity

V05.92XS has been in the ICD-10-CM tabular list since the US adopted ICD-10-CM in October 2015. It is valid for FY2026 with no change to its description or classification. The risk with a stable code is specificity, not obsolescence. Coders default to it when V05.12XS or V05.02XS would be more accurate.

V05.92XS carries no Excludes notes at the code level, and neither does the V05 category. The only exclusions that reach it are the V00-V09 block notes covered above.

How Pabau keeps sequela documentation claim-ready

A sequela visit for a railway collision often lands months after the injury, in a different chart and sometimes a different practice. The coder is left reading whatever the first encounter recorded. Rehabilitation and sports medicine teams feel this most, because their caseload is almost entirely follow-up.

That is where practice management software changes the picture. Pabau keeps the injury mechanism, the accident location, and the encounter history on a single patient record. Intake forms capture location detail while it is still fresh, and the record travels with the patient into every follow-up.

The coder can then see what the first encounter documented, rather than guessing. Pabau also validates claim fields before submission. An injury claim will not bounce over a missing member ID or authorization code.

Keep injury documentation claim-ready

Pabau keeps the injury mechanism and accident location on one patient record from the first visit through long-term follow-up. Coders see what was documented, and claim fields are checked before submission.

Book a demo

Conclusion

V05.92XS is the right code only when the record genuinely cannot say where the collision happened. Reach for it by habit and you are coding a documentation shortfall, not a clinical fact.

The fix sits at the first encounter, not the sequela visit. One line about the accident location gives the coder V05.12XS or V05.02XS a year later, and an audit trail to match. Book a demo to see how Pabau keeps that detail on the record from the first visit to the last.

Continue your research

Working through another fracture sequela? S22.022G walks through the delayed-healing 7th character on a thoracic burst fracture.

Coding a malunion at a follow-up visit? S52.692R covers the malunion 7th character on a distal ulna fracture.

Managing multi-visit injury cases? Automated clinic workflows track follow-up requirements and documentation tasks without manual chasing.

Need claims to clear on first submission? Claims management software validates administrative claim fields such as member ID and authorization codes.

Want a longer view of subsequent-encounter coding? S55.899D shows how the D character works on a forearm blood vessel injury.

Frequently asked questions