ICD code V95.10XD – Unspecified ultralight accident, subsequent encounter

Key takeaways

V95.10XD codes an unspecified ultralight, microlight or powered-glider accident injuring an occupant, at a subsequent encounter.

Use the 7th character D once active treatment is complete and the patient gets routine care while the injury heals.

List the injury code first, because V95.10XD can never be the first-listed or principal diagnosis.

Report Y92, Y93 and Y99 codes once, on the initial encounter claim, and leave them off V95.10XD follow-ups.

Pabau’s claims management software pre-fills claims from the patient record and validates required fields before Claim.MD submission.

What ICD-10 code V95.10XD tells a payer

ICD-10 code V95.10XD is a billable external cause code for an unspecified ultralight, microlight or powered-glider accident injuring an occupant, at a subsequent encounter. It is valid from FY2025 through FY2027. The code explains how the injury happened. A separate injury code, listed first, says what the injury is.

“Unspecified” refers to the type of accident. The record confirms an ultralight-class aircraft but doesn’t say whether it crashed, made a forced landing or collided. When the record does say, a more specific V95.1 code applies.

The tabular hierarchy runs from V95 (powered aircraft) to V95.1 (ultralight, microlight and powered-glider accidents). It then narrows to V95.10, the non-billable unspecified-accident code, and finally to V95.10XD. The X in position six is a placeholder that lets the code reach its 7th character.

The injury codes that pair with it, from rib fractures to concussions, sit in our diagnostic codes library.

The 7th character D starts when active treatment ends

The 7th character D marks a subsequent encounter. Under ICD-10-CM Official Guidelines section I.C.19.a, D applies once the patient has completed active treatment. From then on, the patient receives routine care while the injury heals or recovers.

Typical D visits include a cast change, a follow-up X-ray to check healing, removal of a fixation device and a medication adjustment. The visit count doesn’t decide the character. A patient seen three times during active treatment stays on A for all three visits.

The external cause code always follows the injury code. If the injury code ends in D, the external cause code is V95.10XD. For a sequela visit, the residual condition goes first, then the injury code with S, then V95.10XS.

What V95.10XD covers, and the codes next door

V95.10XD covers anyone riding in or flying an ultralight, microlight or powered glider. That includes the pilot and any passenger. These are light, engine-powered aircraft that sit outside the helicopter and fixed-wing categories.

Other aircraft and other people take different codes:

• V95.00XD-V95.09XD: helicopter accidents, subsequent encounter.
• V95.20XD-V95.29XD: other private fixed-wing aircraft, subsequent encounter.
• V95.30XD-V95.39XD: commercial fixed-wing aircraft, subsequent encounter.
• V95.40XD-V95.49XD: spacecraft accidents, subsequent encounter.
• Category V96: nonpowered aircraft, such as gliders, hang gliders and balloons.
• V97.3-: people on the ground injured in an air transport accident.

A hang glider without an engine moves to V96, as with V96.11XS for a hang-glider crash sequela. Within V95.1, pick the specific accident type whenever the chart names it. V95.10XD is for records that leave the accident type open.

Which V95 code matches the aircraft?

The aircraft type sets the V95 subcategory, and the accident type sets the fifth character. A private-plane crash at the first visit, for example, is V95.21XA. The table maps the main codes and their three encounter versions.

How a V95.10XD claim moves from chart to payer

V95.10XD explains how an injury happened, not what the injury is. Under ICD-10-CM Official Guidelines section I.C.20, external cause codes are always additional codes. They can never be the first-listed or principal diagnosis.

On a subsequent encounter claim, list the codes in this order:

1. First-listed diagnosis: the injury under care, with D as its 7th character. Examples are S22.41XD for multiple right rib fractures and S06.0X0D for concussion.
2. Other injury codes: any further injuries treated at the same visit.
3. V95.10XD: the external cause, matching the injury code’s D.

Place of occurrence (Y92), activity (Y93) and external cause status (Y99) codes don’t go on this claim. Guidelines section I.C.20 says to report each one once, at the initial encounter. Status codes such as Y99.8 follow the same once-only rule.

The chart below shows how the claim changes across the three phases of care.

A worked example

A pilot breaks several right ribs in an ultralight accident, and the record doesn’t name the accident type. The ED visit is active treatment, so that claim uses S22.41XA and V95.10XA. It also carries the Y92, Y93 and Y99 codes.

