The U.S. aircraft register, updated daily
Accidents · NTSB ERA22LA125 · Final report

Cirrus Design CORP SR22 accident near Pinehurst, North Carolina, February 9, 2022

On February 9, 2022 at about 10:48 pm local time, a 2003 Cirrus Design CORP SR22, registered N987AA, was substantially damaged in an accident during approach (VFR pattern final) near Pinehurst, North Carolina (Moore County airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The in-flight encounter while on final approach with high-speed trailing vortices from a military helicopter, resulting in abnormal runway contact. Contributing to the accident was the Cirrus pilot’s incorrect selection of the common traffic advisory frequency on the aircraft’s radio.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
February 9, 2022 · about 10:48 pm local time
Place
Pinehurst, North Carolina · Moore County · map
Type
Accident
Injuries
No one was hurt; 2 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Cirrus Design CORP SR22 NO SERIES, built 2003
Registration
N987AA · no longer on the register · serial 0513
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The Cirrus pilot reported making a radio call on what he thought was the published common traffic advisory frequency (CTAF) when the flight was 10 miles away, then continued to the airport for a straight-in approach to runway 23 making radio calls. During the same time frame, a flightcrew member of an Army helicopter announced on the CTAF when their flight was on 10, 5, and 2 nautical mile final for runway 5. The Cirrus pilot indicated that he did not hear any communication on the CTAF and he was unable to activate the runway lights using the CTAF. When the Cirrus flight was between 2 and 3 miles from the airport, he saw a helicopter at the opposite end of the runway moving to the east, adding that the sun was in his eyes which was “definitely a factor.” He did not hear the helicopter on the selected CTAF frequency and made a radio call on the CTAF that he was on short final approach. A flightcrew member of the military helicopter reported they did not hear any advisory call from the airplane and after they spotted it, the IP took the controls and turned to the right (east) to avoid a collision. The Cirrus pilot indicated that after flying over the airport property fence, he looked to his left and noted a military helicopter several hundred feet above his altitude. He continued his descent to runway 23 and when the flight was about 15 to 20 ft AGL the flight encountered, “very strong turbulence” which caused the left wing to drop. He recovered from that and then when the flight was between 5 and 10 ft AGL encountered another round of “very strong turbulence” which made the right wing contact the runway resulting in substantial damage to the wing. The airplane went to the right and skidded into the grass. The military helicopter continued to the east and reported that since they could not affect the situation continued with the training. A short audio recording of the CTAF recorded a flightcrew member of the military helicopter announcing they were on a 2 mile final for runway 5, followed by an announcement that they were departing to the east off of runway centerline. Postaccident examination of the radios of the Cirrus airplane revealed the pilot had selected the #2 radio to transmit, which was set to 122.700 MHz. That frequency was the departure airport CTAF. The accident airport published CTAF was 123.05MHz.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Loss of control in flight during approach (VFR pattern final)
  2. Abnormal runway contact during landing (flare/touchdown)
  3. Inflight upset during approach (VFR pattern final) defining event

The NTSB's findings

  • Personnel issues › Task performance › Use of equip/info › Use of equip/system › Pilot
  • Environmental issues › Conditions/weather/phenomena › Turbulence › (general) › Effect on operation

Pilot

  • Certificate: private
  • Ratings: single-engine land; instrument: airplane
  • Flight time: 1,468.6 hours in all; 1,369 in this make and model; 65 in the last 90 days; 12.5 in the last 30 days; 1,469 as pilot in command
  • Last flight review: June 25, 2020
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 2,409 hours
  • Last inspection: annual inspection, August 6, 2021
  • Maximum gross weight: 3,400 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Continental IO-550-N7B (piston); 2,587 hours total
  • Fire on the ground

The flight

  • Departed from: HRJ Erwin NC at 10:32 pm
  • Flight plan: none
  • Runway 23, 6,503 ft by 150 ft

Weather at the time

  • Light: dusk
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 50°F (10°C), dew point 30°F (-1°C)
  • Altimeter: 29.98 inHg
  • Observation at 5:56 pm from KSOP

Weather report (METAR): KSOP 092256Z AUTO 00000KT 10SM CLR 10/M01 A2998 RMK AO2 SLP159 T01001006 TSNO

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

8 documents, released by the NTSB on May 26, 2022. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.