ICD code V97.32XA – Person struck by drone

Key takeaways

V97.32XA is the ICD-10-CM external cause code for a person on the ground injured by a rotating aircraft propeller, initial encounter.

It is never the principal diagnosis. Report the injury code first, then V97.32XA to explain how the injury happened.

The placeholder X fills the sixth character, so the string V97.32A without it is not a valid code.

Use V97.32XD for routine visits during healing and V97.32XS when treating a late effect of the propeller injury.

No code in V95-V97 names drones or unmanned aircraft, so a drone injury needs an External Cause Index lookup.

ICD-10 Code V97.32XA: official description and code definition

ICD-10 Code V97.32XA describes a person on the ground injured by an aircraft’s rotating propeller in an air transport accident, initial encounter. It is a valid, billable ICD-10-CM code for FY2027, which runs from October 1, 2026 to September 30, 2027.

What V97.32XA covers and what it does not

V97.32XA applies when someone who is not aboard the aircraft is struck by its turning propeller. Typical patients are ramp agents, refuelers, aircraft marshals, maintenance crew, and bystanders on an airstrip.

The code records the mechanism only. The injury itself, such as a laceration, fracture, or traumatic amputation, takes its own code from Chapter 19.

These situations belong to other codes:

• An object falling from the aircraft: A person on the ground hit by something dropped or shed from an aircraft is coded V97.31XA.
• A jet engine intake: A person on the ground drawn into a jet engine is coded V97.33XA.
• Other ground injuries: Any other injury to a person on the ground in an air transport accident is coded V97.39XA.
• Boarding or alighting: Injuries while getting on or off an aircraft are coded V97.1XXA.
• Aircraft occupants: People aboard the aircraft are coded elsewhere in V95-V97, never in the V97.3 subcategory.
• Drones: ICD-10-CM has no drone code, so a drone injury follows the External Cause Index rather than defaulting to V97.32XA.

Two questions settle the code: where the patient was when the aircraft injured them, and what struck them.

Breaking down the code structure: V97, .32, X, and A

Each character in V97.32XA has a fixed meaning under ICD-10-CM conventions. Reading the code left to right tells you the accident type, the victim, the mechanism, and the encounter.

The X carries no clinical meaning. V97.32 has only five characters, so the X fills the sixth position before the 7th character is added. Without it, the string reads V97.32A, which is not a valid code and gets rejected.

7th character options: XA, XD, and XS for V97.32

The 7th character on V97.32 tracks the patient’s treatment phase for the propeller injury. It should match the 7th character on the injury code it explains.

The treatment phase sets the switch from A to D, so a long course of active care keeps the A character. For a sequela visit, code the late effect first. The injury code with S and V97.32XS follow it.

How V97.32XA fits into the external cause coding sequence

Per the CMS ICD-10-CM Official Guidelines for Coding and Reporting, external cause codes are never the principal or first-listed diagnosis. A propeller-strike encounter follows four steps.

1. Code the injury first. Assign the Chapter 19 code for each injury treated, such as a laceration, fracture, or amputation code. This is the principal or first-listed diagnosis.
2. Add V97.32XA after the injury codes. It explains how the injuries happened and does not describe them. For how this fits the wider claim, see how medical billing works end to end.
3. Add place, activity, and status codes once. Report the Y92 place of occurrence, Y93 activity, and Y99 external cause status codes at the initial encounter only, when the record documents them.
4. Apply the external cause hierarchy. When several external causes apply, transport accidents come first. Only abuse, terrorism, and cataclysmic event codes outrank them.

Worked example: A 41-year-old ramp agent walks into the rotating propeller of a taxiing turboprop and sustains a laceration of the left forearm. The coder reports S51.812A (laceration without foreign body of left forearm, initial encounter) first.

V97.32XA follows as the external cause. Y92.520 (airport as the place of occurrence) and Y99.0 (civilian activity done for income or pay) complete the set.

V97.32XA vs. V97.31XA, V97.33XA, V97.39XA, and V97.89XA

