ICD code V95.42XA – Spacecraft forced landing injuring occupant

Key takeaways

V95.42XA codes an injury to a spacecraft occupant caused by a forced landing, at the visit where active treatment begins.

A forced landing is not a crash: a spacecraft crash is V95.41XA, a collision V95.43XA and a fire V95.44XA.

It is an external cause code, so the injury code goes first and V95.42XA can never be the principal diagnosis.

The X in the sixth position is a required placeholder, and V95.42A without it is an invalid code that payers reject.

ICD-10 code V95.42XA: Definition and official descriptor

ICD-10 Code V95.42XA is the official ICD-10-CM code for “forced landing of spacecraft injuring occupant, initial encounter.”

It belongs to Chapter 20 (External causes of morbidity) of the ICD-10-CM classification, as published on the CMS ICD-10 codes page. The code captures how the injury happened, a spacecraft forced to land, rather than the injury itself.

“Occupant” covers the pilot, crew members, and any passengers aboard the spacecraft at the time of the landing. The fifth character, 2, is what separates a forced landing from its siblings in subcategory V95.4. A spacecraft crash is V95.41, a collision is V95.43, a fire is V95.44 and an explosion is V95.45. Nonpowered aircraft follow the same split in V96, where a balloon collision at the initial encounter is ICD-10 code V96.03XA.

Code structure breakdown: How V95.42XA is built

Each character in V95.42XA carries a specific meaning. Knowing the structure helps coders spot errors before submission, and it explains why the X placeholder cannot be dropped.

The X in the sixth position is a placeholder. ICD-10-CM puts the encounter type in the seventh character, but subcategory V95.42 only has five characters. The X fills the sixth slot so the A lands in seventh place. Submitting “V95.42A” without it produces an invalid code that payers reject outright.

What this spacecraft forced landing code covers and excludes

V95.42XA applies to one type of spacecraft accident. Knowing its boundaries prevents two common errors. One is reaching for a sibling code when the record says forced landing. The other is assigning V95.42XA when the record describes a different event. Three questions about the record settle which code applies, in this order.

Included scenarios

• A spacecraft forced to make an unplanned landing, where a person aboard (pilot, crew member, or passenger) is injured
• The emergency department, trauma center, or inpatient visit where active treatment of those injuries takes place

Excluded scenarios that take a different code

• V95.41XA: Spacecraft crash injuring occupant, initial encounter (the record describes a crash, not a forced landing)
• V95.43XA: Spacecraft collision injuring occupant, initial encounter
• V95.44XA: Spacecraft fire injuring occupant, initial encounter
• V95.45XA: Spacecraft explosion injuring occupant, initial encounter
• V95.49XA: Other spacecraft accident injuring occupant, initial encounter (a documented accident that fits none of the named types)
• V95.40XA: Unspecified spacecraft accident injuring occupant, initial encounter (use only when the record does not say what happened)
• V95.42XD / V95.42XS: The same forced landing, at a subsequent encounter or a sequela visit
• Y36 and Y37: Military aircraft accidents in military or war operations, excluded at the V95-V97 block level
• V97.3-: A person on the ground injured in an air transport accident (V95.42XA requires the patient to be aboard)

Choosing the right 7th character: Initial encounter, subsequent encounter, or sequela

The 7th character is the most commonly misapplied element of the V95.42 subcategory. The ICD-10-CM Official Guidelines for Coding and Reporting define each encounter type, and payers apply those definitions when auditing claims.

Each encounter takes the 7th character that matches the patient’s status at that visit. A patient seen in the emergency department on the day of the landing is coded XA. If they return six weeks later for a wound check, that visit is coded XD. The guidelines tie “active treatment” to the care being given, not to the days since the event.

Sequencing rules for V95.42XA on a claim

V95.42XA is an external cause code. Under ICD-10-CM Official Guidelines Section I.C.20, external cause codes describe the event that caused the injury. They can never be the principal or first-listed diagnosis, so the injury code always comes first.

The correct claim sequencing follows three steps:

1. List the injury code first. Report the specific trauma, such as a fracture, head injury, burn, or wound, with the matching S- or T-series code as the principal diagnosis.
2. Add V95.42XA as an additional code. Place it after the injury codes in the diagnosis field, where it explains how the injury occurred.
3. Add place, activity, and status codes where required. Y92 codes record where the injury happened, Y93 codes record the activity (such as Y93.89, Activity, other specified), and Y99 codes record the patient’s status. Report each only at the initial encounter.

There is no national requirement to report external cause codes. Guideline I.C.20 makes them required only where a state-based reporting mandate or a particular payer calls for them. Everywhere else, it encourages voluntary reporting.

Many state injury databases and payers do want them on trauma claims, so check your payer’s policy before you leave them off. Our guide to the medical billing process follows a claim like this one from encounter to payment.

Documentation requirements to support V95.42XA

The medical record must give a coder what they need to confirm the code without inference. Vague phrases such as “aviation accident” or “transport injury” are not enough. The record should state:

