ICD code V95.21XA – Private fixed-wing aircraft crash

Key takeaways

ICD-10 code V95.21XA covers occupants of other private fixed-wing aircraft (not helicopters, not ultralights) injured in a crash on the first active treatment visit.

It is an external cause of morbidity code, so it must always be paired with a primary injury diagnosis code. It cannot stand alone.

The 7th character determines encounter type: A = initial, D = subsequent, S = sequela. Selecting D when A applies is a top denial trigger.

Pabau’s claims management software supports ICD-10-CM code entry and claim submission workflows to reduce coding errors at the point of documentation.

ICD-10 code V95.21XA: Quick reference

ICD-10 code V95.21XA reports an occupant of another private fixed-wing aircraft injured in a crash, at the first encounter for active treatment. It is billable for FY2026, but only as a supplement to the injury code that leads the claim.

The table below carries the descriptor, code type, and 7th-character rules you need to confirm the code at a glance. For the authoritative descriptor and annual validity status, cross-reference against the CDC/NCHS ICD-10-CM web tool.

Which aircraft the V95.21XA description covers

“Other private fixed-wing aircraft” in ICD-10-CM refers to fixed-wing powered aircraft that are privately owned or operated. The term covers those not classified elsewhere in the V95 family. Knowing what falls in and out of scope prevents selecting the wrong subcategory.

• Included aircraft types: Single-engine and multi-engine private planes (Cessna 172, Piper Cherokee, Beechcraft Bonanza) and light sport aircraft. The subcategory excludes aircraft covered by V95.0 (helicopter), V95.1 (ultralight/microlight/powered glider), or V95.3 (commercial fixed-wing).
• Included occupants: The pilot, co-pilot, and any on-board passengers at the time of the crash.
• “Crash” in context: Encompasses controlled-flight-into-terrain, runway overrun, hard landing causing structural failure, mid-air collision, and engine-failure forced landing with injury. The mechanism does not need to be a full destruction event.
• Excluded persons: Ground crew, bystanders, and air traffic controllers are not occupants and require different external cause codes.
• Excluded aircraft: Commercial airliners sit in V95.3 and ultralights in V95.1. Military aircraft accidents fall outside V95 altogether and are coded in V97, such as V97.818.

Because V95.21XA belongs to Chapter XX (External causes of morbidity), it documents how the injury happened, not what the injury is. A traumatic brain injury coded alongside it uses the appropriate S-code, and a rib fracture uses its own S-code. The external cause code is always secondary.

How the 7th character works on V95.21XA

V95.21XA uses A as its 7th character, which designates the initial encounter. That means the first visit at which the patient receives active treatment for the crash injuries. The 7th character is the most frequently miscoded part of this code family. Selecting D when A applies is consistently cited on remittance advices as a reason for denial.

A practical rule: If the patient walks into the emergency department directly from the crash scene, it is XA. If they return six weeks later for a follow-up x-ray, it is XD. If they present two years later with crash-related PTSD or a malunited fracture, it is XS.

ICD-10-CM code hierarchy: Where V95.21XA sits

Knowing the parent code tree shows coders why specificity matters, and where external cause codes behave differently from clinical diagnosis codes. You can browse the neighboring entries in our ICD-10-CM code library when the descriptor alone does not settle the choice. The CMS ICD-10 codes page publishes the annual tabular list update files where these hierarchies can be verified.

• V00-Y99 – External causes of morbidity (the entire supplemental chapter)
• V95-V97 – Air and space transport accidents
• V95 – Accident to powered aircraft causing injury to occupant
• V95.2 – Other private fixed-wing aircraft accident
• V95.21 – Other private fixed-wing aircraft crash
• V95.21XA / V95.21XD / V95.21XS – 7th-character extensions for encounter type

The “X” placeholder in the 6th position is structural. ICD-10-CM uses it when a code has fewer than 6 characters but requires a 7th-character extension. It carries no clinical meaning and must always be present.

V95.21XA vs related aviation codes: How to choose

The V95 family is where most aviation coding errors originate, because each subcategory maps to one aircraft type. Selecting V95.01XA when the patient was in a Cessna is a correctable error that still costs denial management time. Use the comparison table below to confirm the aircraft type before coding.

