X36.1XXA — Avalanche, landslide, or mudslide, initial encounter
Is X36.1XXA billable?
Yes — X36.1XXA is billable for FY2027. X36.1XXA is a valid, billable ICD-10-CM code at the highest level of specificity in its branch. X36.1XXA may be submitted for encounters from October 1, 2026 through September 30, 2027.
X36.1XXA at a glance
| Code | X36.1XXA |
|---|---|
| Description | Avalanche, landslide, or mudslide, initial encounter |
| Billable | Yes |
| Code set | ICD-10-CM FY2027 |
| Valid for encounters | October 1, 2026 – September 30, 2027 |
| 7th character "A" | initial encounter |
What does the 7th character "A" mean in X36.1XXA?
In X36.1XXA, the 7th character A means initial encounter. The 7th character is required for X36.1XXA to be a valid, complete code.
Same condition, different episode of care — switch the 7th character:
How is X36.1XXA listed in the External Cause Index?
The External Cause of Injuries Index lists these routes under X36.1, the nearest indexed parent of X36.1XXA. This is a separate index from the Alphabetic Index and is where external cause codes are looked up.
- Landslide (falling on transport vehicle)
- Forces of nature › avalanche
- Forces of nature › earth movement
- Forces of nature › landslide
- Forces of nature › mudslide
Excludes1 — never code together — inherited from X36
The conditions below can never be reported together with X36.1XXA on the same claim. An Excludes1 note means the two conditions cannot occur in the same patient, so reporting both is a coding error.
- earthquake (X34)
Excludes2 — not included here — inherited from X36
The conditions below are not part of X36.1XXA, but a patient may have both at the same time. When documentation supports it, X36.1XXA and the excluded code may both be reported.
- transport accident involving collision with avalanche or landslide not in motion (V01-V99)
How long has X36.1XXA existed?
X36.1XXA has been in ICD-10-CM since at least FY2016, the earliest fiscal year on record here.
Derived from the official order files for FY2016–FY2026. FY2017 and FY2020 publish no order file, so those years are not covered.