The V97.3 subcategory splits ground injuries by mechanism, so the documented mechanism decides the code. The table uses the official descriptors.

If the note says only that the patient was struck by an aircraft, query the provider for the mechanism. That answer decides between V97.31XA, V97.32XA, and V97.39XA.

How to code an injury caused by a drone

ICD-10-CM has no code that names drones or unmanned aircraft anywhere in V95-V97, and FY2027 added none. Do not assign V97.32XA because a drone has spinning rotors.

Look up the documented mechanism in the External Cause Index and follow its entry. V97.89XA is one candidate the Index may lead to, but confirm it there before you report it.

Documentation requirements for V97.32XA

The provider’s note has to support each part of the code before the coder assigns it. Check the record for these five elements.

• Mechanism: The note names a rotating propeller as the source of the injury and an aircraft as the vehicle involved.
• Patient position: The note shows the patient was on the ground, not aboard the aircraft or boarding it.
• Injury detail: Site, laterality, and injury type support a specific Chapter 19 code.
• Treatment phase: The note states whether care is active treatment, routine healing care, or treatment of a sequela.
• Place, activity, and work status: These support the Y92, Y93, and Y99 codes reported at the initial encounter.

The CDC/NCHS ICD-10-CM official web tool carries the full Tabular List and External Cause Index. When the documentation is ambiguous, query the provider rather than defaulting to a less specific code.

Payer requirements and billing considerations

There is no national requirement to report external cause codes. The official guidelines make them mandatory only under a state reporting mandate or a payer’s own rule. They still encourage voluntary reporting.

Propeller strikes on airport ramps are usually workplace injuries. Workers’ compensation is then typically the primary payer, so confirm the carrier and claim number before you bill a health plan.

A health plan may send an accident questionnaire when the codes point to a possible liable third party. Answering it quickly keeps the claim from sitting in a pended status. Run insurance eligibility verification at follow-up visits too, since coverage can change during a long recovery.

Common claim denial reasons for V97.32XA

Most rejections on this code trace back to format, sequencing, or payer errors that are fixable before submission. The table applies denial management best practices to V97.32XA.

A clean claim review before submission catches the format and sequencing errors in this table. Spot-check exported claims, because some billing exports strip the X placeholder. If a claim still comes back, its denial reason code narrows down which of these errors to fix first.

How Pabau keeps V97.32XA claims moving

A propeller-strike claim carries several codes from the provider’s note: the injury code, V97.32XA, and the Y92, Y93, and Y99 codes. Retyping them into a separate billing system is where a dropped X or a misordered code slips in.

Pabau, the practice management platform we build, carries the codes already on the patient’s record into the claim. US practices then submit and track those claims through Claim.MD without leaving Pabau.

Your billing team follows each claim’s status with claims management in Pabau, next to the patient’s appointments and records. A pended accident or workers’ compensation claim gets chased sooner.

Submit and track injury claims in one place

Pabau carries the codes on the patient record into each claim, then submits and tracks it through Claim.MD. Your team follows every V97.32XA claim from one dashboard.

Book a demo

Conclusion

V97.32XA is narrow by design. It records one mechanism, a person on the ground struck by a turning aircraft propeller. Code the injury first, keep the X, and match the 7th character to the treatment phase.

When the record describes a drone or a different mechanism, let the External Cause Index decide instead of stretching this code. To see how Pabau moves those codes from the note to a tracked claim, book a demo.

Continue your research

Need to understand how denial codes work? Denial codes in medical billing explains the most common CARC reason codes and how to act on them when a claim comes back.

Coding the work status for a ramp injury? ICD-10 code Y99.8 covers the external cause status codes and when Y99.0 applies instead.

Want to see how electronic remittance works? Electronic remittance advice (ERA) covers how 835 ERAs communicate denial reasons and adjustment codes back to the practice after claim adjudication.

Coding a patient who was aboard the aircraft? ICD-10 code V95.21XA covers an occupant injured in a private fixed-wing aircraft crash, the other side of the V95-V97 split.

Frequently asked questions