The U.S. aircraft register, updated daily
Accidents · NTSB CEN25FA194 · Preliminary: the investigation is not finished

Universal Stinson 108 accident near Farmington, North Carolina, June 3, 2025

On June 3, 2025 at about 3:45 pm local time, a 1946 Universal Stinson 108, registered N40158, was substantially damaged in an accident near Farmington, North Carolina (Sugar Valley Airport). It was a personal flight under general aviation rules (Part 91). 2 people were 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 November 2, 2026. Docket and reports at the NTSB.

What the record shows

Date
June 3, 2025 · about 3:45 pm local time · cases in 2025
Place
Farmington, North Carolina · Sugar Valley Airport · cases near this airport · map
Type
Accident
Injuries
2 people were killed and 1 person was seriously injured.
Weather
visual conditions (good weather)
Aircraft
Universal Stinson 108, built 1946 · all 108s on the register
Registration
N40158 · no longer on the register · serial 108-88
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

On June 3, 2025, about 1145 eastern daylight time, a Universal Stinson 108 airplane, N40518 was destroyed when it was involved in an accident near Farmington, North Carolina. The pilot and one passenger were fatally injured, and one passenger was seriously injured. The airplane was operated under the provisions of Title 14 Code of Federal Regulations Part 91 as a personal flight. The airplane departed runway 2 at the Sugar Valley Airport (5NC2), Mocksville, North Carolina, and flew around the traffic pattern. Upon turning base leg for runway 2, the UNICOM operator, who was looking out the airport office window facing southeast, advised the pilot that there was a turtle on the runway. According to the UNICOM operator, the pilot landed about 1,400 ft down the 2,424 ft runway and then lifted the right main wheel to avoid the turtle. The UNICOM operator stated that she heard the pilot advance the throttle after he raised the right wheel. The airplane left her point of view, and she was unable to see the airplane after that. A man cutting the grass at the end of runway 2 reported that he saw the turtle on the runway and the pilot raised the right wheel to avoid the turtle. After that, the wings began to rock back and forth. Then the airplane took off again, but he lost site of the airplane when it passed behind a hangar. The airplane disappeared just over the trees on the northeast side of the runway and then he heard a loud crash and saw smoke. The airplane impacted a heavily forested area about 255 ft northeast of the departure end of runway 2. A post impact fire ensued. The airplane came to rest on a heading of about 100°. The airplane was wedged between several trees and remained in one piece except for a few pieces of fabric that were found in an adjacent stream next to the accident site. The fabric on the fuselage, cowling, and wings was completely burned off and the airplane frame was visible. The fabric on the vertical stabilizer and horizontal stabilizer was intact; however, parts of the vertical stabilizer fabric were melted. The metal rudder and elevator were not fire damaged. The airplane came to rest on its left side with the left wing folded underneath the fuselage and the right wing bent aft. Control cable continuity was confirmed to the rudder, elevator, and right aileron. Due to impact damage, cable continuity could not be confirmed to the left aileron or flaps. The airplane wreckage and engine were retained for further examination.

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. Unknown or undetermined during unknown defining event

The aircraft

  • Last inspection: annual inspection, August 1, 2024
  • Maximum gross weight: 2,400 lb
  • Seats: 4
  • Landing gear: fixed
  • Fire on the ground

The flight

  • Flight plan: none
  • Runway 02, 2,424 ft by 36 ft

Weather at the time

  • Light: daylight
  • Wind: from 200° at 5 knots
  • Visibility: 10 statute miles
  • Sky: overcast at 4,100 ft
  • Temperature: 77°F (25°C), dew point 54°F (12°C)
  • Altimeter: 30.23 inHg
  • Observation at 11:54 am from KINT, 15 miles away

Weather report (METAR): KINT 031554Z 20005KT 10SM OVC041 25/12 A3023

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers11

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.

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/CEN25FA194.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

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 does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.