Six weeks later, the pilot returns for a follow-up X-ray of the healing ribs. That visit is routine healing care. The claim lists S22.41XD first and V95.10XD second, with no Y codes.

Before you submit: A V95.10XD checklist

Run these checks against the chart before the claim leaves:

• Aircraft class confirmed: the record names an ultralight, microlight or powered glider, or a provider query has clarified it.
• Accident type left open: the note doesn’t say crash, forced landing, collision, fire or explosion. If it does, use the specific V95.1 code.
• Occupant role documented: the patient was the pilot or a passenger, not a bystander on the ground.
• Care phase established: the note shows active treatment is complete and this visit is routine healing care.
• Injury code present: at least one injury code ending in D sits ahead of V95.10XD.
• No Y92, Y93 or Y99 codes: these belong on the initial encounter claim only.

When the aircraft type or the care phase is unclear, query the provider before you submit. Changing a code without provider input means coding something the record doesn’t support. Sound medical billing compliance keeps those queries on file, so an auditor can see why a code changed.

Payer rules for V95.10XD claims

Traditional Medicare doesn’t require external cause codes for claim processing, though some Medicare Advantage plans and supplemental payers ask for them. Reporting V95.10XD on a Medicare claim does no harm. Leaving it off rarely triggers a denial by itself.

Two payer groups give external cause codes more weight:

• State Medicaid programs: several state Medicaid agencies require external cause codes on trauma and accident claims. Rules vary, so check with the state Medicaid agency before treating them as optional.
• Workers’ compensation and personal injury: these payers usually expect external cause codes. They use them to confirm the mechanism of injury and route the claim to the right liability coverage.

Aviation injuries add a coordination of benefits (COB) step. An aircraft liability policy or a pilot’s personal accident cover may pay before health insurance does. Payers often send a COB request when an aviation external cause code appears.

A COB request asks for details of the patient’s other coverage. Answer it promptly so the claim doesn’t age past timely filing. Running insurance eligibility verification before the visit brings that other coverage to light early.

Common V95.10XD mistakes that trigger denials

Each error below has a clear fix, and three of the five go back as a corrected claim.

The denial management workflow is the same as for other coding errors. Find the CARC and RARC codes on the ERA and match them to a row above. Fix the source record, then resubmit inside the payer’s timely filing window.

How Pabau keeps V95.10XD claims moving

Follow-up trauma claims go wrong easily when a biller re-keys codes from the chart. The injury code, the external cause code and the patient’s details all have to line up by hand.

Pabau’s claims management software pre-fills each claim from the patient record. Built-in ICD-10-CM and CPT lookup libraries help coders find V95.10XD and the injury code it explains. Pabau then validates the required claim fields and submits the claim through Claim.MD.

Eligibility checks run before the visit, and ERA posting brings payer responses back into the same record. A COB request or a denial lands where your billing team already works, so follow-up starts sooner.

Send cleaner claims for follow-up injury visits

Pabau pre-fills claims from the patient record, validates required fields and submits through Claim.MD. Eligibility checks and ERA posting keep follow-up visits like V95.10XD in one workflow.

Book a demo

Conclusion

V95.10XD has one job on a claim. It tells the payer that a follow-up visit traces back to an ultralight accident. Take the 7th character from the phase of care, not the visit count, and keep the injury code in first position.

The trade-off is documentation. If the chart never says active treatment ended, a D code invites a query or a denial. Ask the provider before you bill, rather than after the ERA comes back.

If your team bills follow-up trauma care, book a demo to see how Pabau pre-fills these claims and tracks them through to payment.

Continue your research

Need to understand how clean claims prevent downstream denials? Clean claim requirements in medical billing walks through what payers look for before processing a submission.

Working through an ERA denial and not sure how to read the reason codes? Electronic remittance advice explained covers CARC and RARC interpretation for billing staff.

Coding the injury that goes first on the claim? ICD-10 code S22.49XD covers multiple rib fractures at a subsequent encounter.

Still unsure which 7th character fits a visit? ICD-10 code S72.012B works through 7th character choices on a fracture code.

Want the full picture on medical billing workflow? What is medical billing covers the end-to-end revenue cycle from patient encounter to payment posting.

Frequently asked questions