Db Aerocopter LTD AK1-3 accident near Prineville, Oregon, May 17, 2025
On May 17, 2025 at about 6:34 pm local time, a 2022 Db Aerocopter LTD AK1-3 (helicopter), registered N163AK, was substantially damaged in an accident near Prineville, Oregon. It was an instructional flight under general aviation rules (Part 91). 1 person was killed and 1 person was seriously injured. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The NTSB has not yet published a probable cause for this accident. Investigations usually take one to two years; this page updates when the final report is released.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- May 17, 2025 · about 6:34 pm local time
- Place
- Prineville, Oregon · map
- Type
- Accident
- Injuries
- 1 person was killed and 1 person was seriously injured.
- Weather
- visual conditions (good weather)
- Aircraft
- Db Aerocopter LTD AK1-3, built 2022
- Registration
- N163AK · registry record · serial 0097
- Damage
- Substantial damage
- Flight
- Instructional flight · general aviation rules (Part 91)
The NTSB's narrative preliminary · quoted from the NTSB record
On May 17, 2025, about 1134 pacific daylight time, a DB Aerocopter Ltd., AK1-3, N163AK, sustained substantial damage when it was involved in an accident near Prineville, Oregon. The private pilot undergoing instruction was fatally injured, and the flight instructor sustained serious injuries. The helicopter was operated as a Title 14 Code of Federal Regulations part 91 instructional flight. The helicopter was not equipped with an ADS-B transponder, and radar coverage was not available in the area, however the initial departure along with segments of the accident sequence were captured by multiple security cameras in the vicinity of the airport. A camera operated by Prineville Municipal Airport (S39), Prineville, Oregon, indicated that the helicopter took off from runway 29, about 1036. For the next hour it performed a series of takeoffs, landings and low hover maneuvers while remaining in the right traffic pattern for runway 29, with the last takeoff occurring at 1123. A north-facing camera located at a business about 1,800 ft northeast of runway 29 midfield, captured the helicopter passing from left to right at 1134. It then began a rapid descent while in a slight nose-down attitude. The nose then pitched up, and the helicopter struck the ground, accompanied by a large dust cloud (figure 1). White fragments could then be seen being ejected from the initial impact point in an arcing trajectory to the east. Figure 1 – Composite of Security Video Footage (video courtesy Centerline Drilling Inc.) A witness, who was travelling west in her automobile along a road north of the airport observed the helicopter pass in front of her from right to left. She said the helicopter was travelling slower than she would have expected, and it then rapidly began to descend, striking the ground in a field to her left. She stated that the helicopter was not trailing smoke or vapor prior to the accident, and this observation was corroborated by the video footage. The helicopter came to rest in a field, about 4,000 ft north of the approach end of runway 29, in an area that corresponded to the midfield downwind segment of the right traffic pattern. The first identified point of impact was comprised of longitudinal slash marks in the soil, followed by a ground disruption that contained fragments of the tail rotor blades. Debris continued on a heading of about 120°, to a 15-ft-long, and 6-ft-wide soil disruption that matched to the general outline of the helicopter. The disruption contained the complete main skid assembly, which had been compressed such that the skids were level with the upper frame. The debris field, which contained fragments of windshield and cabin contents, continued on the same heading to the main cabin about 60 ft downrange. At the time of examination, the helicopter was sitting upright, but according to first responders it was lying on its right side upon their arrival. The cabin was generally intact, with the main transmission and engine remaining attached to the airframe. Two main rotor blades were still attached to the head of the transmission mast, with the third located about 20 ft south. The tail rotor gearbox assembly was located a further 170 ft downrange, with three sections of the tail tailcone located a further 100 ft northeast. The furthest component in the debris field was the tailrotor driveshaft, which was found 410 ft beyond the initial impact point. (figure 2) Figure 2 – Debris field Weather at the time of the accident included light rain with wind from 280° at 7 knots, gusting to 14 knots.
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
- Collision with terrain or object (not controlled flight into terrain) during unknown defining event
The aircraft
- Last inspection: condition inspection
- Seats: 2
- Landing gear: fixed
The flight
- Flight plan: none
- Runway 29, 5,405 ft by 75 ft
Weather at the time
- Light: daylight
- Wind: from 280° at 7 knots, gusting 14
- Visibility: 9 statute miles
- Sky: broken clouds at 4,300 ft; a few clouds at 2,500 ft
- Temperature: 50°F (10°C), dew point 45°F (7°C)
- Altimeter: 29.88 inHg
- Observation at 11:56 am from KS39, 11 miles away
Weather report (METAR): METAR KS39 171835Z AUTO 28007G14KT 9SM -RA FEW025 BKN043 OVC075 10/07 A2988 RMK AO2=
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The NTSB has not released the docket for this case yet. The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), is usually released when the investigation is nearly complete, and the list here is refreshed when it appears. Check at the NTSB.
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.
