ICD-10 code V96.11XS: Hang-glider crash injuring occupant

Key Takeaways

V96.11XS describes Hang-glider crash injuring occupant, sequela and is a valid billable ICD-10-CM code effective for dates of service on or after October 1, 2015

The 7th character S designates a sequela encounter, meaning the visit treats a condition that is a late effect of a previously healed hang-glider crash injury

V96.11XS must be sequenced alongside the condition being treated as the late effect; the sequela code itself is an external cause code, not a principal diagnosis

Practice management software like Pabau helps practices document sequela encounters accurately and submit clean claims the first time through built-in claims management tools and digital forms

ICD-10 code V96.11XS is a billable ICD-10-CM diagnosis code for a hang-glider crash injuring the occupant, sequela. It’s an external cause code, reported at encounters where a patient is treated for a residual condition that developed after the original crash injury had already healed.

The code sits within Chapter 20 (External Causes of Morbidity) and has been valid for claims with dates of service on or after October 1, 2015.

ICD-10 code V96.11XS: Definition and clinical description

ICD-10 code V96.11XS belongs to Chapter 20 (External Causes of Morbidity, V00-Y99), within block V96 (Accident to nonpowered aircraft causing injury to occupant). Its validity for claims with dates of service on or after October 1, 2015 is confirmed by CMS ICD-10 coding guidance.

The full descriptor reads: Hang-glider crash injuring occupant, sequela. The code hierarchy is:

• Chapter 20: V00-Y99 (External causes of morbidity)
• Block: V95-V97 (Air and space transport accidents)
• Category: V96 (Accident to nonpowered aircraft causing injury to occupant)
• Subcategory: V96.1 (Hang-glider accident injuring occupant)
• Code: V96.11 (Hang-glider crash injuring occupant)
• Full code with 7th character: V96.11XS (sequela)

Because V96.11XS is an external cause code, it does not stand alone on a claim. It describes the origin of the patient’s current condition, not the condition itself. This distinction drives the sequencing rules coders must follow at every sequela visit.

Understanding the 7th character S in ICD-10 code V96.11XS

ICD-10-CM uses 7th character extensions to specify the type of encounter. For transport accident codes in the V00-Y99 range, three values apply:

The “X” placeholder character fills the 6th position because V96.11 only has 5 characters before the 7th character extension. Only ICD-10-CM categories that use 7th-character extensions require a full 7-character code with the X placeholder when a natural 4th, 5th, or 6th character doesn’t exist.

That group includes injury codes, external-cause codes like this V96 family, obstetric codes, and fracture codes. Most ICD-10-CM codes are complete at 3 to 6 characters and never take a 7th character at all.

According to the WHO ICD-10 classification framework, sequela coding applies when the original injury has resolved and the clinician is now treating a residual condition that resulted from it. The key clinical test: has the injury itself healed? If yes, and the patient still has a related condition, S is the correct 7th character.

Practices using claims management software can flag sequela encounters in the workflow before submission, reducing the risk of submitting XA or XD codes at a visit that should carry XS.

Sequencing rules for ICD-10 code V96.11XS

V96.11XS is an external cause code. It cannot serve as the principal diagnosis or the first-listed code on a claim. ICD-10-CM Official Guidelines for Coding and Reporting (Chapter 20) require that the condition being treated for the sequela is coded first, followed by V96.11XS to identify the external cause.

A coder documenting a patient presenting with chronic shoulder pain as a late effect of a hang-glider crash would sequence the claim as:

1. Principal/first-listed diagnosis: The specific residual condition (e.g., M75.10 Rotator cuff syndrome, unspecified shoulder)
2. External cause code: V96.11XS (Hang-glider crash injuring occupant, sequela)

This sequencing mirrors how sequela coding works elsewhere in Chapter 20 external-cause codes, such as V62.3XXS. The external cause always follows the clinical condition on the claim.

Two additional sequencing points from CMS guidance:

• V96.11XS may be reported at every sequela visit for the life of treatment, not just once
• The residual condition code must link clinically to the crash; unrelated diagnoses at the same visit do not require V96.11XS as a companion code

The external-cause-cannot-be-principal rule holds across every transport-accident family, including bus-occupant codes such as V77.1XXD.

Coders who use sports medicine software with built-in coding support can attach external cause codes as a secondary field in the claim record, keeping sequencing errors out of submissions.

Reduce sequela coding errors with Pabau

Pabau's claims management tools help your team attach the right external cause codes, maintain accurate sequencing, and submit cleaner claims for complex encounter types like hang-glider crash sequela.

Book a demo

Related codes in the V96.1x family

V96.11XS sits within a structured family of hang-glider accident codes. Understanding key related codes in the V96.1x family helps coders select the correct code when crash circumstances differ, and supports accurate documentation across encounter types.

The same three-value 7th-character pattern — A, D, and S — repeats across other Chapter 20 categories entirely unrelated to aircraft, including W55.42XS.