The key disambiguator between V95.01XA and V95.21XA is rotor versus fixed wing. A helicopter has rotating blades. A Cessna has wings. Any note that documents the aircraft type clearly will resolve the choice. When the documentation says only “small plane”, without the model or type, query the physician before coding.

What this code does not cover

V95.21XA is an external cause code with defined boundaries. Coding it outside those boundaries produces a clean-looking claim that a payer’s edit logic will still reject. Review the WHO ICD-10 browser for the parent-category excludes notes.

• Cannot be used as a primary or standalone diagnosis. Medicare and commercial payers expect an injury code (S00-T88 range) to lead the claim. V95.21XA always follows it.
• Does not cover fire and flames. If the aircraft caught fire and the patient sustained burn injuries as the primary mechanism, a separate external cause code for exposure to fire applies. That code sits alongside the burn diagnosis codes.
• Does not cover ground personnel. Airport staff, baggage handlers, or mechanics injured by the crashing aircraft use external cause codes from outside the V95 occupant category.
• Does not cover air traffic controllers or crew not on board. These individuals require their own external cause classification.
• Sequela coding (XS) requires a documented late effect. If the physician note does not explicitly link the current condition to the crash, XS cannot be assigned. Using XS on a new injury from a different event is a coding error.

How to use V95.21XA correctly: Documentation and coding guidelines

Correct use of V95.21XA follows a five-step sequence. Skipping any step is the underlying cause of most aviation-related claim rejections.

1. Code the injury first. Assign the primary injury diagnosis code (fracture, TBI, laceration, internal injury) as the principal or first-listed diagnosis. This code comes before V95.21XA in the claim sequence.
2. Add V95.21XA as the external cause supplement. Place it after the primary injury code. It explains the cause of the injury, not the injury itself.
3. Confirm the 7th character matches the encounter type. Initial active treatment = A. Follow-up after the acute phase = D. Late effect = S. The date of service and physician documentation should align.
4. Add a place of occurrence code when known. The ICD-10-CM Official Guidelines recommend a place of occurrence code (Y92 series) when the location of the incident is documented. For an aviation crash, this is typically an airport, runway, or open field.
5. Verify physician documentation supports the aircraft type. The note must identify the aircraft as a fixed-wing private plane, not a helicopter or commercial aircraft. Vague documentation (“aircraft crash”) warrants a physician query before coding V95.21XA specifically.

The finished claim carries those codes in a fixed order. The diagram below shows which one leads, where V95.21XA falls, and which supporting codes are added only when the record documents them.

Submitting a clean claim with aviation external cause codes depends on having all five elements in place before the claim leaves the practice. Practice management software like Pabau flags missing required code fields during claim preparation, which reduces rework after a denial.

Payer requirements and prior authorization for V95.21XA claims

Payers treat V95.21XA as a supplemental code, and their processing rules reflect that. Submitting without understanding those rules is where aviation claims run into preventable delays. Running submissions through claims software for coders catches a missing injury code or an invalid 7th character before the payer sees it.

• Medicare: Accepts V95.21XA as a supplemental code but requires a valid injury code (S or T range) as the primary diagnosis. Medicare does not accept external cause codes as the principal diagnosis under any circumstance.
• Commercial insurers: Policies vary. Most accept external cause codes as supplemental and use them for coordination of benefits when another payer (aviation liability, workers’ compensation) may be primary. Submit with full documentation of the aircraft type.
• Workers’ compensation carriers: Aviation crashes involving employees on business travel may trigger workers’ comp as primary payer. Workers’ comp claims often require the insurer’s own external cause coding schema in addition to ICD-10-CM. Verify with the specific carrier before billing.
• Aviation liability insurers: These carriers operate outside standard health insurance billing. They may require their own claim forms, with the ICD-10-CM code as supporting documentation rather than a primary billing element.
• Verify insurance eligibility before treatment. When a patient presents after an aircraft crash, confirm active coverage with the correct payer first. Aviation accidents often involve several payers at once, and the wrong one delays the whole claim.

