V96.14XD vs Y36

V96.14XD (Hang-glider fire injuring occupant, subsequent encounter) compared with Y36 (Operations of war), from the official CMS tabular data.

Summary

These codes should not be reported together because V96.14XD’s tabular entry lists Y36 under Excludes1.

Official rule

What is different?

The conditions named and billing status.V96.14XD is “Hang-glider fire injuring occupant, subsequent encounter”; Y36 is “Operations of war”. Y36 is a non-billable header; V96.14XD is billable.

Registry fact

Can these codes be reported together?

No.V96.14XD’s entry carries an Excludes1 note covering Y36: “military aircraft accidents in military or war operations (Y36, Y37)”. Both may be reported only when the documentation shows the two conditions are unrelated to each other (ICD-10-CM Official Guidelines, Section I.A.12.a).

Official ruleGuide: Excludes1 vs Excludes2

Is there an Excludes1 relationship?

Yes.V96.14XD’s tabular entry: “military aircraft accidents in military or war operations (Y36, Y37)”. The note covers Y36.

Official ruleGuide: Excludes1 vs Excludes2

Is there an Excludes2 relationship?

None.Neither entry carries an Excludes2 note that names the other code.

Official rule

Is one more specific?

Not comparable.The codes sit in different categories; specificity is only comparable within one category.

Is one a parent or header code?

One is a header.Y36 is a non-billable header, but V96.14XD is not one of its subdivisions.

Registry fact

Are there sequencing instructions?

None.Neither entry carries a Code First or Use Additional Code note that names the other.

Official rule

Are there other coding relationships?

None found.No laterality, encounter-phase, Table of Neoplasms, Table of Drugs and Chemicals, or history-versus-active-disease relationship links these codes.

MedCoder-derived

Official rule: a tabular instructional note or a section of the ICD-10-CM Official Guidelines, quoted as published. Registry fact: the codes’ own published attributes (titles, billable status, position in the hierarchy, code set). MedCoder-derived: a reading MedCoder computes from those facts; it is not itself a rule. How to read the labels

Can these codes be reported together?

Conflict

Excludes1 conflict

V96.14XD

Hang-glider fire injuring occupant, subsequent encounter

↔

Y36

Operations of war

What we found

No — do not report together.V96.14XD carries an Excludes1 note covering Y36: “military aircraft accidents in military or war operations (Y36, Y37)”

Sole exception: when the two conditions are documented as unrelated to each other (ICD-10-CM Official Guidelines, Section I.A.12.a).

What to review

Report one of the two. Both may be reported only when the documentation shows the two conditions are unrelated to each other.

Guide: Excludes1 vs Excludes2 Check these on a claim

Why it matters

An Excludes1 note means the two conditions cannot occur together, so the pair should not be reported for the same encounter. The sole exception is when the conditions are documented as unrelated to each other.

Source / rule

CMS ICD-10-CM tabular instructional notes; ICD-10-CM Official Guidelines, Section I.A.12.a

Official guidance behind these answers

Section I.A.12.a — Excludes1 · applies to: Excludes1
A type 1 Excludes note is a pure excludes note. It means “NOT CODED HERE!” An Excludes1 note indicates that the code excluded should never be used at the same time as the code above the Excludes1 note. An Excludes1 is used when two conditions cannot occur together, such as a congenital form versus an acquired form of the same condition. An exception to the Excludes1 definition is the circumstance when the two conditions are unrelated to each other. If it is not clear whether the two conditions involving an Excludes1 note are related or not, query the provider. For example, code F45.8, Other somatoform disorders, has an Excludes1 note for "sleep related teeth grinding (G47.63)," because "teeth grinding" is an inclusion term under F45.8. Only one of these two codes should be assigned for teeth grinding. However psychogenic dysmenorrhea is also an inclusion term under F45.8, and a patient could have both this condition and sleep related teeth grinding. In this case, the two conditions are clearly unrelated to each other, and so it would be appropriate to report F45.8 and G47.63 together.
ICD-10-CM Official Guidelines FY2026

Quoted from the ICD-10-CM Official Guidelines for Coding and Reporting in effect for the release shown. The tabular notes above are the code-level instruction; these sections are the convention that says how such a note is applied. Source document (CMS PDF) · Release and checksum

Side by side

	V96.14XDHang-glider fire injuring occupant, subsequent encounter	Y36Operations of war
Billing status	Billable	Non-billable header Report instead: Y36.000A, Y36.000D, Y36.000S, Y36.001A, Y36.001D
Classification	V00-Y99 — External Causes of Morbidity (V00-Y99)	V00-Y99 — External Causes of Morbidity (V00-Y99)
Definition	Hang-glider fire injuring occupant, subsequent encounter is a billable ICD-10-CM diagnosis code (V96.14XD).	Operations of war is a non-billable ICD-10-CM category code (Y36).
7th character	The appropriate 7th character is to be added to each code from category V96	The appropriate 7th character is to be added to each code from category Y36
Includes	—	injuries to military personnel and civilians caused by war, civil insurrection, and peacekeeping missions
Excludes1	military aircraft accidents in military or war operations (Y36, Y37)	injury to military personnel occurring during peacetime military operations (Y37.-) military vehicles involved in transport accidents with non-military vehicle during peacetime (V09.01, V09.21, V19.81, V29.818, V39.81, V49.81, V59.81, V69.81, V79.81)

Notes are the code’s own tabular entry, quoted as published. A note that names the other code is the one the verdict above rests on.

Edit this comparison Check a whole claim

Derived from the official CMS ICD-10-CM tabular data (FY2026). A coding-rule comparison, not billing advice: payer-specific edits and medical-necessity policy are outside its scope. All data sources