The distinction between V96.11XS and V96.10XS matters when documentation specifies the crash mechanism. If the medical record clearly states the hang-glider crashed (rather than an unspecified accident), V96.11XS is correct. Where documentation is ambiguous, query the clinician before defaulting to the unspecified code.

For coders who work across multiple injury types, the AAPC ICD-10-CM code lookup allows side-by-side browsing of the V96.1x family and adjacent categories. Accurate client record management that captures the mechanism of injury at the initial encounter makes downstream sequela coding significantly more straightforward.

Documentation requirements for ICD-10 code V96.11XS sequela encounters

Sequela encounters carry a higher documentation burden than initial or subsequent visits. The clinician’s note must support both the diagnosis being treated and the causal link to the original crash.

Elements that should appear in every V96.11XS encounter note:

• Original injury reference: Date and brief description of the hang-glider crash (or reference to the initial encounter note)
• Current complaint: The specific residual condition being treated at this visit
• Causal connection: A clinical statement linking the current complaint to the prior crash (e.g., “chronic rotator cuff tendinopathy resulting from hang-glider crash in March 2024”)
• Status of original injury: Confirmation that the primary injury has resolved; ongoing treatment of a residual effect only
• Treatment plan: What is being done for the sequela condition at this visit

Practices treating these residual conditions over multiple visits often rely on physical therapy EMR software to track functional progress alongside the coding documentation described above.

Pabau’s digital intake forms can be configured to capture mechanism-of-injury fields and prior accident history at every visit type, reducing the risk of incomplete sequela documentation. For practices managing ongoing injury rehabilitation caseloads, these fields become standard workflow rather than an afterthought before claim submission.

Billing and claims workflow for hang-glider crash sequela

External cause codes like V96.11XS do not generate reimbursement on their own. They support medical necessity for the billed procedure by explaining the origin of the patient’s condition.

In a typical sequela billing workflow:

1. Primary diagnosis: Code the residual condition being treated (musculoskeletal, neurological, or other late effect)
2. External cause code: Append V96.11XS as a secondary code to identify the crash as the origin
3. Procedure codes: Bill the CPT or HCPCS procedure codes for services rendered at the sequela visit
4. Claim submission: Submit with full diagnosis code set; payer may require ICD-10 code V96.11XS to match accident-related claims on file

Some payers specifically request external cause codes for accident-related claims to coordinate with auto insurance or liability coverage. V96.11XS signals to those payers that the claim relates to a prior accident, which can trigger coordination of benefits review. Coders should check payer-specific guidelines when the patient has active accident-related insurance.

For practices managing high volumes of injury-related claims, streamlining clinical documentation workflows makes the difference between clean first-pass claims and a backlog of requests for additional information. ICD10Data’s lookup for V96.11XS confirms current billability status and provides crosswalk references.

ICD-9-CM crosswalk and code history for V96.11XS

ICD-10-CM replaced ICD-9-CM for US claims with dates of service on or after October 1, 2015. There is no exact ICD-9-CM equivalent for V96.11XS. Per CMS General Equivalence Mappings, the sequela encounter maps approximately to ICD-9-CM E929.1 (Late effects of other transport accident).

That mapping is approximate only. The aircraft-specific ICD-9-CM code, E842.6, corresponds instead to the initial and subsequent-encounter variants, V96.11XA and V96.11XD, not to the sequela encounter. Neither ICD-9-CM code carried the encounter-type specificity that ICD-10-CM’s 7th character now provides.

The ICD-10-CM transition introduced the 7th character extension system, which is why V96.11XS has no true predecessor in ICD-9. Practices converting legacy records should treat all sequela encounters dated after October 1, 2015 as requiring the full ICD-10-CM code with the S extension.

For practices handling long-term patients whose injuries predate the ICD-10 transition, documentation should note the original injury date alongside the ICD-10-CM V96.11XS code. This supports long-term patient care management and protects the practice in the event of a payer audit.

The AAPC ICD-10-CM lookup provides General Equivalence Mapping (GEM) references for coders who need to document the ICD-9 to ICD-10 transition for legacy records.

Practices that want a full audit trail for injury-related cases benefit from compliance management software that timestamps code changes and maintains a record of which version of ICD applied at the time of each encounter.

Conclusion

Sequela encounters are where most coding errors in hang-glider crash cases occur. The wrong 7th character, a missing causal narrative, or an external cause code placed first on the claim can all trigger denials.

Pabau’s claims management tools help practices build sequela encounter documentation into standard workflows, from intake form fields that capture original injury details to claim-level code sequencing checks before submission. To see how Pabau handles complex injury coding across multi-visit patient records, book a demo.

Continue your research

Need a starting point for injury encounter documentation? S90.812D walks through the same initial, subsequent, and sequela structure for a common foot injury code.

Managing ongoing injury rehabilitation records? Sports medicine software features built for practices handling high volumes of accident-related injury follow-up visits.

Want cleaner documentation before claim submission? Capture forms software can be configured to capture mechanism-of-injury and original accident history at every visit type.

Frequently Asked Questions