Prior authorization for trauma surgery after an aviation crash is typically handled by the treating facility under emergent care exemptions. For non-emergency follow-up care, standard prior authorization rules apply by payer.

Common claim denial reasons for V95.21XA

Aviation trauma claims denied on the external cause code are almost always correctable. The denial patterns are predictable, and catching them at the point of coding prevents the rework. A wider denial management routine gives you the process for working the ones that still slip through.

• Used as primary diagnosis instead of supplemental code. This is the most common denial. V95.21XA must always follow an injury code. Claims that lead with V95.21XA are rejected by payer edits before human review.
• Wrong 7th character. V95.21XD submitted on an initial emergency department visit. The date of service relative to the accident date and the physician note must support the character chosen. Payers cross-reference date of accident with 7th character selection during automated review.
• Missing accompanying injury code. A claim with only V95.21XA and no S- or T-range primary code will fail medical necessity review. Every injury the physician treated must be coded and sequenced first.
• Insufficient documentation of aircraft type. If the medical record only says “aircraft accident” or “plane crash” without specifying private fixed-wing, payer auditors may deny specificity. A physician query to clarify the aircraft type in the note resolves this before claim submission.
• Incorrect code selection (helicopter versus fixed-wing). V95.01XA submitted when the patient was in a fixed-wing aircraft. The error typically starts with a coder defaulting to the first aviation code they locate rather than reading the full descriptor.
• Sequela coded without a documented late effect. V95.21XS requires explicit physician documentation linking the current condition to the prior crash. Without that link in the note, XS is unsupported and the claim is denied for lack of medical necessity.

Reviewing the electronic remittance advice on a denied aviation claim shows which problem caused it. The candidates are a sequencing error, a 7th-character error, or insufficient documentation. Each denial type carries a distinct CARC code that points to the specific fix.

Related ICD-10 codes and crosswalk references

Coding an aviation trauma case often requires multiple codes working together, and V95.21XA is only one part of the claim. The table below maps the codes most commonly needed when documenting a private fixed-wing aircraft crash. Consult the AAPC Codify ICD-10-CM lookup to verify current descriptors and any active Excludes notes before finalizing the claim.

The chart note from the initial encounter should be referenced in every subsequent note. That reference is what supports the 7th character a coder assigns on the later visits.

How Pabau keeps external cause codes in the right claim sequence

Most coding teams find a sequencing error only when the remittance advice arrives. By then the claim has been rejected, someone has to reopen the chart, and the correction goes back out weeks after the encounter.

Pabau is practice management software that keeps coding in the same record as the appointment and the treatment note. Coders build the diagnosis line-up on the claim itself, so the injury code and V95.21XA stay in the order the payer expects. Claim preparation flags a missing required code field before the claim leaves the practice.

Denials are then reported back against the codes that produced them. A billing lead can see whether V95.21 claims keep failing on the 7th character or on thin documentation. The fix then lands in the coding workflow rather than in a spreadsheet nobody else reads.

Reduce coding errors on aviation and trauma claims

Pabau’s claims management workflows help coding teams pair external cause codes correctly, flag missing injury codes before submission, and track denial patterns across your practice.

Book a demo

Conclusion

Aviation trauma claims fail at the external cause code more often than at the injury level, and those failures are avoidable at the desk. The 7th character carries the most weight, because a payer can test it against the date of service without reading a single note.

So treat V95.21XA as the second line on the claim, and query the physician whenever the record says only “aircraft crash”. A query costs a few minutes. A denial costs the encounter, the appeal, and every day in between.

Pabau’s claims management software builds the code sequence at the point of documentation. It also reports denial patterns back to the coders who can act on them. Book a demo to see how it handles multi-code trauma claims from the first encounter through to payment.

Continue your research

Need to understand how clearinghouses validate ICD-10 codes before submission? Claim.MD clearinghouse overview explains how real-time eligibility and code validation reduce denials on external cause code claims.

Working through a denied aviation claim? Denial codes in medical billing maps common CARC codes to the specific coding or documentation fix each denial requires.

Want to understand the 837 transaction that carries your ICD-10 codes to the payer? 837 file guide explains how the electronic claim file is structured and where external cause codes appear in the transaction.

Frequently asked questions