• That the event was a forced landing of a spacecraft, not a crash, collision, fire, or explosion, which each have their own code
• That the patient was aboard the spacecraft as pilot, crew member, or passenger, not a person on the ground
• That this visit is for active treatment of the injuries
• The specific injuries sustained, to pair with the injury codes
• A clinical note linking those injuries to the forced landing

The CDC/NCHS ICD-10-CM browser tool shows one exclusion note that reaches V95.42XA from the V95-V97 block. Military aircraft accidents in military or war operations go to Y36 and Y37 instead.

Name the event in the history of present illness. “Patient was aboard a spacecraft that made a forced landing” supports the code, while “transport accident” does not.

If the note only says the spacecraft “came down hard,” query the provider. The answer decides between a forced landing (V95.42) and a crash (V95.41), and coders should not choose between them on their own.

Commonly confused codes in the V95.4 subcategory

Every code in subcategory V95.4 describes a spacecraft accident injuring an occupant, so the descriptors look alike. The table lists the codes most often picked in error and a decision rule for each.

The AAPC Codify ICD-10-CM lookup shows the full V95 hierarchy, which helps when checking which subcategory fits the documented event.

Top claim denial reasons for ICD-10 code V95.42XA and how to prevent them

The denial patterns for V95.42XA follow the same structure seen across Chapter 20 external cause codes. Each one has a specific corrective action.

Systematic denial management workflows for trauma claims should include a pre-submission check. It confirms that external cause codes sit in an additional diagnosis position and that the placeholder is intact.

Codes to report alongside V95.42XA

V95.42XA never stands alone on a claim. A complete trauma claim carries the injury codes first, then the external cause codes that explain them. The injury codes that lead the claim come from the S- and T-series of the ICD-10-CM codes library.

• Injury codes (S- or T-series, listed first): For example, S09.90XA (Unspecified injury of head, initial encounter). Fracture, wound, burn, and thoracic or abdominal injury codes are also common, depending on the injuries
• V95.42XA (additional code): Records the forced landing of the spacecraft as the external cause
• Place of occurrence (Y92): Records where the injury happened; report it once, at the initial encounter
• Activity (Y93): Records what the patient was doing, such as Y93.89 (Activity, other specified); report it once, at the initial encounter
• External cause status (Y99): Records whether the patient was working, a civilian on leisure activity, or in another status at the time

Check code values against the ICD List lookup tool, which mirrors the official CMS and NCHS data. Getting the sequencing, the placeholder, and the payer’s external cause rules right is what turns this claim into a clean claim on first submission.

ICD-10-CM official coding guidelines for external cause codes

Section I.C.20 of the ICD-10-CM Official Guidelines for Coding and Reporting governs every Chapter 20 code, including V95.42XA. Beyond the sequencing rule above, these are the points coders should have at hand:

• Assign the external cause code, with the right 7th character, for each encounter at which the injury is treated.
• Assign as many external cause codes as needed to describe the event fully.
• Report place of occurrence, activity, and status codes only once, at the initial encounter.
• Use the most specific code available. If the record supports V95.42XA, do not default to V95.40XA (unspecified spacecraft accident).

The CMS ICD-10-CM annual update files publish these guidelines each fiscal year. Always reference the current release, because guideline language can change.

How Pabau helps practices code injury claims correctly

Rare codes like V95.42XA are where coding errors hide. A coder who sees one once a year has to look up the subcategory, count the characters, and remember the sequencing rule. When any of those slips, the error only shows up weeks later as a denial.

Pabau, the practice management platform we build, keeps the clinical note, the diagnosis codes, and the claim in one patient record. Its claims management software lets your team enter ICD-10-CM injury and external cause codes against the encounter. Claims then go out through a clearinghouse, which checks them against payer edits before submission.

So fewer claims come back for avoidable reasons, and your billing team spends less time reworking them.

Submit cleaner claims for trauma and external cause codes

Pabau keeps encounters, diagnosis codes, and claims in one place, and sends claims through a clearinghouse that checks them before they reach the payer. See how practices use Pabau to cut avoidable denials.

Book a demo

Conclusion

V95.42XA is one of the more precise codes in Chapter 20. It has a single X placeholder, a specific accident type, and an encounter type that must match the treatment phase. The descriptor is where errors start, because a forced landing and a crash sit one character apart.

Read the record for the words that name the event, and let those words choose the fifth character. When the note is vague, a provider query costs far less than a denied claim. To see how Pabau keeps coding and claims together for your practice, book a demo.

Continue your research

Need to understand how claims move from code to payment? What is revenue cycle management covers the end-to-end process from charge capture through reimbursement.

Working through a denial on a trauma claim? Denial codes in medical billing explains the most common CARC and RARC combinations and how to respond to each.

Choosing how your claims reach payers? Claim.MD clearinghouse overview explains how Pabau’s clearinghouse partner processes ICD-10-coded claims and ERA responses.

Frequently asked questions